Add files using upload-large-folder tool

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

@@ -0,0 +1,476 @@
+
+
+# 3GPP TS 25.367 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Mobility procedures for Home Node B (HNB); Overall description; Stage 2 (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 'P'. A small 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+## --- **Keywords**
+
+UMTS, stage 2, radio, architecture, HNB, CSG
+
+## **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 .....                                                     | 6         |
+| 4 Overview.....                                                             | 7         |
+| 5 CSG Identification .....                                                  | 8         |
+| 6 CSG Selection.....                                                        | 8         |
+| 6.1 Manual CSG ID Selection.....                                            | 8         |
+| 7 CSG Cell Reselection.....                                                 | 9         |
+| 7.1 Measurement Rules for CSG Cells .....                                   | 9         |
+| 7.2 Reselection to CSG Cell.....                                            | 9         |
+| 7.2.1 Criteria for Intra-frequency Cell Reselection.....                    | 9         |
+| 7.2.2 Criteria for Inter-frequency Cell Reselection.....                    | 9         |
+| 7.2.3 Criteria for Inter-RAT Cell Reselection.....                          | 9         |
+| 7.3 Reselection from CSG Cell .....                                         | 9         |
+| 7.3.1 Criteria for Intra-frequency Cell Reselection.....                    | 9         |
+| 7.3.2 Criteria for Inter-frequency Cell Reselection.....                    | 9         |
+| 7.3.3 Criteria for Inter-RAT Cell Reselection.....                          | 9         |
+| 7.4 Reselection from CSG Cell to CSG Cell .....                             | 10        |
+| 7.5 Parameters for CSG Cell Reselection .....                               | 10        |
+| 8 CSG and Hybrid Cell Handover .....                                        | 10        |
+| 8.1 Handover to CSG/Hybrid Cell .....                                       | 10        |
+| 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure .....           | 11        |
+| 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure ..... | 12        |
+| 8.2 Handover from CSG Cell.....                                             | 13        |
+| 8.3 Handover from CSG Cell to CSG Cell .....                                | 13        |
+| 9 Support of Hybrid Cells .....                                             | 13        |
+| 9.1 Measurement Rules.....                                                  | 13        |
+| 9.2 Reselection .....                                                       | 13        |
+| <b>Annex B (informative): Void.....</b>                                     | <b>14</b> |
+| <b>Annex C (informative): Change history.....</b>                           | <b>14</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
+
+This document provides a high level description of the mobility procedures applicable to Home NodeB support in the current Release. Where appropriate, the reasons behind the agreements are provided. Throughout this document, unless otherwise stated, the UE is assumed to be a current Release UE that supports the Closed Subscriber Group (CSG) feature, whether it is actually a member of a CSG or not. A UE that does not support the CSG feature is not required to support any of the procedures stated in this document.
+
+# --- 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.304: "UE procedures in idle mode and procedures for cell reselection in connected mode".
+- [3] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [4] 3GPP TS 23.011: "Service accessibility".
+- [5] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs".
+- [6] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB)".
+- [7] 3GPP TS 25.214: "Physical layer procedures (FDD)".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Acceptable Cell:** A cell that satisfies certain conditions as specified [2]. A UE can always attempt emergency calls on an acceptable cell.
+
+**CSG whitelist:** A list provided by NAS containing all the CSG Identities of the CSGs to which the subscriber belongs.
+
+NOTE: This list is known as Allowed CSG List in Rel-8 Access Stratum specifications.
+
+**Available PLMN:** A PLMN for which the UE has found at least one cell and read its PLMN identity.
+
+**Barred Cell:** A cell a UE is not allowed to camp on.
+
+**Camped on a cell:** UE has completed the cell selection/reselection process and has chosen a cell. The UE monitors system information and (in most cases) paging information.
+
+**Camped on any cell:** UE is in idle mode and has completed the cell selection/reselection process and has chosen a cell irrespective of PLMN identity.
+
+**Closed Subscriber Group (CSG):** A Closed Subscriber Group identifies subscribers of an operator who are permitted to access one or more cells of the PLMN but which have restricted access (CSG cells).
+
+**CSG Cell:** A cell, part of the PLMN, broadcasting a CSG Indicator that is set to TRUE and a specific CSG identity. A CSG cell is accessible by the members of the closed subscriber group for that CSG identity.
+
+**CSG Identity (CSG ID):** An identifier broadcast by a CSG/Hybrid cell or cells and used by the UE to facilitate access for authorised members of the associated Closed Subscriber Group.
+
+**CSG member cell:** A cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN and for which the CSG whitelist of the UE includes an entry comprising cell's CSG ID and the respective PLMN identity.
+
+**DRX cycle:** Individual time interval between monitoring Paging Occasion for a specific UE.
+
+**Equivalent PLMN list:** List of PLMNs considered as equivalent by the UE for cell selection, cell reselection, MBSFN Cluster selection MBSFN Cluster reselection and handover according to the information provided by the NAS.
+
+**Home NodeB (HNB):** A HNB is a customer-premises equipment that connects a 3GPP UE over UTRAN wireless air interface to a mobile operator's network using broadband IP backhaul.
+
+**HNB Name:** The Home NodeB Name is a broadcast string in free text format that provides a human readable name for the Home NodeB CSG identity.
+
+**Home PLMN:** A PLMN where the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI.
+
+**Hybrid cell:** A cell broadcasting a CSG identity which is accessible as a CSG cell by UEs which are members of the CSG and as a normal cell by all other UEs.
+
+**Non-CSG Cell:** A cell that is not a CSG cell, e.g. a macro cell.
+
+**Process:** A local action in the UE invoked by a RRC procedure or an Idle Mode procedure.
+
+**Radio Access Mode:** Radio access mode of the cell, FDD or TDD.
+
+**Radio Access Technology:** Type of technology used for radio access, for instance UTRA or GSM.
+
+**Registered PLMN:** This is the PLMN on which certain Location Registration outcomes have occurred.
+
+**Registration Area:** (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure.
+
+**Reserved Cell:** A cell on which camping is not allowed, except for particular UEs, if so indicated in the system information.
+
+**Restricted Cell:** A cell on which camping is allowed, but access attempts are disallowed for UEs whose access classes are indicated as barred.
+
+**Selected PLMN:** This is the PLMN that has been selected by the NAS, either manually or automatically.
+
+**Serving cell:** The cell on which the UE is camped.
+
+**Strongest cell:** The cell on a particular carrier that is considered strongest according to the layer 1 cell search procedure [7]. As the details of the layer 1 cell search are implementation dependent, the precise definition of 'strongest cell' is also implementation dependent.
+
+**Suitable Cell:** This is a cell on which an UE may camp.
+
+## 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].
+
+|    |                |
+|----|----------------|
+| AS | Access Stratum |
+|----|----------------|
+
+|        |                                            |
+|--------|--------------------------------------------|
+| BCCH   | Broadcast Control Channel                  |
+| CM     | Connection Management                      |
+| CN     | Core Network                               |
+| CSG    | Closed Subscriber Group                    |
+| DRX    | Discontinuous Reception                    |
+| E-UTRA | Evolved UMTS Terrestrial Radio Access      |
+| FDD    | Frequency Division Duplex                  |
+| GPRS   | General Packet Radio Service               |
+| GSM    | Global System for Mobile Communications    |
+| HCS    | Hierarchical Cell Structure                |
+| HNB    | Home NodeB                                 |
+| IMSI   | International Mobile Subscriber Identity   |
+| MCC    | Mobile Country Code                        |
+| MM     | Mobility Management                        |
+| MNC    | Mobile Network Code                        |
+| NAS    | Non-Access Stratum                         |
+| PCH    | Paging Channel                             |
+| PI     | Page Indicator                             |
+| PICH   | Page Indication Channel                    |
+| PLMN   | Public Land Mobile Network                 |
+| RAT    | Radio Access Technology                    |
+| RRC    | Radio Resource Control                     |
+| SAP    | Service Access Point                       |
+| TDD    | Time Division Duplex                       |
+| TMGI   | Temporary Mobile Group Identity            |
+| UE     | User Equipment                             |
+| UMTS   | Universal Mobile Telecommunications System |
+| UTRA   | UMTS Terrestrial Radio Access              |
+| UTRAN  | UMTS Terrestrial Radio Access Network      |
+
+# 4 Overview
+
+A Home NodeB may provide restricted access to only UEs belonging to a Closed Subscriber Group (CSG). One or more of such cells providing restricted access, known as CSG cells, are identified by a unique numeric identifier called CSG Identity. To facilitate access control, a UE with CSG subscription would have an CSG whitelist, which contains one or more CSG Identities associated with the CSG cells on which the UE is allowed access. The UE uses the CSG whitelist along with the CSG Identity and associated PLMN ID broadcast by the CSG Cells in CSG cell selection and reselection.
+
+A HNB can also be operated as a hybrid cell. A hybrid cell is accessed as a CSG cell by a UE whose CSG whitelist contains the cell's CSG ID and associated PLMN ID and as a normal cell by all other UEs. Members of the CSG are expected to receive preferential access according to [5].
+
+NOTE: Although pre-Rel-9 UEs are able to camp on hybrid cells (which would be regarded as normal cells for access) there is no possibility for these UEs to identify a hybrid cell as a CSG cell even though the cell's CSG identity and associated PLMN ID are in the UE's CSG whitelist.
+
+In addition, manual selection of CSG Identity is introduced, which enables the human user to manually select a CSG Identity for UE to camp on.
+
+This document provides high level descriptions and procedures of the mobility features to support CSG deployment in the current Release. The following areas will be covered in the subsequent chapters:
+
+- Identifiers associated with the CSG framework
+- Manual selection of CSG Identity
+- Measurement rules for CSG Cells
+- Cell reselection to a CSG cell, from a CSG cell, and between CSG cells
+- Handover to a CSG cell, from a CSG cell, and between CSG cells, where applicable
+
+- Measurement rules, (re)selection and handover procedures for hybrid cells.
+
+# --- 5 CSG Identification
+
+One or more Closed Subscriber Group (CSG) cells are identified by a unique numeric identifier called CSG Identity or CSG ID. A UE belonging to a CSG has the corresponding CSG ID and associated PLMN ID in its CSG whitelist. The CSG whitelist is maintained and provided by NAS. The CSG ID is broadcast in system information by the CSG cell or hybrid cell, and used by the UE for cell (re)selection and handover purposes.
+
+A cell may optionally broadcast the CSG Indicator, whose presence and value of TRUE indicates the cell is a CSG cell. The absence of the CSG indicator in a cell which broadcasts a CSG identity indicates that it is a hybrid cell.
+
+A CSG cell or hybrid cell may broadcast the HNB Name, a textual identifier, in system information. The HNB Name can be used to aid the human user in manual selection of a CSG ID.
+
+At the physical layer, a CSG cell is identified by its carrier frequency (UARFCN) and Primary Scrambling Code (PSC). A set of PSCs could be reserved for CSG deployment and this reserved PSC range may be signalled in system information. The PSC of a CSG cell belongs to the reserved PSC range if broadcast.
+
+On the mixed carrier frequency shared by both non-CSG cells (UMTS macro cells) and CSG cells, CSG cells broadcast in system information the PSC range reserved by the network for CSG cells. The non-CSG cells may also broadcast the reserved PSC range. The reserved PSC range is only applicable to the UARFCN within the PLMN where the UE received this information. The UE considers the last received reserved PSC range to be valid within the entire PLMN for the duration of 24 hours. The UE may use the reserved PSC information for CSG cell search and (re)selection purposes, according to UE's implementation.
+
+**NOTE:** In shared network scenario, aligned PSC ranges are beneficial in the shared carrier frequency across the involved PLMNs. Furthermore, in deployments where cells broadcast different primary PLMN (with or without multiple PLMN IDs), it is beneficial that CSG and non-CSG cells will broadcast same PSC ranges. Moreover, it is beneficial if a CSG cell, if listed in system information and associated with a PLMN, is associated with the primary PLMN of the serving cell.
+
+Non-CSG cells and CSG cells may broadcast indications of one or more carrier frequencies used for dedicated CSG deployment. This information may be used by a UE to avoid unnecessary measurements on that frequency even when cell measurement rules would require measurements of this carrier frequency. Indications of which carrier frequencies are dedicated to CSG-only deployment may be signalled in system information and are applicable only in the cell where this information is broadcast.
+
+# --- 6 CSG Selection
+
+## 6.1 Manual CSG ID Selection
+
+Manual CSG ID selection enables a human user to select a CSG ID. In manual CSG ID selection the UE may scan all frequencies in the supported frequency bands and display a list of found CSG IDs or the corresponding HNB Names if broadcast by the CSG cells or hybrid cells, and indications as to whether the found CSG IDs and associated PLMN IDs are contained in the UE's CSG whitelist. When the user selects an entry in the list, the UE selects any CSG cell or hybrid cell among the ones with same CSG ID and PLMN ID. The UE may normally camp on the chosen cell if it is a CSG member cell or a hybrid cell.
+
+During manual CSG ID selection a UE is allowed to perform Location Registration procedure on a CSG cell that is not a CSG member cell.
+
+Based on the outcome of a Location Registration procedure initiated on a CSG cell, the UE's CSG whitelist is updated.
+
+The UE is allowed to *not* support manual CSG ID selection in connected mode.
+
+# 7 CSG Cell Reselection
+
+## 7.1 Measurement Rules for CSG Cells
+
+To measure CSG member cell(s), a UE applies an autonomous search function, per UE implementation, regardless of which RAT the UE is camping on. The autonomous search function determines when and where to search for the CSG member cells.
+
+Autonomous search procedure is disabled by the search function if UE's CSG whitelist does not exist or is empty.
+
+On a mixed carrier, a UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells.
+
+A UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells on the carrier frequency dedicated to CSG deployment.
+
+## 7.2 Reselection to CSG Cell
+
+The cell reselection criteria described in this section is applicable when the UE is in the following call states: Idle Mode, Cell\_PCH, URA\_PCH and Cell\_FACH states, unless otherwise stated.
+
+Inter-RAT and inter-frequency reselection in CELL\_FACH state only needs to be performed when second DRX is used.
+
+### 7.2.1 Criteria for Intra-frequency Cell Reselection
+
+For intra-frequency reselection from a non-CSG cell to a CSG member cell, the UE follows the same cell ranking rules as those defined for the UTRA case in [2]. The UE may ignore not allowed CSG cells in the ranking. The UE applies reselection parameters broadcast by the serving cell. A UE may normally camp on a CSG member cell.
+
+### 7.2.2 Criteria for Inter-frequency Cell Reselection
+
+For inter-frequency cell reselection, the UE considers the frequency where its CSG member cell is on to have the highest priority value, irrespective of network configured frequency priorities, as long as the CSG member cell remains best ranked on that frequency.
+
+### 7.2.3 Criteria for Inter-RAT Cell Reselection
+
+Inter-RAT reselection to a CSG member cell is supported when the UE is camped on another RAT. The UE requirements are defined in the specifications of the concerned RAT.
+
+## 7.3 Reselection from CSG Cell
+
+### 7.3.1 Criteria for Intra-frequency Cell Reselection
+
+For intra-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2].
+
+### 7.3.2 Criteria for Inter-frequency Cell Reselection
+
+For inter-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2].
+
+### 7.3.3 Criteria for Inter-RAT Cell Reselection
+
+For reselection from a CSG cell to a GSM or E-UTRA cell, the UE follows the respective procedures defined in [2].
+
+## 7.4 Reselection from CSG Cell to CSG Cell
+
+For reselection between CSG member cells, the UE follows the same cell ranking rules as those defined for the UTRA case in [2].
+
+## 7.5 Parameters for CSG Cell Reselection
+
+No new parameters are defined for CSG cell ranking. The same cell reselection parameters defined for the UTRA case in [2] are used for CSG cell ranking purposes, if configured. The operator may configure the cell reselection parameters, such as Qoffset and Qhyst, to bias the reselection of CSG cells.
+
+# --- 8 CSG and Hybrid Cell Handover
+
+## 8.1 Handover to CSG/Hybrid Cell
+
+Handover to a HNB/HeNB follows the framework as specified in [3], [6]. Handover to a HNB/HeNB is different from the normal handover procedure in four aspects:
+
+1. **Proximity Estimation:** in case the UE is able to determine, based on UE implementation, that it is near a CSG member cell, the UE may provide to the SRNC an indication of proximity. The CSG proximity indication may be used as follows:
+  - a. If a measurement configuration is not present for the concerned frequency/RAT, the SRNC may configure the UE to perform measurements and reporting for the concerned frequency/RAT.
+  - b. The SRNC may determine whether to perform other actions related to handover to HNB/HeNBs based on having received a proximity indication (for example, the SRNC may not configure compressed mode gaps for the UE to detect the HNB/HeNB on a different frequency/RAT unless it has received a proximity indication).
+2. **PSC/PCI Confusion:** due to the typical cell size of HNB/HeNBs being much smaller than macro cells, there can be multiple HNBs/HeNBs within the coverage of the SRNC that have the same PSC/PCI. This leads to a condition referred to as PSC/PCI confusion, wherein the SRNC is unable to determine the correct target cell for handover from the PSC/PCI included in the measurement reports from the UE. PSC/PCI confusion is solved by the UE reporting the cell identity of the target HNB/HeNB.
+3. **Access Control:** If the target cell is a hybrid cell, prioritization of allocated resources may be performed based on the UE's membership status. Access control is done by a two step process, where first the UE reports whether the target cell is a CSG member cell based on the UE's CSG whitelist, and then the network verifies the reported status.
+4. **PLMN Report:** If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition.
+
+Mobility from SRNC to a CSG/hybrid cell from network perspective is described in [6]. The following two sections describe the radio aspects. The SRNC in the call flows of these sections can be an RNC or a HNB.
+
+### 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure
+
+![Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant SRNC
+    Note right of SRNC: 5. Handover processing [6]
+    SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)]
+    UE-->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication]
+    SRNC->>UE: 3. MEASUREMENT CONTROL [(CSG Intrafrequency cell info), (Intra-frequency SI Acquisition)]
+    UE-->>SRNC: 4. MEASUREMENT REPORT [PSC, Cell Identity, CSG Member Indication]
+  
+```
+
+The diagram shows a sequence of interactions between a User Equipment (UE) and a Serving Radio Network Controller (SRNC). The process begins with the SRNC sending a 'MEASUREMENT CONTROL' message to the UE, specifying 'CSG Proximity detection' as the measurement type. The UE responds with a 'MEASUREMENT REPORT' containing a 'CSG Proximity Indication'. The SRNC then sends another 'MEASUREMENT CONTROL' message, this time providing 'CSG Intrafrequency cell info' and requesting 'Intra-frequency SI Acquisition'. The UE replies with a 'MEASUREMENT REPORT' that includes the 'PSC', 'Cell Identity', and 'CSG Member Indication'. Finally, the SRNC initiates 'Handover processing' as described in reference [6].
+
+Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.
+
+**Figure 8.1.1-1: Intra-frequency Measurement Procedure of CSG and Hybrid cells**
+
+- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type.
+- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation).
+- 3) If a measurement configuration for CSG/hybrid cells is not present, the SRNC configures the UE with relevant measurement configuration which includes the PSCs that the UE must measure and the PSCs for which SI acquisition should be performed. The network may use the CSG proximity indication for intra-frequency case to minimize the time during which measurements for CSG/hybrid cells are configured.
+- 4) The UE sends a measurement report including the measured PSC, Cell Identity, CSG ID and CSG membership indication of the target HNB to the SRNC (e.g., due to a triggered intra-frequency event 1d). The UE can acquire MIB and SIB3/SIB4 of intra-frequency target HNB cells in parallel with reception of the serving cell transmissions in CELL\_DCH. No measurement gaps are required for reading MIB and SIB3/SIB4. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition.
+- 5) SRNC can then proceed with the handover processing as described in [6].
+
+After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements configured.
+
+The PSC confusion is resolved by steps 3 and 4. The SRNC can request SI acquisition and reporting for any PSC, not limited to PSCs of CSG or hybrid cells.
+
+### 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure
+
+![Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant SRNC
+    Note left of UE: 6. UE reads System Information of the target HNB
+    Note right of SRNC: 8. Handover processing [6]
+
+    SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)]
+    UE-->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication]
+    SRNC->>UE: 3. MEASUREMENT CONTROL [ CSG Inter-frequency cell info]
+    UE-->>SRNC: 4. MEASUREMENT REPORT [measured PSCs]
+    SRNC->>UE: 5. MEASUREMENT CONTROL [(report criteria = Periodical reporting criteria), (Amount of reporting = 1), (Inter-frequency SI Acquisition)],
+    UE-->>SRNC: 7. MEASUREMENT REPORT [Cell Identity, CSG Member Indication]
+  
+```
+
+The diagram shows a sequence of interactions between a User Equipment (UE) and a Serving Radio Network Controller (SRNC) for inter-frequency measurement of CSG and hybrid cells. The sequence starts with the SRNC sending a measurement control to the UE with the type set to 'CSG Proximity detection'. The UE responds with a measurement report indicating it may be near a CSG member cell. The SRNC then configures a measurement on the concerned frequency/RAT to measure CSG/hybrid cells, including compressed mode gaps. The UE sends a measurement report with measured PSCs. The SRNC configures the UE for system information (SI) acquisition and reporting of a particular PSC/PCI. The UE reads the system information of the target HNB and sends a measurement report with cell identity and CSG member indication. Finally, the SRNC proceeds with handover processing.
+
+Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.
+
+**Figure 8.1.2-1: Inter-frequency Measurement Procedure of CSG and Hybrid cells.**
+
+- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type.
+- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation). The CSG proximity indication includes the RAT and frequency of the cell.
+- 3) The SRNC configures a measurement on the concerned frequency/RAT to measure CSG/hybrid cells. Compressed mode gaps, if required by the UE, are also activated to allow UE to perform measurements on the reported RAT and frequency. The network may also use the proximity indication to minimize the requesting of handover preparation information of CSG/hybrid cells by avoiding requesting such information when the UE is not in the geographical area where its CSG member cells are located.
+- 4) The UE sends a measurement report including the measured PSCs/PCIs.
+- 5) The SRNC configures the UE to perform SI acquisition and reporting of a particular PSC/PCI.
+- 6) The UE performs SI acquisition using autonomous gaps, i.e., the UE may suspend reception and transmission with the SRNC to acquire the relevant system information from the target HNB/HeNB.
+- 7) The UE sends a measurement report including Cell Identity, CSG ID and CSG membership indication. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition.
+- 8) SRNC can then proceed with the handover processing. The handover processing for inter-frequency handover to a CSG/Hybrid cell is described in [6].
+
+NOTE: The above steps also apply to inter-RAT mobility from UMTS cell to HeNB.
+
+After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements on the reported RAT and frequency.
+
+In the above procedure, step 2 may not be performed in case the UE has not previously visited the HNB, e.g., when the UE first visits a CSG/hybrid cell.
+
+The PSC/PCI confusion is resolved by steps 5, 6 and 7. The SRNC can request SI acquisition and reporting for any PSC/PCI, not limited to PSCs/PCIs of CSG or hybrid cells.
+
+## 8.2 Handover from CSG Cell
+
+In Cell\_DCH state, the handover procedure from a CSG member cell to a non-CSG cell is expected to be the same as the procedure specified in [3].
+
+## 8.3 Handover from CSG Cell to CSG Cell
+
+In Cell\_DCH state, handover between CSG member cells with the same CSG ID is expected to be the same as the procedure specified in Section 8.1.
+
+In Cell\_DCH state, handover between CSG member cells with different CSG IDs is expected to be the same as the procedure specified in Section 8.1.
+
+# --- 9 Support of Hybrid Cells
+
+## 9.1 Measurement Rules
+
+To measure for hybrid cells with a CSG Identity and its associated PLMN ID belonging to an entry in the UE's CSG whitelist, measurement rules of Chapter 7.1 apply. Otherwise, normal measurement rules apply.
+
+NOTE: The autonomous search for hybrid cells does not imply that UE need to constantly check the CSG ID of all cells it sees.
+
+## 9.2 Reselection
+
+In case the UE has CSG ID and its associated PLMN ID of the hybrid cell in its CSG whitelist, cell reselection procedures will be the same as for a CSG cell as described in Chapter 7.2.
+
+For all other UEs, cell reselection procedures will utilise normal cell reselection rules.
+
+# Annex B (informative): Void
+
+# Annex C (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                   |             |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------|-------------|
+| Date           | TSG #   | TSG Doc.  | CR   | Rev | Cat | Subject/Comment                                                   | New version |
+| 2008-11-17     | RAN2#64 |           |      |     |     | Proposal for 25.367 TS structure and Text Proposals               | 0.0.0       |
+| 2008-11-20     | RAN2#64 |           |      |     |     | Revision based on discussion for email agreement.                 | 0.0.1       |
+| 2008-11-21     | RAN2#64 |           |      |     |     | Final text proposals for email agreement.                         | 0.0.2       |
+| 2008-11-25     | RAN2#64 |           |      |     |     | Revision based on email agreement.                                | 1.0.0       |
+| 2008-12        | RP-42   | RP-080873 | -    | -   |     | v1.0.0 was approved at RAN #42 as v8.0.0 and put under CR control | 8.0.0       |
+| 2009-03        | RP-43   | RP-090135 | 0001 | 1   |     | Corrections to manual CSG search                                  | 8.1.0       |
+|                | RP-43   | RP-090135 | 0002 | 1   |     | Allignment to latest stage 3 agreements                           | 8.1.0       |
+| 2009-06        | RP-44   | RP-090524 | 0003 | -   |     | Idle mode requirements to support hybrid cells for HNB            | 9.0.0       |
+| 2009-09        | RP-45   | RP-090930 | 0005 | 4   |     | CR capturing HNB inbound mobility agreements                      | 9.1.0       |
+|                | RP-45   | RP-090911 | 0008 | -   |     | Correction to manual CSG ID selection 25.367CR(R9)                | 9.1.0       |
+| 2009-12        | RP-46   | RP-091343 | 0010 | 1   |     | CR on Add Hybrid cell into the manual CSG ID selection in 25.367  | 9.2.0       |
+|                | RP-46   | RP-091343 | 0011 | 2   |     | Draft CR capturing HNB inbound mobility agreements                | 9.2.0       |
+|                | RP-46   | RP-091343 | 0012 | -   |     | Removal of description related to small repetition of SIB3/4      | 9.2.0       |
+|                | RP-46   | RP-091343 | 0014 | 1   |     | Renaming Allowed CSG List (25.367 Rel-9)                          | 9.2.0       |
+|                | RP-46   | RP-091330 | 0015 | -   |     | Correction to definition of CSG cell.                             | 9.2.0       |
+| 2010-03        | RP-47   | RP-100306 | 0017 | -   |     | CR capturing HNB inbound mobility agreements                      | 9.3.0       |
+| 2010-06        | RP-48   | RP-100551 | 0018 | -   |     | Some corrections to 25.367                                        | 9.4.0       |
+| 2010-12        | RP-50   | RP-101206 | 0019 | -   |     | Correction to the limitation of SI acquisition                    | 9.5.0       |
+| 2011-03        | RP-51   | -         | -    | -   |     | Upgrade to the Release 10 - no technical change                   | 10.0.0      |
+| 2012-06        | RP-56   | RP-120880 | 0026 | -   |     | PSC range note on RAN sharing                                     | 11.0.0      |
+| 2013-03        | RP-59   | RP-130247 | 0028 | 1   |     | Corrections on mobility to CSG and hybrid cells for UMTS          | 11.1.0      |
+| 2013-12        | RP-62   | RP-131998 | 0030 | 1   |     | Introduction of inbound mobility to shared CSG/hybrid cell        | 12.0.0      |
+|                | RP-62   | RP-131998 | 0031 | -   |     | Introduction of CSG CELL_FACH mobility                            | 12.0.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        | SA-80   | -         | -    | -   | -   | Update to Rel-15 version (MCC)                                    | 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/25410/raw.md

@@ -0,0 +1,1102 @@
+
+
+# 3GPP TS 25.410 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 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  
+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  |
+| 3.3 Specification Notations .....                                             | 8  |
+| 4 General Aspects .....                                                       | 9  |
+| 4.1 UTRAN Architecture .....                                                  | 9  |
+| 4.1.1 Iu Interface Architecture.....                                          | 9  |
+| 4.1.2 I <sub>u</sub> connection principles .....                              | 10 |
+| 4.1.3 Implementation of the NAS Node Selection Function.....                  | 10 |
+| 4.1.4 Implementation of MOCN configuration support.....                       | 10 |
+| 4.2 I <sub>u</sub> Interface General Principles .....                         | 10 |
+| 4.3 I <sub>u</sub> Interface Specification Objectives.....                    | 10 |
+| 4.4 I <sub>u</sub> Interface Capabilities.....                                | 11 |
+| 4.5 I <sub>u</sub> Interface Characteristics .....                            | 12 |
+| 4.5.1 Use of Transport Network User Plane as Signalling Bearer .....          | 12 |
+| 4.5.1.1 Use of SCCP.....                                                      | 12 |
+| 4.5.1.1.1 General .....                                                       | 12 |
+| 4.5.1.1.2 SCCP Connection Establishment procedure.....                        | 12 |
+| 4.5.1.1.3 SCCP Connection Release procedure .....                             | 14 |
+| 4.5.1.1.4 General SCCP Abnormal Conditions.....                               | 15 |
+| 4.5.1.2 Use of MTP3b.....                                                     | 15 |
+| 4.5.2 Use of Transport Network User Plane as User Data Bearer.....            | 15 |
+| 4.5.2.1 Use of AAL2.....                                                      | 15 |
+| 4.5.2.2 Use of GTP-U .....                                                    | 15 |
+| 4.5.2.3 Use of RTP.....                                                       | 15 |
+| 4.5.3 Use of Transport Network User Plane on Iu-BC.....                       | 15 |
+| 5 Functions of the I <sub>u</sub> Interface Protocols & Functional Split..... | 16 |
+| 5.1 General .....                                                             | 16 |
+| 5.2 RAB management Functions .....                                            | 18 |
+| 5.2.1 RAB establishment, modification and release function .....              | 18 |
+| 5.2.2 RAB characteristics mapping to Uu bearers function .....                | 18 |
+| 5.2.3 RAB characteristics mapping to I <sub>u</sub> transport bearers.....    | 18 |
+| 5.2.4 RAB queuing, pre-emption and priority function .....                    | 18 |
+| 5.3 Radio Resource Management over I <sub>u</sub> .....                       | 19 |
+| 5.3.1 Radio resource admission control .....                                  | 19 |
+| 5.3.2 Broadcast information management.....                                   | 19 |
+| 5.4 I <sub>u</sub> link Management functions .....                            | 19 |
+| 5.4.1 I <sub>u</sub> Signalling Link Management function .....                | 19 |
+| 5.4.2 ATM Virtual Connection Management function .....                        | 19 |
+| 5.4.3 AAL2 connection establish and release function .....                    | 19 |
+| 5.4.4 AAL5 management function .....                                          | 19 |
+| 5.4.5 GTP-U tunnels management function .....                                 | 19 |
+| 5.4.6 TCP Management Function.....                                            | 20 |
+| 5.4.7 Buffer Management.....                                                  | 20 |
+| 5.4.8 RTP Session Management Function .....                                   | 20 |
+| 5.5 I <sub>u</sub> U-plane (RNL) Management Functions .....                   | 20 |
+| 5.5.1 I <sub>u</sub> U-plane frame protocol mode selection function.....      | 20 |
+| 5.5.2 I <sub>u</sub> U-plane frame protocol initialisation .....              | 20 |
+| 5.6 Mobility Management Functions .....                                       | 20 |
+| 5.6.1 Location information update function .....                              | 20 |
+| 5.6.2 Handover and Relocation functions .....                                 | 21 |
+
+|                               |                                                                                               |           |
+|-------------------------------|-----------------------------------------------------------------------------------------------|-----------|
+| 5.6.2.1                       | Inter RNC hard HO function, Iur not used or not available .....                               | 21        |
+| 5.6.2.2                       | Serving RNS Relocation function.....                                                          | 21        |
+| 5.6.2.3                       | Inter system Handover (e.g. UMTS-GSM) function .....                                          | 21        |
+| 5.6.2A                        | Inter System Change (e.g. UMTS-GSM) function.....                                             | 21        |
+| 5.6.3                         | Paging Triggering .....                                                                       | 21        |
+| 5.6.4                         | Shared Networks Access Control.....                                                           | 21        |
+| 5.6.5                         | GERAN System Information Retrieval.....                                                       | 21        |
+| 5.7                           | Security Functions.....                                                                       | 21        |
+| 5.7.1                         | Data Confidentiality .....                                                                    | 21        |
+| 5.7.1.1                       | Radio interface ciphering function .....                                                      | 21        |
+| 5.7.1.2                       | Ciphering key management function.....                                                        | 22        |
+| 5.7.2                         | Data integrity .....                                                                          | 22        |
+| 5.7.2.1                       | Integrity checking .....                                                                      | 22        |
+| 5.7.2.2                       | Integrity key management .....                                                                | 22        |
+| 5.8                           | Service and Network Access Functions.....                                                     | 22        |
+| 5.8.1                         | Core Network signalling data transfer function .....                                          | 22        |
+| 5.8.2                         | Data Volume Reporting.....                                                                    | 22        |
+| 5.8.3                         | UE Tracing .....                                                                              | 22        |
+| 5.8.4                         | Location reporting function .....                                                             | 22        |
+| 5.8.5                         | MDT .....                                                                                     | 22        |
+| 5.9                           | Co-ordination Functions.....                                                                  | 22        |
+| 5.9.1                         | Paging Co-ordination function .....                                                           | 22        |
+| 5.9.2                         | NAS Node Selection Function .....                                                             | 23        |
+| 5.9.3                         | Information Transfer Function .....                                                           | 23        |
+| 5.9.4                         | MOCN Rerouting Function.....                                                                  | 23        |
+| 5.9.5                         | SIPTO at Iu-PS Function.....                                                                  | 23        |
+| 5.9.6                         | SIPTO at the Local Network with Standalone GW.....                                            | 23        |
+| 5.10                          | MBMS Functions.....                                                                           | 23        |
+| 5.10.1                        | MBMS RAB Management functions .....                                                           | 23        |
+| 5.10.2                        | MBMS UE Linking Function.....                                                                 | 23        |
+| 5.10.3                        | MBMS Registration Control Function .....                                                      | 23        |
+| 5.10.4                        | MBMS Enquiry Function .....                                                                   | 24        |
+| 6                             | I <sub>u</sub> Interface Protocol Structure.....                                              | 24        |
+| 6.1                           | General .....                                                                                 | 24        |
+| 6.2                           | Iu-CS .....                                                                                   | 25        |
+| 6.3                           | Iu-BC.....                                                                                    | 25        |
+| 6.4                           | Iu-PS .....                                                                                   | 27        |
+| 7                             | Other I <sub>u</sub> Interface Specifications .....                                           | 27        |
+| 7.1                           | UTRAN I <sub>u</sub> Interface: Layer 1 (3GPP TS 25.411) .....                                | 27        |
+| 7.2                           | UTRAN I <sub>u</sub> Interface: Signalling Transport (3GPP TS 25.412) .....                   | 27        |
+| 7.3                           | UTRAN I <sub>u</sub> Interface: RANAP Specification (3GPP TS 25.413).....                     | 27        |
+| 7.4                           | UTRAN I <sub>u</sub> Interface: Data Transport and Transport Signalling (3GPP TS 25.414)..... | 28        |
+| 7.5                           | UTRAN I <sub>u</sub> Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415).....            | 28        |
+| 7.6                           | UTRAN I <sub>u</sub> Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419) .....   | 28        |
+| 7.7                           | Summary .....                                                                                 | 28        |
+| <b>Annex A (informative):</b> | <b>Change History.....</b>                                                                    | <b>29</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 3GPP TS 25.41x series of Technical Specifications that define the Iu interface for the interconnection of Radio Network Controller (RNC) component of the UMTS Terrestrial Radio Access Network (UTRAN) to the Core Network of 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 TR 23.930: "Iu Principles".
+- [3] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions".
+- [4] 3GPP TS 25.411: "UTRAN Iu Interface Layer 1".
+- [5] 3GPP TS 25.412: "UTRAN Iu Interface Signalling Transport".
+- [6] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
+- [7] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling".
+- [8] 3GPP TS 25.415: "UTRAN Iu Interface User Plane Protocols".
+- [9] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [10] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages".
+- [11] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [12] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [13] 3GPP TS 23.003: "Numbering, Addressing and Identification".
+- [14] 3GPP TS 25.419: "UTRAN Iu Interface: Service Area Broadcast Protocol SABP".
+- [15] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2".
+- [16] ITU-T Recommendation Q.2630.1: "AAL type 2 signalling protocol - (Capability Set 1)".
+- [17] ITU-T Recommendation Q.2630.2: "AAL type 2 signalling protocol - Capability Set 2".
+- [18] IETF RFC 3332 (2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)".
+- [19] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications".
+- [20] IETF RFC 768 (1980-08): "User Datagram Protocol".
+
+- [21] IETF RFC 793 (1981-09): "TCP, Transmission Control Protocol".
+- [22] IETF RFC 791 (1981-09): "Internet Protocol".
+- [23] Void
+- [24] Void
+- [25] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
+- [26] 3GPP TS 23.251: "Network sharing; Architecture and functional description".
+- [27] 3GPP TS23.246: Multimedia Broadcast/Multicast Service (MBMS) Architecture and functional description
+- [28] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
+- [29] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [30] 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".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TS 25.401 [1] apply.
+
+### **MBMS related terms and definitions:**
+
+**MBMS bearer service:** as defined in TS 23.246 [27].
+
+**MBMS RAB:** as defined in TS 25.346 [28].
+
+**MBMS Iu signalling connection:** as defined in TS 25.346 [28].
+
+**MBMS session start:** as defined in TS 25.346 [28].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                      |
+|---------|------------------------------------------------------|
+| 3G-MSC  | 3 <sup>rd</sup> Generation Mobile Switching Centre   |
+| 3G-SGSN | 3 <sup>rd</sup> Generation Serving GPRS Support Node |
+| AAL     | ATM Adaptation Layer                                 |
+| ATM     | Asynchronous Transfer Mode                           |
+| BC      | Broadcast                                            |
+| BSSMAP  | Base Station Subsystem Management Application Part   |
+| CBS     | Cell Broadcast Service                               |
+| CC      | Connection Confirm                                   |
+| CN      | Core Network                                         |
+| CR      | Connection Release                                   |
+| CREF    | Connection Refusal                                   |
+| CS      | Circuit Switched                                     |
+| GT      | Global Title                                         |
+| GTP-U   | GPRS Tunnelling Protocol                             |
+| GWCN    | Gateway Core Network                                 |
+| IMSI    | International Mobile Subscriber Identity             |
+| IP      | Internet Protocol                                    |
+
+|          |                                                  |
+|----------|--------------------------------------------------|
+| ISDN     | Integrated Services Digital Network              |
+| L-GW     | Local GateWay                                    |
+| LA       | Location Area                                    |
+| M3UA     | MTP3 User Adaptation Layer                       |
+| MBMS     | Multimedia Broadcast Multicast Service           |
+| MDT      | Minimization of Drive-Tests                      |
+| MOCN     | Multi Operator Core Network                      |
+| NAS      | Non Access Stratum                               |
+| NACC     | Network Assisted Cell Change                     |
+| NNSF     | NAS Node Selection Function                      |
+| O&M      | Operation and Maintenance                        |
+| PLMN     | Public Land Mobile Network                       |
+| PS       | Packet Switched                                  |
+| PSTN     | Public Switched Telephone Network                |
+| PVC      | Permanent Virtual Circuit                        |
+| QoE      | Quality of Experience                            |
+| QoS      | Quality of Service                               |
+| RA       | Routing Area                                     |
+| RAB      | Radio Access Bearer                              |
+| RANAP    | Radio Access Network Application Part            |
+| RIM      | RAN Information Management                       |
+| RLP      | Radio Link Protocol                              |
+| RNC      | Radio Network Controller                         |
+| RNL      | Radio Network Layer                              |
+| RRC      | Radio Resource Control                           |
+| RTCP     | Real Time Control Protocol                       |
+| RTP      | Real Time Protocol                               |
+| SA       | Service Area                                     |
+| SABP     | Service Area Broadcast Protocol                  |
+| SAP      | Service Access Point                             |
+| SCCP     | Signalling Connection Control Part               |
+| SIPTO    | Selected IP Traffic Offload                      |
+| SIPTO@LN | Selected IP Traffic Offload at the Local Network |
+| SCTP     | Stream Control Transmission Protocol             |
+| SNA      | Shared Network Area                              |
+| SPC      | Signalling Point Code                            |
+| SRNS     | Serving Radio Network Subsystem                  |
+| SSN      | Sub-System Number                                |
+| SVC      | Switched Virtual Circuit                         |
+| S-GW     | Serving GateWay                                  |
+| TCP      | Transmission Control Protocol                    |
+| UE       | User Equipment                                   |
+| UDP      | User Datagram Protocol                           |
+| UP       | User Plane                                       |
+| URA      | UTRAN Registration Area                          |
+| UTRAN    | UMTS Terrestrial Radio Access Network            |
+| VC       | Virtual Circuit                                  |
+
+## 3.3 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. 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 UTRAN Architecture
+
+### 4.1.1 Iu Interface Architecture
+
+The overall UMTS architecture and UTRAN architectures are described in TS 25.401 [1]. This subclause specifies only the architecture of the Iu interface, and shall not constrain the network architecture of either Core or Radio Access Networks.
+
+The Iu interface is specified at the boundary between the Core Network and UTRAN. Figure 4.1 depicts the logical division of the Iu interface. From the Iu perspective, the UTRAN access point is an RNC.
+
+![Figure 4.1: Iu Interface Architecture diagram showing UTRAN (Node B, RNC) connected to Core Network (CN) domains (CS, PS, BC) via the Iu interface.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg)
+
+The diagram illustrates the Iu Interface Architecture. On the left, the UTRAN (Radio Access Network) contains four Node B units connected to two RNC (Radio Network Controller) units. The RNC units are connected to the Core Network (CN) on the right via the Iu interface, which is represented by a vertical dashed line. The CN is divided into three domains: CS (Circuit Switched) Domain, PS (Packet Switched) Domain, and BC (Broadcast) Domain. The Iu interface is logically divided into three segments: Iu-CS (towards the CS Domain), Iu-PS (towards the PS Domain), and Iu-BC (towards the BC Domain). The RNC units are connected to these segments as follows: the top RNC connects to Iu-CS and Iu-PS, while the bottom RNC connects to Iu-PS and Iu-BC.
+
+Figure 4.1: Iu Interface Architecture diagram showing UTRAN (Node B, RNC) connected to Core Network (CN) domains (CS, PS, BC) via the Iu interface.
+
+Figure 4.1: Iu Interface Architecture
+
+The Iu interface towards the PS-domain of the core network is called Iu-PS, and the Iu interface towards the CS-domain is called Iu-CS. The differences between Iu-CS and Iu-PS are treated elsewhere in the present document. The Iu interface to the Broadcast domain is called Iu-BC.
+
+There shall not be more than one Iu interface (Iu-PS) towards the PS-domain from any one RNC – except where the NNSF is used, see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. Each RNC shall not have more than one Iu interface (Iu-CS) towards its default CN node within the CS domain, but may also have further Iu interfaces (Iu-CS) towards other CN nodes within the CS domain. (See [6] for definition of Default CN node.) These further Iu interfaces (Iu-CS) shall only be used as a result of intra-MSC inter-system handover or SRNS relocation, in the case the anchor CN node directly connects to the target RNC. There may also be more than one Iu interface towards the CS-Domain if the NNSF is used – see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. There shall not be more than one Iu interface (Iu-BC) from an RNC towards the Broadcast domain.
+
+In the separated core network architecture, this means that there shall be separate signalling and user data connections towards the PS and CS domains – this applies in both transport and radio network layers.
+
+In the combined architecture, there shall be separate connections in the user plane towards the PS and CS domains (in both transport and radio network layers). In the control plane, there shall be separate SCCP connections to the two logical domains.
+
+In either architecture, there can be several RNCs within UTRAN and so UTRAN may have several I<sub>u</sub> access points towards the Core Network. As a minimum, each I<sub>u</sub> access point (in UTRAN or CN) shall independently fulfil the requirements of the relevant I<sub>u</sub> specifications (25.41x series – see clause 7).
+
+### 4.1.2 I<sub>u</sub> connection principles
+
+The I<sub>u</sub> interface has a hierarchical architecture where one higher layer entity controls several lower layer entities. The hierarchy for the CN - UTRAN signalling connection end points is described below:
+
+- Each CN Access Point may be connected to one or more UTRAN Access Points.
+- For the PS domain, each UTRAN Access Point shall not be connected to more than one CN Access Point – except where the NNSF is used, see subclause 4.1.3, or when RNC is shared in MOCN configuration..
+- For the CS domain, each UTRAN Access Point may be connected to one or more CN Access Points.
+- For the BC domain, each UTRAN Access Point may be connected to one CN Access Point only.
+
+### 4.1.3 Implementation of the NAS Node Selection Function
+
+The optional NAS Node Selection Function (NNSF) is described in TS 23.236 [25].
+
+If the NAS Node Selection Function is used by an RNC:
+
+- There may be more than one I<sub>u</sub> interface (I<sub>u</sub>-CS) towards the CS domain and/or more than one I<sub>u</sub> interface (I<sub>u</sub>-PS) towards the PS-domain from this RNC.
+
+### 4.1.4 Implementation of MOCN configuration support
+
+The MOCN configuration is described in TS 23.251 [26]. When the RNC is shared in MOCN configuration:
+
+- There may be more than one I<sub>u</sub> interface (I<sub>u</sub>-CS) towards the CS domain of different CN operators and/or more than one I<sub>u</sub> interface (I<sub>u</sub>-PS) towards the PS-domain of different CN operators from this RNC.
+- The MOCN Rerouting Function shall be supported.
+
+## 4.2 I<sub>u</sub> Interface General Principles
+
+From a UTRAN perspective, maximising the commonality of the various protocols that flow on the I<sub>u</sub> interface is desirable. This means at the minimum that:
+
+- A common set of radio access bearer services will be offered by UTRAN to the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN).
+
+There will be a common functional split between UTRAN and the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN).
+
+Signalling in the radio network control plane shall not depend on the specific choice of transport layers.
+
+## 4.3 I<sub>u</sub> Interface Specification Objectives
+
+The following objectives are partly derived from TR 23.930 [2].
+
+The I<sub>u</sub> interface shall be specified such that it can support:
+
+- the interconnection of RNCs with Core Network Access Points within a single PLMN, and within several PLMNs in case of network sharing, as described in TS 23.251 [26].
+
+- the interconnection of RNCs with Core Network Access Points irrespective of the manufacturer of any of the elements.
+- all UMTS services.
+
+The I<sub>u</sub> interface shall facilitate the use of the same RNC, MSC or SGSN in all PLMNs.
+
+The I<sub>u</sub> interface shall facilitate the sharing of transport technology between Iu-PS and Iu-BC.
+
+The I<sub>u</sub> interface shall allow interworking to the GSM Core Network.
+
+Independence between the protocol layers and between control and user planes shall be maintained on the Iu interface.
+
+The I<sub>u</sub> interface shall allow independent evolution of technologies within the Core, Radio Access and Transport Networks.
+
+The I<sub>u</sub> interface shall allow separate evolution of O&M facilities.
+
+The I<sub>u</sub> interface shall be standardised as an open and multi-vendor interface.
+
+The Iu interface specifications shall facilitate the migration of some services from the CS-domain to the PS-domain. In particular, the RANAP protocol shall be common to both PS and CS domains, and the I<sub>u</sub> user plane protocol(s) shall be independent of the core network domain (PS or CS), except where a specific feature is only required for one domain.
+
+## 4.4 I<sub>u</sub> Interface Capabilities
+
+The following capabilities are derived from the requirements described in TR 23.930 [2].
+
+The I<sub>u</sub> interface supports:
+
+- procedures to establish, maintain and release Radio Access Bearers;
+- procedures to perform SRNS relocation, intra-system handover, inter-system handover and inter-system change;
+- procedures to support the Cell Broadcast service;
+- a set of general procedures, not related to a specific UE;
+- the separation of each UE on the protocol level for user specific signalling management;
+- the transfer of NAS signalling messages between UE and CN;
+- location services by transferring requests from the CN to UTRAN, and location information from UTRAN to CN. The location information may comprise a geographical area identifier or global co-ordinates with uncertainty parameters;
+- simultaneous access to multiple CN domains for a single UE;
+- mechanisms for resource reservation for packet data streams;
+- procedures to support MBMS bearer services;
+- mechanisms to support SIPTO at Iu-PS for a specific UE (optional);
+- mechanisms to support SIPTO at the Local Network with standalone GW for a specific UE (optional).
+
+## 4.5 I<sub>u</sub> Interface Characteristics
+
+### 4.5.1 Use of Transport Network User Plane as Signalling Bearer
+
+#### 4.5.1.1 Use of SCCP
+
+##### 4.5.1.1.1 General
+
+The SCCP (ITU-T Rec. Q.711 [9] /ITU-T Rec. Q.712 [10]/ITU-T Rec. Q.713 [11]/ITU-T Rec. Q.714 [12]) is used to support signalling messages between the CNs and the RNC. One user function of the SCCP, called Radio Access Network Application Part (RANAP), is defined. The RANAP uses one SCCP signalling connection per active UE and CN for the transfer of layer 3 messages. RANAP also uses one SCCP signalling connection per MBMS bearer service.
+
+Both connectionless and connection-oriented procedures are used to support the RANAP. TS 25.413 [6] explains whether connection oriented or connectionless services should be used for each layer 3 procedure.
+
+RANAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. Which of the available addressing scheme to use for the SCCP is an operator matter.
+
+When GT addressing is utilised, the following settings shall be used:
+
+- SSN Indicator = 1 (RANAP SSN as defined in TS 23.003 [13] shall always be included).
+- 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.
+
+The following subclauses describe the use of SCCP connections for RANAP transactions. Subclause 4.5.1.2 describes the connection establishment procedures. Subclause 4.5.1.3 describes the connection release procedures. Subclause 4.5.1.4 describes abnormal conditions.
+
+##### 4.5.1.1.2 SCCP Connection Establishment procedure
+
+A new SCCP connection is established when information related to the communication between a UE and the network has to be exchanged between RNC and CN, and no SCCP connection exists between the CN and the RNC involved, for the concerned UE. A new SCCP connection is also established for MBMS service purpose between the RNC and CN.
+
+Various SCCP connection establishment cases have to be distinguished:
+
+- i) RNC Initiated SCCP Signalling Connection for a UE;
+- ii) CN Initiated SCCP Signalling Connection for a UE;
+- iii) CN Initiated SCCP Signalling Connection for an MBMS Service.
+
+The above cases are the only cases currently identified for SCCP connection establishment. Others may emerge in the future.
+
+###### 4.5.1.1.2.1 Establishment procedure in case i
+
+The SCCP signalling connection establishment is initiated, by the RNC, at the reception of the first layer 3 non access stratum message from the UE or at the execution of the enhanced relocation or at the initiation of the UE Registration Query procedure.
+
+###### Initiation
+
+The RNC sends SCCP CONNECTION REQUEST message to the Core Network. A RANAP message shall be included in the user data field of the SCCP CONNECTION REQUEST message when the RANAP message size is less than or equal to the maximum size of the user data field in the SCCP CONNECTION REQUEST message. When the RANAP message is longer than the maximum size, the user data field shall not be included in the SCCP CONNECTION REQUEST message.
+
+If the Core Network receives an SCCP CONNECTION REQUEST message for a UE for which an SCCP connection already exists, or if the Core Network receives an SCCP CONNECTION REQUEST message that does not include a user data field, and later finds out that the SCCP CONNECTION REQUEST message was for a UE for which an SCCP connection already exists, the Core Network shall ensure that the new SCCP connection and the already existing SCCP connection are for the same UE, e.g. by security functions, and if so, release the already existing SCCP connection via the normal Iu Release procedure and all UTRAN resources allocated to it.
+
+###### Termination
+
+- **successful outcome**
+  - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP 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 RANAP message in the user data field.
+
+For more information on how the RANAP procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query are handled, please see the elementary procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query in TS 25.413 [6].
+
+![](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg)
+
+| RNC                                                                                                                                                        | CN |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| CR {SSN=RANAP, a1=x, RANAP message or no user data}<br>----->                                                                                              |    |
+| CC {a1=y, a2=x, RANAP message or no user data}<br><-----                                                                                                   |    |
+| or                                                                                                                                                         |    |
+| CREF{a2=x, RANAP message or no user data}<br><-----                                                                                                        |    |
+| a1 = source local reference,<br>a2 = destination local reference,<br>x = SCCP connection reference at the RNC,<br>y = SCCP connection reference at the CN. |    |
+
+**Figure 4.2: Setting-up of RNC Initiated SCCP Signalling Connection**
+
+###### 4.5.1.1.2.2 Establishment procedure in case ii
+
+The SCCP signalling connection establishment is initiated, by the Core Network, in connection with performing a Relocation.
+
+###### Initiation
+
+The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be 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 connection oriented RANAP message in the user data field, is returned to the Core Network.
+- **unsuccessful outcome**
+  - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field.
+
+![Sequence diagram showing the setting-up of a CN Initiated SCCP Signalling Connection between RNC and CN. The RNC sends a CR message to the CN. The CN responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the RNC, and y is SCCP connection reference at the CN.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+```
+
+sequenceDiagram
+    participant RNC
+    participant CN
+    Note right of RNC: a1 = source local reference,  
+a2 = destination local reference,  
+x = SCCP connection reference at the RNC,  
+y = SCCP connection reference at the CN.
+    RNC->>CN: CR {SSN=RANAP, a1=y, RANAP message or no user data}
+    Note left of CN: <-----
+    CN-->>RNC: CC {a1=x, a2=y, RANAP message or no user data}
+    Note right of CN: ----->
+    Note left of CN: or
+    CN-->>RNC: CREF{a2=y, RANAP message or no user data}
+    Note right of CN: ----->
+  
+```
+
+Sequence diagram showing the setting-up of a CN Initiated SCCP Signalling Connection between RNC and CN. The RNC sends a CR message to the CN. The CN responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the RNC, and y is SCCP connection reference at the CN.
+
+**Figure 4.3: Setting-up of CN Initiated SCCP Signalling Connection**
+
+###### 4.5.1.1.2.3 Establishment procedure in case iii
+
+The SCCP signalling connection establishment is initiated, by the Core Network, to establish a new SCCP connection between the RNC and the CN for an MBMS service at the start of an MBMS session and when no SCCP connection already exists between the CN and the RNC involved, for the concerned MBMS service.
+
+###### Initiation
+
+The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be 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 connection oriented RANAP message in the user data field, is returned to the Core Network.
+- **unsuccessful outcome**
+  - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field.
+
+##### 4.5.1.1.3 SCCP Connection Release procedure
+
+This procedure is always initiated at the Core Network side in normal release case.
+
+An SCCP connection is released when the CN realises that a given signalling connection is no longer required.
+
+The CN sends a SCCP RELEASED message.
+
+The procedure may be initiated at the Core Network side and the RNC side in any abnormal release case.
+
+##### 4.5.1.1.4 General SCCP Abnormal Conditions
+
+If a user-out-of-service information or signalling-point-inaccessible information is received by the RANAP, 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 RANAP procedures are being performed or while a dedicated resource is still allocated, the following actions are taken:
+
+###### At RNC:
+
+- Any RNC procedure relating to that connection is abandoned.
+- The UTRAN resources allocated to the connection are released.
+
+###### At Core Network:
+
+- The resources associated with the SCCP connection are cleared as soon as possible.
+
+#### 4.5.1.2 Use of MTP3b
+
+- For a given MSC, the RNC shall be able to access RANAP and ALCAP either under the same MTP3b (IETF RFC 3332 [18]) destination point code, or under different point codes;
+- For a given RNC, the MSC shall be able to access RANAP and ALCAP either under the same MTP3b destination point code, or under different point codes.
+
+### 4.5.2 Use of Transport Network User Plane as User Data Bearer
+
+#### 4.5.2.1 Use of AAL2
+
+In the ATM transport option AAL2 is used as the user data bearer towards the CS domain.
+
+Q.2630.2 is used as the protocol for dynamically setup AAL-2 connections over Iu towards the CS domain. Q.2630.2 adds new optional capabilities to Q.2630.1.
+
+#### 4.5.2.2 Use of GTP-U
+
+GTP-U is used as the user data bearer towards the PS domain.
+
+RANAP Signalling is used to establish, modify and release the GTP-U tunnels towards the PS domain.
+
+#### 4.5.2.3 Use of RTP
+
+RTP/UDP/IP (IETF RFC 1889 [19]/ IETF RFC 768 [20]/ IETF RFC 791[22]) is used as the user data bearer towards the CS domain in the IP transport option. The use of RTCP (IETF RFC 1889 [19]) is optional.
+
+RANAP Signalling is used to establish, modify and release RTP sessions towards the CS domain.
+
+### 4.5.3 Use of Transport Network User Plane on Iu-BC
+
+TCP/IP (IETF RFC 793[21]/ IETF RFC 791[22]) is used as the bearer for the radio network layer protocol over I<sub>u</sub>-BC.
+
+The TCP connection is normally established by the CN using standard TCP procedures.
+
+A new TCP connection is established by the RNC only when there is information (e.g. failure or restart indications) that needs to be sent from RNC to the CN, and there is no existing TCP connection. The RNC shall establish the connection using standard TCP procedures.
+
+The node that established the connection shall release the TCP connection.
+
+# --- 5 Functions of the I<sub>u</sub> Interface Protocols & Functional Split
+
+## 5.1 General
+
+This subclause defines the functional split between the core network and the UMTS radio access network. In addition, the possible interaction between the functions is defined. The functional split is shown in table 5.1.
+
+Table 5.1: Iu interface functional split
+
+| Function                                            | UTRAN | CN |
+|-----------------------------------------------------|-------|----|
+| <b>RAB management functions:</b>                    |       |    |
+| RAB establishment, modification and release         | X     | X  |
+| RAB characteristics mapping Iu transmission bearers | X     |    |
+| RAB characteristics mapping Uu bearers              | X     |    |
+| RAB queuing, pre-emption and priority               | X     | X  |
+| <b>Radio Resource Management functions:</b>         |       |    |
+| Radio Resource admission control                    | X     |    |
+| Broadcast Information                               | X     | X  |
+| <b>Iu link Management functions:</b>                |       |    |
+| Iu signalling link management                       | X     | X  |
+| ATM VC management                                   | X     | X  |
+| AAL2 establish and release                          | X     | X  |
+| AAL5 management                                     | X     | X  |
+| GTP-U Tunnels management                            | X     | X  |
+| TCP Management                                      | X     | X  |
+| Buffer Management                                   | X     |    |
+| <b>Iu U-plane (RNL) Management:</b>                 |       |    |
+| Iu U-plane frame protocol management                |       | X  |
+| Iu U-plane frame protocol initialization            | X     |    |
+| <b>Mobility management functions:</b>               |       |    |
+| Location information reporting                      | X     | X  |
+| Handover and Relocation                             |       |    |
+| Inter RNC hard HO, Iur not used or not available    | X     | X  |
+| Serving RNS Relocation (intra/inter MSC)            | X     | X  |
+| Inter system hard HO (UMTS-GSM)                     | X     | X  |
+| Inter system Change (UMTS-GSM)                      | X     | X  |
+| Paging Triggering                                   |       | X  |
+| GERAN System Information Retrieval                  | X     | X  |
+| <b>Security Functions:</b>                          |       |    |
+| Data confidentiality                                |       |    |
+| Radio interface ciphering                           | X     |    |
+| Ciphering key management                            |       | X  |
+| User identity confidentiality                       | X     | X  |
+| Data integrity                                      |       |    |
+| Integrity checking                                  | X     |    |
+| Integrity key management                            |       | X  |
+| <b>Service and Network Access functions:</b>        |       |    |
+| CN Signalling data                                  | X     | X  |
+| Data Volume Reporting                               | X     |    |
+| UE Tracing                                          | X     | X  |
+| MDT                                                 | X     | X  |
+| Location reporting                                  | X     | X  |
+| QoE                                                 | X     | X  |
+| <b>Iu Co-ordination functions:</b>                  |       |    |
+| Paging co-ordination                                | X     | X  |
+| NAS Node Selection Function                         | X     |    |
+| MOCN Rerouting Function                             | X     | X  |
+| SIPTO at Iu-PS                                      | X     | X  |
+| SIPTO at the Local Network with Standalone GW       | X     | X  |
+| <b>MBMS functions</b>                               | X     | X  |
+| MBMS RAB Management                                 | X     | X  |
+| MBMS UE Linking Function                            | X     | X  |
+| MBMS Registration Control Function                  | X     | X  |
+
+| Function              | UTRAN | CN |
+|-----------------------|-------|----|
+| MBMS Enquiry Function | X     | X  |
+
+## 5.2 RAB management Functions
+
+### 5.2.1 RAB establishment, modification and release function
+
+The RAB, Radio Access Bearer, is defined to be set-up between UE and CN. Depending on subscription, service, requested QoS etc. different types of RABs will be used. It is the CN that controls towards the UTRAN the establishment, modification or release of a RAB. Furthermore, the CN selects the type of the transport bearer, i.e. ATM or IP.
+
+The RAB identity is allocated by CN by mapping the value for the NAS Binding information (from the actual protocol IE for the respective CN domain) to the RAB ID as specified in TS 23.110 [3]. The RAB identity is globally significant on both the radio bearer and on the Iu bearer for a given UE in a particular CN domain.
+
+RAB establishment, modification and release is a CN initiated function.
+
+RAB establishment, modification and release is a UTRAN executed function.
+
+RAB release request is a UTRAN initiated function, triggered when UTRAN e.g. fails to keep the RAB established with the UE.
+
+### 5.2.2 RAB characteristics mapping to Uu bearers function
+
+The RAB characteristics mapping function is used to map the radio access bearers to the Uu bearers. The mapping is performed during the establishment of the RAB. UTRAN shall perform the mapping between the bearers.
+
+RAB mapping to Uu transmission bearers is a UTRAN function.
+
+### 5.2.3 RAB characteristics mapping to Iu transport bearers
+
+The RAB characteristics mapping function is used to map the radio access bearers to the Iu interface transport bearers. The mapping is performed during the establishment of the RAB.
+
+UTRAN shall perform this mapping between the bearers if AAL2 is used, since it is the UTRAN that establishes the AAL2 connections.
+
+In case of RAB towards the PS domain, UTRAN shall perform the mapping between the radio access bearers and the IP layer.
+
+RAB characteristics mapping to Iu transport bearers is a UTRAN function.
+
+### 5.2.4 RAB queuing, pre-emption and priority function
+
+The allocation/retention priority level of a RAB is determined by the CN based on e.g. subscription information, QoS information etc. Accordingly, the CN shall request RAB establishment or modification with an indication of the priority level and the pre-emption capability of that RAB and the queuing vulnerability. Queuing and resource pre-emption shall be performed by UTRAN accordingly.
+
+RAB queuing, pre-emption and allocation/retention priority handling is a UTRAN controlled function.
+
+RAB queuing, pre-emption and allocation/retention priority setting is a CN function.
+
+## 5.3 Radio Resource Management over Iu
+
+### 5.3.1 Radio resource admission control
+
+When UTRAN receives a request to establish or modify a radio access bearer from the CN, the current radio resource situation is analysed and the admission control either accepts or rejects the request. This is called "Radio resource admission control" and is handled by the UTRAN. If the request is queued, it is handled by the RAB queuing, pre-emption and priority function.
+
+### 5.3.2 Broadcast information management
+
+This function consists in the broadcast from network toward UE of some information in the coverage area of the whole network or different parts of the network.
+
+There are two kinds of Broadcast information management. UTRAN broadcast information, and Cell Broadcast information management. All UTRAN broadcast information management shall be handled locally within UTRAN. All Cell Broadcast information is controlled by CN and executed by UTRAN.
+
+## 5.4 I<sub>u</sub> link Management functions
+
+### 5.4.1 I<sub>u</sub> Signalling Link Management function
+
+The I<sub>u</sub> signalling link management function provides a reliable transfer of the radio network signalling between UTRAN and CN. Both CN and UTRAN manage the function.
+
+This function is in particular responsible for I<sub>u</sub> signalling connection establishment, which can be established either by the CN or the RNC and for I<sub>u</sub> signalling connection release, which is controlled by CN possibly upon UTRAN request.
+
+### 5.4.2 ATM Virtual Connection Management function
+
+This function refers to handling of ATM Virtual Connections (VCs) between CN and UTRAN.
+
+This function shall be used to establish, maintain and release the ATM VCs. For permanent VCs, it is regarded to be an O&M function.
+
+This function also includes the selection of a Virtual Circuit to be used for a particular RAB. The selection of ATM VC upon an I<sub>u</sub> radio access bearer service request, shall be done by UTRAN. The selected VC shall fulfil the requirements of the request. The VC may consist of several sublinks: such as SCCP connections, AAL2 connections or IP flows.
+
+### 5.4.3 AAL2 connection establish and release function
+
+This function is used to establish and release the AAL type 2 connections between CN and UTRAN upon an I<sub>u</sub> radio access bearer service request. Both UTRAN and CN are taking part in the establishment of AAL2 connection. UTRAN shall initiate both establishment and release of AAL2 connections. In abnormal cases, the CN may also initiate release of AAL2 connections. The use of AAL2 for I<sub>u</sub> transmission bearers depends on type of CN.
+
+### 5.4.4 AAL5 management function
+
+AAL5 connections between CN and UTRAN shall be pre-configured at system initialisation. Basic configuration is PVCs. For user data, SVC is possible.
+
+The AAL5 management is a function handled by both the CN and the UTRAN.
+
+### 5.4.5 GTP-U tunnels management function
+
+This function is used to establish and release GTP-U tunnels between CN and UTRAN upon a radio access bearer service request. This involves assigning a tunnel identifier for each direction and the creation of a context containing the tunnel information. The tunnel identifier for the downlink is allocated by the UTRAN, and the tunnel identifier for the
+
+uplink is allocated by the CN. Both CN and UTRAN should maintain the context. The use of GTP-U for I<sub>u</sub> transport bearers depends on type of CN.
+
+### 5.4.6 TCP Management Function
+
+This function is used to establish and release the TCP connections between CN and UTRAN over I<sub>u</sub>-BC.
+
+The TCP management function exists in both UTRAN and CN.
+
+### 5.4.7 Buffer Management
+
+Congestion control shall be performed over the I<sub>u</sub> user plane using buffer management and no flow control.
+
+This function includes buffers to store received packet data units that at reception can not be processed due to e.g. congestion. In UTRAN, there must be a buffer management function handling received packets from the peer CN node.
+
+The used mechanism is not in the scope of the present document and not relevant to be standardised.
+
+Buffer management is a UTRAN function.
+
+### 5.4.8 RTP Session Management Function
+
+This function is used to establish and release RTP sessions between CN and UTRAN upon a radio access bearer service request. This involves assigning a RTP session identifier for each direction and the creation of a context containing the RTP session information. The RTP session identifier for the downlink is allocated by the UTRAN, and the RTP session identifier for the uplink is allocated by the CN. Both CN and UTRAN should maintain the RTP session context. The use of RTP for I<sub>u</sub> transport bearers depends on type of CN.
+
+## 5.5 I<sub>u</sub> U-plane (RNL) Management Functions
+
+### 5.5.1 I<sub>u</sub> U-plane frame protocol mode selection function
+
+The I<sub>u</sub> UP in the Radio Network Layer provides modes of operation that can be activated on RAB basis. For a given RAB, the I<sub>u</sub> UP operates either in a Transparent or in Support mode. I<sub>u</sub> U-plane frame protocol mode is selected by the CN. A set of appropriate U-plane version(s) is indicated within RANAP. The final U-plane version is selected during the I<sub>u</sub> UP initiation procedure among the indicated version(s).
+
+This function is a CN function.
+
+### 5.5.2 I<sub>u</sub> U-plane frame protocol initialisation
+
+I<sub>u</sub> U-plane frame protocol is initialised by the UTRAN. In certain cases, as described in TS 23.153 [15], the I<sub>u</sub> U-plane frame protocol may be initialised by the CN.
+
+## 5.6 Mobility Management Functions
+
+### 5.6.1 Location information update function
+
+Some functionality within the CN, needs information about the present location of an active UE, i.e. a UE with established signalling connection. The Location information update function is used to transfer this information from the UTRAN to the CN. It is the UTRAN responsibility to send this information initially at the signalling connection establishment for a UE and at any change of the UE location as long as the signalling connection exists. For this function, the location information shall be at Location and Routing Area level.
+
+### 5.6.2 Handover and Relocation functions
+
+#### 5.6.2.1 Inter RNC hard HO function, Iur not used or not available
+
+This functionality includes procedures for handover from one RNC to another RNC when Iur interface is not used or is not available, i.e. soft handover is not possible. The connection is switched in the CN, so both UTRAN and CN are involved. Both intra and inter CN entity cases are applicable. This functionality includes also the moving of the Serving RNS functionality from one RNC to another RNC.
+
+#### 5.6.2.2 Serving RNS Relocation function
+
+This functionality allows moving the Serving RNS functionality from one RNC to another RNC, e.g. closer to where the UE has moved during the communication. The Serving RNS Relocation procedure may be applied when active cell management functionality has created a suitable situation for it. Both UTRAN and CN are involved.
+
+#### 5.6.2.3 Inter system Handover (e.g. UMTS-GSM) function
+
+Inter system handover is performed when a mobile hands over between cells belonging to different systems such as GSM and UMTS. For intersystem handover between UMTS and GSM, the GSM procedures are used within the GSM network. Both UTRAN and CN are involved.
+
+NOTE: The GSM BSSMAP procedures are outside the scope of the present document.
+
+### 5.6.2A Inter System Change (e.g. UMTS-GSM) function
+
+Inter system change is performed when a GPRS attached mobile moves from cells belonging to different systems such as GSM and UMTS. For intersystem change between UMTS and GSM, the GPRS procedures are used within the GPRS network. Both UTRAN and CN are involved.
+
+### 5.6.3 Paging Triggering
+
+The Core Network shall, when considered necessary, trigger the Location/Routing/RNC Area paging in the UTRAN system.
+
+### 5.6.4 Shared Networks Access Control
+
+The Shared Networks Access Control function allows the CN to request the UTRAN to apply UE specific access control to the UTRAN and the neighbouring networks on a PLMN or an SNA basis. The Shared Networks Access Control function is further described in TS 25.401 [1].
+
+### 5.6.5 GERAN System Information Retrieval
+
+In order to provide the UE with system information related to NACC towards a GERAN system - to be used as an optimisation - the GERAN System Information Retrieval function allows the source system to request GERAN (via CN) to provide this system information. The request and subsequent transfer of the GERAN System Information is performed transparently with the RIM function. The RIM function is further described in TS 25.401 [1]
+
+## 5.7 Security Functions
+
+### 5.7.1 Data Confidentiality
+
+#### 5.7.1.1 Radio interface ciphering function
+
+The radio interface shall be ciphered upon request of the Core Network. Both Signalling and user data may be subject to ciphering. The ciphering shall be done within UTRAN.
+
+#### 5.7.1.2 Ciphering key management function
+
+The ciphering key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm.
+
+### 5.7.2 Data integrity
+
+#### 5.7.2.1 Integrity checking
+
+The purpose of the integrity check is to make sure that the signalling continues between the same elements as by authentication. The integrity check shall be done within the UTRAN.
+
+#### 5.7.2.2 Integrity key management
+
+The integrity key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm.
+
+## 5.8 Service and Network Access Functions
+
+### 5.8.1 Core Network signalling data transfer function
+
+The NAS CN signalling data such as Call Control (CC), Session Management (SM), Mobility Management (MM), Short Message Services Point to Point and Supplementary Services (SS) shall be transparently conveyed between the CN and the UE. Over the Iu interface, the same Iu interface channel that is used for the UTRAN-CN signalling shall be used.
+
+### 5.8.2 Data Volume Reporting
+
+The data volume reporting function is used to report the volume of unacknowledged data to the CN. The function shall be in the UTRAN and is triggered from the CN.
+
+### 5.8.3 UE Tracing
+
+This feature allows tracing of various events related to the UE and its activities. This is an O&M functionality.
+
+### 5.8.4 Location reporting function
+
+The positioning function performs the determination of the geographical position and optionally the velocity for an UE. The location reporting function transfers the positioning information between the UTRAN and the CN according to CN commands. This function involves UTRAN and CN.
+
+### 5.8.5 MDT
+
+This feature enables the transfer of MDT measurements collected by the UE, as defined in TS 37.320 [30]. This is an O&M functionality.
+
+## 5.9 Co-ordination Functions
+
+### 5.9.1 Paging Co-ordination function
+
+The two CN domain architecture implies need for a page co-ordination, i.e. handling of page triggered by one CN node when UE has a signalling connection to the other CN node. The paging co-ordination is performed by UTRAN and/or optionally by CN. The Common ID is used for UTRAN paging co-ordination. The CN provides the UTRAN with the Common ID.
+
+The paging co-ordination is a UTRAN function. Optionally the paging co-ordination may be performed in the CN.
+
+### 5.9.2 NAS Node Selection Function
+
+The optional NAS Node Selection Function enables the RNC to initially assign CN resources to serve a UE and subsequently setup a signalling connection to the assigned CN resource.
+
+The method by which the RNC initially assigns CN resources is implementation dependent.
+
+The NNSF is described in detail in TS 23.236 [25].
+
+### 5.9.3 Information Transfer Function
+
+The Information Transfer function allows configuration data to be passed from the CN to the RNC upon CN trigger. This function is operated in acknowledged mode. It should be used by the CN to maintain alignment between the data as configured in the CN and the configuration data provided to the UTRAN. This may be used e.g. to coordinate the SNA geographical definition (LA to SNA mapping) between CN and UTRAN in order to apply access control on an SNA basis.
+
+### 5.9.4 MOCN Rerouting Function
+
+Rerouting is a mechanism used as part of the assignment of CN operator in shared networks with MOCN configuration for network sharing non-supporting UEs when they perform initial attach/registration. In this case RNC may not know towards which CN to route the initial UE request message and the latter may be rerouted to another CN via RNC.
+
+The MOCN Rerouting Function is described in detail in TS 23.251 [26].
+
+### 5.9.5 SIPTO at Iu-PS Function
+
+If supported, SIPTO at Iu-PS Function provides the capability to offload certain PS RABs from the CN at RAB setup. The SIPTO at Iu-PS is implementation dependent and may be implemented in a separate entity outside of RNS, for further information see TS 23.060 [29].
+
+### 5.9.6 SIPTO at the Local Network with Standalone GW
+
+SIPTO@LN provides access to a defined IP network (e.g. the Internet) without the user plane traversing the mobile operator's core network by using standalone GW (with S-GW and L-GW collocated) in the local network, as specified in TS 23.060 [29].
+
+## 5.10 MBMS Functions
+
+### 5.10.1 MBMS RAB Management functions
+
+The MBMS RAB, Radio Access Bearer, is defined to be set-up between the CN and one or several UEs for MBMS. Depending on the MBMS service characteristics, different types of MBMS RABs will be used. It is the CN that controls towards the UTRAN the establishment, update or release of an MBMS RAB. The MBMS RAB is defined for the PS domain only.
+
+### 5.10.2 MBMS UE Linking Function
+
+This function provides the RNC with the list of MBMS services that a given UE, with existing dedicated Iu-PS signalling connection, has "joined" or has "left" TS 23.246 [27].
+
+### 5.10.3 MBMS Registration Control Function
+
+This function allows the RNC to either register or deregister to the PS core network domain for a specific MBMS bearer service so that it is notified whenever a session of this service starts.
+
+It also allows the CN to inform the RNC that a given MBMS bearer service is no longer available.
+
+### 5.10.4 MBMS Enquiry Function
+
+This function allows the RNC to request to the SGSN the list of MBMS bearer services that a given UE has “joined” TS 23.246 [27] or the IP Multicast Address and APN defined in TS 23.246 [27] which correspond to a given MBMS bearer service.
+
+# --- 6 I<sub>u</sub> Interface Protocol Structure
+
+## 6.1 General
+
+The Radio Network signalling over I<sub>u</sub> consists of the Radio Access Network Application Part (RANAP). The RANAP protocol consists of mechanisms to handle all procedures between the CN and UTRAN. It is also capable of conveying messages transparently between the CN and the UE without interpretation or processing by the UTRAN.
+
+Over the I<sub>u</sub> interface the RANAP protocol is, e.g. used for:
+
+- Facilitate a set of general UTRAN procedures from the Core Network such as paging -notification as defined by the notification SAP in TS 23.110 [3].
+- Separate each User Equipment (UE) on the protocol level for mobile specific signalling management as defined by the dedicated SAP in TS 23.110 [3].
+- Transfer of transparent non-access signalling as defined in the dedicated SAP in TS 23.110 [3].
+- Request of various types of UTRAN Radio Access Bearers through the dedicated SAP in TS 23.110 [3].
+- Perform the SRNS Relocation function.
+- Perform the various MBMS procedures.
+- Perform SIPTO at I<sub>u</sub>-PS (optional).
+
+The Radio Access Bearers are provided by the Access Stratum.
+
+Over I<sub>u</sub>-BC, a datagram mechanism is used, so there is no clear separation of control and user planes, and the SABP protocol is used for data transfer and signalling.
+
+## 6.2 Iu-CS
+
+Figure 6.1 shows the protocol structure for Iu-CS, following the structure described in TS 25.401 [1].
+
+![Protocol stack diagram for Iu-CS interface showing Control Plane, User Plane, and Transport Network Control Plane layers.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg)
+
+The diagram illustrates the protocol stack for the Iu-CS interface, organized into three main vertical sections: Control Plane, User Plane, and Transport Network Control Plane. All three sections share a common 'Radio Network Layer' at the top and a common 'Physical Layer' at the bottom.
+
+- Control Plane:** The 'Radio Network Layer' contains the 'RANAP' protocol. Below it, the 'Transport Network Control Plane' contains 'Q.2630.2', 'Q.2150.1', 'MTP3b', 'SSCF-NNI', 'SSCOP', and 'AAL5'. The 'Transport User Plane' (part of the Transport Network Layer) contains 'SCCP', which is further divided into 'M3UA', 'MTP3b', 'SSCF-NNI', 'SCTP', 'SSCOP', 'IP', and 'AAL5'. This section ends with 'Data Link' and 'ATM' layers.
+- User Plane:** The 'Radio Network Layer' contains the 'Iu UP Protocol Layer'. Below it, the 'Transport User Plane' contains 'AAL2', 'RTP/RTCP\*)', and 'UDP/IP'. This section ends with 'ATM' and 'Data Link' layers.
+- Transport Network Control Plane:** This central section contains the protocols 'Q.2630.2', 'Q.2150.1', 'MTP3b', 'SSCF-NNI', 'SSCOP', and 'AAL5', which connect to the 'ATM' layer.
+
+Vertical arrows indicate the flow of data and signaling between the layers within each plane. Horizontal dashed lines separate the Control Plane, User Plane, and Transport Network Control Plane sections.
+
+Protocol stack diagram for Iu-CS interface showing Control Plane, User Plane, and Transport Network Control Plane layers.
+
+\*) RTCP is optional.
+
+Figure 6.1: Iu –Interface Protocol Structure towards CS Domain
+
+## 6.3 Iu-BC
+
+Figure 6.2 shows the protocol structure for the Iu-BC.
+
+![Protocol stack diagram for Iu interface towards Broadcast Domain. It shows layers from Radio Network Layer down to Physical Layer, with a specific SA Broadcast Plane highlighted in a dashed box.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+The diagram illustrates the protocol stack for the Iu interface towards the Broadcast Domain. It is divided into two main sections: the Radio Network Layer and the Transport Network Layer.
+
+- Radio Network Layer:** Contains the SA Broadcast Plane, which includes the SABP Protocol Layer.
+- Transport Network Layer:** Contains the Transport User Plane and the Network Plane. The Network Plane is highlighted with a dashed box and includes the following layers from top to bottom:
+  - TCP
+  - IP
+  - AAL5
+  - ATM
+  - Physical Layer
+- Connections:**
+  - A vertical arrow points from the Network Plane (IP layer) up to the SABP Protocol Layer in the SA Broadcast Plane.
+  - Vertical arrows point from the Transport User Plane down to the TCP layer.
+  - Double-headed vertical arrows connect the AAL5 layer to the ATM layer and the IP layer to the Data Link layer.
+
+Protocol stack diagram for Iu interface towards Broadcast Domain. It shows layers from Radio Network Layer down to Physical Layer, with a specific SA Broadcast Plane highlighted in a dashed box.
+
+Figure 6.2: Iu Interface Protocol Structure towards Broadcast Domain
+
+## 6.4 I<sub>u</sub>-PS
+
+Figure 6.3 shows the protocol structure for I<sub>u</sub>-PS, following the structure described in TS 25.401 [1].
+
+![Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram illustrates the protocol stack for the Iu-PS interface, divided into Control Plane and User Plane, running over the Transport Network Layer.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg)
+
+The diagram shows the protocol structure for the I<sub>u</sub>-PS interface towards the PS Domain. It is organized into two main vertical sections: Control Plane and User Plane, both situated above the Transport Network Layer.
+
+- Control Plane:**
+  - Radio Network Layer:** Contains the RANAP protocol.
+  - Transport Network Layer:** RANAP connects to the SCCP layer. The SCCP layer is supported by a stack of protocols: MTP3-B, M3UA, SCTP, SSCF-NNI, SSCOP, IP, and AAL5. Below this, the stack splits into ATM and Data Link, which both connect to the Physical Layer.
+- User Plane:**
+  - Radio Network Layer:** Contains the Iu UP Protocol Layer.
+  - Transport Network Layer:** The Iu UP Protocol Layer connects to a stack of protocols: GTP-U, UDP, IP, and AAL5. Below this, the stack splits into ATM and Data Link, which both connect to the Physical Layer.
+- Transport Network Control Plane:** A central section of the Transport Network Layer, currently empty in this diagram.
+
+Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram illustrates the protocol stack for the Iu-PS interface, divided into Control Plane and User Plane, running over the Transport Network Layer.
+
+Figure 6.3: I<sub>u</sub> Interface Protocol Structure towards PS Domain
+
+# 7 Other I<sub>u</sub> Interface Specifications
+
+## 7.1 UTRAN I<sub>u</sub> Interface: Layer 1 (3GPP TS 25.411)
+
+TS 25.411 [4] specifies the range of physical layer technologies that may be used to support the I<sub>u</sub> interface.
+
+## 7.2 UTRAN I<sub>u</sub> Interface: Signalling Transport (3GPP TS 25.412)
+
+TS 25.412 [5] specifies the signalling bearers for the RANAP and transport network control plane protocols for both I<sub>u</sub>-PS and I<sub>u</sub>-CS.
+
+## 7.3 UTRAN I<sub>u</sub> Interface: RANAP Specification (3GPP TS 25.413)
+
+TS 25.413 [6] specifies the RANAP protocol for radio network control plane signalling over the I<sub>u</sub> interface.
+
+## 7.4 UTRAN I<sub>u</sub> Interface: Data Transport and Transport Signalling (3GPP TS 25.414)
+
+TS 25.414 [7] specifies the transport bearers for the user plane of the I<sub>u</sub> interface. It also specifies the protocol used to control these transport bearers.
+
+## 7.5 UTRAN I<sub>u</sub> Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415)
+
+TS 25.415 [8] specifies the user plane frame handling protocol for the I<sub>u</sub> interface.
+
+## 7.6 UTRAN I<sub>u</sub> Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419)
+
+TS 25.419 [14] specifies the communication requirements over the I<sub>u</sub> interface towards the BC domain.
+
+## 7.7 Summary
+
+The present document, 3GPP TS 25.410, specifies the general aspects and principles of the I<sub>u</sub> interface as a whole.
+
+The relationship between the other technical specifications that define the UTRAN I<sub>u</sub> interface is shown in figure 7.1.
+
+![Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the relationship between various 3GPP specifications across different layers of the Iu interface. The top layer is the Radio Network Layer, which contains three planes: Control Plane (spec 25.413), User Plane (spec 25.415), and SA Broadcast Plane (spec 25.419). The middle layer is the Transport Network Layer, which is divided into Transport User Plane (spec 25.412 for Control Plane, 25.415 for User Plane, and 25.419 for SA Broadcast Plane) and Transport Network Control Plane (spec 25.414). The bottom layer is a common Transport Network Control Plane (spec 25.411). Arrows indicate the flow of data and control between these layers and specifications.](49a49278cad196bdfe0db6b4dd1be7fd_img.jpg)
+
+The diagram shows the specification structure for the I<sub>u</sub> interface across three layers:
+
+- Radio Network Layer:** Contains three planes: Control Plane (25.413), User Plane (25.415), and SA Broadcast Plane (25.419).
+- Transport Network Layer:** Divided into Transport User Plane and Transport Network Control Plane. The Transport User Plane for the Control Plane is 25.412. The Transport Network Control Plane for the User Plane and SA Broadcast Plane is 25.414. The Transport User Plane for the User Plane is 25.415.
+- Common Transport Network Control Plane:** Specification 25.411.
+
+Arrows indicate the relationship between the layers: Control Plane (25.413) ↔ Transport User Plane (25.412) ↔ Common Transport Network Control Plane (25.411); User Plane (25.415) ↔ Transport Network Control Plane (25.414) ↔ Common Transport Network Control Plane (25.411); SA Broadcast Plane (25.419) ↔ Transport User Plane (25.419) ↔ Common Transport Network Control Plane (25.411).
+
+Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the relationship between various 3GPP specifications across different layers of the Iu interface. The top layer is the Radio Network Layer, which contains three planes: Control Plane (spec 25.413), User Plane (spec 25.415), and SA Broadcast Plane (spec 25.419). The middle layer is the Transport Network Layer, which is divided into Transport User Plane (spec 25.412 for Control Plane, 25.415 for User Plane, and 25.419 for SA Broadcast Plane) and Transport Network Control Plane (spec 25.414). The bottom layer is a common Transport Network Control Plane (spec 25.411). Arrows indicate the flow of data and control between these layers and specifications.
+
+Figure 7.1: Summary of I<sub>u</sub> Interface Specification Structure
+
+# 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  |
+| RP-43      | RP-090078 | 0068 | 1   | RANAP: Enhanced Relocation Complete Request in SCCP: Connection Request    | 8.1.0  |
+| 12/2009    | -         | -    | -   | Created version 9.0.0 based on v. 8.1.0                                    | 9.0.0  |
+| 12/2010    | -         | -    | -   | Created version 10.0.0 based on v. 9.0.0                                   | 10.0.0 |
+| RP-50      | RP-101389 | 0070 | -   | Introduction of the SIPTO at Iu-PS Function                                | 10.0.0 |
+| SP-49      | SP-100629 | -    | -   | Clarification on the use of References (TS 21.801 CR#0030)                 | 10.1.0 |
+| RP-51      | RP-110230 | 0074 | 1   | Support for MDT                                                            | 10.1.0 |
+| RP-52      | RP-110684 | 0075 | -   | Correction of references                                                   | 10.2.0 |
+| 09/2012    | -         | -    | -   | Update to Rel-11 version (MCC)                                             | 11.0.0 |
+| RP-62      | RP-131909 | 0076 | 6   | Introduction of Standalone GW for SIPTO@LN                                 | 12.0.0 |
+| RP-70      | RP-152088 | 0077 | 1   | Introduction of improvements to CS/PS coordination in UTRAN Shared Network | 13.0.0 |
+
+| Change history |         |           |      |     |     |                                                  |             |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                  | New version |
+| 2017-03        | RAN#75  | RP-170545 | 0079 | 1   | B   | Introduction of QMC for streaming services       | 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/25411/raw.md

@@ -0,0 +1,270 @@
+
+
+# 3GPP TS 25.411 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd 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
+
+|                               |                                     |           |
+|-------------------------------|-------------------------------------|-----------|
+| 1                             | Scope.....                          | 5         |
+| 2                             | References.....                     | 5         |
+| 3                             | Abbreviations.....                  | 6         |
+| 4                             | Iu Layer 1 .....                    | 6         |
+| 4.1                           | Introduction .....                  | 6         |
+| 4.2                           | Layer 1 Description.....            | 6         |
+| 4.2.1                         | Layer 1 Synchronised .....          | 6         |
+| 4.2.2                         | [IP – Layer 1 Unsynchronised].....  | 8         |
+| 4.3                           | Requirements from higher layer..... | 8         |
+| 4.4                           | Services Provided by Layer 1.....   | 8         |
+| 4.4.1                         | ATM Transport.....                  | 8         |
+| 4.5                           | Interface to Management Plane.....  | 8         |
+| <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 allowed to implement Layer 1 on the Iu interface.
+
+The specification of transmission delay requirements and O&M requirements are 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] ITU-T Recommendation I.432.2 (1996-08): "ISDN User-Network interfaces, Layer 1 Recommendations, 155 520 kbit/s and 622 080 kbit/s operation".
+- [2] Void.
+- [3] ITU-T Recommendation G.703 (1998-10): "Physical/electrical characteristics of hierarchical digital interfaces".
+- [4] ITU-T Recommendation G.704 (1998-10): "Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels".
+- [5] ITU-T Recommendation G.957 (1995-07): "Optical interfaces for equipments and systems relating to the synchronous digital hierarchy".
+- [6] ITU-T Recommendation I.432.1 (1996-08): "ISDN User-Network interfaces, Layer 1 Recommendations, General characteristics".
+- [7] ITU-T Recommendation G.823 (2000-03): "The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy".
+- [8] ITU-T Recommendation G.824 (2000-03): "The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy".
+- [9] ITU-T Recommendation G.825 (2001-08): "The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH)".
+- [10] ITU-T Recommendation G.826 (1996-08): "Error performance parameters and objectives for international, constant bit rate digital paths at or above the primary rate".
+- [11] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [12] ATM Forum AF-PHY-0016.000 (1994-09): "DS1 Physical Layer Specification".
+- [13] ATM Forum AF-PHY-0064.000 (1996-09): "E1 Physical Layer Interface Specification".
+- [14] ATM Forum AF-PHY-0086.001 (1999-02): "Inverse Multiplexing for ATM (IMA) Specification Version 1.1".
+
+- [15] ITU-T Recommendation G.751 (1988-11): "Digital multiplex equipments operating at the third order bit rate of 34 368 kbit/s and the fourth order bit rate of 139 264 kbit/s and using positive justification".
+- [16] ITU-T Recommendation G.811 (1997-02): "Timing Characteristics of Primary Reference Clocks".
+- [17] ITU-T Recommendation G.804 (1998-02): "ATM cell mapping into plesiochronous digital hierarchy (PDH)".
+- [18] Standard ECMA-226: "Private Integrated Services Network (PISN) - Mapping Functions for the Employment of Dedicated Circuit Mode Connections as Inter-PTNX Connections (MAPPING-CM-STATIC)".
+- [19] ITU-T Recommendation I.431 (1988-11): "Primary rate user-network interface - Layer 1 specification".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                  |
+|---------|----------------------------------|
+| ATM     | Asynchronous Transfer Mode       |
+| HEC     | Header Error Control             |
+| IMA     | Inverse Multiplexing on ATM      |
+| IP      | Internet Protocol                |
+| PDH     | Plesiochronous Digital Hierarchy |
+| PMD     | Physical Media Dependent         |
+| PHY-SAP | Physical Service Access Point    |
+| SDH     | Synchronous Digital Hierarchy    |
+| SDU     | Service Data Unit                |
+| SONET   | Synchronous Optical Networking   |
+
+# --- 4 Iu Layer 1
+
+## 4.1 Introduction
+
+The main functions of Layer 1 are summarised in the following:
+
+- Interface to physical medium;
+- [ATM-Cell delineation];
+- Line clock extraction capability;
+- Layer 1 alarms extraction and generation;
+- In-sequence delivery;
+- Transmission quality control.
+
+## 4.2 Layer 1 Description
+
+### 4.2.1 Layer 1 Synchronised
+
+When the Layer 1 Synchronised option is used (i.e. PDH/SDH/SONET links), the following requirements shall be met:
+
+Layer 1 reference configuration shall be according to ITU-T Rec. I.432.1 [6].
+
+The physical layer is divided into:
+
+- Physical Media Dependent (PMD) sublayer;
+- Transmission Convergence (TC) sublayer defined according to ITU-T Rec. I.432.1 [6].
+
+The PMD shall comply with at least one of the following standards:
+
+- ETSI STM-4 (622 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with optical S-4.1 interface according to ITU-T Rec. G.957 [5].
+- SONET STS-12c (622 Mb/s) interface according to ANSI, T1.105-1995 with optical multimode.
+- SONET STS-3c (155 Mb/s) interface according to ANSI, T1.105-1995 with optical multimode.
+- ETSI STM-1 (155 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with electrical interface (CMI) to ITU-T Rec. G.703 [3].
+- ETSI STM-1 (155 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with optical S-1.1 interface according to ITU-T Rec. G.957 [5].
+- ITU STS-1 (51 Mb/s) interface according to ANSI, T1.105-1995 with electrical interface.
+- ITU STM-0 (51 Mb/s) interface according to ETSI/TTC with electrical interface.
+- ITU STM-0 (51 Mb/s) interface according to ETSI/TTC with optical S-1.1 interface according to ITU-T Rec. G.957 [5].
+- J2, 6.3 Mb/s interface according to Japanese standard JT-G.703 (ITU-T Rec. G.703 [3]) and JT-G.704 (ITU-T Rec. G.704 [4]) (75 Ohm).
+
+NOTE: J2 requires that the ATM cells be mapped into the physical layer according to HEC based mapping in ITU-R Rec. G.804 [17].
+
+- E2, 8Mb/s according to ETSI/ITU G.703 (ITU-T Rec. G.703 [3]) and G.704 (ITU-T Rec. G.704 [4]) (75 Ohm).
+- E3, 34 Mb/s interface according to ETSI/ITU G.751 (ITU-T Rec. G.751 [15]) (75 Ohm).
+- T3, 45 Mb/s interface according to ANSI/ITU G.703 (ITU-T Rec. G.703 [3]) and G.704 (ITU-T Rec. G.704 [4]) (75 Ohm).
+- E1, 2Mb/s interface balanced 120 Ohm symmetrical according to ETS 300 420 (Standard ECMA-226 [18]), ITU-T Rec. G.704 [4] and TBR 013 (ITU-T Rec. G.703 [3]), and AF-PHY-0064.000 [13].
+- E1, 2Mb/s according to ITU-T Rec. G.703 [3] and ITU-T Rec. G.704 [4] (75 Ohm), and AF-PHY-0064.000 [13].
+- J1, 1.5 Mb/s interface according to JT-I.431-a (ITU-T Rec. I.431 [19]) (100 Ohm).
+- J1, 1.5 Mb/s interface according to JT-G.703 (ITU-T Rec. G.703 [3]) and JT-G.704 (ITU-T Rec. G.704 [4]) (110 Ohm).
+- T1, 1.5 Mb/s interface according to AF-PHY-0016.000 [12] and ITU-T Rec. G.703 [3] and ITU-T Rec. G.704 [4] (100 Ohm).
+
+Services provided to the upper layer shall be independent from the used underlying technology.
+
+The support of intervening transport networks - like PDH or SDH terrestrial links, Point-to-point or Point-to-Multipoint radio links - shall not be prevented.
+
+When using E1, T1, or J1, it shall be possible to use inverse multiplexing of ATM (IMA) (ATM Forum AF-PHY-0086.001 [14]) within suitable subsets of the physical ports on the respective Exchange Termination (ET).
+
+The jitter and wander performance requirements on the interface shall be in accordance with network limits for output wander at traffic interfaces of either Reference ITU-T Rec. G.823 [7], ITU-T Rec. G.824 [8] or network limits for the maximum output jitter and wander at any hierarchical interface of Reference ITU-T Rec. G.825 [9], whichever is applicable.
+
+The synchronisation reference extracted from the Iu may be used as UTRAN synchronisation reference. A general recommendation is to supply a traceable synchronisation reference according to reference ITU-T Rec. G.811 [16].
+
+Transmission quality control shall be provided according to ITU-T Rec. G.826 [10].
+
+### 4.2.2 [IP – Layer 1 Unsynchronised]
+
+When Layer 1 unsynchronised option is used, the following requirements shall be met:
+
+The support of any suitable physical layer - like Ethernet L1 or other suitable point-to-point or point-to-multipoint techniques - shall not be prevented.
+
+## 4.3 Requirements from higher layer
+
+No specific requirements beyond the ones listed in the introduction have been identified.
+
+## 4.4 Services Provided by Layer 1
+
+### 4.4.1 ATM Transport
+
+The physical layer provides services to the upper layer via the Physical Service Access Point (PHY-SAP) according to ITU-T I.361 [11], as described in the following figure:
+
+![Diagram showing the SAP between Physical Layer and ATM Layer. The ATM Layer is at the top, connected to the Physical Layer at the bottom via a PHY-SAP (represented by an oval).](740442c999390734911677f01af0316d_img.jpg)
+
+The diagram illustrates the interface between the ATM Layer and the Physical Layer. At the top is a rectangular box labeled "ATM Layer". At the bottom is a rectangular box labeled "Physical Layer". A vertical line connects the two boxes. In the middle of this line is an oval shape, and to the right of the oval is the text "PHY-SAP", indicating the Physical Service Access Point.
+
+Diagram showing the SAP between Physical Layer and ATM Layer. The ATM Layer is at the top, connected to the Physical Layer at the bottom via a PHY-SAP (represented by an oval).
+
+**Figure 1: SAP between Physical Layer and ATM Layer**
+
+According to ITU-T Rec. I.361 [11], subclause 3.2, the following primitives are provided over PHY-SAP:
+
+- PHY-DATA request (PHY-SDU);
+- PHY-DATA indication (PHY-SDU).
+
+The parameter PHY-SDU contains one ATM cell as defined in ITU-T I.361 [11] received or to be transferred over the physical medium.
+
+## 4.5 Interface to Management Plane
+
+The description of the interface towards Management Plane is out of scope of this document, anyhow at least the following O&M functions should be foreseen:
+
+- Performance Monitoring Functions;
+
+- Alarm Status Reporting Functions;
+- Synchronisation Source Management.
+
+# 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-110684 | 0019 |     | Correction of 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-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/25420/raw.md

@@ -0,0 +1,935 @@
+
+
+# 3GPP TS 25.420 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN I<sub>ur</sub> 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. 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  |
+| 3.2 Specification Notations .....                                                                         | 8  |
+| 4 General Aspects .....                                                                                   | 9  |
+| 4.1 Introduction .....                                                                                    | 9  |
+| 4.2 Iur Interface General Principles .....                                                                | 9  |
+| 4.3 Iur Interface Specification Objectives.....                                                           | 9  |
+| 4.3.1 General .....                                                                                       | 9  |
+| 4.3.2 Addressing of RNSs over the Iur Interface .....                                                     | 9  |
+| 4.4 Iur Interface Capabilities.....                                                                       | 10 |
+| 4.4.1 Radio application related signalling .....                                                          | 10 |
+| 4.4.2 Iub/Iur DCH data streams.....                                                                       | 10 |
+| 4.4.3 Iur RACH data streams .....                                                                         | 10 |
+| 4.4.4 Iur DSCH data streams [TDD].....                                                                    | 10 |
+| 4.4.5 Iur USCH data streams [TDD].....                                                                    | 10 |
+| 4.4.6 Iur FACH data streams.....                                                                          | 10 |
+| 4.4.7 Iur HS-DSCH data streams .....                                                                      | 10 |
+| 4.4.8 Iub/Iur E-DCH data streams.....                                                                     | 10 |
+| 4.4.9 Iur IuUP data streams for CS data forwarding .....                                                  | 11 |
+| 4.5 Iur Interface Characteristics .....                                                                   | 11 |
+| 4.5.1 Uses of SCCP .....                                                                                  | 11 |
+| 4.5.1.1 General.....                                                                                      | 11 |
+| 4.5.1.2 SCCP connection establishment .....                                                               | 11 |
+| 4.5.1.3 Establishment procedure initiated from the SRNC.....                                              | 11 |
+| 4.5.1.3A Establishment procedure initiated from an RNC requesting common measurements or information..... | 12 |
+| 4.5.1.4 SCCP connection release.....                                                                      | 13 |
+| 4.5.1.5 General SCCP Abnormal Conditions .....                                                            | 13 |
+| 4.5.1.5.1 SCCP bearer failure.....                                                                        | 13 |
+| 4.5.1.5.2 SCCP connection failure .....                                                                   | 13 |
+| 4.5.2 SCCP Addressing Scheme .....                                                                        | 14 |
+| 4.5.2.1 General.....                                                                                      | 14 |
+| 5 Functions of the I <sub>ur</sub> Interface Protocols.....                                               | 14 |
+| 5.1 Functional List.....                                                                                  | 14 |
+| 5.2 Functional Split over Iur .....                                                                       | 15 |
+| 5.2.1 Combining/Splitting .....                                                                           | 15 |
+| 5.2.2 Control of Combining/Splitting Topology .....                                                       | 15 |
+| 5.2.3 Handling of DRNS Hardware Resources .....                                                           | 15 |
+| 5.2.4 Allocation of Physical Channels .....                                                               | 15 |
+| 5.2.5 UpLink Power Control .....                                                                          | 15 |
+| 5.2.6 Down-Link Power Control .....                                                                       | 15 |
+| 5.2.7 Admission Control.....                                                                              | 16 |
+| 5.2.8 Radio Protocol Functional Split .....                                                               | 16 |
+| 5.2.9 MBMS Bearer Type Control.....                                                                       | 16 |
+| 5.2.10 MBSFN MCCH Information Control .....                                                               | 16 |
+| 6 I <sub>ur</sub> Interface Protocols.....                                                                | 16 |
+| 6.1 General .....                                                                                         | 16 |
+| 6.2 Radio Signalling Protocols.....                                                                       | 17 |
+| 6.2.1 RNSAP Protocol.....                                                                                 | 17 |
+
+|                               |                                                                                                                          |           |
+|-------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------|
+| 6.3                           | User Plane Frame Protocols .....                                                                                         | 17        |
+| 6.3.1                         | Iub/Iur DCH Frame Protocol .....                                                                                         | 17        |
+| 6.3.2                         | Iur DSCH Frame Protocol [TDD] .....                                                                                      | 18        |
+| 6.3.3                         | Iur USCH Frame Protocol [TDD] .....                                                                                      | 18        |
+| 6.3.4                         | Iur RACH Frame Protocol .....                                                                                            | 18        |
+| 6.3.5                         | Iur FACH Frame Protocol .....                                                                                            | 18        |
+| 6.3.6                         | Iur HS-DSCH Frame Protocol .....                                                                                         | 18        |
+| 6.3.7                         | Iur E-DCH Frame Protocol .....                                                                                           | 19        |
+| 6.4                           | Mapping of Frame Protocols onto transport bearers .....                                                                  | 19        |
+| 7                             | DRNS logical Model over I <sub>ur</sub> .....                                                                            | 19        |
+| 7.1                           | Overview .....                                                                                                           | 19        |
+| 7.2                           | Logical Model Elements .....                                                                                             | 20        |
+| 7.2.1                         | Radio Link .....                                                                                                         | 20        |
+| 7.2.2                         | Cell .....                                                                                                               | 20        |
+| 7.2.3                         | Iur DCH Data Port .....                                                                                                  | 20        |
+| 7.2.4                         | Iur DSCH Data Port [TDD] .....                                                                                           | 21        |
+| 7.2.5                         | Iur USCH Data Port [TDD] .....                                                                                           | 21        |
+| 7.2.6                         | Iur RACH/FACH Data Port .....                                                                                            | 21        |
+| 7.2.7                         | Iur Control Port .....                                                                                                   | 21        |
+| 7.2.8                         | Iur HS-DSCH Data Port .....                                                                                              | 21        |
+| 7.2.9                         | Iur E-DCH Data Port .....                                                                                                | 21        |
+| 8                             | I <sub>ur</sub> Interface Protocol Structure .....                                                                       | 21        |
+| 9                             | Other I <sub>ur</sub> Interface Specifications .....                                                                     | 22        |
+| 9.1                           | UTRAN Iur Interface: Layer 1 (TS 25.421) .....                                                                           | 22        |
+| 9.2                           | UTRAN Iur Interface: Signalling Transport (TS 25.422) .....                                                              | 22        |
+| 9.3                           | UTRAN Iur Interface: RNSAP Specification (TS 25.423) .....                                                               | 22        |
+| 9.4                           | UTRAN Iur Interface: Data Transport and Transport Signalling for Common Transport Channel Data Streams (TS 25.424) ..... | 22        |
+| 9.5                           | UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams (TS 25.425) .....                    | 22        |
+| 9.6                           | UTRAN Iur & Iub Interface: Data Transport and Transport Signalling for DCH Data Streams (TS 25.426) .....                | 23        |
+| 9.7                           | UTRAN Iur & Iub Interface: User Plane Protocols for DCH Data Streams (TS 25.427) .....                                   | 23        |
+| 9.8                           | Summary of UTRAN Iur Interface Technical Specifications .....                                                            | 23        |
+| <b>Annex A (informative):</b> | <b>Change History .....</b>                                                                                              | <b>24</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.42x series of UMTS Technical Specifications that define the Iur Interface. It is a logical interface for the interconnection of two 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.427: "UTRAN Iub/Iur Interface User Plane Protocol for DCH Data Streams".
+- [2] 3GPP TS 25.425: "UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams".
+- [3] 3GPP TS 25.421: "UTRAN Iur Interface: Layer 1".
+- [4] 3GPP TS 25.422: "UTRAN Iur Interface: Signalling Transport".
+- [5] 3GPP TS 25.423: "UTRAN Iur Interface: Radio Network Subsystem Application Part (RNSAP) signalling".
+- [6] 3GPP TS 25.424: "UTRAN Iur Interface: Data Transport & Transport Signalling ".
+- [7] Void
+- [8] 3GPP TS 25.426: "UTRAN Iur & Iub Interface: Data Transport & Transport Signalling for DCH Data Streams".
+- [9] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [10] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages".
+- [11] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [12] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [13] 3GPP TS 23.003: "Numbering, Addressing and Identification".
+- [14] Void
+- [15] Void
+- [16] Void
+- [17] 3GPP TR 43.930: "Iur-g interface; Stage 2".
+- [18] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast/Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
+- [19] 3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2".
+
+[20]
+
+3GPP TS 25.415: "UTRAN Iu interface user plane protocols"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+None.
+
+## 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                                      |
+| ALCAP    | Access Link Control Application Part                             |
+| ATM      | Asynchronous Transfer Mode                                       |
+| BSS      | Base Station Subsystem                                           |
+| CRNC     | Controlling RNC                                                  |
+| CTP      | Common Transport Protocol                                        |
+| DCH      | Dedicated Transport Channel                                      |
+| DL       | Downlink                                                         |
+| DPCH     | Dedicated Physical Channel                                       |
+| DRNC     | Drift Radio Network Controller                                   |
+| DRNS     | Drift Radio Network Subsystem                                    |
+| DSCH     | Downlink Shared Channel                                          |
+| E-DCH    | Enhanced Dedicated Channel                                       |
+| EDGE     | Enhanced Data rates for GSM Evolution                            |
+| FACH     | Forward Access Channel                                           |
+| F-DPCH   | Fractional DPCH                                                  |
+| FFS      | For Further Study                                                |
+| GERAN    | GSM/EDGE Radio Access Network                                    |
+| GSM      | Global System for Mobile communications                          |
+| GT       | Global Title                                                     |
+| HARQ     | Hybrid Automatic Repeat Request                                  |
+| HS-DSCH  | High Speed Downlink Shared Channel                               |
+| IP       | Internet Protocol                                                |
+| MAC      | Medium Access Control                                            |
+| MBMS     | Multimedia Broadcast Multicast Service                           |
+| MRNC     | MBMS Master RNC                                                  |
+| MTP3-B   | Message Transfer Part level 3 (for Q.2140)                       |
+| PLMN     | Public Land Mobile Network                                       |
+| PTM      | Point To Multipoint                                              |
+| PTP      | Point To Point                                                   |
+| QoS      | Quality of Service                                               |
+| RACH     | Random Access Channel                                            |
+| RF       | Radio Frequency                                                  |
+| RNC      | Radio Network Controller                                         |
+| RNS      | Radio Network Subsystem                                          |
+| RNSAP    | Radio Network Subsystem Application Part                         |
+| RRC      | Radio Resource Control                                           |
+| SCCP     | Signalling Connection Control Part                               |
+| SPC      | Signalling Point Code                                            |
+| SRNC     | Serving Radio Network Controller                                 |
+| SRNS     | Serving Radio Network Subsystem                                  |
+| SS7      | Signalling System N° 7                                           |
+| SSCF-NNI | Service Specific Co-ordination Function – Network Node Interface |
+| SSCOP    | Service Specific Connection Oriented Protocol                    |
+| SSN      | Sub-System Number                                                |
+
+|       |                                           |
+|-------|-------------------------------------------|
+| STC   | Signalling Transport Converter            |
+| UDP   | User Datagram Protocol                    |
+| UE    | User Equipment                            |
+| UL    | Up-link                                   |
+| UMTS  | Universal Mobile Telecommunication System |
+| URA   | UTRAN Registration Area                   |
+| USCH  | Uplink Shared Channel                     |
+| UTRAN | UMTS Terrestrial Radio Access Network     |
+
+## 3.2 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.
+- [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 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.
+- [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.
+
+|           |                                                                                                                                                                                                                        |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 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 connection that exists between any two RNCs within the UTRAN is referred to as the Iur interface.
+
+## 4.2 Iur Interface General Principles
+
+The general principles for the specification of the Iur interface are as follows:
+
+- The Iur interface should be open;
+- The Iur interface shall support the exchange of signalling information between two RNCs, in addition the interface may need to support one or more Iur data streams;
+- From a logical standpoint, the Iur is a point-to-point interface between two RNCs within the UTRAN. A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the two RNCs.
+
+## 4.3 Iur Interface Specification Objectives
+
+### 4.3.1 General
+
+The Iur interface specifications shall facilitate the following:
+
+- inter-connection of RNCs supplied by different manufacturers;
+- support of continuation between RNSs of the UTRAN services offered via the Iu interface;
+- separation of Iur interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology.
+
+### 4.3.2 Addressing of RNSs over the Iur Interface
+
+- For an RRC connection using a dedicated channel or for a UE using F-DPCH in the downlink, the Iur standard shall allow the addition / deletion of radio links supported by cells belonging to any RNS within the PLMN.
+- The specification of the Iur interface shall allow an RNC to address any other RNC within the PLMN for establishing a signalling bearer over Iur.
+- The specification of the Iur interface shall allow an RNC to address any other RNC within the PLMN for establishing user data bearers for Iur data streams.
+
+RNSAP shall allow different kinds of addressing schemes to be used for the signalling bearer.
+
+## 4.4 Iur Interface Capabilities
+
+### 4.4.1 Radio application related signalling
+
+The Iur interface provides capability to support radio interface mobility between RNSs, of UEs having a connection with UTRAN. This capability includes the support of handover, radio resource handling, MBMS handling and synchronisation between RNSs.
+
+### 4.4.2 Iub/Iur DCH data streams
+
+The Iur interface provides the means for transport of uplink and downlink Iub/Iur DCH frames carrying user data and control information between SRNC and Node B (DRNS), via the DRNC.
+
+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 Iur RACH data streams
+
+The Iur interface provides the means for transport of uplink RACH transport frames between DRNC and SRNC.
+
+### 4.4.4 Iur DSCH data streams [TDD]
+
+An Iur DSCH data stream corresponds to the data carried on one DSCH transport channel for one UE. A UE may have multiple Iur DSCH data streams.
+
+The Iur interface provides a means of transporting down link MAC-c/sh SDUs. In addition, the interface provides a means to the SRNC for queue reporting and a means for the DRNC to allocate capacity to the SRNC.
+
+### 4.4.5 Iur USCH data streams [TDD]
+
+An Iur USCH data stream corresponds to the data carried on one USCH transport channel for one UE. A UE may have multiple Iur USCH data streams.
+
+### 4.4.6 Iur FACH data streams
+
+The Iur interface provides the means for transport of downlink FACH transport frames between SRNC and DRNC.
+
+### 4.4.7 Iur HS-DSCH data streams
+
+An Iur HS-DSCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple Iur HS-DSCH data streams.
+
+The Iur interface provides a means of transporting down link MAC-d PDUs. In addition, the interface provides a means to the SRNC for queue reporting and a means for the DRNC to allocate capacity to the SRNC.
+
+### 4.4.8 Iub/Iur E-DCH data streams
+
+The Iur interface provides the means for transport of Iub/Iur E-DCH frames carrying user data between NodeB (DRNS) and SRNC, via the DRNC.
+
+An Iur 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 ITU-T Rec. Q.713 [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 in the DRNSTS 25.427 [1].
+
+### 4.4.9 Iur IuUP data streams for CS data forwarding
+
+In order to support data forwarding for CS services like during enhanced relocation, Iu UP protocol is used according to the procedures described in TS 25.415 [20] on the Iur link for forwarding the CS data from source RNC to target RNC. It is assumed that the Target RNC supports the same Iu UP mode version as the one used between the source SRNC and the CN.
+
+## 4.5 Iur Interface Characteristics
+
+### 4.5.1 Uses of SCCP
+
+#### 4.5.1.1 General
+
+The SCCP (ITU-T Rec. Q.711 [9] / ITU-T Rec. Q.712 [10]/ ITU-T Rec. Q.713 [11]/ ITU-T Rec. Q.714 [12]) is used to support signalling messages between two RNCs. One user function of the SCCP, called Radio Network Subsystem Application Part (RNSAP), is defined. The RNSAP uses one signalling connection per DRNC and UE where a UE is having one or more active radio links for the transfer of layer 3 messages. RNSAP also uses one signalling connection per RNC providing common measurements and information to a particular RNC (i.e. if measurements and information are transferred in both directions between a pair of RNCs, then two SCCP connections are used).
+
+Both connectionless and connection-oriented procedures are used to support the RNSAP. TS 25.423 [6] explains whether connection oriented or connectionless services should be used for a layer 3 procedure.
+
+The following subclauses describe the use of SCCP connections for RNSAP transactions. Subclause 4.5.1.2 describes the connection establishment procedures. Subclause 4.5.1.3 describes the connection establishment procedures initiated from SRNC. Subclause 4.5.1.4 describes the connection release procedures. Subclause 4.5.1.5 describes abnormal conditions.
+
+#### 4.5.1.2 SCCP connection establishment
+
+A new SCCP connection is established when information related to the communication between a UE and the network has to be exchanged between two RNCs, and no SCCP connection exists between the two RNCs involved, for the concerned UE.
+
+In this case, the SCCP connection is established by the SRNC.
+
+A new SCCP connection is established when a request for common measurements or information is made towards a particular RNC and no SCCP connection for common measurements and information transfer has been established from the RNC requesting the measurements or information towards the one providing the measurements or the information.
+
+In this case, the SCCP connection is established by the RNC requesting the measurements or the information.
+
+#### 4.5.1.3 Establishment procedure initiated from the SRNC
+
+The SCCP signalling connection establishment is initiated, by the SRNC, when the SRNC needs to request dedicated resources, i.e. a DCH, from a DRNC.
+
+##### Initiation
+
+- The SRNC sends the SCCP: CR message to the DRNC. The RADIO LINK SETUP REQUEST message or the ENHANCED RELOCATION REQUEST may be included in the user data field of an SCCP Connection Request message.
+
+##### Termination
+
+1. Successful outcome:
+
+- The SCCP Connection Confirm message, which may optionally contain a connection oriented RNSAP message in the user data field, is returned to the SRNC.
+2. Unsuccessful outcome:
+- If the SCCP signalling connection establishment fails, an SCCP Connection Refusal message will be sent back to the SRNC. This message may optionally contain a connection oriented RNSAP message.
+
+For more information on how the RNSAP procedures Radio Link Setup and Enhanced Relocation are handled, please see the procedures Radio Link Setup and Enhanced Relocation in TS 25.423 [5].
+
+![Sequence diagram showing the setting-up of an SCCP Signalling Connection between an SRNC and a DRNC. The SRNC sends a CR message to the DRNC. The DRNC responds with either a CC message or a CREF message. A legend defines the parameters: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC.](7f17c430b9598e4d748a8041457810b3_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SRNC
+    participant DRNC
+    Note right of SRNC: a1 = source local reference,  
+a2 = destination local reference  
+x = SCCP connection reference at the SRNC,  
+y = SCCP connection reference at the DRNC.
+    SRNC->>DRNC: CR {SSN=RNSAP, a1=x,  
+RNSAP message or no user data }
+    DRNC-->>SRNC: CC {a1=y, a2=x, RNSAP message or no user data}
+    Note right of DRNC: OR
+    DRNC-->>SRNC: CREF {a2=x, RNSAP message or no user data}
+  
+```
+
+Sequence diagram showing the setting-up of an SCCP Signalling Connection between an SRNC and a DRNC. The SRNC sends a CR message to the DRNC. The DRNC responds with either a CC message or a CREF message. A legend defines the parameters: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC.
+
+**Figure 1: Setting-up of SCCP Signalling Connection**
+
+#### 4.5.1.3A Establishment procedure initiated from an RNC requesting common measurements or information
+
+The SCCP signalling connection establishment is initiated, by an RNC, when the RNC needs to request common measurements or provision of information from another RNC and there is no signalling bearer existing for this purpose. For the description below, the RNC requesting the measurements or the information is called RNC1 and the RNC being requested to provide the measurements or the information is called RNC2.
+
+##### Initiation
+
+- The RNC1 sends the SCCP: CR message to the RNC2. The COMMON MEASUREMENT INITIATION REQUEST or the INFORMATION EXCHANGE INITIATION REQUEST message shall be included in the user data field of the SCCP Connection Request message.
+
+##### Termination
+
+1. Successful outcome:
+  - The SCCP Connection Confirm message, which may optionally contain a connection oriented RNSAP message in the user data field, is returned to the RNC1.
+2. Unsuccessful outcome:
+  - If the SCCP signalling connection establishment fails, an SCCP Connection Refusal message will be sent back to the RNC1. This message may optionally contain a connection oriented RNSAP message.
+
+RNSAP Common Measurement Initiation and Information Exchange Initiation procedures are described in TS 25.423 [5].
+
+![Sequence diagram showing the setting-up of an SCCP Signalling Connection between RNC1 and RNC2. RNC1 sends a CR message to RNC2. RNC2 responds with either a CC message or a CREF message. A legend defines the variables: a1 (source local reference), a2 (destination local reference), x (SCCP connection reference at the SRNC), and y (SCCP connection reference at the DRNC).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg)
+
+```
+
+sequenceDiagram
+    participant RNC1
+    participant RNC2
+    Note right of RNC1: a1 = source local reference,  
+a2 = destination local reference  
+x = SCCP connection reference at the SRNC,  
+y = SCCP connection reference at the DRNC.
+    RNC1->>RNC2: CR {SSN=RNSAP, a1=x, RNSAP message }
+    RNC2-->>RNC1: CC {a1=y, a2=x, RNSAP message or no user data}
+    Note over RNC1, RNC2: OR
+    RNC2-->>RNC1: CREF {a2=x, RNSAP message or no user data}
+  
+```
+
+Sequence diagram showing the setting-up of an SCCP Signalling Connection between RNC1 and RNC2. RNC1 sends a CR message to RNC2. RNC2 responds with either a CC message or a CREF message. A legend defines the variables: a1 (source local reference), a2 (destination local reference), x (SCCP connection reference at the SRNC), and y (SCCP connection reference at the DRNC).
+
+**Figure 1a: Setting-up of SCCP Signalling Connection**
+
+#### 4.5.1.4 SCCP connection release
+
+An SCCP connection related to a specific UE is released in all normal release cases when the RNC which established the SCCP connection realises that a given signalling connection is no longer required.
+
+The RNC which established SCCP connection sends an SCCP Released message.
+
+The procedure may be initiated at the SRNC side and the DRNC side in any abnormal release case.
+
+An SCCP connection used for common measurements and information exchanges is released in all normal release cases when the RNC1 (see 4.5.1.3A) determines that a given signalling connection is no longer required. The RNC1 sends an SCCP Released message.
+
+In case an SCCP Release message is received after the successful completion of an SRNC Relocation procedure while dedicated resources are still allocated the new SRNC shall only release the SCCP connection and the Iur related dedicated resource.
+
+The procedure may be initiated at the RNC 1 side and the RNC 2 side in any abnormal release case.
+
+#### 4.5.1.5 General SCCP Abnormal Conditions
+
+##### 4.5.1.5.1 SCCP bearer failure
+
+If a user-out-of-service information or signalling-point-inaccessible information is received by the RNSAP, no new attempt to establish SCCP connections or to send SCCP Connectionless messages towards the affected signalling point (indicated by the affected signalling 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 an RNC, an optional timer may be started. When the timer expires, the RNC shall take actions as described in TS 25.423 [5] Annex D.1.1. When the user-in-service or signalling-point-accessible is received, the timer is stopped.
+
+##### 4.5.1.5.2 SCCP connection failure
+
+If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the RNSAP procedures are being performed or while a dedicated resource is still allocated, this shall be handled by the RNC as described in TS 25.423 [5] Annex D.1.2.
+
+### 4.5.2 SCCP Addressing Scheme
+
+#### 4.5.2.1 General
+
+RNSAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. Which of the available addressing schemes to use for the SCCP is an operator matter.
+
+When GT addressing is utilised, the following settings shall be used:
+
+- SSN Indicator = 1 (RNSAP SSN as defined in TS 23.003 [13] shall always be included);
+- 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.
+
+# --- 5 Functions of the I<sub>ur</sub> Interface Protocols
+
+## 5.1 Functional List
+
+The list of functions on the I<sub>ur</sub> interface is the following:
+
+1. Transport Network Management.
+2. Traffic management of Common Transport Channels:
+  - Preparation of Common Transport Channel resources;
+  - Paging.
+3. Traffic Management of Dedicated Transport Channels:
+  - Radio Link Setup/ Addition/ Deletion;
+  - Measurement Reporting.
+4. [TDD - Traffic Management of Downlink Shared Transport Channels and Uplink Shared Transport Channels]:
+  - Radio Link Setup/ Addition/ Deletion;
+  - Capacity Allocation.
+5. Measurement reporting for common and dedicated measurement objects.
+6. Information exchange of UTRAN, GERAN and MBMS bearer service information.
+7. Tracing of various events related to a UE.
+8. MBMS related functions
+  - MBMS UE Linking/De-linking
+  - MBMS URA linking/De-linking
+
+- MBMS Channel type Indication
+- MBSFN MCCH Information Control
+
+## 5.2 Functional Split over Iur
+
+### 5.2.1 Combining/Splitting
+
+DRNS may perform combining/splitting of data streams communicated via its cells. SRNS performs combining/splitting of Iur data streams received from/sent to DRNS(s), and data streams communicated via its own cells.
+
+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)].
+
+The internal DRNS handling of combining (respectively splitting) of Iub (respectively Iur) DCH frames is controlled by the DRNS.
+
+### 5.2.2 Control of Combining/Splitting Topology
+
+When requesting the addition of a new cell for a UE-UTRAN connection for DCH, the RNC of the SRNS (i.e. the SRNC) can explicitly request to the RNC of the DRNS (i.e. the DRNC) a new Iur data stream, in which case the combining and splitting function within the DRNS is not used for that cell. The SRNC can also explicitly request from the DRNC the use of the combining and splitting function inside the DRNS for that cell. Otherwise, the DRNS takes the decision whether combining and splitting function is used inside the DRNS for that cell i.e. whether a new Iur data stream shall be added or not.
+
+For E-DCH combining at the DRNC is not allowed. However, combining in NodeB of the DRNS is mandatory where applicable as described in TS 25.319 [19].
+
+### 5.2.3 Handling of DRNS Hardware Resources
+
+Allocation and control of DRNS hardware resources, used for Iur data streams and radio interface transmission/reception in DRNS is performed by DRNS.
+
+### 5.2.4 Allocation of Physical Channels
+
+Allocation of physical channels in cells belonging to DRNS is performed in DRNS.
+
+### 5.2.5 UpLink Power Control
+
+This group of functions controls the level of the uplink transmitted power in order to minimise uplink interference and keep the quality of the connections. If the connection involves both a SRNS and a DRNS the function UL Outer Loop Power Control (located in the SRNC) sets the target quality for the UL Inner Loop Power Control function (located in Node B for DCH [FDD]). For E-DCH, the DRNS (NodeB) reports the number of HARQ retransmissions to SRNC as an input to the Outer Loop Power Control function.
+
+### 5.2.6 Down-Link Power Control
+
+This group of functions controls the level of the downlink transmitted power. In FDD it is also used to correct the downlink power drifting between several radio links. SRNC regularly (or under some algorithms) sends the target down link power reference based on the measurement report from UE.
+
+### 5.2.7 Admission Control
+
+Admission control in a DRNC is implicitly invoked during radio link setup/modify.
+
+Information on UL interference and DL power on cells controlled by the DRNC should be available across Iur.
+
+Additional information exchanges between admission control functions located in different RNCs are for further study.
+
+### 5.2.8 Radio Protocol Functional Split
+
+Iur supports the radio protocol functional split between SRNC and DRNC.
+
+### 5.2.9 MBMS Bearer Type Control
+
+MBMS Bearer type control is split between SRNC and DRNC. The CRNC is in control of an MBMS Bearer of PTM type. The MBMS bearer services activated by the UE are transferred over Iur from SRNC to DRNC. In case the CRNC is a DRNC for one or several UEs, it indicates the selected bearer type to SRNC but it is SRNC decision to set up or release MBMS bearers of PTP type for a given UE as described in TS 25.346 [18].
+
+### 5.2.10 MBSFN MCCH Information Control
+
+In case MRNC is used, MBSFN MCCH Information Control function is split between MRNC and CRNC. The MRNC controls the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). The MRNC informs the CRNC of the MCCH configuration and schedule information to be used. The CRNC performs the MCCH configuration and sends the MCCH information accordingly.
+
+# --- 6 Iur Interface Protocols
+
+## 6.1 General
+
+There shall exist a clear separation between the Radio Network Layer and the Transport Layer. Therefore, the radio network signalling and Iur data streams are separated from the data transport resource and traffic handling as shown in Figure 2. Data transport resource and traffic handling is controlled by Transport Signalling. The Transport Signalling is carried by a Signalling Bearer over the Iur interface.
+
+![Diagram illustrating the separation of Radio Network Protocols and transport over Iur. The diagram shows two layers: Radio Network layer and Transport layer. The Radio Network layer contains two protocols: Radio Signalling Protocols and User Plane Framing Protocols. The Transport layer contains a Signalling Bearer, Transport Signalling, and Data Transport. Arrows show the flow: Radio Signalling Protocols to Signalling Bearer, User Plane Framing Protocols to Data Transport, and Transport Signalling controlling both the Signalling Bearer and Data Transport.](64fd8bd804acee34ea91bdde28997fe3_img.jpg)
+
+```
+graph TD
+    subgraph RNL [Radio Network layer]
+        RSP((Radio Signalling Protocols))
+        UPFP((User Plane Framing Protocols))
+    end
+    subgraph TL [Transport layer]
+        SB[Signalling Bearer]
+        TS[Transport Signalling]
+        DT[Data Transport]
+    end
+    RSP --> SB
+    UPFP --> DT
+    TS --> SB
+    TS --> DT
+```
+
+Diagram illustrating the separation of Radio Network Protocols and transport over Iur. The diagram shows two layers: Radio Network layer and Transport layer. The Radio Network layer contains two protocols: Radio Signalling Protocols and User Plane Framing Protocols. The Transport layer contains a Signalling Bearer, Transport Signalling, and Data Transport. Arrows show the flow: Radio Signalling Protocols to Signalling Bearer, User Plane Framing Protocols to Data Transport, and Transport Signalling controlling both the Signalling Bearer and Data Transport.
+
+**Figure 2: Separation of Radio Network Protocols and transport over Iur**
+
+## 6.2 Radio Signalling Protocols
+
+### 6.2.1 RNSAP Protocol
+
+The protocol responsible for providing signalling information across the Iur interface is called the Radio Network Subsystem Application Part (RNSAP). A subset of RNSAP is used over the Iur-g interface.
+
+The RNSAP is terminated by the two RNCs inter-connected via the Iur interface RNSAP Procedure Modules. In addition, the RNSAP is terminated by a RNC and a BSS supporting Iu mode inter-connected via the Iur-g interface (TR 43.930 [17]). For 1.28Mcps TDD, the RNSAP may be terminated by a RNC and a BSS supporting A/Gb mode inter-connected via the Iur-g interface.
+
+RNSAP procedures are divided into four modules as follows:
+
+1. RNSAP Basic Mobility Procedures;
+2. RNSAP Dedicated Procedures;
+3. RNSAP Common Transport Channel Procedures;
+4. RNSAP Global Procedures;
+5. RNSAP MBMS Procedures.
+
+The Basic Mobility Procedures module contains procedures used to handle the mobility within UTRAN as well as to handle mobility in case of UTRAN/GERAN interworking.
+
+The Dedicated Procedures module contains procedures that are used to handle DCHs, [FDD – F-DPCH,] E-DCH, [TDD – DSCH, USCHs] and HS-DSCH between two RNSs. If procedures from this module are not used in a specific Iur, then the usage of DCH, [FDD – F-DPCH,] E-DCH, [TDD – DSCH, USCH] and HS-DSCH traffic between corresponding RNSs is not possible.
+
+The Common Transport Channel Procedures module contains procedures that are used to control common transport channel data streams (excluding the DSCH, HS-DSCH, E-DCH and USCH) over Iur interface.
+
+The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this module are in contrast to the above modules involving two peer CRNCs. The procedures in this module are also used in cases involving one RNC and one BSS.
+
+The MBMS Procedures module contains procedures that are specific to MBMS and used for cases that cannot be handled by other modules.
+
+## 6.3 User Plane Frame Protocols
+
+### 6.3.1 Iub/Iur DCH Frame Protocol
+
+There are two types of Iub/Iur DCH FP frames:
+
+- DCH data frame;
+- DCH control frame.
+
+The contents of the Iub/Iur DCH data frame include:
+
+- Transport Block Sets;
+- Quality estimate.
+
+The contents of the Iur DCH control frame include:
+
+- Measurement reports;
+- Power control information;
+
+- Synchronisation information.
+
+For a more detailed description of the Iur/Iub DCH frame protocol refer to 'UTRAN Iur & Iub Interface User Plane Protocol for DCH Data Streams' TS 25.427 [1].
+
+### 6.3.2 Iur DSCH Frame Protocol [TDD]
+
+There are two types of Iur DSCH FP frames:
+
+- DSCH data frame;
+- DSCH control frames.
+
+The contents of the Iur DSCH data frame include:
+
+- MAC-c/sh SDUs;
+- User Buffer Status.
+
+The contents of the Iur DSCH control frame include:
+
+- Flow control Information (UL);
+- Capacity Request Information (DL).
+
+For a more detailed description of the Iur DSCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2].
+
+### 6.3.3 Iur USCH Frame Protocol [TDD]
+
+There is one type of Iur USCH FP frames:
+
+- USCH data frame.
+
+The contents of the Iur USCH data frame include:
+
+- MAC-c/sh SDUs.
+
+For a more detailed description of the Iur USCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2].
+
+### 6.3.4 Iur RACH Frame Protocol
+
+For a more detailed description of the Iur RACH framing protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2].
+
+### 6.3.5 Iur FACH Frame Protocol
+
+For a more detailed description of the Iur FACH framing protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2].
+
+### 6.3.6 Iur HS-DSCH Frame Protocol
+
+There are two types of Iur HS-DSCH FP frames:
+
+- HS-DSCH data frame;
+- HS-DSCH control frames.
+
+The contents of the Iur HS-DSCH data frame include:
+
+- MAC-d PDUs;
+
+- User Buffer Status.
+
+The contents of the Iur HS-DSCH control frame include:
+
+- Flow control Information (UL);
+- Capacity Request Information (DL).
+
+For a more detailed description of the Iur HS-DSCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2].
+
+### 6.3.7 Iur E-DCH Frame Protocol
+
+There is one type of Iur E-DCH FP frames:
+
+- E-DCH data frame;
+
+The contents of the Iur E-DCH data frame include:
+
+- Mac-es PDUs (multiplexed);
+- Number of HARQ retransmissions;
+- CFN and Sub frame number.
+
+For a more detailed description of the Iur E-DCH frame protocol refer to 'UTRAN Iur Interface User Plane Protocols for DCH Data Streams' TS 25.427 [1].
+
+## 6.4 Mapping of Frame Protocols onto transport bearers
+
+|             |                                                                                                                                                                                             |
+|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DCH         | One Iur DCH data stream is carried on one transport bearer except in the case of co-ordinated DCHs in which case a set of co-ordinated DCHs are multiplexed onto the same transport bearer. |
+| [TDD - DSCH | One Iur DSCH data stream is carried on one transport bearer.]                                                                                                                               |
+| HS-DSCH     | One Iur HS-DSCH data stream is carried on one transport bearer.                                                                                                                             |
+| E-DCH       | One Iur E-DCH data stream is carried on one transport bearer. For each E-DCH data stream, a transport bearer must be established over the Iur interface.                                    |
+| [TDD - USCH | One Iur USCH data stream is carried on one transport bearer.]                                                                                                                               |
+| RACH        | Multiple RACH data streams may be carried on one transport bearer.                                                                                                                          |
+| FACH        | Multiple FACH data streams may be carried on one transport bearer.                                                                                                                          |
+
+RACH and FACH data streams for one UE are carried on same transport bearer.
+
+# --- 7 DRNS logical Model over I<sub>ur</sub>
+
+## 7.1 Overview
+
+The model in Figure 3 shows the Drift Radio Network System as seen from the SRNC. It is modelled as a «black box» with a set of Radio Links on the Uu side of the box and another set of User Plane access ports on the Iur side of the box. The Radio Links are connected to the Iur user ports via the internal transport mechanisms of the DRNS. Operations for controlling the connections between ports are sent from the SRNC to the DRNC via an Iur Control Plane port.
+
+![Figure 3: Drift RNS Logical Model diagram showing the architecture of a Drift Radio Network System (DRNS) connected to a Serving Radio Network System (SRNS).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+The diagram illustrates the logical model of a Drift Radio Network System (DRNS). At the top, a large rectangle represents the **Serving Radio Network System** (SRNS). Below it, the **Drift Radio Network System** (DRNS) is shown. The DRNS contains two **Cell** boxes, each enclosing three **Radio Link** circles. These Radio Links are connected to various **Iur Data Ports** located between the SRNS and the DRNS. The Iur Data Ports are of several types: **Iur Control Port**, **Iur DCH Data Port**, **Iur E-DCH Data Port**, **Iur TDD DSCH Data Port**, **Iur HS-DSCH Data Port**, and **Iur RACH/FACH Data Port**. A box labeled **RACH/FACH Traffic Contexts With attributes** is connected to the Iur RACH/FACH Data Ports. The bottom of the diagram is labeled **Radio User Plane**, indicating the flow of user data through the Radio Links.
+
+Figure 3: Drift RNS Logical Model diagram showing the architecture of a Drift Radio Network System (DRNS) connected to a Serving Radio Network System (SRNS).
+
+Figure 3: Drift RNS Logical Model
+
+## 7.2 Logical Model Elements
+
+### 7.2.1 Radio Link
+
+A Radio Link represents a User Plane access point on the UTRAN side of the Uu interface between the User Equipment and the UTRAN.
+
+The semantics of a Radio Link include the following:
+
+- It is created, destroyed, and added by SRNC.
+- It can be attached to one or more Iur Data Ports at any given time.
+- Its resources are allocated and controlled by the DRNS.
+
+### 7.2.2 Cell
+
+It is defined by:
+
+- A Cell identifier.
+
+The semantics of a Cell include the following:
+
+- It is created and destroyed by administrative procedures.
+
+### 7.2.3 Iur DCH Data Port
+
+One Iur 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 co-ordinated DCHs, in which case the data streams of all co-ordinated DCHs shall be multiplexed on one and the same user plane transport bearer.
+
+The semantics of an Iur DCH Data Port include the following:
+
+- It is created and destroyed by administrative procedures when transport facilities are added to, or deleted from, the Iur interface between the SRNS and DRNS. It can also be created and destroyed dynamically using dynamically setup transport bearers to add or remove transport facilities.
+
+- It is assigned and released by the SRNC in reaction to requests for bearer services from the UE.
+- It may be attached to one or more Radio Links. When attached to Radio Links in the downlink direction, it acts as a point-to-multipoint connection for diversity transmission. When attached to multiple Radio Links in the uplink direction, it acts as a multipoint-to-point connection for diversity reception [FDD].
+- The transmit and receive combining/splitting resources required to implement the point-to-multipoint and multipoint-to-point connections are controlled by the DRNS [FDD].
+- The Iur DCH Data Stream emanating from the Iur DCH Data Port terminates in the SRNS connected to DRNS.
+
+### 7.2.4 Iur DSCH Data Port [TDD]
+
+One Iur DSCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one DSCH data stream.
+
+### 7.2.5 Iur USCH Data Port [TDD]
+
+One Iur USCH Data port represents one Iur user plane transport bearer. One Iur user plane transport bearer will carry only one USCH data stream.
+
+### 7.2.6 Iur RACH/FACH Data Port
+
+The Iur RACH/FACH data port represents a transport bearer and is identified with a transport bearer identity.
+
+### 7.2.7 Iur Control Port
+
+An Iur Control Port represents the Control Plane access point on the Iur interface between the SRNS and the DRNS. It is defined by:
+
+- A transport bearer channel identifier.
+
+The semantics of an Iur Control Port include the following:
+
+- It is created via administrative procedures when the Iur interface is created.
+
+### 7.2.8 Iur HS-DSCH Data Port
+
+One Iur HS-DSCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one HS-DSCH data stream.
+
+### 7.2.9 Iur E-DCH Data Port
+
+One Iur E-DCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one E-DCH data stream. It is assigned and released by the SRNC in reaction to requests for bearer services from the UE. [FDD - It may be attached to one or more Radio Links. When attached to multiple Radio Links in the uplink direction, the receive combining resources required to implement the multipoint-to-point connections is in the NodeB of the DRNS.]
+
+# --- 8 Iur Interface Protocol Structure
+
+The Iur interface protocol architecture consists of two functional layers:
+
+- Radio Network Layer, defines the procedures related to the interaction of two RNCs within a PLMN. The radio network layer consists of a Radio Network Control Plane and a Radio Network User Plane.
+- Transport layer, defines procedures for establishing physical connections between two RNCs within a PLMN.
+
+![Figure 4: Iur Interface Protocol Structure. This diagram illustrates the protocol stack for the Iur interface between two Radio Network Controllers (RNCs). The stack is divided into three vertical sections: Control Plane, User Plane, and Transport Network Control Plane. The Control Plane on the left shows RNSAP at the top, connected to the Transport Network User Plane, which in turn connects to SCCP. SCCP is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. The User Plane on the right shows Iur Data Stream(s) at the top, connected to the Transport Network User Plane, which connects to AAL2 and UDP/IP. Below AAL2 and UDP/IP is ATM, which is connected to the Physical Layer. The Transport Network Control Plane in the center shows Q.2630.2 at the top, connected to STC (Q.2150.1). STC (Q.2150.1) is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. All three planes share a common Physical Layer at the bottom.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+Figure 4: Iur Interface Protocol Structure. This diagram illustrates the protocol stack for the Iur interface between two Radio Network Controllers (RNCs). The stack is divided into three vertical sections: Control Plane, User Plane, and Transport Network Control Plane. The Control Plane on the left shows RNSAP at the top, connected to the Transport Network User Plane, which in turn connects to SCCP. SCCP is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. The User Plane on the right shows Iur Data Stream(s) at the top, connected to the Transport Network User Plane, which connects to AAL2 and UDP/IP. Below AAL2 and UDP/IP is ATM, which is connected to the Physical Layer. The Transport Network Control Plane in the center shows Q.2630.2 at the top, connected to STC (Q.2150.1). STC (Q.2150.1) is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. All three planes share a common Physical Layer at the bottom.
+
+Figure 4: Iur Interface Protocol Structure
+
+# 9 Other I<sub>ur</sub> Interface Specifications
+
+## 9.1 UTRAN I<sub>ur</sub> Interface: Layer 1 (TS 25.421)
+
+TS 25.421 [3] specifies the range of physical layer technologies that may be used to support the I<sub>ur</sub> interface and the I<sub>ur-g</sub> interface.
+
+## 9.2 UTRAN I<sub>ur</sub> Interface: Signalling Transport (TS 25.422)
+
+TS 25.422 [4] specifies the signalling bearers for the RNSAP for I<sub>ur</sub> Interface and for I<sub>ur-g</sub> interface.
+
+## 9.3 UTRAN I<sub>ur</sub> Interface: RNSAP Specification (TS 25.423)
+
+TS 25.423 [5] specifies the RNSAP protocol for radio network control plane signalling over the I<sub>ur</sub> interface and over the I<sub>ur-g</sub> interface.
+
+## 9.4 UTRAN I<sub>ur</sub> Interface: Data Transport and Transport Signalling for Common Transport Channel Data Streams (TS 25.424)
+
+TS 25.424 [6] specifies the transport bearers for the user plane of the I<sub>ur</sub> interface. It also specifies the ALCAP protocol used to control these transport bearers.
+
+## 9.5 UTRAN I<sub>ur</sub> Interface: User Plane Protocols for Common Transport Channel Data Streams (TS 25.425)
+
+TS 25.425 [2] specifies the user plane frame handling protocol for the common channels on I<sub>ur</sub> interface.
+
+## 9.6 UTRAN Iur & Iub Interface: Data Transport and Transport Signalling for DCH Data Streams (TS 25.426)
+
+TS 25.426 [8] specifies the transport bearers for the user plane of the Iub/Iur interface. It also specifies the ALCAP protocol used to control these transport bearers.
+
+## 9.7 UTRAN Iur & Iub Interface: User Plane Protocols for DCH Data Streams (TS 25.427)
+
+TS 25.427 [1] specifies the user plane frame handling protocol for the dedicated channels on Iub/Iur interface.
+
+## 9.8 Summary of UTRAN Iur Interface Technical Specifications
+
+The relationship between the technical specifications that define the UTRAN Iur interface is shown in Figure 5.
+
+![Figure 5: Iur Interface Technical Specifications diagram showing the relationship between Radio Network Control Plane, Transport Network Control Plane, and User Plane across Radio Network Layer and Transport Layer.](19a59d6b53059ebd27b13c98793f88e0_img.jpg)
+
+|                     | Radio Network Control Plane       | Transport Network Control Plane                                                                                      | User Plane                                   |                                           |
+|---------------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-------------------------------------------|
+| Radio Network Layer | RNSAP<br>TS 25.423                |                                                                                                                      | Dedicated Channels<br>TS 25.427              | Common Channels<br>TS 25.425              |
+| Transport Layer     | Signalling Transport<br>TS 25.422 | Transport Signaling<br><br>TS 25.426<br>(Dedicated Channel Transport)<br><br>TS 25.424<br>(Common Channel Transport) | Dedicated Channel Transport<br><br>TS 25.426 | Common Channel Transport<br><br>TS 25.424 |
+|                     |                                   | Physical Layer TS 25.421                                                                                             |                                              |                                           |
+
+Figure 5: Iur Interface Technical Specifications diagram showing the relationship between Radio Network Control Plane, Transport Network Control Plane, and User Plane across Radio Network Layer and Transport Layer.
+
+Figure 5: Iur Interface Technical Specifications
+
+# Annex A (informative): Change History
+
+| TSG #   | TSG Doc.  | CR   | Rev | Subject/Comment                                                | New    |
+|---------|-----------|------|-----|----------------------------------------------------------------|--------|
+| 12/2008 | -         | -    | -   | Rel-8 version created based on v7.3.0                          | 8.0.0  |
+| 42      | RP-080849 | 0059 | -   | Enable to dynamically control the MBMS services in MBSFN       | 8.0.0  |
+| 43      | RP-090078 | 0060 | 1   | RNSAP: Enhanced Relocation Request in SCCP: Connection Request | 8.1.0  |
+| 12/2009 | -         | -    | -   | Created Rel-9 version based on v8.1.0                          | 9.0.0  |
+| 49      | RP-100909 | 0061 | -   | CS Data forwarding support for Iur interface                   | 9.1.0  |
+| SP-49   | SP-100629 |      |     | Clarification on the use of References (TS 21.801 CR#0030)     | 9.1.1  |
+| 03/2011 |           |      |     | Created Rel-10 version based on v9.1.1                         | 10.0.0 |
+| 06/2011 | RP-110684 | 0063 | -   | Correction of references                                       | 10.1.0 |
+| 06/2011 | RP-110694 | 0064 | 2   | Introduction of Enhancements of Iur-g Interface                | 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      |
+| 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/25421/raw.md

@@ -0,0 +1,118 @@
+
+
+# 3GPP TS 25.421 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iur 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        |
+| 3.1 Definitions.....                              | 5        |
+| 3.3 Abbreviations .....                           | 5        |
+| 4 Iur Layer 1.....                                | 5        |
+| <b>Annex A (informative): Change history.....</b> | <b>6</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 standards allowed to implement Layer 1 on the Iur interface. The specification of transmission delay requirements and O&M requirements are 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".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.411 [1] apply.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 25.411 [1] apply.
+
+# --- 4 Iur Layer 1
+
+The Iur Layer 1 shall comply with the requirements of chapter 4 in TS 25.411 [1].

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

@@ -0,0 +1,380 @@
+
+
+# 3GPP TS 25.426 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iur and Iub interface data transport & transport signalling for DCH data streams (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.
+
+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         |
+| 4 Data Link Layer .....                                                 | 7         |
+| 4.1 ATM Transport Option .....                                          | 7         |
+| 4.1.1 Protection Switching at ATM Layer .....                           | 7         |
+| 4.2 IP Transport Option.....                                            | 7         |
+| 5 Iur and Iub Data Transport for DCH and E-DCH Data Streams .....       | 8         |
+| 5.1 Introduction .....                                                  | 8         |
+| 5.2 ATM Transport Option .....                                          | 8         |
+| 5.3 IP Transport Option.....                                            | 8         |
+| 6 Transport Signalling Application for DCH and E-DCH Data Streams ..... | 9         |
+| 6.1 Introduction .....                                                  | 9         |
+| 6.2 ALCAP in ATM Transport Option .....                                 | 9         |
+| 6.3 ALCAP in IP Transport Option .....                                  | 9         |
+| 7 Signalling Bearer for ALCAP on Iub Interface .....                    | 9         |
+| 7.1 Introduction .....                                                  | 9         |
+| 7.2 Signalling Bearer in ATM Transport Option .....                     | 10        |
+| 7.3 Signalling Bearer in IP Transport Option .....                      | 10        |
+| 8 Signalling Bearer for ALCAP on Iur Interface.....                     | 10        |
+| 8.1 Introduction .....                                                  | 10        |
+| 8.2 Signalling Bearer in ATM Transport Option .....                     | 11        |
+| 8.3 Signalling Bearer in IP Transport Option .....                      | 11        |
+| 9 Interworking between ATM and IP Transport Options.....                | 11        |
+| 9.1 Introduction .....                                                  | 11        |
+| 9.2 Interworking Alternatives .....                                     | 11        |
+| <b>Annex A (informative): Change history.....</b>                       | <b>13</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 transport bearers for the DCH/E-DCH data streams on UTRAN Iur and Iub interfaces. The corresponding Transport Network Control plane is also specified. The physical layer for the transport bearers is outside the scope of the present document.
+
+# --- 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.427: "UTRAN Iub/Iur interface user plane protocol for DCH data streams".
+- [2] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [3] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation Layer specification; Type 2 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 Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)".
+- [6] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing".
+- [7] ITU-T Recommendation X.213 (1995-11): "Information Technology - Open Systems Interconnection - Systems Interconnection - Network Service Definition".
+- [8] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)".
+- [9] 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 at UNI)".
+- [10] ITU-T Recommendation Q.2150.2 (1999-12): "AAL type 2 signalling transport converter on SSCOP".
+- [11] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of the ITU-T Recommendation Q.2140".
+- [12] 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 at NNI)".
+- [13] ITU-T Recommendation Q.2150.1 (1999-12): "AAL type 2 signalling transport converter on broadband MTP".
+- [14] IETF RFC 791 (1981-09): "Internet Protocol".
+- [15] IETF RFC 1483 (1993-07): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".
+- [16] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM".
+
+- [17] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [18] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol".
+- [19] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)".
+- [20] ITU-T Recommendation I.630 (1999-02): "ATM protection switching".
+- [21] ITU-T Recommendation Q.Imp2210 (1996-07): "Implementor's guide (03/99) for Recommendation Q.2210 (07/96)".
+- [22] ITU-T Recommendation Q.2630.2 (2000-12): "AAL type 2 signalling protocol (Capability Set 2)".
+- [23] IETF RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)".
+- [24] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing".
+- [25] IETF RFC 2507 (1999-02): "IP header compression".
+- [26] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".
+- [27] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [28] IETF RFC 2509 (1999-02): "IP Header Compression over PPP".
+- [29] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
+- [30] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [31] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [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] Void
+- [36] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan ".
+- [37] IETF RFC 3309 (2002-09): "SCTP Checksum Change".
+- [38] 3GPP TS 25.414: "UTRAN Iu Interface data transport & transport signalling".
+- [39] 3GPP TS 25.401: "UTRAN overall description".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following term and definition applies:
+
+**ALCAP:** transport signalling protocol used to setup and tear down transport bearers
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+AAL2                    ATM Adaptation Layer type 2
+
+|         |                                                       |
+|---------|-------------------------------------------------------|
+| AESA    | ATM End System Address                                |
+| ATM     | Asynchronous Transfer Mode                            |
+| CPCS    | Common Part Convergence Sublayer                      |
+| CPS     | Common Part Sublayer                                  |
+| DCH     | Dedicated Channel                                     |
+| E-DCH   | Enhanced DCH                                          |
+| HDLC    | High level Data Link Control                          |
+| HS-DSCH | High Speed Downlink Shared Channel                    |
+| IP      | Internet Protocol                                     |
+| LC      | Link Characteristics                                  |
+| M3UA    | SS7 MTP3 User Adaptation layer                        |
+| ML/MC   | Multi-link / Multi-class                              |
+| MPLS    | Multiprotocol Label Switching                         |
+| MTP     | Message Transfer Part                                 |
+| NNI     | Network-Node Interface                                |
+| NSAP    | Network Service Access Point                          |
+| PPP     | Point to Point Protocol                               |
+| PT      | Path Type                                             |
+| SAAL    | Signalling ATM Adaptation Layer                       |
+| SAR     | Segmentation and Reassembly                           |
+| SCTP    | Stream Control Transmission Protocol                  |
+| SSCF    | Service Specific Co-ordination Function               |
+| SSCP    | Service Specific Connection Oriented Protocol         |
+| SSCS    | Service Specific Convergence Sublayer                 |
+| SSSAR   | Service Specific Segmentation and Reassembly sublayer |
+| STC     | Signalling Transport Converter                        |
+| UDP     | User Datagram Protocol                                |
+| UNI     | User-Network Interface                                |
+
+# --- 4 Data Link Layer
+
+## 4.1 ATM Transport Option
+
+ATM shall be used in the transport network user plane and transport network control plane according to ITU-T Rec. I.361 [2].
+
+### 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 [20].
+
+## 4.2 IP Transport Option
+
+A UTRAN node supporting IP transport option shall support PPP protocol IETF RFC 1661 [23] with HDLC framing (IETF RFC 1662 [24]).
+
+NOTE: This does not preclude the single implementation and use of any other L2/L1 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 towards the upper layers.
+
+A UTRAN node supporting IP transport option and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [25]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [26], IETF RFC 2686 [27]). In this case the negotiation of header compression (ITU-T Rec. I.630 [20]) over PPP shall be performed via IETF RFC 2509 [28].
+
+# 5 Iur and Iub Data Transport for DCH and E-DCH Data Streams
+
+## 5.1 Introduction
+
+The Frame Protocol for DCH and E-DCH data streams (TS 25.427 [1]) is the user of the transport layer specified in the present document.
+
+There are two options for the transport layer of the DCH and E-DCH 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 from top to bottom: 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 from top to bottom: Radio Network Layer, UDP (RFC768), IPv6 (RFC2460) with IPv4 optional (RFC791), Data link layer, and Physical layer. Both stacks are labeled with 'Transport Network Layer' on the left side.](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+Protocol stack for ATM transport option
+Protocol stack for IP transport option
+
+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 from top to bottom: 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 from top to bottom: Radio Network Layer, UDP (RFC768), IPv6 (RFC2460) with IPv4 optional (RFC791), Data link layer, and Physical layer. Both stacks are labeled with 'Transport Network Layer' on the left side.
+
+**Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces**
+
+## 5.2 ATM Transport Option
+
+Asynchronous Transfer Mode (ATM) (ITU-T Rec. I.361 [2]) and ATM Adaptation Layer type 2 (AAL2) (ITU-T Rec. I.363.2 [3], ITU-T Rec. I.366.1 [4]) are used as a transport layer for DCH and E-DCH data streams on Iur and Iub interfaces. Service Specific Segmentation and Reassembly (SSSAR) sublayer for AAL2 is used for the segmentation and reassembly of AAL2 SDUs.
+
+## 5.3 IP Transport Option
+
+UDP (IETF RFC 768 [17]) over IP shall be supported as the transport for DCH and E-DCH data streams on Iub and Iur interfaces. The data link layer is as specified in chapter 4.2.
+
+An IP UTRAN Node shall support IPv6 (IETF RFC 2460[29]). The support of IPv4 (IETF RFC 791[14]) 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.
+
+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 Radio Network Layer on the Iur/Iub interface shall use the NSAP structure. See sub clause 6.1.8.2 of TS 25.401 [39].
+
+IP Differentiated Services code point marking (IETF RFC 2474 [30]) 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 Transport Signalling Application for DCH and E-DCH Data Streams
+
+## 6.1 Introduction
+
+This chapter specifies the ALCAP protocol(s) to be used in Iur and Iub interfaces for DCH data streams.
+
+## 6.2 ALCAP in ATM Transport Option
+
+AAL2 signalling protocol Capability Set 2 (ITU-T Rec. Q.2630.2 [22]) is the signalling protocol to control AAL2 connections on Iub and Iur interfaces. ITU-T Rec. Q.2630.2 [22] adds new optional capabilities to ITU-T Rec. Q.2630.1 [5].
+
+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 [22].
+
+User Plane Transport bearers for Iur interface are established, in all normal cases released and optionally modified by the ALCAP in the Serving RNC. 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 for Iub interface are established, in all normal cases released and optionally modified by the ALCAP in the Controlling RNC. Binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iub interface in the Node B. In case of a Reset initiated by the CRNC, the ALCAP in the Node B shall release the transport bearers involved in the impacted Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers for the removed dedicated channels that were remaining within the cell when the cell is deleted.
+
+AAL2 transport layer addressing is based on embedded E.164 or other AESA variants of the NSAP addressing format (ITU-T Rec. E.191 [6], ITU-T Rec. X.213 [7]). Native E.164 addressing (ITU-T Rec. E.164 [36]) shall not be used.
+
+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 AAL2 signalling messages as specified in reference ITU-T Rec. Q.2630.2 [22] is 2048 Kbit/s, it shall be interpreted as bit rate 2048 Kbit/s or higher.
+
+NOTE: Separation of traffic (e.g. HS-DSCH, E-DCH) that is using this modified interpretation of Link Characteristics in ref. ITU-T Rec. Q.2630.2 [22] 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 ALCAP in IP Transport Option
+
+An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option.
+
+Application of ALCAP in IP to ATM interworking case is defined in chapter 9 of this Technical Specification.
+
+# 7 Signalling Bearer for ALCAP on Iub Interface
+
+## 7.1 Introduction
+
+This clause specifies the signalling bearer for the ALCAP on Iub interface.
+
+## 7.2 Signalling Bearer in ATM Transport Option
+
+SAAL-UNI (ITU-T Rec. Q.2110 [8], ITU-T Rec. Q.2130 [9]) is used as the signalling bearer for the AAL Type 2 Signalling protocol on Iub interface. Signalling Transport Converter for SSCOP is applied ITU-T Rec. Q.2150.2 [10]. The following figure shows the signalling bearer protocol stack for the ALCAP on Iub interface.
+
+![Figure 2: Signalling bearer for ALCAP on Iub interface. The diagram shows a protocol stack with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.2). Below STC is AAL5 SSCS, which contains SSCF-UNI and SSCOP. Below AAL5 SSCS is AAL5 Common Part, which contains CPCS and SAR. Below AAL5 Common Part is ATM, and at the bottom is PHY. The entire stack from STC to PHY is enclosed in a dashed box, and a horizontal line passes through the middle of the stack.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg)
+
+|                     |          |
+|---------------------|----------|
+| ALCAP<br>(Q.2630.2) |          |
+| STC<br>(Q.2150.2)   |          |
+| AAL5 SSCS           | SSCF-UNI |
+|                     | SSCOP    |
+| AAL5 Common Part    | CPCS     |
+|                     | SAR      |
+| ATM                 |          |
+| PHY                 |          |
+
+Figure 2: Signalling bearer for ALCAP on Iub interface. The diagram shows a protocol stack with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.2). Below STC is AAL5 SSCS, which contains SSCF-UNI and SSCOP. Below AAL5 SSCS is AAL5 Common Part, which contains CPCS and SAR. Below AAL5 Common Part is ATM, and at the bottom is PHY. The entire stack from STC to PHY is enclosed in a dashed box, and a horizontal line passes through the middle of the stack.
+
+Figure 2: Signalling bearer for ALCAP on Iub interface
+
+## 7.3 Signalling Bearer in IP Transport Option
+
+An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option.
+
+# --- 8 Signalling Bearer for ALCAP on Iur Interface
+
+## 8.1 Introduction
+
+This clause specifies the signalling bearer for the ALCAP on the Iur interface.
+
+## 8.2 Signalling Bearer in ATM Transport Option
+
+There are two protocol stacks specified for Iur ALCAP Signalling Bearer in ATM option - one based on MTP-3B (ITU-T Rec. Q.2210 [11], ITU-T Rec. Q.Imp2210 [21]) and SAAL-NNI (ITU-T Rec. Q.2140 [12], ITU-T Rec. Q.2110 [8]) and the other based on SCTP (IETF RFC 2960 [18]). Signalling Transport Converter for MTP-3B is applied (ITU-T Rec. Q.2150.1 [13]). MTP-3 User Adaptation Layer (M3UA) for SCTP is applied in IETF RFC 3332 [19]. Classical IP over ATM is specified in IETF RFC 2225 [16]. Multiprotocol Encapsulation over AAL5 is specified in IETF RFC 1483 [15]. The checksum method specified in IETF RFC 3309 [37] shall be used instead of the method specified in IETF RFC 2960 [18]. The following figure shows the signalling bearer protocol stacks for the ALCAP on Iur interface.
+
+![Figure 3: Signalling bearers for ALCAP on Iur interface. The diagram shows two protocol stacks. The left stack is for an MTP-3B based Iur ALCAP Signalling Bearer, and the right stack is for an IP based Iur ALCAP Signalling Bearer. Both stacks start with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1). The left stack then has MTP-3B, followed by AAL5 SSCS (SSCF-NNI, SSCOP) and AAL5 Common Part (CPCS, SAR), then ATM, and finally PHY. The right stack has M3UA, SCTP, IP, AAL5, ATM, and finally PHY.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+| MTP-3B based Iur ALCAP Signalling Bearer | IP based Iur ALCAP Signalling Bearer |
+|------------------------------------------|--------------------------------------|
+| ALCAP (Q.2630.2)                         | ALCAP (Q.2630.2)                     |
+| STC (Q.2150.1)                           | STC (Q.2150.1)                       |
+| MTP-3B                                   | M3UA                                 |
+| AAL5 SSCS (SSCF-NNI, SSCOP)              | SCTP                                 |
+| AAL5 Common Part (CPCS, SAR)             | IP                                   |
+| ATM                                      | AAL5                                 |
+| PHY                                      | ATM                                  |
+|                                          | PHY                                  |
+
+Figure 3: Signalling bearers for ALCAP on Iur interface. The diagram shows two protocol stacks. The left stack is for an MTP-3B based Iur ALCAP Signalling Bearer, and the right stack is for an IP based Iur ALCAP Signalling Bearer. Both stacks start with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1). The left stack then has MTP-3B, followed by AAL5 SSCS (SSCF-NNI, SSCOP) and AAL5 Common Part (CPCS, SAR), then ATM, and finally PHY. The right stack has M3UA, SCTP, IP, AAL5, ATM, and finally PHY.
+
+Figure 3: Signalling bearers for ALCAP on Iur interface
+
+## 8.3 Signalling Bearer in IP Transport Option
+
+An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option.
+
+# 9 Interworking between ATM and IP Transport Options
+
+## 9.1 Introduction
+
+This clause specifies the interworking between IP and ATM transport options. A UTRAN node supporting IP transport option shall provide interworking to a UTRAN node supporting only ATM transport option.
+
+## 9.2 Interworking Alternatives
+
+For interworking with a UTRAN node supporting only ATM option, the UTRAN node supporting IP option shall additionally support at least one of the following interworking mechanisms:
+
+- 1) ATM&IP dual stack. An ALCAP protocol is not required in this interworking solution.
+
+Annex A of TS 25.414 [38] 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 UTRAN node. AAL2 signalling protocol Capability Set 2 (ITU-T Rec. Q.2630.2 [22]) shall be supported as ALCAP protocol between the Interworking Function and the UTRAN node supporting ATM transport option.
+
+Annex A of TS 25.414 [38] shows an example of a protocol stack for the bearer control protocol between the RNC/CN IP Node and its IWF for the case when the IWF is an external unit to the RNC/CN node. Other protocol stacks for this case are not precluded.

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

@@ -0,0 +1,353 @@
+
+
+# 3GPP TS 25.434 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub interface data transport and transport signalling for Common Transport Channel data streams (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  
+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         |
+| 3.4 Specification Notations .....                                                                  | 7         |
+| 4 Data Link Layer .....                                                                            | 8         |
+| 4.1 ATM Transport Option .....                                                                     | 8         |
+| 4.1.1 Protection Switching at ATM Layer .....                                                      | 8         |
+| 4.2 Data Link Layer for IP Transport Option.....                                                   | 8         |
+| 5 I <sub>ub</sub> Data Transport for Common Transport Channel Data Streams.....                    | 8         |
+| 5.1 Introduction .....                                                                             | 8         |
+| 5.2 ATM Transport Option .....                                                                     | 9         |
+| 5.3 IP Transport Option.....                                                                       | 9         |
+| 6 I <sub>ub</sub> Transport Signalling Application for Common Transport Channel Data Streams ..... | 10        |
+| 6.1 Introduction .....                                                                             | 10        |
+| 6.2 Transport Signalling in case of ATM Transport Option .....                                     | 10        |
+| 6.3 Transport Signalling in case of IP Transport Option .....                                      | 10        |
+| 7 Signalling Bearer for ALCAP on I <sub>ub</sub> Interface.....                                    | 10        |
+| 7.1 Introduction .....                                                                             | 10        |
+| 7.2 Signalling Bearer in ATM Transport Option .....                                                | 11        |
+| 7.3 Signalling Bearer in IP Transport Option .....                                                 | 11        |
+| 8 Interworking between ATM and IP Transport Options.....                                           | 11        |
+| <b>Annex A (informative): Change history.....</b>                                                  | <b>12</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-Node B (Iub) 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.363.2 (2000-11): "B-ISDN ATM Adaptation layer specification: Type 2 AAL".
+- [2] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2".
+- [3] ITU-T Recommendation Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)".
+- [4] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)".
+- [5] 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 at UNI)".
+- [6] ITU-T Recommendation Q.2150.2 (1999-12): "Signalling transport converter on SSCOP and SSCOPMCE".
+- [7] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".
+- [8] ITU-T Recommendation I.630 (1999-02): "ATM protection switching".
+- [9] ITU-T Recommendation Q.2630.2 (2000-12): "AAL Type 2 signalling protocol (Capability Set 2)".
+- [10] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing".
+- [11] ITU-T Recommendation X.213 (1995-11): "Information Technology - Open Systems Interconnection - Network Service Definition".
+- [12] IETF RFC 768, (1980-08): "User Datagram Protocol".
+- [13] IETF RFC 2460, (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
+- [14] IETF RFC 791, (1981-09): "Internet Protocol".
+- [15] IETF RFC 2474, (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [16] IETF RFC 1661, (1994-07): "The Point-to-Point Protocol (PPP)".
+- [17] IETF RFC 1662, (1994-07): "PPP in HDLC-like Framing".
+
+- [18] IETF RFC 2507, (1999-02): "IP header compression".
+- [19] IETF RFC 1990, (1996-08): "The PPP Multilink Protocol (MP)".
+- [20] IETF RFC 2686, (1999-09): "The Multi-Class Extension to Multi-Link PPP".
+- [21] Void
+- [22] 3GPP TS 25.401, "UTRAN Overall Description"
+- [23] 3GPP TS 25.426, "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams"
+- [24] IETF RFC 3153, (2001-08): "PPP Multiplexing".
+- [25] IETF RFC 2364, (1998-07): "PPP over AAL5".
+- [26] IETF RFC 3031, (2001-01): "Multiprotocol Label Switching Architecture".
+- [27] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan".
+- [28] IETF RFC 3376 (2002-10), "Internet Group Management Protocol, Version 3".
+- [29] IETF RFC 3810 (2004-06), "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".
+- [30] IETF RFC 3544, (2003-07): "IP Header Compression over PPP".
+
+# --- 3 Definitions, symbols and abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**ALCAP:** "ALCAP" is a generic name for the transport signalling protocol used to setup and tear down transport bearers.
+
+**IP UTRAN node:** An UTRAN Node supporting the IP Transport Option
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+|         |                                    |
+|---------|------------------------------------|
+| AAL     | ATM Adaption Layer                 |
+| AAL2    | AAL Type 2                         |
+| ATM     | Asynchronous Transfer Mode         |
+| CPCS    | Common Part Convergence Sublayer   |
+| CPS     | Common Part Sublayer               |
+| DSCH    | Downlink Shared Channel            |
+| FACH    | Forward Access Channel             |
+| FP      | Frame Protocol                     |
+| HDLC    | High-level Data Link Control       |
+| HS-DSCH | High Speed Downlink Shared Channel |
+| IP      | Internet Protocol                  |
+| LC      | Link Characteristics               |
+| PPP     | Point-to-Point Protocol            |
+
+|       |                                               |
+|-------|-----------------------------------------------|
+| PT    | Path Type                                     |
+| RACH  | Random Access Channel                         |
+| RNC   | Radio Network Controller                      |
+| SAAL  | Signalling ATM Adaption Layer                 |
+| SAR   | Segmentation And Reassembly                   |
+| SSCF  | Service Specific Co-ordination Function       |
+| SSCOP | Service Specific Connection Oriented Protocol |
+| SSCS  | Service Specific Convergence Sublayer         |
+| SSSAR | Service Specific Segmentation And Reassembly  |
+| STC   | Signalling Transport Converter                |
+| UDP   | User Datagram Protocol                        |
+| UMTS  | Universal Mobile Telecommunication Network    |
+| UNI   | User-Network Interface                        |
+| USCH  | Uplink Shared Channel                         |
+| UTRAN | UMTS Terrestrial Radio Access Network         |
+
+## 3.4 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 [7].
+
+### 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 Recommendation I.630 [8].
+
+## 4.2 Data Link Layer for IP Transport Option
+
+An RNC or Node B supporting IP Transport Option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [16], IETF RFC 1662 [17]).
+
+NOTE: This does not preclude the single implementation and use of any other L2/L1 protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [24], IETF RFC 2364 [25]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [26]), etc.) fulfilling the UTRAN requirements towards the upper layers.
+
+An RNC or Node B supporting IP transport option and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [18]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [19], IETF RFC 2686 [20]). In this case, negotiation of header compression (IETF RFC 2507 [18]) over PPP shall be performed via (IETF RFC 3544 [30]).
+
+# --- 5 Iub Data Transport for Common Transport Channel Data Streams
+
+## 5.1 Introduction
+
+This subclause specifies the transport layers that support Common Transport Channel (FACH, RACH, PCH, DSCH, HS-DSCH, USCH [TDD]) data streams.
+
+There are two options for protocol suites for transport of RACH, FACH, USCH [TDD], DSCH and HS-DSCH Iub data streams:
+
+- 1) ATM Transport Option
+- 2) IP Transport Option
+
+The following figure 1 shows the protocol stacks of these two options:
+
+![Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams. The diagram shows two protocol stacks connected to a common Radio Network Layer. The left stack is for the ATM Transport Option, and the right stack is for the IP Transport Option.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates two protocol stacks for transporting data streams from the Radio Network Layer. Both stacks share a common Radio Network Layer at the top, which handles FP for RACH, FACH, PCH, DSCH [TDD], HS-DSCH, and USCH [TDD].
+
+**Protocol Stack for ATM Transport Option (Left):**
+
+- Radio Network Layer:** FP for RACH, FACH, PCH, DSCH [TDD], HS-DSCH, USCH [TDD]
+- Transport Network Layer:**
+  - AAL2 SSSAR (I.366.1)
+  - AAL2 CPS (I.363.2)
+  - ATM
+- PHY**
+
+**Protocol Stack for IP Transport Option (Right):**
+
+- Radio Network Layer:** FP for RACH, FACH, PCH, DSCH [TDD], HS-DSCH, USCH [TDD]
+- Transport Network Layer:**
+  - UDP
+  - IP
+- Data Link Layer**
+- Physical Layer**
+
+Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams. The diagram shows two protocol stacks connected to a common Radio Network Layer. The left stack is for the ATM Transport Option, and the right stack is for the IP Transport Option.
+
+**Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams**
+
+## 5.2 ATM Transport Option
+
+ATM and AAL2 (ITU-T Rec. I.363.2 [1] and ITU-T Rec. I.366.1 [2]) are used at the standard transport layer for Iub RACH, FACH, PCH, DSCH [TDD], USCH [TDD], HS-DSCH data streams.
+
+The Service Specific Segmentation and Reassembly (SSSAR) sublayer is used for the segmentation and reassembly of AAL2 SDUs (i.e. SSSAR is only considered from ITU-T Recommendation I.366.1 [2]).
+
+## 5.3 IP Transport Option
+
+UDP (IETF RFC 768 [12]) over IP shall be supported as the transport for RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH data streams on Iub Interface. The data link layer is as specified in chapter 4.2
+
+An IP UTRAN node shall support IPv6 (IETF RFC 2460 [13]). The support of IPv4 (IETF RFC 791 [14]) 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.
+
+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 Radio Network Layer on the Iur/Iub interface shall use the NSAP structure. See sub clause 6.1.8.2 of TS 25.401 [22].
+
+IP Differentiated Services code point marking (IETF RFC 2474 [15]) 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.
+
+IP multicast (IETF RFC 3376 [28], IETF RFC 3810 [29]) may be supported for FACH data streams on Iub Interface if the security of RAN will not be compromised. This can be guaranteed in a closed IP based RAN.
+
+# 6 I<sub>ub</sub> Transport Signalling Application for Common Transport Channel Data Streams
+
+## 6.1 Introduction
+
+This subclause specifies the transport signalling protocol(s) used to establish the user plane transport bearers. The protocol stack is shown in clause 7 (figure 2).
+
+## 6.2 Transport Signalling in case of ATM Transport Option
+
+Q.2630.2 as developed by ITU-T [9] is selected as the standard AAL2 signalling protocol for I<sub>ub</sub>. ITU-T Recommendation Q.2630.2 [9] adds new optional capabilities to ITU-T Recommendation Q.2630.1 [3].
+
+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 [9]. The binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the I<sub>ub</sub> interface in the Node B.
+
+User Plane Transport bearers are established and in all normal cases released by the ALCAP in the Controlling RNC. The Node B shall initiate release of the user plane transport bearers for the removed common channels that were remaining within the cell when the cell is deleted.
+
+AAL2 transport layer addressing is based on embedded E.164 (ITU-T Rec. E.164 [27]) or other AESA variants of the NSAP addressing format (ITU-T Rec. E.191 [10], ITU-T Rec. X.213 [11]). Native E.164 addressing (ITU-T Rec. E.164 [27]) shall not be used.
+
+If there is an AAL2 switching function in the transport network layer of the interface, 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 AAL2 signalling messages as specified in reference ITU-T Rec. Q.2630.2 [9] is 2048 Kbit/s, it shall be interpreted as bit rate 2048 Kbit/s or higher.
+
+NOTE: Separation of traffic (e.g. HSDPA) using this modified ITU-T Rec. Q.2630.2 [9] from other traffic is highly recommended. Otherwise the bursty nature of the HSDPA traffic in combination with the unknown traffic volume per connection for bit rates exceeding 2048 Kbit/s 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 UTRAN Nodes (RNC and Node B) are using the IP Transport Option.
+
+# 7 Signalling Bearer for ALCAP on I<sub>ub</sub> Interface
+
+## 7.1 Introduction
+
+This subclause specifies the signalling bearer protocol stack which supports the ALCAP.
+
+## 7.2 Signalling Bearer in ATM Transport Option
+
+SAAL-UNI is the standard signalling bearer for the AAL Type Signalling protocol (ITU-T Rec. Q.2630.2 [9]) on Iub (ITU-T Rec. Q.2110 [4], ITU-T Rec. Q.2130 [5]). The protocol stack is shown in figure 2.
+
+![Figure 2: Transport Network Control plane protocol structure on Iub in case of ATM Transport Option. The diagram shows a protocol stack with five layers. From top to bottom: Q.2630.2 (dashed box), STC (Q.2150.2) (solid box), AAL5 SSCS (SSCF-UNI, SSCOP) (solid box), AAL5 Common Part (CPCS / SAR) (dashed box), and PHY (dashed box). The layers are connected by a vertical line with an oval at the top, indicating the interface.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+Figure 2: Transport Network Control plane protocol structure on Iub in case of ATM Transport Option. The diagram shows a protocol stack with five layers. From top to bottom: Q.2630.2 (dashed box), STC (Q.2150.2) (solid box), AAL5 SSCS (SSCF-UNI, SSCOP) (solid box), AAL5 Common Part (CPCS / SAR) (dashed box), and PHY (dashed box). The layers are connected by a vertical line with an oval at the top, indicating the interface.
+
+**Figure 2: Transport Network Control plane protocol structure on Iub in case of ATM Transport Option**
+
+The signalling transport converter (STC) relevant for Iub is ITU-T Recommendation Q.2150.2 [6]. The AAL5 Common Part contains CPCS and SAR.
+
+## 7.3 Signalling Bearer in IP Transport Option
+
+An ALCAP protocol is not required in case of both UTRAN Nodes (RNC and Node B) are using the IP Transport Option.
+
+# --- 8 Interworking between ATM and IP Transport Options
+
+An RNC or Node B supporting IP transport option shall provide interworking to an RNC or Node B supporting only ATM transport option. The interworking alternatives are defined in TS 25.426 [23].

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

@@ -0,0 +1,219 @@
+
+
+# 3GPP TS 25.442 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN implementation-specific O&M 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 '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.
+
+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 .....                           | 5        |
+| 4 Implementation Specific O&M Transport.....      | 6        |
+| 4.1 Requirements.....                             | 6        |
+| 4.2 Routing.....                                  | 6        |
+| 4.3 Transport Bearer.....                         | 7        |
+| 4.3.1 ATM Transport Option.....                   | 7        |
+| 4.3.2 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 transport of implementation specific O&M signalling between Node B and the Management Platform in case that the transport is routed via the RNC.
+
+# --- 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] Void
+- [3] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Type 5 Specification".
+- [4] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM".
+- [5] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".
+- [6] IETF RFC 791 (1981-09): "Internet Protocol".
+- [7] Void
+- [8] 3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport&Transport Signalling for DCH".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Logical O&M:** Logical O&M is the signalling associated with the control of logical resources owned by the RNC but physically implemented in Node B.
+
+**Implementation Specific O&M:** Implementation Specific O&M functions depend on the implementation of the Node B, both for its hardware and software components.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                             |
+|------|-----------------------------|
+| AAL5 | ATM Adaptation Layer type 5 |
+| ATM  | Asynchronous Transfer Mode  |
+| ARP  | Address Resolution Protocol |
+| RFC  | Request For Comment         |
+| IP   | Internet Protocol           |
+
+|     |                           |
+|-----|---------------------------|
+| O&M | Operation and Maintenance |
+| RNC | Radio Network Controller  |
+| TNL | Transport Network Layer   |
+
+# 4 Implementation Specific O&M Transport
+
+## 4.1 Requirements
+
+While this specification only addresses the transport of Node B Implementation Specific O&M signalling, many of the following requirements are derived from generic requirements for O&M of UMTS network elements:
+
+- Common O&M infrastructure for all network elements.
+- Independence from various data link protocols.
+- Support of various higher layer protocols and applications.
+- Secure transmission.
+- No Impact of O&M transport on traffic transport and signalling.
+- Re-use of existing transport facilities, i.e. co-existence of Iub and Implementation Specific O&M on the same bearer.
+
+## 4.2 Routing
+
+It is the responsibility of the RNC to route Implementation Specific O&M signalling traffic. The traffic exchanged over this signalling link is completely transparent to the RNC. Both RNC and Node B have to support the routing of Implementation specific O&M via the RNC.
+
+![Diagram illustrating Implementation Specific O&M Transport via RNC. The diagram shows a central RNC connected to two Node Bs (one blue, one yellow) and a Management Platform(s). The RNC contains an RNC O&M block and a Node B Logical O&M block. The Node Bs contain Implementation Specific O&M and Logical O&M blocks. The Management Platform(s) contain Node B Management Model, RNC Management Model, and Node B Management Model blocks. Arrows indicate the flow of Implementation Specific O&M Transport from the Management Platform(s) through the RNC to the Node Bs. The RNC O&M block is connected to the RNC Management Model. The Node B Logical O&M block is connected to the Node B Management Models. The Implementation Specific O&M Transport flows from the Management Platform(s) through the RNC O&M block to the Node Bs. The Logical O&M flows from the Node Bs through the RNC to the Management Platform(s). The Physical bearer is shown at the bottom of the RNC and Node Bs.](47e8c2042061e08a14e012472e9fdbaa_img.jpg)
+
+The diagram illustrates the architecture for Implementation Specific O&M transport. At the top, a 'Management Platform(s)' box contains three models: 'Node B Management Model' (blue), 'RNC Management Model' (blue), and 'Node B Management Model' (yellow). Below this, a central 'RNC' box (blue) contains an 'RNC O&M' block and a 'Node B Logical O&M' block. The 'RNC O&M' block is connected to the 'RNC Management Model'. The 'Node B Logical O&M' block is connected to both 'Node B Management Model' blocks. On the left, a 'Node B' box (blue) contains 'Implementation Specific O&M' and 'Logical O&M' blocks. On the right, another 'Node B' box (yellow) contains the same two blocks. Arrows show 'Implementation Specific O&M Transport' (blue lines) flowing from the 'Management Platform(s)' through the 'RNC O&M' block to the 'Node Bs'. Green lines represent 'Logical O&M' traffic passing through the 'Node B Logical O&M' block in the RNC. Dashed ovals labeled 'Physical bearer' are shown at the bottom of each Node B and the RNC, indicating the transport medium. The label 'Iub' is placed near the connections between the Node Bs and the RNC.
+
+Diagram illustrating Implementation Specific O&M Transport via RNC. The diagram shows a central RNC connected to two Node Bs (one blue, one yellow) and a Management Platform(s). The RNC contains an RNC O&M block and a Node B Logical O&M block. The Node Bs contain Implementation Specific O&M and Logical O&M blocks. The Management Platform(s) contain Node B Management Model, RNC Management Model, and Node B Management Model blocks. Arrows indicate the flow of Implementation Specific O&M Transport from the Management Platform(s) through the RNC to the Node Bs. The RNC O&M block is connected to the RNC Management Model. The Node B Logical O&M block is connected to the Node B Management Models. The Implementation Specific O&M Transport flows from the Management Platform(s) through the RNC O&M block to the Node Bs. The Logical O&M flows from the Node Bs through the RNC to the Management Platform(s). The Physical bearer is shown at the bottom of the RNC and Node Bs.
+
+Figure 1: Implementation Specific O&M Transport via RNC
+
+## 4.3 Transport Bearer
+
+An appropriate transport bearer for Implementation Specific O&M should consider the requirements listed in subclause 4.1. IP (IETF RFC 791 [6]) should be the transport mechanism in order to allow a data link independent support of a variety of O&M applications and protocols for the Implementation Specific O&M of the Node B.
+
+IP datagrams containing O&M signalling have to be carried over the same bearer as Iub. There are two options for the implementation specific O&M signalling bearer in Iub:
+
+- 1) ATM Transport option
+- 2) IP Transport option
+
+### 4.3.1 ATM Transport Option
+
+The following figure shows the protocol stack for Implementation Specific O&M transport between Node B and RNC in case of ATM transport option in Iub:
+
+![Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option). The diagram shows two protocol stacks. The left stack is for the RNC and consists of three layers: IP at the top, Data Link Layer in the middle (containing AAL5 and ATM sub-layers), and PHY at the bottom. The right stack is for the Node B and consists of four layers: Implementation Specific O&M at the top, followed by IP, AAL5, ATM, and PHY at the bottom. A horizontal line connects the PHY layers of both stacks, representing the Iub interface.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg)
+
+Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option). The diagram shows two protocol stacks. The left stack is for the RNC and consists of three layers: IP at the top, Data Link Layer in the middle (containing AAL5 and ATM sub-layers), and PHY at the bottom. The right stack is for the Node B and consists of four layers: Implementation Specific O&M at the top, followed by IP, AAL5, ATM, and PHY at the bottom. A horizontal line connects the PHY layers of both stacks, representing the Iub interface.
+
+**Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option)**
+
+AAL5 shall be used according to ITU-T Recommendation I.363.5 [3].
+
+AAL5 virtual circuits are used to transport the IP packets containing Implementation Specific O&M signalling data between Node B and RNC. Multiple VCs can 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 can be made using O&M or using ATM Inverse ARP according to Classical IP over ATM.
+
+Classical IP over ATM protocols are used to carry the IP packets over the ATM transport network. Classical IP over ATM is specified in IETF RFC 2225 [4]. Multiprotocol Encapsulation over AAL5 is specified in IETF RFC 2684 [5].
+
+### 4.3.2 IP Transport Option
+
+The following figure shows the protocol stack for Implementation Specific O&M transport between Node B and RNC in case of IP transport option in Iub:
+
+![Protocol stack diagram for Implementation Specific O&M Transport (IP TNL) between RNC and Node B.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The diagram illustrates the protocol stack for Implementation Specific O&M Transport (IP TNL) between an RNC and Node B. The RNC stack consists of three layers: IP at the top, Datalink layer in the middle (with an internal IP layer), and PHY at the bottom. The Node B stack consists of four layers: Implementation Specific O&M at the top, IP below it, IP (if tunnelled) below that, Datalink layer below that, and PHY at the bottom. A horizontal line connects the PHY layers of both stacks, indicating a direct physical connection.
+
+|                |                |                             |
+|----------------|----------------|-----------------------------|
+| IP             |                | Implementation Specific O&M |
+| Datalink layer | IP             | IP                          |
+|                | Datalink layer | IP (if tunnelled)           |
+| PHY            | PHY            | Datalink layer              |
+|                |                | PHY                         |
+
+RNC                      Node B
+
+Protocol stack diagram for Implementation Specific O&M Transport (IP TNL) between RNC and Node B.
+
+**Figure 3: Protocol Stack for Implementation Specific O&M Transport (IP TNL)**
+
+Implementation specific O&M signalling is conveyed by IP between the Node B and the RNC. IP-in-IP tunneling may be applied when the Iub Transport Network Layer is used.
+
+IP based Transport Network Layer of Iub is further defined in TS 25.426 [8].
+

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

@@ -0,0 +1,236 @@
+
+
+# 3GPP TS 25.444 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuh data 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  
+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 ..... 5
+- 4 Data Link Layer ..... 6
+- 5 Circuit switched domain ..... 6
+  - 5.1 Transport Network User Plane without bandwidth efficiency mechanisms..... 6
+  - 5.3 Transport Network User Plane with bandwidth efficiency mechanisms ..... 6
+    - 5.3.1 General ..... 6
+    - 5.3.2 Transport format..... 6
+      - 5.3.2.1 UDP ..... 6
+      - 5.3.2.2 RTP..... 6
+        - 5.3.2.2.1 Transport Format for multiplexing RTP packets ..... 6
+- 6 Packet switched domain..... 8
+  - 6.1 Transport network user plane..... 8
+- Annex A (informative): Change history..... 9**
+
+# --- 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 between the HNB and HNB-GW/CN.
+
+# --- 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] Void
+- [3] Void
+- [4] 3GPP TS 25.414: "UTRAN Iu interface data transport and transport signalling".
+- [5] Void
+- [6] Void
+- [7] Void
+- [8] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [9] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real-Time Applications".
+- [10] Void
+- [11] Void
+- [12] 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 [12] 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 [12].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [12] 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 [12].
+
+|        |                              |
+|--------|------------------------------|
+| CN     | Core Network                 |
+| CS     | Circuit Switched             |
+| HNB    | Home Node B                  |
+| HNB-GW | Home Node B Gateway          |
+| IP     | Internet Protocol            |
+| PS     | Packet Switched              |
+| RFC    | Request For Comment          |
+| RTP    | Real-Time Transport Protocol |
+| UDP    | User Datagram Protocol       |
+
+# --- 4 Data Link Layer
+
+Any data link protocol that fulfils the requirements toward the upper layer may be used.
+
+# --- 5 Circuit switched domain
+
+## 5.1 Transport Network User Plane without bandwidth efficiency mechanisms
+
+Defined in Reference TS 25.414 [4], subclause 5.1.3.
+
+NOTE: The Transport Network Layer as described in ref TS 25.414 [4] subclause 5.1.3, may be directly between HNB and the CN.
+
+## 5.3 Transport Network User Plane with bandwidth efficiency mechanisms
+
+### 5.3.1 General
+
+Bandwidth efficient transport of Uplink CS data payload PDUs may be supported over bearer transport mechanisms for the Iuh interface, using a bearer transport multiplexing scheme that allows transporting several RTP PDUs of different user plane connections within one packet.
+
+### 5.3.2 Transport format
+
+UDP/IP shall be applied on Iuh between HNB and HNB GW as described in TS 25.414 [4] for Iu between RNC and CN, subclause 5.1.3, except as stated below.
+
+#### 5.3.2.1 UDP
+
+The path protocol used shall be UDP (IETF RFC 768 [8]). If multiplexing is applied the source UDP port number shall indicate the local termination used to combine the multiplexed packet and the destination UDP port number shall indicate the remote port number where PDUs are demultiplexed.
+
+#### 5.3.2.2 RTP
+
+RTP (IETF RFC 1889[9]) shall be applied as described in TS 25.414 [4], subclause 5.1.3.3 and requirements below.
+
+##### 5.3.2.2.1 Transport Format for multiplexing RTP packets
+
+Use of multiplexing shall be negotiated between the HNB and HNB-GW.
+
+Before each multiplexed RTP/codec payload PDU inserted into the UDP/IP packet a Multiplex Header, which identifies the multiplexed packet, shall be inserted.
+
+| Bits                                               |                                                        |   |   |   |   |   |   | Number of Octets |                  |  |  |  |  |  |  |  |
+|----------------------------------------------------|--------------------------------------------------------|---|---|---|---|---|---|------------------|------------------|--|--|--|--|--|--|--|
+| 7                                                  | 6                                                      | 5 | 4 | 3 | 2 | 1 | 0 |                  |                  |  |  |  |  |  |  |  |
+| Source IP, Dest IP, ...                            |                                                        |   |   |   |   |   |   | 20/40            | IP               |  |  |  |  |  |  |  |
+| Source Port, Dest Port=<MUX UDP port>, Length, ... |                                                        |   |   |   |   |   |   | 8                | UDP              |  |  |  |  |  |  |  |
+| T=0                                                | Mux ID = (Destination UDP Port of multiplexed PDU) / 2 |   |   |   |   |   |   | 2                | Multiplex Header |  |  |  |  |  |  |  |
+| Length Indicator (LI) = n                          |                                                        |   |   |   |   |   |   | 1                |                  |  |  |  |  |  |  |  |
+| R                                                  | Source ID = (Source UDP Port of multiplexed PDU) / 2   |   |   |   |   |   |   | 2                |                  |  |  |  |  |  |  |  |
+| Full RTP packet                                    |                                                        |   |   |   |   |   |   | n                | RTP header       |  |  |  |  |  |  |  |
+|                                                    |                                                        |   |   |   |   |   |   |                  | RTP Payload      |  |  |  |  |  |  |  |
+| Multiplex Header                                   |                                                        |   |   |   |   |   |   | 5                | Multiplex Header |  |  |  |  |  |  |  |
+| Full RTP packet                                    |                                                        |   |   |   |   |   |   | m                | RTP header       |  |  |  |  |  |  |  |
+|                                                    |                                                        |   |   |   |   |   |   |                  | RTP Payload      |  |  |  |  |  |  |  |
+| ...                                                |                                                        |   |   |   |   |   |   |                  |                  |  |  |  |  |  |  |  |
+
+**Figure 1: UDP/IP Packet with multiplexed RTP payload PDUs**
+
+The Multiplex Header includes :
+
+- T bit.
+
+The field has two possible values. Value 0 shall be used for an uncompressed RTP header, as described in the present sub-clause. Value 1 is FFS.
+
+- Mux ID, 15 bits.
+
+For identification of different user plane connections. The value shall be the UDP destination port of the corresponding non-multiplexed RTP PDU packet divided by two (only even numbered ports are used for RTP sessions).
+
+- Length Indicator (LI), 8 bits, unsigned integer.
+
+Gives the length of the multiplexed RTP PDU packet (RTP header + RTP) in bytes (the last byte of the RTP PDU is padded to the next byte boundary if necessary). Maximum length is 255 bytes. This LI allows to calculate where the next Multiplex Header for the next multiplexed RTP PDU packet starts.
+
+- R bit.
+
+Reserved for future use. Shall be set to 0 by the sending entity and be ignored by the receiving entity.
+
+- Source ID, 15 bits.
+
+For identification of the different connections. The value shall be the source UDP port of the corresponding non-multiplexed RTP/codec PDU packet divided by two (only even numbered ports are used for RTP sessions).
+
+The multiplexed RTP PDU shall be inserted in the IP/UDP packet directly after the corresponding Multiplex Header. The multiplexed RTP packet PDU shall follow the rules defined in IETF RFC 1889 [9] and consists of the full RTP header and the RTP payload. If the multiplexed RTP packet PDU does not end at a byte boundary, then the remaining bits of its last byte shall be padded with zeros.
+
+The multiplexing method does not limit the number of packets being multiplexed and it is thus the data link layer protocol that defines the maximum frame size. In order to avoid additional delay in the network the packets should not be delayed more than 1 ms to 2 ms, which also effectively limits the number of multiplexed packets and makes the multiplexing-jitter low.
+
+![Figure 2: Example of multiplexed packet with two RTP frames. The diagram illustrates the structure of a multiplexed packet containing two RTP frames. At the top, two separate packets are shown. The first packet has a header section (IP (20/40 bytes), UDP (8), RTP (12)) and a payload (IuUP frame (9 ...)). A callout box points to the UDP port, labeled 'Dest. & Source UDP Port: xxxx'. The second packet has a similar header section and payload. A callout box points to its UDP port, labeled 'Dest. & Source UDP Port: yyyy'. Below these, the packets are shown being multiplexed. The first packet's header is replaced by a 'Common header' (IP (20/40 bytes), UDP (8)). The UDP port is now a 'Negotiated UDP MUX port.'. The RTP (12) and IuUP frame (9 ...) are preserved. This is followed by a 'MUX (5)' header. The second packet's RTP (12) and IuUP frame (9 ...) are also preserved, followed by another 'MUX (5)' header. The resulting multiplexed packets are labeled '1. MUX packet' and '2. MUX packet'. A double-headed arrow indicates the maximum length of the multiplexed packet is 'max 255 bytes'. Callout boxes point to the UDP ports for the multiplexed packets, labeled 'Dest. & Source UDP Port: xxxx' and 'Dest. & Source UDP Port: yyyy'.](7affafe7362a2d2d072e9d4bf515f0bb_img.jpg)
+
+Figure 2: Example of multiplexed packet with two RTP frames. The diagram illustrates the structure of a multiplexed packet containing two RTP frames. At the top, two separate packets are shown. The first packet has a header section (IP (20/40 bytes), UDP (8), RTP (12)) and a payload (IuUP frame (9 ...)). A callout box points to the UDP port, labeled 'Dest. & Source UDP Port: xxxx'. The second packet has a similar header section and payload. A callout box points to its UDP port, labeled 'Dest. & Source UDP Port: yyyy'. Below these, the packets are shown being multiplexed. The first packet's header is replaced by a 'Common header' (IP (20/40 bytes), UDP (8)). The UDP port is now a 'Negotiated UDP MUX port.'. The RTP (12) and IuUP frame (9 ...) are preserved. This is followed by a 'MUX (5)' header. The second packet's RTP (12) and IuUP frame (9 ...) are also preserved, followed by another 'MUX (5)' header. The resulting multiplexed packets are labeled '1. MUX packet' and '2. MUX packet'. A double-headed arrow indicates the maximum length of the multiplexed packet is 'max 255 bytes'. Callout boxes point to the UDP ports for the multiplexed packets, labeled 'Dest. & Source UDP Port: xxxx' and 'Dest. & Source UDP Port: yyyy'.
+
+Figure 2: Example of multiplexed packet with two RTP frames
+
+# 6 Packet switched domain
+
+## 6.1 Transport network user plane
+
+Defined in Ref TS 25.414 [4] subclause 6.1.3.
+
+NOTE: The Transport Network Layer as described in ref TS 25.414 [4] subclause 6.1.3, may be directly between HNB and the CN.

marked/Rel-18/29_series/29579/raw.md

@@ -0,0 +1,878 @@
+
+
+# 3GPP TS 29.579 V18.3.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Interworking MSC For Short Message Services; Stage 3 (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 'G' 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
+
+---
+
+<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.
+
+© 2023, 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.....                                                                             | 7  |
+| 2 References.....                                                                        | 7  |
+| 3 Definitions and abbreviations .....                                                    | 8  |
+| 3.1 Definitions.....                                                                     | 8  |
+| 3.2 Abbreviations .....                                                                  | 8  |
+| 4 Overview.....                                                                          | 8  |
+| 4.1 Introduction .....                                                                   | 8  |
+| 5 Services offered by the SMS-IWMSC.....                                                 | 8  |
+| 5.1 Introduction .....                                                                   | 8  |
+| 5.2 Niwmsc_SMService Service.....                                                        | 9  |
+| 5.2.1 Service Description .....                                                          | 9  |
+| 5.2.2 Service Operations.....                                                            | 9  |
+| 5.2.2.1 Introduction.....                                                                | 9  |
+| 5.2.2.2 MoForwardSm .....                                                                | 9  |
+| 5.2.2.2.1 General .....                                                                  | 9  |
+| 5.2.2.2.2 SBI-based MO SM transfer.....                                                  | 9  |
+| 6 API Definitions .....                                                                  | 10 |
+| 6.1 Niwmsc_SMService Service API .....                                                   | 10 |
+| 6.1.1 Introduction .....                                                                 | 10 |
+| 6.1.2 Usage of HTTP.....                                                                 | 10 |
+| 6.1.2.1 General.....                                                                     | 10 |
+| 6.1.2.2 HTTP standard headers.....                                                       | 10 |
+| 6.1.2.2.1 General .....                                                                  | 10 |
+| 6.1.2.2.2 Content type .....                                                             | 10 |
+| 6.1.2.3 HTTP custom headers.....                                                         | 11 |
+| 6.1.2.4 HTTP multipart messages.....                                                     | 11 |
+| 6.1.3 Resources.....                                                                     | 11 |
+| 6.1.3.1 Overview.....                                                                    | 11 |
+| 6.1.3.2 Resource: MoSmInfo.....                                                          | 12 |
+| 6.1.3.2.1 Description .....                                                              | 12 |
+| 6.1.3.2.2 Resource Definition.....                                                       | 12 |
+| 6.1.3.2.3 Resource Standard Methods.....                                                 | 12 |
+| 6.1.3.2.4 Resource Custom Operations.....                                                | 13 |
+| 6.1.4 Custom Operations without associated resources .....                               | 15 |
+| 6.1.5 Notifications .....                                                                | 15 |
+| 6.1.6 Data Model .....                                                                   | 15 |
+| 6.1.6.1 General.....                                                                     | 15 |
+| 6.1.6.2 Structured data types.....                                                       | 15 |
+| 6.1.6.3 Simple data types and enumerations.....                                          | 16 |
+| 6.1.6.3.1 Introduction .....                                                             | 16 |
+| 6.1.6.3.2 Simple data types .....                                                        | 16 |
+| 6.1.6.4 Data types describing alternative data types or combinations of data types ..... | 16 |
+| 6.1.6.5 Binary data.....                                                                 | 16 |
+| 6.1.6.5.1 Binary Data Types.....                                                         | 16 |
+| 6.1.6.5.2 SMS Payload Information.....                                                   | 16 |
+| 6.1.7 Error Handling.....                                                                | 16 |
+| 6.1.7.1 General.....                                                                     | 16 |
+| 6.1.7.2 Protocol Errors .....                                                            | 16 |
+| 6.1.7.3 Application Errors.....                                                          | 16 |
+| 6.1.8 Feature negotiation .....                                                          | 17 |
+| 6.1.9 Security.....                                                                      | 17 |
+| 6.1.10 HTTP redirection.....                                                             | 17 |
+
+**Annex A (normative): OpenAPI specification ..... 18**  
+A.1 General..... 18  
+A.2 Niwmsc\_SMService API..... 18  
+**Annex B (informative): Withdrawn API versions ..... 20**  
+B.1 General..... 20  
+B.2 Niwmsc\_SMService API..... 20  
+**Annex C (informative): Change history..... 21**
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the Niwmsc Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMS-IWMSC.
+
+The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
+
+Stage 2 requirements for the Niwmsc services are specified in 3GPP TS 23.540 [14].
+
+# 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 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", <https://spec.openapis.org/oas/v3.0.0>.
+- [7] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
+- [11] IETF RFC 9113: "HTTP/2".
+- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [13] IETF RFC 9457: "Problem Details for HTTP APIs".
+- [14] 3GPP TS 23.540: "Technical realization of Service Based Short Message Service; Stage 2".
+- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
+- [16] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
+- [17] 3GPP TS 29.577: "5G System; IP Short Message Gateway and SMS Router For Short Message Service; Stage 3".
+- [18] 3GPP TS 24.011: " Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
+
+**Niwmsc:** Service-based interface exhibited by the SMS-IWMSC
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
+
+|       |                                 |
+|-------|---------------------------------|
+| SM MO | Short Message Mobile Originated |
+|-------|---------------------------------|
+
+# 4 Overview
+
+## 4.1 Introduction
+
+The SMS-IWMSC offers services to the SMSF via the Niwmsc service based interface (see 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], and 3GPP TS 23.540 [14]).
+
+Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the SMS-IWMSC.
+
+![Reference model diagram showing SMSF connected to SMS-IWMSC via SM10 interface and Niwmsc service-based interface.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg)
+
+The diagram illustrates the reference model for the SMS-IWMSC. On the left, a white rectangular box is labeled 'SMSF'. A horizontal line, representing the SM10 interface, connects this box to a green rectangular box on the right labeled 'SMS-IWMSC'. The connection point on the SMS-IWMSC side is marked with a small circle and labeled 'Niwmsc', indicating the service-based interface.
+
+Reference model diagram showing SMSF connected to SMS-IWMSC via SM10 interface and Niwmsc service-based interface.
+
+**Figure 4.1-1: Reference model – SMS-IWMSC**
+
+The functionalities supported by the SMS-IWMSC are listed in clause 6.3 of 3GPP TS 23.540 [14].
+
+# 5 Services offered by the SMS-IWMSC
+
+## 5.1 Introduction
+
+The SMS-IWMSC offers the following services via the Niwmsc interface:
+
+- Niwmsc\_SMService Service
+
+Table 5.1-1 summarizes the corresponding APIs defined for this specification.
+
+**Table 5.1-1: API Descriptions**
+
+| Service Name     | Clause | Description                     | OpenAPI Specification File    | apiName           | Annex |
+|------------------|--------|---------------------------------|-------------------------------|-------------------|-------|
+| Niwmsc_SMService | 6.1    | SMS-IWMSC short message service | TS29579_Niwmsc_SMService.yaml | niwmsc-smbservice | A.2   |
+
+## 5.2 Niwmsc\_SMService Service
+
+### 5.2.1 Service Description
+
+See 3GPP TS 23.540 [14] clause 6.3.1
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+For the Niwmsc\_SMService service the following service operations are defined:
+
+- MoForwardSm
+
+The Niwmsc\_SMService Service is used by Consumer NFs (SMSF) to transfer MO short message by means of the MoForwardSm service operation.
+
+#### 5.2.2.2 MoForwardSm
+
+##### 5.2.2.2.1 General
+
+This clause provides a general description of the MoForwardSm service operation.
+
+##### 5.2.2.2.2 SBI-based MO SM transfer
+
+The MoForwardSm service operation shall be used to transmit uplink SMS message via SMS-IWMSC.
+
+It is used in the following procedures:
+
+- Successful Mobile Originated short message transfer via SMS-IWMSC (see clause 5.2.2 of 3GPP TS 23.540 [14]).
+- Unsuccessful Mobile Originated short message transfer via SMS-IWMSC (see clause 5.2.3 of 3GPP TS 23.540 [14]).
+
+The NF Service Consumer (e.g. SMSF) shall transmit uplink SMS message to the SMS-IWMSC by using the HTTP POST method as shown in Figure 5.2.2.2.1-1.
+
+![Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and SMS-IWMSC.](97a08abb8a43f3f8c6ce347199cd909a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant SMS-IWMSC
+    Note right of NF Service Consumer: (SMS Data)
+    NF Service Consumer->>SMS-IWMSC: 1. POST ../mo-sm-info/{supi}/sendsms
+    SMS-IWMSC-->>NF Service Consumer: 2a. 200 OK (Delivery Report)
+    SMS-IWMSC-->>NF Service Consumer: 2b. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+The diagram illustrates the interaction between an NF Service Consumer and an SMS-IWMSC. The consumer sends a POST request (step 1) to the SMS-IWMSC, including SMS data. The SMS-IWMSC responds with either a 200 OK (Delivery Report) (step 2a) or a 4xx/5xx (ProblemDetails) or 3xx (step 2b).
+
+Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and SMS-IWMSC.
+
+**Figure 5.2.2.2.2.1-1: SBI-based MO SM transfer**
+
+1. The NF Service Consumer shall send a POST request to the resource representing the UE's Mobile Originated Short Message Information resource (i.e. .../mo-sm-info/{supi}/sendsmss) of the SMS-IWMSC. The content of the POST request shall contain the SMS message to be sent.
+- 2a. On success, "200 OK" shall be returned with "SmsDeliveryData" object contains the MO SMS Delivery Report in the response body.
+- 2b. On failure, or redirection, one of the HTTP status code listed in Table 6.1.3.2.4.2.2-2 shall be returned.
+
+# --- 6 API Definitions
+
+## 6.1 Niwmsc\_SMService Service API
+
+### 6.1.1 Introduction
+
+The Niwmsc\_SMService shall use the Niwmsc\_SMService API.
+
+The API URI of the Niwmsc\_SMService API shall be:
+
+**{apiRoot}</apiName></apiVersion>**
+
+The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
+
+**{apiRoot}</apiName></apiVersion></apiSpecificResourceUriPart>**
+
+with the following components:
+
+- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
+- The <apiName> shall be "niwmsc-smbservice".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.3.
+
+### 6.1.2 Usage of HTTP
+
+#### 6.1.2.1 General
+
+HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
+
+HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
+
+The OpenAPI [6] specification of HTTP messages and content bodies for the Niwmsc\_SMService API is contained in Annex A.
+
+#### 6.1.2.2 HTTP standard headers
+
+##### 6.1.2.2.1 General
+
+See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
+
+##### 6.1.2.2.2 Content type
+
+JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json".
+
+"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13].
+
+Multipart messages shall also be supported (see clause 6.1.2.4) using the content type "multipart/related", comprising:
+
+- one JSON body part with the "application/json" content type; and
+- one binary body part with 3gpp vendor specific content subtypes.
+
+The 3gpp vendor specific content subtypes defined in Table 6.1.2.2.2-1 shall be supported.
+
+**Table 6.1.2.2.2-1: 3GPP vendor specific content subtypes**
+
+| content subtype | Description                                                                                                                                                       |
+|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| vnd.3gpp.sms    | Binary encoded payload, encoding SMS payload, as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [17].                                                        |
+| NOTE:           | Using 3GPP vendor content subtypes allows to describe the nature of the opaque payload (e.g. SMS payload) without having to rely on metadata in the JSON content. |
+
+See clause 6.1.2.4 for the binary payloads supported in the binary body part of multipart messages.
+
+#### 6.1.2.3 HTTP custom headers
+
+The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported.
+
+#### 6.1.2.4 HTTP multipart messages
+
+HTTP multipart messages shall be supported, to transfer opaque SMS payload (e.g. SMS message, CP Ack, etc.), in the following service operations (and HTTP messages):
+
+- MoForwardSm service operation;
+
+HTTP multipart messages shall include one JSON body part and one binary body part comprising content of SMS payload content (see clause 6.1.6.5).
+
+The JSON body part shall be the "root" body part of the multipart message. It shall be encoded as the first body part of the multipart message. The "Start" parameter does not need to be included.
+
+The multipart message shall include a "type" parameter (see IETF RFC 2387 [18]) specifying the media type of the root body part, i.e. "application/json".
+
+NOTE: The "root" body part (or "root" object) is the first body part the application processes when receiving a multipart/related message, see IETF RFC 2387 [18]. The default root is the first body within the multipart/related message. The "Start" parameter indicates the root body part, e.g. when this is not the first body part in the message.
+
+A binary body part shall include a Content-ID header (see IETF RFC 2045 [19]), and the JSON body part shall make a reference to the binary body part using the Content-ID header field.
+
+Examples of multipart/related messages can be found in Annex B.
+
+### 6.1.3 Resources
+
+#### 6.1.3.1 Overview
+
+This clause describes the structure for the Resource URIs and the resources and methods used for the service.
+
+Figure 6.1.3.1-1 depicts the resource URIs structure for the Niwmse\_SMSService API.
+
+![Diagram showing the hierarchical structure of the Niwmsc_SMSService API URI. The root is {apiRoot}/niwmsc_smbservice/<apiVersion>. It branches to /mo-sm-info, which branches to /{supi}, which branches to /send sms (dashed box).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+{apiRoot}/niwmsc\_smbservice/<apiVersion>
+
+```
+
+graph TD
+    Root["{apiRoot}/niwmsc_smbservice/<apiVersion>"] --> MoSmInfo["/mo-sm-info"]
+    MoSmInfo --> Supi["/{supi}"]
+    Supi --> SendSms["/send sms"]
+    style SendSms stroke-dasharray: 5 5
+  
+```
+
+Diagram showing the hierarchical structure of the Niwmsc\_SMSService API URI. The root is {apiRoot}/niwmsc\_smbservice/. It branches to /mo-sm-info, which branches to /{supi}, which branches to /send sms (dashed box).
+
+**Figure 6.1.3.1-1: Resource URI structure of the Niwmsc\_SMSService API**
+
+Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 6.1.3.1-1: Resources and methods overview**
+
+| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation) |
+|-----------------------|--------------------------------------------|---------------------------------|---------------------------------|
+| SMSService            | /mo-sm-info/{supi}/send sms                | send sms (POST)                 | MO short message transfer       |
+|                       |                                            |                                 |                                 |
+|                       |                                            |                                 |                                 |
+|                       |                                            |                                 |                                 |
+|                       |                                            |                                 |                                 |
+
+#### 6.1.3.2 Resource: MoSmInfo
+
+##### 6.1.3.2.1 Description
+
+This resource represents the collection of Mobile Originated Short Message Information in SMS-IWMSC.
+
+This resource is modelled with the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [5]).
+
+##### 6.1.3.2.2 Resource Definition
+
+Resource URI: {apiRoot}/<apiName>/<apiVersion>/mo-sm-info{supi}
+
+This resource shall support the resource URI variables defined in table 6.1.3.2.2-1.
+
+**Table 6.1.3.2.2-1: Resource URI variables for this resource**
+
+| Name    | Data type | Definition                                                                                                                                         |
+|---------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| apiRoot | string    | See clause 6.1.1                                                                                                                                   |
+| supi    | Supi      | Represents the Subscription Permanent Identifier (see 3GPP TS 23.501 [2] clause 5.9.2)<br>pattern: See pattern of type Supi in 3GPP TS 29.571 [15] |
+
+##### 6.1.3.2.3 Resource Standard Methods
+
+No HTTP method has been defined for the Mobile Originated Short Message Information collection resource.
+
+##### 6.1.3.2.4 Resource Custom Operations
+
+###### 6.1.3.2.4.1 Overview
+
+**Table 6.1.3.2.4.1-1: Custom operations**
+
+| Operation name | Custom operation URI        | Mapped HTTP method | Description                                         |
+|----------------|-----------------------------|--------------------|-----------------------------------------------------|
+| sendsms        | /mo-sm-infos/{supi}/sendsms | POST               | Send MO SMS message or the related Delivery Report. |
+
+###### 6.1.3.2.4.2 Operation: sendsms
+
+###### 6.1.3.2.4.2.1 Description
+
+This custom operation is used for NF Service Consumers to send SMS message in uplink direction.
+
+###### 6.1.3.2.4.2.2 Operation Definition
+
+This custom operation is used to send a SMS payload to an UE's Mobile Originated Short Message Information resource in the SMS-IWMSC.
+
+This operation shall support the request data structures specified in table 6.1.3.2.4.2.2-1 and the response data structure and response codes specified in table 6.1.3.2.4.2.2-2.
+
+**Table 6.1.3.2.4.2.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type | P | Cardinality | Description                                      |
+|-----------|---|-------------|--------------------------------------------------|
+| SmsData   | M | 1           | Representation of the MO SMS message to be sent. |
+
+**Table 6.1.3.2.4.2.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SmsDeliveryData  | M | 1           | 200 OK                 | This case represents the successful of sending SMS message in uplink direction, with necessary response data on the received delivery report.                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. (NOTE 2)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. (NOTE 2)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ProblemDetails   | O | 0..1        | 400 Bad Request        | This case represents an unsuccessful delivery of SMS message.<br>The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- SMS_PAYLOAD_MISSING, if the expected SMS payload content is missing;</li> <li>- SMS_PAYLOAD_ERROR, if error exists in the SMS payload content.</li> </ul>                                                                                                                                                                                                    |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | This case represents an unsuccessful delivery of SMS message.<br>The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- UNKNOWN_SERVICE_CENTRE_ADDRESS, if the SMS-SC was unknown;</li> <li>- SERVICE_CENTRE_CONGESTION, if the SMS-SC was in congestion;</li> <li>- USER_NOT_SERVICE_CENTER, if the user didn't belongs to the SMS-SC;</li> <li>- FACILITY_NOT_SUPPORTED, if the facility not supported;</li> <li>- INVALID_SME_ADDRESS, if the SME address is invalid..</li> </ul> |
+| ProblemDetails   | O | 0..1        | 504 Gateway Timeout    | This case represents an unsuccessful delivery of SMS message.<br>The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- UNREACHABLE_SMS_SC, if the response is timeout.</li> </ul>                                                                                                                                                                                                                                                                                                   |
+
+NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.
+
+**Table 6.1.3.2.4.2.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                                                                                   |
+|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same SMS-IWMSC or SMS-IWMSC (service) set.<br>For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                                                                                     |
+
+**Table 6.1.3.2.4.2.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                                                                                   |
+|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same SMS-IWMSC or SMS-IWMSC (service) set.<br>For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                                                                                     |
+
+### 6.1.4 Custom Operations without associated resources
+
+In this release of this specification, no custom operations without associated resources are defined.
+
+### 6.1.5 Notifications
+
+In this release of this specification, no notification procedures are defined.
+
+### 6.1.6 Data Model
+
+#### 6.1.6.1 General
+
+This clause specifies the application data model supported by the API.
+
+Table 6.1.6.1-1 specifies the data types defined for the Niwmsc\_SMSService service based interface protocol.
+
+**Table 6.1.6.1-1: Niwmsc\_SMSService specific Data Types**
+
+| Data type | Clause defined | Description | Applicability |
+|-----------|----------------|-------------|---------------|
+| N/A       |                |             |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the Niwmsc\_SMSService service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Niwmsc\_SMSService service based interface.
+
+**Table 6.1.6.1-2: Niwmsc\_SMSService re-used Data Types**
+
+| Data type         | Reference           | Comments                                                                                                           | Applicability |
+|-------------------|---------------------|--------------------------------------------------------------------------------------------------------------------|---------------|
+| ProblemDetails    | 3GPP TS 29.571 [15] | Common Data Type used in response bodies                                                                           |               |
+| RedirectResponse  | 3GPP TS 29.571 [15] | Redirect Response                                                                                                  |               |
+| Supi              | 3GPP TS 29.571 [15] | Subscription Permanent Identifier                                                                                  |               |
+| RefToBinaryData   | 3GPP TS 29.571 [15] | Information for indicating the binary content of SMS payload.                                                      |               |
+| Ipv4Addr          | 3GPP TS 29.571 [15] | IPv4 address                                                                                                       |               |
+| Ipv6Addr          | 3GPP TS 29.571 [15] | IPv6 address                                                                                                       |               |
+| SupportedFeatures | 3GPP TS 29.571 [15] | Supported Features                                                                                                 |               |
+| SmsData           | 3GPP TS 29.577 [17] | Information within request message invoking MoForwardSm service operation, for delivering MO SMS.                  |               |
+| SmsDeliveryData   | 3GPP TS 29.571 [17] | Information within response message invoking MoForwardSm service operation, for delivering MO SMS Delivery Report. |               |
+
+#### 6.1.6.2 Structured data types
+
+In this release of this specification, no structure to be used in resource representations is defined.
+
+#### 6.1.6.3 Simple data types and enumerations
+
+##### 6.1.6.3.1 Introduction
+
+This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
+
+##### 6.1.6.3.2 Simple data types
+
+The simple data types defined in table 6.1.6.3.2-1 shall be supported.
+
+**Table 6.1.6.3.2-1: Simple data types**
+
+| Type Name | Type Definition | Description | Applicability |
+|-----------|-----------------|-------------|---------------|
+| N/A       |                 |             |               |
+
+#### 6.1.6.4 Data types describing alternative data types or combinations of data types
+
+None.
+
+#### 6.1.6.5 Binary data
+
+##### 6.1.6.5.1 Binary Data Types
+
+**Table 6.1.6.5.1-1: Binary Data Types**
+
+| Name                    | Clause defined | Content type |
+|-------------------------|----------------|--------------|
+| SMS Payload Information | 6.1.6.4.2      | vnd.3gpp.sms |
+
+##### 6.1.6.5.2 SMS Payload Information
+
+SMS Payload Information shall encode a SMS payload as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [18], using the vnd.3gpp.sms content-type.
+
+SMS Payload Information may encode e.g. the following content:
+
+- CP-DATA, CP-ACK, CP-ERROR as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [18].
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Niwmsc\_SMService API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4].
+
+In addition, the requirements in the following clauses are applicable for the Niwmsc\_SMService API.
+
+#### 6.1.7.2 Protocol Errors
+
+No specific procedures for the Niwmsc\_SMService service are specified.
+
+#### 6.1.7.3 Application Errors
+
+The application errors defined for the Niwmsc\_SMService service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| Application Error         | HTTP status code    | Description                                                                             |
+|---------------------------|---------------------|-----------------------------------------------------------------------------------------|
+| SMS_PAYLOAD_MISSING       | 400 Bad Request     | The expected SMS payload content is missing.                                            |
+| SMS_PAYLOAD_ERROR         | 400 Bad Request     | Errors exist in the format of SMS payload.                                              |
+| SERVICE_CENTRE_CONGESTION | 403 Forbidden       | The delivery of the MO short message failed because SMS-SC was in congestion.           |
+| USER_NOT_SERVICE_CENTER   | 403 Forbidden       | The delivery of the short message failed because the user didn't belongs to the SMS-SC. |
+| FACILITY_NOT_SUPPORTED    | 403 Forbidden       | The delivery of the MO short message failed because of facility not supported.          |
+| INVALID_SME_ADDRESS       | 403 Forbidden       | The delivery of the MO short message failed because the SME address is invalid.         |
+| UNREACHABLE_SMS_SC        | 504 Gateway Timeout | The delivery of the MO short message failed because the response is timeout.            |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Niwmsc\_SMService API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
+
+**Table 6.1.8-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+| N/A            |              |             |
+
+### 6.1.9 Security
+
+As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Niwmsc\_SMService API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server.
+
+If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Niwmsc\_SMService API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2.
+
+NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Niwmsc\_SMService service.
+
+The Niwmsc\_SMService API defines a single scope "niwmsc-smbservice" for the entire service, and it does not define any additional scopes at resource or operation level.
+
+### 6.1.10 HTTP redirection
+
+An HTTP request may be redirected to a different SMS-IWMSC service instance, within the same SMS-IWMSC or a different SMS-IWMSC of an SMS-IWMSC set, e.g. when an SMS-IWMSC service instance is part of an SMS-IWMSC (service) set or when using indirect communications (see 3GPP TS 29.500 [4]).
+
+An SCP that reselects a different SMS-IWMSC producer instance will return the NF Instance ID of the new SMS-IWMSC producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4].
+
+If an SMS-IWMSC within an SMS-IWMSC set redirects a service request to a different SMS-IWMSC of the set using a 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new SMS-IWMSC towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format.
+
+This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
+
+NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]).
+
+## A.2 Niwmsc\_SMService API
+
+```
+openapi: 3.0.0
+info:
+  title: 'Niwmsc_SMService'
+  version: '1.1.0-alpha.2'
+  description: |
+    SMS-IWMSC Short Message Service.
+    © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: 3GPP TS 29.579 V18.1.0; 5G System; SMS Services; Stage 3.
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.579/
+
+servers:
+  - url: '{apiRoot}/niwmsc-smsservice/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+
+security:
+  - oAuth2ClientCredentials:
+    - niwmsc-smsservice
+  - {}
+
+paths:
+  /mo-sm-infos/{supi}/sendsms:
+    post:
+      summary: Send SMS payload for a given UE
+      operationId: SendSMS
+      tags:
+        - Send MO SMS message and the delivery report
+      parameters:
+        - name: supi
+          in: path
+          required: true
+          description: Subscription Permanent Identifier (SUPI)
+          schema:
+            type: string
+      requestBody:
+        content:
+          multipart/related: # message with a binary body part
+            schema:
+              type: object
+              properties:
+                jsonData:
+                  $ref: '#/components/schemas/SmsData'
+                binaryPayload:
+```
+
+```
+        type: string
+        format: binary
+    encoding:
+      jsonData:
+        contentType: application/json
+      binaryPayload:
+        contentType: application/vnd.3gpp.sms
+      headers:
+        Content-Id:
+          schema:
+            type: string
+    required: true
+  responses:
+    '200':
+      description: sending delivery report
+      content:
+        multipart/related: # message with a binary body part
+          schema:
+            type: object
+            properties:
+              jsonData:
+                $ref: '#/components/schemas/SmsDeliveryData'
+              binaryPayload:
+                type: string
+                format: binary
+            encoding:
+              jsonData:
+                contentType: application/json
+              binaryPayload:
+                contentType: application/vnd.3gpp.sms
+              headers:
+                Content-Id:
+                  schema:
+                    type: string
+    '307':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+    '308':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+    '400':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+    '411':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+    '413':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+    '415':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+    '429':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+    '502':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/502'
+    '504':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+    default:
+      $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+components:
+
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            niwmsc-smbservice: Access to the niwmsc-smbservice API
+
+schemas:
+
+  SmsData:
+    description: >
+```
+
+```
+
+    Information within request message invoking MoForwardSm service operation,
+    for delivering MO SMS.
+type: object
+required:
+  - smsPayload
+properties:
+  smsPayload:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+
+SmsDeliveryData:
+  description: >
+    Information within response message invoking MoForwardSm service operation,
+    for delivering MO SMS Delivery Report.
+  type: object
+  required:
+    - smsPayload
+  properties:
+    smsPayload:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+
+# COMPLEX TYPES:
+
+# SIMPLE TYPES:
+
+# ENUMS:
+
+```
+
+# --- Annex B (informative): Withdrawn API versions
+
+## B.1 General
+
+This Annex lists withdrawn API versions of the APIs defined in the present specification. 3GPP TS 29.501 [5] clause 4.3.1.6 describes the withdrawal of API versions.
+
+## --- B.2 Niwmsc\_SMService API
+
+The API versions listed in table B.2-1 are withdrawn for the Niwmsc\_SMService API.
+
+**Table B.2-1: Withdrawn API versions of the Niwmsc\_SMService service**
+
+| API version number | Remarks |
+|--------------------|---------|
+|                    |         |
+
+# Annex C (informative): Change history
+
+| Change history |          |           |      |     |     |                                                       |             |
+|----------------|----------|-----------|------|-----|-----|-------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                       | New version |
+| 2022-04        | CT4#109e | C4-222331 |      |     |     | C4-222331 as basis                                    | 0.1.0       |
+| 2022-04        | CT4#109e | C4-222343 |      |     |     | Implementation of C4-222343 in CT4#109e               | 0.2.0       |
+| 2022-05        | CT4#110e | C4-223452 |      |     |     | Implementation of C4-223219 and C4-223224 in CT4#110e | 0.3.0       |
+| 2022-06        | CT#96    | CP-221080 |      |     |     | TS presented for information and approval             | 1.0.0       |
+| 2022-06        | CT#96    | CP-221080 |      |     |     | TS approved at CT#95                                  | 17.0.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0002 | -   | B   | Add 3xx for the service operation                     | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0003 | -   | F   | Alignment on the service name used with template      | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0004 | -   | F   | Corrections on the table name and NOTE                | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0005 | -   | F   | Update on the content type for OpenAPI                | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0006 | 1   | F   | Update on the reference model                         | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222058 | 0007 | -   | F   | 29.579 Rel-17 API version and External doc update     | 17.1.0      |
+| 2022-12        | CT#98e   | CP-223028 | 0008 | 1   | F   | Missing Mandatory Status Codes in OpenAPI             | 18.0.0      |
+| 2022-12        | CT#98e   | CP-223033 | 0009 | -   | F   | 29.579 Rel-18 API version and External doc update     | 18.0.0      |
+| 2023-03        | CT#99e   | CP-230073 | 0012 | -   | A   | Rel-18 Niwmsc SMService API HTTP code correction      | 18.0.1      |
+| 2023-03        | CT#99e   | CP-230071 | 0014 | -   | F   | 29.579 Rel-18 API version and External doc update     | 18.0.1      |
+| 2023-03        | CT#99e   | CP-230321 | 0015 | -   | F   | 29.579 Rel-18 API version and External doc update     | 18.1.0      |
+| 2023-06        | CT#99e   | CP-231026 | 0013 | 3   | F   | Location header description                           | 18.2.0      |
+| 2023-12        | CT#102   | CP-233027 | 0017 | -   | F   | HTTP RFCs obsoleted by IETF RFC 9113                  | 18.3.0      |
+| 2023-12        | CT#102   | CP-233028 | 0016 | 1   | F   | HTTP RFCs update in TS 29.579                         | 18.3.0      |
+| 2023-12        | CT#102   | CP-233030 | 0018 | -   | F   | ProblemDetails RFC 7807 obsoleted by 9457             | 18.3.0      |

marked/Rel-18/37_series/37106/raw.md

@@ -0,0 +1,167 @@
+
+
+# 3GPP TS 37.106 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) requirements for shared spectrum channel access (Release 18)** ---
+
+## **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 .....                                                           | 4        |
+| 1 Scope.....                                                             | 5        |
+| 2 References.....                                                        | 5        |
+| 3 Definitions, symbols and abbreviations .....                           | 5        |
+| 3.1 Definitions.....                                                     | 5        |
+| 3.2 Symbols.....                                                         | 5        |
+| 3.3 Abbreviations .....                                                  | 6        |
+| 4 General.....                                                           | 6        |
+| 4.1 Relationship between minimum requirements and test requirements..... | 6        |
+| 4.2 Applicability of minimum requirements .....                          | 6        |
+| 5 Channel access procedures.....                                         | 6        |
+| 5.1 Uplink channel access procedure .....                                | 6        |
+| 5.1.1 Channel access parameters .....                                    | 6        |
+| 5.1.2 Minimum requirement.....                                           | 7        |
+| <b>Annex A (informative): Change history.....</b>                        | <b>7</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 UE RF characteristics for shared spectrum channel access.
+
+# --- 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 M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000".
+- [3] Void
+- [4] 3GPP TS 36.101: "User Equipment (UE) radio transmission and reception".
+- [5] 3GPP TS 36.521-1 : "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Conformance testing".
+- [6] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access".
+- [7] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 standalone".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
+
+**Channel bandwidth:** The RF bandwidth supporting a single E-UTRA 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.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                       |                   |
+|-----------------------|-------------------|
+| BW <sub>Channel</sub> | Channel bandwidth |
+|-----------------------|-------------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
+
+|        |                                            |
+|--------|--------------------------------------------|
+| BS     | Base Station                               |
+| E-UTRA | Evolved Universal Terrestrial Radio Access |
+| NR     | New Radio                                  |
+| PUSCH  | Physical Uplink Shared Channel             |
+| UE     | User Equipment                             |
+
+# --- 4 General
+
+## 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 36.521-1 [5] Annex F defines Test Tolerances for E-UTRA, and the test specification TS 38.521-1 [7] Annex F defines Test Tolerances for NR. 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 [2].
+
+## 4.2 Applicability of minimum requirements
+
+- In this specification the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios
+- For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements.
+- The requirements in this specification for E-UTRA TDD operating bands apply for downlink and uplink operations using Frame Structure Type 3.
+
+# --- 5 Channel access procedures
+
+## 5.1 Uplink channel access procedure
+
+For uplink operation in Band 46, Band 49, Band n46 and Band n96, a channel access procedure for PUSCH transmission as described in TS 37.213 [6], Clause 4.2.1 is specified.
+
+### 5.1.1 Channel access parameters
+
+Channel access related parameters for PUSCH are listed in Table 5.1.1-1.
+
+**Table 5.1.1-1: Channel access parameters for PUSCH**
+
+| <b>Parameter</b>               | <b>Unit</b>  | <b>Value</b> |     |
+|--------------------------------|--------------|--------------|-----|
+| LBT measurement bandwidth (BW) | MHz          | 20           | 10  |
+| Energy detection threshold     | dBm/BW       | -72          | -75 |
+| Detection timing               | microseconds | 25           |     |
+
+### 5.1.2 Minimum requirement
+
+The UE shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 5.1.1-1.

marked/Rel-18/37_series/37107/raw.md

@@ -0,0 +1,298 @@
+
+
+# 3GPP TS 37.107 V18.0.0 (2024-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base Station (BS) requirements and conformance tests for shared spectrum channel access (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. 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
+
+---
+
+<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.....                                                             | 6         |
+| 2 References.....                                                        | 6         |
+| 3 Definitions, symbols and abbreviations .....                           | 6         |
+| 3.1 Definitions.....                                                     | 6         |
+| 3.2 Symbols.....                                                         | 6         |
+| 3.3 Abbreviations .....                                                  | 6         |
+| 4 General.....                                                           | 8         |
+| 4.1 Relationship between minimum requirements and test requirements..... | 8         |
+| 5 Channel access procedures (core part).....                             | 8         |
+| 5.1 Downlink channel access procedure .....                              | 8         |
+| 5.1.1 Channel access parameters .....                                    | 8         |
+| 5.1.2 Minimum requirement.....                                           | 8         |
+| 6 Channel access procedures (performance part) .....                     | 9         |
+| 6.1 Downlink channel access procedure .....                              | 9         |
+| 6.1.1 Definition and applicability .....                                 | 9         |
+| 6.1.2 Minimum requirement.....                                           | 9         |
+| 6.1.3 Test purpose.....                                                  | 9         |
+| 6.1.4 Method of test.....                                                | 9         |
+| 6.1.4.1 Initial conditions for band 46 and band 49 .....                 | 9         |
+| 6.1.4.1a Initial conditions for band n46 and band n96 .....              | 9         |
+| 6.1.4.2 Procedure .....                                                  | 9         |
+| 6.1.5 Test Requirements .....                                            | 10        |
+| <b>Annex A (informative): Change history.....</b>                        | <b>11</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the minimum Radio Frequency (RF) characteristics, minimum performance requirements, and the RF test methods and conformance requirements for E-UTRA with LAA Base Stations (BS) and for NR-U Base Stations (BS).
+
+# --- 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 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing".
+- [3] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000".
+- [4] Void.
+- [5] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access".
+- [6] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
+
+|        |                                            |
+|--------|--------------------------------------------|
+| BS     | Base Station                               |
+| E-UTRA | Evolved Universal Terrestrial Radio Access |
+| NR     | New Radio                                  |
+
+|       |                                  |
+|-------|----------------------------------|
+| LBT   | Listen-Before-Talk               |
+| PDSCH | Physical Downlink Shared Channel |
+| RF    | Radio Frequency                  |
+
+# 4 General
+
+## 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 36.141 [2] Annex G defines Test Tolerances for E-UTRA, and the test specification TS 38.141-1 [6] Annex C defines Test Tolerances for NR. 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].
+
+# 5 Channel access procedures (core part)
+
+## 5.1 Downlink channel access procedure
+
+For downlink operation in Band 46, Band 49, Band n46 and Band n96, a channel access procedure for PDSCH transmission as described in TS 37.213 [5], Clause 4.1.1 is specified.
+
+### 5.1.1 Channel access parameters
+
+Channel access related parameters for PDSCH are listed in Table 5.1.1-1.
+
+**Table 5.1.1-1: Channel access parameters for PDSCH**
+
+| Parameter                                             | Unit      | Value                 |
+|-------------------------------------------------------|-----------|-----------------------|
+| LBT measurement bandwidth                             | MHz       | 10, 20                |
+| Energy detection threshold                            | dBm/20MHz | -72<br>or<br>X (Note) |
+|                                                       | dBm/10MHz | -75                   |
+| Maximum channel occupancy time                        | ms        | 8                     |
+| NOTE: The specific value X is declared by the vendor. |           |                       |
+
+### 5.1.2 Minimum requirement
+
+The Base Station shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 5.1.1-1.
+
+# 6 Channel access procedures (performance part)
+
+## 6.1 Downlink channel access procedure
+
+### 6.1.1 Definition and applicability
+
+Channel access procedure for downlink operation in band 46, band 49, band n46 and band n96 for PDSCH transmission is described in TS 37.213 [5], Clause 4.
+
+### 6.1.2 Minimum requirement
+
+The minimum requirement is in clause 5.1.
+
+### 6.1.3 Test purpose
+
+The test purpose is to verify the accuracy of the energy detection threshold, maximum channel occupancy time (MCOT) and minimum idle time under normal conditions for all band 46 and band 49 transmitters in the BS.
+
+### 6.1.4 Method of test
+
+#### 6.1.4.1 Initial conditions for band 46 and band 49
+
+Test environment: normal; see Annex D.2 of TS 36.141 [2].
+
+RF channels to be tested for single carrier: B, M and T; see clause 4.7 of TS 36.141 [2].
+
+Connect the signal analyzer to the base station antenna connector as shown in Annex I of TS 36.141 [2].
+
+#### 6.1.4.1a Initial conditions for band n46 and band n96
+
+Test environment: Normal, see annex B.2 of TS 38.141-1 [6].
+
+RF channels to be tested: M; see clause 4.9.1 of TS 38.141-1 [6].
+
+Set the channel set-up of the connector under as shown in annex D.1 for BS type 1-C and annex D.3 for BS type 1-H in [6].
+
+#### 6.1.4.2 Procedure
+
+##### MCOT and minimum idle time
+
+- 1) Set the base station to transmit a signal according to E-TM 1.1 at manufacturer's declared rated output power with corresponding channel bandwidth (i.e. 10 MHz or 20 MHz) for band 46 and 49, or
+
+Set the base station to transmit a signal according to NR-FR1-TM1.1 at manufacturer's declared rated output power with corresponding channel bandwidth i.e. 10 MHz (only for band n46) or 20 MHz for band n46 or n96.
+
+- 2) Measure the transmitter ON period during the continuous transmission (after the first channel access).
+- 3) Measure the transmitter OFF period between two consecutive transmitter ON periods.
+- 4) Verify minimum idle time as follows:
+
+The transmitter OFF period between two consecutive transmitter ON periods shall not be less than 25  $\mu\text{s}$ .
+
+- 5) Verify maximum channel occupancy time (MCOT) as follows:
+
+- a) The duration of each transmitter ON period continuous transmission shall not exceed the maximum channel occupancy time (MCOT) requirement specified in clause 6.1.5.
+
+##### Energy detection accuracy
+
+- 6) Generate the interfering signal of AWGN with corresponding channel bandwidth (i.e. 10 MHz or 20 MHz) at the same centre frequency as the tested channel. The interfering signal shall be at a level as specified in table 6.1.5-1. The base station shall stop transmission on the current operating channel and will not resume normal transmissions as long as the interference signal is present.
+- 7) The step 6) is repeated multiple times considering the following sub-steps:
+  - Interferer ON: if the interfering signal is present, the interfering signal should be present for 10ms.
+  - Interferer OFF: if the interfering signal is removed, the interfering signal should be absent for 10ms.
+  - The total number of interferer ON duration is assumed to be N and the total number of interferer OFF duration is assumed to be M. The value N, M and the sequence of interferer ON/OFF pattern shall be generated randomly for the test.
+- 8) In the test, a counter is maintained with initial value set to 0 when the test starts.
+- 9) For every 10ms Interferer ON period, the counter is increased by 1 if there is either an ON/OFF transition or no transmission by the DUT. To pass the test, the counter shall not be less than  $N * 0.9$ .
+
+### 6.1.5 Test Requirements
+
+In normal conditions, the measurement result shall meet channel access related test requirements for PDSCH as listed in Table 6.1.5-1.
+
+**Table 6.1.5-1: Channel access test requirements for PDSCH**
+
+| Parameter                                             | Unit      | Value                             |
+|-------------------------------------------------------|-----------|-----------------------------------|
+| LBT measurement bandwidth                             | MHz       | 10, 20                            |
+| Maximum energy detection threshold                    | dBm/20MHz | -72 + 4dB<br>or<br>X + 4dB (Note) |
+|                                                       | dBm/10MHz | -75 + 4dB                         |
+| Maximum channel occupancy time                        | ms        | 8                                 |
+| NOTE: The specific value X is declared by the vendor. |           |                                   |
+
+The Base Station shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 6.1.5-1.

marked/Rel-18/37_series/37114/raw.md

@@ -0,0 +1,979 @@
+
+
+# 3GPP TS 37.114 V18.0.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Active Antenna System (AAS) Base Station (BS) Electromagnetic Compatibility (EMC) (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. 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
+
+---
+
+<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.
+
+© 2023, 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.....                                                    | 7         |
+| 2 References.....                                               | 7         |
+| 3 Definitions, symbols and abbreviations .....                  | 9         |
+| 3.1 Definitions.....                                            | 9         |
+| 3.2 Symbols.....                                                | 11        |
+| 3.3 Abbreviations .....                                         | 11        |
+| 4 Test conditions .....                                         | 12        |
+| 4.1 Exclusion bands.....                                        | 13        |
+| 4.1.1 Transmitter exclusion band .....                          | 13        |
+| 4.1.2 Receiver exclusion band.....                              | 13        |
+| 4.2 Arrangements for establishing a communication link.....     | 14        |
+| 4.3 Narrow band responses on receivers.....                     | 14        |
+| 4.4 BS test configurations .....                                | 14        |
+| 4.5 Manufacturer declarations.....                              | 18        |
+| 5 Performance assessment .....                                  | 18        |
+| 5.1 General .....                                               | 18        |
+| 5.2 Assessment of performance in Downlink .....                 | 19        |
+| 5.3 Assessment of performance in Uplink .....                   | 19        |
+| 6 Performance criteria.....                                     | 19        |
+| 7 Applicability overview.....                                   | 20        |
+| 7.1 Emission.....                                               | 20        |
+| 7.2 Immunity .....                                              | 20        |
+| 8 Emission.....                                                 | 20        |
+| 8.1 Test configurations.....                                    | 20        |
+| 8.2 Radiated emission from base station.....                    | 21        |
+| 8.2.1 Radiated emission, hybrid AAS BS .....                    | 21        |
+| 8.2.2 Radiated emission, OTA AAS BS.....                        | 21        |
+| 8.3 Conducted emissions, DC power input/output port .....       | 22        |
+| 8.4 Conducted emissions, AC mains power input/output port.....  | 22        |
+| 8.5 Harmonic current emissions (AC mains input port) .....      | 22        |
+| 8.6 Voltage fluctuations and flicker (AC mains input port)..... | 22        |
+| 8.7 Conducted emissions, telecommunication ports .....          | 22        |
+| 9 Immunity .....                                                | 23        |
+| 9.1 Test configurations.....                                    | 23        |
+| 9.2 RF electromagnetic field (80 MHz - 6000 MHz).....           | 24        |
+| 9.2.1 RF electromagnetic field, hybrid AAS BS .....             | 24        |
+| 9.2.2 RF electromagnetic field, OTA AAS BS .....                | 24        |
+| 9.3 Electrostatic discharge.....                                | 25        |
+| 9.4 Fast transients common mode.....                            | 25        |
+| 9.5 RF common mode (0.15 MHz - 80 MHz).....                     | 26        |
+| 9.6 Voltage dips and interruptions .....                        | 26        |
+| 9.7 Surges, common and differential mode.....                   | 26        |
+| <b>Annex A (normative): Simplified immunity testing.....</b>    | <b>27</b> |
+| A.1 Applicability.....                                          | 27        |
+| A.2 Capability Sets for simplified immunity testing .....       | 27        |
+| <b>Annex B (informative): Change history .....</b>              | <b>28</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document covers the assessment of UTRA TDD, UTRA FDD, E-UTRA, NR and Multi-Standard Radio (MSR) Active Antenna Systems Base Stations in respect of Electromagnetic Compatibility (EMC).
+
+NOTE 1: Whenever the AAS BS in *single RAT UTRA operation*, or AAS BS in *MSR operation* using UTRA is referred in this specification, UTRA TDD and UTRA FDD shall be considered, unless otherwise stated.
+
+NOTE 2: For NR, scope of this specification is limited to *BS type 1-H* and *BS type 1-O*. For EMC requirements of the MSR BS for *BS type 1-C*, refer to TS 37.113 [4].
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories:
+
+- Active Antenna System Base Station for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3],
+- Active Antenna System Base Station for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of 3TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10].
+
+Technical requirements related to the TAB connector are not included in the present document. These are found in the relevant product standards [2, 3, 10].
+
+The present document does not cover ancillary equipment requirements, where ancillary equipment is not incorporated in the radio equipment and can be assessed on a stand-alone basis, as declared by the manufacturer. Ancillary equipment EMC requirements are still applicable to the AAS BS and are covered by other EMC specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30].
+
+The present document does not specify test conditions, performance assessment and performance criteria for the Narrow-Band Internet of Things (NB-IoT) in band, NB-IoT guard band, or standalone NB-IoT operation, for AAS BS in *single RAT E-UTRA operation* as defined in TS 36.113 [6], or for AAS BS in *MSR operation* using E-UTRA as defined in TS 37.113 [4].
+
+The present document does not specify test conditions, performance assessment and performance criteria for Band 46 operation as it is not supported by AAS BS.
+
+The scope of the present document is twofold:
+
+- Requirement, procedures and values of a *hybrid AAS BS* with *TAB connectors* for every transceiver unit at the *transceiver array boundary* (TAB), subject to conducted requirements,
+
+NOTE 3: *hybrid AAS BS* in the single RAT NR operation is equivalent to *BS type 1-H* defined in NR BS specification TS 38.104 [31].
+
+- Requirements, procedures and values of an OTA AAS BS without *TAB connectors* and relying in the radiated interface, subject to radiated requirements.
+
+NOTE 4: OTA AAS BS in the single RAT NR operation is equivalent to *BS type 1-O* defined in NR BS specification TS 38.104 [31].
+
+The electromagnetic environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [7] and IEC 61000-6-3 [8].
+
+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 TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception".
+- [3] 3GPP TS 37.145-1: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: Conducted conformance testing".
+- [4] 3GPP TS 37.113: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)".
+- [5] 3GPP TS 25.113: "Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)".
+- [6] 3GPP TS 36.113: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)".
+- [7] IEC 61000-6-1: 2016: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards - Immunity standard for residential, commercial and light-industrial environments".
+- [8] IEC 61000-6-3: 2006/AMD1:2010: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards - Emission standard for residential, commercial and light-industrial environments".
+- [9] Void.
+- [10] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing".
+- [11] IEC 61000-3-2: 2014: "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current  $\leq 16$  A per phase)".
+- [12] IEC 61000-3-3: 2013: "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems, for equipment with rated current  $\leq 16$  A per phase and not subject to conditional connection".
+- [13] IEC 61000-3-11: 2017 "Electromagnetic compatibility (EMC) - Part 3-11: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems - Equipment with rated current  $\leq 75$  A and subject to conditional connection".
+- [14] IEC 61000-3-12: 2011: "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic currents produced by equipment connected to public low-voltage systems with input current  $>16$  A and  $\leq 75$  A per phase".
+- [15] IEC 61000-4-2: 2008: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test".
+- [16] IEC 61000-4-3: 2006+AMD1:2007+AMD2:2010: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency, electromagnetic field immunity test".
+- [17] IEC 61000-4-4: 2012: "Electromagnetic compatibility (EMC) – Part 4-4: Testing and measurement techniques – Electrical fast transient/burst immunity test".
+- [18] IEC 61000-4-5: 2014+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test".
+- [19] IEC 61000-4-6: 2013: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to conducted disturbances, induced by radio-frequency fields".
+
+- [20] IEC 61000-4-11: 2004+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations immunity tests".
+- [21] ETSI EN 301 489-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements".
+- [22] Void
+- [23] Void
+- [24] ITU-R SM.329-10: "Unwanted emissions in the spurious domain".
+- [25] ETSI EN 301 489-50, v2.1.0: "ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 50: Specific conditions for Cellular Communication Base Station (BS), repeater and ancillary equipment; Harmonised Standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU".
+- [26] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)".
+- [27] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [28] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [29] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements".
+- [30] 3GPP TS 38.113: "NR; Base Station (BS) ElectroMagnetic Compatibility (EMC)".
+- [31] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception".
+- [32] Void
+- [33] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception".
+- [34] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements".
+- [35] IEC 61000-4-21: "Electromagnetic compatibility (EMC) - Part 4-21: Testing and measurement techniques - Reverberation chamber test methods".
+
+# --- 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], TS 37.113 [4] 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] or TS 37.113 [4].
+
+NOTE: Multi-word definitions are treated as linguistic expressions and printed in italic font throughout this requirement specification. Linguistic expressions may not be split and are printed in their entirety.
+
+**active antenna system base station:** BS system which combines an *antenna array* with a transceiver unit array and a *radio distribution network*.
+
+**antenna array:** group of radiating elements characterized by the geometry and the properties of the *array elements*.
+
+**antenna port:** RF interface at the *transceiver array boundary*, specifically the *TAB connectors*.
+
+**BS type 1-H:** NR base station operating at FR1 with a requirement set consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB.
+
+**BS type 1-O:** NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB.
+
+**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set*.
+
+**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)*, including any of UTRA, E-UTRA and/or NR operation as single RAT or multi-RAT based on TS 37.104 [33] (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]).
+
+**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier.
+
+**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within an E-UTRA carrier's guard-band.
+
+**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment.
+
+**OTA AAS BS:** AAS BS which has  $\geq 8$  *transceiver units* for E-UTRA or MSR and  $\geq 4$  *transceiver units* for UTRA per cell and has a radiated RF interface only and conforms to the *OTA requirements set*.
+
+**OTA requirements set:** complete set of OTA requirements applied to an OTA AAS BS.
+
+**port:** particular interface of EUT used for EMC requirements testing purposes.
+
+NOTE: Any connection point on EUT intended for connection of cables to or from EUT during the EMC testing is considered as a port.
+
+EXAMPLE 1: Examples of ports for *hybrid AAS BS* are as presented in figure 3.1-1:
+
+![Diagram of a hybrid AAS BS showing various ports.](5a24ac755b962fd5f0183f13de0726de_img.jpg)
+
+The diagram shows a central rectangular box labeled "Apparatus" inside a larger outer box. Above the outer box is the label "Enclosure Port". To the left of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". To the right of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "Antenna port", "Signal/control port", and "Telecommunication port".
+
+Diagram of a hybrid AAS BS showing various ports.
+
+**Figure 3.1-1: Examples of ports for *hybrid AAS BS***
+
+EXAMPLE 2: Examples of ports for OTA AAS BS (i.e. with no antenna ports) are as presented in figure 3.1-2:
+
+![Diagram of an OTA AAS BS showing various ports, with no antenna port.](2a0f333f04f8e672bebf288c511c1db5_img.jpg)
+
+The diagram shows a central rectangular box labeled "Apparatus" inside a larger outer box. Above the outer box is the label "Enclosure Port". To the left of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". To the right of the outer box, two lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "Signal/control port" and "Telecommunication port". There is no "Antenna port" shown on the right side.
+
+Diagram of an OTA AAS BS showing various ports, with no antenna port.
+
+**Figure 3.1-2: Examples of ports for OTA AAS BS**
+
+**radiated interface boundary:** operating band specific radiated requirements reference where the radiated requirements apply.
+
+**radio distribution network:** linear passive network which distributes the RF power generated by the transceiver unit array to the *antenna array*, and/or distributes the radio signals collected by the *antenna array* to the transceiver unit array.
+
+NOTE: In the case when the active transceiver units are physically integrated with the *array elements* of the *antenna array*, the *radio distribution network* is a one-to-one mapping.
+
+**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the operating band (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]).
+
+NOTE: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation.
+
+**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the operating band (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]).
+
+**spatial exclusion zone:** range of angles where no tests of radiated immunity are made for *OTA AAS BS* (i.e. half sphere around the EUT's radiating direction).
+
+**TAB connector:** *transceiver array boundary* connector.
+
+**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna.
+
+**transceiver unit:** active unit consisting of transmitter and/or receiver which transmits and/or receives radio signals, and which may include passive RF filters.
+
+**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.
+
+NOTE: ETSI EN 301 489-1 [21] calls *telecommunication port* as the "wired network port".
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                                 |                                                                                                                                                   |
+|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| $BW_{\text{Channel}}$           | Channel bandwidth                                                                                                                                 |
+| $f_{\text{offset}}$             | Frequency offset used for discovering narrowband response for receivers                                                                           |
+| $F_{\text{UL\_high}}$           | The highest frequency of the uplink operating band                                                                                                |
+| $F_{\text{UL\_low}}$            | The lowest frequency of the uplink operating band                                                                                                 |
+| $\Delta f_{\text{OOB}}$         | Maximum offset of the out-of-band boundary from the uplink operating band edge                                                                    |
+| $\Delta f_{\text{R exclusion}}$ | Maximum offset of the Radiated Immunity exclusion band from the uplink operating band edge for test without <i>spatial exclusion zone</i> applied |
+
+## 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].
+
+|        |                                                 |
+|--------|-------------------------------------------------|
+| AAS    | Active Antenna System                           |
+| AAS BS | AAS Base Station                                |
+| CSA    | Capability Set supported by the AAS BS          |
+| EMC    | ElectroMagnetic Compatibility                   |
+| EUT    | Equipment Under Test                            |
+| FR1    | Frequency Range 1                               |
+| MSR    | Multi-Standard Radio                            |
+| NB-IoT | Narrowband – Internet of Things                 |
+| NR     | New Radio                                       |
+| RCSA   | Radiated Capability Set supported by the AAS BS |
+
+|     |                             |
+|-----|-----------------------------|
+| RDN | Radio Distribution Network  |
+| RF  | Radio Frequency             |
+| RIB | Radiated Interface Boundary |
+| TAB | Transceiver Array Boundary  |
+
+# 4 Test conditions
+
+The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 37.145-1 [3], or TS 37.145-2 [10]. The test conditions shall be recorded in the test report.
+
+For an AAS BS supporting more than one RAT (see D6.12 in TS 37.145-1 [3], or D9.25 in TS 37.145-2 [10]), tests shall be performed with RATs activated according to the test configurations in subclause 4.4. Tests shall be performed relating to each type of port and RIB, and need not be repeated for each RAT if operating RATs are assessed simultaneously during the test.
+
+For AAS BS supporting single RAT operation only (see D6.12 in TS 37.145-1 [3], or D9.25 in TS 37.145-2 [10]), tests relating to the *antenna port(s)* and RIBs shall be performed for each supported RAT.
+
+For AAS BS capable of multi-band operation (see D6.13 in TS 37.145-1 [3], or D9.15 in TS 37.145-2 [10]), the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands and RATs shall be activated according to the respective test configurations in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4], or TS 38.113 [30]. Tests shall be performed relating to each type of port and RIB, and all RATs per band shall be assessed during the tests.
+
+Requirements apply only for the declared operating band(s) (see manufacturer's declaration D6.1 in TS 37.145-1 [3], or D9.4 in TS 37.145-2 [10]), and corresponding Band Categories as per CSA (see D6.12 in TS 37.145-1 [3]) and/or RCSA capability sets (see D9.25 in TS 37.145-2 [10]).
+
+The manufacturer shall declare the supported capability set(s) according to TS 37.145-1 [3] and TS 37.145-2 [10]. Tests performed on an AAS BS according to a declared capability set(s) cover all single RAT and multi-RAT configurations included in the declared capability set. Exception can be made for immunity testing based on declaration DEMC.1, DEMC.2, DEMC.3, and DEMC.4 (see table 4.5-1), as detailed in annex A.
+
+NOTE 1: *TAB connector* capability sets (CSA) for *hybrid AAS BS* are defined in TS 37.145-1 [3] and declared in D6.12 declaration.
+
+NOTE 2: Radiated capability sets (RCSA) for *hybrid AAS BS* and OTA AAS BS are defined in TS 37.145-2 [10] and declared by D9.25 declaration.
+
+Where the *hybrid AAS BS* has multiple *TAB connectors* which are declared to be equivalent then it is sufficient to perform EMC tests on a single representative *TAB connector*. For the definition of the *TAB connector* equivalence declaration (D6.70), refer to TS 37.145-1 [3].
+
+EMC test shall not be performed with the AAS BS *antenna array* radiating, all *TAB connectors* shall be disconnected from the *radio distribution network* (RDN)/antenna array as specified in TS 37.105 [2] and terminated in an appropriate load impedance. For the description of the general AAS BS radio architecture and relations between the RDN/*antenna array* and the Transceiver Array Boundary, refer to TS 37.105 [2].
+
+Depending on RAT capability sets supported by the AAS BS, the following test conditions shall be referred and applied for the BS test configurations:
+
+- For AAS BS in *single RAT UTRA operation* the test conditions from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation* the test conditions from TS 36.113 [6] apply.
+- For AAS BS in single RAT NR operation the test conditions from TS 38.113 [30] apply.
+- For AAS BS in *MSR operation* the test conditions from TS 37.113 [4] apply.
+
+Whenever ports are considered for the emissions and immunity testing in the referred TS 25.113 [5], TS 36.113 [6] and TS 37.113 [4] specifications, special considerations shall be taken to test conditions specification for OTA AAS BS due to lack of *antenna ports*.
+
+NOTE 3: The receiver exclusion bands defined in E-UTRA and MSR specifications for Band 46 operation are not applicable for AAS BS, as the Band 46 operation is not supported by AAS BS.
+
+NOTE 4: The NB-IoT operation is not supported by AAS BS.
+
+## 4.1 Exclusion bands
+
+### 4.1.1 Transmitter exclusion band
+
+The *transmitter exclusion band* for BS is the frequency range over which no tests of radiated immunity of a transmitter are made. The *transmitter exclusion band* only applies to OTA AAS BS.
+
+The *transmitter exclusion band* is defined as:
+
+$$F_{DL,low} - \Delta f_{OBUE} < f < F_{DL,high} + \Delta f_{OBUE}$$
+
+Where:
+
+The value of  $\Delta f_{OBUE}$ ,  $F_{UL,low}$  and  $F_{UL,high}$  are defined for each *operating band* for NR, E-UTRA, UTRA in TS 37.105 [2].
+
+NOTE: For BS capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported bands apply.
+
+### 4.1.2 Receiver exclusion band
+
+An exclusion band is a band of frequencies over which no tests of radiated immunity are made.
+
+In case the *spatial exclusion* (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is used during the EMC RI testing, the receiver exclusion band for OTA AAS BS is defined as:
+
+$$F_{UL,low} - \Delta f_{OOB} < f < F_{UL,high} + \Delta f_{OOB}$$
+
+Where:
+
+- Values of  $F_{UL,low}$  and  $F_{UL,high}$  are defined for each *operating band* in TS 37.104 [33].
+- The values of  $\Delta f_{OOB}$  are defined in table 4.1.2-1.
+
+**Table 4.1.2-1: Maximum  $\Delta f_{OOB}$  offset outside the uplink operating band**
+
+| <i>Operating band characteristics</i>                             | $\Delta f_{OOB}$ (MHz) |
+|-------------------------------------------------------------------|------------------------|
+| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$                   | 20                     |
+| $100 \text{ MHz} < F_{UL,high} - F_{UL,low} \leq 900 \text{ MHz}$ | 60                     |
+
+In case the *spatial exclusion zone* (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is not used during the EMC RI testing, the receiver exclusion band for OTA AAS BS and *BS type I-O* is defined as:
+
+$$F_{UL,low} - \Delta f_{RIexclusion} < f < F_{UL,high} + \Delta f_{RIexclusion}$$
+
+Where the values of  $\Delta f_{RIexclusion}$  are defined in table 4.1.2-2.
+
+**Table 4.1.2-2: Maximum  $\Delta f_{RIexclusion}$  offset outside the uplink operating band**
+
+| <i>Operating band characteristics</i>           | $\Delta f_{RIexclusion}$ (MHz) |
+|-------------------------------------------------|--------------------------------|
+| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$ | 60                             |
+| $100 \text{ MHz} < F_{UL,high} - F_{UL,low}$    | 200                            |
+
+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 AAS BS.
+
+NOTE 1: The receiver exclusion bands do not apply for SDL bands.
+
+NOTE 2: Void
+
+## 4.2 Arrangements for establishing a communication link
+
+Depending on RAT capability sets supported by the AAS BS, the following arrangements for establishing a communication link shall be referred and applied:
+
+- For AAS BS in single RAT UTRA operation, the arrangements for establishing a communication link from TS 25.113 [5] apply.
+- For AAS BS in single RAT E-UTRA operation, the arrangements for establishing a communication link from TS 36.113 [6] apply.
+- For AAS BS in MSR operation, the arrangements for establishing a communication link from TS 37.113 [4] apply.
+- For AAS BS in single RAT NR operation, the arrangements for establishing a communication link from TS 38.113 [30] apply.
+
+## 4.3 Narrow band responses on receivers
+
+Depending on RAT capability sets supported by the AAS BS, the following narrow band responses on receivers shall be referred and applied:
+
+- For AAS BS in single RAT UTRA operation, the narrow band responses on receivers from TS 25.113 [5] apply.
+- For AAS BS in single RAT E-UTRA operation, the narrow band responses on receivers from TS 36.113 [6] apply.
+- For AAS BS in MSR operation the arrangements for narrow band responses on receivers from TS 37.113 [4] apply.
+- For AAS BS in single RAT NR operation, the arrangements for narrow band responses on receivers from TS 38.113 [30] apply.
+
+## 4.4 BS test configurations
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories:
+
+- AAS BS for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3]. In this case, the EMC test configuration are listed in tables 4.4-1, 4.4-3, 4.4-5, 4.4-7, 4.4-9, 4.4-11 respectively.
+- AAS BS for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10]. In this case, the EMC test configuration are listed in table 4.4-2, 4.4-4, 4.4-6, 4.4-8, 4.4-10, 4.4-12 respectively.
+
+The test configurations apply according to the declared RAT capability sets (i.e. CSA as declared in D6.12 in TS 37.145-1 [3], or RCSA as declared in D9.25 in TS 37.145-2 [10]) of the AAS BS and the Band Category of the declared operating band (i.e. BC1, BC2 or BC3).
+
+The AAS BS test configurations are defined as ATCx in TS 37.145-1 [3] and ATCRx in TS 37.145-2 [10], clause 4.11.
+
+- For AAS BS declared to be capable of contiguous operation only (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), the test configuration(s) in tables 4.4-1, 4.4-2 and 4.4-3, 4.4-4 denoted by a "C" shall be used for testing.
+- For AAS BS declared to be capable of contiguous and non-contiguous operation (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), and where the parameters in the manufacture's declaration D6.15 in TS 37.145-1 [3] or D9.29 in TS 37.145-2 [10] are identical for contiguous and non-contiguous operation, the test configurations denoted by "CNC" shall be used.
+
+- For AAS BS declared to be capable of contiguous and non-contiguous operation (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), and where the parameters in the manufacturer's D6.15 in TS 37.145-1 [3] or D9.29 in TS 37.145-2 [10] are not identical for contiguous and non-contiguous operation, the test configurations denoted by "C/NC" shall be used for testing.
+
+For AAS BS where signals from supported RATs are processed in common active components (see DEMC.2 and DEMC.4 in table 4.5-1), it is sufficient to consider a reduced set of CSs for immunity testing, as described in Annex A.
+
+For immunity tests:
+
+- The communication link for the RAT(s) listed in the table shall be established according to subclause 4.2.
+- Tests for ports relating to the RAT(s) supported shall be performed according to subclause 4.1.
+
+**Table 4.4-1: Test configuration applicability to requirements and capability sets for TAB connectors supporting MSR operation**
+
+| TAB connector test case | UTRA + E-UTRA (CSA3)                                  |                                                       |          | E-UTRA + NR (CSA3A)                                 |                                                     |                                               | UTRA + E-UTRA + NR (CSA3B)                 |
+|-------------------------|-------------------------------------------------------|-------------------------------------------------------|----------|-----------------------------------------------------|-----------------------------------------------------|-----------------------------------------------|--------------------------------------------|
+|                         | BC1                                                   | BC2                                                   | BC3      | BC1                                                 | BC2                                                 | BC3                                           | BC1,BC2                                    |
+| Emission tests          | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3b | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC: ANTC6<br>C/NC: ATC6,<br>ANTC6 | C: ATC8<br>CNC: ANTC8<br>C/NC: ANTC8, ATC8 |
+| Immunity tests          | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3b | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC: ANTC6<br>C/NC: ATC6,<br>ANTC6 | C: ATC8<br>CNC: ANTC8<br>C/NC: ANTC8, ATC8 |
+
+**Table 4.4-2: Test configuration applicability to requirements and capability sets for AAS BS supporting MSR operation**
+
+| Test case      | UTRA + E-UTRA (RCSA 3)                                    |                                                           |     | E-UTRA + NR (RCSA 3A)                                   |                                                         |                                                   | UTRA + E-UTRA + NR (RCSA 3B)                   |
+|----------------|-----------------------------------------------------------|-----------------------------------------------------------|-----|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------|------------------------------------------------|
+|                | BC1                                                       | BC2                                                       | BC3 | BC1                                                     | BC2                                                     | BC3                                               | BC1,BC2                                        |
+| Emission tests | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | N/A | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC: ANTCR7<br>C/NC: ATCR7,<br>ANTCR7 | C: ATCR9<br>CNC: ANTCR9<br>C/NC: ATCR9, ANTCR9 |
+| Immunity tests | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | N/A | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC: ANTCR7<br>C/NC: ATCR7,<br>ANTCR7 | C: ATCR9<br>CNC: ANTCR9<br>C/NC: ATCR9, ANTCR9 |
+
+**Table 4.4-3: Test configuration applicability to requirements and capability sets for TAB connectors supporting one RAT only MSR operation**
+
+| Capability set          | UTRA (MC) capable BS (CSA1)                       |                                                   |          | E-UTRA (MC) capable BS (CSA2)                |                                              |                                                 |
+|-------------------------|---------------------------------------------------|---------------------------------------------------|----------|----------------------------------------------|----------------------------------------------|-------------------------------------------------|
+| TAB connector test case | BC1                                               | BC2                                               | BC3      | BC1                                          | BC2                                          | BC3                                             |
+| Emission tests          | C: ATC1a<br>CNC: ANTC1a<br>C/NC: ATC1a,<br>ANTC1a | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1b | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2    |
+| Immunity tests          | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1b | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a<br>CNC: ANTC2<br>C/NC: ATC2a,<br>ANTC2 |
+
+**Table 4.4-4: Test configuration applicability to requirements and capability sets for operating bands supporting one RAT only MSR operation**
+
+| Capability set | UTRA (MC) capable BS (RCSA1)                                |                                                             |     | E-UTRA (MC) capable BS (RCSA2)                         |                                                        |                                                        |
+|----------------|-------------------------------------------------------------|-------------------------------------------------------------|-----|--------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------|
+| Test case      | BC1                                                         | BC2                                                         | BC3 | BC1                                                    | BC2                                                    | BC3                                                    |
+| Emission tests | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | N/A | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 |
+| Immunity tests | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | N/A | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 |
+
+**Table 4.4-5: Test configurations for a TAB connector supporting single-RAT UTRA operation**
+
+| TAB connector test case | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C capable only | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC capable TAB connector (CSA4) C capable only |
+|-------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| Emission tests          | ATC1a                                                              | ANTC1                                                                                          | ATC1a, ANTC1                                                                                   | ATC1b                                                              |
+| Immunity tests          | ATC1a                                                              | ANTC1                                                                                          | ATC1a, ANTC1                                                                                   | ATC1b                                                              |
+
+**Table 4.4-6: Test configurations for an AAS BS supporting single-RAT UTRA operation**
+
+| Test case      | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C capable only | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC AAS BS operating band (RCSA4) C capable only |
+|----------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
+| Emission tests | ATC1a                                                                       | ANTC1                                                                                                   | ATC1a, ANTC1                                                                                            | N/A                                                                 |
+| Immunity tests | ATCR1a                                                                      | ANTCR1                                                                                                  | ATCR1a, ANTCR1                                                                                          | N/A                                                                 |
+
+**Table 4.4-7: Test configurations for a *TAB connector* supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band**
+
+| <i>TAB connector</i> test case | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C capable only | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C and NC capable BS with identical parameters (CNC) | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C and NC capable BS with different parameters (CNC) |
+|--------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|
+| Emission tests                 | ATC2a                                                                      | ANTC2                                                                                                           | ATC2a, ANTC2                                                                                                    |
+| Immunity tests                 | ATC2a                                                                      | ANTC2                                                                                                           | ATC2a, ANTC2                                                                                                    |
+
+**Table 4.4-8: Test configurations for an AAS BS supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band**
+
+| Test case      | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C capable only | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C and NC capable BS with identical parameters | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C and NC capable BS with different parameters |
+|----------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|
+| Emission tests | ATCR2a                                                                       | ANTCR2                                                                                                      | ATCR2a, ANTCR2                                                                                              |
+| Immunity tests | ATCR2a                                                                       | ANTCR2                                                                                                      | ATCR2a, ANTCR2                                                                                              |
+
+**Table 4.4-9: Test configuration for *multi-band TAB connectors* supporting MSR operation**
+
+| <i>TAB connector</i> test case | Test configuration for MBT |       |
+|--------------------------------|----------------------------|-------|
+|                                | BC1/BC2                    | BC3   |
+| Emission tests                 | ATC5b                      | ATC5b |
+| Immunity tests                 | ATC5b                      | ATC5b |
+
+**Table 4.4-10: Test configuration for AAS BS operating bands containing beams with multi-band dependencies supporting MSR operation**
+
+| <i>TAB connector</i> test case | Test configuration for MBT |        |
+|--------------------------------|----------------------------|--------|
+|                                | BC1/BC2                    | BC3    |
+| Emission tests                 | ATCR5b                     | ATCR5b |
+| Immunity tests                 | ATCR5b                     | ATCR5b |
+
+**Table 4.4-11: Test configuration for *multi-band TAB connectors* supporting Single-RAT only**
+
+| <i>TAB connector</i> test case | UTRA FDD CSA4                 | UTRA TDD CSA4         | E-UTRA Test CSA5               |
+|--------------------------------|-------------------------------|-----------------------|--------------------------------|
+| Emission test                  | ATC1a/ANTC1 (note 1)<br>ATC5b | ATC1b (note 2), ATC5a | ATC2a/ANTC2 (note 3),<br>ATC5b |
+| Immunity test                  | ATC5b                         | ATC5a                 | ATC5b                          |
+
+NOTE 1: ATC1a and/or ANTC1 shall be applied in each supported operating band according to table 4.4-3a.  
+NOTE 2: ATC1b shall be applied in each supported operating band according to table 4.4-3a.  
+NOTE 3: ATC2 and/or ANTC2 shall be applied in each supported operating band according to table 4.4-4a.
+
+**Table 4.4-12: Test configuration for AAS BS operating bands with multi-band dependencies supporting single-RAT only**
+
+| <i>TAB connector</i> test case | UTRA FDD CSA4                    | UTRA TDD CSA4 | E-UTRA Test CSA5                  |
+|--------------------------------|----------------------------------|---------------|-----------------------------------|
+| Emission test                  | ATCR1a/ANTCR1 (note 1)<br>ATCR5b | N/A           | ATCR2a/ANTCR2 (note 2),<br>ATCR5b |
+| Immunity test                  | ATCR5b                           | N/A           | ATCR5b                            |
+
+NOTE 1: ATCR1a and/or ANTCR1 shall be applied in each supported operating band according to table 4.4-3b.  
+NOTE 2: ATCR2 and/or ANTCR2 shall be applied in each supported operating band according to table 4.4-4b.
+
+## 4.5 Manufacturer declarations
+
+The following EMC-specific manufacturer's declarations listed in table 4.5-1 are required to be provided by the manufacturer for AAS BS requirements testing.
+
+NOTE: The below listed manufacturer's declarations are supplementary to declarations covered in TS 37.145-1 [3], and in TS 37.145-2 [10].
+
+**Table 4.5-1: EMC-specific manufacturer declarations**
+
+| Declaration identifier                           | Declaration                                         | Description                                                                                                                                                                                                                                                                                                               |
+|--------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DEMC.1<br>(NOTE)                                 | Ports intended to be used with cables less than 3 m | Declaration of any port(s) intended to be used with cables less than 3 m.                                                                                                                                                                                                                                                 |
+| DEMC.2                                           | Common and/or RAT-specific active RF components     | Declaration of common and/or RAT-specific active RF components and other HW blocks for a communication link in AAS BS or other BS supporting more than one RAT.                                                                                                                                                           |
+| DEMC.3                                           | Common and/or band-specific active RF components    | Declaration of common and/or band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation.                                                                                                                                                                       |
+| DEMC.4<br>(NOTE)                                 | RAT dependencies for simplified immunity testing    | Declaration of RAT dependencies for simplified immunity testing. For the case where BS employs common active RF components (DEMC.2), declare RATs which are handled per operating band in common active components in the radio digital unit. Declared per supported operating band (in case supported by multiple RATs). |
+| NOTE: This manufacturer declaration is optional. |                                                     |                                                                                                                                                                                                                                                                                                                           |
+
+# 5 Performance assessment
+
+## 5.1 General
+
+The 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 RAT-specific active RF components and other HW blocks for a communication link in AAS BS supporting more than one RAT; (see declaration DEMC.2);
+- information about the common and/or band-specific active RF components and other HW blocks for a communication link in AAS BS capable of multi-band operation; (see declaration DEMC.3);
+- an exhaustive list of ports (and RIBs), classified as either power or signal/control. Power ports shall further be classified as AC or DC power.
+
+A communication link used by more than one tested RAT or more than one tested operating band, shall be assessed on all tested RATs and operating bands. Communication link(s) and/or radio performance parameters for the RATs and operating bands can during the test be assessed simultaneously or separately for each RAT and band, depending on the test environment capability.
+
+NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance assessment the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred.
+
+NOTE 2: The NB-IoT operation is not supported by AAS BS.
+
+## 5.2 Assessment of performance in Downlink
+
+In the immunity tests, the output of the transmitter shall be connected (via port for hybrid AAS BS, or via RIB for OTA AAS BS) to test equipment which meets the requirements for the performance assessment of RAT and bearer used in the immunity tests according to the following:
+
+- BLER assessment in TS 25.102 [26] in case of UTRA TDD
+- BLER assessment in TS 25.101 [27] in case of UTRA FDD
+- Throughput assessment in TS 36.101 [28] in case of E-UTRA
+- Throughput assessment in TS 38.101-4 [34] in case of NR
+
+The level of the signal supplied to the equipment should be within the range for which the assessment of throughput is not impaired. Power control shall be OFF during the immunity testing.
+
+## 5.3 Assessment of performance in Uplink
+
+In the immunity tests, the performance in the uplink shall be monitored at a telecommunications port(s) by using suitable test equipment according to the following:
+
+- The value of the throughput shall be monitored in case of E-UTRA or in case of NR
+- The value of the BLER shall be monitored in case of UTRA FDD or in case of UTRA TDD
+
+# --- 6 Performance criteria
+
+The test should, where possible, be performed using a bearer with the characteristics of data rate and performance criteria defined for UTRA TDD, UTRA FDD, E-UTRA, or NR. If the test is not performed using one of these bearers (for example, if none of them are supported by the BS) the characteristics of the bearer used shall be recorded in the test report.
+
+Depending on RAT capability sets supported by the AAS BS, the following performance criteria for continuous or for transient phenomena shall be referred and applied:
+
+- For AAS BS in *single RAT UTRA operation*, the performance criteria from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the performance criteria from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the performance criteria from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the performance criteria from TS 38.113 [30] apply.
+
+NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance criteria the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred.
+
+NOTE 2: The NB-IoT operation is not supported by AAS BS.
+
+# 7 Applicability overview
+
+## 7.1 Emission
+
+Table 7.1-1: Emission requirements applicability
+
+| Phenomenon                       | Application                | Equipment test requirement                 | Reference subclause in the present document | Reference standard                              |
+|----------------------------------|----------------------------|--------------------------------------------|---------------------------------------------|-------------------------------------------------|
+|                                  |                            | BS equipment                               |                                             |                                                 |
+| Radiated emission                | Enclosure                  | applicable for <i>hybrid AAS BS</i> (Note) | 8.2.1                                       | ITU-R SM.329 [24]                               |
+| Conducted emission               | DC power input/output port | applicable                                 | 8.3                                         | CISPR 32 [29]                                   |
+| Conducted emission               | AC mains input/output port | applicable                                 | 8.4                                         | CISPR 32 [29]                                   |
+| Conducted emission               | Telecommunication port     | applicable                                 | 8.5                                         | CISPR 32 [29]                                   |
+| Harmonic current emissions       | AC mains input port        | applicable                                 | 8.6                                         | IEC 61000-3-2 [11]<br>or<br>IEC 61000-3-12 [14] |
+| Voltage fluctuations and flicker | AC mains input port        | applicable                                 | 8.7                                         | IEC 61000-3-3 [12]<br>or<br>IEC 61000-3-11 [13] |
+
+NOTE: The EMC radiated emissions requirements for the OTA AAS BS are covered by the RF radiated emissions requirement in TS 37.105 [2], conforming to the TS 37.145-2 [10].
+
+## 7.2 Immunity
+
+Table 7.2-1: Immunity requirements applicability
+
+| Phenomenon                               | Application                                                               | Equipment test requirement | Reference subclause in the present document | Reference standard  |
+|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------------------------------|---------------------|
+|                                          |                                                                           | BS equipment               |                                             |                     |
+| RF electromagnetic field (80 – 6000 MHz) | Enclosure                                                                 | applicable                 | 9.2                                         | IEC 61000-4-3 [16]  |
+| Electrostatic discharge                  | Enclosure                                                                 | applicable                 | 9.3                                         | IEC 61000-4-2 [15]  |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | 9.4                                         | IEC 61000-4-4 [17]  |
+| RF common mode 0.15 - 80 MHz             | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | 9.5                                         | IEC 61000-4-6 [19]  |
+| Voltage dips and interruptions           | AC mains power input ports                                                | applicable                 | 9.6                                         | IEC 61000-4-11 [20] |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | applicable                 | 9.7                                         | IEC 61000-4-5 [18]  |
+
+# 8 Emission
+
+## 8.1 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. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- For OTA AAS BS without Radio Frequency (RF) input/output ports but intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup suitable for the radiated power;
+- 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 clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time.
+
+## 8.2 Radiated emission from base station
+
+### 8.2.1 Radiated emission, hybrid AAS BS
+
+This test is applicable to *hybrid AAS BS*. This test shall be performed on a representative configuration of the *hybrid AAS BS*.
+
+Depending on RAT capability sets supported by the *hybrid AAS BS*, the following radiated emission requirements apply:
+
+- For *hybrid AAS BS* in *single RAT UTRA operation*, the base stations radiated emission requirements from TS 25.113 [5] apply.
+- For *hybrid AAS BS* in *single RAT E-UTRA operation* the base stations radiated emission requirements from TS 36.113 [6] apply.
+- For *hybrid AAS BS* in *MSR operation*, the base stations radiated emission requirements from TS 37.113 [4] apply.
+- For *hybrid AAS BS* in *single RAT NR operation*, the *BS type I-H* radiated emission requirements from TS 38.113 [30] apply.
+
+### 8.2.2 Radiated emission, OTA AAS BS
+
+This test is applicable to OTA AAS BS. This test shall be performed on a representative configuration of the OTA AAS BS.
+
+For OTA AAS BS, the radiated emission requirement is covered by RF radiated spurious emission requirement in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10].
+
+- NOTE: As the EMC radiated emissions of the OTA AAS BS cannot be distinguished between the intended emissions (nor to any spurious emissions related to these intentional transmissions) a single radiated emissions requirement is used for the OTA AAS BS.
+
+## 8.3 Conducted emissions, 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.4.
+
+This test shall be performed on a representative configuration of the radio equipment.
+
+Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply:
+
+- For AAS BS in *single RAT UTRA operation*, the DC power input/output port conducted emissions requirements from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the DC power input/output port conducted emissions requirements from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the DC power input/output port conducted emissions requirements from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the DC power input/output port conducted emissions requirements from TS 38.113 [30] apply.
+
+## 8.4 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.
+
+Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply:
+
+- For AAS BS in *single RAT UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the AC mains power input/output port conducted emissions requirements from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the AC mains power input/output port conducted emissions requirements from TS 38.113 [30] apply.
+
+## 8.5 Harmonic current emissions (AC mains input port)
+
+The requirements of IEC 61000-3-2 [11] 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 [14] applies.
+
+## 8.6 Voltage fluctuations and flicker (AC mains input port)
+
+The requirements of IEC 61000-3-3 [12] 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-11 [13] applies.
+
+## 8.7 Conducted emissions, telecommunication ports
+
+This test is applicable for radio equipment for fixed use which have telecommunication ports.
+
+This test shall be performed on a representative configuration of radio equipment.
+
+The test method and limits shall be in accordance with CISPR 32 [29], as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+# --- 9 Immunity
+
+## 9.1 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;
+- During test, the RF output power may be reduced to a power level sufficient for establishing and maintaining the required communication link;
+- 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. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- For OTA AAS BS intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup capable to reduce the power to a level sufficient for establishing and maintaining the communication link;
+- 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 AAS BS shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the S1/Iub interface (e.g. with an RNC/EPC simulator) and evaluating the BLER/throughput (see figures 9.1-1 and 9.1-2);
+- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the radio interface and the S1/Iub interface. BLER/throughput 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 radio interface or S1/Iub interface. In case of looping is used care have to be taken that the BLER/throughput information doesn't change due to looping;
+- For AAS BS capable of multi-RAT and/or multi-band operation, communication links shall be established in such a way that all tested RATs and operating band(s) are activated during the test according to the applicable test configurations in subclause 4.5. Performance assessment may be done separately for each tested RAT and/or operating band
+
+![Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator.
+
+**Figure 9.1-1: Communication link set up for *hybrid AAS BS* immunity measurement**
+
+![Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator.](d9c0a780cd22626253dab4aa41699e2f_img.jpg)
+
+Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator.
+
+**Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement**
+
+## 9.2 RF electromagnetic field (80 MHz - 6000 MHz)
+
+### 9.2.1 RF electromagnetic field, hybrid AAS BS
+
+This test assesses the ability of radio equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. This test is applicable to *hybrid AAS BS* and shall be performed on a representative configuration of the *hybrid AAS BS*.
+
+The test method and levels shall be in accordance with IEC 61000-4-3 [16] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. The use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed.
+
+### 9.2.2 RF electromagnetic field, OTA AAS BS
+
+This test assesses the ability of radio equipment operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. The OTA AAS BS includes an antenna which is an intentional radiator and does not form part of the EMC enclosure, application of RF electromagnetic fields in these directions may damage the BS receivers unintentionally.
+
+In the operational range of angles of the OTA AAS BS antenna receivers are protected by the RF blocking requirements defined in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10] and are not part of the EMC RF electromagnetic field immunity requirement.
+
+In the range of angles except the operational range of angles of the OTA AAS BS antenna (i.e. except for the half sphere around the DUT radiating direction as depicted on figure 9.2.2-1) and for the frequency range above 690 MHz (according to ETSI EN 301 489-50 [25]), the EMC RF electromagnetic field immunity requirement with a level of 10 V/m applies on the non-radiating faces of the OTA AAS BS, as depicted on figure 9.2.2-1.
+
+When no spatial exclusion is implemented the use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed.
+
+![Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg)
+
+Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT.
+
+**Figure 9.2.2-1 EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS (horizontal plane depicted) with the spatial exclusion zone applied**
+
+Depending on RAT capability sets supported by the OTA AAS BS, the following RF electromagnetic field requirements apply over the range of angles covered by the EMC RF electromagnetic field immunity requirement:
+
+- For OTA AAS BS in *single RAT UTRA operation*, the RF electromagnetic field immunity requirements from TS 25.113 [5] apply.
+- For OTA AAS BS in *single RAT E-UTRA operation*, the RF electromagnetic field immunity requirements from TS 36.113 [6] apply.
+- For OTA AAS BS in *MSR operation*, the RF electromagnetic field immunity requirements from TS 37.113 [4] apply.
+- For OTA AAS BS in *single RAT NR operation*, the *BS type I-O* requirements for the RF electromagnetic field immunity from TS 38.113 [30] apply.
+
+## 9.3 Electrostatic discharge
+
+This test assesses the ability of radio equipment to operate as intended in the event of an electrostatic discharge.
+
+The test shall be performed on a representative configuration of the radio equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-2 [15] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.4 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 in DEMC.1 (see table 4.5-1) 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 test method and levels shall be in accordance with IEC 61000-4-4 [17] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.5 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 in DEMC.1 (see table 4.5-1) 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 test method and levels shall be in accordance with IEC 61000-4-6 [19] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [19].
+
+## 9.6 Voltage dips and interruptions
+
+These tests assess the ability of radio equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports.
+
+The tests shall be performed on AC mains power input ports.
+
+These tests shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-11 [20] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.7 Surges, common and differential mode
+
+These tests assess the ability of radio equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports.
+
+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 test method and levels shall be in accordance with IEC 61000-4-5 [18] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+# Annex A (normative): Simplified immunity testing
+
+## A.1 Applicability
+
+Simplified immunity testing applies, per operating band, only to the BS which satisfies both of the following conditions:
+
+- Radio unit employs common active RF components for supported RATs, as described in DEMC.2.
+- Radio digital unit employs common active components for supported RATs, as described in DEMC.4.
+
+NOTE: If the above condition is not met, all applicable test configurations in clause 4.4 apply for testing.
+
+## A.2 Capability Sets for simplified immunity testing
+
+The set of RATs which are considered sufficient for the immunity testing purposes depends on the BS hardware capabilities declared by the manufacturer in DEMC.4.
+
+The following RAT combinations were identified as candidates for the immunity testing reductions:
+
+- For AAS BS declared to support E-UTRA and UTRA, UTRA does not have to be configured.
+- For AAS BS declared to support NR and UTRA, UTRA does not have to be configured.
+
+The above RAT combinations were further translated into the Capability Sets in tables below.
+
+For single-band AAS BS, the sufficient CSs in tables A.2-1 and A.2-2 may be considered, instead of the CSs in tables 4.4-1 and 4.4-2, respectively.
+
+The test configurations (TCx) are associated to the sufficient CSs according to tables 4.4-1 and 4.4-2.
+
+Example: BS declared to support CS9 (corresponding to TC9) in table A.2-2, will be tested using TC8 (corresponding to CS8).
+
+**Table A.2-1: Declared and sufficient CSs for testing**
+
+| Declared Capability Set   | UTRA + E-UTRA (CSA3)          | E-UTRA + NR (CSA3A) | UTRA + E-UTRA + NR (CSA3B) |
+|---------------------------|-------------------------------|---------------------|----------------------------|
+| Sufficient CS for testing | E-UTRA (MC) capable BS (CSA2) | E-UTRA + NR (CSA3A) | E-UTRA + NR (CSA3A)        |
+
+**Table A.2-2: Declared and sufficient CSs for testing**
+
+| Declared Capability Set   | UTRA + E-UTRA (RCSA 3)         | E-UTRA + NR (RCSA 3A) | UTRA + E-UTRA + NR (RCSA 3B) |
+|---------------------------|--------------------------------|-----------------------|------------------------------|
+| Sufficient CS for testing | E-UTRA (MC) capable BS (RCSA2) | E-UTRA + NR (RCSA 3A) | E-UTRA + NR (RCSA 3A)        |
+
+For multi-band multi-RAT capable MSR BS, the rationale described above applies for each band.
+
+# Annex B (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                                                  |               |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------|---------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                  | New version   |
+| 2016-02        | RAN4#78 | R4-161123 |      |     |     | First version of TS                                                                              | 0.1.0         |
+| 2016-03        | RAN#71  | RP-160401 |      |     |     | Presented to RAN for approval.<br>Editorial corrections recommended by ETSI editHelp             | 1.0.0         |
+| 2016-03        | RP-71   |           |      |     |     | TR approved by RAN plenary                                                                       | 13.0.0        |
+| 2016/06        | RP-72   | RP-161142 | 0002 | 1   | F   | Clarification in EMC environmental conditions references                                         | 13.1.0        |
+| 2017/03        | RP-75   | RP-170586 | 0004 | -   | F   | CR to TS 37.114: Clarification of the EMC specification's scope                                  | 13.2.0        |
+| 2017-03        | RP-75   | -         | -    | -   | -   | Update to Rel-14 version (MCC)                                                                   | 14.0.0        |
+| 2017/06        | RP-76   | RP-171306 | 0009 |     | A   | CR to TS 37.114: Isolation of Band 46 and NB-IoT from the AAS BS specification                   | 14.1.0        |
+| 2017-12        | RAN#78  | RP-172599 | 0059 | 1   | B   | Big CR to TS 37.114: eAAS EMC specification, v15.0.0                                             | 15.0.0        |
+| 2018-03        | RAN#79  | RP-180282 | 0064 |     | F   | CR to TS37.114                                                                                   | 15.1.0        |
+| 2018-06        | RAN#80  | RP-181075 | 0067 | 1   | B   | CR to TS 37.114: NR introduction into AAS EMC specification                                      | 15.2.0        |
+| 2018-12        | RAN#82  | RP-182362 | 0071 | 2   | B   | CR to TS 37.114: Clarification on Exclusion Bands for Radiated Immunity Test in FR2              | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0073 | 1   | F   | CR to TS 37.114: additional inputs for introduction of NR to the AAS EMC specification           | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0074 |     | F   | CR to TS 37.114: RAT-specific AAS BS operation terminology corrections                           | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0075 | 1   | B   | CR to TS 37.114: Consideration of the narrowband responses and communication link                | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0076 |     | F   | CR to TS 37.114: clarification on CSA and RCSA capability sets                                   | 15.3.0        |
+| 2019-03        | RAN#83  | RP-190401 | 0077 | 1   | B   | Draft CR to TS 37.114 Exclusion Bands for Radiated                                               | 15.4.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0078 | 1   | F   | CR to TS 37.114: Updates for Rx exclusion zone size and terminology for EMC RI testing purposes  | 15.5.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0080 | 1   | F   | CR to TS 37.114 subclause 4.2                                                                    | 15.5.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0084 |     | F   | CR to 37.114 Subsections index in Section 4.1                                                    | 15.5.0        |
+| 2019-09        | RAN#85  | RP-192019 | 0085 |     | F   | CR to TS 37.114 Correction on CISPR 16-1-1 for DC conducted Emission(clause 2 and subclause 7.1) | 15.6.0        |
+| 2019-09        | RAN#85  | RP-192053 | 0087 | 1   | F   | CR to 37.114 Editorial Corrections                                                               | 15.6.0        |
+| 2019-12        | RAN#86  | RP-193002 | 0093 |     | F   | CR to TS 37.114 Correction on definitions subclause 3.1                                          | 15.7.0        |
+| 2019-12        | RAN#86  | RP-193002 | 0094 |     | F   | CR to TS 37.114 Correction on notes in subclause 7.1                                             | 15.7.0        |
+| 2020-03        | RAN#87  | RP-200393 | 0095 | 1   | F   | CR to TS 37.114 Add the transmitter exclusion band for MSR BS(subclause 4.1)                     | 15.8.0        |
+| 2020-06        | RAN#88  | RP-201005 | 0096 |     | F   | CR to TS 37.114: internal TR reference corrections, Rel-15                                       | 15.9.0        |
+| 2020-06        | RAN#88  | RP-200984 | 0097 | 1   | F   | [R15]CR to TS 37.114 Add the reverberation chamber for radiated immunity testing (clause 2)      | 15.9.0        |
+| 2020-06        | RAN#88  | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                                                   | <b>16.0.0</b> |
+
+| Change history |         |           |      |     |     |                                                                |             |
+|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                | New version |
+| 2022-03        | SA#95   |           |      |     |     | Update to Rel-17 version (MCC)                                 | 17.0.0      |
+| 2023-03        | RAN#99  | RP-230502 | 0100 |     | F   | CR to TS 37.114 AAS BS test configuration R15                  | 17.1.0      |
+| 2023-03        | RAN#99  | RP-230505 | 0106 |     | F   | TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity | 17.1.0      |
+
+| Change history |         |           |      |     |     |                                                                                                                   |             |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                   | New version |
+| 2023-12        | RAN#102 | RP-233360 | 0108 | 1   | F   | [AAS_BS_LTE_UTRA-Core, TE118] CR to TS 37.114: framework for the EMC-specific manufacturer's declarations, Rel-18 | 18.0.0      |
+| 2023-12        | RAN#102 | RP-233364 | 0109 | 1   | B   | CR to TS 37.114: Implementation of AAS BS testing simplifications, Rel-18                                         | 18.0.0      |

marked/Rel-18/37_series/37324/raw.md

@@ -0,0 +1,609 @@
+
+
+# 3GPP TS 37.324 V18.0.0 (2024-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 18)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text is a red graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+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 and abbreviations .....                                     | 6  |
+| 3.1 Definitions.....                                                               | 6  |
+| 3.2 Abbreviations .....                                                            | 6  |
+| 4 General.....                                                                     | 7  |
+| 4.1 Introduction .....                                                             | 7  |
+| 4.2 SDAP architecture.....                                                         | 7  |
+| 4.2.1 SDAP structure .....                                                         | 7  |
+| 4.2.2 SDAP entities .....                                                          | 8  |
+| 4.3 Services .....                                                                 | 9  |
+| 4.3.1 Services provided to upper layers.....                                       | 9  |
+| 4.3.2 Services expected from lower layers.....                                     | 9  |
+| 4.4 Functions .....                                                                | 9  |
+| 5 SDAP procedures.....                                                             | 9  |
+| 5.1 SDAP entity handling.....                                                      | 9  |
+| 5.1.1 SDAP entity establishment.....                                               | 9  |
+| 5.1.2 SDAP entity release.....                                                     | 9  |
+| 5.2 Data transfer .....                                                            | 10 |
+| 5.2.1 Uplink.....                                                                  | 10 |
+| 5.2.2 Downlink.....                                                                | 10 |
+| 5.2.3 SL transmission .....                                                        | 10 |
+| 5.2.4 SL reception.....                                                            | 11 |
+| 5.3 QoS flow to DRB mapping .....                                                  | 11 |
+| 5.3.1 Configuration.....                                                           | 11 |
+| 5.3.2 Reflective mapping.....                                                      | 12 |
+| 5.3.3 DRB release.....                                                             | 12 |
+| 5.4 RQI handling.....                                                              | 12 |
+| 5.5 PC5 QoS flow to SL-DRB mapping .....                                           | 12 |
+| 5.5.1 Configuration.....                                                           | 12 |
+| 5.5.2 SL-DRB release.....                                                          | 13 |
+| 6 Protocol data units, formats, and parameters .....                               | 13 |
+| 6.1 Protocol data units.....                                                       | 13 |
+| 6.1.1 Data PDU.....                                                                | 13 |
+| 6.1.2 Control PDU .....                                                            | 13 |
+| 6.2 Formats.....                                                                   | 13 |
+| 6.2.1 General .....                                                                | 13 |
+| 6.2.2 Data PDU.....                                                                | 13 |
+| 6.2.2.1 Data PDU without SDAP header.....                                          | 13 |
+| 6.2.2.2 DL Data PDU with SDAP header.....                                          | 14 |
+| 6.2.2.3 UL Data PDU with SDAP header.....                                          | 14 |
+| 6.2.2.4 SL Data PDU with SDAP header for unicast of NR sidelink communication..... | 14 |
+| 6.2.3 End-Marker Control PDU .....                                                 | 15 |
+| 6.3 Parameters .....                                                               | 15 |
+| 6.3.1 General .....                                                                | 15 |
+| 6.3.2 Data.....                                                                    | 15 |
+| 6.3.3 D/C .....                                                                    | 15 |
+| 6.3.4 QFI.....                                                                     | 15 |
+| 6.3.5 R .....                                                                      | 16 |
+| 6.3.6 RQI.....                                                                     | 16 |
+| 6.3.7 RDI.....                                                                     | 16 |
+| 6.3.8 PQFI .....                                                                   | 16 |
+
+**Annex A (informative): Change history................................................................................................................ 17**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 Service Data Adaptation Protocol (SDAP) for a UE with connection to the 5G-CN or for a UE in NR sidelink communication.
+
+# 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 38.300: "NG Radio Access Network; Overall description".
+- [3] 3GPP TS 38.331: "NR Radio Resource Control (RRC); Protocol Specification".
+- [4] 3GPP TS 23.501: "System Architecture for the 5G System".
+- [5] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
+- [6] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3".
+
+# 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].
+
+**PC5 QoS flow to SL-DRB mapping rule:** a mapping rule determining on which SL-DRB packets of a PC5 QoS flow shall be carried.
+
+**QoS flow to DRB mapping rule:** a mapping rule determining on which DRB packets of a QoS flow shall be carried.
+
+**Reflective QoS flow to DRB mapping:** a QoS flow to DRB mapping scheme where a UE monitors the QoS flow to DRB mapping rule in the DL, and applies it to in the UL.
+
+**NR sidelink communication:** AS functionality enabling at least V2X communication as defined in TS 23.287 [5], between two or more nearby UEs, using NR technology but not traversing any network node.
+
+## 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].
+
+|      |                 |
+|------|-----------------|
+| PQFI | PC5 QoS Flow ID |
+|------|-----------------|
+
+|        |                                               |
+|--------|-----------------------------------------------|
+| QFI    | QoS Flow ID                                   |
+| RDI    | Reflective QoS flow to DRB mapping Indication |
+| RQI    | Reflective QoS Indication                     |
+| SDAP   | Service Data Adaptation Protocol              |
+| SL     | Sidelink                                      |
+| SL-DRB | Sidelink Data Radio Bearer                    |
+
+# 4 General
+
+## 4.1 Introduction
+
+The objective is to describe the SDAP architecture and the SDAP entity from a functional point of view. The specified functionality only applies to UE with connection to the 5G-CN and UE in NR sidelink communication.
+
+## 4.2 SDAP architecture
+
+### 4.2.1 SDAP structure
+
+Figure 4.2.1-1 illustrates one possible structure for the SDAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2].
+
+![Diagram of SDAP sublayer structure showing QoS Flows, SDAP entities, Radio Bearers, and PDCP entities.](e2c1c672349c10dccb2563eff6d8260e_img.jpg)
+
+The diagram illustrates the SDAP sublayer structure. At the top, multiple 'QoS Flows' are shown, each connected to an 'SDAP-SAP' (Service Access Point). These SAPs are part of the 'SDAP sublayer', which contains two 'SDAP entity' blocks. Below the SDAP sublayer, there are 'Radio Bearers', also connected to 'SDAP-SAP' points. Between the SDAP sublayer and the 'PDCP sublayer' are two boxes labeled 'SDAP - PDU' and 'PDCP - SDU'. The 'PDCP sublayer' contains four 'PDCP entity' blocks. Vertical double-headed arrows connect the 'SDAP-SAP' points in the SDAP sublayer to the 'PDCP-SAP' points in the PDCP sublayer, indicating data flow through the Radio Bearers.
+
+Diagram of SDAP sublayer structure showing QoS Flows, SDAP entities, Radio Bearers, and PDCP entities.
+
+Figure 4.2.1-1: SDAP sublayer, structure view
+
+The SDAP sublayer is configured for DRBs by RRC (TS 38.331 [3]). The SDAP sublayer maps QoS flows to DRBs. One or more QoS flows may be mapped onto one DRB. One QoS flow is mapped onto only one DRB at a time in the UL.
+
+The SDAP sublayer is configured for MRBs by RRC (TS 38.331 [3]). The SDAP sublayer maps MBS QoS flows to MRBs. One or more MBS QoS flows may be mapped onto one MRB.
+
+In NR sidelink communication, the SDAP sublayer maps PC5 QoS flows to SL-DRBs. One or more PC5 QoS flows may be mapped onto one SL-DRB. One PC5 QoS flow is mapped onto only one SL-DRB at a time in the NR sidelink for transmission.
+
+### 4.2.2 SDAP entities
+
+The SDAP entities are located in the SDAP sublayer. Several SDAP entities may be defined for a UE. There is an SDAP entity configured for each individual PDU session or MBS session for NR Uu. For NR sidelink, SDAP entity is configured per Destination Layer-2 ID and cast type in the UE.
+
+An SDAP entity receives/delivers SDAP SDUs from/to upper layers and submits/receives SDAP data PDUs to/from its peer SDAP entity via lower layers.
+
+- At the transmitting side, when an SDAP entity receives an SDAP SDU from upper layers, it constructs the corresponding SDAP data PDU and submits it to lower layers;
+- At the receiving side, when an SDAP entity receives an SDAP data PDU from lower layers, it retrieves the corresponding SDAP SDU and delivers it to upper layers.
+
+Figure 4.2.2-1 illustrates the functional view of the SDAP entity for the SDAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2].
+
+![Figure 4.2.2-1: SDAP layer, functional view. The diagram shows the functional flow of data through the SDAP layer on both the transmitting (UE/NG-RAN/UEA) and receiving (NG-RAN/UE/UEB) sides, connected by a Radio Interface (Uu/PC5).](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+The diagram illustrates the functional view of the SDAP layer across two entities: UE/NG-RAN/UEA (left) and NG-RAN/UE/UEB (right), connected by a Radio Interface (Uu/PC5).
+
+**Transmitting Side (UE/NG-RAN/UEA):**
+
+- A **QoS flow** enters the **Transmitting SDAP entity**.
+- The flow goes to **Mapping of QoS flow to a DRB/MRB/SL DRB**.
+- From this mapping, two paths emerge:
+  - If the **SDAP header is configured**, it goes to **Adding SDAP header** and then down to the Radio Interface.
+  - If the **SDAP header is not configured**, it goes directly down to the Radio Interface.
+
+**Receiving Side (NG-RAN/UE/UEB):**
+
+- Data from the Radio Interface enters the **Receiving SDAP entity**.
+- Two paths emerge from the interface:
+  - If the **SDAP header is configured**, it goes to **Removing SDAP header** and then up to the **QoS flow** output.
+  - If the **SDAP header is not configured**, it goes to a dashed box labeled **Reflective QoS flow to DRB mapping**, then up to **Removing SDAP header**, and finally up to the **QoS flow** output.
+
+Figure 4.2.2-1: SDAP layer, functional view. The diagram shows the functional flow of data through the SDAP layer on both the transmitting (UE/NG-RAN/UEA) and receiving (NG-RAN/UE/UEB) sides, connected by a Radio Interface (Uu/PC5).
+
+**Figure 4.2.2-1: SDAP layer, functional view**
+
+Reflective QoS flow to DRB mapping is performed at UE, as specified in the clause 5.3.2, if DL SDAP header is configured.
+
+Reflective QoS flow to MRB mapping is not supported. There is no SDAP header for MRB.
+
+For NR sidelink communication, reflective PC5 QoS flow to SL-DRB mapping is not supported.
+
+## 4.3 Services
+
+### 4.3.1 Services provided to upper layers
+
+The SDAP sublayer provides its service to the user plane upper layers. The following services are provided by SDAP to upper layers:
+
+- transfer of user plane data.
+
+### 4.3.2 Services expected from lower layers
+
+An SDAP entity expects the following services from lower layers:
+
+- user plane data transfer service;
+- in-order delivery except when out of order delivery is configured by RRC (TS 38.331 [3]).
+
+## 4.4 Functions
+
+The SDAP sublayer supports the following functions:
+
+- transfer of user plane data;
+- mapping between a QoS flow and a DRB for both DL and UL;
+- mapping between an MBS QoS flow and an MRB for DL;
+- mapping between a PC5 QoS flow and a SL-DRB for NR sidelink communication;
+- marking QoS flow ID in both DL and UL packets;
+- marking PC5 QoS flow ID in unicast of NR sidelink communication packets;
+- reflective QoS flow to DRB mapping for the UL SDAP data PDUs.
+
+# --- 5 SDAP procedures
+
+## 5.1 SDAP entity handling
+
+### 5.1.1 SDAP entity establishment
+
+When RRC (TS 38.331 [3]) requests an SDAP entity establishment, the UE shall:
+
+- establish an SDAP entity;
+- follow the procedures in clause 5.2.1 and 5.2.2.
+
+When RRC (TS 38.331 [3]) requests establishment of an SDAP entity for unicast, groupcast or broadcast of NR sidelink communication, the UE shall:
+
+- establish an SDAP entity;
+- follow the procedures in clauses 5.2.3 and 5.2.4.
+
+### 5.1.2 SDAP entity release
+
+When RRC (TS 38.331 [3]) requests an SDAP entity release, the UE shall:
+
+- release the SDAP entity.
+
+When RRC (TS 38.331 [3]) requests release of an SDAP entity for unicast, groupcast or broadcast of NR sidelink communication, the UE shall:
+
+- release the SDAP entity.
+
+## 5.2 Data transfer
+
+### 5.2.1 Uplink
+
+At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity shall:
+
+- if there is no stored QoS flow to DRB mapping rule for the QoS flow as specified in the clause 5.3:
+  - map the SDAP SDU to the default DRB;
+- else:
+  - map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule;
+- if the DRB to which the SDAP SDU is mapped is configured by RRC (TS 38.331 [3]) with the presence of SDAP header,
+  - construct the UL SDAP data PDU as specified in the clause 6.2.2.3;
+- else:
+  - construct the UL SDAP data PDU as specified in the clause 6.2.2.1;
+- submit the constructed UL SDAP data PDU to the lower layers.
+
+NOTE 1: UE behaviour is not defined if there is neither a default DRB nor a stored QoS flow to DRB mapping rule for the QoS flow.
+
+NOTE 2: Default DRB is always configured with UL SDAP header (TS 38.331 [3]).
+
+### 5.2.2 Downlink
+
+At the reception of an SDAP data PDU from lower layers for a QoS flow, the receiving SDAP entity shall:
+
+- if this SDAP data PDU is received from an MRB:
+  - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.1.
+- if the DRB from which this SDAP data PDU is received is configured by RRC (TS 38.331 [3]) with the presence of SDAP header:
+  - perform reflective QoS flow to DRB mapping as specified in the clause 5.3.2;
+  - perform RQI handling as specified in the clause 5.4;
+  - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.2.
+- else:
+  - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.1;
+- deliver the retrieved SDAP SDU to the upper layer.
+
+### 5.2.3 SL transmission
+
+At the reception of an SDAP SDU from upper layer for a PC5 QoS flow, the transmitting SDAP entity shall:
+
+- if there is no stored PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow as specified in the clause 5.5:
+  - map the SDAP SDU to the default SL-DRB;
+- else:
+  - map the SDAP SDU to the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule;
+- if the SL-DRB to which the SDAP SDU is mapped is configured by RRC (TS 38.331 [3]) with the presence of SDAP header:
+  - construct the SL SDAP data PDU as specified in the clause 6.2.2.4;
+- else:
+  - construct the SL SDAP data PDU as specified in the clause 6.2.2.1;
+- submit the constructed SL SDAP data PDU to the lower layers.
+
+### 5.2.4 SL reception
+
+At the reception of an SDAP data PDU from lower layers for a PC5 QoS flow, the receiving SDAP entity shall:
+
+- if the SL-DRB from which this SDAP data PDU is received is configured by RRC (TS 38.331 [3]) with the presence of SDAP header:
+  - retrieve the SDAP SDU from the SL SDAP data PDU as specified in the clause 6.2.2.4;
+- else:
+  - retrieve the SDAP SDU from the SL SDAP data PDU as specified in the clause 6.2.2.1;
+- deliver the retrieved SDAP SDU to the upper layer.
+
+## 5.3 QoS flow to DRB mapping
+
+### 5.3.1 Configuration
+
+When RRC (TS 38.331 [3]) configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:
+
+- if the SDAP entity has already been established and there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the default DRB;
+  - submit the end-marker control PDU to the lower layers.
+- if the stored UL QoS flow to DRB mapping rule is different from the configured QoS flow to DRB mapping rule for the QoS flow and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of UL SDAP header:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;
+  - submit the end-marker control PDU to the lower layers.
+- store the configured UL QoS flow to DRB mapping rule for the QoS flow.
+
+When RRC (TS 38.331 [3]) releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:
+
+- remove the UL QoS flow to DRB mapping rule for the QoS flow.
+
+### 5.3.2 Reflective mapping
+
+For each received DL SDAP data PDU with RDI set to 1, the SDAP entity shall:
+
+- process the QFI field in the SDAP header and determine the QoS flow;
+- if there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the default DRB;
+  - submit the end-marker control PDU to the lower layers;
+- if the stored QoS flow to DRB mapping rule for the QoS flow is different from the QoS flow to DRB mapping of the DL SDAP data PDU and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of UL SDAP header:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;
+  - submit the end-marker control PDU to the lower layers;
+- store the QoS flow to DRB mapping of the DL SDAP data PDU as the QoS flow to DRB mapping rule for the UL.
+
+### 5.3.3 DRB release
+
+When RRC (TS 38.331 [3]) indicates that a DRB is released, the SDAP entity shall:
+
+- remove all QoS flow to DRB mappings associated with the released DRB based on the clauses 5.3.1 and 5.3.2.
+
+## 5.4 RQI handling
+
+For each received DL SDAP data PDU with RQI set to 1, the SDAP entity shall:
+
+- inform the NAS layer of the RQI and QFI.
+
+## 5.5 PC5 QoS flow to SL-DRB mapping
+
+### 5.5.1 Configuration
+
+When RRC (TS 38.331 [3]) configures a PC5 QoS flow to SL-DRB mapping rule for a PC5 QoS flow, the SDAP entity shall:
+
+- for unicast of NR sidelink communication, if the SDAP entity has already been established and there is no stored SL-DRB mapping rule for the PC5 QoS flow and a default SL-DRB is configured:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow;
+  - map the end-marker control PDU to the default SL-DRB;
+  - submit the end-marker control PDU to the lower layers;
+- for unicast of NR sidelink communication, if the stored PC5 QoS flow to SL-DRB mapping rule is different from the configured PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow and the SL-DRB according
+
+to the stored PC5 QoS flow to SL-DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of SL SDAP header:
+
+- construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow;
+- map the end-marker control PDU to the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule;
+- submit the end-marker control PDU to the lower layers;
+- store the configured PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow.
+
+When RRC (TS 38.331 [3]) releases a PC5 QoS flow to SL-DRB mapping rule for a PC5 QoS flow, the SDAP entity shall:
+
+- remove the PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow.
+
+### 5.5.2 SL-DRB release
+
+When RRC (TS 38.331 [3]) indicates that an SL-DRB is released, the SDAP entity shall:
+
+- remove all PC5 QoS flow to SL-DRB mappings associated with the released SL-DRB based on the clause 5.5.1.
+
+# --- 6 Protocol data units, formats, and parameters
+
+## 6.1 Protocol data units
+
+### 6.1.1 Data PDU
+
+The SDAP Data PDU is used to convey one or more of followings:
+
+- SDAP header;
+- user plane data.
+
+### 6.1.2 Control PDU
+
+#### a) End-Marker Control PDU
+
+End-Marker control PDU is used by the SDAP entity at UE to indicate that it stops the mapping of the SDAP SDU of the QoS flow indicated by the QFI/PQFI to the DRB/SL-DRB on which the End-Marker control PDU is transmitted.
+
+## 6.2 Formats
+
+### 6.2.1 General
+
+A SDAP PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. In the figures in clause 6.2, bit strings are represented by tables in which the first and most significant bit is the left most bit of the first line of the table, the last and least significant bit is the rightmost bit of the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines.
+
+SDAP SDUs are bit strings that are byte aligned (i.e. multiple of 8 bits) in length. An SDAP SDU is included into a SDAP PDU from the first bit onward.
+
+For groupcast and broadcast of NR sidelink communication, only SDAP data PDU without SDAP header is supported.
+
+### 6.2.2 Data PDU
+
+#### 6.2.2.1 Data PDU without SDAP header
+
+An SDAP PDU consists only of a data field and does not consist of any SDAP header, as described in Figure 6.2.2.1-1.
+
+![Diagram of SDAP Data PDU format without SDAP header. It shows a vertical stack of data blocks. The top block is labeled 'Data' and 'Oct 1'. Below it is an ellipsis '....'. The bottom block is labeled 'Oct N'.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg)
+
+|      |  |  |  |  |  |  |  |       |
+|------|--|--|--|--|--|--|--|-------|
+|      |  |  |  |  |  |  |  |       |
+| Data |  |  |  |  |  |  |  | Oct 1 |
+| .... |  |  |  |  |  |  |  |       |
+|      |  |  |  |  |  |  |  | Oct N |
+
+Diagram of SDAP Data PDU format without SDAP header. It shows a vertical stack of data blocks. The top block is labeled 'Data' and 'Oct 1'. Below it is an ellipsis '....'. The bottom block is labeled 'Oct N'.
+
+Figure 6.2.2.1-1: SDAP Data PDU format without SDAP header
+
+#### 6.2.2.2 DL Data PDU with SDAP header
+
+Figure 6.2.2.2 – 1 shows the format of SDAP Data PDU of DL with SDAP header being configured.
+
+![Diagram of DL SDAP Data PDU format with SDAP header. The first octet is split into RDI and RQI. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg)
+
+|      |     |     |  |  |  |  |  |       |
+|------|-----|-----|--|--|--|--|--|-------|
+|      |     |     |  |  |  |  |  |       |
+| RDI  | RQI | QFI |  |  |  |  |  | Oct 1 |
+| Data |     |     |  |  |  |  |  | Oct 2 |
+| ...  |     |     |  |  |  |  |  |       |
+| Data |     |     |  |  |  |  |  | Oct N |
+
+Diagram of DL SDAP Data PDU format with SDAP header. The first octet is split into RDI and RQI. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N.
+
+Figure 6.2.2.2-1: DL SDAP Data PDU format with SDAP header
+
+#### 6.2.2.3 UL Data PDU with SDAP header
+
+Figure 6.2.2.3 – 1 shows the format of SDAP Data PDU of UL with SDAP header being configured.
+
+![Diagram of UL SDAP Data PDU format with SDAP header. The first octet is split into D/C and R. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N.](2bc39576969969ffe6d3f3d5264bba75_img.jpg)
+
+|      |   |     |  |  |  |  |  |       |
+|------|---|-----|--|--|--|--|--|-------|
+|      |   |     |  |  |  |  |  |       |
+| D/C  | R | QFI |  |  |  |  |  | Oct 1 |
+| Data |   |     |  |  |  |  |  | Oct 2 |
+| ...  |   |     |  |  |  |  |  |       |
+| Data |   |     |  |  |  |  |  | Oct N |
+
+Diagram of UL SDAP Data PDU format with SDAP header. The first octet is split into D/C and R. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N.
+
+Figure 6.2.2.3-1: UL SDAP Data PDU format with SDAP header
+
+#### 6.2.2.4 SL Data PDU with SDAP header for unicast of NR sidelink communication
+
+Figure 6.2.2.4–1 shows the format of SDAP Data PDU for unicast of NR sidelink communication with SDAP header being configured.
+
+![Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication. The diagram shows a sequence of octets. The first octet (Oct 1) is divided into three fields: D/C (1 bit), R (1 bit), and PQFI (6 bits). Subsequent octets (Oct 2 to Oct N) contain Data. An ellipsis indicates intermediate octets.](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication. The diagram shows a sequence of octets. The first octet (Oct 1) is divided into three fields: D/C (1 bit), R (1 bit), and PQFI (6 bits). Subsequent octets (Oct 2 to Oct N) contain Data. An ellipsis indicates intermediate octets.
+
+Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication
+
+### 6.2.3 End-Marker Control PDU
+
+Figure 6.2.3-1 shows the format of End-Marker Control PDU.
+
+![Figure 6.2.3-1: End-Marker Control PDU. The diagram shows a single octet (Oct 1) divided into three fields: D/C (1 bit), R (1 bit), and QFI/PQFI (6 bits).](bffdddb47fced140f8d17fdc2a29f592_img.jpg)
+
+Figure 6.2.3-1: End-Marker Control PDU. The diagram shows a single octet (Oct 1) divided into three fields: D/C (1 bit), R (1 bit), and QFI/PQFI (6 bits).
+
+Figure 6.2.3-1: End-Marker Control PDU
+
+## 6.3 Parameters
+
+### 6.3.1 General
+
+If not otherwise mentioned in the definition of each field, then the bits in the parameters shall be interpreted as follows: the left most bit is the first and most significant bit and the right most bit is the last and least significant bit.
+
+Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU.
+
+### 6.3.2 Data
+
+Length: Variable
+
+This field includes the SDAP SDU.
+
+### 6.3.3 D/C
+
+Length: 1 bit,
+
+The D/C bit indicates whether the SDAP PDU is an SDAP Data PDU or an SDAP Control PDU.
+
+Table 6.3.3-1: D/C field
+
+| Bit | Description |
+|-----|-------------|
+| 0   | Control PDU |
+| 1   | Data PDU    |
+
+### 6.3.4 QFI
+
+Length: 6 bits
+
+The QFI field indicates the ID of the QoS flow (TS 23.501 [4]) to which the SDAP PDU belongs.
+
+### 6.3.5 R
+
+Length: 1 bit
+
+Reserved. In this version of the specification reserved bits shall be set to 0. Reserved bits shall be ignored by the receiver.
+
+### 6.3.6 RQI
+
+Length: 1 bit,
+
+The RQI bit indicates whether NAS should be informed of the updated of SDF to QoS flow mapping rules (TS 23.501 [4]).
+
+**Table 6.3.6-1: RQI field**
+
+| Bit | Description                             |
+|-----|-----------------------------------------|
+| 0   | No action                               |
+| 1   | To inform NAS that RQI bit is set to 1. |
+
+### 6.3.7 RDI
+
+Length: 1 bit,
+
+The RDI bit indicates whether QoS flow to DRB mapping rule should be updated.
+
+**Table 6.3.7-1: RDI field**
+
+| Bit | Description                            |
+|-----|----------------------------------------|
+| 0   | No action                              |
+| 1   | To store QoS flow to DRB mapping rule. |
+
+### 6.3.8 PQFI
+
+Length: 6 bits
+
+The PQFI field indicates the ID of the PC5 QoS flow (as specified in TS 24.587[6]) to which the SDAP PDU belongs.

marked/Rel-18/37_series/37460/raw.md

@@ -0,0 +1,307 @@
+
+
+# 3GPP TS 37.460 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant 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 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## --- **Keywords**
+
+radio, antenna
+
+## **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 .....                                                       | 4         |
+| 1 Scope.....                                                         | 5         |
+| 2 References.....                                                    | 5         |
+| 3 Abbreviations .....                                                | 5         |
+| 4 General aspects .....                                              | 6         |
+| 4.1 Introduction .....                                               | 6         |
+| 4.2 Iuant interface general principles .....                         | 6         |
+| 4.3 Iuant interface specification objectives .....                   | 6         |
+| 4.4 Iuant interface characteristics.....                             | 6         |
+| 5 Functions of the Iuant interface protocols.....                    | 7         |
+| 5.1 Physical layer functions .....                                   | 7         |
+| 5.2 Data link layer functions .....                                  | 7         |
+| 5.3 Application layer functions .....                                | 8         |
+| 5.3.1 Control of RET antennas .....                                  | 8         |
+| 5.3.2 Application software and configuration data download.....      | 8         |
+| 5.3.3 Alarm reporting .....                                          | 8         |
+| 5.3.4 Operator specific data storage .....                           | 8         |
+| 5.3.5 Control of Tower Mounted Amplifiers (TMAs) .....               | 8         |
+| 6 Other Iuant interface specifications .....                         | 9         |
+| 6.1 Iuant interface: Layer 1 (TS 37.461).....                        | 9         |
+| 6.2 Iuant interface: Signalling Transport (TS 37.462) .....          | 9         |
+| 6.3 Void.....                                                        | 9         |
+| 6.4 Summary of Iuant interface Technical Specifications .....        | 9         |
+| 6.5 Iuant interface: Application part specification (TS 37.466)..... | 9         |
+| <b>Annex A (informative): OSI model overview .....</b>               | <b>10</b> |
+| <b>Annex B (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 is an introduction to the 3GPP TS 37.46x series of Technical Specifications that define the Iuant Interface. The Iuant interface is applicable for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas and between the implementation specific O&M function and the TMA control unit function.
+
+# --- 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 37.461: "Iuant Interface: Layer 1".
+- [3] 3GPP TS 37.462: "Iuant Interface: Signalling Transport".
+- [4] void
+- [5] ISO/IEC 13239 (2nd Edition, March 2000): "Information Technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures".
+- [6] 3GPP TS 25.442: "UTRAN implementation-specific O&M transport".
+- [7] 3GPP TS 37.466: "Iuant interface: Application Part".
+- [8] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [8].
+
+|         |                                            |
+|---------|--------------------------------------------|
+| HDLC    | High-Level Data Link Control               |
+| IP      | Internet Protocol                          |
+| O&M     | Operations & Maintenance                   |
+| OSI     | Open Systems Interconnection               |
+| RET     | Remote Electrical Tilting                  |
+| RETAP   | Remote Electrical Tilting Application Part |
+| TMA     | Tower Mounted Amplifier                    |
+| TMAAP   | Tower Mounted Amplifier application part   |
+| UMTS    | Universal Mobile Telecommunications System |
+| E-UTRAN | Evolved UTRAN                              |
+
+# 4 General aspects
+
+## 4.1 Introduction
+
+The Iuant interface for the control of RET antennas or TMAs is a logical part of the RAN Node as shown for a Node B in figure 9 of TS 25.401 [1] for UTRAN. Therefore, no new RAN element for the RET antennas or TMAs and no new RAN element manager is needed. The existing Implementation Specific O&M transport (see TS 25.442 [6] for UMTS) is used for the connection between the RET antennas or TMAs control unit and the Node B element manager.
+
+The Iuant interface between the Implementation Specific O&M function and the RET antenna control unit function is specified in detail in the specifications for layer 1, signalling transport and RET application part (TS 37.461 [2], TS 37.462 [3], TS 37.466 [7]).
+
+## 4.2 Iuant interface general principles
+
+The Iuant interface for the RET antenna control is based on a three-layer protocol model. The three-layer model is a compact form of the OSI seven-layer reference model and includes only layers 1, 2 and 7:
+
+- The Physical Layer (Layer 1) defines the signalling levels and basic data characteristics including the data rates;
+- The Data Link Layer (Layer 2) for the Signalling Transport uses a specific class of the HDLC standard as defined in ISO/IEC 13239 [5];
+- The Application Layer (Layer 7) defines the data payload format and the required command set. This layer is called the "Iuant: Application Part".
+
+This compact model for the control interface provides an efficient protocol stack suitable for implementation on a single embedded micro-controller.
+
+## 4.3 Iuant interface specification objectives
+
+The Iuant interface specifications shall facilitate the following:
+
+- Controlling the tilting of RET antennas remotely from the O&M Network and locally from the Node B;
+- Indicating of TMA alarms and optionally controlling the gain of TMAs remotely from the O&M Network and locally from the Node B;
+- Interfacing a mix of RET antennas, TMAs and RAN Node from different vendors;
+- Providing RET or TMAs functionality accompanied by an appropriate set of signalling commands and control parameters;
+- Support of error and alarm handling.
+
+## 4.4 Iuant interface characteristics
+
+The Iuant interface has a protocol structure as shown below in figure 4.4.1.
+
+![Figure 4.4.1: Protocol structure for Iuant interface. The diagram shows two protocol stacks separated by a vertical line labeled 'Iuant'. The left stack, labeled 'RAN Node', consists of a top section 'Implementation specific O&M function', a middle section 'See Reference [6]' (blue), and a bottom section 'PHY' (yellow). The right stack consists of a top section 'RETAP TMAAP' (yellow), a middle section 'HDLC' (yellow), and a bottom section 'PHY' (yellow). The 'PHY' layers of both stacks are connected to the 'Iuant' interface.](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+Figure 4.4.1: Protocol structure for Iuant interface. The diagram shows two protocol stacks separated by a vertical line labeled 'Iuant'. The left stack, labeled 'RAN Node', consists of a top section 'Implementation specific O&M function', a middle section 'See Reference [6]' (blue), and a bottom section 'PHY' (yellow). The right stack consists of a top section 'RETAP TMAAP' (yellow), a middle section 'HDLC' (yellow), and a bottom section 'PHY' (yellow). The 'PHY' layers of both stacks are connected to the 'Iuant' interface.
+
+**Figure 4.4.1: Protocol structure for Iuant interface**
+
+As the Iuant and the Implementation Specific O&M are different interfaces with e.g. different addressing schemes a mediation function is needed. This mediation function uses on one side a protocol that uses the implementation specific O&M bearer (e.g. IP) and on the other side the Iuant protocol.
+
+# 5 Functions of the Iuant interface protocols
+
+## 5.1 Physical layer functions
+
+The physical layer provides a multi drop broadcast link between the primary device (RAN Node) and all secondary devices (RET antennas or TMAs). Any message transmitted will be received by all other devices. If two devices transmit at the same time, their messages will be garbled.
+
+The connection requires a half duplex communication, which requires an appropriate scheme for the timing and access control of the connection.
+
+## 5.2 Data link layer functions
+
+The data link layer provides:
+
+- A data packet communication format;
+- An addressing scheme;
+- A relationship whereby the primary device controls the half duplex timing;
+- A message checksum scheme to protect from transmission errors;
+- A message sequence numbering scheme which protects layer 7 from:
+
+- Duplicated messages;
+- Deleted messages;
+- Receiving messages in the wrong order.
+- A flow control mechanism protecting each device from being overrun by messages.
+
+These functions provide layer 7 with a safe full-duplex connection between the primary device and any secondary device. This full duplex connection allows both the primary and secondary device to transmit layer 7 messages to the opposite device of the connection, whenever they need to. Actual delivery time on layer 2 will depend on the layer 2 polling frequency, which is chosen by the primary device.
+
+## 5.3 Application layer functions
+
+The list of functions on the Iuant interface is the following:
+
+- Control of RET antennas;
+- Application software and configuration data download;
+- Alarm Reporting;
+- Operator specific data storage;
+- Control of Tower Mounted Amplifiers (TMAs).
+
+### 5.3.1 Control of RET antennas
+
+A RET device provides means to adjust the electrical tilt of one or multiple antennas. The set of procedures to control RET antennas provides means to control the electrical tilt of one or more RET antennas remotely. The procedures are defined in TS 37.466 [7].
+
+### 5.3.2 Application software and configuration data download
+
+The interface provides means for downloading new application software and configuration data to a secondary device.
+
+The support of application software download to a secondary device is optional. If a secondary device supports application software download, it shall reset itself and start running the new application software automatically after the completed download. Further details on the software download procedure (e.g. the different states of the secondary device and the supported elementary procedures in these states) are described in subclause 6.1 of TS 37.466 [7].
+
+### 5.3.3 Alarm reporting
+
+The secondary device reports every change in error status after subscription for alarm reporting by transmitting alarm messages to the primary device. Alarm information can also be interrogated in the application layer.
+
+### 5.3.4 Operator specific data storage
+
+The secondary device provides means for storage of operator specific data, e.g. inventory information.
+
+### 5.3.5 Control of Tower Mounted Amplifiers (TMAs)
+
+The TMA device provides means to indicate alarms and optionally to adjust the gain of TMAs. The set of procedures to control TMAs are defined in TS 37.466 [7].
+
+# 6 Other Iuant interface specifications
+
+## 6.1 Iuant interface: Layer 1 (TS 37.461)
+
+TS 37.461 [2] specifies the standards allowed for implementation of Layer 1 (physical layer) on the Iuant interface.
+
+## 6.2 Iuant interface: Signalling Transport (TS 37.462)
+
+TS 37.462 [3] specifies the signalling transport related to RETAP and TMAAP signalling to be used across the Iuant interface.
+
+## 6.3 Void
+
+## 6.4 Summary of Iuant interface Technical Specifications
+
+The relationship between the technical specifications that define the Iuant interface is shown in figure 6.4.1.
+
+![Diagram showing the relationship between technical specifications for the Iuant interface layers.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg)
+
+The diagram illustrates the relationship between technical specifications for the Iuant interface across three layers. On the left, the layers are labeled: 'Radio Network Layer', 'Transport Layer', and 'Physical Layer'. To the right of each label is a box containing the corresponding specification. The 'Radio Network Layer' box contains 'RETAP TMAAP' and 'TS 37.466'. The 'Transport Layer' box contains 'Iuant Transport' and 'TS 37.462'. The 'Physical Layer' box contains 'TS 37.461'. A dashed vertical line runs through the center of all three boxes, indicating a common interface or relationship between the specifications.
+
+Diagram showing the relationship between technical specifications for the Iuant interface layers.
+
+Figure 6.4.1: Iuant Interface Technical Specifications
+
+## 6.5 Iuant interface: Application part specification (TS 37.466)
+
+TS 37.466 [7] specifies protocols for application part to be used over the Iuant interface.
+
+# Annex A (informative): OSI model overview
+
+![Diagram of the OSI model showing three layers (7 Application, 2 Data Link, 1 Physical) for two devices. Solid arrows represent the actual message path through the physical layer, while dashed arrows represent the apparent message path between corresponding layers of the two devices.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram illustrates the OSI model layers for two communicating devices. Each device has three layers: 7 Application, 2 Data Link, and 1 Physical. Within each device, arrows show data moving down from the Application layer to the Data Link layer, and then down to the Physical layer. Conversely, arrows show data moving up from the Physical layer to the Data Link layer, and then up to the Application layer. Between the two devices, a solid horizontal arrow connects the 1 Physical layer of the first device to the 1 Physical layer of the second device, representing the actual message path. Dashed horizontal arrows connect the 7 Application layer of the first device to the 7 Application layer of the second device, and the 2 Data Link layer of the first device to the 2 Data Link layer of the second device, representing apparent message paths. A legend at the bottom indicates that a solid arrow represents the 'Actual message path' and a dashed arrow represents the 'Apparent message path'.
+
+Diagram of the OSI model showing three layers (7 Application, 2 Data Link, 1 Physical) for two devices. Solid arrows represent the actual message path through the physical layer, while dashed arrows represent the apparent message path between corresponding layers of the two devices.
+
+**Figure A.1: Relevant OSI model layers**
+
+Figure A.1 shows the relevant OSI model layers and the communication paths between the primary and secondary device.
+
+The two important aspects of the OSI model are:
+
+- It defines a layered structure for the communication software;
+- It provides each layer with an apparent direct link to the same layer at the other device.
+
+However, in real life, the only actual message path between the two devices is through the physical connection between the two layer 1 entities.
+
+The layer 2 entities appear to communicate directly. In actual fact, a message passed from the first device to the second device takes the following path:
+
+- Layer 2 at the first device passes the message down to Layer 1;
+- Layer 1 transmits the message across the physical connection (for instance a wire) to layer 1 at the second device;
+- Layer 1 at the second device passes the message up to Layer 2 at the second device.
+
+Likewise, layer 7 entities appear to communicate directly. In actual fact, a message passed from the first device to the second device takes the following path:
+
+- Layer 7 at the first device passes the message down to Layer 2;
+- Layer 2 at the first device passes the message down to Layer 1;
+- Layer 1 transmits the message across the physical connection (for instance a wire) to layer 1 at the second device;
+- Layer 1 at the second device passes the message up to Layer 2 at the second device;
+- Layer 2 at the second device passes the message up to Layer 7 at the second device.
+
+## Annex B (informative): Change History
+
+| Change history |          |           |      |     |     |                                                                     |             |
+|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                                     | New version |
+| 2019-02        | R3-103   | R3-190079 |      |     |     | Text transferred from 25.460 v15.0.0 (changes shown with rev marks) | 1.15.0      |
+| 2019-04        | RAN#83   | RP-190582 |      |     |     | Specification approved by RAN plenary                               | 15.1.0      |
+| 2019-12        | RP-86    | RP-192915 | 0001 | 5   | F   | Correction for luant                                                | 15.2.0      |
+| 2020-07        | RAN#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                      | 16.0.0      |
+| 2022-03        | RAN#95-e | RP-220238 | 0002 | 1   | D   | Inclusive language review                                           | 17.0.0      |
+| 2024-03        | RAN#103  | RP-240617 | 0004 | -   | D   | Rapporteur Editorial Review                                         | 18.0.0      |

marked/Rel-18/37_series/37461/raw.md

@@ -0,0 +1,492 @@
+
+
+# 3GPP TS 37.461 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant 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
+
+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**
+
+radio, EMC, power supply, antenna
+
+## **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 .....                                          | 4         |
+| 1 Scope.....                                            | 5         |
+| 2 References.....                                       | 5         |
+| 3 Definitions and abbreviations .....                   | 5         |
+| 3.1 Definitions.....                                    | 5         |
+| 3.2 Abbreviations .....                                 | 6         |
+| 4 Iuant layer 1 .....                                   | 6         |
+| 4.1 General .....                                       | 6         |
+| 4.2 RS485 option.....                                   | 7         |
+| 4.3 Modem option .....                                  | 7         |
+| 4.3.1 Interference with existing systems .....          | 9         |
+| 4.3.1.1 Carrier frequency and frequency stability ..... | 9         |
+| 4.3.1.2 Modem isolation and modem emissions.....        | 9         |
+| 4.3.1.3 Modem intermodulation attenuation.....          | 10        |
+| 4.3.2 Recovery time.....                                | 10        |
+| 4.3.3 Impedance.....                                    | 10        |
+| 4.3.4 Modulator characteristics .....                   | 11        |
+| 4.3.4.1 Levels.....                                     | 11        |
+| 4.3.4.2 Spectrum emission mask .....                    | 11        |
+| 4.3.5 Demodulator characteristics .....                 | 11        |
+| 4.3.6 Duty cycle variation .....                        | 11        |
+| 4.3.7 Operating bands.....                              | 12        |
+| 4.3.8 Time delay and accuracy .....                     | 12        |
+| 4.3.9 Insertion Loss .....                              | 12        |
+| 4.3.10 DC port isolation .....                          | 13        |
+| 4.3.11 RET control unit spurious emission .....         | 13        |
+| 4.3.12 Control unit spurious emission.....              | 13        |
+| 4.4 DC power supply.....                                | 14        |
+| 4.4.1 Power consumption .....                           | 14        |
+| 4.4.2 Conducted emission.....                           | 14        |
+| 4.4.3 Power-up characteristics.....                     | 14        |
+| <b>Annex A (normative): Test procedures .....</b>       | <b>16</b> |
+| <b>Annex B (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.
+
+# --- 1 Scope
+
+The present document specifies the standards allowed to implement layer 1 on the Iuant interface for UTRA, E-UTRA and NR.
+
+The specification of transmission delay requirements and O&M requirements are not in the scope of the present document.
+
+The modem option of Iuant layer 1 specification in clause 4.3 applies to UTRA, E-UTRA BS and NR BS type 1-C.
+
+# --- 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 37.462: "UTRAN Iuant interface: Signalling transport".
+- [2] ISO/IEC 8482 (1993-12): "Information technology - Telecommunications and information exchange between systems - Twisted pair multipoint interconnections".
+- [3] TIA/EIA TSB89: "Application guidelines for TIA/EIA-485-A".
+- [4] 3GPP TS 25.101: "Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD)".
+- [5] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [6] 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception (FDD)".
+- [7] 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 [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 [7].
+
+**On-Off-Keying:** A modulation system in which a carrier is switched between two states, ON and OFF.
+
+**Common feeder cable:** Feeder cable where some antenna line devices (e.g. RET, TMA) are connected via the same feeder cable.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                            |
+|------|--------------------------------------------|
+| BS   | Base Station                               |
+| DC   | Direct Current                             |
+| DL   | Downlink                                   |
+| FDD  | Frequency Division Duplex                  |
+| ISB  | Idle-State Biasing                         |
+| OOK  | On-Off-Keying                              |
+| RET  | Remote Electrical Tilting                  |
+| RF   | Radio Frequency                            |
+| TMA  | Tower Mounted Amplifier                    |
+| UE   | User Equipment                             |
+| UL   | Uplink                                     |
+| UMTS | Universal Mobile Telecommunications System |
+| UTRA | UMTS Terrestrial Radio Access              |
+
+# --- 4 Iuant layer 1
+
+## 4.1 General
+
+There are two layer 1 options:
+
+- RS485 option: A screened multicore cable, which supports a conventional RS485 serial multi-drop bus.
+- Modem option: A connection to a RET and/or a TMA control unit by way of a coaxial cable which is shared with DC supply and RF signals.
+
+Both layer 1 options support the connection of two-way serial data and DC power to the RET and/or TMA antenna device.
+
+At least one of these two layer 1 options shall be supported.
+
+The default data rate for both layer 1 options shall be 9.6 kbps. Higher data rates of 38.4 kbps for both layer 1 options and 115.2 kbps only for the RS485 layer 1 option may optionally be supported. Each unit communicates on one of the three data rates, but different units on the same interface may use different data rates.
+
+After a reset, a secondary device shall alternate between supported data rates. When alternating between data rates, the data rate shall be held constant for 300 ms. After every correctly received device scan command (see TS 37.462 [1]) independent of whether it matches or not, at one of the supported data rates, that data rate shall be held constant for 1.5 seconds. After successful reception of an address assignment frame, the secondary device shall use that data rate until it is reset.
+
+Data rates:
+
+- 9.6 kbps  $\pm$  3 %
+- 38.4 kbps  $\pm$  3 %
+- 115.2 kbps  $\pm$  3 %
+
+The format of the data octet shall be as shown in figure 4.1.1:
+
+![Figure 4.1.1: Format and order of transmitted data. The diagram shows a voltage level (Vb-Va) on the vertical axis and Time on the horizontal axis. The signal starts at an 'Idle' state (Logical 1, Carrier Off). It then transitions to a 'Startbit (0)' (Logical 0, Carrier On). This is followed by a sequence of bits, with the 'Least significant bit' at the beginning and the 'Most significant bit' at the end. The sequence ends with a 'Stop bit (1)' (Logical 1, Carrier Off), returning to the 'Idle' state.](a6a8016b231533e7f34b550f4676afc6_img.jpg)
+
+The figure illustrates the signal format for transmitted data. The vertical axis represents the voltage difference  $V_b - V_a$ , with two levels marked: 'Logical 1 Carrier Off' (higher level) and 'Logical 0 Carrier On' (lower level). The horizontal axis represents 'Time'. The signal begins at the 'Idle' state (Logical 1). It then drops to the 'Startbit (0)' (Logical 0). This is followed by a series of bits, with the 'Least significant bit' being the first bit after the start bit and the 'Most significant bit' being the last bit before the stop bit. The sequence concludes with a 'Stop bit (1)' (Logical 1), returning to the 'Idle' state.
+
+Figure 4.1.1: Format and order of transmitted data. The diagram shows a voltage level (Vb-Va) on the vertical axis and Time on the horizontal axis. The signal starts at an 'Idle' state (Logical 1, Carrier Off). It then transitions to a 'Startbit (0)' (Logical 0, Carrier On). This is followed by a sequence of bits, with the 'Least significant bit' at the beginning and the 'Most significant bit' at the end. The sequence ends with a 'Stop bit (1)' (Logical 1, Carrier Off), returning to the 'Idle' state.
+
+Figure 4.1.1: Format and order of transmitted data
+
+## 4.2 RS485 option
+
+This option is constituted by a two wire bi-directional multi-drop configuration conforming to ISO/IEC 8482 [2]. The mapping of mark/space to logical one and zero as referred to in ISO/IEC 8482 [2] shall be according to figure 4.1.1.
+
+The use of ISB, also called idle-line failsafe in TIA/EIA TSB89 [3], is mandatory. The bias voltages shall be applied only by the primary device to any separate RS485 bus. The polarity of the idle-state bias is defined as a transmitted 1.
+
+The RS485 transmitter shall be set to drive the bus before the first start bit is sent and held active until the last stop bit is sent. The RS485 transmitter shall stop driving the bus within 20 bit-times after the last stop bit is sent.
+
+If an antenna modem is used ISB shall be implemented by the antenna modem.
+
+## 4.3 Modem option
+
+The connection to a RET and/or a TMA control unit by way of a coaxial cable which is shared with DC supply and RF signals is provided by two modems, a BS modem and an antenna modem. The BS modem shall be either connected to the antenna connector of the BS or integrated in the BS. It provides signal transmission to the antenna modem and signal reception from the antenna modem over the antenna feeder cable. The antenna modem is located between the antenna feeder cable and the antenna. Modem configurations and reference points for modem characteristics are specified in figure 4.3.1 and figure 4.3.2. Unless otherwise stated, requirements in this section apply to both BS modem and antenna modem.
+
+![Diagram of modem configuration and reference points for a BS without BS modem. It shows an antenna connected to an Antenna modem, which is connected via an antenna feeder cable (labeled Iuant) to a BS modem, which is in turn connected to a BS without BS modem. Reference points 1 through 6 are marked at various interfaces.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The diagram illustrates the modem configuration and reference points for a Base Station (BS) without a BS modem. It consists of three main components connected vertically: an Antenna at the top, an Antenna modem, a BS modem, and a BS without BS modem at the bottom. The connections and reference points are as follows:
+
+- Antenna:** The top component, connected to the Antenna modem.
+- Reference point 4:** Located at the interface between the Antenna and the Antenna modem.
+- Antenna modem:** The second component from the top. It receives **Control data** and **DC power** from the left. **Reference point 5** is located on its left side.
+- Reference point 3:** Located at the interface between the Antenna modem and the Antenna feeder cable.
+- Iuant:** The label for the **Antenna feeder cable** connecting the Antenna modem and the BS modem.
+- Reference point 2:** Located at the interface between the Antenna feeder cable and the BS modem.
+- BS modem:** The third component from the top. It receives **Control data** and **DC power** from the left. **Reference point 6** is located on its left side.
+- Reference point 1 (BS antenna connector):** Located at the interface between the BS modem and the BS without BS modem.
+- BS without BS modem:** The bottom component.
+
+Diagram of modem configuration and reference points for a BS without BS modem. It shows an antenna connected to an Antenna modem, which is connected via an antenna feeder cable (labeled Iuant) to a BS modem, which is in turn connected to a BS without BS modem. Reference points 1 through 6 are marked at various interfaces.
+
+Reference point 6, DC power to the BS modem, is optional and does not exist if the BS modem has integrated power supply.
+
+Figure 4.3.1: Modem configuration and modem reference points for a BS without BS modem
+
+![Diagram of modem configuration and reference points for a BS with integrated BS modem. The diagram shows an antenna connected to an 'Antenna modem' box. The 'Antenna modem' is connected to a 'BS with integrated BS modem' box via an 'Antenna feeder cable'. Reference points are indicated: Reference point 4 is at the antenna input to the Antenna modem; Reference point 3 is at the output of the Antenna modem; Reference point 2 (BS antenna connector) is at the input of the BS with integrated BS modem; Reference point 5 is at the DC power input to the Antenna modem. Control data and DC power are shown entering the Antenna modem from the left. The Iuant is indicated on the Antenna feeder cable.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+Diagram of modem configuration and reference points for a BS with integrated BS modem. The diagram shows an antenna connected to an 'Antenna modem' box. The 'Antenna modem' is connected to a 'BS with integrated BS modem' box via an 'Antenna feeder cable'. Reference points are indicated: Reference point 4 is at the antenna input to the Antenna modem; Reference point 3 is at the output of the Antenna modem; Reference point 2 (BS antenna connector) is at the input of the BS with integrated BS modem; Reference point 5 is at the DC power input to the Antenna modem. Control data and DC power are shown entering the Antenna modem from the left. The Iuant is indicated on the Antenna feeder cable.
+
+**Figure 4.3.2: Modem configuration and modem reference points for a BS with integrated BS modem**
+
+### 4.3.1 Interference with existing systems
+
+The modem circuit shall be capable of managing its transmitting characteristic according to subclause 4.3.5.
+
+#### 4.3.1.1 Carrier frequency and frequency stability
+
+The following carrier frequency shall be used for this application:
+
+$2.176 \text{ MHz} \pm 100 \text{ ppm}$
+
+#### 4.3.1.2 Modem isolation and modem emissions
+
+The external BS modem shall provide minimum attenuation according to figure 4.3.1.2.1 between reference point 2 and reference point 1 to protect the BS from emissions of the antenna modem.
+
+External BS modem emissions at reference point 1 shall be attenuated at least according to the modem attenuation in figure 4.3.1.2.1 below the levels specified for the modem spectrum emission mask in subclause 4.3.4.2 to protect the BS from emissions of the BS modem.
+
+The antenna modem shall provide minimum attenuation according to figure 4.3.1.2.1 between reference point 3 and reference point 4 to protect other radio systems from emission of the BS modem.
+
+Antenna modem emissions at reference point 4 shall be attenuated at least according to the modem attenuation in figure 4.3.1.2.1 below the levels specified for the modem spectrum emission mask in subclause 4.3.4.2 to protect other radio systems from emission of the antenna modem.
+
+![Figure 4.3.1.2.1: Modem attenuation. A graph showing attenuation in dB versus frequency. The x-axis shows frequency points: 9 kHz, 1 MHz, 10 MHz, 20 MHz, and 30 MHz. The y-axis shows attenuation levels: 0 dB, 10 dB, 21 dB, 41 dB, and 42 dB. The curve starts at 10 dB from 9 kHz to 1 MHz, then rises steeply to 21 dB and 41 dB. It peaks at 42 dB at center frequency f0. It then descends symmetrically to 41 dB, 21 dB, and back to 10 dB at 10 MHz. It stays at 10 dB until 20 MHz, then drops to 0 dB at 30 MHz. Bandwidth markers show 400 kHz and 1 MHz centered at f0. A 200 kHz offset is indicated from f0 to the 21 dB point on the right side.](f519a5be118c846f631c992412353fb9_img.jpg)
+
+Figure 4.3.1.2.1: Modem attenuation. A graph showing attenuation in dB versus frequency. The x-axis shows frequency points: 9 kHz, 1 MHz, 10 MHz, 20 MHz, and 30 MHz. The y-axis shows attenuation levels: 0 dB, 10 dB, 21 dB, 41 dB, and 42 dB. The curve starts at 10 dB from 9 kHz to 1 MHz, then rises steeply to 21 dB and 41 dB. It peaks at 42 dB at center frequency f0. It then descends symmetrically to 41 dB, 21 dB, and back to 10 dB at 10 MHz. It stays at 10 dB until 20 MHz, then drops to 0 dB at 30 MHz. Bandwidth markers show 400 kHz and 1 MHz centered at f0. A 200 kHz offset is indicated from f0 to the 21 dB point on the right side.
+
+**Figure 4.3.1.2.1: Modem attenuation**
+
+#### 4.3.1.3 Modem intermodulation attenuation
+
+The modem intermodulation attenuation is specified in terms of the power in intermodulation products of WCDMA modulated carriers present at reference point 1 or reference point 3.
+
+For 2 downlink carriers of 43 dBm the power of third order intermodulation products in the UL operating bands for the external BS modem and antenna modem shall not exceed:
+
+- – 130 dBm/100 kHz for frequencies  $< 1$  GHz
+- – 120 dBm/1 MHz for frequencies  $\geq 1$  GHz
+
+NOTE: Using the modem with higher power than 43 dBm and or with more carriers than 2 carriers at 43dBm/carrier may increase intermodulation products and may degrade the receiver sensitivity of the BS if these intermodulation products fall at BS receive frequencies.
+
+For the worst input configuration of power and number of carriers declared by the modem manufacturer the power of any intermodulation product for the external BS modem and antenna modem shall not exceed:
+
+- – 98dBm/100kHz
+
+In addition, for the worst input configuration of power and number of carriers declared by the modem manufacturer the power of fifth or higher order intermodulation products in the UL operating bands for the external BS modem and antenna modem shall not exceed:
+
+- – 135 dBm/100 kHz for frequencies  $< 1$  GHz
+- – 125 dBm/1 MHz for frequencies  $\geq 1$  GHz
+
+### 4.3.2 Recovery time
+
+A minimum recovery time shall be allowed between receiving and transmitting messages on the bus. For this reason a minimum permitted response time is specified in subclause 4.5 in TS 37.462 [1].
+
+### 4.3.3 Impedance
+
+The modem transceiver shall provide constant impedance in both transmitting and receiving modes:
+
+- Nominal impedance  $Z_0$ : 50  $\Omega$ ;
+- Return loss at modem carrier frequency  $\pm 0.1$  MHz  $> 10$  dB;
+- Return loss in external BS and antenna modem operating bands  $> 20$  dB.
+
+### 4.3.4 Modulator characteristics
+
+#### 4.3.4.1 Levels
+
+ON-Level:  $+3 \text{ dBm} \pm 2 \text{ dB}$
+
+OFF-Level:  $\leq -40 \text{ dBm}$
+
+#### 4.3.4.2 Spectrum emission mask
+
+The modem spectrum emission mask is specified in figure 4.3.4.2.1. Intermediate values may be obtained by linear interpolation between the points shown. The corresponding measurement bandwidths are specified in table 4.3.4.2.1. For modem configurations according to figure 4.3.1 the BS modem emissions shall not exceed the limits of the spectrum emission mask at reference point 2. For modem configurations according to figure 4.3.2 the BS with integrated BS modem emissions shall not exceed the limits of the spectrum emission mask at reference point 2 only for frequencies below 20 MHz. Antenna modem emissions shall not exceed the limits of the spectrum emission mask at reference point 3.
+
+![Figure 4.3.4.2.1: Modem spectrum emission mask. The graph shows power density in dBm versus frequency. The x-axis is logarithmic, with markers at 9 kHz, 1 MHz, 10 MHz, 20 MHz, 30 MHz, 400 MHz, and 12.75 GHz. The y-axis is linear in dBm. The mask starts at -36 dBm from 9 kHz to 1 MHz. At 1 MHz, it rises to -25 dBm at 200 kHz offset from the carrier f0. At f0, it rises to +5 dBm. At 400 kHz offset from f0, it drops to -25 dBm. At 1 MHz offset from f0, it drops to -36 dBm. From 10 MHz to 30 MHz, it is -36 dBm. At 30 MHz, it drops to -67 dBm. From 400 MHz to 12.75 GHz, it is -67 dBm. A 'Note 1' is indicated for frequencies above 1 GHz.](1640ec1dfae8bdfa5af950db7623febc_img.jpg)
+
+Figure 4.3.4.2.1: Modem spectrum emission mask. The graph shows power density in dBm versus frequency. The x-axis is logarithmic, with markers at 9 kHz, 1 MHz, 10 MHz, 20 MHz, 30 MHz, 400 MHz, and 12.75 GHz. The y-axis is linear in dBm. The mask starts at -36 dBm from 9 kHz to 1 MHz. At 1 MHz, it rises to -25 dBm at 200 kHz offset from the carrier f0. At f0, it rises to +5 dBm. At 400 kHz offset from f0, it drops to -25 dBm. At 1 MHz offset from f0, it drops to -36 dBm. From 10 MHz to 30 MHz, it is -36 dBm. At 30 MHz, it drops to -67 dBm. From 400 MHz to 12.75 GHz, it is -67 dBm. A 'Note 1' is indicated for frequencies above 1 GHz.
+
+Figure 4.3.4.2.1: Modem spectrum emission mask.
+
+Note 1: For frequencies  $< 1 \text{ GHz}$  the general emission limit is  $-108 \text{ dBm}$ , except modem operating band UL frequencies where the emission limit is  $-135 \text{ dBm}$ .  
+For frequencies  $\geq 1 \text{ GHz}$  the general emission limit is  $-98 \text{ dBm}$ , except modem operating band UL frequencies where the emission limit is  $-125 \text{ dBm}$ .
+
+Table 4.3.4.2.1: Modem spectrum emission mask measurement bandwidth
+
+| Band              | Measurement Bandwidth |
+|-------------------|-----------------------|
+| 9 kHz - 150 kHz   | 1 kHz                 |
+| 150 kHz - 30 MHz  | 10 kHz                |
+| 30 MHz - 1 GHz    | 100 kHz               |
+| 1 GHz - 12.75 GHz | 1 MHz                 |
+
+### 4.3.5 Demodulator characteristics
+
+The demodulator shall fulfil the requirement in subclause 4.3.6 for a carrier ON-Level within  $+5 \text{ dBm}$  to  $-12 \text{ dBm}$  and a carrier OFF-Level less than  $-18 \text{ dBm}$ . The levels within  $-12 \text{ dBm}$  to  $-18 \text{ dBm}$  are undefined.
+
+### 4.3.6 Duty cycle variation
+
+In order to guarantee proper transmission of data bits through the processes of modulation and demodulation, the following limit shall be met for the duty cycle variation:
+
+$$\Delta DC_{\text{SYSTEM}} = |DC_{\text{RX}} - DC_{\text{TX}}| \leq 10 \%$$
+
+Where:  $\Delta DC_{SYSTEM}$  is the difference between the duty cycles of the transmitted and received bit streams,  
+ $DC_{TX}$  = Duty cycle for the input bit stream, and  
+ $DC_{RX}$  = Duty cycle for the output bit stream.
+
+![Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier. The figure shows two waveforms. The top waveform is a bit stream with '1' and '0' levels, a 50% reference line, a bit period t_BS, and a cycle period T. The bottom waveform is an OOK modulated subcarrier with a 50% reference line, an on-period t_OOK, and a cycle period T.](252ea48d02dce93965b91746fb376f35_img.jpg)
+
+The figure consists of two vertically aligned waveforms. The top waveform represents a bit stream with two bits: a '1' followed by a '0'. The '1' bit is a high-level pulse, and the '0' bit is a low-level pulse. A horizontal dashed line at the center represents the 50% duty cycle reference. The duration of one bit is labeled  $t_{BS}$ , and the duration of one full cycle (one '1' and one '0' bit) is labeled  $T$ . The bottom waveform represents an OOK modulated subcarrier. It shows two cycles of a modulated signal. Each cycle consists of a period of high-frequency oscillation (the 'on' state) followed by a period of zero amplitude (the 'off' state). A horizontal dashed line at the center represents the 50% duty cycle reference. The duration of the 'on' state is labeled  $t_{OOK}$ , and the duration of one full cycle is labeled  $T$ .
+
+Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier. The figure shows two waveforms. The top waveform is a bit stream with '1' and '0' levels, a 50% reference line, a bit period t\_BS, and a cycle period T. The bottom waveform is an OOK modulated subcarrier with a 50% reference line, an on-period t\_OOK, and a cycle period T.
+
+Duty cycle for bit stream =  $t_{BS}/T$ ; duty cycle for OOK =  $T_{OOK}/T$
+
+**Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier**
+
+For transmission through a coaxial cable, two converters are required, one from a bit stream to OOK (modulator) and one from OOK back to a bit stream (demodulator). Therefore half of the total duty cycle tolerance is available for each converter.
+
+For an input bit stream with a duty ratio of 50 %, the cascaded modulator and demodulator shall provide an output bit stream with a duty ratio within the limits 40 % - 60 %, measured in each case at 0.5 times peak amplitude (see figure 4.3.6.1).
+
+### 4.3.7 Operating bands
+
+A UTRA/FDD BS, UTRA/TDD BS, E-UTRA BS, NR BS or antenna modem is designed to operate in one or several of the operating bands defined in 3GPP TS 25.101 [4], 3GPP TS 36.101 [5] and 3GPP TS 38.101 [6].
+
+**Table 4.3.7.1: Void**
+
+The operating bands of the BS modem or antenna modem shall be declared by the manufacturer.
+
+### 4.3.8 Time delay and accuracy
+
+The time delay in the operating bands shall be declared by the manufacturer with  $\pm 1$  ns accuracy. The time delay shall not exceed 30 ns. This requirement is only applicable to external BS modem and antenna modem.
+
+### 4.3.9 Insertion Loss
+
+The insertion loss in the external BS modem or antenna modem operating band shall be  $\leq 0.3$  dB.
+
+The actual insertion loss shall be declared by the manufacturer.
+
+### 4.3.10 DC port isolation
+
+The isolation between DC port and RF ports shall meet the minimum values in figure 4.3.10.1 and 4.3.10.2. Figure 4.3.10.1 is valid for antenna modems between reference point 5 and 4 as well as 5 and 3 and for BS modems without integrated power supply between reference point 6 and 2 as well as 6 and 1. Figure 4.3.10.2 is valid as additional requirement for antenna modems between reference point 5 and 3 and for BS modems without integrated power supply between reference point 6 and 2.
+
+![Figure 4.3.10.1: DC port isolation graph showing isolation levels across a wide frequency range from 9 kHz to 3 GHz.](8b79f5ec940d107c246612c2a2ec519f_img.jpg)
+
+This graph shows the DC port isolation in dB across a frequency range from 9 kHz to 3 GHz. The isolation levels are defined in several segments:
+ 
+
+- From 9 kHz to 150 kHz: 10 dB
+- From 150 kHz to 1 MHz: 16 dB
+- From 1 MHz to 30 MHz: 16 dB (Note 3 applies here)
+- From 30 MHz to 400 MHz: 21 dB
+- From 400 MHz to 1 GHz: 38 dB (Note 1 applies here)
+- From 1 GHz to 2.57 GHz: 38 dB (Note 2 applies here)
+- From 2.57 GHz to 3 GHz: 20 dB
+
+Figure 4.3.10.1: DC port isolation graph showing isolation levels across a wide frequency range from 9 kHz to 3 GHz.
+
+Note 1: 38 dB, except for UL and DL operating bands where it is 65 dB
+
+Note 2: 38 dB, except for UL and DL operating bands where it is 65 dB
+
+Note 3: 16 dB. Between reference point 5 and 3 as well as 6 and 2 see figure 4.3.10.2.
+
+Figure 4.3.10.1: DC port isolation
+
+![Figure 4.3.10.2: DC port isolation graph showing a detailed view of the isolation around the carrier frequency f0.](3084f66c81a49b6225666f212179642c_img.jpg)
+
+This graph provides a detailed view of the DC port isolation around the carrier frequency  $f_0$ . The isolation levels are:
+ 
+
+- Outside the 1 MHz band (e.g., at 10 MHz, 20 MHz, 30 MHz): 16 dB
+- At the edges of the 1 MHz band (1 MHz and 10 MHz): 35 dB
+- At the carrier frequency  $f_0$ : 36 dB
+- At a distance of 200 kHz from  $f_0$ : 35 dB
+- At a distance of 400 kHz from  $f_0$ : 36 dB
+
+Figure 4.3.10.2: DC port isolation graph showing a detailed view of the isolation around the carrier frequency f0.
+
+Figure 4.3.10.2: DC port isolation
+
+### 4.3.11 RET control unit spurious emission
+
+Void.
+
+### 4.3.12 Control unit spurious emission
+
+The control unit, or a combination of control units, shall not generate spurious emission, at reference point 5, above a level that will violate the spectrum emission mask requirement according to chapter 4.3.4.2. The DC port isolation according to chapter 4.3.10 shall be taken into account.
+
+## 4.4 DC power supply
+
+### 4.4.1 Power consumption
+
+The DC supply requirements refers to reference points 3 and 5 in subclause 4.3.
+
+BS modem and an antenna modem shall be able to operate with a DC supply voltage range of 10 V – 30 V.
+
+Power consumption modes are specified in table 4.4.1.1. and table 4.4.1.2.
+
+**Table 4.4.1.1: Power consumption modes for RET**
+
+| RET Power mode | Maximum power consumption |
+|----------------|---------------------------|
+| High           | < 13 W                    |
+| Low            | < 2 W                     |
+
+**Table 4.4.1.2: Power consumption modes for TMA**
+
+| TMA Type       | Maximum power consumption |
+|----------------|---------------------------|
+| Single Unit    | < 7,5 W                   |
+| Multi Unit (N) | < N * 7,5 W               |
+
+BS modem and antenna modem maximum power consumption shall be < 2 W.
+
+BS modem and antenna modem shall impose a voltage drop less than 2 V between reference point 3 and 5.
+
+A Single Unit considers one RF amplifier in one TMA. A Multi Unit considers N RF amplifiers in equal or less than N TMAs.
+
+### 4.4.2 Conducted emission
+
+The levels of generated conducted noise and ripple on DC Power supply shall be within the limits given in table 4.4.2.1.
+
+**Table 4.4.2.1: Noise and ripple**
+
+| Item                   | Limit               | Frequency     | Remarks                                                   |
+|------------------------|---------------------|---------------|-----------------------------------------------------------|
+| RET power mode High    | 70 mV <sub>pp</sub> | 0.15 - 30 MHz | Only one operating unit a time                            |
+| RET power mode Low     | 20 mV <sub>pp</sub> | 0.15 - 30 MHz |                                                           |
+| TMA                    | 20 mV <sub>pp</sub> | 0.15 - 30 MHz |                                                           |
+| Antenna modem, RF port | 15 mV <sub>pp</sub> | 0.15 - 30 MHz | Generated Noise and Ripple at RF feeder (in RX mode)      |
+| Antenna modem, DC port | 20 mV <sub>pp</sub> | 0.15 - 30 MHz | Allowed Noise and Ripple at external DC port (in TX mode) |
+
+All units connected to a DC supply bus shall exhibit full performance up to the limit of 112 mV<sub>pp</sub> total noise and ripple within 0.15 - 30 MHz.
+
+### 4.4.3 Power-up characteristics
+
+A BS modem, antenna modem or RET/TMA control units shall have a power-up period of 3 s.
+
+During the power-up period a BS modem, antenna modem or a RET control unit shall exhibit the circuit equivalent of a DC power consumer with a current consumption of maximum 400 mA in parallel with a capacitor of maximum 0.5 µF.
+
+During the power-up period the TMA control unit shall exhibit the circuit equivalent of a DC power consumer with a current consumption of maximum 1A in parallel with a capacitor of maximum 0.5 µF.
+
+After the power-up period, the unit shall be fully functional and the power consumption requirement as described in subclause 4.4.1 applies.
+
+# --- Annex A (normative): Test procedures
+
+## Test pattern
+
+Spectrum mask and emission requirement shall be tested both with a consecutive series of "0" and an alternating sequence of "0" and "1".
+
+## Emission requirement below noise floor
+
+As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy and sensitivity when measuring close to or below the noise floor, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth.
+
+## Conversion between modulated and CW for IM measurement
+
+The requirement for IM3 below 1 GHz shall be relaxed 15 dB and tested with CW interferers at the specified levels.  
+The requirement for IM3 above 1 GHz shall be relaxed 5 dB and tested with CW interferers at the specified levels.
+
+The requirement for IM5 or higher below 1 GHz shall be relaxed 10 dB and tested with CW interferers at the specified levels.
+
+The requirement for IM5 or higher above 1 GHz shall be relaxed 0 dB and tested with CW interferers at the specified levels.
+
+Example: A –130 dBm/100 kHz requirement below 1 GHz with two WCDMA-modulated carriers at 43 dBm is converted to a –115 dBm requirement with two CW carriers at 43 dBm.

marked/Rel-18/37_series/37462/raw.md

@@ -0,0 +1,714 @@
+
+
+# 3GPP TS 37.462 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant 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 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+radio, antenna
+
+### **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 .....                                                         | 4         |
+| 1 Scope.....                                                           | 5         |
+| 2 References.....                                                      | 5         |
+| 3 Definitions and abbreviations .....                                  | 5         |
+| 3.1 Definitions.....                                                   | 5         |
+| 3.2 Abbreviations .....                                                | 6         |
+| 4 Iuant data link layer.....                                           | 6         |
+| 4.1 Invalid receptions .....                                           | 6         |
+| 4.2 Frame lengths .....                                                | 6         |
+| 4.3 Default address.....                                               | 7         |
+| 4.4 Window size.....                                                   | 7         |
+| 4.5 Message timing .....                                               | 7         |
+| 4.6 State model.....                                                   | 7         |
+| 4.7 Device types .....                                                 | 7         |
+| 4.8 XID negotiation.....                                               | 8         |
+| 4.8.1 HDLC parameters.....                                             | 8         |
+| 4.8.2 Protocol version.....                                            | 8         |
+| 4.8.3 Address assignment.....                                          | 8         |
+| 4.8.4 Device scan.....                                                 | 9         |
+| 4.8.5 Reset device.....                                                | 9         |
+| 4.9 Link establishment .....                                           | 10        |
+| 4.10 Link timeout .....                                                | 10        |
+| <b>Annex A (informative): HDLC description .....</b>                   | <b>11</b> |
+| A.1 Basic structure .....                                              | 11        |
+| A.2 UNC commands.....                                                  | 12        |
+| A.2.1 Set Normal Response Mode (SNRM) .....                            | 12        |
+| A.2.2 Disconnect (DISC) .....                                          | 12        |
+| A.2.3 Unnumbered Acknowledge (UA).....                                 | 12        |
+| A.2.4 Disconnected Mode (DM).....                                      | 12        |
+| A.2.5 Receiver Ready (RR).....                                         | 12        |
+| A.2.6 Receiver Not Ready (RNR).....                                    | 12        |
+| A.2.7 Information (I) .....                                            | 12        |
+| A.2.8 Frame Reject (FRMR).....                                         | 12        |
+| A.3 Option 1.....                                                      | 13        |
+| A.4 Option 4.....                                                      | 13        |
+| A.5 Option 15.1 .....                                                  | 13        |
+| A.6 Link safety.....                                                   | 13        |
+| A.7 Full duplex link .....                                             | 13        |
+| <b>Annex B (informative): HDLC parameter negotiation .....</b>         | <b>15</b> |
+| <b>Annex C (informative): HDLC parameter negotiation example .....</b> | <b>16</b> |
+| <b>Annex D (informative): Address assignment example.....</b>          | <b>17</b> |
+| D.1 Address assignment command .....                                   | 17        |
+| D.2 Address assignment response .....                                  | 17        |
+| <b>Annex E (informative): Device scan example.....</b>                 | <b>18</b> |
+| <b>Annex F (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 specifies the signalling transport related to RETAP and TMAAP signalling to be used across the Iuant interface for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas and between the implementation specific O&M function and the TMA control unit function.
+
+# --- 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] ISO/IEC 13239 (3rd Edition, 2002-07): "Information Technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures".
+- [3] 3GPP TS 37.461: "Iuant Interface: Layer 1".
+- [4] Antenna Interface Standards Group: "Control Interface for Antenna Line Devices", Standard No. AISG v2.0.
+- [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 3GPP 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 3GPP TR 21.905 [5].
+
+**ASCII character:** A character forming part of the International Reference Version of the 7-bit character set defined in ISO/IEC 646:1991 represented as one octet.
+
+**Octet:** 8 bits as used in ISO/IEC 13239 [2].
+
+**Device type:** One octet identifying the type of a device.
+
+**Unique ID:** A concatenation of the vendor code (2 octets) and a 1 to 17 octets long unit specific code (e.g. serial number) exclusive for each secondary device from the vendor to whom the vendor code is assigned. The vendor code is placed in the left-most (most significant) position of the unique ID. The vendor to whom the vendor code is assigned is responsible for ensuring the uniqueness of the unique ID for each device.
+
+**Vendor code:** A unique ASCII 2-character code assigned to each vendor in AISG v2.0 [4].
+
+**Reset:** A process by which the device is put in the state it reaches after a completed power-up.
+
+**SecondaryPayloadTransmitLength:** The maximum length of the INFO field of an HDLC I-frame in the direction secondary device to primary device.
+
+**SecondaryPayloadReceiveLength:** The maximum length of the INFO field of an HDLC I-frame in the direction primary device to secondary device.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [5].
+
+|       |                                                 |
+|-------|-------------------------------------------------|
+| ADDR  | Address                                         |
+| ACK   | Acknowledgment                                  |
+| CRC   | Cyclic Redundancy Check                         |
+| DISC  | Disconnect (frame type)                         |
+| DM    | Disconnected Mode (frame type)                  |
+| FCS   | Frame Checking Sequence                         |
+| FI    | Format Identifier                               |
+| FRMR  | Frame Reject (frame type)                       |
+| GI    | Group Identifier                                |
+| GL    | Group Length                                    |
+| HDLC  | High-Level Data Link Control                    |
+| I     | Information (frame type)                        |
+| ID    | Identifier                                      |
+| INFO  | Information (field name)                        |
+| NAK   | Non Acknowledgment                              |
+| NRM   | Normal Response Mode                            |
+| P/F   | Poll/Final                                      |
+| PI    | Parameter Identifier                            |
+| PL    | Parameter Length                                |
+| PV    | Parameter Value                                 |
+| RET   | Remote Electrical Tilting                       |
+| RETAP | Remote Electrical Tilting Application Part      |
+| RNR   | Receive Not Ready (frame type)                  |
+| RR    | Receive Ready (frame type)                      |
+| SNRM  | Set Normal Response Mode (frame type)           |
+| TMA   | Tower Mounted Amplifier                         |
+| TMAAP | Tower Mounted Amplifier Application Part        |
+| TWA   | Two Way Alternate                               |
+| UA    | Unnumbered Acknowledgement (frame type)         |
+| UNC   | Unbalanced Operation Normal Response Mode Class |
+| XID   | Exchange ID (frame type)                        |
+
+# 4 Iuant data link layer
+
+The Data Link Layer uses HDLC Class UNC1,15.1 TWA (see 6.10 in ISO/IEC 13239 [2]) according to ISO/IEC 13239 [2].
+
+## 4.1 Invalid receptions
+
+Frames shall be discarded if a framing error or data overrun occurs.
+
+## 4.2 Frame lengths
+
+HDLC frame lengths may vary between 4 and N octets.
+
+All secondary devices shall support an N of 78 octets. A secondary device may, after XID negotiation, support a larger N.
+
+## 4.3 Default address
+
+After reset, a secondary device shall use the no-device address (0x00). While it has the no-device address, it may only respond to device scan and address assignment messages, but any broadcast messages shall be evaluated without response.
+
+## 4.4 Window size
+
+All devices shall support a window size of 1. A device may, after XID negotiation, support any window size up to 7.
+
+## 4.5 Message timing
+
+A minimum of 3 ms shall elapse between receiving and transmitting messages.
+
+A secondary device shall, after reception of a command with the P/F bit set, start transmitting a response within 10 ms from the time the final flag octet of that command frame was received.
+
+The transmission of the response shall be finalised within the time  $t = n \cdot 10 \cdot 10^{-4} / \text{datarate}$  where n is the number of octets in the response frame including all HDLC framing overhead. The maximum gap time between two consecutive octets shall not exceed the time  $t = 3 \cdot 10^{-4} / \text{datarate}$ . This corresponds to a 25% utilisation of the Data Link Layer.
+
+The data rate is specified in TS 37.461 [3].
+
+## 4.6 State model
+
+The connection state model for the layer 2 of the secondary device is shown in figure 4.1. The events written in *italic* are procedures from higher levels e.g. link establishment. The HDLC frames that correspond to the events are written in bold as **command / response** messages.
+
+![Figure 4.6.1: Connection state model diagram showing three states: NoAddress, AddressAssigned, and Connected. Transitions are triggered by events (italic) and HDLC frames (bold).](06da11ab76cacc38bbcd714e437797ea_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> NoAddress : Reset (reset, power on, watchdog etc.)
+    NoAddress --> AddressAssigned : Address Configuration
+    AddressAssigned --> NoAddress : XID/XID
+    NoAddress --> Connected : DISC/UA
+    Connected --> NoAddress : Link Disconnection
+    Connected --> AddressAssigned : SNRM/UA, Link Establishment
+  
+```
+
+The diagram illustrates the connection state model for a secondary device. It consists of three states: **NoAddress**, **AddressAssigned**, and **Connected**. Transitions between states are triggered by specific events (shown in *italic*) and HDLC frames (shown in **bold**).
+
+- NoAddress** to **AddressAssigned**: Triggered by *Address Configuration* (event) and **XID/XID** (HDLC frame).
+- AddressAssigned** to **NoAddress**: Triggered by **XID/XID** (HDLC frame).
+- NoAddress** to **Connected**: Triggered by **DISC/UA** (HDLC frame).
+- Connected** to **NoAddress**: Triggered by *Link Disconnection* (event) and **DISC/UA** (HDLC frame).
+- Connected** to **AddressAssigned**: Triggered by **SNRM/UA** (HDLC frame) and *Link Establishment* (event).
+- Initial state: **NoAddress** is reached upon **Reset (reset, power on, watchdog etc.)** (event).
+
+Figure 4.6.1: Connection state model diagram showing three states: NoAddress, AddressAssigned, and Connected. Transitions are triggered by events (italic) and HDLC frames (bold).
+
+Figure 4.6.1: Connection state model
+
+## 4.7 Device types
+
+Three device types are defined and identified by the assigned 1-octet unsigned integer code.
+
+**Table 4.7.1: Device types and codes**
+
+| <b>Device Type</b>            | <b>1-octet unsigned integer code</b> |
+|-------------------------------|--------------------------------------|
+| Single-Antenna RET Device     | 0x01                                 |
+| Multi-Antenna RET Device      | 0x11                                 |
+| Tower mounted amplifier (TMA) | 0x02                                 |
+
+## 4.8 XID negotiation
+
+XID negotiation shall use the standard format (see 5.5.3.1-5.5.3.2.3.2 in ISO/IEC 13239 [2]). See Annex B for a brief description of XID negotiation and Annex C to E for examples of XID negotiations. All GL fields have a size of 1 octet.
+
+Any parameter combination of 4.8.1 (HDLC parameter), 4.8.2 (Protocol Version) and 4.8.3 (Address assignment) in an XID command shall be supported by all secondary devices.
+
+### 4.8.1 HDLC parameters
+
+Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0x80. All secondary devices shall support the following parameters:
+
+**Table 4.8.1.1: HDLC parameters for secondary devices**
+
+| <b>PI</b> | <b>PL</b> | <b>Description of PV</b>                           |
+|-----------|-----------|----------------------------------------------------|
+| 5         | 4         | Maximum information field length – transmit (bits) |
+| 6         | 4         | Maximum information field length – receive (bits)  |
+| 7         | 1         | Window size – transmit (frames)                    |
+| 8         | 1         | Window size – receive (frames)                     |
+
+The SecondaryPayloadTransmitLength shall be 74 octets by default. It can be increased via XID negotiation, but shall always be 74 octets or larger.
+
+The SecondaryPayloadReceiveLength shall be 74 octets by default. It can be increased via XID negotiation, but shall always be 74 octets or larger.
+
+### 4.8.2 Protocol version
+
+Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0xF0. All secondary devices shall support the following parameter:
+
+**Table 4.8.2.1: HDLC parameter for protocol version**
+
+| <b>PI</b> | <b>PL</b> | <b>Description of PV</b> |
+|-----------|-----------|--------------------------|
+| 5         | 1         | 3GPP Release ID          |
+
+### 4.8.3 Address assignment
+
+The primary device broadcasts the XID commands. The secondary device(s) which match shall respond. The primary shall ensure that only one secondary matches the supplied parameter(s). See below for details.
+
+Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0xF0. All secondary devices shall support the following parameters:
+
+**Table 4.8.3.1: HDLC parameters for address assignment and device scan**
+
+| PI | PL      | Description of PV                                 |
+|----|---------|---------------------------------------------------|
+| 1  | 0 to 19 | Unique ID                                         |
+| 2  | 1       | HDLC Address                                      |
+| 3  | 0 to 19 | Bit Mask (for Unique ID), indicates a device scan |
+| 4  | 1       | Device Type (see table 4.7.1)                     |
+| 6  | 2       | Vendor Code as given in AISG v2.0 [4]             |
+
+The XID message can be used to assign HDLC addresses or to scan for devices.
+
+An address assignment XID command shall contain at least PI=2 (HDLC Address) and shall not contain PI=3 (Bit Mask). During an address assignment all secondary devices first assume a match and then carry out the following steps:
+
+- If PI=1 (Unique ID) is supplied, the right-most PL octets of the secondary devices Unique ID are compared to the Unique ID in the XID command. If they are different, the secondary device does not match, and the message is ignored. If the Unique ID in the XID command is longer than the secondary devices Unique ID, the secondary device does not match, and the message is ignored.
+- If PI=4 (Device Type) is supplied, the device type of the secondary device is compared to the device type in the XID command. If they are different, the secondary device does not match, and the message is ignored.
+- If PI=6 (Vendor Code) is supplied, the vendor code of the secondary device is compared to the vendor code in the XID command. If they are different, the secondary device does not match, and the message is ignored.
+
+If the secondary device still matches after these steps, the secondary device sets its HDLC address to the address specified in PI=2 and responds with an XID response which contains PI=1 and PI=4.
+
+NOTE: Unlike the normal XID negotiation, in this XID negotiation, the XID response message returns a different set of parameters than the XID command message.
+
+### 4.8.4 Device scan
+
+The device scan messages may be utilised by the primary to identify all secondary stations in the NoAddress state on an interface .
+
+A device scan XID command shall only contain PI=1 (Unique ID) and PI=3 (Bit Mask), see table 4.8.3.1. PI=1 and PI=3 shall be of equal length PL octets.
+
+If in the NoAddress state, the secondary device masks the  $\min(PL,2)$  left-most octets of its own unique ID with the  $\min(PL,2)$  left-most octets of the bit mask in the XID command and compares the result with the  $\min(PL,2)$  left-most octets the unique ID supplied in the XID command. If they match, the secondary device masks the  $\max(0,PL-2)$  right-most octets of its own unique ID with the  $\max(0,PL-2)$  right-most octets of the bit mask in the XID command and compares the result with the  $\max(0,PL-2)$  right-most octets of the unique ID supplied in the XID command. If they also match, the secondary device transmits an XID response message with its own identification data in the fields PI=1 (complete unique ID), PI=4 (device type) and PI=6 (vendor code).
+
+For the device scan comparison, the unique ID of the secondary device shall be padded with NUL characters (character code 0x00) between the second and third left-most positions to a length of 19 octets.
+
+The scan command with zero length (PL=0) of the Unique ID (PI=1) and the Bit Mask (PI=3) shall match all secondary devices in the NoAddress state.
+
+Only matching secondary devices in the NoAddress state shall respond to the device scan messages.
+
+### 4.8.5 Reset device
+
+Format identifier (FI) shall be 0x81 and group identifier (GI) shall be 0xF0. All secondary devices shall support the following parameter:
+
+**Table 4.8.5.1: HDLC parameters for reset of secondary devices**
+
+| PI | PL | Description of PV |
+|----|----|-------------------|
+| 7  | 0  | Reset device      |
+
+If the XID command reset device is received as a broadcast (0xFF) by the secondary device, the secondary device shall reset without responding, otherwise the addressed secondary device shall reset after responding.
+
+The reset device parameter shall not be combined with other parameters in an XID command.
+
+NOTE: There is no PV in the XID command Reset device.
+
+## 4.9 Link establishment
+
+Once the secondary device has been assigned an HDLC address, the primary device initiates the link establishment by sending the SNRM command frame. The secondary device responds with an UA frame and enters the state *Connected*.
+
+## 4.10 Link timeout
+
+Whenever a secondary device receives an HDLC frame addressed to itself, i.e. not an all-device address (0xFF), it shall restart a 3 minute timer. If this 3 minute timer expires, the secondary device shall be reset.
+
+# Annex A (informative): HDLC description
+
+HDLC is defined in ISO/IEC 13239 [2]. This description only covers the aspects of HDLC which are used by this TS.
+
+The HDLC definition “UNC1,15.1, TWA” can be broken down to:
+
+- UNC;
+  - The “U” means Unbalanced operation;
+  - The “N” means Normal response mode (sequence numbers used in data frames);
+  - The “C” means Class.
+- Options supported;
+  - “1” means use of XID negotiation;
+  - “15.1” means use of start/stop transmission with basic transparency;
+  - Two Way Alternate (TWA) is the HDLC term for half duplex.
+
+## A.1 Basic structure
+
+In unbalanced operation, there is one primary station which controls the bus and a number of secondary stations which only are allowed to transmit when the primary station gives them permission to do so.
+
+All messages are transmitted as frames with the layout shown in table A.1.1:
+
+**Table A.1.1: Format of an HDLC frame**
+
+| Flag<br>1 octet | ADDR<br>1 octet           | Control<br>1 octet | INFO<br>N octets | FCS<br>2 octets | Flag<br>1 octet |
+|-----------------|---------------------------|--------------------|------------------|-----------------|-----------------|
+| 0x7E            | Secondary Station Address | Control bits       | Variable length  | CRC             | 0x7E            |
+
+HDLC frames begin and end with a Flag (0x7E) (see A.5 for details).
+
+The transmitting station calculates a Frame Check Sequence (CRC16) on all octets which follow the starting flag but not including the FCS octets. The checksum is transmitted as FCS in little endian order and is followed by the closing flag.
+
+The receiving station calculates the checksum on all octets between the flags. When it finds the closing flag, it compares the checksum to 0xF0B8. If it is a match, the HDLC frame is processed.
+
+The address field contains the HDLC address of the secondary station. If the primary station sends the message, it is called a command and the address field contains the address of the secondary station as destination. If the secondary station sends the message, it is called a response and the address field contains the address of the secondary station as source. Secondary stations cannot communicate directly to each other.
+
+The control field defines one of three frame types:
+
+- I frames contain data as well as a send and receive counter;
+- S frames contain a receive counter;
+- U frames contain unnumbered commands.
+
+The INFO field is only present in I frames and XID frames. The INFO field in an I frame contains the layer 7 payload.
+
+## A.2 UNC commands
+
+According to 6.6.2.1 in ISO/IEC 13239 [2] the following commands in shall be supported in UNC mode:
+
+**Table A.2.1: Commands supported in UNC mode**
+
+| Commands<br>(Primary Station) | Responses<br>(Secondary Station) |
+|-------------------------------|----------------------------------|
+| Frame type I                  | Frame type I                     |
+| Frame type RR                 | Frame type RR                    |
+| Frame type RNR                | Frame type RNR                   |
+| Frame type SNRM               | Frame type UA                    |
+| Frame type DISC               | Frame type DM                    |
+|                               | Frame type FRMR                  |
+
+### A.2.1 Set Normal Response Mode (SNRM)
+
+This command is used to set the secondary station in connected mode and reset its sequence number variables.
+
+### A.2.2 Disconnect (DISC)
+
+This command is used to terminate the connection.
+
+### A.2.3 Unnumbered Acknowledge (UA)
+
+This response is used to confirm that the secondary station received and acted on an SNRM or DISC command.
+
+### A.2.4 Disconnected Mode (DM)
+
+This response is used to inform the primary station that the secondary station is disconnected.
+
+### A.2.5 Receiver Ready (RR)
+
+This command and response is used to inform the opposite station (primary or secondary) that the transmitting station has empty buffers, i.e. is ready to receive an I frame. This aspect is used for flow control.
+
+It also contains the sequence number of the next frame the transmitting station expects to see. This works both as an ACK and a NAK depending on the value.
+
+### A.2.6 Receiver Not Ready (RNR)
+
+Just like RR, except it informs the opposite station that the transmitting station does not have empty buffers, i.e. that it is not ready to receive an I frame. This aspect is used for flow control.
+
+### A.2.7 Information (I)
+
+This command and response is used to transfer a block of data together with its sequence number. The command also includes the sequence number of the next frame the transmitting station expects to see. This way, it works as an RR. Like RR, it enables transmission of I frames from the opposite side.
+
+### A.2.8 Frame Reject (FRMR)
+
+This response is used to indicate an error condition. The two most likely error conditions are:
+
+- Invalid command;
+- Sequence number problem.
+
+The latter is used when the primary station has requested retransmission of a sequence number which it has already acknowledged.
+
+## A.3 Option 1
+
+Option 1 means the addition of the XID command/response, which is used for parameter negotiation.
+
+## A.4 Option 4
+
+Option 4 means the addition of the UI command/response, which is used to transfer information without changing the sequence numbers used by I frames.
+
+## A.5 Option 15.1
+
+Option 15.1 means that the serial link is not synchronous and start/stop flags are used (asynchronous serial link). The flags are coded as 0x7E and basic transparency is used.
+
+This means that all octets between the flags are part of the frame and shall not be transmitted as 0x7E. Since the frame may contain 0x7E, basic transparency is used, which means that 0x7E is transmitted as 0x7D 0x5E and 0x7D is transmitted as 0x7D 0x5D. The receiving station converts back on reception.
+
+All checksum calculations are done on unconverted data.
+
+## A.6 Link safety
+
+HDLC provides the upper layer with a safe link between two stations.
+
+Unless excessive frame lengths are used, the CRC16 checksum provides excellent protection against transmission errors. At worst,  $10^{-5}$  of the bit errors will not be detected. The likelihood of an undetected error in a frame can be calculated by multiplying  $10^{-5}$  with the Bit Error Rate (at least  $10^{-9}$  for a reasonable link) and the frame length.
+
+The sequence numbers provide protection against:
+
+- Message duplication;
+- Message deletion;
+- Message re-ordering.
+
+Without sequence numbers, the protection is only given by a checksum and some sort of ACK.
+
+If the original message is lost, there will be no ACK and a timeout will cause retransmission which solves the problem.
+
+If the original message is not lost, but the ACK is lost, the same timeout will cause a retransmission.
+
+With sequence numbers, the message is retransmitted, but the receiving station sees that the sequence number is the same, i.e. that the message is a retransmission, and throws it away without processing it further. It does send an ACK which informs the transmitting station that the message got through.
+
+## A.7 Full duplex link
+
+The upper layer sees the HDLC link as a full duplex link, although the actual transmissions on layer 1 are half duplex. The reason for this is that the upper layer is not aware of any restrictions on transmissions or receptions between layer 2 and layer 1 or between the stations.
+
+Whenever the upper layer wants to transmit, it places a message on the queue to layer 2. The message will not be transmitted until the primary station does a poll.
+
+NOTE: This applies to both the primary and the secondary station.
+
+The same applies to reception. The upper layer will either be told by layer 2 when a message has arrived, or it will periodically check to see if a message has arrived at layer 2. Neither of these two methods will in any way influence the reception of a message. That only depends on when the primary does a poll.
+
+NOTE This still applies to both the primary and the secondary station.
+
+A poll is a command frame from the primary station where the P/F (Poll/Final) bit in the control field is set to 1. This informs the secondary that it is allowed to transmit response frames.
+
+U frames set the P/F bit, which means that they are polls. However, since the U frames used in UNC 1,4 require a specific U frame response, they are not used for I frame transmission, which is what the upper layer messages depend upon.
+
+An I, RR or RNR frame type with the P/F bit set constitutes a poll as used above. An RNR frame prevents transmission of I frames, so it does not really apply.
+
+NOTE: Whenever an I or RR poll occurs, the secondary station may transmit whatever I frame it wishes (as long as the window size is not exceeded, i.e. previous messages have been acknowledged). This means that the secondary station does not have to transmit a reply to a layer 7 instruction. It is free to transmit an alarm instruction, if an alarm has occurred. It is also free to transmit any valid reply to an earlier layer 7 instruction, if it has received (acknowledged) more than one.
+
+# Annex B (informative): HDLC parameter negotiation
+
+See also sections 5.5.3.1 – 5.5.3.2.3.2 in ISO/IEC 13239 [2].
+
+**Table B.1: Format of XID parameters**
+
+|           |           |           |           |           |           |           |           |           |
+|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|
+| <b>FI</b> | <b>GI</b> | <b>GL</b> | <b>PI</b> | <b>PL</b> | <b>PV</b> | <b>PI</b> | <b>PL</b> | <b>PV</b> |
+|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|
+
+XID parameter negotiation uses a specific format (see table C.1) to transfer parameters.
+
+The parameters are identified by a one octet Format Identifier (FI) code and a one octet Group Identifier (GI) code. The Group Length (GL) is a one octet unsigned integer giving the length in octets of the parameters following it.
+
+The parameters are a sequence of PI/PL/PV values. The Parameter Identifier (PI) is a one octet code identifying the parameter. Parameter Length (PL) is a one octet unsigned integer giving the length in octets of the Parameter Value. The parameter order is not defined.
+
+The HDLC parameter negotiation is initiated by the primary station. The primary station transmits an XID frame with the values it suggests. The secondary station can either accept these or lower them. Regardless, it responds with an XID frame with the appropriate values.
+
+Generally this means that the primary station initially uses whatever its maximum limit is for each parameter. If the secondary can accept this, it responds with the same values. If it cannot support that, it lowers the values.
+
+Maximum information field length is a good example. If the primary station suggests using an information field length of 28000 bits (3500 octets), the secondary station can respond with 28000 bits, if it can use that much or even more, or respond with a lower number of e.g. 592 bits (74 octets) if that is its maximum supported information field length.
+
+The same applies to the Release ID. If a release 7 primary station attempts to communicate with a release 6 secondary station, the initial message will suggest release 7 and the response will be release 6.
+
+On the other hand, if a release 6 primary station attempts to communicate with a release 7 secondary station, the initial message will suggest release 6 and the response will release 6.
+
+Regardless, the primary station will have the final decision, since it can refuse to communicate with a station that does not support whatever parameter values it suggests. It can always repeat the XID negotiation with a new value.
+
+# Annex C (informative): HDLC parameter negotiation example
+
+XID Frame from primary station:
+
+**Table C.1: XID frame from primary station**
+
+| Field | Content | Description                                  |
+|-------|---------|----------------------------------------------|
+| ADDR  | 12      | Station address                              |
+| CTRL  | XID     | Command                                      |
+| FI    | 0x81    | Format identifier                            |
+| GI    | 0x80    | HDLC Parameter set                           |
+| GL    | 18      | Length of the parameter field (PI) in octets |
+| PI    | 5       | Maximum I Field length Transmit              |
+| PL    | 4       | Length of the PV field in octets             |
+| PV    | 341040  | Maximum I Field length Transmit in bits      |
+| PI    | 6       | Maximum I Field length Receive               |
+| PL    | 4       | Length of the PV field in octets             |
+| PV    | 224000  | Maximum I Field length Receive in bits       |
+| PI    | 7       | Maximum window size Transmit                 |
+| PL    | 1       | Length of the PV field in octets             |
+| PV    | 7       | Maximum window size Transmit                 |
+| PI    | 8       | Maximum window size Receive                  |
+| PL    | 1       | Length of the PV field in octets             |
+| PV    | 3       | Maximum window size Receive                  |
+
+Response from secondary station:
+
+**Table C.2: XID frame from secondary station**
+
+| Field | Content | Description                             |
+|-------|---------|-----------------------------------------|
+| ADDR  | 12      | Station address                         |
+| CTRL  | XID     | Command                                 |
+| FI    | 0x81    | Format identifier                       |
+| GI    | 0x80    | HDLC Parameters set                     |
+| GL    | 16      | Length of the parameter field in octets |
+| PI    | 5       | Maximum I field length Transmit         |
+| PL    | 2       | Length of the PV field (octets)         |
+| PV    | 3200    | Maximum I field length Transmit in bits |
+| PI    | 6       | Maximum I field length Receive          |
+| PL    | 4       | Length of the PV field (octets)         |
+| PV    | 341040  | Maximum I field length Receive in bits  |
+| PI    | 7       | Maximum window size Transmit            |
+| PL    | 1       | Length of the PV field (octets)         |
+| PV    | 3       | Maximum window size Transmit            |
+| PI    | 8       | Maximum window size Receive             |
+| PL    | 1       | Length of the PV field (octets)         |
+| PV    | 1       | Maximum window size Receive             |
+
+# Annex D (informative): Address assignment example
+
+## D.1 Address assignment command
+
+**Table D.1: Format of the XID frame originated by the primary station**
+
+| Field | Content                               | Description                                                                                           |
+|-------|---------------------------------------|-------------------------------------------------------------------------------------------------------|
+| ADDR  | 0xFF                                  | All-station address (Broadcast)                                                                       |
+| CTRL  | 0xBF                                  | XID command                                                                                           |
+| FI    | 0x81                                  | Format identifier                                                                                     |
+| GI    | 0xF0                                  | User defined parameter set                                                                            |
+| GL    | 0x10                                  | Length of the parameter field (rest of the message) in octets                                         |
+| PI    | 0x01                                  | Unique ID                                                                                             |
+| PL    | 0x07                                  | Length of PV field in octets                                                                          |
+| PV    | 0x58 0x59 0x7B 0x20<br>0x41 0x42 0x43 | Unique ID of the secondary station                                                                    |
+| PI    | 0x02                                  | HDLC address                                                                                          |
+| PL    | 0x01                                  | Length of PV field in octets                                                                          |
+| PV    | 0x17                                  | Assigned HDLC address                                                                                 |
+| PI    | 0x06                                  | Vendor code as given in AISG v2.0 [4]                                                                 |
+| PL    | 0x02                                  | Length of PV field in octets                                                                          |
+| PV    | 0x58 0x59                             | Unique assigned vendor code as given in AISG v2.0 [4] (virtual vendor code "XY" used in this example) |
+
+## D.2 Address assignment response
+
+**Table D.2: Format of Address Assignment Response by the secondary station**
+
+| Field | Content                                  | Description                                                |
+|-------|------------------------------------------|------------------------------------------------------------|
+| ADDR  | 0x17                                     | HDLC address of the station                                |
+| CTRL  | 0xBF                                     | XID command                                                |
+| FI    | 0x81                                     | Format identifier                                          |
+| GI    | 0xF0                                     | User defined parameter set                                 |
+| GL    | 0x0C                                     | Length of parameter field (rest of the message) in octets. |
+| PI    | 0x01                                     | Unique ID                                                  |
+| PL    | 0x07                                     | Length of PV field in octets                               |
+| PV    | 0x58 0x59 0x7B<br>0x20 0x41 0x42<br>0x43 | Unique ID of the secondary station                         |
+| PI    | 0x04                                     | Device type                                                |
+| PL    | 0x01                                     | Length of PV field in octets                               |
+| PV    | 0x01                                     | Device type as defined in table 4.7.1                      |
+
+NOTE: In this address assignment example messages the virtual vendor code "XY", the unique ID 0x58 0x59 0x7B 0x20 0x41 0x42 0x43, the HDLC address 0x17 and the device type 0x01 for a single-antenna device are used.
+
+# Annex E (informative): Device scan example
+
+In some situations it may be found that the Unique ID of a bus device is unknown or has been inaccurately recorded. This HDLC command exchange is used by the primary station to perform a binary tree scan of the bus, in order to identify all connected and disconnected devices.
+
+**Table E.1: Primary device scan command (XID Frame)**
+
+| Field | Content        | Description                                                                                                 |
+|-------|----------------|-------------------------------------------------------------------------------------------------------------|
+| ADDR  | 0xFF           | All-station address (Broadcast)                                                                             |
+| CTRL  | 0xBF           | XID command                                                                                                 |
+| FI    | 0x81           | Format identifier                                                                                           |
+| GI    | 0xF0           | User defined parameter set                                                                                  |
+| GL    | 0x0A           | Length in octets for the rest of the message                                                                |
+| PI    | 0x01           | Unique ID                                                                                                   |
+| PL    | 0x03           | Length of PV field in octets                                                                                |
+| PV    | 0x58 0x11 0x15 | Unique ID supplied by the primary station for masked comparison with the unique ID of the secondary station |
+| PI    | 0x03           | Bit mask                                                                                                    |
+| PL    | 0x03           | Length of PV field in octets (same as for PI=1)                                                             |
+| PV    | 0xFF 0x17 0xFF | Bit mask to be applied                                                                                      |
+
+NOTE: The parameters may occur in any order in the XID command.
+
+## Device Scan Response
+
+When each secondary station in the NoAddress state receives the command it masks its Unique ID with the bit mask and compares the result with the Unique ID supplied as described in clause 4.8.4. If they match, the secondary station responds using XID format frame according to table 8 of section 5.5 of ISO/IEC 13239 [2].
+
+**Table E.2: Secondary device scan response (XID Frame) in case of a match**
+
+| Field | Content                          | Description                                                                                              |
+|-------|----------------------------------|----------------------------------------------------------------------------------------------------------|
+| ADDR  | 0x00                             | No station address                                                                                       |
+| CTRL  | 0xBF                             | XID command                                                                                              |
+| FI    | 0x81                             | Format identifier                                                                                        |
+| GI    | 0xF0                             | User defined parameter set                                                                               |
+| GL    | 0x0F                             | Length in octets for the rest of the message                                                             |
+| PI    | 0x01                             | Unique ID                                                                                                |
+| PL    | 0x06                             | Length of PV field in octets                                                                             |
+| PV    | 0x58 0x59 0x07 0x5B<br>0xCD 0x15 | Unique ID of the secondary station                                                                       |
+| PI    | 0x06                             | Vendor code                                                                                              |
+| PL    | 0x02                             | Length of PV field in octets                                                                             |
+| PV    | 0x58 0x59                        | Unique assigned vendor code as given in AISG v2.0 [4] (virtual vendor code "XY" is used in this example) |
+| PI    | 0x04                             | Device type                                                                                              |
+| PL    | 0x01                             | Length of PV field in octets                                                                             |
+| PV    | 0x01                             | Single-antenna RET device type as defined in table 4.7.1                                                 |
+
+NOTE1: In this device scan example, the virtual vendor code "XY", the unique ID "0x58 0x59 0x07 0x5B 0xCD 0x15", and the device type 0x01 for a single-antenna RET device are used.
+
+NOTE2: The parameters may occur in any order in the response.
+
+It is recommended that the response of individual devices is subject to a random delay (within the permitted response time) to aid collision detection at the primary station.
+
+If there is no response, the primary station knows that no secondary station had those bits in its Unique ID or that the secondary stations having those bits in their unique ID already have assigned addresses, so the tree scan can be truncated at that branch.
+
+If multiple secondary stations respond, the responses might garble each other, unless one secondary station is close enough to overpower the signal from the other(s).
+
+If any response arrives, a single frame, multiple frames or frames with incorrect checksums or framing errors, the branch of the tree is inhabited.
+
+# Annex F (informative): Change History
+
+| Change history |          |           |      |     |     |                                                                     |             |
+|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                                     | New version |
+| 2019-02        | R3-103   | R3-190095 |      |     |     | Text transferred from 25.462 v15.0.0 (changes shown with rev marks) | 1.15.0      |
+| 2019-04        | RAN#83   | RP-190598 |      |     |     | Specification approved by RAN plenary                               | 15.1.0      |
+| 2019-12        | RP-86    | RP-192915 | 0001 | 6   | F   | Correction for luant                                                | 15.2.0      |
+| 2020-07        | RAN#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                      | 16.0.0      |
+| 2022-03        | RAN#95-e | RP-220238 | 0002 | 1   | D   | Inclusive language review                                           | 17.0.0      |
+| 2024-03        | RAN#103  | RP-240617 | 0004 | -   | D   | Rapporteur Editorial Review                                         | 18.0.0      |

marked/Rel-18/37_series/37470/raw.md

@@ -0,0 +1,461 @@
+
+
+# 3GPP TS 37.470 V18.0.0(2024-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 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 .....                                                               | 4         |
+| 1 Scope.....                                                                 | 6         |
+| 2 References.....                                                            | 6         |
+| 3 Definitions of terms, symbols and abbreviations.....                       | 6         |
+| 3.1 Terms.....                                                               | 6         |
+| 3.2 Symbols.....                                                             | 6         |
+| 3.3 Abbreviations .....                                                      | 7         |
+| 4 General aspects .....                                                      | 7         |
+| 4.0 General .....                                                            | 7         |
+| 4.1 W1 interface general principles.....                                     | 7         |
+| 4.2 W1 interface specification objectives .....                              | 8         |
+| 4.3 W1 interface capabilities.....                                           | 8         |
+| 4.4 W1 interface characteristics .....                                       | 8         |
+| 5 Functions of the W1 interface.....                                         | 8         |
+| 5.1 General .....                                                            | 8         |
+| 5.2 W1-C functions .....                                                     | 8         |
+| 5.2.1 Interface management function .....                                    | 8         |
+| 5.2.2 System Information management function .....                           | 9         |
+| 5.2.3 Paging function.....                                                   | 9         |
+| 5.2.4 UE context management function .....                                   | 9         |
+| 5.2.5 RRC message transfer function .....                                    | 10        |
+| 5.2.6 Warning messages information transfer function.....                    | 10        |
+| 5.3 W1-U functions .....                                                     | 10        |
+| 5.3.1 Transfer of user data.....                                             | 10        |
+| 5.3.2 Flow control function .....                                            | 10        |
+| 6 Procedures of the W1 interface.....                                        | 10        |
+| 6.1 Control plane procedures .....                                           | 10        |
+| 6.1.1 Interface Management procedures.....                                   | 10        |
+| 6.1.2 Context Management procedures.....                                     | 10        |
+| 6.1.3 RRC Message Transfer procedures .....                                  | 11        |
+| 6.1.3A Void .....                                                            | 11        |
+| 6.1.4 Warning Message Transmission procedures .....                          | 11        |
+| 6.1.5 Paging procedures .....                                                | 11        |
+| 6.2 User plane procedures .....                                              | 11        |
+| 6.2.1 User Data Transfer .....                                               | 11        |
+| 6.2.2 Flow Control.....                                                      | 11        |
+| 7 W1 interface protocol structure.....                                       | 12        |
+| 7.1 W1 Control Plane Protocol (W1-C).....                                    | 12        |
+| 7.2 W1 User Plane Protocol (W1-U) .....                                      | 12        |
+| 8 Other W1 interface specifications.....                                     | 12        |
+| 8.0 General .....                                                            | 12        |
+| 8.1 E-UTRAN and NG-RAN; W1 interface: layer 1 (3GPP TS 37.471) .....         | 13        |
+| 8.2 E-UTRAN and NG-RAN; W1 signalling transport (3GPP TS 37.472) .....       | 13        |
+| 8.3 E-UTRAN and NG-RAN; W1 application protocol (WIAP) (3GPP TS 37.473)..... | 13        |
+| 8.4 NG-RAN; NR user plane protocol (3GPP TS 38.425) .....                    | 13        |
+| <b>Annex A (informative): Change history.....</b>                            | <b>14</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document is an introduction to the 3GPP TS 37.4xx series of technical specifications that define the W1 interface. The W1 interface provides means for interconnecting an ng-eNB-CU and an ng-eNB-DU of an ng-eNB within an NG-RAN.
+
+# --- 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 38.425: "NR user plane protocol".
+- [3] 3GPP TS 38.300: "NR; Overall description; Stage-2"
+- [4] 3GPP TS 37.471: "E-UTRAN and NG-RAN; W1 interface: layer 1".
+- [5] 3GPP TS 37.472: "E-UTRAN and NG-RAN; W1 signalling transport".
+- [6] 3GPP TS 37.473: "E-UTRAN and NG-RAN; W1 application protocol (WIAP)".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
+
+**W1:** interface between an ng-eNB-CU and an ng-eNB-DU, providing an interconnection point between the ng-eNB-CU and the ng-eNB-DU.
+
+**W1-C:** Reference point for the control plane protocol between ng-eNB-CU and ng-eNB-DU.
+
+**ng-eNB-CU:** a logical node hosting RRC, SDAP and PDCP protocols of the ng-eNB that controls the operation of one or more ng-eNB-DUs. The ng-eNB-CU terminates the W1 interface connected with the ng-eNB-DU.
+
+**ng-eNB-DU:** a logical node hosting RLC, MAC and PHY layers of the ng-eNB, and its operation is partly controlled by ng-eNB-CU. One ng-eNB-DU supports one or multiple cells. One cell is supported by only one ng-eNB-DU. The ng-eNB-DU terminates the W1 interface connected with the ng-eNB-CU.
+
+**ng-eNB:** as defined in TS 38.300 [3].
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
+
+|        |                                      |
+|--------|--------------------------------------|
+| DRB    | Data Radio Bearers                   |
+| W1-U   | W1 User plane interface              |
+| W1-C   | W1 Control plane interface           |
+| W1AP   | W1 Application Protocol              |
+| GTP-U  | GPRS Tunnelling Protocol             |
+| IP     | Internet Protocol                    |
+| NR-MIB | NR-Master Information Block          |
+| O&M    | Operation and Maintenance            |
+| PA     | Paging Area                          |
+| PF     | Paging Frame                         |
+| PO     | Paging Occasion                      |
+| QoS    | Quality of Service                   |
+| RRC    | Radio Resource Control               |
+| SCTP   | Stream Control Transmission Protocol |
+| SRB    | Signalling Radio Bearers             |
+| SIB1   | System Information Block 1           |
+| TNL    | Transport Network Layer              |
+
+# --- 4 General aspects
+
+## 4.0 General
+
+This clause captures the W1 interface principles and characteristics.
+
+## 4.1 W1 interface general principles
+
+The general principles for the specification of the W1 interface are as follows:
+
+- An ng-eNB may consist of an ng-eNB-CU and ng-eNB-DUs. An ng-eNB-CU and an ng-eNB-DU is connected via W1 logical interface.
+- One ng-eNB-CU controls one or more ng-eNB-DUs.
+- One ng-eNB-DU supports one or multiple cells. One cell is supported by only one ng-eNB-DU.
+- ng-eNB-DU ID is used to identify ng-eNB-DU only over W1AP procedures, ng-eNB-DU ID is not connected to cell identifier.
+- The ng-eNB-CU terminates W1 interface connected with the ng-eNB-DU.
+- The ng-eNB-DU terminates W1 interface connected with the ng-eNB-CU.
+- The W1 interface shall separate Radio Network Layer and Transport Network Layer.
+- The W1 interface shall enable exchange of UE associated information and non-UE associated information.
+- The W1 interface is open;
+- From a logical standpoint, the W1 is a point-to-point interface between an ng-eNB-CU and an ng-eNB-DU.
+
+NOTE: A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints.
+
+- The W1 interface supports control plane and user plane separation;
+- The W1 interface enables exchange of UE associated information and non-UE associated information;
+- The standard should not prevent to separated CP and UP.
+
+## 4.2 W1 interface specification objectives
+
+The W1 interface specifications facilitate the following:
+
+- inter-connection of an ng-eNB-CU and an ng-eNB-DU supplied by different manufacturers.
+
+## 4.3 W1 interface capabilities
+
+The W1 interface supports:
+
+- procedures to establish, maintain and release radio bearers for the NG-RAN part of PDU sessions and for E-UTRAN Radio Access Bearers;
+- the separation of each UE on the protocol level for user specific signalling management;
+- the transfer of RRC signalling messages between the UE and the ng-eNB-CU.
+
+## 4.4 W1 interface characteristics
+
+# --- 5 Functions of the W1 interface
+
+## 5.1 General
+
+The following clauses describe the functions supported over W1-C and W1-U.
+
+## 5.2 W1-C functions
+
+### 5.2.1 Interface management function
+
+The W1 setup function allows to exchange application level data needed for the ng-eNB-DU and ng-eNB-CU to interoperate correctly on the W1 interface. The W1 setup is initiated by the ng-eNB-DU.
+
+The ng-eNB-CU Configuration Update and ng-eNB-DU Configuration Update functions allow to update application level configuration data needed between ng-eNB-CU and ng-eNB-DU to interoperate correctly over the W1 interface, and may activate or deactivate cells.
+
+For NG-RAN, the W1 setup and ng-eNB-DU Configuration Update functions allow to inform the S-NSSAI(s) supported by the ng-eNB-DU.
+
+The error indication function is used by the ng-eNB-DU or ng-eNB-CU to indicate to the ng-eNB-CU or ng-eNB-DU that an error has occurred.
+
+The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the ng-eNB-DU and the ng-eNB-CU.
+
+The W1 resource coordination function is used to transfer information about frequency resource sharing between ng-eNB-CU and ng-eNB-DU.
+
+The ng-eNB-DU status indication function allows the ng-eNB-DU to indicate overload status to ng-eNB-CU.
+
+### 5.2.2 System Information management function
+
+Scheduling of system broadcast information is carried out in the ng-eNB-DU. The ng-eNB-DU is responsible for transmitting the system information according to the scheduling parameters available.
+
+The ng-eNB-DU is responsible for the encoding of ng-eNB-MIB. In case broadcast of SIB1 and other SI messages is needed, the ng-eNB-DU is responsible for assembling SIB1, SIB2, SIB3, SIB8 and SIB16 and the ng-eNB-CU is responsible for assembling other SIBs.
+
+### 5.2.3 Paging function
+
+The ng-eNB-DU is responsible for transmitting the paging information.
+
+The ng-eNB-CU provides paging information to enable the ng-eNB-DU to calculate the exact PO and PF. The ng-eNB-CU determines the PA. The ng-eNB-DU consolidates all the paging records for a particular PO, PF and PA, and encodes the final RRC message and broadcasts the paging message on the respective PO, PF in the PA.
+
+### 5.2.4 UE context management function
+
+The W1 UE context management function supports the establishment and modification of the necessary overall UE context.
+
+The establishment of the W1 UE context is initiated by the ng-eNB-CU and accepted or rejected by the ng-eNB-DU based on admission control criteria (e.g., resource not available).
+
+The modification of the W1 UE context can be initiated by either ng-eNB-CU or ng-eNB-DU. The receiving node can accept or reject the modification. The W1 UE context management function also supports the release of the context previously established in the ng-eNB-DU. The release of the context is triggered by the ng-eNB-CU either directly or following a request received from the ng-eNB-DU. The ng-eNB-CU requests the ng-eNB-DU to remove the UE Context when the UE enters RRC\_IDLE or RRC\_INACTIVE.
+
+This function can be also used to manage DRBs and SRBs, i.e., establishing, modifying and releasing DRB and SRB resources. The establishment and modification of DRB resources are triggered by the ng-eNB-CU and accepted/rejected by the ng-eNB-DU based on resource reservation information and QoS information to be provided to the ng-eNB-DU. For each DRB to be setup or modified, the S-NSSAI may be provided by ng-eNB-CU to the ng-eNB-DU in the UE Context Setup procedure and the UE Context Modification procedure.
+
+For NG-RAN, the mapping between QoS flows and radio bearers is performed by ng-eNB-CU and the granularity of bearer related management over W1 is radio bearer level, and the ng-eNB-CU decides an aggregated DRB QoS profile for each radio bearer based on received QoS flow profile, and provides both aggregated DRB QoS profile and QoS flow profile to the ng-eNB-DU, and the ng-eNB-DU either accepts the request or rejects it with appropriate cause value.
+
+With this function, ng-eNB-DU could also notify ng-eNB-CU whether the QoS for already established DRBs is not fulfilled any longer or it is fulfilled again.
+
+The UE Inactivity Notification function is initiated by the ng-eNB-DU to indicate the UE activity event.
+
+The Notify function is to enable the ng-eNB-DU to inform the ng-eNB-CU that the QoS of an already established GBR DRB cannot be fulfilled any longer or that it can be fulfilled again.
+
+With this function, the ng-eNB-CU indicates the UL UE AMBR limit to the ng-eNB-DU, and the ng-eNB-DU enforces the indicated limit.
+
+With this function, the ng-eNB-CU indicates the UL UE AMBR limit to the ng-eNB-DU, and the ng-eNB-DU enforces the indicated limit.
+
+With this function, ng-eNB-CU requests the ng-eNB-DU to setup or change of the SpCell for the UE, and the ng-eNB-DU either accepts or rejects the request with appropriate cause value.
+
+With this function, the ng-eNB-CU requests the setup of the SCell(s) at the ng-eNB-DU side, and the ng-eNB-DU accepts all, some or none of the SCell(s) and replies to the ng-eNB-CU. The ng-eNB-CU requests the removal of the SCell(s) for the UE.
+
+With this function, the ng-eNB-DU indicates that a bearer, or a UE is inactive or active. The ng-eNB-CU consolidates all the serving ng-eNB-DUs for the UE and takes further action.
+
+### 5.2.5 RRC message transfer function
+
+This function allows to transfer RRC messages between ng-eNB-CU and ng-eNB-DU. RRC messages are transferred over W1-C. The ng-eNB-CU is responsible for the encoding of the dedicated RRC message with assistance information provided by ng-eNB-DU. This function also allows ng-eNB-DU to report to ng-eNB-CU if the downlink RRC message has been successfully delivered to UE or not.
+
+### 5.2.6 Warning messages information transfer function
+
+This function allows to cooperate with the warning message transmission procedures over NG interface. The ng-eNB-CU is responsible for encoding the warning related SI message and sending it together with other warning related information for the ng-eNB-DU to broadcast over the radio interface.
+
+## 5.3 W1-U functions
+
+### 5.3.1 Transfer of user data
+
+This function allows to transfer of user data between ng-eNB-CU and ng-eNB-DU.
+
+### 5.3.2 Flow control function
+
+This function allows to control the downlink user data flow to the ng-eNB-DU. The detailed protocol is specified in TS 38.425 [2]
+
+# --- 6 Procedures of the W1 interface
+
+## 6.1 Control plane procedures
+
+### 6.1.1 Interface Management procedures
+
+The W1 Interface management procedures are listed below:
+
+- Reset procedure
+- Error Indication procedure
+- W1 Setup procedure
+- ng-eNB-DU Configuration Update procedure
+- ng-eNB-CU Configuration Update procedure
+- ng-eNB-DU Resource Coordination procedure
+- ng-eNB-DU Status Indication procedure
+
+### 6.1.2 Context Management procedures
+
+The W1 Context management procedures are listed below:
+
+- UE Context Setup procedure
+- UE context Release Request (ng-eNB-DU initiated) procedure
+
+- UE context Release (ng-eNB-CU initiated) procedure
+- UE Context Modification (ng-eNB-CU initiated) procedure
+- UE Context Modification Required (ng-eNB-DU initiated) procedure
+- UE Inactivity Notification procedure
+- Notify procedure
+
+### 6.1.3 RRC Message Transfer procedures
+
+The W1 RRC message transfer procedures are listed below:
+
+- Initial UL RRC Message Transfer procedure
+- UL RRC Message Transfer procedure
+- DL RRC Message Transfer procedure
+- RRC Delivery Report procedure
+
+### 6.1.3A Void
+
+### 6.1.4 Warning Message Transmission procedures
+
+The W1 Warning message transmission procedures are listed below:
+
+- Write-Replace Warning procedure
+- PWS Cancel procedure
+- PWS Restart Indication procedure
+- PWS Failure Indication procedure
+
+### 6.1.5 Paging procedures
+
+The W1 Paging procedures are listed below:
+
+- Paging
+
+## 6.2 User plane procedures
+
+### 6.2.1 User Data Transfer
+
+Void
+
+### 6.2.2 Flow Control
+
+Void
+
+# 7 W1 interface protocol structure
+
+## 7.1 W1 Control Plane Protocol (W1-C)
+
+Figure 7.1-1 shows the protocol structure for W1-C. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as WIAP (W1 Application Protocol).
+
+![Figure 7.1-1: Interface protocol structure for W1-C](08441fa90c5fd11994626f662ac13f19_img.jpg)
+
+The diagram illustrates the protocol stack for the W1 Control Plane (W1-C). At the top, the 'Control Plane' label is centered. Below it, the 'Radio Network Layer' is indicated on the left, containing a box labeled 'WIAP'. A horizontal line with an oval in the center separates the Radio Network Layer from the 'Transport Network Layer' below. The Transport Network Layer contains four stacked boxes: 'SCTP', 'IP', 'Data link layer', and 'Physical layer'.
+
+Figure 7.1-1: Interface protocol structure for W1-C
+
+Figure 7.1-1: Interface protocol structure for W1-C
+
+## 7.2 W1 User Plane Protocol (W1-U)
+
+Figure 7.2-1 shows the protocol structure for W1-U. The TNL is based on IP transport, comprising the UDP and GTP-U on top of IP.
+
+![Figure 7.2-1: Interface protocol structure for W1-U](af6be343f0c0a8f155f965dcf337b8af_img.jpg)
+
+The diagram illustrates the protocol stack for the W1 User Plane (W1-U). At the top, the 'User Plane' label is centered. Below it, the 'Radio Network Layer' is indicated on the left, containing an empty box. A horizontal line with an oval in the center separates the Radio Network Layer from the 'Transport Network Layer' below. The Transport Network Layer contains four stacked boxes: 'GTP-U', 'UDP', 'IP', and 'Data link layer'. The 'Physical layer' is shown as a separate box at the bottom of the stack.
+
+Figure 7.2-1: Interface protocol structure for W1-U
+
+Figure 7.2-1: Interface protocol structure for W1-U
+
+# 8 Other W1 interface specifications
+
+## 8.0 General
+
+This clause contains the description of the other related 3GPP specifications.
+
+## 8.1 E-UTRAN and NG-RAN; W1 interface: layer 1 (3GPP TS 37.471)
+
+3GPP TS 37.471 [4] specifies the physical layer technologies that may be used to support the W1 interface.
+
+## 8.2 E-UTRAN and NG-RAN; W1 signalling transport (3GPP TS 37.472)
+
+3GPP TS 37.472 [5] specifies the signalling bearers for the W1AP for the W1-C interface.
+
+## 8.3 E-UTRAN and NG-RAN; W1 application protocol (W1AP) (3GPP TS 37.473)
+
+3GPP TS 37.473 [6] specifies the FIAP protocol for radio network control plane signalling over the W1 interface.
+
+## 8.4 NG-RAN; NR user plane protocol (3GPP TS 38.425)
+
+3GPP TS 38.425 [2] specifies the user plane protocol being used over the W1-U interface.

marked/Rel-18/37_series/37471/raw.md

@@ -0,0 +1,168 @@
+
+
+# 3GPP TS 37.471 V18.0.0(2024-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 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.....                                           | 6        |
+| 2 References.....                                      | 6        |
+| 3 Definitions of terms, symbols and abbreviations..... | 6        |
+| 3.1 Terms.....                                         | 6        |
+| 3.2 Symbols.....                                       | 6        |
+| 3.3 Abbreviations .....                                | 6        |
+| 4 Introduction.....                                    | 6        |
+| <b>Annex A (informative): Change history.....</b>      | <b>7</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the standards allowed to implement Layer 1 on the W1 interface. The W1 interface provides means for interconnecting an ng-eNB-CU and an ng-eNB-DU of an ng-eNB within NG-RAN.
+
+The specification of transmission delay requirements and O&M requirements are 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 TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+
+[3] 3GPP TS 38.411: "NG-RAN; NG layer 1".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP 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 3GPP TR 21.905 [1].
+
+ng-eNB: as defined in 3GPP TS 38.300 [2].
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1], in TS 38.411 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+# --- 4 Introduction
+
+The W1 Layer 1 shall comply with the requirements of clauses 4 through 6 in 3GPP TS 38.411 [3].

marked/Rel-18/37_series/37472/raw.md

@@ -0,0 +1,251 @@
+
+
+# 3GPP TS 37.472 V18.0.0(2024-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 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
+
+|                                                        |          |
+|--------------------------------------------------------|----------|
+| Foreword .....                                         | 4        |
+| 1 Scope.....                                           | 6        |
+| 2 References.....                                      | 6        |
+| 3 Definitions of terms, symbols and abbreviations..... | 6        |
+| 3.1 Terms.....                                         | 6        |
+| 3.2 Symbols.....                                       | 6        |
+| 3.3 Abbreviations .....                                | 7        |
+| 4. W1-C signalling bearer .....                        | 7        |
+| 4.1 Function and protocol stack .....                  | 7        |
+| 5 Data link layer.....                                 | 7        |
+| 6 IP layer.....                                        | 7        |
+| 7 Transport layer .....                                | 8        |
+| <b>Annex A (informative): Change History.....</b>      | <b>9</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the standards for Signalling Transport to be used across the W1 interface. The W1 interface provides means for interconnecting a ng-eNB-CU and a ng-eNB-DU of a ng-eNB within a NG-RAN. The present document describes how the W1AP signalling messages are transported over W1.
+
+# --- 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] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification".
+- [3] IETF RFC 791 (1981-09): "Internet Protocol".
+- [4] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [5] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol".
+- [6] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
+
+**ng-eNB:** as defined in 3GPP TS 38.300 [6]
+
+**SCTP association:** as defined in IETF RFC 4960 (2007-09) [5]
+
+**SCTP endpoint:** as defined in IETF RFC 4960 (2007-09) [5]
+
+**W1:** interface between a ng-eNB-CU and a ng-eNB-DU, providing an interconnection point between the ng-eNB-CU and the ng-eNB-DU.
+
+**W1-C:** Reference point for the control plane protocol between ng-eNB-CU and ng-eNB-DU.
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
+
+|          |                                      |
+|----------|--------------------------------------|
+| DiffServ | Differentiated Service               |
+| IANA     | Internet Assigned Number Authority   |
+| IP       | Internet Protocol                    |
+| PPP      | Point to Point Protocol              |
+| SCTP     | Stream Control Transmission Protocol |
+
+# 4. W1-C signalling bearer
+
+## 4.1 Function and protocol stack
+
+The W1-C signalling bearer provides the following functions:
+
+- Provision of reliable transfer of W1AP messages over the W1-C interface.
+- Provision of networking and routing function.
+- Provision of redundancy in the signalling network.
+- Support for flow control and congestion control.
+
+The protocol stack for W1-C Signalling Bearer is shown in figure 4.1-1 and details on each protocol are described in the following clauses.
+
+![Figure 4.1-1: W1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the W1AP protocol. Below W1AP is a horizontal line with an oval in the center, representing an interface. Below the interface is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer stacked vertically.](c9d8a18a6137ad054b841d7a614afb48_img.jpg)
+
+The diagram illustrates the protocol stack for the W1-C signalling bearer. It is divided into two main layers: the Radio Network Layer and the Transport Network Layer. The Radio Network Layer contains the W1AP protocol. Below the Radio Network Layer is an interface, represented by a horizontal line with an oval in the center. The Transport Network Layer consists of four stacked protocols: SCTP, IP, Data link layer, and Physical layer.
+
+Figure 4.1-1: W1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the W1AP protocol. Below W1AP is a horizontal line with an oval in the center, representing an interface. Below the interface is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer stacked vertically.
+
+**Figure 4.1-1: W1-C signalling bearer protocol stack**
+
+The Transport Network Layer is based on IP transport, comprising SCTP on top of IP.
+
+# --- 5 Data link layer
+
+The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented.
+
+# --- 6 IP layer
+
+The ng-eNB-CU and ng-eNB-DU shall support IPv6 (IETF RFC 8200 [2]) and/or IPv4 (IETF RFC 791 [3]).
+
+The IP layer of W1-C only supports point-to-point transmission for delivering W1AP message.
+
+The ng-eNB-CU and ng-eNB-DU shall support the Diffserv Code Point marking as described in IETF RFC 2474 [4].
+
+# 7 Transport layer
+
+SCTP (IETF RFC 4960 [5]) shall be supported as the transport layer of W1-C signalling bearer. The Payload Protocol Identifier assigned by IANA to be used by SCTP for the application layer protocol W1AP is 73.
+
+SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network.
+
+The ng-eNB-DU and ng-eNB-CU shall support a configuration with a single SCTP association per ng-eNB-DU/ng-eNB-CU pair.
+
+The ng-eNB-DU shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for W1AP is 37472.
+
+Within the set of SCTP associations established between one ng-eNB-CU and ng-eNB-DU pair, a single SCTP association shall be employed for W1AP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness.
+
+Between one ng-eNB-CU and ng-eNB-DU pair:
+
+- A single pair of stream identifiers shall be reserved over an SCTP association for the sole use of W1AP elementary procedures that utilize non UE-associated signalling.
+- At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of W1AP elementary procedures that utilize UE-associated signalling. However, a few pairs (i.e. more than one) should be reserved.
+- For a single UE-associated signalling, the ng-eNB-DU shall use one SCTP association and one SCTP stream, and the association/stream should not be changed during the communication of the UE-associated signalling unless TNL binding update is performed.
+
+Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from a ng-eNB-CU or ng-eNB-DU, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960[5] in sub clause 5.2.
+
+The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages.
+
+# Annex A (informative): Change History
+
+| Change history |               |           |      |     |     |                                                                           |             |
+|----------------|---------------|-----------|------|-----|-----|---------------------------------------------------------------------------|-------------|
+| Date           | Meeting       | TDoc      | CR   | Rev | Cat | Subject/Comment                                                           | New version |
+| 2018-05        | RAN3#100      | R3-183554 |      |     |     | BL TS submission for approval.                                            |             |
+| 2019-08        | RAN3#105      | R3-194678 |      |     |     | Add the description of procedure for the W1 signalling transport protocol | 0.1.0       |
+| 2019-10        | RAN3#105 -Bis | R3-196134 |      |     |     | Add the description of References, Definitions and abbreviations.         | 0.1.0       |
+| 2019-11        | RAN3#106 -Bis | R3-197634 |      |     |     | Change the version number to 0.2.0.                                       | 0.2.0       |
+| 2019-12        | RP-86         | RP-192954 |      |     |     | TS submitted to TSG RAN plenary for approval                              | 1.3.0       |
+| 2019-12        | RP-86         |           |      |     |     | TS approved by TSG RAN plenary                                            | 16.0.0      |
+| 2020-07        | RP-88-e       | RP-201236 | 0002 | -   | F   | SCTP Payload Protocol Identifier for W1AP                                 | 16.1.0      |
+| 2020-09        | RP-89-e       | RP-201948 | 0003 | -   | F   | SCTP port number allocatd by IANA                                         | 16.2.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/37_series/37480/raw.md

@@ -0,0 +1,431 @@
+
+
+# 3GPP TS 37.480 V18.0.0 (2023-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 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 capital 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 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo.
+
+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.
+
+© 2023, 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         |
+| 4 General aspects .....                                      | 6         |
+| 4.1 E1 interface general principles.....                     | 6         |
+| 4.2 E1 interface specification objectives.....               | 7         |
+| 5 Functions of the E1 interface .....                        | 7         |
+| 5.1 General .....                                            | 7         |
+| 5.1.1 E1 interface management function.....                  | 7         |
+| 5.1.2 E1 bearer context management function .....            | 7         |
+| 5.1.3 Trace function.....                                    | 8         |
+| 5.1.4 Load management function .....                         | 8         |
+| 5.1.5 Measurement results transfer function .....            | 8         |
+| 5.1.6 Support for IAB .....                                  | 8         |
+| 5.1.7 E1 bearer context management function for NR MBS.....  | 9         |
+| 5.2 TEIDs allocation .....                                   | 9         |
+| 6 Procedures of the E1 interface .....                       | 9         |
+| 6.1 Interface Management procedures .....                    | 9         |
+| 6.2 Bearer Context Management procedures .....               | 9         |
+| 6.3 UE Tracing procedures.....                               | 10        |
+| 6.4 Load management procedures.....                          | 10        |
+| 6.5 Measurement results transfer procedures.....             | 10        |
+| 6.6 IAB procedures .....                                     | 10        |
+| 6.7 NR MBS procedures .....                                  | 10        |
+| 7 E1 interface protocol structure.....                       | 11        |
+| 8 Other E1 interface specifications .....                    | 11        |
+| 8.1 E1 interface: layer 1 (3GPP TS 37.481).....              | 11        |
+| 8.2 E1 interface: signalling transport (3GPP TS 37.482)..... | 11        |
+| 8.3 E1 interface: E1AP specification (3GPP TS 37.483).....   | 12        |
+| <b>Annex A (informative): Change history.....</b>            | <b>13</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 3GPP TS 37.48x series of technical specifications that define the E1 interface. The E1 interface provides means for interconnecting a gNB-CU-CP and a gNB-CU-UP of a gNB-CU within an NG-RAN, or for interconnecting a gNB-CU-CP and a gNB-CU-UP of an en-gNB within an E-UTRAN, or for interconnecting an eNB-CP and an eNB-UP of an eNB within an E-UTRAN, or for interconnecting an ng-eNB-CU-CP and an ng-eNB-CU-UP of an ng-eNB-CU within an NG-RAN.
+
+# 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 38.401: "NG-RAN; Architecture Description".
+- [3] 3GPP TS 37.481: "E1 layer 1".
+- [4] 3GPP TS 37.482: "E1 signalling transport".
+- [5] 3GPP TS 37.483: "E1 Application Protocol (E1AP)".
+- [6] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+- [7] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".
+- [8] 3GPP TS 37.470: "W1 interface; General aspects and principles".
+- [9] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description".
+- [10] 3GPP TS 23.247: "5G multicast-broadcast services; Stage 2".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
+
+**eNB-CP:** as defined in TS 36.401 [9].
+
+**eNB-UP:** as defined in TS 36.401 [9].
+
+**en-gNB:** as defined in TS 37.340 [7].
+
+**gNB-CU:** as defined in TS 38.401 [2].
+
+**gNB-CU-CP:** as defined in TS 38.401 [2].
+
+**gNB-CU-UP:** as defined in TS 38.401 [2].
+
+**gNB-DU:** as defined in TS 38.401 [2].
+
+**gNB:** as defined in TS 38.300 [6].
+
+**IAB:** as defined in TS 38.300 [6].
+
+**ng-eNB-CU:** as defined in TS 37.470 [8].
+
+**ng-eNB-CU-CP:** as defined in TS 38.401 [2].
+
+**ng-eNB-CU-UP:** as defined in TS 38.401 [2].
+
+**ng-eNB-DU:** as defined in TS 37.470 [8].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
+
+|        |                                           |
+|--------|-------------------------------------------|
+| DL     | Downlink                                  |
+| DRB    | Data Radio Bearer                         |
+| E1AP   | E1 Application Protocol                   |
+| IP     | Internet Protocol                         |
+| MBS    | Multicast/Broadcast Service               |
+| MT-SDT | Mobile Terminated Small Data Transmission |
+| PTP    | Point to Point                            |
+| PTM    | Point to Multipoint                       |
+| SCTP   | Stream Control Transmission Protocol      |
+| TNL    | Transport Network Layer                   |
+
+# --- 4 General aspects
+
+This clause captures the E1 interface principles and characteristics.
+
+**Note:** The principles, functions and procedures specified in this specification also apply to the case where E1AP is used between an ng-eNB-CU-CP and an ng-eNB-CU-UP or between an eNB-CP and an eNB-UP, unless stated otherwise.
+
+## 4.1 E1 interface general principles
+
+The general principles for the specification of the E1 interface are as follows:
+
+- the E1 interface is open;
+- the E1 interface supports the exchange of signalling information between the endpoints;
+- from a logical standpoint, the E1 is a point-to-point interface between a gNB-CU-CP and a gNB-CU-UP, or between an ng-eNB-CU-CP and an ng-eNB-CU-UP, or between an eNB-CP and an eNB-UP.
+
+**NOTE 1:** A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints.
+
+- the E1 interface separates Radio Network Layer and Transport Network Layer;
+- the E1 interface enables exchange of UE associated information and non-UE associated information;
+- the E1 interface is future proof to fulfil different new requirements, support of new services and new functions.
+
+## 4.2 E1 interface specification objectives
+
+The E1 interface specifications facilitate the following:
+
+- inter-connection of a gNB-CU-CP and a gNB-CU-UP supplied by different manufacturers.
+- inter-connection of an ng-eNB-CU-CP and an ng-eNB-CU-UP supplied by different manufacturers.
+- inter-connection of an eNB-CP and an eNB-UP supplied by different manufacturers.
+
+# --- 5 Functions of the E1 interface
+
+## 5.1 General
+
+The following clauses describe the functions supported over E1.
+
+### 5.1.1 E1 interface management function
+
+The error indication function is used by the gNB-CU-UP or gNB-CU-CP to indicate to the gNB-CU-CP or gNB-CU-UP that an error has occurred.
+
+The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the gNB-CU-UP and the gNB-CU-CP.
+
+The E1 setup function allows to exchange application level data needed for the gNB-CU-UP and gNB-CU-CP to interoperate correctly on the E1 interface. The E1 setup is initiated by both the gNB-CU-UP and gNB-CU-CP.
+
+The gNB-CU-UP Configuration Update and gNB-CU-CP Configuration Update functions allow to update application level configuration data needed between the gNB-CU-CP and the gNB-CU-UP to interoperate correctly over the E1 interface.
+
+The E1 setup and gNB-CU-UP Configuration Update functions allow to inform NR CGI(s), ECGI(s), S-NSSAI(s), PLMN-ID(s), QoS information and NID(s) supported by the gNB-CU-UP.
+
+The E1 setup and gNB-CU-UP Configuration Update functions allow the gNB-CU-UP to signal its capacity information to the gNB-CU-CP.
+
+The E1 gNB-CU-UP Status Indication function allows to inform the overloaded or non-overloaded status over the E1 interface.
+
+### 5.1.2 E1 bearer context management function
+
+The establishment of the E1 bearer context is initiated by the gNB-CU-CP and accepted or rejected by the gNB-CU-UP based on admission control criteria (e.g., resource not available).
+
+The modification of the E1 bearer context can be initiated by either gNB-CU-CP or gNB-CU-UP. The receiving node can accept or indicate failure to carry out the modification request. The E1 bearer context management function also supports the release of the bearer context previously established in the gNB-CU-UP. The release of the bearer context is triggered by the gNB-CU-CP either directly or following a request received from the gNB-CU-UP.
+
+This function is used to setup and modify the QoS-flow to DRB mapping configuration. The gNB-CU-CP decides flow-to-DRB mapping and provides the generated SDAP and PDCP configuration to the gNB-CU-UP. The gNB-CU-CP also decides the Reflective QoS flow to DRB mapping. The function is also used to send to the gNB-CU-UP the alternative QoS Parameters Sets when available for a QoS flow. For each PDU Session Resource to be setup or modified, the S-NSSAI, shall be provided in the E1 bearer context setup procedure and may be provided in the E1 bearer context modification procedure by gNB-CU-CP to the gNB-CU-UP.
+
+This function is also used to setup and modify the EPS bearer/E-RAB to DRB mapping configuration for the case of eNB-CP and eNB-UP separation. The eNB-CP decides EPS bearer/E-RAB-to-DRB mapping and provides the E-UTRAN/NR PDCP configuration to the eNB-UP.
+
+This function is also used for the gNB-CU-UP to report the MT-SDT data size to the gNB-CU-CP.
+
+This function is used for the gNB-CU-CP to send the security information to the gNB-CU-UP.
+
+This function is used for the gNB-CU-CP to send to the gNB-CU-UP transport layer information to be used for data forwarding e.g., during handovers.
+
+This function is used for the gNB-CU-CP to send the parameters for header compression for certain traffic types e.g., IP, Ethernet to the gNB-CU-UP.
+
+This function is used for the gNB-CU-CP to send the uplink data compression parameters to the gNB-CU-UP for certain data radio bearer(s).
+
+This function is used for the gNB-CU-UP to notify the event of DL data arrival detection to the gNB-CU-CP. With this function, the gNB-CU-UP requests gNB-CU-CP to trigger paging procedure over F1 or Xn to support RRC Inactive state. RRC Inactive state is not supported when this function is used between an eNB-CP and an eNB-UP.
+
+This function is used for the gNB-CU-UP to notify the gNB-CU-CP that a DL packet including a QFI value not configured by the gNB-CU-CP or an UL packet including a QFI value in the SDAP header of the default DRB not configured by the gNB-CU-CP is received for the first time. The gNB-CU-CP can take further action if needed.
+
+This function is used for the gNB-CU-UP to notify the gNB-CU-CP during the SDT procedure that the received DL SDT data crossed the data size threshold. The gNB-CU-CP can take further action if needed.
+
+This function is used for the gNB-CU-UP to notify the event of user inactivity to the gNB-CU-CP. With this function, the gNB-CU-UP indicates that the inactivity timer associated with a bearer, a PDU session or a UE expires, or that user data is received for the bearer, the PDU session or the UE whose inactivity timer has expired. The gNB-CU-CP consolidates all the serving gNB-CU-UPs for the UE and takes further action.
+
+This function is used for the gNB-CU-UP to report data volume to the gNB-CU-CP.
+
+This function is used for the gNB-CU-CP to notify the suspension and resumption of bearer contexts to the gNB-CU-UP. Suspension and resumption of bearer contexts are not applicable to eNB-CP/eNB-UP and ng-eNB-CU-CP/ng-eNB-CU-UP.
+
+This function also allows to support CA based packet duplication as described in TS 38.300 [6], i.e. one data radio bearer should be configured with at least two GTP-U tunnels between gNB-CU-UP and a gNB-DU.
+
+This function is used to support the enhanced mobility operations as described in TS 38.300 [6] in the gNB-CU-UP.
+
+### 5.1.3 Trace function
+
+The Trace function provides means to control trace sessions for a UE over E1 interface.
+
+### 5.1.4 Load management function
+
+The load management function allows an gNB-CU-CP to request the reporting of load measurements to gNB-DU and is used by gNB-CU-UP to report the result of measurements admitted by gNB-CU-UP.
+
+### 5.1.5 Measurement results transfer function
+
+The measurement results transfer is used by the gNB-CU-CP to transfer UE associated measurement results to the gNB-CU-UP.
+
+### 5.1.6 Support for IAB
+
+Note: IAB is an NR feature, and this function is not applicable to eNB CP-UP separation and ng-eNB CP-UP separation.
+
+This function is used to update the DL/UL F1-U GTP-U tunnels for an IAB network, and allow the gNB-CU-CP to send the security key info to the gNB-CU-UP for the protection of the F1-U interface with IAB-DU.
+
+### 5.1.7 E1 bearer context management function for NR MBS
+
+The E1 bearer context management function for NR MBS consists of two sub-sets for functions, one for NR MBS broadcast, one for NR MBS multicast.
+
+Both sets follow the principles of the E1 bearer context management functions, with the following differences.
+
+- E1 NR MBS procedure concerns a single MBS Session Resource only.
+- E1 NR MBS procedures concern the control of MRB resources in gNB-CU-UP.
+- E1 NR MBS procedures do not control security information, as for NR MBS, PDCP does not apply security as specified in TS 38.300 [6].
+- QoS flow to MRB mapping is determined by the gNB-CU-CP or, in case of shared NR-U terminations, the gNB-CU-UP may be notified about the QoS flow to MRB mapping already determined in the bearer context for the shared NR-U termination. The gNB-CU-CP may inform the gNB-CU-UP whether it is contended with the already determined mapping decision.
+
+NOTE: Not all QoS flow parameters are applicable for NR MBS, as specified in TS 23.247 [10].
+
+- Data volume reporting is not applicable for NR MBS.
+- CA based packet duplication is not applicable for NR MBS.
+
+## 5.2 TEIDs allocation
+
+The gNB-CU-UP is responsible for the allocation of the F1-U UL GTP TEID for each data radio bearer.
+
+The gNB-CU-UP is responsible for the allocation of the S1-U DL GTP TEID for each E-RAB and the NG-U DL GTP TEID for each PDU Session.
+
+The gNB-CU-UP is responsible for the allocation of the X2-U DL/UL GTP TEID or the Xn-U DL/UL GTP TEID for each data radio bearer.
+
+# --- 6 Procedures of the E1 interface
+
+## 6.1 Interface Management procedures
+
+The E1 interface management procedures are listed below:
+
+- Reset procedure
+- Error Indication procedure
+- gNB-CU-UP E1 Setup procedure
+- gNB-CU-CP E1 Setup procedure
+- gNB-CU-UP Configuration Update procedure
+- gNB-CU-CP Configuration Update procedure
+- E1 Release procedure
+- gNB-CU-UP Status Indication procedure
+
+## 6.2 Bearer Context Management procedures
+
+The E1 bearer management procedures are listed below:
+
+- Bearer Context Setup procedure
+- Bearer Context Release Request (gNB-CU-UP initiated) procedure
+- Bearer Context Release (gNB-CU-CP initiated) procedure
+- Bearer Context Modification (gNB-CU-CP initiated) procedure
+- Bearer Context Modification Required (gNB-CU-UP initiated) procedure
+- DL Data Notification procedure
+- Bearer Context Inactivity Notification procedure
+- Data Usage Report procedure
+- MR-DC Data Usage Report procedure
+
+## 6.3 UE Tracing procedures
+
+The following procedures are used to trace the UE:
+
+- Trace Start procedure
+- Deactivate Trace procedure
+- Cell Traffic Trace procedure
+
+## 6.4 Load management procedures
+
+The load management procedures are listed as below:
+
+- Resource Status Reporting Initiation procedure
+- Resource Status Reporting procedure
+
+## 6.5 Measurement results transfer procedures
+
+The measurement results transfer procedures are listed as below:
+
+- gNB-CU-CP Measurement Results Information
+
+## 6.6 IAB procedures
+
+Note: IAB is an NR feature, and this procedure is not applicable to eNB CP-UP separation and ng-eNB CP-UP separation.
+
+The IAB procedures are listed as below:
+
+- IAB UP TNL Address Update procedure
+- IAB PSK Notification procedure
+
+## 6.7 NR MBS procedures
+
+The E1 MBS procedures are listed below:
+
+- Broadcast E1AP MBS procedures
+- BC Bearer Context Setup
+
+- BC Bearer Context Modification (gNB-CU-CP initiated)
+- BC Bearer Context Modification (gNB-CU-UP initiated)
+- BC Bearer Context Release (gNB-CU-CP initiated)
+- BC Bearer Context Release (gNB-CU-UP initiated)
+- Multicast E1AP MBS procedures
+  - MC Bearer Context Setup
+  - MC Bearer Context Modification (gNB-CU-CP initiated)
+  - MC Bearer Context Modification (gNB-CU-UP initiated)
+  - MC Bearer Context Release (gNB-CU-CP initiated)
+  - MC Bearer Context Release (gNB-CU-UP initiated)
+  - MC Bearer Notification
+
+# 7 E1 interface protocol structure
+
+Figure 7.1-1 shows the protocol structure for E1. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as E1AP (E1 Application Protocol).
+
+![Diagram of E1 interface protocol structure showing Control Plane and User Plane layers.](5e92d9e8e9ce204e405bff2367f88176_img.jpg)
+
+The diagram illustrates the protocol stack for the E1 interface. It is divided into two main sections: the Control Plane and the User Plane. The Control Plane contains the E1-AP (E1 Application Protocol) block. The User Plane consists of a stack of four layers: SCTP (Stream Control Transmission Protocol), IP (Internet Protocol), Data link layer, and Physical layer. The E1-AP block is connected to the SCTP block via a horizontal line with an oval symbol, representing a protocol data unit (PDU) or a connection point. The SCTP block is part of the Transport Network Layer, which also includes the IP, Data link layer, and Physical layer blocks. The Radio Network Layer is shown above the E1-AP block, indicating its position in the overall network architecture.
+
+Diagram of E1 interface protocol structure showing Control Plane and User Plane layers.
+
+Figure 7.1-1: Interface protocol structure for E1
+
+# 8 Other E1 interface specifications
+
+This clause contains the description of the other related 3GPP specifications.
+
+## 8.1 E1 interface: layer 1 (3GPP TS 37.481)
+
+3GPP TS 37.481 [3] specifies the physical layer technologies that may be used to support the E1 interface.
+
+## 8.2 E1 interface: signalling transport (3GPP TS 37.482)
+
+3GPP TS 37.482 [4] specifies the signalling bearers for the E1AP for the E1 interface.
+
+## 8.3 E1 interface: E1AP specification (3GPP TS 37.483)
+
+3GPP TS 37.483 [5] specifies the E1AP protocol for radio network control plane signalling over the E1 interface.
+
+# Annex A (informative): Change history
+
+| Change history |             |           |      |     |     |                                                                                                                                                                                            |             |
+|----------------|-------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting     | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                            | New version |
+| 2022-01        | R3#114bis-e | R3-220846 |      |     |     | Text transferred from TS 38.460 v16.4.0 and references updated to 37.48x series                                                                                                            | 0.0.1       |
+| 2022-02        | R3#115-e    | R3-221646 |      |     |     | Changes from Rel-17 WI "LTE_NR_arch_evo_enh-Core" incorporated and change history updated.                                                                                                 | 0.1.0       |
+| 2022-03        | R3#115-e    | R3-222579 |      |     |     | Agreements from Rel-17 WI "LTE_NR_arch_evo_enh-Core" at RAN3#115-e incorporated.                                                                                                           | 0.1.1       |
+| 2022-03        | R3#115-e    | R3-222973 |      |     |     | Change history updated                                                                                                                                                                     | 0.2.0       |
+| 2022-03        | RAN#95-e    | RP-220795 |      |     |     | Version submitted for approval in RAN#95-e                                                                                                                                                 | 1.0.0       |
+| 2022-03        | RAN#95-e    | R3-220848 |      |     |     | Agreed Rel-16/17 CRs from other WIs are merged.<br>Including REL-16 38.460 changes of R3-221224 of RP-220276, and REL-17 38.460 changes of R3-222614 of RP-220234, R3-222929 of RP-220224. | 1.1.0       |
+| 2022-03        | SA#95-e     |           |      |     |     | Promotion to Release 17 without technical change                                                                                                                                           | 17.0.0      |
+| 2022-06        | RAN#96      | RP-221145 | 0001 | -   | D   | E1 TS 37.480 Editorial corrections                                                                                                                                                         | 17.1.0      |
+| 2022-06        | RAN#96      | RP-221134 | 0002 | -   | F   | Corrections on E1 bearer context management function for NR MBS                                                                                                                            | 17.1.0      |
+| 2023-12        | RAN#102     | RP-233849 | 0005 | 2   | F   | Correction on Temp no data and DL data arrival for Activate Multicast Session                                                                                                              | 17.2.0      |
+| 2023-12        | RAN#102     | RP-233820 | 0003 | 5   | B   | Introduction on MT-SDT                                                                                                                                                                     | 18.0.0      |

marked/Rel-18/37_series/37481/raw.md

@@ -0,0 +1,108 @@
+
+
+# 3GPP TS 37.481 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 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 .....                                    | 5        |
+| 1 Scope.....                                      | 6        |
+| 2 References.....                                 | 6        |
+| 3 Abbreviations .....                             | 6        |
+| 4 Introduction.....                               | 6        |
+| <b>Annex A (informative): Change history.....</b> | <b>6</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 standards allowed to implement layer 1 on the E1 interface.
+
+The specification of transmission delay requirements and O&M requirements are 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 38.411: "NG-RAN; NG layer 1".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TS 38.411 [1] apply.
+
+# --- 4 Introduction
+
+The E1 Layer 1 shall comply with the requirements of clauses 4 through 6 in TS 38.411 [1].

marked/Rel-18/37_series/37482/raw.md

@@ -0,0 +1,231 @@
+
+
+# 3GPP TS 37.482 V18.1.0 (2024-06)
+
+Technical Specification
+
+## 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 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 stylized font with a red signal wave icon below the 'G', 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 and abbreviations .....             | 6        |
+| 3.1 Definitions.....                              | 6        |
+| 3.2 Abbreviations .....                           | 6        |
+| 4 E1 signalling bearer .....                      | 6        |
+| 4.1 Function and protocol stack .....             | 6        |
+| 5 Data link layer.....                            | 7        |
+| 6 IP layer.....                                   | 7        |
+| 7 Transport layer .....                           | 7        |
+| <b>Annex A (informative): Change history.....</b> | <b>9</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 the E1 interface. The E1 interface provides means for the interconnection of gNB-CU-CP and gNB-CU-UP within the NG-RAN architecture (TS 38.401 [2]), or for the interconnection of ng-eNB-CU-CP and ng-eNB-CU-UP within the NG-RAN architecture (TS 38.401 [2]), or for the interconnection of eNB-CP and eNB-UP within the E-UTRAN architecture (TS 36.401 [13]).
+
+# --- 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 38.401: "NG-RAN; Architecture description".
+- [3] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification".
+- [4] IETF RFC 791 (1981-09): "Internet Protocol".
+- [5] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [6] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol".
+- [7] 3GPP TS 37.480: "E1 general aspects and principles".
+- [8] 3GPP TS 37.481: "E1 layer 1".
+- [9] 3GPP TS 37.483: "E1 Application Protocol (E1AP)".
+- [10] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage-2".
+- [11] IETF RFC 6083 (2011-01): "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)".
+- [12] IETF RFC 6335 (2011-08): "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry".
+- [13] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description".
+- [14] 3GPP TS 37.470: "W1 interface; General aspects and principles".
+- [15] IANA: "Stream Control Transmission Protocol (SCTP) Parameters", [<https://www.iana.org/assignments/sctp-parameters/sctp-parameters.xhtml#sctp-parameters-25>].
+- [16] IANA: "Service Name and Transport Protocol Port Number Registry", [<https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml>].
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
+
+**E1:** interface between a gNB-CU-CP and a gNB-CU-UP, providing an interconnection point between the gNB-CU-CP and the gNB-CU-UP, as defined in TS 38.300 [10]. This interface also applies to between the ng-eNB-CU-CP and the ng-eNB-CU-UP or between the eNB-CP and the eNB-UP.
+
+**eNB-CP:** as defined in TS 36.401 [13].
+
+**eNB-UP:** as defined in TS 36.401 [13].
+
+**gNB-CU:** as defined in TS 38.401 [2].
+
+**gNB-CU-CP:** as defined in TS 38.401 [2].
+
+**gNB-CU-UP:** as defined in TS 38.401 [2].
+
+**ng-eNB-CU:** as defined in TS 37.470 [14].
+
+**ng-eNB-CU-CP:** as defined in TS 38.401 [2].
+
+**ng-eNB-CU-UP:** as defined in TS 38.401 [2].
+
+**ng-eNB-DU:** as defined in TS 37.470 [14].
+
+**SCTP endpoint:** as defined in IETF RFC 4960 (2007-09) [6].
+
+**SCTP association:** as defined in IETF RFC 4960 (2007-09) [6].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
+
+|          |                                      |
+|----------|--------------------------------------|
+| DiffServ | Differentiated Service               |
+| IANA     | Internet Assigned Number Authority   |
+| IP       | Internet Protocol                    |
+| PPP      | Point to Point Protocol              |
+| SCTP     | Stream Control Transmission Protocol |
+
+# 4 E1 signalling bearer
+
+## 4.1 Function and protocol stack
+
+E1 signalling bearer provides the following functions:
+
+- Provision of reliable transfer of E1AP message over E1 interface;
+- Provision of networking and routing function;
+- Provision of redundancy in the signalling network;
+- Support for flow control and congestion control.
+
+The protocol stack for E1 Signalling Bearer is shown in figure 4.1-1 and details on each protocol are described in the following sections.
+
+![Figure 4.1-1: E1 signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the EIAP protocol. Below EIAP is a horizontal line with an oval in the center, representing a connection point. Below this line is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer protocols stacked vertically.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg)
+
+|                         |                 |
+|-------------------------|-----------------|
+| Radio Network Layer     | EIAP            |
+|                         | — ( ) —         |
+| Transport Network Layer | SCTP            |
+|                         | IP              |
+|                         | Data link layer |
+|                         | Physical layer  |
+
+Figure 4.1-1: E1 signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the EIAP protocol. Below EIAP is a horizontal line with an oval in the center, representing a connection point. Below this line is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer protocols stacked vertically.
+
+**Figure 4.1-1: E1 signalling bearer protocol stack**
+
+The Transport Network Layer is based on IP transport, comprising SCTP on top of IP.
+
+# 5 Data link layer
+
+The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented.
+
+# 6 IP layer
+
+The gNB-CU-CP, gNB-CU-UP, ng-eNB-CU-CP, ng-eNB-CU-UP, eNB-CP and eNB-UP shall support IPv6 (IETF RFC 8200 [3]) and/or IPv4 (IETF RFC 791 [4]).
+
+The IP layer of E1 only supports point-to-point transmission for delivering EIAP message.
+
+The gNB-CU-CP, gNB-CU-UP, ng-eNB-CU-CP, ng-eNB-CU-UP, eNB-CP and eNB-UP shall support the Diffserv Code Point marking as described in IETF RFC 2474 [5].
+
+# 7 Transport layer
+
+**NOTE:** The transport layer structure and mechanism specified in this section are also used between ng-eNB-CU-CP and ng-eNB-CU-UP or between eNB-CP and eNB-UP, unless stated otherwise. With this understanding, in this section each instance of gNB-CU-CP could be treated as eNB-CP or ng-eNB-CU-CP, and each gNB-CU-UP could be treated as eNB-UP or ng-eNB-CU-UP, for eNB or ng-eNB CP/UP separation respectively.
+
+SCTP (IETF RFC 4960 [6]) shall be supported as the transport layer of E1 signalling bearer. The Payload Protocol Identifier to be used by SCTP for the application layer protocol EIAP and for DTLS over SCTP (IETF RFC 6083 [11]) is assigned by IANA in [15]. The byte order of the ppid shall be big-endian.
+
+SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network.
+
+The gNB-CU-CP and gNB-CU-UP shall support a configuration with a single SCTP association per gNB-CU-CP/gNB-CU-UP pair. Configurations with multiple SCTP endpoints per gNB-CU-CP/gNB-CU-UP pair should be supported. When configurations with multiple SCTP associations are supported, the gNB-CU-CP or the gNB-CU-UP may request to dynamically add/remove SCTP associations between the gNB-CU-CP/gNB-CU-UP pair. Within the set of SCTP associations established between one gNB-CU-CP and gNB-CU-UP pair, a single SCTP association shall be employed
+
+for E1AP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness.
+
+When the configuration with multiple SCTP endpoints per gNB-CU-UP is supported and gNB-CU-UP wants to add additional SCTP endpoints, the gNB-CU-UP Configuration Update procedure shall be the first E1AP procedure triggered on an additional TNLA of an already setup E1 interface instance after the TNL association has become operational, and the gNB-CU-CP shall associate the TNLA to the E1 interface instance using the included gNB-CU-UP ID.
+
+Either the gNB-CU-CP or gNB-CU-UP shall establish the first SCTP association. The additional SCTP associations are established by the gNB-CU-UP. The SCTP Destination Port number value to be used for E1AP is assigned by IANA in [16]. When the gNB-CU-CP requests to dynamically add additional SCTP associations between the gNB-CU-CP and gNB-CU-UP pair, the gNB-CU-CP port is selected and signalled by the gNB-CU-CP to the gNB-CU-UP, and it can be port number value assigned by IANA in [16] or any dynamic port value as defined by IETF RFC 6335 [12].
+
+Between one gNB-CU-CP and gNB-CU-UP pair:
+
+- A single pair of stream identifiers shall be reserved over an SCTP association for the sole use of E1AP elementary procedures that utilize non UE-associated signalling;
+- At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of E1AP elementary procedures that utilize UE-associated signalling. However, a few pairs (i.e. more than one) should be reserved;
+- For a single UE-associated signalling the gNB-CU-CP and the gNB-CU-UP shall use one SCTP association and one SCTP stream, and the SCTP association/stream should not be changed during the communication of the UE-associated signalling until after current SCTP association is failed or removed, or TNL binding update is performed.
+
+Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from a gNB-CU-CP or a gNB-CU-UP, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960 [6] in sub clause 5.2.
+
+The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages.
+
+For MBS-associated signalling, principles specified above for UE-associated signalling shall apply.