5G MAC Procedures Index
The procedures index is the route map for procedural navigation. Instead of entering from a definition page, these readers want to know which MAC procedures exist and where to go next.
This page should stay structured and navigation-heavy. It is most useful once the MAC cluster grows, because it gives readers a single map of the operational procedures without turning the pillar page into a giant index.
| Page type | Index and navigation page |
|---|---|
| Main use | Find the right procedure page quickly |
| Best use | Workflow-based navigation instead of definition-based navigation |
| Design rule | Stay light, linked, and grouped |
What this index should contain
The scope of the page.
The procedures index should list the main MAC procedures and route readers to the right child page. It is not meant to duplicate every procedure explanation.
The page becomes more useful as the library expands because it gives a map organized by action, not just by terminology.
Recommended procedure groups
The first organizational model to use.
| Procedure group | Representative pages |
|---|---|
| Access procedures | Random access, timing advance |
| Retransmission and reliability | HARQ |
| Demand and reporting | SR, BSR, PHR |
| Monitoring and efficiency | DRX, energy-saving behavior |
| Advanced procedures | Small data transmission, SCG activation, RACH-less handover first PUSCH |
Best navigation paths into the procedure library
How to use the index when starting from a problem or task.
| Starting point | Best first procedure page |
|---|---|
| Initial access or re-entry issue | Random access |
| Queued uplink data but weak service | Scheduling Request, then BSR |
| Uplink grant exists but outcome is poor | PHR, timing advance, then HARQ |
| Throughput is unstable | HARQ, then multiplexing and prioritization |
| Activity visibility is unclear | DRX, then energy-saving behavior |
How to keep the procedures index useful
Simple design rules.
- Group procedures by operational purpose
- Keep summaries short and link outward
- Use the page as a map, not a duplicate tutorial
- Add new advanced procedures here as the section expands
FAQ
Why build a MAC procedures index?
Because workflow-based navigation needs a single map of the MAC procedures rather than a list of definitions.
Should procedure detail live on this page?
No. The page should stay concise and route readers to the proper child pages.
When does this page become especially useful?
As the MAC cluster grows beyond a small set of core pages and needs stronger navigation support.