3GPP-Specifications-Tour

 

Link for 5G-NR Specification series : https://www.3gpp.org/DynaReport/38-series.htm

Link to LTE Specification series : https://www.3gpp.org/DynaReport/36-series.htm

There are usually two types of documents available once you go in the XX Series (eg. 38 Series for NR)

TS: Technical Specification [These are the final versions of the specifications that are published]

TR: Technical report [ TR Contains discussion related to a specific topic which needs to be finalized in the TS]

I believe below three items should help you navigate through the specifications.

Decoding the Specification Numbering
How to Navigate through the Specifications and Referencing

How to read ASN.1 Encoding for RRC Messages

 1. Decoding the Specification Numbering

• Decoding Specification numbering can be simple but might also quickly turn into complex decoding, lets get started with the basics of the spec numbering.
• All 3GPP specifications(UMTS and later release) have a specification number consisting of 5 digits. (e.g. 36.101).
• 
  
• The first two digits define the series followed by 3 more digits that relate to different specifications within the series.
• 
  
• The 3GPP Specifications are stored on the file server as zipped MS-Word files.  So when you go and download a specification you will get a zipped document with an alphanumeric.zip file.
• Those filenames have a reason behind them and are named as per the following defined structure by 3GPP.

SM[-P[-Q]]-V.zip

Each character fields have the following significance …

• S = series number – 2 characters (see the table above)
• M = mantissa (the part of the spec number after the series number) – 2 or 3 characters (see above)
• P = optional part number – 1 or 2 digits if present
• Q = optional sub-part number – 1 or 2 digits if present
• V =  – see the fifth example below)

So for example, I will use RRC RRC Specification for 5G-NR as an example to navigate the specs.

First Lets download the Specs for NR RRC from the link below, I will download the latest spec available at the time of the writing, once I clicked the version number it will download a zip file and it should look similar to 38331-g10.zip, and after unzipping 38331-g10.docx  now it’s easier to understand when you download once since you know which version of the specification it is, but if you have a number of versions it will get difficult to understand which folder belongs to which specification.

As per the above structure shown above, it will translate into 38.331- V 16.1.0

Once you have downloaded the spec, and open it we will see a version number associated with each specification, number, for example

3GPP TS 38.331 V16.1.0

There is a pattern for the version number i.e  V x.y.z

X – First digit :

• 1    presented to TSG for information;
• 2    presented to TSG for approval;
• 3    or greater indicates TSG approved document under change control.
• y    the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
• z    the third digit is incremented when editorial only changes have been incorporated in the document.
• 
  

2. How to Navigate through the Specifications and Referencing

3GPP specifications have a lot of references to other specifications, it’s always a good idea to go through the topic in the specification first and then go to the referring specifications for more details and clarifications on that topics. Specifications are interconnected with other specs.

There are two ways how references are made in the specs

1. Same document with reference of a section number.
2. External document Specification number with or without a section number.

Below is an example from the 38.331 Specification referring to the reference number with Section number in the same document and with a Clause and section number in an external document.

Almost every Topic in the specification has local references or references pointing to external documents. So just need to have multiple documents open to read through a topic.

3. How to read ASN.1 Encoding for RRC Messages