Add files using upload-large-folder tool

marked/Rel-18/25_series/25111/raw.md

@@ -0,0 +1,606 @@
+
+
+# 3GPP TS 25.111 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+![5G Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Measurement Unit (LMU) performance specification; User Equipment (UE) positioning in UTRAN (Release 18)**
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+---
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+UMTS, radio
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                   |           |
+|---------------------------------------------------|-----------|
+| Foreword .....                                    | 4         |
+| Introduction .....                                | 5         |
+| 1 Scope.....                                      | 6         |
+| 2 References.....                                 | 6         |
+| 3 Definitions and abbreviations .....             | 6         |
+| 3.1 Definitions.....                              | 6         |
+| 3.2 Abbreviations .....                           | 6         |
+| 4 General.....                                    | 7         |
+| 4.1 Main concepts .....                           | 7         |
+| 4.2 LMU Classes.....                              | 7         |
+| 4.3 U-TDOA architecture.....                      | 7         |
+| 5 LMU radio characteristics.....                  | 8         |
+| 5.1 Frequency bands.....                          | 8         |
+| 5.2 Channel arrangement.....                      | 8         |
+| 5.3 Reference sensitivity level .....             | 9         |
+| 5.4 Dynamic range .....                           | 9         |
+| 5.5 Adjacent Channel Selectivity (ACS).....       | 9         |
+| 5.6 Blocking characteristics .....                | 9         |
+| 5.7 Intermodulation characteristics .....         | 13        |
+| 5.8 Spurious emissions.....                       | 14        |
+| 6 LMU measurement requirements.....               | 15        |
+| 6.1 General .....                                 | 15        |
+| 6.2 RRC States supported.....                     | 15        |
+| 6.3 Maximum response times.....                   | 15        |
+| 6.4 Nominal time accuracy.....                    | 15        |
+| 6.5 Multipath scenarios .....                     | 16        |
+| 6.6 Moving scenario.....                          | 16        |
+| 6.7 Cross correlation .....                       | 16        |
+| <b>Annex A (informative): Change history.....</b> | <b>17</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- Introduction
+
+In order to ensure correctness and consistency of the specifications (i.e., technical specifications and technical reports) under responsibility of the Technical Specification Groups (TSG) of the 3<sup>rd</sup> Generation Partnership Project (3GPP), clear, manageable and efficient mechanisms are necessary to handle version control, change control, document updating, distribution and management.
+
+Also, the fact that the specifications are/will be implemented by industry almost in parallel with the writing of them requires strict and fast procedures for handling of changes to the specifications.
+
+It is very important that the changes that are brought into the standard, from the past, at present and in the future, are well documented and controlled, so that technical consistency and backwards tracing are ensured.
+
+The 3GPP TSGs, and their sub-groups together with the Support Team are responsible for the technical content and consistency of the specifications whilst the Support Team alone is responsible for the proper management of the entire documentation, including specifications, meeting documents, administrative information and information exchange with other bodies.
+
+# --- 1 Scope
+
+The present document establishes the Location Measurement Unit (LMU) minimum RF characteristics of the FDD mode of UTRA.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 25.104: “Base Station (BS) radio transmission and reception (FDD)”.
+- [2] 3GPP TS 45.004: “Modulation”.
+- [3] 3GPP TS 25.141: “Base Station (BS) conformance testing (FDD)”.
+
+[4] 3GPP TR 25.942: “Radio Frequency (RF) system scenarios”.
+
+[5] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”.
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [5].
+
+**Mean power:** When applied to a W-CDMA modulated signal this is the power (transmitted or received) in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode. The period of measurement shall be at least one timeslot unless otherwise stated.
+
+NOTE: The roll-off factor  $\alpha$  is defined in clause 6.8.1 of [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [5].
+
+|      |                                         |
+|------|-----------------------------------------|
+| ACS  | Adjacent Channel Selectivity            |
+| BS   | Base Station                            |
+| BER  | Bit Error Ratio                         |
+| BLER | Block Error Ratio                       |
+| CW   | Continuous Wave (unmodulated signal)    |
+| DL   | Down Link (forward link)                |
+| FDD  | Frequency Division Duplexing            |
+| GSM  | Global System for Mobile Communications |
+
+|        |                                              |
+|--------|----------------------------------------------|
+| LMU    | Location Measurement Unit                    |
+| UARFCN | UTRA Absolute Radio Frequency Channel Number |
+| UE     | User Equipment                               |
+| UL     | Up Link (reverse link)                       |
+| U-TDOA | Uplink Time Difference Of Arrival            |
+| WCDMA  | Wideband Code Division Multiple Access       |
+
+# --- 4 General
+
+## 4.1 Main concepts
+
+The LMU is either located as a separate unit in an existing network or typically located at Node B or BTS sites. Therefore the LMU radio requirements assume that the isolation between the LMU and any other network to be protected is to be at least 30dB.
+
+The communication link between LMU and Stand-Alone SMLC is not a radio interface over the air. Requirements in this document therefore do not cover the situation when the LMU is transmitting over the air on this interface between LMU and Stand-Alone SMLC.
+
+## 4.2 LMU Classes
+
+The requirements in this specification apply to Wide Area LMUs and Medium Range LMUs.
+
+Wide Area LMUs are characterised by requirements derived from Macro Cell scenarios with an LMU to UE minimum coupling loss equal to 70 dB.
+
+Medium Range LMUs are characterised by requirements derived from Micro Cell scenarios with an LMU to UE minimum coupling loss equal to 53 dB.
+
+For Pico Cell scenarios, the location of the BS provides sufficient accuracy; therefore, a Local Area LMUs class is not specified.
+
+## 4.3 U-TDOA architecture
+
+A sample architecture is shown in Figure 3.1 depicting the LMU's relationship with other network elements. The LMU is typically located at the Node B. The LMUs communicate with the SMLC that distributes UTDOA reference data from the reference LMU to other cooperating LMUs when performing UE positioning.
+
+![Figure 3.1: Example of UTDOA deployment. The diagram shows a network architecture with two Node Bs, two RNCs, a Stand-Alone SMLC, an MSC, and an SGSN. Node Bs are connected to RNCs via Iub interfaces. RNCs are connected to the Stand-Alone SMLC via Iupc interfaces. The Stand-Alone SMLC is connected to the MSC and SGSN. LMUs are shown connected to the Stand-Alone SMLC. A vertical arrow on the left indicates that LMUs are 'Typically located at Node B'.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+Figure 3.1: Example of UTDOA deployment. The diagram shows a network architecture with two Node Bs, two RNCs, a Stand-Alone SMLC, an MSC, and an SGSN. Node Bs are connected to RNCs via Iub interfaces. RNCs are connected to the Stand-Alone SMLC via Iupc interfaces. The Stand-Alone SMLC is connected to the MSC and SGSN. LMUs are shown connected to the Stand-Alone SMLC. A vertical arrow on the left indicates that LMUs are 'Typically located at Node B'.
+
+Figure 3.1: Example of UTDOA deployment
+
+# 5 LMU radio characteristics
+
+An LMU performs BS receiver functions to obtain reference data for use at a cooperating LMU. The following clause describes the required LMU radio characteristics when performing these functions.
+
+## 5.1 Frequency bands
+
+- a) The LMU is designed to operate in the following bands:
+
+Table 4.1: Frequency bands
+
+| Operating Band | UL Frequencies<br>UE transmit, LMU receive |
+|----------------|--------------------------------------------|
+| I              | 1920 – 1980 MHz                            |
+| II             | 1850 -1910 MHz                             |
+| III            | 1710-1785 MHz                              |
+| IV             | 1710-1755 MHz                              |
+| V              | 824 – 849MHz                               |
+| VI             | 830-840 MHz                                |
+| VII            | 2500 – 2570 MHz                            |
+| VIII           | 880 – 915 MHz                              |
+| IX             | 1749.9 – 1784.9 MHz                        |
+| X              | 1710-1770 MHz                              |
+
+- b) Deployment in other frequency bands is not precluded
+
+## 5.2 Channel arrangement
+
+The channel arrangement shall be as specified in Section 5.4 of [1].
+
+## 5.3 Reference sensitivity level
+
+Using the reference measurement channel specification in TS 25.104 Annex A [1], the reference sensitivity level and performance of the LMU shall be as specified in Table 4.2.
+
+**Table 4.2: LMU reference sensitivity levels**
+
+| LMU Class        | Reference measurement channel data rate | LMU sensitivity level (dBm) | BER                        |
+|------------------|-----------------------------------------|-----------------------------|----------------------------|
+| Wide Area LMU    | 12.2 kbps                               | -121                        | BER shall not exceed 0.001 |
+| Medium Range LMU | 12.2 kbps                               | -111                        | BER shall not exceed 0.001 |
+
+## 5.4 Dynamic range
+
+Receiver dynamic range is the receiver ability to handle a rise of interference in the reception frequency channel. The receiver shall fulfil a specified BER requirement for a specified sensitivity degradation of the wanted signal in the presence of an interfering AWGN signal in the same reception frequency channel.
+
+The BER shall not exceed 0.001 for the parameters specified in Table 4.3.
+
+**Table 4.3: Dynamic range**
+
+| Parameter                               | Level Wide Area LMU | Level Medium Range LMU | Unit         |
+|-----------------------------------------|---------------------|------------------------|--------------|
+| Reference measurement channel data rate | 12.2                | 12.2                   | kbps         |
+| Wanted signal mean power                | -91                 | -81                    | dBm          |
+| Interfering AWGN signal                 | -73                 | -63                    | dBm/3.84 MHz |
+
+## 5.5 Adjacent Channel Selectivity (ACS)
+
+Adjacent channel selectivity (ACS) is a measure of the LMU receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the LMU receiver filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s).
+
+The interference signal is offset from the wanted signal by the frequency offset Fuw. The interference signal shall be a W-CDMA signal as specified in Annex C of TS 25.104 [1].
+
+The BER shall not exceed 0.001 for the parameters specified in Table 4.4.
+
+**Table 4.4: LMU Adjacent channel selectivity**
+
+| Parameter                     | Level Wide Area LMU | Level Medium Range LMU | Unit |
+|-------------------------------|---------------------|------------------------|------|
+| Data rate                     | 12.2                | 12.2                   | kbps |
+| Wanted signal mean power      | -115                | -105                   | dBm  |
+| Interfering signal mean power | -52                 | -42                    | dBm  |
+| Fuw offset (Modulated)        | 5                   | 5                      | MHz  |
+
+## 5.6 Blocking characteristics
+
+The blocking characteristics are a measure of the LMU receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The
+
+performance as specified in Table 4.5-4.10 shall be met with a wanted and an interfering signal coupled to the LMU antenna input using the following parameters for the blocking and narrowband blocking requirements:
+
+**Table 4.5: Blocking performance requirement for Wide Area LMU**
+
+| Operating Band | Center Frequency of Interfering Signal       | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| I              | 1920 – 1980 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1900 – 1920 MHz<br>1980 – 2000 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -1900 MHz<br>2000 MHz – 12750 MHz      | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| II             | 1850 – 1910 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1830 – 1850 MHz<br>1910 – 1930 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1830 MHz<br>1930 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| III            | 1710 – 1785 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1785 – 1805 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1805 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| IV             | 1710 – 1755 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1755 – 1775 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1775 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| V              | 824-849 MHz                                  | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 804-824 MHz<br>849-869 MHz                   | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 804 MHz<br>869 MHz – 12750 MHz       | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| VI             | 810 – 830 MHz<br>840 – 860 MHz               | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 810 MHz<br>860 MHz – 12750 MHz       | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| VII            | 2500 – 2570 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 2480 – 2500 MHz<br>2570 – 2590 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -2480 MHz<br>2590 MHz – 12750 MHz      | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| VIII           | 880 – 915 MHz                                | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 860 – 880 MHz<br>915 – 925 MHz               | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -860 MHz<br>925 MHz – 12750 MHz        | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| IX             | 1749.9 – 1784.9 MHz                          | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1729.9 – 1749.9 MHz<br>1784.9 – 1804.9 MHz   | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1729.9 MHz<br>1804.9 MHz – 12750 MHz | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| X              | 1710 – 1770 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1770 – 1790 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1790 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+
+NOTE \*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1]
+
+Table 4.6: Blocking performance requirement for the Medium range LMU
+
+| Operating Band | Center Frequency of Interfering Signal       | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| I              | 1920 – 1980 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1900 – 1920 MHz<br>1980 – 2000 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -1900 MHz<br>2000 MHz – 12750 MHz      | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| II             | 1850 – 1910 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1830 – 1850 MHz<br>1910 – 1930 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1830 MHz<br>1930 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| III            | 1710 – 1785 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1785 – 1805 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1805 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| IV             | 1710 – 1755 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1755 – 1775 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1775 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| V              | 824-849 MHz                                  | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 804-824 MHz<br>849-869 MHz                   | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 804 MHz<br>869 MHz – 12750 MHz       | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| VI             | 810 – 830 MHz<br>840 – 860 MHz               | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 810 MHz<br>860 MHz – 12750 MHz       | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| VII            | 2500 – 2570 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 2480 – 2500 MHz<br>2570 – 2590 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -2480 MHz<br>2590 MHz – 12750 MHz      | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| VIII           | 880 – 915 MHz                                | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 860 – 880 MHz<br>915 – 925 MHz               | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -860 MHz<br>925 MHz – 12750 MHz        | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| IX             | 1749.9 – 1784.9 MHz                          | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1729.9 – 1749.9 MHz<br>1784.9 – 1804.9 MHz   | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1729.9 MHz<br>1804.9 MHz – 12750 MHz | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+| X              | 1710 – 1770 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1770 – 1790 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1790 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+|                |                                              |                               |                          |                                      |                            |
+
+NOTE \*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1]
+
+**Table 4.7: Blocking performance requirement (narrowband) for the Wide Area LMU**
+
+| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| II             | 1850 – 1910 MHz                        | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| III            | 1710 – 1785 MHz                        | - 47 dBm                      | -115 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| IV             | 1710 – 1755 MHz                        | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| V              | 824 – 849 MHz                          | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| VIII           | 880 – 915 MHz                          | - 47 dBm                      | -115 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| X              | 1710 – 1770 MHz                        | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+
+NOTE \*: GMSK modulation as defined in TS 45.004 [2].
+
+**Table 4.8: Narrowband blocking performance requirement for the Medium Range LMU**
+
+| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| II             | 1850 – 1910 MHz                        | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| III            | 1710 – 1785 MHz                        | - 42 dBm                      | -105 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| IV             | 1710 – 1755 MHz                        | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| V              | 824 – 849 MHz                          | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| VIII           | 880 – 915 MHz                          | - 42 dBm                      | -105 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| X              | 1710 – 1770 MHz                        | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+
+NOTE \*: GMSK modulation as defined in TS 45.004 [2].
+
+Additional blocking requirements shall be applied for the protection of the LMU receiver in the presence of GSM900, DCS1800, PCS1900, GSM850, UTRA TDD, and UTRA FDD in bands I to X.
+
+**Table 4.9: Additional blocking performance requirement for Wide Area LMU.**
+
+| Co-located BS type    | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal |
+|-----------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------|
+| Macro GSM900          | 921 – 960 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| Macro DCS1800         | 1805 – 1880 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| Macro PCS1900         | 1930 – 1990 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| Macro GSM850          | 869 – 894 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band I    | 2110 – 2170 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band II   | 1930 – 1990 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band III  | 1805 – 1880 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band IV   | 2110 – 2155 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band V    | 869 – 894 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band VI   | 875 – 885 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band VII  | 2620 – 2690 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band VIII | 925 – 960 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band IX   | 1844.9 – 1879.9 MHz                    | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band X    | 2110 – 2170 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+
+**Table 4.10: Additional blocking performance requirements for the LMU**
+
+| Co-located BS type    | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal |
+|-----------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------|
+| Micro GSM900          | 921 – 960 MHz                          | -3 dBm                        | -105 dBm                 | CW carrier                 |
+| Micro DCS1800         | 1805 – 1880 MHz                        | +5 dBm                        | -105 dBm                 | CW carrier                 |
+| Micro PCS1900         | 1930 – 1990 MHz                        | +5 dBm                        | -105 dBm                 | CW carrier                 |
+| Micro GSM850          | 869 – 894 MHz                          | -3 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band I    | 2110 – 2170 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band II   | 1930 – 1990 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band III  | 1805 – 1880 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band IV   | 2110 – 2155 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band V    | 869 – 894 MHz                          | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band VI   | 875 – 885 MHz                          | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band VII  | 2620 – 2690 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band VIII | 925 – 960 MHz                          | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band IX   | 1844.9 – 1879.9 MHz                    | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band X    | 2110 – 2170 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+
+An additional blocking requirement may be applied for the protection of the LMU receivers when UTRA TDD is co-located with an LMU.
+
+The current state-of-the-art technology does not allow a single generic solution for co-location with UTRA-TDD on adjacent frequencies for 30dB BS-BS minimum coupling loss.
+
+However, there are certain site-engineering solutions that can be used in these cases. These techniques are addressed in TR 25.942 [4].
+
+For an LMU, the static reference performance as specified in clause 5.3 should be met with a wanted and an interfering signal coupled to BS antenna input using the parameters in Table 4.11.
+
+**Table 4.11: Blocking performance requirement for a Wide Area LMU when co-located with UTRA TDD BS in other bands.**
+
+| Co-located BS type | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal |
+|--------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------|
+| Wide Area TDD      | 2585 – 2620 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+
+## 5.7 Intermodulation characteristics
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal.
+
+The static reference performance as specified in clause 5.3 shall be met for a LMU when the following signals are coupled to LMU antenna input:
+
+- A wanted signal at the assigned channel frequency with a mean power of -115 dBm.
+- Two interfering signals with the following parameters.
+
+**Table 4.12: Intermodulation performance requirement (Wide Area LMU)**
+
+| Operating band                                                                               | Interfering Signal mean power | Offset | Type of Interfering Signal |
+|----------------------------------------------------------------------------------------------|-------------------------------|--------|----------------------------|
+| All bands                                                                                    | - 48 dBm                      | 10 MHz | CW signal                  |
+|                                                                                              | - 48 dBm                      | 20 MHz | WCDMA signal *             |
+| Note*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1] |                               |        |                            |
+
+**Table 4.13: Narrowband intermodulation performance requirement (Wide Area LMU)**
+
+| Operating band                    | Interfering Signal mean power | Offset  | Type of Interfering Signal |
+|-----------------------------------|-------------------------------|---------|----------------------------|
+| II, III, IV, V, VIII, X           | - 47 dBm                      | 3.5 MHz | CW signal                  |
+|                                   | - 47 dBm                      | 5.9 MHz | GMSK modulated*            |
+| * GMSK as defined in TS45.004 [2] |                               |         |                            |
+
+The static reference performance as specified in clause 5.3 shall be met for a Medium Range LMU when the following signals are coupled to LMU antenna input:
+
+- A wanted signal at the assigned channel frequency with a mean power of -105 dBm.
+- Two interfering signals with the following parameters.
+
+**Table 4.14: Intermodulation performance requirement (Medium Range LMU)**
+
+| Operating band                                                                               | Interfering Signal mean power | Offset | Type of Interfering Signal |
+|----------------------------------------------------------------------------------------------|-------------------------------|--------|----------------------------|
+| All bands                                                                                    | - 44 dBm                      | 10 MHz | CW signal                  |
+|                                                                                              | - 44 dBm                      | 20 MHz | WCDMA signal *             |
+| Note*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1] |                               |        |                            |
+
+**Table 4.15: Narrowband intermodulation performance requirement (Medium Range LMU)**
+
+| Operating band                    | Interfering Signal mean power | Offset  | Type of Interfering Signal |
+|-----------------------------------|-------------------------------|---------|----------------------------|
+| II, III, IV, V, VIII, X           | - 43 dBm                      | 3.5 MHz | CW signal                  |
+|                                   | - 43 dBm                      | 5.9 MHz | GMSK modulated*            |
+| * GMSK as defined in TS45.004 [2] |                               |         |                            |
+
+## 5.8 Spurious emissions
+
+The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the LMU antenna connector.
+
+The power of any spurious emission shall not exceed:
+
+**Table 4.16: General LMU spurious emission requirement**
+
+| Band              | Maximum level | Measurement Bandwidth | Note                                                                                                                                                |
+|-------------------|---------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| 30MHz – 1 GHz     | -57 dBm       | 100 kHz               |                                                                                                                                                     |
+| 1 GHz – 12.75 GHz | -47 dBm       | 1 MHz                 | With the exception of frequencies between 12.5 MHz below the first carrier frequency and 12.5 MHz above the last carrier frequency used by the LMU. |
+
+In addition the following requirements shall be applied for the protection of UE, MS, and Node B, BS of the same and other systems, where the power of any spurious emission shall not exceed the limits:
+
+**Table 4.17: Additional LMU Spurious emissions limits**
+
+| Operating Band | Band                | Maximum level | Measurement Bandwidth | Note |
+|----------------|---------------------|---------------|-----------------------|------|
+| I              | 1920 – 1980 MHz     | -78 dBm       | 3.84 MHz              |      |
+| II             | 1850 – 1910 MHz     | -78 dBm       | 3.84 MHz              |      |
+| III            | 1710 – 1785 MHz     | -78 dBm       | 3.84 MHz              |      |
+| IV             | 1710 – 1755 MHz     | -78 dBm       | 3.84 MHz              |      |
+| V              | 824 – 849 MHz       | -78 dBm       | 3.84 MHz              |      |
+| VI             | 815 – 850 MHz       | -78 dBm       | 3.84 MHz              |      |
+| VII            | 2500 – 2570 MHz     | -78 dBm       | 3.84 MHz              |      |
+| VIII           | 880 – 915 MHz       | -78 dBm       | 3.84 MHz              |      |
+| IX             | 1749.9 – 1784.9 MHz | -78 dBm       | 3.84 MHz              |      |
+| X              | 1710 – 1770 MHz     | -78 dBm       | 3.84 MHz              |      |
+
+In addition, the requirement in Table 4.18 may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed.
+
+**Table 4.18: Additional spurious emission requirements for the TDD bands**
+
+| Operating Band | Band                               | Maximum level | Measurement Bandwidth | Note                    |
+|----------------|------------------------------------|---------------|-----------------------|-------------------------|
+| I              | 1900 – 1920 MHz<br>2010 – 2025 MHz | -78 dBm       | 3.84 MHz              | Not applicable in Japan |
+|                | 2010 – 2025 MHz                    | -52 dBm       | 1MHz                  | Applicable in Japan     |
+| VI, IX         | 2010 – 2025 MHz                    | -52 dBm       | 1MHz                  |                         |
+
+# 6 LMU measurement requirements
+
+## 6.1 General
+
+All tests at specified detection levels require that the LMU detection threshold be set such that the false alarm rate is at or below 5 % when no signal is present (noise only).
+
+## 6.2 RRC States supported
+
+UTDOA positioning technique does work in CELL\_DCH and CELL\_FACH state, not in URA\_PCH nor CELL\_PCH state.
+
+## 6.3 Maximum response times
+
+- 1) The maximum time for a Master LMU to establish a reference signal shall be, after the data capture has started, less than 5 seconds.
+- 2) The maximum time for the distribution of the reference signal to another LMU involved in the positioning shall be less than 3 seconds.
+- 3) The maximum time of detection of the time of arrival in an LMU given the reference signal shall be less than 15 seconds.
+
+## 6.4 Nominal time accuracy
+
+Nominal Time Accuracy requirement verifies the difference between the detected time of arrival and the real time of arrival.
+
+In an AWGN environment with no fading or multi-paths, the standard deviation of the timing error of the LMU shall be less than 30 ns when the signal presence is correctly detected.
+
+## 6.5 Multipath scenarios
+
+The purpose of the test case is to verify the LMU receiver's performance in multipath.
+
+For the 12.2 kbps reference measurement channel specified in 3GPP TS 25.104 Annex A [1], and with Rx diversity (using both diversity paths), the LMU shall be capable of detecting the earliest path, for at least 90 % of the location attempts, at the levels in Table 5.1.
+
+Nominal time accuracy for multipath fading scenarios includes an additional chip duration of 260 nanoseconds over that in Section 5.4.
+
+**Table 5.1: Multipath detection level**
+
+| Propagation condition   | Detection level: Signal to Noise level in (dB) | Note   |
+|-------------------------|------------------------------------------------|--------|
+| Static (AWGN)           | -51.2 dB                                       | NOTE 1 |
+| Multipath fading Case 1 | -47.2dB                                        | NOTE 2 |
+| Multipath fading Case 2 | - 43.8 dB                                      | NOTE 2 |
+| Multipath fading Case 3 | - 41.9 dB                                      | NOTE 2 |
+| Multipath fading Case 4 | - 39.8 dB                                      | NOTE 2 |
+
+NOTE 1: Static propagation condition is described in 3GPP TS 25.104 Annex B.1 [1].
+
+NOTE 2: Multipath-fading case 1-4 is described in 3GPP TS 25.104 Annex B.2 [1].
+
+## 6.6 Moving scenario
+
+The purpose of the test case is to verify the LMU receiver's performance to Doppler shift.
+
+In an AWGN environment with no fading or multi-paths, and at a speed of 250km/h, the detectability of the LMU shall be degraded by no more than 1.5 dB.
+
+## 6.7 Cross correlation
+
+The ability of the LMU to detect a weak terminal signal in the presence of a strong other terminal is covered in Section 5.5 when the other terminal interference is modelled as AWGN.
+
+# Annex A (informative): Change history
+
+| Change history |       |           |    |     |                                                                       |     |        |        |
+|----------------|-------|-----------|----|-----|-----------------------------------------------------------------------|-----|--------|--------|
+| Date           | TSG   | Doc.      | CR | Rev | Subject/Comment                                                       | Cat | Old    | New    |
+| 2005-08        |       |           |    |     | Initial version created                                               |     |        | 0.1.0  |
+| 2007-11        |       |           |    |     | Incorporate simulation results and synchronize with TS.104            |     | 0.1.0  | 1.0.0  |
+| 2007-12        | 38    | RP-071015 |    |     | Approved version at RAN TSG # 38                                      |     | 1.0.0  | 7.0.0  |
+| 2008-03        | 39    | RP-080122 | 1  |     | Correcting multipath detection level in LMU performance specification | F   | 7.0.0  | 7.1.0  |
+| 2008-12        | SP-42 |           |    |     | Upgraded unchanged from Rel-7                                         |     |        | 8.0.0  |
+| 2009-12        | SP-46 |           |    |     | Upgraded unchanged from Rel-8                                         |     |        | 9.0.0  |
+|                | SP-51 |           |    |     | Upgraded unchanged from Rel-9                                         |     | 9.0.0  | 10.0.0 |
+| 2012-09        | SP-57 | -         | -  | -   | Update to Rel-11 version (MCC)                                        |     | 10.0.0 | 11.0.0 |
+| 2014-09        | SP-65 | -         | -  | -   | Update to Rel-12 version (MCC)                                        |     | 11.0.0 | 12.0.0 |
+| 2016-01        | SP-70 | -         | -  | -   | Update to Rel-13 version (MCC)                                        |     | 12.0.0 | 13.0.0 |
+| 2017-03        | RP-75 | -         | -  | -   | Update to Rel-14 version (MCC)                                        |     | 13.0.0 | 14.0.0 |
+
+| Change history |         |      |    |     |     |                                |             |
+|----------------|---------|------|----|-----|-----|--------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version |
+| 2018-06        | SA#80   | -    | -  | -   | -   | Update to Rel-15 version (MCC) | 15.0.0      |
+| 2020-06        | SA#88   | -    | -  | -   | -   | Update to Rel-16 version (MCC) | 16.0.0      |
+| 2022-03        | SA#95   |      |    |     |     | Update to Rel-17 version (MCC) | 17.0.0      |
+| 2024-03        | RAN#103 |      |    |     |     | Update to Rel-18 version (MCC) | 18.0.0      |

marked/Rel-18/25_series/25113/raw.md

@@ -0,0 +1,1234 @@
+
+
+# 3GPP TS 25.113 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+![5G Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC) (Release 18)**
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+---
+
+3GPP logo
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                 |    |
+|---------------------------------------------------------------------------------|----|
+| Foreword .....                                                                  | 5  |
+| 1 Scope.....                                                                    | 6  |
+| 2 References.....                                                               | 6  |
+| 3 Definitions, symbols and abbreviations.....                                   | 7  |
+| 3.1 Definitions .....                                                           | 8  |
+| 3.2 Symbols .....                                                               | 9  |
+| 3.3 Abbreviations .....                                                         | 9  |
+| 4 Test conditions.....                                                          | 10 |
+| 4.1 General .....                                                               | 10 |
+| 4.2 Arrangements for establishing a communication link.....                     | 10 |
+| 4.2.1 Multiple enclosure BS solution.....                                       | 10 |
+| 4.3 Narrow band responses on receivers.....                                     | 11 |
+| 4.3.1 FDD and 3,84 Mcps TDD option .....                                        | 11 |
+| 4.3.2 1,28 Mcps TDD option .....                                                | 11 |
+| 4.4 Test condition for Repeater .....                                           | 11 |
+| 4.4.1 Arrangements for test signals for repeaters .....                         | 12 |
+| 4.5 Exclusion bands.....                                                        | 12 |
+| 4.5.1 Transmitter exclusion band.....                                           | 12 |
+| 4.5.2 Receiver exclusion band .....                                             | 12 |
+| 4.6 BS test configurations.....                                                 | 13 |
+| 5 Performance assessment .....                                                  | 13 |
+| 5.1 General .....                                                               | 13 |
+| 5.2 Assessment of BLER in Downlink.....                                         | 14 |
+| 5.3 Assessment of BLER in Uplink .....                                          | 14 |
+| 5.4 Ancillary equipment .....                                                   | 14 |
+| 5.5 Repeaters .....                                                             | 14 |
+| 6 Performance Criteria.....                                                     | 14 |
+| 6.1 Performance criteria for continuous phenomena for BS .....                  | 14 |
+| 6.2 Performance criteria for transient phenomena for BS.....                    | 15 |
+| 6.3 (void) .....                                                                | 15 |
+| 6.4 Performance criteria for continuous phenomena for Ancillary equipment ..... | 15 |
+| 6.5 Performance criteria for transient phenomena for Ancillary equipment .....  | 16 |
+| 6.6 (void) .....                                                                | 16 |
+| 6.7 Performance criteria for continuous phenomena for repeaters.....            | 16 |
+| 6.8 Performance criteria for transient phenomena for repeaters .....            | 16 |
+| 6.9 (void) .....                                                                | 17 |
+| 7 Applicability overview .....                                                  | 17 |
+| 7.1 Emission .....                                                              | 17 |
+| 7.2 Immunity .....                                                              | 18 |
+| 7.3 Applicability of requirements in TS 37.113 .....                            | 18 |
+| 8 Emission.....                                                                 | 20 |
+| 8.1 Methods of measurement and limits for EMC emissions .....                   | 20 |
+| 8.2 Test configurations .....                                                   | 20 |
+| 8.3 Radiated emission from Base station, Repeater and ancillary equipment.....  | 20 |
+| 8.3.1 Radiated emission, Base stations and Repeater .....                       | 20 |
+| 8.3.1.1 Definition .....                                                        | 20 |
+| 8.3.1.2 Test method.....                                                        | 20 |
+| 8.3.1.2.1 FDD and 3,84 Mcps TDD option .....                                    | 20 |
+| 8.3.1.2.2 1,28 Mcps TDD option.....                                             | 21 |
+| 8.3.1.3 Limits .....                                                            | 21 |
+| 8.3.1.3.1 FDD and 3,84 Mcps TDD option.....                                     | 21 |
+| 8.3.1.3.2 1,28 Mcps TDD option.....                                             | 22 |
+
+|                               |                                                                                   |           |
+|-------------------------------|-----------------------------------------------------------------------------------|-----------|
+| 8.3.1.4                       | Interpretation of the measurement results .....                                   | 22        |
+| 8.3.2                         | Radiated emission, Ancillary equipment .....                                      | 23        |
+| 8.3.2.1                       | Definition .....                                                                  | 23        |
+| 8.3.2.2                       | Test method.....                                                                  | 23        |
+| 8.3.2.3                       | Limits .....                                                                      | 23        |
+| 8.4                           | Conducted emission DC power input/output port .....                               | 23        |
+| 8.4.1                         | Definition .....                                                                  | 24        |
+| 8.4.2                         | Test method.....                                                                  | 24        |
+| 8.4.3                         | Limits .....                                                                      | 24        |
+| 8.5                           | Conducted emissions, AC mains power input/output port .....                       | 24        |
+| 8.5.1                         | Definition .....                                                                  | 24        |
+| 8.5.2                         | Test method.....                                                                  | 24        |
+| 8.5.3                         | Limits .....                                                                      | 25        |
+| 8.6                           | Harmonic Current emissions (AC mains input port).....                             | 25        |
+| 8.7                           | Voltage fluctuations and flicker (AC mains input port) .....                      | 25        |
+| 8.8                           | Telecommunication ports .....                                                     | 25        |
+| 8.8.1                         | Definition .....                                                                  | 25        |
+| 8.8.2                         | Test method.....                                                                  | 25        |
+| 8.8.3                         | Limits .....                                                                      | 26        |
+| 9                             | Immunity.....                                                                     | 26        |
+| 9.1                           | Test methods and levels for immunity tests .....                                  | 26        |
+| 9.2                           | Test configurations .....                                                         | 26        |
+| 9.3                           | RF electromagnetic field (80 MHz - 6000 MHz).....                                 | 27        |
+| 9.3.1                         | Definition .....                                                                  | 27        |
+| 9.3.2                         | Test method and level.....                                                        | 27        |
+| 9.3.3                         | Performance criteria.....                                                         | 28        |
+| 9.4                           | Electrostatic discharge.....                                                      | 28        |
+| 9.4.1                         | Definition .....                                                                  | 28        |
+| 9.4.2                         | Test method and level.....                                                        | 28        |
+| 9.4.3                         | Performance criteria.....                                                         | 28        |
+| 9.5                           | Fast transients common mode .....                                                 | 28        |
+| 9.5.1                         | Definition .....                                                                  | 29        |
+| 9.5.2                         | Test method and level.....                                                        | 29        |
+| 9.5.3                         | Performance criteria.....                                                         | 29        |
+| 9.6                           | RF common mode (0,15 MHz - 80 MHz).....                                           | 29        |
+| 9.6.1                         | Definition .....                                                                  | 29        |
+| 9.6.2                         | Test method and level.....                                                        | 29        |
+| 9.6.3                         | Performance criteria.....                                                         | 30        |
+| 9.7                           | Voltage dips and interruptions.....                                               | 30        |
+| 9.7.1                         | Definition .....                                                                  | 30        |
+| 9.7.2                         | Test method and level.....                                                        | 30        |
+| 9.7.3                         | Performance criteria.....                                                         | 30        |
+| 9.8                           | Surges, common and differential mode.....                                         | 31        |
+| 9.8.1                         | Definition .....                                                                  | 31        |
+| 9.8.2                         | Test method and level.....                                                        | 31        |
+| 9.8.2.1                       | Test method for telecommunication ports directly connected to outdoor cables..... | 31        |
+| 9.8.2.2                       | Test method for telecommunication ports connected to indoor cables.....           | 31        |
+| 9.8.2.3                       | Test method for AC power ports.....                                               | 32        |
+| 9.8.3                         | Performance criteria.....                                                         | 32        |
+| <b>Annex A (informative):</b> | <b>Change History.....</b>                                                        | <b>33</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version 3.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 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 specification.
+
+# 1 Scope
+
+The present document covers the assessment of base stations, repeaters and associated ancillary equipment in respect of Electromagnetic Compatibility (EMC).
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations, repeaters and associated ancillary equipment in one of the following categories:
+
+- base stations for the FDD mode of UTRA meeting the requirements of TS 25.104 [1], with conformance demonstrated by compliance to TS 25.141 [3].
+- base stations for both options of the TDD mode of UTRA meeting the requirements of TS 25.105 [2], with conformance demonstrated by compliance to TS 25.142 [4]. The two options are the 3,84 Mcps and 1,28 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate.
+- repeaters for the FDD mode of UTRA meeting the requirements of TS 25.106 [10], with conformance demonstrated by compliance to TS 25.143 [11].
+
+Technical requirements related to the antenna port of base stations or repeaters are not included in the present document. These are found in the relevant product standards [1], [2], [3], [4], [10], [11].
+
+The environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [5] and IEC 61000-6-3 [6].
+
+The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TS 25.104: "UTRA (BS) FDD; Radio transmission and reception".
+- [2] 3GPP TS 25.105: "UTRA (BS) TDD; Radio transmission and reception".
+- [3] 3GPP TS 25.141: "UTRA (BS) FDD; Base station conformance testing (FDD)".
+- [4] 3GPP TS 25.142: "UTRA (BS) TDD; Base station conformance testing (TDD)".
+- [5] IEC 61000-6-1: 2005; "Electromagnetic compatibility (EMC) - Part 6: Generic standards - Section 1: Immunity for residential, commercial and light-industrial environments".
+- [6] IEC 61000-6-3: 2006/AMD1:2010: "Electromagnetic compatibility (EMC) - Part 6: Generic standards - Section 3: Emission standard for residential, commercial and light industrial environments".
+- [7] IEC 60050(161): "International Electrotechnical Vocabulary - Chapter 161: Electromagnetic compatibility".
+- [8] 3GPP TS 25.101: "UTRA (UE) FDD; UE Radio transmission and reception (FDD)".
+
+- [9] 3GPP TS 25.102: "UTRA (UE) TDD: UE Radio transmission and reception (TDD)".
+- [10] 3GPP TS 25.106: "UTRA Repeater; Radio Transmission and Reception".
+- [11] 3GPP TS 25.143: "UTRA Repeater conformance testing".
+- [12] ITU-R Rec. SM.329: "Unwanted emissions in the spurious domain".
+- [13] Void
+- [14] CISPR 16-1-1: "Specification for radio disturbance and immunity measuring apparatus and methods - Measuring apparatus".
+- [15] IEC 61000-3-2 (2004): "Electromagnetic compatibility (EMC) - Part 3: Limits - Section 2: Limits for harmonic current emissions (equipment input current  $\leq 16$  A)".
+- [16] IEC 61000-3-3 (2002): "Electromagnetic compatibility (EMC) - Part 3: Limits - Section 3: Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current  $\leq 16$  A".
+- [17] IEC 61000-4-2: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 2: Electrostatic discharge immunity test".
+- [18] IEC 61000-4-3: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 3: Radiated, radio-frequency electromagnetic field immunity test".
+- [19] IEC 61000-4-4: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 4: Electrical fast transient/burst immunity test".
+- [20] IEC 61000-4-5: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 5: Surge immunity test".
+- [21] IEC 61000-4-6: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 6: Immunity to contacted disturbances, induced by radio frequency fields".
+- [22] IEC 61000-4-11: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 11: Voltage dips, short interruptions and voltage variations. Immunity tests".
+- [23] ITU-R Recommendation SM.1539 (2001): "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329".
+- [24] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [25] IEC 61000-3-12 (2005): "Electromagnetic compatibility (EMC) - Part 3-12: Limits- Limits for harmonic current produced by equipment connected to public low-voltage system with input current  $>16$  A and  $\leq 75$  A.
+- [26] IEC 61000-3-11 (2000): "Electromagnetic compatibility (EMC) - Part 3-11: Limits –Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current  $\leq 75$  A and subject to conditional connections"3Definitions, symbols and abbreviations
+- [27] 3GPP TS 37.113: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)".
+- [28] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Ancillary equipment:** Equipment (apparatus), used in connection with a receiver, transmitter or transceiver is considered as an ancillary equipment (apparatus) if:
+
+- the equipment is intended for use in conjunction with a receiver, transmitter or transceiver to provide additional operational and/or control features to the radio equipment, (e.g. to extend control to another position or location); and
+- the equipment cannot be used on a stand-alone basis to provide user functions independently of a receiver, transmitter or transceiver; and
+- the receiver, transmitter or transceiver to which it is connected, is capable of providing some intended operation such as transmitting and/or receiving without the ancillary equipment (i.e. it is not a sub-unit of the main equipment essential to the main equipment basic functions).
+
+**Base Station equipment:** Radio and/or ancillary equipment intended for operation at a fixed location and powered directly or indirectly (e.g. via an AC/DC converter or power supply) by AC mains network, or an extended local DC mains network.
+
+**BLER:** BLER is block error ratio. The BLER calculation shall be based on evaluating the CRC on each transport block.
+
+**Continuous phenomena (continuous disturbance):** Electromagnetic disturbance, the effects of which on a particular device or equipment cannot be resolved into a succession of distinct effects (IEC 60050-161 [7]).
+
+**Multi-band Base Station:** Base Station characterized by the ability of its transmitter and/or receiver to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different non-overlapping operating band than the other carrier(s).
+
+**Pass band:** The repeater can have one or several pass bands. The pass band is the frequency range that the repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal channels. If they are not consecutive each subset of channels shall be considered as an individual pass band.
+
+**Port:** A particular interface, of the specified equipment (apparatus), with the electromagnetic environment. For example, any connection point on an equipment intended for connection of cables to or from that equipment is considered as a port (see figure 1).
+
+**Radio communications equipment :** Telecommunications equipment which includes one or more transmitters and/or receivers and/or parts thereof for use in a fixed, mobile or portable application. It can be operated with ancillary equipment but if so, is not dependent on it for basic functionality.
+
+**Radio equipment:** Equipment which contains Radio digital unit and Radio unit.
+
+**Radio digital unit:** Equipment which contains base band and functionality for controlling Radio unit.
+
+**Radio unit:** Equipment which contains transmitter and/or receiver.
+
+**Receiver exclusion band:** The receiver exclusion band is the band of frequencies over which no tests of radiated immunity of a receiver are made. The exclusion band for receivers is expressed relative to the base station receive band.
+
+**Repeater:** A device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station). In operating bands specified with only down-link or up-link, only the up-link or down-link as specified for the operating band is repeated.
+
+**Signal and control :** Port which carries information or control signals, excluding antenna ports.
+
+**Telecommunication port:** Ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks.
+
+**Transient phenomena:** Pertaining to or designating a phenomena or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [7]).
+
+**Transmitter exclusion band:** The transmitter exclusion band is the band of frequencies over which no tests of radiated immunity of a transmitter are made. The exclusion band for transmitters is expressed relative to the carrier frequencies used (the carrier frequencies of the base stations activated transmitter(s).)
+
+![Diagram of an Apparatus with various ports.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+The diagram shows a central box labeled 'Apparatus' inside a larger box labeled 'Enclosure Port'. On the left side, three lines extend from the 'Apparatus' box to labels: 'AC power port', 'DC power port', and 'Earth port'. On the right side, three lines extend from the 'Apparatus' box to labels: 'Antenna port', 'Signal/control port', and 'Telecommunication port'.
+
+Diagram of an Apparatus with various ports.
+
+Figure 1: Examples of ports
+
+![Diagram of BS Equipment with a single enclosure solution.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+The diagram shows a large box labeled 'BS Equipment' containing a smaller box labeled 'Radio Equipment' in its top right corner.
+
+Diagram of BS Equipment with a single enclosure solution.
+
+Figure 1A: BS with single enclosure solution
+
+![Diagram of BS Equipment with a multiple enclosure solution.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+The diagram shows a large box labeled 'BS Equipment' containing two boxes: 'Radio digital unit' on the left and 'Radio unit' on the right, connected by a horizontal line. A dashed box labeled 'Radio Equipment' encloses both the 'Radio digital unit' and the 'Radio unit'.
+
+Diagram of BS Equipment with a multiple enclosure solution.
+
+Figure 1B: BS with multiple enclosure solution
+
+## 3.2 Symbols
+
+(void)
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [24] and the following apply:
+
+|    |                     |
+|----|---------------------|
+| AC | Alternating Current |
+|----|---------------------|
+
+|      |                                    |
+|------|------------------------------------|
+| AMN  | Artificial Mains Network           |
+| CDN  | Coupling/Decoupling Network        |
+| DC   | Direct Current                     |
+| EMC  | Electromagnetic Compatibility      |
+| ESD  | Electrostatic discharge            |
+| EUT  | Equipment Under Test               |
+| RF   | Radio frequency                    |
+| rms  | root mean square                   |
+| UTRA | Universal Terrestrial Radio Access |
+
+# --- 4 Test conditions
+
+## 4.1 General
+
+The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 25.141 [3] or TS 25.142 [4] or in the UTRA Repeater conformance testing specification TS25.143 [11]. The test conditions shall be recorded in the test report.
+
+For an EUT which contains more than one BS, it is sufficient to perform tests relating to each type of port of each representative type of the BS forming part of the EUT.
+
+For BS capable of multi-band operation, the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands shall be activated according to the test configuration in subclause 4.6. Tests shall be performed relating to each type of port and all bands shall be assessed during the tests.
+
+## 4.2 Arrangements for establishing a communication link
+
+The wanted RF input signal nominal frequency shall be selected by setting the UTRA Absolute Radio Frequency Channel Number (UARFCN) to an appropriate number.
+
+A communication link shall be set up with a suitable test system capable of evaluating the required performance criteria (hereafter called "the test system") at the air interface and/or the Iub interface. The test system shall be located outside of the test environment.
+
+When the EUT is required to be in the transmit/receive mode, the following conditions shall be met:
+
+- the EUT shall be commanded to operate at maximum rated transmit power;
+- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment;
+- The wanted input signal level shall be set to a level where the performance is not limited by the receiver noise floor or strong signal effects e.g. 15 dB above the reference sensitivity level as defined in TS 25.141 (for FDD) [3] or TS 25.142 (for TDD) [4], to provide a stable communication link.
+
+For immunity tests subclause 4.3 shall apply and the conditions shall be as follows:
+
+### 4.2.1 Multiple enclosure BS solution
+
+For a BS with multiple enclosures, the BS part with Radio digital unit and the Radio unit may be tested separately. Communication link shall be set up in the same way as if they are in single BS enclosure. The Radio Digital unit and the Radio unit shall communicate over an interface enabling establishment of a communication link.
+
+## 4.3 Narrow band responses on receivers
+
+### 4.3.1 FDD and 3,84 Mcps TDD option
+
+Responses on receivers or duplex transceivers occurring during the immunity test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method:
+
+- if during an immunity test the quantity being monitored goes outside the specified tolerances (clause 6), it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased, and then decreased by 10 MHz;
+- if the deviation disappears in either or both of the above 10 MHz offset cases, then the response is considered as a narrow band response;
+- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to 12,5 MHz;
+- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test.
+
+Narrow band responses are disregarded.
+
+For BS capable of multi-band operation, all supported operating bands shall be considered for narrowband responses.
+
+### 4.3.2 1,28 Mcps TDD option
+
+For 1.28Mcps chip rate TDD option, responses on receivers or duplex transceivers occurring during the test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method:
+
+- if during an immunity test the quantity being monitored goes outside the specified tolerances, it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased, and then decreased by 3.2MHz;
+- if the deviation disappears in either or both of the above 3.2 MHz offset cases, then the response is considered as a narrow band response;
+- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to 4MHz;
+- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test.
+
+Narrow band responses are disregarded.
+
+For BS capable of multi-band operation, all supported operating bands shall be considered for narrowband responses.
+
+## 4.4 Test condition for Repeater
+
+The wanted RF input signal nominal frequency shall be selected by setting the Absolute Radio Frequency Channel Number (ARFCN) to an appropriate number within the pass band of the Repeater.
+
+The Repeater path shall be tested with a suitable test system capable of measuring RF performance criteria (hereafter called "the test system"). The test system shall be located outside of the test environment.
+
+When the EUT is required to be in the operational mode, the following conditions shall be met:
+
+- the EUT shall be commanded to operate at maximum rated gain;
+- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment;
+
+For immunity tests conditions subclause 4.3 shall apply.
+
+### 4.4.1 Arrangements for test signals for repeaters
+
+For immunity tests of repeaters, the wanted RF input signal shall be coupled to one antenna port at a level which will result, when measured, in the maximum rated RF output power per channel, as declared by the manufacturer. The test shall either be repeated with a wanted signal coupled to the other antenna port, or a single test shall be performed with the specified input signals being simultaneously coupled to both antenna ports.
+
+## 4.5 Exclusion bands
+
+### 4.5.1 Transmitter exclusion band
+
+For the purpose of EMC specifications there shall be a transmitter exclusion band.
+
+#### For UTRA FDD:
+
+Lower carrier frequency used - 12,5 MHz. to upper carrier frequency used + 12,5 MHz.
+
+#### For UTRA 3,84 Mcps TDD option:
+
+Lower carrier frequency used - 12,5 MHz. to upper carrier frequency used + 12,5 MHz.
+
+#### For UTRA 1,28 Mcps TDD option:
+
+Lower carrier frequency used - 4 MHz to upper carrier frequency used + 4 MHz.
+
+#### For UTRA 7,68 Mcps TDD option:
+
+Lower carrier frequency used - 25 MHz. to upper carrier frequency used + 25 MHz.
+
+### 4.5.2 Receiver exclusion band
+
+The receiver exclusion band for base stations extends from the lower frequency of the Base Station receive band minus 20 MHz to the upper frequency of the Base Station receive band plus 20 MHz. The exclusion bands are as set out below:
+
+#### UTRA FDD:
+
+- a) 1900 MHz to 2000 MHz (Band I)
+- b) 1830 MHz to 1930 MHz (Band II)
+- c) 1690 MHz to 1805 MHz (Band III)
+- d) 1690 MHz to 1775 MHz (Band IV)
+- e) 804 MHz to 869 MHz (Band V)
+- f) 810 MHz to 860 MHz (Band VI)
+- g) 2480 MHz to 2590 MHz (Band VII)
+- h) 860 MHz to 935 MHz (Band VIII)
+- i) 1729.9 MHz to 1804.9 MHz (Band IX)
+- j) 1690 MHz to 1790 MHz (Band X)
+- k) 1407.9 MHz to 1467.9 MHz (Band XI)
+- l) 679-736 MHz (Band XII)
+- m) 757-807 MHz (Band XIII)
+
+- n) 768-818 MHz (Band XIV)
+- o) 810-865 MHz (Band XIX)
+- p) 712-782 MHz (Band XX)
+- q) 1427.9-1482.9 MHz (Band XXI)
+- r) 3390-3510 MHz (Band XXII)
+- s) 1830 MHz to 1935 MHz (Band XXV)
+- t) 794 MHz to 869 MHz (Band XXVI)
+- u) N/A (Band XXXII)
+
+UTRA 3.84 Mcps TDD option, UTRA 1.28 Mcps TDD option and UTRA 7.68 Mcps TDD option:
+
+- a) 1880 MHz to 1940 MHz  
+1990 MHz to 2045 MHz
+- b) 1830 MHz to 2010 MHz
+- c) 1890 MHz to 1950 MHz
+- d) 2550 MHz to 2640 MHz
+- e) 2280 MHz to 2420 MHz
+- f) 1860 MHz to 1940 MHz
+
+For BS capable of multi-band operation, the total receiver exclusion band shall be the combination of the exclusion bands for each operating band supported by the BS.
+
+## 4.6 BS test configurations
+
+The present clause defines the BS test configurations that shall be used for demonstrating conformance. A single UTRA carrier shall be used for testing of single-carrier capable BS. For other BS types, the test configurations in Table 4.6.1 shall be used. The test configurations (UTCx) are defined in TS 25.141 [3], subclause 4.12.
+
+**Table 4.6.1: Test configurations for UTRA BS**
+
+| BS test case                                                                                                                                                                                           | BS capable of multi-carrier operation in contiguous spectrum in single band only | BS capable of multi-carrier operation in both contiguous and non-contiguous spectrum in single band | BS capable of multi-band operation |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------------------|
+| Emission tests                                                                                                                                                                                         | UTC1                                                                             | UTC2                                                                                                | UTC1/2 (Note 1), UTC4              |
+| Immunity tests                                                                                                                                                                                         | UTC1                                                                             | UTC2                                                                                                | UTC1/2 (Note 1), UTC4              |
+| NOTE 1: UTC1 or UTC2 shall be applied in each supported operating band according to the respective capability in each band, as defined in the 2 <sup>nd</sup> and 3 <sup>rd</sup> column of the table. |                                                                                  |                                                                                                     |                                    |
+
+# 5 Performance assessment
+
+## 5.1 General
+
+Following information shall be recorded in or annexed to the test report:
+
+- the primary functions of the radio equipment to be tested during and after the EMC testing;
+
+- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment;
+- the method to be used to verify that a communications link is established and maintained
+- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress;
+- the ancillary equipment to be combined with the radio equipment for testing (where applicable);
+- the information about ancillary equipment intended to be used with the radio equipment;
+- information about the common and/or band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation;
+- an exhaustive list of ports, classified as either power or signal/control. Power ports shall further be classified as AC or DC power.
+
+Performance assessment of a BS with multiple enclosures may be done separately for the BS part with the Radio digital unit and the Radio unit respectively, according to the manufacturer's choice.
+
+A communication link used by more than one operating band shall be assessed on all operating bands. Communication link(s) and/or radio performance parameters for the operating bands can during the test be assessed simultaneously or separately for each band, depending on the test environment capability.
+
+## 5.2 Assessment of BLER in Downlink
+
+The output of the transmitter shall be connected to an equipment which meet the requirements for the BLER assessment of TS25.101 [8] in case of FDD and TS25.102 [9] in case of TDD for the bearer used in the immunity tests. The level of the signal supplied to the equipment should be within the range for which the assessment of BLER is not impaired. Power control shall be off during the immunity testing.
+
+## 5.3 Assessment of BLER in Uplink
+
+The value of the BLER at the output of the receiver shall be monitored at Iub-interface by using suitable test equipment.
+
+## 5.4 Ancillary equipment
+
+At the manufacturer's discretion the test may be performed on the ancillary equipment separately or a representative configuration of the combination of radio and ancillary equipment. In each case EUT is tested against all applicable immunity and emission clauses of the present document and in each case, compliance enables the ancillary equipment to be used with different radio equipment.
+
+## 5.5 Repeaters
+
+The parameter used for assessment of performance of a repeater is the gain within the pass band.
+
+# --- 6 Performance Criteria
+
+## 6.1 Performance criteria for continuous phenomena for BS
+
+The test should, where possible, be performed using a bearer with the characteristics of data rate and BLER defined in Table 1. If the test is not performed using one of these bearers (for, example, of none of them are supported by the BS), the characteristics of the bearer used shall be recorded in the test report.
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in Table 1 during the test. If the Uplink and Downlink paths are evaluated as a one loop then the criteria is two times the value shown in Table 1. After
+
+each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 1: BS Performance Criteria for continuous phenomena for BS**
+
+| Bearer Information Data Rate | Performance Criteria                   |
+|------------------------------|----------------------------------------|
+| 12.2 kbps                    | BLER < $10^{-2}$<br>No loss of service |
+| 64 kbps                      | BLER < $10^{-2}$<br>No loss of service |
+| 144 kbps                     | BLER < $10^{-2}$<br>No loss of service |
+| 384 kbps                     | BLER < $10^{-2}$<br>No loss of service |
+
+NOTE: The performance criteria, BLER <  $10^{-2}$  / No loss of service, applies also if a bearer with another characteristics is used in the test.
+
+## 6.2 Performance criteria for transient phenomena for BS
+
+The test should be, where possible, be performed using a bearer with the characteristics of data rate and BLER defined in Table 2. If the test is not performed using one of these bearers (for, example, of none of them are supported by the BS), the characteristics of the bearer used shall be recorded.
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 2 during the test. If the Uplink and Downlink paths are evaluated as a one loop then the criteria is two times the value shown in Table 2. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 2: BS Performance Criteria for transient phenomena for BS**
+
+| Bearer Information Data Rate | Performance Criteria                                                                |
+|------------------------------|-------------------------------------------------------------------------------------|
+| 12.2 kbps                    | BLER > $10^{-2}$ temporarily,<br>however the communication link shall be maintained |
+| 64 kbps                      | BLER > $10^{-2}$ temporarily,<br>however the communication link shall be maintained |
+| 144 kbps                     | BLER > $10^{-2}$ temporarily,<br>however the communication link shall be maintained |
+| 384 kbps                     | BLER > $10^{-2}$ temporarily,<br>however the communication link shall be maintained |
+
+NOTE: The performance criteria, BLER >  $10^{-2}$  temporarily / however the communication link shall be maintained, applies also if a bearer with another characteristics is used in the test.
+
+## 6.3 (void)
+
+## 6.4 Performance criteria for continuous phenomena for Ancillary equipment
+
+The apparatus shall continue to operate as intended during and after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss of performance. If the minimum performance level or the permissible performance loss is not specified by the manufacture, either of these may be
+
+derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended.
+
+## 6.5 Performance criteria for transient phenomena for Ancillary equipment
+
+The apparatus shall continue to operate as intended after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss of performance. During the test, degradation of performance is however allowed. If the minimum performance level or the permissible performance loss is not specified by the manufacture, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended.
+
+## 6.6 (void)
+
+## 6.7 Performance criteria for continuous phenomena for repeaters
+
+The gain of the EUT shall be measured throughout the period of exposure of the phenomenon. The gain measured during the test shall not change from the gain measured before the test by more than  $\pm 1$  dB. At the conclusion of the test the EUT shall operate as intended with no loss of user control functions or stored data.
+
+## 6.8 Performance criteria for transient phenomena for repeaters
+
+The gain of the EUT shall be measured before the test and after each exposure. At the conclusion of each exposure the gain of the EUT shall not have changed by more than  $\pm 1$  dB. At the conclusion of the total test comprising the series of individual exposures, the EUT shall operate as intended with no loss of user control functions or stored data, as declared by the manufacturer, and the gain of the EUT shall not have changed by more than  $\pm 1$  dB.
+
+## 6.9 (void)
+
+# 7 Applicability overview
+
+## 7.1 Emission
+
+Table 3: Emission applicability
+
+| Phenomenon                       | Application                | Equipment test requirement |                     |            | Reference subclause in the present document | Reference Standard                        |
+|----------------------------------|----------------------------|----------------------------|---------------------|------------|---------------------------------------------|-------------------------------------------|
+|                                  |                            | BS equipment               | Ancillary equipment | Repeater   |                                             |                                           |
+| Radiated emission (NOTE 2)       | Enclosure                  | applicable                 |                     | applicable | 8.3.1                                       | ITU-R SM.329 [12]                         |
+| Radiated emission                | Enclosure                  |                            | applicable          |            | 8.3.2                                       | CISPR 32 [28]                             |
+| Conducted emission               | DC power input/output port | applicable                 | applicable          | applicable | 8.4                                         | CISPR 32 [28], CISPR 16-1-1 [14]          |
+| Conducted emission               | AC mains input/output port | applicable                 | applicable          | applicable | 8.5                                         | CISPR 32 [28]                             |
+| Harmonic current emissions       | AC mains input port        | applicable                 | applicable          | applicable | 8.6                                         | IEC 61000-3-2 [15] or IEC 61000-3-12 [25] |
+| Voltage fluctuations and flicker | AC mains input port        | applicable                 | applicable          | applicable | 8.7                                         | IEC 61000-3-3 [16] or IEC 61000-3-11 [26] |
+| Conducted emission               | Telecommunication port     | applicable                 | applicable          | applicable | 8.8                                         | CISPR 32 [28]                             |
+
+NOTE 1: Spurious emissions from antenna connector shall be measured according to TS 25.141 [3] and TS 25.142 [4] and TS 25.143 [11].
+
+NOTE 2: The radiated emissions requirement for the BS equipment covers radiated emissions in the spurious domain. Note that in ETSI standards and in 3GPP GERAN specifications it is considered a part of radio aspects.
+
+## 7.2 Immunity
+
+Table 4: Immunity applicability
+
+| Phenomenon                               | Application                                                               | Equipment test requirement |                     |            | Reference subclause in the present document | Reference standard |
+|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------|------------|---------------------------------------------|--------------------|
+|                                          |                                                                           | BS equipment               | Ancillary equipment | Repeater   |                                             |                    |
+| RF electromagnetic field (80 - 6000 MHz) | Enclosure                                                                 | applicable                 | applicable          | applicable | 9.3                                         | IEC 61000-4-3 [18] |
+| Electrostatic discharge                  | Enclosure                                                                 | applicable                 | applicable          | applicable | 9.4                                         | IEC 61000-4-2 [17] |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | applicable          | applicable | 9.5                                         | IEC 61000-4-4 [19] |
+| RF common mode 0,15 - 80 MHz             | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | applicable          | applicable | 9.6                                         | IEC 61000-4-6 [21] |
+| Voltage dips and interruptions           | AC mains power input ports                                                | applicable                 | applicable          | applicable | 9.7                                         | IEC 61000-4-11     |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | applicable                 | applicable          | applicable | 9.8                                         | IEC 61000-4-5 [20] |
+
+## 7.3 Applicability of requirements in TS 37.113
+
+For a BS that is UTRA (single-RAT) capable only, the requirements in the present document are applicable and additional conformance to TS 37.113 [27] is optional. For a BS additionally conforming to TS 37.113 [27], conformance to some of the emission test requirements in the present document can be demonstrated through the corresponding requirements in TS 37.113 [27] as listed in Table 4A and conformance to some of the immunity test requirements in the present document can be demonstrated through the corresponding requirements in TS 37.113 [27] as listed in Table 4B.
+
+Table 4A: Alternative emission test requirements for a BS additionally conforming to TS 37.113 [27]
+
+| Phenomenon                       | Application                | Clause in the present document | Alternative clause in TS 37.113 [27] |
+|----------------------------------|----------------------------|--------------------------------|--------------------------------------|
+| Radiated emission                | Enclosure                  | 8.3.1                          | 8.2.1                                |
+| Conducted emission               | DC power input/output port | 8.4                            | 8.3                                  |
+| Conducted emission               | AC mains input/output port | 8.5                            | 8.4                                  |
+| Harmonic current emissions       | AC mains input port        | 8.6                            | 8.5                                  |
+| Voltage fluctuations and flicker | AC mains input port        | 8.7                            | 8.6                                  |
+| Conducted emission               | Telecommunication port     | 8.8                            | 8.7                                  |
+
+**Table 4B: Alternative immunity test requirements for a BS additionally conforming to TS 37.113 [27]**
+
+| <b>Phenomenon</b>                        | <b>Application</b>                                                        | <b>Clause in the present document</b> | <b>Alternative clause in TS 37.113 [27]</b> |
+|------------------------------------------|---------------------------------------------------------------------------|---------------------------------------|---------------------------------------------|
+| RF electromagnetic field (80 - 6000 MHz) | Enclosure                                                                 | 9.3                                   | 9.2                                         |
+| Electrostatic discharge                  | Enclosure                                                                 | 9.4                                   | 9.3                                         |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | 9.5                                   | 9.4                                         |
+| RF common mode (0,15 - 80 MHz)           | Signal, telecommunications and control ports, DC and AC power input ports | 9.6                                   | 9.5                                         |
+| Voltage dips and interruptions           | AC mains power input ports                                                | 9.7                                   | 9.6                                         |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | 9.8                                   | 9.7                                         |
+
+# 8 Emission
+
+## 8.1 Methods of measurement and limits for EMC emissions
+
+## 8.2 Test configurations
+
+This subclause defines the configurations for emission tests as follows:
+
+- the equipment shall be tested under normal test conditions as specified in the functional standards;
+- the test configuration shall be as close to normal intended use as possible;
+- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- the test conditions, test configuration and mode of operation shall be recorded in the test report;
+- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- the test arrangements for transmitter and receiver sections of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter section and receiver section of the EUT may be carried out simultaneously to reduce test time.
+
+## 8.3 Radiated emission from Base station, Repeater and ancillary equipment
+
+### 8.3.1 Radiated emission, Base stations and Repeater
+
+This test is applicable to Base station and Repeater. This test shall be performed on a representative configuration of the Base station or Repeater.
+
+#### 8.3.1.1 Definition
+
+This test assesses the ability of BS and Repeater to limit unwanted emission from the enclosure port.
+
+#### 8.3.1.2 Test method
+
+##### 8.3.1.2.1 FDD and 3,84 Mcps TDD option
+
+- a) A test site fulfilling the requirements of ITU-R SM. 329 [12] shall be used. The BS or Repeater shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads.
+
+Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the BS or Repeater shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarization plane.
+
+NOTE: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2,15 dB between e.i.r.p. and e.r.p.
+
+$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2,15 \quad \text{Ref: ITU-R SM.329 ANNEX 1 [12].}$$
+
+- b) The BS shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the base station to transmit a signal as stated for measurement of spurious emission for FDD in the TS25.141 [3] and for 3.84 Mcps TDD option in the TS25.142 [4].
+
+In case of a Repeater the gain and the output power shall be set to the maximum value as declared by the manufacturer.
+
+- c) The received power shall be measured over the frequency range 30 MHz to 12.75 GHz, excluding 12.5MHz below the first carrier frequency to 12.5 MHz above the last carrier frequency used. The measurement bandwidth shall be 100 kHz between 30 MHz and 1 GHz and 1 MHz above 1 GHz as given in ITU-R SM.329 [12]. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. Unless otherwise stated, all measurements are done as mean power (RMS).
+
+##### 8.3.1.2.2 1,28 Mcps TDD option
+
+- a) A test site fulfilling the requirements of ITU-R SM. 329 [12] shall be used. The BS shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads.
+
+Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the BS shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarisation plane.
+
+NOTE: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2,15 dB between e.i.r.p. and e.r.p.
+
+$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2,15 \quad \text{Ref: ITU-R SM.329 ANNEX 1 [12].}$$
+
+- b) The BS shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the base station to transmit a signal as stated for measurement of spurious emission for 1.28 Mcps TDD in the TS25.142 [4].
+- c) The received power shall be measured over the frequency range 30 MHz to 12.75 GHz, excluding 4MHz below the first carrier frequency to 4 MHz above the last carrier frequency used. The measurement bandwidth shall be 100 kHz between 30 MHz and 1 GHz and 1 MHz above 1 GHz as given in ITU-R SM.329 [12]. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. Unless otherwise stated, all measurements are done as mean power (RMS).
+
+#### 8.3.1.3 Limits
+
+The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R Recommendations SM.329 [12] and SM.1539 [23].
+
+##### 8.3.1.3.1 FDD and 3,84 Mcps TDD option
+
+The BS or the Repeater shall meet the limits below:
+
+**Table 5: Limits for radiated emissions from BS and repeater**
+
+| Frequency range                                                                                                             | Minimum requirement (e.r.p.)/Reference Bandwidth |
+|-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|
+| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$                                                                                  | -36 dBm/100 kHz                                  |
+| $1 \text{ GHz} \leq f < 12,75 \text{ GHz}$                                                                                  | -30 dBm/ 1MHz                                    |
+| $Fc1 - 12,5 \text{ MHz} < f < Fc2+12,5 \text{ MHz}$ (Note 1)                                                                | Not defined                                      |
+| NOTE 1: For BS capable of multi-band operation, the frequency ranges relating to the carriers of all supported bands apply. |                                                  |
+
+Key:
+
+Fc1: Center frequency of first carrier frequency used by the BS and repeater.
+
+Fc2: Center frequency of last carrier frequency used by the BS and repeater.
+
+##### 8.3.1.3.2 1,28 Mcps TDD option
+
+The BS shall meet the limits below:
+
+**Table 5A: Limits for radiated emissions from BS**
+
+| Frequency range                               | Minimum requirement (e.r.p.)/Reference Bandwidth |
+|-----------------------------------------------|--------------------------------------------------|
+| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$    | -36 dBm/100 kHz                                  |
+| $1 \text{ GHz} \leq f < 12,75 \text{ GHz}$    | -30 dBm/ 1MHz                                    |
+| $Fc1 - 4 \text{ MHz} < f < Fc2+4 \text{ MHz}$ | Not defined                                      |
+
+Key:
+
+Fc1: Center frequency of first carrier frequency used by the BS.
+
+Fc2: Center frequency of last carrier frequency used by the BS.
+
+#### 8.3.1.4 Interpretation of the measurement results
+
+The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows:
+
+- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document;
+- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report;
+- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the figures in table 5B for BS and repeater.
+
+Table 5B specifies the Maximum measurement uncertainty of the Test System. The Test System shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated.
+
+A confidence level of 95% is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment.
+
+**Table 5B: Maximum measurement uncertainty (BS, and Repeater)**
+
+| Parameter                                              | Uncertainty for EUT dimension $\leq 1$ m | Uncertainty for EUT dimension $> 1$ m |
+|--------------------------------------------------------|------------------------------------------|---------------------------------------|
+| Effective radiated RF power between 30 MHz to 180 MHz  | $\pm 6$ dB                               | $\pm 6$ dB                            |
+| Effective radiated RF power between 180 MHz to 4 GHz   | $\pm 4$ dB                               | $\pm 6$ dB                            |
+| Effective radiated RF power between 4 GHz to 12,75 GHz | $\pm 6$ dB                               | $\pm 9^*$ dB                          |
+
+\*Note: This value may be reduced to  $\pm 6$  dB when further information on the potential radiation characteristic of the EUT is available.
+
+NOTE: If the Test System for a test is known to have a measurement uncertainty greater than that specified in table 5B, this equipment can still be used, provided that an adjustment is made follows:
+
+Any additional uncertainty in the Test System over and above that specified in table 5B is used to tighten the Test Requirements - making the test harder to pass. This procedure will ensure that a Test System not compliant with table 5B does not increase the probability of passing an EUT that would otherwise have failed a test if a Test System compliant with table 5B had been used.
+
+### 8.3.2 Radiated emission, Ancillary equipment
+
+This test is applicable to ancillary equipment. This test shall be performed on a representative configuration of the ancillary equipment.
+
+#### 8.3.2.1 Definition
+
+This test assesses the ability of ancillary equipment to limit unwanted emission from the enclosure port.
+
+#### 8.3.2.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28]
+
+#### 8.3.2.3 Limits
+
+The ancillary equipment shall meet the limits according to CISPR 32 [28] shown in table 6 and table 6A.
+
+**Table 6: Limits for radiated emissions from ancillary equipment, measured on a stand-alone basis (10 m measuring distance)**
+
+| Frequency range  | Quasi-peak      |
+|------------------|-----------------|
+| 30 MHz-230 MHz   | 30 dB $\mu$ V/m |
+| 230 MHz-1000 MHz | 37 dB $\mu$ V/m |
+
+**Table 6A: Limits for radiated emissions from ancillary equipment, measured on a stand-alone basis (3 m measuring distance)**
+
+| Frequency range GHz                                        | Average limit dB $\mu$ V/m | Peak limit dB $\mu$ V/m |
+|------------------------------------------------------------|----------------------------|-------------------------|
+| 1 to 3                                                     | 50                         | 70                      |
+| 3 to 6                                                     | 54                         | 74                      |
+| Note: The lower limit applies at the transition frequency. |                            |                         |
+
+## 8.4 Conducted emission DC power input/output port
+
+This test is applicable to equipment which may have DC cables longer than 3 m.
+
+If the DC power cable of the radio equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in subclause 8.5.
+
+This test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 8.4.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the DC power input/output ports.
+
+### 8.4.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28] and the Artificial Mains Network (AMN) shall be connected to a DC power source.
+
+In the case of DC output ports, the ports shall be connected via a AMN to a load drawing the rated current of the source.
+
+A measuring receiver shall be connected to each AMN measurement port in turn and the conducted emission recorded.
+
+The equipment shall be installed with a ground plane as defined in CISPR 32 [28]. The reference earth point of the AMNs shall be connected to the reference ground plane with a conductor as short as possible.
+
+The measurement receiver shall be in accordance with the requirements of section one of CISPR 16-1 [14].
+
+### 8.4.3 Limits
+
+The equipment shall meet the limits below (including the average limit and the quasi-peak limit) when using, respectively, an average detector receiver and a quasi-peak detector receiver and measured in accordance with the method described in subclause 8.4.2 above. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary.
+
+The equipment shall meet the limits given in table 7.
+
+**Table 7: Limits for conducted emissions**
+
+| <b>Frequency range</b> | <b>Quasi-peak</b> | <b>Average</b> |
+|------------------------|-------------------|----------------|
+| >0,15-0,5MHz           | 79dB $\mu$ V      | 66dB $\mu$ V   |
+| >0,5-30 MHz            | 73dB $\mu$ V      | 60dB $\mu$ V   |
+
+## 8.5 Conducted emissions, AC mains power input/output port
+
+This test is applicable to equipment powered by the AC mains.
+
+This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT.
+
+This test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 8.5.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the AC mains power input/output ports.
+
+### 8.5.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28].
+
+Mains connected ancillary equipment which is not part of the EUT shall be connected to the mains via a separate AMN. According to CISPR 16-1 [14], the Protective Earth (PE) conductor shall also be terminated by a 50  $\Omega$ /50  $\mu$ H common mode RF impedance.
+
+### 8.5.3 Limits
+
+The equipment shall meet the limits below (including the average limit and the quasi-peak limit) when using, respectively, an average detector receiver and a quasi-peak detector receiver and measured in accordance with the method described in subclause 8.5.2 above. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary.
+
+**Table 8: Limits for conducted emissions**
+
+| Frequency range                                                                                           | Quasi-peak         | Average            |
+|-----------------------------------------------------------------------------------------------------------|--------------------|--------------------|
+| > 0,15-0,5 MHz                                                                                            | 66 - 56 dB $\mu$ V | 56 - 46 dB $\mu$ V |
+| > 0,5- 5 MHz                                                                                              | 56 dB $\mu$ V      | 46 dB $\mu$ V      |
+| > 5-30 MHz                                                                                                | 60 dB $\mu$ V      | 50 dB $\mu$ V      |
+| NOTE: The limit decreases linearly with the logarithm of the frequency in the range 0,15 MHz to 0,50 MHz. |                    |                    |
+
+Alternatively, for equipment intended to be used in telecommunication centres the limits given in table 9 shall be used.
+
+**Table 9: Limits for conducted emissions**
+
+| Frequency range | Quasi-peak   | Average      |
+|-----------------|--------------|--------------|
+| >0,15-0,5MHz    | 79dB $\mu$ V | 66dB $\mu$ V |
+| >0,5-30 MHz     | 73dB $\mu$ V | 60dB $\mu$ V |
+
+## 8.6 Harmonic Current emissions (AC mains input port)
+
+The requirements of IEC 61000-3-2 [15] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [25] applies.
+
+## 8.7 Voltage fluctuations and flicker (AC mains input port)
+
+The requirements of IEC 61000-3-3 [16] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [26] applies.
+
+## 8.8 Telecommunication ports
+
+This test is applicable for radio equipment and/or ancillary equipment for fixed use which have telecommunication ports.
+
+This test shall be performed on a representative configuration of radio equipment, the associated ancillary equipment, or a representative configuration of the combination of radio and ancillary equipment.
+
+### 8.8.1 Definition
+
+This test assesses the EUT unwanted emission present at the telecommunication ports.
+
+### 8.8.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28].
+
+The measurement frequency range extends from 150 kHz to 30 MHz. When the EUT is a transmitter operating at frequencies below 30 MHz, then the exclusion band for transmitters applies (see subclause 4.5) for measurements in the transmit mode of operation.
+
+### 8.8.3 Limits
+
+The telecommunication ports shall meet the limits according to CISPR 32 [28] shown in table 10.
+
+**Table 10: Limits for conducted emissions from telecommunication ports**
+
+| Frequency range<br>MHz | Voltage limits<br>dB (μV) |          | Current limits<br>dB (μA) |          |
+|------------------------|---------------------------|----------|---------------------------|----------|
+|                        | Quasi-peak                | Average  | Quasi-peak                | Average  |
+| 0,15 to 0,5            | 84 to 74                  | 74 to 64 | 40 to 30                  | 30 to 20 |
+| 0,5 to 30              | 74                        | 64       | 30                        | 20       |
+
+NOTE 1: The limits decrease linearly with the logarithm of the frequency in the range 0,15 MHz to 0,5 MHz.  
+NOTE 2: The current and voltage disturbance limits are derived for use with an impedance stabilization network (ISN) which presents a common mode (asymmetric mode) impedance of 150 Ω to the telecommunication port under test (conversion factor is  $20 \log_{10} 150/I = 44 \text{ dB}$ ).
+
+Alternatively, for equipment intended to be used in telecommunication centres only, the limits given in table 11 may be used.
+
+**Table 11: Limits for conducted emissions from telecommunication ports of equipment intended for use in telecommunication centres only**
+
+| Frequency range<br>MHz | Voltage limits<br>dB (μV) |          | Current limits<br>dB (μA) |          |
+|------------------------|---------------------------|----------|---------------------------|----------|
+|                        | Quasi-peak                | Average  | Quasi-peak                | Average  |
+| 0,15 to 0,5            | 97 to 87                  | 84 to 74 | 53 to 43                  | 40 to 30 |
+| 0,5 to 30              | 87                        | 74       | 43                        | 30       |
+
+NOTE 1: The limits decrease linearly with the logarithm of the frequency in the range 0,15 MHz to 0,5 MHz.  
+NOTE 2: The current and voltage disturbance limits are derived for use with an impedance stabilization network (ISN), which presents a common mode (asymmetric mode) impedance of 150 Ω to the telecommunication port under test (conversion factor is  $20 \log_{10} 150/I = 44 \text{ dB}$ ).
+
+# 9 Immunity
+
+## 9.1 Test methods and levels for immunity tests
+
+## 9.2 Test configurations
+
+This subclause defines the configurations for immunity tests as follows:
+
+- the equipment shall be tested under normal test conditions as specified in the functional standards;
+- the test configuration shall be as close to normal intended use as possible;
+- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- the test conditions, test configuration and mode of operation shall be recorded in the test report;
+- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated;
+
+- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- Immunity tests on the entire base station shall be performed by establishing communication links at the air-interface (e.g. with the mobile simulator) and the Iub-interface (e.g. with an RNC simulator) and evaluating the BLER (see figure 2);
+- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the air-interface and Iub-interface. BLER evaluation may be carried out at either interface, where appropriate, and the measurements for the Uplink and Downlink paths may be carried out as a single path looped at either the air-interface or Iub-interface. In case of looping is used care have to be taken that the BLER information doesn't change due to looping. The BLER evaluation shall be based on the number of transmitted blocks i.e including possible deleted blocks.
+- For BS capable of multi-band operation, communication links shall be established in such a way that all operating band(s) are activated during the test according to the applicable test configurations in subclause 4.6. Performance assessment may be done separately for each operating band.
+
+![Figure 2: Communication link set up for BS immunity measurement. The diagram shows a 'Mobile simulator' box on the left connected to a 'Base station' box in the center. The 'Base station' box contains 'TX' (transmitter), 'RX 1', 'RX 2', and '(terminated)'. Arrows indicate bidirectional communication between the 'Mobile simulator' and the 'Base station'. The 'Base station' is also connected to an 'RNC simulator' box on the right, with arrows indicating bidirectional communication between them.](e90987faabad6a6665cd8ed1151dc474_img.jpg)
+
+```
+
+graph LR
+    MS[Mobile simulator] <--> BS[Base station  
+TX  
+RX 1  
+RX 2  
+(terminated)]
+    BS <--> RNC[RNC simulator]
+  
+```
+
+Figure 2: Communication link set up for BS immunity measurement. The diagram shows a 'Mobile simulator' box on the left connected to a 'Base station' box in the center. The 'Base station' box contains 'TX' (transmitter), 'RX 1', 'RX 2', and '(terminated)'. Arrows indicate bidirectional communication between the 'Mobile simulator' and the 'Base station'. The 'Base station' is also connected to an 'RNC simulator' box on the right, with arrows indicating bidirectional communication between them.
+
+Figure 2: Communication link set up for BS immunity measurement
+
+## 9.3 RF electromagnetic field (80 MHz - 6000 MHz)
+
+The test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.3.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure.
+
+### 9.3.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-3 [18]:
+
+- for transmitters, receivers and transceivers the following requirements shall apply:
+- the test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz;
+- the stepped frequency increments shall be 1 % of the momentary frequency;
+- the test shall be performed over the frequency range 80 MHz - 6000 MHz;
+- responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3;
+- the frequencies selected during the test shall be recorded in the test report.
+
+### 9.3.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.1 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.4 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.7 shall apply.
+
+## 9.4 Electrostatic discharge
+
+The test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.4.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of an electrostatic discharge.
+
+### 9.4.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-2 [17]:
+
+- for contact discharge, the equipment shall pass at  $\pm 4$  kV;
+- for air discharge shall pass at  $\pm 8$  kV;
+- electrostatic discharge shall be applied to all exposed surfaces of the EUT except where the user documentation specially indicates a requirement for appropriate protective measures.
+
+NOTE: Ensure that the EUT is fully discharged between each ESD exposure.
+
+### 9.4.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.5 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.8 shall apply.
+
+## 9.5 Fast transients common mode
+
+The test shall be performed on AC mains power input ports.
+
+This test shall be performed on signal ports, telecommunication ports, control ports and DC power input/output ports if the cables may be longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.5.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of fast transients present on one of the input/output ports.
+
+### 9.5.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-4 [19]:
+
+- the test level for signal ports, telecommunication ports and control ports shall be 0,5 kV open circuit voltage as given in IEC 61000-4-4 [19];
+- the test level for DC power input/output ports shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [19];
+- the test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [19].
+
+For AC and DC power input ports the transients shall be applied (in parallel) to all the conductors in the cable with reference to the cabinet reference earth (true common mode) and the source impedance shall be 50 Ω.
+
+### 9.5.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.5 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.8 shall apply.
+
+## 9.6 RF common mode (0,15 MHz - 80 MHz)
+
+The test shall be performed on AC mains power input/output ports.
+
+This test shall be performed on signal ports, telecommunication ports, control and DC power input/output ports, which may have cables longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+NOTE: This test can also be performed using the intrusive method, where appropriate, see IEC 61000-4-6 [21].
+
+### 9.6.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic disturbance.
+
+### 9.6.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-6 [21]:
+
+- the test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz;
+- the stepped frequency increments shall be 50 kHz in the frequency range 150 kHz to 5 MHz and 1% frequency increment of the momentary frequency in the frequency range 5 MHz to 80 MHz.
+- the test level shall be severity level 2 as given in IEC 61000-4-6 [21] corresponding to 3 V rms, at a transfer impedance of 150 Ω;
+- the test shall be performed over the frequency range 150 kHz - 80 MHz;
+- the injection method to be used shall be selected according to the basic standard IEC 61000-4-6 [21];
+- responses of stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3;
+- the frequencies of the immunity test signal selected and used during the test shall be recorded in the test report.
+
+### 9.6.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.1 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.4 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.7 shall apply.
+
+## 9.7 Voltage dips and interruptions
+
+The tests shall be performed on AC mains power input ports.
+
+These tests shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.7.1 Definition
+
+These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports.
+
+### 9.7.2 Test method and level
+
+The following requirements shall apply.
+
+The test method shall be in accordance with IEC 61000-4-11 [22].
+
+The test levels shall be:
+
+- a voltage dip corresponding to a reduction of the supply voltage of 30 % for 10 ms;
+- a voltage dip corresponding to a reduction of the supply voltage of 60 % for 100 ms;
+- a voltage interruption corresponding to a reduction of the supply voltage of > 95 % for 5 000 ms.
+
+### 9.7.3 Performance criteria
+
+For a voltage dip corresponding to a reduction of the supply voltage of 30 % for 10 ms the performance criteria for transient phenomena shall be applied:
+
+- Criteria 6.2 for base station
+
+- Criteria 6.5 for ancillary equipment
+- Criteria 6.8 for repeater
+
+For a voltage dip corresponding to a reduction of the supply voltage of 60 % for 100 ms and/or a voltage interruption corresponding to a reduction of the supply voltage of > 95 % for 5 000 ms, the following applies:
+
+1. In the case where the equipment is fitted with or connected to a battery back-up, the following performance criteria shall be applied:
+  - Criteria 6.2 for base station
+  - Criteria 6.5 for ancillary equipment
+  - Criteria 6.8 for repeater
+2. In the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) volatile user data may have been lost and if applicable the communication link need not to be maintained and lost functions should be recoverable by user or operator:
+  - No unintentional responses shall occur at the end of the test
+  - In the event of loss of communications link or in the event of loss of user data, this fact shall be recorded in the test report
+
+## 9.8 Surges, common and differential mode
+
+The tests shall be performed on AC mains power input ports.
+
+This test shall be additionally performed on telecommunication ports.
+
+These tests shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.8.1 Definition
+
+These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports.
+
+### 9.8.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-5 [20].
+
+The requirements and evaluation of test results given in clause 9.8.2.1 (telecommunication ports, outdoor cables), clause 9.8.2.2 (telecommunication ports, indoor cables) and clause 9.8.2.3 (AC power ports) shall apply, but no test shall be required where normal functioning cannot be achieved, because of the impact of the CDN on the EUT.
+
+#### 9.8.2.1 Test method for telecommunication ports directly connected to outdoor cables
+
+The test level for telecommunications ports, intended to be directly connected to the telecommunications network via outdoor cables, shall be 1 kV line to ground as given in IEC 61000-4-5 [20], however, in telecommunications centres 0,5 kV line to ground shall be used. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [20].
+
+The test generator shall provide the 1,2/50 µs pulse as defined in IEC 61000-4-5 [20]
+
+#### 9.8.2.2 Test method for telecommunication ports connected to indoor cables
+
+The test level for telecommunication ports, intended to be connected to indoor cables (longer than 10 m) shall be 0,5 kV line to ground. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [20]
+
+The test generator shall provide the 1,2/50  $\mu\text{s}$  pulse as defined in IEC 61000-4-5 [20].
+
+#### 9.8.2.3 Test method for AC power ports
+
+The test level for AC power input ports shall be 2 kV line to ground, and 1 kV line to line, with the output impedance of the surge generator as given in IEC 61000-4-5 [20].
+
+In telecom centres 1 kV line to ground and 0,5 kV line to line shall be used.
+
+The test generator shall provide the 1,2/50  $\mu\text{s}$  pulse as defined in IEC 61000-4-5 [20].
+
+### 9.8.3 Performance criteria
+
+#### **Base station:**
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### **Ancillary equipment:**
+
+The performance criteria of subclause 6.5 shall apply.
+
+#### **Repeater:**
+
+The performance criteria of subclause 6.8 shall apply.
+
+# Annex A (informative): Change History
+
+| TSG   | Doc       | CR   | R | Title                                                                                                          | Cat | Curr   | New    | Work Item                |
+|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------|-----|--------|--------|--------------------------|
+| RP-37 |           |      |   | Rel-8 version created from v7.6.0                                                                              |     |        | 8.0.0  |                          |
+| RP-37 | RP-070658 | 0036 |   | Introduction of UMTS1500 requirements (Rel-8)                                                                  | B   | 7.6.0  | 8.0.0  | RInImp8-UMTS1500         |
+| RP-39 | RP-080124 | 0038 | 1 | Introduction of UMTS700 requirements                                                                           | B   | 8.0.0  | 8.1.0  | RInImp8-UMTS700          |
+| RP-40 | RP-080384 | 0039 |   | Introduction of UMTS2300 requirements                                                                          | B   | 8.1.0  | 8.2.0  | RInImp8-UMTS2300TD D     |
+| RP-41 | RP-080631 | 0040 |   | EMC for BS equipment divided into more than one cabinet                                                        | B   | 8.2.0  | 8.3.0  | TEI8                     |
+| RP-43 | RP-080197 | 0041 |   | Introduction of band 1880MHz for 25.113                                                                        | F   | 8.3.0  | 8.4.0  | RInImp9-UMTS1880TD D     |
+| RP-44 | RP-090559 | 0042 |   | Introduction of Extended UMTS800 requirements                                                                  | B   | 8.4.0  | 9.0.0  | RInImp9-UMTSLTE800       |
+| RP-46 | RP-091286 | 043  |   | Introduction of Extended UMTS1500 requirements for TS25.113 (Technically endorsed at RAN 4 52bis in R4-093626) | B   | 9.0.0  | 9.1.0  | UMTSLTE1500              |
+| RP-46 | RP-091279 | 045  |   | BS emission applicability correction (Technically endorsed at RAN 4 52bis in R4-094024)                        | A   | 9.0.0  | 9.1.0  | TEI8                     |
+| RP-47 | RP-100263 | 47   |   | Introduction of Band XX in 25.113                                                                              | B   | 9.1.0  | 9.2.0  | RInImp9-UMTSLTE800EU     |
+| RP-49 | RP-100923 | 048  |   | Clarification of radiated emissions requirement                                                                | F   | 9.2.0  | 9.3.0  | RInImp9-RFmulti          |
+| RP-50 | RP-101334 | 052  |   | Band XII channel arrangement correction on 25.113                                                              | A   | 9.3.0  | 9.4.0  | TEI8                     |
+| RP-50 | RP-101338 | 050  |   | Correction due to the introduction of the definition of pass band                                              | A   | 9.3.0  | 9.4.0  | TEI8                     |
+| RP-51 | RP-110344 | 0055 | - | Applicability of EMC requirements                                                                              | F   | 9.4.0  | 9.5.0  | TEI9                     |
+| RP-51 | -         | -    |   | Automatic upgrade from rel-9 to rel-10                                                                         | -   | 9.5.0  | 10.0.0 | -                        |
+| RP-52 | RP-110804 | 056  |   | Add Expanded 1900MHz band in 25.113                                                                            | B   | 10.0.0 | 10.1.0 | E1900-Core               |
+| RP-53 | RP-111255 | 057  |   | Add Band 22/XXII for LTE/UMTS 3500 (FDD) to TS 25.113                                                          | B   | 10.1.0 | 10.2.0 | RInImp8-UMTSLTE3500      |
+| RP-55 | RP-120305 | 058  |   | Add upper 850MHz band in 25.113                                                                                | B   | 10.2.0 | 11.0.0 | e850_UB-Core             |
+| RP-64 | RP-140926 | 061  |   | Introduction of operating band XXXII in TS25.113                                                               | B   | 11.0.0 | 12.0.0 | LTE_UTRA_SD L_BandL-Core |
+| RP-65 | RP-141562 | 062  | 1 | Update of definitions to support supplemental DL in TS25.113                                                   | F   | 12.0.0 | 12.1.0 | TEI12                    |
+| RP-68 | RP-150955 | 064  |   | EMC testing of multi-band operation for UTRA BS                                                                | A   | 12.1.0 | 12.2.0 | MB_MSR_RF-Perf           |
+| SP-70 | -         | -    | - | Update to Rel-13 version (MCC)                                                                                 | -   | 12.2.0 | 13.0.0 |                          |
+|       |           |      |   | Editorial correction in the cover page                                                                         |     | 13.0.0 | 13.0.1 |                          |
+
+| Change history |         |           |      |     |     |                                                                   |             |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                   | New version |
+| 2016/06        | RP-72   | RP-161142 | 0065 | 1   | F   | Clarification in EMC environmental conditions references          | 13.1.0      |
+| 2017-03        | RP-75   | -         | -    | -   | -   | Update to Rel-14 version (MCC)                                    | 14.0.0      |
+| 2018-03        | RAN#79  | RP-180282 | 0066 | 1   | F   | CR to TS 25.113: correction of the CISPR reference and ESD levels | 15.0.0      |
+| 2020-06        | SA#88   | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                    | 16.0.0      |
+| 2022-03        | SA#95   |           |      |     |     | Update to Rel-17 version (MCC)                                    | 17.0.0      |
+| 2024-03        | RAN#103 |           |      |     |     | Update to Rel-18 version (MCC)                                    | 18.0.0      |

marked/Rel-18/25_series/25116/raw.md

@@ -0,0 +1,850 @@
+
+
+# 3GPP TS 25.116 V18.0.0 (2024-03)
+
+*Technical Specification*
+
+![5G Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base station radio transmission and reception (LCR TDD) (Release 18)**
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon at its base, and a 'TM' trademark symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## --- **Keywords**
+
+UMTS, radio, repeater
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+|                                                                           |    |
+|---------------------------------------------------------------------------|----|
+| Foreword .....                                                            | 5  |
+| 1 Scope.....                                                              | 6  |
+| 2 References.....                                                         | 6  |
+| 3 Definitions, symbols and abbreviations .....                            | 6  |
+| 3.1 Definitions.....                                                      | 6  |
+| 3.2 Symbols.....                                                          | 7  |
+| 3.3 Abbreviations .....                                                   | 7  |
+| 4 General.....                                                            | 7  |
+| 4.1 Relationship between Minimum Requirements and Test Requirements ..... | 8  |
+| 4.2 Regional requirements.....                                            | 9  |
+| 5 Frequency bands and channel arrangement .....                           | 10 |
+| 5.1 General .....                                                         | 10 |
+| 5.2 Frequency bands.....                                                  | 10 |
+| 5.3 TX-RX frequency separation .....                                      | 10 |
+| 5.4 Channel arrangement.....                                              | 11 |
+| 5.4.1 Channel spacing.....                                                | 11 |
+| 5.4.2 Channel raster.....                                                 | 11 |
+| 5.4.3 Channel number.....                                                 | 11 |
+| 6 Output power.....                                                       | 11 |
+| 6.1 Maximum output power.....                                             | 11 |
+| 6.1.1 Minimum Requirements.....                                           | 11 |
+| 7 Frequency stability.....                                                | 12 |
+| 7.1 Minimum requirement.....                                              | 12 |
+| 8 Out of band gain.....                                                   | 12 |
+| 8.1 Minimum requirement.....                                              | 12 |
+| 9 Unwanted emission .....                                                 | 13 |
+| 9.1 Spectrum emission mask.....                                           | 13 |
+| 9.2 Spurious emissions.....                                               | 14 |
+| 9.2.1 Mandatory Requirements .....                                        | 15 |
+| 9.2.1.1 Spurious emissions (Category A) .....                             | 15 |
+| 9.2.1.1.1 Minimum Requirement .....                                       | 15 |
+| 9.2.1.2 Spurious emissions (Category B) .....                             | 15 |
+| 9.2.1.2.1 Minimum Requirement .....                                       | 15 |
+| 9.2.2 Co-existence with GSM 900 .....                                     | 16 |
+| 9.2.2.1 Operation in the same geographic area.....                        | 16 |
+| 9.2.2.1.1 Minimum Requirement .....                                       | 16 |
+| 9.2.2.2 Co-located base stations.....                                     | 16 |
+| 9.2.2.2.1 Minimum Requirement .....                                       | 16 |
+| 9.2.3 Co-existence with DCS 1800 .....                                    | 16 |
+| 9.2.3.1 Operation in the same geographic area.....                        | 16 |
+| 9.2.3.1.1 Minimum Requirement .....                                       | 16 |
+| 9.2.3.2 Co-located base stations.....                                     | 17 |
+| 9.2.3.2.1 Minimum Requirement .....                                       | 17 |
+| 9.2.4 Co-existence with UTRA-FDD.....                                     | 17 |
+| 9.2.4.1 Operation in the same geographic area.....                        | 17 |
+| 9.2.4.1.1 Minimum Requirement .....                                       | 17 |
+| 9.2.4.2 Co-located base stations.....                                     | 18 |
+| 9.2.4.2.1 Minimum Requirement .....                                       | 18 |
+| 9.2.5 Co-existence with unsynchronised TDD.....                           | 18 |
+| 9.2.5.1 Operation in the same geographic area.....                        | 18 |
+| 9.2.5.1.1 Minimum Requirement .....                                       | 19 |
+
+|                               |                                                                   |           |
+|-------------------------------|-------------------------------------------------------------------|-----------|
+| 9.2.5.2                       | Co-located base stations.....                                     | 19        |
+| 9.2.5.2.1                     | Minimum Requirement .....                                         | 19        |
+| 10                            | Modulation accuracy.....                                          | 20        |
+| 10.1                          | Error Vector Magnitude .....                                      | 20        |
+| 10.1.1                        | Minimum requirement.....                                          | 20        |
+| 10.2                          | Peak code domain error.....                                       | 20        |
+| 10.2.1                        | Minimum requirement.....                                          | 20        |
+| 11                            | Input intermodulation.....                                        | 20        |
+| 11.1                          | General requirement.....                                          | 20        |
+| 11.1.1                        | Minimum requirement.....                                          | 20        |
+| 12                            | Output intermodulation .....                                      | 21        |
+| 12.0                          | General .....                                                     | 21        |
+| 12.1                          | Minimum requirement.....                                          | 21        |
+| 13                            | Adjacent Channel Rejection Ratio (ACRR) .....                     | 21        |
+| 13.1                          | Definitions and applicability .....                               | 21        |
+| 13.2                          | Co-existence with UTRA.....                                       | 21        |
+| 13.2.1.                       | Minimum Requirements.....                                         | 21        |
+| 14                            | Timing Accuracy.....                                              | 22        |
+| 14.1                          | Minimum requirement.....                                          | 22        |
+| <b>Annex A (normative):</b>   | <b>Environmental requirements for the Repeater equipment.....</b> | <b>24</b> |
+| <b>Annex B (informative):</b> | <b>Change history.....</b>                                        | <b>25</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# 1 Scope
+
+The present document establishes the minimum RF characteristics of LCR TDD Repeater.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] ITU-R Recommendation SM.329, "Unwanted emissions in the spurious domain".
+- [3] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000".
+- [4] 3GPP TS 25.153: "LCR TDD Repeater conformance testing"
+- [5] 3GPP TR 25.942: "RF system scenarios".
+- [6] IEC 60721-3-3 (2002): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 3: Stationary use at weather protected locations".
+- [7] IEC 60721-3-4 (1995): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Carrier:** The modulated waveform conveying the LCR TDD physical channels
+
+**Channel bandwidth:** The RF bandwidth supporting a single LCR TDD RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.
+
+**Channel edge:** The lowest and highest frequency of the LCR TDD carrier, separated by the channel bandwidth.
+
+**Donor coupling loss:** is the coupling loss between the repeater and the donor base station.
+
+**Downlink:** Signal path where base station transmits and mobile receives.
+
+**Maximum output power, Pmax:** This is the mean power level per carrier measured at the antenna connector of the Repeater in specified reference condition.
+
+**Output power, Pout:** This is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter.
+
+**Pass band:** The repeater can have one or several pass bands. The pass band is the frequency range that the repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal channels. If they are not consecutive each subset of channels shall be considered as an individual pass band.
+
+**Rated output power:** Rated output power of the repeater is the mean power level per carrier that the manufacturer has declared to be available at the antenna connector.
+
+**Repeater:** A device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station)
+
+**Transmission bandwidth:** Bandwidth of an instantaneous transmission from a UE or BS, measured in Resource Block units.
+
+**Transmission bandwidth configuration:** The highest transmission bandwidth allowed for uplink or downlink in a given channel bandwidth, measured in Resource Block units.
+
+**Uplink:** Signal path where mobile transmits and base station receives.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                        |                                                                                        |
+|------------------------|----------------------------------------------------------------------------------------|
+| BW <sub>Channel</sub>  | Channel bandwidth                                                                      |
+| BW <sub>Config</sub>   | Transmission bandwidth configuration, expressed in MHz.                                |
+| BW <sub>Meas</sub>     | Measurement bandwidth                                                                  |
+| BW <sub>Signal</sub>   | Bandwidth of the repeater input signal filling the repeater pass band                  |
+| F <sub>DL_low</sub>    | The lowest frequency of the downlink operating band                                    |
+| F <sub>DL_high</sub>   | The highest frequency of the downlink operating band                                   |
+| F <sub>UL_low</sub>    | The lowest frequency of the uplink operating band                                      |
+| F <sub>UL_high</sub>   | The highest frequency of the uplink operating band                                     |
+| f <sub>offset_PB</sub> | Distance from the channel edge frequency of the first or last channel in the pass band |
+| N <sub>DL</sub>        | Downlink LARFCN                                                                        |
+| N <sub>Offs-DL</sub>   | Offset used for calculating downlink LARFCN                                            |
+| N <sub>Offs-UL</sub>   | Offset used for calculating uplink LARFCN                                              |
+| N <sub>RB</sub>        | Transmission bandwidth configuration, expressed in units of resource blocks            |
+| N <sub>UL</sub>        | Uplink LARFCN                                                                          |
+| P <sub>max</sub>       | Maximum output power                                                                   |
+| P <sub>out</sub>       | Output power                                                                           |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|        |                                                 |
+|--------|-------------------------------------------------|
+| ACRR   | Adjacent Channel Rejection Ratio                |
+| BS     | Base Station                                    |
+| LARFCN | LCR TDD Absolute Radio Frequency Channel Number |
+| PB     | Pass Band                                       |
+
+# 4 General
+
+This specification applies only to LCR TDD repeaters.
+
+Unless otherwise stated, all requirements in this specification apply to both the up-link and down-link directions.
+
+## 4.1 Relationship between Minimum Requirements and Test Requirements
+
+The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 25.153 section 4 defines Test Tolerances. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements.
+
+The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle.
+
+The Shared Risk principle is defined in ITU-R M.1545 [3].
+
+## 4.2 Regional requirements
+
+Some requirements in the present document may only apply in certain regions. Table 4.2-1 lists all requirements that may be applied differently in different regions.
+
+**Table 4.2-1: List of regional requirements**
+
+| Clause number | Requirement                                                                  | Comments                                                                                                                                                                                       |
+|---------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5.2           | Channel bandwidth                                                            | Some channel bandwidths may be applied regionally.                                                                                                                                             |
+| 5.3           | Frequency bands                                                              | Some bands may be applied regionally.                                                                                                                                                          |
+| 5.4           | Channel arrangement                                                          | The requirement is applied according to what frequency bands in Clause 5.3 that are supported by the Repeater.                                                                                 |
+| 6.1           | Maximum output power                                                         | In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal.                                        |
+| 9.1.1.1       | Operating band unwanted emissions (Category A)                               | This requirement is mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply.                                                 |
+| 9.1.1.2       | Operating band unwanted emissions (Category B)                               | This requirement is mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2], apply.                                                |
+| 9.1.3         | Operating band unwanted emissions : Additional requirements                  | These requirements may be applied regionally for some operating bands.                                                                                                                         |
+| 9.2.1.1       | Spurious emissions (Category A)                                              | This requirement is mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply.                                                 |
+| 9.2.1.2       | Spurious emissions (Category B)                                              | This requirement is mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2], apply.                                                |
+| 9.2.2.1       | Co-existence with GSM900 - Operation in the same geographic area             | This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS in geographic areas in which both GSM 900 and LCR TDD repeater are deployed.                                  |
+| 9.2.2.2       | Co-existence with GSM900 - Co-located base stations                          | This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and LCR TDD repeater are co-located.                                                              |
+| 9.2.3.1       | Co-existence with DCS1800 - Operation in the same geographic area            | This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS in geographic areas in which both DCS 1800 and LCR TDD repeater are deployed.                               |
+| 9.2.3.2       | Co-existence with DCS1800 - Co-located base stations                         | This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and LCR TDD repeater are co-located.                                                            |
+| 9.2.4.1       | Co-existence with UTRA FDD - Operation in the same geographic area           | This requirement may be applied to geographic areas in which both LCR TDD repeater and UTRA-FDD are deployed.                                                                                  |
+| 9.2.4.2       | Co-existence with UTRA FDD - Co-located base stations                        | This requirement may be applied for the protection of UTRA-FDD BS receivers when LCR TDD repeater and UTRA FDD BS are co-located.                                                              |
+| 9.2.5.1       | Co-existence with unsynchronized TDD - Operation in the same geographic area | This requirement may be applied for the protection of UTRA-TDD BS receivers in same geographic areas in which unsynchronized TDD is deployed.                                                  |
+| 9.2.5.2       | Co-existence with unsynchronized TDD -Co-located base stations               | This requirement may be applied for the protection of UTRA-TDD BS receivers when UTRA-TDD BS are unsynchronized co-located.                                                                    |
+| 11.2          | Input Intermodulation: Co-location with other systems                        | These requirements may be applied for the protection of FDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with an LCR TDD Repeater. |
+
+|      |                                                        |                                                                                                                                                                                     |
+|------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 11.3 | Input Intermodulation: Co-existence with other systems | These requirements may be applied when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS operating in another frequency band co-exist with an LCR TDD Repeater. |
+|------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+# 5 Frequency bands and channel arrangement
+
+## 5.1 General
+
+The information presented in this section is based on the chip rates of 1.28 Mcps TDD.
+
+NOTE: Other chip rates may be considered in future releases.
+
+## 5.2 Frequency bands
+
+UTRA/TDD is designed to operate in the following bands;
+
+- a) 1900 - 1920 MHz: Uplink and downlink transmission  
+2010 - 2025 MHz Uplink and downlink transmission
+- b) 1850 - 1910 MHz Uplink and downlink transmission  
+1930 - 1990 MHz Uplink and downlink transmission
+- c) 1910 - 1930 MHz Uplink and downlink transmission
+- d) 2570 - 2620 MHz Uplink and downlink transmission
+- e) 2300 - 2400 MHz Uplink and downlink transmission
+- f) 1880 - 1920 MHz: Uplink and downlink transmission
+
+Note: Deployment in existing and other frequency bands is not precluded.
+
+The co-existence of TDD and FDD in the same bands is still under study in WG4.
+
+## 5.3 TX-RX frequency separation
+
+No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe consists of 7 main timeslots where all main timeslots (at least the first one) before the single switching point are allocated DL and all main timeslots (at least the last one) after the single switching point are allocated UL.
+
+## 5.4 Channel arrangement
+
+### 5.4.1 Channel spacing
+
+The channel spacing is 1.6MHz, but this can be adjusted to optimise performance in a particular deployment scenario.
+
+### 5.4.2 Channel raster
+
+The channel raster is 200 kHz for all bands, which means that the carrier frequency must be a multiple of 200 kHz.
+
+### 5.4.3 Channel number
+
+The carrier frequency is designated by the UTRA absolute radio frequency channel number (UARFCN). The value of the UARFCN in the IMT2000 band is defined in the general case as follows:
+
+$$N_t = 5 * F \qquad 0.0 \leq F \leq 3276.6 \text{ MHz}$$
+
+where F is the carrier frequency in MHz.
+
+# 6 Output power
+
+Output power,  $P_{out}$ , of the repeater is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter.
+
+Rated output power,  $P_{RAT}$ , of the repeater is the mean power level per carrier at maximum repeater gain that the manufacturer has declared to be available at the antenna connector.
+
+## 6.1 Maximum output power
+
+Maximum output power,  $P_{max}$ , of the repeater is the mean power level per carrier measured at the antenna connector in specified reference condition.
+
+### 6.1.1 Minimum Requirements
+
+The requirements shall apply at maximum gain, with LCR TDD signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel.
+
+When the power of all signals is increased by 10 dB, compared to the power level that produce the maximum rated output power, the requirements shall still be met.
+
+In normal conditions, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power.
+
+**Table 6.1: Repeater output power; normal conditions**
+
+| Rated output power      | Limit           |
+|-------------------------|-----------------|
+| $P \geq 31 \text{ dBm}$ | +2 dB and -2 dB |
+| $P < 31 \text{ dBm}$    | +3 dB and -3 dB |
+
+In extreme conditions, the Repeater maximum output power shall remain within the limits specified in Table 6.2 relative to the manufacturer's rated output power.
+
+**Table 6.2: Repeater output power; extreme conditions**
+
+| Rated output power | Limit               |
+|--------------------|---------------------|
+| $P \geq 31$ dBm    | +2,5 dB and -2,5 dB |
+| $P < 31$ dBm       | +4 dB and -4 dB     |
+
+In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal.
+
+# 7 Frequency stability
+
+Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal.
+
+## 7.1 Minimum requirement
+
+The frequency deviation of the output signal with respect to the input signal shall be no more than  $\pm 0,01$  ppm.
+
+# 8 Out of band gain
+
+Out of band gain refers to the gain of the repeater outside the pass band.
+
+## 8.1 Minimum requirement
+
+The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station.
+
+In the intended application of the repeater, the out of band gain is less than the donor coupling loss.
+
+The repeater minimum donor coupling loss shall be declared by the manufacturer. This is the minimum required attenuation between the donor BS and the repeater for proper repeater operation.
+
+The gain outside the pass band shall not exceed the maximum level specified in table 8.1, where:
+
+- $f\_offset$  is the distance from the centre frequency of the first or last channel within the pass band.
+
+**Table 8.1: Out of band gain limits 1**
+
+| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain |
+|----------------------------------------------------------|--------------|
+| $1,0 \leq f\_offset < 1,8$ MHz                           | 60 dB        |
+| $1,8 \leq f\_offset < 5,8$ MHz                           | 45 dB        |
+| $5,8 \leq f\_offset < 10,8$ MHz                          | 45 dB        |
+| $10,8$ MHz $\leq f\_offset$                              | 35 dB        |
+
+For  $10,8$  MHz  $\leq f\_offset$  the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower.
+
+**Table 8.2: Out of band gain limits 2**
+
+| Repeater maximum output power as in 9.1.1.1                                 | Maximum gain                                                        |
+|-----------------------------------------------------------------------------|---------------------------------------------------------------------|
+| $P < 31$ dBm                                                                | Out of band gain $\leq$ minimum donor coupling loss                 |
+| $31$ dBm $\leq P < 43$ dBm                                                  | Out of band gain $\leq$ minimum donor coupling loss                 |
+| $P \geq 43$ dBm                                                             | Out of band gain $\leq$ minimum donor coupling loss - ( $P-43$ dBm) |
+| NOTE 1: The out of band gain is considered with $10,8$ MHz $\leq f\_offset$ |                                                                     |
+
+# 9 Unwanted emission
+
+## 9.1 Spectrum emission mask
+
+The mask defined in Table 9.1 to 9.3 may be mandatory in certain regions. In other regions this mask may not be applied.
+
+For regions where this clause applies, the requirement shall be met by a LCR TDD repeater transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in table 9.1 to 9.3 for the appropriate LCR TDD repeater maximum output power, in the frequency range from  $\Delta f = 0.8$  MHz to  $\Delta f_{max}$  from the carrier frequency, where:
+
+- $\Delta f$  is the separation between the carrier frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency.
+- $f_{offset}$  is the separation between the carrier frequency and the center frequency of the measuring filter.
+- $f_{offset_{max}}$  is either 4 MHz or the offset to the UMTS Tx band edge as defined in section 5.2, whichever is the greater.
+- $\Delta f_{max}$  is equal to  $f_{offset_{max}}$  minus half of the bandwidth of the measurement filter.
+
+![Illustrative diagram of spectrum emission mask showing power density vs frequency separation.](303b94716b6713757d1fdf940a6b345f_img.jpg)
+
+The figure is an illustrative diagram of a spectrum emission mask. The x-axis represents the frequency separation  $\Delta f$  from the carrier in MHz, with markers at 0.8, 1.0, 1.8, 2.4, and  $\Delta f_{max}$ . A break in the axis is indicated between 2.4 and  $\Delta f_{max}$ . The y-axis represents power density in 30kHz [dBm] on the left (ranging from -45 to -20) and in 1 MHz [dBm] on the right (ranging from -30 to -5). The mask is defined by two power levels:  $P = 26$  dBm and  $P = 34$  dBm. The mask starts at -20 dBm (30kHz) for  $\Delta f < 1.0$  MHz. At  $\Delta f = 1.0$  MHz, it drops to -26 dBm (30kHz). At  $\Delta f = 1.8$  MHz, it drops further to -34 dBm (30kHz). From  $\Delta f = 1.8$  MHz to  $\Delta f_{max}$ , the mask remains at -34 dBm (30kHz). The  $P = 26$  dBm label points to the -26 dBm (30kHz) level, and the  $P = 34$  dBm label points to the -34 dBm (30kHz) level.
+
+Illustrative diagram of spectrum emission mask
+
+Illustrative diagram of spectrum emission mask showing power density vs frequency separation.
+
+Figure 9.1
+
+**Table 9.1: Spectrum emission mask values, BS maximum output power  $P \geq 34$  dBm**
+
+| Frequency offset of measurement filter - 3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                               | Measurement bandwidth |
+|----------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------|
+| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$              | $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$               | -20 dBm                                                                                     | 30 kHz                |
+| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$              | $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$               | $-20 \text{ dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz                |
+| See note                                                       | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$                 | -28 dBm                                                                                     | 30 kHz                |
+| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$           | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                  | -13 dBm                                                                                     | 1 MHz                 |
+
+**Table 9.2: Spectrum emission mask values, BS maximum output power  $26 \leq P < 34$  dBm**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                                 | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------|
+| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$             | $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$               | P-54 dB                                                                                       | 30 kHz                |
+| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$             | $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$               | $P - 54 \text{ dB} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz                |
+| See note                                                      | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$                 | P-62 dB                                                                                       | 30 kHz                |
+| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$          | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                  | P - 47 dB                                                                                     | 1 MHz                 |
+
+**Table 9.3: Spectrum emission mask values, BS maximum output power  $P < 26$  dBm**
+
+| Frequency offset of measurement filter - 3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                               | Measurement bandwidth |
+|----------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------|
+| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$              | $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$               | -28 dBm                                                                                     | 30 kHz                |
+| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$              | $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$               | $-28 \text{ dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz                |
+| See note                                                       | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$                 | -36 dBm                                                                                     | 30 kHz                |
+| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$           | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                  | -21 dBm                                                                                     | 1 MHz                 |
+
+NOTE: This frequency range ensures that the range of values of  $f\_offset$  is continuous.
+
+## 9.2 Spurious emissions
+
+Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the base station RF output port.
+
+The requirements shall apply whatever the type of transmitter considered (single carrier or multi carrier). It applies for all transmission modes foreseen by the manufacturer's.
+
+For 1.28 Mcps TDD option, either requirement applies at frequencies within the specified frequency ranges which are more than 4 MHz under the first carrier frequency used or more than 4 MHz above the last carrier frequency used.
+
+Unless otherwise stated, all requirements are measured as mean power.
+
+### 9.2.1 Mandatory Requirements
+
+The requirements of either subclause 9.2.1.1 or subclause 9.2.1.2 shall apply.
+
+#### 9.2.1.1 Spurious emissions (Category A)
+
+The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [1], are applied.
+
+##### 9.2.1.1.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.4: LCR TDD repeater Mandatory spurious emissions limits, Category A**
+
+| Band             | Minimum requirement | Measurement Bandwidth | Notes  |
+|------------------|---------------------|-----------------------|--------|
+| 9kHz - 150kHz    | -13 dBm             | 1 kHz                 | Note 1 |
+| 150kHz - 30MHz   |                     | 10 kHz                | Note 1 |
+| 30MHz - 1GHz     |                     | 100 kHz               | Note 1 |
+| 1GHz - 12.75 GHz |                     | 1 MHz                 | Note 2 |
+
+NOTE 1: Bandwidth as in ITU SM.329 [1], s4.1  
+NOTE 2: Upper frequency as in ITU SM.329 [1], s2.5 table 1
+
+NOTE: only the measurement bands are different according to the occupied bandwidth.
+
+#### 9.2.1.2 Spurious emissions (Category B)
+
+The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied.
+
+##### 9.2.1.2.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.5: LCR TDD repeater Mandatory spurious emissions limits, Category B**
+
+| Band                         | Maximum Level | Measurement Bandwidth | Notes  |
+|------------------------------|---------------|-----------------------|--------|
+| 9kHz - 150kHz                | -36 dBm       | 1 kHz                 | Note 1 |
+| 150kHz - 30MHz               | -36 dBm       | 10 kHz                | Note 1 |
+| 30MHz - 1GHz                 | -36 dBm       | 100 kHz               | Note 1 |
+| 1GHz<br>↔<br>Fl -10 MHz      | -30 dBm       | 1 MHz                 | Note 1 |
+| Fl -10MHz<br>↔<br>Fu +10 MHz | -15 dBm       | 1 MHz                 | Note 2 |
+| Fu +10 MHz<br>↔<br>12,5 GHz  | -30 dBm       | 1 MHz                 | Note 3 |
+
+NOTE 1: Bandwidth as in ITU SM.329 [1], s4.1  
+NOTE 2: Limit based on ITU-R SM.329 [1], s4.3 and Annex 7  
+NOTE 3: Bandwidth as in ITU-R SM.329 [1], s4.3 and Annex 7. Upper frequency as in ITU-R SM.329 [1], s2.5 table 1
+
+Fl: Lower frequency of the band in which TDD operates
+
+Fu: Upper frequency of the band in which TDD operates
+
+### 9.2.2 Co-existence with GSM 900
+
+#### 9.2.2.1 Operation in the same geographic area
+
+This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS receivers in geographic areas in which both GSM 900 and UTRA are deployed.
+
+##### 9.2.2.1.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.6: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of GSM 900 MS and GSM 900 BTS receiver**
+
+| Band          | Maximum Level | Measurement Bandwidth | Note |
+|---------------|---------------|-----------------------|------|
+| 876 - 915 MHz | -61 dBm       | 100 kHz               |      |
+| 921 - 960MHz  | -57 dBm       | 100 kHz               |      |
+
+#### 9.2.2.2 Co-located base stations
+
+This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located.
+
+##### 9.2.2.2.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.7: LCR TDD repeater Spurious emissions limits for protection of the GSM 900 BTS receiver**
+
+| Band          | Maximum Level | Measurement Bandwidth | Note |
+|---------------|---------------|-----------------------|------|
+| 876 - 915 MHz | -98 dBm       | 100 kHz               |      |
+
+### 9.2.3 Co-existence with DCS 1800
+
+#### 9.2.3.1 Operation in the same geographic area
+
+This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS receivers in geographic areas in which both DCS 1800 and UTRA are deployed.
+
+##### 9.2.3.1.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.8: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1785 MHz | -61 dBm       | 100 kHz               |      |
+| 1805 - 1880MHz  | -47 dBm       | 100 kHz               |      |
+
+**Table 9.8a: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver operating in 1710-1755 MHz/1805-1850 MHz**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1755 MHz | -61 dBm       | 100 kHz               |      |
+| 1805 - 1850MHz  | -47 dBm       | 100 kHz               |      |
+
+#### 9.2.3.2 Co-located base stations
+
+This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located.
+
+##### 9.2.3.2.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.9: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when co-located with DCS 1800 BTS**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1785 MHz | -98 dBm       | 100 kHz               |      |
+
+**Table 9.10: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when co-located with DCS1800 BTS**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1755 MHz | -98 dBm       | 100 kHz               |      |
+
+### 9.2.4 Co-existence with UTRA-FDD
+
+#### 9.2.4.1 Operation in the same geographic area
+
+This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD operating in bands specified in Table 9.11 are deployed.
+
+##### 9.2.4.1.1 Minimum Requirement
+
+For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.11. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz.
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.11: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of UTRA-FDD**
+
+| Band                                                                                                                                                                                                                                                                                                  | Maximum Level | Measurement Bandwidth | Note |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------|
+| 1920 - 1980 MHz                                                                                                                                                                                                                                                                                       | -43 dBm (*)   | 3.84 MHz              |      |
+| 2110 - 2170 MHz                                                                                                                                                                                                                                                                                       | -52 dBm       | 1 MHz                 |      |
+| 2500 - 2570 MHz                                                                                                                                                                                                                                                                                       | -43 dBm(**)   | 3.84 MHz              |      |
+| 2620 - 2690 MHz                                                                                                                                                                                                                                                                                       | -52 dBm       | 1 MHz                 |      |
+| NOTE* For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. |               |                       |      |
+| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6 MHz below the lowest TDD carrier used, whichever is lower.                |               |                       |      |
+
+NOTE: The requirements in Table 9.11 are based on a coupling loss of 70 dB between LCR TDD repeater and FDD Wide Area base stations.
+
+#### 9.2.4.2 Co-located base stations
+
+This requirement may be applied for the protection of UTRA-FDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located.
+
+##### 9.2.4.2.1 Minimum Requirement
+
+For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.12. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz.
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.12: LCR TDD repeater Spurious emissions limits for BS co-located with UTRA-FDD**
+
+| Band                                                                                                                                                                                                                                                                                                   | Maximum Level | Measurement Bandwidth |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|
+| 1920 - 1980 MHz                                                                                                                                                                                                                                                                                        | -80 dBm (*)   | 3.84 MHz              |
+| 2110 - 2170 MHz                                                                                                                                                                                                                                                                                        | -52 dBm       | 1 MHz                 |
+| 2500 - 2570 MHz                                                                                                                                                                                                                                                                                        | - 80 dBm(**)  | 3.84 MHz              |
+| 2620 - 2690 MHz                                                                                                                                                                                                                                                                                        | -52 dBm       | 1 MHz                 |
+| NOTE * For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. |               |                       |
+| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6MHz below the lowest TDD carrier used, whichever is lower.                  |               |                       |
+
+NOTE: The requirements in Table 9.12 are based on a minimum coupling loss of 30 dB between LCR TDD repeater and UTRA-FDD base stations.
+
+### 9.2.5 Co-existence with unsynchronised TDD
+
+#### 9.2.5.1 Operation in the same geographic area
+
+This requirement shall apply in case the equipment is operated in the same geographic area with unsynchronised TDD BS.
+
+##### 9.2.5.1.1 Minimum Requirement
+
+In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission shall not exceed the limits specified in table 9.13, otherwise the limits in table 9.14 shall apply.
+
+**Table 9.13: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised 1,28 Mcps TDD**
+
+| Band            | Maximum Level | Measurement Bandwidth |
+|-----------------|---------------|-----------------------|
+| 1900 - 1920 MHz | -39 dBm       | 1,28 MHz              |
+| 2010 - 2025 MHz | -39 dBm       | 1,28 MHz              |
+| 2300 - 2400 MHz | -39 dBm       | 1,28 MHz              |
+| 2570 - 2620 MHz | -39 dBm       | 1,28 MHz              |
+| 1880 – 1920 MHz | -39 dBm       | 1,28 MHz              |
+
+**Table 9.14: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised TDD**
+
+| Band            | Maximum Level | Measurement Bandwidth |
+|-----------------|---------------|-----------------------|
+| 1900 - 1920 MHz | -39 dBm       | 3,84 MHz              |
+| 2010 - 2025 MHz | -39 dBm       | 3,84 MHz              |
+| 2570 - 2620 MHz | -39 dBm       | 3,84 MHz              |
+
+NOTE: The requirements in Table 9.13 and 9.14 for the LCR TDD repeater are based on a minimum coupling loss of 67 dB between LCR TDD repeater and unsynchronised TDD base stations.
+
+#### 9.2.5.2 Co-located base stations
+
+This requirement shall apply in case of co-location with unsynchronised TDD BS.
+
+##### 9.2.5.2.1 Minimum Requirement
+
+In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission in case of co-location shall not exceed the limits specified in table 9.15, otherwise the limits in table 9.16 shall apply.
+
+**Table 9.15: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised 1,28 Mcps TDD**
+
+| Band                                                                                                                                | Maximum Level | Measurement Bandwidth |
+|-------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|
+| 1900 - 1920 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 2010 - 2025 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 2300 - 2400 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 2570 - 2620 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 1880 - 1920 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| NOTE: The requirement applies for frequencies more than 10 MHz below or above the supported frequency range declared by the vendor. |               |                       |
+
+**Table 9.16: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised TDD**
+
+| Band            | Maximum Level | Measurement Bandwidth |
+|-----------------|---------------|-----------------------|
+| 1900 - 1920 MHz | -76 dBm       | 3,84 MHz              |
+| 2010 - 2025 MHz | -76 dBm       | 3,84 MHz              |
+| 2570 - 2620MHz  | -76 dBm       | 3,84 MHz              |
+
+NOTE: The requirements in Table 9.15 and 9.16 for the LCR TDD repeater are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations.
+
+# 10 Modulation accuracy
+
+## 10.1 Error Vector Magnitude
+
+The modulation accuracy is defined by the Error Vector Magnitude (EVM), which is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. This difference is called the error vector. The measured waveform is modified by first passing it through a matched root raised cosine filter with bandwidth 1.28MHz and roll-off  $\alpha=0.22$ . The waveform is then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as root of the ratio of the mean error vector power to the mean reference signal power expressed as a %.
+
+The measurement interval is one power control group (timeslot). The repeater shall operate with an ideal LCR TDD signal in the pass band of the repeater at a level, which produce the maximum rated output power per channel, as specified by the manufacturer.
+
+### 10.1.1 Minimum requirement
+
+The Error Vector Magnitude shall not be worse than 8 %.
+
+## 10.2 Peak code domain error
+
+The code domain error is computed by projecting the error vector power onto the code domain at a specific spreading factor. The error power for each code is defined as the ratio to the mean power of the reference waveform expressed in dB. And the Peak Code Domain Error is defined as the maximum value for Code Domain Error. The measurement interval is one timeslot.
+
+### 10.2.1 Minimum requirement
+
+The peak code domain error shall not exceed -30 dB at spreading factor 16.
+
+# 11 Input intermodulation
+
+The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band.
+
+## 11.1 General requirement
+
+The following requirement applies for interfering signals in the frequency bands defined in sub-clause 5.2, depending on the repeaters pass band.
+
+This requirement applies to the uplink and downlink of the repeater, at maximum gain.
+
+### 11.1.1 Minimum requirement
+
+For the parameters specified in table 11.1.1-1, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied.
+
+The frequency separation between the two interfering signals shall be adjusted so that the 3<sup>rd</sup> order intermodulation product is positioned in the centre of the pass band.
+
+Table 11.1.1-1 specifies the parameters for two interfering signals, where:
+
+- $f_i$  offset is the offset from the channel edge frequency of the first or last channel in the pass band of the closer carrier.
+
+**Table 11.1.1-1: Input intermodulation requirement**
+
+| <b>f<sub>1</sub> offset</b> | <b>Interfering Signal Levels</b> | <b>Type of signals</b> | <b>Measurement bandwidth</b> |
+|-----------------------------|----------------------------------|------------------------|------------------------------|
+| 1,0 MHz                     | -40 dBm                          | 2 CW carriers          | 1 MHz                        |
+
+# --- 12 Output intermodulation
+
+## 12.0 General
+
+The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna.
+
+The transmit intermodulation level is the power of the intermodulation products when a LCR TDD modulated interference signal is injected into the antenna connector at a mean power level of 30 dB lower than that of the mean power of the subject signal.
+
+## 12.1 Minimum requirement
+
+The frequency of the interference signal shall be  $\pm 1.6$  MHz,  $\pm 3.2$  MHz and  $\pm 4.8$  MHz offset from the subject signal. The Transmit intermodulation level shall not exceed the out of band or the spurious emission requirements of section 9.1 and 9.2.
+
+# --- 13 Adjacent Channel Rejection Ratio (ACRR)
+
+## 13.1 Definitions and applicability
+
+Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. The carrier in the pass band and in the adjacent channel shall be of the same type (reference carrier).
+
+The requirement shall apply to the uplink and downlink of Repeater, at maximum gain, where the donor link is maintained via antennas (over the air Repeater).
+
+## 13.2 Co-existence with UTRA
+
+This requirement shall be applied for the protection of UTRA signals in geographic areas in which LCR TDD Repeater and UTRA BS are deployed so that they serve adjacent channels. The reference carrier is a UTRA-FDD carrier.
+
+### 13.2.1. Minimum Requirements
+
+In normal conditions the ACRR shall be higher than the value specified in the Table 13.2.1-1.
+
+Table 13.2.1-1: Repeater ACRR
+
+| Co-existence with other systems | Repeater maximum output Pmax | Channel offset from the channel edge from the first or last 5MHz channel within the pass band. | ACRR limit |
+|---------------------------------|------------------------------|------------------------------------------------------------------------------------------------|------------|
+| UTRA                            | $P \geq 31$ dBm              | 2,5 MHz                                                                                        | 33dB       |
+|                                 | $P \geq 31$ dBm              | 5,0 MHz                                                                                        | 33dB       |
+|                                 | $P < 31$ dBm                 | 2,5 MHz                                                                                        | 20dB       |
+|                                 | $P < 31$ dBm                 | 5,0 MHz                                                                                        | 20dB       |
+
+Note: For co-existence with TDD, a narrow band requirement is for further study.
+
+# 14 Timing Accuracy
+
+Timing Accuracy is the repeater synchronization accuracy with NodeB, it includes the downlink ramp on/off time and uplink ramp on/off time.
+
+## 14.1 Minimum requirement
+
+The downlink gain versus time should meet the mask specified in figure 14.1. The beginning and end point of downlink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator.
+
+![Figure 14.1: Downlink gain ON/OFF template. The diagram shows a rectangular pulse representing the downlink gain over time. The vertical axis is labeled 'Rated Gain' at the top and 'Zero Gain' at the bottom. The horizontal axis has two '8 chips' intervals marked with double-headed arrows at the leading and trailing edges of the pulse. The main body of the pulse is labeled 'Downlink burst without GP'.](85ad73d1c8ff59cd647b95f084937bc0_img.jpg)
+
+Figure 14.1: Downlink gain ON/OFF template. The diagram shows a rectangular pulse representing the downlink gain over time. The vertical axis is labeled 'Rated Gain' at the top and 'Zero Gain' at the bottom. The horizontal axis has two '8 chips' intervals marked with double-headed arrows at the leading and trailing edges of the pulse. The main body of the pulse is labeled 'Downlink burst without GP'.
+
+Figure 14.1: Downlink gain ON/OFF template
+
+The uplink gain versus time should meet the mask specified in figure 14.2. The beginning and end point of uplink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator.
+
+![Uplink gain ON/OFF template diagram showing Rated Gain, Zero Gain, 8 chips transition periods, and Uplink burst without GP.](a289b64f80c6df506c0c55d553fc4496_img.jpg)
+
+The diagram illustrates the gain profile for an uplink burst. A horizontal line at the bottom represents 'Zero Gain'. A horizontal dotted line represents 'Rated Gain'. The gain transitions from Zero Gain to Rated Gain at the start of the burst, remains at Rated Gain throughout the 'Uplink burst without GP', and then transitions back to Zero Gain at the end. Two '8 chips' intervals are marked with double-headed arrows at the beginning and end of the burst, indicating the duration of the gain transition. Vertical lines mark the start and end of the 'Uplink burst without GP' and the start and end of the Rated Gain period.
+
+Uplink gain ON/OFF template diagram showing Rated Gain, Zero Gain, 8 chips transition periods, and Uplink burst without GP.
+
+Figure 14.2: Uplink gain ON/OFF template
+
+# --- Annex A (normative): Environmental requirements for the Repeater equipment
+
+The Repeater equipment shall fulfil all the requirements in the full range of environmental conditions for the relevant environmental class from the relevant IEC specifications listed below
+
+- 60 721-3-3 "Stationary use at weather protected locations" [6];
+- 60 721-3-4 "Stationary use at non weather protected locations" [7]
+
+Normally it should be sufficient for all tests to be conducted using normal test conditions except where otherwise stated. For guidance on the use of test conditions to be used in order to show compliance refer to TS 25.153.
+
+# Annex B (informative): Change history
+
+| Change history |         |           |    |     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |        |        |
+|----------------|---------|-----------|----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #   | TSG Doc.  | CR | Rev | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Old    | New    |
+| 2009-08        | RAN4#52 | R4-093324 |    |     | TS skeleton created from 3GPP TS template.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |        | 0.0.1  |
+| 2009-11        | RAN4#53 | R4-094876 |    |     | TS with the TP approved at RAN4#52 and RAN4#52bis<br>R4-092917 Text proposal for LCR TDD Repeater Specification:<br>Output Power<br>R4-092918 Text proposal for LCR TDD Repeater Specification:<br>Frequency Error<br>R4-092919 Text proposal for LCR TDD Repeater Specification:<br>EVM<br>R4-092920 Text proposal for LCR TDD Repeater Specification:<br>PCDE<br>R4-092922 Text proposal for LCR TDD Repeater Specification:<br>Output Intermodulation<br>R4-093323 Text Proposal for LCR TDD Repeater Specification:<br>Frequency bands and channel arrangements<br>R4-093350 Text proposal for LCR TDD Repeater Specification:<br>Input Intermodulation<br>R4-093351 Text proposal for LCR TDD Repeater Specification:<br>Out of Band Gain<br>R4-093353 Text proposal for LCR TDD Repeater Specification:<br>ACRR<br>R4-093363 Text proposal for LCR TDD Repeater Specification:<br>Timing Accuracy<br>R4-093372 Text proposal for LCR TDD Repeater Specification:<br>Unwanted Emissions<br>R4-093746 Text proposal for 25.116: Clause 1 to Clause 3<br>R4-094015 Text proposal for 25.116: Clause 4 General | 0.0.1  | 1.0.0  |
+| 2009-11        | RAN#46  | RP-091136 |    |     | Presentation to TSG for information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |        |        |
+| 2010-03        | RAN#47  | RP-100112 |    |     | Version update, presentation to TSG for approval,                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | 1.0.0  | 2.0.0  |
+| 2010-03        | RAN#47  | RP-100112 |    |     | Approved by TSG RAN                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 2.0.0  | 10.0.0 |
+| 2012-09        | SP-57   | -         | -  | -   | Update to Rel-11 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 10.0.0 | 11.0.0 |
+| 2014-09        | SP-65   | -         | -  | -   | Update to Rel-12 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 11.0.0 | 12.0.0 |
+| 2016-01        | SP-70   | -         | -  | -   | Update to Rel-13 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 12.0.0 | 13.0.0 |
+| 2017-03        | -       | -         | -  | -   | Update to Rel-14 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 13.0.0 | 14.0.0 |
+
+| Change history |         |      |    |     |     |                                |             |
+|----------------|---------|------|----|-----|-----|--------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version |
+| 2018-06        | SA#80   | -    | -  | -   | -   | Update to Rel-15 version (MCC) | 15.0.0      |
+| 2020-06        | SA#88   | -    | -  | -   | -   | Update to Rel-16 version (MCC) | 16.0.0      |
+| 2022-03        | SA#95   |      |    |     |     | Update to Rel-17 version (MCC) | 17.0.0      |
+| 2024-03        | RAN#103 |      |    |     |     | Update to Rel-18 version (MCC) | 18.0.0      |

marked/Rel-18/25_series/25171/raw.md

@@ -0,0 +1,1012 @@
+
+
+# 3GPP TS 25.171 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of Assisted Global Positioning System (A-GPS); Frequency Division Duplex (FDD) (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+---
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                       |           |
+|-----------------------------------------------------------------------|-----------|
+| Foreword .....                                                        | 5         |
+| 1 Scope.....                                                          | 6         |
+| 2 References.....                                                     | 6         |
+| 3 Definitions, symbols, abbreviations and test tolerances .....       | 7         |
+| 3.1 Definitions.....                                                  | 7         |
+| 3.2 Symbols.....                                                      | 7         |
+| 3.3 Abbreviations .....                                               | 7         |
+| 3.4 Test tolerances.....                                              | 8         |
+| 4 General.....                                                        | 8         |
+| 4.1 Introduction .....                                                | 8         |
+| 4.2 Measurement parameters.....                                       | 8         |
+| 4.2.1 UE based A-GPS measurement parameters .....                     | 8         |
+| 4.2.2 UE assisted A-GPS measurement parameters.....                   | 8         |
+| 4.3 Response time .....                                               | 8         |
+| 4.4 Time assistance .....                                             | 8         |
+| 4.4.1 Use of fine time assistance .....                               | 9         |
+| 4.5 RRC states.....                                                   | 9         |
+| 4.6 2D position error .....                                           | 9         |
+| 5 A-GPS minimum performance requirements .....                        | 9         |
+| 5.1 Sensitivity.....                                                  | 9         |
+| 5.1.1 Coarse time assistance.....                                     | 9         |
+| 5.1.1.1 Minimum Requirements (Coarse time assistance) .....           | 10        |
+| 5.1.2 Fine time assistance.....                                       | 10        |
+| 5.1.2.1 Minimum Requirements (Fine time assistance) .....             | 10        |
+| 5.2 Nominal Accuracy.....                                             | 10        |
+| 5.2.1 Minimum requirements (nominal accuracy) .....                   | 11        |
+| 5.3 Dynamic Range.....                                                | 11        |
+| 5.3.1 Minimum requirements (dynamic range).....                       | 11        |
+| 5.4 Multi-Path scenario .....                                         | 11        |
+| 5.4.1 Minimum Requirements (multi-path scenario) .....                | 12        |
+| 5.5 Moving scenario and periodic update .....                         | 12        |
+| 5.5.1 Minimum Requirements (moving scenario and periodic update)..... | 13        |
+| <b>Annex A (normative): Test cases.....</b>                           | <b>14</b> |
+| A.1 Conformance tests.....                                            | 14        |
+| A.2 Requirement classification for statistical testing .....          | 14        |
+| <b>Annex B (normative): Test conditions.....</b>                      | <b>15</b> |
+| B.1 General.....                                                      | 15        |
+| B.1.1 Parameter values .....                                          | 15        |
+| B.1.2 Time assistance .....                                           | 15        |
+| B.1.3 GPS Reference Time.....                                         | 15        |
+| B.1.4 Reference and UE locations.....                                 | 16        |
+| B.1.5 Satellite constellation and assistance data.....                | 16        |
+| B.1.6 Atmospheric delays.....                                         | 16        |
+| B.1.7 UTRA Frequency and frequency error.....                         | 16        |
+| B.1.8 Information elements.....                                       | 16        |
+| B.1.9 GPS signals .....                                               | 16        |
+| B.1.10 RESET UE POSITIONING STORED INFORMATION Message .....          | 16        |
+| <b>Annex C (normative): Propagation conditions .....</b>              | <b>18</b> |
+| C.1 General.....                                                      | 18        |
+
+|                               |                                                                                                |           |
+|-------------------------------|------------------------------------------------------------------------------------------------|-----------|
+| C.2                           | Propagation Conditions .....                                                                   | 18        |
+| C.2.1                         | Static propagation conditions .....                                                            | 18        |
+| C.2.2                         | Multi-path Case G1 .....                                                                       | 18        |
+| <b>Annex D (normative):</b>   | <b>Measurement sequence chart.....</b>                                                         | <b>19</b> |
+| D.1                           | General.....                                                                                   | 19        |
+| D.2                           | UE Based A-GPS Measurement Sequence Chart .....                                                | 19        |
+| D.2.1                         | UE Based GPS Message Sequence Normal.....                                                      | 19        |
+| D.2.2                         | UE Based GPS Message Sequence Normal for moving scenario and periodic update test case.....    | 21        |
+| D.2.3                         | UE Based GPS Message Sequence Failure.....                                                     | 22        |
+| D.3                           | UE Assisted A-GPS Measurement Sequence Chart .....                                             | 22        |
+| D.3.1                         | UE Assisted A-GPS Measurement Sequence Chart Normal .....                                      | 22        |
+| D.3.2                         | UE assisted A-GPS Measurement Sequence for moving scenario and periodic update test case ..... | 24        |
+| <b>Annex E (normative):</b>   | <b>Assistance data required for testing .....</b>                                              | <b>25</b> |
+| E.1                           | Introduction.....                                                                              | 25        |
+| E.2                           | Information elements required for UE-based.....                                                | 25        |
+| E.3                           | Information elements available for UE-assisted .....                                           | 26        |
+| <b>Annex F (normative):</b>   | <b>Converting UE-assisted measurement reports into position estimates ....</b>                 | <b>29</b> |
+| F.1                           | Introduction.....                                                                              | 29        |
+| F.2                           | UE measurement reports .....                                                                   | 29        |
+| F.3                           | WLS position solution .....                                                                    | 30        |
+| <b>Annex G (informative):</b> | <b>Change History .....</b>                                                                    | <b>32</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document establishes the minimum performance requirements for A-GPS for FDD mode of UTRA for the User Equipment (UE).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
+- [3] 3GPP TS 34.171: "Terminal Conformance Specification, Assisted Global Positioning System (A-GPS) (FDD)".
+- [4] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [5] 3GPP TS 25.302: "Services provided by the physical layer".
+- [6] 3GPP TS 25.215: "Physical layer; Measurements (FDD)".
+- [7] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [8] Navstar GPS Space Segment/Navigation User Interfaces, ICD-GPS 200, Rev. C.
+- [9] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996.
+- [10] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119.
+- [11] 3GPP TS 34.109: "Special conformance testing functions"
+
+# 3 Definitions, symbols, abbreviations and test tolerances
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.101 [1], 3GPP TS 25.104 [2] and the following apply:
+
+**Horizontal Dilution Of Precision (HDOP):** measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna
+
+**Node B:** logical node responsible for radio transmission / reception in one or more cells to/from the User Equipment. Terminates the Iub interface towards the RNC
+
+**L1:** L band GPS transmission frequency of 1575.42 MHz
+
+## 3.2 Symbols
+
+Void
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                           |
+|-------|-----------------------------------------------------------|
+| A-GPS | Assisted - Global Positioning System                      |
+| AWGN  | Additive White Gaussian Noise                             |
+| C/A   | Coarse/Acquisition                                        |
+| CPICH | Common Pilot CHannel                                      |
+| DCH   | Dedicated CHannel                                         |
+| DPCH  | Dedicated Physical CHannel                                |
+| DUT   | Device Under Test                                         |
+| ECEF  | Earth Centred, Earth Fixed                                |
+| FACH  | Fast Access CHannel                                       |
+| FDD   | Frequency Division Duplex                                 |
+| GPS   | Global Positioning System                                 |
+| GSS   | GPS System Simulator                                      |
+| HDOP  | Horizontal Dilution Of Precision                          |
+| LOS   | Line Of Sight                                             |
+| PICH  | Paging Indicator CHannel                                  |
+| RRC   | Radio Resource Control                                    |
+| RSCP  | Received Signal Code Power                                |
+| SFN   | System Frame Number                                       |
+| SMLC  | Standalone Mobile Location Center                         |
+| SRNC  | Serving Radio Network Controller                          |
+| SS    | FDD System simulator                                      |
+| TDD   | Time Division Duplex                                      |
+| TLM   | TeLeMetry word. It contains an 8-bits preamble (10001011) |
+| TOW   | Time Of Week                                              |
+| TTFF  | Time To First Fix                                         |
+| UE    | User Equipment                                            |
+| UTRA  | Universal Terrestrial Radio Access                        |
+| UTRAN | Universal Terrestrial Radio Access Network                |
+| WLS   | Weighted Least Square                                     |
+
+## 3.4 Test tolerances
+
+The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 34.171 [3] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle.
+
+Shared Risk is defined in ETR 273-1-2 [7], subclause 6.5.
+
+# --- 4 General
+
+## 4.1 Introduction
+
+The present document defines the minimum performance requirements for both UE based and UE assisted FDD A-GPS terminals.
+
+## 4.2 Measurement parameters
+
+### 4.2.1 UE based A-GPS measurement parameters
+
+In case of UE-based A-GPS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter in case of UE-based A-GPS is the horizontal position estimate reported by the UE and expressed in latitude/longitude.
+
+### 4.2.2 UE assisted A-GPS measurement parameters
+
+In case of UE-assisted A-GPS, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE. The measurement parameters in case of UE-assisted A-GPS are the UE GPS Code Phase measurements, as specified in 3GPP TS 25.302 [5] and 3GPP TS 25.215 [6]. The UE GPS Code Phase measurements are converted into a horizontal position estimate using the procedure detailed in Annex F.
+
+## 4.3 Response time
+
+Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re-use any information on GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [11] clause 5.4 for the purpose of deleting this information and is detailed in subclause B.1.10.
+
+## 4.4 Time assistance
+
+Time assistance is the provision of GPS time to the UE from the network via RRC messages. Currently two different GPS time assistance methods can be provided by the network.
+
+- Coarse time assistance is always provided by the network and provides current GPS time to the UE. The time provided is within  $\pm 2$  seconds of GPS system time. This allows the GPS time to be known within one GPS navigation data sub-frame. It is signalled to the UE by means of the GPS Week and GPS TOW msec fields in the Reference Time assistance data IE.
+- Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GPS system time and the current UTRAN time. The accuracy of this relationship is  $\pm 10 \mu\text{s}$  of the actual relationship. This addresses the case when the network can provide an improved GPS time accuracy. It is
+
+signalled to the UE by means of the SFN and UTRAN GPS timing of cell frames fields in the Reference Time assistance data IE.
+
+The time of applicability of time assistance is the beginning of the System Frame of the message containing the GPS Reference time.
+
+### 4.4.1 Use of fine time assistance
+
+The use of fine time assistance to improve the GPS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in subclause 5.1.2.
+
+## 4.5 RRC states
+
+The minimum A-GPS performance requirements are specified in clause 5 for different RRC states that include Cell\_DCH and Cell\_FACH. Cell\_PCH and URA\_PCH states are for further study. The test and verification procedures are separately defined in annex B.
+
+## 4.6 2D position error
+
+The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual position of the UE in the test case considered.
+
+# --- 5 A-GPS minimum performance requirements
+
+The A-GPS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network.
+
+In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in annexes D and E.
+
+The requirements in CELL\_PCH and URA\_PCH states are for further study.
+
+## 5.1 Sensitivity
+
+A sensitivity requirement is essential for verifying the performance of A-GPS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance.
+
+### 5.1.1 Coarse time assistance
+
+In this test case 8 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 1: Test parameters**
+
+| Parameters                             | Unit    | Value      |
+|----------------------------------------|---------|------------|
+| Number of generated satellites         | -       | 8          |
+| HDOP Range                             | -       | 1.1 to 1.6 |
+| Propagation conditions                 | -       | AWGN       |
+| GPS Coarse time assistance error range | seconds | ±2         |
+| GPS Signal for one satellites          | dBm     | -142       |
+| GPS Signal for remaining satellites    | dBm     | -147       |
+
+#### 5.1.1.1 Minimum Requirements (Coarse time assistance)
+
+The position estimates shall meet the accuracy and response time specified in table 2.
+
+**Table 2: Minimum requirements (coarse time assistance)**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+### 5.1.2 Fine time assistance
+
+This requirement is only valid for fine time assistance capable UEs. In this requirement 8 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 3: Test parameters for fine time assistance capable terminals**
+
+| Parameters                             | Unit          | Value      |
+|----------------------------------------|---------------|------------|
+| Number of generated satellites         | -             | 8          |
+| HDOP Range                             | -             | 1.1 to 1.6 |
+| Propagation conditions                 | -             | AWGN       |
+| GPS Coarse time assistance error range | seconds       | $\pm 2$    |
+| GPS Fine time assistance error range   | $\mu\text{s}$ | $\pm 10$   |
+| GPS Signal for all satellites          | dBm           | -147       |
+
+#### 5.1.2.1 Minimum Requirements (Fine time assistance)
+
+The position estimates shall meet the accuracy and response time requirements in table 4.
+
+**Table 4: Minimum requirements for fine time assistance capable terminals**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+## 5.2 Nominal Accuracy
+
+Nominal accuracy requirement verifies the accuracy of A-GPS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate.
+
+In this requirement 8 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5: Test parameters**
+
+| Parameters                             | Unit    | Value      |
+|----------------------------------------|---------|------------|
+| Number of generated satellites         | -       | 8          |
+| HDOP Range                             | -       | 1.1 to 1.6 |
+| Propagation conditions                 | -       | AWGN       |
+| GPS Coarse time assistance error range | seconds | $\pm 2$    |
+| GPS Signal for all satellites          | dBm     | -130       |
+
+### 5.2.1 Minimum requirements (nominal accuracy)
+
+The position estimates shall meet the accuracy and response time requirements in table 6.
+
+**Table 6: Minimum requirements**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 30 m               | 20 s              |
+
+## 5.3 Dynamic Range
+
+The aim of a dynamic range requirement is to ensure that a GPS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 7: Test parameters**
+
+| Parameters                               | Unit    | Value      |
+|------------------------------------------|---------|------------|
+| Number of generated satellites           | -       | 6          |
+| HDOP Range                               | -       | 1.4 to 2.1 |
+| GPS Coarse time assistance error range   | seconds | ±2         |
+| Propagation conditions                   | -       | AWGN       |
+| GPS Signal for 1 <sup>st</sup> satellite | dBm     | -129       |
+| GPS Signal for 2 <sup>nd</sup> satellite | dBm     | -135       |
+| GPS Signal for 3 <sup>rd</sup> satellite | dBm     | -141       |
+| GPS Signal for 4 <sup>th</sup> satellite | dBm     | -147       |
+| GPS Signal for 5 <sup>th</sup> satellite | dBm     | -147       |
+| GPS Signal for 6 <sup>th</sup> satellite | dBm     | -147       |
+
+### 5.3.1 Minimum requirements (dynamic range)
+
+The position estimates shall meet the accuracy and response time requirements in table 8.
+
+**Table 8: Minimum requirements**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+## 5.4 Multi-Path scenario
+
+The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate.
+
+In this requirement 5 satellites are generated for the terminal. Two of the satellites have one tap channel representing Line-Of-Sight (LOS) signal. The three other satellites have two-tap channel, where the first tap represents LOS signal and the second reflected and attenuated signal as specified in Case G1 in subclause C.2.2.
+
+**Table 9: Test parameters**
+
+| Parameters                                                                                                               | Unit    | Value                                                 |
+|--------------------------------------------------------------------------------------------------------------------------|---------|-------------------------------------------------------|
+| Number of generated satellites (Satellites 1, 2 unaffected by multi-path)<br>(Satellites 3, 4, 5 affected by multi-path) | -       | 5                                                     |
+| GPS Coarse time assistance error range                                                                                   | seconds | ±2                                                    |
+| HDOP Range                                                                                                               | -       | 1.8 to 2.5                                            |
+| Satellite 1, 2 signal                                                                                                    | dBm     | -130                                                  |
+| Satellite 3, 4, 5 signal                                                                                                 | dBm     | LOS signal of -130 dBm, multi-path signal of -136 dBm |
+
+### 5.4.1 Minimum Requirements (multi-path scenario)
+
+The position estimates shall meet the accuracy and response time requirements in table 10.
+
+**Table 10: Minimum requirements**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+## 5.5 Moving scenario and periodic update
+
+The purpose of the test case is to verify the receiver's capability to produce GPS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for a certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GPS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test.
+
+In this requirement 5 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds.
+
+The UE moves on a rectangular trajectory of 940 m by 1 440 m with rounded corner defined in figure 1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle.
+
+**Table 11: Trajectory Parameters**
+
+| Parameter                        | Distance (m) | Speed (km/h)            |
+|----------------------------------|--------------|-------------------------|
+| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20           | 25                      |
+| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250          | 25 to 100 and 100 to 25 |
+| $l_{13}$                         | 400          | 100                     |
+| $l_{23}$                         | 900          | 100                     |
+
+![Figure 1: Rectangular trajectory of the moving scenario and periodic update test case. The diagram shows a rectangle with a width of 1 440 m and a height of 940 m. The bottom-left corner has a radius of r = 20 m. The vertical axis is labeled with I_11, I_12, I_13, I_14, and I_15. The horizontal axis is labeled with I_21, I_22, I_23, I_24, and I_25.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg)
+
+Figure 1: Rectangular trajectory of the moving scenario and periodic update test case. The diagram shows a rectangle with a width of 1 440 m and a height of 940 m. The bottom-left corner has a radius of r = 20 m. The vertical axis is labeled with I\_11, I\_12, I\_13, I\_14, and I\_15. The horizontal axis is labeled with I\_21, I\_22, I\_23, I\_24, and I\_25.
+
+Figure 1: Rectangular trajectory of the moving scenario and periodic update test case
+
+Table 12: Test Parameters
+
+| Parameters                     | Unit | Value      |
+|--------------------------------|------|------------|
+| Number of generated satellites | -    | 5          |
+| HDOP Range                     | -    | 1.8 to 2.5 |
+| Propagation condition          | -    | AWGN       |
+| GPS signal for all satellites  | dBm  | -130       |
+
+### 5.5.1 Minimum Requirements (moving scenario and periodic update)
+
+The position estimates shall meet the accuracy requirement of table 13 with the periodical reporting interval defined in table 13 after the first reported position estimates.
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 13.
+
+Table 13: Minimum requirements
+
+| Success Rate | 2-D position error | Periodical reporting interval |
+|--------------|--------------------|-------------------------------|
+| 95 %         | 100 m              | 2 s                           |
+
+# --- Annex A (normative): Test cases
+
+## A.1 Conformance tests
+
+The conformance tests are specified in 3GPP TS 34.171 [3]. Statistical interpretation of the requirements is described in clause A.2.
+
+## --- A.2 Requirement classification for statistical testing
+
+Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested.
+
+Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for.
+
+When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in 3GPP TS 34.171 [3].
+
+# Annex B (normative): Test conditions
+
+## B.1 General
+
+This annex specifies the additional parameters that are needed for the test cases specified in clause 5 and applies to all tests unless otherwise stated.
+
+### B.1.1 Parameter values
+
+Additionally, amongst all the listed parameters (see annex E), the following values for some important parameters are to be used in the measurement control message.
+
+**Table B.1: Parameter values**
+
+| Information element                                 | Value - TTFF tests (except nominal accuracy test) | Value - TTFF tests (nominal accuracy test) | Value - Periodic tests |
+|-----------------------------------------------------|---------------------------------------------------|--------------------------------------------|------------------------|
+| Measurement Reporting Mode                          | Periodical reporting                              | Periodical reporting                       | Periodical reporting   |
+| Amount of reporting                                 | 1                                                 | 1                                          | Infinite (see note)    |
+| Reporting interval                                  | 20 000 ms                                         | 20 000 ms                                  | 2 000 ms               |
+| Horizontal accuracy                                 | 50 m                                              | 15 m                                       | 50 m                   |
+| Vertical accuracy                                   | 100 m                                             | 100 m                                      | 100 m                  |
+| NOTE: Infinite means during the complete test time. |                                                   |                                            |                        |
+
+In the Sensitivity test case with Fine Time Assistance, the following parameter values are used.
+
+**Table B.2: Parameters for Fine Time Assistance test**
+
+| Information element   | Value      |
+|-----------------------|------------|
+| TUTRAN-GPS drift rate | 0          |
+| SFN-TOW Uncertainty   | lessThan10 |
+
+### B.1.2 Time assistance
+
+For every Test Instance in each TTFF test case, the IE GPS TOW msec shall have a random offset, relative to GPS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+In addition, for every Fine Time Assistance Test Instance the IE UTRAN GPS timing of cell frames shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+For the Moving Scenario and Periodic Update Test Case the IE GPS TOW msec shall be set to the nominal value.
+
+### B.1.3 GPS Reference Time
+
+For every Test Instance in each TTFF test case, the GPS reference time shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix.
+
+### B.1.4 Reference and UE locations
+
+There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km. The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %.
+
+For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions.
+
+### B.1.5 Satellite constellation and assistance data
+
+The satellite constellation shall consist of 24 satellites. Almanac assistance data shall be available for all these 24 satellites. At least 9 of the satellites shall be visible to the UE (that is above 5 degrees elevation with respect to the UE). Other assistance data shall be available for 9 of these visible satellites. In each test, signals are generated for only a sub-set of these satellites for which other assistance data is available. The number of satellites in this sub-set is specified in the test. The satellites in this sub-set shall all be above 15 degrees elevation with respect to the UE. The HDOP for the test shall be calculated using this sub-set of satellites. The selection of satellites for this sub-set shall be random and consistent with achieving the required HDOP for the test.
+
+### B.1.6 Atmospheric delays
+
+Typical Ionospheric and Tropospheric delays shall be simulated and the corresponding values inserted into the Ionospheric Model IEs.
+
+### B.1.7 UTRA Frequency and frequency error
+
+In all test cases the UTRA frequency used shall be the mid range for the UTRA operating band. The UTRA frequency with respect to the GPS carrier frequency shall be offset by +0.025 PPM.
+
+### B.1.8 Information elements
+
+The information elements that are available to the UE in all the test cases are listed in annex E.
+
+### B.1.9 GPS signals
+
+The GPS signal is defined at the A-GPS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
+
+### B.1.10 RESET UE POSITIONING STORED INFORMATION Message
+
+In order to ensure each Test Instance in each TTFF test is performed under Time to First Fix (TTFF) conditions, a dedicated test signal (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 34.109 [11] clause 5.4 shall be used.
+
+When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' signal, with the IE *UE POSITIONING TECHNOLOGY* set to *AGPS* it shall:
+
+- discard any internally stored GPS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler);
+- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition;
+
+- calculate the position or perform GPS measurements using the 'new' reference time or reference location or other information.
+
+# Annex C (normative): Propagation conditions
+
+## C.1 General
+
+Void
+
+## C.2 Propagation Conditions
+
+### C.2.1 Static propagation conditions
+
+The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model.
+
+### C.2.2 Multi-path Case G1
+
+Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GPS L1 signal are defined in table C.1.
+
+**Table C.1: Case G1**
+
+| Initial relative Delay [GPS chip]                      | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean Power [dB] |
+|--------------------------------------------------------|---------------------------------------|------------------------------------|--------------------------|
+| 0                                                      | $F_d$                                 | $F_d / N$                          | 0                        |
+| 0.5                                                    | $F_d - 0.1$                           | $(F_d - 0.1) / N$                  | -6                       |
+| NOTE: Discrete Doppler frequency is used for each tap. |                                       |                                    |                          |
+
+$N = f_{\text{GPSL1}} / f_{\text{chip}}$ , where  $f_{\text{GPSL1}}$  is the nominal carrier frequency of the GPS L1 signal (1575.42 MHz) and  $f_{\text{chip}}$  is the GPS L1 C/A code chip rate (1.023 Mchips/s).
+
+The initial carrier phase difference between taps shall be randomly selected between  $[0, 2\pi]$ . The initial value shall have uniform random distribution.
+
+# --- Annex D (normative): Measurement sequence chart
+
+## D.1 General
+
+The measurement Sequence Charts that are required in all the proposed test cases, are defined in this clause.
+
+## --- D.2 UE Based A-GPS Measurement Sequence Chart
+
+### D.2.1 UE Based GPS Message Sequence Normal
+
+![Sequence diagram showing UE-Based GPS Message Sequence Normal between SRNC and UE.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (1))
+    SRNC->>UE: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (1), Iono Model)
+    SRNC->>UE: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (1), ReferencePosition (1))
+    UE-->>SRNC: RRC Measurement Report (Position Estimate), 1st test instance
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (2))
+    SRNC->>UE: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (2), Iono Model)
+    SRNC->>UE: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (2), ReferencePosition (2))
+    UE-->>SRNC: RRC Measurement Report (Position Estimate), 2nd test instance
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    Note right of SRNC: .....
+    UE-->>SRNC: RRC Measurement Report (Position Estimate), nth test instance
+```
+
+The diagram illustrates the message sequence between an SRNC and a UE for UE-Based GPS. The sequence starts with the SRNC sending a 'RESET UE POSITIONING STORED INFORMATION' message to the UE. This is followed by a series of RRC measurement control messages from the SRNC to the UE: 'RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (1))', 'RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (1), Iono Model)', and 'RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (1), ReferencePosition (1))'. The UE responds with 'RRC Measurement Report (Position Estimate), 1<sup>st</sup> test instance'. The SRNC then sends another 'RESET UE POSITIONING STORED INFORMATION' message, followed by 'RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (2))', 'RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (2), Iono Model)', and 'RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (2), ReferencePosition (2))'. The UE responds with 'RRC Measurement Report (Position Estimate), 2<sup>nd</sup> test instance'. The SRNC sends a third 'RESET UE POSITIONING STORED INFORMATION' message, followed by a dotted line indicating further instances, and finally the UE responds with 'RRC Measurement Report (Position Estimate), n<sup>th</sup> test instance'.
+
+Sequence diagram showing UE-Based GPS Message Sequence Normal between SRNC and UE.
+
+**Figure D.1: UE-Based GPS Message Sequence Normal**
+
+### D.2.2 UE Based GPS Message Sequence Normal for moving scenario and periodic update test case
+
+![Sequence diagram showing message exchange between SRNC and UE for GPS positioning.](a3472689858b068ef469213682965325_img.jpg)
+
+The diagram illustrates a sequence of messages between an SRNC (Source RNC) and a UE (User Equipment). The sequence starts with the SRNC sending a 'RESET UE POSITIONING STORED INFORMATION' message to the UE. This is followed by three 'RRc measurement control' messages from the SRNC to the UE: 'Setup, No Reporting, Nav model Satellites 1, 2, 3, 4, 5'; 'Modify, No Reporting, Nav model Satellites 6,7,8,9, Iono Model'; and 'Modify, Periodical Reporting Criterion, GPS Ref time, ReferencePosition'. The UE then responds with a series of 'RRc Measurement Report (Position Estimate)' messages, indicated by arrows pointing from the UE to the SRNC. A vertical dotted line between the second and third reports indicates that multiple such reports are sent over time.
+
+Sequence diagram showing message exchange between SRNC and UE for GPS positioning.
+
+Figure D.2: UE-Based GPS Message Sequence Normal for moving scenario test case
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire a position estimate.
+
+### D.2.3 UE Based GPS Message Sequence Failure
+
+![Sequence diagram showing UE Based GPS Message Sequence Failure between SRNC and UE.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note right of SRNC: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5)
+    SRNC->>UE: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5)
+    Note right of SRNC: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9, Iono Model)
+    SRNC->>UE: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9, Iono Model)
+    Note right of SRNC: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time, ReferencePosition)
+    SRNC->>UE: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time, ReferencePosition)
+    Note left of UE: RRC Measurement Report (Position Error of type "There were not enough satellites to be received ")
+    UE->>SRNC: RRC Measurement Report (Position Error of type "There were not enough satellites to be received ")
+```
+
+The diagram illustrates a sequence of messages between an SRNC (Source RNC) and a UE (User Equipment) for a UE-based GPS measurement sequence failure. The sequence starts with the SRNC sending three RRC measurement control messages to the UE. The first message is a 'Setup' with 'No Reporting' and a 'Nav model Satellites 1,2,3,4,5'. The second message is a 'Modify' with 'No Reporting' and a 'Nav model Satellites 6,7,8,9, Iono Model'. The third message is a 'Modify' with 'Periodical Reporting Criterion, GPS Ref time, ReferencePosition'. After these three messages, the UE sends an RRC Measurement Report back to the SRNC. The report indicates a 'Position Error of type "There were not enough satellites to be received "'.
+
+Sequence diagram showing UE Based GPS Message Sequence Failure between SRNC and UE.
+
+Figure D.3: UE-Based GPS Message Sequence Failure
+
+## D.3 UE Assisted A-GPS Measurement Sequence Chart
+
+### D.3.1 UE Assisted A-GPS Measurement Sequence Chart Normal
+
+The assistance data requested by the UE and provided by the SRNC in this sequence of messages shall be selected from among those information elements described as available in clause E.3.
+
+![Sequence diagram showing UE-Assisted GPS Message Sequence between SRNC and UE.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note over SRNC, UE: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)
+    UE-->>SRNC: RRC Measurement Report (Additional Assistance Data Request)
+    SRNC->>UE: RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)
+    SRNC->>UE: RRC Measurement Control (Modify, Periodical Reporting Criteria)
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #1)
+    Note over SRNC, UE: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)
+    UE-->>SRNC: RRC Measurement Report (Additional Assistance Data Request)
+    SRNC->>UE: RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)
+    SRNC->>UE: RRC Measurement Control (Modify, Periodical Reporting Criteria)
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #2)
+    Note over SRNC, UE: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: ...
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #n)
+```
+
+The diagram illustrates the message sequence between an SRNC (Radio Network Controller) and a UE (User Equipment) for UE-assisted GPS. The sequence starts with a 'RESET UE POSITIONING STORED INFORMATION' message from SRNC to UE. This is followed by an 'RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)' message from SRNC to UE. The UE responds with an 'RRC Measurement Report (Additional Assistance Data Request)'. The SRNC then sends an 'RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)' message. The UE replies with an 'RRC Measurement Control (Modify, Periodical Reporting Criteria)' message. The UE then sends an 'RRC Measurement Report (GPS Measured Results #1)'. The SRNC sends another 'RESET UE POSITIONING STORED INFORMATION' message. This is followed by an 'RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)' message from SRNC to UE. The UE responds with an 'RRC Measurement Report (Additional Assistance Data Request)'. The SRNC then sends an 'RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)' message. The UE replies with an 'RRC Measurement Control (Modify, Periodical Reporting Criteria)' message. The UE then sends an 'RRC Measurement Report (GPS Measured Results #2)'. The SRNC sends another 'RESET UE POSITIONING STORED INFORMATION' message. The sequence continues with an ellipsis (...) and ends with an 'RRC Measurement Report (GPS Measured Results #n)' from the UE.
+
+Sequence diagram showing UE-Assisted GPS Message Sequence between SRNC and UE.
+
+Figure D.4: UE-Assisted GPS Message Sequence
+
+### D.3.2 UE assisted A-GPS Measurement Sequence for moving scenario and periodic update test case
+
+The assistance data requested by the UE and provided by the SRNC in this sequence of messages shall be selected from among those information elements described as available in clause E.3.
+
+![Sequence diagram showing the message exchange between SRNC and UE for A-GPS measurement. The sequence starts with SRNC sending a RESET UE POSITIONING STORED INFORMATION message to UE. This is followed by RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time) from SRNC to UE. UE responds with RRC Measurement Report (Additional Assistance Data Request). SRNC then sends RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9) to UE. UE responds with RRC Measurement Control (Modify, Periodical Reporting Criteria). UE then sends a series of RRC Measurement Reports (GPS Measured Results #1, #2, ..., #n) to SRNC.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)
+    UE-->>SRNC: RRC Measurement Report (Additional Assistance Data Request)
+    SRNC->>UE: RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)
+    UE-->>SRNC: RRC Measurement Control (Modify, Periodical Reporting Criteria)
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #1)
+    Note right of SRNC: ...
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #n)
+```
+
+Sequence diagram showing the message exchange between SRNC and UE for A-GPS measurement. The sequence starts with SRNC sending a RESET UE POSITIONING STORED INFORMATION message to UE. This is followed by RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time) from SRNC to UE. UE responds with RRC Measurement Report (Additional Assistance Data Request). SRNC then sends RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9) to UE. UE responds with RRC Measurement Control (Modify, Periodical Reporting Criteria). UE then sends a series of RRC Measurement Reports (GPS Measured Results #1, #2, ..., #n) to SRNC.
+
+Figure D.5: UE assisted GPS Message Sequence for moving scenario and periodic update
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS measured results.
+
+# Annex E (normative): Assistance data required for testing
+
+## E.1 Introduction
+
+This annex defines the assistance data IEs available in all test cases. The assistance data shall be given for satellites as defined in B.1.5.
+
+The information elements are given with reference to 3GPP TS 25.331 [4], where the details are defined.
+
+Clause E.2 lists the assistance data IEs required for testing of UE-based mode, and clause E.3 lists the assistance data available for testing of UE-assisted mode.
+
+## E.2 Information elements required for UE-based
+
+The following GPS assistance data IEs shall be present for each test:
+
+- a) **UE positioning GPS reference time IE.** This information element is defined in subclause 10.3.7.96 of 3GPP TS 25.331 [4].
+
+**Table E.1: UE positioning GPS reference time IE**
+
+| Name of the IE                                                                    | Fields of the IE                 | UE Based Coarse time | UE Based Fine Time |
+|-----------------------------------------------------------------------------------|----------------------------------|----------------------|--------------------|
+| UE positioning GPS reference time<br>subclause 10.3.7.96 of<br>3GPP TS 25.331 [4] |                                  |                      |                    |
+|                                                                                   | GPS Week                         | Yes                  | Yes                |
+|                                                                                   | GPS TOW msec                     | Yes                  | Yes                |
+|                                                                                   | UTRAN GPS reference time         |                      | Yes                |
+|                                                                                   | >UTRAN GPS timing of cell frames |                      | Yes                |
+|                                                                                   | >CHOICE mode                     |                      | Yes                |
+|                                                                                   | >>FDD                            |                      | Yes                |
+|                                                                                   | >>>Primary CPICH Info            |                      | Yes                |
+|                                                                                   | >>TDD                            |                      |                    |
+|                                                                                   | >>>cell parameters id            |                      |                    |
+|                                                                                   | >SFN                             |                      | Yes                |
+|                                                                                   | SFN-TOW Uncertainty              |                      | Yes                |
+|                                                                                   | TUTRAN-GPS drift rate            |                      | Yes                |
+|                                                                                   | GPS TOW Assist                   | Yes                  | Yes                |
+|                                                                                   | SatID                            | Yes                  | Yes                |
+|                                                                                   | TLM Message                      | Yes                  | Yes                |
+|                                                                                   | TLM Reserved                     | Yes                  | Yes                |
+|                                                                                   | Alert                            | Yes                  | Yes                |
+|                                                                                   | Anti-Spoof                       | Yes                  | Yes                |
+
+- b) **UE positioning GPS reference UE position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [4].
+
+**Table E.2: UE positioning GPS reference UE position IE**
+
+| Name of the IE                                               | Fields of the IE                                        | UE Based Coarse time | UE Based Fine Time |
+|--------------------------------------------------------------|---------------------------------------------------------|----------------------|--------------------|
+| Reference Location subclause 10.3.8.4c of 3GPP TS 25.331 [4] | Ellipsoid point with Altitude and uncertainty ellipsoid | Yes                  | Yes                |
+
+- c) **UE positioning GPS navigation model IE.** This information element is defined in subclause 10.3.7.94 of 3GPP TS 25.331 [4]. The Navigation model will be chosen for the reference time and reference position.
+
+**Table E.3: UE positioning GPS navigation model IE**
+
+| Name of the IE                                             | Fields of the IE | UE Based Coarse time | UE Based Fine Time |
+|------------------------------------------------------------|------------------|----------------------|--------------------|
+| Navigation Model subclause 10.3.7.94 of 3GPP TS 25.331 [4] |                  | Yes                  | Yes                |
+
+- d) **UE positioning GPS ionospheric model IE.** This information element is defined in subclause 10.3.7.92 of 3GPP TS 25.331 [4].
+
+**Table E.4: UE positioning GPS ionospheric model IE**
+
+| Name of the IE                                              | Fields of the IE | UE Based Coarse time | UE Based Fine Time |
+|-------------------------------------------------------------|------------------|----------------------|--------------------|
+| Ionospheric Model subclause 10.3.7.92 of 3GPP TS 25.331 [4] |                  | Yes                  | Yes                |
+
+## --- E.3 Information elements available for UE-assisted
+
+The following GPS assistance data IEs shall be available for each test:
+
+- a) **UE positioning GPS reference time IE.** This information element is defined in subclause 10.3.7.96 of 3GPP TS 25.331 [4].
+
+**Table E.5: UE positioning GPS reference time IE**
+
+| Name of the IE                                                                 | Fields of the IE                 | UE Assisted Coarse time | UE Assisted Fine Time |
+|--------------------------------------------------------------------------------|----------------------------------|-------------------------|-----------------------|
+| UE positioning GPS reference time<br>subclause 10.3.7.96 of 3GPP TS 25.331 [4] |                                  |                         |                       |
+|                                                                                | GPS Week                         | Yes                     | Yes                   |
+|                                                                                | GPS TOW msec                     | Yes                     | Yes                   |
+|                                                                                | UTRAN GPS reference time         |                         | Yes                   |
+|                                                                                | >UTRAN GPS timing of cell frames |                         | Yes                   |
+|                                                                                | >CHOICE mode                     |                         | Yes                   |
+|                                                                                | >>FDD                            |                         | Yes                   |
+|                                                                                | >>>Primary CPICH Info            |                         | Yes                   |
+|                                                                                | >>TDD                            |                         |                       |
+|                                                                                | >>>cell parameters id            |                         |                       |
+|                                                                                | >SFN                             |                         | Yes                   |
+|                                                                                | SFN-TOW Uncertainty              |                         | Yes                   |
+|                                                                                | TUTRAN-GPS drift rate            |                         | Yes                   |
+|                                                                                | GPS TOW Assist                   | Yes                     | Yes                   |
+|                                                                                | SatID                            | Yes                     | Yes                   |
+|                                                                                | TLM Message                      | Yes                     | Yes                   |
+|                                                                                | TLM Reserved                     | Yes                     | Yes                   |
+|                                                                                | Alert                            | Yes                     | Yes                   |
+|                                                                                | Anti-Spoof                       | Yes                     | Yes                   |
+
+- b) **UE positioning GPS reference UE position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [4].
+
+**Table E.6: UE positioning GPS reference UE position IE**
+
+| Name of the IE                                                  | Fields of the IE                                        | UE Assisted Coarse Time | UE Assisted Fine Time |
+|-----------------------------------------------------------------|---------------------------------------------------------|-------------------------|-----------------------|
+| Reference Location<br>subclause 10.3.8.4c of 3GPP TS 25.331 [4] | Ellipsoid point with Altitude and uncertainty ellipsoid | Yes                     | Yes                   |
+
+- c) **UE positioning GPS almanac** This information element is defined in subclause 10.3.7.89 of 3GPP TS 25.331 [4]. The Almanac shall be chosen for the reference time.
+
+**Table E.7: UE positioning GPS almanac IE**
+
+| Name of the IE                                                          | Fields of the IE       | UE Assisted Coarse Time | UE Assisted Fine Time |
+|-------------------------------------------------------------------------|------------------------|-------------------------|-----------------------|
+| UE positioning GPS almanac<br>subclause 10.3.7.89 of 3GPP TS 25.331 [4] |                        |                         |                       |
+|                                                                         | Almanac Reference Week | Yes                     | Yes                   |
+|                                                                         | Satellite information  | Yes                     | Yes                   |
+
+- d) **UE positioning GPS navigation model IE.** This information element is defined in subclause 10.3.7.94 of 3GPP TS 25.331 [4]. The Navigation model will be chosen for the reference time and reference position.
+
+**Table E.8: UE positioning GPS navigation model IE**
+
+| Name of the IE                                                | Fields of the IE | UE Assisted Coarse Time | UE Assisted Fine Time |
+|---------------------------------------------------------------|------------------|-------------------------|-----------------------|
+| Navigation Model<br>subclause 10.3.7.94 of 3GPP TS 25.331 [4] |                  | Yes                     | Yes                   |
+
+- e) **UE positioning GPS acquisition assistance IE.** This information element is defined in subclause 10.3.7.88 of 3GPP TS 25.331 [4].
+
+**Table E.9: UE positioning GPS acquisition assistance IE**
+
+| Name of the IE                                                   | Fields of the IE                       | UE Assisted Coarse time | UE Assisted Fine Time |
+|------------------------------------------------------------------|----------------------------------------|-------------------------|-----------------------|
+| Acquisition Assistance subclause 10.3.7.88 of 3GPP TS 25.331 [4] |                                        |                         |                       |
+| -                                                                | GPS TOW msec                           | Yes                     | Yes                   |
+| -                                                                | UTRAN GPS reference time               |                         | Yes                   |
+| -                                                                | >UTRAN GPS timing of cell frames       |                         | Yes                   |
+| -                                                                | >CHOICE <i>mode</i>                    |                         | Yes                   |
+| -                                                                | >>FDD                                  |                         | Yes                   |
+| -                                                                | >>>Primary CPICH Info                  |                         | Yes                   |
+| -                                                                | >SFN                                   |                         | Yes                   |
+| -                                                                | Satellite information                  | Yes                     | Yes                   |
+| -                                                                | >SatID                                 | Yes                     | Yes                   |
+|                                                                  | >Doppler (0 <sup>th</sup> order term)  | Yes                     | Yes                   |
+|                                                                  | >Extra Doppler                         | Yes                     | Yes                   |
+|                                                                  | >>Doppler (1 <sup>st</sup> order term) | Yes                     | Yes                   |
+|                                                                  | >>Doppler Uncertainty                  | Yes                     | Yes                   |
+|                                                                  | >Code Phase                            | Yes                     | Yes                   |
+|                                                                  | >Integer Code Phase                    | Yes                     | Yes                   |
+|                                                                  | >GPS Bit number                        | Yes                     | Yes                   |
+|                                                                  | >Code Phase Search Window              | Yes                     | Yes                   |
+|                                                                  | >Azimuth and Elevation                 | Yes                     | Yes                   |
+|                                                                  | >> Azimuth                             | Yes                     | Yes                   |
+|                                                                  | >> Elevation                           | Yes                     | Yes                   |
+
+# --- Annex F (normative): Converting UE-assisted measurement reports into position estimates
+
+## F.1 Introduction
+
+To convert the UE measurement reports in case of UE-assisted mode of A-GPS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [8], [9] and [10].
+
+## --- F.2 UE measurement reports
+
+In case of UE-assisted A-GPS, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE (subclause 10.3.7.93 in 3GPP TS 25.331 [4]). The measurement parameters required for calculating the UE position are:
+
+- 1) Reference Time: The UE has two choices for the Reference Time:
+  - a) "UE GPS timing of cell frames";
+  - b) "GPS TOW msec".
+- 2) Measurement Parameters: 1 to <maxSat>:
+  - a) "Satellite ID (SV PRN)";
+  - b) "Whole GPS chips";
+  - c) "Fractional GPS Chips";
+  - d) "Pseudorange RMS Error".
+
+Additional information required at the system simulator:
+
+- 1) "UE positioning GPS reference UE position" (subclause 10.3.8.4c in 3GPP TS 25.331 [4]):  
+Used for initial approximate receiver coordinates.
+- 2) "UE positioning GPS navigation model" (subclause 10.3.7.94 in 3GPP TS 25.331 [4]):  
+Contains the GPS ephemeris and clock correction parameters as specified in [8]; used for calculating the satellite positions and clock corrections.
+- 3) "UE positioning GPS ionospheric model" (subclause 10.3.7.92 in 3GPP TS 25.331 [4]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [8] for computation of the ionospheric delay.
+
+## F.3 WLS position solution
+
+The WLS position solution problem is concerned with the task of solving for four unknowns;  $x_u, y_u, z_u$  the receiver coordinates in a suitable frame of reference (usually ECEF) and  $b_u$  the receiver clock bias. It typically requires the following steps:
+
+### Step 1: Formation of pseudo-ranges
+
+The observation of code phase reported by the UE for each satellite  $SV_i$  is related to the pseudo-range/c modulo 1 ms (the length of the C/A code period). For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite  $SV_i$  is calculated and the integer number of milli-seconds to be added to the UE code phase measurements is obtained.
+
+### Step 2: Formation of weighting matrix
+
+The UE reported "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm [9]. According to 3GPP TS 25.331 [4], the encoding for this field is a 6 bit value that consists of a 3 bit mantissa,  $X_i$  and a 3 bit exponent,  $Y_i$  for each  $SV_i$ :
+
+$$w_i = RMSError = 0.5 \times \left(1 + \frac{X_i}{8}\right) \times 2^{Y_i}$$
+
+The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "Pseudorange RMS Error" values:
+
+$$\mathbf{W} = \text{diag}\{1/w_1^2, 1/w_2^2, \dots, 1/w_n^2\}$$
+
+### Step 3: WLS position solution
+
+The WLS position solution is described in reference [9] and usually requires the following steps:
+
+- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in [8] section 20.3.3.4.3.
+- 2) Computation of clock correction parameters using the parameters and algorithms as defined in [8] section 20.3.3.3.1.
+- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in [8] section 20.3.3.5.2.5 for the ionospheric delay, and using the Gupta model in reference [10] p. 121 equation (2) for the tropospheric delay.
+- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required:
+  - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report.
+  - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in [8,9].
+  - c) Calculate difference between predicted and measured pseudo-ranges  $\Delta p$
+  - d) Calculate the "Geometry Matrix" **G** as defined in [9]:
+
+$$\mathbf{G} \equiv \begin{bmatrix} -\hat{\mathbf{l}}_1^T & 1 \\ -\hat{\mathbf{l}}_2^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{l}}_n^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{l}}_i \equiv \frac{\mathbf{r}_{si} - \hat{\mathbf{r}}_u}{|\mathbf{r}_{si} - \hat{\mathbf{r}}_u|} \text{ where } \mathbf{r}_{si} \text{ is the Satellite position vector for SV}_i \text{ (calculated in 1)} \\ \text{above), and } \hat{\mathbf{r}}_u \text{ is the estimate of the user location.}$$
+
+- e) Calculate the WLS solution according to [9]:
+
+$$\Delta \hat{\mathbf{x}} = (\mathbf{G}^T \mathbf{W} \mathbf{G})^{-1} \mathbf{G}^T \mathbf{W} \Delta \boldsymbol{\rho}$$
+
+- f) Adding the  $\Delta \hat{\mathbf{x}}$  to the initial state estimate gives an improved estimate of the state vector:
+
+$$\hat{\mathbf{x}} \rightarrow \hat{\mathbf{x}} + \Delta \hat{\mathbf{x}}.$$
+
+- 5) This new state vector  $\hat{\mathbf{x}}$  can be used as new initial estimate and the procedure is repeated until the change in  $\hat{\mathbf{x}}$  is sufficiently small.
+
+### Step 4: Transformation from Cartesian coordinate system to Geodetic coordinate system
+
+The state vector  $\hat{\mathbf{x}}$  calculated in Step 3 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates  $x_u, y_u, z_u$  to geodetic latitude  $\varphi$ , longitude  $\lambda$  and altitude  $h$  on the WGS84 reference ellipsoid.
+
+### Step 5: Calculation of "2-D Position Errors"
+
+The latitude  $\varphi$  / longitude  $\lambda$  obtained after Step 4 is used to calculate the 2-D position error.
+
+# Annex G (informative): Change History
+
+**Table G.1: TS history before approval**
+
+| Date     | Meeting                        | Document  | Comment                                                                             | Version old | Version New |
+|----------|--------------------------------|-----------|-------------------------------------------------------------------------------------|-------------|-------------|
+|          | RAN WG4 #29                    | R4-031082 | Document proposed at RAN#29                                                         |             |             |
+|          | RAN WG4 #29                    | R4-031156 | Comments added inline with discussion at RAN#29                                     |             |             |
+| Dec 2003 |                                |           | Comment on R4-031156                                                                |             |             |
+| Jan 2004 | RAN WG4 #30                    | R4-040104 | Comments added after Ad-hoc 29/1/04                                                 |             |             |
+| Jan 2004 | RAN WG4 #29                    | R4-040169 | Revised version of R4-040104 to allow printing                                      |             |             |
+| May 2004 | RAN WG4 #31                    | R4-040362 | Revised version of R4-040233                                                        |             |             |
+| May 2004 | RAN WG4 #31                    | R4-040387 | Approved version at RAN#31                                                          |             |             |
+| May 2004 | RAN WG4 #31                    |           | V0.0.0 produced based on R4-040387                                                  |             | 0.0.0       |
+| May 2004 |                                |           | V0.1.0 with input from R4-040364                                                    | 0.0.0       | 0.1.0       |
+| Aug 2004 | Conference call on Aug 5, 2004 |           | V0.1.0 with approved CRs: R4-04043, R4-04048, R4AH-04049, R4AH-04050 and R4AH-04052 | 0.1.0       | 0.2.0       |
+| Aug 2004 | RAN WG4 #32                    | R4-040465 | V0.2.0 for approval at RAN WG4 #32                                                  |             |             |
+| Aug 2004 | RAN WG4 #32                    | R4-040564 | V0.3.0 for approval at RAN WG4 #32, inclusion of changes in R4-040535               | 0.2.0       | 0.3.0       |
+| Sep 2004 | RAN #25                        | RP-040341 | Submit for approval                                                                 | 0.3.0       | 1.0.0       |
+| Sep 2004 | RAN #25                        |           | Approved at RAN#24                                                                  | 1.0.0       | 6.0.0       |
+
+**Table G.2: Release 6 CR approved at TSG RAN #26**
+
+| RAN Tdoc  | Spec   | CR  | R | Ph    | Title                                   | Cat | Curr  | New   | Work Item          |
+|-----------|--------|-----|---|-------|-----------------------------------------|-----|-------|-------|--------------------|
+| RP-040413 | 25.171 | 001 | 2 | Rel-6 | Removal of inconsistencies in TS 25.171 | F   | 6.0.0 | 6.1.0 | LCS-UEPos-AGPSPerf |
+
+**Table G.3: Release 6 CR approved at TSG RAN #29**
+
+| RAN Tdoc  | Spec   | CR   | R | Ph    | Title                    | Cat | Curr  | New   | Work Item          |
+|-----------|--------|------|---|-------|--------------------------|-----|-------|-------|--------------------|
+| RP-050499 | 25.171 | 0003 | 1 | Rel-6 | Changes to GPS scenarios | F   | 6.1.0 | 6.2.0 | LCS-UEPos-AGPSPerf |
+
+**Table G.4: Creation of Release 7**
+
+| RAN Tdoc | Spec   | CR | R | Ph    | Title                                          | Cat | Curr  | New   | Work Item |
+|----------|--------|----|---|-------|------------------------------------------------|-----|-------|-------|-----------|
+|          | 25.171 |    |   | Rel-7 | Release 7 created following decision at RAN#31 |     | 6.1.0 | 7.0.0 |           |
+
+**Table G.4: Release 7 CRs approved at TSG RAN #32**
+
+| RAN Tdoc  | Spec   | CR   | R | Ph    | Title                                                          | Cat | Curr  | New   | Work Item |
+|-----------|--------|------|---|-------|----------------------------------------------------------------|-----|-------|-------|-----------|
+| RP-060305 | 25.171 | 0005 |   | Rel-7 | Horizontal Accuracy IE change for nominal accuracy requirement | A   | 7.0.0 | 7.1.0 | TEI6      |
+| RP-060305 | 25.171 | 0007 |   | Rel-7 | Change to altitude of simulated UE position                    | A   | 7.0.0 | 7.1.0 | TEI6      |
+
+Table G.5: Release 8
+
+| RAN Meeting | RAN Tdoc | CR | R | Title                          | Cat | Curr   | New    | Work Item |
+|-------------|----------|----|---|--------------------------------|-----|--------|--------|-----------|
+| SP-42       |          |    |   | Upgrade unchanged from Rel 7   |     |        | 8.0.0  |           |
+| SP-46       |          |    |   | Upgrade unchanged from Rel 8   |     |        | 9.0.0  |           |
+| SP-51       |          |    |   | Upgraded unchanged from Rel-9  |     | 9.0.0  | 10.0.0 |           |
+| SP-57       | -        | -  | - | Update to Rel-11 version (MCC) | -   | 10.0.0 | 11.0.0 | -         |
+| SP-65       | -        | -  | - | Update to Rel-12 version (MCC) | -   | 11.0.0 | 12.0.0 |           |
+| SP-70       | -        | -  | - | Update to Rel-13 version (MCC) | -   | 12.0.0 | 13.0.0 |           |
+| RP-75       | -        | -  | - | Update to Rel-14 version (MCC) | -   | 13.0.0 | 14.0.0 |           |
+
+| Change history |         |      |    |     |     |                                |  |             |
+|----------------|---------|------|----|-----|-----|--------------------------------|--|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                |  | New version |
+| 2018-06        | SA#80   | -    | -  | -   | -   | Update to Rel-15 version (MCC) |  | 15.0.0      |
+| 2020-06        | SA#88   | -    | -  | -   | -   | Update to Rel-16 version (MCC) |  | 16.0.0      |
+| 2022-03        | SA#95   |      |    |     |     | Update to Rel-17 version (MCC) |  | 17.0.0      |
+| 2024-03        | RAN#103 |      |    |     |     | Update to Rel-18 version (MCC) |  | 18.0.0      |

marked/Rel-18/25_series/25172/raw.md

@@ -0,0 +1,1214 @@
+
+
+# 3GPP TS 25.172 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of Galileo and Additional Navigation Satellite Systems (A-GNSS) Frequency Division Duplex (FDD) (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                       |           |
+|-----------------------------------------------------------------------|-----------|
+| Foreword .....                                                        | 5         |
+| 1 Scope.....                                                          | 6         |
+| 2 References.....                                                     | 6         |
+| 3 Definitions, symbols, abbreviations and test tolerances .....       | 7         |
+| 3.1 Definitions.....                                                  | 7         |
+| 3.2 Symbols.....                                                      | 7         |
+| 3.3 Abbreviations .....                                               | 7         |
+| 3.4 Test tolerances.....                                              | 8         |
+| 4 General.....                                                        | 8         |
+| 4.1 Introduction .....                                                | 8         |
+| 4.2 Measurement parameters.....                                       | 9         |
+| 4.2.1 UE-based A-GNSS measurement parameters .....                    | 9         |
+| 4.2.2 UE-assisted A-GNSS measurement parameters.....                  | 9         |
+| 4.3 Response time .....                                               | 9         |
+| 4.4 Time assistance .....                                             | 9         |
+| 4.4.1 Use of fine time assistance .....                               | 9         |
+| 4.5 RRC states.....                                                   | 10        |
+| 4.6 2D position error .....                                           | 10        |
+| 4.7 User equipment supporting multiple constellations .....           | 10        |
+| 4.8 User equipment supporting multiple signals.....                   | 10        |
+| 5 A-GNSS minimum performance requirements.....                        | 10        |
+| 5.1 Sensitivity.....                                                  | 11        |
+| 5.1.1 Coarse time assistance.....                                     | 11        |
+| 5.1.1.1 Minimum requirements (coarse time assistance).....            | 11        |
+| 5.1.2 Fine time assistance.....                                       | 12        |
+| 5.1.2.1 Minimum requirements (fine time assistance).....              | 12        |
+| 5.2 Nominal accuracy.....                                             | 12        |
+| 5.2.1 Minimum requirements (nominal accuracy) .....                   | 13        |
+| 5.3 Dynamic range .....                                               | 13        |
+| 5.3.1 Minimum requirements (dynamic range).....                       | 14        |
+| 5.4 Multi-path scenario .....                                         | 14        |
+| 5.4.1 Minimum requirements (multi-path scenario).....                 | 15        |
+| 5.5 Moving scenario and periodic update .....                         | 15        |
+| 5.5.1 Minimum requirements (moving scenario and periodic update)..... | 16        |
+| <b>Annex A (normative): Test cases.....</b>                           | <b>18</b> |
+| A.1 Conformance tests.....                                            | 18        |
+| A.2 Requirement classification for statistical testing .....          | 18        |
+| <b>Annex B (normative): Test conditions.....</b>                      | <b>19</b> |
+| B.1 General.....                                                      | 19        |
+| B.1.1 Parameter values .....                                          | 19        |
+| B.1.2 Time assistance .....                                           | 19        |
+| B.1.3 GNSS reference time.....                                        | 19        |
+| B.1.4 Reference and UE locations.....                                 | 20        |
+| B.1.5 Satellite constellation and assistance data.....                | 20        |
+| B.1.6 Atmospheric delay.....                                          | 20        |
+| B.1.7 Sensors .....                                                   | 20        |
+| B.1.8 Information elements.....                                       | 20        |
+| B.1.9 GNSS signals.....                                               | 20        |
+| B.1.10 RESET UE POSITIONING STORED INFORMATION Message .....          | 20        |
+| B.1.11 GNSS system time offsets.....                                  | 21        |
+
+|                               |                                                                                |           |
+|-------------------------------|--------------------------------------------------------------------------------|-----------|
+| <b>Annex C (normative):</b>   | <b>Propagation conditions .....</b>                                            | <b>22</b> |
+| C.1                           | Static propagation conditions.....                                             | 22        |
+| C.2                           | Multi-path case.....                                                           | 22        |
+| <b>Annex D (normative):</b>   | <b>Measurement sequence chart.....</b>                                         | <b>24</b> |
+| D.1                           | General.....                                                                   | 24        |
+| D.2                           | TTFF measurement sequence chart .....                                          | 24        |
+| D.3                           | Periodic update measurement sequence chart.....                                | 25        |
+| <b>Annex E (normative):</b>   | <b>Assistance data required for testing .....</b>                              | <b>27</b> |
+| E.1                           | Introduction.....                                                              | 27        |
+| E.2                           | GPS assistance data.....                                                       | 27        |
+| E.3                           | GANSS assistance data.....                                                     | 27        |
+| <b>Annex F (normative):</b>   | <b>Converting UE-assisted measurement reports into position estimates ....</b> | <b>31</b> |
+| F.1                           | Introduction.....                                                              | 31        |
+| F.2                           | UE measurement reports.....                                                    | 31        |
+| F.3                           | Weighted Least Squares (WLS) position solution .....                           | 32        |
+| <b>Annex G (informative):</b> | <b>Change history.....</b>                                                     | <b>35</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# 1 Scope
+
+The present document establishes the minimum performance requirements for A-GANSS for FDD mode of UTRA for the User Equipment (UE) that supports A-GANSS. It includes the minimum performance requirements for both UE-based and UE-assisted A-GANSS. The minimum performance requirements also include combinations of A-GPS and A-GANSS.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
+- [3] IS-GPS-200, Revision D, "Navstar GPS Space Segment/Navigation User Interfaces", March 7<sup>th</sup>, 2006.
+- [4] IS-GPS-705, "Navstar GPS Space Segment/User Segment L5 Interfaces", September 22, 2005.
+- [5] IS-GPS-800, "Navstar GPS Space Segment/User Segment L1C Interfaces", September 4, 2008.
+- [6] IS-QZSS, "Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS", Ver.1.1, July 31, 2009.
+- [7] "Galileo OS Signal in Space ICD (OS SIS ICD)", Draft 0, Galileo Joint Undertaking, May 23<sup>rd</sup>, 2006.
+- [8] "Global Navigation Satellite System GLONASS Interface Control Document", Version 5.1, 2008.
+- [9] "Specification for the Wide Area Augmentation System (WAAS) ", US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.
+- [10] 3GPP TS 25.171: "Requirements for support of Assisted Global Positioning System (A-GPS) Frequency Division Duplex (FDD)".
+- [11] 3GPP TS 34.171: "Terminal Conformance Specification, Assisted Global Positioning System (A-GPS) (FDD)".
+- [12] 3GPP TS 34.172: "Terminal Conformance Specification, Assisted Galileo and Additional Navigation Satellite Systems (A-GANSS) (FDD)".
+- [13] 3GPP TS 34.109: "Special conformance testing functions".
+- [14] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [15] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+
+- [16] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996.
+- [17] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119.
+- [18] 3GPP TS 25.215: "Physical layer; Measurements (FDD)".
+- [19] BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal BII(Version 1.0), China Satellite Navigation Office, December 2012.
+
+# 3 Definitions, symbols, abbreviations and test tolerances
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.101 [1], 3GPP TS 25.104 [2] and the following apply:
+
+**Horizontal Dilution Of Precision (HDOP):** measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbol applies:
+
+|                                |                                                                                                                            |
+|--------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| B1I                            | BeiDou B1I navigation signal with carrier frequency of 1561.098 MHz.                                                       |
+| $c$                            | Speed of light.                                                                                                            |
+| E1                             | Galileo E1 navigation signal with carrier frequency of 1575.420 MHz.                                                       |
+| E5                             | Galileo E5 navigation signal with carrier frequency of 1191.795 MHz.                                                       |
+| E6                             | Galileo E6 navigation signal with carrier frequency of 1278.750 MHz.                                                       |
+| G1                             | GLONASS navigation signal in the L1 sub-bands with carrier frequencies $1602 \text{ MHz} \pm k \times 562.5 \text{ kHz}$ . |
+| G2                             | GLONASS navigation signal in the L2 sub-bands with carrier frequencies $1246 \text{ MHz} \pm k \times 437.5 \text{ kHz}$ . |
+| $k$                            | GLONASS channel number, $k = -7 \dots 13$ .                                                                                |
+| L1 C/A                         | GPS or QZSS L1 navigation signal carrying the Coarse/Acquisition code with carrier frequency of 1575.420 MHz.              |
+| L1C                            | GPS or QZSS L1 Civil navigation signal with carrier frequency of 1575.420 MHz.                                             |
+| L2C                            | GPS or QZSS L2 Civil navigation signal with carrier frequency of 1227.600 MHz.                                             |
+| L5                             | GPS or QZSS L5 navigation signal with carrier frequency of 1176.450 MHz.                                                   |
+| $\mathbf{G}$                   | Geometry Matrix.                                                                                                           |
+| $\rho_{\text{GNSS}_m,i}$       | Measured pseudo-range of satellite $i$ of $\text{GNSS}_m$ .                                                                |
+| $\mathbf{W}$                   | Weighting Matrix.                                                                                                          |
+| $\mathbf{l}_{\text{GNSS}_m,i}$ | Line of sight unit vector from the user to the satellite $i$ of $\text{GNSS}_m$ .                                          |
+| $\mathbf{x}$                   | State vector of user position and clock bias.                                                                              |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                              |
+|---------|--------------------------------------------------------------|
+| A-GANSS | Assisted-Galileo and Additional Navigation Satellite Systems |
+| A-GNSS  | Assisted-GNSS                                                |
+| A-GPS   | Assisted-Global Positioning System                           |
+| AWGN    | Additive White Gaussian Noise                                |
+| BDS     | BeiDou Navigation Satellite System                           |
+
+|         |                                                                                              |
+|---------|----------------------------------------------------------------------------------------------|
+| C/A     | Coarse/Acquisition                                                                           |
+| DUT     | Device Under Test                                                                            |
+| ECEF    | Earth-Centered, Earth-Fixed                                                                  |
+| ECI     | Earth-Centered-Inertial                                                                      |
+| FDD     | Frequency Division Duplex                                                                    |
+| GEO     | Geostationary Earth Orbit                                                                    |
+| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) |
+| GNSS    | Global Navigation Satellite System                                                           |
+| GPS     | Global Positioning System                                                                    |
+| GSS     | GNSS System Simulator                                                                        |
+| HDOP    | Horizontal Dilution Of Precision                                                             |
+| ICD     | Interface Control Document                                                                   |
+| IGSO    | Inclined Geosynchronous Satellite Orbit                                                      |
+| IS      | Interface Specification                                                                      |
+| LOS     | Line Of Sight                                                                                |
+| MEO     | Medium Earth Orbit                                                                           |
+| QZS     | Quasi-Zenith Satellite                                                                       |
+| QZSS    | Quasi-Zenith Satellite System                                                                |
+| RF      | Radio Frequency                                                                              |
+| RRC     | Radio Resource Control                                                                       |
+| SBAS    | Space Based Augmentation System                                                              |
+| SFN     | System Frame Number                                                                          |
+| SS      | FDD System Simulator                                                                         |
+| SV      | Space Vehicle                                                                                |
+| TBD     | To Be Determined                                                                             |
+| TOD     | Time Of Day                                                                                  |
+| TOW     | Time Of Week                                                                                 |
+| TTFF    | Time To First Fix                                                                            |
+| UE      | User Equipment                                                                               |
+| UTRA    | Universal Terrestrial Radio Access                                                           |
+| UTRAN   | Universal Terrestrial Radio Access Network                                                   |
+| WLS     | Weighted Least Squares                                                                       |
+| WGS-84  | World Geodetic System 1984                                                                   |
+
+## 3.4 Test tolerances
+
+The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 34.172 [12] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle.
+
+Shared Risk is defined in ETR 273-1-2 [15], subclause 6.5.
+
+# --- 4 General
+
+## 4.1 Introduction
+
+The present document defines the minimum performance requirements for both UE-based and UE-assisted FDD A-GNSS terminals. The minimum performance requirements also include combinations of A-GPS and A-GNSS.
+
+## 4.2 Measurement parameters
+
+### 4.2.1 UE-based A-GNSS measurement parameters
+
+In case of UE-based A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter in case of UE-based A-GNSS is the horizontal position estimate reported by the UE and expressed in latitude/longitude.
+
+### 4.2.2 UE-assisted A-GNSS measurement parameters
+
+In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GNSS MEASURED RESULTS IE. The measurement parameters in case of UE-assisted A-GNSS are the UE GNSS code measurements, as specified in 3GPP TS 25.215 [18]. The UE GNSS code measurements that may be combined with UE GPS code phase measurements as specified in 3GPP TS 25.215 [18] are converted into a horizontal position estimate using the procedure detailed in Annex F.
+
+## 4.3 Response time
+
+Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GNSS and GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS and GNSS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re-use any information on GNSS and GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [13] clause 5.4 for the purpose of deleting this information and is detailed in subclause B.1.10.
+
+## 4.4 Time assistance
+
+Time assistance is the provision of GNSS reference time to the UE from the network via RRC messages. Currently two different GNSS time assistance methods can be provided by the network.
+
+- a) Coarse time assistance is always provided by the network and provides current GNSS time to the UE. The time provided is within  $\pm 2$  seconds of GNSS system time. It is signalled to the UE by means of the GNSS Day and GNSS TOD fields in the GNSS Reference Time assistance data IE.
+- b) Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GNSS system time and the current UTRAN time. The accuracy of this relationship is  $\pm 10 \mu\text{s}$  of the actual relationship. This addresses the case when the network can provide an improved GNSS time accuracy. It is signalled to the UE by means of the SFN and UTRAN GNSS timing of cell frames fields in the GNSS Reference Time assistance data IE.
+
+The specific GNSS system time is identified through the GNSS Time ID field of the GNSS Reference Time IE. In case where several GNSS are used in the tests, only one GNSS Time ID is used to determine the Time of Day. For all the constellations, the GNSS Time Model assistance and UTC Model assistance shall be available at the system simulator, as specified in Annex E.
+
+The time of applicability of time assistance is the beginning of the System Frame of the message containing the GNSS Reference time.
+
+### 4.4.1 Use of fine time assistance
+
+The use of fine time assistance to improve the GNSS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in subclause 5.1.2.
+
+## 4.5 RRC states
+
+The minimum A-GNSS performance requirements are specified in clause 5 for different RRC states that include Cell\_DCH and Cell\_FACH. Cell\_PCH and URA\_PCH states are for further study. The test and verification procedures are separately defined in Annex B.
+
+## 4.6 2D position error
+
+The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual position of the UE in the test case considered.
+
+## 4.7 User equipment supporting multiple constellations
+
+Minimum performance requirements are defined for each global GNSS constellation (Galileo, Modernized GPS, GLONASS and BDS). UEs supporting multiple global constellations shall meet the minimum performance requirements for a combined scenario where each UE supported constellation is simulated.
+
+NOTE: For test cases where signals from "GPS" and "Modernized GPS" are included, "GPS" and "Modernized GPS" are considered as a single constellation, unless otherwise specified.
+
+## 4.8 User equipment supporting multiple signals
+
+For UEs supporting multiple signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the UE. Signals not supported by the UE do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 4.8-1. The individual test scenarios in clause 5 define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clause 5 plus the relative power level defined in Table 4.8-1.
+
+**Table 4.8-1: Relative signal power levels for each signal type for each GNSS**
+
+|                                                        | Galileo |       | GPS/Modernized GPS |         | GLONASS |       | QZSS   |         | SBAS |      | BDS |    |       |
+|--------------------------------------------------------|---------|-------|--------------------|---------|---------|-------|--------|---------|------|------|-----|----|-------|
+|                                                        | E1      | 0 dB  | L1 C/A             | 0 dB    | G1      | 0 dB  | L1 C/A | 0 dB    | L1   | 0 dB | B1I | D1 | 0 dB  |
+| Signal power levels relative to reference power levels | E6      | +2 dB | L1C                | +1.5 dB | G2      | -6 dB | L1C    | +1.5 dB |      |      |     | D2 | +5 dB |
+|                                                        | E5      | +2 dB | L2C                | -1.5 dB |         |       | L2C    | -1.5 dB |      |      |     |    |       |
+|                                                        |         |       | L5                 | +3.6 dB |         |       | L5     | +3.6 dB |      |      |     |    |       |
+
+NOTE 1: For test cases which involve "Modernized GPS", the satellite simulator shall also generate the GPS L1 C/A signal if the UE supports "GPS" in addition to "Modernized GPS".
+
+NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately.
+
+NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites B1I signal type and D2 represents GEO satellites B1I signal type.
+
+# 5 A-GNSS minimum performance requirements
+
+The A-GNSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS and GNSS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network.
+
+In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in Annexes D and E.
+
+The requirements in CELL\_PCH and URA\_PCH states are for further study.
+
+## 5.1 Sensitivity
+
+A sensitivity requirement is essential for verifying the performance of A-GNSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance.
+
+### 5.1.1 Coarse time assistance
+
+In this test case 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5.1.1-1: Test parameters**
+
+| System             | Parameters                                | Unit    | Value             |
+|--------------------|-------------------------------------------|---------|-------------------|
+|                    | Number of generated satellites per system | -       | See Table 5.1.1-2 |
+|                    | Total number of generated satellites      | -       | 6                 |
+|                    | HDOP range                                |         | 1.4 to 2.1        |
+|                    | Propagation conditions                    | -       | AWGN              |
+|                    | GANSS coarse time assistance error range  | seconds | $\pm 2$           |
+| Galileo            | Reference high signal power level         | dBm     | -142              |
+|                    | Reference low signal power level          | dBm     | -147              |
+| GPS <sup>(1)</sup> | Reference high signal power level         | dBm     | -142              |
+|                    | Reference low signal power level          | dBm     | -147              |
+| GLONASS            | Reference high signal power level         | dBm     | -142              |
+|                    | Reference low signal power level          | dBm     | -147              |
+| BDS                | Reference high signal power level         | dBm     | -136              |
+|                    | Reference low signal power level          | dBm     | -145              |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+**Table 5.1.1-2: Power level and satellite allocation**
+
+|                      |                   | Satellite allocation for each constellation |        |        |
+|----------------------|-------------------|---------------------------------------------|--------|--------|
+|                      |                   | GNSS-1 <sup>(1)</sup>                       | GNSS-2 | GNSS-3 |
+| Single constellation | High signal level | 1                                           | -      | -      |
+|                      | Low signal level  | 5                                           | -      | -      |
+| Dual constellation   | High signal level | 1                                           | -      | -      |
+|                      | Low signal level  | 2                                           | 3      | -      |
+| Triple constellation | High signal level | 1                                           | -      | -      |
+|                      | Low signal level  | 1                                           | 2      | 2      |
+
+Note 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.
+
+#### 5.1.1.1 Minimum requirements (coarse time assistance)
+
+The position estimates shall meet the accuracy and response time specified in table 5.1.1.1-1.
+
+**Table 5.1.1.1-1: Minimum requirements (coarse time assistance)**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+### 5.1.2 Fine time assistance
+
+This requirement is only valid for fine time assistance capable UEs. In this requirement 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5.1.2-1: Test parameters**
+
+| System             | Parameters                                | Unit          | Value             |
+|--------------------|-------------------------------------------|---------------|-------------------|
+|                    | Number of generated satellites per system | -             | See Table 5.1.2-2 |
+|                    | Total number of generated satellites      | -             | 6                 |
+|                    | HDOP range                                |               | 1.4 to 2.1        |
+|                    | Propagation conditions                    | -             | AWGN              |
+|                    | GANSS coarse time assistance error range  | seconds       | $\pm 2$           |
+|                    | GANSS fine time assistance error range    | $\mu\text{s}$ | $\pm 10$          |
+| Galileo            | Reference signal power level              | dBm           | -147              |
+| GPS <sup>(1)</sup> | Reference signal power level              | dBm           | -147              |
+| GLONASS            | Reference signal power level              | dBm           | -147              |
+| BDS                | Reference signal power level              | dBm           | -147              |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+**Table 5.1.2-2: Satellite allocation**
+
+|                      | Satellite allocation for each constellation |        |        |
+|----------------------|---------------------------------------------|--------|--------|
+|                      | GNSS-1                                      | GNSS-2 | GNSS-3 |
+| Single constellation | 6                                           | -      | -      |
+| Dual constellation   | 3                                           | 3      | -      |
+| Triple constellation | 2                                           | 2      | 2      |
+
+#### 5.1.2.1 Minimum requirements (fine time assistance)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.1.2.1-1.
+
+**Table 5.1.2.1-1: Minimum requirements for fine time assistance capable terminals**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.2 Nominal accuracy
+
+Nominal accuracy requirement verifies the accuracy of A-GANSS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. If SBAS is to be tested one additional satellite shall be generated. AWGN channel model is used. The number of simulated satellites for each constellation is as defined in table 5.2-2.
+
+**Table 5.2-1: Test parameters**
+
+| System             | Parameters                                                                          | Unit    | Value                 |
+|--------------------|-------------------------------------------------------------------------------------|---------|-----------------------|
+|                    | Number of generated satellites per system                                           | -       | See Table 5.2-2       |
+|                    | Total number of generated satellites                                                | -       | 6 or 7 <sup>(2)</sup> |
+|                    | HDOP Range                                                                          | -       | 1.4 to 2.1            |
+|                    | Propagation conditions                                                              | -       | AWGN                  |
+|                    | GANSS coarse time assistance error range                                            | seconds | ±2                    |
+| GPS <sup>(1)</sup> | Reference signal power level for all satellites                                     | dBm     | -128.5                |
+| Galileo            | Reference signal power level for all satellites                                     | dBm     | -127                  |
+| GLONASS            | Reference signal power level for all satellites                                     | dBm     | -131                  |
+| QZSS               | Reference signal power level for all satellites                                     | dBm     | -128.5                |
+| SBAS               | Reference signal power level for all satellites                                     | dBm     | -131                  |
+| BDS                | Reference signal power level for all satellites                                     | dBm     | -133                  |
+| Note 1:            | "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |         |                       |
+| Note 2:            | 7 satellites apply only for SBAS case.                                              |         |                       |
+
+If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support.
+
+If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario.
+
+**Table 5.2-2: Satellite allocation**
+
+|                      | Satellite allocation for each constellation                        |                       |                       |      |
+|----------------------|--------------------------------------------------------------------|-----------------------|-----------------------|------|
+|                      | GNSS 1 <sup>(1)</sup>                                              | GNSS 2 <sup>(1)</sup> | GNSS 3 <sup>(1)</sup> | SBAS |
+| Single constellation | 6                                                                  | --                    | --                    | 1    |
+| Dual constellation   | 3                                                                  | 3                     | --                    | 1    |
+| Triple constellation | 2                                                                  | 2                     | 2                     | 1    |
+| Note 1:              | GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |                       |                       |      |
+
+### 5.2.1 Minimum requirements (nominal accuracy)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.2.1-1.
+
+**Table 5.2.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 15 m               | 20 s              |
+
+## 5.3 Dynamic range
+
+The aim of a dynamic range requirement is to ensure that a GANSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. Two different reference power levels, denoted as "high" and "low" are used for each GNSS. The allocation of "high" and "low" power level satellites depends on the number of supported GNSSs and it is defined in Table 5.3-2. AWGN channel model is used.
+
+**Table 5.3-1: Test parameters**
+
+| System             | Parameters                                | Unit    | Value           |
+|--------------------|-------------------------------------------|---------|-----------------|
+|                    | Number of generated satellites per system | -       | See Table 5.3-2 |
+|                    | Total number of generated satellites      | -       | 6               |
+|                    | HDOP Range                                | -       | 1.4 to 2.1      |
+|                    | Propagation conditions                    | -       | AWGN            |
+|                    | GANSS coarse time assistance error range  | seconds | ±2              |
+| Galileo            | Reference high signal power level         | dBm     | -127.5          |
+|                    | Reference low signal power level          | dBm     | -147            |
+| GPS <sup>(1)</sup> | Reference high signal power level         | dBm     | -129            |
+|                    | Reference low signal power level          | dBm     | -147            |
+| GLONASS            | Reference high signal power level         | dBm     | -131.5          |
+|                    | Reference low signal power level          | dBm     | -147            |
+| BDS                | Reference high signal power level         | dBm     | -133.5          |
+|                    | Reference low signal power level          | dBm     | -145            |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+**Table 5.3-2: Power level and satellite allocation**
+
+|                      |                   | Satellite allocation for each constellation |                       |                       |
+|----------------------|-------------------|---------------------------------------------|-----------------------|-----------------------|
+|                      |                   | GNSS 1 <sup>(1)</sup>                       | GNSS 2 <sup>(1)</sup> | GNSS 3 <sup>(1)</sup> |
+| Single constellation | High signal level | 2                                           | --                    | --                    |
+|                      | Low signal level  | 4                                           | --                    | --                    |
+| Dual constellation   | High signal level | 1                                           | 1                     | --                    |
+|                      | Low signal level  | 2                                           | 2                     | --                    |
+| Triple constellation | High signal level | 1                                           | 1                     | 1                     |
+|                      | Low signal level  | 1                                           | 1                     | 1                     |
+
+Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.
+
+### 5.3.1 Minimum requirements (dynamic range)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.3.1-1.
+
+**Table 5.3.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.4 Multi-path scenario
+
+The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate.
+
+In this test 6 satellites are generated for the terminal. Some of the satellites have a one tap channel representing the Line-Of-Sight (LOS) signal. The other satellites have a two-tap channel, where the first tap represents the LOS signal and the second represents a reflected and attenuated signal as specified in Annex C.2. The number of satellites generated for each GNSS as well as the channel model used depends on the number of systems supported by the UE and is defined in table 5.4-2. The channel model as specified in Annex C.2 further depends on the generated signal.
+
+Table 5.4-1: Test parameter
+
+| System             | Parameters                                | Unit    | Value           |
+|--------------------|-------------------------------------------|---------|-----------------|
+|                    | Number of generated satellites per system | -       | See Table 5.4-2 |
+|                    | Total number of generated satellites      | -       | 6               |
+|                    | HDOP range                                |         | 1.4 to 2.1      |
+|                    | Propagation conditions                    | -       | AWGN            |
+|                    | GANSS coarse time assistance error range  | seconds | ±2              |
+| Galileo            | Reference signal power level              | dBm     | -127            |
+| GPS <sup>(1)</sup> | Reference signal power level              | dBm     | -128.5          |
+| GLONASS            | Reference signal power level              | dBm     | -131            |
+| BDS                | Reference signal power level              | dBm     | -133            |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+Table 5.4-2: Channel model allocation
+
+|                      |                 | Channel model allocation for each constellation |        |        |
+|----------------------|-----------------|-------------------------------------------------|--------|--------|
+|                      |                 | GNSS-1                                          | GNSS-2 | GNSS-3 |
+| Single constellation | One-tap channel | 2                                               | --     | --     |
+|                      | Two-tap channel | 4                                               | --     | --     |
+| Dual constellation   | One-tap channel | 1                                               | 1      | --     |
+|                      | Two-tap channel | 2                                               | 2      | --     |
+| Triple constellation | One-tap channel | 1                                               | 1      | 1      |
+|                      | Two-tap channel | 1                                               | 1      | 1      |
+
+### 5.4.1 Minimum requirements (multi-path scenario)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.4.1-1.
+
+Table 5.4.1-1: Minimum requirements
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.5 Moving scenario and periodic update
+
+The purpose of the test case is to verify the receiver's capability to produce GANSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GANSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test.
+
+In this requirement 6 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds.
+
+The UE moves on a rectangular trajectory of 940 m by 1440 m with rounded corner defined in figure 5.5-1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle.
+
+Table 5.5-1: Trajectory Parameters
+
+| Parameter                        | Distance (m) | Speed (km/h)            |
+|----------------------------------|--------------|-------------------------|
+| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20           | 25                      |
+| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250          | 25 to 100 and 100 to 25 |
+| $l_{13}$                         | 400          | 100                     |
+| $l_{23}$                         | 900          | 100                     |
+
+![Diagram of a rectangular trajectory. The rectangle has a width of 1 440 m and a height of 940 m. The bottom-left corner is labeled with a radius r = 20 m. The top-left corner is marked with l15 and l14. The bottom-left corner is marked with l12 and l11. The bottom edge is marked with l21, l22, l23, l24, and l25. Arrows indicate the clockwise direction of the trajectory.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg)
+
+Diagram of a rectangular trajectory. The rectangle has a width of 1 440 m and a height of 940 m. The bottom-left corner is labeled with a radius r = 20 m. The top-left corner is marked with l15 and l14. The bottom-left corner is marked with l12 and l11. The bottom edge is marked with l21, l22, l23, l24, and l25. Arrows indicate the clockwise direction of the trajectory.
+
+Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case
+
+Table 5.5-2: Test Parameters
+
+| System             | Parameters                                      | Unit    | Value           |
+|--------------------|-------------------------------------------------|---------|-----------------|
+|                    | Number of generated satellites per system       | -       | See Table 5.5-3 |
+|                    | Total number of generated satellites            | -       | 6               |
+|                    | HDOP Range per system                           | -       | 1.4 to 2.1      |
+|                    | Propagation conditions                          | -       | AWGN            |
+|                    | GANSS coarse time assistance error range        | seconds | $\pm 2$         |
+| Galileo            | Reference signal power level for all satellites | dBm     | -127            |
+| GPS <sup>(1)</sup> | Reference signal power level for all satellites | dBm     | -128.5          |
+| GLONASS            | Reference signal power level for all satellites | dBm     | -131            |
+| BDS                | Reference signal power level for all satellites | dBm     | -133            |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+Table 5.5-3: Satellite allocation
+
+|                      | Satellite allocation for each constellation |                       |                       |
+|----------------------|---------------------------------------------|-----------------------|-----------------------|
+|                      | GNSS 1 <sup>(1)</sup>                       | GNSS 2 <sup>(1)</sup> | GNSS 3 <sup>(1)</sup> |
+| Single constellation | 6                                           | --                    | --                    |
+| Dual constellation   | 3                                           | 3                     | --                    |
+| Triple constellation | 2                                           | 2                     | 2                     |
+
+Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.
+
+### 5.5.1 Minimum requirements (moving scenario and periodic update)
+
+The position estimates shall meet the accuracy requirement of table 5.5.1-1 with the periodical reporting interval defined in table 5.5.1-1 after the first reported position estimates.
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS/GNSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 5.5.1-1.
+
+**Table 5.5.1-1: Minimum requirements**
+
+| <b>System</b> | <b>Success rate</b> | <b>2-D position error</b> | <b>Periodical reporting interval</b> |
+|---------------|---------------------|---------------------------|--------------------------------------|
+| All           | 95 %                | 50 m                      | 2 s                                  |
+
+# --- Annex A (normative): Test cases
+
+## A.1 Conformance tests
+
+The conformance tests are specified in 3GPP TS 34.172 [12]. Statistical interpretation of the requirements is described in clause A.2.
+
+## --- A.2 Requirement classification for statistical testing
+
+Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested.
+
+Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for.
+
+When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in 3GPP TS 34.172 [12].
+
+# Annex B (normative): Test conditions
+
+## B.1 General
+
+This annex specifies the additional parameters that are needed for the test cases specified in clause 5 and applies to all tests unless otherwise stated.
+
+### B.1.1 Parameter values
+
+Additionally, amongst all the listed parameters (see Annex E), the following values for some important parameters are to be used in the measurement control message.
+
+**Table B.1.1-1: Parameter values**
+
+| Information element                                 | Value - TTFF tests (except nominal accuracy test) | Value - TTFF tests (nominal accuracy test) | Value - Periodic tests |
+|-----------------------------------------------------|---------------------------------------------------|--------------------------------------------|------------------------|
+| Measurement Reporting Mode                          | Periodical reporting                              | Periodical reporting                       | Periodical reporting   |
+| Amount of reporting                                 | 1                                                 | 1                                          | Infinite (see Note)    |
+| Reporting interval                                  | 20 000 ms                                         | 20 000 ms                                  | 2 000 ms               |
+| Horizontal accuracy                                 | 51.2 m                                            | 7.7 m                                      | 24.5 m                 |
+| Vertical accuracy                                   | 102 m                                             | 102 m                                      | 102 m                  |
+| Note: Infinite means during the complete test time. |                                                   |                                            |                        |
+
+In the Sensitivity test case with Fine Time Assistance, the following parameter values are used.
+
+**Table B.1.1-2: Parameters for fine time assistance test**
+
+| Information element                           | Value   |
+|-----------------------------------------------|---------|
+| TUTRAN-GPS drift rate                         | 0       |
+| TUTRAN-GNSS drift rate                        | 0       |
+| UE Positioning GPS Reference Time Uncertainty | 10.2 µs |
+| GNSS TOD Uncertainty                          | 10.2 µs |
+
+### B.1.2 Time assistance
+
+For every Test Instance in each TTFF test case, the GNSS/GPS Reference Time shall have a random offset, relative to GNSS/GPS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+In addition, for every Fine Time Assistance Test Instance the IE UTRAN GPS/GNSS timing of cell frames shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+For the Moving Scenario and Periodic Update Test Case the GNSS/GPS Reference Time shall be set to the nominal value.
+
+### B.1.3 GNSS reference time
+
+For every Test Instance in each TTFF test case, the GNSS reference time (and GPS reference time, if applicable) shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix.
+
+### B.1.4 Reference and UE locations
+
+There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km. The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %.
+
+For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions.
+
+For test cases which include satellites from regional systems, such as QZSS and SBAS, the reference location shall be selected within the defined coverage area of the systems.
+
+### B.1.5 Satellite constellation and assistance data
+
+The satellite constellation shall consist of 24 satellites for GLONASS; 27 satellites for GPS, Modernized GPS and Galileo; 3 satellites for QZSS; 2 satellites for SBAS and 35 satellites for BDS (5 GEO, 27 MEO, 3 IGSO). Almanac assistance data shall be available for all these satellites. At least 7 of the satellites per GPS, Modernized GPS, Galileo, GLONASS and BDS constellation shall be visible to the UE (that is, above 15 degrees elevation with respect to the UE). At least 1 of the satellites for QZSS shall be within 15 degrees of zenith; and at least 1 of the satellites for SBAS shall be visible to the UE. For BDS with reference location in Asia, at least 1 of the visible satellites shall be a GEO (above 15 degrees elevation with respect to the UE). All other satellite specific assistance data shall be available for all visible satellites. In each test, signals are generated for only 6 satellites (or 7 if SBAS is included). The HDOP for the test shall be calculated using these satellites. The simulated satellites for GPS, Modernized GPS, Galileo, GLONASS and BDS shall be selected from the visible satellites for each constellation consistent with achieving the required HDOP for the test. For BDS with reference location in Asia, 1 of the simulated satellites shall be a GEO.
+
+NOTE: Currently up to 30 BDS satellites (maximum 22 MEO) can be supported.
+
+### B.1.6 Atmospheric delay
+
+Typical Ionospheric and Tropospheric delays shall be simulated and the corresponding values inserted into the Ionospheric Model IEs.
+
+### B.1.7 Sensors
+
+The minimum performance requirements shall be met without the use of any data coming from sensors that can aid the positioning.
+
+### B.1.8 Information elements
+
+The information elements that are available to the UE in all the test cases are listed in Annex E.
+
+### B.1.9 GNSS signals
+
+The GNSS signal is defined at the A-GNSS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
+
+### B.1.10 RESET UE POSITIONING STORED INFORMATION Message
+
+In order to ensure each Test Instance in each TTFF test is performed under Time to First Fix (TTFF) conditions, a dedicated test signal (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 34.109 [13] clause 5.4 shall be used.
+
+When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' signal, with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS* it shall:
+
+- discard any internally stored GPS and GANSS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler);
+- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition;
+- calculate the position or perform GNSS measurements using the 'new' reference time or reference location or other information.
+
+### B.1.11 GNSS system time offsets
+
+If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than 3 ns.
+
+# Annex C (normative): Propagation conditions
+
+## C.1 Static propagation conditions
+
+The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model.
+
+## C.2 Multi-path case
+
+Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GANSS signals are defined in table C.2-1.
+
+**Table C.2-1: Multipath case**
+
+| Initial Relative Delay [m] | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean Power [dB] |
+|----------------------------|---------------------------------------|------------------------------------|--------------------------|
+| 0                          | Fd                                    | Fd / N                             | 0                        |
+| X                          | Fd-0.1                                | (Fd-0.1) / N                       | Y                        |
+
+Note: Discrete Doppler frequency is used for each tap.
+
+Where the X and Y depends on the GNSS signal type and is shown in table C.2-2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in table C.2-3 (where k in table C.2-3 is the GLONASS frequency channel number).
+
+**Table C.2-2: Relative Delay and Attenuation of Non Line of Sight Signals**
+
+| System             | Signals | X [m] | Y [dB] |
+|--------------------|---------|-------|--------|
+| Galileo            | E1      | 125   | -4.5   |
+|                    | E5a     | 15    | -6     |
+|                    | E5b     | 15    | -6     |
+| GPS/Modernized GPS | L1 C/A  | 150   | -6     |
+|                    | L1C     | 125   | -4.5   |
+|                    | L2C     | 150   | -6     |
+|                    | L5      | 15    | -6     |
+| GLONASS            | G1      | 275   | -12.5  |
+|                    | G2      | 275   | -12.5  |
+| BDS                | B1I     | 75    | -4.5   |
+
+**Table C.2-3: Ratio between the transmitted carrier frequency of the signals and the transmitted chip rate**
+
+| System             | Signals | N                        |
+|--------------------|---------|--------------------------|
+| Galileo            | E1      | 1540                     |
+|                    | E5a     | 115                      |
+|                    | E5b     | 118                      |
+| GPS/Modernized GPS | L1 C/A  | 1540                     |
+|                    | L1C     | 1540                     |
+|                    | L2C     | 1200                     |
+|                    | L5      | 115                      |
+| GLONASS            | G1      | $3135.03 + k \cdot 1.10$ |
+|                    | G2      | $2438.36 + k \cdot 0.86$ |
+| BDS                | B1I     | 763                      |
+
+The initial carrier phase difference between taps shall be randomly selected between 0 and  $2\pi$ . The initial value shall have uniform random distribution.
+
+# Annex D (normative): Measurement sequence chart
+
+## D.1 General
+
+The measurement Sequence Charts that are required in all the test cases, are defined in this clause.
+
+## D.2 TTFF measurement sequence chart
+
+The measurement sequence chart for the TTFF test cases, for both UE-assisted and UE-based GANSS, is defined in this subclause.
+
+![Sequence diagram showing the measurement sequence for TTFF test cases between a System Simulator (SS) and a User Equipment (UE).](19a5f0db57a21a0e82a7f326083e96fd_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SS
+    participant UE
+    Note left of SS: (a)
+    SS->>UE: Reset UE Positioning Stored Information
+    Note left of SS: (b)
+    SS->>UE: RRC Measurement Control (Setup)
+    Note left of SS: (c)
+    UE-->>SS: RRC Measurement Report (Assistance Data Request)
+    Note left of SS: (d)
+    SS->>UE: RRC Measurement Control (Modify)
+    Note left of SS: (e)
+    SS-->>UE: RRC Measurement Control (Modify)
+    Note left of SS: (f)
+    UE-->>SS: RRC Measurement Report
+  
+```
+
+Sequence diagram showing the measurement sequence for TTFF test cases between a System Simulator (SS) and a User Equipment (UE).
+
+Figure D.2-1: Measurement Sequence Chart for the TTFF Test Cases
+
+- (a) The system simulator sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*.
+- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements:
+
+|                                          |                                                                        |
+|------------------------------------------|------------------------------------------------------------------------|
+| <i>MEASUREMENT COMMAND</i>               | Setup                                                                  |
+| <i>CHOICE MEASUREMENT TYPE</i>           | UE positioning measurement                                             |
+| <i>UE POSITIONING REPORTING QUANTITY</i> |                                                                        |
+| >Method Type                             | set to either 'UE assisted' or 'UE based', dependent on the test case; |
+| >Positioning Methods                     | set to 'GPS';                                                          |
+| >Horizontal Accuracy                     | as defined in Annex B;                                                 |
+| >Vertical Accuracy                       | as defined in Annex B;                                                 |
+| >Additional Assistance Data Request      | TRUE                                                                   |
+| >GANSS Positioning Methods               | set according to the UE capabilities and test case;                    |
+| <i>MEASUREMENT VALIDITY</i>              |                                                                        |
+| >UE state                                | All states                                                             |
+| <i>CHOICE REPORTING CRITERIA</i>         | Periodical reporting criteria                                          |
+
+>Amount of reporting 1 (see Annex B);  
+>Reporting interval 20 seconds (see Annex B);
+
+- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GANSS assistance data.
+- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b).
+- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GANSS MEASURED RESULTS* present in case of UE-assisted GANSS.
+
+Steps (a) to (f) are repeated for each test instance.
+
+## D.3 Periodic update measurement sequence chart
+
+The measurement sequence chart for the Moving Scenario and Periodic Update test case, for both UE-assisted and UE-based GANSS, is defined in this subclause.
+
+![Sequence diagram showing the measurement sequence for the Moving Scenario and Periodic Update Test Case between a System Simulator (SS) and a User Equipment (UE).](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SS
+    participant UE
+    Note left of SS: (a)
+    SS->>UE: Reset UE Positioning Stored Information
+    Note left of SS: (b)
+    SS->>UE: RRC Measurement Control (Setup)
+    Note left of SS: (c)
+    UE-->>SS: RRC Measurement Report (Assistance Data Request)
+    Note left of SS: (d)
+    SS->>UE: RRC Measurement Control (Modify)
+    Note left of SS: (e)
+    SS-->>UE: RRC Measurement Control (Modify)
+    Note left of SS: (f)
+    UE-->>SS: RRC Measurement Report
+    Note left of SS: (g)
+    UE-->>SS: RRC Measurement Report
+    Note left of SS: (h)
+    UE-->>SS: RRC Measurement Report
+    Note left of SS: ...
+    Note left of SS: (i)
+    UE-->>SS: RRC Measurement Report
+  
+```
+
+Sequence diagram showing the measurement sequence for the Moving Scenario and Periodic Update Test Case between a System Simulator (SS) and a User Equipment (UE).
+
+Figure D.3-1: Measurement Sequence Chart for the Moving Scenario and Periodic Update Test Case
+
+- (a) The system simulator sends a RESET *UE POSITIONING STORED INFORMATION* message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*.
+
+- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements:
+
+|                                          |                                                                        |
+|------------------------------------------|------------------------------------------------------------------------|
+| <i>MEASUREMENT COMMAND</i>               | Setup                                                                  |
+| <i>CHOICE MEASUREMENT TYPE</i>           | UE positioning measurement                                             |
+| <i>UE POSITIONING REPORTING QUANTITY</i> |                                                                        |
+| >Method Type                             | set to either 'UE assisted' or 'UE based', dependent on the test case; |
+| >Positioning Methods                     | set to 'GPS';                                                          |
+| >Horizontal Accuracy                     | as defined in Annex B;                                                 |
+| >Vertical Accuracy                       | as defined in Annex B;                                                 |
+| >Additional Assistance Data Request      | TRUE                                                                   |
+| >GNSS Positioning Methods                | set according to the UE capabilities and test case;                    |
+| <i>MEASUREMENT VALIDITY</i>              |                                                                        |
+| >UE state                                | All states                                                             |
+| <i>CHOICE REPORTING CRITERIA</i>         | Periodical reporting criteria                                          |
+| >Amount of reporting                     | infinite (see Annex B);                                                |
+| >Reporting interval                      | 2 seconds (see Annex B);                                               |
+
+- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GNSS assistance data.
+- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with *MEASUREMENT COMMAND* IE set to 'modify' and the *CHOICE REPORTING CRITERIA* set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the *CHOICE REPORTING CRITERIA* set to 'Periodical reporting criteria' as defined in step (b).
+- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GNSS MEASURED RESULTS* present in case of UE-assisted GNSS.
+- (g) – (i) The UE continues to provide RRC MEASUREMENT REPORT messages as in step (g) until the moving trajectory has been completed.
+
+NOTE: The UE may report error messages at step (f) until it has been able to acquire GNSS signals.
+
+# Annex E (normative): Assistance data required for testing
+
+## E.1 Introduction
+
+This annex defines the assistance data IEs available at the SS in all test cases. The assistance data shall be given for satellites as defined in B.1.5.
+
+The information elements are given with reference to 3GPP TS 25.331 [14], where the details are defined.
+
+## E.2 GPS assistance data
+
+The GPS L1 C/A assistance data are as defined in 3GPP TS 25.171 [10], Annex E.
+
+## E.3 GANSS assistance data
+
+- a) **UE Positioning GANSS Reference Time IE.** This information element is defined in subclause 10.3.7.96o of 3GPP TS 25.331 [14].
+
+**Table E.3-1: GANSS reference time IE**
+
+| Name of the IE                      | Fields of the IE                   | All tests except Sensitivity Fine Time Assistance | Sensitivity Fine Time Assistance test |
+|-------------------------------------|------------------------------------|---------------------------------------------------|---------------------------------------|
+| UE Positioning GANSS Reference Time |                                    |                                                   |                                       |
+|                                     | GANSS Day                          | Yes                                               | Yes                                   |
+|                                     | GANSS TOD                          | Yes                                               | Yes                                   |
+|                                     | GANSS TOD Uncertainty              | Yes                                               | Yes                                   |
+|                                     | GANSS Time ID                      | Yes                                               | Yes                                   |
+|                                     | UTRAN GANSS Reference Time         |                                                   |                                       |
+|                                     | >UTRAN GANSS Timing of Cell Frames |                                                   | Yes                                   |
+|                                     | >CHOICE mode                       |                                                   | Yes                                   |
+|                                     | >>FDD                              |                                                   | Yes                                   |
+|                                     | >>>Primary CPICH Info              |                                                   | Yes                                   |
+|                                     | >SFN                               |                                                   | Yes                                   |
+|                                     | TUTRAN-GANSS Drift Rate            |                                                   | Yes                                   |
+
+- b) **UE Positioning GANSS Reference UE Position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [14].
+
+**Table E.3-2: GANSS reference location IE**
+
+| Name of the IE                             | Fields of the IE                                        |
+|--------------------------------------------|---------------------------------------------------------|
+| UE Positioning GANSS Reference UE Position | Ellipsoid point with Altitude and uncertainty ellipsoid |
+
+- c) **UE Positioning GANSS Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92a of 3GPP TS 25.331 [14].
+
+**Table E.3-3: GANSS ionospheric model IE**
+
+| Name of the IE                         | Fields of the IE |
+|----------------------------------------|------------------|
+| UE Positioning GANSS Ionospheric Model |                  |
+
+- d) **UE Positioning GANSS Additional Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92b of 3GPP TS 25.331 [14].
+
+**Table E.3-4: GANSS additional ionospheric model IE**
+
+| Name of the IE                                    | Fields of the IE |
+|---------------------------------------------------|------------------|
+| UE Positioning GANSS Additional Ionospheric Model |                  |
+
+- e) **UE Positioning GANSS Time Model IE.** This information element is only required for multi system tests, and is defined in subclause 10.3.7.97a of 3GPP TS 25.331 [14].
+
+**Table E.3-5: GANSS time model IE**
+
+| Name of the IE                  | Fields of the IE                                   |
+|---------------------------------|----------------------------------------------------|
+| UE Positioning GANSS Time Model |                                                    |
+|                                 | GNSS_TOD_ID<br>For each GNSS included in the test. |
+
+- f) **UE Positioning GANSS Navigation Model IE.** This information element is defined in subclause 10.3.7.94a of 3GPP TS 25.331 [14].
+
+**Table E.3-6: GANSS navigation model IE**
+
+| Name of the IE                        | Fields of the IE |
+|---------------------------------------|------------------|
+| UE Positioning GANSS Navigation Model |                  |
+
+- g) **UE Positioning GANSS Additional Navigation Models IE.** This information element is defined in subclause 10.3.7.94b of 3GPP TS 25.331 [14].
+
+**Table E.3-7: GANSS navigation model IE**
+
+| Name of the IE                        | Fields of the IE |
+|---------------------------------------|------------------|
+| UE Positioning GANSS Navigation Model |                  |
+
+**Table E.3-8: GANSS clock and orbit model choices**
+
+| GANSS               | Clock and Orbit Model Choice |
+|---------------------|------------------------------|
+| Galileo             | Model-1                      |
+| Modernized GPS      | Model-3                      |
+| GLONASS             | Model-4                      |
+| QZSS QZS-L1         | Model-2                      |
+| QZSS QZS-L1C/L2C/L5 | Model-3                      |
+| SBAS                | Model-5                      |
+| BDS                 | Model-6                      |
+
+- h) **UE Positioning GANSS Reference Measurement Information IE.** This information element is defined in subclause 10.3.7.88b of 3GPP TS 25.331 [14].
+
+**Table E.3-9: GANSS reference measurement information IE**
+
+| Name of the IE                                         | Fields of the IE                     |
+|--------------------------------------------------------|--------------------------------------|
+| UE Positioning GANSS Reference Measurement Information |                                      |
+|                                                        | SatID                                |
+|                                                        | Doppler (0 <sup>th</sup> order term) |
+|                                                        | Doppler (1 <sup>st</sup> order term) |
+|                                                        | Doppler Uncertainty                  |
+|                                                        | Code Phase                           |
+|                                                        | Integer Code Phase                   |
+|                                                        | Code Phase Search Window             |
+|                                                        | Azimuth                              |
+|                                                        | Elevation                            |
+
+- i) **UE Positioning GANSS Almanac IE.** This information element is defined in subclause 10.3.7.89a of 3GPP TS 25.331 [14].
+
+**Table E.3-10: GANSS almanac model IE**
+
+| Name of the IE               | Fields of the IE |
+|------------------------------|------------------|
+| UE Positioning GANSS Almanac |                  |
+
+**Table E.3-11: GANSS almanac choices**
+
+| GANSS               | Almanac Model Choice |
+|---------------------|----------------------|
+| Galileo             | Model-1              |
+| Modernized GPS      | Model-3,4            |
+| GLONASS             | Model-5              |
+| QZSS QZS-L1         | Model-2              |
+| QZSS QZS-L1C/L2C/L5 | Model-3,4            |
+| SBAS                | Model-6              |
+| BDS                 | Model-7              |
+
+- j) **UE Positioning GANSS UTC Model IE.** This information element is defined in subclause 10.3.7.97c of 3GPP TS 25.331 [14].
+
+**Table E.3-12: GANSS UTC model IE**
+
+| Name of the IE                 | Fields of the IE |
+|--------------------------------|------------------|
+| UE Positioning GANSS UTC Model |                  |
+
+- k) **UE Positioning GANSS Additional UTC Models IE.** This information element is defined in subclause 10.3.7.97d of 3GPP TS 25.331 [14].
+
+**Table E.3-13: GANSS additional UTC model IE**
+
+| Name of the IE                                | Fields of the IE |
+|-----------------------------------------------|------------------|
+| UE Positioning GANSS Additional UTC Models IE |                  |
+
+**Table E.3-14: GANSS UTC model choices**
+
+| <b>GANSS</b>        | <b>UTC Model Choice</b>        |
+|---------------------|--------------------------------|
+| Galileo             | UE Positioning GANSS UTC Model |
+| Modernized GPS      | Model-1                        |
+| GLONASS             | Model-2                        |
+| QZSS QZS-L1         | UE Positioning GANSS UTC Model |
+| QZSS QZS-L1C/L2C/L5 | Model-1                        |
+| SBAS                | Model-3                        |
+| BDS                 | Model-4                        |
+
+- I) **UE Positioning GANSS Auxiliary Information IE.** This information element is defined in subclause 10.3.7.97f of 3GPP TS 25.331 [14].
+
+**Table E.3-15: GANSS auxiliary information IE**
+
+| <b>Name of the IE</b>                         | <b>Fields of the IE</b> |
+|-----------------------------------------------|-------------------------|
+| UE Positioning GANSS Auxiliary Information IE |                         |
+
+# --- Annex F (normative): Converting UE-assisted measurement reports into position estimates
+
+## F.1 Introduction
+
+To convert the UE measurement reports in case of UE-assisted mode of A-GNSS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [3], [4], [5], [6], [7], [8], [9], [16] and [17].
+
+## --- F.2 UE measurement reports
+
+In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE (subclause 10.3.7.93a in 3GPP TS 25.331 [14]). In case the UE provides also measurements on the GPS L1 C/A signal, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE (subclause 10.3.7.93 in 3GPP TS 25.331 [14]). The measurement parameters required for calculating the UE position are:
+
+- 1) Reference Time: The UE has two choices for the Reference Time:
+  - a) "UE GANSS Timing of Cell Frames" and/or "UE GPS Timing of Cell Frames";
+  - b) "GANSS TOD msec" and/or "GPS TOW msec" if GPS L1 C/A signal measurements are also provided.
+
+NOTE: It is not expected that an UE will ever report both a GANSS TOD and a GPS TOW. However if two time stamps are provided and they derive from different user times, be aware that no compensation is made for this difference and this could affect the location accuracy.
+
+- 2) Measurement Parameters for each GANSS and GANSS Signal: 1 to <maxGANSSSat>:
+  - a) "Satellite ID"; mapping according to table 10.3.7.88b in 3GPP TS 25.331 [14];
+  - b) "GANSS Code Phase";
+  - c) "GANSS Integer Code Phase";
+  - d) "GANSS Integer Code Phase Extension";
+  - e) "Code Phase RMS Error";
+- 3) Additional Measurement Parameters in case of GPS L1 C/A signal measurements are also provided: 1 to <maxSat>:
+  - a) "Satellite ID (SV PRN)";
+  - b) "Whole GPS chips";
+  - c) "Fractional GPS Chips";
+  - d) "Pseudorange RMS Error".
+
+Additional information required at the system simulator:
+
+- 1) "UE Positioning GANSS Reference UE Position" or "UE Positioning GPS Reference UE Position" (subclause 10.3.8.4c in 3GPP TS 25.331 [14]):  
+Used for initial approximate receiver coordinates.
+
+- 2) "UE Positioning GANSS Navigation Model" and "UE Positioning GANSS Additional Navigation Models" (subclauses 10.3.7.94a and 10.3.7.94b in 3GPP TS 25.331 [14]):  
+Contains the ephemeris and clock correction parameters as specified in the relevant ICD of each supported GANSS; used for calculating the satellite positions and clock corrections.
+- 3) "UE Positioning GANSS Ionospheric Model" (subclause 10.3.7.92a in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [7] for computation of the ionospheric delay.
+- 4) "UE Positioning GANSS Additional Ionospheric Model" (subclause 10.3.7.92b in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [6] for computation of the ionospheric delay.
+- 5) "UE Positioning GANSS Time Model" (subclause 10.3.7.97a in 3GPP TS 25.331 [14]):  
+Contains the GNSS-GNSS Time Offset for each supported GANSS. Note, that "UE Positioning GANSS Time Model" IE contains only the sub-ms part of the offset. Any potential integer seconds offset may be obtained from "UE Positioning GPS UTC Model" (subclause 10.3.7.97 in 3GPP TS 25.331 [14]), "UE Positioning GANSS UTC Model" (subclause 10.3.7.97c in 3GPP TS 25.331 [14]), or "UE Positioning GANSS Additional UTC Models" (subclause 10.3.7.97d in 3GPP TS 25.331 [14]).
+- 6) "UE Positioning GPS Navigation Model" (subclause 10.3.7.94 in 3GPP TS 25.331 [14]):  
+Contains the GPS ephemeris and clock correction parameters as specified in [3]; used for calculating the GPS satellite positions and clock corrections in case of GPS L1 C/A signal measurements are the only GPS measurements provided in addition to GANSS measurements.
+- 7) "UE Positioning GPS Ionospheric Model" (subclause 10.3.7.92 in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [3] for computation of the ionospheric delay.
+
+## F.3 Weighted Least Squares (WLS) position solution
+
+The WLS position solution problem is concerned with the task of solving for four unknowns;  $x_u, y_u, z_u$  the receiver coordinates in a suitable frame of reference (usually ECEF) and  $b_u$  the receiver clock bias relative to the selected GNSS specific system time. It typically requires the following steps:
+
+### Step 1: Formation of pseudo-ranges
+
+The observation of code phase reported by the UE for each satellite  $SV_i$  is related to the pseudo-range/ $c$  modulo the "GANSS Code Phase Ambiguity", or modulo 1 ms (the length of the C/A code period) in case of GPS L1 C/A signal measurements. For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite  $SV_i$  at the time of measurement is calculated, and the integer number of milliseconds to be added to the UE code phase measurements is obtained.
+
+### Step 2: Correction of pseudo-ranges for the GNSS-GNSS time offsets
+
+In case the UE reports measurements for more than a single GNSS, the pseudo-ranges are corrected for the time offsets between the GNSSs relative to the selected reference time using the GNSS-GNSS time offsets available at the system simulator:
+
+$$\rho_{GNSS_m,i} \equiv \rho_{GNSS_m,i} - c \cdot (t_{GNSS_k} - t_{GNSS_m}),$$
+
+where  $\rho_{GNSS_m,i}$  is the measured pseudo-range of satellite  $i$  of GNSS $_m$ . The system time  $t_{GNSS_k}$  of GNSS $_k$  is the reference time frame, and  $(t_{GNSS_k} - t_{GNSS_m})$  is the available GNSS-GNSS time offset, and  $c$  is the speed of light.
+
+### Step 3: Formation of weighting matrix
+
+The UE reported "Code Phase RMS Error" and/or "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm described in [16]. According to 3GPP TS 25.331 [14], the encoding for these fields is a 6 bit value that consists of a 3 bit mantissa,  $X_i$  and a 3 bit exponent,  $Y_i$  for each  $SV_i$  of GNSS $_j$ :
+
+$$w_{GNSS_j,i} = RMSError = 0.5 \times \left( 1 + \frac{X_i}{8} \right) \times 2^{Y_i}$$
+
+The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "Code Phase RMS Error" and/or "Pseudorange RMS Error" values:
+
+$$\mathbf{W} = \text{diag} \left\{ 1/w_{GNSS_1,1}^2, 1/w_{GNSS_1,2}^2, \dots, 1/w_{GNSS_1,n}^2, \dots, 1/w_{GNSS_m,1}^2, 1/w_{GNSS_m,2}^2, \dots, 1/w_{GNSS_m,l}^2 \right\}$$
+
+### Step 4: WLS position solution
+
+The WLS position solution is described in e.g., [16] and usually requires the following steps:
+
+- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in the relevant ICD of the particular GNSS. The satellite locations are transformed into WGS-84 reference frame, if needed.
+- 2) Computation of clock correction parameters using the parameters and algorithms as defined in the relevant ICD of the particular GNSS.
+- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in the relevant ICD of the particular GNSS for the ionospheric delay, and using the Gupta model defined in [17] p. 121 equation (2) for the tropospheric delay. For GNSSs which do not natively provide ionospheric correction models (e.g., GLONASS), the ionospheric delay is determined using the available ionospheric model (see subclause F.2) adapted to the particular GNSS frequency.
+- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required:
+  - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report.
+  - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in the relevant ICD of the particular GNSS and [16].
+  - c) Calculate difference between predicted and measured pseudo-ranges  $\Delta \rho$ .
+  - d) Calculate the "Geometry Matrix" **G** as defined in [16]:
+
+$$\mathbf{G} \equiv \begin{bmatrix} -\hat{\mathbf{i}}_{GNSS_1,1}^T & 1 \\ -\hat{\mathbf{i}}_{GNSS_1,2}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{GNSS_1,n}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{GNSS_m,1}^T & 1 \\ -\hat{\mathbf{i}}_{GNSS_m,2}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{GNSS_m,l}^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{i}}_{GNSS_m,i} \equiv \frac{\mathbf{r}_{s_{GNSS_m,i}} - \hat{\mathbf{r}}_u}{\left| \mathbf{r}_{s_{GNSS_m,i}} - \hat{\mathbf{r}}_u \right|} \text{ where } \mathbf{r}_{s_{GNSS_m,i}} \text{ is the satellite position vector for } SV_i$$
+
+of GNSS $_m$  (calculated in 1) above), and  $\hat{\mathbf{r}}_u$  is the estimate of the user location.
+
+- e) Calculate the WLS solution according to [16]:
+
+$$\Delta \hat{\mathbf{x}} = \left( \mathbf{G}^T \mathbf{W} \mathbf{G} \right)^{-1} \mathbf{G}^T \mathbf{W} \Delta \rho$$
+
+- f) Adding the  $\Delta\hat{x}$  to the initial state estimate gives an improved estimate of the state vector:
+
+$$\hat{x} \rightarrow \hat{x} + \Delta\hat{x}.$$
+
+- 5) This new state vector  $\hat{x}$  can be used as new initial estimate and the procedure is repeated until the change in  $\hat{x}$  is sufficiently small.
+
+### Step 5: Transformation from Cartesian coordinate system to Geodetic coordinate system
+
+The state vector  $\hat{x}$  calculated in Step 4 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias relative to the selected GNSS system time. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates  $x_u, y_u, z_u$  to geodetic latitude  $\phi$ , longitude  $\lambda$  and altitude  $h$  on the WGS84 reference ellipsoid.
+
+### Step 6: Calculation of "2-D Position Errors"
+
+The latitude  $\phi$  / longitude  $\lambda$  obtained after Step 5 is used to calculate the 2-D position error.
+
+# Annex G (informative): Change history
+
+| Date    | Meeting | Document  | CR num | Rev | Comment                                                                                         | Version old | Version New |
+|---------|---------|-----------|--------|-----|-------------------------------------------------------------------------------------------------|-------------|-------------|
+| 2010-02 | RAN4#54 | R4-100668 |        |     | Text proposal for A-GANSS minimum performance requirements in UTRAN                             |             | 0.0.1       |
+| 2010-03 | RAN#47  | RP-100133 |        |     | TS presented for information                                                                    | 0.0.1       | 1.0.0       |
+| 2010-05 | RAN4#55 | R4-101671 |        |     | Minor editorial corrections and alignments with GERAN                                           | 1.0.0       | 2.0.0       |
+| 2010-05 | RAN4#55 | R4-101671 |        |     | Approved by TSG RAN                                                                             | 2.0.0       | 10.0.0      |
+| 2010-12 | RP-50   | RP-101350 | 001    | 1   | Addition of Galileo sensitivity numbers in the A-GANSS minimum performance requirements in UMTS | 10.0.0      | 10.1.0      |
+| 2011-04 | RP-51   | RP-110351 | 002    |     | Addition of missing values and references                                                       | 10.1.0      | 10.2.0      |
+| 2012-09 | SP-57   | -         | -      | -   | Update to Rel-11 version (MCC)                                                                  | 10.2.0      | 11.0.0      |
+| 2014-06 | RP-64   | RP-140924 | 004    | 2   | CR to TS 25.172 on introduction BDS to A-GANSS of FDD mode of UTRA                              | 11.0.0      | 12.0.0      |
+| 2014-12 | RP-66   | RP-142151 | 005    | -   | Correction on BDS satellites number                                                             | 12.0.0      | 12.1.0      |
+| 2016-01 | SP-70   | -         | -      | -   | Update to Rel-13 version (MCC)                                                                  | 12.1.0      | 13.0.0      |
+| 2017-03 | RP-75   | -         | -      | -   | Update to Rel-14 version (MCC)                                                                  | 13.0.0      | 14.0.0      |
+
+| Change history |         |      |    |     |     |                                |             |
+|----------------|---------|------|----|-----|-----|--------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version |
+| 2018-06        | SA#80   | -    | -  | -   | -   | Update to Rel-15 version (MCC) | 15.0.0      |
+| 2020-06        | SA#88   | -    | -  | -   | -   | Update to Rel-16 version (MCC) | 16.0.0      |
+| 2022-03        | SA#95   |      |    |     |     | Update to Rel-17 version (MCC) | 17.0.0      |
+| 2024-03        | RAN#103 |      |    |     |     | Update to Rel-18 version (MCC) | 18.0.0      |

marked/Rel-18/25_series/25300/raw.md

@@ -0,0 +1,612 @@
+
+
+# 3GPP TS 25.300 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; Universal Terrestrial Radio Access Network (UTRAN); General description; Stage 2 (Release 18)** ---
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo features the letters '3GPP' in a stylized, bold, black font. The '3' is a thick, rounded shape. The 'G' is a thick, rounded shape with a small red signal icon (three curved lines) at its bottom right. The two 'P's are thick, rounded shapes. A small 'TM' trademark symbol is located to the right of the final 'P'.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+## --- **Keywords**
+
+---
+
+UTRAN
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+|                                                                            |    |
+|----------------------------------------------------------------------------|----|
+| Foreword .....                                                             | 5  |
+| 1 Scope.....                                                               | 6  |
+| 2 References.....                                                          | 6  |
+| 3 Definitions, symbols and abbreviations .....                             | 7  |
+| 3.1 Definitions.....                                                       | 7  |
+| 3.2 Symbols.....                                                           | 7  |
+| 3.3 Abbreviations .....                                                    | 7  |
+| 4 Heterogeneous Networks Mobility Enhancements.....                        | 7  |
+| 5 Heterogeneous Networks Enhancements.....                                 | 7  |
+| 6 DCH Enhancements (FDD only) .....                                        | 8  |
+| 6.1 DL overhead optimization.....                                          | 8  |
+| 6.2 Enhanced rate matching and transport channel multiplexing .....        | 8  |
+| 6.3 DL frame early termination (DL FET) and UL DPCCH with DL FET ACK ..... | 9  |
+| 6.3.1 DL FET Full mode (Mode 1) .....                                      | 9  |
+| 6.3.2 DL FET Basic mode (Mode 0).....                                      | 9  |
+| 6.4 Uplink DPDCH dynamic 10ms transmission.....                            | 9  |
+| 7 Access Control in Connected Mode (CELL_FACH, CELL_PCH and URA_PCH) ..... | 10 |
+| 8 Access control enhancements .....                                        | 10 |
+| 8.1 DSAC and PPAC update for the UE in CELL_DCH state.....                 | 10 |
+| 9 Enhanced Broadcast of System Information.....                            | 10 |
+| 9.1 Second system information broadcast channel .....                      | 10 |
+| 9.2 Scheduling information overhead reduction .....                        | 12 |
+| 9.3 MIB and Cell Value Tag range extension.....                            | 12 |
+| 10 RAN assisted WLAN interworking .....                                    | 12 |
+| 10.1 General principles .....                                              | 12 |
+| 10.2 Access network selection and traffic steering rules .....             | 13 |
+| 11 Increased minimum number of carriers to monitor .....                   | 13 |
+| 12 Extended DRX in Idle mode.....                                          | 13 |
+| 13 L2 and L3 Downlink enhancements for UMTS.....                           | 14 |
+| 13.1 Retrievable configurations .....                                      | 14 |
+| 13.2 URA_PCH with seamless transition .....                                | 14 |
+| 13.3 Optimization from IDLE to CONNECTED state .....                       | 14 |
+| 13.4 Blind HARQ retransmissions for HSDPA .....                            | 15 |
+| 13.5 Enhanced state transition.....                                        | 15 |
+| 13.6 Improved synchronized RRC procedures .....                            | 15 |
+| 14 Downlink TPC enhancements for UMTS.....                                 | 15 |
+| 15 NAICS offloading (FDD only) .....                                       | 15 |
+| 16 ACDC in Idle Mode .....                                                 | 15 |
+| 17 RRC optimization .....                                                  | 16 |
+| 17.1 RRC measurement events for UPH reporting.....                         | 16 |
+| 17.2 Simultaneous Setup and Release of RABs and RBs.....                   | 16 |
+
+18 HS-SCCH DRX in CELL\_FACH state (FDD only) ..... 16
+
+19 Dual Cell E-DCH operation enhancements ..... 16
+
+20 QoE Measurement Collection..... 16
+
+21 DL Interference Mitigation (FDD only) ..... 17
+
+22 Simplified HS-SCCH type 1 operation..... 17
+
+23 NR SRVCC to UTRAN ..... 17
+
+**Annex A (informative): Change history..... 18**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# 1 Scope
+
+The present document provides an overview and overall description of the UTRA radio interface functionalities from Release 12 onwards which are not covered by the Technical Specifications TS 25.308 [2] or TS 25.319 [3].
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.308: "UTRA HSDPA: UTRAN Overall Description (Stage 2) ".
+- [3] 3GPP TS 25.319: "Enhanced Uplink: Overall description (Stage 2) ".
+- [4] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols - Stage 3".
+- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [6] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
+- [7] 3GPP TR 25.704: "Study on enhanced broadcast of system information".
+- [8] 3GPP TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)".
+- [9] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
+- [10] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
+- [11] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)".
+- [12] 3GPP TS 25.331: "Radio Resource Control (RRC)".
+- [13] 3GPP TR 25.993: "Typical examples of Radio Access Bearers (RABs) and Radio Bearers (RBs) supported by Universal Terrestrial Radio Access (UTRA)".
+- [14] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2".
+- [15] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
+- [16] 3GPP TS 38.300: "NR; Overall description; Stage 2".
+- [17] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Power saving mode:** Mode configured and controlled by NAS that allows the UE to reduce its power consumption, as defined in TS 24.008 [4], TS 23.060 [5], TS 23.682 [6].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+<symbol>            <Explanation>
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|        |                                                                |
+|--------|----------------------------------------------------------------|
+| ACDC   | Application specific Congestion control for Data Communication |
+| ANDSF  | Access Network Discovery and Selection Function                |
+| DPCCH2 | Dedicated Physical Control Channel 2                           |
+| NCL    | Neighbour Cell List                                            |
+| NR     | NR Radio Access                                                |
+| OPI    | Offload Preference Indicator                                   |
+| PSM    | Power Saving Mode                                              |
+| SRVCC  | Single Radio Voice Call Continuity                             |
+| QoE    | Quality of Experience                                          |
+| WLAN   | Wireless Local Area Network                                    |
+
+# 4 Heterogeneous Networks Mobility Enhancements
+
+Neighbour Cell List (NCL) extension
+
+- The size of the inter-frequency neighbour cell list is extended for CELL\_DCH, CELL\_FACH, CELL\_PCH, URA\_PCH states and Idle mode, so that network could configure more inter-frequency neighbour cells than 32 for UE to monitor and detect under massive small cell deployment scenario.
+
+Change of best cell on a configured secondary downlink frequency (event 2g)
+
+- Event 2g is an inter-frequency measurement event. It is applicable only to the secondary downlink frequency with configured HS-DSCH operation, and it can be configured on more than one secondary downlink frequency.
+
+Enhanced Serving Cell Change for Event 1C
+
+- The enhanced Serving Cell Change procedure could also be applied to Event 1C, which is defined in TS 25.308 [2].
+
+# 5 Heterogeneous Networks Enhancements
+
+Serving E-DCH cell decoupling
+
+- Serving E-DCH cell decoupling is introduced in order to improve the quality of reception of the uplink E-DCH control channels and the E-DCH SI in the presence of strong uplink/downlink imbalance. The UE is configured with different serving HS-DSCH cell and serving E-DCH cell.
+
+### Radio Links without DPCH/F-DPCH
+
+- The UE is configured with a subset of non-serving E-DCH radio links in the UE's E-DCH active set to operate in the absence of DPCH/F-DPCH. However, a UE is allowed to only receive either E-HICH or both E-HICH and E-RGCH from these non-serving E-DCH cells to mitigate uplink interference to a cell that is unable to power control a UE in the presence of strong uplink/downlink imbalance.
+
+### DPCCH2 transmission
+
+- In order to improve the quality of reception of the HS-DPCCH in the presence of strong uplink/imbalance, a new secondary uplink pilot channel (DPCCH2) is introduced in the serving HS-DSCH cell as the reference for the HS-DPCCH channel power.
+
+# --- 6 DCH Enhancements (FDD only)
+
+DCH enhancements aims at improving the link efficiency and UE battery performance for voice calls compared to R99 DCH. DCH enhancements constitutes of the following sub-features:
+
+- DL overhead optimization
+- Enhanced rate matching and transport channel multiplexing
+- DL Frame Early Termination (DL FET)
+- Uplink DPCCH with DL FET ACK
+- Uplink DPDCH dynamic 10ms transmission
+
+DCH enhancements supports two modes (Basic and Full). The mode choice controls how the DL Frame Early Termination sub-feature operates, as described in 6.3. All other sub-features are active in both modes.
+
+DCH enhancements is only applicable if the TTI of all DCH transport channels on both downlink and uplink is at least 20 ms.
+
+If a UE is configured with both CS and PS mapped to the DCH transport channel (in uplink or downlink or both), then DCH enhancements may be configured only when PS has UL:0 and DL:0kbps RAB configuration (3GPP TR 25.993 [13]).
+
+## 6.1 DL overhead optimization
+
+This sub-feature introduces new DL DPCH slot format by removing the dedicated pilot bits from DL DPCCH and reusing them for DL DPDCH instead.
+
+The R99 downlink physical channel (DPCH) consists of 0.66ms slots that contain 2 groups of data (DPDCH) symbols and 3 groups of control (DPCCH) symbols. The size of the groups is determined by the slot format. The control symbol groups are TPC - controlling uplink transmit power, TFCI - specifying the downlink packet type, and dedicated pilot - supporting channel estimation for DL power control and closed-loop transmit diversity. While the TFCI group may be empty in certain slot formats, the pilot and TPC are currently always non-empty. The dedicated pilot bits are used for estimation of DL SIR. With this sub-feature, new DL DPCH slot formats are introduced by removing the dedicated pilot bits and reusing the TPC bits instead for estimating the DL SIR. Correspondingly, the number of data symbols in a slot is increased leading to less control channel overhead on the downlink.
+
+DL closed-loop transmit diversity is not supported when this sub-feature is configured.
+
+## 6.2 Enhanced rate matching and transport channel multiplexing
+
+The physical layer in R99 is designed to carry potentially a large variety of transport blocks with different sizes. The drawback for this design is the rate matching may not be efficient when some transport format combinations are not
+
+frequently used. For example, DCCH channel carries non-zero transport blocks not as often as voice DTCH channel. The enhanced rate matching and transport channel multiplexing sub-feature sets a zero rate matching attribute for DCCH, whenever DCCH channel does not carry a transport block together with DTCH channel. The DCCH bit fields are used to transmit DTCH transport channels instead. This potentially improves link efficiency due to less puncturing and better rate matching of the transport block with the available physical channel resources.
+
+## 6.3 DL frame early termination (DL FET) and UL DPCCH with DL FET ACK
+
+In a power-controlled system such as R99 DCH, inefficiencies in the power-control loop, such as limited granularity, delays and errors in the feedback, result in the presence of excess SINR at the receiver. This means that packets such as the voice packets which have a long (20ms) transmission time interval (TTI) can often be early-decoded, i.e, decoded prior to reception of all the data symbols in a TTI by running the channel decoder at multiple time instants during the TTI instead of only once at the end of the TTI. This is referred to as Frame Early Termination (FET). As described below, DCH enhancements introduces new mechanisms to R99 DCH in order to support DL FET.
+
+A new design of UL DPCCH is introduced to support DL FET. With the new design, TFCI information is carried in the first 10 slots of each 20ms TTI for the uplink. Sending the TFCI information early in each 20ms TTI allows sending of DL FET ACK or NACK information using the TFCI bits in remaining UL DPCCH slots that do not carry TFCI.
+
+Furthermore, there are two modes of operation introduced with support for DL FET in DCH enhancements as described below.
+
+### 6.3.1 DL FET Full mode (Mode 1)
+
+In the Full mode of operation:
+
+- The UE acknowledges successful early decoding of a DL packet via a DL FET ACK on the newly designed UL DPCCH channel, which then allows the NodeB to stop transmission of the packet.
+- AMR Class A, B, C transport channels are concatenated on the DL which further helps in early decoding of DL DPDCH.
+
+### 6.3.2 DL FET Basic mode (Mode 0)
+
+In the Basic mode of operation:
+
+- DL FET is achieved by applying the DL BLER target at slot 14 (10ms) in each 20ms TTI duration. The NodeB may decide to stop transmission of the DL voice packet at slot 14 provided that the Uplink is in 10ms transmission mode (see sub-clause 6.4). The UE does not indicate successful decoding of the DL packet via the DL FET ACK or NACK field in UL DPCCH.
+- AMR Class A, B, C transport channels are not concatenated on the downlink.
+
+## 6.4 Uplink DPDCH dynamic 10ms transmission
+
+The R99 DCH transport channels for a voice call are typically configured with 20ms TTI. However, the transport block sizes for a voice call could potentially be transmitted over a shorter duration. The sub-feature of uplink DPDCH dynamic 10ms transmission allows for dynamically selecting a shorter transmission time, i.e. 10ms, at the physical layer to transmit a voice packet on the uplink. The UE selects on whether to use a 10ms or 20ms transmission duration based on considerations such as the power headroom at the UE. The UE also discontinues the transmission of UL DPCCH for the remaining duration of the TTI when both UL transport block has been completed transmitted and DL has been successfully decoded early.
+
+With 20ms TTI transmission at the physical layer, the pilot channel (UL DPCCH) is sent for the entire 20ms duration. This sub-feature potentially improves link efficiency due to reduction in UL DPCCH overhead as well as improves UE battery performance by allowing the UE to turn off its transceiver once the reception and transmission has been completed before the end of a 20ms TTI.
+
+# 7 Access Control in Connected Mode (CELL\_FACH, CELL\_PCH and URA\_PCH)
+
+For FDD, certain categories of UEs may be configured for Access Control in connected mode. This feature allows for a network to differentiate and control accesses of UE for DTCH transmission in CELL\_FACH state and for DCCH/CCCH due to uplink data transmission in CELL\_PCH state or URA\_PCH state, when uplink congestion is being experienced.
+
+The network may differentiate among the UE population by assigning UEs to one of 16 defined Access Groups. The network can indicate the identity of the access group to which the UE is assigned via RRC dedicated signalling.
+
+For each network assigned Access Group, the network can indicate in System Information whether the UEs in CELL\_FACH state, CELL\_PCH state or URA\_PCH state in that group are Blocked or Unblocked for DTCH data transmission and for DCCH/CCCH due to uplink data transmission. The System Information Block containing the Access Group information is scheduled by the network only during periods of uplink congestion. A UE in CELL\_FACH state, CELL\_PCH state or URA\_PCH state which has data to transmit and has an access group identity will reacquire the System Information Block containing the Access Group information based on the expiration of a timer.
+
+UEs in CELL\_PCH (without seamless transition to CELL\_FACH state) or URA\_PCH (without seamless transition to CELL\_FACH) are not allowed to initiate Cell Update procedure triggered due to DTCH data transmission with cause "uplink data transmission" when the Access Group of the UE is Blocked.
+
+UEs in CELL\_PCH (with seamless transition to CELL\_FACH state) or URA\_PCH (with seamless transition to CELL\_FACH state) are not allowed to initiate Measurement Report procedure triggered due to DTCH data transmission when the Access Group of the UE is Blocked.
+
+A UE in CELL\_FACH state, CELL\_PCH state or URA\_PCH state which is blocked for DTCH transmission and for DCCH/CCCH due to data transmission in the uplink is permitted to transmit uplink RLC Control PDUs.
+
+# 8 Access control enhancements
+
+## 8.1 DSAC and PPAC update for the UE in CELL\_DCH state
+
+In CELL\_DCH state, it allows the network to indicate to the UE about the DSAC and PPAC parameters through dedicated signalling so that the UE can obtain the updated DSAC and PPAC information.
+
+# 9 Enhanced Broadcast of System Information
+
+## 9.1 Second system information broadcast channel
+
+In order to increase system information capacity (see TR 25.704 [7]) a second system information broadcast channel on SCCPCH can be configured, in addition to the system information broadcast channel on PCCPCH.
+
+The second system information broadcast channel is mapped to a separate SCCPCH, which is different from the SCCPCH used for paging and FACH/CTCH, as depicted in Figure 9.1-1.
+
+![](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+```
+
+graph TD
+    subgraph Logical_channel [Logical channel]
+        PCCH
+        CCCH_CTCH_DCCH_DTCH[CCCH  
+CTCH (CBS)  
+DCCH  
+DTCH]
+        BCCH
+    end
+
+    subgraph Transport_channel [Transport channel]
+        PCH
+        FACH
+        BCH
+    end
+
+    subgraph Physical_channel [Physical channel]
+        PICH
+        SCCPCH1[SCCPCH]
+        SCCPCH2[SCCPCH]
+        SCCPCH3[SCCPCH]
+        PCCPCH
+    end
+
+    PCCH --> PCH
+    PCH --> PICH
+    PCH --> SCCPCH1
+    CCCH_CTCH_DCCH_DTCH --> FACH
+    FACH --> SCCPCH2
+    BCCH --> BCH
+    BCH --> SCCPCH3
+    BCH --> PCCPCH
+
+    style SCCPCH3 stroke-dasharray: 5 5
+    style PCCPCH stroke-dasharray: 5 5
+
+```
+
+*Note: The diagram shows the mapping of logical channels to transport channels and then to physical channels. Dashed ellipses group SCCPCH as "Second system information broadcast channel 'BCH on SCCPCH'" and PCCPCH as "System information broadcast channel 'BCH on PCCPCH'".*
+
+**Figure 9.1-1: Channel mapping of system information broadcast channel and second system information broadcast channel.**
+
+The UE should be able to monitor at least two SCCPCHs simultaneously, but the UE may skip reading the second system information broadcast channel during CTCH occasions in Idle mode and CELL\_PCH/URA\_PCH state. When HS-DSCH in CELL\_FACH is used, a UE supporting second system information broadcast channel monitors the corresponding SCCPCH while listening to HS-DSCH.
+
+REL-12 and later SIBs are introduced on both the system information broadcast channel as well as the second system information broadcast channel. Pre-REL-12 SIBs may be broadcasted on the second system information broadcast channel in addition to the system information broadcast channel. Any SIB type may be scheduled simultaneously on system information broadcast channel and second system information broadcast channel provided that the content is the same.
+
+Most of the existing principles and procedures for system information reading are retained for the second system information broadcast channel. To reduce the latency to acquire the system information on both system information broadcast channel and second system information broadcast channel, the UE acquires the system information on both channels simultaneously. The simultaneous acquisition of system information on both system information broadcast channel and second system information broadcast channel is depicted in Figure 9.1-2.
+
+![Figure 9.1-2: System information acquisition on system information broadcast channel and second system information broadcast channel.](c78c2eefd86269d1740ab85a916f24f2_img.jpg)
+
+The diagram illustrates the acquisition process. A UE receives a "Paging / SICI message with MIB value tag and SB3 value tag". This triggers the UE to read two parallel timelines: 
+1. **System information broadcast channel (BCH on PCCPCH):** Contains a sequence of blocks: MIB, SB1, followed by several orange blocks, then SIBx, more orange blocks, SIBy, and more orange blocks.
+2. **Second system information broadcast channel (BCH on SCCPCH):** Contains SB3, followed by orange blocks, SIBa, more orange blocks, SIBb, and more orange blocks.
+Arrows indicate that the UE reads MIB and SB1 from the first channel, SB3 from the second channel, and then proceeds to read SIBx/SIBy from the first channel and SIBa/SIBb from the second channel simultaneously.
+
+Figure 9.1-2: System information acquisition on system information broadcast channel and second system information broadcast channel.
+
+**Figure 9.1-2: System information acquisition on system information broadcast channel and second system information broadcast channel.**
+
+When the SB3 value tag in PAGING TYPE 1 or SYSTEM INFORMATION CHANGE INDICATION (SICI) message is updated the UE supporting second system information broadcast channel is required to re-acquire the system information on the second system information broadcast channel. When the SB3 value tag is updated, but the MIB
+
+value tag is not, the UE supporting second system information broadcast channel is only required to re-acquire the system information on the second system information broadcast channel.
+
+The scheduling block 3 (SB3) contains the scheduling information for the system information on the second system information broadcast channel. This scheduling information uses the SFN of the PCCPCH.
+
+The SB3 is broadcasted with a pre-defined offset (40 ms) from the start of the frame containing the MIB, as depicted in the Figure 9.1-3. The MIB on BCH mapped on PCCPCH contains the channelization code of the second system information broadcast channel, the repetition interval of SB3 and the number of segments of SB3. The remaining configuration parameters of the second system information broadcast channel are pre-defined.
+
+![Figure 9.1-3: SB3 pre-defined offset from the start of the frame containing the MIB. The diagram shows two horizontal timelines representing broadcast channels. The top timeline is labeled 'System information broadcast channel (BCH on PCCPCH)' and contains a red block labeled 'MIB' followed by an orange block labeled 'SB1'. A double-headed arrow between the MIB and SB1 is labeled 'MIB interval 80 ms'. The bottom timeline is labeled 'Second system information broadcast channel (BCH on SCCPCH)' and contains an orange block labeled 'SB3'. A vertical dashed line connects the start of the MIB block on the top timeline to the start of the SB3 block on the bottom timeline. A horizontal double-headed arrow between these two start points is labeled '40 ms'.](08441fa90c5fd11994626f662ac13f19_img.jpg)
+
+Figure 9.1-3: SB3 pre-defined offset from the start of the frame containing the MIB. The diagram shows two horizontal timelines representing broadcast channels. The top timeline is labeled 'System information broadcast channel (BCH on PCCPCH)' and contains a red block labeled 'MIB' followed by an orange block labeled 'SB1'. A double-headed arrow between the MIB and SB1 is labeled 'MIB interval 80 ms'. The bottom timeline is labeled 'Second system information broadcast channel (BCH on SCCPCH)' and contains an orange block labeled 'SB3'. A vertical dashed line connects the start of the MIB block on the top timeline to the start of the SB3 block on the bottom timeline. A horizontal double-headed arrow between these two start points is labeled '40 ms'.
+
+Figure 9.1-3: SB3 pre-defined offset from the start of the frame containing the MIB.
+
+## 9.2 Scheduling information overhead reduction
+
+To reduce the overhead of SIB scheduling information, included in MIB and Scheduling Blocks, the network may use mandatory default values for SIB\_OFF and SEG\_COUNT (when SIB\_POS offset info is included) for SIBs of REL-12 or later.
+
+## 9.3 MIB and Cell Value Tag range extension
+
+To reduce the risk of Cell Value Tag wrap around, the network may broadcast a range extension (1..16) of the Cell Value Tag for SIB3, SIB5, SIB5bis, SIB21 and SIB22. The network may also extend the MIB value tag range (1..16). For UEs supporting these extensions the SIBs and MIB wrap around at 16, while for UEs not supporting this feature the SIBs wraps around at 4 (and MIB at 8). SIBs of REL-12 or later use the extended Cell Value Tag range (1..16).
+
+# 10 RAN assisted WLAN interworking
+
+This clause describes the mechanisms to support traffic steering between UTRAN and WLAN.
+
+## 10.1 General principles
+
+This version of the specification supports UTRAN assisted UE based bi-directional traffic steering between UTRAN and WLAN for UEs in Idle mode and CELL\_DCH, CELL\_FACH, CELL\_PCH and URA\_PCH states.
+
+UTRAN provides assistance parameters via broadcast and dedicated RRC signalling to the UE. The RAN assistance parameters may include UTRAN signal strength thresholds, WLAN channel utilization thresholds, WLAN backhaul data rate thresholds, WLAN signal strength thresholds and Offload Preference Indicator (OPI). UTRAN can also provide a list of WLAN identifiers to the UE via broadcast and dedicated signalling.
+
+The UE uses the RAN assistance parameters in the evaluation of:
+
+- access network selection and traffic steering rules defined in TS 25.304 [9]; or
+- ANDSF policies defined in TS 24.312 [8]
+
+for traffic steering decisions between UTRAN and WLAN as specified in TS 23.402 [10].
+
+The OPI is only used in ANDSF policies as specified in TS 24.312 [8].
+
+WLAN identifiers are only used in access network selection and traffic steering rules defined in TS 25.304 [9].
+
+If the UE is provisioned with ANDSF policies it shall forward the received RAN assistance parameters to upper layers, otherwise it shall use them in the access network selection and traffic steering rules defined in subclause 10.2 and TS 25.304 [9]. The access network selection and traffic steering rules defined in subclause 10.2 and TS 25.304 [9] are applied only to the WLANs of which identifiers are provided by the UTRAN.
+
+The UE in CELL\_DCH state shall apply the parameters obtained via dedicated signalling, and shall keep those parameters during handover if they are not reconfigured or deleted; the UE shall discard the parameters obtained via dedicated signalling at SRNS relocation.
+
+The UE in CELL\_FACH state shall apply the parameters obtained via dedicated signalling if such have been received from the serving cell; otherwise the UE shall apply the parameters obtained via broadcast signalling. Upon cell selection/reselection the UE shall discard the dedicated parameters.
+
+The UE in Idle mode, CELL\_PCH or URA\_PCH state shall keep and apply the parameters obtained via dedicated signalling until selection/reselection of another cell than the one where these parameters were received or a timer has expired since the UE moved from CELL\_DCH or CELL\_FACH to Idle mode, CELL\_PCH or URA\_PCH state, upon which the UE shall discard the dedicated parameters and apply the parameters obtained via broadcast signalling.
+
+In the case of RAN sharing, each PLMN sharing the RAN can broadcast independent sets of RAN assistance parameters.
+
+## 10.2 Access network selection and traffic steering rules
+
+The UE indicates to upper layers when (and for which WLAN identifiers) access network selection and traffic steering rules defined in TS 25.304 [9] are fulfilled. The selection among WLANs that fulfil the access network selection and traffic steering rules is up to UE implementation.
+
+When the UE applies the access network selection and traffic steering rules defined in TS 25.304 [9], higher layers perform traffic steering between UTRAN and WLAN.
+
+# --- 11 Increased minimum number of carriers to monitor
+
+The increased number of carrier monitoring feature allows a UE to monitor more UMTS and LTE frequencies in all RRC states.
+
+When increased carrier monitoring is used, the network signals whether a carrier should be measured with "reduced measurement performance" together with a scaling factor applicable for CELL\_DCH and CELL\_FACH states. In Idle mode, CELL\_PCH and URA\_PCH states a fixed scaling factor is used. When a carrier does not belong to the "reduced measurement performance" group, it belongs to the "normal measurement performance" group.
+
+The value and the use of scaling factor are specified in [11].
+
+# --- 12 Extended DRX in Idle mode
+
+The extended DRX (eDRX) feature enables DRX 10,24 seconds up to 2621.44 seconds (~44 minutes) in Idle mode for the PS domain.
+
+The eDRX feature in Idle mode uses the Paging Occasions (PO) as determined by the CN domain specific DRX cycle length coefficient (PS domain) in SIB1 [12] and specified by the Discontinuous Reception for Paging [9]. However the UE is not required to monitor every PO, but only the POs that belong to the Paging Transmission Window (PTW):
+
+![Figure 12-1: Extended DRX in Idle mode. The diagram shows two horizontal timelines. The top timeline shows a 'Sleep period' followed by a 'Paging Transmission Window (PTW)'. The duration of the sleep period plus the PTW is labeled as T_eDRX. The bottom timeline is an expanded view of the PTW, showing four Paging Occasions (PO) separated by 'PS DRX cycles'. The total duration of this window is labeled T_PTW.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+```
+
+  graph LR
+    subgraph Top_Timeline
+    A[Sleep period] -- T_eDRX --> B[Paging Transmission Window - PTW]
+    end
+    subgraph Bottom_Timeline_Zoom
+    B1[PO] -- PS DRX cycle --> B2[PO] -- PS DRX cycle --> B3[PO] -- PS DRX cycle --> B4[PO]
+    B1 -- T_PTW --> B4
+    end
+  
+```
+
+Figure 12-1: Extended DRX in Idle mode. The diagram shows two horizontal timelines. The top timeline shows a 'Sleep period' followed by a 'Paging Transmission Window (PTW)'. The duration of the sleep period plus the PTW is labeled as T\_eDRX. The bottom timeline is an expanded view of the PTW, showing four Paging Occasions (PO) separated by 'PS DRX cycles'. The total duration of this window is labeled T\_PTW.
+
+**Figure 12-1: Extended DRX in Idle mode**
+
+The eDRX parameter in Idle mode values, i.e. timer values for  $T_{eDRX}$  and  $T_{PTW}$  are negotiated and configured during ATTACH and RAU procedure ([4] and [5]). Timer  $T_{eDRX}$  is (re-)started when upper layers indicate successful completion of the ATTACH/RAU procedure, including eDRX parameters in Idle mode. When timer  $T_{eDRX}$  expires, the UE wakes-up from sleep, it checks the MIB for any system information changes and it starts monitoring the paging occasions in the PS DRX in Idle mode. When timer  $T_{eDRX}$  expires it is re-started, and timer  $T_{PTW}$  is started. When timer  $T_{PTW}$  expires the UE stops monitoring paging occasions in the PS DRX in Idle mode. The timer  $T_{eDRX}$  and  $T_{PTW}$  do not stop/reset when the UE transitions from Idle to Connected or transitions from Connected to Idle. The timers  $T_{eDRX}$  and  $T_{PTW}$  are stopped, if running, when upper layer indicates that the eDRX parameters in Idle mode are not included in the ATTACH/RAU complete. The timers  $T_{eDRX}$  and  $T_{PTW}$  are reset when upper layer indicates that a new value is configured in ATTACH/RAU complete. The value of  $T_{eDRX}$  is signaled in IE “eDRX value” in ATTACH/RAU [4] for timer T331 in RRC [12]. The value of  $T_{PTW}$  is signaled in IE “Paging Time Window” in ATTACH/RAU [4] for timer T332 in RRC [12].
+
+# 13 L2 and L3 Downlink enhancements for UMTS
+
+## 13.1 Retrievable configurations
+
+The retrievable configurations feature allows the UE to store configurations together with an identity. When the network invokes a retrievable configuration, it needs to signal only its identity. A retrievable configuration can be signalled to a UE in any state except for idle. Retrievable configurations are cleared when entering idle mode and at SRNS relocation.
+
+There are two ways of signalling the retrievable configurations: one way is that as a result of an RRC signalling procedure, the UE stores the received configuration as a retrievable configuration, and the other way is that the network preconfigures the UE with at least one retrievable configuration. The network can signal a delta to a stored configuration for either of the two ways. The UE validates a retrievable configuration when it invokes it.
+
+## 13.2 URA\_PCH with seamless transition
+
+The feature URA\_PCH with seamless transition to CELL\_FACH is described in 3GPP TS 25.319 [3].
+
+## 13.3 Optimization from IDLE to CONNECTED state
+
+If the UE supports "NodeB triggered HS-DPCCH transmission", the RNC can issue the indication to trigger acquisition of the common E-DCH resource or to release the allocated common E-DCH resource for the particular UE.
+
+## 13.4 Blind HARQ retransmissions for HSDPA
+
+The feature blind HARQ retransmissions for HSDPA is described in 3GPP TS 25.308 [2].
+
+## 13.5 Enhanced state transition
+
+This feature allows the UE to move to a more power efficient state without explicit RRC reconfiguration. The UE sends the RRC indication to the RNC and moves to the target state upon reception of the RLC ACK from the RNC. The state transition is applicable to the following cases: from CELL\_DCH to CELL\_FACH, from CELL\_FACH to CELL\_PCH/URA\_PCH, and from CELL\_DCH to CELL\_PCH/URA\_PCH.
+
+While configuring a UE with enhanced state transition, the RNC can provide RRC configuration that will be applied once the UE enters the target state.
+
+## 13.6 Improved synchronized RRC procedures
+
+In improved synchronized RRC procedures, firstly the UE receives an RRC reconfiguration message for a synchronized RRC procedure indicating that the activation time shall be dynamically determined. Then, when the UE is ready to switch to the new configuration indicated in the RRC message, it sends a MAC Control Information to the Node B. On reception of the HARQ ACK to the MAC Control Information, the UE calculates the activation time by adding an offset to the current CFN. The UE reconfigures at the calculated activation time and sends an RRC configuration complete message upon successful completion of the procedure.
+
+The network can also indicate a legacy activation time, at which the switch to the new configuration latest shall occur. The UE will choose the smallest value of the legacy activation time and the calculated activation time as the final activation time.
+
+# --- 14 Downlink TPC enhancements for UMTS
+
+In CELL\_DCH state, the network can configure a UE with power control Algorithm 3 when the F-DPCH is also configured. For this algorithm, the TPC command is transmitted only once in a certain number of consecutive slots, and other TPC commands are DTXed in the remaining slots. The number of consecutive slots can be configured with 3 or 5 slots.
+
+If a UE is configured with Algorithm 3 on any of the radio links, then all the radio links within the same RLS must have power control Algorithm 3. If power control Algorithm 3 is configured in one RLS, and any of the legacy algorithms is configured in another RLS, then the UE will behave as per Algorithm 3 to determine transmission power under such configuration.
+
+For generation of TPC in uplink DPCCH, the UE will generate and transmit TPC command as per the algorithm configured on the serving radio link.
+
+# --- 15 NAICS offloading (FDD only)
+
+In this offloading mechanism, the UE is configured with the Multiflow operation 3GPP TS 25.308 [2], which allows the UE to measure and send CQIs for cells belonging to a different Node B. Based on received channel quality information, the UE can be offloaded from the serving Node B HS-DSCH cell(s) to HS-DSCH cell(s) belonging to a different Node B through the network specific behaviour, e.g. serving cell change procedure.
+
+# --- 16 ACDC in Idle Mode
+
+The ACDC feature allows network to control new PS domain access attempts from particular applications in the UE in idle mode to prevent/mitigate overload of the access network and/or the core network.
+
+The applications on the UE may be associated with an ACDC category. At subscription, at least four ACDC categories, and up to 16 ACDC categories, are allocated to the subscriber and stored in the ACDC Management Object (MO) or USIM [9].
+
+The access barring information for each ACDC category is broadcast in SIB. The ACDC capable UE controls the access attempt for a certain application based on the broadcast barring information and the configuration of ACDC categories in the UE.
+
+The following guidelines define the behaviour of a UE configured with ACDC when other access control mechanisms (ACB, EAB and DSAC) are co-existing:
+
+- When DSAC and ACDC are configured together, the PS domain DSAC will be ignored by the UEs.
+- When EAB and ACDC are configured together, the UE will first check EAB and then check ACDC.
+- For UEs configured with ACDC, ACB is ignored.
+
+# --- 17 RRC optimization
+
+## 17.1 RRC measurement events for UPH reporting
+
+The RRC measurement events for UPH reporting allow the UE to perform measurements on UE Power Headroom (UPH) and signal measurement events when the UPH becomes larger or less than an absolute threshold respectively. The thresholds are configurable, as well as hysteresis, time-to-trigger, filter coefficient and pending time after trigger for each of the events.
+
+## 17.2 Simultaneous Setup and Release of RABs and RBs
+
+The simultaneous setup and release of RABs and RBs enhancement allows setup, release and reconfiguration of radio access bearers and radio bearers in the same RRC message.
+
+# --- 18 HS-SCCH DRX in CELL\_FACH state (FDD only)
+
+With the feature HS-SCCH DRX in CELL\_FACH state, the UE discontinuously receives only HS-SCCH orders without decoding HS-DSCH in CELL\_FACH state. Details could be referred in 3GPP TS 25.308 [2].
+
+# --- 19 Dual Cell E-DCH operation enhancements
+
+This feature Dual Cell E-DCH operation enhancements is described in 3GPP TS 25.319 [3].
+
+# --- 20 QoE Measurement Collection
+
+With this feature, the network can configure collection of measurements from the UE. The feature defines QoE measurement configuration and measurement reporting containers, and the feature uses the MDT framework [14]. QoE measurement configuration received from OAM or CN is encapsulated in a container, which is inserted in a Measurement Control message and forwarded to the UE transparently. QoE measurements received from UE higher layer are inserted in a container in a Measurement Report message and sent over SRB4.
+
+The supported service types for QoE Measurement Collection are QoE Measurement Collection for streaming services and QoE Measurement Collection for MTSI services.
+
+The QoE measurement configuration is supported in CELL\_DCH and CELL\_FACH states, whereas the QoE measurement reporting is supported in CELL\_DCH state only.
+
+Both signalling based and management based initiation cases are allowed. For the signalling based case, the QoE Measurement Collection is initiated towards a specific UE from CN nodes using the MDT mechanism as described in clause 5.1.3 [14]; for the management based case, the QoE Measurement Collection is initiated from OAM targeting an area (without targeting a specific UE).
+
+# --- 21 DL Interference Mitigation (FDD only)
+
+The feature DL interference mitigation enables the UE to receive an indication about a potential increase in the DL adjacent channel interference level (e.g. due to adjacent GSM carriers). The corresponding signalling indication is conveyed in broadcast messages SIB5, SIB5bis and SIB6. The UE may use this indication to mitigate the DL interference, e.g. by using optimized Rx filtering.
+
+# --- 22 Simplified HS-SCCH type 1 operation
+
+This feature Simplified HS-SCCH type 1 operation is described in 3GPP TS 25.308 [2].
+
+# --- 23 NR SRVCC to UTRAN
+
+The feature NR SRVCC to UTRAN enables a UE to perform a SRVCC procedure from NR only to UTRAN FDD. The SRVCC architecture and signalling flow have been defined in TS 23.216 [15]. In TS 38.300 [16], inter-RAT mobility procedure on NR SRVCC to UTRAN FDD has been defined. The UE receives in the handover to UTRAN command security information which is used to derive both ciphering and integrity protection keys for operation in UTRAN, as specified in TS 38.300 [16]. During the handover, as specified in TS 25.413 [17], the target RNC node receives the SRVCC source RAT indication from the source NR node. After the UE completes the IMS voice service in UTRAN FDD, the security mode control procedure is performed to activate the integrity protection for the voice service in the CS domain. When and how to perform the return procedure from UTRAN to NR after the UE completes the voice service depends on UE implementation.
+
+# Annex A (informative): Change history
+
+| Change history |        |           |      |     |     |                                                                                                           |        |
+|----------------|--------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Cat | Subject/Comment                                                                                           | New    |
+| 02/2014        | R2-85  | R2-140618 | -    | -   |     | Initial Skeleton Document                                                                                 | 0.0.1  |
+| 02/2014        | R2-85  | R2-140860 | -    | -   |     | Updates after review. Removal of section 4, updated wording of the scope                                  | 0.0.2  |
+| 02/2014        | R2-85  | R2-140895 | -    | -   |     | TS version 0.1.0 as agreed                                                                                | 0.1.0  |
+| 05/2014        | R2-86  | R2-142782 | -    | -   |     | Incorporating the Hetnet stage 2 description                                                              | 0.1.1  |
+|                | R2-86  | R2-142925 | -    | -   |     | TS version 0.2.0 as agreed by email discussion [86#11] after RAN2 #86                                     | 0.2.0  |
+|                | R2-86  | R2-142926 | -    | -   |     | TS version 1.0.0 as agreed by email discussion [86#11] after RAN2 #86                                     | 1.0.0  |
+| 06/2014        | RP-64  | RP-140844 | -    | -   |     | TS version 1.0.0 submitted to RAN#64 for 1-step approval<br>Approved as 12.0.0 at RAN#64 and MCC clean-up | 12.0.0 |
+|                | RP-64  | RP-140882 | 0001 | -   |     | Stage 2 description of Power Saving Mode feature for UMTS                                                 | 12.1.0 |
+| 09/2014        | RP-65  | RP-141504 | 0002 | -   |     | Stage-2 details of WLAN/3GPP Radio Interworking for UMTS                                                  | 12.2.0 |
+|                | RP-65  | RP-141503 | 0008 | 1   |     | Introduction of DSAC and PPAC update in CELL_DCH                                                          | 12.2.0 |
+|                | RP-65  | RP-141500 | 0007 | 1   |     | Introduction of DCH Enhancements                                                                          | 12.2.0 |
+|                | RP-65  | RP-141503 | 0003 | 1   |     | Introduction of Further EUL enhancements                                                                  | 12.2.0 |
+|                | RP-65  | RP-141502 | 0006 | 2   |     | Introduction of a second broadcast channel                                                                | 12.2.0 |
+|                | RP-65  | RP-141501 | 0005 | -   |     | CR to 25.300 on the introduction of Heterogeneous Networks Enhancements                                   | 12.2.0 |
+| 12/2014        | RP-66  | RP-142127 | 0009 | -   |     | Cleanup corrections for Access group mechanism                                                            | 12.3.0 |
+|                | RP-66  | RP-142122 | 0011 | -   |     | Clarification on handling of dedicated parameters upon cell selection&reselection                         | 12.3.0 |
+|                | RP-66  | RP-142126 | 0010 | 1   |     | CR to 25.300 on the correction of Second Broadcast Channel                                                | 12.3.0 |
+|                | RP-66  | RP-142128 | 0013 | 1   |     | Introduction of increased UE carrier monitoring                                                           | 12.3.0 |
+| 06/2015        | RP-68  | RP-150919 | 0014 | -   |     | Clarification for Access Group based access control                                                       | 12.4.0 |
+| 12/2015        | RP-70  | RP-152064 | 0032 | -   |     | Introduction of NAICS for UMTS                                                                            | 13.0.0 |
+|                | RP-70  | RP-152060 | 0031 | 1   |     | CR to 25.300 on the introduction of Downlink TPC enhancements for UMTS                                    | 13.0.0 |
+|                | RP-70  | RP-152061 | 0025 | 1   |     | Introduction of retrievable configurations                                                                | 13.0.0 |
+|                | RP-70  | RP-152061 | 0026 | 1   |     | Introduction of URA_PCH with seamless transition                                                          | 13.0.0 |
+|                | RP-70  | RP-152061 | 0027 | 1   |     | Introduction of improved synchronized RRC procedures                                                      | 13.0.0 |
+|                | RP-70  | RP-152061 | 0030 | 1   |     | Introduction of blind HARQ retransmissions for HSDPA                                                      | 13.0.0 |
+|                | RP-70  | RP-152062 | 0029 | 1   |     | Introduction of enhanced state transition                                                                 | 13.0.0 |
+|                | RP-70  | RP-152061 | 0028 | 1   |     | Introduction of optimization from IDLE to CONNECTED state                                                 | 13.0.0 |
+|                | RP-70  | RP-152063 | 0022 | 1   |     | Introduction of extended DRX in Idle mode                                                                 | 13.0.0 |
+|                | RP-70  | RP-152066 | 0033 | 1   |     | Introduction of Application specific Congestion control for Data Communication (ACDC) in UTRAN            | 13.0.0 |
+| 03/2016        | RP-71  | RP-160466 | 0035 | 2   |     | Correction on signalling transmission control due to access group blocking of DTCH                        | 13.1.0 |
+| 06/2016        | RP-72  | R2-164343 | 0040 | 1   |     | Correction on DCH enhancements                                                                            | 13.2.0 |
+| 09/2016        | RP-73  | RP-161748 | 0045 | 1   |     | Introduction of RRC events for UPH reporting                                                              | 14.0.0 |
+|                | RP-73  | RP-161748 | 0046 | 1   |     | Introduction of simultaneous setup and release of RABs and RBs                                            | 14.0.0 |
+| 12/2016        | RP-74  | RP-162330 | 0047 | 1   |     | Introduction of HS-SCCH DRX operation in CELL_FACH state                                                  | 14.1.0 |
+|                | RP-74  | RP-162331 | 0048 | 1   |     | Introduction of Dual Cell E-DCH operation enhancements                                                    | 14.1.0 |
+| 03/2017        | RP-75  | RP-170654 | 0053 | -   | A   | Correction for traffic steering granularity for RAN assisted WLAN interworking                            | 14.2.0 |
+| 03/2017        | RP-75  | RP-170648 | 0054 | 1   | B   | Introduction of QoE Measurement Collection for streaming services                                         | 14.2.0 |
+| 06/2017        | RP-76  | RP-171240 | 0056 | 2   | B   | Introduction of DL interference mitigation                                                                | 14.3.0 |
+| 09/2017        | RP-77  | RP-171591 | 0058 | 1   | F   | Corrections for DL Interference Mitigation                                                                | 14.4.0 |
+| 09/2017        | RP-77  | RP-171592 | 0057 | -   | B   | Introduction of Simplified HS-SCCH type 1 operation for UMTS                                              | 15.0.0 |
+| 03/2018        | RP-79  | RP-180067 | 0059 | 1   | C   | Introduction of QoE Measurement Collection for MTSI services                                              | 15.1.0 |
+| 03/2020        | RP-87e | RP-200051 | 0060 | 2   | B   | Introduction of NR SRVCC to UTRAN                                                                         | 16.0.0 |
+| 07/2020        | RP-88e | RP-200573 | 0061 | -   | F   | Correction on ciphering for NR SRVCC to UTRAN                                                             | 16.1.0 |
+| 03/2022        | RP-95e | -         | -    | -   | -   | Upgrade to Rel-17 version without technical change                                                        | 17.0.0 |
+| 03/2024        | RP-103 | -         | -    | -   | -   | Upgrade to Rel-18 version without technical change                                                        | 18.0.0 |

marked/Rel-18/25_series/25307/raw.md

@@ -0,0 +1,303 @@
+
+
+# 3GPP TS 25.307 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements on User Equipments (UEs) supporting a release- independent frequency band (Release 18)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. There is a small red signal icon below the 'P'.
+
+3GPP logo
+
+## --- **Keywords**
+
+UMTS, radio
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles – Sophia Antipolis  
+Valbonne – France  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTET™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                                                         |           |
+|-----------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                          | 4         |
+| 1 Scope.....                                                                            | 5         |
+| 2 References.....                                                                       | 5         |
+| 3 Definitions and abbreviations .....                                                   | 5         |
+| 3.1 Definitions.....                                                                    | 5         |
+| 3.2 Abbreviations .....                                                                 | 5         |
+| 3A General .....                                                                        | 5         |
+| 4 Void.....                                                                             | 6         |
+| 5 Void.....                                                                             | 6         |
+| 6 Void.....                                                                             | 6         |
+| 7 Void.....                                                                             | 6         |
+| 8 Void.....                                                                             | 6         |
+| 9 Void.....                                                                             | 6         |
+| 10 Void.....                                                                            | 6         |
+| 11 Void.....                                                                            | 6         |
+| 12 Void.....                                                                            | 6         |
+| 13 Void.....                                                                            | 6         |
+| 14 Void.....                                                                            | 6         |
+| 15 Void.....                                                                            | 7         |
+| 16 Void.....                                                                            | 7         |
+| 17 Void.....                                                                            | 7         |
+| 18 Void.....                                                                            | 7         |
+| 19 Void.....                                                                            | 7         |
+| 20 Void.....                                                                            | 7         |
+| 21 Void.....                                                                            | 7         |
+| 22 Void.....                                                                            | 7         |
+| 23 Void.....                                                                            | 7         |
+| 24 Void.....                                                                            | 7         |
+| 25 Void.....                                                                            | 7         |
+| <b>Annex A (normative): Void.....</b>                                                   | <b>9</b>  |
+| <b>Annex B (normative): Frequency arrangement for overlapping operating bands .....</b> | <b>10</b> |
+| <b>Annex C (informative): Change history.....</b>                                       | <b>11</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies requirements on UEs supporting a frequency band that is independent of release.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] to [29] Void.
+
+[30] 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)".
+
+[31] 3GPP TS 25.102: "UE Radio Transmission and Reception (TDD)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in [1] apply.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                           |
+|-----|---------------------------|
+| FDD | Frequency Division Duplex |
+| RRC | Radio Resource Control    |
+| UE  | User Equipment            |
+
+## --- 3A General
+
+TSG-RAN has agreed that the standardisation of new frequency bands may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band of operation that is specified in a later release, it is necessary to specify some extra requirements.
+
+For example, Band III is contained in the Release 5 specifications. In order to implement a UE conforming to Release '4 but supporting Band III, it is necessary for the UE to additionally conform to some parts of the Release 5 specifications, such as the radio frequency requirements for the Band III and some signalling extensions relating to the UE radio access capabilities.
+
+NOTE: See NOTE in clause 4.4 in [30] or [31].
+
+---
+
+4 Void
+
+---
+
+5 Void
+
+---
+
+6 Void
+
+---
+
+7 Void
+
+---
+
+8 Void
+
+---
+
+9 Void
+
+---
+
+10 Void
+
+---
+
+11 Void
+
+---
+
+12 Void
+
+---
+
+13 Void
+
+---
+
+14 Void
+
+---
+
+15 Void
+
+---
+
+16 Void
+
+---
+
+17 Void
+
+---
+
+18 Void
+
+---
+
+19 Void
+
+---
+
+20 Void
+
+---
+
+21 Void
+
+---
+
+22 Void
+
+---
+
+23 Void
+
+---
+
+24 Void
+
+---
+
+25 Void
+
+
+
+## --- Annex A (normative): Void
+
+## Annex B (normative): Frequency arrangement for overlapping operating bands
+
+The following information is provided in order to assist a UE to derive the DL UARFCN and UL UARFCN in a multi-band environment, in which multiple overlapping operating bands may be indicated in the IE "Multiple Frequency Band indicator list" (System Information Block type 5, System Information Block type 5bis and System Information Block type 6), or the IE "Multiple Frequency Info List FDD" (System Information Block type 11, System Information Block type 11bis and System Information Block type 12).
+
+The sets of bands (multi-band environment), independent of release, that may be indicated in a cell are shown in Table B-1. Subsets of these may also be indicated. The DL UARFCN and UL UARFCN are derived according to [25.101].
+
+**Table B-1: Overlapping bands (multi-band environments) for each UTRA band**
+
+| UTRA Operating Band | Overlapping UTRA operating bands | Duplex Mode |
+|---------------------|----------------------------------|-------------|
+| 2                   | 25                               | FDD         |
+| 3                   | 9                                | FDD         |
+| 4                   | 10                               | FDD         |
+| 5                   | 18, 19, 26                       | FDD         |
+| 9                   | 3                                | FDD         |
+| 10                  | 4                                | FDD         |
+| 18                  | 5, 26                            | FDD         |
+| 19                  | 5, 26                            | FDD         |
+| 25                  | 2                                | FDD         |
+| 26                  | 5, 18, 19                        | FDD         |
+
+## Annex C (informative): Change history
+
+| Change history |        |           |      |     |     |                                                                                                                                           |        |
+|----------------|--------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Cat | Subject/Comment                                                                                                                           | New    |
+| 09/2001        | RP-13  | RP-010557 |      |     |     | Approved at TSG-RAN #13 and placed under Change Control                                                                                   | 3.0.0  |
+|                | RP-13  | RP-010558 | 001  | 1   |     | Correction to create Release 4                                                                                                            | 4.0.0  |
+| 12/2001        | RP-14  | RP-010759 | 003  |     |     | Inclusion of release independent RF related information                                                                                   | 4.1.0  |
+| 03/2002        | RP-15  | RP-020096 | 004  |     |     | Creation of Rel-5 specification                                                                                                           | 5.0.0  |
+| 12/2003        | RP-22  | RP-030630 | 010  |     |     | Introduction of UMTS800                                                                                                                   | 6.0.0  |
+| 03/2004        | RP-23  | RP-040092 | 016  | 1   |     | Frequency band alignment with 25.101                                                                                                      | 6.1.0  |
+|                | RP-23  | RP-040090 | 023  |     |     | Introduction of UMTS1700/2100 (Band IV)                                                                                                   | 6.1.0  |
+|                | RP-23  | RP-040091 | 027  |     |     | Introduction of UMTS850(Band V)                                                                                                           | 6.1.0  |
+| 09/2005        | RP-29  | RP-050467 | 0038 |     |     | Introduction of UMTS2600 internal band, Band VII                                                                                          | 6.2.0  |
+| 12/2005        | RP-30  | RP-050800 | 0042 |     |     | Introduction of UMTS 900 (Band VIII)                                                                                                      | 6.3.0  |
+|                | RP-30  | RP-050801 | 0034 |     |     | Introduction of UMTS1700                                                                                                                  | 6.3.0  |
+| 06/2006        | RP-32  | RP-060369 | 0043 |     |     | Creation of release 7 version                                                                                                             | 7.0.0  |
+| 12/2006        | RP-34  | RP-060715 | 0057 |     |     | Introduction of Band X (Extended UMTS 1.7/2.1 GHz) in 25.307                                                                              | 7.1.0  |
+| 09/2007        | RP-37  | RP-070633 | 0066 |     |     | Introduction of Band XI                                                                                                                   | 8.0.0  |
+| 03/2008        | RP-39  | RP-080200 | 0072 | -   |     | Introduction of UMTS 700 MHz (Bands XII – XIV) in 25.307                                                                                  | 8.1.0  |
+| 09/2008        | RP-41  | RP-080676 | 0077 | -   |     | Introduction of UMTS Band d in 25.307                                                                                                     | 8.2.0  |
+| 09/2008        | RP-41  | RP-080695 | 0082 | -   |     | Introduction of UMTS Band e in 25.307                                                                                                     | 8.2.0  |
+| 03/2009        | RP-43  | RP-090146 | 0087 | -   |     | Introduction of UMTS Band f in 25.307                                                                                                     | 8.3.0  |
+| 09/2009        | RP-45  | RP-090921 | 0089 | -   |     | Introduction of Band XIX                                                                                                                  | 8.4.0  |
+| 09/2009        | RP-45  | RP-090921 | 0088 | 1   |     | Introduction of Band XIX                                                                                                                  | 9.0.0  |
+| 12/2009        | RP-46  | RP-091333 | 0094 | -   |     | Editorial corrections for Introduction of Band XIX                                                                                        | 9.1.0  |
+|                | RP-46  | RP-091335 | 0100 | 1   |     | Introduction of band XXI - 25.307                                                                                                         | 9.1.0  |
+| 03/2010        | RP-47  | RP-100302 | 0106 | -   |     | Introduction of band XX (800 MHz)                                                                                                         | 9.2.0  |
+| 03/2011        | RP-51  | -         | -    | -   |     | Upgrade to Release 10 - no technical change                                                                                               | 10.0.0 |
+| 06/2011        | RP-52  | RP-110844 | 0141 | 1   |     | Add Expanded 1900 MHz Band for UTRA and LTE to TS25.307                                                                                   | 10.1.0 |
+| 09/2011        | RP-53  | RP-111294 | 0161 | -   |     | Add Band XXII for LTE/UMTS 3500 (FDD)                                                                                                     | 10.2.0 |
+| 03/2012        | RP-55  | RP-120328 | 0168 | -   |     | Add Extending 850 MHz Upper Band (814 - 849 MHz) to TS25.307                                                                              | 10.3.0 |
+| 06/2012        | RP-56  | RP-120816 | 0170 | -   |     | Add Extending 850 MHz Upper Band (814 - 849 MHz) to TS25.307                                                                              | 11.0.0 |
+| 12/2012        | RP-58  | RP-121922 | 0193 | -   |     | Multiple frequency band indicators per cell                                                                                               | 11.1.0 |
+| 03/2014        | RP-63  | RP-140336 | 0207 | 1   |     | Introducing 'General' clause with note referring to notes in clause 4.4 in TS25.101 and TS25.102, editorial modifications to Scope clause | 11.2.0 |
+| 09/2014        | RP-65  | -         | -    | -   |     | Upgrade to the Release 12 - no technical change                                                                                           | 12.0.0 |
+| 12/2015        | RP-70  | -         | -    | -   |     | Upgrade to the Release 13 - no technical change                                                                                           | 13.0.0 |
+| 03/2017        | RP-75  | -         | -    | -   |     | Upgrade to Release 14 - no technical change                                                                                               | 14.0.0 |
+| 06/2018        | RP-80  | -         | -    | -   |     | Upgrade to Release 15 - no technical change                                                                                               | 15.0.0 |
+| 2020-07        | RP-88e | -         | -    | -   | -   | Upgrade to Rel-16 version without technical change                                                                                        | 16.0.0 |
+| 2022-03        | RP-95e | -         | -    | -   | -   | Upgrade to Rel-17 version without technical change                                                                                        | 17.0.0 |
+| 2024-03        | RP-103 | -         | -    | -   | -   | Upgrade to Rel-18 version without technical change                                                                                        | 18.0.0 |

marked/Rel-18/25_series/25324/raw.md

@@ -0,0 +1,991 @@
+
+
+# 3GPP TS 25.324 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Broadcast/Multicast Control (BMC) (Release 18)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. There is a small red signal icon below the 'G' and a 'TM' symbol to the right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, radio, broadcast
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+|                                                                   |    |
+|-------------------------------------------------------------------|----|
+| Foreword .....                                                    | 5  |
+| 1 Scope.....                                                      | 6  |
+| 2 References.....                                                 | 6  |
+| 3 Definitions and abbreviations .....                             | 6  |
+| 3.1 Definitions.....                                              | 6  |
+| 3.2 Abbreviations .....                                           | 7  |
+| 4 General.....                                                    | 7  |
+| 4.1 Model of BMC .....                                            | 7  |
+| 5 Functions.....                                                  | 8  |
+| 6 Services provided to Upper Layers.....                          | 8  |
+| 7 Services expected from RLC .....                                | 9  |
+| 8 Elements for layer-to-layer communication .....                 | 9  |
+| 8.1 Service Primitives between RRC and BMC .....                  | 9  |
+| 8.1.1 Primitives.....                                             | 9  |
+| 8.1.1.1 CBMC-Measurement-IND .....                                | 9  |
+| 8.1.1.2 CBMC-Rx-IND .....                                         | 9  |
+| 8.1.1.3 CBMC-Config-REQ .....                                     | 10 |
+| 8.1.2 Parameters .....                                            | 10 |
+| 8.1.2.1 CB-Traffic-Volume .....                                   | 10 |
+| 8.1.2.2 Action.....                                               | 10 |
+| 8.1.2.3 DRX selection.....                                        | 10 |
+| 8.1.2.4 CTCH configuration .....                                  | 10 |
+| 8.2 Service Primitives between upper layer (U-plane) and BMC..... | 11 |
+| 8.2.1 Primitives.....                                             | 11 |
+| 8.2.1.1 Primitives used in relation to UMTS Core Network .....    | 11 |
+| 8.2.1.1.1 BMC-Data-REQ.....                                       | 11 |
+| 8.2.1.1.2 BMC-Data-IND.....                                       | 12 |
+| 8.2.1.1.3 BMC-Data-CNF .....                                      | 12 |
+| 8.2.1.1.4 BMC-Congestion-IND .....                                | 12 |
+| 8.2.1.1.5 BMC-Normal-IND .....                                    | 12 |
+| 8.2.1.1.6 BMC-Activation-REQ .....                                | 12 |
+| 8.2.1.1.7 BMC-Deactivation-REQ.....                               | 12 |
+| 8.2.1.1.8 BMC-DRX-REQ.....                                        | 13 |
+| 8.2.1.1.9 BMC-Error-IND .....                                     | 13 |
+| 8.2.1.2 Primitives used for ANSI-41 Core Network.....             | 13 |
+| 8.2.1.2.1 BMC-Data41-REQ.....                                     | 13 |
+| 8.2.1.2.2 BMC-Data41-IND.....                                     | 13 |
+| 8.2.1.2.3 BMC-Error41-IND .....                                   | 13 |
+| 8.2.2 Parameters .....                                            | 14 |
+| 8.2.2.1 Message-ID.....                                           | 14 |
+| 8.2.2.2 Serial Number .....                                       | 14 |
+| 8.2.2.3 Data-Coding-Scheme.....                                   | 14 |
+| 8.2.2.4 CB-Data .....                                             | 14 |
+| 8.2.2.5 Category.....                                             | 14 |
+| 8.2.2.6 Repetition-Period .....                                   | 14 |
+| 8.2.2.7 Number-of-Broadcasts-Requested.....                       | 14 |
+| 8.2.2.8 CB-DRX-Schedule-Period.....                               | 14 |
+| 8.2.2.9 Reserved-CB-Capacity .....                                | 15 |
+| 8.2.2.10 Cause.....                                               | 15 |
+| 8.2.2.11 Transport Layer Message.....                             | 15 |
+| 8.2.2.12 Broadcast Address .....                                  | 15 |
+| 8.2.2.13 Error Type.....                                          | 15 |
+
+|                               |                                           |           |
+|-------------------------------|-------------------------------------------|-----------|
+| 9                             | Procedures.....                           | 15        |
+| 9.1                           | BMC Message Broadcast.....                | 15        |
+| 9.2                           | Generation of Schedule message.....       | 15        |
+| 9.3                           | Traffic volume measurement .....          | 16        |
+| 9.4                           | BMC message reception.....                | 16        |
+| 10                            | BMC Messages .....                        | 17        |
+| 10.1                          | General .....                             | 17        |
+| 10.2                          | BMC CBS Message .....                     | 17        |
+| 10.3                          | BMC Schedule Message .....                | 17        |
+| 10.4                          | BMC CBS41 Message .....                   | 18        |
+| 11                            | Information Elements.....                 | 19        |
+| 11.1                          | Message Type.....                         | 19        |
+| 11.2                          | Message ID.....                           | 19        |
+| 11.3                          | Serial Number .....                       | 19        |
+| 11.4                          | Data Coding Scheme.....                   | 20        |
+| 11.5                          | CB Data.....                              | 20        |
+| 11.6                          | Offset to Begin CTCH Block Set Index..... | 20        |
+| 11.7                          | Length of CBS Schedule Period.....        | 21        |
+| 11.8                          | New Message Bitmap.....                   | 21        |
+| 11.9                          | Message Description .....                 | 22        |
+| 11.10                         | Broadcast Address.....                    | 23        |
+| 11.11                         | CB Data41 .....                           | 23        |
+| 11.12                         | CBS Schedule Message Extension.....       | 24        |
+| 11.13                         | CBS Message Serial Numbers .....          | 24        |
+| 11.14                         | Serial Number List Entry .....            | 25        |
+| <b>Annex A (informative):</b> | <b>Change history.....</b>                | <b>26</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document provides the description of the Broadcast/Multicast Control Protocol (BMC). This protocol adapts broadcast and multicast services on the radio interface.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 25.322: "RLC Protocol Specification".
+- [2] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [3] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
+- [4] 3GPP TS 23.038: "Alphabets and Language".
+- [5] 3GPP TS 25.419: "UTRAN Iu interface: Service Area Broadcast Protocol SABP".
+- [6] 3GPP TS 25.925: "Radio Interface for Broadcast/Multicast Services".
+- [7] TTA/EIA-41-D: "Technical realization of Cell Broadcast Service (CBS)".
+- [8] TTA/EIA-637-A: "TR45 – Short Message Service for Spread Spectrum Systems".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**CB message:** user data as transmitted from Cell Broadcast Centre to UE (BMC SDU)
+
+**CB repetition period:** period after which a CB message should be broadcast again if more than one repetition are requested
+
+**Number of Broadcast Requested:** number of broadcasts requested for a CB message. This number is infinite or finite
+
+**DRX Schedule Period:** schedule period as optionally requested by the CBC (unit: seconds)
+
+**Reserved CB Capacity:** percentage of the capacity reserved for CB messages with category HIGH on the allocated radio resources CTCH, FACH and S-CCPCH. This parameter can be set optionally by the CBC.
+
+**CTCH Block Set:** subset of the transport block set of FACH on which the CTCH used for CBS is mapped uniquely
+
+**CBS schedule period:** finite sequence of CTCH Block Sets of variable length in which scheduled CB messages are broadcast
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                    |
+|---------|------------------------------------|
+| AS      | Access Stratum                     |
+| BMC     | Broadcast/Multicast Control        |
+| C-SAP   | Control Service Access Point       |
+| CBC     | Cell Broadcast Centre              |
+| CBS     | Cell Broadcast Service             |
+| CTCH    | Common Traffic Channel             |
+| CTCH-BS | CTCH Block Set                     |
+| FACH    | Forward Access Channel             |
+| IE      | Information Element                |
+| kbps    | kilo-bits per second               |
+| L1      | Layer 1 (physical layer)           |
+| L2      | Layer 2 (data link layer)          |
+| L3      | Layer 3 (network layer)            |
+| MAC     | Medium Access Control              |
+| NAS     | Non Access Stratum                 |
+| NSAPI   | Network layer Service Access Point |
+| PDCP    | Packet Data Convergence Protocol   |
+| RLC     | Radio Link Control                 |
+| RRC     | Radio Resource Control             |
+| UE      | User Equipment                     |
+
+# --- 4 General
+
+## 4.1 Model of BMC
+
+Broadcast/Multicast Control (BMC) is a sublayer of L2 that exists in the User-Plane only. It is located above RLC. The L2/BMC sublayer is assumed as transparent for all services except broadcast/multicast.
+
+Figure 4.1-1 shows the model of the L2/BMC sublayer within the UTRAN radio interface protocol architecture.
+
+At the UTRAN side, the BMC sublayer shall consist of one BMC protocol entity per cell. Each BMC entity requires a single CTCH, which is provided by the MAC sublayer, through the RLC sublayer. The BMC requests the Unacknowledged Mode service of the RLC.
+
+It is assumed that there is a function in the RNC above BMC that resolves the geographical area information of the CB message (or, if applicable, performs evaluation of a cell list) received from the Cell Broadcast Centre (CBC). A BMC protocol entity serves only those messages at BMC-SAP that are to be broadcast into a specified cell.
+
+![Figure 4.1-1: BMC protocol model diagram showing the stack of layers for BMC. At the top is a dashed box labeled 'user-plane'. Below it is an oval 'BMC-SAP' connected to the 'user-plane'. Below 'BMC-SAP' is a grey box 'L2/BMC sublayer' containing a white box 'BMC'. To the left of 'BMC' is an oval 'CBMC-SAP' connected to a grey box 'RRC'. Below 'BMC' is an oval 'UM'. Below 'UM' is a grey box 'L2/RLC sublayer' containing a white box 'RLC'. At the bottom is an oval 'CTCH-SAP' connected to 'RLC'.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+Figure 4.1-1: BMC protocol model diagram showing the stack of layers for BMC. At the top is a dashed box labeled 'user-plane'. Below it is an oval 'BMC-SAP' connected to the 'user-plane'. Below 'BMC-SAP' is a grey box 'L2/BMC sublayer' containing a white box 'BMC'. To the left of 'BMC' is an oval 'CBMC-SAP' connected to a grey box 'RRC'. Below 'BMC' is an oval 'UM'. Below 'UM' is a grey box 'L2/RLC sublayer' containing a white box 'RLC'. At the bottom is an oval 'CTCH-SAP' connected to 'RLC'.
+
+Figure 4.1-1: BMC protocol model
+
+# 5 Functions
+
+The functions are specified in [2]. They are:
+
+- Storage of Cell Broadcast Messages.
+- Traffic volume monitoring and radio resource request for CBS.
+- Scheduling of BMC messages.
+- Transmission of BMC messages to UE.
+- Delivery of Cell Broadcast messages to upper layer (NAS).
+
+# 6 Services provided to Upper Layers
+
+The BM-SAP provides a broadcast/multicast transmission service in the user plane on the radio interface for common user data in unacknowledged mode.
+
+The BMC sublayer interacts with other entities as illustrated in figure 1 of chapter 4. The interactions with the upper layer/U-plane and the RRC layer are specified in terms of primitives where the primitives represent the logical exchange of information and control between the BMC sublayer and higher layers. They do not specify or constrain implementations. The (adjacent) layers connect to each other through Service Access Points (SAPs).
+
+Three types of primitives are used for this document, as follows:
+
+- **REQUEST:**  
+This type is used when a higher layer is requesting a service from a lower layer.
+
+###### - **INDICATION:**
+
+This type is used by a lower layer providing a service to notify its higher layer of activities concerning that higher layer.
+
+###### - **CONFIRM:**
+
+This type is used by a lower layer providing the requested service to confirm to the higher layer that the activity has been completed.
+
+The primitives defined below are for communications between upper layer and BMC, as well as RRC and BMC in the same protocol stack.
+
+For the BMC sublayer two sets of primitives are defined.
+
+### - **Primitives between BMC and upper layer (U-plane):**
+
+BMC - Generic name - Type: Parameters.
+
+### - **Primitives between BMC and the RRC entity:**
+
+CBMC - Generic name - Type: Parameters.
+
+# 7 Services expected from RLC
+
+The BMC uses the unacknowledged mode service of the RLC sublayer.
+
+See [1] for details.
+
+# 8 Elements for layer-to-layer communication
+
+## 8.1 Service Primitives between RRC and BMC
+
+### 8.1.1 Primitives
+
+The primitives supported at CBMC-SAP between RRC and BMC are shown in Table 8.1.1-1.
+
+**Table 8.1.1-1: Primitives between BMC and RRC**
+
+| Generic Name         | Parameters            |
+|----------------------|-----------------------|
+| CBMC-Measurement-IND | CB-Traffic-Volume     |
+| CBMC-Rx-IND          | Action, DRX selection |
+| CBMC-Config-REQ      | CTCH configuration    |
+
+#### 8.1.1.1 CBMC-Measurement-IND
+
+The CBMC-Measurement-IND primitive is used by BMC to indicate the CB traffic volume.
+
+**Primitive Type:** indication.
+
+##### **Parameters:**
+
+CB-Traffic-Volume.
+
+#### 8.1.1.2 CBMC-Rx-IND
+
+The CBMC-Rx-IND primitive is used by BMC to indicate to RRC whether CB message reception shall start or stop and indicate when CB messages of interest are arriving in the next CBS schedule period.
+
+**Primitive Type:** indication.
+
+##### **Parameters:**
+
+Action.
+
+DRX selection.
+
+#### 8.1.1.3 CBMC-Config-REQ
+
+The CBMC-Config-REQ primitive is used by RRC to inform the BMC about the setting of the CTCH configuration.
+
+**Primitive Type:** indication.
+
+##### **Parameters:**
+
+CTCH configuration.
+
+### 8.1.2 Parameters
+
+#### 8.1.2.1 CB-Traffic-Volume
+
+Expected CTCH transmission rate [kbps].
+
+Value set: 0,1,...,32.
+
+#### 8.1.2.2 Action
+
+Start CBS reception.
+
+Stop CBS reception.
+
+#### 8.1.2.3 DRX selection
+
+List of absolute CTCH BS indices which are of interest and which should be received by Layer 1.
+
+#### 8.1.2.4 CTCH configuration
+
+Current CTCH-BS index,  $1 \leq i \leq 256$ .
+
+FACH identification.
+
+Transport Format Set of the allocated FACH (TB size, TBS size, TTI).
+
+Reserved CTCH transmission rate [kbps]: 0,1,...,32.
+
+## 8.2 Service Primitives between upper layer (U-plane) and BMC
+
+### 8.2.1 Primitives
+
+The primitives supported at BMC-SAP between BMC and upper layer (U-plane) are shown in Table 8.2.1-1.
+
+**Table 8.2.1-1: Primitives between BMC and upper layer**
+
+**Legend: [ ] optional parameters**
+
+| Generic Name         | Parameters                                                                                                                                                             |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| BMC-Data-REQ         | Message-ID,<br>[, Old-Serial-Number],<br>New-Serial-Number,<br>Data-Coding-Scheme,<br>CB-Data ,<br>[Category],<br>Repetition-Period,<br>Number-of-Broadcasts-Requested |
+| BMC-Data-IND         | Message-ID,<br>Serial-Number,<br>Data-Coding-Scheme,<br>CB-Data                                                                                                        |
+| BMC-Data-CNF         | Message-ID,<br>Serial-Number                                                                                                                                           |
+| BMC-Congestion-IND   |                                                                                                                                                                        |
+| BMC-Normal-IND       |                                                                                                                                                                        |
+| BMC-Activation-REQ   | Message-ID (n times)                                                                                                                                                   |
+| BMC-Deactivation-REQ | Message-ID (n times)                                                                                                                                                   |
+| BMC-DRX-REQ          | CB-DRX-Schedule-Period, Reserved-CB-Capacity                                                                                                                           |
+| BMC-Error-IND        | Cause                                                                                                                                                                  |
+| BMC-Data41-REQ       | Transport Layer Message,<br>Broadcast Address                                                                                                                          |
+| BMC-Data41-IND       | Transport Layer Message,                                                                                                                                               |
+| BMC-Error41-IND      | Error Type                                                                                                                                                             |
+
+#### 8.2.1.1 Primitives used in relation to UMTS Core Network
+
+##### 8.2.1.1.1 BMC-Data-REQ
+
+The BMC-Data-REQ primitive is used by upper layer to request repeated transmission of CB messages.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+Message-ID;  
+[Old-Serial-Number];  
+New-Serial-Number;  
+Data-Coding-Scheme;  
+CB-Data;  
+[Category];  
+Repetition-Period;  
+Number-of-Broadcasts-Requested.
+
+##### 8.2.1.1.2 BMC-Data-IND
+
+The BMC-Data-IND primitive is used to indicate received CB messages (i.e. CB Data) to upper layer.
+
+**Primitive Type:** indication.
+
+###### **Parameters:**
+
+Message-ID;  
+Serial-Number;  
+Data-Coding-Scheme;  
+CB-Data.
+
+##### 8.2.1.1.3 BMC-Data-CNF
+
+The BMC-Data-CNF primitive is used to indicate the complete broadcast of CB messages.
+
+**Primitive Type:** confirmation.
+
+###### **Parameters:**
+
+Message-ID.  
+Serial-Number.
+
+##### 8.2.1.1.4 BMC-Congestion-IND
+
+The BMC-Congestion-IND primitive is used to indicate to upper layer (BM-IWF) that the BMC entity is congested.
+
+**Primitive Type:** indication.
+
+**Parameters:** None.
+
+##### 8.2.1.1.5 BMC-Normal-IND
+
+The BMC-Normal-IND primitive is used to indicate to upper layer (BM-IWF) that the BMC has recovered from a congestion situation and is operating normal.
+
+**Primitive Type:** indication.
+
+**Parameters:** None.
+
+##### 8.2.1.1.6 BMC-Activation-REQ
+
+The BMC-Activation-REQ primitive is used to request CB message reception and to notify which CB messages are of interest and shall be delivered to the upper layer.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+Message-ID (n times).
+
+##### 8.2.1.1.7 BMC-Deactivation-REQ
+
+The BMC-Deactivation-REQ primitive is used to request stop of reception of listed CB messages. If no more CB messages are to be received, CB message reception shall stop.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+Message-ID (n times).
+
+##### 8.2.1.1.8 BMC-DRX-REQ
+
+The BMC-DRX-REQ primitive is used to command CBS discontinuous reception (CB DRX).
+
+NOTE: In UMTS, a Set DRX procedure is not requested for the CBC in TS 23.041. It is left to an O&M system to provide such a function or not.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+CB-DRX-Schedule-Period.
+
+Reserved-CB-Capacity.
+
+##### 8.2.1.1.9 BMC-Error-IND
+
+The BMC-Error-IND primitive is used to indicate unsuccessful operations of the BMC entity requested.
+
+**Primitive Type:** indication.
+
+###### **Parameters:**
+
+Cause.
+
+#### 8.2.1.2 Primitives used for ANSI-41 Core Network
+
+##### 8.2.1.2.1 BMC-Data41-REQ
+
+The BMC-Data41-REQ primitive is used by upper layer (Transport Layer) to request repeated transmission of CBS messages if the source is ANSI-41 core network.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+Transport Layer Message.
+
+Broadcast Address.
+
+##### 8.2.1.2.2 BMC-Data41-IND
+
+The BMC-Data-IND primitive is used to indicate received CB messages to upper layer (Transport Layer) if the source is ANSI-41 core network.
+
+**Primitive Type:** indication.
+
+###### **Parameters:**
+
+Transport Layer Message.
+
+Broadcast Address.
+
+##### 8.2.1.2.3 BMC-Error41-IND
+
+The BMC-Error-IND primitive is used to report BMC Layer Error to the upper layer (Transport Layer) if the source is ANSI-41 core network.
+
+**Primitive Type:** indication.
+
+###### **Parameters:**
+
+Error Type.
+
+### 8.2.2 Parameters
+
+#### 8.2.2.1 Message-ID
+
+Part of the CB message identification describing the source and type of a CB message.  
+ This parameter is described in [3].
+
+#### 8.2.2.2 Serial Number
+
+Part of the CB message identification describing variants of a CB message.  
+ This parameter is described in [3].
+
+#### 8.2.2.3 Data-Coding-Scheme
+
+Data coding scheme applied to the CB information.  
+ This parameter is described in [4] and [3].
+
+#### 8.2.2.4 CB-Data
+
+CB information to be broadcast.
+
+NOTE: The relation to GSM CBS pages can be found in [6] or [3].
+
+#### 8.2.2.5 Category
+
+Indicates the category (priority) of the CB message.
+
+Values:
+
+HIGH (CB message is to be broadcast at the earliest opportunity in the reserved CB capacity of the current CB DRX schedule period).
+
+NORMAL (default, CB messages to be broadcast according to the associated repetition period).
+
+BACKGROUND (CB message to be broadcast in the CB capacity not occupied by HIGH or NORMAL CB messages within a CB DRX schedule period).
+
+This parameter is described in [3].
+
+#### 8.2.2.6 Repetition-Period
+
+Indicates the period of time after which broadcast of the CB message should be repeated.  
+ This parameter is described in [3].
+
+NOTE: For GSM, the repetition period is a multiple of 1.883 seconds (cf. [3]).
+
+#### 8.2.2.7 Number-of-Broadcasts-Requested
+
+Number of times a CB message is to be broadcast.
+
+Values:
+
+0 indefinitely.
+
+n,  $1 \leq n \leq 65535$  finite number of times to be broadcast.
+
+This parameter is described in [3].
+
+#### 8.2.2.8 CB-DRX-Schedule-Period
+
+Indication of the CB DRX schedule period length.
+
+#### 8.2.2.9 Reserved-CB-Capacity
+
+Indicates the capacity reserved for CB messages with Category = HIGH or new CB messages.
+
+#### 8.2.2.10 Cause
+
+CB message already stored.
+
+Old CB message not stored.
+
+#### 8.2.2.11 Transport Layer Message
+
+This parameter is described in [8].
+
+#### 8.2.2.12 Broadcast Address
+
+This parameter is described in [8].
+
+#### 8.2.2.13 Error Type
+
+The error codes shall be SMS\_CauseCode values as defined in the SMS\_CauseCode Table in [7].
+
+# --- 9 Procedures
+
+## 9.1 BMC Message Broadcast
+
+![Sequence diagram showing the procedure for broadcast of BMC messages. A UE (User Equipment) box is on the left and a UTRAN (UMTS Radio Access Network) box is on the right. A horizontal arrow labeled 'BMC message' points from the UTRAN box to the UE box. Vertical lines extend downwards from both boxes, representing their lifelines.](57f8e374b0e99c488f68c46b713ffc64_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant UTRAN
+    Note left of UE: UE
+    Note right of UTRAN: UTRAN
+    UTRAN->>UE: BMC message
+```
+
+Sequence diagram showing the procedure for broadcast of BMC messages. A UE (User Equipment) box is on the left and a UTRAN (UMTS Radio Access Network) box is on the right. A horizontal arrow labeled 'BMC message' points from the UTRAN box to the UE box. Vertical lines extend downwards from both boxes, representing their lifelines.
+
+**Figure 9.1-1: Procedure for broadcast of BMC messages**
+
+This procedure is used for broadcasting BMC messages from the network to UEs in a cell. A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in the Idle mode and in CELL\_PCH and URA\_PCH RRC-states of Connected mode.
+
+Three types of BMC messages are identified: CBS Message, CBS41 Message and Schedule Message.
+
+## 9.2 Generation of Schedule message
+
+NOTE: Principles and examples are described in [6].
+
+This procedure calculates the CBS schedule periods and assigns BMC messages (i.e. CBS Messages, CBS41 Messages and Schedule Messages) to the CBS schedule periods and gives an indication which of the CTCH Block Sets containing a part of or a complete BMC messages has the status "new".
+
+NOTE: The concatenation function of RLC shall not be applied. RLC Length Indicators shall not be concatenated with RLC SDUs they do not refer to.
+
+Algorithms used for scheduling are implementation dependent and thus do not need to be specified. Some parameters may be set by CBC or O&M system.
+
+CTCH Block Sets are indicated in a New Message Bitmap IE of BMC Schedule Message as new (bit position of a CTCH Block Set is set to value "1") when one of the following conditions is met:
+
+The CTCH Block Set contains part of or a complete BMC message which was either not sent during the previous CBS schedule period, or sent unscheduled during the preceding CBS schedule period; or, the CTCH Block Set is indicated as of free usage, reading advised, or it contains the Schedule Message partly or complete of the following CBS schedule period, or it contains a CBS41 Message partly or complete.
+
+Other BMC messages sent in the same CBS schedule messages are indicated as "old" (bit position of CTCH Block Set containing this message partly or complete is set to value 0).
+
+The indication "new" is set both for the first transmission of a BMC message in the CBS schedule period or a repetition of it within the CBS schedule period. For CBS41 Messages, repetition is not specified.
+
+The input parameters of the scheduling procedure are set by CBC or RRC or by the O&M system for the BMC.
+
+The CBC input parameters are:
+
+CB messages (i.e. BMC SDUs),  
+Message Identifier per CB message,  
+Serial Number per CB message,  
+CB repetition period per CB message,  
+Number of Broadcast Requested per CB message.
+
+The RRC input parameters are:
+
+Sizes of CTCH Block Sets,  
+Timing of CTCH Block Set sequence.
+
+The O&M (BMC) input parameters are:
+
+DRX Schedule Period (cell related parameter) requested optionally,  
+Reserved CB Capacity (cell related parameter) requested optionally.
+
+## 9.3 Traffic volume measurement
+
+The BMC entity on the network side predicts periodically the expected amount of CBS traffic volume (unit: kbps) that is needed for transmission of CB messages currently and indicates this to RRC.
+
+The algorithms used for traffic volume prediction are implementation dependent and thus do not need to be specified. Some parameters may be set by O&M system. The algorithms depend on the chosen algorithms for CB message scheduling (cf. subclause 9.2).
+
+## 9.4 BMC message reception
+
+The BMC entity on the UE side evaluates received BMC Schedule Messages and takes decisions which BMC messages should be received. The reception of a BMC message is indicated to RRC if the CTCH Block Sets carrying this BMC message are indicated as new. If the upper layer has requested reception of individual CB messages when in status "old", the reception of these BMC messages are also indicated to RRC.
+
+If not otherwise requested by upper layers, only those CB messages received in BMC CBS Messages should be delivered to upper layers for which the Serial Number associated with the CB message has changed. This implies that the BMC has to store the last received Serial Number of each CB message activated by upper layers.
+
+Every CBS41 Message received by BMC shall be delivered to upper layer.
+
+# 10 BMC Messages
+
+## 10.1 General
+
+A BMC message is equivalent with a BMC PDU. There are three types of BMC messages defined, CBS messages and CBS41 messages, which carry cell broadcast data from higher layer, and *Schedule messages*, which provide information for support of Discontinuous Reception (DRX) of cell broadcast data at the UE.
+
+BMC messages and information elements are specified using the tabular format methodology as specified in TR 25.921, and additional text is describing the encoding.
+
+NOTE: Only IEs marked as MP or CV in the "Need" column exist, with the exception of the IE "BMC Schedule Message Extension" of the BMC Schedule Message (see subclause 10.3).
+
+BMC messages (i.e. BMC PDUs) specified by tabular format consist of an ordered sequence IE1,...,IEn of information element fields.
+
+The octet string of a BMC message is defined as the concatenation of the octets of the IEs maintaining the sequence order. The bits within an octet are numbered 0 to 7; bit 0 is the least significant bit and is transmitted first. The octets are transmitted in order of increasing octet number, i.e. starting with octet 1. This means that bit 0 of octet 1 is transmitted as the first (leftmost) bit in the Data field of the UMD PDU [1].
+
+The UE shall ignore any unrecognised bits at the end of a BMC message.
+
+NOTE: Although not explicitly stated as a requirement in release '99, 4 and 5 specifications it is assumed that release '99, 4, 5 UEs will also ignore any unrecognised bits at the end of a BMC message.
+
+## 10.2 BMC CBS Message
+
+The CBS Message carries the cell broadcast data and the address information if the address information is based on GSM CBS.
+
+RLC-SAP: UM;
+
+Logical channel: CTCH;
+
+Direction: UTRAN → UE.
+
+**Table 10.2-1: CBS Message**
+
+| Information Element | Need | Multi | Type and reference | Semantics description |
+|---------------------|------|-------|--------------------|-----------------------|
+| Message Type        | MP   |       | Sec. 11.1          |                       |
+| Message ID          | MP   |       | Sec. 11.2          |                       |
+| Serial Number       | MP   |       | Sec. 11.3          |                       |
+| Data Coding Scheme  | MP   |       | Sec. 11.4          |                       |
+| CB Data             | MP   |       | Sec. 11.5          |                       |
+
+## 10.3 BMC Schedule Message
+
+The BMC Schedule Message describes for the succeeding CBS schedule period the time locations for each CBS Message and the location of the Schedule Message of the following CBS schedule period. The UE is not required to start receiving a CBS Schedule Period earlier than 100ms after UE has received the complete BMC Schedule message.
+
+RLC-SAP: UM.
+
+Logical channel: CTCH.
+
+Direction: UTRAN → UE.
+
+Table 10. 3-1: Schedule Message
+
+| Information Element             | Need | Multi                                  | Type and reference | Semantics description                                                                                                                                                                                                                                                                                                                                                                                                                                 | Version |
+|---------------------------------|------|----------------------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Message Type                    | MP   |                                        | Sec. 11.1          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| Offset to Begin CTCH BS index   | MP   |                                        | Sec. 11.6          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| Length of CBS Scheduling Period | MP   |                                        | Sec. 11.7          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| New Message Bitmap              | MP   |                                        | Sec. 11.8          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| Message Description             | MP   | 1 to <Length of CBS Scheduling Period> | Sec. 11.9          | Message Description IE is included for each new message (1 in the New message bitmap) as well as for each old message (0 in the New message bitmap). The i-th Message Description IE refers to the i-th bit in the New Message Bitmap IE. The multiplicity for the IE "Message Description" does not require an additional length indication in the encoded message. The multiplicity shall be derived from the IE "Length of CBS Scheduling Period". |         |
+| BMC Schedule Message Extension  | OP   |                                        | Sec 11.12          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       | REL-6   |
+
+The IE "BMC Schedule Message Extension" is optional. There is no explicit mechanism to indicate the presence of this IE in the BMC Schedule Message.
+
+## 10.4 BMC CBS41 Message
+
+The CBS41 Message carries the cell broadcast data and the address information if the address information is based on ANSI-41 CBS.
+
+RLC-SAP: UM.
+
+Logical channel: CTCH.
+
+Direction: UTRAN → UE.
+
+Table 10.4-1: CBS41 Message
+
+| Information Element | Need | Multi | Type and reference | Semantics description |
+|---------------------|------|-------|--------------------|-----------------------|
+| Message Type        | MP   |       | Sec. 11.1          |                       |
+| Broadcast Address   | MP   |       | Sec. 11.10         |                       |
+| CB Data41           | MP   |       | Sec. 11.11         |                       |
+
+# 11 Information Elements
+
+## 11.1 Message Type
+
+Table 11.1-1: Message Type IE
+
+| IE/Group name | Need | Multi | Type and reference                    | Semantics description                                                                                     |
+|---------------|------|-------|---------------------------------------|-----------------------------------------------------------------------------------------------------------|
+| Message Type  | MP   |       | Enumerated (0 .. 255)<br>Table 11.1-2 | This IE is coded as the binary representation of the Message Type. This IE is mapped onto a single octet. |
+
+Coding of Message Type
+
+Table 11.1-2: Coding of Message Type IE
+
+|            |                                                                                                   |
+|------------|---------------------------------------------------------------------------------------------------|
+| 1          | CBS Message                                                                                       |
+| 2          | Schedule Message                                                                                  |
+| 3          | CBS41 Message                                                                                     |
+| 0, 4.. 255 | Reserved for future use (PDUs with this coding will be discarded by this version of the protocol) |
+
+## 11.2 Message ID
+
+Table 11.2-1: Message ID IE
+
+| IE/Group name | Need | Multi | Type and reference | Semantics description                                                                                                                                      |
+|---------------|------|-------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Message ID    | MP   |       | Octet string (2)   | Identification of source and type of CBS message. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on. |
+
+## 11.3 Serial Number
+
+Table 11.3-1: Serial Number IE
+
+| IE/Group Name | Need | Multi | Type and reference | Semantics description                                                                                                                                                                                    |
+|---------------|------|-------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Serial Number | MP   |       | Octet string (2)   | Identification of variations of a CBS message (part of the overall CBS message identification). The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on. |
+
+## 11.4 Data Coding Scheme
+
+Table 11.4-1: Data Coding Scheme IE
+
+| IE/Group name      | Need | Multi | Type and reference | Semantics description                                                                                   |
+|--------------------|------|-------|--------------------|---------------------------------------------------------------------------------------------------------|
+| Data Coding Scheme | MP   |       | Bitstring(8)       | Identification of the alphabet/coding and the language applied.<br>This IE is encoded according to [4]. |
+
+## 11.5 CB Data
+
+Table 11.5-1: CB Data IE
+
+| IE/Group name | Need | Multi | Type and reference             | Semantics description                                                                                                                                                                                                                                                                     |
+|---------------|------|-------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CB Data       | MP   |       | Octet string (N)<br>$N \geq 1$ | Content of CBS message. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [4] and so on.<br>NOTE: This IE contains the CB Data as received in the SABP with the length indicator of the PER aligned bit string as received on SABP being removed. |
+
+NOTE: The number N is less than or equal to 1246 octets if a GSM CBS message is broadcast.
+
+## 11.6 Offset to Begin CTCH Block Set Index
+
+Table 11.6-1: Offset to Begin CTCH Block Set Index IE
+
+| IE/Group name                 | Need | Multi | Type and reference  | Semantics description                                                                                                                                                                                                                                                                                       |
+|-------------------------------|------|-------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Offset to Begin CTCH BS Index | MP   |       | Integer<br>(1..255) | Pointer to the first CTCH BS of the next CBS Schedule Period relative to the CTCH BS index of the first part of the current BMC Schedule Message.<br>This IE is coded as the binary representation of the Offset to Begin CTCH BS Index. This IE is mapped onto a single octet.<br>The value 0 is reserved. |
+
+## 11.7 Length of CBS Schedule Period
+
+Table 11.7-1: Length of CBS Schedule Period IE
+
+| Information Element/Group name | Need | Multi | Type and reference | Semantics description                                                                                                                                                                                                                                                                                                 |
+|--------------------------------|------|-------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Length of CBS Schedule Period  | MP   |       | Integer (1..255)   | Number of consecutive CTCH BS of the next CBS Schedule Period. Together with Offset to Begin CTCH BS Index it points to the end of the CBS schedule period.<br>This IE is coded as the binary representation of the Length of CBS Schedule Period. This IE is mapped onto a single octet.<br>The Value 0 is reserved. |
+
+## 11.8 New Message Bitmap
+
+Table 11.8-1: New Message Bitmap IE
+
+| Information Element/Group name | Need | Multi | Type and reference                                                                                                                                                                                | Semantics description                                                          |
+|--------------------------------|------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| New Message Bitmap             | MP   |       | Octet string (N)<br><br>if "Length of CBS Schedule Period" mod 8 = 0 then<br>N = "Length of CBS Schedule Period" div 8,<br>else<br>N = "Length of CBS Schedule Period" div 8 + 1.<br>Table 11.8-2 | Bitmap indicating CTCH BS which contains new CBS Messages completely or partly |
+
+Coding of New Message Bitmap.
+
+Table 11.8-2: Coding of New Message Bitmap IE
+
+| 0                                                                                                                                                                                       | 1                 | 2                 | 3               | 4 | 5 | 6 | 7 | Bit     |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------|-----------------|---|---|---|---|---------|
+| CTCH BS index B                                                                                                                                                                         | CTCH BS index B+1 | CTCH BS index B+2 | ...             |   |   |   |   | Octet 1 |
+|                                                                                                                                                                                         |                   |                   |                 |   |   |   |   | Octet 2 |
+|                                                                                                                                                                                         |                   |                   |                 |   |   |   |   | ...     |
+|                                                                                                                                                                                         | ...               | CTCH BS index E-1 | CTCH BS index E | 0 | 0 | 0 | 0 | Octet n |
+| Legend: B First CTCH BS index of the CBS schedule period, $1 \leq B \leq 256$<br>E Last CTCH BS index of the CBS schedule period,<br>$E = B + \text{Length of CBS Schedule Period} - 1$ |                   |                   |                 |   |   |   |   |         |
+
+CTCH BS Index i:
+
+Each bit of the New CBS Message Bitmap refers to the content of CTCH BS index i,  $i=B, \dots, E$ . Its meaning is as follows:
+
+- 1 The CTCH BS index i contains a BMC Message partly or completely which was either not sent during the previous schedule period, or sent unscheduled during the preceding schedule period; or, the CTCH BS is indicated as of free usage, reading advised; or it contains the Schedule Message partly or complete of the following CBS schedule period, or it contains a CBS41 Message partly or complete. The value is 1 both for the first transmission of a given BMC message in the CBS schedule period or a repetition of it within the CBS schedule period.
+- 0 The CTCH BS is such that value 1 is not suitable.
+
+The length of the New Message Bitmap is given by the IE Length of CBS Schedule Period. If it is not a multiple of 8 the remaining bit positions are padded with "0".
+
+## 11.9 Message Description
+
+**Table 11.9-1: Message Description IE**
+
+| IE/Group Name                                 | Need    | Multi | Type and reference                     | Semantics description                                                                                                                                                                       |
+|-----------------------------------------------|---------|-------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Message Description Type                      | MP      |       | Enumerated(0..255)<br><br>Table 11.9-3 | This IE is coded as the binary representation of the Message Description Type. This IE is mapped onto a single octet.                                                                       |
+| Message ID                                    | CV MDT1 |       | Octet string (2)                       | This IE is coded as the binary representation of the Message ID. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on.                   |
+| Offset to CTCH BS index of first transmission | CV MDT2 |       | Integer (0..255)                       | This IE is coded as the binary representation of the Offset to CTCH BS index of first transmission relative to the start of the BMC schedule period. This IE is mapped onto a single octet. |
+
+**Table 11.9-2: Conditions**
+
+| Condition | Explanation                                                                                                                                                                                                               |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MDT1      | If Message Description Type = 1 or 5 then: the CB-Message-Id IE is included                                                                                                                                               |
+| MDT2      | If Message Description Type = 0 or 4 then: the Offset to CTCH BS index of first transmission IE is included pointing to the CTCH BS index where the BMC message is transmitted the first time within the schedule period. |
+
+**Table 11.9-3: Encoding of Message Description Type**
+
+| Value   | Explanation                                                                              |
+|---------|------------------------------------------------------------------------------------------|
+| 0       | Repetition of new BMC CBS message within schedule period                                 |
+| 1       | New BMC CBS message (a BMC CBS message never previously sent)                            |
+| 2       | Reading advised                                                                          |
+| 3       | Reading optional                                                                         |
+| 4       | Repetition of old BMC CBS message within schedule period                                 |
+| 5       | Old BMC CBS message (repetition of a BMC CBS message sent in a previous schedule period) |
+| 6       | Schedule message                                                                         |
+| 7       | CBS41 message                                                                            |
+| 8       | no message                                                                               |
+| 9.. 255 | Reserved for future use<br>(IEs received with this value will be replaced by value 3)    |
+
+NOTE: Message Description Type values 0, 1, 4, 5 and 6 indicate transmission of a BMC message partly or completely.
+
+## 11.10 Broadcast Address
+
+**Table 11.10-1: Data Coding Scheme IE**
+
+| IE/Group name     | Need | Multi | Type and reference | Semantics description                                                                                                                          |
+|-------------------|------|-------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| Broadcast Address | MP   |       | Octet string (5)   | Address information for higher layer. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [8] and so on. |
+
+## 11.11 CB Data41
+
+**Table 11.11-1: CB Data IE**
+
+| IE/Group name | Need | Multi | Type and reference             | Semantics description                                                                                                                      |
+|---------------|------|-------|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| CB Data41     | MP   |       | Octet string (N)<br>$N \geq 1$ | Content of CBS message (ANSI-41). The first octet contains octet 1 of the equivalent IE defined in and encoded according to [8] and so on. |
+
+## 11.12 CBS Schedule Message Extension
+
+Table 11.12-1: CBS Schedule Message Extension IE
+
+| Information Element     | Need    | Multi | Type and reference                   | Semantics description | Version |
+|-------------------------|---------|-------|--------------------------------------|-----------------------|---------|
+| Future extension bitmap | MP      |       | Octet string(1)                      |                       | REL-6   |
+| Extension 0             | CV ext0 |       | CBS Message Serial Numbers Sec 11.13 |                       | REL-6   |
+| Extension 1             | CV ext1 |       | Null                                 |                       | REL-6   |
+| Extension 2             | CV ext2 |       | Null                                 |                       | REL-6   |
+| Extension 3             | CV ext3 |       | Null                                 |                       | REL-6   |
+| Extension 4             | CV ext4 |       | Null                                 |                       | REL-6   |
+| Extension 5             | CV ext5 |       | Null                                 |                       | REL-6   |
+| Extension 6             | CV ext6 |       | Null                                 |                       | REL-6   |
+| Extension 7             | CV ext7 |       | Null                                 |                       | REL-6   |
+
+Table 11.12-2: Conditions
+
+| Condition | Explanation                                                                                                                                                                                          |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| extn      | If bit <i>n</i> of the Future extension bitmap is set to 1 then Extension <i>n</i> is present.<br>If bit <i>n</i> of the Future extension bitmap is set to 0 then Extension <i>n</i> is not present. |
+
+## 11.13 CBS Message Serial Numbers
+
+Table 11.13: CBS Message Serial Numbers IE
+
+| Information Element          | Need | Multi                              | Type and reference | Semantics description | Version |
+|------------------------------|------|------------------------------------|--------------------|-----------------------|---------|
+| Length of Serial Number List | MP   |                                    | Integer (0..255)   |                       | REL-6   |
+| Serial Number List Entry     | MP   | 0 to <Length of Serial Number List | Sec. 11.14         |                       | REL-6   |
+
+## 11.14 Serial Number List Entry
+
+**Table 11.14: Serial Number List Entry IE**
+
+| Information Element | Need | Multi | Type and reference | Semantics description                                                                                                                                                                                                                                            | Version |
+|---------------------|------|-------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Serial Number       | MP   |       | Sec. 11.3          | The CBS Message Serial Number of the BMC CBS Message referred to by the CTCH BS Index.                                                                                                                                                                           | REL-6   |
+| CTCH BS Index       | MP   |       | Integer (0..255)   | <p>The CTCH BS Index IE indicates the index of the CTCH BS within the BMC Schedule Period which contains the start of the BMC CBS Message.</p> <p>This IE is coded as the binary representation of the CTCH BS Index. This IE is mapped onto a single octet.</p> | REL-6   |
+
+# Annex A (informative): Change history
+
+| Change history |        |           |      |     |     |                                                                                           |             |
+|----------------|--------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------|-------------|
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Cat | Subject/Comment                                                                           | New version |
+| 12/1999        | RP-06  | RP-99647  | -    |     |     | Approved at TSG-RAN #6 and placed under Change Control                                    | 3.0.0       |
+| 03/2000        | RP-07  | RP-000042 | 001  |     |     | Miscellaneous corrections                                                                 | 3.1.0       |
+|                | RP-07  | RP-000042 | 002  | 2   |     | Correction of messages and bit ordering                                                   | 3.1.0       |
+| 09/2000        | RP-09  | RP-000360 | 005  |     |     | Corrections                                                                               | 3.2.0       |
+| 12/2000        | RP-10  | RP-000569 | 006  | 1   |     | Correction to ANSI-41 Cell Broadcast Service                                              | 3.3.0       |
+| 03/2001        | RP-11  | RP-010028 | 007  |     |     | Corrections                                                                               | 3.4.0       |
+|                | RP-11  | -         | -    |     |     | Upgrade to Release 4 - no technical change                                                | 4.0.0       |
+| 03/2002        | RP-15  | -         | -    |     |     | Upgrade to Release 5 - no technical change                                                | 5.0.0       |
+| 06/2002        | RP-16  | RP-020329 | 010  |     |     | Clarification on BMC message encoding                                                     | 5.1.0       |
+| 12/2002        | RP-18  | RP-020720 | 013  | 1   |     | Bit order in BMC messages                                                                 | 5.2.0       |
+| 03/2003        | RP-19  | RP-030102 | 016  | 1   |     | Maximum size of BMC PDU                                                                   | 5.3.0       |
+| 12/2003        | RP-22  | -         | -    |     |     | Upgrade to Release 6 - no technical changes                                               | 6.0.0       |
+| 06/2004        | RP-24  | RP-040202 | 020  |     |     | Corrections to BMC Schedule message                                                       | 6.1.0       |
+| 12/2004        | RP-26  | RP-040476 | 024  | 1   |     | Correction of BMC message bit order and IE coding                                         | 6.2.0       |
+| 06/2005        | RP-28  | RP-050319 | 0025 |     |     | Clarification of RLC concatenation procedure with BMC                                     | 6.3.0       |
+| 09/2005        | RP-29  | RP-050464 | 0027 | 1   |     | Cell Broadcast                                                                            | 6.4.0       |
+| 03/2006        | RP-31  | RP-060090 | 0028 |     |     | Introduction of Serial Number in BMC Schedule Message                                     | 6.5.0       |
+|                | RP-31  | -         | -    |     |     | Upgrade to Release 7 - no technical changes                                               | 7.0.0       |
+| 06/2006        | RP-32  | RP-060363 | 0030 |     |     | Interpretation of "Offset to CTCH BS index of first transmission" in BMC Schedule message | 7.1.0       |
+| 12/2007        | RP-38  | -         | -    |     |     | Upgrade to the Release 8 - no technical change                                            | 8.0.0       |
+| 12/2009        | RP-46  | -         | -    |     |     | Upgrade to the Release 9 - no technical change                                            | 9.0.0       |
+| 03/2011        | RP-51  | -         | -    | -   |     | Upgrade to the Release 10 - no technical change                                           | 10.0.0      |
+| 09/2012        | RP-57  | -         | -    | -   |     | Upgrade to the Release 11 - no technical change                                           | 11.0.0      |
+| 09/2014        | RP-65  | -         | -    | -   |     | Upgrade to the Release 12 - no technical change                                           | 12.0.0      |
+| 12/2015        | RP-70  | -         | -    | -   |     | Upgrade to the Release 13 - no technical change                                           | 13.0.0      |
+| 03/2017        | RP-75  | -         | -    | -   |     | Upgrade to Release 14 - no technical change                                               | 14.0.0      |
+| 06/2018        | RP-80  | -         | -    | -   |     | Upgrade to Release 15 - no technical change                                               | 15.0.0      |
+| 2020-07        | RP-88e | -         | -    | -   | -   | Upgrade to Rel-16 version without technical change                                        | 16.0.0      |
+| 2022-03        | RP-95e | -         | -    | -   | -   | Upgrade to Rel-17 version without technical change                                        | 17.0.0      |
+| 2024-03        | RP-103 | -         | -    | -   | -   | Upgrade to Rel-18 version without technical change                                        | 18.0.0      |

marked/Rel-18/25_series/25327/raw.md

@@ -0,0 +1,175 @@
+
+
+# 3GPP TS 25.327 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; High Speed Packet Access (HSPA); Requirements on User Equipments (UEs) supporting a release-independent frequency band and multi-carrier configuration (Release 18)** ---
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo features the letters '3GPP' in a stylized, bold, black font. The '3' is a thick, curved line. The 'G' is a thick, curved line. The 'P' is a thick, vertical line with a loop. The 'P' has a small red signal icon below it, consisting of three curved lines of increasing height. To the right of the 'P' is a small 'TM' symbol.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+## --- **Keywords**
+
+UMTS, radio
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                          |          |
+|----------------------------------------------------------|----------|
+| Foreword .....                                           | 4        |
+| 1 Scope.....                                             | 5        |
+| 2 References.....                                        | 5        |
+| 3 Definitions, symbols and abbreviations .....           | 5        |
+| 3.1 Definitions.....                                     | 5        |
+| 3.2 Abbreviations .....                                  | 5        |
+| 4 DB-DC-HSDPA configurations independent of release..... | 6        |
+| 4.1 Void.....                                            | 6        |
+| 4.2 Void.....                                            | 6        |
+| 4.3 Void.....                                            | 6        |
+| 5 4C-HSDPA configurations independent of release .....   | 6        |
+| 5.1 Single-band contiguous configurations.....           | 6        |
+| 5.1.1 Void .....                                         | 6        |
+| 5.1.2 Void .....                                         | 6        |
+| 5.2 Dual-band configurations .....                       | 6        |
+| 5.2.1 Void .....                                         | 6        |
+| 5.2.2 Void .....                                         | 6        |
+| 5.2.3 Void .....                                         | 6        |
+| 5.2.4 Void .....                                         | 6        |
+| 5.2.5 Void .....                                         | 6        |
+| 6 8C-HSDPA configurations independent of release .....   | 6        |
+| <b>Annex A (informative): Change history.....</b>        | <b>7</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies requirements on UEs supporting a DB-DC-HSDPA, 4C-HSDPA, and 8C-HSDPA configuration that is independent of release. TSG-RAN has agreed that the standardisation of new configurations may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a configuration that is specified in a later release, it is necessary to specify some extra requirements.
+
+For example, Band I-XI combination for DB-DC-HSDPA (referred to as DB-DC-HSDPA configuration 4 in [2]) is contained in the Release 10 specifications. In order to implement a UE conforming to Release 9 but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 10 specifications, such as the radio frequency and radio resource management requirements for the configuration.
+
+Similarly, 4C-HSDPA configuration I-3 is contained in the Release 11 specification [3]. In order to implement a UE conforming to Release 10, but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 11 specifications.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.101 (Release 10): "User Equipment (UE) radio transmission and reception (FDD)".
+- [3] 3GPP TS 25.101 (Release 11): "User Equipment (UE) radio transmission and reception (FDD)".
+- [4] Void
+- [5] Void
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|             |                           |
+|-------------|---------------------------|
+| DB-DC-HSDPA | Dual Band Dual Cell HSDPA |
+| 4C-HSDPA    | Four-carrier HSDPA        |
+| 8C-HSDPA    | Eight-carrier HSDPA       |
+
+# --- 4 DB-DC-HSDPA configurations independent of release
+
+4.1 Void
+
+4.2 Void
+
+4.3 Void
+
+# --- 5 4C-HSDPA configurations independent of release
+
+5.1 Single-band contiguous configurations
+
+5.1.1 Void
+
+5.1.2 Void
+
+5.2 Dual-band configurations
+
+5.2.1 Void
+
+5.2.2 Void
+
+5.2.3 Void
+
+5.2.4 Void
+
+5.2.5 Void
+
+# --- 6 8C-HSDPA configurations independent of release
+
+# Annex A (informative): Change history
+
+| Change history |        |           |      |     |     |                                                                 |             |
+|----------------|--------|-----------|------|-----|-----|-----------------------------------------------------------------|-------------|
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Cat | Subject/Comment                                                 | New version |
+| 2013-11        |        |           |      |     |     | Skeleton report based on 25.317 contents                        | 1.0.0       |
+| 2013-12        | RP-62  | RP-131629 |      |     |     | TS 25.327 approved by RAN #62                                   | 9.0.0       |
+|                | RP-62  | RP-131980 | 0002 | 1   |     | Introduction of TS 25.327                                       | 11.0.0      |
+| 2014-03        | RP-63  | -         | -    | -   |     | Introduction of TS 25.327 REL-12                                | 12.0.0      |
+| 2014-06        | RP-64  | RP-140872 | 0009 | -   |     | Introduction of the new band combinations related to Band XXXII | 12.1.0      |
+| 2015-12        | RP-70  | -         | -    | -   |     | Upgrade to the Release 13 - no technical change                 | 13.0.0      |
+| 2017-03        | RP-75  | -         | -    | -   |     | Upgrade to Release 14 - no technical change                     | 14.0.0      |
+| 2018-06        | RP-80  |           |      |     |     | Upgrade to Release 15 - no technical change                     | 15.0.0      |
+| 2020-07        | RP-88e | -         | -    | -   | -   | Upgrade to Rel-16 version without technical change              | 16.0.0      |
+| 2022-03        | RP-95e | -         | -    | -   | -   | Upgrade to Rel-17 version without technical change              | 17.0.0      |
+| 2024-03        | RP-103 | -         | -    | -   | -   | Upgrade to Rel-18 version without technical change              | 18.0.0      |

marked/Rel-18/25_series/25412/raw.md

@@ -0,0 +1,345 @@
+
+
+# 3GPP TS 25.412 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface signalling transport (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the letters is a red signal wave icon, and below that, the text 'A GLOBAL INITIATIVE' in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                               |                                                     |           |
+|-------------------------------|-----------------------------------------------------|-----------|
+| 1                             | Scope.....                                          | 5         |
+| 2                             | References.....                                     | 5         |
+| 3                             | Abbreviations.....                                  | 6         |
+| 4                             | Data Link Layer .....                               | 7         |
+| 4.1                           | ATM Transport Option .....                          | 7         |
+| 4.2                           | IP Transport Option.....                            | 7         |
+| 5                             | RANAP Signalling Bearer .....                       | 7         |
+| 5.1                           | Introduction .....                                  | 7         |
+| 5.2                           | Signalling Bearer for Circuit Switched Domain ..... | 7         |
+| 5.2.1                         | Protocol Stack for the CS Domain .....              | 7         |
+| 5.2.2                         | ATM Transport Option.....                           | 8         |
+| 5.2.3                         | IP Transport Option.....                            | 8         |
+| 5.3                           | Signalling Bearer for Packet Switched Domain.....   | 9         |
+| 5.3.1                         | Protocol Stack for the PS Domain.....               | 9         |
+| 5.3.2                         | ATM Transport Option 1 .....                        | 9         |
+| 5.3.3                         | ATM Transport Option 2.....                         | 10        |
+| 5.3.4                         | IP Transport Option.....                            | 10        |
+| 5.4                           | Services Provided by the Signalling Bearer.....     | 10        |
+| <b>Annex A (informative):</b> | <b>Change History.....</b>                          | <b>11</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the standards for Signalling Transport to be used across Iu Interface. Iu Interface is a logical interface between the RNC and the UTRAN Core Network. The present document describes how the RANAP signalling messages are transported over Iu.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] ITU-T Recommendation Q.2100 (1994-07): "B-ISDN Signalling ATM Adaptation Layer (SAAL) - overview description".
+- [2] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM Adaptation Layer – Service Specific Connection Oriented Protocol (SSCOP)".
+- [3] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer – Service Specific Co-ordination Function for signalling at the Network Node Interface (SSCF AT NNI)".
+- [4] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".
+- [5] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [6] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Type 5".
+- [7] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [8] ITU-T Recommendation Q.712 (1996-07): "Definition and function of Signalling connection control part messages".
+- [9] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [10] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [11] ITU-T Recommendation Q.715 (1996-07): "Signalling connection control part user guide".
+- [12] ITU-T Recommendation Q.716 (1993-03): "Signalling Connection Control Part (SCCP) performance".
+- [13] IETF RFC 791 (1981-09): "Internet Protocol".
+- [14] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".
+- [15] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM".
+- [16] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol".
+- [17] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)"
+
+- [18] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles".
+- [19] IETF RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)".
+- [20] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [21] IETF RFC 2507 (1999-02): "IP header compression".
+- [22] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [23] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [24] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [25] IETF RFC 2460 (1996-12): "Internet Protocol, Version 6 (Ipv6) Specification".
+- [26] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [27] Void.
+- [28] IETF RFC 3031 (2001-01): "MPLS".
+- [29] IETF RFC 3153 (2001-08): "PPPmultiplexing".
+- [30] IETF RFC 3309 (2002-09): "SCTP Checksum Change".
+- [31] ANSI T1.111-2001: "Signalling System Number 7 (SS7) - Message Transfer Part (MTP)".
+- [32] ANSI T1.112-2001: "Signalling System Number 7 (SS7) -- Signalling Connection Control Part (SCCP)".
+- [33] ANSI T1.645-1995 (R2003), "B-ISDN Signaling ATM Adaptation Layer - Service Specific Coordination Function for Support of Signaling at the Network Node Interface (SSCF at the NNI)".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|           |                                                          |
+|-----------|----------------------------------------------------------|
+| AAL       | ATM Adaptation Layer                                     |
+| AAL2      | ATM Adaptation Layer 2                                   |
+| AAL5      | ATM Adaptation Layer 5                                   |
+| ATM       | Asynchronous Transfer Mode                               |
+| CS        | Circuit Switched                                         |
+| DiffServ  | Differentiated Services                                  |
+| HDLC      | High Level Data Link Control                             |
+| IP        | Internet Protocol                                        |
+| M3UA      | SS7 MTP3 User Adaptation Layer                           |
+| ML/MC-PPP | Muti-Link/Multi-Class PPP                                |
+| MPLS      | Multiprotocol Label Switching                            |
+| MSC       | Mobile services Switching Center                         |
+| MTP3-B    | Message Transfer Part                                    |
+| PPP       | Point-to-Point protocol                                  |
+| PPPMux    | PPP Multiplexing                                         |
+| PS        | Packet Switched                                          |
+| RANAP     | Radio Access Network Application Part                    |
+| RNC       | Radio Network Controller                                 |
+| SAAL-NNI  | Signalling ATM Adaptation Layer – Network Node Interface |
+| SCCP      | Signalling Connection Control Part                       |
+| SCTP      | Stream Control Transmission Protocol                     |
+| SGSN      | Serving GPRS Support Node                                |
+| SSCF      | Service Specific Co-ordination Function                  |
+
+# 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the radio network control plane according to (ITU-T Rec. I.361 [5]). The structure of the cell header used in the UTRAN Iu interface is the cell header format and encoding at NNI (see Figure 3/I.361).
+
+## 4.2 IP Transport Option
+
+An RNC/CN using IP transport option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [19], IETF RFC 1662 [20]).
+
+Note: This does not preclude the single implementation and use of any other data link layer protocol (e.g. PPPMux (IETF RFC 3153 [29])/AAL5/ATM, PPP/AAL2/ATM, Ethernet, MPLS (IETF RFC 3031 [28])/ATM, etc.) fulfilling the UTRAN requirements toward the upper Layers.
+
+An RNC/CN using IP transport option having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [21]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [22], IETF RFC 2686 [23]). In this case, the negotiation of header compression (IETF RFC 2507 [21]) over PPP shall be performed via IETF RFC 2509 [24].
+
+# 5 RANAP Signalling Bearer
+
+## 5.1 Introduction
+
+This subclause specifies the Signalling Bearer protocol stack that supports the RANAP signalling protocol.
+
+The following requirements on the Signalling Bearer can be stated:
+
+- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode;
+- provide separate independent connections for distinguishing transactions with individual UE's;
+- supervise the 'UE connections' and provide connection status information to the Upper Layers for individual UE's;
+- provide networking and routing functions;
+- provide redundancy in the signalling network;
+- provide load sharing.
+
+## 5.2 Signalling Bearer for Circuit Switched Domain
+
+### 5.2.1 Protocol Stack for the CS Domain
+
+The protocol stacks for the CS Domain are shown in figure 1. The standard allows operators to choose one out of two standardised protocol suites for transport of SCCP messages.
+
+Figure 1 shows, for the Iu IP CS domain, the point at which the service primitives are invoked. A single SAP is defined independently of the signalling bearer. The SAP provides the SCCP primitives. The figure is not intended to constrain the architecture.
+
+The following figure 1 also illustrates the protocol model having Broadband Signalling System No.7 as the signalling bearer for RANAP over the Iu interface that fulfils the requirements. Figure 1 shows, for the CS domain, the point at which the service primitives are invoked. The SAP provides the SCCP primitives.
+
+![Figure 1: SAP between RANAP and its transport for Iu - CS Domain. The diagram shows two protocol stacks for the Iu-CS Control Plane. The left stack is for the ATM transport option, showing RANAP at the top, followed by SCCP-SAP, SCCP, MTP3-B, SAAL-NNI, and ATM. The right stack is for the IP transport option, showing RANAP at the top, followed by SCCP-SAP, SCCP, M3UA, SCTP, IP, and Data Link.](35a7554182eb055209552843f341a1ae_img.jpg)
+
+The diagram illustrates two protocol stacks for the Iu-CS Control Plane. Both stacks start with RANAP at the top. In the left stack (ATM transport option), RANAP is connected to an SCCP-SAP, which is then connected to a stack of SCCP, MTP3-B, SAAL-NNI, and ATM. In the right stack (IP transport option), RANAP is connected to an SCCP-SAP, which is then connected to a stack of SCCP, M3UA, SCTP, IP, and Data Link.
+
+Figure 1: SAP between RANAP and its transport for Iu - CS Domain. The diagram shows two protocol stacks for the Iu-CS Control Plane. The left stack is for the ATM transport option, showing RANAP at the top, followed by SCCP-SAP, SCCP, MTP3-B, SAAL-NNI, and ATM. The right stack is for the IP transport option, showing RANAP at the top, followed by SCCP-SAP, SCCP, M3UA, SCTP, IP, and Data Link.
+
+Protocol stack for ATM transport option
+
+Protocol stack for IP transport option
+
+Figure 1: SAP between RANAP and its transport for Iu - CS Domain
+
+### 5.2.2 ATM Transport Option
+
+1. **SCCP** (ITU-T Rec. Q.711 [7] or ANSI T1.112-2001 [32]) provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis. SCCP shall be used as specified in TS 25.410 [18].
+2. **MTP3-B** (ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]) provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded. MTP3-B shall comply with ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31].
+3. **SAAL-NNI** (ITU-T Rec. Q.2100 [1]) consists of the following sub-layers: - **SSCF** (ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 (R2003) [33]), - **SSCOP** (ITU-T Rec. Q.2110 [2]) and - **AAL5** (ITU-T Rec. I.363.5 [6]). The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells. It shall be possible to use SAAL-NNI connections pre-configured as PVCs for signalling transport on the Iu-Interface.
+4. **ATM** (ITU-T Rec. I.361 [5]).
+
+### 5.2.3 IP Transport Option
+
+1. **SCCP**, see subclause 5.2.2.
+2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the MSC when it is a newly introduced entity in the network.
+3. **SCTP** refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. The checksum method specified in IETF RFC 3309 [30] shall be used instead of the method specified in IETF RFC 2960 [16]. Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint.
+
+4. **IP.** IPv6 shall be supported according to IETF RFC 2460 [25]. IPv4 support (IETF RFC 791 [13]) is optional.
+
+Note: This does not preclude the single implementation and use of IPv4.
+
+Due to the possible transition from IPv4 to IPv6 the IP dual stack support is recommended.
+
+An RNC/CN using IP transport option shall support Diffserv code point marking IETF RFC 2474 [26]. The Diffserv code point may be determined from the application parameters.
+
+## 5.3 Signalling Bearer for Packet Switched Domain
+
+### 5.3.1 Protocol Stack for the PS Domain
+
+The protocol stacks for the PS Domain is shown in figure 2. The standard allows operators to choose one out of three standardised protocol suites for transport of SCCP messages.
+
+![](99bae07626f60f9ede10e2e387ef7051_img.jpg)
+
+Iu-PS Control Plane
+
+|                 |      |
+|-----------------|------|
+| RANAP           |      |
+| SCCP-SAP (oval) |      |
+| SCCP            |      |
+| MTP3-B          | M3UA |
+|                 | SCTP |
+| SAAL-NNI        | IP   |
+|                 | AAL5 |
+| ATM             |      |
+
+Protocol stacks for ATM transport options
+
+![](2ba086df3506f81bae3a9b53725dcfea_img.jpg)
+
+Iu-PS Control Plane
+
+|                 |
+|-----------------|
+| RANAP           |
+| SCCP-SAP (oval) |
+| SCCP            |
+| M3UA            |
+| SCTP            |
+| IP              |
+| Data Link       |
+
+Protocol stack for IP transport option
+
+Figure 2: SAP between RANAP and its transport for the Iu –IP domain
+
+Figure 2 shows, for the Iu IP domain, the point at which the service primitives are invoked. A single SAP is defined independently of the signalling bearer. The SAP provides the SCCP primitives. The figure is not intended to constrain the architecture.
+
+### 5.3.2 ATM Transport Option 1
+
+1. **SCCP** (ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8] /ITU-T Rec. Q.713 [9] /ITU-T Rec. Q.714 [10] /ITU-T Rec. Q.715 [11] /ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32]) provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis. The SCCP shall be used as specified in TS 25.410 [18].
+2. **MTP3-B** (ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]) provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded. MTB3-B shall comply with ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31].
+3. **SAAL-NNI** (ITU-T Rec. Q.2100 [1]) consists of the following sub-layers: - **SSCF-NNI** (ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 (R2003) [33]), - **SSCOP** (ITU-T Rec. Q.2110 [2]) and – **AAL5** (ITU-T Rec. I.363.5 [6]). The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells. It shall be possible to use SAAL-NNI connections pre-configured as PVCs for signalling transport on the Iu-interface.
+
+4. **ATM** (ITU-T Rec. I.361 [5]).
+
+### 5.3.3 ATM Transport Option 2
+
+1. **SCCP**, see subclause 5.3.2.
+2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the SGSN when it is a newly introduced entity in the network.
+3. **SCTP** refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. The multi-homing services of SCTP shall be required at both ends of an SCTP-association to enable transport redundancy and reliability. **M3UA**. An implementation of SCTP to this document shall utilise the new checksum method specified in IETF RFC 3309 [30] instead of the method specified in IETF RFC 2960 [16].
+4. **IP** (IETF RFC 791 [13]) over ATM is defined in IETF RFC 2684 [14] and IETF RFC 2225 [15].
+5. **AAL5** refers to ITU-T Rec. I.363.5 [6]. It shall be possible to use AAL5 connections pre-configured as PVCs for signalling transport on the Iu-interface.
+
+### 5.3.4 IP Transport Option
+
+1. **SCCP**, see subclause 5.3.2.
+2. **M3UA**, refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the SGSN when it is a newly introduced entity in the network.
+3. **SCTP**, refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. An implementation of SCTP to this document shall utilise the new checksum method specified in IETF RFC 3309 [30] instead of the method specified in IETF RFC 2960 [16]. Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint.
+4. **IP**. IPv6 shall be supported according to IETF RFC 2460 [25]. IPv4 support (IETF RFC 791 [13]) is optional.
+
+Note: This does not preclude the single implementation and use of IPv4.
+
+Due to the possible transition from IPv4 to IPv6, the IP dual stack support is recommended.
+
+An RNC/CN using IP transport option shall support Diffserv code point marking (IETF RFC 2474 [26]). The Diffserv code point may be determined from the application parameters.
+
+## 5.4 Services Provided by the Signalling Bearer
+
+When considering the requirements that the upper layers, i.e. RANAP, have on the Signalling Bearer, there are a number of services it has to provide and a number of functions to perform. These numbers of services that the signalling bearer shall provide, to the upper layers, are stated in references ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8] /ITU-T Rec. Q.713 [9] /ITU-T Rec. Q.714 [10] /ITU-T Rec. Q.715 [11] / ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32].
+
+# Annex A (informative): Change History
+
+| Date / TSG | TSG Doc.  | CR   | Rev | Subject/Comment                                            | New    |
+|------------|-----------|------|-----|------------------------------------------------------------|--------|
+| 12/2008    | -         | -    | -   | Creation of Rel-8 version based on v7.1.0                  | 8.0.0  |
+| 12/2009    | -         | -    | -   | Creation of Rel-9 version based on v8.0.0                  | 9.0.0  |
+| 03/2011    | SP-100629 |      |     | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1  |
+| 03/2011    |           |      |     | Creation of Rel-10 version based on v9.0.1                 | 10.0.0 |
+| 06/2011    | RP-110685 | 0026 |     | Correction to the References in 25.412                     | 10.1.0 |
+| 09/2012    |           |      |     | Update to Rel-11 version (MCC)                             | 11.0.0 |
+| 09/2014    |           |      |     | Update to Rel-12 version (MCC)                             | 12.0.0 |
+| 12/2015    |           |      |     | Update to Rel-13 version (MCC)                             | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                                  |             |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                  | New version |
+| 2017-03        | SA#75   |      |    |     |     | Promotion to Release 14 without technical change | 14.0.0      |
+| 2018-06        | SA#80   | -    | -  | -   | -   | Promotion to Release 15 without technical change | 15.0.0      |
+| 2020-07        | SA#88-e | -    | -  | -   | -   | Update to Rel-16 version (MCC)                   | 16.0.0      |
+| 2022-03        | SA#95-e |      |    |     |     | Promotion to Release 17 without technical change | 17.0.0      |
+| 2024-03        | SA#103- | -    | -  | -   | -   | Update to Rel-18 version (MCC)                   | 18.0.0      |

marked/Rel-18/25_series/25414/raw.md

@@ -0,0 +1,721 @@
+
+
+# 3GPP TS 25.414 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface data transport and transport signalling (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                 |    |
+|-------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                  | 5  |
+| 1 Scope.....                                                                                    | 6  |
+| 2 References.....                                                                               | 6  |
+| 3 Definitions and abbreviations .....                                                           | 7  |
+| 3.1 Definitions.....                                                                            | 7  |
+| 3.2 Abbreviations .....                                                                         | 7  |
+| 4 Data Link Layer .....                                                                         | 8  |
+| 4.1 ATM Transport Option .....                                                                  | 8  |
+| 4.2 IP Transport Option.....                                                                    | 8  |
+| 5 Circuit switched domain .....                                                                 | 8  |
+| 5.1 Transport network user plane.....                                                           | 8  |
+| 5.1.1 General .....                                                                             | 8  |
+| 5.1.2 ATM Transport Option.....                                                                 | 9  |
+| 5.1.2.1 ATM Adaptation Layer 2 .....                                                            | 9  |
+| 5.1.2.1.1 AAL2-Segmentation and Reassembly Service Specific Convergence Sublayer (I.366.1)..... | 9  |
+| 5.1.2.1.2 AAL2-specification (I.363.2).....                                                     | 9  |
+| 5.1.3 IP Transport Option.....                                                                  | 9  |
+| 5.1.3.1 General.....                                                                            | 9  |
+| 5.1.3.2 UDP/IP.....                                                                             | 9  |
+| 5.1.3.3 RTP.....                                                                                | 10 |
+| 5.1.3.3.1 RTP Header.....                                                                       | 10 |
+| 5.1.3.3.1.4 Contributing Source (CSRC) count.....                                               | 10 |
+| 5.1.3.3.1.5 Marker Bit .....                                                                    | 10 |
+| 5.1.3.3.1.6 Payload Type.....                                                                   | 10 |
+| 5.1.3.3.1.7 Sequence Number.....                                                                | 10 |
+| 5.1.3.3.1.8 Timestamp.....                                                                      | 10 |
+| 5.1.3.3.1.9 Synchronisation Source (SSRC).....                                                  | 11 |
+| 5.1.3.3.1.10 CSRC list.....                                                                     | 11 |
+| 5.1.3.3.2 RTP Payload.....                                                                      | 11 |
+| 5.1.3.4 RTCP .....                                                                              | 11 |
+| 5.1.3.5 Diffserv code point marking.....                                                        | 11 |
+| 5.2 Transport network control plane .....                                                       | 11 |
+| 5.2.1 General .....                                                                             | 11 |
+| 5.2.2 Transport Signalling for the ATM Transport Option .....                                   | 12 |
+| 5.2.2.1 Signalling protocol (ALCAP).....                                                        | 12 |
+| 5.2.2.1.1 AAL2 Signalling Protocol (Q.2630.2) .....                                             | 12 |
+| 5.2.2.2 Signalling transport converter.....                                                     | 12 |
+| 5.2.2.2.1 AAL2 MTP3B Signalling Transport Converter (Q.2150.1) .....                            | 12 |
+| 5.2.2.3 MTP3b (Q.2210).....                                                                     | 12 |
+| 5.2.2.4 SSCF-NNI (Q.2140).....                                                                  | 12 |
+| 5.2.2.5 SSCOP (Q.2110).....                                                                     | 12 |
+| 5.2.2.6 ATM Adaptation Layer Type 5 (I.363.5) .....                                             | 13 |
+| 5.3 Interworking between ATM and IP Transport Options .....                                     | 13 |
+| 5.3.1 Introduction .....                                                                        | 13 |
+| 5.3.2 Interworking Alternatives.....                                                            | 13 |
+| 6 Packet switched domain.....                                                                   | 13 |
+| 6.1 Transport network user plane.....                                                           | 13 |
+| 6.1.1 General .....                                                                             | 13 |
+| 6.1.2 ATM Transport Option.....                                                                 | 14 |
+| 6.1.2.1 General.....                                                                            | 14 |
+| 6.1.2.2 GTP-U.....                                                                              | 14 |
+| 6.1.2.3 UDP /IP.....                                                                            | 14 |
+| 6.1.2.4 ATM Adaptation Layer Type 5 (I.363.5) .....                                             | 14 |
+
+|                               |                                                                                                                                                    |           |
+|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| 6.1.2.5                       | IP/ATM.....                                                                                                                                        | 15        |
+| 6.1.3                         | IP Transport Option.....                                                                                                                           | 15        |
+| 6.1.3.1                       | General.....                                                                                                                                       | 15        |
+| 6.1.3.2                       | GTP-U.....                                                                                                                                         | 15        |
+| 6.1.3.3                       | UDP /IP.....                                                                                                                                       | 15        |
+| 6.1.3.4                       | Diffserv code point marking.....                                                                                                                   | 16        |
+| 6.2                           | Transport network control plane .....                                                                                                              | 16        |
+| 7                             | Broadcast Domain.....                                                                                                                              | 16        |
+| 7.1                           | Transport network user plane.....                                                                                                                  | 16        |
+| 7.1.1                         | General .....                                                                                                                                      | 16        |
+| 7.1.2                         | ATM Transport Option.....                                                                                                                          | 16        |
+| 7.1.2.1                       | General.....                                                                                                                                       | 16        |
+| 7.1.2.2                       | TCP/IP .....                                                                                                                                       | 16        |
+| 7.1.2.3                       | ATM Adaptation Layer Type 5 (I.363.5) .....                                                                                                        | 17        |
+| 7.1.2.4                       | IP/ATM.....                                                                                                                                        | 17        |
+| 7.1.3                         | IP Transport Option.....                                                                                                                           | 17        |
+| 7.1.3.1                       | General.....                                                                                                                                       | 17        |
+| 7.1.3.3                       | TCP /IP .....                                                                                                                                      | 17        |
+| 7.1.3.4                       | Diffserv code point marking.....                                                                                                                   | 17        |
+| 7.2                           | Transport network control plane .....                                                                                                              | 17        |
+| <b>Annex A (informative):</b> | <b>IP-ATM Interworking .....</b>                                                                                                                   | <b>19</b> |
+| A.1                           | Application of IP tunnelling in IP-ATM interworking alternative 1 in case of no direct ATM connectivity at the IP&ATM dual stack RNC/CN-node ..... | 19        |
+| A.2                           | Application of IP-ALCAP in IP-ATM interworking alternative 2 .....                                                                                 | 19        |
+| <b>Annex B (informative):</b> | <b>Change history.....</b>                                                                                                                         | <b>20</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the standards for user data transport protocols and related signalling protocols to establish user plane transport bearers over the UTRAN Iu interface.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [2] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation layer specification: Type 2 AAL".
+- [3] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation layer specification: Type 5 AAL".
+- [4] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2".
+- [5] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan".
+- [6] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)".
+- [7] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer - Service Specific Coordination Function for Support of Signalling at the Network Node Interface (SSCF-NNI)".
+- [8] ITU-T Recommendation Q.2150.1 (1999-12): "AAL type 2 signalling transport converter on broadband MTP".
+- [9] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".
+- [10] ITU-T Recommendation Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)".
+- [11] ITU-T Recommendation X.213 (1995-11): "Information technology - Open systems interconnection - Network Service Definitions".
+- [12] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [13] IETF RFC 791 (1981-09): "Internet Protocol".
+- [14] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".
+- [15] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM".
+- [16] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
+- [17] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ".
+
+- [18] IETF RFC 793 (1981-09): "Transmission Control Protocol".
+- [19] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers".
+- [20] ITU-T Implementor's guide (1999-12) for recommendation Q.2210 (1996-07).
+- [21] ITU-T Recommendation Q.2630.2 (2000-12): "AAL type 2 signalling protocol (Capability Set 2)".
+- [22] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications".
+- [23] IETF RFC 1890 (1996-01): "RTP Profile for Audio and Video Conferences with Minimal Control".
+- [24] 3GPP TS 25.415: "UTRAN Iu Interface User Plane Protocols"
+- [25] IETF RFC 1661 (1994-07): "The Point-to-Point Protocol (PPP)".
+- [26] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [27] IETF RFC 2507 (1999-02): "IP header compression".
+- [28] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [29] IETF RFC 2686 (1996-09): "The Multi-Class Extension to Multi-Link PPP".
+- [30] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [31] Void
+- [32] IETF RFC 3153 (2001-08): "PPP Multiplexing".
+- [33] IETF RFC 2364 (1998-07): "PPP over AAL5".
+- [34] IETF RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture".
+- [35] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing".
+- [36] 3GPP TS 25.401: "UTRAN overall description".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Access Link Control Application Part (ALCAP):** generic name for the transport signalling protocols used to set-up and teardown transport bearers
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                      |
+|-------|--------------------------------------|
+| AAL   | ATM Adaptation Layer                 |
+| AESA  | ATM End System Address               |
+| ALCAP | Access Link Control Application Part |
+| ARP   | Address Resolution Protocol          |
+| ATM   | Asynchronous Transfer Mode           |
+| CN    | Core Network                         |
+| GTP   | GPRS Tunnelling Protocol             |
+| HDLC  | High-level Data Link Control         |
+| IP    | Internet Protocol                    |
+
+|          |                                                               |
+|----------|---------------------------------------------------------------|
+| LC       | Link Characteristics                                          |
+| LIS      | Logical IP Subnet                                             |
+| MTP3b    | Message Transfer Part level 3 for Q.2140                      |
+| NSAP     | Network Service Access Point                                  |
+| PDU      | Protocol Data Unit                                            |
+| PPP      | Point-to-Point Protocol                                       |
+| RFC      | Request For Comment                                           |
+| RNC      | Radio Network Controller                                      |
+| RTCP     | Real-time Transport Control Protocol                          |
+| RTP      | Real-time Transport Protocol                                  |
+| SA       | Service Area                                                  |
+| SABP     | Service Area Broadcast Protocol                               |
+| SABS     | Service Area Broadcast Service                                |
+| SAR      | Segmentation and Reassembly                                   |
+| SCSF-NNI | Service Specific Coordination Function-Network Node Interface |
+| SSCOP    | Service Specific Connection Oriented Protocol                 |
+| SSCS     | Service Specific Convergence Sublayer                         |
+| SSRC     | Synchronisation Source                                        |
+| TCP      | Transmission Control Protocol                                 |
+| TEID     | Tunnel Endpoint Identifier                                    |
+| UDP      | User Datagram Protocol                                        |
+| VC       | Virtual Circuit                                               |
+
+# --- 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the transport network user plane and the transport network control plane according to ITU-T Recommendation I.361 [1]. The structure of the cell header used in the UTRAN Iu interface is the cell header format and encoding at NNI (see figure 3/I.361).
+
+## 4.2 IP Transport Option
+
+An RNC/CN-node supporting IP transport option on the Iu interface shall support PPP protocol with HDLC framing (IETF RFC 1661 [25], IETF RFC 1662 [26]).
+
+NOTE: This does not preclude the single implementation and use of any other protocols (e.g. PPPMux /AAL5/ATM (IETF RFC 3153 [32], IETF RFC 2364 [33]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [34]), etc.) fulfilling the UTRAN requirements toward the upper layers.
+
+An RNC/CN-node supporting IP transport option on the Iu interface and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [27]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [28], IETF RFC 2686 [29]). In this case the negotiation of header compression (IETF RFC 2507 [27]) over PPP shall be performed via IETF RFC 2509 [30].
+
+# --- 5 Circuit switched domain
+
+## 5.1 Transport network user plane
+
+### 5.1.1 General
+
+There are two options for the transport layer for data streams over Iu-CS:
+
+- 1) ATM based Transport (ATM transport option)
+
+#### 2) IP based Transport (IP transport option)
+
+The following figure shows the protocol stacks of the two options.
+
+![Figure 1: Transport network layer for data streams over Iu-CS. The diagram shows two protocol stacks. The left stack, labeled 'Protocol Stack for the ATM transport option', consists of four layers: AAL-2 SAR SSCS (I.366.1), AAL2 (I.363.2), ATM (I.361), and Physical Layer. The right stack, labeled 'Protocol Stack for the IP transport option', consists of five layers: RTP (RFC 1889), UDP (RFC 768), IPv6 (RFC 2460) with IPv4 optional (RFC 791), Data Link Layer, and Physical Layer.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+|                          |                                            |
+|--------------------------|--------------------------------------------|
+| AAL-2 SAR SSCS (I.366.1) | RTP (RFC 1889)                             |
+| AAL2 (I.363.2)           | UDP (RFC 768)                              |
+| ATM (I.361)              | IPv6 (RFC 2460)<br>IPv4 optional (RFC 791) |
+| Physical Layer           | Data Link Layer                            |
+|                          | Physical Layer                             |
+
+Figure 1: Transport network layer for data streams over Iu-CS. The diagram shows two protocol stacks. The left stack, labeled 'Protocol Stack for the ATM transport option', consists of four layers: AAL-2 SAR SSCS (I.366.1), AAL2 (I.363.2), ATM (I.361), and Physical Layer. The right stack, labeled 'Protocol Stack for the IP transport option', consists of five layers: RTP (RFC 1889), UDP (RFC 768), IPv6 (RFC 2460) with IPv4 optional (RFC 791), Data Link Layer, and Physical Layer.
+
+**Figure 1. Transport network layer for data streams over Iu-CS.**
+
+### 5.1.2 ATM Transport Option
+
+#### 5.1.2.1 ATM Adaptation Layer 2
+
+##### 5.1.2.1.1 AAL2-Segmentation and Reassembly Service Specific Convergence Sublayer (I.366.1)
+
+Service Specific Segmentation and Reassembly (SSSAR) sublayer of ITU-T Recommendation I.366.1 [4] is used for the segmentation and reassembly of AAL2 SDUs (i.e., only SSSAR is used from ITU-T Recommendation I.366.1).
+
+##### 5.1.2.1.2 AAL2-specification (I.363.2)
+
+AAL2 shall be used according to ITU-T Recommendation I.363.2 [2].
+
+### 5.1.3 IP Transport Option
+
+#### 5.1.3.1 General
+
+In the IP transport option RTP over UDP over IP shall be supported as the transport for data streams on the Iu-CS interface. The data link layer is as specified in subclause 4.2.
+
+The transport bearer is identified by the UDP port number and the IP address (source UDP port number, destination UDP port number, source IP address, destination IP address).
+
+The source IP address and destination IP address exchanged via RANAP on the Iu-CS interface shall use the NSAP structure. See sub clause 6.1.8.2 in TS 25.401 [36].
+
+#### 5.1.3.2 UDP/IP
+
+The path protocol used shall be UDP (IETF RFC 768 [12]).
+
+An IP RNC/CN-node shall support IPv6. The support of IPv4 is optional.
+
+NOTE: This does not preclude single implementation and use of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+There may be one or several IP addresses in the RNC and in the CN. The packet processing function in the CN shall send downstream packets of a given RAB to the RNC IP address / UDP port (received in RANAP) associated to that particular RAB. The packet processing function in the RNC shall send upstream packets of a given RAB to the CN IP address / UDP port (received in RANAP) associated to that particular RAB. If there is no RNC IP address / UDP port yet associated to the packet processing function in the CN for a RAB not yet finally set-up, the packet processing function in the CN for that RAB shall extract the source IP address / UDP port from the first received IP packet to identify the peer IP/UDP entity. The packet processing function in the RNC shall use the same source IP address / UDP port as is sent to CN in RANAP.
+
+The RNC/CN-node shall use two consecutive port numbers for the RTP bearer and for the optional RTCP connection that transport a single Iu UP connection. Two such consecutive port numbers are termed “port number block” in what follows. The first port number shall be even and shall be assigned to the RTP protocol. The next port number shall be assigned to the RTCP protocol. This port shall be reserved even if the optional RTCP protocol is not used.
+
+Each RNC/CN-node shall administer the port numbers it intends to use for RTP/RTCP port number blocks.
+
+#### 5.1.3.3 RTP
+
+RTP (IETF RFC 1889 [22]) shall be applied.
+
+##### 5.1.3.3.1 RTP Header
+
+The RTP Header Fields shall be used as described in the following subclauses:
+
+###### 5.1.3.3.1.1 Version
+
+RTP Version 2 shall be used.
+
+###### 5.1.3.3.1.2 Padding
+
+Padding shall not be used.
+
+###### 5.1.3.3.1.3 Extension
+
+The RTP Header shall not have an extension.
+
+###### 5.1.3.3.1.4 Contributing Source (CSRC) count
+
+There are zero CSRCs.
+
+###### 5.1.3.3.1.5 Marker Bit
+
+The marker bit is ignored.
+
+###### 5.1.3.3.1.6 Payload Type
+
+A dynamic Payload Type (IETF RFC 1890 [23]) shall be used. Values in the Range between 96 and 127 shall be used. The value shall be ignored in the receiving entity.
+
+###### 5.1.3.3.1.7 Sequence Number
+
+The sequence number shall be supplied by the source of an RTP PDU. The sink of an RTP PDU may ignore the sequence number or it may use it to obtain statistics about the link quality and / or to correct out-of-sequence delivery, e.g. by dropping out-of-sequence packets.
+
+###### 5.1.3.3.1.8 Timestamp
+
+The timestamp shall be supplied by the source of an RTP PDU. A clock frequency of 16000 Hz shall be used. The sink of an RTP PDU may ignore the timestamp or it may use it to obtain statistics about the link quality and / or to correct jitter.
+
+###### 5.1.3.3.1.9 Synchronisation Source (SSRC)
+
+The source of an RTP PDU shall supply a SSRC. The sink of an RTP PDU may ignore the SSRC if it does not use RTCP.
+
+###### 5.1.3.3.1.10 CSRC list
+
+This list is empty.
+
+##### 5.1.3.3.2 RTP Payload
+
+A single Iu UP PDU, as described in TS 25.415 [24], shall be transported as RTP payload.
+
+#### 5.1.3.4 RTCP
+
+RTCP (IETF RFC 1889 [22]) may be applied. RTCP over UDP (IETF RFC 768 [12]) over IPv6 (IETF RFC 2460 [16]) shall be used (IPv4 (IETF RFC 791 [13]) may be used optionally). The use of the RTCP protocol is optional. The receiving entity may ignore incoming RTCP PDUs.
+
+Figure 1a shows the protocol stack for the transport of RTCP. The above Sections about IP and UDP shall also apply for the transport of RTCP.
+
+![](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg)
+
+|                                           |
+|-------------------------------------------|
+| RTCP( <i>RFC 1889</i> )                   |
+| UDP ( <i>RFC 768</i> )                    |
+| IPv6 (RFC2460)<br>IPv4 optional (RFC 791) |
+
+**Figure 1a. RTCP Protocol stack for data stream transport on Iu-CS.**
+
+#### 5.1.3.5 Diffserv code point marking
+
+IP Differentiated Services code point marking (IETF RFC 2474 [19]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M for each traffic category. Traffic categories are implementation-specific and may be determined from the application parameters.
+
+## 5.2 Transport network control plane
+
+### 5.2.1 General
+
+The following figure shows the protocol stack for transport signalling over Iu-CS in ATM based transport (ATM transport option). An ALCAP protocol is not required when both UTRAN and CN nodes are using the IP based transport (IP transport option).
+
+The protocol stack for IP-ALCAP in IP to ATM interworking case is defined in chapter 5.3.3 of this Technical Specification.
+
+![Diagram showing the signalling bearer for ALCAP on the Iu-CS interface. The diagram consists of seven stacked rectangular boxes representing protocol layers. From top to bottom, they are: AAL2 connection signalling (Q.2630.2), AAL2 Signalling Transport Converter for MTP3b (Q.2150.1), MTP3b, SSCF-NNI, SSCOP, ATM, and Physical Layer.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+|                                                                |
+|----------------------------------------------------------------|
+| AAL2 connection signalling<br>(Q.2630.2)                       |
+| AAL2 Signalling Transport<br>Converter for MTP3b<br>(Q.2150.1) |
+| MTP3b                                                          |
+| SSCF-NNI                                                       |
+| SSCOP                                                          |
+| ATM                                                            |
+| Physical Layer                                                 |
+
+Diagram showing the signalling bearer for ALCAP on the Iu-CS interface. The diagram consists of seven stacked rectangular boxes representing protocol layers. From top to bottom, they are: AAL2 connection signalling (Q.2630.2), AAL2 Signalling Transport Converter for MTP3b (Q.2150.1), MTP3b, SSCF-NNI, SSCOP, ATM, and Physical Layer.
+
+**Figure 2. Signalling bearer for ALCAP on Iu-CS interface.**
+
+### 5.2.2 Transport Signalling for the ATM Transport Option
+
+#### 5.2.2.1 Signalling protocol (ALCAP)
+
+##### 5.2.2.1.1 AAL2 Signalling Protocol (Q.2630.2)
+
+In the ATM transport option ITU-T Recommendation Q.2630.2 [21] shall be used for establishing AAL2 connections towards the circuit switched domain. ITU-T Recommendation Q.2630.2 [21] adds new optional capabilities to ITU-T Recommendation Q.2630.1 [10].
+
+The AAL2 transport layer uses the embedded E.164 or other AESA variants of the NSAP addressing formats ITU-T Rec. X.213 [11], and ITU-T Recommendation E.191 [35]. Native E.164 addressing (ITU-T Recommendation E.164 [5]) shall not be used.
+
+Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH request primitive of ITU-T Recommendation Q.2630.2 [21].
+
+The Link Characteristics parameter (LC) shall be included in the Establish Request message and in the Modification Request message of AAL2 signalling protocol.
+
+#### 5.2.2.2 Signalling transport converter
+
+##### 5.2.2.2.1 AAL2 MTP3B Signalling Transport Converter (Q.2150.1)
+
+The AAL2 MTP3b Signalling Transport Converter shall be used according to ITU-T Recommendation Q.2150.1 [8].
+
+#### 5.2.2.3 MTP3b (Q.2210)
+
+MTP3b shall be used according to ITU-T Recommendation Q.2210 [9] and ITU-T Implementor's guide (12/99) for recommendation Q.2210 [20].
+
+#### 5.2.2.4 SSCF-NNI (Q.2140)
+
+SSCF-NNI shall be used according to ITU-T Recommendation Q.2140 [7].
+
+#### 5.2.2.5 SSCOP (Q.2110)
+
+SSCOP shall be used according to ITU-T Recommendation Q.2110 [6].
+
+#### 5.2.2.6 ATM Adaptation Layer Type 5 (I.363.5)
+
+AAL5 shall be used according to ITU-T Recommendation I.363.5 [3].
+
+## 5.3 Interworking between ATM and IP Transport Options
+
+### 5.3.1 Introduction
+
+This clause specifies the interworking between IP and ATM transport options. An RNC/CN-node supporting IP transport option shall provide interworking to a CN-node/RNC supporting only ATM transport option.
+
+### 5.3.2 Interworking Alternatives
+
+For interworking with a CN-node/RNC supporting only ATM transport option, the RNC/CN-node supporting IP transport option shall additionally support at least one of the following interworking mechanisms:
+
+- 1) ATM&IP dual stack. An IP-ALCAP protocol is not required in this interworking solution.
+
+Annex A of this technical specification shows an example of protocols for the case the ATM&IP RNC/CN-node has no ATM connectivity.
+
+- 2) An Interworking Function (IWF), either internal or external to the RNC/CN node.
+
+Annex A of this technical specification shows an example of a protocol stack for the case when the IWF is an external unit to the RNC/CN node. Other protocol stacks for this case are not precluded.
+
+# --- 6 Packet switched domain
+
+## 6.1 Transport network user plane
+
+### 6.1.1 General
+
+There are two options for the transport layer for data streams over Iu-PS:
+
+- 1) ATM based Transport (ATM transport option)
+- 2) IP based Transport (IP transport option)
+
+The following figure shows the protocol stacks of the two options.
+
+![Figure 3: Transport network layer for data streams over Iu-PS. The diagram shows two protocol stacks. The left stack, labeled 'Protocol Stack for the ATM transport option', consists of GTP-U, UDP, IP, AAL5, ATM, and Physical Layer. The right stack, labeled 'Protocol Stack for the IP transport option', consists of GTP-U, UDP, IPv6 (RFC 2460) with IPv4 optional (RFC 791), Data Link Layer, and Physical Layer. Both stacks have dashed lines at the bottom indicating the boundary between the network layer and the physical layer.](bd671b21db63e6fdb2196e9b18502aac_img.jpg)
+
+|                |                                            |
+|----------------|--------------------------------------------|
+| GTP-U          | GTP-U                                      |
+| UDP            | UDP                                        |
+| IP             | IPv6 (RFC 2460)<br>IPv4 optional (RFC 791) |
+| AAL5           | Data Link Layer                            |
+| ATM            | Physical Layer                             |
+| Physical Layer |                                            |
+
+Figure 3: Transport network layer for data streams over Iu-PS. The diagram shows two protocol stacks. The left stack, labeled 'Protocol Stack for the ATM transport option', consists of GTP-U, UDP, IP, AAL5, ATM, and Physical Layer. The right stack, labeled 'Protocol Stack for the IP transport option', consists of GTP-U, UDP, IPv6 (RFC 2460) with IPv4 optional (RFC 791), Data Link Layer, and Physical Layer. Both stacks have dashed lines at the bottom indicating the boundary between the network layer and the physical layer.
+
+**Figure 3. Transport network layer for data streams over Iu-PS.**
+
+### 6.1.2 ATM Transport Option
+
+#### 6.1.2.1 General
+
+In the ATM transport option, the protocol architecture for the User Plane of the Iu interface towards the packet switched domain shall be GTP-U (TS 29.060 [17]) over UDP over IP over AAL5 over ATM. One or several AAL5/ATM permanent VC's may be used as the common layer 2 resources between the UTRAN and the packet switched domain of the CN.
+
+One switched VC may be used per user flow. The standardisation of the procedures and protocols for use of Switched VC is outside the scope of 3GPP.
+
+Congestion control shall be performed over the Iu user plane toward the packet switched domain using buffer management and no flow control.
+
+#### 6.1.2.2 GTP-U
+
+The GTP-U (TS 29.060 [17]) protocol shall be used over the Iu interface toward the packet switched domain.
+
+#### 6.1.2.3 UDP /IP
+
+The path protocol used shall be UDP (IETF RFC 768 [12]), which is specified in RFC 768.
+
+The UDP port number for GTP-U shall be as defined in TS 29.060 [17].
+
+IPv4 (IETF RFC 791 [13]) shall be supported; IPv6 (IETF RFC 2460 [16]) support is optional.
+
+There may be one or several IP addresses in the RNC and in the CN. The packet processing function in the CN shall send downstream packets of a given RAB to the RNC IP address (received in RANAP) associated to that particular RAB. The packet processing function in the RNC shall send upstream packets of a given RAB to the CN IP address (received in RANAP) associated to that particular RAB.
+
+There is one RNC IP address per RNC in the CN associated with one MBMS RAB. This address is received in RANAP at the establishment of the MBMS RAB. The packet processing function in the CN shall send the downstream packets of the MBMS RAB to this associated RNC IP address.
+
+#### 6.1.2.4 ATM Adaptation Layer Type 5 (I.363.5)
+
+AAL5 shall be used according to ITU-T Recommendation I.363.5 [3].
+
+AAL5 virtual circuits shall be used to transport the IP packets across the Iu interface toward the packet switched domain. Multiple VCs may be used over the interface. An association shall be made between a VC and the IP addresses that are related to this VC in the peer node side. This association shall be made using O&M or using "ATM Inverse ARP" when PVCs are used.
+
+When PVCs are used, quality of service differentiation shall only be performed at the IP layer using differentiated services (IETF RFC 2474 [19]).
+
+#### 6.1.2.5 IP/ATM
+
+When the association mentioned in 6.1.2.4 is made using O&M, the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used.
+
+When the association mentioned in 6.1.2.4 is made using "ATM Inverse ARP", "Classical IP and ARP" over ATM protocols and the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used. "Classical IP and ARP over ATM" is specified in IETF RFC 2225 [15]. "Multiprotocol Encapsulation over AAL5" is specified in IETF RFC 2684 [14].
+
+"Classical IP and ARP over ATM" allows routers to be members of one or more LISs. The CN side of the Iu interface shall provide IP routing functionalities. The RNC side of the Iu interface may provide routing functionalities. If the RNC side of the Iu interface does not provide routing functionalities, the RNC routing tables shall include default route entries.
+
+### 6.1.3 IP Transport Option
+
+#### 6.1.3.1 General
+
+In the IP transport option GTP-U (TS 29.060 [17]) over UDP over IP shall be supported as the transport for data streams on the Iu-PS interface. The data link layer is as specified in subclause 4.2.
+
+The transport bearer is identified by the GTP-U TEID (TS 29.060 [17]) and the IP address (source TEID, destination TEID, source IP address, destination IP address).
+
+#### 6.1.3.2 GTP-U
+
+The GTP-U (TS 29.060 [17]) protocol shall be used over the Iu interface toward the packet switched domain.
+
+#### 6.1.3.3 UDP /IP
+
+The path protocol used shall be UDP (IETF RFC 768 [12]).
+
+The UDP port number for GTP-U shall be as defined in TS 29.060 [17].
+
+An IP RNC/CN-node shall support IPv6. The support of IPv4 is optional.
+
+NOTE: This does not preclude single implementation and use of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+RNC shall support fragmentation and assembly of GTP packets at the IP layer.
+
+There may be one or several IP addresses in the RNC and in the CN. The packet processing function in the CN shall send downstream packets of a given RAB to the RNC IP address (received in RANAP) associated to that particular RAB. The packet processing function in the RNC shall send upstream packets of a given RAB to the CN IP address (received in RANAP) associated to that particular RAB.
+
+There is one RNC IP address per RNC in the CN associated with one MBMS RAB. This address is received in RANAP at the establishment of the MBMS RAB. The packet processing function in the CN shall send the downstream packets of the MBMS RAB to this associated RNC IP address.
+
+#### 6.1.3.4 Diffserv code point marking
+
+IP Differentiated Services code point marking (IETF RFC 2474 [19]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M for each traffic category. Traffic categories are implementation-specific and may be determined from the application parameters.
+
+## 6.2 Transport network control plane
+
+ALCAP is not required over the Iu interface towards the packet switched domain.
+
+# 7 Broadcast Domain
+
+## 7.1 Transport network user plane
+
+### 7.1.1 General
+
+There are two options for the transport layer for data streams over Iu-BC:
+
+- 1) ATM based Transport (ATM transport option)
+- 2) IP based Transport (IP transport option)
+
+The following figure shows the protocol stacks of the two options.
+
+![Figure 4: Transport network layer for data streams over Iu-BC. The diagram shows two protocol stacks. The left stack for the ATM transport option includes layers TCP, IP, AAL5, ATM, and Physical Layer. The right stack for the IP transport option includes layers TCP, IPv6 (RFC 2460) / IPv4 optional (RFC 791), Data Link Layer, and Physical Layer. The bottom layers (Physical Layer and Data Link Layer) are shown with dashed borders.](2de714cedbbdd36f901f71bafa78f75a_img.jpg)
+
+|                |
+|----------------|
+| TCP            |
+| IP             |
+| AAL5           |
+| ATM            |
+| Physical Layer |
+
+Protocol Stack  
+for the ATM transport option
+
+|                                            |
+|--------------------------------------------|
+| TCP                                        |
+| IPv6 (RFC 2460)<br>IPv4 optional (RFC 791) |
+| Data Link Layer                            |
+| Physical Layer                             |
+
+Protocol Stack  
+for the IP transport option
+
+Figure 4: Transport network layer for data streams over Iu-BC. The diagram shows two protocol stacks. The left stack for the ATM transport option includes layers TCP, IP, AAL5, ATM, and Physical Layer. The right stack for the IP transport option includes layers TCP, IPv6 (RFC 2460) / IPv4 optional (RFC 791), Data Link Layer, and Physical Layer. The bottom layers (Physical Layer and Data Link Layer) are shown with dashed borders.
+
+**Figure 4. Transport network layer for data streams over Iu-BC.**
+
+### 7.1.2 ATM Transport Option
+
+#### 7.1.2.1 General
+
+In the ATM transport option, the protocol architecture for the Service Area Broadcast Plane of the Iu interface shall be TCP over IP over AAL5 over ATM.
+
+#### 7.1.2.2 TCP/IP
+
+The path protocol used shall be TCP, which is specified in IETF RFC793 [18]. IPv4 (IETF RFC 791 [13]) shall be supported, IPv6 (IETF RFC 2460 [16]) support is optional.
+
+The TCP Destination Port number for SABP messages is 3452. It is the registered port number for SABP.
+
+The 3452 destination port number shall be used by both entities (RNC or CN) whenever it sets up a new TCP connection. When it sends SABP messages on an existing TCP connection, the sending entity (RNC or CN) shall use as TCP destination port number either 3452 if it was the initiator of this TCP connection, or the TCP source port number that was received from the peer entity that had initiated this existing TCP connection.
+
+#### 7.1.2.3 ATM Adaptation Layer Type 5 (I.363.5)
+
+AAL5 shall be used according to ITU-T Recommendation I.363.5.
+
+AAL5 virtual circuits shall be used to transport the IP packets across the Iu interface toward the broadcast domain. Multiple VCIs may be used over the interface. An association shall be made between a VCI and the IP addresses that are related to this VCI in the peer node side. This association shall be made using O&M or using ATM Inverse ARP according to Classical IP over ATM when PVCs are used.
+
+#### 7.1.2.4 IP/ATM
+
+When the association mentioned in 7.1.2.3 is made using O&M, the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used.
+
+When the association mentioned in 7.1.2.3 is made using "ATM Inverse ARP", "Classical IP and ARP over ATM" protocols and the "LLC encapsulation" option of "Multiprotocol Encapsulation over AAL5" shall be used to carry the IP packets over the ATM transport network when PVCs are used. "Classical IP and ARP over ATM" is specified in IETF RFC 2225 [15]. "Multiprotocol Encapsulation over AAL5" is specified in IETF RFC 2684 [14].
+
+### 7.1.3 IP Transport Option
+
+#### 7.1.3.1 General
+
+In the IP transport option TCP over IP shall be supported as the transport for data streams on the Iu-BC interface. The data link layer is as specified in subclause 4.2.
+
+The transport bearer is identified by the TCP port number and the IP address (source TCP port number, destination TCP port number, source IP address, destination IP address).
+
+#### 7.1.3.3 TCP/IP
+
+The path protocol used shall be TCP, which is specified in IETF RFC 793 [18].
+
+The TCP Destination Port number for SABP messages is 3452. It is the registered port number for SABP.
+
+The 3452 destination port number shall be used by both entities (RNC or CN) whenever it sets up a new TCP connection. When it sends SABP messages on an existing TCP connection, the sending entity (RNC or CN) shall use as TCP destination port number either 3452 if it was the initiator of this TCP connection, or the TCP source port number that was received from the peer entity that had initiated this existing TCP connection.
+
+An IP RNC/CN-node shall support IPv6. The support of IPv4 is optional.
+
+NOTE: This does not preclude single implementation and use of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+#### 7.1.3.4 Diffserv code point marking
+
+IP Differentiated Services code point marking (IETF RFC 2474 [19]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M for each traffic category. Traffic categories are implementation-specific and may be determined from the application parameters.
+
+## 7.2 Transport network control plane
+
+ALCAP is not required over the Iu interface towards the broadcast domain.
+
+
+
+# --- Annex A (informative): IP-ATM Interworking
+
+## A.1 Application of IP tunnelling in IP-ATM interworking alternative 1 in case of no direct ATM connectivity at the IP&ATM dual stack RNC/CN-node
+
+One possibility of enabling ATM connectivity to the IP&ATM dual stack RNC/CN-node in the IP-ATM interworking alternative 1 scenario specified in chapter 5.3.2 is to use any ATM emulation over IP protocol from the IETF standards e.g. via tunnelling techniques.
+
+## --- A.2 Application of IP-ALCAP in IP-ATM interworking alternative 2
+
+One example scenario of IP-ATM interworking alternative 2 of section 5.3.2 is to use IP-ALCAP as specified in ITU-T Recommendation Q.2631.1 (10/2003) as the bearer control protocol between the RNC/CN Node and its external IWF. The following figure shows the corresponding protocol stack.
+
+![Protocol stack diagram for IP-ALCAP in IP-ATM interworking alternative 2](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg)
+
+The diagram shows a vertical stack of five protocol layers. From top to bottom, they are: IP-ALCAP (Q.2631.1), Q.2150.3, SCTP (RFC2960), IPv6 (RFC2640) with IPv4 optional (RFC791), and Datalink Layer.
+
+|                                          |
+|------------------------------------------|
+| IP-ALCAP<br>(Q.2631.1)                   |
+| Q.2150.3                                 |
+| SCTP<br>(RFC2960)                        |
+| IPv6 (RFC2640)<br>IPv4 optional (RFC791) |
+| Datalink Layer                           |
+
+Protocol stack diagram for IP-ALCAP in IP-ATM interworking alternative 2
+
+Figure A.1. Protocol stack for IP-ALCAP in IP-ATM interworking alternative 2

marked/Rel-18/25_series/25422/raw.md

@@ -0,0 +1,254 @@
+
+
+# 3GPP TS 25.422 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iur interface signalling transport (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                               |                                                 |           |
+|-------------------------------|-------------------------------------------------|-----------|
+| 1                             | Scope.....                                      | 5         |
+| 2                             | References.....                                 | 5         |
+| 3                             | Abbreviations.....                              | 6         |
+| 4                             | Data Link Layer .....                           | 7         |
+| 4.1                           | ATM Transport Option .....                      | 7         |
+| 4.2                           | IP Transport Option.....                        | 7         |
+| 5                             | RNSAP Signalling Bearer.....                    | 7         |
+| 5.1                           | Introduction .....                              | 7         |
+| 5.2                           | Signalling Bearer.....                          | 8         |
+| 5.2.1                         | ATM Option 1 .....                              | 8         |
+| 5.2.2                         | ATM Option 2 .....                              | 8         |
+| 5.2.3                         | IP Transport Option.....                        | 9         |
+| 5.3                           | Services Provided by the Signalling Bearer..... | 9         |
+| <b>Annex A (informative):</b> | <b>Change history .....</b>                     | <b>10</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the standards for Signalling Transport to be used across Iur Interface. Iur Interface is a logical interface between the two RNC of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. The present document describes how the RNSAP signalling messages are transported between the two RNCs.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] ITU-T Recommendation Q.2100 (1994-07): "B-ISDN Signalling ATM Adaptation Layer (SAAL) - Overview description".
+- [2] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)".
+- [3] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer - Service Specific Co-ordination Function for signalling at the Network Node Interface (SSCF AT NNI)".
+- [4] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".
+- [5] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [6] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer specification: Type 5 AAL".
+- [7] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [8] ITU-T Recommendation Q.712 (1996-07): "Definition and function of Signalling connection control part messages".
+- [9] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [10] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [11] ITU-T Recommendation Q.715 (1996-07): "Signalling connection control part user guide".
+- [12] ITU-T Recommendation Q.716 (1993-03): "Signalling System No. 7 - Signalling Connection Control Part (SCCP) performance".
+- [13] IETF RFC 791 (September 1981): "Internet Protocol".
+- [14] IETF RFC 1483 (July 1993): "Multi protocol Encapsulation over ATM Adaptation Layer 5".
+- [15] IETF RFC 2225 (April 1998): "Classical IP and ARP over ATM".
+- [16] IETF RFC 2960 (October 2000): "Stream Control Transmission Protocol".
+- [17] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)"
+
+- [18] IETF STD 51, RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)".
+- [19] IETF STD 51, RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [20] IETF RFC 2507 (1999-02): "IP header compression".
+- [21] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [22] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [23] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [24] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (Ipv6) Specification".
+- [25] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [26] Void [27] IETF RFC 3153 (2001-08): "PPP Multiplexing".
+- [28] IETF RFC 2364 (1998-07): "PPP over AAL5".
+- [29] IETF RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture".
+- [30] IETF RFC 3309 (2002-09): "SCTP Checksum Change".
+- [31] ANSI T1.111-2001: "Signalling System Number 7 (SS7) - Message Transfer Part (MTP)".
+- [32] ANSI T1.112-2001: "Signaling System Number 7 (SS7) -- Signaling Connection Control Part (SCCP)".
+- [33] ANSI T1.645-1995 (R2003): "B-ISDN Signaling ATM Adaptation Layer - Service Specific Coordination Function for Support of Signaling at the Network Node Interface (SSCF at the NNI)".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|           |                                                          |
+|-----------|----------------------------------------------------------|
+| AAL       | ATM Adaptation Layer                                     |
+| AAL2      | ATM Adaptation Layer 2                                   |
+| AAL5      | ATM Adaptation Layer 5                                   |
+| ATM       | Asynchronous Transfer Mode                               |
+| DiffServ  | Differentiated Services                                  |
+| HDLC      | High level Data Link Control                             |
+| IP        | Internet Protocol                                        |
+| IPv4      | Internet Protocol, version 4                             |
+| IPv6      | Internet Protocol, version 6                             |
+| M3UA      | SS7 MTP3 User Adaptation layer                           |
+| ML/MC-PPP | Muti-Link/Multi-Class PPP                                |
+| MPLS      | Multiprotocol Label Switching                            |
+| MTP3-B    | Message Transfer Part level 3 for Q.2140                 |
+| PLMN      | Public Land Mobile Network                               |
+| PPP       | Point-to-Point protocol                                  |
+| PPPMux    | PPP Multiplexing                                         |
+| QoS       | Quality of Service                                       |
+| RNC       | Radio Network Controller                                 |
+| RNSAP     | Radio Network Subsystem Application Part                 |
+| SAAL-NNI  | Signalling ATM Adaptation Layer - Network Node Interface |
+| SCCP      | Signalling Connection Control Part                       |
+| SCTP      | Stream Control Transmission Protocol                     |
+| SSCF      | Service Specific Co-ordination Function                  |
+| SSCOP     | Service Specific Connection Oriented Protocol            |
+| UE        | User Equipment                                           |
+
+# --- 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the radio network control plane according to ITU-T Rec. I.361 [5]. The structure of the cell header used in the UTRAN Iur interface is the cell header format and encoding at NNI (see figure 3 of ITU-T Rec. I.361 [5]).
+
+## 4.2 IP Transport Option
+
+A UTRAN Node supporting IP transport option shall support PPP protocol with HDLC framing IETF RFC 1661 [18], IETF RFC 1662 [19].
+
+Note: This does not preclude the single implementation and use of any other data link layer protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [27], IETF RFC 2364 [28]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [29]), etc.) fulfilling the UTRAN requirements toward the upper layers.
+
+An RNC using IP transport option having interfaces connected via slow bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression IETF RFC 2507 [20] and the PPP extensions ML/MC-PPP IETF RFC 1990 [21], IETF RFC 2686 [22]. In this case, negotiation of header compression IETF RFC 2507 [20] over PPP shall be performed via IETF RFC 2509 [23].
+
+# --- 5 RNSAP Signalling Bearer
+
+## 5.1 Introduction
+
+This subclause specifies the Signalling Bearer protocol stack that supports the RNSAP signalling protocol.
+
+The following requirements on the RNSAP signalling bearer can be stated:
+
+- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode;
+- provide separate independent connections for distinguishing transactions with individual UEs;
+- supervise the "UE connections" and provide connection status information to the Upper Layers for individual UEs;
+- provide networking and routing functions;
+- provide redundancy in the signalling network;
+- provide load sharing.
+
+## 5.2 Signalling Bearer
+
+This subclause refers to specifications of the Signalling Bearer for the Radio Network Layer protocols. As shown in figure 1, the standard allows operators to choose one out of three protocol suites for transport of SCCP messages.
+
+![Figure 1: Signalling bearer for RNSAP. The diagram shows three protocol stacks for RNSAP transport. All three start with RNSAP at the top, connected via an SCCP-SAP to an SCCP layer. The first stack (ATM Transport Option 1) consists of SCCP, MTP3-B, SSCF-NNI, SSCOP, AAL5, and ATM. The second stack (ATM Transport Option 2) consists of SCCP, M3UA, SCTP, IP, Data Link, and PHY. The third stack (IP Transport Option) consists of SCCP, M3UA, SCTP, IP, Data Link, and PHY.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg)
+
+The diagram illustrates three protocol stacks for RNSAP transport, all sharing a common top section: RNSAP connected via an SCCP-SAP to an SCCP layer. The differences lie in the lower layers:
+
+- ATM Transport Option 1:** SCCP, MTP3-B, SSCF-NNI, SSCOP, AAL5, ATM.
+- ATM Transport Option 2:** SCCP, M3UA, SCTP, IP, Data Link, PHY.
+- IP Transport Option:** SCCP, M3UA, SCTP, IP, Data Link, PHY.
+
+Figure 1: Signalling bearer for RNSAP. The diagram shows three protocol stacks for RNSAP transport. All three start with RNSAP at the top, connected via an SCCP-SAP to an SCCP layer. The first stack (ATM Transport Option 1) consists of SCCP, MTP3-B, SSCF-NNI, SSCOP, AAL5, and ATM. The second stack (ATM Transport Option 2) consists of SCCP, M3UA, SCTP, IP, Data Link, and PHY. The third stack (IP Transport Option) consists of SCCP, M3UA, SCTP, IP, Data Link, and PHY.
+
+Figure 1: Signalling bearer for RNSAP
+
+### 5.2.1 ATM Option 1
+
+1. **SCCP** ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8]/ ITU-T Rec. Q.713 [9]/ ITU-T Rec. Q.714 [10]/ ITU-T Rec. Q.715 [11]/ ITU-T Rec. Q.716[12] or ANSI T1.112-2001 [32] provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis.
+2. **MTP3-B** ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31] provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded.
+3. **SAAL-NNI** ITU-T Rec. Q.2100 [1] consists of the following sub-layers: - **SSCF** ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 [33], - **SSCOP** ITU-T Rec. Q.2110 [2] and - **AAL5** ITU-T Rec. I.363.5 [6]. The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells.
+4. **ATM** ITU-T Rec. I.361 [5].
+
+### 5.2.2 ATM Option 2
+
+1. **SCCP.** See subclause 5.2.1
+2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 - User Adaptation Layer" IETF RFC 3332 [17] also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall
+
+support both the client and the server functionality towards another RNC. This enables the RNC to report to another RNC when it is a newly introduced entity in the network.
+
+3. **SCTP** refers to the Stream Control Transmission Protocol IETF RFC 2960 [16] developed by the Sigtran working group of the IETF for the purposes of transporting various signalling protocols over IP networks. The checksum method specified in RFC 3309 IETF RFC 3309 [30] shall be used instead of the method specified in IETF RFC 2960 [16].
+4. **IP** IETF RFC 791 [13] over ATM is defined in IETF RFC 1483 [14] and IETF RFC 2225 [15].
+5. **ATM** ITU-T Rec. I.361 [5].
+
+### 5.2.3 IP Transport Option
+
+1. **SCCP**. See subclause 5.2.1.
+2. **M3UA**: See subclause 5.2.2.
+3. **SCTP**. See subclause 5.2.2. In addition, Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint.
+4. **IP**. An IP UTRAN Node shall support IPv6 IETF RFC 2460 [24]. The support of IPv4 IETF RFC 791 [13] is optional.
+
+NOTE: This does not preclude single implementation of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network
+
+IP Differentiated Services code point marking IETF RFC 2474 [25] shall be supported. The Diffserv code point may be determined from the application parameters.
+
+5. Data link layer is as specified in chapter 4.2.
+
+## 5.3 Services Provided by the Signalling Bearer
+
+When considering the requirements that the upper layers, i.e. RNSAP, have on the Signalling Bearer, there are a number of services it has to provide and a number of functions to perform. These numbers of services that the signalling bearer shall provide, to the upper layers, are stated in the references ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8]/ ITU-T Rec. Q.713 [9]/ ITU-T Rec. Q.714 [10]/ ITU-T Rec. Q.715 [11]/ ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32].

marked/Rel-18/25_series/25424/raw.md

@@ -0,0 +1,322 @@
+
+
+# 3GPP TS 25.424 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN I<sub>ur</sub> Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                                                    |           |
+|----------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                     | 4         |
+| 1 Scope.....                                                                                       | 5         |
+| 2 References.....                                                                                  | 5         |
+| 3 Definitions and abbreviations .....                                                              | 6         |
+| 3.1 Definitions.....                                                                               | 6         |
+| 3.2 Abbreviations .....                                                                            | 6         |
+| 3.3 Specification Notations .....                                                                  | 7         |
+| 4 Data Link Layer .....                                                                            | 7         |
+| 4.1 ATM Transport Option .....                                                                     | 7         |
+| 4.2 IP Transport Option.....                                                                       | 8         |
+| 5 I <sub>ur</sub> Data Transport for Common Transport Channel Data Streams .....                   | 8         |
+| 5.1 Introduction .....                                                                             | 8         |
+| 5.2 ATM Transport Option .....                                                                     | 8         |
+| 5.3 IP Option .....                                                                                | 9         |
+| 6 I <sub>ur</sub> Transport Signalling Application for Common Transport Channel Data Streams ..... | 9         |
+| 6.1 Introduction .....                                                                             | 9         |
+| 6.2 Transport Signalling in case of ATM option .....                                               | 9         |
+| 6.3 Transport Signalling in case of IP Transport Option .....                                      | 10        |
+| 7 Signalling Bearer for ALCAP on I <sub>ur</sub> Interface .....                                   | 10        |
+| 7.1 ATM Transport Option .....                                                                     | 10        |
+| 7.2 IP Transport Option.....                                                                       | 10        |
+| 8 Interworking between ATM and IP Transport Options .....                                          | 10        |
+| <b>Annex A (informative): Change history .....</b>                                                 | <b>11</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document shall provide a specification of the UTRAN RNC-RNC (Iur) interface Data Transport and Transport Signalling for Common Transport Channel data streams.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM Layer Specification".
+- [2] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation Layer type 2".
+- [3] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Re-assembly Service Specific Convergence Sublayer for the AAL type 2".
+- [4] ITU-T Recommendation Q.2630.1 (1999-12): "AAL Type 2 signalling protocol (Capability Set 1)".
+- [5] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing".
+- [6] 3GPP TS 25.426: "UTRAN Iur and Iub interface data transport & transport signalling for DCH data streams".
+- [7] Void
+- [8] ITU-T Recommendation Q.2630.2 (2000-12): "AAL Type 2 signalling protocol (Capability Set 2)".
+- [9] ITU-T Recommendation X.213 (1995-11): "Information Technology - Open Systems Interconnection - Network Service Definition".
+- [10] IETF RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)".
+- [11] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [12] IETF RFC 2507 (1999-02): "IP header compression".
+- [13] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [14] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [15] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [16] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (Ipv6) Specification".
+- [17] IETF RFC 791 (1981-09): "Internet Protocol".
+- [18] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [19] IETF RFC 768 (1980-08): "User Datagram Protocol".
+
+- [20] IETF RFC 3153 (2001-08): "PPP Multiplexing".
+- [21] IETF RFC 2364 (1998-07): "PPP over AAL5".
+- [22] IETF RFC 3031 (2001-01):"Multiprotocol Label Switching Architecture".
+- [23] ITU-T Recommendation E.164 (1997-05): " The international public telecommunication numbering plan ".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Common Transport Channels are defined as transport channels that are shared by several users i.e. RACH, FACH, DSCH [TDD], USCH [TDD] and HS-DSCH.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|           |                                                        |
+|-----------|--------------------------------------------------------|
+| AAL2      | ATM Adaptation Layer type 2                            |
+| AAL5      | ATM Adaptation Layer type 5                            |
+| AESA      | ATM End System Address                                 |
+| ALCAP     | Access Link Control Application Part                   |
+| ATM       | Asynchronous Transfer Mode                             |
+| CPS       | Common Part Sublayer                                   |
+| DiffServ  | Differentiated Services                                |
+| DSCH      | Downlink Shared Channel                                |
+| FACH      | Forward Access Channel                                 |
+| HDLC      | High level Data Link Control                           |
+| HS-DSCH   | High Speed Downlink Shared Channel                     |
+| IP        | Internet Protocol                                      |
+| IPv4      | Internet Protocol, version 4                           |
+| IPv6      | Internet Protocol, version 6                           |
+| IWF       | Interworking Function                                  |
+| IWU       | Interworking Unit                                      |
+| LC        | Link Characteristics                                   |
+| ML/MC PPP | Multilink-Multiclass PPP                               |
+| MPLS      | Multiprotocol Label Switching                          |
+| MTP       | Message Transfer Part                                  |
+| NNI       | Network-Node Interface                                 |
+| NSAP      | Network Service Access Point                           |
+| PPP       | Point-to-Point Protocol                                |
+| PPPMux    | PPP Multiplexing                                       |
+| PT        | Path Type                                              |
+| QoS       | Quality of Service                                     |
+| RACH      | Random Access Channel                                  |
+| SAAL      | Signalling ATM Adaptation Layer                        |
+| SDU       | Service Data Unit                                      |
+| SSCOP     | Service Specific Connection Oriented Protocol          |
+| SSCF      | Service Specific Co-ordination Function                |
+| SSCS      | Service Specific Convergence Sublayer                  |
+| SSSAR     | Service Specific Segmentation and Re-assembly sublayer |
+| STC       | Signalling Transport Converter                         |
+| TNL       | Transport Network Layer                                |
+| UDP       | User Datagram Protocol                                 |
+| UNI       | User-Network Interface                                 |
+| USCH      | Uplink Shared Channel                                  |
+
+## 3.3 Specification Notations
+
+For the purposes of the present document, the following notations apply:
+
+- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD.
+- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD.
+- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.
+- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.
+- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.
+- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.
+- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.
+- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.
+- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs.
+- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs.
+
+# --- 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the transport network user plane and the transport network control plane according to ITU-T Recommendation I.361 [1]. The structure of the cell header used in the UTRAN Iur interface is the cell header format and encoding at NNI (see Figure 3/I.361 [1]).
+
+## 4.2 IP Transport Option
+
+A UTRAN Node supporting IP transport option shall support PPP protocol with HDLC framing (IETF RFC 1661 [10], IETF RFC 1662 [11]).
+
+Note: This does not preclude the single implementation and use of any other data link layer protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [20], IETF RFC 2364 [21]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [22]), etc.) fulfilling the UTRAN requirements toward the upper layers.
+
+An RNC using IP transport option having interfaces connected via slow bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [12]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [13]), (IETF RFC 2686 [14]). In this case, negotiation of header compression (IETF RFC 2507 [12]) over PPP shall be performed via IETF RFC 2509 [15].
+
+# 5 Iur Data Transport for Common Transport Channel Data Streams
+
+## 5.1 Introduction
+
+This clause specifies the transport layers that support Common Channels (FACH, RACH, DSCH [TDD], USCH [TDD], HS-DSCH) Iur data streams.
+
+There are two options for the transport layer of the Common Channels data streams in Iur and Iub:
+
+- 1) ATM based Transport (ATM transport option)
+- 2) IP based Transport (IP transport option)
+
+The following figure shows the protocol stacks of the two options.
+
+![Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces. The diagram shows two protocol stacks. The left stack is for the ATM transport option, showing layers: Radio Network Layer, AAL2 SSSAR (I.366.1), AAL2 CPS (I.363.2), ATM, and Physical layer. The right stack is for the IP transport option, showing layers: Radio Network Layer, UDP (RFC768), IPv6 (RFC2460), IPv4 optional (RFC791), Data link layer, and Physical layer. Both stacks are labeled 'Transport Network Layer' on the left.](740442c999390734911677f01af0316d_img.jpg)
+
+The diagram illustrates two protocol stacks for DCH data streams over Iur and Iub interfaces. Both stacks are labeled 'Transport Network Layer' on the left.
+
+**Protocol stack for ATM transport option:**
+
+- Radio Network Layer
+- AAL2 SSSAR (I.366.1)
+- AAL2 CPS (I.363.2)
+- ATM
+- Physical layer
+
+**Protocol stack for IP transport option:**
+
+- Radio Network Layer
+- UDP (RFC768)
+- IPv6 (RFC2460)
+- IPv4 optional (RFC791)
+- Data link layer
+- Physical layer
+
+Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces. The diagram shows two protocol stacks. The left stack is for the ATM transport option, showing layers: Radio Network Layer, AAL2 SSSAR (I.366.1), AAL2 CPS (I.363.2), ATM, and Physical layer. The right stack is for the IP transport option, showing layers: Radio Network Layer, UDP (RFC768), IPv6 (RFC2460), IPv4 optional (RFC791), Data link layer, and Physical layer. Both stacks are labeled 'Transport Network Layer' on the left.
+
+Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces
+
+## 5.2 ATM Transport Option
+
+ATM (ITU-T Rec. I.361 [1]), AAL type 2 (ITU-T Recommendations I.363.2 [2] and ITU-T Rec. I.366.1 [3]) is used as the standard transport layer for RACH, FACH, USCH [TDD], DSCH [TDD] and HS-DSCH Iur data streams.
+
+These AAL2 connections are established via the transport signalling protocol described in clause 5.
+
+Figure 1 shows the protocol stack for the transport of RACH, FACH, USCH [TDD], DSCH [TDD] and HS-DSCH Iur data streams using the ATM Transport Option. Service Specific Segmentation and Re-assembly (SSSAR) is used for the segmentation and re-assembly of AAL2 SDUs (i.e. SSSAR is only considered from ITU-T Recommendation I.366.1 [3]).
+
+## 5.3 IP Option
+
+UDP (IETF RFC 768 [19]) over IP shall be used as the transport for RACH, FACH, USCH [TDD], DSCH [TDD] and HS-DSCH data streams on Iur. The data link layer is as specified in subclause 4.2.
+
+An IP UTRAN Node shall support IPv6 (IETF RFC 2460 [16]). The support of IPv4 (IETF RFC 791 [17]) is optional.
+
+Note: This does not preclude single implementation of IPv4.
+
+IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+The transport bearer is identified by the UDP port number and the IP address (source UDP port number, destination UDP port number, source IP address, destination IP address).
+
+IP Differentiated Services code point marking (IETF RFC 2474 [18]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M. Traffic categories are implementation-specific and may be determined from the application parameters.
+
+# --- 6 I<sub>ur</sub> Transport Signalling Application for Common Transport Channel Data Streams
+
+## 6.1 Introduction
+
+This clause specifies the transport signalling protocol(s) used to establish the user plane transport bearers. The protocol stack is shown in TS 25.426 [6].
+
+## 6.2 Transport Signalling in case of ATM option
+
+AAL2 signalling protocol Capability Set 2, ITU-T Recommendation Q.2630.2 [8], is the signalling protocol to control the AAL2 connections on Iur interfaces. ITU-T Rec. Q.2630.2 [8] adds new optional capabilities to ITU-T Rec. Q.2630.1 [4].
+
+AAL2 transport layer addressing is based on embedded E.164 or other AESA variants of the NSAP addressing format ITU-T Rec. E.191 [5], ITU-T Rec. X.213 [9]. Native E.164 (ITU-T Rec. E.164 [23]) addressing shall not be used.
+
+Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH.request primitive of ITU-T Rec. Q.2630.2 [8]. The binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iur interface in the Drift RNC.
+
+User Plane Transport bearers are established by the ALCAP in Serving RNC, and in all normal cases released by the ALCAP in the RNC which established the AAL2 connection.
+
+The Link Characteristics parameter (LC) shall be included in the Establish Request message and in the Modification Request message of AAL2 signalling protocol.
+
+If there is an AAL2 switching function in the transport network layer of the interface, the Path Type parameter (PT) may be included in the Establish Request message of AAL2 signalling protocol for prioritisation at ATM level.
+
+If the value in either the Maximum CPS-SDU Bit Rate or the Average CPS-SDU Bit Rate of the Link Characteristics(LC) in AAL 2 signalling messages as specified in reference ITU-T Rec. Q.2630.2 [8] is 2048 Kbit/s, it shall be interpreted as bit rate 2048 Kbit/s or higher.
+
+NOTE: Separation of traffic (e.g. HS-DSCH) that is using this modified interpretation of Link Characteristics in ref. ITU-T Rec. Q.2630.2 [8] from other traffic is highly recommended. Otherwise the potential bursty nature of this specific traffic in combination with its unknown bit rate may decrease the QoS of all traffic within the same AAL type 2 path.
+
+## 6.3 Transport Signalling in case of IP Transport Option
+
+An ALCAP protocol is not required in case both RNCs are using the IP transport option.
+
+# --- 7 Signalling Bearer for ALCAP on I<sub>ur</sub> Interface
+
+## 7.1 ATM Transport Option
+
+The signalling bearer for the ALCAP on the I<sub>ur</sub> interface for common transport channels data streams is the same as the signalling bearer for the ALCAP on the I<sub>ur</sub> interface for DCH data streams, defined in TS 25.426 [6].
+
+## 7.2 IP Transport Option
+
+An ALCAP protocol is not required in case both RNCs are using the IP transport option.
+
+# --- 8 Interworking between ATM and IP Transport Options
+
+An RNC supporting IP transport option shall provide interworking to an RNC supporting only ATM transport option. The interworking alternatives are defined in TS 25.426 [6].

marked/Rel-18/25_series/25430/raw.md

@@ -0,0 +1,920 @@
+
+
+# 3GPP TS 25.430 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub interface: general aspects and principles (Release 18)**
+
+![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G ADVANCED logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                             |    |
+|-----------------------------------------------------------------------------|----|
+| Foreword .....                                                              | 5  |
+| 1 Scope.....                                                                | 6  |
+| 2 References.....                                                           | 6  |
+| 3 Definitions and abbreviations .....                                       | 6  |
+| 3.1 Definitions.....                                                        | 6  |
+| 3.2 Abbreviations .....                                                     | 7  |
+| 3.3 Specification Notations .....                                           | 8  |
+| 4 General Aspects .....                                                     | 9  |
+| 4.1 Introduction .....                                                      | 9  |
+| 4.2 Iub Interface General Principles.....                                   | 9  |
+| 4.3 Iub Interface Specification Objectives .....                            | 9  |
+| 4.4 Iub Interface Capabilities .....                                        | 9  |
+| 4.4.1 Radio application related signalling .....                            | 9  |
+| 4.4.2 Iub/Iur DCH data stream .....                                         | 10 |
+| 4.4.3 Iub RACH data stream .....                                            | 10 |
+| 4.4.4 Iub CPCH data stream [FDD] .....                                      | 10 |
+| 4.4.5 Iub FACH data stream.....                                             | 10 |
+| 4.4.6 Iub DSCH data stream [TDD].....                                       | 10 |
+| 4.4.7 Iub USCH data stream [TDD].....                                       | 10 |
+| 4.4.8 Iub PCH data stream.....                                              | 10 |
+| 4.4.9 Iub FDD TFCI2 data stream.....                                        | 10 |
+| 4.4.10 Iub HS-DSCH data stream .....                                        | 11 |
+| 4.4.11 Iub E-DCH data stream .....                                          | 11 |
+| 4.5 Iub Interface Characteristics.....                                      | 11 |
+| 4.5.1 Mapping of Iub data streams .....                                     | 11 |
+| 4.6 Iub Protocols .....                                                     | 11 |
+| 5 Functions of the I <sub>ub</sub> Interface Protocols .....                | 12 |
+| 5.1 Iub Functions.....                                                      | 12 |
+| 5.2 Functional split over Iub .....                                         | 13 |
+| 5.2.1 Management of Iub Transport Resources.....                            | 13 |
+| 5.2.2 Logical O&M of Node B.....                                            | 13 |
+| 5.2.2.1 Handling of Node B Hardware Resources.....                          | 13 |
+| 5.2.3 Implementation Specific O&M Transport.....                            | 13 |
+| 5.2.4 System Information Management .....                                   | 13 |
+| 5.2.5 Traffic management of Common Channels.....                            | 14 |
+| 5.2.6 Traffic management of Dedicated Channels .....                        | 14 |
+| 5.2.6.1 Combining/Splitting and Control.....                                | 14 |
+| 5.2.6.2 Handover Decision .....                                             | 14 |
+| 5.2.6.3 Allocation of Physical Channel Resources .....                      | 14 |
+| 5.2.6.4 UpLink Power Control.....                                           | 14 |
+| 5.2.6.5 Down-Link Power Control .....                                       | 15 |
+| 5.2.6.6 Admission Control.....                                              | 15 |
+| 5.2.6.7 Power and Interference Reporting .....                              | 15 |
+| 5.2.7 Traffic management of Shared Channels [TDD] .....                     | 15 |
+| 5.2.7A Traffic management of High Speed Shared Channels.....                | 15 |
+| 5.2.8 Timing and Synchronization Management .....                           | 15 |
+| 6 Node B logical Model over Iub.....                                        | 15 |
+| 6.1 Overview .....                                                          | 15 |
+| 6.2 Elements of the logical model.....                                      | 16 |
+| 6.2.1 Node B Communication Contexts for Dedicated and Shared Channels ..... | 16 |
+| 6.2.2 Common Transport Channels.....                                        | 17 |
+| 6.2.3 Transport network logical resources.....                              | 17 |
+| 6.2.3.1 Node B Control Port .....                                           | 17 |
+
+|                               |                                                                                                                             |           |
+|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-----------|
+| 6.2.3.2                       | Communication Control Port.....                                                                                             | 17        |
+| 6.2.3.3                       | Traffic Termination Point .....                                                                                             | 17        |
+| 6.2.3.4                       | Iub DCH Data Port .....                                                                                                     | 18        |
+| 6.2.3.5                       | Iub RACH Data Port.....                                                                                                     | 18        |
+| 6.2.3.6                       | Iub CPCH Data Port [FDD].....                                                                                               | 18        |
+| 6.2.3.7                       | Iub FACH Data Port .....                                                                                                    | 18        |
+| 6.2.3.8                       | Iub DSCH Data Port [TDD] .....                                                                                              | 18        |
+| 6.2.3.8A                      | Iub HS-DSCH Data Port.....                                                                                                  | 18        |
+| 6.2.3.9                       | Iub USCH Data Port [TDD] .....                                                                                              | 18        |
+| 6.2.3.10                      | Iub PCH Data Port .....                                                                                                     | 18        |
+| 6.2.3.11                      | Iub FDD TFCI2 Data Port .....                                                                                               | 18        |
+| 6.2.3.12                      | Iub E-DCH Data Port.....                                                                                                    | 18        |
+| 6.2.4                         | Radio Network Logical resources .....                                                                                       | 19        |
+| 6.2.4.1                       | Common Resources .....                                                                                                      | 19        |
+| 6.2.4.2                       | Cell.....                                                                                                                   | 19        |
+| 6.2.4.3                       | Common Physical Channels and Common Transport Channels .....                                                                | 21        |
+| 6.2.4.4                       | Physical Shared Channels .....                                                                                              | 22        |
+| 7                             | Iub Interface Protocol Structure.....                                                                                       | 23        |
+| 8                             | Other Iub Interface Specifications .....                                                                                    | 23        |
+| 8.1                           | UTRAN Iub Interface: Layer 1 (TSG RAN 25.431) .....                                                                         | 23        |
+| 8.2                           | UTRAN Iub Interface: Signalling Transport (TSG RAN 25.432).....                                                             | 23        |
+| 8.3                           | NBAP Specification (TSG RAN 25.433) .....                                                                                   | 24        |
+| 8.4                           | UTRAN Iub Interface: Data Transport & Transport Signalling for Common Transport Channel Data Streams (TSG RAN 25.434) ..... | 24        |
+| 8.5                           | UTRAN Iub Interface: User Plane Protocols for Common Transport Channel Data Streams (TSG RAN 25.435).....                   | 24        |
+| 8.6                           | UTRAN Iur/Iub Interface: Data Transport & Transport Signalling for DCH Data Streams (TSG RAN 25.426).....                   | 24        |
+| 8.7                           | UTRAN Iur/Iub Interface: User Plane Protocol for DCH Data Streams (TSG RAN 25.427) .....                                    | 24        |
+| 8.8                           | Summary of UTRAN Iub Interface Technical Specifications .....                                                               | 25        |
+| <b>Annex A (informative):</b> | <b>Change history.....</b>                                                                                                  | <b>26</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document is an introduction to the TSG RAN TS 25.43x series of UMTS Technical Specifications that define the Iub Interface. The Iub interface is a logical interface for the interconnection of Node B and Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TS 25.401: "UTRAN overall description".
+- [2] 3GPP TS 25.442: "UTRAN implementation-specific O&M transport".
+- [3] 3GPP TS 25.432: "UTRAN Iub interface: signalling transport".
+- [4] 3GPP TS 25.302: "Services provided by the physical layer".
+- [5] 3GPP TS 25.431: "UTRAN Iub interface layer 1".
+- [6] Void
+- [7] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling".
+- [8] 3GPP TS 25.434: "UTRAN Iub Interface Data Transport and Transport Signalling for Common Transport Channel Data Streams".
+- [9] 3GPP TS 25.435: "UTRAN Iub Interface user plane protocols for Common Transport Channel data streams".
+- [10] 3GPP TS 25.426: "UTRAN Iur and Iub Interface data transport & transport signalling for DCH data streams".
+- [11] 3GPP TS 25.427: "UTRAN Iur/Iub Interface user plane protocol for DCH data streams".
+- [12] 3GPP TS 25.402: "Synchronization in UTRAN Stage 2".
+- [13] ITU-T Recommendation Q.2630.2 (1999-12): "AAL type 2 Signalling Protocol (Capability Set 2)".
+- [14] 3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Propagation delay (PD):** it is the round trip propagation delay of the radio signal from the Node B to the UE and back to the BS in one chip resolution.
+
+**Timing Advance (TA):** it is the amount of time, expressed in number of chips, by which the transmission of an uplink burst is anticipated by the UE in order to be received by the cell inside the corresponding time slot.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|          |                                                                  |
+|----------|------------------------------------------------------------------|
+| AAL2     | ATM Adaptation Layer type 2                                      |
+| AAL5     | ATM Adaptation Layer type 5                                      |
+| AICH     | Acquisition Indication Channel                                   |
+| ALCAP    | Access Link Control Application Part                             |
+| ATM      | Asynchronous Transfer Mode                                       |
+| BCH      | Broadcast Channel                                                |
+| BCCH     | Broadcast Control Channel                                        |
+| CCH      | Control Channel                                                  |
+| CPCId    | Common Physical Channel Identifier                               |
+| CPICH    | Common Pilot Channel                                             |
+| CTCId    | Common Transport Channel Identifier                              |
+| CRNC     | Controlling Radio Network Controller                             |
+| DCH      | Dedicated Transport Channel                                      |
+| DPCCH    | Dedicated Physical Control Channel                               |
+| DPCH     | Dedicated Physical Channel                                       |
+| DSCH     | Down-link Shared Channel                                         |
+| E-DCH    | Enhanced Dedicated Channel                                       |
+| FACH     | Forward Access Channel                                           |
+| FAUSCH   | Fast Up-link Signalling Channel                                  |
+| FDD      | Frequency Division Duplex                                        |
+| F-DPCH   | Fractional DPCH                                                  |
+| HARQ     | Hybrid Automatic Repeat Request                                  |
+| HS-DSCH  | High Speed Downlink Shared Channel                               |
+| IP       | Internet Protocol                                                |
+| MICH     | MBMS notification Indicator Channel                              |
+| NBAP     | Node B Application Part                                          |
+| O&M      | Operation and Maintenance                                        |
+| PICH     | Page Indication Channel                                          |
+| PCCH     | Paging Control Channel                                           |
+| PCCPCH   | Primary Common Control Physical Channel                          |
+| PCPICH   | Primary Common Pilot Channel                                     |
+| PCH      | Paging Channel                                                   |
+| PDSCH    | Physical Downlink Shared Channel                                 |
+| PLCCH    | Physical Layer Common Control Channel                            |
+| PRACH    | Physical Random Access Channel                                   |
+| PUSCH    | Physical Uplink Shared Channel                                   |
+| RACH     | Random Access Channel                                            |
+| RNC      | Radio Network Controller                                         |
+| RNS      | Radio Network Subsystem                                          |
+| SCH      | Synchronization Channel                                          |
+| SCCPCH   | Secondary Common Control Physical Channel                        |
+| SCPICH   | Secondary Common Pilot Channel                                   |
+| SCTP     | Stream Control Transmission Protocol                             |
+| SRNC     | Serving Radio Network Controller                                 |
+| SSCF-UNI | Service Specific Co-ordination Function - User Network Interface |
+| SSCOP    | Service Specific Connection Oriented Protocol                    |
+| TDD      | Time Division Duplex                                             |
+| UE       | User Equipment                                                   |
+| UC-ID    | UTRAN Cell Identifier                                            |
+| UDP      | User Datagram Protocol                                           |
+| UMTS     | Universal Mobile Telecommunication System                        |
+
+|       |                                       |
+|-------|---------------------------------------|
+| USCH  | Up-link Shared Channel                |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+
+## 3.3 Specification Notations
+
+For the purposes of the present document, the following notations apply:
+
+- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD.
+- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD.
+- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.
+- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.
+- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.
+- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.
+- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.
+- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs.
+- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.
+- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs.
+- Procedure When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Network Layer procedures.
+- Message When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message.
+- Frame When referring to a control or data frame in the specification the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH transport frame.
+
+# 4 General Aspects
+
+## 4.1 Introduction
+
+The logical interface between a RNC and a Node B is called the Iub interface.
+
+## 4.2 Iub Interface General Principles
+
+The general principles for the specification of the Iub interface are as follows:
+
+- Transmission sharing between the GSM/GPRS Abis interface and the Iub interface shall not be precluded.
+- The functional division between RNC and Node B shall have as few options as possible.
+- Iub should be based on a logical model of Node B.
+- Node B controls a number of cells and can be ordered to add/remove radio links in those cells.
+- Neither the physical structure nor any internal protocols of the Node B shall be visible over Iub and are thus not limiting factors, e.g., when introducing future technology.
+- Only the logical O&M (TS 25.401 [1]) of Node B is supported by the Iub.
+- Complex functionality shall as far as possible be avoided over Iub. Advanced optimisation solutions may be added in later versions of the standard.
+- The Iub functional split shall take into account the probability of frequent switching between different channel types.
+
+## 4.3 Iub Interface Specification Objectives
+
+The I<sub>ub</sub> interface specifications shall facilitate the following:
+
+- Inter-connection of RNCs and Node Bs from different manufacturers.
+- Separation of I<sub>ub</sub> interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology.
+
+The Iub parts to be standardised are:
+
+1. User data transport.
+2. Signalling for handling the user data.
+3. Node B Logical O&M (TS 25.401 [1]).
+
+Note: It should be possible to transport the Implementation Specific O&M (TS 25.401 [1]) interface via the same transport bearer as the Iub interface and, hence, the lower layer transport mechanisms should be standardised to this effect. The application level content of the Implementation Specific O&M interface is out of scope of UTRAN standardization. Where the implementation specific O&M interface shares the same bearer as the Iub interface, the transport layers shall be as specified in TS 25.442 [2] and TS 25.432 [3] respectively.
+
+## 4.4 Iub Interface Capabilities
+
+### 4.4.1 Radio application related signalling
+
+The Iub interface allows the RNC and the Node B to negotiate about radio resources, for example to add and delete cells controlled by the Node B to support communication of the dedicated connection between UE and SRNC.
+
+Information used to control the broadcast channel and information to be transported on the broadcast channel belongs to this category also. In addition, logical O&M (TS 25.401 [1]) between the Node B and RNC shall also be included in this category.
+
+### 4.4.2 Iub/Iur DCH data stream
+
+The Iub interface provides the means for transport of uplink and downlink DCH transport frames between RNC and Node B. An Iub/Iur DCH data stream corresponds to the data carried on one DCH transport channel.
+
+In the UTRAN, one DCH data stream always corresponds to a bi-directional transport channel. Although the TFS is configured separately for each DCH direction and a DCH could be configured with e.g. only a zero-bit transport format in one direction, the DCH is always treated as a bi-directional transport channel in the UTRAN. As a result, two uni-directional Uu DCH transport channels with opposite directions can be mapped to either one or two DCH transport channels in the UTRAN.
+
+### 4.4.3 Iub RACH data stream
+
+The Iub interface provides the means for transport of uplink RACH transport frames between Node B and RNC. An Iub RACH data stream corresponds to the data carried on one RACH transport channel.
+
+### 4.4.4 Iub CPCH data stream [FDD]
+
+Void.
+
+### 4.4.5 Iub FACH data stream
+
+The Iub interface provides the means for transport of downlink FACH transport frames between RNC and Node B. An Iub FACH data stream corresponds to the data carried on one FACH transport channel.
+
+### 4.4.6 Iub DSCH data stream [TDD]
+
+The Iub interface provides the means for transport of downlink shared channel, DSCH, data frames between RNC and Node B. An Iub DSCH data stream corresponds to the data carried on one DSCH transport channel for one UE. A UE may have multiple DSCH data streams.
+
+### 4.4.7 Iub USCH data stream [TDD]
+
+The Iub interface provides the means for transport of uplink shared channel, USCH, data frames between Node B and RNC. An Iub USCH data stream corresponds to the data carried on one USCH transport channel for one UE. A UE may have multiple USCH data streams.
+
+### 4.4.8 Iub PCH data stream
+
+The Iub interface provides the means for transport of PCH transport frames between RNC and Node B. An Iub PCH data stream corresponds to the data carried on one PCH transport channel.
+
+### 4.4.9 Iub FDD TFCI2 data stream
+
+Void.
+
+### 4.4.10 Iub HS-DSCH data stream
+
+The Iub interface provides the means for transport of high speed downlink shared channel, HS-DSCH, data frames between RNC and Node B. An Iub HS-DSCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple HS-DSCH data streams.
+
+### 4.4.11 Iub E-DCH data stream
+
+The Iub interface provides the means for transport of uplink E-DCH transport frames between Node B and RNC. An Iub E-DCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple E-DCH data streams.
+
+In addition, the interface provides the following:
+
+- A means for the Node B to indicate the number of HARQ retransmissions to the SRNC (TS 25.427 [11]);
+- A means to indicate to the SRNC, for the purposes of re-ordering, the CFN and Subframe Number that have been added by the Node B (TS 25.427 [11]).
+
+## 4.5 Iub Interface Characteristics
+
+### 4.5.1 Mapping of Iub data streams
+
+|                     |                                                                                                                                                                                                                                                                                                                               |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>DCH</b>          | One Iub DCH data stream is carried on one transport bearer. For each DCH data stream a transport bearer must be established over Iub, except in the case of coordinated DCHs in which case a set of coordinated DCHs are multiplexed onto the same transport bearer.                                                          |
+| <b>RACH</b>         | One Iub RACH data stream is carried on one transport bearer. For each RACH in a cell, a transport bearer must be established over the Iub interface.                                                                                                                                                                          |
+| <b>FACH</b>         | One Iub FACH data stream is carried on one transport bearer. For each FACH in a cell, a transport bearer must be established over the Iub Interface, except in case of transport bearer sharing for MBMS, where only one transport bearer is established at the Iub interface for several FACHs belonging to different cells. |
+| <b>[TDD - DSCH]</b> | One Iub DSCH data stream is carried on one transport bearer. For each DSCH data stream, a transport bearer must be established over the Iub interface.]                                                                                                                                                                       |
+| <b>HS-DSCH</b>      | One Iub HS-DSCH data stream is carried on one transport bearer. For each HS-DSCH data stream, a transport bearer must be established over the Iub interface.                                                                                                                                                                  |
+| <b>E-DCH</b>        | One Iub E-DCH data stream is carried on one transport bearer. For each E-DCH data stream, a transport bearer must be established over the Iub interface.]                                                                                                                                                                     |
+| <b>[TDD - USCH]</b> | One Iub USCH data stream is carried on one transport bearer. For each USCH data stream, a transport bearer must be established over the Iub interface.]                                                                                                                                                                       |
+| <b>PCH</b>          | One Iub PCH data stream is carried on one transport bearer.                                                                                                                                                                                                                                                                   |
+
+## 4.6 Iub Protocols
+
+There shall exist a clear separation between the radio network layer and the transport layer. Therefore, the radio network signalling and Iub data streams are separated from the data transport resource and traffic handling as shown in figure 1. This resource and traffic handling is controlled by the Transport Signalling. The Transport Signalling is carried by a Signalling Bearer over the Iub interface.
+
+![Diagram illustrating the separation of Radio Network protocols and transport over Iub. The diagram shows two layers: Radio Network layer and Transport layer. In the Radio Network layer, there are two components: Radio Signaling Protocol and Iub Data Streams. In the Transport layer, there are three components: Signalling Bearer, Transport Signalling, and Data Transport. Arrows indicate the flow of data and signaling between the layers. The Radio Signaling Protocol connects to the Signalling Bearer, which in turn connects to the Transport Signalling. The Iub Data Streams connect to the Data Transport, which also connects to the Transport Signalling. A dashed arrow points from the Transport Signalling to the Data Transport.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+
+graph TD
+    subgraph RNL [Radio Network layer]
+        RSP((Radio Signaling Protocol))
+        IDS((Iub Data Streams))
+    end
+    subgraph TL [Transport layer]
+        SB[Signalling Bearer]
+        TS[Transport Signalling]
+        DT[Data Transport]
+    end
+    RSP <--> SB
+    SB --> TS
+    IDS <--> DT
+    DT --> TS
+    TS -.-> DT
+  
+```
+
+Diagram illustrating the separation of Radio Network protocols and transport over Iub. The diagram shows two layers: Radio Network layer and Transport layer. In the Radio Network layer, there are two components: Radio Signaling Protocol and Iub Data Streams. In the Transport layer, there are three components: Signalling Bearer, Transport Signalling, and Data Transport. Arrows indicate the flow of data and signaling between the layers. The Radio Signaling Protocol connects to the Signalling Bearer, which in turn connects to the Transport Signalling. The Iub Data Streams connect to the Data Transport, which also connects to the Transport Signalling. A dashed arrow points from the Transport Signalling to the Data Transport.
+
+Figure 1: Separation of Radio Network protocols and transport over Iub
+
+# 5 Functions of the I<sub>ub</sub> Interface Protocols
+
+## 5.1 Iub Functions
+
+The list of functions on the Iub interface is the following:
+
+1. Management of Iub Transport Resources;
+2. Logical O&M of Node B:
+  - Iub Link Management;
+  - Cell Configuration Management;
+  - Radio Network Performance Measurements;
+  - Resource Event Management;
+  - Common Transport Channel Management;
+  - Radio Resource Management;
+  - Radio Network Configuration Alignment;
+3. Implementation Specific O&M Transport;
+4. System Information Management;
+5. Traffic Management of Common Channels:
+  - Admission Control;
+  - Power Management;
+  - Data Transfer;
+6. Traffic Management of Dedicated Channels:
+  - Radio Link Management;
+  - Radio Link Supervision;
+  - Channel Allocation / De-allocation;
+  - Power Management;
+  - Measurement Reporting;
+
+- Dedicated Transport Channel Management;
+  - Data Transfer;
+7. Traffic Management of Shared Channels:
+- Channel Allocation / De-allocation;
+  - Power Management;
+  - Transport Channel Management;
+  - Dynamic Physical Channel Assignment;
+  - Radio Link Management;
+  - Data Transfer;
+8. Timing and Synchronization Management:
+- Transport Channel Synchronization (Frame synchronization);
+  - Node B - RNC node Synchronization;
+  - Inter Node B node Synchronization.
+
+## 5.2 Functional split over Iub
+
+### 5.2.1 Management of Iub Transport Resources
+
+The underlying transport resources (AAL2 and UDP/IP transport bearers) shall be set up and controlled by the RNC. Further information on these functions is provided in the transport layer specifications (TS 25.432 [3], TS 25.434 [8], TS 25.426 [10]).
+
+### 5.2.2 Logical O&M of Node B
+
+Logical O&M is the signalling associated with the control of logical resources (channels, cells,...) owned by the RNC but physically implemented in the Node B. The RNC controls these logical resources. A number of O&M procedures physically implemented in Node B impact on the logical resources and therefore require an information exchange between RNC and Node B. All messages needed to support this information exchange are classified as Logical O&M forming an integral part of NBAP over the Iub interface.
+
+#### 5.2.2.1 Handling of Node B Hardware Resources
+
+Mapping of Node B logical resources onto Node B hardware resources, used for Iub data streams and radio interface transmission/reception, is performed by Node B.
+
+### 5.2.3 Implementation Specific O&M Transport
+
+The Iub interface may support the transport of Implementation specific O&M information. Further detail on this can be found in the UMTS technical specification on Implementation Specific O&M Transport (TS 25.442 [2]).
+
+### 5.2.4 System Information Management
+
+System Information is sent by the CRNC to a Node B. CRNC can also request the Node B to autonomously create and update certain Node B related system information. Scheduling of system broadcast information is carried out in the CRNC. Scheduling information is always sent by the CRNC to the Node B. The Node B is responsible for transmitting the received system information according to the scheduling parameters provided. If requested by the CRNC, the Node B is also responsible for autonomously creating and updating the Node B related system information according to the scheduling parameters provided.
+
+### 5.2.5 Traffic management of Common Channels
+
+The common channels need to be controlled from the RNC. This is typically the control of the RACH and FACH channels, the information that is broadcast on the Broadcast control channel, and the control and request for sending information on the paging channels.
+
+### 5.2.6 Traffic management of Dedicated Channels
+
+These functions are related to the activation of logical resources (e.g. Radio Links, Iub ports), and the connection of these various resources together.
+
+[FDD - Some freedom may be left for Node B implementation on some functions like soft combining within Node B, since soft combining has merits for being executed as close as possible to the radio (both in terms of transmission cost and efficiency).]
+
+#### 5.2.6.1 Combining/Splitting and Control
+
+Node B may perform combining/splitting of DCH data streams communicated via its cells. RNC performs combining/splitting of Iub data streams received from/sent to several Node B(s).
+
+The UL combining of information streams may be performed using any suitable algorithm, for example:
+
+- [FDD - based on maximum ratio algorithm (maximum ratio combining)];
+- [FDD - based on quality information associated to each TBS (selection-combining)];
+- [TDD - based on the presence/absence of the signal (selection)].
+
+When requesting the addition of a new cell for a UE-UTRAN connection, the RNC can explicitly request to the Node B a new Iub data stream, in which case the combining and splitting function within the Node B is not used for that cell. Otherwise, the Node B takes the decision whether combining and splitting function is used inside the Node B for that cell i.e. whether a new Iub data stream shall be added or not.
+
+The internal Node B handling of the combining/splitting of radio frames is controlled by the Node B.
+
+For E-DCH combining of UL streams in the Node B is mandatory as described in TS 25.319 [14].
+
+#### 5.2.6.2 Handover Decision
+
+To support mobility of the UE to UTRAN connection between cells, UTRAN uses measurement reports from the UE and detectors at the cells.
+
+The RNC takes the decision to add or delete cells from the connection.
+
+#### 5.2.6.3 Allocation of Physical Channel Resources
+
+In FDD allocation of downlink channelisation codes of cells belonging to Node B is performed in the CRNC.
+
+In TDD allocation of uplink and downlink physical channel resources of cells belonging to Node B is performed in the CRNC.
+
+#### 5.2.6.4 UpLink Power Control
+
+This function controls the level of the transmitted power in order to minimise interference and keep the quality of the connections. The function uplink Outer Loop Power Control located in the SRNC sets the target quality for the uplink Inner Loop Power Control function, for E-DCH the Node B reports the number of HARQ retransmissions to the SRNC as an input to the Outer Loop Power Control function. In FDD and 1.28Meps TDD, Inner Loop Power Control Function is located in Node B, while in 3.84Meps TDD it is located in the UE.
+
+#### 5.2.6.5 Down-Link Power Control
+
+This function controls the level of the downlink transmitted power. In FDD it is also used to correct the downlink power drifting between several radio links. A SRNC regularly (or under some algorithms) shall send the target down link power range based on the measurement report from UE.
+
+#### 5.2.6.6 Admission Control
+
+The Admission Control function based on uplink interference and downlink power is located in the CRNC.
+
+Node B shall report uplink interference measurements and downlink power information over the Iub.
+
+The CRNC controls this reporting function, i.e. if this information needs to be reported and the period of these reports.
+
+#### 5.2.6.7 Power and Interference Reporting
+
+A threshold for reporting may be given to Node B from the CRNC to prevent frequent reporting over the Iub. Node B shall have a function to measure "uplink interference level and downlink TX Power" and a function to compare the averaged "uplink interference level and downlink TX power" with the threshold value. Node B shall also have a function to report when the average measured value exceeds the threshold value. The CRNC shall have a function to modify the "threshold value" for neighbour cell co-ordination.
+
+An indication of exceeding uplink interference threshold or downlink TX power may be included as a cause of failure when a Node B is requested to set-up a radio link or add to an existing radio link. This may be used when a number of radio links set-up requests or additions are received on the Iub during the reporting interval.
+
+### 5.2.7 Traffic management of Shared Channels [TDD]
+
+The shared channels shall be controlled from the RNC. This is typically the control of the TDD DSCH channels and the TDD USCH channels.
+
+### 5.2.7A Traffic management of High Speed Shared Channels
+
+The high speed shared channels shall be controlled from the Node B. This includes the control of the HS-DSCH channels as well as the required control channels on the radio interface.
+
+### 5.2.8 Timing and Synchronization Management
+
+The Iub interface shall support timing and synchronization management functions. Further detail regarding these functions can be found in the UMTS technical specification on UTRAN synchronization (TS 25.402 [12]).
+
+# --- 6 Node B logical Model over Iub
+
+## 6.1 Overview
+
+The model described in figure 2 shows the Node B as seen from the controlling RNC. The model includes:
+
+- The logical resources provided by Node B to UTRAN (via its Controlling RNC) - depicted as "cells" which include the physical channel resources DPCH, [FDD – F-DPCH] [TDD - PDSCH and PUSCH];
+- The dedicated channels which have been established on Node B;
+- The common transport channels that Node B provides to the RNC.
+
+The procedures for controlling the connections between radio links and Iub DCH data ports are sent from the RNC to the Node B via the Communication Control Ports.
+
+![Figure 2: Logical Model of Node B. The diagram shows a 'Controlling RNC' at the top connected to a 'Node B' below. The Node B contains two main components: 'Common Transport Channels, with attributes' and 'Node B Communication Contexts, with attributes'. Above these components are two 'Traffic termination point' boxes. The left traffic termination point includes ports for Node B Control Port, Iub RACH Data port, Iub FACH Data port, Iub PCH Data port, HS-DSCH Data port, Iub TDD DSCH Data port, TDD USCH Data port, Iub DCH Data port, Iub E-DCH Data port, and a Communication Control Port. The right traffic termination point includes ports for HS-DSCH Data port, Iub TDD DSCH Data port, TDD USCH Data port, Iub DCH Data port, Iub E-DCH Data port, and a Communication Control Port. Below the Node B components are several 'Cell' circles.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+Figure 2: Logical Model of Node B. The diagram shows a 'Controlling RNC' at the top connected to a 'Node B' below. The Node B contains two main components: 'Common Transport Channels, with attributes' and 'Node B Communication Contexts, with attributes'. Above these components are two 'Traffic termination point' boxes. The left traffic termination point includes ports for Node B Control Port, Iub RACH Data port, Iub FACH Data port, Iub PCH Data port, HS-DSCH Data port, Iub TDD DSCH Data port, TDD USCH Data port, Iub DCH Data port, Iub E-DCH Data port, and a Communication Control Port. The right traffic termination point includes ports for HS-DSCH Data port, Iub TDD DSCH Data port, TDD USCH Data port, Iub DCH Data port, Iub E-DCH Data port, and a Communication Control Port. Below the Node B components are several 'Cell' circles.
+
+**Figure 2: Logical Model of Node B**
+
+## 6.2 Elements of the logical model
+
+### 6.2.1 Node B Communication Contexts for Dedicated and Shared Channels
+
+A Node B Communication Context corresponds to all the dedicated resources that are necessary for a user in dedicated mode and using dedicated and/or shared channels as restricted to a given Node B. [TDD - The Node B Communication Context also exists for users in Cell\_FACH mode (i.e. non-dedicated mode) provided a USCH and/or DSCH and/or HS-DSCH has been allocated to these users.]
+
+There are a number of Node B Communication Contexts inside a given Node B.
+
+The attributes to a Node B Communication Context shall include the following (not exhaustive):
+
+- The list of Cells where dedicated and/or shared physical resources are used.
+- The list of DCH which are mapped on the dedicated physical resources for that Node B Communication Context.
+- [TDD - The list of DSCH and USCH which are used by the respective UE.]
+- The list of HS-DSCH MAC-d flows which are used by the respective UE.
+- The list of E-DCH MAC-d flows which are used by the respective UE.]
+- The complete DCH characteristics for each DCH, identified by its DCH-identifier (TS 25.302 [4]).
+- [TDD - The complete Transport Channel characteristics for each DSCH and USCH, identified by its Shared Channel identifier (TS 25.302 [4]).]
+- The complete HS-DSCH characteristics for each HS-DSCH MAC-d Flow, identified by its HS-DSCH MAC-d Flow identifier (TS 25.302 [4]).
+- The complete E-DCH characteristics for each E-DCH MAC-d Flow, identified by its E-DCH MAC-d Flow identifier (TS 25.302 [4]).]
+- The list of Iub DCH Data Ports.
+- [TDD - The list of Iub DSCH Data ports and Iub USCH data ports.]
+- The list of Iub HS-DSCH Data ports.
+- The list of Iub E-DCH Data ports.]
+- For each Iub DCH Data Port, the corresponding DCH and cells which are carried on this data port.
+
+- [TDD - For each Iub DSCH and USCH data port, the corresponding DSCH or USCH and cell which serves that DSCH or USCH.]
+- For each Iub HS-DSCH data port, the corresponding HS-DSCH data stream and cell which serves that HS-DSCH data stream.
+- Physical layer parameters (outer loop power control, etc).
+
+### 6.2.2 Common Transport Channels
+
+Common Transport Channels are defined in TS 25.435 [9]. A Common Transport Channel is configured in the Node B, on request of the CRNC.
+
+The BCH is carried directly on the Node B control port using NBAP procedures. This Common Channel will not be mapped to an individual data port.
+
+The RACH has an associated Iub RACH Data Port and the FACH has an associated Iub FACH Data Port.
+
+[TDD - The Iub DSCH data port is associated to one DSCH and to one Node B Communication Context.]
+
+[TDD - the Iub USCH data port is associated to one USCH and to one Node B Communication Context.]
+
+The attributes of a Common transport channel shall include (not exhaustive):
+
+- Type (RACH, FACH, DSCH [TDD], USCH [TDD], PCH).
+- Associated Iub RACH Data Port for a RACH, Iub FACH Data Port for a FACH, Iub PCH Data Port for the PCH.
+- Physical parameters.
+
+[TDD - The DSCHs used by one UE are multiplexed to one or several CCTrCHs where each CCTrCH is mapped to a set of PDSCH ("PDSCH Set"). These PDSCH Sets are included in the Common Transport Channel data base. The same applies for the USCHs and the corresponding PUSCH Sets.]
+
+### 6.2.3 Transport network logical resources
+
+#### 6.2.3.1 Node B Control Port
+
+The Node B Control Port is used to exchange the signalling information for the logical O&M of Node B, the creation of Node B Communication Contexts, the configuration of the common transport channels that Node B provides in a given cell, PCH and BCH control information between the RNC and the Node B. The Node B Control Port corresponds to one signalling bearer between the controlling RNC and the Node B. There is one Node B Control Port per Node B.
+
+#### 6.2.3.2 Communication Control Port
+
+A Communication Control Port corresponds to one signalling bearer between the RNC and Node B for the control of Node B Communication Contexts. One signalling bearer between RNC and Node B can at most correspond to one Communication Control Port. Node B may have multiple Communication Control Ports (one per Traffic Termination Point). The Communication Control Port is selected at creation of the Node B Communication Context. The Communication Control Port is re-selected when the signalling bearer for the control of Node B Communication is rearranged.
+
+#### 6.2.3.3 Traffic Termination Point
+
+Traffic Termination Point represents DCH, DSCH [TDD], USCH [TDD], HS-DSCH and E-DCH data streams belonging to one or more Node B Communication Contexts (UE contexts), which are controlled via one Communication Control Port. The Traffic Termination Point is thus a descriptive entity which neither is controlled over Iub nor by O&M.
+
+#### 6.2.3.4 Iub DCH Data Port
+
+One Iub DCH Data port represents one user plane transport bearer. One user plane transport bearer will carry only one DCH data stream except in the case of coordinated DCHs, in which case the data streams of all combined DCHs shall be multiplexed on one and the same user plane transport bearer.
+
+#### 6.2.3.5 Iub RACH Data Port
+
+An Iub RACH Data Port represents a user plane bearer carrying one Iub RACH Data Stream between the Node B and the RNC. There is one RACH Data Port for each RACH channel of Node B.
+
+#### 6.2.3.6 Iub CPCH Data Port [FDD]
+
+Void.
+
+#### 6.2.3.7 Iub FACH Data Port
+
+An Iub FACH Data Port represents a user plane bearer carrying one Iub FACH Data Stream between the Node B and the RNC. There is one FACH Data Port for each FACH channel of Node B.
+
+#### 6.2.3.8 Iub DSCH Data Port [TDD]
+
+An Iub DSCH Data Port represents a user plane bearer carrying one Iub DSCH Data Stream between the Node B and the RNC. For each DSCH, that is used by an individual UE, there is one Iub DSCH Data Port per Node B exclusively assigned to the communication context of that UE.
+
+#### 6.2.3.8A Iub HS-DSCH Data Port
+
+An Iub HS-DSCH Data Port represents a user plane bearer carrying one Iub HS-DSCH Data Streams between the Node B and the RNC.
+
+#### 6.2.3.9 Iub USCH Data Port [TDD]
+
+An Iub USCH Data Port represents a user plane bearer carrying one Iub USCH Data Stream between the Node B and the RNC. For each USCH, that is used by an individual UE, there is one Iub USCH Data Port with data exclusively assigned to the Node B communication context of that UE.
+
+#### 6.2.3.10 Iub PCH Data Port
+
+An Iub PCH Data Port represents an Iub PCH Data Stream between the Node B and the RNC.
+
+#### 6.2.3.11 Iub FDD TFCI2 Data Port
+
+Void.
+
+#### 6.2.3.12 Iub E-DCH Data Port
+
+An Iub E-DCH Data Port represents a user plane bearer carrying one Iub E-DCH Data Stream between the Node B and the RNC.
+
+### 6.2.4 Radio Network Logical resources
+
+#### 6.2.4.1 Common Resources
+
+The CRNC manages logical radio network resources in Node B and needs to use both common and dedicated resources in a Node B to run a radio network. Therefore, it is the CRNC that orders the Node B to configure, reconfigure and delete these resources. However, if the equipment in Node B cannot fully support the configuration that the CRNC requests, or the equipment breaks down, then Node B can indicate the availability of the common resources (i.e. both downgrade and upgrade).
+
+The common resources are the Cell, the common physical channels and the common transport channels.
+
+In Node B these common resources have an operational state, that indicates whether they are operational or not, i.e. whether they can carry traffic or not.
+
+Figure 3 shows the common resources that a CRNC is managing in a Node B to be able to run a radio network.
+
+![Figure 3: Common resources in a Node B that are managed by the CRNC. The diagram shows a hierarchy of resources starting from the Cell (Cell-Id) at the top. The Cell is connected to several groups of channels. The first group contains PCPICH (1), SCPICH (0-m), SCH1 (1), and SCH2 (1), labeled [FDD Only]. The second group contains PCCPCH (1), PICH (0-i), MICH (0-1), SCCPCH (0-i), PRACH (0-k), and AICH (0-k), labeled [FDD Only]. The third group contains E-RUCCH (0-t) and SCH (1), labeled [3.84 Mcps TDD, 7.68 Mcps TDD Only]. The fourth group contains UpPCH (1), DwPCH (1), FPACH (0-r), and PLCCH (0-s), labeled [1.28 Mcps TDD Only]. The diagram also shows relationships between physical channels (CPCId) and transport channels (CTCId).](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg)
+
+The diagram illustrates the hierarchy of common resources in a Node B managed by the CRNC. At the top is the **Cell** (Cell-Id). Below it, the resources are organized into several groups:
+
+- [FDD Only] Group:**
+  - PCPICH (CPCId) - 1 instance
+  - SCPICH (CPCId) - 0 to m instances
+  - SCH1 (CPCId) - 1 instance
+  - SCH2 (CPCId) - 1 instance
+- Physical Channels (CPCId) Group:**
+  - PCCPCH (CPCId) - 1 instance, connected to 1 instance of BCH (CTCId)
+  - PICH (CPCId) - 0 to i instances
+  - MICH (CPCId) - 0 to 1 instance
+  - SCCPCH (CPCId) - 0 to i instances, connected to 0 to 1 instance of PCH (CTCId) [FDD 1] [TDD ≥ 1]
+  - PRACH (CPCId) - 0 to k instances, connected to 1 instance of RACH (CTCId)
+  - AICH (CPCId) - 0 to k instances [FDD Only]
+- [3.84 Mcps TDD, 7.68 Mcps TDD Only] Group:**
+  - E-RUCCH (CPCId) - 0 to t instances
+  - SCH (CPCId) - 1 instance
+- [1.28 Mcps TDD Only] Group:**
+  - UpPCH - 1 instance
+  - DwPCH (CPCId) - 1 instance
+  - FPACH (CPCId) - 0 to r instances
+  - PLCCH (CPCId) - 0 to s instances
+
+Figure 3: Common resources in a Node B that are managed by the CRNC. The diagram shows a hierarchy of resources starting from the Cell (Cell-Id) at the top. The Cell is connected to several groups of channels. The first group contains PCPICH (1), SCPICH (0-m), SCH1 (1), and SCH2 (1), labeled [FDD Only]. The second group contains PCCPCH (1), PICH (0-i), MICH (0-1), SCCPCH (0-i), PRACH (0-k), and AICH (0-k), labeled [FDD Only]. The third group contains E-RUCCH (0-t) and SCH (1), labeled [3.84 Mcps TDD, 7.68 Mcps TDD Only]. The fourth group contains UpPCH (1), DwPCH (1), FPACH (0-r), and PLCCH (0-s), labeled [1.28 Mcps TDD Only]. The diagram also shows relationships between physical channels (CPCId) and transport channels (CTCId).
+
+The number or range above each box indicates how many of the channels named in that box can exist as "children" under one instant of a "parent" box to which the "child" box is connected.
+
+The number or range beneath each box indicates how many of the channels named in that box can exist as "parent" boxes for one instant of a "child" channel to which the "parent" box is connected.
+
+CPCId = Common Physical Channel Identifier
+
+CTCId = Common Transport Channel Identifier
+
+[TDD - The number of PICH = the number of PCH]
+
+[FDD - The number of AICH = the number of PRACH]
+
+[TDD - PCH and FACHs can be mapped on one or more SCCPCH]
+
+**Figure 3: Common resources in a Node B that are managed by the CRNC**
+
+#### 6.2.4.2 Cell
+
+A Cell is identified by a UTRAN Cell identifier (UC-id) (TS 25.401 [1]).
+
+The semantics of a Cell include the following:
+
+- The Cell can be created and removed by administrative procedures. When a Local Cell, i.e. equipment in a Node B, is made available to the CRNC for configuration of a cell, the CRNC can configure the cell with configuration data, common physical channels and common transport channels in Node B. In so doing a Local cell is added to the RNS.
+- If any Iub transport bearers for common or dedicated transport channels exist when the cell is deleted, the Node B shall initiate the release of those transport bearers.
+- Node B may support one or more cells. [1.28Mcps TDD - A cell may support one or more frequencies. If multiple frequencies are configured in one cell, the cell is called the multi-frequency cell.]
+- Configuration of a cell over the Iub interface cannot be successful unless Node B has reported a Local Cell Id (TS 25.401 [1]) as available to the CRNC.
+- Once a Local Cell is configured to support a cell, it cannot be deleted without the CRNC first deleting the cell.
+
+Figure 4 illustrates the state diagram for a Local Cell in Node B, as seen over the Iub interface.
+
+![State diagram for a Local Cell in Node B. It shows two states: 'Not existing' and 'Existing'. A transition from 'Not existing' to 'Existing' is triggered by 'Local Cell defined and taken into service' with the action 'Resource Status Indication: Add/Delete Indicator=Add'. A transition from 'Existing' to 'Not existing' is triggered by 'Local Cell withdrawn' with the action 'Resource Status Indication: Add/Delete Indicator=Delete'. A legend indicates that bold text represents the trigger and italics represent the action.](3da1a07cb87051bf616c9876db958cf0_img.jpg)
+
+```
+stateDiagram-v2
+    [*] --> Not existing
+    Not existing --> Existing : Local Cell defined and taken into service  
+Resource Status Indication: Add/Delete Indicator=Add
+    Existing --> Not existing : Local Cell withdrawn  
+Resource Status Indication: Add/Delete Indicator=Delete
+```
+
+**Bold represents the trigger**  
+*Italics represent the action*
+
+State diagram for a Local Cell in Node B. It shows two states: 'Not existing' and 'Existing'. A transition from 'Not existing' to 'Existing' is triggered by 'Local Cell defined and taken into service' with the action 'Resource Status Indication: Add/Delete Indicator=Add'. A transition from 'Existing' to 'Not existing' is triggered by 'Local Cell withdrawn' with the action 'Resource Status Indication: Add/Delete Indicator=Delete'. A legend indicates that bold text represents the trigger and italics represent the action.
+
+**Figure 4: States for a Local Cell that are seen over the Iub interface**
+
+Cells in Node B have a resource operational state.
+
+Figure 5 illustrates the state diagram for the states of a cell, as seen over the Iub interface.
+
+![State diagram for a cell in Node B showing three states: Not existing, Enabled, and Disabled. Transitions are triggered by specific events and result in specific actions.](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Not existing
+    Not existing --> Enabled: Cell is created / Cell Setup Request
+    Enabled --> Not existing: Cell is deleted / Cell Delete Request
+    Enabled --> Disabled: Total resource capability reduction / Resource Status Indication: Op.State=Disabled
+    Disabled --> Enabled: Resource capability increase / Resource Status Indication: Op.State=Enable
+    Disabled --> Not existing: Cell is deleted / Cell Delete Request
+  
+```
+
+**Bold represents the trigger**  
+*Italics represent the action*
+
+State diagram for a cell in Node B showing three states: Not existing, Enabled, and Disabled. Transitions are triggered by specific events and result in specific actions.
+
+**Figure 5: States for a cell in Node B, as reported to the CRNC**
+
+There are three states seen over the Iub interface:
+
+1. Not existing, meaning that the cell does not exist in Node B.
+2. Enabled, meaning that the resource can be used by the RNC.
+3. Disabled, meaning that the resource cannot be used by the RNC.
+
+When a cell becomes disabled in Node B, that shall be reported to the CRNC together with the cause.
+
+#### 6.2.4.3 Common Physical Channels and Common Transport Channels
+
+Common physical channels and common transport channels in Node B have a resource operational state.
+
+Figure 6 illustrates the state diagram for common physical channels and common transport channels in Node B, as seen over the Iub interface.
+
+![State transition diagram for a common channel in Node B. The diagram shows three states: 'Not Existing', 'Enabled', and 'Disabled'. Transitions are triggered by specific messages and result in specific actions. Transitions from 'Not Existing' to 'Enabled' are triggered by 'Channel is created' (Cell Setup Request or Common Transport Channel Setup Request). Transitions from 'Enabled' to 'Not Existing' are triggered by 'Channel is deleted' (Cell Delete Request or Common Transport Channel Delete Request). Transitions from 'Enabled' to 'Disabled' are triggered by 'Total resource capability reduction' (Resource Status Indication: Op.State=Disabled). Transitions from 'Disabled' to 'Enabled' are triggered by 'Resource capability increase' (Resource Status Indication: Op.State=Enable). A long transition from 'Disabled' back to 'Not Existing' is also triggered by 'Channel is deleted' (Cell Delete Request or Common Transport Channel Delete Request).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Not_Existing : Channel is created  
+Cell Setup Request or Common Transport Channel Setup Request
+    Not_Existing --> Enabled : Channel is deleted  
+Cell Delete Request or Common Transport Channel Delete Request
+    Enabled --> Not_Existing : Channel is deleted  
+Cell Delete Request or Common Transport Channel Delete Request
+    Enabled --> Disabled : Total resource capability reduction  
+Resource Status Indication: Op.State=Disabled
+    Disabled --> Enabled : Resource capability increase  
+Resource Status Indication: Op.State=Enable
+    Disabled --> Not_Existing : Channel is deleted  
+Cell Delete Request or Common Transport Channel Delete Request
+  
+```
+
+**Bold represents the trigger**  
+*Italics represent the action*
+
+State transition diagram for a common channel in Node B. The diagram shows three states: 'Not Existing', 'Enabled', and 'Disabled'. Transitions are triggered by specific messages and result in specific actions. Transitions from 'Not Existing' to 'Enabled' are triggered by 'Channel is created' (Cell Setup Request or Common Transport Channel Setup Request). Transitions from 'Enabled' to 'Not Existing' are triggered by 'Channel is deleted' (Cell Delete Request or Common Transport Channel Delete Request). Transitions from 'Enabled' to 'Disabled' are triggered by 'Total resource capability reduction' (Resource Status Indication: Op.State=Disabled). Transitions from 'Disabled' to 'Enabled' are triggered by 'Resource capability increase' (Resource Status Indication: Op.State=Enable). A long transition from 'Disabled' back to 'Not Existing' is also triggered by 'Channel is deleted' (Cell Delete Request or Common Transport Channel Delete Request).
+
+**Figure 6: States for a common channel in Node B, as reported to the CRNC**
+
+There are three states seen over the Iub interface:
+
+1. Not existing, meaning that the resource does not exist in Node B;
+2. Enabled, meaning that the resource can be used by the RNC;
+3. Disabled, meaning that the resource cannot be used by the RNC.
+
+When a channel becomes disabled in the Node B, this shall be reported to the CRNC together with the cause.
+
+#### 6.2.4.4 Physical Shared Channels
+
+Physical Shared Channels includes [TDD - the Physical Downlink Shared Channels (PDSCH), the Physical Uplink Shared Channels (PUSCH) and] the High Speed Physical Shared Channels (HS-PDSCH). [TDD - These PDSCH and PUSCH [TDD] are special cases of the Common Physical Channels].
+
+[FDD - A HS-PDSCH is defined by a channelisation code within a code subtree that is configured within a specific Communication Context. The HS-PDSCH is activated dynamically as part of the HS-DSCH scheduling.]
+
+[TDD - A PDSCH is defined by a channelisation code, a time slot and other Physical Channel parameters. Several PDSCH may be grouped into a PDSCH Set, which is given a "PDSCH Set Id". The PDSCH Sets are configured in the Node B in the "Common Transport Channel" data base by Common NBAP messages. These PDSCH Sets are available to carry DSCH data. The PDSCH Sets are dynamically activated to carry DSCH data, as part of the DSCH scheduling.]
+
+[TDD - A HS-PDSCH is defined by a channelisation code, a time slot and other Physical Channel parameters. The HS-PDSCH is activated dynamically as part of the HS-DSCH scheduling.]
+
+[TDD - A PUSCH is defined by a channelisation code, a time slot and other Physical Channel parameters. Several PUSCH may be grouped into a PUSCH Set, which is given a "PUSCH Set Id". The PUSCH Sets are configured in the Node B in the "Common Transport Channel" data base by Common NBAP messages. These PUSCH Sets are available to carry USCH data. The PUSCH Sets are dynamically activated to carry USCH data, as part of the USCH scheduling.]
+
+# 7 Iub Interface Protocol Structure
+
+![Figure 7: Iub Interface Protocol Structure. A diagram showing the protocol stack for the Iub interface, divided into three vertical sections: Radio Network Control Plane, Transport Network Control Plane, and User Plane. The stack consists of four layers: Radio Network Layer, Transport Layer, and Physical Layer (at the bottom). The Radio Network Layer contains the Node B Application Part (NBAP) in the control plane and various FPs (DCH FP, RACH FP, FACH FP, PCH FP, HS-DSCH FP, TDD DSCH FP, USCH FP, TF12 FP, E-DCH FP) in the user plane. The Transport Layer includes ALCAP (Q.2630.2), Q.2150.2, SSCF-UNI, SSCOP, AAL 5, and ATM in the control plane, and SSCF-UNI, SSCOP, AAL5, IP, ATM, and Data Link Layer in the user plane. The Physical Layer is common to all planes.](844077b3034f0030b404207db0ad76b4_img.jpg)
+
+The diagram illustrates the Iub Interface Protocol Structure, organized into three main vertical sections: Radio Network Control Plane, Transport Network Control Plane, and User Plane. The horizontal layers are Radio Network Layer, Transport Layer, and Physical Layer.
+
+- Radio Network Layer:**
+  - Radio Network Control Plane:** Contains the Node B Application Part (NBAP).
+  - User Plane:** Contains several FPs: DCH FP, RACH FP, FACH FP, PCH FP, HS-DSCH FP, TDD DSCH FP, USCH FP, TF12 FP, and E-DCH FP.
+- Transport Layer:**
+  - Transport Network Control Plane:** Contains ALCAP (Q.2630.2), Q.2150.2, SSCF-UNI, SSCOP, AAL 5, and ATM.
+  - User Plane:** Contains SSCF-UNI, SSCOP, AAL5, IP, ATM, and Data Link Layer.
+- Physical Layer:** Common to all planes.
+
+Figure 7: Iub Interface Protocol Structure. A diagram showing the protocol stack for the Iub interface, divided into three vertical sections: Radio Network Control Plane, Transport Network Control Plane, and User Plane. The stack consists of four layers: Radio Network Layer, Transport Layer, and Physical Layer (at the bottom). The Radio Network Layer contains the Node B Application Part (NBAP) in the control plane and various FPs (DCH FP, RACH FP, FACH FP, PCH FP, HS-DSCH FP, TDD DSCH FP, USCH FP, TF12 FP, E-DCH FP) in the user plane. The Transport Layer includes ALCAP (Q.2630.2), Q.2150.2, SSCF-UNI, SSCOP, AAL 5, and ATM in the control plane, and SSCF-UNI, SSCOP, AAL5, IP, ATM, and Data Link Layer in the user plane. The Physical Layer is common to all planes.
+
+Figure 7: Iub Interface Protocol Structure.
+
+The Iub interface protocol architecture consists of two functional layers:
+
+1. Radio Network Layer, defines procedures related to the operation of Node B. The radio network layer consists of a radio network control plane and a radio network user plane.
+2. Transport Layer, defines procedures for establishing physical connections between Node B and the RNC with AAL type 2 Signalling Protocol (Capability Set 2) (ITU-T Rec. Q.2630.2 [13]).
+
+There shall be one dedicated AAL2 or UDP/IP transport bearer for each RACH, and one for each FACH transport channel or for each set of FACH transport channels in case of transport bearer sharing (see section 4.5.1).
+
+# 8 Other Iub Interface Specifications
+
+## 8.1 UTRAN Iub Interface: Layer 1 (TSG RAN 25.431)
+
+This document (TS 25.431 [5]) specifies the standards allowed for the implement of Layer 1 (physical layer) on the Iub interface.
+
+## 8.2 UTRAN Iub Interface: Signalling Transport (TSG RAN 25.432)
+
+This document (TS 25.432 [3]) specifies the signalling transport related to NBAP signalling to be used across the Iub Interface.
+
+## 8.3 NBAP Specification (TSG RAN 25.433)
+
+This document (TS 25.433 [7]) specifies the standards for NBAP specification to be used over Iub Interface.
+
+## 8.4 UTRAN Iub Interface: Data Transport & Transport Signalling for Common Transport Channel Data Streams (TSG RAN 25.434)
+
+This document (TS 25.434 [8]) provides a specification of the UTRAN RNC-Node B (Iub) interface Data Transport and Transport Signalling for Common Transport Channel data streams.
+
+## 8.5 UTRAN Iub Interface: User Plane Protocols for Common Transport Channel Data Streams (TSG RAN 25.435)
+
+This document (TS 25.435 [9]) provides a specification of the UTRAN RNC-Node B (Iub) interface user plane protocols for Common Transport Channel data streams.
+
+## 8.6 UTRAN Iur/Iub Interface: Data Transport & Transport Signalling for DCH Data Streams (TSG RAN 25.426)
+
+This Technical Specification (TS 25.426 [10]) specifies the transport bearers for the DCH data streams on UTRAN Iur and Iub interfaces. The corresponding Transport Network Control plane is also specified.
+
+## 8.7 UTRAN Iur/Iub Interface: User Plane Protocol for DCH Data Streams (TSG RAN 25.427)
+
+This document (TS 25.427 [11]) provides a specification of the UTRAN Iur and Iub interfaces user plane protocols for Dedicated Transport Channel data streams.
+
+## 8.8 Summary of UTRAN Iub Interface Technical Specifications
+
+The relationship between the technical specifications that define the UTRAN Iub interface is shown in figure 8.
+
+![Diagram showing the relationship between technical specifications for the UTRAN Iub interface across different layers and planes.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg)
+
+The diagram illustrates the technical specifications for the UTRAN Iub interface, organized by layer and plane. It is structured as a grid with three main columns: Radio Network Control Plane, Transport Network Control Plane, and User Plane. The rows represent the layers: Radio Network Layer, Transport Layer, and Physical Layer.
+
+|                     | Radio Network Control Plane        | Transport Network Control Plane                                          | User Plane                                      |                                              |
+|---------------------|------------------------------------|--------------------------------------------------------------------------|-------------------------------------------------|----------------------------------------------|
+| Radio Network Layer | NBAP<br><b>TS 25.433</b>           |                                                                          | Dedicated Channels<br><b>TS 25.427</b>          | Common Channels<br><b>TS 25.435</b>          |
+| Transport Layer     |                                    | Transport Signaling<br><b>TS 25.426</b><br>(Dedicated Channel Transport) |                                                 |                                              |
+|                     | NBAP Transport<br><b>TS 25.432</b> | <b>TS 25.434</b><br>(Common Channel Transport)                           | Dedicated Channel Transport<br><b>TS 25.426</b> | Common Channel Transport<br><b>TS 25.434</b> |
+| Physical Layer      | Physical Layer <b>TS 25.431</b>    |                                                                          |                                                 |                                              |
+
+Diagram showing the relationship between technical specifications for the UTRAN Iub interface across different layers and planes.
+
+Figure 8: Iub Interface Technical Specifications.

marked/Rel-18/25_series/25431/raw.md

@@ -0,0 +1,114 @@
+
+
+# 3GPP TS 25.431 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub interface layer 1 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+- Foreword ..... 4
+- 1 Scope..... 5
+- 2 References..... 5
+- 3 Definitions and abbreviations ..... 5
+- 4 Iub Layer 1 ..... 5
+- Annex A (informative): Change history..... 6**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the standards allowed to implement Layer 1 on the Iub interface.
+
+The specification of transmission delay requirements and O&M requirements is not in the scope of this document.
+
+In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TS 25.411: "UTRAN Iu interface Layer 1".
+
+[2] ATM Forum AF-PHY-0130.00 (1999-10): "ATM on Fractional E1/T1".
+
+# --- 3 Definitions and abbreviations
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.411 [1] apply.
+
+# --- 4 Iub Layer 1
+
+The Iub Layer 1 shall comply with the requirements of chapter 4 in TS 25.411 [1].
+
+In addition, for the Iub Layer 1, it shall be possible to use n 64 kbit/s time slots within the scope of "ATM on Fractional E1/T1" as specified in ATM Forum AF-PHY-0130.00 [2], and to allow the co-existence of this interface with other interfaces on the same physical medium.

marked/Rel-18/25_series/25432/raw.md

@@ -0,0 +1,209 @@
+
+
+# 3GPP TS 25.432 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub interface: signalling transport (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                            |          |
+|------------------------------------------------------------|----------|
+| Foreword .....                                             | 4        |
+| 1 Scope.....                                               | 5        |
+| 2 References.....                                          | 5        |
+| 3 Definitions, symbols and abbreviations .....             | 6        |
+| 3.1 Definitions.....                                       | 6        |
+| 3.2 Symbols.....                                           | 6        |
+| 3.3 Abbreviations .....                                    | 6        |
+| 4 Data Link Layer .....                                    | 6        |
+| 4.1 ATM Transport Option .....                             | 6        |
+| 4.1.1 Protection switching at ATM Layer .....              | 6        |
+| 4.2 Data Link Layer for IP Transport Option.....           | 6        |
+| 5 NBAP signalling bearer .....                             | 7        |
+| 5.1 Introduction .....                                     | 7        |
+| 5.2 Signalling bearer in case of ATM Transport Option..... | 7        |
+| 5.3 Signalling bearer in case of IP Transport Option.....  | 7        |
+| <b>Annex A (informative): Change history .....</b>         | <b>9</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the signalling transport related to NBAP signalling to be used across the Iub Interface. The Iub interface is a logical interface for the interconnection of Node B and Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. The radio network control signalling between these nodes is based on the Node B application part (NBAP).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] ITU-T Recommendation Q.2100 (1994-07): "B-ISDN signalling ATM adaptation layer (SAAL) overview description".
+- [2] ITU-T Recommendation Q.2130 (1994-07): "B-ISDN signalling ATM adaptation layer – Service specific coordination function for support of signalling at the user network interface (SSCF–UNI)".
+- [3] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer – Service specific connection oriented protocol (SSCOP)".
+- [4] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Specification : Type 5 AAL".
+- [5] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [6] ITU-T Recommendation I.630 (1999-02): "ATM protection switching".
+- [7] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol".
+- [8] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
+- [9] IETF RFC 791 (1981-09): "Internet Protocol".
+- [10] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [11] IETF RFC 1661 (1994-07): "The Point-to-Point Protocol (PPP)".
+- [12] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [13] IETF RFC 2507 (1999-02): "IP header compression".
+- [14] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [15] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [16] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [17] IETF RFC 3153 (2001-08): "PPP Multiplexing".
+- [18] IETF RFC 2364 (1998-07): "PPP over AAL5".
+
+- [19] IETF RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture".
+- [20] IETF RFC 3309 (2002-09): "Stream Control Transmission Protocol (SCTP) Checksum Change".
+- [21] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**IP UTRAN node:** An UTRAN Node supporting the IP Transport Option
+
+## 3.2 Symbols
+
+(void)
+
+## 3.3 Abbreviations
+
+|       |                                               |
+|-------|-----------------------------------------------|
+| AAL   | ATM Adaptation Layer                          |
+| ATM   | Asynchronous Transfer Mode                    |
+| HDLC  | High-level Data Link Control                  |
+| IP    | Internet Protocol                             |
+| NBAP  | Node B Application Part                       |
+| PPP   | Point-to-Point Protocol                       |
+| RNC   | Radio Network Controller                      |
+| SAAL  | Signalling ATM Adaptation Layer               |
+| SCTP  | Stream Control Transmission Protocol          |
+| SSCF  | Service Specific Coordination Function        |
+| SSCOP | Service Specific Connection Oriented Protocol |
+| UNI   | User-Network Interface                        |
+
+# --- 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the radio network control plane according to ITU-T Rec. I.361 [5].
+
+### 4.1.1 Protection switching at ATM Layer
+
+If redundancy of pathways at ATM layer between RNC and Node B is supported, it shall be implemented using ATM Protection Switching according to ITU-T Rec. I.630 [6].
+
+## 4.2 Data Link Layer for IP Transport Option
+
+A RNC or Node B supporting IP Transport Option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [11], IETF RFC 1662 [12]).
+
+NOTE: This does not preclude the single implementation and use of any other L2/L1 protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [17], IETF RFC 2364 [18]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [19]), etc.) fulfilling the UTRAN requirements towards the upper layers.
+
+A RNC or Node B supporting IP transport option and having interfaces connected via slow bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [13]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [14], IETF RFC 2686 [15]). In this case, negotiation of header compression (IETF RFC 2507 [13]) over PPP shall be performed via (IETF RFC 2509 [16]).
+
+# 5 NBAP signalling bearer
+
+## 5.1 Introduction
+
+The Signalling Bearer for NBAP (TS 25.433 [21]) is a point-to-point protocol. There may be multiple point-to-point links between an RNC and a Node B. As shown in figure 1, the standard allows operators to choose one out of two protocol suites for transporting the NBAP messages.
+
+![Diagram showing two protocol stacks for NBAP signalling transport. The left stack is for the ATM transport option, consisting of NodeB Application Part (NBAP) on top of SSCF-UNI, SSCOP, AAL Type 5, ATM, and a dashed Physical Layer. The right stack is for the IP transport option, consisting of NodeB Application Part (NBAP) on top of SCTP, IP, a dashed Data Link Layer, and a dashed Physical Layer. Labels below each stack identify them as 'Protocol Suite for ATM Transport Option' and 'Protocol Suite for IP Transport Option'.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg)
+
+Diagram showing two protocol stacks for NBAP signalling transport. The left stack is for the ATM transport option, consisting of NodeB Application Part (NBAP) on top of SSCF-UNI, SSCOP, AAL Type 5, ATM, and a dashed Physical Layer. The right stack is for the IP transport option, consisting of NodeB Application Part (NBAP) on top of SCTP, IP, a dashed Data Link Layer, and a dashed Physical Layer. Labels below each stack identify them as 'Protocol Suite for ATM Transport Option' and 'Protocol Suite for IP Transport Option'.
+
+Figure 1: Iub NBAP Signalling Transport
+
+## 5.2 Signalling bearer in case of ATM Transport Option
+
+The signalling bearer in the Radio Network Control Plane is SAAL-UNI (ITU-T Rec. Q.2100 [1]) over ATM. The protocols to be used to support NBAP signalling are SSCF-UNI (ITU-T Rec. Q.2130 [2]) on top of SSCOP (ITU-T Rec. Q.2110 [3]) and AAL Type 5 (ITU-T Rec. I.363.5 [4]).
+
+## 5.3 Signalling bearer in case of IP Transport Option
+
+SCTP (IETF RFC 2960 [7]) over IP shall be supported as the transport for NBAP signalling bearer on Iub Interface. A RNC equipped with the SCTP stack option shall initiate the INIT procedure for establishing association. The data link layer is as specified in chapter 4.2.
+
+The checksum method specified in IETF RFC 3309 [20] shall be used instead of the method specified in IETF RFC 2960 ([7]).
+
+An IP UTRAN node shall support IPv6 (IETF RFC 2460 [8]). The support of IPv4 (IETF RFC 791 [9]) is optional.
+
+NOTE: This does not preclude single implementation and use of IPv4.
+
+IP dual stack is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
+
+Each signalling bearer between the RNC and Node B shall correspond to one single SCTP stream in UL and one single SCTP stream in DL direction, both streams belonging to the same SCTP association.
+
+IP Differentiated Services code point marking (IETF RFC 2474 [10]) shall be supported. The Diffserv code point may be determined from the application parameters.

marked/Rel-18/25_series/25446/raw.md

@@ -0,0 +1,685 @@
+
+
+# 3GPP TS 25.446 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; MBMS synchronisation protocol (SYNC) (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+# --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                               |    |
+|-----------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                | 5  |
+| 1 Scope.....                                                                                  | 6  |
+| 2 References.....                                                                             | 6  |
+| 3 Definitions and abbreviations .....                                                         | 6  |
+| 3.1 Definitions.....                                                                          | 6  |
+| 3.2 Abbreviations .....                                                                       | 6  |
+| 3.4 Specification notations .....                                                             | 7  |
+| 4 General.....                                                                                | 7  |
+| 4.1 General aspects for the SYNC protocol for UTRAN.....                                      | 7  |
+| 4.1.1 General aspects.....                                                                    | 7  |
+| 4.2 General aspects for the SYNC protocol for E-UTRAN.....                                    | 8  |
+| 4.2.1 General aspects.....                                                                    | 8  |
+| 5 SYNC protocol version 1 .....                                                               | 9  |
+| 5.1 General .....                                                                             | 9  |
+| 5.1.1 Applicability of SYNC protocol version 1 .....                                          | 9  |
+| 5.1.1 Operation of the SYNC protocol.....                                                     | 9  |
+| 5.1.2 Interfaces of the SYNC protocol layer .....                                             | 9  |
+| 5.2 SYNC protocol layer services.....                                                         | 9  |
+| 5.3 Services Expected from the UP Data Transport layer.....                                   | 9  |
+| 5.4 Elementary procedures.....                                                                | 10 |
+| 5.4.1 Transfer of User Data for MBMS procedure.....                                           | 10 |
+| 5.4.1.1 Successful operation .....                                                            | 10 |
+| 5.4.1.2 Unsuccessful operation .....                                                          | 10 |
+| 5.4.2 Transfer of Synchronisation Information for MBMS procedure (without user data) .....    | 11 |
+| 5.4.2.1 Successful operation .....                                                            | 11 |
+| 5.4.2.2 Unsuccessful operation.....                                                           | 11 |
+| 5.5 Elements for the SYNC protocol .....                                                      | 12 |
+| 5.5.1 General .....                                                                           | 12 |
+| 5.5.2 Frame format for the SYNC protocol.....                                                 | 12 |
+| 5.5.2.1 Transfer of Synchronisation Information without payload (SYNC PDU Type 0).....        | 12 |
+| 5.5.2.2 Transfer of User Data for MBMS with uncompressed header (SYNC PDU Type 1).....        | 13 |
+| 5.5.2.3 Transfer of User Data for MBMS with compressed header (SYNC PDU Type 2).....          | 14 |
+| 5.5.2.4 Transfer of Synchronisation Information with Length of Packets (SYNC PDU Type 3)..... | 15 |
+| 5.5.3 Coding of information elements in frames.....                                           | 17 |
+| 5.5.3.1 PDU Type .....                                                                        | 17 |
+| 5.5.3.2 Timestamp .....                                                                       | 18 |
+| 5.5.3.3 Packet Number.....                                                                    | 18 |
+| 5.5.3.4 Elapsed Octet Counter .....                                                           | 18 |
+| 5.5.3.5 Total Number Of Packet .....                                                          | 18 |
+| 5.5.3.6 Total Number Of Octet.....                                                            | 18 |
+| 5.5.3.7 PDCP Information .....                                                                | 19 |
+| 5.5.3.8 IPv6 Indicator .....                                                                  | 19 |
+| 5.5.3.9 Uncompressed Payload IP header.....                                                   | 19 |
+| 5.5.3.10 Header CRC.....                                                                      | 19 |
+| 5.5.3.11 Payload CRC.....                                                                     | 19 |
+| 5.5.3.12 Padding .....                                                                        | 19 |
+| 5.5.3.13 Spare .....                                                                          | 19 |
+| 5.5.3.14 Spare extension.....                                                                 | 20 |
+| 5.5.3.15 Payload fields.....                                                                  | 20 |
+| 5.5.3.16 Length of the N <sup>th</sup> Packet.....                                            | 20 |
+| 5.5.4 Timers.....                                                                             | 20 |
+| 5.6 Handling of unknown, unforeseen and erroneous protocol data.....                          | 20 |
+| 5.6.1 General .....                                                                           | 20 |
+| 5.6.2 CRC Calculation.....                                                                    | 20 |
+
+5.6.3 Relation between input and output of the Cyclic Redundancy Check ................................................................. 21
+
+**Annex A (informative): Change history.................................................................................................................. 22**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the MBMS Synchronisation Protocol. For the release of this specification it is used on Iu towards UTRAN and M1 towards E-UTRAN.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.410: "UTRAN Iu interface: General Aspects and Principles".
+- [3] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) specification".
+- [4] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
+- [5] 3GPP TS 36.440: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN".
+- [6] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**RAN Access interface:** interface between the Core Network and the Radio Access Network.
+
+**RAN Access node:** termination point of the RAN Access interface at the Radio Access Network.
+
+**MBMS RAB:** denotes the Radio Access data bearer together with the RAN Access Interface data bearer for MBMS service user data transmission.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|        |                                                 |
+|--------|-------------------------------------------------|
+| MRNC   | MBMS Master RNC (as specified in TS 25.346 [4]) |
+| SC-PTM | Single Cell – Point To Multipoint               |
+
+SYNC MBMS synchronisation protocol
+
+## 3.4 Specification notations
+
+For the purposes of the present document, the following notations apply:
+
+|                |                                                                                                                                                                                                                                                                               |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure      | When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Iu Rate Control procedure.                                                               |
+| Frame          | When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. TIME ALIGNMENT control frame.                                               |
+| IE             | When referring to an information element (IE) in the specification the <i>Information Element Name</i> is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. <i>Frame Number</i> IE. |
+| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 5.6.3 enclosed by quotation marks, e.g. "0" or "255".                                                                                  |
+
+# --- 4 General
+
+## 4.1 General aspects for the SYNC protocol for UTRAN
+
+### 4.1.1 General aspects
+
+The MBMS Synchronisation protocol (SYNC) is located in the User plane of the Radio Network layer over the Iu interface: the Iu UP protocol layer.
+
+The SYNC protocol for UTRAN is used to convey user data associated to MBMS Radio Access Bearers.
+
+One SYNC protocol instance is associated to one MBMS RAB and one MBMS RAB only. If several MBMS RABs are established towards one given UE, then these MBMS RABs make use of several SYNC protocol instances.
+
+SYNC protocol instances exist at Iu access point as defined (TS 25.410 [2]) i.e. at CN and UTRAN.
+
+Whenever an MBMS RAB requires transfer of user data in the Iu UP, an Iu UP protocol instance exists at each Iu interface access points. These Iu UP protocol instances are established and released together with the associated MBMS RAB.
+
+The following figure illustrates the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum.
+
+![Figure 4.1.1-1: SYNC protocol layer occurrence in UTRAN overall architecture (User Plane View).](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+This diagram illustrates the protocol stack for the User Plane in UTRAN. It shows three main entities: UE, UTRAN, and CN, connected by interfaces Radio (Uu) and Iu. The stack is divided into Non-Access Stratum (NAS) and Access Stratum. In the NAS, there are NAS Data Streams. The Access Stratum contains Radio protocols, a Transport Layer, and a TNL Protocol. The SYNC protocol is shown as a layer within the Radio protocols in the UTRAN and CN, positioned above the TNL Protocol. Arrows indicate the flow of data between the NAS Data Streams and the Radio protocols, and between the Radio protocols and the TNL Protocol.
+
+Figure 4.1.1-1: SYNC protocol layer occurrence in UTRAN overall architecture (User Plane View).
+
+Figure 4.1.1-1: SYNC protocol layer occurrence in UTRAN overall architecture (User Plane View)
+
+## 4.2 General aspects for the SYNC protocol for E-UTRAN
+
+### 4.2.1 General aspects
+
+The MBMS Synchronisation protocol (SYNC) is located in the User plane of the Radio Network layer over the M1 interface: the M1 UP protocol layer.
+
+The SYNC protocol for E-UTRAN is used to convey user data associated to MBMS Radio Access Bearers.
+
+One SYNC protocol instance is associated to one MBMS E-RAB and one MBMS E-RAB only.
+
+SYNC protocol instances exist at M1 access point as defined (TS 36.440 [5]) i.e. at EPC and E-UTRAN.
+
+Whenever an MBMS E-RAB requires transfer of user data in the M1 UP, an M1 UP protocol instance exists at each M1 interface access points. These M1 UP protocol instances are established and released together with the associated MBMS E-RAB.
+
+The following figure illustrates the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum.
+
+![Figure 4.2.1-1: SYNC protocol layer occurrence in E-UTRAN overall architecture (User Plane View).](740442c999390734911677f01af0316d_img.jpg)
+
+This diagram illustrates the protocol stack for the User Plane in E-UTRAN. It shows three main entities: UE, E-UTRAN, and CN, connected by interfaces Radio (Uu) and M1. The stack is divided into Non-Access Stratum (NAS) and Access Stratum. In the NAS, there are NAS Data Streams. The Access Stratum contains Radio protocols, a Transport Layer, and a TNL Protocol. The SYNC protocol is shown as a layer within the Radio protocols in the E-UTRAN and CN, positioned above the TNL Protocol. Arrows indicate the flow of data between the NAS Data Streams and the Radio protocols, and between the Radio protocols and the TNL Protocol.
+
+Figure 4.2.1-1: SYNC protocol layer occurrence in E-UTRAN overall architecture (User Plane View).
+
+Figure 4.2.1-1: SYNC protocol layer occurrence in E-UTRAN overall architecture (User Plane View)
+
+# 5 SYNC protocol version 1
+
+## 5.1 General
+
+### 5.1.1 Applicability of SYNC protocol version 1
+
+This version of the specification specifies the SYNC protocol for UTRAN and E-UTRAN. It is on top of TNL in Iu (UTRAN) and M1 (E-UTRAN) user plane, i.e. Iu userplane TNL transports SYNC protocol PDUs over the Iu interface, M1 userplane TNL transports SYNC protocol PDUs over the M1 interface.
+
+As a specification convention, within this specification, the interface between the Core Network and the Radio Access Network is denoted as the “RAN Access Interface”, the termination point at the Radio Access Network is denoted as “RAN Access Node”, the termination point at the Core Network is denoted as “Core Network” (CN). Further, “MBMS RAB” denotes the Radio Access data bearer together with the RAN Access Interface data bearer for MBMS service user data transmission.
+
+For the application of the SYNC protocol to UTRAN, the RAN Access Interface is the Iu interface, the RAN Access Node is the RNC.
+
+For the application of the SYNC protocol to E-UTRAN, the RAN Access Interface is the M1 interface, the RAN Access Node is the eNB.
+
+### 5.1.1 Operation of the SYNC protocol
+
+The SYNC protocol layer is present for data streams that originate in the CN and carry additional information within a specific userplane-frame.
+
+The two strata communicate through a Service Access Point for Non Access Stratum (NAS) Data Streams transfer.
+
+### 5.1.2 Interfaces of the SYNC protocol layer
+
+As part of the Access Stratum responsibility, the SYNC protocol layer provides the services and functions that are necessary to handle non access stratum data streams for MBMS. The SYNC protocol layer is providing these services to the UP upper layers through a Dedicated Service Access Point used for Information Transfer.
+
+The SYNC protocol layer is using services of the Transport layers in order to transfer user plane PDUs over the RAN Access interface.
+
+## 5.2 SYNC protocol layer services
+
+The following functions are needed to support the SYNC protocol:
+
+- Transfer of user data along with synchronisation information;
+- Transfer of synchronisation information without user data.
+
+## 5.3 Services Expected from the UP Data Transport layer
+
+The SYNC protocol layer expects the following services from the Transport Network Layer:
+
+- Transfer of user data.
+- No flow control.
+
+## 5.4 Elementary procedures
+
+### 5.4.1 Transfer of User Data for MBMS procedure
+
+#### 5.4.1.1 Successful operation
+
+The purpose of the Transfer of User Data procedure for MBMS is to transfer RAN Access Interface UP frames from the RAN Access interface UP protocol layers at CN to the RAN Access interface UP protocol layer at the RAN Access Node. One RAN Access interface UP instance is associated to a single MBMS RAB only.
+
+The Transfer of User Data procedure is invoked whenever user data for that particular RAB needs to be sent across the Radio Access interface.
+
+The NAS Data Streams specific functions make the padding of the payload (if needed) so that the Radio Access interface UP frame payload will be an integer number of octets. Then the NAS Data Streams specific functions perform, if needed, CRC calculation of the Iu/M1 frame payload and passes the Radio Access interface UP frame payload down to the Frame Handler function.
+
+The Frame Handler function within the CN retrieves the packet counter and octet counter value from its internal memory, formats the frame header and frame payload into the appropriate PDU Type and sends the Radio Access interface UP frame PDU to the lower layers for transfer across the Radio Access interface. If the user data is provided with compressed IP header, the Radio Access interface UP frame contains PDCP information and the uncompressed IP header.
+
+The Frame Handler function within the CN is also responsible for appropriate setting of the Time Stamp value in order to allow all RAN Access nodes to submit the MBMS user data in a synchronised manner.
+
+Upon reception of a user data frame, the RAN Access interface UP protocol layer within the RAN Access node checks the consistency of the RAN Access interface UP frame as follows:
+
+- The Frame Handler function checks the consistency of the frame header and the consistency of the packet counter value.
+- Then the RAN Access node utilises the time stamp information to schedule the user data on the radio interface on the next TTI for UTRAN or MCH scheduling period for E-UTRAN as defined in TS 36.300 [6].
+
+![Diagram illustrating the successful transfer of user data from the CN to the RAN Access node.](4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg)
+
+The diagram shows two vertical lines representing the RAN Access node and the CN. A horizontal arrow labeled 'TRANSFER OF USER DATA' points from the CN line to the RAN Access node line. Both lines have a small horizontal bar at the bottom.
+
+Diagram illustrating the successful transfer of user data from the CN to the RAN Access node.
+
+Figure 5.4.1.1-1. Successful Transfers of User Data.
+
+#### 5.4.1.2 Unsuccessful operation
+
+If multiple consecutive RAN Access interface UP frames carrying the user data are incorrectly formatted or cannot be correctly treated by the receiving RAN Access interface UP protocol layer, or if multiple consecutive frames loss is detected due to gaps in the sequence of the received frame numbers, the RAN Access node shall, if packet length information in Type 3 is not provided,
+
+- in case the RAN Access Interface UP is the Iu UP.
+  - cease to provide user data to the radio interface protocol entities and wait until the next synchronisation sequence if soft combining and MBSFN are used, or until the next scheduling transmission interval if the RNC acts as an MRNC and TDM multiplexing is used, as described in TS 25.346 [4].
+
+- in case the RAN Access Interface UP is the M1 UP and MBSFN is used,
+  - cease to provide user data to the radio interface protocol entities and wait until the next dynamic scheduling interval, as described in TS 36.300 [6].
+- in case the RAN Access Interface UP is the M1 UP and SC-PTM is used,
+  - provide other correctly received user data to the radio interface protocol entities, as described in TS 36.300 [6].
+
+If packet length information in Type 3 is provided, the RAN Access nodes could cease to provide user data to the radio interface protocol entities for those lost subframes.
+
+### 5.4.2 Transfer of Synchronisation Information for MBMS procedure (without user data)
+
+#### 5.4.2.1 Successful operation
+
+The purpose of the Transfer of Synchronisation Information for MBMS procedure is to transfer synchronisation information from the CN to the RAN Access node at the end of each synchronization sequence (see TS 25.346 [4], TS 36.300 [6]) to improve the RAN Access node resynchronization in case of packet loss.
+
+The Frame Handler function within the CN retrieves the synchronisation time stamp from its internal clock and the total packet counter and total octet counter from its internal memory, formats the frame header and frame payload into the appropriate PDU Type and sends the RAN Access interface UP frame PDU to the lower layers for transfer across the RAN Access interface.
+
+If there is no data frame in a synchronization sequence, synchronization information shall still be transmitted.
+
+Furthermore, the SYNC PDU towards RAN Access node could contain length of each packet if supported.
+
+Upon reception of a user data frame, the RAN Access interface UP protocol layer checks the consistency of the RAN Access interface UP frame as follows:
+
+- The Frame Handler function checks the consistency of the frame header and the consistency of the synchronisation time stamp, total packet counter, total octet counter and packets length counter value if contained.
+
+![Diagram illustrating the successful transfer of synchronisation information from the CN to the RAN Access node.](f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg)
+
+The diagram shows two vertical lifelines. The left lifeline is labeled 'RAN Access node' and the right lifeline is labeled 'CN'. A horizontal arrow points from the CN lifeline to the RAN Access node lifeline, with the text 'TRANSFER OF SYNC INFO' written above it. Both lifelines end in a thick horizontal bar at the bottom.
+
+Diagram illustrating the successful transfer of synchronisation information from the CN to the RAN Access node.
+
+**Figure 5.4.2.1-1. Successful Transfers of Synchronisation Information.**
+
+#### 5.4.2.2 Unsuccessful operation
+
+If the RAN Access interface UP frame without user data is incorrectly formatted or cannot be correctly treated by the receiving RAN Access interface UP protocol layer, the RAN Access interface UP protocol layer shall either discard the frame or pass it to the upper layers with a frame classification indicating a corrupted frame.
+
+## 5.5 Elements for the SYNC protocol
+
+### 5.5.1 General
+
+In the present document the structure of frames will be specified by using figures similar to Figure 5.5.1-1.
+
+![](08441fa90c5fd11994626f662ac13f19_img.jpg)
+
+| Bits             |   |   |   |         |   |         |   | Number of Octets |         |              |
+|------------------|---|---|---|---------|---|---------|---|------------------|---------|--------------|
+| 7                | 6 | 5 | 4 | 3       | 2 | 1       | 0 |                  |         |              |
+| Field 1          |   |   |   | Field 2 |   |         |   | 1                | Octet 1 | Header part  |
+| Field 3          |   |   |   |         |   | Field 4 |   | 2                | Octet 2 |              |
+| Field 4 continue |   |   |   | Spare   |   |         |   |                  | Octet 3 |              |
+| Field 6          |   |   |   |         |   |         |   | 2                | Octet 4 | Payload part |
+| Field 6 continue |   |   |   | Padding |   |         |   |                  | Octet 5 |              |
+| Spare extension  |   |   |   |         |   |         |   | 0-m              |         |              |
+
+Figure 5.5.1-1. Example frame format.
+
+Unless otherwise indicated, fields which consist of multiple bits within an octet will have the most significant bit located at the higher bit position (indicated above frame in Figure 5.5.1-1). In addition, if a field spans several octets, most significant bits will be located in lower numbered octets (right of frame in Figure 5.5.1-1).
+
+On the Iu/M1 interface, the frame will be transmitted starting from the lowest numbered octet. Within each octet, the bits are sent according decreasing bit position (bit position 7 first).
+
+Spare bits should be set to "0" by the sender and should not be checked by the receiver.
+
+The header part of the frame is always an integer number of octets. The payload part is octet aligned (by adding 'Padding' when needed).
+
+The receiver should be able to remove an additional spare extension field that may be present at the end of a frame. See description of Spare extension field.
+
+### 5.5.2 Frame format for the SYNC protocol
+
+#### 5.5.2.1 Transfer of Synchronisation Information without payload (SYNC PDU Type 0)
+
+This Frame Format is defined to transfer synchronisation information over the RAN Access Interface UP without user data payload.
+
+The following shows the SYNC frame structure for PDU TYPE 0 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP).
+
+| Bits                   |   |   |   |       |   |         |   | Number of Octets |                      |  |  |  |  |
+|------------------------|---|---|---|-------|---|---------|---|------------------|----------------------|--|--|--|--|
+| 7                      | 6 | 5 | 4 | 3     | 2 | 1       | 0 |                  |                      |  |  |  |  |
+| PDU Type (=0)          |   |   |   | spare |   |         |   | 1                | Frame Control Part   |  |  |  |  |
+| Time Stamp             |   |   |   |       |   |         |   | 2                |                      |  |  |  |  |
+| Packet Number          |   |   |   |       |   |         |   | 2                |                      |  |  |  |  |
+| Elapsed Octet Counter  |   |   |   |       |   |         |   | 4                |                      |  |  |  |  |
+| Total Number Of Packet |   |   |   |       |   |         |   | 3                |                      |  |  |  |  |
+| Total Number Of Octet  |   |   |   |       |   |         |   | 5                |                      |  |  |  |  |
+| Header CRC             |   |   |   |       |   | Padding |   | 1                | Frame Check Sum Part |  |  |  |  |
+
+**Figure 5.5.2.1-1. SYNC PDU Type 0 Format.**
+
+The SYNC PDU TYPE 0 data frame is made of two parts:
+
+- 1) SYNC Frame Control part (fixed size);
+- 2) SYNC Frame Check Sum part (fixed size);
+
+#### 5.5.2.2 Transfer of User Data for MBMS with uncompressed header (SYNC PDU Type 1)
+
+This Frame Format is defined to transfer user data over the RAN Access Interface UP for user data with uncompressed header.
+
+The following shows the SYNC frame structure for PDU TYPE 1 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP).
+
+| Bits                  |   |   |   |         |   |             |   | Number of Octets |                      |  |  |  |  |
+|-----------------------|---|---|---|---------|---|-------------|---|------------------|----------------------|--|--|--|--|
+| 7                     | 6 | 5 | 4 | 3       | 2 | 1           | 0 |                  |                      |  |  |  |  |
+| PDU Type (=1)         |   |   |   | spare   |   |             |   | 1                | Frame Control Part   |  |  |  |  |
+| Time Stamp            |   |   |   |         |   |             |   | 2                |                      |  |  |  |  |
+| Packet Number         |   |   |   |         |   |             |   | 2                |                      |  |  |  |  |
+| Elapsed Octet Counter |   |   |   |         |   |             |   | 4                |                      |  |  |  |  |
+| Header CRC            |   |   |   |         |   | Payload CRC |   | 2                | Frame Check Sum Part |  |  |  |  |
+| Payload CRC           |   |   |   |         |   |             |   |                  |                      |  |  |  |  |
+| Payload Fields        |   |   |   |         |   |             |   | 1-n              | Frame Payload part   |  |  |  |  |
+| Payload Fields        |   |   |   | Padding |   |             |   |                  |                      |  |  |  |  |
+| Spare extension       |   |   |   |         |   |             |   | 0-4              |                      |  |  |  |  |
+
+**Figure 5.5.2.2-1. SYNC PDU Type 1 Format.**
+
+The SYNC PDU TYPE 1 data frame is made of three parts:
+
+- 1) SYNC Frame Control part (fixed size);
+- 2) SYNC Frame Check Sum part (fixed size);
+- 3) SYNC Frame Payload part (SDU sizes rounded up to octets [Note: this does not consider the usage of spare extension field]).
+
+#### 5.5.2.3 Transfer of User Data for MBMS with compressed header (SYNC PDU Type 2)
+
+This Frame Format is defined to transfer user data over the RAN Access Interface UP for user data with compressed header.
+
+The following shows the SYNC frame structure for PDU TYPE 2 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP).
+
+For this version of the specification, SYNC PDU TYPE 2 is only applicable if the RAN Access Interface UP is the Iu UP, it shall not be used over M1.
+
+| Bits                           |   |   |         |             |   |            |   | Number of Octets |                      |  |  |  |  |  |  |
+|--------------------------------|---|---|---------|-------------|---|------------|---|------------------|----------------------|--|--|--|--|--|--|
+| 7                              | 6 | 5 | 4       | 3           | 2 | 1          | 0 |                  |                      |  |  |  |  |  |  |
+| PDU Type (=2)                  |   |   | spare   |             |   | IPv6 indic |   | 1                | Frame Control Part   |  |  |  |  |  |  |
+| Time Stamp                     |   |   |         |             |   |            |   | 2                |                      |  |  |  |  |  |  |
+| Packet Number                  |   |   |         |             |   |            |   | 2                |                      |  |  |  |  |  |  |
+| Elapsed Octet Counter          |   |   |         |             |   |            |   | 4                |                      |  |  |  |  |  |  |
+| PDCP Information               |   |   |         |             |   |            |   | 1                |                      |  |  |  |  |  |  |
+| Uncompressed Payload IP header |   |   |         |             |   |            |   | 20(40)           |                      |  |  |  |  |  |  |
+| Header CRC                     |   |   |         | Payload CRC |   |            |   | 2                | Frame Check Sum Part |  |  |  |  |  |  |
+| Payload CRC                    |   |   |         |             |   |            |   |                  |                      |  |  |  |  |  |  |
+| Payload Fields                 |   |   |         |             |   |            |   | 1-n              | Frame Payload part   |  |  |  |  |  |  |
+| Payload Fields                 |   |   | Padding |             |   |            |   |                  |                      |  |  |  |  |  |  |
+| Spare extension                |   |   |         |             |   |            |   | 0-4              |                      |  |  |  |  |  |  |
+
+**Figure 5.5.2.3-1. SYNC PDU Type 2 Format.**
+
+The SYNC PDU TYPE 2 data frame is made of three parts:
+
+- 1) SYNC Frame Control part (fixed size);
+- 2) SYNC Frame Check Sum part (fixed size);
+- 3) SYNC Frame Payload part (SDU sizes rounded up to octets [Note: this does not consider the usage of spare extension field]).
+
+#### 5.5.2.4 Transfer of Synchronisation Information with Length of Packets (SYNC PDU Type 3)
+
+This Frame Format is defined to transfer synchronisation information over the RAN Access Interface UP with Length of Packets.
+
+The following shows the SYNC frame structure for PDU TYPE 3 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP).
+
+| Bits                                        |   |   |   |                                  |   |             |   | Number of Octets               |                      |  |  |  |  |  |  |  |  |  |  |
+|---------------------------------------------|---|---|---|----------------------------------|---|-------------|---|--------------------------------|----------------------|--|--|--|--|--|--|--|--|--|--|
+| 7                                           | 6 | 5 | 4 | 3                                | 2 | 1           | 0 |                                |                      |  |  |  |  |  |  |  |  |  |  |
+| PDU Type (=3)                               |   |   |   | spare                            |   |             |   | 1                              | Frame Control Part   |  |  |  |  |  |  |  |  |  |  |
+| Time Stamp                                  |   |   |   |                                  |   |             |   | 2                              |                      |  |  |  |  |  |  |  |  |  |  |
+| Packet Number                               |   |   |   |                                  |   |             |   | 2                              |                      |  |  |  |  |  |  |  |  |  |  |
+| Elapsed Octet Counter                       |   |   |   |                                  |   |             |   | 4                              |                      |  |  |  |  |  |  |  |  |  |  |
+| Total Number Of Packet                      |   |   |   |                                  |   |             |   | 3                              |                      |  |  |  |  |  |  |  |  |  |  |
+| Total Number Of Octet                       |   |   |   |                                  |   |             |   | 5                              |                      |  |  |  |  |  |  |  |  |  |  |
+| Header CRC                                  |   |   |   |                                  |   | Payload CRC |   | 2                              | Frame Check Sum Part |  |  |  |  |  |  |  |  |  |  |
+| Payload CRC                                 |   |   |   |                                  |   |             |   |                                |                      |  |  |  |  |  |  |  |  |  |  |
+| Length of the 1 <sup>st</sup> Packet        |   |   |   |                                  |   |             |   | 1.5*<br>(Packet Number -1) + 2 | Frame Payload part   |  |  |  |  |  |  |  |  |  |  |
+| Length of the 1 <sup>st</sup> Packet (cont) |   |   |   | Length of 2 <sup>nd</sup> packet |   |             |   |                                |                      |  |  |  |  |  |  |  |  |  |  |
+| ...                                         |   |   |   |                                  |   |             |   |                                |                      |  |  |  |  |  |  |  |  |  |  |
+| Length of the N <sup>th</sup> Packet        |   |   |   |                                  |   |             |   |                                |                      |  |  |  |  |  |  |  |  |  |  |
+| Length of the N <sup>th</sup> Packet (cont) |   |   |   | Padding                          |   |             |   |                                |                      |  |  |  |  |  |  |  |  |  |  |
+| Spare extension                             |   |   |   |                                  |   |             |   | 0-4                            |                      |  |  |  |  |  |  |  |  |  |  |
+
+Figure 5.5.2.4-1. SYNC PDU Type 3 Format (Odd number of packets, i.e. N=1, 3, 5, ...)
+
+| Bits                                        |   |   |   |                                      |   |             |   | Number of Octets         |                      |
+|---------------------------------------------|---|---|---|--------------------------------------|---|-------------|---|--------------------------|----------------------|
+| 7                                           | 6 | 5 | 4 | 3                                    | 2 | 1           | 0 |                          |                      |
+| PDU Type (=3)                               |   |   |   | spare                                |   |             |   | 1                        | Frame Control Part   |
+| Time Stamp                                  |   |   |   |                                      |   |             |   | 2                        |                      |
+| Packet Number                               |   |   |   |                                      |   |             |   | 2                        |                      |
+| Elapsed Octet Counter                       |   |   |   |                                      |   |             |   | 4                        |                      |
+| Total Number Of Packet                      |   |   |   |                                      |   |             |   | 3                        |                      |
+| Total Number Of Octet                       |   |   |   |                                      |   |             |   | 5                        |                      |
+| Header CRC                                  |   |   |   |                                      |   | Payload CRC |   | 2                        | Frame Check Sum Part |
+| Payload CRC                                 |   |   |   |                                      |   |             |   |                          |                      |
+| Length of the 1 <sup>st</sup> Packet        |   |   |   |                                      |   |             |   | 1.5*<br>Packet<br>Number | Frame Payload part   |
+| Length of the 1 <sup>st</sup> Packet (cont) |   |   |   | Length of the 2 <sup>nd</sup> Packet |   |             |   |                          |                      |
+| ...                                         |   |   |   |                                      |   |             |   |                          |                      |
+| Length of the N <sup>th</sup> Packet        |   |   |   |                                      |   |             |   |                          |                      |
+| Spare extension                             |   |   |   |                                      |   |             |   | 0-4                      |                      |
+
+**Figure 5.5.2.4-2. SYNC PDU Type 3 Format (Even number of packets, i.e. N=2, 4, 6, ...)**
+
+The SYNC PDU TYPE 3 data frame is made of three parts:
+
+- 1) SYNC Frame Control part (fixed size);
+- 2) SYNC Frame Check Sum part (fixed size);
+- 3) SYNC Frame Payload part (variable size); the size of the SYNC Frame Payload part is the length of the *Length of the N<sup>th</sup> Packet IE* in octets =  $1.5 * (\text{Packet Number} - 1) + 2 + \text{the length of Spare Extension}$ , if the number of packets is odd in the synchronization sequence; the length of the *Length of the N<sup>th</sup> Packet IE* in octets =  $1.5 * \text{Packet Number} + \text{the length of Spare Extension}$ , if the number of packets is even in the synchronization sequence.
+
+### 5.5.3 Coding of information elements in frames
+
+#### 5.5.3.1 PDU Type
+
+**Description:** The PDU type indicates the structure of the SYNC frame. The field takes the value of the PDU Type it identifies: i.e. "0" for PDU Type 0. The PDU type is in bit 4 to bit 7 in the first octet of the frame.
+
+**Value range:** {0=synchronisation frame without payload, 1=user data with synchronisation frame for uncompressed headers, 2=user data with synchronisation frame for compressed headers, 3=synchronisation frame with Length of Packets, 4-15=reserved for future PDU type extensions}
+
+**Field length:** 4 bits
+
+#### 5.5.3.2 Timestamp
+
+**Description:** Relative time value for the starting time of a synchronization sequence within the synchronisation period.
+
+**Value range:** {0...60000-1} Unit: multiples of 10ms.
+
+Note: The value range allows for a synchronisation period of 600s.
+
+**Field length:** 2 octets
+
+#### 5.5.3.3 Packet Number
+
+**Description:** This parameter indicates the number of elapsed SYNC PDUs cumulatively within the synchronization sequence. It helps the RAN Access node to notice the loss of SYNC PDUs. Additionally it is used to reorder the PDUs in the RAN Access node. The Packet number is reset at the end of every synchronisation sequence, and is set to 0 for the 1<sup>st</sup> SYNC PDU of every synchronisation sequence. SYNC PDUs of Type 0 and Type 3 are not counted by this parameter.
+
+**Value range:** {0..2<sup>16</sup>-1}.
+
+**Field length:** 2 octets.
+
+#### 5.5.3.4 Elapsed Octet Counter
+
+**Description:** This parameter indicates the number of elapsed cumulative octets cumulatively within one synchronisation sequence. It helps the RAN Access node to know how many packets were not received in case of packet loss. This counter is reset at the end of every synchronisation sequence, and is set to 0 for the 1<sup>st</sup> SYNC PDU of every synchronisation sequence. This parameter does not count the header part of the SYNC PDU. Octets of SYNC PDUs of Type 0 and Type 3 are not counted by this parameter.
+
+**Value range:** {0..2<sup>32</sup>-1}.
+
+**Field length:** 4 octets.
+
+#### 5.5.3.5 Total Number Of Packet
+
+**Description:** This parameter indicates cumulatively the number of the packets for the MBMS service within one synchronization period. SYNC PDUs of Type 0 and Type 3 are not counted by this parameter.
+
+**Value range:** {0..2<sup>24</sup>-1}.
+
+Note: In case of soft combining and MBSFN(except in case the RNC acts as an MRNC and TDM multiplexing is used), the parameter shall be ignored in RNC.
+
+**Field length:** 3 octets.
+
+#### 5.5.3.6 Total Number Of Octet
+
+**Description:** This parameter indicates cumulatively the number of the octets for the MBMS service within one synchronization period. This parameter does not count the header part of the SYNC PDU. Octets of SYNC PDUs of Type 0 and Type 3 are not counted by this parameter.
+
+**Value range:** {0..2<sup>40</sup>-1}.
+
+Note: In case of soft combining and MBSFN(except in case the RNC acts as an MRNC and TDM multiplexing is used), the parameter shall be ignored in RNC.
+
+**Field length:** 5 octets.
+
+#### 5.5.3.7 PDCP Information
+
+**Description:** This parameter contains PDCP Information as specified in TS 25.323 [3].
+
+**Value range:** as specified in TS 25.323 [3].
+
+**Field length:** 1 octet.
+
+#### 5.5.3.8 IPv6 Indicator
+
+**Description:** This parameter indicates whether the Uncompressed Payload IP header is of IPv6 type.
+
+**Value range:** {0=IPv4, 1=IPv6}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.9 Uncompressed Payload IP header
+
+**Description:** This parameter provides the uncompressed IP header of the payload.
+
+**Value range:** {any value}
+
+**Field length:** 20 octets if IPv6 Indicator=0, 40 octets if IPv6 Indicator=1.
+
+#### 5.5.3.10 Header CRC
+
+**Description:** This field contains the CRC of all fields in Frame Control Part. The CRC is a 6-bit checksum based on the generator polynomial  $G(D) = D^6+D^5+D^3+D^2+D^1+1$ , see subclause 5.6.2. With this CRC all error bursts shorter than 7 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 24 bits, (max 3 octets).
+
+**Field length:** 6 bits.
+
+#### 5.5.3.11 Payload CRC
+
+**Description:** This field contains the CRC of all the fields (including Padding and possible Spare extension) of the Frame Payload Part. The CRC is a 10 bit checksum based on the generator polynomial  $G(D) = D^{10}+ D^9+D^5+D^4+D^1+1$ , see subclause 5.6.2. With this CRC all error bursts shorter than 11 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 500 bits (max 62 octets).
+
+**Field length:** 10 bits.
+
+#### 5.5.3.12 Padding
+
+**Description:** This field is an additional field used to make the frame header or payload part an integer number of octets when needed. Padding is set to "0" by the sender and is not interpreted by the receiver.
+
+**Value range:** {0-127}.
+
+**Field length:** 0-7 bits.
+
+#### 5.5.3.13 Spare
+
+**Description:** The spare field is set to "0" by the sender and should not be interpreted by the receiver. This field is reserved for later versions.
+
+**Value range:** (0- $2^n-1$ ).
+
+**Field Length:** n bits.
+
+#### 5.5.3.14 Spare extension
+
+**Description:** The spare extension field is reserved for extension in later versions. It shall not be sent. The receiver should be capable of receiving a spare extension. The spare extension should not be interpreted by the receiver since in later versions of the present document additional new fields might be added in place of the spare extension. The spare extension can be an integer number of octets carrying new fields or additional information; the maximum length of the spare extension field (m) depends on the PDU type.
+
+**Value range:**  $0-2^{m*8}-1$ .
+
+**Field Length:** 0–m octets. For PDU Types in the set {1,2,3}, m=4.
+
+#### 5.5.3.15 Payload fields
+
+**Description:** This field contains the payload of the MBMS user data.
+
+**Value range:** {any value}.
+
+**Field length:** n bits
+
+#### 5.5.3.16 Length of the N<sup>th</sup> Packet
+
+**Description:** This parameter indicates the length of the SYNC PDU within the synchronization sequence in octets. It helps the RAN Access node to recover from de-synchronization in case of the loss of consecutive SYNC PDUs.
+
+**Value range:** {0..2<sup>12</sup>-1}
+
+**Field length:** 12 bits
+
+### 5.5.4 Timers
+
+not applicable
+
+## 5.6 Handling of unknown, unforeseen and erroneous protocol data
+
+### 5.6.1 General
+
+void
+
+### 5.6.2 CRC Calculation
+
+The parity bits are generated by one of the following cyclic generator polynomials:
+
+$$g_{CRC6}(D) = D^6 + D^5 + D^3 + D^2 + D^1 + 1;$$
+
+$$g_{CRC10}(D) = D^{10} + D^9 + D^5 + D^4 + D^1 + 1.$$
+
+Denote the bits to be protected of a frame by  $a_1, a_2, a_3, \dots, a_{A_i}$  ( $a_1$  being the bit with the highest bit position in the first octet), and the parity bits by  $p_1, p_2, p_3, \dots, p_{L_i}$ .  $A_i$  is the length of the protected data and  $L_i$  is 6 or 10 depending on the CRC length.
+
+The encoding is performed in a systematic form, which means that in GF(2), the polynomial
+
+$$a_1 D^{A_i+5} + a_2 D^{A_i+4} + \dots + a_{A_i} D^6 + p_1 D^5 + p_2 D^4 + \dots + p_5 D^1 + p_6$$
+
+yields a remainder equal to 0 when divided by  $g_{CRC6}(D)$  and the polynomial
+
+$$a_1 D^{4+9} + a_2 D^{4+8} + \dots + a_{A_i} D^{10} + p_1 D^9 + p_2 D^8 + \dots + p_9 D^1 + p_{10}$$
+
+yields a remainder equal to 0 when divided by  $g_{CRC10}(D)$ . If  $A_i = 0$ ,  $p_1 = p_2 = p_3 = \dots = p_{L_i} = 0$ .
+
+### 5.6.3 Relation between input and output of the Cyclic Redundancy Check
+
+The protected bits are left unchanged in the frame. The parity bits for the Header CRC are put in the Header CRC field with  $p_1$  being the highest bit position of the first octet of the Header CRC field. The parity bits for the Payload CRC are put in the Payload CRC field with  $p_1$  being the highest bit position of the first octet of the Payload CRC field.

marked/Rel-18/25_series/25450/raw.md

@@ -0,0 +1,377 @@
+
+
+# 3GPP TS 25.450 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iupc interface general aspects and principles (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon below it.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                       |           |
+|-----------------------------------------------------------------------|-----------|
+| Foreword .....                                                        | 4         |
+| 1 Scope.....                                                          | 5         |
+| 2 References.....                                                     | 5         |
+| 3 Definitions and abbreviations .....                                 | 5         |
+| 3.1 Definitions.....                                                  | 5         |
+| 3.2 Abbreviations .....                                               | 6         |
+| 3.3 Specification Notations .....                                     | 6         |
+| 4 General Aspects .....                                               | 7         |
+| 4.1 Introduction .....                                                | 7         |
+| 4.2 Iupc Interface General Principles .....                           | 7         |
+| 4.3 Iupc Interface Specification Objectives .....                     | 8         |
+| 4.4 Iupc Interface Capabilities .....                                 | 8         |
+| 4.4.1 General .....                                                   | 8         |
+| 4.4.2 Position Calculation Services .....                             | 8         |
+| 4.4.3 Information Exchange Services.....                              | 8         |
+| 4.4.4 SAS Centric Position Services .....                             | 8         |
+| 4.5 Iupc Interface Characteristics.....                               | 8         |
+| 4.5.1 Uses of SCCP .....                                              | 8         |
+| 4.5.1.1 General.....                                                  | 8         |
+| 4.5.1.2 SCCP Addressing .....                                         | 8         |
+| 4.5.1.3 SCCP connection establishment .....                           | 9         |
+| 4.5.1.4 SCCP connection release.....                                  | 9         |
+| 4.5.1.5 General SCCP Abnormal Conditions .....                        | 10        |
+| 5 Functions of the Iupc Interface Protocols .....                     | 10        |
+| 5.1 List of Functions.....                                            | 10        |
+| 5.2 Management of GPS Related Data.....                               | 10        |
+| 5.3 Management of Position Calculation Functions .....                | 10        |
+| 5.4 Management of SAS Centric Position Functions.....                 | 10        |
+| 5.5 Management of GANSS Related Data.....                             | 11        |
+| 6 Other Iupc Interface Specifications.....                            | 11        |
+| 6.1 UTRAN Iupc Interface: Layer 1 (TSG RAN 25.451).....               | 11        |
+| 6.2 UTRAN Iupc Interface: Signalling Transport (TSG RAN 25.452) ..... | 11        |
+| 6.3 PCAP Specification (TSG RAN 25.453) .....                         | 11        |
+| 6.4 Summary of UTRAN Iupc Interface Technical Specifications .....    | 11        |
+| <b>Annex A (informative): Change history.....</b>                     | <b>12</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# 1 Scope
+
+The present document is an introduction to the TSG RAN TS 25.45z series of UMTS Technical Specifications that define the Iupc Interface. The Iupc interface is a logical interface for the interconnection of Stand-Alone SMLC (SAS) and Radio Network Controller (RNC) components of the Universal Terrestrial Radio Access Network (UTRAN) for the UMTS system.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] Void
+- [2] 3GPP TS 25.451: "UTRAN Iupc Interface: Layer 1".
+- [3] 3GPP TS 25.452: "UTRAN Iupc Interface: Signalling Transport".
+- [4] 3GPP TS 25.453: "UTRAN Iupc Interface PCAP Signalling".
+- [5] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [6] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages".
+- [7] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [8] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [9] 3GPP TS 23.003: "Numbering, Addressing and Identification".
+- [10] Void
+- [11] 3GPP TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN"
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Stand-Alone SMLC (SAS):** As defined in TS 25.305 [11].
+
+**RNC Centric:** In this mode of operation (defined in TS 25.305 [11]), the RNC is responsible for position method selection and initiation of the selected positioning method. Once a position method is selected, the RNC may interact with the SAS to exchange data as well as for execution of the selected positioning method.
+
+**SAS Centric:** In this mode of operation (defined in TS 25.305 [11]), the SAS is responsible for position method selection and initiation of the selected positioning method. Once a position method is selected, the SAS may interact with the RNC to exchange data to enable it to execute the selected positioning method.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                     |
+|-------|-----------------------------------------------------|
+| GANSS | Galileo and Additional Navigation Satellite Systems |
+| GNSS  | Global Navigation Satellite System                  |
+| GPS   | Global Positioning System                           |
+| GT    | Global Title                                        |
+| M3UA  | SS7 MTP3 User Adaptation Layer                      |
+| PCAP  | Position Calculation Application Part               |
+| RNC   | Radio Network Controller                            |
+| SAS   | Stand-Alone SMLC                                    |
+| SCCP  | Signalling Connection Control Part                  |
+| SMLC  | Serving Mobile Location Centre                      |
+| SPC   | Signalling Point Code                               |
+| SRNC  | Serving Radio Network Controller                    |
+| SS7   | Signalling System N° 7                              |
+| SSN   | Sub-System Number                                   |
+| UE    | User Equipment                                      |
+| UMTS  | Universal Mobile Telecommunication System           |
+| UTRAN | Universal Terrestrial Radio Access Network          |
+
+## 3.3 Specification Notations
+
+For the purposes of the present document, the following notations apply:
+
+- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD.
+- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD.
+- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.
+- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.
+- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.
+- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.
+- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.
+
+- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs.
+- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.
+- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs.
+- Procedure When referring to a procedure in the specification, the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. RNSAP Basic Mobility Procedures.
+- Message When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message.
+- Frame When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH data frame.
+
+# --- 4 General Aspects
+
+## 4.1 Introduction
+
+The logical interface between a RNC and a SAS within the UTRAN is referred to the Iupc interface.
+
+## 4.2 Iupc Interface General Principles
+
+The general principles for the specification of the Iupc interface are as follows:
+
+- the Iupc interface should be open;
+- complex functionality shall as far as possible be avoided over Iupc. Advanced optimisation solutions may be added in later versions of the standard;
+- from a logical standpoint, the Iupc is a point-to-point signalling interface between an RNC and SAS within the UTRAN, even though there may not be a direct physical connection between these two nodes;
+- one RNC may connect to one SAS. One SAS may provide services to one RNC;
+- neither the physical structure nor any internal protocols of the RNC or SAS shall be visible over Iupc and are thus not limiting factors, e.g., when introducing future technology.
+
+## 4.3 Iupc Interface Specification Objectives
+
+The Iupc interface specifications shall facilitate the following:
+
+- inter-connection of RNCs and SASs from different manufacturers;
+- separation of Iupc interface Application functionality and Transport Network functionality to facilitate introduction of future technology.
+
+## 4.4 Iupc Interface Capabilities
+
+### 4.4.1 General
+
+The Iupc interface connects a RNC and a SAS.
+
+### 4.4.2 Position Calculation Services
+
+The Iupc interface enables an SRNC and a SAS to exchange information that is related to the positioning of a single UE. These exchanges involve the transfer of UE Positioning measurement data or UE position estimate data.
+
+### 4.4.3 Information Exchange Services
+
+The Iupc interface enables an RNC to request specific GNSS (GPS or GANSS) related data from an SAS on demand, on modification, or at regular intervals.
+
+### 4.4.4 SAS Centric Position Services
+
+The Iupc interface enables an RNC and a SAS to exchange information that is related to the positioning of a single UE, using SAS Centric mode of operation.
+
+## 4.5 Iupc Interface Characteristics
+
+### 4.5.1 Uses of SCCP
+
+#### 4.5.1.1 General
+
+The SCCP, ITU-T Rec. Q.711 [5], ITU-T Rec. Q.712 [6], ITU-T Rec. Q.713 [7] and ITU-T Rec. Q.714 [8], is used to transport messages between the RNC and SAS. One user function of the SCCP, called Positioning Calculation Application Part (PCAP), is defined TS 25.453 [4].
+
+Both connectionless and connection-oriented procedures are used to support PCAP. TS 25.453 [4] explain whether connection oriented or connectionless services should be used for a layer 3 procedure.
+
+#### 4.5.1.2 SCCP Addressing
+
+The inclusion of caller party address in SCCP message is mandatory. PCAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. When GT addressing is utilised, the following settings shall be used:
+
+- SSN Indicator = 1 (PCAP SSN as defined in TS 23.003 [9]).
+- Global Title Indicator = 0100 (GT includes translation type, numbering plan, encoding scheme and nature of address indicator).
+- Translation Type = 0000 0000 (not used).
+- Numbering Plan = 0001 (E.163/4).
+
+- Nature of Address Indicator = 000 0100 (International Significant Number).
+- Encoding Scheme = 0001 or 0010 (BCD, odd or even).
+- Routing indicator = 0 or 1 (route on GT or PC/SSN).
+
+When used, the GT shall be the E.164 address of the relevant node.
+
+#### 4.5.1.3 SCCP connection establishment
+
+##### Information Exchange services
+
+A new SCCP connection is established when the RNC initiates a class-1 elementary procedure for Information Exchange services and there is no signalling bearer existing for this purpose.
+
+An SCCP connection is always established by the RNC.
+
+##### SAS Centric Position services
+
+A new SCCP connection is established when the RNC initiates a class-1 elementary procedure, with respect to each new positioning request, for SAS Centric Position services.
+
+An SCCP connection is always established by the RNC.
+
+##### Initiation
+
+The RNC sends SCCP CONNECTION REQUEST message to the SAS. A PCAP message is included in the user data field of the SCCP CONNECTION REQUEST message. **Termination**
+
+- **successful outcome:**
+  - The SCCP CONNECTION CONFIRM message, which may optionally contain a PCAP message in the user data field, is returned to the RNC.
+- **unsuccessful outcome:**
+  - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the RNC. This message may contain a PCAP message.
+
+![](9283a3f6b39120df9dc9aee4712b3a0a_img.jpg)
+
+| RNC                                                                                                                                                         | SAS |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
+| CR {SSN=SAS, a1=x, PCAP message}                                                                                                                            |     |
+| ----->                                                                                                                                                      |     |
+| CC {a1=y, a2=x, PCAP message or no user data}                                                                                                               |     |
+| <-----                                                                                                                                                      |     |
+| or                                                                                                                                                          |     |
+| CREF{a2=x, PCAP message or no user data}                                                                                                                    |     |
+| <-----                                                                                                                                                      |     |
+| a1 = source local reference,<br>a2 = destination local reference,<br>x = SCCP connection reference at the RNC,<br>y = SCCP connection reference at the SAS. |     |
+
+**Figure 1: Setting-up of RNC Initiated SCCP Signalling Connection with SAS**
+
+#### 4.5.1.4 SCCP connection release
+
+This procedure is always initiated by the RNC. An SCCP connection is released when the RNC realises that a given signalling connection is no longer required. This is accomplished by the RNC sending a SCCP RELEASED message.
+
+#### 4.5.1.5 General SCCP Abnormal Conditions
+
+If a user-out-of-service information or signalling-point-inaccessible information is received by the RNC, no new attempt to establish SCCP connections towards the affected point code will be started until the corresponding user-in-service information or signalling-point-accessible information is received.
+
+When a user-out-of-service information or signalling-point-inaccessible is received by the RNC, an optional timer may be started. When the timer expires, all the SCCP connections towards the affected point code will be released. When the user-in-service or signalling-point-accessible is received, the timer is stopped.
+
+If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the SAS procedures are being performed or while a dedicated resource is still allocated, the procedures associated to that SCCP connection shall be terminated (at both the RNC side and the SAS side).
+
+# --- 5 Functions of the Iupc Interface Protocols
+
+## 5.1 List of Functions
+
+The list of functions on the Iupc interface is the following:
+
+1. Management of GPS Related Data;
+2. Management of Position Calculation Functions;
+3. Management of SAS Centric Position Functions;
+4. Management of GANSS Related Data,
+
+## 5.2 Management of GPS Related Data
+
+An RNC may request GPS related data from an SAS in order to provide GPS assistance data to a single UE. Alternatively, an RNC may request GPS related data from an SAS in order to support the broadcast of GPS assistance data to multiple UEs in a particular area via system information messages. Each type of GPS related data may be requested on demand, on modification, or at regular intervals.
+
+## 5.3 Management of Position Calculation Functions
+
+To support a *UE-assisted* positioning attempt involving a single UE, an RNC provides an SAS with one or more sets of
+
+- GPS or GANSS measurement data,
+- ODTOA measurement data,
+- Cell ID measurement data.
+
+Subsequently, the SAS calculates the position estimate of the specific UE and returns this result to the RNC.
+
+## 5.4 Management of SAS Centric Position Functions
+
+In the SAS Centric mode of operation, the RNC may initiate a positioning event, the SAS may activate a positioning method requesting the RNC for relevant data, and on completion of the position determination process the SAS may return the final response to the RNC. In addition, during an ongoing positioning event, the RNC may send the SAS a modified set of positioning parameters, or the RNC may even instruct the SAS to abort the positioning process itself.
+
+## 5.5 Management of GANSS Related Data
+
+This management of the GANSS Related Data is the same as the management of the GPS Related Data described in section 5.2, except that it is applicable to Galileo and Additional Navigation Satellite Systems instead of GPS.
+
+# 6 Other Iupc Interface Specifications
+
+## 6.1 UTRAN Iupc Interface: Layer 1 (TSG RAN 25.451)
+
+TS 25.451 [2] specifies the standards allowed for implementation of Layer 1 (physical layer) on the Iupc interface.
+
+## 6.2 UTRAN Iupc Interface: Signalling Transport (TSG RAN 25.452)
+
+TS 25.452 [3] specifies the signalling transport related to PCAP signalling to be used across the Iupc interface.
+
+## 6.3 PCAP Specification (TSG RAN 25.453)
+
+TS 25.453 [4] specifies the standards for PCAP specification to be used over the Iupc interface.
+
+## 6.4 Summary of UTRAN Iupc Interface Technical Specifications
+
+The relationship between the technical specifications that define the UTRAN Iupc interface is shown in figure 2.
+
+![Diagram showing the relationship between technical specifications for the UTRAN Iupc interface. It consists of three layers: Radio Network Layer (PCAP TS 25.453), Transport Layer (PCAP Transport TS 25.452), and Physical Layer (TS 25.451). The layers are stacked vertically, with the Radio Network Layer at the top, the Transport Layer in the middle, and the Physical Layer at the bottom. A dashed vertical line runs through the center of all three layers, indicating their relationship.](536951b2bbd94325ae266d8d1363df8f_img.jpg)
+
+The diagram illustrates the technical specifications for the UTRAN Iupc interface across three layers:
+
+- Radio Network Layer:** Contains a box with "PCAP" and "TS 25.453".
+- Transport Layer:** Contains a box with "PCAP Transport" and "TS 25.452".
+- Physical Layer:** Contains a box with "Physical Layer TS 25.451".
+
+The layers are stacked vertically, with the Radio Network Layer at the top, the Transport Layer in the middle, and the Physical Layer at the bottom. A dashed vertical line runs through the center of all three layers, indicating their relationship.
+
+Diagram showing the relationship between technical specifications for the UTRAN Iupc interface. It consists of three layers: Radio Network Layer (PCAP TS 25.453), Transport Layer (PCAP Transport TS 25.452), and Physical Layer (TS 25.451). The layers are stacked vertically, with the Radio Network Layer at the top, the Transport Layer in the middle, and the Physical Layer at the bottom. A dashed vertical line runs through the center of all three layers, indicating their relationship.
+
+Figure 2: Iupc Interface Technical Specifications.

marked/Rel-18/25_series/25451/raw.md

@@ -0,0 +1,135 @@
+
+
+# 3GPP TS 25.451 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iupc interface layer 1 (Release 18)**
+
+![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G ADVANCED logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+Foreword ..... 4
+
+1 Scope..... 5
+
+2 References..... 5
+
+3 Definitions, symbols and abbreviations ..... 5
+
+4 Iupc Layer 1 ..... 5
+
+**Annex A (informative): Change History..... 6**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+## --- 1 Scope
+
+The present document specifies the standards allowed to implement Layer 1 on the Iupc interface.
+
+The specification of transmission delay requirements and O&M requirements is not in the scope of the present document.
+
+In the following "Layer 1" and "Physical Layer" are assumed to be synonymous.
+
+## --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TS 25.411: "UTRAN Iu interface Layer 1".
+
+## --- 3 Definitions, symbols and abbreviations
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.411 [1] apply.
+
+## --- 4 Iupc Layer 1
+
+The Iupc Layer 1 shall comply with the requirements of clause 4 in TS 25.411 [1].
+
+## Annex A (informative): Change History
+
+| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment                            | New    |
+|------------|----------|----|-----|--------------------------------------------|--------|
+| 12/2008    | -        | -  | -   | Creation of Rel-8 version based on v7.0.0  | 8.0.0  |
+| 12/2009    | -        | -  | -   | Creation of Rel-9 version based on v8.0.0  | 9.0.0  |
+| 03/2011    | -        | -  | -   | Creation of Rel-10 version based on v9.0.0 | 10.0.0 |
+| 09/2012    |          |    |     | Update to Rel-11 version (MCC)             | 11.0.0 |
+| 09/2014    |          |    |     | Update to Rel-12 version (MCC)             | 12.0.0 |
+| 12/2015    |          |    |     | Update to Rel-13 version (MCC)             | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                                  |             |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                  | New version |
+| 2017-03        | SA#75   |      |    |     |     | Promotion to Release 14 without technical change | 14.0.0      |
+| 2018-07        | SA#80   | -    | -  | -   | -   | Promotion to Release 15 without technical change | 15.0.0      |
+| 2020-07        | SA#88-e | -    | -  | -   | -   | Update to Rel-16 version (MCC)                   | 16.0.0      |
+| 2022-03        | SA#95-e |      |    |     |     | Promotion to Release 17 without technical change | 17.0.0      |
+| 2024-03        | SA#103- | -    | -  | -   | -   | Update to Rel-18 version (MCC)                   | 18.0.0      |

marked/Rel-18/25_series/25452/raw.md

@@ -0,0 +1,159 @@
+
+
+# 3GPP TS 25.452 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iupc interface: signalling transport (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                      |          |
+|------------------------------------------------------|----------|
+| Foreword .....                                       | 4        |
+| <i>1</i> Scope.....                                  | 5        |
+| 2 References.....                                    | 5        |
+| 3 Definitions and abbreviations .....                | 5        |
+| 3.1 Definitions.....                                 | 5        |
+| 3.2 Abbreviations .....                              | 5        |
+| 4 PCAP Signalling Bearer.....                        | 6        |
+| 4.1 Introduction .....                               | 6        |
+| 4.2 Signalling Bearer.....                           | 6        |
+| 4.3 Services Provided by the Signalling Bearer ..... | 6        |
+| <b>Annex A (informative): Change history.....</b>    | <b>7</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the signalling transport related to PCAP signalling to be used across the Iupc interface. The Iupc interface is a logical interface for the interconnection of Stand-Alone SMLC (SAS) and Radio Network Controller (RNC) components of the Universal Terrestrial Radio Access Network (UTRAN) for the UMTS system. The radio network control signalling between these nodes is based upon the Position Calculation Application Part (PCAP).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 25.422: "UTRAN Iur Interface Signalling Transport".
+- [2] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [3] ITU-T Recommendation Q.712 (1996-07): "Definition and function of Signalling connection control part messages".
+- [4] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [5] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [6] ITU-T Recommendation Q.715 (1996-07): "Signalling connection control part user guide".
+- [7] ITU-T Recommendation Q.716 (1993-03): "Signalling Connection Control Part (SCCP) performance".
+- [8] 3GPP TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definition applies:
+
+**Stand-Alone SMLC (SAS):** As defined in TS 25.305 [8].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                       |
+|------|---------------------------------------|
+| PCAP | Position Calculation Application Part |
+| SAP  | Service Access Point                  |
+| SAS  | Stand-Alone SMLC                      |
+| SCCP | Signalling Connection Control Part    |
+| SMLC | Serving Mobile Location Centre        |
+
+|       |                                           |
+|-------|-------------------------------------------|
+| UE    | User Equipment                            |
+| UMTS  | Universal Mobile Telecommunication System |
+| UTRAN | UMTS Terrestrial Radio Access Network     |
+
+# --- 4 PCAP Signalling Bearer
+
+## 4.1 Introduction
+
+This clause specifies the Signalling Bearer protocol stack that supports the PCAP signalling protocol.
+
+The following requirements on the Signalling Bearer can be stated:
+
+- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode;
+- provide separate independent connections for distinguishing individual transactions;
+- provide networking and routing functions;
+- provide redundancy in the signalling network;
+- provide load sharing.
+
+## 4.2 Signalling Bearer
+
+The IuPC signalling bearer shall comply with the requirements of clause 5.2 in TS 25.422 [1].
+
+## 4.3 Services Provided by the Signalling Bearer
+
+When considering the requirements that the upper layers, i.e. PCAP, have on the Signalling Bearer, there are a number of services it has to provide and a number of functions to perform. These numbers of services that the signalling bearer shall provide, to the upper layers, are stated in references ITU-T Rec. Q.711 [2], ITU-T Rec. Q.712 [3], ITU-T Rec. Q.713 [4], ITU-T Rec. Q.714 [5], ITU-T Rec. Q.715 [6], and ITU-T Rec. Q.716 [7].

marked/Rel-18/25_series/25460/raw.md

@@ -0,0 +1,141 @@
+
+
+# 3GPP TS 25.460 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface: General aspects and principles (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+Foreword ..... 4
+
+1 Scope..... 5
+
+2 References..... 5
+
+3 to 6 Void..... 5
+
+7 Iuant interface: General aspects and principles..... 5
+
+**Annex A: Void..... 6**
+
+**Annex B (informative): Change History..... 7**
+
+## --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+## --- 1 Scope
+
+See TS 37.460 [8].
+
+## --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1]-[7] Void
+
+[8] 3GPP TS 37.460: "Iuant interface: General aspects and principles".
+
+## --- 3 to 6 Void
+
+## --- 7 Iuant interface: General aspects and principles
+
+See TS 37.460 [8].
+
+## --- Annex A: Void
+
+## Annex B (informative): Change History
+
+| TSG #   | TSG Doc.  | CR   | Rev | Subject/Comment                                            | New    |
+|---------|-----------|------|-----|------------------------------------------------------------|--------|
+| 06/2008 | -         | -    | -   | Creation of Rel-8 version based on v7.1.0                  | 8.0.0  |
+| 40      | RP-080309 | 0007 |     | Correction of figure 6.4.1                                 | 8.0.0  |
+| 43      | RP-090085 | 0008 | 1   | RET and TMA support in LTE                                 | 8.1.0  |
+| 12/2009 | -         | -    | -   | Creation of Rel-9 version based on v8.1.0                  | 9.0.0  |
+| 01/2011 | -         | -    | -   | Creation of Rel-10 version based on v9.0.0                 | 10.0.0 |
+| 03/2011 | SP-100629 |      |     | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.1 |
+| 09/2012 |           |      |     | Update to Rel-11 version (MCC)                             | 11.0.0 |
+| 09/2014 |           |      |     | Update to Rel-12 version (MCC)                             | 12.0.0 |
+| 12/2015 |           |      |     | Update to Rel-13 version (MCC)                             | 13.0.0 |
+
+| Change history |         |           |      |     |     |                                                                       |             |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                       | New version |
+| 2017-03        | SA#75   |           |      |     |     | Promotion to Release 14 without technical change                      | 14.0.0      |
+| 2018-07        | SA#80   | -         | -    | -   | -   | Promotion to Release 15 without technical change                      | 15.0.0      |
+| 2019-04        | RAN#83  | RP-190557 | 0019 | -   | F   | Transfer of Iuant interface specification from 25-series to 37-series | 15.1.0      |
+| 2020-07        | SA#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                        | 16.0.0      |
+| 2022-03        | SA#95-e |           |      |     |     | Promotion to Release 17 without technical change                      | 17.0.0      |
+| 2024-03        | SA#103- | -         | -    | -   | -   | Update to Rel-18 version (MCC)                                        | 18.0.0      |

marked/Rel-18/25_series/25461/raw.md

@@ -0,0 +1,115 @@
+
+
+# 3GPP TS 25.461 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface: Layer 1 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in small black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+Foreword ..... 4
+
+1 Scope..... 5
+
+2 References..... 5
+
+3 to 4 Void..... 5
+
+5 Iuant interface: Layer 1 ..... 5
+
+**Annex A: Void ..... 6**
+
+**Annex B (informative): Change history..... 7**
+
+## --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+## --- 1 Scope
+
+See TS 37.461 [7].
+
+## --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1]-[6] Void.
+
+[7] 3GPP TS 37.461: "Iuant interface: Layer 1".
+
+## --- 3 to 4 Void
+
+## --- 5 Iuant interface: Layer 1
+
+See TS 37.461 [7].
+
+## --- Annex A: Void

marked/Rel-18/25_series/25462/raw.md

@@ -0,0 +1,144 @@
+
+
+# 3GPP TS 25.462 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface: Signalling transport (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+Foreword ..... 4
+
+1 Scope..... 5
+
+2 References..... 5
+
+3 to 4 Void..... 5
+
+5 Iuant interface: Signalling transport..... 5
+
+**Annex A to E: Void ..... 6**
+
+**Annex F (informative): Change History ..... 7**
+
+## --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+## --- 1 Scope
+
+See TS 37.462 [5].
+
+## --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1]-[4] Void.
+
+[5] 3GPP TS 37.462: "Iuant interface: Signalling transport".
+
+## --- 3 to 4 Void
+
+## --- 5 Iuant interface: Signalling transport
+
+See TS 37.462 [5].
+
+---
+
+Annex A to E:  
+Void
+
+## Annex F (informative): Change History
+
+| Date / TSG | TSG Doc.  | CR   | Rev | Subject/Comment                                            | New    |
+|------------|-----------|------|-----|------------------------------------------------------------|--------|
+| 12/2008    | -         | -    | -   | Creation of Rel-8 version based on v7.4.0                  | 8.0.0  |
+| 43         | RP-090085 | 0029 | 1   | RET and TMA support in LTE                                 | 8.1.0  |
+| 12/2009    | -         | -    | -   | Creation of Rel-9 version based on v8.1.0                  | 9.0.0  |
+| 01/2011    | -         | -    | -   | Creation of Rel-10 version based on v9.0.0                 | 10.0.0 |
+| 03/2011    | SP-100629 |      |     | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.1 |
+| 52         | RP-110685 | 0032 |     | Removal of unused references                               | 10.1.0 |
+| 09/2012    |           |      |     | Update to Rel-11 version (MCC)                             | 11.0.0 |
+| 09/2014    |           |      |     | Update to Rel-12 version (MCC)                             | 12.0.0 |
+| 12/2015    |           |      |     | Update to Rel-13 version (MCC)                             | 13.0.0 |
+
+| Change history |         |           |      |     |     |                                                                       |             |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                       | New version |
+| 2017-03        | SA#75   |           |      |     |     | Promotion to Release 14 without technical change                      | 14.0.0      |
+| 2018-07        | SA#80   | -         | -    | -   | -   | Promotion to Release 15 without technical change                      | 15.0.0      |
+| 2019-04        | RAN#83  | RP-190557 | 0040 | -   | F   | Transfer of Iuant interface specification from 25-series to 37-series | 15.1.0      |
+| 2020-07        | SA#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                        | 16.0.0      |
+| 2022-03        | SA#95-e |           |      |     |     | Promotion to Release 17 without technical change                      | 17.0.0      |
+| 2024-03        | SA#103- | -         | -    | -   | -   | Update to Rel-18 version (MCC)                                        | 18.0.0      |

marked/Rel-18/25_series/25466/raw.md

@@ -0,0 +1,179 @@
+
+
+# 3GPP TS 25.466 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iuant Interface: Application Part (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                    |          |
+|----------------------------------------------------|----------|
+| Foreword .....                                     | 4        |
+| 1 Scope.....                                       | 5        |
+| 2 References.....                                  | 5        |
+| 3 to 7 Void.....                                   | 5        |
+| 8 Iuant interface: Application part .....          | 5        |
+| <b>Annex A to F: Void.....</b>                     | <b>6</b> |
+| <b>Annex G (informative): Change History .....</b> | <b>7</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+See TS 37.466 [5].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1]-[4] Void.
+
+[5] 3GPP TS 37.466: "Iuant interface: Application part".
+
+## --- 3 to 7 Void
+
+# --- 8 Iuant interface: Application part
+
+See TS 37.466 [5].
+
+---
+
+Annex A to F:  
+Void
+
+## Annex G (informative): Change History
+
+| TSG #   | TSG Doc.  | CR   | Rev | Subject/Comment                                                                          | New    |
+|---------|-----------|------|-----|------------------------------------------------------------------------------------------|--------|
+| 09/2007 | -         | -    | -   | Creation of Rel-8 version based on v7.2.0                                                | 8.0.0  |
+| 37      | RP-070576 | 0013 |     | Introduction of UMTS1500 requirement                                                     | 8.0.0  |
+| 38      | RP-070838 | 0015 |     | Missing Parameter for "TMA Get Supported Non-Linear Gain Values"                         | 8.1.0  |
+| 39      | RP-080082 | 0016 |     | Introduction of UMTS 700 MHz (Bands XII XIV) in 25.466                                   | 8.2.0  |
+| 43      | RP-090085 | 0017 | 1   | RET and TMA support in LTE                                                               | 8.3.0  |
+| 09/2009 | -         | -    | -   | Creation of Rel-9 version based on v8.3.0                                                |        |
+| 45      | RP-090782 | 0022 |     | Introduction of new antenna operating bands in IuantAP                                   | 9.0.0  |
+| 46      | RP-091185 | 0023 | 1   | Introduction of Extended UMTS/LTE1500 requirements for TS25.466                          | 9.1.0  |
+| 47      | RP-100223 | 0024 | 1   | Introduction of UMTS/LTE in 800 MHz for Europe requirements in TS 25.466                 | 9.2.0  |
+| 09/2010 | -         | -    | -   | Creation of Rel-10 version based on v9.2.0                                               | 10.0.0 |
+| 49      | RP-100912 | 0025 |     | Spectrum band definition additions for TDD 2600 MHz                                      | 10.0.0 |
+| 50      | RP-101184 | 0026 | 1   | Introduction of L-band in TS 25.466                                                      | 10.1.0 |
+| 50      | RP-101278 | 0028 | 1   | CR UMTS/LTE-3500 spectrum band definition additions for TDD Iuant interface to TS 25.466 | 10.1.0 |
+| SP-49   | SP-100629 |      |     | Clarification on the use of References (TS 21.801 CR#0030)                               | 10.1.1 |
+| 52      | RP-110699 | 0036 |     | Add 2 GHz band LTE for ATC of MSS in North America to TS25.466 (Rel-10)                  | 10.2.0 |
+| 52      | RP-110696 | 0037 |     | Add Expanded 1900 MHz Band for UTRA and LTE to TS25.466 (Rel-10)                         | 10.2.0 |
+| 52      | RP-110685 | 0039 |     | Removal of unused references                                                             | 10.2.0 |
+| 54      | RP-111733 | 0042 |     | Removal of references to operating bands i) and h)                                       | 10.3.0 |
+| 03/2012 |           |      |     | Creation of Rel-11 version based on v10.3.0                                              |        |
+| 55      | RP-120266 | 0044 | 2   | Addition of new Band 26 for E850                                                         | 11.0.0 |
+| 56      | RP-120749 | 0045 | 1   | Introduction of E850 LB Band 27 to TS 25.466                                             | 11.1.0 |
+| 56      | RP-120750 | 0046 | -   | Introduction of LTE band for 700 MHz digital dividend                                    | 11.1.0 |
+| 56      | RP-120750 | 0047 | -   | Introduction of TDD band for 700 MHz digital dividend                                    | 11.1.0 |
+| 57      | RP-121140 | 0048 | 1   | Operating bands Numbering for UTRA and EUTRA                                             | 11.2.0 |
+| 58      | RP-121736 | 0049 | -   | Introduction of band 22 in TS 25.466                                                     | 11.3.0 |
+| 58      | RP-121735 | 0050 | 1   | Introduction of Band 29 into TS 25.466                                                   | 11.3.0 |
+| 62      | RP-131903 | 0051 | 1   | Introduction of LTE 450 MHZ                                                              | 12.0.0 |
+| 62      | RP-131904 | 0052 | 1   | Introduction of Band 30                                                                  | 12.0.0 |
+| 64      | RP-140900 | 0054 | 2   | Introduction of L-band for Supplemental Downlink in E-UTRA and UTRA                      | 12.1.0 |
+| 67      | RP-150356 | 0055 | 1   | Correction of the reference                                                              | 12.2.0 |
+| 70      | RP-152107 | 0056 | 2   | Introduction of band 45 in 25.466                                                        | 13.0.0 |
+| 70      | RP-152108 | 0057 | -   | Extension of operating bands field                                                       | 13.0.0 |
+| 70      | RP-152105 | 0058 | -   | Introduction of band 65                                                                  | 13.0.0 |
+| 70      | RP-152106 | 0059 | -   | Introduction of band 66                                                                  | 13.0.0 |
+| 70      | RP-152104 | 0060 | -   | Introduction of band 67                                                                  | 13.0.0 |
+| 71      | RP-160446 | 0061 | -   | Introduction of Band 68 into 25.466                                                      | 13.1.0 |
+| 71      | RP-160450 | 0062 | 1   | Introduction of Band 46 in TS 25.466                                                     | 13.1.0 |
+| 06/2016 |           |      |     | Creation of Rel-14 version based on v13.1.0                                              | 14.0.0 |
+| 72      | RP-161040 | 0063 | 1   | Introduction of band 70                                                                  | 14.0.0 |
+| 72      | RP-161041 | 0064 | 1   | Introduction of 2.6GHz SDL band                                                          | 14.0.0 |
+| 74      | RP-162335 | 0066 | -   | Introduction of band 48                                                                  | 14.1.0 |
+
+| Change history |         |           |      |     |     |                                                                       |             |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                       | New version |
+| 09/2017        | RP-77   | RP-171982 | 0072 | -   | A   | Correction to make band extensions applicable also for TMAAP          | 14.2.0      |
+| 09/2017        | RP-77   | RP-171976 | 0068 | 1   | B   | Introduction of Band 72                                               | 15.0.0      |
+| 09/2017        | RP-77   | RP-171978 | 0070 | 1   | B   | Introduction of the TDD L-band(Band 50 and Band 51)                   | 15.0.0      |
+| 09/2017        | RP-77   | RP-171980 | 0074 |     | B   | Introduction of Band 71                                               | 15.0.0      |
+| 09/2017        | RP-77   | RP-171977 | 0076 | 1   | B   | Introduction of Band 74                                               | 15.0.0      |
+| 09/2017        | RP-77   | RP-171979 | 0077 | 1   | B   | Introduction of Band 75 and 76                                        | 15.0.0      |
+| 12/2017        | RP-78   | RP-172675 | 0067 | 2   | B   | CR to 25.466: Introduction of Band 49 (3.5 GHz LAA in US )            | 15.1.0      |
+| 12/2017        | RP-78   | RP-172711 | 0078 | -   | B   | Introduction of Band 73                                               | 15.1.0      |
+| 03/2018        | RP-79   | RP-180471 | 0079 | 1   | B   | Introduction of band 85                                               | 15.2.0      |
+| 03/2018        | RP-79   | RP-180470 | 0080 | 1   | B   | Introduction of the TDD 3.3-3.4GHz band (Band 52)                     | 15.2.0      |
+| 12/2018        | RP-82   | RP-182447 | 0081 | 1   | F   | Antenna Interface Function support                                    | 15.3.0      |
+| 2019-04        | RAN#83  | RP-190557 | 0089 | -   | F   | Transfer of luant interface specification from 25-series to 37-series | 15.4.0      |
+| 2020-07        | SA#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                        | 16.0.0      |
+| 2022-03        | SA#95-e |           |      |     |     | Promotion to Release 17 without technical change                      | 17.0.0      |
+| 2024-03        | SA#103- | -         | -    | -   | -   | Update to Rel-18 version (MCC)                                        | 18.0.0      |

marked/Rel-18/25_series/25470/raw.md

@@ -0,0 +1,1761 @@
+
+
+# 3GPP TS 25.470 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iuh interface PCAP User Adaption (PUA) signalling (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                     |    |
+|-----------------------------------------------------|----|
+| Foreword .....                                      | 5  |
+| 1 Scope.....                                        | 6  |
+| 2 References.....                                   | 6  |
+| 3 Definitions and abbreviations .....               | 6  |
+| 3.1 Definitions.....                                | 6  |
+| 3.2 Abbreviations .....                             | 6  |
+| 4 General.....                                      | 7  |
+| 4.1 Procedure specification principles .....        | 7  |
+| 4.2 Forwards and backwards compatibility.....       | 7  |
+| 4.3 Specification notations .....                   | 7  |
+| 5 PUA services.....                                 | 8  |
+| 6 Services expected from the transport layer.....   | 8  |
+| 7 Functions of PUA.....                             | 8  |
+| 8 PUA procedures .....                              | 8  |
+| 8.1 Elementary Procedures.....                      | 8  |
+| 8.2 Connect.....                                    | 8  |
+| 8.2.1 General .....                                 | 8  |
+| 8.2.2 Successful Operation .....                    | 9  |
+| 8.3 Direct Transfer .....                           | 9  |
+| 8.3.1 General .....                                 | 9  |
+| 8.3.2 Successful Operation (HNB-GW Originated)..... | 9  |
+| 8.3.3 Successful Operation (HNB Originated).....    | 9  |
+| 8.3.4 Abnormal Conditions .....                     | 10 |
+| 8.4 Disconnect.....                                 | 10 |
+| 8.4.1 General .....                                 | 10 |
+| 8.4.2 Successful Operation (HNB Originated).....    | 10 |
+| 8.4.3 Successful Operation (HNB-GW Originated)..... | 10 |
+| 8.5 Connectionless Transfer.....                    | 10 |
+| 8.5.1 General .....                                 | 10 |
+| 8.5.2 Successful Operation (HNB-GW Originated)..... | 11 |
+| 8.5.3 Successful Operation (HNB Originated).....    | 11 |
+| 8.5.4 Abnormal Conditions .....                     | 11 |
+| 8.6 Error Indication .....                          | 11 |
+| 8.6.1 General .....                                 | 11 |
+| 8.6.2 Successful Operation .....                    | 11 |
+| 9 Elements for PUA communication .....              | 12 |
+| 9.1 Message functional definition and content.....  | 12 |
+| 9.1.1 General .....                                 | 12 |
+| 9.1.2 Message contents.....                         | 12 |
+| 9.1.2.1 Presence .....                              | 12 |
+| 9.1.2.2 Criticality .....                           | 12 |
+| 9.1.2.3 Range .....                                 | 13 |
+| 9.1.2.4 Assigned Criticality .....                  | 13 |
+| 9.1.3 CONNECT .....                                 | 13 |
+| 9.1.4 DIRECT TRANSFER .....                         | 13 |
+| 9.1.5 DISCONNECT.....                               | 13 |
+| 9.1.6 CONNECTIONLESS TRANSFER .....                 | 14 |
+| 9.1.7 ERROR INDICATION .....                        | 14 |
+| 9.2 Information Element Definitions .....           | 14 |
+| 9.2.0 General .....                                 | 14 |
+| 9.2.1 Message Type.....                             | 15 |
+
+|                               |                                                                                                    |           |
+|-------------------------------|----------------------------------------------------------------------------------------------------|-----------|
+| 9.2.2                         | PCAP Context ID .....                                                                              | 15        |
+| 9.2.3                         | PCAP Message .....                                                                                 | 15        |
+| 9.2.4                         | SAS Indicator .....                                                                                | 15        |
+| 9.2.5                         | Transaction ID .....                                                                               | 15        |
+| 9.2.6                         | Cause .....                                                                                        | 15        |
+| 9.2.7                         | Criticality Diagnostics .....                                                                      | 17        |
+| 9.3                           | Message and Information Element Abstract Syntax (with ASN.1) .....                                 | 19        |
+| 9.3.0                         | General .....                                                                                      | 19        |
+| 9.3.1                         | Usage of private message mechanism for non-standard use .....                                      | 19        |
+| 9.3.2                         | Elementary Procedure Definitions .....                                                             | 19        |
+| 9.3.3                         | PDU definitions .....                                                                              | 22        |
+| 9.3.4                         | Information Element definitions .....                                                              | 26        |
+| 9.3.5                         | Common definitions .....                                                                           | 28        |
+| 9.3.6                         | Constant definitions .....                                                                         | 29        |
+| 9.3.7                         | Container definitions .....                                                                        | 30        |
+| 9.4                           | Message transfer syntax .....                                                                      | 34        |
+| 10                            | Handling of unknown, unforeseen, and erroneous protocol data .....                                 | 35        |
+| 10.1                          | General .....                                                                                      | 35        |
+| 10.2                          | Transfer Syntax Error .....                                                                        | 35        |
+| 10.3                          | Abstract Syntax Error .....                                                                        | 35        |
+| 10.3.1                        | General .....                                                                                      | 35        |
+| 10.3.2                        | Criticality Information .....                                                                      | 36        |
+| 10.3.3                        | Presence Information .....                                                                         | 36        |
+| 10.3.4                        | Not comprehended IE/IE group .....                                                                 | 37        |
+| 10.3.4.1                      | Procedure Code .....                                                                               | 37        |
+| 10.3.4.1A                     | Type of Message .....                                                                              | 37        |
+| 10.3.4.2                      | IEs other than the Procedure Code and Type of Message .....                                        | 37        |
+| 10.3.5                        | Missing IE or IE group .....                                                                       | 38        |
+| 10.3.6                        | IEs or IE groups received in wrong order or with too many occurrences or erroneously present ..... | 39        |
+| 10.4                          | Logical Error .....                                                                                | 40        |
+| 10.5                          | Exceptions .....                                                                                   | 40        |
+| <b>Annex A (informative):</b> | <b>Change history .....</b>                                                                        | <b>41</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document specifies the *PCAP User Adaption* (PUA) between the Home Node B (HNB) and the Home Node B Gateway (HNB-GW). It fulfils the HNB- HNB-GW communication requirements specified in TS 25.467 [5] and is defined over the Iuh – reference point. It provides transport for PCAP messages.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.453: "UTRAN Iupc interface Positioning Calculation Application Part (PCAP) signalling".
+- [3] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol".
+- [4] 3GPP TR 25.921 (Version 7.0.0): "Guidelines and principles for protocol description and error handling".
+- [5] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B; Stage 2".
+- [6] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".
+- [7] ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
+- [8] ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|     |                      |
+|-----|----------------------|
+| CN  | Core Network         |
+| EP  | Elementary Procedure |
+| HNB | Home Node B          |
+
+|        |                                      |
+|--------|--------------------------------------|
+| HNB-GW | Home Node B Gateway                  |
+| PDU    | Protocol Data Unit                   |
+| PUA    | PCAP User Adaption                   |
+| SCTP   | Stream Control Transmission Protocol |
+
+# --- 4 General
+
+The protocol described in the present document is the protocol between HNB-GW and HNB.
+
+## 4.1 Procedure specification principles
+
+The principle for specifying the procedure logic is to specify the functional behaviour of the HNB & HNB-GW exactly and completely.
+
+The following specification principles have been applied for the procedure text in clause 8:
+
+- The procedure text discriminates between:
+  - 1) Functionality which "shall" be executed:
+    - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
+  - 2) Functionality which "shall, if supported" be executed:
+    - The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
+- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included.
+
+## 4.2 Forwards and backwards compatibility
+
+The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.
+
+## 4.3 Specification notations
+
+For the purposes of the present document, the following notations apply:
+
+- |           |                                                                                                                                                                                                                                                                              |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Direct Transfer procedure.                                                  |
+| Message   | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. CONNECT message.                                                                                                 |
+| IE        | When referring to an information element (IE) in the specification the <i>Information Element Name</i> is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. <i>Context ID IE</i> . |
+
+Value of an IE When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ".
+
+# 5 PUA services
+
+PUA provides the signalling service between the HNB and the HNB-GW that is required to fulfil the PUA functions described in Clause 7.
+
+# 6 Services expected from the transport layer
+
+Following service is expected from the transport layer:
+
+- reliable and in sequence delivery of Signalling data using SCTP (IETF RFC 4960 [3])
+
+# 7 Functions of PUA
+
+The PUA has the following functions:
+
+- Transparent transfer of PCAP messages
+- Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined.
+
+These functions are implemented by one or several PUA elementary procedures described in the following clauses.
+
+# 8 PUA procedures
+
+## 8.1 Elementary Procedures
+
+Table 1 summarizes the EPs.
+
+**Table 1; Elementary procedures**
+
+| Elementary Procedure    | Message                 |
+|-------------------------|-------------------------|
+| Connect                 | CONNECT                 |
+| Direct Transfer         | DIRECT TRANSFER         |
+| Disconnect              | DISCONNECT              |
+| Connectionless Transfer | CONNECTIONLESS TRANSFER |
+| Error Indication        | ERROR INDICATION        |
+
+## 8.2 Connect
+
+### 8.2.1 General
+
+The HNB can initiate this procedure to establish a Signalling Connection and carry a PCAP message.
+
+### 8.2.2 Successful Operation
+
+![Sequence diagram for Figure 8.2.2-1: Connect procedure – successful operation. It shows two nodes, HNB and HNB-GW, each with a lifeline. A horizontal arrow labeled 'CONNECT' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick vertical bar representing the end of the procedure.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+Sequence diagram for Figure 8.2.2-1: Connect procedure – successful operation. It shows two nodes, HNB and HNB-GW, each with a lifeline. A horizontal arrow labeled 'CONNECT' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick vertical bar representing the end of the procedure.
+
+**Figure 8.2.2-1: Connect procedure – successful operation**
+
+This procedure is used to carry the first PCAP message from the HNB to the HNB-GW.
+
+If the *SAS Indicator* IE is included the HNB-GW may use to select a SAS for connection.
+
+Additional information is provided to enable the HNB-GW to trigger the establishment of a new Signalling Connection between HNB and HNB-GW, which is directly mapped to the IuPC Signalling Connection the PCAP message refers to.
+
+NOTE: The Context ID is used as the IuPC Signalling Connection identifier in the corresponding PCAP messages.
+
+## 8.3 Direct Transfer
+
+### 8.3.1 General
+
+This procedure is initiated by either the HNB or HNB-GW to transport a PCAP message between the two nodes.
+
+### 8.3.2 Successful Operation (HNB-GW Originated)
+
+![Sequence diagram for Figure 8.3.2-1: Direct Transfer procedure – successful operation. It shows two nodes, HNB and HNB-GW, each with a lifeline. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB-GW lifeline to the HNB lifeline. Both lifelines end in a thick vertical bar representing the end of the procedure.](5a24ac755b962fd5f0183f13de0726de_img.jpg)
+
+Sequence diagram for Figure 8.3.2-1: Direct Transfer procedure – successful operation. It shows two nodes, HNB and HNB-GW, each with a lifeline. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB-GW lifeline to the HNB lifeline. Both lifelines end in a thick vertical bar representing the end of the procedure.
+
+**Figure 8.3.2-1: Direct Transfer procedure – successful operation**
+
+This procedure is used to carry any downlink connection-oriented PCAP message defined in TS 25.453 [2] from the HNB-GW to the HNB.
+
+### 8.3.3 Successful Operation (HNB Originated)
+
+![Sequence diagram for Figure 8.3.3-1: Direct Transfer procedure – successful operation. It shows two nodes, HNB and HNB-GW, each with a lifeline. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick vertical bar representing the end of the procedure.](22b127dfdf650562ffc121fe88693c85_img.jpg)
+
+Sequence diagram for Figure 8.3.3-1: Direct Transfer procedure – successful operation. It shows two nodes, HNB and HNB-GW, each with a lifeline. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick vertical bar representing the end of the procedure.
+
+**Figure 8.3.3-1: Direct Transfer procedure – successful operation**
+
+This procedure is used to carry any uplink connection-oriented PCAP message defined in TS 25.453 [2], except those carried in CONNECT or DISCONNECT messages, from the HNB to the HNB-GW.
+
+### 8.3.4 Abnormal Conditions
+
+-
+
+## 8.4 Disconnect
+
+### 8.4.1 General
+
+This procedure is normally initiated by the HNB to terminate a Signalling Connection between the HNB and HNB-GW, but may be initiated by the HNB-GW to close a refused connection or if an existing connection is released (e.g. for error reasons) by the SAS or HNB-GW.
+
+### 8.4.2 Successful Operation (HNB Originated)
+
+![Sequence diagram for HNB-originated DISCONNECT procedure](b0211cee4b20034939d883ac0d70f696_img.jpg)
+
+A sequence diagram showing the interaction between an HNB and an HNB-GW. The HNB is on the left and the HNB-GW is on the right. A horizontal arrow labeled 'DISCONNECT' points from the HNB to the HNB-GW. Both entities are represented by a box above a thick horizontal line representing the ground or base.
+
+Sequence diagram for HNB-originated DISCONNECT procedure
+
+Figure 8.4.2-1: Disconnect procedure
+
+This procedure is used to release a signalling connection between the HNB and HNB-GW and may carry the last PCAP (TS 25.453 [2]) uplink connection-oriented message of a given Signalling Connection to the HNB-GW over the Iuh interface. This procedure may also be used to indicate error conditions at the HNB. This procedure will indicate the cause of the termination in the *Cause* IE.
+
+### 8.4.3 Successful Operation (HNB-GW Originated)
+
+![Sequence diagram for HNB-GW-originated DISCONNECT procedure](ee8536b235eb6aad21e2048fd5308900_img.jpg)
+
+A sequence diagram showing the interaction between an HNB and an HNB-GW. The HNB is on the left and the HNB-GW is on the right. A horizontal arrow labeled 'DISCONNECT' points from the HNB-GW to the HNB. Both entities are represented by a box above a thick horizontal line representing the ground or base.
+
+Sequence diagram for HNB-GW-originated DISCONNECT procedure
+
+Figure 8.4.3-1: Disconnect procedure
+
+This procedure is used to close a given Signalling Connection between the HNB and the HNB-GW over the Iuh interface. This procedure will indicate the cause of the termination in the *Cause* IE.
+
+## 8.5 Connectionless Transfer
+
+### 8.5.1 General
+
+This procedure is initiated by either the HNB or the HNB-GW to transfer connectionless PCAP messages between the HNB and HNB-GW.
+
+### 8.5.2 Successful Operation (HNB-GW Originated)
+
+![Sequence diagram for Figure 8.5.2-1: Connectionless Transfer procedure to HNB. It shows two entities, HNB and HNB-GW, each with a vertical lifeline. A horizontal arrow labeled 'CONNECTIONLESS TRANSFER' points from the HNB-GW lifeline to the HNB lifeline. Both lifelines end in a thick horizontal bar at the bottom.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+Sequence diagram for Figure 8.5.2-1: Connectionless Transfer procedure to HNB. It shows two entities, HNB and HNB-GW, each with a vertical lifeline. A horizontal arrow labeled 'CONNECTIONLESS TRANSFER' points from the HNB-GW lifeline to the HNB lifeline. Both lifelines end in a thick horizontal bar at the bottom.
+
+Figure 8.5.2-1: Connectionless Transfer procedure to HNB
+
+This procedure is used to carry any downlink connectionless PCAP message defined in TS 25.453 [2] from the HNB-GW to the HNB.
+
+### 8.5.3 Successful Operation (HNB Originated)
+
+![Sequence diagram for Figure 8.5.3-1: Connectionless Transfer procedure to HNB-GW. It shows two entities, HNB and HNB-GW, each with a vertical lifeline. A horizontal arrow labeled 'CONNECTIONLESS TRANSFER' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick horizontal bar at the bottom.](c78c2eefd86269d1740ab85a916f24f2_img.jpg)
+
+Sequence diagram for Figure 8.5.3-1: Connectionless Transfer procedure to HNB-GW. It shows two entities, HNB and HNB-GW, each with a vertical lifeline. A horizontal arrow labeled 'CONNECTIONLESS TRANSFER' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick horizontal bar at the bottom.
+
+Figure 8.5.3-1: Connectionless Transfer procedure to HNB-GW
+
+This procedure is used to carry any uplink connectionless PCAP message defined in TS 25.453 [2] from the HNB to the HNB-GW. If the *SAS Indicator* IE is included the HNB-GW may use to select a SAS as the destination of the message.
+
+### 8.5.4 Abnormal Conditions
+
+-
+
+## 8.6 Error Indication
+
+### 8.6.1 General
+
+The Error Indication procedure is initiated by either HNB or HNB-GW to report detected errors in one incoming message.
+
+### 8.6.2 Successful Operation
+
+![Sequence diagram for Figure 8.6.2-1: Error Indication HNB Originated, Successful Operation. It shows two entities, HNB and HNB-GW, each with a vertical lifeline. A horizontal arrow labeled 'ERROR INDICATION' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick horizontal bar at the bottom.](04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg)
+
+Sequence diagram for Figure 8.6.2-1: Error Indication HNB Originated, Successful Operation. It shows two entities, HNB and HNB-GW, each with a vertical lifeline. A horizontal arrow labeled 'ERROR INDICATION' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick horizontal bar at the bottom.
+
+Figure 8.6.2-1 Error Indication HNB Originated, Successful Operation
+
+![Sequence diagram showing an ERROR INDICATION message from HNB-GW to HNB.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+
+sequenceDiagram
+    participant HNB
+    participant HNB-GW
+    Note left of HNB: 
+    Note right of HNB-GW: 
+    HNB-GW->>HNB: ERROR INDICATION
+  
+```
+
+The diagram shows two vertical lifelines. The left lifeline is labeled 'HNB' and the right lifeline is labeled 'HNB-GW'. Both lifelines have a small black rectangle at the bottom. A horizontal arrow labeled 'ERROR INDICATION' points from the HNB-GW lifeline to the HNB lifeline.
+
+Sequence diagram showing an ERROR INDICATION message from HNB-GW to HNB.
+
+Figure 8.6.2-2 Error Indication HNB-GW Originated, Successful Operation
+
+# 9 Elements for PUA communication
+
+## 9.1 Message functional definition and content
+
+### 9.1.1 General
+
+Section 9.1 presents the contents of PUA messages in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence.
+
+NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [4].
+
+For each message there is, a table listing the signalling elements in their order of appearance in the transmitted message.
+
+### 9.1.2 Message contents
+
+#### 9.1.2.1 Presence
+
+All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 3.
+
+**Table 2: Meaning of abbreviations used in PUA messages**
+
+| Abbreviation | Meaning                                                                                                                            |
+|--------------|------------------------------------------------------------------------------------------------------------------------------------|
+| M            | IE's marked as Mandatory (M) will always be included in the message.                                                               |
+| O            | IE's marked as Optional (O) may or may not be included in the message.                                                             |
+| C            | IE's marked as Conditional (C) will be included in a message only if the condition is satisfied. Otherwise the IE is not included. |
+
+#### 9.1.2.2 Criticality
+
+Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible.
+
+**Table 3: Meaning of content within "Criticality" column**
+
+| Abbreviation  | Meaning                                                                                                                                                                             |
+|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| –             | No criticality information is applied explicitly.                                                                                                                                   |
+| <b>YES</b>    | Criticality information is applied. This is usable only for non-repeatable IEs                                                                                                      |
+| <b>GLOBAL</b> | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs.                                                            |
+| <b>EACH</b>   | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. |
+
+#### 9.1.2.3 Range
+
+The Range column indicates the allowed number of copies of repetitive IEs/IE groups.
+
+#### 9.1.2.4 Assigned Criticality
+
+This column provides the actual criticality information as defined in subclause 10.3.2, if applicable.
+
+### 9.1.3 CONNECT
+
+This message is sent by the HNB to the HNB-GW to establish a signalling connection and carry a PCAP message.
+
+Direction: HNB → HNB-GW
+
+| PARAMETER       | PRESENCE | RANGE | IE Type and Reference | Semantics Description                                                                                     | Criticality | Assigned Criticality |
+|-----------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type    | M        |       | 9.2.1                 |                                                                                                           | YES         | ignore               |
+| PCAP Context ID | M        |       | 9.2.2                 |                                                                                                           | YES         | reject               |
+| PCAP Message    | M        |       | 9.2.3                 |                                                                                                           | YES         | reject               |
+| SAS Indicator   | O        |       | 9.2.4                 | SAS indicator is used to select a target SAS where multiple SAS are connected and is set by configuration | YES         | ignore               |
+
+### 9.1.4 DIRECT TRANSFER
+
+This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to transport a connection-oriented PCAP message between the two nodes.
+
+Direction: HNB → HNB-GW and HNB-GW → HNB
+
+| PARAMETER       | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type    | M        |       | 9.2.1                 |                       | YES         | ignore               |
+| PCAP Context ID | M        |       | 9.2.2                 |                       | YES         | reject               |
+| PCAP Message    | M        |       | 9.2.3                 |                       | YES         | reject               |
+
+### 9.1.5 DISCONNECT
+
+This message is sent either by the HNB to the HNB-GW or the HNB-GW to the HNB to close the signalling connection between the two nodes.
+
+Direction: HNB → HNB-GW and HNB-GW → HNB
+
+| PARAMETER       | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type    | M        |       | 9.2.1                 |                       | YES         | ignore               |
+| PCAP Context ID | M        |       | 9.2.2                 |                       | YES         | reject               |
+| Cause           | M        |       | 9.2.6                 |                       | YES         | reject               |
+| PCAP Message    | O        |       | 9.2.3                 |                       | YES         | reject               |
+
+### 9.1.6 CONNECTIONLESS TRANSFER
+
+This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to transport a connectionless PCAP message between the two nodes.
+
+Direction: HNB → HNB-GW and HNB-GW → HNB
+
+| PARAMETER     | PRESENCE | RANGE | IE Type and Reference | Semantics Description                                                                                     | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type  | M        |       | 9.2.1                 |                                                                                                           | YES         | ignore               |
+| PCAP Message  | M        |       | 9.2.3                 |                                                                                                           | YES         | reject               |
+| SAS Indicator | O        |       | 9.2.4                 | SAS indicator is used to select a target SAS where multiple SAS are connected and is set by configuration | YES         | ignore               |
+
+### 9.1.7 ERROR INDICATION
+
+This message is sent by either the HNB to HNB-GW or the HNB-GW to the HNB and is used to indicate that some errors have been detected.
+
+Direction: HNB → HNB-GW, HNB-GW → HNB
+
+| PARAMETER               | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.2.1                 |                       | YES         | ignore               |
+| Cause                   | M        |       | 9.2.6                 |                       | YES         | ignore               |
+| Criticality Diagnostics | O        |       | 9.2.7                 |                       | YES         | ignore               |
+| PCAP Context ID         | O        |       | 9.2.2                 |                       | YES         | ignore               |
+| Transaction ID          | O        |       | 9.2.5                 |                       | YES         | ignore               |
+
+## 9.2 Information Element Definitions
+
+### 9.2.0 General
+
+Section 9.2 presents the PUA IE definitions in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence.
+
+When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits:
+
+- The first bit (leftmost bit) contains the most significant bit (MSB);
+- The last bit (rightmost bit) contains the least significant bit (LSB);
+
+- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information.
+
+### 9.2.1 Message Type
+
+*Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages.
+
+| IE/GROUP NAME       | PRESENCE | RANGE | IE Type and Reference                                                                          | Semantics Description |
+|---------------------|----------|-------|------------------------------------------------------------------------------------------------|-----------------------|
+| <b>Message Type</b> |          |       |                                                                                                |                       |
+| >Procedure Code     | M        |       | INTEGER(0..255)                                                                                |                       |
+| >Type of Message    | M        |       | ENUMERATED<br>(Initiating Message,<br>Successful Outcome,<br>Unsuccessful Outcome,<br>Outcome) |                       |
+
+### 9.2.2 PCAP Context ID
+
+*PCAP Context ID* IE uniquely identifies a PUA context in the HNB and HNB-GW.
+
+| IE/GROUP NAME | PRESENCE | RANGE | IE Type and          | Semantics Description |
+|---------------|----------|-------|----------------------|-----------------------|
+| Context ID    |          |       | BIT STRING(SIZE(24)) |                       |
+
+### 9.2.3 PCAP Message
+
+*PCAP Message* IE contains the transferred PCAP message.
+
+| IE/GROUP NAME | PRESENCE | RANGE | IE Type and  | Semantics Description |
+|---------------|----------|-------|--------------|-----------------------|
+| PCAP Message  |          |       | OCTET STRING |                       |
+
+### 9.2.4 SAS Indicator
+
+This element indicates the SAS to be used.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| SAS Indicator | M        |       | INTEGER(0..255)       |                       |
+
+### 9.2.5 Transaction ID
+
+This element indicates the Transaction ID as described in PCAP.
+
+| IE/Group Name  | Presence | Range | IE Type and Reference | Semantics Description         |
+|----------------|----------|-------|-----------------------|-------------------------------|
+| Transaction ID | M        |       | BIT STRING (SIZE(16)) | As defined in PCAP 25.453 [2] |
+
+### 9.2.6 Cause
+
+*Cause* IE indicates the reason for a particular error event or disconnect for the PUA protocol.
+
+| IE/Group Name                | Presence | Range | IE Type and Reference                                                                                                                                                                                                                                                    | Semantics Description |
+|------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| CHOICE <i>Cause Group</i>    |          |       |                                                                                                                                                                                                                                                                          |                       |
+| > <i>Radio Network Layer</i> |          |       |                                                                                                                                                                                                                                                                          |                       |
+| >>Radio Network Layer Cause  | M        |       | ENUMERATED<br>(<br>Normal,<br>Connect failed,<br>HNB-GW release,<br>SAS release,<br>Unspecified,<br>...<br>)                                                                                                                                                             |                       |
+| > <i>Transport Layer</i>     |          |       |                                                                                                                                                                                                                                                                          |                       |
+| >>Transport Layer Cause      | M        |       | ENUMERATED<br>(Transport Resource Unavailable,<br>Unspecified,<br>...)                                                                                                                                                                                                   |                       |
+| > <i>Protocol</i>            |          |       |                                                                                                                                                                                                                                                                          |                       |
+| >>Protocol Cause             | M        |       | ENUMERATED<br>(Transfer Syntax Error,<br>Abstract Syntax Error (Reject),<br>Abstract Syntax Error (Ignore and Notify),<br>Message not Compatible with Receiver State,<br>Semantic Error,<br>Unspecified,<br>Abstract Syntax Error (Falsely Constructed Message),<br>...) |                       |
+| > <i>Misc</i>                |          |       |                                                                                                                                                                                                                                                                          |                       |
+| >>Misc Cause                 | M        |       | ENUMERATED<br>(Processing Overload,<br>Hardware Failure,<br>O&M Intervention,<br>SAS unavailable,<br>SAS not configured,<br>Unspecified,<br>...)                                                                                                                         |                       |
+
+The meaning of the different cause values is described in the following table. Cause values for information 'not valid' indicates that the information is not valid in the context that it was received.
+
+| Radio Network Layer cause | Meaning                                                                                              |
+|---------------------------|------------------------------------------------------------------------------------------------------|
+| Normal                    | No error has occurred                                                                                |
+| Connect failed            | Connect attempt failed                                                                               |
+| HNB-GW release            | Connection released by HNB-GW                                                                        |
+| SAS release               | Connection released by SAS                                                                           |
+| Unspecified               | Sent when none of the above cause values applies but still the cause is Radio Network layer related. |
+
+| Transport Network Layer cause  | Meaning                                                                                                  |
+|--------------------------------|----------------------------------------------------------------------------------------------------------|
+| Transport resource unavailable | <b>The required transport resources are not available.</b>                                               |
+| Unspecified                    | Sent when none of the above cause values applies but still the cause is Transport Network layer related. |
+
+| Protocol cause                                      | Meaning                                                                                                             |
+|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
+| Abstract Syntax Error (Reject)                      | The received message included an abstract syntax error and the concerned criticality indicated "reject".            |
+| Abstract Syntax Error (Ignore and Notify)           | The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify". |
+| Abstract syntax error (falsely constructed message) | The received message contained IEs in wrong order or with too many occurrences.                                     |
+| Message not Compatible with Receiver State          | The received message was not compatible with the receiver state.                                                    |
+| Semantic Error                                      | The received message included a semantic error.                                                                     |
+| Transfer Syntax Error                               | The received message included a transfer syntax error.                                                              |
+| Unspecified                                         | Sent when none of the above cause values applies but still the cause is protocol related.                           |
+
+| Miscellaneous cause | Meaning                                                |
+|---------------------|--------------------------------------------------------|
+| Processing Overload | Control processing overload.                           |
+| Hardware Failure    | HNB hardware failure.                                  |
+| O&M Intervention    | Operation and Maintenance intervention related to HNB. |
+| SAS unavailable     | Connection to the SAS is not possible.                 |
+| SAS not configured  | No SAS is configured, or selected SAS is unrecognized. |
+| Unspecified         | Sent when none of the above cause values applies.      |
+
+### 9.2.7 Criticality Diagnostics
+
+The *Criticality Diagnostics* IE is sent by the HNB or the HNB-GW when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing.
+
+| IE/Group Name                                      | Presence | Range                 | IE type and reference                                                     | Semantics description                                                                                                                                                          |
+|----------------------------------------------------|----------|-----------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Criticality Diagnostics</b>                     |          |                       |                                                                           |                                                                                                                                                                                |
+| >Procedure Code                                    | O        |                       | INTEGER (0..255)                                                          | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error |
+| >Triggering Message                                | O        |                       | ENUMERATED (initiating message, successful outcome, unsuccessful outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure.                                                                      |
+| >Procedure Criticality                             | O        |                       | ENUMERATED(reject, ignore, notify)                                        | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure).                                                                        |
+| <b>Information Element Criticality Diagnostics</b> |          | 0 to <maxNr OfErrors> |                                                                           |                                                                                                                                                                                |
+| >IE Criticality                                    | M        |                       | ENUMERATED(reject, ignore, notify)                                        | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used.                                                           |
+| >IE ID                                             | M        |                       | INTEGER (0..65535)                                                        | The IE Id of the not understood or missing IE                                                                                                                                  |
+| >Type of Error                                     | M        |                       | ENUMERATED(not                                                            |                                                                                                                                                                                |
+
+| IE/Group Name                  | Presence | Range | IE type and reference     | Semantics description |
+|--------------------------------|----------|-------|---------------------------|-----------------------|
+| <b>Criticality Diagnostics</b> |          |       |                           |                       |
+|                                |          |       | understood, missing, ...) |                       |
+
+| Range bound   | Explanation                                                                                                |
+|---------------|------------------------------------------------------------------------------------------------------------|
+| maxNrOfErrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxNrOfErrors is 256. |
+
+## 9.3 Message and Information Element Abstract Syntax (with ASN.1)
+
+### 9.3.0 General
+
+PUA ASN.1 definition conforms with ITU-T Rec. X.680 [7] and ITU-T Rec. X.681 [8].
+
+The ASN.1 definition specifies the structure and content of PUA messages. PUA messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a PUA message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids):
+
+- IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
+- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
+
+If a PUA message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in subclause 10.3.6.
+
+### 9.3.1 Usage of private message mechanism for non-standard use
+
+The private message mechanism for non-standard use may be used:
+
+- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability;
+- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.
+
+The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.
+
+### 9.3.2 Elementary Procedure Definitions
+
+```
+
+-- *****
+--
+-- Elementary Procedure definitions
+--
+-- *****
+
+```
+
+```
+
+PUA-PDU-Descriptions {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  umts-Access (20) modules (3) pua(7) version1 (1) pUA-PDU-Descriptions (0)}
+
+```
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+```
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+```
+
+IMPORTS
+
+```
+  Criticality,
+  ProcedureCode
+FROM PUA-CommonDataTypes
+  Connect,
+  DirectTransfer,
+  Disconnect,
+  ConnectionlessTransfer,
+  ErrorIndication,
+  PrivateMessage
+```
+
+FROM PUA-PDU-Contents
+
+```
+  id-Connect,
+  id-DirectTransfer,
+  id-Disconnect,
+  id-ConnectionlessTransfer,
+  id-ErrorIndication,
+  id-privateMessage
+```
+
+FROM PUA-Constants;
+
+```
+-- *****
+--
+-- Interface Elementary Procedure Class
+--
+-- *****
+```
+
+PUA-ELEMENTARY-PROCEDURE ::= CLASS {
+
+```
+  &InitiatingMessage      ,
+  &SuccessfulOutcome    OPTIONAL,
+  &UnsuccessfulOutcome  OPTIONAL,
+  &procedureCode        ProcedureCode  UNIQUE,
+  &criticality          Criticality  DEFAULT ignore
+}
+```
+
+WITH SYNTAX {
+
+```
+  INITIATING MESSAGE      &InitiatingMessage
+  [SUCCESSFUL OUTCOME    &SuccessfulOutcome]
+  [UNSUCCESSFUL OUTCOME  &UnsuccessfulOutcome]
+  PROCEDURE CODE        &procedureCode
+  [CRITICALITY           &criticality]
+}
+```
+
+```
+-- *****
+--
+-- Interface PDU definitions
+```
+
+```
+
+--
+-- *****
+--
+PUA-PDU ::= CHOICE {
+    initiatingMessage     InitiatingMessage,
+    successfulOutcome     SuccessfulOutcome,
+    unsuccessfulOutcome   UnsuccessfulOutcome,
+    ...
+}
+
+InitiatingMessage ::= SEQUENCE {
+    procedureCode     PUA-ELEMENTARY-PROCEDURE.&procedureCode      ({PUA-ELEMENTARY-PROCEDURES}),
+    criticality         PUA-ELEMENTARY-PROCEDURE.&criticality        ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value               PUA-ELEMENTARY-PROCEDURE.&InitiatingMessage  ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+SuccessfulOutcome ::= SEQUENCE {
+    procedureCode     PUA-ELEMENTARY-PROCEDURE.&procedureCode      ({PUA-ELEMENTARY-PROCEDURES}),
+    criticality         PUA-ELEMENTARY-PROCEDURE.&criticality        ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value               PUA-ELEMENTARY-PROCEDURE.&SuccessfulOutcome  ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+UnsuccessfulOutcome ::= SEQUENCE {
+    procedureCode     PUA-ELEMENTARY-PROCEDURE.&procedureCode      ({PUA-ELEMENTARY-PROCEDURES}),
+    criticality         PUA-ELEMENTARY-PROCEDURE.&criticality        ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value               PUA-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome  ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+-- *****
+--
+-- Interface Elementary Procedure List
+--
+-- *****
+
+PUA-ELEMENTARY-PROCEDURES PUA-ELEMENTARY-PROCEDURE ::= {
+    PUA-ELEMENTARY-PROCEDURES-CLASS-1 |
+    PUA-ELEMENTARY-PROCEDURES-CLASS-2 ,
+    ...
+}
+
+PUA-ELEMENTARY-PROCEDURES-CLASS-1 PUA-ELEMENTARY-PROCEDURE ::= {
+    ...
+}
+
+PUA-ELEMENTARY-PROCEDURES-CLASS-2 PUA-ELEMENTARY-PROCEDURE ::= {
+    connectionRequest |
+    directTransfer |
+    disconnectRequest |
+    connectionlessTransfer |
+    errorIndication |
+    privateMessage,
+    ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- Interface Elementary Procedures
+--
+-- *****
+
+connectionRequest PUA-ELEMENTARY-PROCEDURE ::= {
+  INITIATING MESSAGE      Connect
+  PROCEDURE CODE          id-Connect
+  CRITICALITY             ignore
+}
+
+directTransfer PUA-ELEMENTARY-PROCEDURE ::= {
+  INITIATING MESSAGE      DirectTransfer
+  PROCEDURE CODE          id-DirectTransfer
+  CRITICALITY             ignore
+}
+
+disconnectRequest PUA-ELEMENTARY-PROCEDURE ::= {
+  INITIATING MESSAGE      Disconnect
+  PROCEDURE CODE          id-Disconnect
+  CRITICALITY             ignore
+}
+
+connectionlessTransfer PUA-ELEMENTARY-PROCEDURE ::= {
+  INITIATING MESSAGE      ConnectionlessTransfer
+  PROCEDURE CODE          id-ConnectionlessTransfer
+  CRITICALITY             ignore
+}
+
+errorIndication PUA-ELEMENTARY-PROCEDURE ::= {
+  INITIATING MESSAGE      ErrorIndication
+  PROCEDURE CODE          id-ErrorIndication
+  CRITICALITY             ignore
+}
+
+privateMessage PUA-ELEMENTARY-PROCEDURE ::= {
+  INITIATING MESSAGE      PrivateMessage
+  PROCEDURE CODE          id-privateMessage
+  CRITICALITY             ignore
+}
+
+END
+
+```
+
+### 9.3.3 PDU definitions
+
+```
+
+-- *****
+--
+-- PDU definitions for PUA.
+--
+-- *****
+
+PUA-PDU-Contents {
+
+```
+
+```
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+umts-Access (20) modules (3) pua(7) version1 (1) pUA-PDU-Contents (1) }
+```
+
+```
+DEFINITIONS AUTOMATIC TAGS ::=
+```
+
+```
+BEGIN
+```
+
+```
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+```
+
+```
+IMPORTS
+```
+
+```
+    Cause,
+    CriticalityDiagnostics,
+    PCAP-Context-ID,
+    PCAP-Message,
+    SAS-Indicator,
+    TransactionID
+```
+
+```
+FROM PUA-IEs
+```
+
+```
+    ProtocolExtensionContainer{},
+    ProtocolIE-ContainerList{},
+    ProtocolIE-Container{},
+    ProtocolIE-Single-Container{},
+    PrivateIE-Container{},
+    PUA-PRIVATE-IES,
+    PUA-PROTOCOL-EXTENSION,
+    PUA-PROTOCOL-IES
+```
+
+```
+FROM PUA-Containers
+```
+
+```
+    id-Cause,
+    id-CriticalityDiagnostics,
+    id-PCAP-Context-ID,
+    id-PCAP-Message,
+    id-SAS-Indicator,
+    id-TransactionID
+```
+
+```
+FROM PUA-Constants;
+```
+
+```
+-- *****
+--
+-- Connect
+--
+-- *****
+```
+
+```
+Connect ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container { {ConnectIEs} },
+    protocolExtensions ProtocolExtensionContainer { {ConnectExtensions} } OPTIONAL,
+    ...
+}
+```
+
+```
+
+ConnectIEs PUA-PROTOCOL-IES ::= {
+  { ID id-PCAP-Context-ID          CRITICALITY reject  TYPE PCAP-Context-ID          PRESENCE mandatory } |
+  { ID id-PCAP-Message             CRITICALITY reject  TYPE PCAP-Message             PRESENCE mandatory } |
+  { ID id-SAS-Indicator            CRITICALITY ignore  TYPE SAS-Indicator            PRESENCE optional },
+  ...
+}
+
+ConnectExtensions PUA-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- *****
+--
+-- Direct Transfer
+--
+-- *****
+
+DirectTransfer ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { {DirectTransferIEs} },
+  protocolExtensions ProtocolExtensionContainer { {DirectTransferExtensions} }  OPTIONAL,
+  ...
+}
+
+DirectTransferIEs PUA-PROTOCOL-IES ::= {
+  { ID id-PCAP-Context-ID          CRITICALITY reject  TYPE PCAP-Context-ID          PRESENCE mandatory } |
+  { ID id-PCAP-Message             CRITICALITY reject  TYPE PCAP-Message             PRESENCE mandatory },
+  ...
+}
+
+DirectTransferExtensions PUA-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- *****
+--
+-- Disconnect
+--
+-- *****
+
+Disconnect ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { {DisconnectIEs} },
+  protocolExtensions ProtocolExtensionContainer { {DisconnectExtensions} }  OPTIONAL,
+  ...
+}
+
+DisconnectIEs PUA-PROTOCOL-IES ::= {
+  { ID id-PCAP-Context-ID          CRITICALITY reject  TYPE PCAP-Context-ID          PRESENCE mandatory } |
+  { ID id-Cause                      CRITICALITY reject  TYPE Cause                      PRESENCE mandatory } |
+  { ID id-PCAP-Message             CRITICALITY reject  TYPE PCAP-Message             PRESENCE optional },
+  ...
+}
+
+DisconnectExtensions PUA-PROTOCOL-EXTENSION ::= {
+
+```
+
+```
+
+    ...
+  }
+
+  -- *****
+  --
+  -- Connectionless Transfer
+  --
+  -- *****
+
+  ConnectionlessTransfer := SEQUENCE {
+    protocolIEs      ProtocolIE-Container      { {ConnectionlessTransferIEs} },
+    protocolExtensions ProtocolExtensionContainer { {ConnectionlessTransferExtensions} } OPTIONAL,
+    ...
+  }
+
+  ConnectionlessTransferIEs PUA-PROTOCOL-IES := {
+    { ID id-PCAP-Message      CRITICALITY reject  TYPE PCAP-Message      PRESENCE mandatory } |
+    { ID id-SAS-Indicator      CRITICALITY ignore  TYPE SAS-Indicator      PRESENCE optional },
+    ...
+  }
+
+  ConnectionlessTransferExtensions PUA-PROTOCOL-EXTENSION := {
+    ...
+  }
+
+  -- *****
+  --
+  -- ERROR INDICATION
+  --
+  -- *****
+
+  ErrorIndication := SEQUENCE {
+    protocolIEs      ProtocolIE-Container      { {ErrorIndicationIEs} },
+    protocolExtensions ProtocolExtensionContainer { {ErrorIndicationExtensions} } OPTIONAL,
+    ...
+  }
+
+  ErrorIndicationIEs PUA-PROTOCOL-IES := {
+    { ID id-Cause      CRITICALITY ignore  TYPE Cause      PRESENCE mandatory } |
+    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics      PRESENCE optional } |
+    { ID id-PCAP-Context-ID      CRITICALITY ignore  TYPE PCAP-Context-ID      PRESENCE optional } |
+    { ID id-TransactionID      CRITICALITY ignore  TYPE TransactionID      PRESENCE optional },
+    ...
+  }
+
+  ErrorIndicationExtensions PUA-PROTOCOL-EXTENSION := {
+    ...
+  }
+
+  -- *****
+  --
+  -- PRIVATE MESSAGE
+  --
+  -- *****
+
+```
+
+```
+PrivateMessage ::= SEQUENCE {
+    privateIEs      PrivateIE-Container {{PrivateMessage-IEs}},
+    ...
+}
+```
+
+```
+PrivateMessage-IEs PUA-PRIVATE-IES ::= {
+    ...
+}
+```
+
+END
+
+### 9.3.4 Information Element definitions
+
+```
+-- **************************************************************
+--
+-- Information Element Definitions
+--
+-- **************************************************************
+```
+
+```
+PUA-IEs {
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+umts-Access (20) modules (3) pua(7) version1 (1) pUA-IEs (2) }
+```
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+IMPORTS
+
+```
+    maxNrOfErrors
+FROM PUA-Constants
+```
+
+```
+    Criticality,
+    ProcedureCode,
+    ProtocolIE-ID,
+    TriggeringMessage
+FROM PUA-CommonDataTypes
+```
+
+```
+    ProtocolExtensionContainer{},
+    PUA-PROTOCOL-EXTENSION
+FROM PUA-Containers;
+```
+
+```
+PCAP-Context-ID ::= BIT STRING (SIZE(24))
+```
+
+```
+PCAP-Message ::=            OCTET STRING
+```
+
+```
+SAS-Indicator ::=           INTEGER(0..255)
+```
+
+```
+TransactionID           ::= BIT STRING (SIZE(16))
+```
+
+```
+-- *****
+--
+-- Cause IE
+--
+-- *****
+
+Cause ::= CHOICE {
+    radioNetwork      CauseRadioNetwork,
+    transport         CauseTransport,
+    protocol          CauseProtocol,
+    misc              CauseMisc,
+    ...
+}
+CauseRadioNetwork ::= ENUMERATED {
+    normal,
+    connect-failed,
+    hnb-gw-release,
+    sas-release,
+    unspecified,
+    ...
+}
+CauseTransport ::= ENUMERATED {
+    transport-resource-unavailable,
+    unspecified,
+    ...
+}
+
+CauseProtocol ::= ENUMERATED {
+    transfer-syntax-error,
+    abstract-syntax-error-reject,
+    abstract-syntax-error-ignore-and-notify,
+    message-not-compatible-with-receiver-state,
+    semantic-error,
+    unspecified,
+    abstract-syntax-error-falsely-constructed-message,
+    ...
+}
+
+CauseMisc ::= ENUMERATED {
+    processing-overload,
+    hardware-failure,
+    o-and-m-intervention,
+    sas-unavailable,
+    sas-not-configured,
+    unspecified,
+    ...
+}
+
+-- *****
+--
+-- CriticalityDiagnostics
+--
+-- *****
+```
+
+```
+
+CriticalityDiagnostics ::= SEQUENCE {
+    procedureCode           ProcedureCode                                   OPTIONAL,
+    triggeringMessage       TriggeringMessage                               OPTIONAL,
+    procedureCriticality    Criticality                                     OPTIONAL,
+    iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List                OPTIONAL,
+    iE-Extensions           ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL,
+    ...
+}
+
+CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF
+    SEQUENCE {
+        iECriticality           Criticality,
+        iE-ID                   ProtocolIE-ID,
+        typeOfError             TypeOfError,
+        iE-Extensions           ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL,
+        ...
+    }
+
+CriticalityDiagnostics-IE-List-ExtIEs PUA-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+CriticalityDiagnostics-ExtIEs PUA-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+TypeOfError ::= ENUMERATED {
+    not-understood,
+    missing,
+    ...
+}
+
+END
+
+```
+
+### 9.3.5 Common definitions
+
+```
+
+-- **************************************************************
+--
+-- Common definitions
+--
+-- **************************************************************
+
+PUA-CommonDataTypes {
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+umts-Access (20) modules (3) pua(7) version1 (1) pUA-CommonDataTypes (3) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- **************************************************************
+
+```
+
+```
+
+--
+-- Extension constants
+--
+-- *****
+
+maxPrivateIEs                INTEGER := 65535
+maxProtocolExtensions          INTEGER := 65535
+maxProtocolIEs               INTEGER := 65535
+
+-- *****
+--
+-- Common Data Types
+--
+-- *****
+Criticality      := ENUMERATED { reject, ignore, notify }
+
+Presence         := ENUMERATED { optional, conditional, mandatory }
+
+ProcedureCode    := INTEGER (0..255)
+
+PrivateIE-ID     := CHOICE {
+    local          INTEGER (0..65535),
+    global         OBJECT IDENTIFIER
+}
+
+ProtocolIE-ID    := INTEGER (0..maxProtocolIEs)
+
+TriggeringMessage := ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome }
+
+END
+
+```
+
+### 9.3.6 Constant definitions
+
+```
+
+-- *****
+--
+-- Constant definitions
+--
+-- *****
+
+PUA-Constants {
+    itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+    umts-Access (20) modules (3) pua(7) version1 (1) pUA-Constants (4) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+IMPORTS
+    ProcedureCode,
+    ProtocolIE-ID
+FROM PUA-CommonDataTypes;
+
+```
+
+```
+
+-- *****
+--
+-- Elementary Procedures
+--
+-- *****
+
+id-Connect                ProcedureCode ::= 1
+id-DirectTransfer         ProcedureCode ::= 2
+id-Disconnect             ProcedureCode ::= 3
+id-ConnectionlessTransfer ProcedureCode ::= 4
+id-ErrorIndication        ProcedureCode ::= 5
+id-privateMessage         ProcedureCode ::= 6
+
+-- *****
+--
+-- Lists
+--
+-- *****
+
+maxNrOfErrors             INTEGER ::= 256
+
+-- *****
+--
+-- IEs
+--
+-- *****
+
+id-Cause                  ProtocolIE-ID ::= 1
+id-CriticalityDiagnostics ProtocolIE-ID ::= 2
+id-PCAP-Context-ID        ProtocolIE-ID ::= 3
+id-PCAP-Message           ProtocolIE-ID ::= 4
+id-SAS-Indicator          ProtocolIE-ID ::= 5
+id-TransactionID          ProtocolIE-ID ::= 6
+
+END
+
+```
+
+### 9.3.7 Container definitions
+
+```
+
+-- *****
+--
+-- Container definitions
+--
+-- *****
+
+PUA-Containers {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  umts-Access (20) modules (3) pua(7) version1 (1) pUA-Containers (5) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+```
+
+BEGIN
+
+```
+-- *****  
+--  
+-- IE parameter types from other modules.  
+--  
+-- *****
+```
+
+IMPORTS
+
+```
+    Criticality,  
+    Presence,  
+    PrivateIE-ID,  
+    ProtocolIE-ID,  
+    maxPrivateIEs,  
+    maxProtocolExtensions,  
+    maxProtocolIEs
+```
+
+FROM PUA-CommonDataTypes;
+
+```
+-- *****  
+--  
+-- Class Definition for Private IEs  
+--  
+-- *****
+```
+
+PUA-PRIVATE-IEs ::= CLASS {
+
+```
+    &id           PrivateIE-ID,  
+    &criticality  Criticality,  
+    &Value,  
+    &presence     Presence
+```
+
+}
+
+WITH SYNTAX {
+
+```
+    ID            &id  
+    CRITICALITY   &criticality  
+    TYPE          &Value  
+    PRESENCE      &presence
+```
+
+}
+
+```
+-- *****  
+--  
+-- Class Definition for Protocol IEs  
+--  
+-- *****
+```
+
+PUA-PROTOCOL-IEs ::= CLASS {
+
+```
+    &id           ProtocolIE-ID      UNIQUE,  
+    &criticality  Criticality,  
+    &Value,  
+    &presence     Presence
+```
+
+}
+
+WITH SYNTAX {
+
+```
+    ID            &id  
+    CRITICALITY   &criticality  
+    TYPE          &Value  
+    PRESENCE      &presence
+```
+
+}
+
+```
+-- *****
+--
+-- Class Definition for Protocol Extensions
+--
+-- *****
+
+PUA-PROTOCOL-EXTENSION ::= CLASS {
+    &id               ProtocolIE-ID UNIQUE,
+    &criticality        Criticality,
+    &Extension,
+    &presence           Presence
+}
+WITH SYNTAX {
+    ID                &id
+    CRITICALITY       &criticality
+    EXTENSION         &Extension
+    PRESENCE          &presence
+}
+
+-- *****
+--
+-- Container for Protocol IEs
+--
+-- *****
+
+ProtocolIE-Container {PUA-PROTOCOL-IES : IEsSetParam} ::=
+    SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+        ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-Single-Container {PUA-PROTOCOL-IES : IEsSetParam} ::=
+    ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-Field {PUA-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {
+    id                PUA-PROTOCOL-IES.&id                {{IEsSetParam}},
+    criticality       PUA-PROTOCOL-IES.&criticality        {{IEsSetParam}{@id}},
+    value             PUA-PROTOCOL-IES.&Value              {{IEsSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container Lists for Protocol IE Containers
+--
+-- *****
+
+ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, PUA-PROTOCOL-IES : IEsSetParam} ::=
+    SEQUENCE (SIZE (lowerBound..upperBound)) OF
+        ProtocolIE-Container {{IEsSetParam}}
+
+-- *****
+--
+-- Container for Protocol Extensions
+--
+-- *****
+```
+
+```
+ProtocolExtensionContainer {PUA-PROTOCOL-EXTENSION : ExtensionSetParam} ::=
+  SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
+    ProtocolExtensionField {{ExtensionSetParam}}
+
+ProtocolExtensionField {PUA-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {
+  id                PUA-PROTOCOL-EXTENSION.&id                {{ExtensionSetParam}},
+  criticality       PUA-PROTOCOL-EXTENSION.&criticality        {{ExtensionSetParam}{@id}},
+  extensionValue    PUA-PROTOCOL-EXTENSION.&Extension          {{ExtensionSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container for Private IEs
+--
+-- *****
+
+PrivateIE-Container {PUA-PRIVATE-IES : IEsSetParam } ::=
+  SEQUENCE (SIZE (1.. maxPrivateIEs)) OF
+    PrivateIE-Field {{IEsSetParam}}
+
+PrivateIE-Field {PUA-PRIVATE-IES : IEsSetParam} ::= SEQUENCE {
+  id                PUA-PRIVATE-IES.&id                {{IEsSetParam}},
+  criticality       PUA-PRIVATE-IES.&criticality        {{IEsSetParam}{@id}},
+  value             PUA-PRIVATE-IES.&Value               {{IEsSetParam}{@id}}
+}
+
+END
+```
+
+## 9.4 Message transfer syntax
+
+PUA shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU-T Rec. X.691 [6].
+
+# 10 Handling of unknown, unforeseen, and erroneous protocol data
+
+## 10.1 General
+
+Protocol Error cases can be divided into three classes:
+
+- Transfer Syntax Error;
+- Abstract Syntax Error;
+- Logical Error.
+
+Protocol errors can occur in the following functions within a receiving node:
+
+![Diagram illustrating protocol errors in PUA. It shows two boxes: 'PUA functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. Brackets on the right side of the boxes group the errors: 'Logical Errors' and 'Abstract Syntax Errors' are associated with the PUA functional entity, while 'Transfer Syntax Errors' are associated with ASN.1 Decoding. A large upward arrow on the far right indicates the flow of error reporting.](446100c084b94817a19c319fa776b412_img.jpg)
+
+The diagram shows two functional blocks in a receiving node. The top block is the 'PUA functional entity' and the bottom block is 'ASN.1 Decoding', connected by a double-headed arrow indicating bidirectional interaction. To the right of the 'PUA functional entity' block, a bracket groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the 'ASN.1 Decoding' block, a bracket groups 'Transfer Syntax Errors'. A large vertical arrow on the far right points upwards, indicating the overall flow or hierarchy of error handling.
+
+Diagram illustrating protocol errors in PUA. It shows two boxes: 'PUA functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. Brackets on the right side of the boxes group the errors: 'Logical Errors' and 'Abstract Syntax Errors' are associated with the PUA functional entity, while 'Transfer Syntax Errors' are associated with ASN.1 Decoding. A large upward arrow on the far right indicates the flow of error reporting.
+
+**Figure 10.1-1: Protocol errors in PUA**
+
+The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1.
+
+## 10.2 Transfer Syntax Error
+
+A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error.
+
+## 10.3 Abstract Syntax Error
+
+### 10.3.1 General
+
+An Abstract Syntax Error occurs when the receiving functional PUA entity:
+
+1. receives IEs or IE groups that cannot be understood (unknown IE id);
+2. receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message);
+3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message;
+4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group;
+
+5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message.
+
+Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure.
+
+If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6.
+
+### 10.3.2 Criticality Information
+
+In the PUA messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4.
+
+In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5).
+
+The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are:
+
+- Reject IE;
+- Ignore IE and Notify Sender;
+- Ignore IE.
+
+The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable:
+
+1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by the receiving entity (some may still remain unsupported).
+2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied.
+
+### 10.3.3 Presence Information
+
+For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, PUA specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerning object of class PUA-PROTOCOL-IES, PUA-PROTOCOL-IES-PAIR, PUA-PROTOCOL-EXTENSION or PUA-PRIVATE-IES.
+
+The presence field of the indicated classes supports three values:
+
+1. Optional;
+2. Conditional;
+3. Mandatory.
+
+If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group.
+
+### 10.3.4 Not comprehended IE/IE group
+
+#### 10.3.4.1 Procedure Code
+
+The receiving node shall treat the different types of received criticality information of the *Procedure Code* according to the following:
+
+Reject IE:
+
+- If a message is received with a *Procedure Code* marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure.
+
+Ignore IE and Notify Sender:
+
+- If a message is received with a *Procedure Code* marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure.
+
+Ignore IE:
+
+- If a message is received with a *Procedure Code* marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure.
+
+When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE.
+
+#### 10.3.4.1A Type of Message
+
+When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value.
+
+#### 10.3.4.2 IEs other than the Procedure Code and Type of Message
+
+The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following:
+
+Reject IE:
+
+- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure.
+- If a *response* message is received containing one or more IEs marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
+
+##### Ignore IE and Notify Sender:
+
+- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored.
+- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IE/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure.
+
+##### Ignore IE:
+
+- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using only the understood IEs/IE groups.
+- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.
+
+When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group.
+
+When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group.
+
+### 10.3.5 Missing IE or IE group
+
+The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of the present document used by the receiver:
+
+#### Reject IE:
+
+- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- if a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall terminate the procedure and initiate the Error Indication procedure.
+- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
+
+#### Ignore IE and Notify Sender:
+
+- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.
+- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.
+
+#### Ignore IE:
+
+- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message.
+- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message.
+
+When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group.
+
+When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group.
+
+### 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present
+
+If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following:
+
+- If a message *initiating* a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
+- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)".
+- If a *response* message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
+
+When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered.
+
+## 10.4 Logical Error
+
+Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IE's/IE groups containing the erroneous values.
+
+### Class 1:
+
+Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are:
+
+- Semantic Error;
+- Message not compatible with receiver state.
+
+Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error.
+
+Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated.
+
+### Class 2:
+
+Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error.
+
+## 10.5 Exceptions
+
+The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10.
+
+- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling.
+- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated.
+- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure.

marked/Rel-18/25_series/25484/raw.md

@@ -0,0 +1,704 @@
+
+
+# 3GPP TS 25.484 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Automatic Neighbour Relation (ANR) for UTRAN; Stage 2 (Release 18)**
+
+![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G ADVANCED logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                              |           |
+|------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                               | 4         |
+| 1 Scope.....                                                                 | 5         |
+| 2 References.....                                                            | 5         |
+| 3 Definitions, symbols and abbreviations .....                               | 5         |
+| 3.1 Definitions.....                                                         | 5         |
+| 3.2 Symbols.....                                                             | 6         |
+| 3.3 Abbreviations .....                                                      | 7         |
+| 4 Automatic Neighbour Relation Function, Main Concepts.....                  | 7         |
+| 4.1 General .....                                                            | 7         |
+| 4.2 ANR Handling in the UTRAN Infrastructure - Overall Description.....      | 8         |
+| 4.2.1 Iur Connectivity exists between the involved RNCs.....                 | 8         |
+| 4.2.1.1 ANR Report over Uu for UTRAN cells .....                             | 8         |
+| 4.2.1.2 ANR Report over Iur for UTRAN cells.....                             | 9         |
+| 4.2.1.3 ANR Report over Iur for IRAT cells .....                             | 11        |
+| 4.2.2 Iur Connectivity does not exist between some RNCs involved in ANR..... | 12        |
+| 4.2.2.1 ANR report over Uu for UTRAN cells.....                              | 12        |
+| 4.2.3 ANR Report over Uu for IRAT cells - with and without Iur .....         | 13        |
+| 5 Functions and Procedures .....                                             | 14        |
+| 5.1 ANR Management.....                                                      | 15        |
+| 5.1.1 ANR Report Forwarding .....                                            | 15        |
+| 5.1.2 ANR Report Distribution Controlling .....                              | 15        |
+| 5.2 Neighbour Cell Configuration.....                                        | 16        |
+| 5.2.1 Neighbour Cell Configuration for Intra-RNS cells .....                 | 16        |
+| 5.2.2 Neighbour Cell Configuration for Inter-RNS cells (with Iur).....       | 16        |
+| 5.2.3 Neighbour Cell Configuration (without Iur) .....                       | 16        |
+| 5.3 ANR Logging configuration .....                                          | 16        |
+| 5.3.1 Configuration parameters .....                                         | 17        |
+| 5.3.2 Configuration validity .....                                           | 17        |
+| 5.4 Measurement Collection .....                                             | 18        |
+| 5.5 Measurement Reporting .....                                              | 18        |
+| 5.6 UE Capabilities .....                                                    | 19        |
+| <b>Annex A (informative): Change history.....</b>                            | <b>20</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the 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.
+
+# --- 1 Scope
+
+The present document is a technical specification of the overall support of Automatic Neighbour Relation (ANR) Function in UTRA.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Base UTRAN Cell:** A cell in UTRAN for which a missing neighbour cell is detected.
+
+**Neighbour Cell:** A cell in UTRAN, LTE or GSM/GERAN that is a neighbour cell to a Base UTRAN Cell.
+
+**Neighbour Cell Identifier (NCI):** The identifier of a Neighbour Cell
+
+**Neighbour cell Relation (NR):** Information that a Neighbour Cell, identified with NCI, is a neighbour to a Base UTRAN Cell. NR is stored in the RNC controlling the Base UTRAN Cell.
+
+**Conceptual Neighbour Relation Functions:** The ANR is described using a number of conceptual entities and functions in the RNC: Neighbour Relation Table, Neighbour Relation Table Management Function, Neighbour Removal Function and Neighbour Detection Function. These entities and functions are used for descriptive purpose only and shall not be regarded as requirements on the implementation in RNC.
+
+**Receiving RNC:** the RNC receiving the ANR report over Uu
+
+**Base RNC:** the CRNC of the Base UTRAN Cell
+
+**Neighbour RNC:** the CRNC of the Neighbour Cell in UTRAN
+
+**ANR-PLMN List:** A list of PLMNs that is the RPLMN and the list of equivalent PLMNs for the UE at the point of receiving ANR logging configuration.
+
+**ANR measurement:** Physical measurements and reading of System Information towards detected cells outside NCL.
+
+**ANR logging:** Storing of essential information of detected cell into UE internal ANR log, when one or more detected cell satisfies ANR logging criteria.
+
+## 3.2 Symbols
+
+Void
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply.
+
+# 4 Automatic Neighbour Relation Function, Main Concepts
+
+## 4.1 General
+
+![Diagram showing the interaction between RNC and O&M due to ANR. The RNC contains an ANR function with NRT Management, Neighbour Detection, and Neighbour Removal functions, which interact with a Neighbor Relation Table and the RRC. The O&M interacts with the NRT Management function via NR reports and Add/Update Neighbor Relations messages.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg)
+
+The diagram illustrates the interaction between the RNC and O&M for ANR. The RNC contains an ANR function block with three main components: NRT Management Function, Neighbour Removal Function, and Neighbour Detection Function. The NRT Management Function interacts with the Neighbor Relation Table (NRT) and the O&M. The Neighbour Detection Function receives Cell Information from the RRC and sends NR\_add messages to the NRT Management Function. The Neighbour Removal Function receives Internal information and sends NR\_remove messages to the NRT Management Function. The NRT Management Function sends NR\_update messages to the Neighbor Relation Table and NR reports to the O&M. The O&M sends Add/Update Neighbor Relations messages to the NRT Management Function. The Neighbor Relation Table is a table with columns for NR, NCI, No Remove, and No HO. The RRC is shown as an oval at the bottom of the RNC block.
+
+| Neighbor Relation |       | O&M controlled Neighbour Relation Attributes |       |
+|-------------------|-------|----------------------------------------------|-------|
+| NR                | NCI   | No Remove                                    | No HO |
+| 1                 | NCI#1 |                                              |       |
+| 2                 | NCI#1 | ✓                                            |       |
+| 3                 | NCI#1 |                                              | ✓     |
+|                   |       |                                              |       |
+
+Diagram showing the interaction between RNC and O&M due to ANR. The RNC contains an ANR function with NRT Management, Neighbour Detection, and Neighbour Removal functions, which interact with a Neighbor Relation Table and the RRC. The O&M interacts with the NRT Management function via NR reports and Add/Update Neighbor Relations messages.
+
+Figure 4.1-1: Interaction between RNC and O&M due to ANR
+
+The ANR function resides in the RNC and is composed of the Neighbour Relation Table (NRT) Management Function, Neighbour Detection Function and Neighbour Removal Function.
+
+The Neighbour Detection Function detects new neighbours and adds them to the NRT. The Neighbour Removal Function removes outdated NRs.
+
+A Neighbour cell Relation (NR) between a Base UTRAN Cell and a Neighbour Cell exists if the RNC controlling the Base UTRAN Cell:
+
+- a) Knows the following Neighbour Cell information:
+  - Neighbour cell is in UTRAN: PLMN-Id, Cell Identifier(C-ID), RNC-ID/Extended RNC-ID,
+  - Neighbour cell is in LTE: ECGI (PLMN Id + Cell Identity)
+  - Neighbour cell is in GSM/GERAN: PLMN Id, LAC, CI, BSIC
+- b) Has an entry in the Neighbour Relation Table for the Base UTRAN Cell identifying the neighbour cell.
+- c) Has all required attributes defined in the Neighbour Relation Table entry or set to default values. Among these attributes are the frequency information (UARFCN, BCCH ARFCN, EARFCN) and handover routing parameters not already considered in (a):
+  - Neighbour cell is in UTRAN: LAC and RAC
+  - Neighbour cell is in LTE: TAI
+
+For each NR, the NRT contains the Neighbour Cell Identifier (NCI), which identifies the neighbour cells. A neighbour cell may be a UTRAN, LTE or GSM cell. Furthermore, each NR has two attributes, the No Remove and the No HO attributes. These attributes have the following definitions:
+
+- No Remove: If checked, the RNC shall not remove the Neighbour cell Relation from the NRT.
+- No HO: If checked, the Neighbour cell Relation shall not be used as a neighbour cell by Intra RNS, Inter RNS or Inter RAT mobility functions in UTRAN.
+
+The ANR function also allows O&M to manage the NRT. O&M can add and delete NRs. It can also change the attributes of the NR. The O&M system is informed about changes in the NRT.
+
+## 4.2 ANR Handling in the UTRAN Infrastructure - Overall Description
+
+If UTRAN ANR functionality is supported in UTRAN, RNC shall be able to configure the UE to perform the ANR measurement. ANR capable UE performs the ANR measurement and records in its logbook newly detected cells which meet the criteria given in the configuration. The Receiving RNC uses RRC signalling to retrieve the ANR report over the Uu interface after the UE has indicated that it has a logged ANR report. The Receiving RNC handles the ANR report and may forward the ANR report to different RNCs.
+
+This chapter illustrates the handling and message sequences to be used to configure a new neighbour relation for a UTRAN cell.
+
+### 4.2.1 Iur Connectivity exists between the involved RNCs
+
+The ANR function supports forwarding of ANR reports from the Receiving RNC to RNCs indicated as Base RNCs in the ANR report. Furthermore the ANR function supports suspension (and resuming) ANR logs reporting over Iur from other RNCs as described in 5.1.2. This chapter describes the handling in the Receiving, Base and Neighbour RNCs when Iur connectivity exists between the involved RNCs.
+
+#### 4.2.1.1 ANR Report over Uu for UTRAN cells
+
+When receiving an ANR report over Uu, the Receiving RNC uses the globally unique cell identities in the report to determine the network addresses of the RNCs that are controlling the Base UTRAN cells. The network address of this Base RNC is retrieved using configuration in the Receiving RNC and/or O&M.
+
+The Receiving RNC decides the necessity to forward the ANR report. If the Base UTRAN Cell is under control of the Receiving RNC, the Receiving RNC terminates the relevant ANR report entry, and may update the Neighbouring Relation accordingly. Otherwise, the ANR report is forwarded to the Base RNCs over Iur with the RNSAP Direct Information Transfer procedure.
+
+If newly detected neighbour cells are controlled by another RNC the RNSAP Information Exchange Initiation procedure is used to request cell information from the neighbour RNC. In addition the Base RNC may interact with O&M before a neighbour relation is stored in the NRT.
+
+![Sequence diagram for ANR Report over Uu for UTRAN cells. The diagram shows interactions between UE, RNC1 (Receiving RNC - Base RNC), RNC2 (Base RNC), RNC3 (Base RNC), and O&M. RNC1 sends an ANR report request to the UE. The UE responds with an ANR report containing a list of neighbour cells. RNC1 then uses the RNSAP Direct Information Transfer procedure to send the ANR report to RNC2 and RNC3. RNC1 then uses the RNSAP Information Exchange Initiation procedure to request cell information from RNC2. RNC2 responds with cell attributes. RNC1 then performs neighbour handling, which may involve interaction with O&M. Finally, RNC1 stores the UTRAN neighbour cells in the NRT.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant RNC1 as RNC1  
+(Role:  
+- Receiving RNC  
+- Base RNC)
+    participant RNC2 as RNC2  
+(Role:  
+- Base RNC)
+    participant RNC3 as RNC3  
+(Role:  
+- Base RNC)
+    participant OM as O&M
+
+    Note right of RNC1: Role receiving RNC:  
+Use RRC Cell-ID of the listed cells to retrieve addresses of  
+Base RNCs that shall have the ANR report (from configuration  
+in RNC /O&M).  
+RNC2 and RNC3 are receivers of ANR report.
+
+    Note right of RNC1: Role Base RNC:  
+RNC1 retrieves its potential neighbours:  
+Cell information is needed for potential neighbours in RNC2  
+Address of RNC2 are retrieved based on Cell-ID
+
+    Note right of RNC1: Store UTRAN neighbour cells C-ID n in NRT after  
+interaction with O&M. Store the cell attributes  
+received over lur and other cell configuration  
+parameters (from configuration or O&M).
+
+    RNC1->>UE: ANR report request
+    UE-->>RNC1: UE ANR Report  
+(list NR:  
+- Cell-ID a -> Cell-ID b,  
+- Cell-ID c->Cell-ID-d  
+- Cell-ID e->Cell-ID f...)
+    RNC1->>RNC2: RNSAP: DIRECT INFORMATION  
+TRANSFER  
+(ANR report: transparent to RNSAP)
+    RNC1->>RNC3: RNSAP: DIRECT INFORMATION TRANSFER  
+(ANR report: transparent to RNSAP)
+    RNC1->>RNC2: RNSAP: INFORMATION EXCHANGE  
+INITIATION REQUEST  
+(List: C-ID n, type=on demand)
+    RNC2-->>RNC1: RNSAP: INFORMATION EXCHANGE  
+INITIATION RESPONSE  
+(List: cell attributes)
+    RNC1->>RNC2: Neighbour handling: RNC1(C-ID m)-> RNC2(C-ID n), [implementation dependent]
+    RNC1->>OM: 
+    OM-->>RNC1: 
+  
+```
+
+Sequence diagram for ANR Report over Uu for UTRAN cells. The diagram shows interactions between UE, RNC1 (Receiving RNC - Base RNC), RNC2 (Base RNC), RNC3 (Base RNC), and O&M. RNC1 sends an ANR report request to the UE. The UE responds with an ANR report containing a list of neighbour cells. RNC1 then uses the RNSAP Direct Information Transfer procedure to send the ANR report to RNC2 and RNC3. RNC1 then uses the RNSAP Information Exchange Initiation procedure to request cell information from RNC2. RNC2 responds with cell attributes. RNC1 then performs neighbour handling, which may involve interaction with O&M. Finally, RNC1 stores the UTRAN neighbour cells in the NRT.
+
+Figure 4.2.1.1-1 ANR Report over Uu for UTRAN cells
+
+#### 4.2.1.2 ANR Report over lur for UTRAN cells
+
+On reception of an ANR report from another RNC using the RNSAP Direct Information Transfer procedure, the Base RNC uses the globally unique cell identities and L1 information in the ANR report, and optionally also configuration in the RNC/O&M, to determine if the ANR report contains any potential neighbour cells. If any of these potential neighbour cells is controlled by another RNC the RNSAP Information Exchange Initiation procedure may be used to request cell information from the neighbour RNC. In addition the Base RNC may interact with O&M before a neighbour relation is be stored in the NRT as shown in the figure below:
+
+![Sequence diagram showing ANR report over lur for UTRAN cells. Lifelines: RNC1 (Receiving RNC), RNC2 (Base RNC), RNC3 (Neighbour RNC), and O&M. The process involves an ANR report from RNC1 to RNC2, internal processing in RNC2, an information exchange initiation between RNC2 and RNC3, neighbour handling, and final storage in RNC2.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+Intra UMTS, Inter RNS, ANR report over lur
+
+```
+
+sequenceDiagram
+    participant RNC1 as RNC1  
+(Role:  
+- Receiving RNC)
+    participant RNC2 as RNC2  
+(Role:  
+- Base RNC)
+    participant RNC3 as RNC3  
+(Role:  
+- Neighbour RNC)
+    participant OM as O&M
+
+    Note left of RNC1: RNSAP: DIRECT INFORMATION TRANSFER,  
+ANR report transparent:  
+(list NR:  
+- Cell-ID a -> Cell-ID b,  
+- Cell-ID c->Cell-ID d,  
+- Cell-ID e->Cell-ID f,...)
+    RNC1->>RNC2: RNSAP: DIRECT INFORMATION TRANSFER, ANR report transparent
+    Note right of RNC2: Role Base RNC:  
+RNC2 retrieves its potential neighbours:  
+Cell information is needed for potential neighbours in RNC3  
+Address of RNC3 is retrieved based on Cell-ID in ANR report
+    RNC2->>RNC3: RNSAP: INFORMATION EXCHANGE INITIATION REQUEST  
+(List: C-ID n, type=on demand)
+    RNC3-->>RNC2: RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE  
+(List: cell attributes)
+    Note right of RNC2: Neighbour handling: RNC2 (C-ID m)-> RNC3 (C-ID n)  
+[implementation dependent]
+    RNC2->>OM: 
+    Note right of RNC2: Store UTRAN neighbour cells (C-ID n) in NRT after  
+interaction with O&M. Store the cell attributes received  
+over lur and other cell configuration parameters (from  
+configuration and/or O&M).
+  
+```
+
+Sequence diagram showing ANR report over lur for UTRAN cells. Lifelines: RNC1 (Receiving RNC), RNC2 (Base RNC), RNC3 (Neighbour RNC), and O&M. The process involves an ANR report from RNC1 to RNC2, internal processing in RNC2, an information exchange initiation between RNC2 and RNC3, neighbour handling, and final storage in RNC2.
+
+**Figure 4.2.1.2-1 ANR Report over lur for UTRAN cells**
+
+A Base RNC may control the information flow for ANR reporting over lur. The suspension and resume are initiated from Base RNC to Receiving RNC using class 2 RNSAP procedure (Information Transfer Control procedure, defined in 5.1.2). The suspension may be performed per single cell basis or the whole cells under control of Base RNC. The ANR reporting is resumed again with initiating resume procedure for a certain target in the message.
+
+![Sequence diagram showing ANR report suspension and resume between RNC1, RNC2, RNC3, and O&M.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+Intra UMTS, Inter RNS, ANR report over lur Suspend/Resume
+
+```
+
+sequenceDiagram
+    participant RNC1 as RNC1  
+(Role:  
+- Receiving RNC)
+    participant RNC2 as RNC2  
+(Role:  
+- Base RNC)
+    participant RNC3 as RNC3  
+(Role:  
+- Neighbour RNC)
+    participant OM as O&M
+
+    Note left of RNC1: RNSAP: DIRECT INFORMATION TRANSFER,  
+ANR report transparent:  
+(list NR:  
+- Cell-ID a -> Cell-ID b,  
+- Cell-ID c->Cell-ID d,  
+- Cell-ID e->Cell-ID f,...)
+    RNC1->>RNC2: RNSAP: DIRECT INFORMATION TRANSFER, ANR report transparent
+    Note right of RNC2: Role Base RNC:  
+RNC2 decides to suspend the ANR reporting to RNC2.  
+RNC2 initiates suspension procedure
+    RNC2->>RNC1: RNSAP: ANR LOG MANAGEMENT REQ:  
+(Type: Suspend,  
+Suspension Target: RNC)
+    Note right of RNC2: Role Base RNC:  
+RNC2 Earlier decided to suspend the ANR reporting to Cell-ID a in RNC2.  
+RNC2 initiates resume Of the procedure
+    RNC2->>RNC1: RNSAP: ANR LOG MANAGEMENT REQ:  
+(Type: Resume,  
+Target: Cell a)
+  
+```
+
+The diagram illustrates the interaction for ANR report suspension and resume. It starts with RNC1 (Receiving RNC) sending an RNSAP DIRECT INFORMATION TRANSFER message to RNC2 (Base RNC) containing a transparent ANR report with multiple cell ID pairs. RNC2 then decides to suspend ANR reporting and sends an RNSAP ANR LOG MANAGEMENT REQ (Type: Suspend) to RNC1. Later, RNC2 decides to resume reporting for Cell-ID a and sends another RNSAP ANR LOG MANAGEMENT REQ (Type: Resume, Target: Cell a) to RNC1. RNC3 (Neighbour RNC) and O&M are shown but not involved in this specific sequence.
+
+Sequence diagram showing ANR report suspension and resume between RNC1, RNC2, RNC3, and O&M.
+
+**Figure 4.2.1.2-2 ANR Report suspension and resume**
+
+#### 4.2.1.3 ANR Report over lur for IRAT cells
+
+On reception of an ANR report containing IRAT neighbour cells from another RNC, using the RNSAP Direct Information Transfer procedure, the Base RNC uses the globally unique cell identities and L1 information in the ANR report, and optionally also configuration in the RNC/O&M, to determine if any of these IRAT neighbour cells are potential neighbour cells. The RNC retrieves the necessary information about these potential neighbour IRAT cells from configuration in the RNC/O&M. In addition the Base RNC may interact with O&M before a neighbour relation is stored in the NRT as shown in the figure below:
+
+![Sequence diagram showing the interaction between RNC1 (Base RNC), RNC2 (Receiving RNC), and O&M for an ANR report over Iur.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+Inter RAT – ANR report received over Iur
+
+```
+
+sequenceDiagram
+    participant RNC1 as RNC1  
+(Role:  
+- Base RNC)
+    participant RNC2 as RNC2  
+(Role:  
+- Receiving RNC)
+    participant OM as O&M
+
+    Note left of RNC1: RNC1 retrieves its potential neighbours:  
+- Cell-ID a -> Cell-ID b (GERAN)  
+- Cell-ID c -> Cell-ID d (LTE)
+
+    RNC1->>RNC2: RNSAP: DIRECT INFORMATION TRANSFER,  
+ANR report transparent:  
+(list NR:  
+- Cell-ID a (RNC1) -> Cell-ID b (GERAN),  
+- Cell-ID c (RNC1)->Cell-ID d (LTE),...)
+    RNC2->>OM: Neighbour handling: RNC1/Cell-ID a -> Cell-ID b (GERAN),  
+RNC1/Cell-ID c -> Cell-ID d (LTE)  
+[implementation dependent]
+    Note left of RNC2: Store IRAT neighbour cells in NRT after  
+interaction with O&M. Store cell configuration  
+parameters and address to controlling node (BSC  
+or eNB), retrieved from configuration and/or O&M.
+  
+```
+
+Sequence diagram showing the interaction between RNC1 (Base RNC), RNC2 (Receiving RNC), and O&M for an ANR report over Iur.
+
+**Figure 4.2.1.3-1 ANR Report over Iur for IRAT cells**
+
+*[The working assumption is that ANR report reports are forwarded in current RNSAP IE "L3 Information".]*
+
+### 4.2.2 Iur Connectivity does not exist between some RNCs involved in ANR
+
+This chapter describes the handling in the Receiving RNC when the ANR function can not rely on Iur connectivity between the involved RNCs.
+
+#### 4.2.2.1 ANR report over Uu for UTRAN cells
+
+When receiving an ANR report over Uu the Receiving RNC uses the globally unique cell identities in the report to determine the network address of the Base RNCs that are controlling the Base UTRAN cells. The network address of this Base RNC is retrieved using configuration in the Receiving RNC and/or O&M. If any Base RNC involved in the logged neighbour relations in the ANR report is another RNC than the Receiving RNC, and no Iur connectivity exists to this RNC, the Receiving RNC may report the neighbour relation to O&M.
+
+On reception of an ANR report over Uu the Receiving RNC uses the globally unique cell identities and L1 information in the ANR report, and optionally also configuration in the RNC/O&M, to determine if the ANR report contains potential neighbours to the cells controlled by the Receiving RNC. If any of these potential neighbour cells is controlled by another RNC without Iur connectivity, the configuration in the RNC/O&M may be used to determine the necessary cell information. In addition the Base RNC may interact with O&M before a neighbour relation is stored in the NRT.
+
+Example: Utran network without lur connectivity between some of the RNCs
+
+![Diagram of a UTRAN network without Iur connectivity between some RNCs. At the top, a 'Core Network' box is connected to four RNCs (RNC1, RNC2, RNC3, RNC4) via 'Iu' interfaces. RNC1 (RNSa) is a Receiving RNC and Base RNC. RNC2 (RNSb) is a Neighbour RNC. RNC3 (RNSc) is a Neighbour RNC. RNC4 (RNSd) is a Base RNC. Dashed arrows represent neighbour relations in an ANR report: 1 (RNC1) to 2 (RNC2), 3 (RNC1) to 4 (RNC3), and 5 (RNC4) to 6 (RNC3). A legend indicates that dashed arrows represent 'Example neighbour relations in the ANR report' and circles represent 'Cells in the example'.](cab0834804fb031b43865554cc8d06ab_img.jpg)
+
+Diagram of a UTRAN network without Iur connectivity between some RNCs. At the top, a 'Core Network' box is connected to four RNCs (RNC1, RNC2, RNC3, RNC4) via 'Iu' interfaces. RNC1 (RNSa) is a Receiving RNC and Base RNC. RNC2 (RNSb) is a Neighbour RNC. RNC3 (RNSc) is a Neighbour RNC. RNC4 (RNSd) is a Base RNC. Dashed arrows represent neighbour relations in an ANR report: 1 (RNC1) to 2 (RNC2), 3 (RNC1) to 4 (RNC3), and 5 (RNC4) to 6 (RNC3). A legend indicates that dashed arrows represent 'Example neighbour relations in the ANR report' and circles represent 'Cells in the example'.
+
+**Figure 4.2.2.1-1 Example: UTRAN network without Iur between some of the RNCs**
+
+Example of the handling in a receiving RNC (RNC1) when there is no Iur connectivity to some of the RNCs included in the ANR report.
+
+The RNC1 receives an ANR report over Uu:
+
+- UE ANR Report sent to RNC 1:
+  - B.C1(RNC1) -> N.C2(RNC3)
+  - B.C3(RNC1) -> N.C4(RNC2)
+  - B.C5(RNC4) -> N.C6(RNC3)
+
+In the role of a receiving RNC, the RNC 1 uses the RRC Cell-ID in the ANR report to retrieve the addresses of the CRNCs involved in neighbour relations of the ANR report as Base RNC (from configuration and/or O&M). RNC 1 reports the entry B.C5(RNC4) -> N.C6(RNC3) to O&M<sup>1</sup> as there are no Iur connectivity between RNC 1 and RNC 4.
+
+RNC 1 identifies the neighbour relations in which RNC1 is involved: B.C1(RNC1) -> N.C2(RNC3), B.C3(RNC1) -> N.C4(RNC2). For B.C3(RNC1) -> N.C4(RNC2) the actions in 4.2.1.1 are performed. For B.C1(RNC1) -> N.C2(RNC3) the cell N.C2(RNC3) is configured as an external cell in RNC1<sup>1</sup> and the necessary cell information is already known to RNC1, hence after O&M interaction the neighbour relation B.C1(RNC1) -> N.C2(RNC3) is stored in the NRT.
+
+### 4.2.3 ANR Report over Uu for IRAT cells - with and without Iur
+
+When receiving an ANR report over Uu where neighbour cell(s) are in another RAT, the Receiving RNC performs the forwarding of the report to Base RNCs over Iur as described in chapter 4.2.1.1 or, in case of no Iur connectivity
+
+<sup>1</sup> These operations in RNC 1 is an implementational options used in this example.
+
+between Receiving RNC and Base RNC, handles the IRAT neighbour relation as described in 4.2.2.1. Reception over Iur of an ANR report containing IRAT neighbour cells are described in 4.2.1.3.
+
+When an RNC receives an ANR report over Uu containing IRAT neighbour cells, and if the Receiving RNC is also the Base RNC, it retrieves the necessary information for neighbour IRAT cells from O&M and/or the information of the ANR logs and determines if any of these IRAT neighbour cells are potential neighbour cells. In addition the Base RNC may interact with O&M before the neighbour relation is stored in the NRT.
+
+![Sequence diagram showing the interaction between UE, RNC1, and O&M for an ANR report over Uu for IRAT cells. The diagram shows the flow of an ANR report request, the UE ANR Report containing cell IDs for GERAN and LTE, RNC1 retrieving potential neighbours, neighbour handling, and finally storing IRAT neighbour cells in the NRT.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+**Inter RAT – ANR report received from UE - Base RNC is the same as the Receiving RNC**
+
+```
+
+sequenceDiagram
+    participant UE
+    participant RNC1
+    participant OM as O&M
+
+    Note right of RNC1: Inter RAT – ANR report received from UE - Base RNC is the same as the Receiving RNC
+
+    RNC1->>UE: ANR report request
+    UE-->>RNC1: UE ANR Report
+    Note right of UE: - Cell-ID a (RNC1) -> Cell-ID b (GERAN),  
+- Cell-ID c (RNC1)->Cell-ID d (LTE),...
+    Note right of RNC1: RNC1 retrieves its potential neighbours:  
+- Cell-ID a -> Cell-ID b (GERAN)  
+- Cell-ID c -> Cell-ID d (LTE)
+    Note right of RNC1: Neighbour handling: RNC1/Cell-ID a -> Cell-ID b (GERAN),  
+RNC1/Cell-ID c -> Cell-ID d (LTE)  
+[implementation dependent]
+    Note right of RNC1: Store IRAT neighbour cells in NRT after interaction with O&M. Store cell configuration parameters and address to controlling node (BSC or eNB), retrieved from configuration and/or O&M.
+  
+```
+
+Sequence diagram showing the interaction between UE, RNC1, and O&M for an ANR report over Uu for IRAT cells. The diagram shows the flow of an ANR report request, the UE ANR Report containing cell IDs for GERAN and LTE, RNC1 retrieving potential neighbours, neighbour handling, and finally storing IRAT neighbour cells in the NRT.
+
+**Figure 4.2.3-1 ANR Report over Uu for IRAT cells**
+
+# 5 Functions and Procedures
+
+The ANR for UTRAN supports the following functions:
+
+- ANR Management
+- Neighbour cell configuration
+  - Neighbour cell configuration for Intra-RNS cells
+  - Neighbour cell configuration for Inter-RNS cells (with Iur)
+  - Neighbour cell configuration (without Iur)
+- ANR Logging configuration
+  - Configuration parameters
+  - Configuration validity
+- Measurement Collection
+- Measurement Reporting
+- UE Capabilities
+
+## 5.1 ANR Management
+
+The ANR Management function provides means for an RNC, which receives an ANR report over the Uu interface, to distribute the report to other RNCs involved in the neighbour relations contained in the report as Base RNCs. The function also enables RNC for suspending and resuming ANR report over Iur.
+
+### 5.1.1 ANR Report Forwarding
+
+The ANR Report Forwarding uses RNSAP Direct Information Transfer procedure for sending of the ANR Report received over the Uu interface to the involved Base RNCs.
+
+![Sequence diagram for ANR Report Forwarding](bffdddb47fced140f8d17fdc2a29f592_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant Receiving RNC
+    participant Base RNC
+    Note left of Receiving RNC: Measurement reporting
+    Receiving RNC->>Base RNC: RNSAP: DIRECT INFORMATION TRANSFER (ANR report)
+```
+
+The diagram illustrates the ANR Report Forwarding process. It features three entities: UE, Receiving RNC, and Base RNC. The UE sends a 'Measurement reporting' message to the Receiving RNC. The Receiving RNC then sends an 'RNSAP: DIRECT INFORMATION TRANSFER (ANR report)' message to the Base RNC.
+
+Sequence diagram for ANR Report Forwarding
+
+Figure 5.1.1-1 ANR Report Forwarding
+
+Using the RNSAP: Direct Information Transfer procedure, the RNC receiving an ANR report over Uu may forward the ANR report to RNCs involved as Base RNCs in neighbour relations of the ANR report. The ANR report received in the RRC message over Uu is transparently forwarded in the RNSAP message. The receiving RNC extracts the neighbouring ANR cell information concerning the Base RNC from the Logged ANR Report Info list contained in the ANR Report over Uu, and includes the whole RRC message in RNSAP *L3 Information* IE.
+
+#### Abnormal conditions:
+
+When an RNC receives an ANR report outside the defined services of the ANR Report Distribution function, or if the ANR Report Distribution from the sender of the report has been suspended as described in 5.1.2, local error handling in the receiving RNC should be invoked.
+
+### 5.1.2 ANR Report Distribution Controlling
+
+The ANR Report Distribution Controlling function uses a new RNSAP procedure, Information Transfer Control procedure, for suspending and resuming ANR log reporting over Iur. An RNC receiving ANR report over Iur suspends (or resumes) ANR Reports over Iur for particular cells or for all cells in the initiating RNC.
+
+![Sequence diagram for ANR Report Distribution Controlling (Suspend/Resume)](df0bcbfa8f8e1937e071445426c28022_img.jpg)
+
+```
+sequenceDiagram
+    participant Base RNC
+    participant Receiving RNC
+    Note left of Receiving RNC: RNSAP: ANR LOG MANAGEMENT REQ  
+(Type: Suspend, Resume)  
+(Object: Cell List, All Cells)
+    Base RNC->>Receiving RNC: RNSAP: ANR LOG MANAGEMENT REQ
+```
+
+The diagram illustrates the ANR Report Distribution Controlling (Suspend/Resume) process. It features two entities: Base RNC and Receiving RNC. The Base RNC sends an 'RNSAP: ANR LOG MANAGEMENT REQ' message to the Receiving RNC. The message details include 'Type: Suspend, Resume' and 'Object: Cell List, All Cells'.
+
+Sequence diagram for ANR Report Distribution Controlling (Suspend/Resume)
+
+Figure 5.1.1-2 ANR Report Distribution Controlling (Suspend/Resume)
+
+The ANR report over Iur is resumed again using the same procedure with resume indication for any particular cells or all cells belong to initiating RNC.
+
+## 5.2 Neighbour Cell Configuration
+
+The Neighbour Cell Configuration function supports configuration of new neighbour cell relations between:
+
+- cells controlled by the same RNC
+- cells controlled by different RNCs
+- UTRAN cells and cells controlled by LTE or GERAN
+
+For the case of inter RNS and inter RAT neighbour cells, the neighbour cell may also be configured in the Base RNC. Such cell is called external cell in this chapter.
+
+### 5.2.1 Neighbour Cell Configuration for Intra-RNS cells
+
+At the reception of the ANR report over Uu interface, or at the reception of RNSAP: DIRECT INFORMATION TRANSFER message that contains an ANR report, the CRNC may configure new neighbour cell relations between the cells it controls.
+
+### 5.2.2 Neighbour Cell Configuration for Inter-RNS cells (with Iur)
+
+For configuration of neighbour cell relations and external cells when the Base UTRAN Cell and the Neighbour Cell are in different RNS, the Base RNC may use Iur to fetch the necessary cell information of the neighbour cell from neighbour RNC. The Neighbour Cell Configuration function uses RNSAP: Information Exchange Initiation procedure to fetch this cell information of the potential neighbour cell from the neighbour RNC.
+
+![Sequence diagram showing Neighbour Cell Configuration using Iur. The diagram involves three main components: an external source (grey box), a Base RNC, and a Neighbour RNC. The process starts with the reception of an ANR report from the external source by the Base RNC. The Base RNC then sends an RNSAP: INFORMATION EXCHANGE INITIATION REQUEST (on demand, type: neighbour cell) to the Neighbour RNC. The Neighbour RNC responds with an RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE (neighbour cell information) back to the Base RNC.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg)
+
+```
+sequenceDiagram
+    participant External
+    participant Base RNC
+    participant Neighbour RNC
+    Note left of Base RNC: Reception of:  
+"ANR report" over Uu or  
+"ANR report" over Iur
+    Base RNC->>Neighbour RNC: RNSAP: INFORMATION EXCHANGE INITIATION  
+REQUEST (on demand, type: neighbour cell)
+    Neighbour RNC-->>Base RNC: RNSAP: INFORMATION EXCHANGE INITIATION  
+RESPONSE (neighbour cell information)
+```
+
+Sequence diagram showing Neighbour Cell Configuration using Iur. The diagram involves three main components: an external source (grey box), a Base RNC, and a Neighbour RNC. The process starts with the reception of an ANR report from the external source by the Base RNC. The Base RNC then sends an RNSAP: INFORMATION EXCHANGE INITIATION REQUEST (on demand, type: neighbour cell) to the Neighbour RNC. The Neighbour RNC responds with an RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE (neighbour cell information) back to the Base RNC.
+
+Figure 5.2.2-1 Neighbour Cell Configuration using Iur
+
+Base RNC requests cell information required to configure the neighbour cell relation from the CRNC of potential neighbour cells using the RNSAP Information Exchange Initiation.
+
+### 5.2.3 Neighbour Cell Configuration (without Iur)
+
+At the reception of the ANR report over Uu, or at the reception of a RNSAP: DIRECT INFORMATION TRANSFER message that contains an ANR report, the Neighbour Cell Configuration function configures inter RNS and/or inter RAT neighbour cell relations and external cells in the RNC. For the necessary cell information of the neighbour cell in neighbour RNC, neighbour BSS or neighbour eNB, the Base RNC uses local configuration and/or O&M.
+
+## 5.3 ANR Logging configuration
+
+ANR logging is configured with Logged Measurements Configuration procedure, as shown in Figure 5.3-1.
+
+![Sequence diagram showing the ANR Logging configuration process. A UTRAN box is on the right and a UE box is on the left. A horizontal arrow labeled 'LOGGING MEASUREMENT CONFIGURATION' points from the UTRAN box to the UE box.](8307f6b04df072c9332f9987e034272c_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UTRAN
+    participant UE
+    Note left of UTRAN: ANR Logging configuration
+    UTRAN->>UE: LOGGING MEASUREMENT CONFIGURATION
+  
+```
+
+Sequence diagram showing the ANR Logging configuration process. A UTRAN box is on the right and a UE box is on the left. A horizontal arrow labeled 'LOGGING MEASUREMENT CONFIGURATION' points from the UTRAN box to the UE box.
+
+**Figure 5.3-1: ANR Logging configuration with Logging measurement configuration message**
+
+UTRAN initiates the ANR logging procedure to UE by sending ANR logging configuration in the Logging measurement configuration message as defined in TS 25.331.
+
+### 5.3.1 Configuration parameters
+
+- ANR logging threshold for Intra-RAT:
+  - ANR logging relative threshold. If the measured signal strength/quality of a detected cell exceeds the threshold relative to signal strength/quality in the serving cell, the UE shall treat the detected cell as candidate for one log entry in its ANR log. The detailed usage and value range of ANR logging relative threshold is defined in TS 25.304 and TS 25.331.
+  - ANR logging absolute threshold. If the measured signal strength/quality of a detected cell exceeds the absolute threshold, the UE shall treat the detected cell as candidate for one log entry in its ANR log . The detailed usage and value range of ANR logging absolute threshold is defined in TS 25.304 and TS 25.331.
+
+Note: The UTRAN provide an ANR logging absolute threshold and optionally an ANR logging relative threshold in an ANR logging configuration.
+
+- ANR logging duration timer. This configuration parameter defines a timer activated at the moment when UE receives ANR configuration. When the timer expires, the ANR logging is stopped, and the ANR configuration is deleted completely. The details and value range of ANR logging duration timer is defined in TS 25.331.
+- ANR logging indicators for Inter-RAT. The detailed usage of ANR logging indicators for Inter-RAT are defined in TS 25.331.
+
+### 5.3.2 Configuration validity
+
+The ANR logging configuration is provided in the UTRA serving cell, and its validity is described below:
+
+- ANR logging configuration is:
+  - enabled in IDLE mode, CELL\_PCH and URA\_PCH states in UTRAN.
+  - enabled in Cell\_FACH state when second DRX cycle is used in UTRAN
+  - valid until ANR logging is disabled as specified in 5.4.
+- ANR logging configuration is maintained regardless of RRC state, e.g. during multiple IDLE periods interrupted by IDLE-> Cell\_FACH or Cell\_DCH->IDLE state transitions. The configured ANR logging is enabled as described in first bullet above.
+- When UE is not in IDLE mode, CELL\_PCH, URA\_PCH state or Cell\_FACH state when second DRX cycle is used and has a valid ANR logging configuration, the ANR logging duration timer is kept running.
+- ANR logging configuration is maintained by the UE regardless of camping RAT. When UE changes the RAT, the ANR logging duration timer is kept running. The configured ANR logging is enabled as described in first bullet above.
+- When ANR log is retrieved by UTRAN, UE deletes the ANR configuration and the logged data.
+
+- When UE moves to a new PLMN within its ANR-PLMN List, the ANR logging configuration is maintained.
+
+## 5.4 Measurement Collection
+
+Within a serving cell, the UE may log multiple detected cells if satisfied by the ANR logging threshold and other criteria specified in this section. The UE should ensure that, for a serving cell, the log contains only one entry per detected cell, identified with Cell Id (i.e. Cell Identity in UTRAN, CGI for LTE and GSM).
+
+UE collects ANR measurement results and continues ANR logging according to the ANR logging configuration, and ANR logging shall be disabled if any of the following conditions is met:
+
+- the maximum number of NRs are reached.
+- the ANR logging duration timer expires.
+
+Once ANR logging is disabled, the UE stops ANR logging and stops the ANR logging duration timer and the ANR logging configuration is deleted.
+
+Note: The maximum number of NRs to be logged by the UE is hard coded.
+
+During ANR logging, UE should decide when to read the system information blocks of the target detected cell that can be logged by UE, in order to acquire the necessary ANR related information to be logged as defined in TS 25.331. The SI-reading activity in support of ANR is of best effort from UE perspective, and should not impact UE paging or mobility behaviour.
+
+For intra-UTRA case, the UE is allowed to perform ANR logging when camping on any cell belonging to its ANR-PLMN List, as well as to perform ANR measurement and to log any UTRA cell that it can detect.
+
+For logging of intra or inter -RAT neighbors, UE shall not log any neighbouring relationship entry related to CSG cell.
+
+For logging of inter-RAT GERAN neighbors, UE shall only log if the GERAN cell is not included in the neighbour list in SIB11/11bis/12.
+
+For logging of inter-RAT E-UTRAN neighbours, UE shall only log if the E-UTRAN cell is not included in the exclude-list for the EUTRAN frequency in SIB19.
+
+When UE camps on certain GSM/GERAN or E-UTRAN cell with valid ANR logging configuration and the ANR logging duration timer is still running, and then UE reselects to a certain target UTRAN cell from the source GSM/GERAN or E-UTRAN cell, UE shall log inter-RAT cell information for the source GSM/GERAN or E-UTRAN cell.
+
+## 5.5 Measurement Reporting
+
+A UE configured to perform ANR logging indicates the availability of ANR logs, by means of a one bit indicator in RRC\_CONNECTION\_SETUP\_COMPLETE, CELL\_UPDATE, URA\_UPDATE and MEASUREMENT REPORT (only applicable in case when UE is able to make seamless transition from Cell\_PCH state to Cell\_FACH state) messages.
+
+The network may decide to retrieve the ANR logs based on this indicator in Cell\_DCH or Cell\_FACH states.
+
+In case the network will not retrieve ANR logs, UE should store non-retrieved ANR logs for 48 hours from the moment when the UE receives the logged ANR configuration. There is no requirement to store non-retrieved ANR logs beyond 48 hours. In addition, all related ANR configuration and ANR logs shall be removed by the UE at NAS detach or switch off.
+
+For Logged ANR, UE checks if the RPLMN is the same as one of the PLMNs in the "ANR-PLMN List" before signalling the presence of ANR logs in its memory, and UE checks if the RPLMN is the same as one of the PLMNs in the "ANR-PLMN List" before sending back the ANR logs to the network.
+
+When ANR logs are retrieved, the reported measurement results are deleted.
+
+The ANR log reporting should not prevent reporting two detected cells with the same PSC/Frequency if the Cell-Id is different for the two detected cells.
+
+Note: The UE information request/response procedure is used for ANR log request/reporting. The details for ANR log retrieval is defined in TS 25.331.
+
+## 5.6 UE Capabilities
+
+One UE capability indicator is used to indicate UE support of UTRA ANR, covering both Intra-RAT and Inter-RAT detected cells. The UTRAN ANR logging capability is independent of other logging capability in UE.

marked/Rel-18/specs_problems.md

@@ -0,0 +1,152 @@
+# Rel-18 Spec Conversion Problems
+
+## Root Cause
+
+Datalab API converts DOCX -> PDF via LibreOffice internally.
+26 specs have large `document.xml` and many embedded OLE objects
+(Visio diagrams, binary embeddings) that cause LibreOffice to
+exceed its 60-second server-side timeout.
+
+Error: `Conversion to PDF failed: LibreOffice conversion timed out after 60 seconds`
+
+## Resolution
+
+Each DOCX was split into 3 smaller parts, converted individually,
+then merged back into a single markdown file.
+
+## Results
+
+| Spec ID | Filename | Status | DOCX Words | MD Words | Ratio | Parts |
+|---------|----------|--------|------------|----------|-------|-------|
+| 23228 | 23228-i40.docx | OK | 142,024 | 172,006 | 1.211 | 10 |
+| 23280 | 23280-i80.docx | OK | 107,340 | 150,748 | 1.404 | 10 |
+| 23281 | 23281-i60.docx | OK | 57,888 | 84,189 | 1.454 | 10 |
+| 23282 | 23282-i60.docx | OK | 76,910 | 113,660 | 1.478 | 10 |
+| 23288 | 23288-i40.docx | OK | 104,702 | 147,626 | 1.410 | 10 |
+| 23379 | 23379-i80.docx | OK | 83,882 | 117,173 | 1.397 | 10 |
+| 23401 | 23401-i40.docx | OK | 242,808 | 284,524 | 1.172 | 10 |
+| 23402 | 23402-i30.docx | OK | 132,703 | 164,701 | 1.241 | 10 |
+| 23434 | 23434-i70.docx | OK | 75,664 | 112,892 | 1.492 | 10 |
+| 23501 | 23501-i40.docx | OK | 341,122 | 427,013 | 1.252 | 10 |
+| 23502 | 23502-i40.docx | OK | 374,897 | 478,846 | 1.277 | 10 |
+| 23558 | 23558-i50.docx | OK | 72,732 | 112,422 | 1.546 | 10 |
+| 23700-60 | 23700-60-i00.docx | OK | 107,341 | 125,201 | 1.166 | 10 |
+| 23700-81 | 23700-81-i00.docx | OK | 96,778 | 121,620 | 1.257 | 10 |
+| 23700-98 | 23700-98-i10.docx | OK | 81,208 | 106,371 | 1.310 | 10 |
+| 28552 | 28552-i50.docx | OK | 119,235 | 133,285 | 1.118 | 10 |
+| 29213 | 29213-i00.docx | OK | 66,426 | 96,510 | 1.453 | 10 |
+| 29503 | 29503-i40.docx | OK | 94,505 | 162,437 | 1.719 | 20 |
+| 29513 | 29513-i40.docx | OK | 80,341 | 112,077 | 1.395 | 10 |
+| 32260 | 32260-i20.docx | WARN | 31,665 | 86,085 | 2.719 | 10 |
+| 32422 | 32422-i10.docx | OK | 60,619 | 79,495 | 1.311 | 20 |
+| 33501 | 33501-i40.docx | OK | 132,697 | 160,934 | 1.213 | 50 |
+| 36300 | 36300-i00.docx | OK | 145,138 | 191,301 | 1.318 | 10 |
+| 38331 | 38331-i00.docx | OK | 313,362 | 459,512 | 1.466 | 10 |
+| 38521-3 | 38521-3-i11.docx | WARN | 185,354 | 388,990 | 2.099 | 10 |
+| 38870 | 38870-i00.docx | OK | 22,994 | 40,357 | 1.755 | 10 |
+
+## Spec Details
+
+### 23228 (23228-i40.docx)
+- Compressed size: 4.9 MB
+- Split part sizes: [4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3] MB
+
+### 23280 (23280-i80.docx)
+- Compressed size: 8.1 MB
+- Split part sizes: [7.3, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4] MB
+
+### 23281 (23281-i60.docx)
+- Compressed size: 4.9 MB
+- Split part sizes: [4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.5] MB
+
+### 23282 (23282-i60.docx)
+- Compressed size: 4.2 MB
+- Split part sizes: [3.6, 3.6, 3.6, 3.7, 3.7, 3.6, 3.6, 3.6, 3.6, 3.7] MB
+
+### 23288 (23288-i40.docx)
+- Compressed size: 6.5 MB
+- Split part sizes: [5.7, 5.8, 5.8, 5.8, 5.7, 5.8, 5.8, 5.8, 5.8, 5.8] MB
+
+### 23379 (23379-i80.docx)
+- Compressed size: 6.6 MB
+- Split part sizes: [6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.4] MB
+
+### 23401 (23401-i40.docx)
+- Compressed size: 5.4 MB
+- Split part sizes: [4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.7] MB
+
+### 23402 (23402-i30.docx)
+- Compressed size: 5.2 MB
+- Split part sizes: [5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0] MB
+
+### 23434 (23434-i70.docx)
+- Compressed size: 5.1 MB
+- Split part sizes: [4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8] MB
+
+### 23501 (23501-i40.docx)
+- Compressed size: 7.8 MB
+- Split part sizes: [6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.7] MB
+
+### 23502 (23502-i40.docx)
+- Compressed size: 15.3 MB
+- Split part sizes: [14.1, 14.2, 14.2, 14.2, 14.2, 14.2, 14.1, 14.2, 14.1, 14.5] MB
+
+### 23558 (23558-i50.docx)
+- Compressed size: 5.6 MB
+- Split part sizes: [4.7, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8] MB
+
+### 23700-60 (23700-60-i00.docx)
+- Compressed size: 6.6 MB
+- Split part sizes: [5.9, 6.0, 5.9, 5.9, 5.9, 6.0, 5.9, 5.9, 5.9, 5.9] MB
+
+### 23700-81 (23700-81-i00.docx)
+- Compressed size: 7.8 MB
+- Split part sizes: [7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2] MB
+
+### 23700-98 (23700-98-i10.docx)
+- Compressed size: 4.9 MB
+- Split part sizes: [4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6] MB
+
+### 28552 (28552-i50.docx)
+- Compressed size: 1.3 MB
+- Split part sizes: [0.7, 0.8, 0.7, 0.7, 0.7, 0.7, 0.7, 0.7, 0.7, 0.8] MB
+
+### 29213 (29213-i00.docx)
+- Compressed size: 4.9 MB
+- Split part sizes: [4.8, 4.8, 4.8, 4.7, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8] MB
+
+### 29503 (29503-i40.docx)
+- Compressed size: 4.3 MB
+- Split part sizes: [3.2, 3.2, 3.2, 3.3, 3.3, 3.3, 3.3, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.3] MB
+
+### 29513 (29513-i40.docx)
+- Compressed size: 3.7 MB
+- Split part sizes: [3.4, 3.4, 3.4, 3.4, 3.4, 3.4, 3.4, 3.5, 3.4, 3.5] MB
+
+### 32260 (32260-i20.docx)
+- Compressed size: 3.2 MB
+- Split part sizes: [3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.1] MB
+
+### 32422 (32422-i10.docx)
+- Compressed size: 4.3 MB
+- Split part sizes: [4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2] MB
+
+### 33501 (33501-i40.docx)
+- Compressed size: 6.5 MB
+- Split part sizes: [6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1] MB
+
+### 36300 (36300-i00.docx)
+- Compressed size: 9.3 MB
+- Split part sizes: [8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 9.0] MB
+
+### 38331 (38331-i00.docx)
+- Compressed size: 3.4 MB
+- Split part sizes: [1.2, 1.2, 1.2, 1.3, 1.3, 1.3, 1.2, 1.1, 1.2, 1.5] MB
+
+### 38521-3 (38521-3-i11.docx)
+- Compressed size: 3.0 MB
+- Split part sizes: [1.1, 1.2, 1.3, 1.1, 1.1, 1.1, 1.4, 1.5, 1.1, 1.4] MB
+
+### 38870 (38870-i00.docx)
+- Compressed size: 8.3 MB
+- Split part sizes: [7.6, 7.6, 7.7, 7.6, 7.6, 7.7, 7.7, 7.6, 7.7, 7.7] MB

marked/Rel-18/split_convert_log.jsonl

@@ -0,0 +1,30 @@
+{"spec_id": "28552", "filename": "28552-i50.docx", "parts": 10, "part_sizes_mb": [0.7, 0.8, 0.7, 0.7, 0.7, 0.7, 0.7, 0.7, 0.7, 0.8], "merged_chars": 979117, "docx_words": 119235, "md_words": 133285, "ratio": 1.118, "status": "OK"}
+{"spec_id": "23228", "filename": "23228-i40.docx", "parts": 10, "part_sizes_mb": [4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3, 4.3], "merged_chars": 1342254, "docx_words": 142024, "md_words": 172006, "ratio": 1.211, "status": "OK"}
+{"spec_id": "23280", "filename": "23280-i80.docx", "parts": 10, "part_sizes_mb": [7.3, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4, 7.4], "merged_chars": 1440070, "docx_words": 107340, "md_words": 150748, "ratio": 1.404, "status": "OK"}
+{"spec_id": "23281", "filename": "23281-i60.docx", "parts": 10, "part_sizes_mb": [4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.4, 4.5], "merged_chars": 841257, "docx_words": 57888, "md_words": 84189, "ratio": 1.454, "status": "OK"}
+{"spec_id": "23282", "filename": "23282-i60.docx", "parts": 10, "part_sizes_mb": [3.6, 3.6, 3.6, 3.7, 3.7, 3.6, 3.6, 3.6, 3.6, 3.7], "merged_chars": 1169822, "docx_words": 76910, "md_words": 113660, "ratio": 1.478, "status": "OK"}
+{"spec_id": "23288", "filename": "23288-i40.docx", "parts": 10, "part_sizes_mb": [5.7, 5.8, 5.8, 5.8, 5.7, 5.8, 5.8, 5.8, 5.8, 5.8], "merged_chars": 1552184, "docx_words": 104702, "md_words": 147626, "ratio": 1.41, "status": "OK"}
+{"spec_id": "23379", "filename": "23379-i80.docx", "parts": 10, "part_sizes_mb": [6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.4], "error": "Part 6 returned no content", "status": "CONVERT_ERROR"}
+{"spec_id": "23401", "filename": "23401-i40.docx", "parts": 10, "part_sizes_mb": [4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.7], "merged_chars": 2027425, "docx_words": 242808, "md_words": 284524, "ratio": 1.172, "status": "OK"}
+{"spec_id": "23402", "filename": "23402-i30.docx", "parts": 10, "part_sizes_mb": [5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0, 5.0], "merged_chars": 1162450, "docx_words": 132703, "md_words": 164701, "ratio": 1.241, "status": "OK"}
+{"spec_id": "23434", "filename": "23434-i70.docx", "parts": 10, "part_sizes_mb": [4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8], "merged_chars": 1157151, "docx_words": 75664, "md_words": 112892, "ratio": 1.492, "status": "OK"}
+{"spec_id": "23379", "filename": "23379-i80.docx", "parts": 10, "part_sizes_mb": [6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.4], "merged_chars": 1098270, "docx_words": 83882, "md_words": 117173, "ratio": 1.397, "status": "OK"}
+{"spec_id": "23501", "filename": "23501-i40.docx", "parts": 10, "part_sizes_mb": [6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.3, 6.7], "merged_chars": 3091724, "docx_words": 341122, "md_words": 427013, "ratio": 1.252, "status": "OK"}
+{"spec_id": "23502", "filename": "23502-i40.docx", "parts": 10, "part_sizes_mb": [14.1, 14.2, 14.2, 14.2, 14.2, 14.2, 14.1, 14.2, 14.1, 14.5], "merged_chars": 3777087, "docx_words": 374897, "md_words": 478846, "ratio": 1.277, "status": "OK"}
+{"spec_id": "23558", "filename": "23558-i50.docx", "parts": 10, "part_sizes_mb": [4.7, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8], "merged_chars": 1132946, "docx_words": 72732, "md_words": 112422, "ratio": 1.546, "status": "OK"}
+{"spec_id": "23700-60", "filename": "23700-60-i00.docx", "parts": 10, "part_sizes_mb": [5.9, 6.0, 5.9, 5.9, 5.9, 6.0, 5.9, 5.9, 5.9, 5.9], "merged_chars": 954733, "docx_words": 107341, "md_words": 125201, "ratio": 1.166, "status": "OK"}
+{"spec_id": "23700-81", "filename": "23700-81-i00.docx", "parts": 10, "part_sizes_mb": [7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2, 7.2], "merged_chars": 1116792, "docx_words": 96778, "md_words": 121620, "ratio": 1.257, "status": "OK"}
+{"spec_id": "23700-98", "filename": "23700-98-i10.docx", "parts": 10, "part_sizes_mb": [4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6, 4.6], "merged_chars": 935679, "docx_words": 81208, "md_words": 106371, "ratio": 1.31, "status": "OK"}
+{"spec_id": "29213", "filename": "29213-i00.docx", "parts": 10, "part_sizes_mb": [4.8, 4.8, 4.8, 4.7, 4.8, 4.8, 4.8, 4.8, 4.8, 4.8], "merged_chars": 847173, "docx_words": 66426, "md_words": 96510, "ratio": 1.453, "status": "OK"}
+{"spec_id": "29513", "filename": "29513-i40.docx", "parts": 10, "part_sizes_mb": [3.4, 3.4, 3.4, 3.4, 3.4, 3.4, 3.4, 3.5, 3.4, 3.5], "merged_chars": 1031877, "docx_words": 80341, "md_words": 112077, "ratio": 1.395, "status": "OK"}
+{"spec_id": "32260", "filename": "32260-i20.docx", "parts": 10, "part_sizes_mb": [3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.0, 3.1], "merged_chars": 1043419, "docx_words": 31665, "md_words": 86085, "ratio": 2.719, "status": "WARN"}
+{"spec_id": "36300", "filename": "36300-i00.docx", "parts": 10, "part_sizes_mb": [8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 8.8, 9.0], "merged_chars": 1532929, "docx_words": 145138, "md_words": 191301, "ratio": 1.318, "status": "OK"}
+{"spec_id": "38331", "filename": "38331-i00.docx", "parts": 10, "part_sizes_mb": [1.2, 1.2, 1.2, 1.3, 1.3, 1.3, 1.2, 1.1, 1.2, 1.5], "merged_chars": 6651982, "docx_words": 313362, "md_words": 459512, "ratio": 1.466, "status": "OK"}
+{"spec_id": "38521-3", "filename": "38521-3-i11.docx", "parts": 10, "part_sizes_mb": [1.1, 1.2, 1.3, 1.1, 1.1, 1.1, 1.4, 1.5, 1.1, 1.4], "merged_chars": 4031618, "docx_words": 185354, "md_words": 388990, "ratio": 2.099, "status": "WARN"}
+{"spec_id": "38870", "filename": "38870-i00.docx", "parts": 10, "part_sizes_mb": [7.6, 7.6, 7.7, 7.6, 7.6, 7.7, 7.7, 7.6, 7.7, 7.7], "merged_chars": 447506, "docx_words": 22994, "md_words": 40357, "ratio": 1.755, "status": "OK"}
+{"spec_id": "29503", "filename": "29503-i40.docx", "parts": 20, "part_sizes_mb": [3.2, 3.2, 3.2, 3.3, 3.3, 3.3, 3.3, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.3], "merged_chars": 2503220, "docx_words": 94505, "md_words": 162437, "ratio": 1.719, "status": "OK"}
+{"spec_id": "32422", "filename": "32422-i10.docx", "parts": 20, "part_sizes_mb": [4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2, 4.2], "merged_chars": 712629, "docx_words": 60619, "md_words": 79495, "ratio": 1.311, "status": "OK"}
+{"spec_id": "33501", "filename": "33501-i40.docx", "parts": 50, "part_sizes_mb": [6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1], "error": "Part 37 returned no content", "status": "CONVERT_ERROR"}
+{"spec_id": "33501", "filename": "33501-i40.docx", "parts": 50, "part_sizes_mb": [6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1], "error": "Part 37 retry failed: Part with 4 elements below min_elements=5 still fails Datalab conversion", "status": "CONVERT_ERROR"}
+{"spec_id": "33501", "filename": "33501-i40.docx", "parts": 50, "part_sizes_mb": [6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1], "error": "Part 37 retry failed: Reached max retry depth (8) with 1 elements still failing", "status": "CONVERT_ERROR"}
+{"spec_id": "33501", "filename": "33501-i40.docx", "parts": 50, "part_sizes_mb": [6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.1], "merged_chars": 1198017, "docx_words": 132697, "md_words": 160934, "ratio": 1.213, "status": "OK"}