# Analysis of 26 Series Specifications in Preparation of 6G Specs Modernization

## 1. Introduction

This document provides SA4 with an initial assessment of SA4-controlled specifications (26 series) in the context of the 6G Specs Modernization (6GSM) activity. The 6GSM initiative is exploring modernization of specification development workflows, including review of current spec formats and working practices, with progress captured in TR 21.802. This contribution focuses specifically on the current state of 26 series specifications and their alignment with 6GSM findings.

## 2. Potential Outcomes of 6GSM Work

The definitive target format for Rel-20 specifications remains unclear. Options under consideration include:

- Maintaining current DOCX format (potentially with restrictions)
- Moving to streamlined formats: Markdown, ASCIIDoc, LaTeX, or OpenDocument

A key open question is whether new formats and working methods will apply only to newly developed specifications or also to existing specifications continuing in Rel-20 and beyond. This assessment aims to provide SA4 with visibility on technical debt present in current specifications.

## 3. Issues Observed in the 26 Series

An initial assessment was conducted on latest SA4 specifications from Rel-19 using Python scripting to extract structural insights and identify improvement areas.

### 3.1 DOC vs. DOCX

**Finding:** All specifications are now in DOCX format except TS 26.445, which has been split into subparts with only recently updated parts migrated to DOCX.

**Recommendation:** Convert all TS 26.445 subparts to DOCX for consistency. Consider consolidating subparts into a single DOCX file, as handling speed issues are less problematic than when the series was originally created.

### 3.2 Tables

**Finding:** Tables can slow down word processor performance. TS 26.114, TS 26.253, and TR 26.930 include numerous tables, but their size and quantity remain well below "mega tables" seen in other 3GPP specifications.

**Assessment:** Performance impacts are limited and not a significant issue in the 26 series.

### 3.3 Embedded Images

**Finding:** Embedded images cause MS Word lag, particularly in Print view. Key observations:

- TS 26.447 contains >1,000 embedded images
- Other specifications contain several hundred images
- Some images included at higher resolution than necessary
- Large file sizes noted: TR 26.998, TS 26.506, and TR 26.804 each exceed 50MB

**Recommendation:** Review specifications to identify images that could be replaced with lower-resolution versions. All specifications could benefit from such optimization.

### 3.4 Embedded Objects

**Finding:** 26 series specifications feature broad range of embedded objects with the following distribution:

- vsdx: 357
- bin: 235
- sldx: 46
- vsd: 41
- docx: 19
- vsdm: 10
- doc: 1

Most objects are embedded as OLE objects, presenting challenges when working across formats other than DOCX.

**Recommendation:** 
- Streamline range of embedded formats with preference for interoperable standards
- Move away from Visio (not all delegates have access)
- Adopt "Diagrams as Code" approach
- Use widely supported formats like SVG and PNG to enhance accessibility and future-proof specifications

### 3.5 Relationships / Template

**Finding:** Templates with 3GPP styles (e.g., 3GPP_70.dot) are typically referenced as local files.

**Recommendation:** Switch to online version to eliminate editing warnings about missing templates and make contribution process smoother. Templates do not contain macros and are therefore safe to use online.

### 3.6 Equations

**Finding:** 
- Some equations remain in legacy Equation Editor format (deprecated due to unresolvable security vulnerabilities)
- Some equations exist only as images and cannot be edited directly in MS Word

**Recommendation:** 
- Migrate legacy equations to modern OMML format used in DOCX files
- Identify and convert image-based equations to editable formats to improve maintainability and alignment with 3GPP document best practice

## 4. Summary and Recommendations

The review has identified several areas where technical debt has accumulated in SA4 specifications. These issues should ideally be addressed as part of Rel-19. While MCC may handle some aspects, spec rapporteurs are encouraged to examine their own specifications and consider required updates or clean-up actions.

The source is also assessing feasibility of converting 3GPP specifications from DOCX to Markdown format, with updates to be shared as progress is made.