Add files using upload-large-folder tool

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

@@ -0,0 +1,670 @@
+
+
+# 3GPP TS 29.016 V18.0.0 (2024-04)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification (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.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                               |           |
+|-------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                | 4         |
+| Introduction .....                                                            | 4         |
+| 1 Scope.....                                                                  | 5         |
+| 2 References.....                                                             | 5         |
+| 2.1 Normative references .....                                                | 5         |
+| 2.2 Informative references.....                                               | 6         |
+| 3 Definitions, symbols and abbreviations .....                                | 7         |
+| 4 Configuration of the Gs interface.....                                      | 7         |
+| 4.1 Use of Protocol Stacks .....                                              | 7         |
+| 5 Conformance to message transfer part (MTP) .....                            | 7         |
+| 5.1 General .....                                                             | 7         |
+| 5.2 MTP Level 1.....                                                          | 8         |
+| 5.3 MTP Level 2.....                                                          | 8         |
+| 5.3.1 MTP Level 2 for E1 Interface.....                                       | 8         |
+| 5.3.2 MTP Level 2 for T1 Interface.....                                       | 8         |
+| 5.4 MTP Level 3.....                                                          | 8         |
+| 5.4.1 MTP Level 3 for E1 Interface.....                                       | 8         |
+| 5.4.1.1 General clauses .....                                                 | 9         |
+| 5.4.1.2 Configuration dependent clauses .....                                 | 9         |
+| 5.4.1.3 Informative clauses .....                                             | 11        |
+| 5.4.2 MTP Level 3 for T1 Interface.....                                       | 12        |
+| 5.4.2.1 General clauses .....                                                 | 12        |
+| 5.4.2.2 Configuration dependent clauses .....                                 | 13        |
+| 5.4.2.3 Informative clauses .....                                             | 15        |
+| 6 Conformance to SCCP .....                                                   | 16        |
+| 6.1 Overview .....                                                            | 16        |
+| 6.2 SCCP Primitives.....                                                      | 16        |
+| 6.2.1 SCCP Primitives for E1 Interface (ITU Recommendation Q.711) .....       | 16        |
+| 6.2.2 SCCP Primitives for T1 Interface (ANSI Standards T1.112.1) .....        | 16        |
+| 6.3 SCCP messages.....                                                        | 17        |
+| 6.3.1 SCCP messages for E1 Interface (ITU Recommendation Q.712).....          | 17        |
+| 6.3.2 SCCP messages for T1 Interface (ANSI Standards T1.112.2).....           | 17        |
+| 6.4 SCCP formats and codes.....                                               | 18        |
+| 6.4.1 SCCP format and codes for E1 Interface (ITU Recommendation Q.713) ..... | 18        |
+| 6.4.2 SCCP format and codes for T1 Interface (ANSI Standards T1.112.3) .....  | 18        |
+| 6.5 SCCP procedures.....                                                      | 19        |
+| 6.5.1 SCCP procedures for E1 Interface (ITU Recommendation Q.714) .....       | 19        |
+| 6.5.2 SCCP procedures for T1 Interface (ANSI Standards T1.112.4) .....        | 19        |
+| 7 Use of the SCCP (E1/T1 Interface).....                                      | 20        |
+| <b>Annex A (informative): Change history.....</b>                             | <b>21</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document provides a mechanism giving reliable transfer of signalling messages between the Serving GPRS Support Node (SGSN) and the data base of a Visitors Location Register (VLR) for co-ordination between GSM circuit switched services and GSM packet data services within the 3GPP system.
+
+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 Indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the specification;
+
+# --- Introduction
+
+The present document specifies or references the necessary information to provide a reliable transfer of signalling messages between the Serving GPRS Support Node (SGSN) and the Visitors Location Register (VLR). This reliable transfer of messages is provided by the Network Service Part (NSP) of the Signalling System No 7 (SS7). This document specifies or references the subset of MTP and SCCP to be used in the Gs interface.
+
+# --- 1 Scope
+
+The present document specifies or references the subset of MTP and SCCP which is used for the reliable transport of BSSAP+ messages in the Gs interface. The present document references the 3GPP TS 29.202 which specifies alternative transport layers that can be applied instead of the MTP. The present document also specifies the SCCP addressing capabilities to be provided in the Gs interface.
+
+The present document is divided into two main parts, clause 5 dealing with the use of MTP and clauses 6 and 7 dealing with the use of SCCP.
+
+Clause 5 of the present document deals with the subset of the MTP that is required between an SGSN and a VLR. It is intended that this implementation of MTP is compatible with a full MTP implementation. Clause 4 references the 3GPP TS 29.202 which specifies alternatives to the MTP.
+
+The SCCP is used to provide message routing between the SGSN and the VLR. The SCCP routing principles specified in the present document allow to connect one SGSN to several VLR. No segmentation at SCCP level is needed on the Gs interface. Only SCCP class 0 is used on the Gs interface. Clauses 6 and 7 identify the SCCP subset that should be used between an SGSN and an VLR.
+
+# --- 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*.
+
+## 2.1 Normative references
+
+- [1] Void.
+- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1".
+- [3] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [4] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode".
+- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [6] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface".
+- [7] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification".
+- [8] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)".
+- [9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+
+- [10] 3GPP TS 49.008: "Application of the Base Station System Application Part (BSSAP) on the E-interface".
+- [11] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface Layer 3 specification".
+- [12] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
+- [13] ITU-T Recommendation Q.711: "Functional description of the signalling connection control part".
+- [14] ITU-T Recommendation Q.712: "Definition and function of signalling connection control part messages".
+- [15] ITU-T Recommendation Q.713: "Signalling connection control part formats and codes".
+- [16] ITU-T Recommendation Q.714: "Signalling connection control part procedures".
+- [17] ITU-T Recommendation Q.702: "Signalling data link".
+- [18] ITU-T Recommendation Q.703: "Signalling link".
+- [19] ITU-T Recommendation Q.704: "Signalling network functions and messages".
+- [20] ITU-T Recommendation Q.707: "Testing and maintenance".
+- [21] ANSI T1.111 (1996):"Signalling System No. 7 (SS7); Message Transfer Part".
+- [22] ANSI T1.112 (1996): "Signalling System No. 7 (SS7); Signalling Connection Control Part Functional Description".
+- [41] 3GPP TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3".
+
+## 2.2 Informative references
+
+- [23] 3GPP TS 22.001: "Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)".
+- [24] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
+- [25] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
+- [26] Void.
+- [27] Void.
+- [28] 3GPP TS 43.064: "Overall description of the GPRS Radio interface; Stage 2".
+- [29] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration".
+- [30] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
+- [31] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".
+- [32] 3GPP TS 44.065: "Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDPCP)".
+- [33] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels."
+- [34] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface".
+- [35] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN)".
+
+- [36] Void.
+- [37] Void.
+- [38] Void.
+- [39] Void.
+- [40] Void.
+
+# --- 3 Definitions, symbols and abbreviations
+
+Unless listed below, the definitions, symbols and abbreviations are listed in 3GPP TR 21.905 and 3GPP TS 23.060.
+
+# --- 4 Configuration of the Gs interface
+
+The Gs interface connects the Serving GPRS Support Node (SGSN) to the Visitors Location Register (VLR). This interface is defined in the 64 kbit/s for E1 interface and for 64 kbit/s or 56 kbit/s for T1 interface boundary of an SGSN to a VLR or of a VLR to an SGSN. The configuration of the Gs interface shall not impose any restriction on the number of VLRs or SGSNs to be connected by the Gs interface. The Gs interface definition shall support an early implementation of GPRS when one SGSN may be connected to several VLRs or a more mature implementation when several SGSNs may be connected to one VLR. Therefore the interface shall support the use of an STP.
+
+The level of resilience in the Gs interface is determined by the operator, however it is recommended that the operator considers the use of more than one multiplex system between the SGSN and the VLR. Each multiplex system should be used to carry one signalling link and routing diversity should be provided among the signalling links to increase the resilience of the system.
+
+## 4.1 Use of Protocol Stacks
+
+BSSAP+ shall be transported over SCCP and the transport layers specified in 3GPP TS 29.202. The protocol stack is shown in figure 4.1.
+
+When MTP is used to transport BSSAP+ then the conformance rules specified in clause 5 shall apply.
+
+![](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg)
+
+|                                                    |
+|----------------------------------------------------|
+| BSSAP+                                             |
+| SCCP                                               |
+| Transport layers as specified in<br>3GPP TS 29.202 |
+
+**Figure 4.1: Protocol stack for the transportation of BSSAP+**
+
+# --- 5 Conformance to message transfer part (MTP)
+
+## 5.1 General
+
+The MTP functions as specified in ITU-T Recommendations Q.702, Q.703, Q.704 and Q.707 for E1 interface and ANSI T1.111 Recommendations for the T1 interface are applicable. However, the following subclauses provide a minimum set of MTP requirements that shall be implemented at a SGSN or VLR to support the functionality required by the BSSAP+ protocol in the Gs interface. The set of exceptions and modifications to those recommendations maintain compatibility with the implementation of a full specification of the MTP. The ITU-T recommendations for E1 interface and ANSI recommendation for T1 interface concerning the MTP shall be taken as requirements unless covered by a statement in the present document.
+
+## 5.2 MTP Level 1
+
+The MTP level 1 exceptions and modifications to ITU-T Recommendation Q.702 and ANSI T1.111 Recommendation can be found in 3GPP TS 48.006 subclause 3.2.
+
+## 5.3 MTP Level 2
+
+### 5.3.1 MTP Level 2 for E1 Interface
+
+The MTP level 2 exceptions and modifications to ITU-T Recommendation Q.703 are listed below.
+
+- ITU-T Recommendation Q.703, subclause 1.4:
+  - Only the basic error correction protocol is required.
+- ITU-T Recommendation Q.703, clause 6:
+  - Not applicable, only basic error correction is required.
+- ITU-T Recommendation Q.703, clause 7:
+  - Both the SGSN and the VLR may apply the emergency proving period or the normal proving period in the initial alignment procedure. If all the signalling links between the two entities are unavailable then the SGSN or the VLR shall apply the emergency proving period until one signalling link becomes available.
+- ITU-T Recommendation Q.703, clause 8:
+  - The processor outage status indicator shall be recognised at the SGSN and the VLR and the procedures defined in ITU-T Recommendation Q.703 clause 8 supported. The SGSN and the VLR should support the generation of the processor outage indication towards the peer entity if this is appropriate.
+
+### 5.3.2 MTP Level 2 for T1 Interface
+
+The MTP level 2 exceptions and modifications to ANSI T1.111.3 are listed below.
+
+- ANSI T1.111.3, subclause 1.4:
+  - Only the basic error correction protocol is required (subclause 1.4.3 is not required).
+- ANSI T1.111.3, clause 6:
+  - Not applicable, only basic error correction is required.
+- ANSI T1.111.3, clause 7:
+  - Both the SGSN and the VLR may apply the emergency proving period or the normal proving period in the initial alignment procedure. If all the signalling links between the two entities are unavailable the SGSN or the VLR shall apply the emergency proving period until one signalling link becomes available.
+- ANSI T1.111.3, clause 8:
+  - The processor outage status indicator shall be recognised at the SGSN and the procedures defined in ANSI T1.111.3 clause 8 supported. The SGSN and the VLR shall support the generation of the processor outage indication towards the peer entity if this is appropriate.
+
+## 5.4 MTP Level 3
+
+### 5.4.1 MTP Level 3 for E1 Interface
+
+The Gs interface may be configured as a point to point interface or may use an intermediate SS7 network. In this last case an SGSN or a VLR may act always as end points of the Gs interface (SP functionality) or may be configured to act
+
+as an transfer point between a VLR and an SGSN (SP and STP functionality). The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 are listed regarding whether the SGSN and the VLR are connected by a point to point link or are configured to act as SPs in an SS7 network or if they support STP functionality.
+
+Subclause 5.4.1.1 applies to all configurations of the Gs interface. In subclause 5.4.1.2 the exceptions and modifications to ITU-T Recommendation Q.704 are listed depending upon the configuration of the Gs interface, whether it is a point to point interface or the SGSN and VLR act as an SP only or as SP and STP. Subclause 5.4.1.3 provides points of clarification about the ITU-T Recommendation Q.704.
+
+#### 5.4.1.1 General clauses
+
+The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 regardless of whether the SGSN supports STP functionality are listed below.
+
+- ITU-T Recommendation Q.704, subclause 2.3.5:
+  - Either of the two methods of congestion control is acceptable. The most appropriate method is dependent on national ITU-T No. 7 implementations.
+- ITU-T Recommendation Q.704, subclause 2.4:
+  - The signalling point code for an SGSN may be included in the national signalling point code scheme or in a separate signalling network.
+- ITU-T Recommendation Q.704, subclause 3.8.2:
+  - There are two acceptable methods of congestion control defined in ITU-T Recommendation Q.704, in subclauses 3.8.2.1 a) and b). The most appropriate method is dependent on national ITU-T No. 7 implementations. Each administration should specify its congestion threshold setting algorithm and nodal congestion abatement procedures at system procurement.
+- ITU-T Recommendation Q.704, clause 12:
+  - Only basic link management procedures are required.
+- ITU-T Recommendation Q.704, subclause 14.2.1:
+  - Since all messages are passed using the SCCP, the service indicator for Gs interface operation will be:
+ 
+
+|      |   |   |   |   |
+|------|---|---|---|---|
+| bits | D | C | B | A |
+|      | 0 | 0 | 1 | 1 |
+- ITU-T Recommendation Q.704, subclause 14.2.2:
+  - The sub service field for Gs interface operation will always be set to one of the following values:
+ 
+
+|      |   |   |                  |
+|------|---|---|------------------|
+| bits | D | C |                  |
+|      | 1 | 0 | national network |
+|      | 1 | 1 | local network    |
+- ITU-T Recommendation Q.704, clause 15:
+  - The formats and codes listed are only relevant to the messages that are required, i.e. those not excluded in the rest of this recommendation.
+
+#### 5.4.1.2 Configuration dependent clauses
+
+The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 are permitted if the SGSN or the VLR does not support STP functionality are listed below.
+
+- ITU-T Recommendation Q.704, subclause 1.1.2:
+
+- If the Gs interface is configured as a point to point interface, then there will be no signalling network management features which need to be considered.
+  - ITU-T Recommendation Q.704, clause 2:
+    - If STP functionality is not required the discrimination function of the MTP used for GPRS application can be significantly simplified.
+- NOTE: If the implementation of this interface is for point to point application the routing function within the MTP will be present to select the point code appropriate to the parent VLR.
+- ITU-T Recommendation Q.704, subclause 2.3:
+    - If the implementation of the Gs interface is point to point, load sharing between linksets is not required since there will only be one linkset between SGSN and VLR.
+  - ITU-T Recommendation Q.704, subclause 2.4:
+    - At an SGSN or VLR that does not implement STP functionality, only messages with a correctly checking DPC will be accepted. Others will be discarded. It is recommended that discarding a message because of an incorrectly set point code causes an incident report to be generated.
+  - ITU-T Recommendation Q.704, subclause 3.1.3 c):
+    - In a point to point configuration there is no requirement for signalling route management.
+  - ITU-T Recommendation Q.704, subclause 3.3.2.3:
+    - In a point to point configuration there is no requirement for signalling route management.
+  - ITU-T Recommendation Q.704, subclause 3.3.3.3:
+    - In a point to point configuration there is no requirement for signalling route management.
+  - ITU-T Recommendation Q.704, subclause 3.3.4.3:
+    - In a point to point configuration there is no requirement for signalling route management.
+  - ITU-T Recommendation Q.704, subclause 3.4.3:
+    - Not applicable if no STP functionality is implemented by the SGSN or the VLR.
+  - ITU-T Recommendation Q.704, subclause 3.5.3:
+    - Not applicable if no STP functionality is implemented by the SGSN or the VLR.
+  - ITU-T Recommendation Q.704, subclause 3.8.5.2:
+    - The signalling-route-set-congestion-test procedure is not required.
+  - ITU-T Recommendation Q.704, subclause 4.1.2:
+    - In a point to point configuration signalling routes are not applicable.
+  - ITU-T Recommendation Q.704, subclause 4.2:
+    - The normal routing situation in a point to point configuration will be that there are 1 or more signalling links available between a SGSN and VLR, these will constitute a link set. They will be run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links.
+    - The normal routing situation if more than one route is available between the SGSN and the VLR will be that the load sharing, changeover and changeback procedures would be provided between signalling links within the same signalling linkset and between signalling linksets.
+  - ITU-T Recommendation Q.704, subclause 4.3.3:
+    - There will be no alternative linkset in a point to point configuration of the Gs interface.
+
+- ITU-T Recommendation Q.704, subclause 4.4.3:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, subclause 4.5:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, subclause 4.6:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, subclause 4.7:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, clause 5:
+  - Changeover between link sets is not applicable in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, clause 6:
+  - Changeback between link sets is not applicable in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, clause 7:
+  - Forced re-routing is not applicable if there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, clause 8:
+  - Not applicable if there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface.
+- ITU-T Recommendation Q.704, subclause 13.2:
+  - The transfer prohibited function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of a TFP message, the SGSN or VLR acting as SP shall process the message.
+- ITU-T Recommendation Q.704, subclause 13.3:
+  - The transfer allowed function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of a TFA-message, the SGSN or VLR acting as SP shall process the message.
+- ITU-T Recommendation Q.704, subclause 13.4:
+  - The transfer restricted function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of the TFR message, the SGSN or VLR acting as SP shall process the message.
+- ITU-T Recommendation Q.704, subclause 13.5:
+  - The signalling-route-set-test procedure is not applicable.
+- ITU-T Recommendation Q.704, subclauses 13.6, 13.7 and 13.8:
+  - The transfer controlled function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of TFC message, the SGSN or VLR acting as SP shall process the message.
+- ITU-T Recommendation Q.704, subclause 13.9:
+  - The signalling route-set-congestion-test function is not required.
+  - At the reception of signalling-route-set-congestion-test message no action is required by the receiving entity.
+
+#### 5.4.1.3 Informative clauses
+
+A list of clarifications to ITU-T Recommendation Q.704 are listed below.
+
+- ITU-T Recommendation Q.704, subclause 2.3.4:
+  - The load sharing procedures shall allow any value of the SLC field in the MTP3 network management messages that are not related to a specific signalling link. This allows compatibility between blue book implementations where only the 0000 value is used and white book implementations where load sharing may be applicable to network management messages
+- ITU-T Recommendation Q.704, subclause 3.4.1:
+  - It should be noted that for point to point working, the signalling route will become unavailable when the associated link set fails.
+- ITU-T Recommendation Q.704, subclause 3.4.2:
+  - It should be noted that for point to point working, the signalling route will become available when the associated link set is restored.
+- ITU-T Recommendation Q.704, subclause 3.5.1:
+  - It should be noted that for point to point working the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ITU-T Recommendation Q.704 subclause 11.2.1.
+- ITU-T Recommendation Q.704, subclause 3.5.2:
+  - It should be noted that for point to point interworking the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ITU-T Recommendation Q.704 subclause 11.2.2.
+- ITU-T Recommendation Q.704, clause 9:
+  - The SGSN and the MSC/VLR shall implement the restart procedures specified in ITU-T Recommendation Q.704 (03/1993) MTP3. The restart procedure specified in ITU-T Recommendation Q.704 (11/1988) MTP3 shall not be used.
+- ITU-T Recommendation Q.704, clause 11:
+  - It should be noted that for point to point working the signalling route set will consist of one associated signalling route only.
+
+### 5.4.2 MTP Level 3 for T1 Interface
+
+The Gs interface may be configured as a point to point interface or may use an intermediate SS7 network. In this last case an SGSN or a VLR may act always as end points of the Gs interface (SP functionality) or may be configured to act as a transfer point between a VLR and an SGSN (SP and STP functionality). The MTP level 3 exceptions and modifications to ANSI T1.111.4 are listed regarding whether the SGSN and the VLR are connected by a point to point link or are configured to act as SPs in an SS7 network or if they support STP functionality.
+
+Subclause 5.4.2.1 applies to all configurations of the Gs interface. In subclause 5.4.2.2 the exceptions and modifications to ANSI T1.111.4 are listed depending upon the configuration of the Gs interface, whether it is a point to point interface or the SGSN and VLR act as an SP only or SP and STP. Subclause 5.4.2.3 provides points of clarification about the ANSI T1.111.4.
+
+#### 5.4.2.1 General clauses
+
+The MTP level 3 exceptions and modifications to ANSI T1.111.4 regardless of whether the SGSN supports STP functionality are listed below.
+
+- ANSI T1.111.4, subclause 2.3.5:
+  - Support of ANSI specific Signalling Link Congestion Control as specified in this subclause is required.
+- ANSI T1.111.4, subclause 2.4:
+
+- The signalling point code for an SGSN may be included in the national signalling point code scheme or in a separate signalling network.
+- ANSI T1.111.4, subclause 3.8.2:
+  - Support of ANSI specific Network Congestion as defined in this subclause is required.
+- ANSI T1.111.4, clause 12:
+  - Only basic link management procedures are required.
+- ANSI T1.111.4, subclause 14.2.1:
+  - Since all messages are passed using the SCCP, the service indicator for Gs interface operation will be:
+ 
+
+|      |   |   |   |   |
+|------|---|---|---|---|
+| bits | D | C | B | A |
+|      | 0 | 0 | 1 | 1 |
+- ANSI T1.111.4, subclause 14.2.2:
+  - The sub service field for Gs interface operation will always be set to one of the following values:
+ 
+
+|      |                  |   |
+|------|------------------|---|
+| bits | D                | C |
+|      | 1                | 0 |
+|      | national network |   |
+- ANSI T1.111.4, clause 15:
+  - The formats and codes listed are only relevant to the messages that are required.
+
+#### 5.4.2.2 Configuration dependent clauses
+
+The MTP level 3 exceptions and modifications to ANSI T1.111.4 are permitted if the SGSN or the VLR does not support STP functionality are listed below.
+
+- ANSI T1.111.4, subclause 1.1.2:
+  - If the Gs interface is configured as point to point interface, i.e., it does not support STP function, then the signalling transfer point network management features are not required.
+- ANSI T1.111.4, clause 2:
+  - If STP function is not required, then the discrimination functions of the MTP used for GPRS application can be significantly simplified.
+
+NOTE: If the implementation of this interface is for point to point application the routing function within the MTP will be present to select the point code appropriate to the parent VLR.
+
+- ANSI T1.111.4, subclause 2.3:
+  - If the implementation of the Gs interface is point to point, load sharing between linksets is not required since there will only be one linkset between SGSN and VLR.
+- ANSI T1.111.4, subclause 2.4:
+  - At the SGSN or VLR that does not implement STP functionality, only messages with a correctly checking DPC will be accepted. Other messages will be discarded. It is recommended that when messages are discarded because of an incorrectly set point code, an incident report should be generated.
+- ANSI T1.111.4, subclause 3.1.3 (3):
+  - In a point to point configuration, there is no requirement for signalling route management.
+- ANSI T1.111.4, subclause 3.3.2.3:
+  - In a point to point configuration, there is no requirement for signalling route management.
+
+- ANSI T1.111.4, subclause 3.3.3.3:
+  - In a point to point configuration, there is no requirement for signalling route management.
+- ANSI T1.111.4, subclause 3.3.4.3:
+  - In a point to point configuration, there is no requirement for signalling route management.
+- ANSI T1.111.4, subclause 3.4.3:
+  - Not applicable if no STP functionality is implemented in SGSN or VLR.
+- ANSI T1.111.4, subclause 3.5.3:
+  - Not applicable if no STP functionality is implemented in SGSN or VLR.
+- ANSI T1.111.4, subclause 3.8.5.2:
+  - The signalling-route-set-congestion-test procedure is not required.
+- ANSI T1.111.4, subclause 4.1.2:
+  - In a point to point configuration signalling routes are not applicable.
+- ANSI T1.111.4, subclause 4.2:
+  - The normal routing situation in a point to point configuration will be that there are 1 or more signalling links available between a SGSN and VLR, these will constitute a link set. They will run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links.
+  - The normal routing situation if more than one route is available between the SGSN and the VLR will be that the load sharing, changeover and changeback procedures would be provided between signalling links within the same signalling linkset and between signalling linksets.
+- ANSI T1.111.4, subclause 4.3.3:
+  - There will be no alternative linkset in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, subclause 4.4.3:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, subclause 4.5:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, subclause 4.6:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, subclause 4.7:
+  - Not applicable in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, clause 5:
+  - Changeover between link sets is not applicable in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, clause 6:
+  - Changeback between link sets is not applicable in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, clause 7:
+  - Forced re-routing is not applicable since there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, clause 8:
+
+- Not applicable since there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface.
+- ANSI T1.111.4, subclause 13.2:
+  - The transfer prohibited function is not applicable if the SGSN does not support STP functionality. At the reception of a TFP message, the SGSN or VLR acting as SP shall process the message.
+- ANSI T1.111.4, subclause 13.3:
+  - The transfer allowed function is not applicable if the SGSN does not support STP functionality. At the reception of a TFA-message, the SGSN or VLR acting as SP shall process the message.
+- ANSI T1.111.4, subclause 13.4:
+  - The transfer restricted function is not applicable if the SGSN does not support STP functionality. At the reception of the TFR message the SGSN or VLR acting as SP shall process the message.
+- ANSI T1.111.4, subclause 13.5:
+  - The signalling-route-set-test procedure is not applicable.
+- ANSI T1.111.4, subclauses 13.6, 13.7 and 13.8:
+  - The transfer controlled function is not applicable if the SGSN does not support STP functionality. At the reception of TFC message, the SGSN or VLR acting as SP shall process the message.
+- ANSI T1.111.4, subclause 13.9:
+  - The signalling route-set-congestion-test function is not applicable. At the reception of signalling-route-set-congestion-test message no action is taken by the receiving entity.
+
+#### 5.4.2.3 Informative clauses
+
+A list of clarifications to ANSI Recommendation T1.111.4 are listed below.
+
+- ANSI T1.111.4, subclause 2.3.4:
+  - The load sharing procedures shall allow any value of the SLS field in the MTP3 network management messages that are not related to a specific signalling link or a default value of 00000000 should be used.
+- ANSI T1.111.4, subclause 3.4.1:
+  - For point to point working, the signalling route will become unavailable when the associated link set fails.
+- ANSI T1.111.4, subclause 3.4.2:
+  - For point to point working, the signalling route will become available when the associated link set is restored.
+- ANSI T1.111.4, subclause 3.5.1:
+  - For point to point working, the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ANSI Recommendation T1.111.4 subclause 11.2.1.
+- ANSI T1.111.4, subclause 3.5.2:
+  - For point to point working, the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ANSI Recommendation T1.111.4 subclause 11.2.2.
+- ANSI T1.111.4, clause 9:
+  - The SGSN and the MSC/VLR shall implement the restart procedures specified in ANSI T1.111.4.
+- ANSI T1.111.4, clause 11:
+  - For point to point working, the signalling route set will consist of one associated signalling route only.
+
+# 6 Conformance to SCCP
+
+## 6.1 Overview
+
+The purpose of this clause is to identify the subset of the SCCP functions which are necessary to provide addressing, error detection and segmentation facilities in the Gs interface. If this subset of SCCP functions is implemented, compatibility with a full ITU-T or ANSI SCCP shall be maintained. Only the needs of the user of SCCP (refer to 3GPP TS 29.018) are taken into account in this clause: the operations and maintenance requirements about SCCP functions are outside the scope of the present document.
+
+No SCCP translation function is required in the VLR or the SGSN between the national and the local MTP. The Destination Point Code and Subsystem Number would allow direct routing by the local SCCP and MTP. Global Title addressing is supported on the Gs interface to provide flexibility in the addressing scheme implementation (note that the SGSN is assigned a global title in order to communicate with an HLR across an inter PLMN boundary).
+
+Only connectionless class 0 SCCP services are used on the Gs interface. These simplifications are applicable to the signalling between an SGSN and a VLR in GSM PLMNs.
+
+The minimum set of SCCP functions which apply are specified in the ITU-T Recommendations Q.711, Q.712, Q.713 and Q.714, for E1 interface and ANSI T1.112 for T1 interface with the qualifications specified in this Recommendation.
+
+## 6.2 SCCP Primitives
+
+### 6.2.1 SCCP Primitives for E1 Interface (ITU Recommendation Q.711)
+
+- ITU-T Recommendation Q.711, clause 1:
+  - No SCCP connection-oriented services are used.
+- ITU-T Recommendation Q.711, clause 2:
+  - No SCCP connection-oriented services are used. Only connectionless class 0 is used.
+- ITU-T Recommendation Q.711, subclause 2.1:
+  - Not applicable.
+- ITU-T Recommendation Q.711, subclause 4.1:
+  - Connection-oriented functions are not applicable
+
+### 6.2.2 SCCP Primitives for T1 Interface (ANSI Standards T1.112.1)
+
+- ANSI T1.112.1, clause 1:
+  - No SCCP connection-oriented services are used.
+- ANSI T1.112.1, clause 2:
+  - No SCCP connection-oriented services are used. Only connectionless class 0.
+- ANSI T1.112.1, subclause 2.1:
+  - Not applicable.
+- ANSI T1.112.1, subclause 4.1:
+  - Connection-oriented functions are not applicable.
+
+## 6.3 SCCP messages
+
+### 6.3.1 SCCP messages for E1 Interface (ITU Recommendation Q.712)
+
+- ITU-T Recommendation Q.712, subclauses 1.1 to 1.14:
+  - Messages not used.
+- ITU-T Recommendation Q.712, subclause 1.16:
+  - The Subsystem-Out-Of-Service-Grant (SOG) message is not used.
+- ITU-T Recommendation Q.712, subclause 1.17:
+  - The Subsystem-Out-Of-Service-Request (SOR) message is not used.
+- ITU-T Recommendation Q.712, subclauses 2.4, 2.6, 2.7, 2.9, 2.11, 2.12, 2.13, 2.14, 2.16 and 2.17:
+  - Parameters not used.
+
+### 6.3.2 SCCP messages for T1 Interface (ANSI Standards T1.112.2)
+
+- ANSI T1.112.2, subclauses 2.1 to 2.14:
+  - Messages not used.
+- ANSI T1.112.2, subclause 3.4:
+  - The Subsystem-Out-Of-Service-Request (SOR) message is not used.
+- ANSI T1.112.2, subclause 3.5:
+  - The Subsystem-Out-Of-Service-Grant (SOG) message is not used.
+- ANSI T1.112.2, subclause 3.6:
+  - The Subsystem-Backup Routing (SBR) (Optional) message is not used.
+- ANSI T1.112.2, subclause 3.7:
+  - The Subsystem-Normal Routing (SNR) (Optional) message is not used.
+- ANSI T1.112.2, subclause 3.8:
+  - The Subsystem-Routing Status Test (SRT) (Optional) message is not used.
+- ANSI T1.112.2, subclauses 4.2, 4.4, 4.6, 4.7, 4.10, 4.11, 4.12, 4.13, 4.15, 4.16, 4.17, 4.18 and 4.19:
+  - Parameters not used.
+
+## 6.4 SCCP formats and codes
+
+### 6.4.1 SCCP format and codes for E1 Interface (ITU Recommendation Q.713)
+
+- ITU-T Recommendation Q.713, subclause 3.4:
+  - The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific.
+- ITU-T Recommendation Q.713, subclause 3.4.2.2:
+  - SSN value:
+    - This is a national network concern. Different SSN values can be allocated for SGSN and VLR.
+- ITU-T Recommendation Q.713, subclause 3.5:
+  - The calling party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific.
+- ITU-T Recommendation Q.713, subclause 3.6:
+  - Protocol class: the classes 1, 2 and 3 are not used.
+- ITU-T Recommendation Q.713, subclauses 3.7 3.8, 3.9, 3.10, 3.11, 3.13, 3.14 and 3.15:
+  - Parameters not used.
+- ITU-T Recommendation Q.713, subclauses 4.2 to 4.9 and 4.12 to 4.17:
+  - Messages not used.
+- ITU-T Recommendation Q.713, subclause 5.1.1:
+  - SOR and SOG not needed.
+
+### 6.4.2 SCCP format and codes for T1 Interface (ANSI Standards T1.112.3)
+
+- ANSI T1.112.3, subclause 3.4:
+  - The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific.
+- ANSI T1.112.3, subclause 3.4.2.1:
+  - The SSN values are a national network concern. Different SSN values can be allocated for SGSN and VLR.
+- ANSI T1.112.3, subclause 3.5:
+  - The calling party address shall include the appropriate sub-system number. All other aspects of SCCP addressing are network specific.
+- ANSI T1.112.3, subclause 3.6:
+  - Protocol class: the classes 2 and 3 are not used.
+- ANSI T1.112.3, subclauses 3.7, 3.8, 3.9, 3.10, 3.11, 3.13, 3.14 and 3.15:
+  - Parameters not used.
+- ANSI T1.112.3, subclauses 4.2 to 4.9 and 4.12 to 4.17:
+  - Messages not used.
+
+- ANSI T1.112.3, subclause 5.1.1:
+  - SOR, SNR, SRT, SBR, and SOG not needed.
+
+## 6.5 SCCP procedures
+
+### 6.5.1 SCCP procedures for E1 Interface (ITU Recommendation Q.714)
+
+- ITU-T Recommendation Q.714, subclauses 1.1.2 and 1.1.3:
+  - Protocol classes 2 and 3 not used.
+  - Connection-oriented services are not used.
+- ITU-T Recommendation Q.714, subclause 1.2:
+  - Connection-oriented services are not used.
+- ITU-T Recommendation Q.714, subclause 1.3:
+  - Protocol class 1 not used.
+- ITU-T Recommendation Q.714, subclause 2.1:
+  - The two basic categories of addresses for connectionless messages are used.
+- ITU-T Recommendation Q.714, subclause 2.2 and 2.3:
+  - No connection-oriented message is used.
+- ITU-T Recommendation Q.714, clause 3:
+  - Connection-oriented procedures are not used.
+- ITU-T Recommendation Q.714, clause 5:
+  - Only those messages and procedures relating to non-replicated subsystems or nodes are required.
+
+### 6.5.2 SCCP procedures for T1 Interface (ANSI Standards T1.112.4)
+
+- ANSI T1.112.4, subclauses 1.1.2 and 1.1.3:
+  - Protocol classes 2 and 3 not used.
+  - Connection-oriented services are not used.
+- ANSI T1.112.4, subclause 1.2:
+  - Connection-oriented services are not used.
+- ANSI T1.112.4, subclause 1.3:
+  - Protocol class 1 is not used.
+- ANSI T1.112.4, subclause 2.1:
+  - The two basic categories of addresses for connectionless messages are used.
+- ANSI T1.112.4, subclause 2.2 and 2.3:
+  - No connection-oriented message is used.
+- ANSI T1.112.4, clause 3:
+  - Connection-oriented procedures not used.
+
+- ANSI T1.112.4, clause 5:
+  - Only those messages and procedures relating to non-replicated subsystems or nodes are required.
+
+# --- 7 Use of the SCCP (E1/T1 Interface)
+
+The underlying transport stack and the SCCP are used to support signalling messages between the SGSN and the MSC. The BSSAP+ protocol specified in 3GPP TS 29.018 is the user of the SCCP. 3GPP TS 29.018 only uses the services of the class 0 of the SCCP.
+
+The Gs interface connects an SGSN to a VLR within the same PLMN. The use of point codes or global titles is allowed for routing of SCCP messages.
+
+The format and coding of address parameters carried by the SCCP for routing purpose shall comply with ITU-T Recommendation Q.713 for E1 interface and ANSI T1.112.3 T1 interface with the following restrictions:
+
+- The called party address shall include:
+  - an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface);
+  - all other aspects of the SCCP signalling are specified in 3GPP TS 29.002.
+- The calling party address shall include:
+  - an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface);
+  - all other aspects of the SCCP signalling are specified in 3GPP TS 29.002.
+
+When an SCCP message is sent, the Called Party Address is derived from the Called Address of the N-UNITDATA-REQUEST primitive issued by the local SCCP user.
+
+When an SCCP message is received, the Calling Address within the N-UNITDATA-INDICATION primitive is derived from the Calling Party Address of the SCCP UNITDATA message received.
+
+Only address information belonging to the E.164 numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. The SGSN and the VLR store the address of the other entity using the format received in the Calling Party Address field or the address information received in the application part of the message.

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

