5G MAC Release 18 Additions
Release 18 coverage should exist in the MAC section, but it should not overload the pillar page. This page gives modern readers a focused entry point into the advanced features and topic groups that extend beyond the baseline MAC library.
Use this page as the modern MAC roadmap. It is intentionally organized as a release-aware navigation and summary page, sending readers into advanced child pages instead of trying to explain every new behavior inline.
| Page type | Release-aware navigation and summary page |
|---|---|
| Why it matters | Modern readers expect current MAC scope, not only baseline release material |
| Best use | Readers tracking evolving NR behavior |
| Main use | Organize and route advanced MAC topics cleanly |
What this page should do
The role of the Release 18 page in the library.
This page should act as the modern-feature entry point, not as a full spec dump. It proves the section is current and gives advanced readers a clean way to branch into the exact feature they need.
That approach protects the pillar page from overload while still making the section feel current and standards-aware.
Advanced feature groups to organize here
The key clusters this page should route to.
| Feature group | Suggested child pages |
|---|---|
| Direct communication and service models | Sidelink MAC, MBS MAC |
| Advanced procedure support | Positioning support, small data transmission |
| Advanced control and deployment behavior | SCG activation, FR2 UL gap behavior, energy-saving behavior |
| Specialized mobility behavior | First PUSCH in RACH-less handover |
How to use this page without turning it into a spec dump
The practical design model for the release page.
A release page becomes weak when it tries to hold every feature detail inline. The better pattern is short summaries, a clear feature-group map, and strong routing into dedicated advanced pages.
That model keeps the section current while preserving page purpose. Readers can enter through the release lens, then move directly into the exact feature that needs real detail.
| Page task | What belongs here | What belongs on child pages |
|---|---|---|
| Release summary | Feature family overview and why it matters | Procedure-specific or decoder-level detail |
| Navigation | Strong grouped links to advanced topics | Deep examples, edge cases, and troubleshooting |
| Scalability | A place to add new release-aware clusters | Feature-specific reference content |
Design rules for a good release page
How to keep it useful.
- Summarize feature families instead of copying full spec-level detail
- Use strong outbound linking to child pages
- Keep the page current-focused and easy to scan
- Use it to support future release-driven growth without destabilizing the pillar page
FAQ
Why have a separate Release 18 page for MAC?
Because it gives advanced readers a clean modern entry point without overloading the main MAC pillar page.
Should full Release 18 detail live here?
No. This page should summarize feature groups and route readers to dedicated advanced pages.
Who is this page for?
Readers tracking current NR feature scope and modern MAC behavior.