3GPP Study on Modernization of Specification Format and Procedures for 6G (6GSM)

Key Takeaways

• Current 3GPP specs rely on Word DOCX workflow.
• Growing spec size causes delays, conflicts, and tooling limits.
• Study evaluates Markdown, AsciiDoc, LaTeX, and structured DOCX.
• Git version control could improve traceability and parallel work.
• Automated validation tools may reduce editorial workload.

Summary

3GPP has launched a study (TR 21.802) to modernize the format and procedures used to develop its mobile standards as the industry prepares for 6G. The study highlights that the long‑standing Word‑based, document‑centric workflow is straining under increasingly large and complex specifications, leading to delays and limited automation. It evaluates alternative markup formats such as Markdown, AsciiDoc, LaTeX, and more structured DOCX, and recommends adopting version‑control systems like Git and automated validation tools. The goal is to improve traceability, reduce editorial effort, and keep the standards process scalable for future 6G innovations.

Pulse Analysis

The 3rd Generation Partnership Project (3GPP) has been the backbone of mobile standards for decades, delivering the specifications that enable global roaming and device compatibility. Yet its core authoring process still hinges on Microsoft Word documents and manual change‑request merging, a model that worked well for 4G and early 5G but now shows cracks as specifications swell to thousands of pages. Editors must reconcile overlapping edits, and engineers struggle to trace feature evolution across releases, slowing time‑to‑market for new capabilities.

The 6GSM study (TR 21.802) surveys several modern alternatives, from plain‑text markup languages like Markdown and AsciiDoc to LaTeX for mathematically dense sections, and even constrained DOCX variants that preserve legacy compatibility. Text‑based formats separate content from presentation, making them ideal for Git‑style version control, granular diff tracking, and automated linting. By treating specifications as code, 3GPP could introduce continuous‑integration pipelines that validate change requests for formatting, reference integrity, and structural consistency before human review, dramatically cutting editorial overhead.

If 3GPP adopts these practices, the ripple effect will be felt across the entire mobile ecosystem. Faster, more transparent standard updates lower development risk for chipset makers, device OEMs, and network operators, accelerating the rollout of 6G services such as ultra‑low‑latency IoT and terahertz‑band communications. Transitioning to new tools will require training and careful migration to protect existing contributions, but the long‑term gains in scalability, reproducibility, and cross‑industry collaboration make modernizing the specification workflow a strategic imperative for the next generation of wireless innovation. Stakeholders are already piloting Git‑based repositories for draft releases.