@@ -0,0 +1,431 @@
+
+
+# 3GPP TS 29.108 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Application of the Radio Access Network Application Part (RANAP) on the E-interface (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 'P', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+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 Abbreviations .....                                                                                            | 5         |
+| 4 Principles for the use of RANAP on the E-interface .....                                                       | 6         |
+| 4.1 General .....                                                                                                | 6         |
+| 4.2 Transfer of RANAP layer 3 messages on the E-interface.....                                                   | 6         |
+| 4.3 Roles of 3G_MSC-A, 3G_MSC-I and 3G_MSC-T .....                                                               | 6         |
+| 5 Use of the RANAP on the E-interface .....                                                                      | 7         |
+| 5.1 RAB Assignment.....                                                                                          | 7         |
+| 5.2 RAB Release Request .....                                                                                    | 7         |
+| 5.3 Iu Release Request .....                                                                                     | 8         |
+| 5.4 Relocation Resource Allocation.....                                                                          | 8         |
+| 5.5 Relocation Cancel .....                                                                                      | 8         |
+| 5.6 Relocation Detect and Relocation Complete .....                                                              | 8         |
+| 5.7 CN Trace invocation .....                                                                                    | 9         |
+| 5.8 Security mode control .....                                                                                  | 9         |
+| 5.9 Location Reporting Control .....                                                                             | 9         |
+| 5.10 Location Report.....                                                                                        | 9         |
+| 5.11 Direct Transfer .....                                                                                       | 9         |
+| 5.12 Error Indication .....                                                                                      | 10        |
+| 5.13 CN Deactivate Trace .....                                                                                   | 10        |
+| 5.14 Common ID.....                                                                                              | 10        |
+| 5.15 Location Related Data.....                                                                                  | 10        |
+| 5.16 UE Specific Information .....                                                                               | 10        |
+| 5.17 RAB Modification Request.....                                                                               | 10        |
+| 6 RANAP messages transferred on the E-interface .....                                                            | 11        |
+| 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface ..... | 12        |
+| 7.1 Message Contents.....                                                                                        | 12        |
+| 8 RANAP message error handling when transferred on the E-interface .....                                         | 12        |
+| <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 describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413 [4], which is used on the E-interface. A general description can be found in 3GPP TS 23.002 [7] and 3GPP TS 23.009 [2].
+
+For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G\_MSC.
+
+# --- 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".
+- [2] 3GPP TS 23.009: "Handover procedures".
+- [3] Void
+- [4] 3GPP TS 25.413: "UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling".
+- [5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [6] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP)".
+- [7] 3GPP TS 23.002: "Network architecture".
+- [8] Void
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the abbreviations defined in TR 21.905 [1] and the following apply:
+
+|           |                                                                                                                        |
+|-----------|------------------------------------------------------------------------------------------------------------------------|
+| 3G_MSC    | A third generation Mobile services Switching Centre that supports the Iu interface (and possibly also the A-interface) |
+| 3G_MSC-A  | The controlling 3G_MSC on which the call was originally established                                                    |
+| 3G_MSC-B  | The 3G_MSC to which the UE is handed over in a Basic Handover                                                          |
+| 3G_MSC-B' | The 3G_MSC to which the UE is handed over in a Subsequent Handover                                                     |
+| 3G_MSC-I  | Interworking 3G_MSC                                                                                                    |
+| 3G_MSC-T  | Target 3G_MSC                                                                                                          |
+| EP        | Elementary Procedure                                                                                                   |
+| NNSF      | NAS Node Selection Function                                                                                            |
+| RNC       | Radio Network Controller                                                                                               |
+
+# 4 Principles for the use of RANAP on the E-interface
+
+## 4.1 General
+
+The mechanism for the transfer of the RANAP messages on the E-interface is defined in TS 29.002 [5]. The operation of the relocation procedures between 3G\_MSCs and the use of the RANAP messages for those procedures is described in TS 23.009 [2] and TS 29.010 [6].
+
+RANAP is defined to connect the RNS to both, the cs and ps domain of an UMTS CN. Procedures, messages and IEs, only defined for communication between the RNS and the ps domain of an UMTS CN will, of course, never appear on the E-interface.
+
+In the same way as a the connection oriented service of SCCP is used for the messages relating to one UE on the 3G\_MSC-RNS interface a TCAP dialogue is used on the E-interface for messages relating to one UE. As no correspondence to the connectionless service on the 3G\_MSC-RNS interface is used on the E-interface none of the global procedures are applicable.
+
+The management of the terrestrial circuits between the 3G\_MSCs is outside the scope of the E-interface (see TS 23.009 [2]), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the RANAP procedures and messages used on the E-interface.
+
+## 4.2 Transfer of RANAP layer 3 messages on the E-interface
+
+The RANAP data which on the 3G\_MSC-RNS interface is contained in the user data field of the exchanged SCCP frames is on the E-interface transferred as the contents of the access network signalling info in the AN-APDU parameter as described in TS 29.002 [5], indicating the access network protocol identification "ts3G-25413".
+
+## 4.3 Roles of 3G\_MSC-A, 3G\_MSC-I and 3G\_MSC-T
+
+For the description in the present document, the 3G\_MSC's functionality related to the relocation between 3G\_MSCs has been split into three logical parts, 3G\_MSC-A, 3G\_MSC-T and 3G\_MSC-I. The different roles need not necessarily be performed by different 3G\_MSCs.
+
+3G\_MSC-A is the call/connection controlling part of the 3G\_MSC where the call/connection was originally established and the switching point for relocation between 3G\_MSCs. (This corresponds to 3G\_MSC-A as defined in TS 23.009 [2] and TS 29.002 [5]). The 3G\_MSC that is the 3G\_MSC-A will not be changed during the duration of a call/connection.
+
+3G\_MSC-T is the part relating to the transitory state during the relocation for the 3G\_MSC controlling the RNS the serving RNS functionality is relocated to, when basic relocation or subsequent relocation (see TS 23.009) take place. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]).
+
+3G\_MSC-I is the part of a 3G\_MSC through which the 3G\_MSC-A, via an E-interface (or an internal interface) is in contact with the UE. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]).
+
+The 3G\_MSC that is the 3G\_MSC-A can also have the role of either the 3G\_MSC-I or the 3G\_MSC-T during a period of the call/connection.
+
+The following is applicable for the involved 3G\_MSCs concerning the exchange of RANAP data on an E-interface before and after a successful inter 3G\_MSC relocation:
+
+- 1) At basic relocation, two 3G\_MSCs are involved, one 3G\_MSC being 3G\_MSC-A and one being 3G\_MSC-T. When this relocation has been performed, the two 3G\_MSCs interworking on the E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I.
+- 2) At subsequent relocation back to 3G\_MSC-A, two 3G\_MSCs are involved. The 3G\_MSC having the role of 3G\_MSC-A has also the role of 3G\_MSC-T. The other 3G\_MSC involved has the role of 3G\_MSC-I. When this
+
+relocation has been completed, there is no exchange of RANAP data on the E-interface, i.e. the 3G\_MSC being the 3G\_MSC-I before and during the relocation is now no longer taking part.
+
+- 3) At subsequent relocation of SRNS to an 3G\_MSC not being 3G\_MSC-A, three 3G\_MSCs are involved. The roles of these 3G\_MSCs are 3G\_MSC-A, 3G\_MSC-I, and 3G\_MSC-T respectively. When this relocation has been performed, the two 3G\_MSCs interworking on an E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I and the 3G\_MSC being 3G\_MSC-I during the relocation is now no longer taking part.
+
+# --- 5 Use of the RANAP on the E-interface
+
+The dedicated RANAP procedures used on the E-interface to some extent are:
+
+- RAB assignment;
+- RAB Release Request;
+- Iu Release Request;
+- Relocation resource allocation;
+- Relocation Detect;
+- Relocation Complete;
+- Relocation Cancel;
+- CN Invoke Trace;
+- Security mode control;
+- Location Reporting Control;
+- Location Report;
+- Direct Transfer;
+- Error Indication;
+- Common ID;
+- Location Related Data;
+- UE Specific Information;
+- RAB Modification Request.
+
+## 5.1 RAB Assignment
+
+The RAB Assignment procedure (TS 25.413 [4] subclause 8.2) is applied on the E-interface with following conditions:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-I.
+
+## 5.2 RAB Release Request
+
+For the RAB Release Request procedure (TS 25.413 [4] subclauses 8.3) the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-I acts as the RNS;
+- the 3G\_MSC-A acts as the 3G\_MSC.
+
+## 5.3 Iu Release Request
+
+For the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-I acts as the RNS;
+- the 3G\_MSC-A acts as the 3G\_MSC.
+
+Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) is applied on the E-interface with the following conditions:
+
+- the 3G\_MSC-T acts as the RNS;
+- the 3G\_MSC-A acts as the 3G\_MSC.
+
+## 5.4 Relocation Resource Allocation
+
+At basic Inter-3G\_MSC relocation (TS 23.009 [2]) the Relocation Resource Allocation procedure (TS 25.413 [4] subclause 8.7) is applied on the E-interface with the following conditions:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-T acts as the target RNS.
+
+At subsequent Inter-3G\_MSC relocation the Relocation Resource Allocation procedure is applied on the E-interface with the following conditions:
+
+- the 3G\_MSC-I acts as the 3G\_MSC;
+- the 3G\_MSC-T acts as the target RNS;
+- if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, then this 3G\_MSC shall act as the target RNS towards the 3G\_MSC-I and as the 3G\_MSC towards the 3G\_MSC-T.
+
+The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-T.
+
+In case NNSF is active, the *Iu Signalling Connection Identifier* IE and the *Global CN ID* IE shall be set by the 3G\_MSC-T towards Target RNC.
+
+## 5.5 Relocation Cancel
+
+For subsequent Inter-3G\_MSC relocation the Relocation Cancel procedure (TS 25.413 [4] subclause 8.10) is applied on the E-interface with the following conditions.
+
+- the 3G\_MSC-A, acts as the 3G\_MSC;
+- the 3G\_MSC-I, acts as the serving RNS.
+
+## 5.6 Relocation Detect and Relocation Complete
+
+For the Relocation Detect and Relocation Complete procedure (TS 25.413 [4] subclauses 8.8 and 8.9) the applicable parts on the E-interface are the transfer of RELOCATION DETECT, RELOCATION COMPLETE messages at inter 3G\_MSC relocation. For those parts, the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+
+- the 3G\_MSC-T acts as the target RNS.
+
+## 5.7 CN Trace invocation
+
+For the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17) is applied on the E-interface with the following conditions:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-T acts as the RNS.
+
+## 5.8 Security mode control
+
+For the Security mode control procedure (TS 25.413 [4], subclause 8.18), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.9 Location Reporting Control
+
+For the Location Reporting Control procedure (TS 25.413 [4], subclause 8.19), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (3GPP TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Location Reporting Control procedure (TS 25.413 [4] subclause 8.19) is applied on the E-interface with the following conditions:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-T acts as the RNS.
+
+## 5.10 Location Report
+
+For the Location Report procedure (TS 25.413 [4], subclause 8.20), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.11 Direct Transfer
+
+For the Direct Transfer procedure (TS 25.413 [4], subclause 8.23), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.12 Error Indication
+
+For the Error Indication procedure (TS 25.413 [4], subclause 8.27), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.13 CN Deactivate Trace
+
+For the CN Deactivate Trace procedure procedure (TS 25.413 [4], subclause 8.28), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.14 Common ID
+
+For the Common ID procedure (TS 25.413 [4], subclause 8.16), the involved 3G MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.15 Location Related Data
+
+For the Location Related Data procedure (TS 25.413 [4], subclause 8.31), the involved 3G\_MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.16 UE Specific Information
+
+For the UE Specific Information procedure (TS 25.413 [4], subclause 8.33), the involved 3G MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+## 5.17 RAB Modification Request
+
+For the RAB Modification Request procedure (TS 25.413 [4], subclause 8.30), the involved 3G MSCs shall act according to the following:
+
+- the 3G\_MSC-A acts as the 3G\_MSC;
+- the 3G\_MSC-I acts as the RNS.
+
+# 6 RANAP messages transferred on the E-interface
+
+The list given below shows the RANAP messages, defined in TS 25.413 [4] subclause 9.1(tabular format) and 9.3 (ASN.1 notation) that are transferred on the E-interface.
+
+|                                    |                                                 |
+|------------------------------------|-------------------------------------------------|
+| RAB ASSIGNMENT REQUEST             | (3G_MSC-A -> 3G_MSC-I)                          |
+| RAB ASSIGNMENT RESPONSE            | (3G_MSC-I -> 3G_MSC-A)                          |
+| RAB RELEASE REQUEST                | (3G_MSC-I -> 3G_MSC-A)                          |
+| IU RELEASE REQUEST                 | (3G_MSC-I -> 3G_MSC-A and 3G_MSC-T -> 3G_MSC-A) |
+| * RELOCATION REQUEST               | (3G_MSC-A -> 3G_MSC-T and 3G_MSC-I -> 3G_MSC-A) |
+| * RELOCATION REQUEST ACKNOWLEDGE   | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) |
+| * RELOCATION DETECT                | (3G_MSC-T -> 3G_MSC-A)                          |
+| * RELOCATION COMPLETE              | (3G_MSC-T -> 3G_MSC-A)                          |
+| * RELOCATION FAILURE               | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) |
+| * RELOCATION CANCEL                | (3G_MSC-I -> 3G_MSC-A)                          |
+| * RELOCATION CANCEL ACKNOWLEDGE    | (3G_MSC-A -> 3G_MSC-I)                          |
+| # CN INVOKE TRACE                  | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) |
+| SECURITY MODE COMMAND              | (3G_MSC-A -> 3G_MSC-I)                          |
+| SECURITY MODE COMPLETE             | (3G_MSC-I -> 3G_MSC-A)                          |
+| SECURITY MODE REJECT               | (3G_MSC-I -> 3G_MSC-A)                          |
+| LOCATION REPORTING CONTROL         | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) |
+| LOCATION REPORT                    | (3G_MSC-I -> 3G_MSC-A)                          |
+| DIRECT TRANSFER                    | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) |
+| ERROR INDICATION                   | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) |
+| # CN DEACTIVATE TRACE              | (3G_MSC-A -> 3G_MSC-I)                          |
+| COMMON ID                          | (3G_MSC-A -> 3G_MSC-I)                          |
+| LOCATION RELATED DATA REQUEST      | (3G_MSC-A -> 3G_MSC-I)                          |
+| LOCATION RELATED DATA RESPONSE     | (3G_MSC-I -> 3G_MSC-A)                          |
+| LOCATION RELATED DATA FAILURE      | (3G_MSC-I -> 3G_MSC-A)                          |
+| UE SPECIFIC INFORMATION INDICATION | (3G_MSC-A -> 3G_MSC-I)                          |
+| RAB MODIFY REQUEST                 | (3G_MSC-I -> 3G_MSC-A)                          |
+
+All other RANAP messages shall be considered as non-existent on the E-interface.
+
+Some of the messages above are qualified by \* or #. This indicates whether the message, when sent on the E interface, is considered as:
+
+- relocation related message (\*); or
+- trace related message (#).
+
+# --- 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface
+
+## 7.1 Message Contents
+
+For the applicable RANAP messages transferred on the E-interface the following exceptions to the descriptions in TS 25.413 [4] are valid:
+
+### RAB ASSIGNMENT REQUEST message
+
+- Transport Layer Address IE:
+  - if received, this IE shall be ignored;
+- Iu Transport Association IE:
+  - if received, this IE shall be ignored;
+- UP Mode Versions IE:
+  - the information given within this IE is only useful in case of TrFO.
+
+### RELOCATION REQUEST message
+
+- Transport Layer Address IE:
+  - if received, this IE shall be ignored;
+- Iu Transport Association IE:
+  - if received, this IE shall be ignored;
+- UP Mode Versions IE:
+  - the information given within this IE is only useful in case of TrFO;
+- Iu Signalling Connection Identifier IE:
+  - if received, this IE shall be ignored;
+- Global CN ID IE:
+  - if received, this IE shall be ignored.
+
+# --- 8 RANAP message error handling when transferred on the E-interface
+
+The RANAP error handling (TS 25.413 [4], clause 10) is applicable. The handling of faults concerning the use of SCCP is not applicable.
+
+The RANAP error messages sent on the E-interface shall only be sent as response to RANAP messages received on the same interface.

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

@@ -0,0 +1,344 @@
+
+
+# 3GPP TS 29.139 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP system - fixed broadband access network interworking; Home (e)Node B - security gateway interface (Release 18)**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a green signal icon consisting of three curved lines.
+
+LTE Advanced Pro logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo. It features the letters "3GPP" in a stylized, bold font. Below the "P" is a red signal icon consisting of three curved lines. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, uppercase 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.....                                                         | 5         |
+| 2 References.....                                                    | 5         |
+| 3 Definitions and abbreviations .....                                | 5         |
+| 3.1 Definitions.....                                                 | 5         |
+| 3.2 Abbreviations .....                                              | 6         |
+| 4 General.....                                                       | 6         |
+| 4.1 Protocol Stack .....                                             | 6         |
+| 4.1.1 Control Plane for H(e)NB – SeGW .....                          | 6         |
+| 4.1.2 User Plane for H(e)NB – SeGW .....                             | 7         |
+| 5 Supporting QoS.....                                                | 8         |
+| 5.1 General .....                                                    | 8         |
+| 5.2 H(e)NB procedures .....                                          | 8         |
+| 5.2.1 General .....                                                  | 8         |
+| 5.2.2 QCI mapping .....                                              | 8         |
+| 5.2.3 Reflective QoS.....                                            | 8         |
+| 5.3 SeGW procedures.....                                             | 8         |
+| 6 Tunnel Management .....                                            | 8         |
+| 6.1 General .....                                                    | 8         |
+| 6.2 H(e)NB procedures .....                                          | 9         |
+| 6.2.1 Tunnel establishment.....                                      | 9         |
+| 6.2.1.1 IP address allocation .....                                  | 9         |
+| 6.2.1.2 NAT Traversal .....                                          | 9         |
+| 6.2.1.3 H(e)NB NATed Tunnel-IP address discovery.....                | 9         |
+| 6.2.2 Tunnel modification .....                                      | 9         |
+| 6.2.3 Tunnel disconnection.....                                      | 9         |
+| 6.3 SeGW procedures.....                                             | 9         |
+| 6.3.1 Tunnel establishment.....                                      | 9         |
+| 6.3.1.1 IP address allocation .....                                  | 9         |
+| 6.3.1.2 NAT Traversal .....                                          | 10        |
+| 6.3.1.3 H(e)NB NATed Tunnel-IP address discovery.....                | 10        |
+| 6.3.2 Tunnel modification .....                                      | 10        |
+| 6.3.3 Tunnel disconnection.....                                      | 10        |
+| 7 PDUs and parameters specific to the present document.....          | 10        |
+| 7.1 IETF RFC coding information defined within present document..... | 10        |
+| 7.1.1 IKEv2 Configuration Payloads attributes.....                   | 10        |
+| 7.1.1.1 EXTERNAL_SOURCE_IP4_NAT_INFO attribute .....                 | 10        |
+| <b>Annex A (informative): Change history.....</b>                    | <b>12</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the H(e)NB – SeGW interface. The interface is used for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum. The interworking procedure provides the IP connectivity to a 3GPP UE using a H(e)NB connected to a Fixed Broadband Access network as specified in 3GPP TS 23.139 [2].
+
+The specification covers the QoS aspects and Tunnel management procedures.
+
+# --- 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.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 2".
+- [3] 3GPP TS 24.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 3".
+- [4] IETF RFC 2474 (December 1998): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [5] IETF RFC 5996: "Internet Key Exchange Protocol Version 2 (IKEv2)".
+- [6] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets".
+- [7] 3GPP TS 33.320: "Security of Home Node B (HNB) / Home evolved Node B (HeNB)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**H(e)NB Reflective QoS function:** H(e)NB Reflective QoS function is a H(e)NB function in order to support QoS for uplink traffic over a Fixed Broadband Access network as specified in 3GPP TS 23.139 [2].
+
+**H(e)NB local IP address Info:** H(e)NB local IP address Info is defined as either the public IPv4 address or IPv6 address assigned to the H(e)NB by the Fixed Broadband Access Network domain, or the public IPv4 address and the UDP port number used by the NATed RG that is used for this H(e)NB. The public IPv4 address used by the NATed RG is assigned by the Fixed Broadband Access Network domain.
+
+## 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].
+
+|        |                                    |
+|--------|------------------------------------|
+| DSCP   | Differentiated Services Code Point |
+| H(e)NB | Home (e)NodeB                      |
+| NAT    | Network Address Translation        |
+| NAT-T  | NAT Traversal                      |
+| SeGW   | Security Gateway                   |
+
+# 4 General
+
+## 4.1 Protocol Stack
+
+### 4.1.1 Control Plane for H(e)NB – SeGW
+
+![Protocol stack diagram for Control Plane for H(e)NB - SeGW Interface over IPv4 transport network. It shows three main components: H(e)NB, NAT, and SeGW. H(e)NB and SeGW have identical protocol stacks: IKEv2, UDP, IPv4, L2, L1. The NAT component is shown as a dashed box containing two parallel paths, each with UDP, IPv4, L2, and L1 layers. Lines connect the layers between H(e)NB and NAT, and between NAT and SeGW, showing the flow of the control plane traffic.](5d76c2e9976aaf97001ee189908830fb_img.jpg)
+
+Protocol stack diagram for Control Plane for H(e)NB - SeGW Interface over IPv4 transport network. It shows three main components: H(e)NB, NAT, and SeGW. H(e)NB and SeGW have identical protocol stacks: IKEv2, UDP, IPv4, L2, L1. The NAT component is shown as a dashed box containing two parallel paths, each with UDP, IPv4, L2, and L1 layers. Lines connect the layers between H(e)NB and NAT, and between NAT and SeGW, showing the flow of the control plane traffic.
+
+#### **Legend:**
+
+- **IKEv2 Protocol:** This protocol is used to between H(e)NB and SeGW. The IKEv2 protocol is defined in IETF RFC 5996 [5].
+
+**Figure 4.1.1-1: Control Plane for H(e)NB - SeGW Interface over IPv4 transport network**
+
+![Control Plane for H(e)NB - SeGW Interface over IPv6 transport network](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+This diagram illustrates the control plane protocol stack for the H(e)NB - SeGW interface over an IPv6 transport network. It shows two vertical protocol stacks, one for H(e)NB on the left and one for SeGW on the right, connected by horizontal lines representing the interface. Both stacks consist of five layers: IKEv2 at the top, followed by UDP, IPv6, L2, and L1 at the bottom. The layers are aligned across the interface.
+
+Control Plane for H(e)NB - SeGW Interface over IPv6 transport network
+
+##### **Legend:**
+
+- **IKEv2 Protocol:** This protocol is used to between H(e)NB and SeGW. The IKEv2 protocol is defined in RFC 5996 [5].
+
+**Figure 4.1.1-2: Control Plane for H(e)NB - SeGW Interface over IPv6 transport network**
+
+### 4.1.2 User Plane for H(e)NB – SeGW
+
+![User Plane for H(e)NB - SeGW Interface over IPv4 transport network](9791722d75115ddcc599b07d7bc35d73_img.jpg)
+
+This diagram illustrates the user plane protocol stack for the H(e)NB - SeGW interface over an IPv4 transport network. It shows two vertical protocol stacks, one for H(e)NB on the left and one for SeGW on the right, connected by a central NAT (Network Address Translation) block. The H(e)NB stack has five layers: Payload, IPsec, UDP, IPv4, L2, and L1. The SeGW stack also has five layers: Payload, IPsec, UDP, IPv4, L2, and L1. The NAT block, enclosed in a dashed box, contains two columns of four layers: UDP, IPv4, L2, and L1. The UDP layers in the H(e)NB and SeGW stacks are connected to the corresponding UDP layers in the NAT block.
+
+User Plane for H(e)NB - SeGW Interface over IPv4 transport network
+
+#### **Legend:**
+
+- **UDP:** UDP encapsulation is used if NAT is detected between the H(e)NB and the SeGW.
+
+**Figure 4.1.2-1: User Plane for H(e)NB - SeGW Interface over IPv4 transport network**
+
+![User Plane for H(e)NB - SeGW Interface over IPv6 transport network](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg)
+
+This diagram illustrates the user plane protocol stack for the H(e)NB - SeGW interface over an IPv6 transport network. It shows two vertical protocol stacks, one for H(e)NB on the left and one for SeGW on the right, connected by horizontal lines representing the interface. Both stacks consist of five layers: Payload at the top, followed by IPsec, IPv6, L2, and L1 at the bottom. The layers are aligned across the interface.
+
+User Plane for H(e)NB - SeGW Interface over IPv6 transport network
+
+**Figure 4.1.2-2: User Plane for H(e)NB - SeGW Interface over IPv6 transport network**
+
+# --- 5 Supporting QoS
+
+## 5.1 General
+
+At interworking with a Fixed Broadband Access network, QoS is provided by DSCP marking as specified in IETF RFC 2474 [4].
+
+## 5.2 H(e)NB procedures
+
+### 5.2.1 General
+
+The H(e)NB shall support DSCP marking on the IPsec header when forwarding the UE uplink traffic.
+
+Based on H(e)NB configuration either the QCI mapping or the Reflective QoS may be used.
+
+### 5.2.2 QCI mapping
+
+The QCI mapping table contains a one-to-one mapping from QCI value to DSCP marking value. The QCI mapping table is configured in the H(e)NB by the operator.
+
+When forwarding an uplink IP packet, the H(e)NB shall perform a lookup in the QCI mapping table based on the QCI value of the EPS bearer/PDP context before the IPsec tunnel encapsulation. The H(e)NB shall set the DSCP marking value of the IPsec header according to the matched QCI mapping table entry.
+
+### 5.2.3 Reflective QoS
+
+To support the H(e)NB Reflective QoS function for uplink traffic, the H(e)NB shall create and maintain the uplink DSCP marking rules for each active PDN connection as specified for UE Reflective QoS function in 3GPP TS 24.139 [3].
+
+When forwarding an uplink IP packet, the H(e)NB shall perform a lookup in the DSCP marking table based on the n-tuple of the IP header before the IPsec tunnel encapsulation. If a matching entry is found, the H(e)NB shall set the DSCP marking value of the IPsec header according to the matched DSCP marking rule. If no matching entry is found, the H(e)NB shall copy the DSCP field of the outer IP header into the IPsec header before forwarding to the SeGW.
+
+## 5.3 SeGW procedures
+
+When receiving a downlink data packet, the SeGW shall copy the DSCP marking value from the outer IP header into the IPsec header before forwarding to the H(e)NB using the IPsec tunnel, as specified in 3GPP TR 23.139 [2].
+
+# --- 6 Tunnel Management
+
+## 6.1 General
+
+The tunnel is an IPsec tunnel established via an IKEv2 protocol exchange IETF RFC 5996 [5] between the H(e)NB and the SeGW which is through the Fixed Broadband Access Network.
+
+In an IPv4 Fixed Broadband Access Network, NAT can be deployed between the H(e)NB and the SeGW, e.g. in a Residence Gateway. A H(e)NB behind the NAT shall invoke the NAT traversal procedure for IKEv2. The IPsec tunnel is encapsulated over UDP in the Tunnel-Mode as specified in IETF RFC 5996 [5].
+
+## 6.2 H(e)NB procedures
+
+### 6.2.1 Tunnel establishment
+
+#### 6.2.1.1 IP address allocation
+
+The SeGW shall provide the IP address to the H(e)NB for the communication with the EPC network.
+
+For dynamic IP address allocation, the H(e)NB shall include the requested IP address type (IPv4 address or IPv6 address) that needs to be configured in an IKEv2 CFG\_REQUEST Configuration Payload in the IKE\_AUTH request message as defined in IETF RFC 5996 [5] after reception of the IKE\_SA\_INIT response from the SeGW.
+
+#### 6.2.1.2 NAT Traversal
+
+NAT can be deployed in an IPv4 Fixed Broadband Access Network. IKEv2 NAT Traversal specified in section 2.23 of IETF RFC 5996 [5] shall be supported by H(e)NB.
+
+If NAT is detected between the H(e)NB and SeGW, the following procedures shall be performed:
+
+- UDP-Encapsulated ESP as defined in IETF RFC 5996 [5];
+- sending the NAT-keepalive packet to keep NAT mapping alive if no other packet to the SeGW has been sent in M seconds as defined in the IETF RFC 3948 [6];
+
+NOTE: M is a locally configurable parameter with a default value of 20 seconds as defined in the IETF RFC 3948 [6].
+
+#### 6.2.1.3 H(e)NB NATed Tunnel-IP address discovery
+
+If NAT is detected between the H(e)NB and SeGW, the H(e)NB shall request the SeGW to return the H(e)NB local IP address information by including the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as defined in subclause 7.1.1.1 in the CFG\_REQUEST Configuration Payload within the IKE\_AUTH request message. The length field of the attribute shall be set to zero. The NATed IPv4 Address field and UDP Port number field shall be absent.
+
+If the H(e)NB subsequently receives the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute in the CFG\_REPLY configuration payload from the SeGW, the H(e)NB shall report the IP address received in EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as the H(e)NB local IP address to the MME/SGSN.
+
+### 6.2.2 Tunnel modification
+
+NAT mappings can change when the UDP port number is reassigned by the NAT, and/or H(e)NB local IP address is reallocated due to NAT restart.
+
+Upon NAT remapping, the SeGW initiates the tunnel disconnection procedure as specified in subclause 6.3.3. Then the H(e)NB shall re-initiate the tunnel establishment procedure as specified in sub-clause 6.2.1.
+
+### 6.2.3 Tunnel disconnection
+
+The H(e)NB shall use the procedures defined in IETF RFC 5996 [5] to disconnect an IPsec tunnel to the SeGW.
+
+## 6.3 SeGW procedures
+
+### 6.3.1 Tunnel establishment
+
+#### 6.3.1.1 IP address allocation
+
+For dynamic IP address allocation, upon receipt of an IKE\_AUTH request message from the H(e)NB requesting the IP address, the SeGW shall include the remote IP address information in the IKEv2 Configuration Payload (CFG\_REPLY)
+
+of the final IKE\_AUTH response message to the H(e)NB. The SeGW shall assign either an IPv4 or an IPv6 address to the H(e)NB via a single CFG\_REPLY Configuration Payload.
+
+#### 6.3.1.2 NAT Traversal
+
+NAT can be deployed in an IPv4 Fixed Broadband Access Network. IKEv2 NAT Traversal specified in section 2.23 of IETF RFC 5996 [5] shall be supported by SeGW.
+
+If NAT is detected between the H(e)NB and SeGW, the SeGW shall use UDP-Encapsulated ESP as defined in IETF RFC 5996 [5].
+
+#### 6.3.1.3 H(e)NB NATed Tunnel-IP address discovery
+
+If the SeGW receives the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as defined in subclause 7.1.1.1 in the CFG\_REQUEST configuration payload within IKE\_AUTH request message, the SeGW shall provide the H(e)NB local IP address information (i.e. NATed IPv4 address and UDP port number) to the H(e)NB by including the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute in the CFG\_REPLY configuration payload within the IKE\_AUTH response message.
+
+### 6.3.2 Tunnel modification
+
+NAT mappings can change when the UDP port number is reassigned by the NAT, and/or H(e)NB local IP address is reallocated due to NAT restart.
+
+If NAT remapping is detected by the SeGW, the SeGW shall initiate the tunnel disconnection procedure (see subclause 6.3.3).
+
+NOTE: No procedures are defined in current release of specification to enable the SeGW to send the modified H(e)NB local IP address information to the H(e)NB during the lifetime of IKEv2 security association.
+
+### 6.3.3 Tunnel disconnection
+
+The SeGW shall use the procedures defined in IETF RFC 5996 [5] to disconnect an IPsec tunnel to the H(e)NB.
+
+# --- 7 PDUs and parameters specific to the present document
+
+## 7.1 IETF RFC coding information defined within present document
+
+### 7.1.1 IKEv2 Configuration Payloads attributes
+
+#### 7.1.1.1 EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute
+
+The format of the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute follows the definition of Configuration Attributes as specified in IETF RFC 5996 [5], section 3.15.1. The format is shown in figure 7.1.1.1-1 as below. The length of the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute is 0 or 6 bytes.
+
+| 7                  | 6              | 5 | 4 | 3 | 2 | 1 | 0 | Octets |  |  |  |  |  |  |  |
+|--------------------|----------------|---|---|---|---|---|---|--------|--|--|--|--|--|--|--|
+| R                  | Attribute Type |   |   |   |   |   |   | 1      |  |  |  |  |  |  |  |
+| Attribute Type     |                |   |   |   |   |   |   | 2      |  |  |  |  |  |  |  |
+| Length             |                |   |   |   |   |   |   | 3, 4   |  |  |  |  |  |  |  |
+| NATed IPv4 Address |                |   |   |   |   |   |   | 5 - 8  |  |  |  |  |  |  |  |
+| UDP Port number    |                |   |   |   |   |   |   | 9 - 10 |  |  |  |  |  |  |  |
+
+**Figure 7.1.1.1-1: EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute**
+
+The R bit in the first octet is as defined in IETF RFC 5996 [5].
+
+The Attribute Type indicating EXTERNAL\_SOURCE\_IP4\_NAT\_INFO is of the value 23.