Add files using upload-large-folder tool

marked/Rel-18/23_series/23011/raw.md

@@ -0,0 +1,664 @@
+
+
+# 3GPP TS 23.011 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Technical realization of Supplementary Services (Release 18)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold, black font. The '3' is on the left, 'G' is in the middle, 'P' is on the right, and 'P' is slightly overlapping the 'G'. A small red signal icon is located below the 'G'.
+
+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.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                                           |           |
+|-------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                            | 4         |
+| 1 Scope.....                                                                              | 5         |
+| 1.1 References .....                                                                      | 5         |
+| 1.2 Abbreviations .....                                                                   | 6         |
+| 2 Activation, deactivation, registration, erasure, interrogation and invocation .....     | 6         |
+| 2.1 General .....                                                                         | 6         |
+| 2.1.1 Definition of "state vectors" .....                                                 | 7         |
+| 2.1.2 Handling of service states at the HLR.....                                          | 8         |
+| 2.1.2.1 Encoding of SS-Status .....                                                       | 8         |
+| 2.1.2.2 Invocation of services at the HLR .....                                           | 8         |
+| 2.1.3 Handling of SS-Status at the VLR or the SGSN .....                                  | 9         |
+| 2.1.3.1 Invocation of services at the VLR or the SGSN .....                               | 9         |
+| 2.1.3.2 Interrogation of the service at the VLR and notifications from VLR.....           | 9         |
+| 2.1.4 Handling of SS-Status at the MS.....                                                | 9         |
+| 2.2 Handling of call independent SS procedures with respect to basic service groups ..... | 9         |
+| 2.3 Exceptional handling of basic service codes.....                                      | 10        |
+| 3 Password handling .....                                                                 | 14        |
+| 3.1 General .....                                                                         | 14        |
+| 3.2 Registration of password.....                                                         | 20        |
+| 3.3 Use of password .....                                                                 | 20        |
+| 3.4 Deactivation .....                                                                    | 22        |
+| 4 Supplementary service data management.....                                              | 23        |
+| 5 Format of description .....                                                             | 23        |
+| <b>Annex A (informative): Change history.....</b>                                         | <b>24</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document describes the general aspects on how supplementary 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 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 general aspects on how supplementary services in the 3GPP system are realised from a technical point of view.
+
+Description of technical realisation for specific supplementary services can be found in 3GPP TS 23.072, 230.8x and 230.9x-series technical specifications.
+
+All supplementary services may require signalling on the radio path. Signalling procedures and messages used are defined in the 3GPP TS 24.072, 24.08x and 24.09x-series of technical specifications.
+
+For some supplementary services information needs to be transferred between the Home Location Register (HLR), the Visitor Location Register (VLR), the Mobile services Switching Centre (MSC) and the Serving GPRS Support Node (SGSN). Signalling procedures for such information transfer are defined in 3GPP TS 29.002.
+
+Definitions and descriptions of supplementary services are given in the 3GPP TS 22.072, 22.08x and 22.09x-series of technical specifications.
+
+Definitions are given in 3GPP TS 22.004..
+
+NOTE: The technical specifications on the technical realisation of supplementary services do not distinguish between subscriber, user and customer, since all three do not fully cover the textual needs. Generally the term "subscriber" is used, even if this person is not having the subscription.
+
+## 1.1 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TS 21.905: "3G Vocabulary".
+- [2] 3GPP TS 22.004: "General on Supplementary Services".
+- [3] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [4] 3GPP TS 23.081: "Line Identification Supplementary Services - Stage 2".
+- [5] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services - Stage 2".
+- [6] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service - Stage 2".
+- [7] 3GPP TS 23.084: "MultiParty (MPTY) Supplementary Service - Stage 2".
+- [8] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service - Stage 2".
+- [9] 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Service - Stage 2".
+- [10] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service - Stage 2".
+- [11] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD) - Stage 2".
+- [12] 3GPP TS 24.080: "Mobile radio Layer 3 Supplementary Service specification - Formats and coding".
+
+- [13] 3GPP TS 24.081: "Line Identification Supplementary Service - Stage 3".
+- [14] 3GPP TS 24.082: "Call Forwarding Supplementary Service - Stage 3".
+- [15] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service - Stage 3".
+- [16] 3GPP TS 24.084: "MultiParty (MPTY) Supplementary Service - Stage 3".
+- [17] 3GPP TS 24.085: "Closed User Group (CUG) Supplementary Service - Stage 3".
+- [18] 3GPP TS 24.086: "Advice of Charge (AoC) Supplementary Service - Stage 3".
+- [19] 3GPP TS 24.088: "Call Barring (CB) Supplementary Service - Stage 3".
+- [20] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD) - Stage 3".
+- [21] 3GPP TS 29.002: "Mobile Application Part (MAP)".
+
+## 1.2 Abbreviations
+
+Abbreviations used in the present document are listed in 3GPP TS 21.905.
+
+# --- 2 Activation, deactivation, registration, erasure, interrogation and invocation
+
+## 2.1 General
+
+Activation, deactivation, registration, erasure, interrogation and invocation are defined independently from a particular supplementary service. Whether they are applicable to a particular supplementary service or not is defined in the corresponding 3GPP TS 23.08x and 23.09x-series. Activation, deactivation, registration, erasure and invocation are applicable for CS domain. For PS domain only invocation of call barring of SMS is applicable.
+
+The invocation of a supplementary service is executed as described in the corresponding stage 2 description and always includes an MSC and a location register for CS domain and an SGSN for PS domain.
+
+When an MSC receives a request for either activation/deactivation or registration/erasure or an interrogation, it invokes one of the following procedures.
+
+The MSC then can:
+
+- contact only the current VLR (e.g. interrogation of a call forwarding conditional supplementary service);
+- contact only the HLR (e.g. interrogation of the supplementary service call forwarding unconditional);
+- contact the HLR, after which the HLR updates the VLR (e.g. registration of a forwarding number for a conditional call forwarding supplementary service).
+
+Which of the above listed procedures is applied for a call independent supplementary service operation is described in the corresponding 3GPP TS 23.08x and 23.09x -series.
+
+Successful activation, deactivation, registration and erasure change the service state at the HLR. These transitions (if applicable to a particular service) are defined in the 3GPP TS 23.08x and 23.09x -series. Note that the HLR may also change the service state due to "HLR Induction" (see clause 2.1.1).
+
+In connection with supplementary service operations the served subscriber or remote subscribers may get notifications from the network. .
+
+If an SGSN receives a request for registration, erasure, activation, deactivation, interrogation or change of password, it shall return an error to the MS.
+
+### 2.1.1 Definition of "state vectors"
+
+In order to provide a tool to define service states the concept of a "state vector" is introduced. The state vector is used to represent the state of the service in terms of four variables:
+
+- 1) Provisioning State,  
+possible values are "Provisioned" or "Not Provisioned";
+- 2) Registration State,  
+possible values are "Registered", "Erased", or "Not Applicable";
+- 3) Activation State,  
+possible values are "Not Active", "Active and Operative" or "Active and Quiescent";
+- 4) HLR Induction State,  
+possible values are "Induced" or "Not Induced".
+
+The state vector represents the state of the service by using all four variables together. The state vector is represented using the notation:
+
+*(Provisioning State, Registration State, Activation State, HLR Induction State)*
+
+e.g.: (Provisioned, Registered, Not Active, Not Induced).
+
+Note that the state vector is a logical (not a physical) representation of the service state. Note also that though some parts of the state vector are similar to elements of SS-Status the mapping between the state vector and SS-Status is not one to one. The use of state vectors is not intended to specify any particular implementation internally in a node. There is a relationship specified between the state vector and parts of the transfer syntax. This relationship is not a direct one-to-one mapping.
+
+The following text specifies the semantics of each variable in the state vector.
+
+The three variables "Provisioning State", "Registration State" and "Activation State" are used to represent the state of the service according to the normal behaviour based on service provider and user actions.
+
+The "HLR Induction State" records whether or not the HLR has temporarily induced the service (e.g. if the VLR does not support CUG, the HLR may induce an outgoing barring service). The Provisioning State, Registration State and Activation State are not affected by HLR induction of a service.
+
+#### Provisioning State
+
+- has value "provisioned", if the subscriber has a subscription to the service;
+- has value "Not Provisioned" otherwise.
+
+#### Registration State
+
+- has value "Not Applicable", if registration is not applicable to the service;
+- has value "Registered", if registration is applicable, and there is registration data available;
+- has value "Erased" otherwise.
+
+#### Activation State
+
+- has value "Active and Operative", if the service is in a state where it can be invoked (and this is not due to HLR induction);
+- has value "Active and Quiescent", if the service is in a state where it cannot be invoked, but where it will automatically move to the "Active and Operative" state when conflicting conditions are removed;
+- has value "Not Active" otherwise.
+
+#### HLR Induction State
+
+- has the value "Induced" if the HLR has induced the service (e.g. if the VLR does not support CUG, the HLR may induce an outgoing barring service);
+- has the value "Not Induced" otherwise.
+
+For further information about how HLR induction applies to particular services refer to the 3GPP TS 23.08x and 23.09x-series.
+
+### 2.1.2 Handling of service states at the HLR
+
+Valid states (represented by state vectors) are defined on a service-by-service basis in the 3GPP TS 23.08x and 23.09x-series. For each service the set of valid states represents the logical states that can exist in the HLR. The HLR contains the master copy of service state information.
+
+#### 2.1.2.1 Encoding of SS-Status
+
+To send service state information to the VLR, the SGSN or the MS, the HLR often uses the SS-Status parameter. This parameter contains four bits (referred to here as the "P bit", "R bit", "A bit" and "Q bit"). In a phase 2 context the HLR shall encode the SS-Status using the mapping defined in this clause from the service states to SS-Status.
+
+If the HLR Induction State is "Not Induced" then:
+
+- If the Provisioning State is "Provisioned", then the P bit shall be 1, otherwise the P bit shall be 0.
+- If the Registration State is "Registered", the R bit shall be 1. If the Registration State is "Not Registered" the R bit shall be 0. If the Registration State is "Not Applicable" the R bit shall be either 0 or 1.
+- If the Activation State is "Active and Operative" the A bit shall be 1 and the Q bit shall be 0. If the Activation State is "Active and Quiescent" the A bit shall be 1 and the Q bit shall be 1. If the Activation State is "Not Active" the A bit shall be 0 and the Q bit shall be either 0 or 1.
+
+If the HLR Induction State is "Induced" then the P bit shall be 1, the R bit shall be 0 or 1, the A bit shall be 1 and the Q bit shall be 0.
+
+**Table 2.1: Encoding of the P, R, A and Q bits in the SS-Status parameter**
+
+| HLR Induction State "Not Induced"                                                 | P bit  | R bit         | A bit       | Q bit         |
+|-----------------------------------------------------------------------------------|--------|---------------|-------------|---------------|
+| Provisioning State "Provisioned"<br>"Not Provisioned"                             | 1<br>0 |               |             |               |
+| Registration State "Registered"<br>"Not Registered"<br>"Not Applicable"           |        | 1<br>0<br>0/1 |             |               |
+| Activation State "Active and Operative"<br>"Active and Quiescent"<br>"Not Active" |        |               | 1<br>1<br>0 | 0<br>1<br>0/1 |
+
+| HLR Induction State "Induced" | P bit | R bit | A bit | Q bit |
+|-------------------------------|-------|-------|-------|-------|
+|                               | 1     | 0/1   | 1     | 0     |
+
+#### 2.1.2.2 Invocation of services at the HLR
+
+If the service can be invoked at the HLR (e.g. to bar an incoming call) then invocation is possible only if the Activation State is "Active and Operative". Note that the concept of HLR induction does not apply to services invoked at the HLR as the HLR can invoke the effect of these services without needing to induce them first.
+
+### 2.1.3 Handling of SS-Status at the VLR or the SGSN
+
+The VLR shall store sufficient information to support VLR based invocation, interrogation and notifications from the VLR to the MS. The SGSN shall store sufficient information to support SGSN based invocation.
+
+The VLR or the SGSN shall not check the internal consistency of SS-Status values received from the HLR (i.e. it shall not impose any rules relating values of some bits in SS-Status to other bits). The VLR or the SGSN shall not check that the SS-Status received from the HLR is valid according to the VLR's or SGSN's definition of the relevant service.
+
+#### 2.1.3.1 Invocation of services at the VLR or the SGSN
+
+The ability to invoke the service at the VLR (e.g. to forward a call, or create an MPTY call) is based on the A and Q bits of SS-Status. The service can only be invoked if A=1 and Q=0. Other bits in SS-Status are not relevant to invocation at the VLR. .
+
+The ability to invoke the service at the SGSN (i.e. to bar MO SMS submission) is based on the A bit of SS-Status. The service can only be invoked if A=1. Other bits in SS-Status are not relevant to invocation at the SGSN.
+
+#### 2.1.3.2 Interrogation of the service at the VLR and notifications from VLR
+
+If the VLR sends a notification or an interrogation result that includes an SS-Status parameter the VLR shall set the P, R, A and Q bits to the same values received from the HLR. Unless stated otherwise in individual service specifications, if the service is not provisioned and the VLR has not received a value for SS-Status from the HLR then if the VLR has to send SS-Status for that service it shall set the P, R, A, and Q bits to 0.
+
+### 2.1.4 Handling of SS-Status at the MS
+
+The MS has to interpret SS-Status values received from the network. The following information is provided as guidance as to how to treat the SS-Status information:
+
+- The P, A and Q bits are relevant for all phase 2 supplementary services for which the MS may receive SS-Status information from the network.
+- The value of the R bit is only relevant if registration is applicable to the supplementary service the SS-Status relates to.
+- The A and Q bits shall be treated as a pair with the following meanings assumed:
+  - If A=1 and Q=0, then the service is "Active and Operative";
+  - If A=1 and Q=1, then the service is "Active and Quiescent";
+  - If A=0 and Q=0 or 1, then the service is deactivated.
+- The MS may assume that if P=0 then the service is also deactivated (and if registration is applicable erased).
+- If registration is applicable to the service then the MS may assume that if R=0 then the service is also deactivated.
+
+## 2.2 Handling of call independent SS procedures with respect to basic service groups
+
+A request for registration, erasure, activation, deactivation or interrogation of a supplementary service always refers to a basic service group.
+
+The basic service group may be either an elementary basic service group (defined in 3GPP TS 22.004) or a collective basic service group (defined in 3GPP TS 22.030).
+
+The following text and figure 2.1 describe the general handling of call independent SS procedures in the destination entity with respect to basic service groups.
+
+- The VLR or HLR (i.e. the destination entity) shall check the received request for general problems (see figure 2.1 sheet 2 and sheet 3).
+- In case of general error the procedure shall be terminated by sending an error towards the MS (see figure 2.1 sheet 1).
+- If there is no general problem, the HLR or VLR shall split the received basic service group (BSG) into elementary basic service groups (EBSG) and continue with separate handling of each elementary basic service group (see figure 2.1 sheet 1).
+
+Note that the received basic service group may be an elementary basic service group. In this case splitting is not required.
+
+- Elementary basic service groups shall be ignored if:
+  - there is no basic service provisioned in the group; or
+  - the supplementary service is not applicable for any basic service within this elementary basic service group;(see figure 2.1 sheet 4).
+
+Note that in case the SS is either not provisioned or all the elementary basic service groups were ignored a general error will be returned (see above).
+
+For interrogation the following handling continues (see figure 2.1 sheet 4):
+
+- For all other elementary basic service groups the information requested will be returned to the MS and the procedure is terminated.
+
+For registration/erasure and activation/deactivation the following handling continues (see figure 2.1 sheet 4):
+
+- For all other elementary basic service groups the requested procedure will either be executed or rejected due to interaction with other supplementary services.
+- If the request cannot be accepted for any of these elementary basic service groups due to interaction, the corresponding error will be returned and the procedure is terminated.
+- If the request was executed for all of these elementary basic service groups an acknowledgement is returned towards the MS and the procedure is terminated.
+
+Note that this acknowledgement will include the same basic service group as received in the request.
+
+- In case the request is accepted for some but not for all of these elementary basic service groups, partial acceptance will be signalled towards the MS and the procedure will be terminated.
+
+The return errors for supplementary service operations and applicability of these errors are defined in 3GPP TS 24.080. Detailed description of call independent handling for a specific supplementary service is described in 3GPP TS 23.08x and 23.09x -series of technical specifications.
+
+## 2.3 Exceptional handling of basic service codes
+
+When an individual teleservice code or bearer service code is sent by an MS instead of an elementary basic service group the network shall treat such a request as a request for the corresponding elementary basic service group.
+
+The response to such a request shall include the elementary basic service group code of this basic service code if this is required by the protocol or application.
+
+![Flowchart for Process SS_REQUEST_WITH_BS_GROUP showing the logic for handling SS requests with basic service groups.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+### Process SS\_REQUEST\_WITH\_BS\_GROUP
+
+311\_211(1)
+
+Handling in HLR and VLR
+
+BS: Basic Service.  
+ BSG: Basic Service group.  
+ EBSG: Elementary Basic Service group.  
+ SS: Supplementary Service.  
+  
+ NOTE: Only BS and SS included in  
+ the request are relevant.
+
+```
+
+graph TD
+    Start([idle]) --> SS_Req[/SS request/]
+    SS_Req --> Gen_Handling[general SS_request_handling]
+    Gen_Handling -.-> Sheets23[see sheets 2 and 3]
+    Gen_Handling --> Error1{error}
+    Error1 -- yes --> Error_End[error]
+    Error1 -- no --> Split[split request to EBSG]
+    Split --> TakeFirst[take request of first EBSG]
+    TakeFirst --> Conn1_In((1))
+    Conn1_In --> Spec_Handling[specific SS_request_handling]
+    Spec_Handling -.-> Sheet4[see sheet 4]
+    Spec_Handling --> LastEBSG{last EBSG}
+    LastEBSG -- no --> TakeNext[take request of next EBSG]
+    TakeNext --> Conn1_Loop((1))
+    Conn1_Loop --> Spec_Handling
+    LastEBSG -- yes --> Error2{error}
+    Error2 -- yes --> Error_End
+    Error2 -- no --> Success{successful for any EBSG}
+    Success -- no --> Error_End
+    Success -- yes --> Ack[/acknowledge/]
+    Ack --> Idle_End([idle])
+    Partial[/partial acceptance/] --> Idle_End
+    Error_End --> Idle_End
+    
+```
+
+Flowchart for Process SS\_REQUEST\_WITH\_BS\_GROUP showing the logic for handling SS requests with basic service groups.
+
+**Figure 2.1 (sheet 1 of 4): Handling of call independent SS procedures with respect to basic service groups**
+
+![Flowchart for general_SS_request_handling. It starts with a connector, then checks if SS is supported by the entity. If no, it goes to 'set error unexpected data value'. If yes, it checks if required parameters are missing. If yes, it goes to 'set error data missing'. If no, it checks if irrelevant parameter values are present. If yes, it goes to 'set error unexpected data value'. If no, it checks if the request is applicable for this SS. If no, it goes to 'set error illegal SS operation'. If yes, it checks if an interrogation is needed. If yes, it goes to connector 1. If no, it checks if the SS is provisioned. If no, it goes to 'set error SS error status'. If yes, it goes to connector 1. All error states lead to connector 2.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+Procedure general\_SS\_request\_handling
+
+311\_212(2)
+
+```
+graph TD; Start([ ]) --> D1{SS supported by this entity}; D1 -- no --> E1[set error unexpected data value]; D1 -- yes --> D2{required parameter missing}; D2 -- yes --> E2[set error data missing]; D2 -- no --> D3{irrelevant parameter value}; D3 -- yes --> E3[set error unexpected data value]; D3 -- no --> D4{request applicable for this SS}; D4 -- no --> E4[set error illegal SS operation]; D4 -- yes --> D5{interrogation}; D5 -- yes --> C1((1)); D5 -- no --> D6{SS provisioned}; D6 -- no --> E5[set error SS error status]; D6 -- yes --> C1; E1 --> C2((2)); E2 --> C2; E3 --> C2; E4 --> C2; E5 --> C2;
+```
+
+Handling of the entire request
+
+BS: Basic Service.  
+BSG: Basic Service Group.  
+SS: Supplementary Service.
+
+Flowchart for general\_SS\_request\_handling. It starts with a connector, then checks if SS is supported by the entity. If no, it goes to 'set error unexpected data value'. If yes, it checks if required parameters are missing. If yes, it goes to 'set error data missing'. If no, it checks if irrelevant parameter values are present. If yes, it goes to 'set error unexpected data value'. If no, it checks if the request is applicable for this SS. If no, it goes to 'set error illegal SS operation'. If yes, it checks if an interrogation is needed. If yes, it goes to connector 1. If no, it checks if the SS is provisioned. If no, it goes to 'set error SS error status'. If yes, it goes to connector 1. All error states lead to connector 2.
+
+Figure 2.1 (sheet 2 of 4): Handling of call independent SS procedures with respect to basic service groups
+
+![Flowchart for general_SS_request_handling procedure. It starts at connector 1, checks if any BS is provisioned within the BSG, if any BS is applicable within the same EBSG, and if SS requiring password or password registration is needed. If any check fails, it sets an error 'BS Not Provisioned' and goes to connector 2. If all checks pass, it sends an SS_request to process PW1, waits for indications from PW1-PW4, then branches into SS Get Password, SS Get New Password, SS Get New Password Again, SS User Errors, SS Password Changed, and SS Acknowledge. SS Get Password leads to a wait for password, then SS Get Password_Ack, then SS Receive_Password to processes PW1-PW4, and finally waits for PW. SS User Errors leads to Set ERROR and then to connector 2. SS Password Changed and SS Acknowledge also lead to connector 2. The procedure ends at a final connector symbol.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg)
+
+Procedure general\_SS\_request\_handling 311\_213(2)
+
+```
+graph TD; Start((1)) --> Q1{any BS provisioned within the BSG}; Q1 -- no --> End((2)); Q1 -- yes --> Q2{any BS applicable within the same EBSG}; Q2 -- no --> End; Q2 -- yes --> Q3{SS requiring password or password registration}; Q3 -- no --> SetError1[set error BS Not Provisioned]; SetError1 --> End; Q3 -- yes --> SS_request{{SS_request}}; SS_request -.-> PW1[To process PW1 as specified in TS GSM 03.11]; SS_request --> WaitPW1([Wait_for_PW]); WaitPW1 -.-> PW1_4[Waiting for indications from process PW1, PW2, PW3 or PW4 as specified in TS GSM 03.11.]; WaitPW1 --> Branch[ ]; subgraph Branch; direction LR; SSGetPassword1{{SS Get Password}}; SSGetNewPassword1{{SS Get New Password}}; SSGetNewPasswordAgain1{{SS Get New Password Again}}; SSUserErrors1{{SS User Errors}}; SSPasswordChanged1{{SS Password Changed}}; SSAcknowledge1{{SS Acknowledge}}; end; SSGetPassword1 --> SSGetPassword2{{SS Get Password}}; SSGetPassword2 --> WaitPassword([Wait for password]); WaitPassword --> SSGetPasswordAck{{SS Get Password_Ack}}; SSGetPasswordAck --> SSReceivePassword{{SS Receive_Password}}; SSReceivePassword -.-> PW1_4_2[To processes PW1, PW2, PW3 or PW4 specified in TS GSM 03.11.]; SSReceivePassword --> WaitPW2([Wait_for_PW]); SSUserErrors1 --> SetERROR[Set ERROR]; SetERROR --> End; SSPasswordChanged1 --> End; SSAcknowledge1 --> End;
+```
+
+Flowchart for general\_SS\_request\_handling procedure. It starts at connector 1, checks if any BS is provisioned within the BSG, if any BS is applicable within the same EBSG, and if SS requiring password or password registration is needed. If any check fails, it sets an error 'BS Not Provisioned' and goes to connector 2. If all checks pass, it sends an SS\_request to process PW1, waits for indications from PW1-PW4, then branches into SS Get Password, SS Get New Password, SS Get New Password Again, SS User Errors, SS Password Changed, and SS Acknowledge. SS Get Password leads to a wait for password, then SS Get Password\_Ack, then SS Receive\_Password to processes PW1-PW4, and finally waits for PW. SS User Errors leads to Set ERROR and then to connector 2. SS Password Changed and SS Acknowledge also lead to connector 2. The procedure ends at a final connector symbol.
+
+Figure 2.1 (sheet 3 of 4): Handling of call independent SS procedures with respect to basic service groups
+
+![Flowchart for handling call independent SS procedures with respect to basic service groups. The process starts with a connector, followed by a decision 'any BS provisioned within the EBSG'. If 'no', it goes to an end connector. If 'yes', it checks 'no SS applicable for any BS within this EBSG'. If 'no', it checks 'incompatible with other SS for this EBSG'. If 'yes', it sets an error; if 'no', it executes the procedure. Both lead to an end connector. If 'yes' to the second decision, it sets SS info for EBSG and then leads to an end connector.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+Procedure specific\_SS\_request\_handling
+
+311\_214(1)
+
+Handling of elementary BS groups
+
+BS: Basic Service  
+EBSG: Elementary Basic Service Group  
+SS: Supplementary Service
+
+NOTE: Execution of the procedure and setting of SS info for EBSGs is described in the GSM 03.8x and 03.9x series of technical specifications.
+
+```
+graph TD; Start([ ]) --> D1{any BS provisioned within the EBSG}; D1 -- no --> End1(( )); D1 -- yes --> D2{no SS applicable for any BS within this EBSG}; D2 -- no --> D3{incompatible with other SS for this EBSG}; D2 -- yes --> D4{interrogation}; D3 -- yes --> SetError[set error $S incompatibility]; D3 -- no --> Execute[execute requested procedure]; SetError --> End2(( )); Execute --> End2; D4 -- yes --> SetSS[set SS info for EBSG]; SetSS --> End2;
+```
+
+Flowchart for handling call independent SS procedures with respect to basic service groups. The process starts with a connector, followed by a decision 'any BS provisioned within the EBSG'. If 'no', it goes to an end connector. If 'yes', it checks 'no SS applicable for any BS within this EBSG'. If 'no', it checks 'incompatible with other SS for this EBSG'. If 'yes', it sets an error; if 'no', it executes the procedure. Both lead to an end connector. If 'yes' to the second decision, it sets SS info for EBSG and then leads to an end connector.
+
+Figure 2.1 (sheet 4 of 4): Handling of call independent SS procedures with respect to basic service groups
+
+# 3 Password handling
+
+## 3.1 General
+
+Some supplementary services can be subscribed with the option "control of supplementary service by subscriber using password" as described in the corresponding 3GPP TS 23.08x and 23.09x -series of technical specifications. This option
+
+is applicable only for the CS domain. These services are referenced in the following as protected supplementary services.
+
+The password is stored in the HLR only.
+
+It has to be memorised by the network, if a wrong password has been used. Therefore, the HLR stores the value of the Wrong Password Attempts counter (WPA).
+
+If a password check is done with an incorrect password, the WPA is incremented by one. If a password check is passed, WPA is set to zero. If WPA exceeds the value three, the subscription option "control of supplementary service" is set to "by the service provider". This makes registration of password and activation or deactivation of protected supplementary services impossible (see 3GPP TS 22.004).
+
+When the service provider registers a password, the WPA is set to zero.
+
+When an attempt to perform an operation requiring a password is received by the network, the network has to check whether the requesting subscriber has subscribed to the option "control of supplementary service by subscriber using password". This is shown in figure 3.1 (function PW1).
+
+If this option has the value "by the service provider" the WPA has to be checked. When WPA exceeds three, then more than three attempts with a wrong password have been made and the appropriate message will be sent to the user. If the value of WPA is less than or equal to three, then the subscriber has not subscribed to "control of supplementary service by subscriber using password".
+
+When a password is supplied, it has to be checked, whether it is identical to the one stored. If this applies, then WPA is reset to zero. Otherwise WPA is incremented by one and dependent of the value of the counter, the network shall request the password again, or shall send an error message and update the subscription option as shown in figure 3.2 (function PW2).
+
+After the input of a wrong password more than three consecutive times, the only possibility to reset the Wrong Password Attempts counter (WPA) is, to register a new password by the service provider.
+
+Figures 3.3 and 3.4 show the procedures executed by the network in order to check the format (function PW3) and to check the new password (function PW4).
+
+![Flowchart for Process PW1: Check of subscription option (HLR). The process starts at an 'idle' state, branches into 'register password', 'activate protected SS', and 'deactivate protected SS'. It then checks 'PW option control by subscriber'. If 'yes', it proceeds to 'get password' and 'wait for old password'. If 'no', it checks 'WPA <= 3'. If 'yes', it proceeds to 'error SS subscription violation' and 'idle'. If 'no', it proceeds to 'error number of PW attempts violation' and 'idle'. A note indicates 'PW: Password.'](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+**Process PW1** 311\_31(1)
+
+```
+graph TD; Start([ ]) --> Idle1([idle]); Idle1 --> Register[/register password/]; Idle1 --> Activate[/activate protected SS/]; Idle1 --> Deactivate[/deactivate protected SS/]; Register --> Join(( )); Activate --> Join; Deactivate --> Join; Join --> PWOption{PW option control by subscriber}; PWOption -- yes --> GetPassword{get password}; GetPassword --> WaitOld[wait for old password]; PWOption -- no --> WPA{WPA <= 3}; WPA -- yes --> ErrorSS{error SS subscription violation}; WPA -- no --> ErrorPW{error number of PW attempts violation}; ErrorSS --> Idle2([idle]); ErrorPW --> Idle2;
+```
+
+PW: Password.
+
+Flowchart for Process PW1: Check of subscription option (HLR). The process starts at an 'idle' state, branches into 'register password', 'activate protected SS', and 'deactivate protected SS'. It then checks 'PW option control by subscriber'. If 'yes', it proceeds to 'get password' and 'wait for old password'. If 'no', it checks 'WPA <= 3'. If 'yes', it proceeds to 'error SS subscription violation' and 'idle'. If 'no', it proceeds to 'error number of PW attempts violation' and 'idle'. A note indicates 'PW: Password.'
+
+Figure 3.1: PW1; Check of subscription option (HLR)
+
+![Flowchart for Process PW2: Check of password input (HLR). The process starts with 'wait for old password', followed by 'receive password'. A decision 'password OK' follows. If 'yes', WPA is reset to 0, and then 'register password' is checked. If 'yes', it goes to 'get new password' and 'wait for new password'. If 'no', it goes to 'acknowledge' and 'idle'. If 'password OK' is 'no', WPA is incremented. A decision 'WPA > 3' follows. If 'yes', it goes to 'set subscription option control by SP', 'error PW attempts violation', and 'idle'. If 'no', it goes to 'negative password check' and 'idle'.](8307f6b04df072c9332f9987e034272c_img.jpg)
+
+**Process PW2** 311\_32(1)
+
+PW: Password.  
+WPA: Wrong Password attempts counter.  
+SP: Service Provider.
+
+```
+graph TD; Start([wait for old password]) --> Receive[/receive password/]; Receive --> PasswordOK{password OK}; PasswordOK -- yes --> WPA0[WPA ::= 0]; PasswordOK -- no --> WPAinc[WPA ::= WPA + 1]; WPA0 --> Register{register password}; Register -- yes --> GetNew[get new password]; Register -- no --> Acknowledge[/acknowledge/]; GetNew --> WaitNew([wait for new password]); Acknowledge --> Idle1([idle]); WPAinc --> WPAgt3{WPA > 3}; WPAgt3 -- yes --> SetOption[set subscription option control by SP]; SetOption --> ErrorPW[/error PW attempts violation/]; ErrorPW --> Idle2([idle]); WPAgt3 -- no --> NegativeCheck[/negative password check/]; NegativeCheck --> Idle3([idle]);
+```
+
+Flowchart for Process PW2: Check of password input (HLR). The process starts with 'wait for old password', followed by 'receive password'. A decision 'password OK' follows. If 'yes', WPA is reset to 0, and then 'register password' is checked. If 'yes', it goes to 'get new password' and 'wait for new password'. If 'no', it goes to 'acknowledge' and 'idle'. If 'password OK' is 'no', WPA is incremented. A decision 'WPA > 3' follows. If 'yes', it goes to 'set subscription option control by SP', 'error PW attempts violation', and 'idle'. If 'no', it goes to 'negative password check' and 'idle'.
+
+**Figure 3.2: PW2; Check of password input (HLR)**
+
+![Flowchart for Process PW3: Format check (HLR). The process starts with 'wait for new password', followed by 'receive new password', then a decision 'format OK'. If 'yes', it goes to 'get new password again' and back to 'wait for new password again'. If 'no', it goes to 'error password registration failure (invalid format)' and then to 'idle'.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+**Process PW3** 311\_33(1)
+
+```
+graph TD; Start([wait for new password]) --> Receive[/receive new password/]; Receive --> FormatOK{format OK}; FormatOK -- yes --> GetAgain[/get new password again/]; GetAgain --> WaitAgain([wait for new password again]); FormatOK -- no --> Error[/error password registration failure (invalid format)/]; Error --> Idle([idle]);
+```
+
+Flowchart for Process PW3: Format check (HLR). The process starts with 'wait for new password', followed by 'receive new password', then a decision 'format OK'. If 'yes', it goes to 'get new password again' and back to 'wait for new password again'. If 'no', it goes to 'error password registration failure (invalid format)' and then to 'idle'.
+
+**Figure 3.3: PW3; Format check (HLR)**
+
+![Flowchart for Process PW4: Check of new password (HLR). The process starts with 'wait for new password again', followed by 'receive new password', then a decision 'password twice identical?'. If 'yes', it goes to 'password changed'. If 'no', it goes to 'error password registration failure (new Passwords Mismatch)'. Both 'password changed' and 'error password registration failure' lead to 'idle'.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+**Process PW4** 311\_34(1)
+
+```
+graph TD; A([wait for new password again]) --> B[/receive new password/]; B --> C{password twice identical?}; C -- yes --> D[/password changed/]; C -- no --> E[/error password registration failure (new Passwords Mismatch)/]; D --> F([idle]); E --> F;
+```
+
+Flowchart for Process PW4: Check of new password (HLR). The process starts with 'wait for new password again', followed by 'receive new password', then a decision 'password twice identical?'. If 'yes', it goes to 'password changed'. If 'no', it goes to 'error password registration failure (new Passwords Mismatch)'. Both 'password changed' and 'error password registration failure' lead to 'idle'.
+
+**Figure 3.4: PW4; Check of new password (HLR)**
+
+## 3.2 Registration of password
+
+If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by subscriber using password", the service provider has to register a password at provision time. Furthermore the served mobile subscriber can change the password by an appropriate control procedure at any time. The control procedure consists of three steps: first, the old password has to be provided; secondly, the new password has to be given, after which it has to be verified by providing it once more (see figure 3.5).
+
+If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by the service provider" an attempt to register a password will be denied and the served mobile subscriber should receive a notification.
+
+The subscriber can register a new password, thus causing the previous registration to be overridden (see figure 3.5).
+
+## 3.3 Use of password
+
+If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by subscriber using password" the supplementary service is activated only if the subscriber provides the correct password to the network.
+
+If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by the service provider", the supplementary service cannot be activated by the subscriber. The activation has to be performed by the service provider. An attempt to activate the service will be denied and the served mobile subscriber should receive a notification.
+
+If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by subscriber using password", and if a wrong password is entered to activate the service the supplementary service will not be activated and the served mobile subscriber is notified.
+
+The information flow for activation of a protected supplementary service is shown in figure 3.6.
+
+![Sequence diagram showing the registration of a new password between MS, MSC, VLR, and HLR. The diagram includes messages like Register, Get password, Old password, New password, and Password changed, with HLR responses labeled PW1, PW2, PW3, and PW4.](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+
+    Note right of HLR: PW1
+    MS->>MSC: Register
+    MSC->>VLR: Register password
+    VLR->>HLR: Register password
+    HLR-->>VLR: Get password
+    VLR-->>MSC: Get password
+    MSC-->>MS: Get password
+    MS->>MSC: Old password
+    MSC->>VLR: Old password
+    VLR->>HLR: Old password
+    Note right of HLR: PW2
+    HLR-->>VLR: Get password
+    VLR-->>MSC: Get password
+    MSC-->>MS: Get password
+    MS->>MSC: New password
+    MSC->>VLR: New password
+    VLR->>HLR: New password
+    Note right of HLR: PW3
+    HLR-->>VLR: Get password
+    VLR-->>MSC: Get password
+    MSC-->>MS: Get password
+    MS->>MSC: New password
+    MSC->>VLR: New password
+    VLR->>HLR: New password
+    Note right of HLR: PW4
+    HLR-->>VLR: Password changed
+    VLR-->>MSC: Password changed
+    MSC-->>MS: Release complete
+    Note left of MS: \ Facility
+```
+
+Sequence diagram showing the registration of a new password between MS, MSC, VLR, and HLR. The diagram includes messages like Register, Get password, Old password, New password, and Password changed, with HLR responses labeled PW1, PW2, PW3, and PW4.
+
+Figure 3.5: Registration of a new password
+
+NOTE: PW1, PW2 and PW3 indicate password handling programs.
+
+![Sequence diagram showing the activation of a protected supplementary service. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Activate SS' to MSC. MSC sends 'Activate SS' to VLR. VLR sends 'Activate SS' to HLR. HLR responds with 'Get password' (labeled PW1) to VLR. VLR sends 'Get password' to MSC. MSC sends 'Password' to MS. MSC also sends 'Password' to VLR. VLR sends 'Password' to HLR (labeled PW2). HLR responds with 'Acknowledge' (labeled ICH) to VLR. VLR sends 'Acknowledge' to MSC. MSC sends 'Release complete \ Facility' to MS.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    Note right of HLR: PW1
+    Note right of HLR: PW2
+    Note right of HLR: ICH
+    MS->>MSC: Activate SS
+    MSC->>VLR: Activate SS
+    VLR->>HLR: Activate SS
+    HLR-->>VLR: Get password
+    VLR-->>MSC: Get password
+    MSC-->>MS: Password
+    MSC->>VLR: Password
+    VLR->>HLR: Password
+    HLR-->>VLR: Acknowledge
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Release complete \ Facility
+```
+
+Sequence diagram showing the activation of a protected supplementary service. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Activate SS' to MSC. MSC sends 'Activate SS' to VLR. VLR sends 'Activate SS' to HLR. HLR responds with 'Get password' (labeled PW1) to VLR. VLR sends 'Get password' to MSC. MSC sends 'Password' to MS. MSC also sends 'Password' to VLR. VLR sends 'Password' to HLR (labeled PW2). HLR responds with 'Acknowledge' (labeled ICH) to VLR. VLR sends 'Acknowledge' to MSC. MSC sends 'Release complete \ Facility' to MS.
+
+**Figure 3.6: Activation of protected supplementary service**
+
+NOTE: SS indicates any of the protected supplementary services.  
+PW1 and PW2 indicate password handling programs.  
+ICH indicates interaction checks if necessary.
+
+## 3.4 Deactivation
+
+The procedure for activation, described in clause 3.3, is valid also correspondingly for deactivation.
+
+The information flow for deactivation of protected supplementary service is shown in figure 3.7.
+
+![Sequence diagram showing the deactivation of a protected supplementary service. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The process starts with the MS sending a 'Deactivate SS' message to the MSC. The MSC then sends a 'Deactivate SS' message to the VLR. The VLR sends a 'Deactivate SS' message to the HLR. The HLR responds with 'PW1' (Get password) to the VLR. The VLR sends a 'Get password' message to the MSC. The MSC sends a 'Get password' message to the MS. The MS responds with 'Password' to the MSC. The MSC sends a 'Password' message to the VLR. The VLR sends a 'Password' message to the HLR. The HLR responds with 'PW2' (Acknowledge) to the VLR. The VLR sends an 'Acknowledge' message to the MSC. The MSC sends a 'Release complete' message to the MS, followed by '\ Facility'.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    Note right of HLR: PW1
+    MS->>MSC: Deactivate SS
+    MSC->>VLR: Deactivate SS
+    VLR->>HLR: Deactivate SS
+    HLR-->>VLR: Get password
+    VLR->>MSC: Get password
+    MSC->>MS: Get password
+    MS->>MSC: Password
+    MSC->>VLR: Password
+    VLR->>HLR: Password
+    Note right of HLR: PW2
+    HLR-->>VLR: Acknowledge
+    VLR->>MSC: Acknowledge
+    MSC->>MS: Release complete
+    MS-->>MSC: \ Facility
+  
+```
+
+Sequence diagram showing the deactivation of a protected supplementary service. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The process starts with the MS sending a 'Deactivate SS' message to the MSC. The MSC then sends a 'Deactivate SS' message to the VLR. The VLR sends a 'Deactivate SS' message to the HLR. The HLR responds with 'PW1' (Get password) to the VLR. The VLR sends a 'Get password' message to the MSC. The MSC sends a 'Get password' message to the MS. The MS responds with 'Password' to the MSC. The MSC sends a 'Password' message to the VLR. The VLR sends a 'Password' message to the HLR. The HLR responds with 'PW2' (Acknowledge) to the VLR. The VLR sends an 'Acknowledge' message to the MSC. The MSC sends a 'Release complete' message to the MS, followed by '\ Facility'.
+
+**Figure 3.7: Deactivation of protected supplementary service**
+
+NOTE: SS indicates any of the protected supplementary services. PW1 and PW2 indicate password handling programs.
+
+# 4 Supplementary service data management
+
+For the supplementary services that are considered "activated as a result of provision", when the service is provisioned the following applies:
+
+when subscription data is sent from the HLR to the VLR, and when an interrogation is sent from the HLR or VLR to the MS:
+
+- "Provision status" indicators shall be set to "Provisioned";
+- "Activation status" indicators shall be set to "Active".
+
+# 5 Format of description
+
+The supplementary services are described according to the following format:
+
+- clause x.1 Functions and information flows;
+- clause x.2 Information stored in HLR;
+- clause x.3 Information stored in VLR and SGSN;
+- clause x.4 Handover.

marked/Rel-18/23_series/23016/raw.md

@@ -0,0 +1,1337 @@
+
+
+# 3GPP TS 23.016 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Subscriber data management; Stage 2 (Release 18)**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the right of the "e" is a green signal icon consisting of three curved lines. Below the "e" is a small "TM" trademark symbol.
+
+LTE Advanced Pro logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo. It features the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a horizontal line. Below the "P" is a red signal icon consisting of three curved lines. Below the logo is the text "A GLOBAL INITIATIVE" in a smaller, black, uppercase font. To the right of the "P" is a small "TM" trademark symbol.
+
+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 .....                                               | 6         |
+| 3.1 Abbreviations .....                                                             | 6         |
+| 3.2 Definitions.....                                                                | 7         |
+| 4 General on handling of subscriber information .....                               | 10        |
+| 4.1 Updating of the VLR or the SGSN in framed operation.....                        | 11        |
+| 4.2 Updating of VLR and the SGSN in stand alone operation .....                     | 12        |
+| 4.2.1 Insertion of data in the VLR or the SGSN .....                                | 12        |
+| 4.2.2 Deletion of data in the VLR or the SGSN .....                                 | 13        |
+| 4.2.3 Change of data in the VLR or in the SGSN .....                                | 13        |
+| 4.3 Order of information and distribution over message boundaries.....              | 13        |
+| 4.3.1 Order of information sent by the HLR .....                                    | 13        |
+| 4.3.2 Order of information received by the VLR or the SGSN.....                     | 14        |
+| 4.4 Abstract data structure of shared subscriber data.....                          | 14        |
+| 4.5 Handling of supplementary service data with respect to basic service data ..... | 15        |
+| 4.5.1 General .....                                                                 | 15        |
+| 4.5.2 Changes to basic service subscription .....                                   | 15        |
+| 4.5.3 Special rules for BS61 and BS81 "alternate" and "followed-by" services.....   | 16        |
+| 4.5.4 Consistency of Supplementary Service data .....                               | 16        |
+| <b>Annex A (informative): Change history.....</b>                                   | <b>32</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+This specification gives the stage 2 description of the subscriber data management handling between:
+
+- the Home Location Register (HLR) and the Visitor Location Register (VLR);
+- the Home Location Register (HLR/HSS) and the Serving GPRS Support Node (SGSN).
+
+A number of procedures require updating of subscriber information:
+
+- location updating;
+- restoration;
+- modification of data by the operator;
+- modification of data by the subscriber via the Mobile Station (MS).
+
+Updating of subscriber information from HLR/HSS to SGSN is required in the following situations:
+
+- GPRS location updating;
+- EPS location updating;
+- modification of data by the operator.
+
+Only the rules for the updating of subscriber data from the HLR to the VLR and from the HLR/HSS to the SGSN are described in this specification; these rules only apply when the MAP protocol is used for subscriber data updating (see 3GPP TS 29.002 [23]). Public Land Mobile Network (PLMN) specific and Unstructured Supplementary Service Data (USSD) subscriber data are out of scope of this specification. The GPRS context update from the SGSN to the GGSN and the EPC bearer context update from the SGSN to the P-GW via S-GW are out of scope of this specification.
+
+NOTE: The term 'HLR' should be read 'HLR/HSS' throughout the document.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
+- [3] 3GPP TS 22.004: "General on supplementary services".
+- [4] 3GPP TS 23.007: "Restoration procedures".
+- [5] 3GPP TS 23.008: "Organization of subscriber data".
+- [6] 3GPP TS 23.011: "Technical realization of Supplementary Services".
+- [7] 3GPP TS 23.015: "Technical realization of Operator Determined Barring (ODB)".
+
+- [8] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".
+- [9] 3GPP TS 23.067: "Enhanced Multi-Level Precedence and Preemption service (EMLPP); Stage 2".
+- [10] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) phase 3 - Stage 2".
+- [11] 3GPP TS 23.081: "Line identification supplementary services; Stage 2".
+- [12] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services; Stage 2".
+- [13] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services; Stage 2".
+- [14] 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Service; Stage 2".
+- [15] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service; Stage 2".
+- [16] 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Service; Stage 2".
+- [17] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2".
+- [18] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD); Stage 2".
+- [19] 3GPP TS 23.091: "Explicit Call Transfer (ECT) Supplementary Service; Stage 2".
+- [20] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2".
+- [21] 3GPP TS 23.096: "Name Identification Supplementary Service; Stage 2".
+- [22] 3GPP TS 23.116: "Super-Charger technical realization; Stage 2."
+- [23] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [24] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface".
+- [25] 3GPP TS 22.001: "Principles of circuit telecommunications services supported by a Public Land Mobile Network (PLMN)".
+- [26] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
+- [27] 3GPP TS 42.032: " Immediate Service Termination (IST); Service Description - Stage 1".
+- [28] 3GPP TS 43.035: " Immediate Service Termination (IST); Stage 2".
+- [29] 3GPP TS 43.068: " Voice Group Call Service (VGCS); Stage 2".
+- [30] 3GPP TS 43.069: " Voice Broadcast Service (VBS); Stage 2".
+- [31] 3GPP TS 23.071: "Location Services (LCS); Functional Description; Stage 2".
+- [32] 3GPP TS 23.135: "Multicall supplementary service; Stage 2".
+- [33] 3GPP TS 23.072: "Call Deflection Supplementary Service; Stage 2".
+- [34] 3GPP TS 23.012: "Location Management Procedures".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 apply.
+
+## 3.2 Definitions
+
+Subscriber data to be stored in the HLR, VLR and SGSN are defined in 3GPP TS 23.008, 3GPP TS 23.271, 3GPP TS 23.135 and in 3GPP TS 23.06x, 3GPP TS 23.08x and 3GPP TS 23.09x-series of technical specifications.
+
+Voice Broadcast Service (VBS), Voice Group Call Service (VGCS) and enhanced Multi Level Precedence and Pre-emption Service (eMLPP) Data related to group call area, cell or dispatcher attributes is only stored in the Group Call Register (GCR) which is linked to each MSC/VLR.
+
+The GCR and its stored data is out of scope of this specification.
+
+Subscriber related VBS, VGCS and eMLPP Data only concerns entitlement data for these-services and is seen as shared non-GPRS subscriber data.
+
+### **GPRS and non-GPRS subscriber data:**
+
+The HLR has to download data to the VLR and to the SGSN. In this specification those data sent to the VLR are called non-GPRS subscriber data and those data sent to the SGSN are called GPRS subscriber data.
+
+Whenever the refining identifier non-GPRS or GPRS is missing a common rule is addressed which hold for both kinds of subscriber data.
+
+Subscriber data specific to non-GPRS shall only be sent from the HLR to the VLR. Subscriber data specific to GPRS shall only be sent from the HLR to the SGSN.
+
+Subscriber data common to both non-GPRS and GPRS (regional subscription information) are downloaded from the HLR to both entities.
+
+**Shared non-GPRS subscriber data:** Common subset of subscriber data defined to be stored in both the HLR and VLR. Subscriber data only stored in the HLR is not part of shared subscriber data. Shared subscriber data includes:
+
+- BS: Bearer Service (see 3GPP TS 22.002);
+- TS: Teleservice (see 3GPP TS 22.003);
+- BSG: Basic Service Group (see 3GPP TS 22.001, 3GPP TS 22.004 and 3GPP TS 23.011);
+- EBSG: Elementary Basic Service Group (see 3GPP TS 23.011);
+- CBSG: Collective Basic Service Group (see 3GPP TS 23.011);
+- LSA Information: Localized Service Area Information (see 3GPP TS 23.073);
+- SC Information: Super-Charger Information (see 3GPP TS 23.116);
+- IST Information: Immediate Service Termination Information (see 3GPP TS 43.035).
+
+**Shared GPRS subscriber data:** Common subset of subscriber data defined to be stored in both the HLR and SGSN. Subscriber data only stored in the HLR is not part of shared subscriber data. Shared GPRS subscriber data includes:
+
+- TS: Teleservice (see 3GPP TS 22.003);
+- PDP Context (see 3GPP TS 23.060);
+- LSA Information: Localized Service Area Information (see 3GPP TS 23.073);
+- SC Information: Super-Charger Information (see 3GPP TS 23.116);
+- Charging Information (see 3GPP TS 23.060).
+
+**Mandatory data:** Data required to form a self-consistent set of subscriber data. The context governs whether a specific parameter is mandatory, e.g. the data set for a specific service may be optional, however if data for this service is present, then parameters within this data set may be mandatory.
+
+Mandatory data is defined by the service description (see e.g. 3GPP TS 23.06x, 3GPP TS 23.08x and 3GPP TS 23.09x-series of technical specifications, 3GPP TS 23.015, 3GPP TS 23.071 and 3GPP TS 23.135) and by PLMN defined requirements.
+
+NOTE: The above definition is seen from a semantic point of view. Semantically, mandatory parameters may be defined as syntactically optional or mandatory by the protocol.
+
+**Optional data:** Data which is defined as subscriber data, but which is not required to form a self-consistent set of subscriber data; the context governs whether a specific parameter is optional.
+
+Optional data is data which is defined by the service description (see e.g. 3GPP TS 23.06x, 3GPP TS 23.08x and 3GPP TS 23.09x-series of technical specifications, 3GPP TS 23.015, 3GPP TS 23.271 and 3GPP TS 23.135) or by PLMN defined requirements but is not defined as mandatory data.
+
+NOTE: The above definition is seen from a semantic point of view. Semantically optional parameters are always defined as syntactically optional by the protocol.
+
+**Missing data:** Data which is mandatory in a given context but is not received nor is valid data available locally.
+
+**Unexpected data:** Data which is received and cannot be further processed. This may be either:
+
+- optional data not required in a given context; or
+- optional or mandatory data, required in this context but received with an unexpected value.
+
+**Overlapping data:** Two different cases of overlapping within subscriber data are possible:
+
+- two or more parameters are to be stored at the same address in the data structure (see clause 4.4);
+- two or more BSGs within a BSG list include or are identical with one and the same EBSG.
+
+The following groups of non-GPRS subscriber information are defined:
+
+- Subscriber information (Group A):
+  - International Mobile Subscriber Identity (IMSI);
+  - basic Mobile Station International ISDN Number (MSISDN);
+  - category;
+  - subscriber status;
+  - LMU identifier (GSM only).
+- Basic service information (Group B):
+  - Bearer Service list;
+  - Teleservice list.
+
+NOTE: VBS and VGCS entitlement data are subsumed under Teleservices.
+
+- Supplementary Service (SS) information (Group C):
+  - forwarding information including deflection information;
+  - call barring information;
+  - Closed User Group (CUG) information;
+  - eMLPP data;
+  - MC data;
+  - SS Data.
+- Operator Determined Barring (ODB) information (Group D):
+  - ODB Data for non-GPRS services;
+- Roaming restriction information (Group E):
+
+- roaming restriction due to unsupported feature.
+- Regional subscription information (Group F):
+  - regional subscription data.
+- VBS/VGCS subscription information (Group G):
+  - VBS subscription data;
+  - VGCS subscription data.
+- CAMEL subscription information (Group H):
+  - Originating CAMEL Subscription Information (O-CSI);
+  - Dialled Service CAMEL Subscription Information (D-CSI);
+  - VMSC Terminating CAMEL Subscription Information (VT-CSI);
+  - Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI);
+  - Translation Information Flag CAMEL Subscription Information (TIF-CSI);
+  - Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI);
+  - Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI);
+  - Mobility Management Event Notification CAMEL Subscription Information (M-CSI).
+- LSA Information (Group I):
+  - LSA data.
+- Super-Charger (SC) Information (Group K):
+  - Age Indicator.
+- Location Services (LCS) information (Group X):
+  - GMLC List;
+  - LCS Privacy Exception List;
+  - MO-LR List;
+  - LCS Service Types.
+- IST Information (Group J):
+  - IST data.
+- Bearer Service Priority Information (Group L):
+  - Bearer Service Priority Data.
+- Administrative Restriction Information (Group M):
+  - Access Restriction Data.
+
+The following groups of GPRS subscriber information are defined:
+
+- Subscriber information (Group P1):
+  - International Mobile Subscriber Identity (IMSI);
+  - basic Mobile Station International ISDN Number (MSISDN);
+  - subscriber status.
+
+- Basic service information (Group P2):
+  - Teleservice list.
+- Operator Determined Barring (ODB) information (Group P3):
+  - ODB Data for GPRS services.
+- Roaming restriction information (Group P4):
+  - roaming restriction in SGSN due to unsupported feature.
+- Regional subscription information (Group P5):
+  - regional subscription data.
+- GPRS subscription information (Group P6):
+  - GPRS subscription data.
+- EPS subscription information (Group P6a):
+  - EPS subscription data.
+- SGSN CAMEL subscription information (Group P7):
+  - GPRS CAMEL subscription information;
+  - Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI);
+  - Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI);
+  - Mobility Management Event for GPRS Notification CAMEL Subscription Information (MG-CSI).
+- LSA Information (Group P8):
+  - LSA data.
+- Super-Charger (SC) Information (Group P9):
+  - Age Indicator.
+- Charging Information (Group P10):
+  - Subscribed Charging Characteristics.
+- Location Services (LCS) information (Group P11):
+  - GMLC List;
+  - LCS Privacy Exception List;
+  - MO-LR Lis;
+  - LCS Service Types.
+- Administrative Restriction Information (Group P12):
+  - Access Restriction Data.
+
+# --- 4 General on handling of subscriber information
+
+In general, the VLR and SGSN stores only a subset of the subscriber data available in the HLR. Similarly, the GGSN stores only a subset of the subscriber data available in the SGSN. Updating of subscriber information shall be done in a way to make available and to keep consistency of data shared between the HLR and the VLR, and between the HLR and the SGSN as appropriate.
+
+Two different cases for the updating of subscriber data can be identified:
+
+1. framed operation: during location update or restoration a complete set of the shared subscriber data needs to be inserted in the VLR or the SGSN;
+2. stand-alone operation: whenever subscriber data are added, deleted or changed in the HLR, this may need partial insertion, deletion or change of shared subscriber data in the VLR or the SGSN.
+
+Clauses 4.1 to 4.4 explain the actions of the HLR and the VLR or the SGSN within a framed or stand-alone dialogue on subscriber data handling.
+
+## 4.1 Updating of the VLR or the SGSN in framed operation
+
+For some services the VLR or the SGSN shall indicate in the subscriber data request to the HLR whether it supports the service, or (in case of a service with multiple phases) which phases it supports. Whether or not this indication is required for the service is defined in service specification.
+
+If requested by the framing operation, the HLR shall send all relevant stored shared subscriber data to the VLR or the SGSN. This may be done with one or more messages within a single dialogue.
+
+For services for which the VLR or the SGSN is required to indicate support of the service, the HLR shall send subscriber data to the VLR or the SGSN only if corresponding indication was received from the VLR or the SGSN in the subscriber data request. If both the originating entity and the HLR support the Super-Charger functionality the HLR may provide no subscriber data as part of the location update procedure, see 3GPP TS 23.116. For control of stand-alone operation the HLR shall store the information for which of these services the subscriber data was sent.
+
+For services for which the VLR or the SGSN is required to indicate supported phases of the service, the HLR shall send subscriber data to the VLR for at most one of the supported phases of service indicated in the subscriber data request. In this case the HLR may send also no data at all if none of the supported phases is suitable. For the case of stand-alone operation the HLR shall store the information for which phase of service the data was sent.
+
+The HLR may send all stored shared subscriber data to the VLR or the SGSN with one or more messages within a single dialogue.
+
+The VLR or the SGSN shall check the received messages, and:
+
+- a) if mandatory data is missing in a message:
+  - the VLR or the SGSN may immediately reject the message towards the HLR; or
+  - the VLR or the SGSN may acknowledge the message towards the HLR and wait for further data from the HLR.
+
+NOTE: Which of the two options apply is either defined by the protocol specification or is an implementation option.
+
+- b) if unexpected data are received in a message:
+  - the VLR or the SGSN may reject the message towards the HLR; or
+  - in case of unexpected data not required in a given context, the VLR or the SGSN may acknowledge the message towards the HLR and ignore this unexpected data. All other data shall be stored by the VLR or the SGSN.
+
+NOTE: Which of the two possibilities apply is an implementation option.
+
+- c) if data for unsupported services or features is received:
+  - the VLR or the SGSN shall respond towards the HLR to the message indicating these features and shall ignore all received data related to them. All other subscriber data shall be stored;
+- d) if cases a), b) and c) do not apply for a message, the VLR or SGSN shall store all subscriber data received.
+
+If during the entire dialogue none of the messages was rejected by the VLR or the SGSN and at termination of the dialogue no mandatory subscriber data are missing, the VLR or the SGSN shall erase all previously stored data and
+
+shall store the data received from the HLR and mark the subscriber data as "confirmed by HLR". Otherwise the subscriber data shall remain marked as "not confirmed by HLR" (see TS 3GPP TS 23.007).
+
+The HLR shall check all responses from the VLR or the SGSN, and:
+
+- a) if a message is rejected, no further updating of the VLR or the SGSN shall occur. The further action on the framing operation is out of scope of this specification;
+- b) if one or more unsupported features are indicated by the VLR or the SGSN, the HLR may:
+  - store subscriber data including replacement feature(s) locally;
+  - store and send subscriber data including replacement feature(s);
+  - ignore this indication.
+
+NOTE: Which of the three options apply for which feature is out of scope of this specification
+
+- c) if a message is acknowledged by the VLR or the SGSN, this shall be recognized by the HLR.
+
+The further action on the framing operation after all shared subscriber and replacement data have been sent (e.g. closing of the dialogue) is out of scope of this specification.
+
+## 4.2 Updating of VLR and the SGSN in stand alone operation
+
+If shared subscriber data are added, deleted or changed in the HLR, the HLR shall insert or delete this subscriber data in the VLR or the SGSN to keep consistency of data stored.
+
+For services for which the VLR or the SGSN is required to indicate support of the service in the request, the HLR shall insert or delete this subscriber data in the VLR or the SGSN only if an appropriate indication is stored in the HLR (see clause 4.1).
+
+For services for which the VLR or the SGSN is required to indicate supported phases of the service in the request, the HLR shall insert or delete subscriber data in the VLR or the SGSN only if it was added, deleted or changed for the phase of the service for which the data was sent to the VLR or the SGSN in the framed operation.
+
+### 4.2.1 Insertion of data in the VLR or the SGSN
+
+For the insertion of data, the HLR may send one or more messages in a single dialogue.
+
+The VLR or the SGSN shall check the received data, and:
+
+- a) if mandatory data is missing in a message:
+  - the VLR or the SGSN may reject the message towards the HLR; or
+  - the VLR or the SGSN may acknowledge the message towards the HLR and wait for further data from HLR.
+
+NOTE: Which of the two possibilities apply is either defined by the protocol specification or an implementation option.
+
+- b) if unexpected data are received:
+
+- the VLR or the SGSN may reject the message towards the HLR; or
+- in case of unexpected data not required in a given context, the VLR or the SGSN may acknowledge the message towards the HLR and ignore this unexpected data. All other data shall be stored by the VLR or the SGSN.
+
+NOTE: Which of the two possibilities apply is an implementation option.
+
+- c) if data for unsupported services or features is received:
+
+- the VLR or the SGSN shall respond towards the HLR to the message indicating these features and shall ignore all data assigned to them. All other subscriber data shall be stored.
+
+- d) if cases a), b) and c) do not apply for a message, the VLR or the SGSN shall store all subscriber data received.
+
+If during the entire dialogue none of the messages was rejected by the VLR or the SGSN and at termination of the dialogue no subscriber data are missing, the VLR or the SGSN shall mark the subscriber data as "confirmed by HLR". Otherwise the subscriber data shall be marked as "not confirmed by HLR" (see 3GPP TS 23.007).
+
+The HLR shall check all responses from the VLR or the SGSN, and:
+
+- a) if a message is rejected no further updating of the VLR or the SGSN is allowed and the HLR shall terminate the dialogue;
+  - b) if one or more unsupported features are indicated by the VLR or the SGSN, the HLR may:
+    - store subscriber data including replacement feature(s) locally;
+    - store and send subscriber data including replacement feature(s);
+    - ignore this indication.
+- NOTE: Which of the three possibilities apply for which feature is out of scope of this specification
+- c) if a message is acknowledged by the VLR or the SGSN, this shall be recognized by the HLR.
+
+After all required shared subscriber and replacement data have been sent, the HLR shall terminate the dialogue with the VLR or the SGSN.
+
+### 4.2.2 Deletion of data in the VLR or the SGSN
+
+Deletion needs a separate dialogue.
+
+HLR and VLR or SGSN actions are the same as above except for the following case:
+
+- if, in response to deletion, one or more unsupported features are indicated by the VLR or the SGSN, the HLR may:
+  - delete subscriber data including replacement feature(s) locally;
+  - delete subscriber data including replacement feature(s) locally and in the VLR or the SGSN (NOTE);
+  - take no further action.
+
+NOTE 1: Which of the three options apply for which feature is out of scope of this specification.
+
+NOTE 2: This deletion in the VLR or the SGSN needs a separate dialogue.
+
+The VLR or SGSN shall terminate the dialogue with the HLR in response to the HLR.
+
+### 4.2.3 Change of data in the VLR or in the SGSN
+
+If existing data in the VLR or the SGSN is to be modified, the HLR may insert the replacing data, which overwrites the existing data according to the rules described in clause 4.4. Alternatively, the HLR may delete the existing data as described in clause 4.2.2 and then insert the replacing data as described in clause 4.2.1.
+
+## 4.3 Order of information and distribution over message boundaries
+
+### 4.3.1 Order of information sent by the HLR
+
+The order of information is defined by the order in which the transfer syntax is generated by the HLR. This includes a sequence of messages as well as the syntax within a message (first to last message, component, operation, parameter, etc...).
+
+With the above definitions, the following rules shall apply for non-GPRS subscriber data for the order of information within an HLR-VLR dialogue:
+
+- Group A information (subscriber status) shall be sent first;
+- Group B information shall be sent after Group A information and before any Group C, E, F, G, H, J, L, M or X information;
+- Group D information shall be sent after Group A information and in any order with respect to Group B, C, E, F, G, H, J, K, L, M and X information;
+- a specific order of Group C, E, F, G, H, J, K, L, M or X information is not required.
+
+There is no requirement for the sending of subscriber information groups in the same message.
+
+With the above definitions, the following rules shall apply for GPRS subscriber data for the order of information within a dialogue:
+
+- Group P1 information (subscriber status) shall be sent first;
+- Group P2 information shall be sent after P1 information and before P4 and P5 information;
+- Group P3 information shall be sent after Group P1 information and in any order with respect to Group P2, P4, P5, P6, P6a, P7, P8, P11 and P12 information;
+- a specific order of Group P4, P5, P6, P6a, P9, P10, P11 and P12 information is not required.
+
+### 4.3.2 Order of information received by the VLR or the SGSN
+
+Normally, the order of information sent and received shall be identical. However, if subscriber data are sent distributed over several messages within a dialogue in exceptional cases the order of these messages may change during transmission.
+
+If the order of information received violates the rules given above, the VLR or the SGSN has the following options:
+
+- the VLR or the SGSN rejects all messages which cannot be processed due to violation of these rules. In this case, checking of missing mandatory parameters is done for each message;
+- the VLR or the SGSN processes and accepts all received messages although rules are violated. In this case, checking of missing mandatory parameters is done after the last message i.e. after termination of the dialogue.
+
+Both options may be used in a single implementation. Missing parameters may be detected during the dialogue. For other parameters, the checking is done after termination of the dialogue between the HLR and the VLR or the SGSN.
+
+The VLR or the SGSN is not required to handle received data in a specific order. As a consequence, any overlapping of data within a dialogue should be avoided to keep consistency of data between HLR and VLR or the SGSN. If the VLR or SGSN indicates that it does not support a feature or service, the HLR may send data for a feature or service to replace the unsupported one. If the data of that service or feature had already been sent, this shall not be regarded as overlapping data.
+
+## 4.4 Abstract data structure of shared subscriber data
+
+Figure 1 shows the general organization of the shared non-GPRS subscriber data stored in the HLR and VLR. Figure 2 shows the overall organization of subscriber data stored in HLR and SGSN. The figures 3 to 25 show the organization of the shared subscriber data stored in the HLR and VLR or in the HLR and SGSN. This structure is only valid for data stored in the registers and is not identical with the structure in the protocol, defining how data are transferred.
+
+NOTE: This description is only a model for the logical structure and does not define the specific implementation of the data storage.
+
+With this structure, the following general rules for the handling of subscriber data are defined:
+
+- the root of this data tree is always the IMSI which identifies the subscriber;
+
+- to address a specific parameter within this hierarchical tree, it is necessary to start from the IMSI and to go through the branches until the parameter is reached. The list of parameters met on the way defines the address of the parameter within the data structure;
+- to delete or insert a specific parameter, the complete address information is required;
+- if a parameter is inserted, all parameters in the address and the parameter itself shall be marked as present. A parameter value is stored irrespective of whether a value was already stored;
+- if a parameter is deleted, all parameters connected to it in the sub-branches are also deleted i.e. they are marked as not present;
+- if a parameter is overwritten with a new value, parameters connected to it in the sub-branches shall be set according to the rules of the individual service specification.
+
+In addition to the general rules given above, special rules apply to certain specific subscriber data. This is out of scope of this specification (see references in the notes in figures 1 to 25).
+
+## 4.5 Handling of supplementary service data with respect to basic service data
+
+Some supplementary service data is qualified by Elementary Basic Service Group (EBSG) data. This part of the service data is below the parameter "BSG" in the abstract data hierarchy, and is referred to as the "EBSG-related SS data". This clause provides special rules for handling of EBSG-related SS data.
+
+The internal representation of EBSGs and EBSG-related SS data in the HLR and VLR is outside the scope of this specification. For simplicity this description uses a model where all EBSG-related SS data is stored against individual EBSGs. Implementations may use alternative internal data structures.
+
+### 4.5.1 General
+
+EBSG-related SS data shall be stored in the HLR and VLR for all EBSGs that meet all the following criteria:
+
+- at least one basic service in the EBSG is supported; and
+- the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and
+- the subscriber has a subscription to at least one (possibly different) basic service in the EBSG.
+
+EBSG-related SS data shall not be stored for any other EBSGs.
+
+For each service for which the HLR sends EBSG-related SS data to the VLR, the HLR shall send the data for all EBSGs that meet all the following criteria:
+
+- at least one basic service in the EBSG is supported at the HLR; and
+- the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and
+- the subscriber has a subscription to at least one (possibly different) basic service in the EBSG.
+
+At any time, if the HLR has to send identical EBSG-Related SS data for several EBSGs, then it may be able to represent a set of EBSGs by a collective basic service group (CBSG), or by omitting the EBSG information altogether. This is specified in detail in 3GPP TS 29.002.
+
+### 4.5.2 Changes to basic service subscription
+
+Changes to the basic service subscription can impact EBSG-related SS data.
+
+If a new basic service is provisioned, and this is the first basic service to be provisioned for this subscriber in a particular EBSG, then the HLR shall update supplementary service data in the VLR if necessary. The HLR shall insert in the VLR EBSG-related SS data for the new EBSG for all supplementary services that:
+
+- have EBSG-related SS data; and
+
+- are applicable to at least one basic service in the new EBSG; and
+- are in a state where the VLR should receive data (normally this means the service must be provisioned).
+
+If a new basic service is provisioned, and this is not the first basic service provisioned for this subscriber in a particular EBSG, then the HLR is not required to send any new supplementary service data as a result.
+
+If a basic service is withdrawn, and this was the last remaining basic service provisioned for this subscriber in a particular EBSG, then when they are informed about the withdrawal of the basic service the HLR and VLR shall locally delete any supplementary service data relating to that EBSG.
+
+If a basic service is withdrawn, and this was not the last remaining basic service provisioned for this subscriber in a particular EBSG, then the HLR and VLR shall not make any changes to supplementary service data as a result.
+
+### 4.5.3 Special rules for BS61 and BS81 "alternate" and "followed-by" services
+
+There is no EBSG-related SS data for the groups BS61 and BS81 ("alternate" and "followed-by"). Instead, supplementary services related to these basic services are handled according to the bearer service group BS2x or BS3x corresponding to the data part of the "alternate" and "followed by" bearer service (see 3GPP TS 22.004). This means that special rules are required for subscribers with subscriptions to BS61 or BS81.
+
+For the handling of EBSG-related SS data, a subscription to BS61 or BS81 shall be treated in the same way as a subscription to a basic service in each of the groups "all data circuit asynchronous" and "all data circuit synchronous" (BS2x and BS3x). If a user subscribes to BS61 or BS81 then the HLR shall send any relevant EBSG-related SS data to the VLR for the groups BS2x and BS3x even if the subscriber does not subscribe to any basic services in the groups BS2x and BS3x.
+
+Examples:
+
+- if a user who does not subscribe to any basic services in BS2x or BS3x is given a subscription to BS81 then the HLR updates the VLR with any relevant EBSG-related SS data for the groups BS2x and BS3x. If the subscription to BS81 is then withdrawn, the VLR locally deletes all EBSG-related SS data for BS2x and BS3x.
+- if a user who has a subscription to BS21, but not to any basic services in BS3x is given a subscription to BS81 then the HLR updates the VLR with any relevant EBSG-related SS data for the group BS3x. If the subscription to BS81 is then withdrawn, the VLR locally deletes all EBSG-related SS data for BS3x (though not for BS2x).
+
+EBSG-related SS data shall not be qualified by the groups BS61 or BS81.
+
+### 4.5.4 Consistency of Supplementary Service data
+
+In some cases, the protocol used between the HLR and VLR encodes some data that is not EBSG-related SS data with an EBSG qualifier. In this case, the HLR shall ensure that when this data is sent it is always the same for all EBSGs. If this data is modified, the HLR must send the supplementary service data to the VLR for all EBSGs which meet all the following criteria:
+
+- at least one basic service in the EBSG is supported; and
+- the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and
+- the subscriber has a subscription to at least one (possibly different) basic service in the EBSG.
+
+![Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR)](8307f6b04df072c9332f9987e034272c_img.jpg)
+
+The diagram illustrates the hierarchical structure of non-GPRS subscriber data. At the root is the IMSI. Below it, several data elements are listed, some of which are grouped into boxes. The elements are: Basic MSISDN, Category, Basic Service List (boxed), Forwarding Info (boxed), Call Barring Info (boxed), CUG Info (boxed), SS Data (boxed), ODB Data for non-GPRS services (boxed), Roaming Restriction Data in the VLR (boxed), Regional Subscription Data (boxed), VBS, VGCS Data (boxed), CAMEL Subscription Info (boxed), NAEA, Preferred Carrier Id (boxed), LSA Data (boxed), IST Data (boxed), LMU Indicator, LCS Information (boxed), Super Charger Information (boxed), Bearer Service Priority Data (boxed), and Administrative Restriction Information (boxed).
+
+```
+graph TD; IMSI --- Basic_MSISDN[Basic MSISDN]; IMSI --- Category[Category]; IMSI --- BSL[Basic Service List]; IMSI --- FI[Forwarding Info]; IMSI --- CI[Call Barring Info]; IMSI --- CUG[CUG Info]; IMSI --- SD[SS Data]; IMSI --- ODB[ODB Data for non-GPRS services]; IMSI --- RRD[Roaming Restriction Data in the VLR]; IMSI --- RSD[Regional Subscription Data]; IMSI --- VBS[\"VBS, VGCS Data\"]; IMSI --- CSI[CAMEL Subscription Info]; IMSI --- NCI[\"NAEA, Preferred Carrier Id\"]; IMSI --- LSA[LSA Data]; IMSI --- IST[IST Data]; IMSI --- LMU[LMU Indicator]; IMSI --- LI[LCS Information]; IMSI --- SCI[Super Charger Information]; IMSI --- BPD[Bearer Service Priority Data]; IMSI --- ARI[Administrative Restriction Information];
+```
+
+Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR)
+
+Figure 1: Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR)
+
+![Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN)](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+This diagram illustrates the hierarchical structure of GPRS subscriber data sent to the SGSN. At the root is the IMSI. A vertical line descends from the IMSI, with horizontal branches leading to various data elements. The elements are: Access Mode, Basic MSISDN, Basic Service List (in a box), Call Barring Info (in a box), ODB Data for GPRS services (in a box), Roaming Restriction Data in the SGSN (in a box), Regional Subscription Data (in a box), GPRS subscription Data (in a box), EPS subscription Data (in a box), SGSN CAMEL subscription information (in a box), LSA Data (in a box), Super-Charger Information (in a box), Charging Information (in a box), LCS Information (in a box), and Administrative Restriction Information (in a box).
+
+Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN)
+
+Figure 2: Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN)
+
+![Basic Service List](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+This diagram shows the internal structure of the Basic Service List. It branches into two main categories: Teleservices and Bearer Services. Under Teleservices, there is a list of items: TS (1), a vertical ellipsis, and TS (n). Under Bearer Services, there is a similar list: BS (1), a vertical ellipsis, and BS (n).
+
+Basic Service List
+
+Figure 3: Basic Service List
+
+NOTE: For detailed information see 3GPP TS 22.001, 3GPP TS 22.002, 3GPP TS 22.003 and 3GPP TS 29.002.
+
+![A hierarchical tree diagram showing the structure of Forwarding Info. The root branches into five main categories: Call Forwarding Unconditional (CFU), Call Forwarding on mobile subscriber Busy (CFB), Call Forwarding on mobile subscriber Not Reachable (CFNRc), Call Forwarding on No Reply (CFNRy), and Call Deflection (CD). Each category has a list of sub-elements, with CFU, CFB, CFNRc, and CFNRy each containing BSG(1) and BSG(n) blocks with specific activation and registration states. CD contains Subscription Options and Provisioning State.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+```
+graph TD
+    Root[Forwarding Info] --> CFU[Call Forwarding Unconditional (CFU)]
+    Root --> CFB[Call Forwarding on mobile subscriber Busy (CFB)]
+    Root --> CFNRc[Call Forwarding on mobile subscriber Not Reachable (CFNRc)]
+    Root --> CFNRy[Call Forwarding on No Reply (CFNRy)]
+    Root --> CD[Call Deflection (CD)]
+
+    CFU --> CFU_1[Provisioning State]
+    CFU --> CFU_2[BSG(1)]
+    CFU --> CFU_3[....]
+    CFU --> CFU_4[BSG(n)]
+
+    CFU_2 --> CFU_2_1[Activation State]
+    CFU_2 --> CFU_2_2[Registration State]
+
+    CFU_4 --> CFU_4_1[Activation State]
+    CFU_4 --> CFU_4_2[Registration State]
+
+    CFB --> CFB_1[Subscription Options]
+    CFB --> CFB_2[Provisioning State]
+    CFB --> CFB_3[BSG(1)]
+    CFB --> CFB_4[....]
+    CFB --> CFB_5[BSG(n)]
+
+    CFB_3 --> CFB_3_1[Activation State]
+    CFB_3 --> CFB_3_2[Registration State]
+    CFB_3 --> CFB_3_3[Forwarded-to Number]
+    CFB_3_3 --> CFB_3_3_1[Subaddress]
+
+    CFB_5 --> CFB_5_1[Activation State]
+    CFB_5 --> CFB_5_2[Registration State]
+    CFB_5 --> CFB_5_3[Forwarded-to Number]
+    CFB_5_3 --> CFB_5_3_1[Subaddress]
+
+    CFNRc --> CFNRc_1[Subscription Options]
+    CFNRc --> CFNRc_2[Provisioning State]
+    CFNRc --> CFNRc_3[BSG(1)]
+    CFNRc --> CFNRc_4[....]
+    CFNRc --> CFNRc_5[BSG(n)]
+
+    CFNRc_3 --> CFNRc_3_1[Activation State]
+    CFNRc_3 --> CFNRc_3_2[Registration State]
+    CFNRc_3 --> CFNRc_3_3[Forwarded-to Number]
+    CFNRc_3_3 --> CFNRc_3_3_1[Subaddress]
+
+    CFNRc_5 --> CFNRc_5_1[Activation State]
+    CFNRc_5 --> CFNRc_5_2[Registration State]
+    CFNRc_5 --> CFNRc_5_3[Forwarded-to Number]
+    CFNRc_5_3 --> CFNRc_5_3_1[Subaddress]
+
+    CFNRy --> CFNRy_1[Subscription Options]
+    CFNRy --> CFNRy_2[Provisioning State]
+    CFNRy --> CFNRy_3[BSG(1)]
+    CFNRy --> CFNRy_4[....]
+    CFNRy --> CFNRy_5[BSG(n)]
+
+    CFNRy_3 --> CFNRy_3_1[Activation State]
+    CFNRy_3 --> CFNRy_3_2[Registration State]
+    CFNRy_3 --> CFNRy_3_3[No Reply Condition Timer]
+    CFNRy_3 --> CFNRy_3_4[Forwarded-to Number]
+    CFNRy_3_4 --> CFNRy_3_4_1[Subaddress]
+
+    CFNRy_5 --> CFNRy_5_1[Activation State]
+    CFNRy_5 --> CFNRy_5_2[Registration State]
+    CFNRy_5 --> CFNRy_5_3[No Reply Condition Timer]
+    CFNRy_5 --> CFNRy_5_4[Forwarded-to Number]
+    CFNRy_5_4 --> CFNRy_5_4_1[Subaddress]
+
+    CD --> CD_1[Subscription Options]
+    CD --> CD_2[Provisioning State]
+```
+
+A hierarchical tree diagram showing the structure of Forwarding Info. The root branches into five main categories: Call Forwarding Unconditional (CFU), Call Forwarding on mobile subscriber Busy (CFB), Call Forwarding on mobile subscriber Not Reachable (CFNRc), Call Forwarding on No Reply (CFNRy), and Call Deflection (CD). Each category has a list of sub-elements, with CFU, CFB, CFNRc, and CFNRy each containing BSG(1) and BSG(n) blocks with specific activation and registration states. CD contains Subscription Options and Provisioning State.
+
+NOTE: For detailed information see 3GPP TS 23.072, 3GPP TS 23.082 and 3GPP TS 29.002.
+
+**Figure 4: Forwarding Info**
+
+![Hierarchical tree diagram for Call Barring Info showing BAOC, BOIC, and BOIC-exHC categories with their respective provisioning states and barring subgroups (BSG).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+```
+
+└Barring of All Outgoing Calls (BAOC)
+├Provisioning State
+├BSG(1)
+│└Activation State
+├.....
+└BSG(n)
+└Activation State
+└Barring of Outgoing International Calls (BOIC)
+├Provisioning State
+├BSG(1)
+│└Activation State
+├.....
+└BSG(n)
+└Activation State
+└Barring of Outgoing International Calls except
+  those directed to the Home PLMN Country (BOIC-exHC)
+├Provisioning State
+├BSG(1)
+│└Activation State
+├.....
+└BSG(n)
+└Activation State
+
+```
+
+Hierarchical tree diagram for Call Barring Info showing BAOC, BOIC, and BOIC-exHC categories with their respective provisioning states and barring subgroups (BSG).
+
+NOTE: For detailed information see 3GPP TS 23.088 and 3GPP TS 29.002.
+
+**Figure 5: Call Barring Info**
+
+![Hierarchical tree diagram for CUG Info showing Closed User Group (CUG) details including Interlock, BSG, and Preferential CUG settings.](2eb23c2210154279f8013a1594fbcc5a_img.jpg)
+
+```
+
+└Closed User Group (CUG)
+├Interlock(1)
+│├CUG Index
+│├Intra CUG Restrictions
+│├BSG(1)
+│├.....
+│└BSG(n)
+├.....
+├Interlock(m)
+│├CUG Index
+│├Intra CUG Restrictions
+│├BSG(1)
+│├.....
+│└BSG(n)
+├BSG(1)
+│├Preferential CUG
+│└Inter CUG Accessibility
+├.....
+└BSG(n)
+├Preferential CUG
+└Inter CUG Accessibility
+
+```
+
+Hierarchical tree diagram for CUG Info showing Closed User Group (CUG) details including Interlock, BSG, and Preferential CUG settings.
+
+NOTE: For detailed information see 3GPP TS 23.085 and 3GPP TS 29.002.
+
+**Figure 6: CUG Info**
+
+- Calling Line Identification Presentation (CLIP)
+  - Provisioning State
+  - Activation State
+  - Override Category
+- Calling Line Identification Restriction (CLIR)
+  - Provisioning State
+  - Activation State
+  - Presentation Mode
+- Connected Line identification Presentation (COLP)
+  - Provisioning State
+  - Activation State
+  - Override Category
+- Connected Line identification Restriction (COLR)
+  - Provisioning State
+  - Activation State
+- Call Waiting (CW)
+  - Provisioning State
+  - BSG (1)
+    - Activation State
+  - .....
+  - BSG (n)
+    - Activation State
+- Call Hold (HOLD)
+  - Provisioning State
+  - Activation State
+- Multi Party (MPTY)
+  - Provisioning State
+  - Activation State
+- Advice of Charge Information (AoCI)
+  - Provisioning State
+  - Activation State
+- Advice of Charge Charging (AoCC)
+  - Provisioning State
+  - Activation State
+- Explicit Call Transfer (ECT)
+  - Provisioning State
+  - Activation State
+- Calling Name Presentation (CNAP)
+  - Provisioning State
+  - Activation State
+  - Override Category
+- enhanced Multi-Level Precedence Pre-Emption (eMLPP)
+  - Provisioning State
+  - Activation State
+  - Maximum Entitled Priority
+  - Default
+- Multicall (MC)
+  - Provisioning State
+  - Activation State
+  - Registration State
+  - Subscribed maximum CS bearers
+  - User defined maximum CS bearers
+
+![A hierarchical tree diagram showing various network service classes and their associated states. The root branches into 'Completion of Calls to Busy Subscriber (CCBS)-originating NW' and 'Completion of Calls to Busy Subscriber (CCBS)-destination NW'. The 'LCS Privacy Exception' section includes Universal, Call Session Related, Call Session Unrelated, PLMN Operator, and Service Type classes. The 'MO-LR' section includes Basic Self Location, Autonomous Self Location, and Transfer To Third Party classes. Most classes have 'Provisioning State', 'Activation State', and 'Registration State' as sub-items, though some omit 'Registration State'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+```
+graph TD
+    Root[ ] --- CCBS_O[Completion of Calls to Busy Subscriber (CCBS)-originating NW]
+    Root --- CCBS_D[Completion of Calls to Busy Subscriber (CCBS)-destination NW]
+    CCBS_O --- PS_O[Provisioning State]
+    CCBS_O --- AS_O[Activation State]
+    CCBS_D --- PS_D[Provisioning State]
+    CCBS_D --- AS_D[Activation State]
+    Root --- LCS_UE[LCS Privacy Exception Class Universal]
+    LCS_UE --- PS_UE[Provisioning State]
+    LCS_UE --- AS_UE[Activation State]
+    LCS_UE --- RS_UE[Registration State]
+    Root --- LCS_CSR[LCS Privacy Exception Class Call Session Related]
+    LCS_CSR --- PS_CSR[Provisioning State]
+    LCS_CSR --- AS_CSR[Activation State]
+    LCS_CSR --- RS_CSR[Registration State]
+    Root --- LCS_CSU[LCS Privacy Exception Class Call Session Unrelated]
+    LCS_CSU --- PS_CSU[Provisioning State]
+    LCS_CSU --- AS_CSU[Activation State]
+    LCS_CSU --- RS_CSU[Registration State]
+    Root --- LCS_PO[LCS Privacy Exception Class PLMN Operator]
+    LCS_PO --- PS_PO[Provisioning State]
+    LCS_PO --- AS_PO[Activation State]
+    LCS_PO --- RS_PO[Registration State]
+    Root --- LCS_ST[LCS Privacy Exception Class Service Type]
+    LCS_ST --- PS_ST[Provisioning State]
+    LCS_ST --- AS_ST[Activation State]
+    LCS_ST --- RS_ST[Registration State]
+    Root --- MO_LR_BS[MO-LR Class Basic Self Location]
+    MO_LR_BS --- PS_BS[Provisioning State]
+    MO_LR_BS --- AS_BS[Activation State]
+    MO_LR_BS --- RS_BS[Registration State]
+    Root --- MO_LR_AS[MO-LR Class Autonomous Self Location]
+    MO_LR_AS --- PS_AS[Provisioning State]
+    MO_LR_AS --- AS_AS[Activation State]
+    MO_LR_AS --- RS_AS[Registration State]
+    Root --- MO_LR_TTP[MO-LR Class Transfer To Third Party]
+    MO_LR_TTP --- PS_TTP[Provisioning State]
+    MO_LR_TTP --- AS_TTP[Activation State]
+    MO_LR_TTP --- RS_TTP[Registration State]
+```
+
+A hierarchical tree diagram showing various network service classes and their associated states. The root branches into 'Completion of Calls to Busy Subscriber (CCBS)-originating NW' and 'Completion of Calls to Busy Subscriber (CCBS)-destination NW'. The 'LCS Privacy Exception' section includes Universal, Call Session Related, Call Session Unrelated, PLMN Operator, and Service Type classes. The 'MO-LR' section includes Basic Self Location, Autonomous Self Location, and Transfer To Third Party classes. Most classes have 'Provisioning State', 'Activation State', and 'Registration State' as sub-items, though some omit 'Registration State'.
+
+NOTE: For detailed information see 3GPP TS 23.067, 3GPP TS 23.081, 3GPP TS 23.083, 3GPP TS 23.084, 3GPP TS 23.086, 3GPP TS 23.091, 3GPP TS 23.093, 3GPP TS 23.096, 3GPP TS 23.135, 3GPP TS 29.002 and 3GPP TS 23.071.
+
+The codes below are used for the single purpose of enabling the visited network to notify the home network whether or not the particular Supplementary Service is supported. These codes are also included in the LCS Information parameter and the visited network shall use the codes in the LCS Information parameter, and only this parameter, to obtain the information needed for the LCS Supplementary Service.
+
+- LCS Privacy Exception Class Universal
+- LCS Privacy Exception Class Call Session Related
+- LCS Privacy Exception Class Call Session Unrelated
+- LCS Privacy Exception Class PLMN Operator
+- LCS Privacy Exception Class Service Type
+- MO-LR Class Basic Self Location
+- MO-LR Class Autonomous Self Location
+
+- MO-LR Class Transfer To Third Party
+
+**Figure 7: SS Data**
+
+```
+
+└Subscriber Status
+├all OG-Calls Barred
+├international OG-Calls Barred
+├international OG-Calls Not To HPLMN Country Barred
+├inter-zonal OG-Calls Barred
+├inter-zonal OG-Calls Not To HPLMN Country Barred
+├international OG-Calls Not To HPLMN Country AND
+  inter-zonal OG-Calls Barred
+├Premium Rate Information OG-Calls Barred
+├Premium Rate Entertainment OG-Calls Barred
+├SS Access Barred
+├all call transfers Barred
+├chargeable call transfers Barred
+├international call transfers Barred
+├inter-zonal call transfers Barred
+├doubly chargeable call transfers Barred
+├multiple call transfers Barred
+├PLMN-Specific Barring Type 1
+├PLMN-Specific Barring Type 2
+├PLMN-Specific Barring Type 3
+└PLMN-Specific Barring Type 4
+
+```
+
+NOTE: For detailed information see 3GPP TS 23.015 and 3GPP TS 29.002.
+
+**Figure 8: ODB Data for non-GPRS services**
+
+```
+
+└Subscriber Status
+├all OG-Calls Barred
+├international OG-Calls Barred
+├international OG-Calls Not To HPLMN Country Barred
+├inter-zonal OG-Calls Barred
+├inter-zonal OG-Calls Not To HPLMN Country Barred
+├international OG-Calls Not To HPLMN Country AND
+  inter-zonal OG-Calls Barred
+├PLMN-Specific Barring Type 1
+├PLMN-Specific Barring Type 2
+├PLMN-Specific Barring Type 3
+├PLMN-Specific Barring Type 4
+├All Packet Oriented Services Barred
+├Roamer Access To HPLMN AP-Barred
+└Roamer Access To VPLMN AP-Barred
+
+```
+
+NOTE: For detailed information see 3G TS 23.015 and 3G TS 29.002.
+
+**Figure 9: ODB Data for GPRS services**
+
+```
+
+└Roaming Restriction Due To Unsupported Feature
+
+```
+
+NOTE: For detailed information see 3GPP TS 29.002.
+
+**Figure 10: Roaming Restriction Data in the VLR**
+
+```
+
+└Roaming Restricted in the SGSN Due To Unsupported Feature
+
+```
+
+NOTE: For detailed information see 3GPP TS 29.002.
+
+**Figure 11: Roaming Restriction Data in the SGSN**
+
+![Diagram of Regional Subscription Data structure](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg)
+
+```
+└ZoneCode (1)
+└.....
+└ZoneCode (k)
+```
+
+A hierarchical diagram showing a list of ZoneCodes. It starts with ZoneCode (1), followed by an ellipsis, and ends with ZoneCode (k).
+
+Diagram of Regional Subscription Data structure
+
+NOTE: For detailed information see 3GPP TS 29.002.
+
+**Figure 12: Regional Subscription Data**
+
+![Diagram of VGCS membership List structure](171115f072e42b379238ed0dd438e9d7_img.jpg)
+
+```
+└VGCS membership List
+└Group-Id (1)
+└.....
+└Group-Id (n)
+```
+
+A hierarchical diagram showing a VGCS membership list. It starts with VGCS membership List, followed by Group-Id (1), an ellipsis, and Group-Id (n).
+
+Diagram of VGCS membership List structure
+
+NOTE: For detailed information see 3GPP TS 43.068 and 3GPP TS 29.002.
+
+**Figure 13: Voice Group Call Data**
+
+![Diagram of VBS membership List structure](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg)
+
+```
+└VBS membership List
+└Group-Id (1)
+└Broadcast Call Initiation Entitlement
+└.....
+└Group-Id (n)
+└Broadcast Call Initiation Entitlement
+```
+
+A hierarchical diagram showing a VBS membership list. It starts with VBS membership List, followed by Group-Id (1) with its associated Broadcast Call Initiation Entitlement, an ellipsis, and Group-Id (n) with its associated Broadcast Call Initiation Entitlement.
+
+Diagram of VBS membership List structure
+
+NOTE: For detailed information see 3GPP TS 43.069 and 3GPP TS 29.002.
+
+**Figure 14: Voice Broadcast Call Data**
+
+![A hierarchical tree diagram showing CAMEL Subscription Information. The root is 'CAMEL Subscription Information', which branches into four main categories: 'Originating CAMEL Subscription Info', 'Dialled Service CAMEL Subscription Info', 'VMS C Terminating CAMEL Subscription Info', and 'SS Invocation Notification CAMEL Subscription Info'. Each category has its own sub-elements, such as TDP Data Lists, DP Criteria Lists, and CAMEL Capability Handling.](26d664119ad25250780f554633444e54_img.jpg)
+
+```
+graph TD; Root[CAMEL Subscription Information] --- OCSI[Originating CAMEL Subscription Info]; Root --- DSCSI[Dialled Service CAMEL Subscription Info]; Root --- VTCSI[VMS C Terminating CAMEL Subscription Info]; Root --- SINCSI[SS Invocation Notification CAMEL Subscription Info]; OCSI --- TDL[TDP Data List]; OCSI --- CCH1[CAMEL Capability Handling]; TDL --- OBCSM1[O-BCSM CAMEL TDP Data (1)]; TDL --- Dots1[.....]; TDL --- OBCSMn[O-BCSM CAMEL TDP Data (n)]; OBCSM1 --- OBCSM1_1[O-BCSM TDP]; OBCSM1 --- OBCSM1_2[DP Criteria]; OBCSM1 --- OBCSM1_3[Service Key]; OBCSM1 --- OBCSM1_4[gsmSCF Address]; OBCSM1 --- OBCSM1_5[Default Call Handling]; OBCSMn --- OBCSMn_1[O-BCSM TDP]; OBCSMn --- OBCSMn_2[DP Criteria]; OBCSMn --- OBCSMn_3[Service Key]; OBCSMn --- OBCSMn_4[gsmSCF Address]; OBCSMn --- OBCSMn_5[Default Call Handling]; DSCSI --- DCL[DP Criteria List]; DSCSI --- CCH2[CAMEL Capability Handling]; DCL --- DC1[DP Criterion (1)]; DCL --- Dots2[.....]; DCL --- DCn[DP Criterion (n)]; DC1 --- DC1_1[Service Key]; DC1 --- DC1_2[gsmSCF Address]; DC1 --- DC1_3[Default Call Handling]; DCn --- DCn_1[Service Key]; DCn --- DCn_2[gsmSCF Address]; DCn --- DCn_3[Default Call Handling]; VTCSI --- TDL2[TDP Data List]; VTCSI --- CCH3[CAMEL Capability Handling]; TDL2 --- VTBCSM1[VT-BCSM CAMEL TDP Data (1)]; TDL2 --- Dots3[.....]; TDL2 --- VTBCSMn[VT-BCSM CAMEL TDP Data (n)]; VTBCSM1 --- VTBCSM1_1[VT-BCSM TDP]; VTBCSM1 --- VTBCSM1_2[DP Criteria]; VTBCSM1 --- VTBCSM1_3[Service Key]; VTBCSM1 --- VTBCSM1_4[gsmSCF Address]; VTBCSM1 --- VTBCSM1_5[Default Call Handling]; VTBCSMn --- VTBCSMn_1[VT-BCSM TDP]; VTBCSMn --- VTBCSMn_2[DP Criteria]; VTBCSMn --- VTBCSMn_3[Service Key]; VTBCSMn --- VTBCSMn_4[gsmSCF Address]; VTBCSMn --- VTBCSMn_5[Default Call Handling]; SINCSI --- NC[Notification Criterion]; SINCSI --- gsmSCF[ gsmSCF Address]; SINCSI --- AF1[Activation Flag]; SINCSI --- NF[Notification Flag];
+```
+
+A hierarchical tree diagram showing CAMEL Subscription Information. The root is 'CAMEL Subscription Information', which branches into four main categories: 'Originating CAMEL Subscription Info', 'Dialled Service CAMEL Subscription Info', 'VMS C Terminating CAMEL Subscription Info', and 'SS Invocation Notification CAMEL Subscription Info'. Each category has its own sub-elements, such as TDP Data Lists, DP Criteria Lists, and CAMEL Capability Handling.
+
+![A hierarchical tree diagram showing CAMEL subscription information. The root is a vertical line. To its right are: 'Notify on Change of Subscriber Data Flag', 'Translation Information Flag CAMEL Subscription Information', 'MO SMS CAMEL Subscription Info', and 'MT SMS CAMEL Subscription Info'. Below 'MT SMS CAMEL Subscription Info' are: 'Mobility Management Event Notification CAMEL Subscription Info', 'Mobility Trigger List', 'Service Key', and 'gsmSCF Address'.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+```
+graph LR; Root[ ] --- NCSDF[Notify on Change of Subscriber Data Flag]; Root --- TIFCSI[Translation Information Flag CAMEL Subscription Information]; Root --- MOSMS[MO SMS CAMEL Subscription Info]; Root --- MTMS[MT SMS CAMEL Subscription Info]; MTMS --- MMENCSI[Mobility Management Event Notification CAMEL Subscription Info]; MTMS --- MTL[Mobility Trigger List]; MTMS --- SK[Service Key]; MTMS --- GSMSCF[gsmSCF Address]; style Root fill:none,stroke:none
+```
+
+A hierarchical tree diagram showing CAMEL subscription information. The root is a vertical line. To its right are: 'Notify on Change of Subscriber Data Flag', 'Translation Information Flag CAMEL Subscription Information', 'MO SMS CAMEL Subscription Info', and 'MT SMS CAMEL Subscription Info'. Below 'MT SMS CAMEL Subscription Info' are: 'Mobility Management Event Notification CAMEL Subscription Info', 'Mobility Trigger List', 'Service Key', and 'gsmSCF Address'.
+
+NOTE: For detailed information see 3GPP TS 23.072, 3GPP TS 23.078 and 3GPP TS 29.002.
+
+**Figure 15: CAMEL subscription info**
+
+![A hierarchical tree diagram showing the structure of LCS Information. The root is 'LCS Information', which branches into 'GMLC List', 'LCS Privacy Exception List', 'PLMN Operator Privacy Class', 'MO-LR List', and 'LCS Service Types'. Each of these branches further subdivides into specific classes and their attributes, such as 'Universal Privacy Class', 'Call/Session Related Privacy Class', 'Basic Self Location Class', etc.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg)
+
+```
+
+LCS Information
+├── GMLC List
+│   ├── GMLC Address (1)
+│   └── GMLC Address (n)
+├── LCS Privacy Exception List
+│   ├── Universal Privacy Class
+│   │   ├── Provisioning State
+│   │   ├── Activation State
+│   │   └── Registration State
+│   ├── Call/Session Related Privacy Class
+│   │   ├── Provisioning State
+│   │   ├── Activation State
+│   │   ├── Registration State
+│   │   ├── Notification to MS User
+│   │   └── External Client List
+│   │       ├── External Client (1)
+│   │       │   ├── Address
+│   │       │   ├── Notification to MS User
+│   │       │   └── GMLC restriction
+│   │       │   .....
+│   │       └── External Client (n)
+│   │           ├── Address
+│   │           ├── Notification to MS User
+│   │           └── GMLC restriction
+│   ├── Call/Session Unrelated Privacy Class
+│   │   ├── Provisioning State
+│   │   ├── Activation State
+│   │   ├── Registration State
+│   │   ├── External Client List
+│   │   │   ├── External Client (1)
+│   │   │   │   ├── Address
+│   │   │   │   ├── Notification to MS User
+│   │   │   │   └── GMLC restriction
+│   │   │   │   .....
+│   │   │   └── External Client (n)
+│   │   │       ├── Address
+│   │   │       ├── Notification to MS User
+│   │   │       └── GMLC restriction
+│   │   └── Notification to MS User
+│   └── PLMN Operator Privacy Class
+│       ├── Provisioning State
+│       ├── Activation State
+│       ├── Registration State
+│       └── PLMN Client List
+│           ├── PLMN client ID (1)
+│           │   .....
+│           └── PLMN client ID (n)
+├── MO-LR List
+│   ├── Basic Self Location Class
+│   │   ├── Provisioning State
+│   │   ├── Activation State
+│   │   └── Registration State
+│   ├── Autonomous Self Location Class
+│   │   ├── Provisioning State
+│   │   ├── Activation State
+│   │   └── Registration State
+│   └── Transfer to Third Party Class
+│       ├── Provisioning State
+│       ├── Activation State
+│       └── Registration State
+└── LCS Service Types
+    ├── Provisioning State
+    ├── Activation State
+    ├── Registration State
+    ├── Service Type List
+    └── Service Type Identity (1)
+
+```
+
+A hierarchical tree diagram showing the structure of LCS Information. The root is 'LCS Information', which branches into 'GMLC List', 'LCS Privacy Exception List', 'PLMN Operator Privacy Class', 'MO-LR List', and 'LCS Service Types'. Each of these branches further subdivides into specific classes and their attributes, such as 'Universal Privacy Class', 'Call/Session Related Privacy Class', 'Basic Self Location Class', etc.
+
+![Diagram showing LCS Information structure with Notification to MS User and GMLC restriction.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+- ... | .. | ... |—Notification to MS User
+- └—GMLC restriction
+- ... | .. | ... |—....
+- ... | .. | ... |—Service Type Identity (n)
+- ├—Notification to MS User
+- └—GMLC restriction
+
+Diagram showing LCS Information structure with Notification to MS User and GMLC restriction.
+
+NOTE: For detailed information see 3GPP TS 23.271 and 3GPP TS 29.002.
+
+**Figure 16: LCS Information**
+
+![Diagram showing PDP Context List structure with multiple PDP Context entries.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg)
+
+- └—PDP Context List
+  - ├—PDP Context (1)
+    - ├—PDP Context Identifier
+    - ├—PDP Type
+    - ├—PDP Address
+    - ├—VPLMN Address Allowed
+    - ├—Quality of Service Subscribed
+    - ├—Access Point Name
+    - └—PDP Context Charging Characteristics
+  - ├—....
+  - └—PDP Context (n)
+
+Diagram showing PDP Context List structure with multiple PDP Context entries.
+
+NOTE: The figure shows the information in the SGSN. For detailed information see 3GPP TS 23.060. For information about the GGSN information, see 3GPP TS 23.008.
+
+**Figure 17: GPRS subscription data**
+
+![Diagram showing APN Configuration List structure with Default Context and multiple APN Configuration entries.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg)
+
+- └—APN Configuration List
+  - ...
+  - ├—Default Context
+  - ├—APN Configuration (1)
+    - ├—Context Identifier
+    - ├—PDN Type
+    - ├—Served Party IPv4 Address
+    - ├—APN
+    - ├—EPS QoS Subscribed
+    - ├—PDN GW Identity
+    - ├—PDN GW Allocation Type
+    - ├—VPLMN Address Allowed
+    - ├—Charging Characteristics
+    - ├—AMBR
+    - ├—Specific APN Info List
+    - └—Served Party IPv6 Address
+  - ├—....
+  - └—APN Configuration (n)
+
+Diagram showing APN Configuration List structure with Default Context and multiple APN Configuration entries.
+
+**Figure 17a: EPS subscription data**
+
+![Diagram of LSA data in the VLR structure showing LSA Only Access Indicator and a list of LSA Data entries containing Identity, Attributes, and Active Mode Indicator.](28d75f39a24203712ee907b32cf0bbe5_img.jpg)
+
+```
+
+—LSA Only Access Indicator
+—LSA Data List
+   |
+   —LSA Data (1)
+   |  —LSA Identity
+   |  —LSA Attributes
+   |  —LSA Active Mode Indicator
+   |
+   — . . . .
+   |
+   —LSA Data (n)
+  
+```
+
+Diagram of LSA data in the VLR structure showing LSA Only Access Indicator and a list of LSA Data entries containing Identity, Attributes, and Active Mode Indicator.
+
+NOTE: For detailed information see 3GPP TS 23.073 and 3GPP TS 29.002.
+
+**Figure 18: LSA data in the VLR**
+
+![Diagram of LSA data in the SGSN structure, identical to Figure 18.](f0a97d0d3818a253c1d2a009966081b1_img.jpg)
+
+```
+
+—LSA Only Access Indicator
+—LSA Data List
+   |
+   —LSA Data (1)
+   |  —LSA Identity
+   |  —LSA Attributes
+   |  —LSA Active Mode Indicator
+   |
+   — . . . .
+   |
+   —LSA Data (n)
+  
+```
+
+Diagram of LSA data in the SGSN structure, identical to Figure 18.
+
+NOTE: For detailed information see 3GPP TS 23.073 and 3GPP TS 29.002.
+
+**Figure 19: LSA data in the SGSN**
+
+![Diagram of IST data in the VLR showing a single entry: IST Alert Timer.](e9b43ac020435f8121e8592f31afdc52_img.jpg)
+
+```
+
+—IST Alert Timer
+  
+```
+
+Diagram of IST data in the VLR showing a single entry: IST Alert Timer.
+
+NOTE: For detailed information see 3GPP TS 43.035 and 3GPP TS 29.002.
+
+**Figure 20: IST data in the VLR**
+
+└Age Indicator
+
+NOTE: For detailed information see TS 23.116 and TS 29.002.
+
+**Figure 21: Super-Charger Information**
+
+![Hierarchical tree diagram for Super-Charger Information showing GPRS CAMEL Subscription Information, TDP Data List, CAMEL Capability Handling, MO SMS CAMEL Subscription Info, MT SMS CAMEL Subscription Info, and Mobility Management Event for GPRS Notification CAMEL Subscription Info.](6470d350326789d5306eabcb76533951_img.jpg)
+
+```
+└SGSN CAMEL subscription information
+├ GPRS CAMEL Subscription Information
+│ ├── TDP Data List
+│ │ ├── GPRS CAMEL TDP Data (1)
+│ │ │ ├── GPRS TDP
+│ │ │ ├── Service Key
+│ │ │ ├── gsmSCF Address
+│ │ │ └ Default GPRS Handling
+│ │ ├── ....
+│ │ └ GPRS CAMEL TDP Data (n)
+│ │ │ ├── GPRS TDP
+│ │ │ ├── Service Key
+│ │ │ ├── gsmSCF Address
+│ │ │ └ Default GPRS Handling
+│ ├── CAMEL Capability Handling
+├ MO SMS CAMEL Subscription Info
+├ MT SMS CAMEL Subscription Info
+└ Mobility Management Event for GPRS Notification CAMEL Subscription Info
+├ Mobility Trigger List
+├ Service Key
+└ gsmSCF Address
+```
+
+Hierarchical tree diagram for Super-Charger Information showing GPRS CAMEL Subscription Information, TDP Data List, CAMEL Capability Handling, MO SMS CAMEL Subscription Info, MT SMS CAMEL Subscription Info, and Mobility Management Event for GPRS Notification CAMEL Subscription Info.
+
+**Figure 22: SGSN CAMEL subscription info**
+
+![Hierarchical tree diagram for MO SMS CAMEL Subscription Info showing TDP Data List, MO SMS CAMEL TDP Data (1), MO SMS CAMEL TDP Data (n), and CAMEL Capability Handling.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg)
+
+```
+└ MO SMS CAMEL Subscription Info
+├ TDP Data List
+│ ├── MO SMS CAMEL TDP Data (1)
+│ │ ├── MO SMS TDP
+│ │ ├── Service Key
+│ │ ├── gsmSCF Address
+│ │ └ Default SMS Handling
+│ ├── ....
+│ └ MO SMS CAMEL TDP Data (n)
+│ │ ├── MO SMS TDP
+��� │ ├── Service Key
+│ │ ├── gsmSCF Address
+│ │ └ Default SMS Handling
+└ CAMEL Capability Handling
+```
+
+Hierarchical tree diagram for MO SMS CAMEL Subscription Info showing TDP Data List, MO SMS CAMEL TDP Data (1), MO SMS CAMEL TDP Data (n), and CAMEL Capability Handling.
+
+**Figure 23a: MO SMS CAMEL Subscription Info**
+
+![Figure 23b: MT SMS CAMEL Subscription Info](00504fc688ebcf131ccbeff94dfc9939_img.jpg)
+
+```
+
+├ MT SMS CAMEL Subscription Info
+│   ├ TDP Data List
+│   │   ├ MT SMS CAMEL TDP Data (1)
+│   │   │   ├ MT SMS TDP
+│   │   │   ├ DP Criteria
+│   │   │   ├ Service Key
+│   │   │   ├ gsmSCF Address
+│   │   │   └ Default SMS Handling
+│   │   ├ . . . . .
+│   │   └ MT SMS CAMEL TDP Data (n)
+│   │       ├ MT SMS TDP
+│   │       ├ DP Criteria
+│   │       ├ Service Key
+│   │       ├ gsmSCF Address
+│   │       └ Default SMS Handling
+│   └ CAMEL Capability Handling
+
+```
+
+Figure 23b: MT SMS CAMEL Subscription Info
+
+**Figure 23b: MT SMS CAMEL Subscription Info**![Figure 24: Bearer Service Priority Data in the VLR](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg)
+
+```
+
+└ CS Allocation/Retention priority
+
+```
+
+Figure 24: Bearer Service Priority Data in the VLR
+
+NOTE: For detailed information see 3GPP TS 23.008.
+
+**Figure 24: Bearer Service Priority Data in the VLR**![Figure 25: Charging Information](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg)
+
+```
+
+└ Subscribed Charging Characteristics
+
+```
+
+Figure 25: Charging Information
+
+NOTE: For detailed information see 3GPP TS 23.060.
+
+**Figure 25: Charging Information.**![Figure 26: Administrative Restriction Information in the VLR](ca5dc5fde2061d0ca2051ef7840fc842_img.jpg)
+
+```
+
+└ Access Restriction Data
+
+```
+
+Figure 26: Administrative Restriction Information in the VLR
+
+NOTE: For detailed information see 3GPP TS 23.012 [34].
+
+**Figure 26: Administrative Restriction Information in the VLR**

marked/Rel-18/23_series/23034/raw.md

@@ -0,0 +1,1001 @@
+
+
+# 3GPP TS 23.034 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; High Speed Circuit Switched Data (HSCSD); Stage 2 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                      |           |
+|--------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                       | 4         |
+| 1 Scope.....                                                                         | 5         |
+| 2 References.....                                                                    | 5         |
+| 3 Definitions.....                                                                   | 6         |
+| 4 Main concepts .....                                                                | 7         |
+| 4.1 HSCSD service aspects .....                                                      | 8         |
+| 4.2 HSCSD service aspects in UTRAN Iu mode.....                                      | 9         |
+| 4.2.1 UTRAN Iu mode to GERAN Iu mode or A/Gb mode handover .....                     | 9         |
+| 5 HSCSD architecture and transmission .....                                          | 9         |
+| 5.1 Air interface.....                                                               | 9         |
+| 5.2 Functions and information flows.....                                             | 10        |
+| 5.2.1 Call establishment procedures.....                                             | 10        |
+| 5.2.1.1 Mobile originated call establishment (A/Gb mode) .....                       | 10        |
+| 5.2.1.1a Mobile originated call establishment (GERAN Iu mode) .....                  | 12        |
+| 5.2.1.2 Mobile terminated call establishment (A/Gb mode).....                        | 13        |
+| 5.2.1.2a Mobile terminated call establishment (GERAN Iu mode) .....                  | 14        |
+| 5.2.2 Handover procedures.....                                                       | 16        |
+| 5.2.2.1 Intra BSC handover (A/Gb mode) .....                                         | 16        |
+| 5.2.2.1a Intra BSC handover (GERAN Iu mode).....                                     | 16        |
+| 5.2.2.2 Inter BSC, intra-MSC handover (A/Gb mode).....                               | 18        |
+| 5.2.2.2a Inter BSC, intra-MSC handover (GERAN Iu mode).....                          | 19        |
+| 5.2.2.3 Inter MSC handover.....                                                      | 20        |
+| 5.2.3 Resource upgrading, downgrading and configuration change (A/Gb mode).....      | 20        |
+| 5.2.3a Resource upgrading, downgrading and configuration change (GERAN Iu mode)..... | 22        |
+| 5.2.4 User initiated service level up- and downgrading (A/Gb mode).....              | 23        |
+| 5.2.4a User initiated service level up- and downgrading (GERAN Iu mode).....         | 24        |
+| 5.2.5 Link adaptation for ECSD .....                                                 | 25        |
+| 5.2.6 Start of ciphering .....                                                       | 25        |
+| 5.3 Transparent data transmission.....                                               | 25        |
+| 5.3.1 Numbering of data substreams .....                                             | 25        |
+| 5.3.2 Padding .....                                                                  | 25        |
+| 5.4 Non-Transparent data transmission.....                                           | 25        |
+| 5.4.1 HSCSD RLP .....                                                                | 25        |
+| 5.5 Interworking .....                                                               | 26        |
+| 5.6 Subscription aspects and storage of subscriber data .....                        | 26        |
+| 6 Charging.....                                                                      | 26        |
+| 6.1 General principles .....                                                         | 26        |
+| 6.2 Call forwardings .....                                                           | 26        |
+| 6.3 AoC and toll ticketing .....                                                     | 26        |
+| <b>Annex A (informative): Change history.....</b>                                    | <b>27</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document specifies the Stage 2 description of High Speed Circuit Switched Data (HSCSD) 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 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 contains the stage 2 service description for a High Speed Circuit Switched Data (HSCSD) on GSM/GERAN in A/Gb mode and Iu mode. HSCSD utilizes the multislot mechanism, i.e. using multiple traffic channels (/bearers) for the communication.
+
+Additionally, the present document specifies some HSCSD related requirements for multi system mobile stations operating in UTRAN Iu mode. In UTRAN Iu mode one bearer can provide all needed data rates, and the multislot mechanism is therefore not needed. However, for inter-system handover to GERAN, certain information has to be provided by the mobile station during the service negotiation. The UTRAN Iu mode aspects concerning HSCSD are described exclusively in clause 4.2.
+
+In analogy with ITU-T Recommendation I.130 [6] (refer to annex A) and with reference of ITU-T Recommendation Q.65 [7] VI.1 (Stage 2 of the method for characterization of services supported by an ISDN), the second stage of the HSCSD is defined as follows.
+
+Stage 2 identifies the functional capabilities and information flows needed to support the service as described in 3GPP TS 22.034 [9]. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
+
+The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] Void.
+- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
+- [3] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3".
+- [4] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification".
+- [5] 3GPP TS 24.022: "Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC)".
+- [6] ITU-T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
+- [7] ITU-T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities".
+- [8] ITU-T Recommendation I.460: "Multiplexing, rate adaptation and support of existing interfaces".
+
+- [9] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD); Stage 1".
+- [10] 3GPP TS 43.020: "Security related network functions".
+- [11] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) Interface".
+- [12] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface".
+- [13] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using Asynchronous bearer capabilities".
+- [14] 3GPP TS 27.003: "Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities".
+- [15] 3GPP TS 45.008: "Radio Subsystem Link Control".
+- [16] 3GPP TS 23.008: "Organisation of subscriber data".
+- [17] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
+- [18] 3GPP TS 43.051: "GSM/EDGE Radio Access Network; Overall description - Stage 2".
+- [19] 3GPP TS 25.413: "UTRAN Iu interface RANAP Signalling".
+- [20] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols".
+- [21] 3GPP TS 44.118, Release 11: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) Protocol, Iu Mode".
+- [22] 3GPP TS 29.415: "Core Network Nb Interface User Plane Protocols".
+- [23] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
+- [24] 3GPP TS 33.102: "3G Security; Security Architecture".
+
+# --- 3 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**A/Gb mode:** mode of operation of the MS when connected to the Core Network via GERAN and the A and/or Gb interfaces.
+
+**GERAN:** GSM/EDGE radio access network
+
+**HSCSD:** High Speed Circuit Switched Data
+
+**HSCSD configuration:** multislot configuration consisting of one or several full rate traffic channels for data transmission
+
+**HSCSD channel:** full rate traffic channel belonging to a HSCSD configuration
+
+**Iu mode:** mode of operation of the MS when connected to the Core Network via GERAN or UTRAN and the Iu interface. When preceded by the word GERAN or UTRAN, it means access over the Iu interface using the respective radio access network.
+
+**main channel:** only channel in a HSCSD configuration carrying an FACCH
+
+**symmetric configuration:** configuration consisting of bi-directional channels
+
+**asymmetric configuration:** configuration consisting of bi-directional channels and at least one uni-directional channel
+
+UTRAN: UMTS radio access network
+
+For further abbreviations see 3GPP TR 21.905 [1a].
+
+# 4 Main concepts
+
+The air interface user rate in the original GSM data transmission is limited to 9,6 kbps with the 12 kbps air interface rate. The HSCSD described in the present document Stage 2 description allows higher air interface user rates to be used for transparent and non-transparent data services.
+
+NOTE: In the present document the term "air interface user rate" corresponds to the transfer rate in radio interface for user data and "air interface rate" includes additional data related to transmission protocols.
+
+HSCSD is a feature enabling the co-allocation of multiple full rate traffic channels (TCH/F) into a HSCSD configuration. The aim of HSCSD is to provide a mixture of services with different air interface user rates by a single physical layer structure. Further improvements in data rates are achieved through enhancement of the radio interface (modulation and coding schemes), which allows higher bit rates per one GSM time slot. The available capacity of a HSCSD configuration is several times the capacity of a TCH/F, leading to a significant enhancement in the air interface data transfer rate.
+
+Figure 1 represents the network architecture to support HSCSD in A/Gb mode based on the concept of multiple independent channels in one HSCSD configuration. Figure 1a represents the network architecture to support HSCSD in GERAN Iu mode.
+
+NOTE: 3GPP TS 43.051 [18] does not specify the GERAN internal interface between BSC and BTS.
+
+In case when enhanced modulation is used the number of time slots in the radio interface may not correspond to the number of data streams in the network side, for example a 28,8 kbps service may be offered through one air interface time slot, but it requires two 14,4 (16 kbps) Abis channels. Another example is bit transparent 56 kbps to 64 kbps service where two air interface time slots of 32 kbps are multiplexed onto one 64 kbps data stream on the network side.
+
+![Figure 1: Network architecture for supporting HSCSD in A/Gb mode. The diagram shows a sequence of four main components: MS (Mobile Station), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The MS contains a TAF (Traffic Access Function). The MSC contains an IWF (Interworking Function). The interfaces are: Air I/F between MS and BTS, Abis I/F between BTS and BSC, and A I/F between BSC and MSC. Below the MS, an arrow points to the Air I/F with the text 'n full-rate or n time slots per TDMA'. Below the BSC, an arrow points to the A I/F with the text '1 circuit'.](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg)
+
+Figure 1: Network architecture for supporting HSCSD in A/Gb mode. The diagram shows a sequence of four main components: MS (Mobile Station), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The MS contains a TAF (Traffic Access Function). The MSC contains an IWF (Interworking Function). The interfaces are: Air I/F between MS and BTS, Abis I/F between BTS and BSC, and A I/F between BSC and MSC. Below the MS, an arrow points to the Air I/F with the text 'n full-rate or n time slots per TDMA'. Below the BSC, an arrow points to the A I/F with the text '1 circuit'.
+
+Figure 1: Network architecture for supporting HSCSD in A/Gb mode
+
+![Figure 1a: Network architecture for supporting HSCSD in GERAN Iu mode. The diagram shows a sequence of four main components: MS (Mobile Station), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The MS contains a TAF (Traffic Access Function). The MSC contains an IWF (Interworking Function). The interfaces are: Air I/F between MS and BTS, Abis I/F between BTS and BSC, and Iu I/F between BSC and MSC. Below the MS, an arrow points to the Air I/F with the text 'n full-rate or n time slots per TDMA'. Below the BSC, an arrow points to the Iu I/F with the text '1 circuit'.](4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg)
+
+Figure 1a: Network architecture for supporting HSCSD in GERAN Iu mode. The diagram shows a sequence of four main components: MS (Mobile Station), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The MS contains a TAF (Traffic Access Function). The MSC contains an IWF (Interworking Function). The interfaces are: Air I/F between MS and BTS, Abis I/F between BTS and BSC, and Iu I/F between BSC and MSC. Below the MS, an arrow points to the Air I/F with the text 'n full-rate or n time slots per TDMA'. Below the BSC, an arrow points to the Iu I/F with the text '1 circuit'.
+
+Figure 1a: Network architecture for supporting HSCSD in GERAN Iu mode
+
+A new functionality is introduced at the network and MS to provide the functions of combining and splitting the data into separate data streams which will then be transferred via n channels at the radio interface, where  $n = 1, 2, 3, \dots, 8$ . Once split, the data streams shall be carried by the n full rate traffic channels, called HSCSD channels, as if they were independent of each other, for the purpose of data relay and radio interface L1 error control, until to the point in the network where they are combined. However, logically the n full rate traffic channels at the radio interface belong to the same HSCSD configuration, and therefore they shall be controlled as one radio link by the network for the purpose of cellular operations, e.g. handover. This requires a new functionality in BSS.
+
+The different user data substreams carried on the radio channels (one substream being the data flow over a single TCH) shall be mapped over the A interface or GERAN Iu interface, and vice versa, following the rules defined in 3GPP TS 24.008 [3] and 3GPP TS 48.020 [12].
+
+In A/Gb mode, the use of resources on the A and E interfaces is restricted to one 64 kbps circuit by multiplexing the data streams into one A interface circuit (see ITU-T Recommendation I.460 [8]).
+
+In GERAN Iu mode, the user plane at the Iu interface shall comply to the Iu UP protocol (3GPP TS 25.415 [20]). For transparent calls the Iu user plane is operated in transparent mode, version 1, for non-transparent calls it is operated in support mode for predefined SDU sizes, version 2.
+
+After an inter-MSC SRNS relocation the user plane between the anchor MSC or MGW and the target MSC or MGW shall comply to the Nb UP protocol (3GPP TS 29.415 [22]), if the anchor MSC or MGW and the target MSC or MGW are connected via an ATM interface or IP interface. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream (for details see 3GPP TS 29.007 [23]).
+
+If both MSCs are connected via a TDM interface the use of resources on the E interface is restricted to one 64 kbps circuit (see 3GPP TS 29.007 [23]).
+
+## 4.1 HSCSD service aspects
+
+At call setup a user indicates a maximum number of TCH/F, acceptable channel codings (including extensions to acceptable channel codings for ECSO channel codings), possible other modem type, and fixed network user rate values. For non-transparent HSCSD connection, in addition, wanted air interface user rate is indicated and the network resource needs, if user wishes to make use of the user initiated modification of the maximum number of TCH/F and/or wanted air interface user rate (user initiated service level up- and downgrading described in subclauses 5.2.4 and 5.2.4a) during the call. In case the indicated acceptable channel coding(s) implies that enhanced modulation is possible, the user may indicate a preference for channel coding asymmetry, i.e. downlink biased channel coding asymmetry, uplink biased channel coding asymmetry or channel coding symmetry. Together these parameters describe the HSCSD characteristics and network uses them to allocate an appropriate HSCSD connection.
+
+For both transparent and non-transparent HSCSD connections the call can be established with any number of TCH/F from one up to the maximum number of TCH/F, i.e. the minimum channel requirement is always one TCH/F.
+
+If the wanted air interface user rate requirement cannot be met using a symmetric configuration, an asymmetric configuration can be chosen. The network shall in this case give priority to fulfilling the air interface user rate requirement in downlink direction.
+
+For non-transparent HSCSD connection the network can use dynamic allocation of resources, i.e. TCH/F, as long as the configuration is not in contradiction with the limiting values defined by the MS and the mobile equipment is capable of handling the allocated channel configuration. For transparent HSCSD connection the dynamic resource allocation is applicable, if the air interface user rate is kept constant. The change of channel configuration within the limits of minimum and maximum channel requirements is done with resource upgrading and resource downgrading procedures (described in subclauses 5.2.3 and 5.2.3a) during the call.
+
+The MS may request a service level up- or downgrading during the call, if so negotiated in the beginning of the call. In the user initiated modification procedure, the user can modify the channel coding asymmetry preference when enhanced modulation is indicated. This modification of channel requirements and/or wanted air interface user rate and/or channel coding asymmetry preference is applicable to non-transparent HSCSD connections only.
+
+## 4.2 HSCSD service aspects in UTRAN Iu mode
+
+The multislot mechanism is not needed in UTRAN Iu mode, as one bearer can provide all needed data rates. In UTRAN Iu mode, consequently the parameters required for setup of a multislot call are not needed in a call setup, and the MSC shall ignore the parameters.
+
+The parameters which are specific to multislot are (all contained in the Bearer Capability Information Element):
+
+- Maximum number of traffic channels.
+- Acceptable Channel coding(s).
+- UIMI, User initiated modification indication.
+- Acceptable Channel Codings extended.
+
+### 4.2.1 UTRAN Iu mode to GERAN Iu mode or A/Gb mode handover
+
+In case of handover from UTRAN Iu mode to GERAN Iu mode or A/Gb mode the multislot parameters are required in the middle of an ongoing call. A multi system mobile station supporting UTRAN Iu mode and at least one GERAN mode shall therefore always include the multislot parameters in the setup, also in UTRAN Iu mode.
+
+# 5 HSCSD architecture and transmission
+
+## 5.1 Air interface
+
+The HSCSD configuration is a multislot configuration using the TCH/F data channel mapping described in 3GPP TS 45.002 [2].
+
+Two types of HSCSD configurations exist, symmetric configuration and asymmetric configuration. For both types of configurations the channels may be allocated on either consecutive or non-consecutive time slots taking into account the restrictions defined by the classmark.
+
+An example of the HSCSD operation with two consecutive time slots is shown in figure 2.
+
+![Figure 2: Double slot operation in the air interface. The diagram shows three horizontal timelines: MS RX, MS TX, and Monitor. MS RX has time slots 0, 1, 2, 3, 4, 5, 6, 7. Slots 0 and 1 are shaded. MS TX has time slots 5, 6, 7, 0, 1, 2, 3, 4, 5, 6, 7. Slots 0 and 1 are shaded. Monitor has time slots 0, 1, 2, 3, 4, 5, 6, 7. Slot 5 is shaded. Lines connect the shaded slots in MS RX and MS TX to the shaded slot in Monitor, indicating double slot operation.](5a24ac755b962fd5f0183f13de0726de_img.jpg)
+
+Figure 2: Double slot operation in the air interface. The diagram shows three horizontal timelines: MS RX, MS TX, and Monitor. MS RX has time slots 0, 1, 2, 3, 4, 5, 6, 7. Slots 0 and 1 are shaded. MS TX has time slots 5, 6, 7, 0, 1, 2, 3, 4, 5, 6, 7. Slots 0 and 1 are shaded. Monitor has time slots 0, 1, 2, 3, 4, 5, 6, 7. Slot 5 is shaded. Lines connect the shaded slots in MS RX and MS TX to the shaded slot in Monitor, indicating double slot operation.
+
+Figure 2: Double slot operation in the air interface
+
+A symmetric HSCSD configuration consists of a bi-directional FACCH and co-allocated bi-directional TCH/F and SACCH channels. An asymmetric HSCSD configuration consists of a bi-direction FACCH and co-allocated uni-directional or bi-directional TCH/F and SACCH channels. A bi-directional channel is a channel on which the data is transferred in both uplink and downlink directions. On uni-directional channels for HSCSD the data is transferred in downlink direction, only.
+
+In both symmetric and asymmetric HSCSD configurations one bi-directional channel, the main channel, carries a FACCH used for all the signalling not carried on the SACCH(s).
+
+For HSCSD configuration all SACCHs are synchronized so that idle frames for each time slot coincide.
+
+The classification of mobile stations used for HSCSD shall be based on Multislot classes, described in detail in 3GPP TS 45.002 [2]. Further classification shall be based on the Mobile Station Classmark depending on the supported modulations.
+
+The same frequency hopping sequence and training sequence is used for all the channels in the HSCSD configuration.
+
+The same channel coding is used for all the channels in the HSCSD configuration, though in the enhanced modulation mode, for non-transparent services, it is possible to have one channel coding used in the downlink and another channel coding used in the uplink. Different channel codings for up- and downlink could be applied in three cases, see 3GPP TS 22.034 [9]:
+
+- a) If the mobile station only supports enhanced modulation in the downlink direction.
+- b) If the mobile station supports enhanced modulation in both directions, but the user indicates preference for uplink or downlink biased channel coding asymmetry.
+- c) If the mobile station supports enhanced modulation in both directions, and the user indicates preference for channel coding symmetry, but the link conditions justifies different channel coding in uplink or downlink.
+
+For Mobile Stations supporting 8-PSK modulation additional channel codings shall apply. The change between different TCH/F channel codings can be provided in A/Gb mode with the RR Channel Mode Modify or the Configuration Change procedure, and in GERAN Iu mode with the Radio Bearer Reconfiguration procedure. It shall be possible to change between channel codings of different modulation schemes.
+
+In symmetric HSCSD configuration individual signal level and quality reporting for each HSCSD channel is applied.
+
+For an asymmetric HSCSD configuration individual signal level and quality reporting is used for those channels, which have uplink SACCH associated with them. The quality measurements reported on the main channel are based on the worst quality measured among the main and the uni-directional downlink time slots used.
+
+In both symmetric and asymmetric HSCSD configuration the neighbouring cell measurement reports are copied on every uplink channel used. See 3GPP TS 45.008 [15] for more detail on signal level and quality reporting.
+
+In A/Gb mode, separate ciphering keys are used for each HSCSD channels. The ciphering keys used on different channels are derived from the Kc. See 3GPP TS 43.020 [10] for more details. In GERAN Iu mode, the same ciphering architecture is used as in UTRAN Iu mode. See 3GPP TS 43.051 [18] and 3GPP TS 33.102 [24] for more details.
+
+## 5.2 Functions and information flows
+
+The procedures discussed in this clause follow the procedures described in detail in 3GPP TS 48.008 [4], 3GPP TS 23.413 [19], 3GPP TS 23.415 [20], and 3GPP TS 24.008 [3]. Modifications are referred with text in brackets and conditional procedures with dashed line. Normal signalling or signalling presented earlier in the document is drawn with ovals.
+
+NOTE: 3GPP TS 43.051 [18] does not specify the GERAN internal interface between BSC and BTS. For the information flows in this document it is assumed that the protocols and procedures on this interface follow the conventions for the Abis interface, however, this is only an implementation option.
+
+### 5.2.1 Call establishment procedures
+
+#### 5.2.1.1 Mobile originated call establishment (A/Gb mode)
+
+Figure 3 depicts the procedures for a successful HSCSD call establishment in mobile originated case in A/Gb mode.
+
+The Multislot class is sent from MS to network using the early classmark sending.
+
+At the call setup the mobile station sends a set of parameters describing the HSCSD characteristics to the network. These parameters and their presence in the Setup message in transparent (T) and non-transparent (NT) calls are as follows:
+
+- |                                                        |         |
+|--------------------------------------------------------|---------|
+| - Other Modem Type, OMT                                | (T/NT); |
+| - Fixed Network User Rate, FNUR                        | (T/NT); |
+| - Acceptable Channel Codings, ACC (including ACC ext.) | (T/NT); |
+| - maximum number of traffic channels, Max TCH/F        | (T/NT); |
+| - User Initiated Modification Indication, UIMI         | (NT);   |
+
+- wanted Air Interface User Rate, AIUR (NT), and
+- channel coding ASYMmetry indication, ASYM (NT).
+
+In reply the network responds in Call Proceeding with the Other Modem Type, OMT, Fixed Network User Rate, FNUR, and User Initiated Modification Indication, UIMI (NT only), parameters it is prepared to give to the mobile station.
+
+![Sequence diagram for Mobile originated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS
+    participant BSC
+    participant MSC
+
+    Note over MS, MSC: Normal signalling
+    Note over BTS, BSC: Classmark change, CLM3  
+( MS Multislot Class, Modulation capability)
+    Note over MS, MSC: Normal signalling
+    Note over BTS, BSC: SetUp  
+( OMT, FNUR, ACC, Max TCH/F, UIMI(NT only), AIUR(NT only), ASYM(NT only) )
+    Note over MS, BSC: Call Proceeding  
+( OMT, FNUR, UIMI(NT only) )
+    Note over BSC, MSC: Assignment Request  
+( Max TCH/F allowed, Allowed radio interface data rates, Wanted total radio interface data rate(NT) / Requested air interface user rate (T), Configuration evolution indication, ASYM(NT only) )
+    Note over BSC: Resource allocation
+    Note over BTS, BSC: Physical context interrogation
+    Note over BTS, BSC: Channel activation  
+( Bi-directional / Uni-directional Bm Multislot configuration)
+    Note over BTS, BSC: Channel activation ack
+    Note over MS, BSC: n times [ ... ]
+    Note over MS, BSC: Assignment command  
+( Description of multislot configuration )
+    Note over MS, BSC: Signalling link establishment
+    Note over BTS, BSC: Assignment complete  
+( Channel mode, n TCH/F )
+    Note over MSC: Seize IW resources
+    Note over MS, MSC: Normal signalling
+  
+```
+
+n = number of time slots allocated
+
+Sequence diagram for Mobile originated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC.
+
+**Figure 3: Mobile originated call establishment (A/Gb mode)**
+
+The MSC requests the BSC to allocate the channel configuration using parameters derived from the HSCSD related parameters agreed in the setup phase. Based on these parameters and operator preferences the BSC then allocates a suitable number of channels and a suitable channel coding for the connection.
+
+The following rule for the channel allocation apply:
+
+- The BSS shall try to reach but not exceed, with one exception, the wanted AIUR. The exception is the case when the chosen configuration can reach the wanted AIUR with lower number of TCH/F, e.g. in case AIUR=14,4 kbit/s, max number of TCH/F=3, ACC=TCH/F4.8 and TCH/F9.6, the network shall choose 2 x 9,6 over 3 x 4,8 if the TCH/F9.6 is available in the cell.
+- A separate channel activation is applied for each of the HSCSD channels before the selected channel configuration with information of the channel coding is forwarded to the mobile station. When the preference for downlink or uplink biased channel coding asymmetry is indicated by the user, and an asymmetric channel coding
+
+connection is set up based on this indication, the BSC shall always assign a TCH/F14.4 channel on the unbiased link of the connection.
+
+- At assignment completion, the BSS informs the MSC of the chosen HSCSD configuration and the MSC may seize the IW resources accordingly.
+
+#### 5.2.1.1a Mobile originated call establishment (GERAN Iu mode)
+
+Figure 3a depicts the procedures for a successful HSCSD call establishment in mobile originated case in GERAN Iu mode.
+
+The MS GERAN Iu mode radio access capabilities, including the multislot capabilities of the MS, are sent from the MS to the network during the establishment of the RRC connection.
+
+The BSC includes the GERAN classmark in the RANAP Initial UE message to inform the MSC about the BSS capabilities of the serving cell:
+
+- Acceptable Channel Codings, ACC (including ACC ext.); and
+- maximum number of traffic channels, Max TCH/F.
+
+The parameters in the Setup message and their presence requirements for transparent (T) and non-transparent (NT) calls are the same as for A/Gb mode, however, for non-transparent calls in GERAN Iu mode the channel coding asymmetry indication will be ignored. When negotiating the parameters for a transparent call, the MSC shall take the GERAN classmark into account.
+
+![Sequence diagram for Mobile originated call establishment (GERAN Iu mode) showing interactions between MS, BTS, BSC, and MSC.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS
+    participant BSC
+    participant MSC
+
+    Note left of MS: 
+    MS->>BSC: RRC connection establishment with transfer of MS radio access capabilities
+    Note right of BSC: 
+    BSC->>MSC: Initial UE ( CM Service Request, GERAN Classmark )
+    Note left of BSC: 
+    BSC->>BTS: Normal signalling
+    Note right of BTS: 
+    BTS->>BSC: SetUp ( OMT, FNUR, ACC, Max TCH/F, UIMI(NT only), AIUR(NT only), ASYM(NT only) )
+    Note left of BSC: 
+    BSC->>BTS: Call Proceeding ( OMT, FNUR, UIMI(NT only) )
+    Note right of BSC: 
+    BSC->>MSC: RAB Assignment Request ( RAB subflow combinations (NT only), GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates )
+    Note right of BSC: 
+    BSC->>BSC: Resource allocation
+    Note right of BSC: 
+    BSC->>BTS: Setup of radio access bearer
+    Note right of BTS: 
+    BTS->>BSC: Physical context interrogation
+    Note right of BTS: 
+    BTS->>BSC: Channel activation
+    Note left of BTS: n times
+    Note right of BSC: 
+    BSC->>BTS: Setup of radio bearer
+    Note right of BSC: 
+    BSC->>MSC: RAB Assignment Response ( accepting all RAB subflow combinations (NT only) )
+    Note right of BSC: 
+    BSC->>BSC: Iu UP initialisation (NT only)
+    Note right of MSC: 
+    MSC->>BSC: Seize IW resources
+    Note left of BSC: 
+    BSC->>BTS: Normal signalling
+  
+```
+
+n = number of time slots allocated
+
+Sequence diagram for Mobile originated call establishment (GERAN Iu mode) showing interactions between MS, BTS, BSC, and MSC.
+
+**Figure 3a: Mobile originated call establishment (GERAN Iu mode)**
+
+The MSC requests the BSC to allocate a radio access bearer by sending a RANAP RAB Assignment Request message. The RAB parameters in this message are set according to the parameters negotiated between MS and MSC and the GERAN classmark of the serving cell. For non-transparent calls the RAB parameters contain the description of all RAB subflow combinations allowable for the maximum bit rate at the Iu interface, and thus for the maximum possible AIUR that can be allocated by the BSC for this call.
+
+Additionally, the MSC includes a GERAN BSC container, indicating the Max TCH/F allowed and the Allowed radio interface data rates. In this version, the MSC shall indicate only one radio interface data rate as allowed.
+
+Based on these parameters and operator preferences the BSC then allocates a suitable number of channels for the allowed channel coding.
+
+After the successful setup of the radio access bearer, for non-transparent calls the BSC initiates the Iu user plane protocol. In the Iu UP initialisation message the first RAB subflow combination proposed in the list of RAB subflow combinations indicates the RAB subflow combination and thus the AIUR to be used by the IW function when starting the communication phase (see 3GPP TS 25.415 [20]). The BSC shall use the same RAB subflow combination in uplink direction.
+
+#### 5.2.1.2 Mobile terminated call establishment (A/Gb mode)
+
+Figure 4 depicts the procedures for a successful HSCSD call establishment in mobile terminated case in A/Gb mode.
+
+At the call setup the network sends the Other Modem Type, OMT, Fixed Network User Rate, FNUR, and User Initiated Modification Indication, UIMI (NT only), parameters to the mobile station.
+
+In reply the mobile station responds to the network with the set of parameters describing the HSCSD characteristics. These parameters and their presence in the Call Confirmed message in transparent (T) and non-transparent (NT) calls are as follows:
+
+- wanted Other Modem Type, OMT (T/NT);
+- wanted Fixed Network User Rate, FNUR (T/NT);
+- Acceptable Channel Codings, ACC (including ACC ext.) (T/NT);
+- maximum number of traffic channels, Max TCH/F (T/NT);
+- User Initiated Modification Indication, UIMI (NT);
+- wanted Air Interface User Rate, AIUR (NT), and
+- channel coding ASYMmetry indication, ASYM (NT).
+
+![Sequence diagram for Mobile terminated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS
+    participant BSC
+    participant MSC
+
+    Note right of BSC: Normal signalling
+    MSC->>BSC: Classmark change, CLM3  
+( Multislot class, Modulation capability)
+    Note right of BSC: Normal signalling
+    MSC->>BSC: SetUp  
+( OMT, FNUR, UIMI(NT only) )
+    BSC->>BTS: Call Confirmed  
+( OMT, FNUR, ACC, Max TCH/F, UIMI(NT only) , AIUR(NT only), ASYM(NT only) )
+    Note right of BSC: Signalling as in mobile originated case
+  
+```
+
+Sequence diagram for Mobile terminated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC.
+
+**Figure 4: Mobile terminated call establishment (A/Gb mode)**
+
+The MSC requests the BSC to allocate the channel configuration using parameters derived from the HSCSD related parameters agreed in the setup phase. Based on these parameters and operator preferences the BSC then allocates a suitable number of channels and a suitable channel coding for the connection.
+
+The same channel allocation rules as in mobile originated case apply.
+
+The same channel activation rules as in mobile originated case apply.
+
+At assignment completion, the BSS informs the MSC of the chosen HSCSD configuration and the MSC may seize the IW resources accordingly.
+
+#### 5.2.1.2a Mobile terminated call establishment (GERAN Iu mode)
+
+Figure 4a depicts the procedures for a successful HSCSD call establishment in mobile terminated case in GERAN Iu mode.
+
+![Sequence diagram for Mobile terminated call establishment (GERAN Iu mode)](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant BTS
+    participant BSC
+    participant MSC
+
+    Note right of BSC: Normal signalling (paging)
+    Note right of BSC: RRC connection establishment with transfer of MS radio access capabilities
+    Note right of BSC: Initial Direct Transfer ( Paging Response )
+    Note right of MSC: Initial UE ( Paging Response, GERAN Classmark )
+    Note right of BSC: Normal signalling
+    Note right of BSC: SetUp ( OMT, FNUR, UIMI(NT only) )
+    Note right of BSC: Call Confirmed ( OMT, FNUR, ACC, Max TCH/F, UIMI(NT only) , AIUR(NT only), ASYM(NT only) )
+    Note right of BSC: Signalling like in mobile originated case
+```
+
+The diagram illustrates the sequence of messages for a mobile terminated call establishment in GERAN Iu mode. It involves four main entities: MS (Mobile Station), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The sequence starts with 'Normal signalling (paging)' from the MSC to the BSC. The BSC then performs 'RRC connection establishment with transfer of MS radio access capabilities' with the MS. Next, an 'Initial Direct Transfer (Paging Response)' is sent from the BSC to the MSC. The MSC responds with 'Initial UE (Paging Response, GERAN Classmark)'. This is followed by 'Normal signalling' from the MSC to the BSC. The BSC then sends a 'SetUp' message to the MS, containing parameters like OMT, FNUR, and UIMI(NT only). The MS responds with a 'Call Confirmed' message, which includes parameters such as OMT, FNUR, ACC, Max TCH/F, UIMI(NT only), AIUR(NT only), and ASYM(NT only). Finally, the diagram indicates that the subsequent 'Signalling like in mobile originated case' begins.
+
+Sequence diagram for Mobile terminated call establishment (GERAN Iu mode)
+
+**Figure 4a: Mobile terminated call establishment (GERAN Iu mode)**
+
+For the Setup message and the Call Confirmed message the same rules apply as in A/Gb mode.
+
+The signalling for the setup of the radio bearer and the radio access bearer, and the initialisation of the Iu user plane (NT only) is as in the mobile originated case.
+
+### 5.2.2 Handover procedures
+
+#### 5.2.2.1 Intra BSC handover (A/Gb mode)
+
+Figure 5 depicts the procedures for a successful HSCSD intra BSC handover in A/Gb mode.
+
+![Sequence diagram for Intra BSC handover (A/Gb mode) showing interactions between MS, BTS old, BTS new, BSC, and MSC.](41a438d7e4adc17c3a4005e7c9500091_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS_old as BTS old
+    participant BTS_new as BTS new
+    participant BSC
+    participant MSC
+
+    MS->>BTS_old: Measurement report
+    BTS_old->>BSC: Measurement result
+    Note right of BSC: HO decision
+    Note right of BSC: Resource allocation
+    
+    rect rgb(255, 255, 255)
+    Note over BTS_new, BSC: n times
+    BSC->>BTS_new: Channel activation  
+(Bi-directional / Uni-directional Bm Multislot configuration)
+    BTS_new->>BSC: Channel activation ack
+    end
+
+    BSC->>MS: Handover command  
+(Description of multislot configuration)
+    
+    Note over MS, BSC: Handover access and signalling link establishment
+    
+    MS->>BTS_new: Handover complete
+    BTS_new->>BSC: Handover complete
+    BSC->>MSC: Handover performed  
+(Channel mode, n TCH/F)
+    
+    rect rgb(255, 255, 255)
+    Note over BTS_old, BSC: m times RF channel release procedure
+    end
+
+    Note right of MSC: Adjust IW resources
+  
+```
+
+$n$  = number of time slots in the new cell  
+ $m$  = number of time slots in the old cell
+
+Sequence diagram for Intra BSC handover (A/Gb mode) showing interactions between MS, BTS old, BTS new, BSC, and MSC.
+
+**Figure 5: Intra BSC handover (A/Gb mode)**
+
+For a non-transparent call, the HSCSD configuration may be modified during an intra BSS handover within the maximum number of TCH/F and channel codings acceptable for the user and allowed by the network.
+
+The same allocation and activation rules as in call establishment apply.
+
+At handover completion, the BSC signals to the MSC the new HSCSD configuration and the MSC may adjust the IW resources accordingly.
+
+#### 5.2.2.1a Intra BSC handover (GERAN Iu mode)
+
+Figure 5a depicts the procedures for a successful HSCSD intra BSC handover in GERAN Iu mode.
+
+For a non-transparent call in GERAN Iu mode, the HSCSD configuration may be modified during an intra BSS handover within the maximum number of TCH/F acceptable for the user and allowed by the network. The outcome of the handover shall be reported to the MSC by means of an Iu UP rate control procedure (see 3GPP TS 25.415 [20]). The
+
+BSC shall set the maximum rate permitted downlink over the Iu interface according to the new HSCSD configuration, i.e. according to the AIUR to be used by the IW function when the communication is resumed after the handover. The BSC shall use the same RAB subflow combination in uplink direction.
+
+For a transparent call in GERAN Iu mode, the AIUR remains unchanged during the handover. Since the payload format at the Iu interface only depends on the AIUR, the IW resources do not need to be readjusted.
+
+![Sequence diagram for Intra BSC handover (GERAN Iu mode) showing interactions between MS, BTS old, BTS new, BSC, and MSC.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS old
+    participant BTS new
+    participant BSC
+    participant MSC
+
+    Note over MS, BSC: Normal signalling (measurement reporting)
+    Note right of BSC: HO decision
+    Note right of BSC: Resource allocation
+    BSC->>BTS new: Channel activation (n times)
+    BSC->>MS: Handover command (Description of multislot configuration)
+    Note over MS, BSC: Handover access and signalling link establishment
+    MS->>BTS new: Handover complete
+    BTS new->>BSC: Handover complete
+    BSC->>MSC: Iu UP rate control (NT only)
+    Note right of MSC: Adjust IW resources
+    Note over BTS old, BSC: m times RF channel release procedure
+  
+```
+
+The sequence diagram illustrates the Intra BSC handover process in GERAN Iu mode. It involves five main participants: MS (Mobile Station), BTS old (Old Base Transceiver Station), BTS new (New Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The process begins with 'Normal signalling (measurement reporting)' involving MS, BTS old, BTS new, and BSC. The BSC performs an 'HO decision' and 'Resource allocation'. It then sends 'Channel activation' (n times) to the BTS new. A 'Handover command' (containing a 'Description of multislot configuration') is sent from the BSC to the MS. This is followed by 'Handover access and signalling link establishment' across MS, BTS old, BTS new, and BSC. The MS sends a 'Handover complete' message to the BTS new, which in turn sends a 'Handover complete' message to the BSC. The BSC then initiates 'Iu UP rate control (NT only)' towards the MSC, which triggers 'Adjust IW resources'. Finally, an 'RF channel release procedure' (m times) occurs between the BTS old and the BSC.
+
+n = number of time slots in the new cell  
+m = number of time slots in the old cell
+
+Sequence diagram for Intra BSC handover (GERAN Iu mode) showing interactions between MS, BTS old, BTS new, BSC, and MSC.
+
+**Figure 5a: Intra BSC handover (GERAN Iu mode)**
+
+#### 5.2.2.2 Inter BSC, intra-MSC handover (A/Gb mode)
+
+Figure 6 depicts the procedures for a successful HSCSD inter BSC handover in A/Gb mode.
+
+![Sequence diagram for Inter BSC, intra-MSC handover (A/Gb mode).](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS old
+    participant BSC old
+    participant MSC
+    participant BSC new
+    participant BTS new
+
+    Note left of MS: Measurement report
+    MS->>BTS old: Measurement report
+    BTS old->>BSC old: Measurement result
+    Note right of BSC old: HO decision
+    BSC old->>MSC: Handover required
+    MSC->>BSC new: Handover request  
+
+    Note right of BSC new: ( Max TCH/F allowed, Allowed radio interface data rates, Wanted total radio interface data rate(NT) / Requested air interface user rate (T), Configuration evolution indication )
+    Note right of BSC new: Resource allocation
+    BSC new->>MSC: Channel activation  
+
+    Note right of BSC new: ( Bi-directional / Uni-directional Bm Multislot configuration )
+    Note right of BSC new: n times
+    MSC->>BSC new: Channel activation ack  
+
+    Note right of BSC new: ( Channel mode, n TCH/F )
+    MSC->>BSC old: Handover command  
+
+    Note right of BSC old: ( Description of multislot configuration )
+    Note right of BSC old: Handover access and signalling link establishment
+    BSC new->>MSC: Handover complete
+    Note right of MSC: Adjust IW resources
+    MSC->>BSC old: Clear command
+    Note right of BTS old: m times RF channel release procedure
+    BSC old->>MSC: Clear complete
+  
+```
+
+*n* = number of time slots in the new cell  
+*m* = number of time slots in the old cell
+
+Sequence diagram for Inter BSC, intra-MSC handover (A/Gb mode).
+
+**Figure 6: Inter BSC intra MSC handover (A/Gb mode)**
+
+In inter BSS handover the MSC requests the new BSS to allocate a channel configuration using parameters derived from the HSCSD related parameters agreed earlier during the call. Based on these parameters and operator preferences the BSC then allocates a suitable number of TCH/F and a suitable channel coding for the connection.
+
+For a non-transparent call, the HSCSD configuration may be modified during an intra BSS handover within the maximum number of TCH/F and channel codings acceptable for the user and allowed by the network.
+
+The same channel allocation and activation rules as in call establishment apply.
+
+The BSC informs the MSC of the chosen HSCSD configuration and at handover completion the MSC may adjust the IW resources accordingly.
+
+##### 5.2.2.2a Inter BSC, intra-MSC handover (GERAN Iu mode)
+
+Figure 6a depicts the procedures for a successful HSCSD inter BSC handover in GERAN Iu mode.
+
+![Sequence diagram for Inter BSC, intra-MSC handover (GERAN Iu mode).](898fb89a50d9ec1dfb4e425c816976a7_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS old
+    participant BSC old
+    participant MSC
+    participant BSC new
+    participant BTS new
+
+    Note over MS, BSC old: Normal signalling (measurement reporting)
+    Note over BSC old: HO decision
+    BSC old->>MSC: Relocation required (GERAN Classmark)
+    MSC->>BSC new: Relocation request (RAB subflow combinations (NT only), GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates)
+    Note over BSC new: Resource allocation
+    MSC->>BSC new: Setup of radio access bearer
+    BSC new->>BTS new: n times Channel activation
+    BSC new->>MSC: Relocation request ack (Iu UP initialisation (NT only))
+    MSC->>BSC old: Relocation command
+    BSC old->>MS: Handover command (Description of multislot configuration)
+    Note over MS, BTS new: Handover access and signalling link establishment
+    BTS new->>BSC new: Handover complete
+    BSC new->>MSC: Relocation complete
+    Note over MSC: Adjust IW resources
+    MSC->>BSC old: Iu Release command
+    Note over BTS old, BSC old: m times RF channel release procedure
+    BSC old->>MSC: Iu Release complete
+
+```
+
+*n* = number of time slots in the new cell  
+*m* = number of time slots in the old cell
+
+Sequence diagram for Inter BSC, intra-MSC handover (GERAN Iu mode).
+
+**Figure 6a: Inter BSC intra MSC handover (GERAN Iu mode)**
+
+The serving BSC includes the GERAN classmark of the target cell in the RANAP Relocation Required message. The MSC takes this information into account when it selects the RAB parameters for the RANAP Relocation Request message.
+
+For a non-transparent call in GERAN Iu mode, the HSCSD configuration may be modified during an inter BSC handover within the maximum number of TCH/F acceptable for the user and allowed by the network. After the successful setup of the radio access bearer towards the new BSC, for non-transparent calls the new BSC initiates the Iu user plane protocol. In the Iu UP initialisation message the first RAB subflow combination proposed in the list of RAB subflow combinations indicates the RAB subflow combination and thus the AIUR to be used by the IW function when the communication is resumed after the handover (see 3GPP TS 25.415 [20]). The new BSC shall use the same RAB subflow combination in uplink direction.
+
+For a transparent call in GERAN Iu mode, the AIUR remains unchanged during the handover. Since the payload format at the Iu interface only depends on the AIUR, the IW resources do not need to be readjusted.
+
+#### 5.2.2.3 Inter MSC handover
+
+In inter MSC handover the requested channel configuration is forwarded to a BSS within the new MSC using MAP protocol between MSCs. Procedures similar to those in inter BSS handover case can be applied in order to establish the HSCSD connection in a new cell.
+
+In GERAN Iu mode, the GERAN classmark of the target cell is forwarded to the anchor MSC and to the target MSC using MAP protocol between MSCs.
+
+### 5.2.3 Resource upgrading, downgrading and configuration change (A/Gb mode)
+
+Resource upgrading means allocating more channels to the HSCSD configuration. Similarly, in resource downgrading channels are released.
+
+Both of these procedures are initiated by the network and they are used in non-transparent calls to alter the channel resources between one TCH/F and the maximum number of TCH/F allowed. For transparent connection the alteration of resources is also applicable required that the AIUR for the connection remains constant.
+
+Figure 7 depicts the procedures for a successful resource upgrading and downgrading for an ongoing HSCSD call in A/Gb mode, in case the position of the main TCH/F remains unchanged.
+
+A separate channel activation for the new HSCSD channels is carried out and the earlier activated HSCSD channels may be modified, before RR Configuration change procedure is used for forwarding the new channel configuration to the mobile station. Similarly, the Configuration change procedure can be used in both transparent and non-transparent calls for reordering the channels in a call without changing the number of TCH/Fs allocated.
+
+At resource modification completion, the BSC signals to the MSC the new HSCSD configuration and the MSC may adjusts the IW resources accordingly.
+
+![Sequence diagram for Figure 7: Resource upgrading and downgrading in A/Gb mode, the position of the main channel unchanged. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs a 'Resource change decision' and 'Resource allocation'. It then sends 'Channel activation / Mode modify' messages to the BTS, which are acknowledged by 'Channel activation ack / Mode modify ack'. This exchange happens (A + M) times, with the message content being '( Bi-directional / Uni-directional Bm Multislot configuration)'. Next, the BSC sends a 'Configuration change command' to the MS, described as '( Description of multislot configuration )', which is acknowledged by 'Configuration change ack'. Simultaneously, the BSC signals 'Handover Performed' to the MSC, with details '( Channel mode, n TCH/F )'. Finally, the BSC sends 'RF channel release' messages to the BTS, acknowledged by 'RF channel release ack'. This exchange happens R times. Upon completion, the MSC 'Adjust IW resources'. A legend defines: A = number of time slots added to the connection; R = number of time slots released from the connection; M = number of time slots modified; n = number of time slots after upgrading/downgrading.](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+A = number of time slots added to the connection  
+R = number of time slots released from the connection  
+M = number of time slots modified  
+n = number of time slots after upgrading/downgrading
+
+Sequence diagram for Figure 7: Resource upgrading and downgrading in A/Gb mode, the position of the main channel unchanged. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs a 'Resource change decision' and 'Resource allocation'. It then sends 'Channel activation / Mode modify' messages to the BTS, which are acknowledged by 'Channel activation ack / Mode modify ack'. This exchange happens (A + M) times, with the message content being '( Bi-directional / Uni-directional Bm Multislot configuration)'. Next, the BSC sends a 'Configuration change command' to the MS, described as '( Description of multislot configuration )', which is acknowledged by 'Configuration change ack'. Simultaneously, the BSC signals 'Handover Performed' to the MSC, with details '( Channel mode, n TCH/F )'. Finally, the BSC sends 'RF channel release' messages to the BTS, acknowledged by 'RF channel release ack'. This exchange happens R times. Upon completion, the MSC 'Adjust IW resources'. A legend defines: A = number of time slots added to the connection; R = number of time slots released from the connection; M = number of time slots modified; n = number of time slots after upgrading/downgrading.
+
+**Figure 7: Resource upgrading and downgrading in A/Gb mode, the position of the main channel unchanged**
+
+Figure 8 depicts the procedures for a successful resource upgrading and downgrading for an ongoing HSCSD call in A/Gb mode in case the position of the main channel is changed.
+
+A separate channel activation for the new HSCSD channels, is carried out and the earlier activated HSCSD channels may be modified or, in case of the new main channel, reactivated, before RR Assignment procedure is used for forwarding the new channel configuration to the mobile station. Similarly, the Assignment procedure can be used in both transparent and non-transparent calls for reordering the channels in a call without changing the number of TCH/Fs allocated.
+
+At resource modification completion, the BSC signals to the MSC the new HSCSD configuration and the MSC may adjust the IW resources accordingly.
+
+![Sequence diagram for Figure 8: Resource upgrading and downgrading in A/Gb mode, the position of the main channel changed. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs a 'Resource change decision' and 'Resource allocation'. It then sends 'Channel (re-)activation / Mode modify' messages to the BTS, which are acknowledged. The BSC sends an 'Assignment command' to the MS. A 'Signalling link establishment' occurs between the MS and BSC. The BSC sends an 'Assignment complete' message to the MSC, which responds with 'Handover Performd ( Channel mode, n TCH/F )'. The BSC then sends 'Channel re-activation' messages to the BTS, which are acknowledged. Finally, the BSC sends 'RF channel release' messages to the BTS, which are acknowledged. A note indicates that the old signalling link is deactivated by modifying the old main channel. Another note indicates that the MSC should 'Adjust IW resources'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS
+    participant BSC
+    participant MSC
+
+    Note right of BSC: Resource change decision
+    Note right of BSC: Resource allocation
+
+    BSC->>BTS: Channel (re-)activation / Mode modify  
+(Bi-directional / Uni-directional Bm Multislot configuration)
+    Note left of BTS: ( A + M - 1 ) times
+    BTS->>BSC: Channel (re-)activation ack / Mode modify ack
+
+    BSC->>MS: Assignment command  
+( Description of multislot configuration )
+    Note over MS,BSC: Signalling link establishment
+
+    BSC->>MSC: Assignment complete
+    MSC-->>BSC: Handover Performd  
+( Channel mode, n TCH/F )
+
+    Note right of MSC: Adjust IW resources
+
+    BSC->>BTS: Channel re-activation  
+( Bi-directional / Uni-directional Bm Multislot configuration)
+    Note right of BSC: Note !
+    BTS->>BSC: Channel re-activation ack
+
+    Note left of BTS: R times
+    BSC->>BTS: RF channel release
+    BTS->>BSC: RF channel release ack
+  
+```
+
+Sequence diagram for Figure 8: Resource upgrading and downgrading in A/Gb mode, the position of the main channel changed. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs a 'Resource change decision' and 'Resource allocation'. It then sends 'Channel (re-)activation / Mode modify' messages to the BTS, which are acknowledged. The BSC sends an 'Assignment command' to the MS. A 'Signalling link establishment' occurs between the MS and BSC. The BSC sends an 'Assignment complete' message to the MSC, which responds with 'Handover Performd ( Channel mode, n TCH/F )'. The BSC then sends 'Channel re-activation' messages to the BTS, which are acknowledged. Finally, the BSC sends 'RF channel release' messages to the BTS, which are acknowledged. A note indicates that the old signalling link is deactivated by modifying the old main channel. Another note indicates that the MSC should 'Adjust IW resources'.
+
+NOTE: Deactivates the old signalling link by modifying the old main channel. The old main can not be modified before a new main has been established. If the time slot for the old main is not used in the new HSCSD configuration, RF channel release is used instead.
+
+A = number of time slots added to the HSCSD connection
+
+R = number of time slots released from the HSCSD connection
+
+M = number of time slots modified or re-activated
+
+n = number of time slots after upgrading/downgrading
+
+**Figure 8: Resource upgrading and downgrading in A/Gb mode, the position of the main channel changed**
+
+#### 5.2.3a Resource upgrading, downgrading and configuration change (GERAN Iu mode)
+
+In GERAN Iu mode a Radio bearer reconfiguration procedure is used for forwarding the new channel configuration to the mobile station, regardless whether the position of the main channel is changed or not.
+
+Figure 8a depicts the procedures for a successful resource upgrading and downgrading for an ongoing HSCSD call in GERAN Iu mode, in case the position of the main TCH/F remains unchanged.
+
+![Sequence diagram for Figure 8a: Resource upgrading and downgrading in GERAN Iu mode. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs a 'Resource change decision' and 'Resource allocation'. The BTS sends '(A + M) times' 'Channel (re-)activation / Mode modify' to the MS, followed by a 'Radio bearer reconfiguration'. The BSC sends 'Iu UP rate control (NT only)' to the MSC. The BTS sends 'R times' 'RF channel release' to the MS. Finally, the MSC sends 'Adjust IW resources' to the BSC.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+A = number of time slots added to the HSCSD connection  
+R = number of time slots released from the HSCSD connection  
+M = number of time slots modified or re-activated  
+n = number of time slots after upgrading/downgrading
+
+Sequence diagram for Figure 8a: Resource upgrading and downgrading in GERAN Iu mode. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs a 'Resource change decision' and 'Resource allocation'. The BTS sends '(A + M) times' 'Channel (re-)activation / Mode modify' to the MS, followed by a 'Radio bearer reconfiguration'. The BSC sends 'Iu UP rate control (NT only)' to the MSC. The BTS sends 'R times' 'RF channel release' to the MS. Finally, the MSC sends 'Adjust IW resources' to the BSC.
+
+**Figure 8a: Resource upgrading and downgrading in GERAN Iu mode, the position of the main channel unchanged**
+
+The outcome of the procedure shall be reported to the MSC by means of an Iu UP rate control procedure (see 3GPP TS 25.415 [20]). The BSC shall set the maximum rate permitted downlink over the Iu interface according to the new HSCSD configuration, i.e. according to the AIUR to be used by the IW function when the communication is resumed after the handover. The BSC shall use the same RAB subflow combination in uplink direction.
+
+For a transparent call in GERAN Iu mode, the resource upgrading or downgrading is not applicable since the AIUR remains unchanged during the call, and the allowed radio interface data rate is set by the MSC.
+
+### 5.2.4 User initiated service level up- and downgrading (A/Gb mode)
+
+Figure 9 depicts the procedures for a successful user initiated service level up- and downgrading for on-going HSCSD call in A/Gb mode.
+
+During a HSCSD call the user may request, if so indicated in the call setup, the network to change the current maximum number of traffic channels and air interface user rate parameters and/or channel coding asymmetry preference. This is done by using the CC User initiated service level up- and downgrading procedure.
+
+If network allows the modification, the resulting new parameters are forwarded to BSC and the radio interface resources may be adjusted accordingly. The resource upgrading or downgrading is done separately from the change in HSCSD parameters. However, if a contradiction between the new parameters and the used air interface resources exists, the resource downgrading may be needed before the network acknowledges the new parameters.
+
+The user initiated service level up- and downgrading is applicable in non-transparent mode connections, only.
+
+![Sequence diagram for Figure 9: User initiated service level up- and downgrading in A/Gb mode. The diagram shows four lifelines: MS, BTS, BSC, and MSC. The MS sends a 'Modify' message to the MSC with parameters: ( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) ). The MSC sends an 'Assignment Request' to the BSC with parameters: ( Max TCH/F allowed, Allowed radio interface data rates, Wanted total radio interface data rate, ASYM(NT) ). The BSC performs a 'Possible resource up- or downgrading procedure' with the BTS. The BSC then sends an 'Assignment complete' message to the MSC with parameters: ( Channel mode, n TCH/F ). Finally, the MSC sends a 'Modify complete' message back to the MS.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS
+    participant BSC
+    participant MSC
+    Note right of MSC: n = number of time slots allocated
+    MS->>MSC: Modify  
+( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) )
+    MSC->>BSC: Assignment Request  
+( Max TCH/F allowed, Allowed radio interface data rates, Wanted total radio interface data rate, ASYM(NT) )
+    BSC->>BTS: Possible resource up- or downgrading procedure
+    BSC->>MSC: Assignment complete  
+( Channel mode, n TCH/F )
+    MSC->>MS: Modify complete
+  
+```
+
+Sequence diagram for Figure 9: User initiated service level up- and downgrading in A/Gb mode. The diagram shows four lifelines: MS, BTS, BSC, and MSC. The MS sends a 'Modify' message to the MSC with parameters: ( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) ). The MSC sends an 'Assignment Request' to the BSC with parameters: ( Max TCH/F allowed, Allowed radio interface data rates, Wanted total radio interface data rate, ASYM(NT) ). The BSC performs a 'Possible resource up- or downgrading procedure' with the BTS. The BSC then sends an 'Assignment complete' message to the MSC with parameters: ( Channel mode, n TCH/F ). Finally, the MSC sends a 'Modify complete' message back to the MS.
+
+n = number of time slots allocated
+
+Figure 9: User initiated service level up- and downgrading in A/Gb mode
+
+#### 5.2.4a User initiated service level up- and downgrading (GERAN Iu mode)
+
+Figure 9a depicts the procedures for a successful user initiated service level up- and downgrading for on-going HSCSD call in GERAN Iu mode.
+
+The user initiated service level up- and downgrading is applicable in non-transparent mode connections, only.
+
+![Sequence diagram for Figure 9a: User initiated service level up- and downgrading in GERAN Iu mode. The diagram shows four lifelines: MS, BTS, BSC, and MSC. The MS sends a 'Modify' message to the MSC with parameters: ( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) ). The MSC sends a 'RAB Assignment Request' to the BSC with parameters: ( RAB subflow combinations, GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates ). The BSC performs a 'Modification of radio access bearer' and a 'Possible resource up- or downgrading procedure' with the BTS. The BSC then sends a 'RAB Assignment Response' to the MSC with parameters: ( accepting all RAB subflow combinations ). The BSC also performs 'Iu UP initialisation'. Finally, the MSC sends a 'Modify complete' message back to the MS.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BTS
+    participant BSC
+    participant MSC
+    Note right of MSC: n = number of time slots allocated
+    MS->>MSC: Modify  
+( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) )
+    MSC->>BSC: RAB Assignment Request  
+( RAB subflow combinations, GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates )
+    BSC->>BSC: Modification of radio access bearer
+    BSC->>BTS: Possible resource up- or downgrading procedure
+    BSC->>MSC: RAB Assignment Response  
+( accepting all RAB subflow combinations )
+    BSC->>BSC: Iu UP initialisation
+    MSC->>MS: Modify complete
+  
+```
+
+Sequence diagram for Figure 9a: User initiated service level up- and downgrading in GERAN Iu mode. The diagram shows four lifelines: MS, BTS, BSC, and MSC. The MS sends a 'Modify' message to the MSC with parameters: ( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) ). The MSC sends a 'RAB Assignment Request' to the BSC with parameters: ( RAB subflow combinations, GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates ). The BSC performs a 'Modification of radio access bearer' and a 'Possible resource up- or downgrading procedure' with the BTS. The BSC then sends a 'RAB Assignment Response' to the MSC with parameters: ( accepting all RAB subflow combinations ). The BSC also performs 'Iu UP initialisation'. Finally, the MSC sends a 'Modify complete' message back to the MS.
+
+n = number of time slots allocated
+
+Figure 9a: User initiated service level up- and downgrading in GERAN Iu mode
+
+### 5.2.5 Link adaptation for ECSD
+
+Link adaptation for ECSD particularly in high data rate call becomes essential in order to provide good enough service over large coverage areas. In A/Gb mode, signalling for link adaptation between channel coding schemes in 8-PSK modulation and between GMSK and 8-PSK coding schemes is done using existing signalling mechanisms, i.e. RR Channel Mode Modify procedure, intracell handover, etc. In performing link adaption between 8-PSK modulated channels, the normal Channel Mode (or the assignment or the intra-cell HO procedure) should be used and in case of link adaptation between 8-PSK modulated channels and GMSK modulated channels the assignment procedure or the intra-cell handover should be used.
+
+In GERAN Iu mode, the Radio bearer reconfiguration procedure is used for link adaptation.
+
+### 5.2.6 Start of ciphering
+
+In A/Gb mode, in order to start ciphering, the RR Encryption procedure is controlled by the main signalling link, only. The encryption information for secondary HSCSD channel is forwarded to the corresponding TCH/F in initial channel activation or later in the channel reactivation or Mode modify message.
+
+The change of ciphering modes for separate channels within the HSCSD connection might not be perfectly synchronized.
+
+In GERAN Iu mode, the Security mode control procedure is used to start ciphering (see 3GPP TS 44.118 [21]).
+
+## 5.3 Transparent data transmission
+
+### 5.3.1 Numbering of data substreams
+
+In transparent data transmission the V.110 data frames on the HSCSD channels carry data substream numbers to retain the order of transmission over GSM, between the split/combine functions. Between these functions a channel internal multiframing is also used in order to increase the tolerance against inter channel transmission delays. In A/Gb mode, depending on the location of the access point to external networks the split/combine functionality is located in the BSS or in the IWF on the network side, and at the mobile station. In GERAN Iu mode, the split/combine functionality on the network side is always located in the BSS.
+
+A detailed description of the numbering scheme is given in 3GPP TS 44.021 [11].
+
+### 5.3.2 Padding
+
+HSCSD also supports user rates which are not multiples of rates provided by one TCH/F.
+
+If the selected user rate requires n TCH/F channels but is less than the total rate that can be achieved with these n TCH/F then in the first n-1 channels the data frames carry user data on all D bits. In the n th channel the unneeded D bits of the V.110 frames are padded with fill bits.
+
+## 5.4 Non-Transparent data transmission
+
+### 5.4.1 HSCSD RLP
+
+Non-transparent mode of HSCSD is realized by modifying the RLP and L2R functions to support multiple parallel TCH/Fs instead of only one TCH/F (figure 9a). In addition the RLP frame numbering is increased to accommodate the enlarged data transmission rate.
+
+The detailed specification of the RLP is given in 3GPP TS 24.022 [5], and L2R is defined in 3GPP TS 27.002 [13] and 3GPP TS 27.003 [14].
+
+![Figure 9a: The HSCSD concept in non-transparent mode. The diagram shows two main entities, MS (Mobile Station) and IWF (Interworking Function), connected by multiple L1 entities. The MS contains an L2R block connected to an HSCSD RLP block, which is then connected to multiple L1 entities. The IWF contains an HSCSD RLP block connected to an L2R block, which is also connected to multiple L1 entities. The L1 entities are connected between the MS and the IWF.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+Figure 9a: The HSCSD concept in non-transparent mode. The diagram shows two main entities, MS (Mobile Station) and IWF (Interworking Function), connected by multiple L1 entities. The MS contains an L2R block connected to an HSCSD RLP block, which is then connected to multiple L1 entities. The IWF contains an HSCSD RLP block connected to an L2R block, which is also connected to multiple L1 entities. The L1 entities are connected between the MS and the IWF.
+
+Figure 9a: The HSCSD concept in non-transparent mode
+
+## 5.5 Interworking
+
+Interworking of HSCSD will be arranged to all the services to which interworking is provided in the existing GSM-system; these services are PSTN, ISDN, CSPDN and PSPDN.
+
+## 5.6 Subscription aspects and storage of subscriber data
+
+The HSCSD uses general bearer services defined in 22 series specifications. No HSCSD related subscriber data is stored in HLR or VLR with the exception of the bearer capability allocation (see 3GPP TS 23.008 [16]).
+
+# 6 Charging
+
+## 6.1 General principles
+
+The A party is liable for the usage of all TCH/F in her PLMN. The B party may have to pay for one or more TCH/F in her PLMN. In case the originating or terminating subscriber is in the PSTN there is no additional charge for them.
+
+## 6.2 Call forwardings
+
+The A party is liable for the leg A-B. The B party who forwards the call to the forwarded-to subscriber (C party) is liable for the primary (basic) channel on the leg B-C. Forwarded-to (C party) is liable for the usage of one or more TCH/F in her PLMN.
+
+## 6.3 AoC and toll ticketing
+
+MSC will send the modified e-parameters to the MS, both in MO and in MT calls, every time the charging rate will change. This can happen when:
+
+- the coding on the air interface channel is changed;
+- the number of TCH/F allocated is increased or decreased;
+
+during an existing HSCSD data call and when AoC supplementary service is activated.
+
+Appropriate information concerning these changes have to also be included in the charging record (toll ticket).

marked/Rel-18/23_series/23035/raw.md

@@ -0,0 +1,295 @@
+
+
+# 3GPP TS 23.035 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Immediate Service Termination (IST); Stage 2 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.  
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+---
+
+GSM, UMTS, IST, Security, stage 2
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                        |           |
+|--------------------------------------------------------|-----------|
+| Foreword .....                                         | 4         |
+| 1 Scope.....                                           | 5         |
+| 2 References.....                                      | 5         |
+| 3 Definitions and abbreviations .....                  | 5         |
+| 3.1 Definitions.....                                   | 5         |
+| 3.2 Abbreviations .....                                | 5         |
+| 4 Information flows.....                               | 6         |
+| 4.1 CAMEL implementation.....                          | 6         |
+| 4.2 Non-CAMEL implementation.....                      | 6         |
+| 5 Functional behaviour - CAMEL implementation .....    | 7         |
+| 5.1 Subscriber settings.....                           | 7         |
+| 5.2 DP Settings.....                                   | 7         |
+| 5.3 Call termination.....                              | 7         |
+| 6 Functional behaviour - Non-CAMEL implementation..... | 7         |
+| 6.1 Subscriber Settings .....                          | 8         |
+| 6.2 Periodic reporting mechanism.....                  | 8         |
+| 6.2.1 IST Alert timer Settings.....                    | 8         |
+| 6.2.2 Call termination .....                           | 9         |
+| 6.3 IST standalone mechanism.....                      | 9         |
+| 6.4 Exception procedure.....                           | 9         |
+| 7 Control of IST .....                                 | 10        |
+| <b>Annex A (Informative): Change History.....</b>      | <b>11</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+This Technical Specification specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
+
+Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP message.
+
+# --- 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: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.032: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Immediate Service Termination (IST), Service description - Stage 1".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Subscriber activities:** subscriber activities that must be terminated. These can be call related events (e.g. call set-up, call termination) or the invocation of call related and call independent supplementary services (e.g. Call Hold, Call Waiting, Call Transfer, Call Forwarding, Unstructured Supplementary Service Data (USSD)).
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following abbreviations apply:
+
+|       |                                            |
+|-------|--------------------------------------------|
+| IST   | Immediate Service Termination              |
+| FDS   | Fraud Detection System                     |
+| FIGS  | Fraud Information Gathering System         |
+| MO    | Mobile Originated                          |
+| MT    | Mobile Terminated                          |
+| O-CSI | Originating CAMEL Subscription Information |
+| T-CSI | Terminating CAMEL Subscription Information |
+
+# 4 Information flows
+
+## 4.1 CAMEL implementation
+
+For the Customised Applications for Mobile network Enhanced Logic (CAMEL) implementation of Immediate Service Termination (IST) for a particular subscriber, an "IST" command (in reality, the CAMEL message "ReleaseCall") must be sent by the gsmSCF of the home PLMN to the gsmSSF controlling the call, for all the calls of the subscriber.
+
+Prior to the sending of the IST command, the Mobile Application Part (MAP) command "Cancel Location" should be sent to the VLR at which the subscriber is registered. This will ensure that the subscriber cannot re-commence service at that VLR after the IST command has been executed. See Annex A of TS 22.032 [2].
+
+The compilation of the list of MSCs to which the IST command should be sent is outside the scope of this specification. However, if a PLMN operator wishes to implement IST using CAMEL, the list of MSCs to which the IST command should be sent for a subscriber is the list of MSCs with which the CAMEL server has a relationship for that subscriber. If this data is not available directly from the CAMEL server, it may be obtained using Fraud Information Gathering System (FIGS) or an Fraud Detection System (FDS) (if the HPLMN is using CAMEL for IST then it is likely that it will also be monitoring the subscriber's activities using FIGS level 2 or 3, which use CAMEL).
+
+## 4.2 Non-CAMEL implementation
+
+For each non-CAMEL-subscriber under IST control, the HLR shall request the MSCs during location update and routing information retrieval to report for each remaining activity periodically at the frequency defined by the IST Alert timer value about the remaining activity for this subscriber in the node by sending an IST Alert Message to the HLR, as long as the activity is ongoing. The IST Alert timer value is set by HPLMN and communicated to VPLMN and IPLMN on subscriber basis.
+
+The HLR shall be able to request termination of ongoing call activities for a subscriber by returning a call termination indicator to the MSC in response to the IST Alert message initiated by this MSC. When this call termination indicator is received, the MSC shall terminate the call activities for that subscriber (the MSC shall terminate the call activity that triggered the IST Alert dialogue, and optionally other call activities in that MSC if the MSC is able to link the calls related to the subscriber).
+
+As an implementation option the HLR may for each non-CAMEL-subscriber under IST control maintain a list of MSCs which possibly have ongoing activities for the subscriber. The HLR may then send at any time (i.e. without waiting for the IST Alert message) an unsolicited IST Command message to these MSCs in order to request termination of all ongoing activities for the subscriber. The HLR should send unsolicited IST Command message only to those MSCs that are likely to be carrying a call that needs to be terminated.
+
+Before sending of any IST Command message for a subscriber, the HLR should send the MAP Cancel Location message to the VLR at which the subscriber is registered. This will ensure that the subscriber cannot re-commence service at the corresponding MSC after the IST Command message has been executed. See Annex A of TS 22.032 [2]. The MSC shall be prepared to receive an IST Command message before and/or after the subscriber record has been removed from the VLR.
+
+# 5 Functional behaviour - CAMEL implementation
+
+This clause describes the implementation of IST using CAMEL. CAMEL can be used to terminate all the mobile originated (MO), mobile terminated (MT) and forwarded (CF) calls of a subscriber, provided there is a control relationship between the CAMEL server (the gsmSCF) in the HPLMN and the MSC (visited MSC or GMSC) (the gsmSSF) controlling the call or forwarding leg.
+
+## 5.1 Subscriber settings
+
+The subscriber is marked as a CAMEL subscriber by setting Originating CAMEL Subscription Information (O-CSI) and Terminating CAMEL Subscription Information (T-CSI) in the subscriber data stored in the HLR of the HPLMN. The O-CSI is sent to the VPLMN when the subscriber first registers in the VPLMN; the T-CSI is sent to the GMSC in the response to a request for routing information. If the subscriber is being monitored using FIGS, it will already be marked as a CAMEL subscriber.
+
+If the HPLMN wishes to mark a subscriber as a CAMEL subscriber when the subscriber is already registered in the VPLMN, it modifies the subscriber data in the VPLMN using the command *Insert Subscriber Data*.
+
+## 5.2 DP Settings
+
+A call cannot be terminated using CAMEL unless there is a control relationship between the gsmSCF and the gsmSSF controlling the call. To ensure that the IST command can be used at any point in the duration of a call, right up to the end of the call, there must be a control relationship until the end of the call.
+
+A "control relationship" exists where there is at least one armed DP in the gsmSSF. This can be achieved if the DP *O/T\_Disconnect* (which will trigger the sending of an *Event\_Report\_BCSM* to the gsmSCF) is set for the call.
+
+If the subscriber is being monitored using FIGS level 2 or 3, the subscriber will already be marked as a CAMEL subscriber and DP *O/T\_Disconnect* will already have been set.
+
+If the subscriber is not being monitored using FIGS levels 2 or 3 then *O/T\_Disconnect* is set with command *Request\_Report\_BCSM\_Event* sent to the gsmSSF by the gsmSCF after the gsmSCF has received notification of a call attempt via the *Initial\_DP* message received from the gsmSSF.
+
+*Initial\_DP* notifies the gsmSCF of call attempts. If the gsmSCF wishes to be notified of the success or failure of a call attempt, and so not be keeping a register of "calls" that may not have commenced, DP *O/T\_Answer* can be set to inform the gsmSCF when a call is answered by the calling party.
+
+If the **non**-reception of an *Event\_Report\_BCSM* indicating call answer is **not** sufficient indication to the HPLMN of the failure of a call attempt, DPs *O\_Route\_Select\_Failure*, *O/T\_Busy*, *O/T\_No\_Answer*, *O/T\_Abandon*, *O/T\_Not\_Reachable* can be set to inform the gsmSCF explicitly if the call attempt fails. If the various failure DPs are not armed, the gsmSCF can still deduce that the call attempt has failed because the gsmSSF will terminate the relationship when the call fails by sending message *Abort* to the gsmSCF.
+
+All these DPs can be set via the *Request\_Report\_BCSM\_Event* sent to the gsmSSF by the gsmSCF after receiving the *InitialDP* message. If all these DPs are set then the subscriber is in fact being monitored with the equivalent of FIGS level 2 monitoring.
+
+## 5.3 Call termination
+
+The HPLMN will be informed of the call attempts (MO, MT and CF) of the subscriber with message *InitialDP*. This message will give the address of the gsmSSF (=MSC) controlling the call. The call can be terminated by the gsmSSF at any time by sending message *ReleaseCall* to the controlling gsmSSF. The gsmSSF will then terminate the call.
+
+# 6 Functional behaviour - Non-CAMEL implementation
+
+This clause describes the implementation of IST using non-CAMEL implementation. This mechanism can be used to terminate all the originated (MO), terminated (MT) Deflected (CD), Transferred (ECT) and forwarded (CF) calls of a
+
+subscriber, provided that this IST mechanism is supported in the HLR and in the serving MSC/VLRs (visited MSC or GMSC controlling the call or forwarding leg).
+
+## 6.1 Subscriber Settings
+
+The subscriber is marked as a non-CAMEL IST subscriber by setting an IST Alert timer value in the subscriber data stored in the HLR. The IST Alert timer value is sent to the VLR in response to an Update Location request which indicates that the MSC/VLR supports IST; the IST Alert timer value is sent to the GMSC in the response to a request for routing information which indicates that the GMSC supports IST.
+
+The IST Alert timer value is in a range from 15 to 255 minutes with steps of 1 minute. For the subscribers not marked as IST non-CAMEL subscribers, the IST Alert timer value is not transmitted to the VLR or to the GMSC. The IST Alert timer value may be assigned on subscriber basis depending on the risk associated to the specific subscriber. As a network option the IST Alert timer value transmitted for a certain subscriber may be different for different entities (or PLMNs).
+
+If the HLR operator wishes to mark a subscriber as a non-CAMEL IST subscriber when the subscriber is already registered in a VLR, provided that the VLR supports IST, the HLR modifies the subscriber data in the VLR using the MAP Insert Subscriber Data message. Note that this does not affect already ongoing activities in the MSC. If the subscriber is under IST condition and the HLR operator decides to remove this condition, the HLR modifies the subscriber data in the VLR using the MAP Delete Subscriber Data message. Note that this does not affect the operation of any timer which is currently running.
+
+## 6.2 Periodic reporting mechanism
+
+### 6.2.1 IST Alert timer Settings
+
+The call termination shall be provided based on a "notification relationship". The HLR shall request to the MSCs during location update and routing information retrieval to report for each remaining activity periodically at the frequency defined by the IST Alert timer value about the remaining activity for that subscriber in the node by sending an IST Alert message to the HLR, as long as the activity is ongoing.
+
+The timer supervision starts in the MSC after initiation of any outgoing call activity [MO, CD, CF, ECT calls] for that subscriber. A separate timer supervision shall be initiated per each outgoing call activity for each subscriber. The notification IST Alert message is then transmitted to the HLR per call activity whenever the IST Alert timer running for that call expires. When the HLR receives an IST Alert message from an MSC, it can either return an empty result component, return a component including the subscribed IST Alert timer value, return an indication that the IST condition has been removed for the subscriber or return a call termination indicator. This returned call termination indicator is used by the MSC to terminate the outgoing call activities (either the call activity that initiated the IST Alert dialogue, or optionally to release all outgoing call activities) for that subscriber in the MSC. Release of all call activities using the returned call termination indicator is possible only if the MSC is able to link all call activities related to that subscriber. If the HLR has returned an indication that the IST condition has been removed from the subscriber, IST control for that call in the MSC is terminated. The IST Alert timer that monitors the activity that initiated the IST Alert is restarted when no call termination indicator has been received in the IST Alert dialogue and the IST Alert response received does not indicate termination of IST condition; the IST Alert timer value shall be the same as in the previous count, or the new value received in the IST Alert response if any.
+
+The timer supervision starts in the GMSC after reception of the response to a request for routing information. A separate timer supervision shall be initiated per each incoming call activity [MT, CF] for each subscriber. An IST Alert message is then transmitted to the HLR per call activity whenever the IST Alert timer running for that call expires. When the HLR receives an IST Alert message from a GMSC, it can either return an empty result component, return a component including the subscribed IST Alert timer value, return an indication that the IST condition has been withdrawn for the subscriber or return a call termination indicator. This returned call termination indicator is used by the GMSC to terminate the incoming call activities (either the call activity that initiated the IST Alert dialogue, or optionally to release all incoming call activities) for that subscriber in the GMSC. Release of all incoming call activities using the returned call termination indicator is possible only if the GMSC is able to link all call activities related to that subscriber. If the HLR has returned an indication that IST condition has been withdrawn from the subscriber, IST control for that call in the GMSC is terminated. The IST Alert timer that monitors the activity that initiated the IST Alert is restarted when no call termination indicator has been received in the IST Alert dialogue and the IST Alert
+
+response received does not indicate termination of IST condition; the timer value shall be the same as in the previous count, or the new value received in the IST Alert response if any.
+
+### 6.2.2 Call termination
+
+The VMSC (current or previous) will inform the HLR about each of the remaining outgoing call activities (MO, CD, ECT and CF) of the subscriber with a IST Alert message. This message contains the IMSI of that subscriber. Each of the originating, deflected, transferred or forwarded calls for a specific subscriber can be terminated in the MSC by returning a call termination indicator from the HLR to the controlling MSC in response to the IST Alert message. The MSC shall then terminate the call activity that initiated the alert, or it may also terminate all call activities for that subscriber if these activities are linked in the MSC.
+
+The GMSC will inform the HLR about each of the remaining incoming call activities (MT and CF) of the subscriber with a IST Alert message. This message contains the IMSI of that subscriber. Each of the terminating or forwarded calls for a specific subscriber can be terminated in the GMSC by returning a call termination indicator from the HLR to the controlling GMSC in response to the IST Alert message. The GMSC shall then terminate the call activity that initiated the alert, or it may also terminate all call activities for that subscriber if these activities are linked in the GMSC.
+
+## 6.3 IST standalone mechanism
+
+In addition to the periodic reporting mechanism, the IST standalone mechanism can optionally be supported in the HLR, the VMSC and the GMSC. This mechanism can be used to immediately terminate all outgoing subscriber activities in a VMSC and all incoming subscriber activities in the GMSC even when the subscriber is not under IST condition i.e. the MSC shall be able to terminate the call activities upon reception of the standalone IST command without having any previous IST subscriber settings defined.
+
+Provided that the MSC/VLR supports IST standalone mechanism, the HLR may request the immediate disconnection of the outgoing calls by sending a MAP Cancel Location message to the current VLR, and afterwards the IST Command message to the current VMSC without waiting for an IST Alert message.
+
+The HLR may also be able to request the immediate disconnection of outgoing call activities of a subscriber in previous VMSCs; for this purpose, the HLR may maintain a list of previous VMSCs with possibly remaining activities, to which the IST Command message may be sent without waiting for an IST Alert message. The mechanism used to maintain this list is out of the scope of this specification. The HLR may also be able to request the immediate disconnection of incoming call activities of a subscriber in any GMSC that may have requested routeing info from the HLR; for this purpose, the HLR may maintain a list of GMSCs with possibly remaining activities to which the IST Command message may be sent without waiting for an IST Alert message. The mechanism used to maintain this list is outside the scope of this specification.
+
+The standalone IST Command is used in the MSC to terminate immediately all outgoing call activities for a subscriber. This is only possible if the MSC is able to link all the call activities for the same subscriber using the IMSI as key. Then, when a standalone IST command is received including the IMSI of the subscriber, the MSC can terminate all the outgoing call activities for that subscriber. If the MSC does not support IST standalone mechanism, it shall return an error in response to the HLR.
+
+The standalone IST Command is used in the GMSC to terminate immediately all incoming call activities for a subscriber. This is only possible if the GMSC is able to link all the call activities for the same subscriber using the IMSI as key. Then, when a standalone IST Command is received including the IMSI of the subscriber, the GMSC can terminate all the incoming call activities for that subscriber. If the GMSC does not support IST standalone mechanism, it shall return an error in response to the HLR.
+
+## 6.4 Exception procedure
+
+The MSC/VLR shall inform the HLR about the support of IST function whenever a subscriber roams into that MSC/VLR area. Information about support of the IST standalone mechanism shall also be included. This information shall be included in the Update Location message sent to the HLR. The HLR can use the absence of any of these information to allow alternative actions in HLR in case of interworking with MSC/VLRs not supporting IST.
+
+The alternative actions when the MSC/VLR does not support the IST function can be, as an operator option:
+
+- Limit the service for the subscriber:
+
+Activating temporarily an Operator Determined barring of Roaming, Incoming or outgoing calls.
+
+- Allowing the service assuming associate risk of not having the IST mechanism available.
+
+The GMSC shall inform the HLR about the support of IST function whenever it requests routing information to establish a call. Information about support of the IST standalone mechanism shall also be included. This information shall be included in the Send Routing Information message sent to the HLR. The HLR can use the absence of any of these information to allow alternative actions in HLR in case of interworking with GMSCs not supporting IST.
+
+The alternative actions when the GMSC does not support the IST function can be, as an operator option:
+
+- Limit the service for the subscriber:
+
+Activating temporarily an Operator Determined barring of incoming calls, deactivate temporarily the Call forwarding services invoked in the GMSC.
+
+- Allowing the service assuming associate risk of not having the IST mechanism available.
+
+Error responses from HLR are also part of the exception procedures. Whenever the error "Unknown Subscriber" is received from the HLR in response to an IST Alert message, the receiving entity (MSC or GMSC) shall terminate the call that initiated the alert procedure. Also, if the receiving entity is able to link the activities for that subscriber (outgoing call activities in the MSC and incoming call activities in the GMSC), it shall terminate all of them if an "Unknown Subscriber" error is received in response to any IST Alert message.
+
+# --- 7 Control of IST
+
+Definition of the method used by a PLMN to decide which subscribers to use IST upon is outside the scope of this specification. However, it is likely that the decision will be made by some sort of FDS within the PLMN. The interface between the FDS and the PLMN node that sends the IST Command message to the VPLMN (the CAMEL server for a CAMEL implementation of IST) is outside the scope of this specification.
+
+# Annex A (Informative): Change History
+
+| Change history                                         |       |           |     |     |     |                                                                                                                      |                  |                   |
+|--------------------------------------------------------|-------|-----------|-----|-----|-----|----------------------------------------------------------------------------------------------------------------------|------------------|-------------------|
+| Date                                                   | TSG # | TSG Doc   | CR  | Rev | Cat | Subject/Comment                                                                                                      | Old              | New               |
+| 03-2001                                                | SP-11 | -         | -   | -   | -   | Upgrade to Release 4 (and 3GPP numbering)                                                                            | 03.35<br>v 8.0.0 | 43.035<br>v 4.0.0 |
+| 03-2002                                                | SP-15 | SP-020113 | 001 |     | A   | IST implementation for non-CAMEL subscribers                                                                         | 4.0.0            | 4.1.0             |
+| Status of TS 23.035 (Created from TS 43.035 Release 4) |       |           |     |     |     |                                                                                                                      |                  |                   |
+| 06-2002                                                | SP-16 | -         | -   | -   | -   | Decision to transfer IST to 3GPP system specification set.<br>References corrected to 3GPP specification references. | 43.035<br>4.1.0  | 23.035<br>4.0.0   |
+| Status of TS 23.035 (Release 5)                        |       |           |     |     |     |                                                                                                                      |                  |                   |
+| 06-2002                                                | SP-16 | -         | -   | -   | -   | Upgrade to Release 5                                                                                                 | 4.0.0            | 5.0.0             |
+| 09-2002                                                | SP-17 | SP-020509 | 003 |     | A   | Correction of use IST Command message and Call Termination Indication parameter                                      | 5.0.0            | 5.1.0             |
+| 12-2004                                                | SP-26 | -         | -   | -   | -   | Upgrade to Release 6                                                                                                 | 5.0.0            | 6.0.0             |
+| 06-2007                                                | SP-36 | -         | -   | -   | -   | Upgrade to Release 7                                                                                                 | 6.0.0            | 7.0.0             |
+| 12-2008                                                | SP-42 | -         | -   | -   | -   | Upgrade to Release 8                                                                                                 | 7.0.0            | 8.0.0             |
+| 12-2009                                                | SP-46 | -         | -   | -   | -   | Upgrade to Release 9                                                                                                 | 8.0.0            | 9.0.0             |
+| 2011-03                                                | -     | -         | -   | -   | -   | Update to Rel-10 version (MCC)                                                                                       | 9.0.0            | 10.0.0            |
+| 2012-09                                                | -     | -         | -   | -   | -   | Update to Rel-11 version (MCC)                                                                                       | 10.0.0           | 11.0.0            |
+| 2014-09                                                | -     | -         | -   | -   | -   | Update to Rel-12 version (MCC)                                                                                       | 11.0.0           | 12.0.0            |
+| 2016-01                                                | -     | -         | -   | -   | -   | Update to Rel-13 version (MCC)                                                                                       | 12.0.0           | 13.0.0            |
+| 2017-03                                                | -     | -         | -   | -   | -   | Update to Rel-14 version (MCC)                                                                                       | 13.0.0           | 14.0.0            |
+| 2018-06                                                | -     | -         | -   | -   | -   | Update to Rel-15 version (MCC)                                                                                       | 14.0.0           | 15.0.0            |
+| 2020-07                                                | -     | -         | -   | -   | -   | Update to Rel-16 version (MCC)                                                                                       | 15.0.0           | 16.0.0            |
+| 2022-03                                                | -     | -         | -   | -   | -   | Update to Rel-17 version (MCC)                                                                                       | 16.0.0           | 17.0.0            |
+| 2024-03                                                | -     | -         | -   | -   | -   | Update to Rel-18 version (MCC)                                                                                       | 17.0.0           | 18.0.0            |

marked/Rel-18/23_series/23067/raw.md

@@ -0,0 +1,950 @@
+
+
+# 3GPP TS 23.067 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2 (Release 18)**
+
+![LTE Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in bold lowercase letters with a red signal icon above the "l", and the word "ADVANCED" in smaller uppercase letters to the right. A trademark symbol (TM) is at the bottom right.
+
+LTE Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters "3GPP" in a stylized, bold font with a red signal icon below the "P", and a trademark symbol (TM) at the top right.
+
+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.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                      |    |
+|--------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                       | 5  |
+| 1 Scope.....                                                                         | 6  |
+| 2 References.....                                                                    | 6  |
+| 3 Definitions and abbreviations .....                                                | 6  |
+| 3.1 Definitions.....                                                                 | 6  |
+| 3.2 Abbreviations .....                                                              | 7  |
+| 4 Main concepts .....                                                                | 7  |
+| 5 General architecture .....                                                         | 10 |
+| 6 Compatibility issues.....                                                          | 10 |
+| 7 Transmission .....                                                                 | 10 |
+| 8 Information storage .....                                                          | 10 |
+| 8.1 Stored in the HLR .....                                                          | 10 |
+| 8.1.1 State transition model .....                                                   | 11 |
+| 8.1.2 Transfer of information from HLR to VLR .....                                  | 11 |
+| 8.2 Stored in the VLR .....                                                          | 11 |
+| 8.3 Stored in the MSC .....                                                          | 11 |
+| 8.4 Stored in the SIM .....                                                          | 12 |
+| 8.5 Stored in the GCR (GSM only).....                                                | 12 |
+| 9 Identities.....                                                                    | 12 |
+| 10 Operation and maintenance aspects .....                                           | 12 |
+| 11 Functions and information flow .....                                              | 13 |
+| 11.1 Subscription.....                                                               | 13 |
+| 11.2 Change of subscription.....                                                     | 13 |
+| 11.3 Call set-up .....                                                               | 13 |
+| 11.3.1 Mobile originated calls .....                                                 | 13 |
+| 11.3.1.1 Indication of priority .....                                                | 13 |
+| 11.3.1.2 Subscription checking.....                                                  | 13 |
+| 11.3.1.3 Authentication and ciphering.....                                           | 13 |
+| 11.3.1.4 Indication of priority to the BSC/RNC .....                                 | 14 |
+| 11.3.1.5 Choice of radio channel .....                                               | 14 |
+| 11.3.1.6 Indication of priority to the Mobile Station .....                          | 14 |
+| 11.3.2 Mobile terminated calls .....                                                 | 14 |
+| 11.3.2.1 Indication of priority .....                                                | 14 |
+| 11.3.2.2 Indication of priority to the BSC/RNC .....                                 | 15 |
+| 11.3.2.3 Authentication and ciphering.....                                           | 15 |
+| 11.3.2.4 Termination with called subscriber in idle mode or group receive mode ..... | 15 |
+| 11.3.2.5 Termination with called subscriber in dedicated mode .....                  | 15 |
+| 11.3.3 Voice group call or voice broadcast call (GSM only) .....                     | 16 |
+| 11.3.3.1 Indication of priority to the related MSC.....                              | 16 |
+| 11.3.3.2 Authentication and ciphering.....                                           | 16 |
+| 11.3.3.3 Indication of priority to the called Mobile Stations .....                  | 16 |
+| 11.4 Pre-emption .....                                                               | 16 |
+| 11.4.1 Choice of communication to pre-empt .....                                     | 16 |
+| 11.4.2 Release procedures .....                                                      | 16 |
+| 11.5 Pre-emption at handover/relocation .....                                        | 16 |
+| 11.6 Overview of call related signalling .....                                       | 16 |
+| 11.7 Overview of call independent signalling.....                                    | 24 |
+| 11.7.1 Registration.....                                                             | 24 |
+| 11.7.2 Interrogation .....                                                           | 24 |
+
+**Annex A (informative): Change history..... 25**
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the stage 2 description of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP) which provides different call priorities in combination with fast call set-up and pre-emption for different applications according to 3GPP TS 22.067.
+
+# --- 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.
+- [1] 3GPP TR 21.905: "3G Vocabulary".
+- [2] 3GPP TS 22.101: "UMTS Service Principles".
+- [3] 3GPP TS 22.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 1".
+- [4] 3GPP TS 23.011: "Technical realization of supplementary services".
+- [5] 3GPP TS 43.068: "Voice Group Call Service (VGCS) - Stage 2".
+- [6] 3GPP TS 43.069: "Voice Broadcast Service (VBS) - Stage 2".
+- [7] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification".
+- [8] ITU-T Recommendation Q.85: "Stage 2 description for community of interest supplementary services (clause 3: Multi-Level Precedence and Pre-emption MLPP)".
+- [9] ITU-T Recommendation Q.735: "Stage 3 description for community of interest supplementary services using SS No. 7 (clause 3: Multi-Level Precedence and Pre-emption (MLPP))".
+- [10] *Void*
+- [11] 3GPP TS 25.331: "RRC Protocol Specification".
+- [12] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
+- [13] 3GPP TS 24.008: "Core Network Protocols - Stage 3".
+- [14] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".
+- [15] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 22.067 and the following apply:
+
+**resource pre-emption:** the termination of a call of a low priority user such that resources can be made available for a precedence call of higher priority. Resource pre-emption could be initiation resource pre-emption or handover resource pre-emption
+
+**called-party pre-emption:** termination of a call to a particular user when a higher priority call is directed towards that specific user. Called party pre-emption is decided by the Mobile Station. In case of point-to-point calls, this shall be performed by Call Waiting with automatic acceptance of the waiting call by the Mobile Station
+
+**compatible Mobile Station:** mobile stations which support eMLPP and therefore have precedence and pre-emption capabilities
+
+**non-compatible Mobile Station:** mobile stations which do not support eMLPP
+
+**SIM:** subscriber Identity Module. This specification makes no distinction between SIM and USIM.
+
+Handover: This specification uses the term handover for GSM and the same term meaning relocation in UMTS.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3G TR 21.905 apply.
+
+# --- 4 Main concepts
+
+The enhanced Multi-Level Precedence and Pre-emption service (eMLPP) provides different levels of precedence for call set-up and for call continuity in case of handover.
+
+There are seven priority levels which are defined in 3GPP TS 22.067. The highest level (A) is reserved for network internal use. The second highest level (B) may be used for network internal use or, optionally, depending on regional requirements, for subscription. These two levels (A and B) may only be used locally, i.e. in the domain of one MSC. The other five priority levels are offered for subscription and may be applied globally, e.g. on inter switch trunks, if supported by all related network elements, and also for interworking with ISDN networks providing the MLPP service.
+
+The seven priority levels are defined as follows:
+
+- A (highest, for network internal use)
+- B (for network internal use or, optionally, for subscription)
+- 0 (for subscription)
+- 1 (for subscription)
+- 2 (for subscription)
+- 3 (for subscription)
+- 4 (lowest, for subscription).
+
+Levels A and B shall be mapped to level 0 for priority treatment outside of the MSC area in which they are applied.
+
+As a network specific configuration, the ability to pre-empt other calls of lower priority and the application of fast call set-up procedures can be assigned to each priority level. An example for an eMLPP configuration is given in 3GPP TS 22.067.
+
+NOTE 1: The present specification defines the concepts for handling of priorities in the network including the indication whether pre-emption or fast call set-up procedures are to be applied. Note that the call set-up procedures themselves are specified in the corresponding stage 2 descriptions of the services where they are to be used. There is presently only a requirement for VBS and VGCS (3GPP TS 43.069 and 3GPP TS 43.068, respectively).
+
+NOTE 2: The network operator has to assure that the particular eMLPP configuration he applies and the subscriptions he issues are co-ordinated with the network planning (especially for blocking) and the implementation options applied (e.g. the use of OACSU) in order to guarantee the service performance for the subscriber.
+
+Considering aspects of priority handling, the following issues can be considered for each call:
+
+- a) contention during the initial random access (no specific definitions apply for eMLPP. Delays due to access collision have to be managed by a corresponding planning of the network resources);
+- b) in GSM, contention in gaining radio resources during the call set-up phase and during handover (this item relates to the assignment of SDCCH and TCH for which queuing and pre-emption mechanisms are applied for eMLPP);  
+in UMTS, contention in gaining radio resources during the call set-up phase and during relocation (this item relates to the assignment of DCCH and DTCH for which queuing and pre-emption mechanisms are applied for eMLPP);  
+A pre-emption might already be performed as a network option on the basis of the establishment cause if a network specific eMLPP configuration assigns a certain priority level to a particular establishment cause.
+- c) contention in gaining terrestrial resources inside the GSM or UMTS network (this item relates to the assignment of terrestrial channels between the GSM or UMTS network nodes. Priority actions shall be performed on basis of the MLPP service implementations. The eMLPP priority levels A and B shall be mapped to the MLPP priority level 0. No further specific definitions apply for eMLPP);
+- d) contention in gaining terrestrial resources in external networks (this item relates to interworking with external networks which shall be performed on basis of the MLPP service if provided in the related external networks.);
+- e) application of different call set-up procedures in relation to the priority levels and the network specific configuration (three classes of set-up performance are defined in 3GPP TS 22.067, one very fast class for VBS or VGCS emergency call services, one class for fast but normal set-up times and one class allowing some delay in the set-up. The application of the corresponding procedures shall be decided by the network on the basis of the requested priority level);
+- f) automatic answering of calls if the incoming call exceeds a defined priority level (if the MS is in idle mode), or called party pre-emption (if the called subscriber is engaged in communication of a lower priority);
+- g) the means by which the called user is informed of priority issues and is able to make appropriate decisions if no called party pre-emption applies;
+- h) the accommodation of non-compatible Mobile Stations.
+
+The definitions in the present specification focus on the issues under item b), e), f), g) and h). Items c) and d) are related to the MLPP service implementation for the signalling system No. 7 according to ITU-T Recommendations Q.85 and Q.735.
+
+For a call establishment, a subscriber shall be able to select any one of the priority levels he has subscribed to.
+
+Priorities shall be treated in the network as defined in 3GPP TS 22.067. Priority treatment is different for point-to-point calls and voice broadcast calls or voice group calls, respectively:
+
+- mobile originated point-to-point call:
+
+The priority level depends on the calling subscriber. If the user has no eMLPP subscription, the call shall have a default priority level defined in the network. If the user has an eMLPP subscription, the call shall have the priority level selected by the user at set-up or the priority level predefined by the subscriber as default priority level by registration.
+
+- mobile terminated point-to-point calls:
+
+The priority level depends on the calling party. For this, interworking with the ISDN MLPP service is required. If the call is not an MLPP call, i.e. no priority level is defined, the call shall be treated in the mobile network with a default priority level. If the call is an MLPP call, the call shall be treated with the priority level provided by the interfacing network.
+
+- mobile to mobile point-to-point calls:
+
+The priority shall be treated for the calling subscriber as for mobile originated calls and for the called subscriber as for mobile terminated calls. However, an interworking with MLPP is not required if both the calling subscriber and the called subscriber are located in the same MSC area.
+
+- Voice Broadcast Calls (VBS) and Voice Group Calls (VGCS):
+
+The link on the voice broadcast call channel or voice group call channel shall have the priority level as defined in the corresponding registration for the related voice broadcast call or voice group call in the GCR. At the early stage of a voice broadcast call or voice group call establishment, before the GCR request is made and the voice broadcast call channel or voice group call channels are assigned, the procedure shall be the same as for point-to-point calls. If the GCR response includes a priority level it shall be applied to the dedicated link of the calling mobile station as well.
+
+Queuing and resource pre-emption shall then be applied as appropriate according to the network service configuration. In addition, automatic answering or called party pre-emption shall be applied as appropriated according to the Mobile Station's internal service configuration.
+
+The MSC shall maintain a record of the priority level of each call in progress in its area such that it can arbitrate over resources in a defined manner.
+
+The priority level can be included in the CM\_SERVICE\_REQUEST message in the case that a user establishing a point-to-point call is using a compatible Mobile Station (see clause 6).
+
+If the subscriber has not selected a priority level for that call or uses a non compatible Mobile Station (see clause 6), the priority level shall be assigned according to the respective VLR data.
+
+The priority level of a call shall be determined by the MSC. Accordingly, the MSC shall request channel assignment with an indication of the priority level and the pre-emption capability of that call. For this the MSC shall use the priority message element as defined in 3GPP TS 48.008. Mapping of the priority information in this message element on the network specific eMLPP configuration shall be performed in the MSC. Queuing and resource pre-emption shall be performed accordingly if necessary.
+
+In GSM, in addition to the priority signalling, the requirement for a direct assignment of a TCH shall be included in the establishment cause of the CHAN\_REQ message in order to support a fast call set-up procedure in the BSC at the earliest possible stage of the call establishment for high priority calls if applicable.
+
+In UMTS, in addition to the priority signalling, the RRC CONNECTION REQUEST message shall be included the establishment cause.
+
+Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following:
+
+- point-to-point calls:
+
+If the user is in idle mode, the Mobile Station shall automatically connect to an incoming call of a sufficient priority level. The priority level shall be included in the paging message and in the set-up message. If the user is in dedicated mode and has a subscription to Call Waiting, a Call Waiting indication including the priority level of the call shall be given to the Mobile Station which automatically accepts the waiting call.
+
+There is no called party pre-emption for point-to-point calls without Call Waiting.
+
+- voice group calls and voice broadcast calls:
+
+Notifications for other voice group calls, voice broadcast calls or information on paging for point-to-point calls shall be given to the Mobile Stations involved in on-going voice group calls or voice broadcast calls as defined in 3GPP TS 43.068 and 3GPP TS 43.069, respectively. The notifications include the related priority level of the call. In case of a notified call with higher priority where called-party pre-emption applies, the Mobile Station shall automatically leave the on-going voice group call or voice broadcast call and react according to the type of the notified call type.
+
+For both cases, the priority level applied shall be included, either in the paging message or Call Waiting indication, or in the notification message, in order to enable the Mobile Station to decide on an automatic reaction (automatic answering or called-party pre-emption) or to indicate the incoming, non pre-empting call to the user.
+
+The priority information of the assignment request shall also be applied for BSS internal and also UTRAN internal handover. For external handover, the MSC shall include the priority information in the handover request according to the definition in 3GPP TS 48.008 (for GSM) and TS 25.413 (for UMTS) in the same way as for the assignment request.
+
+# --- 5 General architecture
+
+No specific requirements are identified.
+
+# --- 6 Compatibility issues
+
+eMLPP cannot be applied with standard GSM Phase 1 or Phase 2 Mobile Stations (non compatible Mobile Stations) with all service aspects. A dedicated Mobile Station (compatible Mobile Station) with eMLPP capability is required.
+
+Specific functions a compatible Mobile Station shall provide are:
+
+- priority selection via MMI for call establishment in case of an eMLPP subscription including priority levels above level 4;
+- analysis of the priority level included in a paging message, Call Waiting indication or notification into a voice group call or voice broadcast call, respectively;
+- automatic reaction on basis of the analysed priority level in case of an incoming call while in dedicated mode, group transmit mode or group receive mode, respectively, according to the user defined Mobile Station configuration (for each subscribed priority level the user shall be able to configure the Mobile Station for automatic acceptance or indication or rejection of an incoming call);
+
+NOTE: Functions related to notifications are only required for Mobile Stations providing VBS or VGCS functions as defined in 3GPP TS 43.069 and 3GPP TS 43.068, respectively.
+
+However, if eMLPP is provided in a network, it can be applied to non compatible Mobile Stations in the following way:
+
+- calls of subscribers which have no specific eMLPP subscription shall be treated for resource pre-emption with a default priority level.
+
+This shall also apply independent of the use of compatible or non compatible Mobile Stations;
+
+- calls of eMLPP subscribers which use a non compatible Mobile Station shall be treated for resource pre-emption with the subscriber's default priority level;
+- calls to eMLPP subscribers which use a non compatible Mobile Station shall be indicated to the user by Call Waiting as normal.
+
+# --- 7 Transmission
+
+No specific requirements are identified.
+
+# --- 8 Information storage
+
+## 8.1 Stored in the HLR
+
+Information concerning the maximum priority level which a subscriber is entitled to use at call establishment shall be stored in the HLR.
+
+If the maximum priority level is above level 4, one level shall be indicated as default level. This default level shall be used for mobile originated calls if no priority selection is performed by the user at call establishment.
+
+The default selection can be performed by the subscriber by means of a registration procedure.
+
+**NOTE** The priority levels in the subscription are related to point-to-point calls. VBS and VGCS calls are treated with the priority level defined in the GCR for a certain group ID in a certain group call area which can be different to the priority levels explicitly defined in the eMLPP subscription. However, these levels are then implicitly defined with the subscribed group IDs.
+
+eMLPP may have the following logical states (refer to 3GPP TS 23.011 for an explanation of the notation):
+
+| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> |
+|---------------------------|---------------------------|-------------------------|----------------------------|
+| (Not Provisioned,         | Not Registered,           | Not Active              | Not Induced)               |
+| (Provisioned,             | Registered,               | Active and Operative    | Not Induced)               |
+
+The HLR shall store the logical state of eMLPP (which shall be one of the valid states listed above) on a per subscriber basis.
+
+### 8.1.1 State transition model
+
+The following figure shows the successful cases of transition between the applicable logical states of eMLPP. The state changes are caused by actions of the service provider.
+
+Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram.
+
+![State transition model for eMLPP diagram showing two states and two transitions.](b3c108e7145f2017957569d06ea359cb_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> State1 : (Not Provisioned, Not Registered, Not Active, Not Induced)
+    State1 --> State2 : Provision
+    State2 --> State1 : Withdrawal
+    state " (Not Provisioned, Not Registered, Not Active, Not Induced) " as State1
+    state " (Provisioned, Registered, Active and Operative, Not Induced) " as State2
+  
+```
+
+The diagram illustrates the state transition model for eMLPP. It consists of two circular states. The left state is labeled "(Not Provisioned, Not Registered, Not Active, Not Induced)". The right state is labeled "(Provisioned, Registered, Active and Operative, Not Induced)". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state.
+
+State transition model for eMLPP diagram showing two states and two transitions.
+
+**Figure 1: State transition model for eMLPP**
+
+### 8.1.2 Transfer of information from HLR to VLR
+
+If the provisioning state for eMLPP is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of eMLPP, the maximum priority level and the default priority level.
+
+If any of the eMLPP subscriber data is changed, the HLR shall send to the VLR the complete eMLPP subscriber data.
+
+## 8.2 Stored in the VLR
+
+For eMLPP, the VLR shall store the service state information, the maximum priority level a subscriber is entitled to use and the default priority level received from the HLR.
+
+## 8.3 Stored in the MSC
+
+The network specific service configuration of eMLPP defined by the network operator as specified in 3GPP TS 22.067 shall be stored within each MSC. This includes information on resource pre-emption actions for any given levels of incoming and on-going call priority. An example for a network specific service configuration is given in 3GPP TS 22.067.
+
+## 8.4 Stored in the SIM
+
+Each compatible Mobile Station shall be aware of the automatic answering actions for any given levels of priority so that when in idle mode or dedicated mode or group receive mode or group transmit mode, it can decide on the necessary reactions to be taken according to the priority information of the incoming call.
+
+**For this, the SIM shall store the following data:**
+
+| Priority level | Subscription available | Automatic answering applies | Fast set-up actions (note) |
+|----------------|------------------------|-----------------------------|----------------------------|
+| A              | yes/no                 | yes/no                      | yes/no                     |
+| B              | yes/no                 | yes/no                      | yes/no                     |
+| 0              | yes/no                 | yes/no                      | yes/no                     |
+| 1              | yes/no                 | yes/no                      | yes/no                     |
+| 2              | yes/no                 | yes/no                      | yes/no                     |
+| 3              | yes/no                 | yes/no                      | yes/no                     |
+| 4              | yes/no                 | --                          | yes/no                     |
+
+NOTE: Fast set-up actions which shall be performed by the Mobile Stations if indicated in the SIM data are the use of the appropriate establishment cause and the reaction on accelerated establishment procedures allowed by the network (see clause 11.6).
+
+The automatic reaction of the Mobile Station for automatic answering or called party pre-emption shall be predefined by the user via MMI. For each subscribed priority level the user shall be able to configure the Mobile Station for automatic acceptance or indication or rejection of an incoming call.
+
+In addition, the Mobile Station shall verify a priority level selected by the user at call establishment against the priority levels stored on the SIM and act accordingly as defined in clause 11.5.1.2.
+
+The Mobile Station shall perform automatically the related functions for a fast call set-up if related with a selected priority.
+
+## 8.5 Stored in the GCR (GSM only)
+
+In the network, specific service configurations for VBS and VGCS calls which are registered in the GCR, a priority level shall be assigned to each voice broadcast call or voice group call configuration, according to 3GPP TS 43.069 and 3GPP TS 43.068, respectively.
+
+# 9 Identities
+
+No specific requirements are identified.
+
+# 10 Operation and maintenance aspects
+
+NOTE: A list and short description of the operation and maintenance aspects will be given. This includes the options and parameters which can be set by the operator.
+
+- Handling of timers;
+- registration aspects etc.
+
+# 11 Functions and information flow
+
+## 11.1 Subscription
+
+When the subscriber record is created in the HLR, the maximum priority level a subscriber is entitled to use shall be included.
+
+## 11.2 Change of subscription
+
+The network operator can change the maximum priority level of any eMLPP subscriber at any time. A change of subscription shall not affect any on-going calls at the moment of change. The subscriber cannot change the maximum priority level via the MMI.
+
+## 11.3 Call set-up
+
+### 11.3.1 Mobile originated calls
+
+#### 11.3.1.1 Indication of priority
+
+The Mobile Station may indicate the priority of each call initiated. If no priority is indicated by the user or a non-compatible Mobile Station is used then the default priority level shall be applied which is stored in the VLR. The selection of priority shall be an MMI function.
+
+Mobile stations indicate the priority of their call in the signalling that takes place during the call establishment process.
+
+No preferential treatment will be possible during this initial random access until the point at which the priority information is received by the network (CM\_SERV\_REQ message). Alternatively, a resource pre-emption might already take place on basis of an establishment cause.
+
+In GSM, prior to the indication of the selected priority level in the CM\_SERV\_REQ message, the BSC may decide on the assignment of an SDCCH or direct assignment of a TCH on the basis of the establishment cause in the CHAN\_REQ message. This allows the BSC to support a fast call set-up at the earliest stage of the call establishment. The establishment cause for emergency calls or an establishment cause indicating the request for fast call set-up shall be able to trigger this function.
+
+In UMTS, prior to the indication of the selected priority level in the CM\_SERV\_REQ message, the RNC shall receive the establishment cause in the RRC CONNECTION SETUP REQUEST.
+
+#### 11.3.1.2 Subscription checking
+
+The Mobile Station shall verify the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level.
+
+The MSC shall request the VLR to verify if the subscriber is allowed to use the selected priority level.
+
+#### 11.3.1.3 Authentication and ciphering
+
+A GSM network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up.
+
+If the network decides to omit or postpone authentication and ciphering for a call it can send a CM\_SERV\_ACC message in reply to the CM\_SERV\_REQ message.
+
+#### 11.3.1.4 Indication of priority to the BSC/RNC
+
+In GSM, the channel assignment request to the BSC shall also include the priority level and pre-emption capability of the connection as defined in 3GPP TS 48.008. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the BSC in the assignment request. The BSC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities.
+
+In UMTS, the RAB assignment request to the RNC may also include the priority level and pre-emption capability of the connection as defined in TS 25.413 [12]. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the RNC in the RAB assignment request. Values for radio access bearer service attributes defined in TS 23.107 [14] should be taken into account for mapping from eMLPP priority into priority related information element in RANAP. The RNC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities.
+
+#### 11.3.1.5 Choice of radio channel
+
+If an appropriate radio channel is available the BSC (for GSM) or the RNC (for UMTS) shall assign it as normal. If no channels are available then the BSC (for GSM) or the RNC (for UMTS) shall perform queuing according to the priority levels. If the assignment request has a pre-emption capability indicator, pre-emption shall be performed.
+
+In addition, the network related service configuration defines the set-up class in relation to a priority level and therefore the allowable delay of the call establishment (see 3GPP TS 22.067). By using this information, the MSC shall decide whether OACSU may be applied for a call or not.
+
+#### 11.3.1.6 Indication of priority to the Mobile Station
+
+The network shall include the assigned priority level in a CALL\_PROCEEDING message if the network supports priority.
+
+The Mobile Station shall store the priority level requested by the user, possibly overridden by the level received by the network, to perform automatic answering of calls or pre-emption of on-going calls.
+
+NOTE: When the mobile station connects to the R98 or older network, the mobile station may not receive priority granted even if the network supports priority.
+
+### 11.3.2 Mobile terminated calls
+
+#### 11.3.2.1 Indication of priority
+
+For a mobile terminated call, the priority level is defined in the ISUP set-up message to the VMSC. It may also be present in the MAP\_PROVIDE\_ROAMING\_NUMBER request (see 3GPP TS 29.002 [15]). The priority and pre-emption indications used in the ISUP shall follow the definitions of the MLPP service as defined in the ITU-T recommendations Q.85 and Q.735, respectively.
+
+In GSM, a PAGING REQUEST message on CCCH may also include a priority level as described in GSM 04.08 [10], clause 'Paging initiation using paging subchannel on CCCH'.
+
+NOTE: A mobile stations in idle mode which are going to respond to a paging message do not need to analyse the priority level in the paging request message but can take the priority level provided in the set-up message. A mobile stations in group receive mode or an MS in class-B mode that communicates on GPRS radio channels when a dedicated channel is needed need to analyse the priority level in the paging request message in order to decide to respond to the paging request. (see TS 23.060 clause 16.2.2)
+
+In UMTS, if the MSC identifies a mobile terminated call as a high priority call based on local configuration of the eMLPP service, the MSC shall include in the Paging message the Paging Cause IE set to the value "Terminating High Priority Signalling".
+
+#### 11.3.2.2 Indication of priority to the BSC/RNC
+
+In GSM, the channel assignment request to the BSC may include the priority level and pre-emption capability of the connection as defined in 3GPP TS 48.008. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the BSC in the assignment request. The BSC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities.
+
+In UMTS, the RAB assignment request to the RNC may include the priority level and pre-emption capability of the connection as defined in TS 25.413. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the RNC in the RAB assignment request. Values for radio access bearer service attributes defined in TS 23.107 [14] should be taken into account for mapping from eMLPP priority into priority related information element in RANAP. The RNC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities.
+
+#### 11.3.2.3 Authentication and ciphering
+
+The network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up according to the priority level to be applied for the call and the network specific service configuration stored in the MSC.
+
+If the network decides to omit or postpone authentication and ciphering for a call it, can send the SETUP message immediately after reception of the initial layer 3 message.
+
+#### 11.3.2.4 Termination with called subscriber in idle mode or group receive mode
+
+In this case the Mobile Station shall be paged in the normal manner, but with the paging messages also containing the priority level of the call. In addition, the priority level will be provided with the SETUP message.
+
+The Mobile Station in group receive mode shall consult the internal service configuration list stored on the SIM to check whether it should automatically respond to the paging request. If it does respond to the paging request and if a following Call Control SETUP message (received as a response to paging response) specifies a priority different from the one specified in the paging request, this fact is not a reason for the mobile station to reject the (point-to-point) call for which the SETUP message was received.
+
+The Mobile Station in idle mode does not need to analyse the priority level from the paging request message but can derive it from the SETUP message and then decide on automatic acceptance of the call.
+
+In the case where the called subscriber is using a non compatible Mobile Station, automatic answering is not possible.
+
+#### 11.3.2.5 Termination with called subscriber in dedicated mode
+
+In the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal.
+
+In the case where the called subscriber has no subscription for Call Waiting, called party pre-emption is not possible.
+
+In the case where the called subscriber is using a non compatible Mobile Station and has a subscription for Call Waiting, Call Waiting shall be performed as normal.
+
+### 11.3.3 Voice group call or voice broadcast call (GSM only)
+
+#### 11.3.3.1 Indication of priority to the related MSC
+
+For each voice group call or voice broadcast call service configuration registered in the GCR as defined in 3GPP TS 43.068 and 3GPP TS 43.069, respectively, a priority level is assigned at registration of the GCR data by the service provider. The priority level will be provided by the GCR together with the call attributes.
+
+#### 11.3.3.2 Authentication and ciphering
+
+Authentication of the calling service subscriber shall be performed equivalent to the standard mobile originated call case as defined in clause 11.5.1.3. If the GCR response provides a priority level then the calling service subscriber shall be treated with the GCR defined priority. If not, then the calling service subscriber shall be treated with his selected priority or with his default priority as known in the VLR as long as he has an own link with the network (see 3GPP TS 43.068 and 3GPP TS 43.069). The priority which applies to the voice group call channel or voice broadcast call channel is defined in the GCR.
+
+Authentication and ciphering of the calling service subscriber might therefore be performed, omitted or postponed (see clause 11.3.1.3).
+
+#### 11.3.3.3 Indication of priority to the called Mobile Stations
+
+The priority level shall be indicated together with the related paging messages or notification messages and treated in the Mobile Station as defined in 3GPP TS 43.068 and 3GPP TS 43.069, respectively.
+
+## 11.4 Pre-emption
+
+### 11.4.1 Choice of communication to pre-empt
+
+For all resources where pre-emption may be required, namely radio channels, A-interface (for GSM) or Iu interface (for UMTS) channels and inter switch trunks, the network specific service configuration stored within the MSC shall be used to determine whether pre-emption should occur, and if so, which communication to pre-empt. The MSC shall inform the BSS (for GSM) or RNC (for UMTS) about priority and pre-emption by using the priority message element in the assignment request as defined in 3GPP TS 48.008 (for GSM) and TS 25.413 [12] (for UMTS). Mapping of the priority information in this message element on the network specific eMLPP configuration shall be performed in the MSC.
+
+### 11.4.2 Release procedures
+
+Suitable messages shall be passed from the point at which the pre-emption is to occur, to other affected entities. In the case of fast call set-up, such pre-indication may need to be foregone to meet the required set-up time.
+
+The indication to the pre-empted user shall be performed by an indication for congestion as defined in 3GPP TS 22.101.
+
+## 11.5 Pre-emption at handover/relocation
+
+When an on-going call is handed over or relocated into a fully used cell, the BSC or RNC shall perform queuing and pre-emption if necessary according to the priority and pre-emption capability information received with the assignment request.
+
+In case of BSS external handover or RNC relocation, the priority and pre-emption capability information shall be included in the handover request as defined in 3GPP TS 48.008 (for GSM) and TS 25.413 [12] (for UMTS).
+
+## 11.6 Overview of call related signalling
+
+In this overview, the message structure to implement the specified concept is identified, and brief details are given of each message.
+
+A diagrammatic representation of the transport procedures to be used to carry the priority information in case of standard point-to-point calls are given in figures 1 to 6. The message flow is not represented completely.
+
+The corresponding message flows in case of voice group calls or voice broadcast calls are given in 3GPP TS 23.068 and 3GPP TS 23.069, respectively.
+
+![Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment without fast call set-up (for GSM). The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The message flow is as follows: 1. MS sends RACH_CHAN_REQ to BSS. 2. BSS sends IMM_ASS to MS. 3. MS sends SABM (SERV_REQ) to BSS. 4. BSS sends COM L3_INFO to MSC. 5. BSS sends UA (SERV_REQ) to MS. 6. MSC sends AUTH_REQ to BSS. 7. BSS sends AUTH_RES to MSC. 8. MSC sends CIPH_MOD_CMD to BSS. 9. BSS sends CIPH_MOD_COM to MS. 10. MS sends SETUP to BSS. 11. BSS sends CALL_PROCEEDING to MSC. 12. MSC sends ASS_REQ to BSS. 13. BSS sends ASS_CMD to MS. 14. MS sends SABM to BSS. 15. BSS sends UA to MS. 16. MS sends ASS_COM to BSS. 17. BSS sends ASS_COM to MSC.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BSS
+    participant MSC
+    Note left of MS: Initial RACH_CHAN_REQ
+    MS->>BSS: RACH_CHAN_REQ
+    BSS-->>MS: IMM_ASS
+    Note left of MS: SABM (SERV_REQ)
+    MS->>BSS: SABM (SERV_REQ)
+    BSS->>MSC: COM L3_INFO
+    BSS-->>MS: UA (SERV_REQ)
+    Note right of MSC: AUTH_REQ
+    MSC->>BSS: AUTH_REQ
+    BSS->>MSC: AUTH_RES
+    Note right of MSC: CIPH_MOD_CMD
+    MSC->>BSS: CIPH_MOD_CMD
+    BSS->>MS: CIPH_MOD_COM
+    Note left of MS: SETUP
+    MS->>BSS: SETUP
+    BSS->>MSC: CALL_PROCEEDING
+    Note right of MSC: ASS_REQ
+    MSC->>BSS: ASS_REQ
+    BSS->>MS: ASS_CMD
+    Note left of MS: SABM
+    MS->>BSS: SABM
+    BSS-->>MS: UA
+    Note left of MS: ASS_COM
+    MS->>BSS: ASS_COM
+    BSS->>MSC: ASS_COM
+  
+```
+
+Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment without fast call set-up (for GSM). The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The message flow is as follows: 1. MS sends RACH\_CHAN\_REQ to BSS. 2. BSS sends IMM\_ASS to MS. 3. MS sends SABM (SERV\_REQ) to BSS. 4. BSS sends COM L3\_INFO to MSC. 5. BSS sends UA (SERV\_REQ) to MS. 6. MSC sends AUTH\_REQ to BSS. 7. BSS sends AUTH\_RES to MSC. 8. MSC sends CIPH\_MOD\_CMD to BSS. 9. BSS sends CIPH\_MOD\_COM to MS. 10. MS sends SETUP to BSS. 11. BSS sends CALL\_PROCEEDING to MSC. 12. MSC sends ASS\_REQ to BSS. 13. BSS sends ASS\_CMD to MS. 14. MS sends SABM to BSS. 15. BSS sends UA to MS. 16. MS sends ASS\_COM to BSS. 17. BSS sends ASS\_COM to MSC.
+
+**Figure 2: Signalling information required for the prioritisation at mobile originating call establishment without fast call set-up (for GSM)**
+
+**Initial RACH\_CHAN\_REQ:** Standard message.
+
+**IMM\_ASS:** Standard message.
+
+**SABM (SERV\_REQ):** Modified form of the current L3-MM CM SERVICE REQUEST where the priority level is provided in addition if a priority selection is performed by the user. In case of no priority selection or use of a non-compatible Mobile Station the Mobile Station shall send a standard service request message and the network shall apply a default priority to their request.
+
+**UA (SERV\_REQ):** Standard message.
+
+**COM L3\_INFO:** The MSC is provided with initial information about the requested service together with the selected priority level if applicable.
+
+**AUTH\_REQ:** Standard message.
+
+**AUTH\_RES:** Standard message.
+
+**CIPH\_MOD\_CMD:** Standard message.
+
+**CIPH\_MOD\_COM:** Standard message.
+
+**SETUP:** Standard message.
+
+**CALL\_PROCEEDING:** The network shall include the assigned priority level in a CALL\_PROCEEDING message when the network supports priority.
+
+**ASS\_REQ:** This message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from the service request or from the VLR data. In addition, the eMLPP level is included as explicit information.
+
+**ASS\_CMD:** Standard message.
+
+**SABM:** Standard message.
+
+**UA:** Standard message.
+
+**ASS\_COM:** Standard message.
+
+###### Release 9
+
+![Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment with fast call set-up (for GSM). The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. MS receives [SYSTEM INFO] from BSS. 2. MS sends RACH (CHAN_REQ) to BSS. 3. BSS sends IMM_ASS to MS. 4. MS sends SABM (SERV_REQ) to BSS. 5. BSS sends COM_L3_INFO to MSC. 6. BSS sends UA (SERV_REQ) to MS. 7. MS sends SETUP to BSS. 8. BSS sends CALL_PROCEEDING to MSC. 9. MSC sends CHAN_MOD_MODIFY to BSS. 10. BSS sends CHAN_MOD_MODIFY_ACK to MS.](7b8b192e2853ef28d28eff0241ebe86b_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BSS
+    participant MSC
+    Note left of MS: MS receives [SYSTEM INFO] from BSS
+    MS->>BSS: RACH (CHAN_REQ)
+    BSS-->>MS: IMM_ASS
+    MS->>BSS: SABM (SERV_REQ)
+    BSS->>MSC: COM_L3_INFO
+    BSS-->>MS: UA (SERV_REQ)
+    MS->>BSS: SETUP
+    BSS->>MSC: CALL_PROCEEDING
+    MSC->>BSS: CHAN_MOD_MODIFY
+    BSS-->>MS: CHAN_MOD_MODIFY_ACK
+  
+```
+
+Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment with fast call set-up (for GSM). The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. MS receives [SYSTEM INFO] from BSS. 2. MS sends RACH (CHAN\_REQ) to BSS. 3. BSS sends IMM\_ASS to MS. 4. MS sends SABM (SERV\_REQ) to BSS. 5. BSS sends COM\_L3\_INFO to MSC. 6. BSS sends UA (SERV\_REQ) to MS. 7. MS sends SETUP to BSS. 8. BSS sends CALL\_PROCEEDING to MSC. 9. MSC sends CHAN\_MOD\_MODIFY to BSS. 10. BSS sends CHAN\_MOD\_MODIFY\_ACK to MS.
+
+**Figure 3: Signalling information required for the prioritisation at mobile originating call establishment with fast call set-up (for GSM)**
+
+**SYSTEM INFO:** The network may provide information on the BCCH system information, that a MM connection is provisional granted after establishment of the main signalling link.
+
+If such information is provided on the BCCH and the user has selected a fast call set-up, the Mobile Station shall immediately send a SETUP message to the network after the main signalling link is established.
+
+**Initial RACH CHAN\_REQ:** Standard message.
+
+**IMM\_ASS:** Standard message.
+
+**SABM (SERV\_REQ):** Modified form of the current L3-MM CM SERVICE REQUEST where the priority level is provided in addition if a priority selection is performed by the user.
+
+**UA (SERV\_REQ):** Standard message.
+
+**COM\_L3\_INFO:** The MSC is provided with initial information about the requested service together with the selected priority level if applicable.
+
+If the network itself decides not to perform ciphering, it shall send an CM\_SERV\_ACC message.
+
+**SETUP:** Standard message.
+
+**CALL\_PROCEEDING:** The network shall include the assigned priority level in a CALL\_PROCEEDING message when the network supports priority
+
+**ASS\_REQ:** This standard message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from the service request or from the VLR data. In addition, the eMLPP level is included as explicit information.
+
+**CHAN\_MOD\_MODIFY:** Standard message.
+
+**CHAN\_MOD\_MODIFY\_ACK:** Standard message.
+
+![Sequence diagram showing signalling information for mobile terminating call establishment between MS, BSS, and MSC.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BSS
+    participant MSC
+    Note right of MSC: SETUP (prec.)  
+req. ind.
+    MSC->>BSS: PAGING
+    BSS->>MS: PAG_REQ
+    MS->>BSS: RACH (CHAN_REQ)
+    BSS->>MS: IMM_ASS
+    MS->>BSS: SABM (PAG_RSP)
+    BSS->>MSC: PAG_RSP
+    MSC->>BSS: AUTH_REQ
+    BSS->>MS: AUTH_RES
+    MSC->>BSS: CIPH_MOD_CMD
+    BSS->>MS: CIPH_MOD_COM
+    MSC->>BSS: SETUP
+    BSS->>MS: CALL_CONF
+    MSC->>BSS: ASS_REQ
+    BSS->>MS: ASS_CMD
+    MS->>BSS: SABM
+    BSS->>MS: UA
+    BSS->>MSC: ASS_COM
+  
+```
+
+Sequence diagram showing signalling information for mobile terminating call establishment between MS, BSS, and MSC.
+
+**Figure 4: Signalling information required for the prioritisation at mobile terminating call establishment without fast call set-up and without called-party pre-emption (for GSM)**
+
+**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level.
+
+**PAGING:** Modified paging command including the priority level to be applied.
+
+**PAG\_REQ:** Modified paging message including the related priority level.
+
+**Initial RACH CHAN\_REQ:** Standard message.
+
+**IMM\_ASS:** Standard message.
+
+**SABM (PAG\_RSP):** Standard message.
+
+**UA (PAG\_RSP):** Standard message.
+
+**PAG\_RSP:** Standard message.
+
+**AUTH\_REQ:** Standard message.
+
+**AUTH\_RES:** Standard message.
+
+**CIPH\_MOD\_CMD:** Standard message.
+
+**CIPH\_MOD\_COM:** Standard message.
+
+**SETUP:** Standard message.
+
+**CALL\_CONF:** Standard message.
+
+**ASS\_REQ:** This standard message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from the incoming set-up message. In addition, the eMLPP level is included as explicit information.
+
+**ASS\_CMD:** Standard message.
+
+**SABM:** Standard message.
+
+**UA:** Standard message.
+
+**ASS\_COM:** Standard message.
+
+![Sequence diagram showing signalling information required for prioritisation at mobile terminating call establishment with fast call set-up and without called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is: 1. MSC sends SETUP (prec.) req. ind. to BSS. 2. BSS sends PAGING to MS. 3. MS responds with PAG_REQ. 4. BSS sends RACH (CHAN_REQ) to MS. 5. MS responds with IMM_ASS. 6. BSS sends SABM (PAG_RSP) to MS. 7. MS responds with UA (PAG_RSP). 8. BSS sends PAG_RSP to MSC. 9. MSC sends SETUP to BSS. 10. BSS sends CALL_CONF to MSC. 11. MSC sends CHAN_MOD_MODIFY to BSS. 12. BSS responds with CHAN_MOD_MODIFY_ACK.](2876be3592c7b4878400b85f209b2b6a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BSS
+    participant MSC
+    Note right of MSC: SETUP (prec.)  
+req. ind.
+    MSC->>BSS: SETUP (prec.) req. ind.
+    BSS->>MS: PAGING
+    MS->>BSS: PAG_REQ
+    BSS->>MS: RACH (CHAN_REQ)
+    MS->>BSS: IMM_ASS
+    BSS->>MS: SABM (PAG_RSP)
+    MS->>BSS: UA (PAG_RSP)
+    BSS->>MSC: PAG_RSP
+    MSC->>BSS: SETUP
+    BSS->>MSC: CALL_CONF
+    MSC->>BSS: CHAN_MOD_MODIFY
+    BSS->>MSC: CHAN_MOD_MODIFY_ACK
+  
+```
+
+Sequence diagram showing signalling information required for prioritisation at mobile terminating call establishment with fast call set-up and without called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is: 1. MSC sends SETUP (prec.) req. ind. to BSS. 2. BSS sends PAGING to MS. 3. MS responds with PAG\_REQ. 4. BSS sends RACH (CHAN\_REQ) to MS. 5. MS responds with IMM\_ASS. 6. BSS sends SABM (PAG\_RSP) to MS. 7. MS responds with UA (PAG\_RSP). 8. BSS sends PAG\_RSP to MSC. 9. MSC sends SETUP to BSS. 10. BSS sends CALL\_CONF to MSC. 11. MSC sends CHAN\_MOD\_MODIFY to BSS. 12. BSS responds with CHAN\_MOD\_MODIFY\_ACK.
+
+**Figure 5: Signalling information required for the prioritisation at mobile terminating call establishment with fast call set-up and without called-party pre-emption**
+
+**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level.
+
+**PAGING:** Modified paging command including the priority level to be applied.
+
+**PAG\_REQ:** Modified paging message including the related priority level.
+
+**Initial RACH CHAN\_REQ:** Standard message. A new establishment cause shall be provided to indicate the requirement for the direct assignment of a TCH (very early assignment) for the support of fast call set-up procedure.
+
+**IMM\_ASS:** Standard message.
+
+**SABM (PAG\_RSP):** Standard message.
+
+**UA (PAG\_RSP):** Standard message.
+
+**PAG\_RSP:** Standard message.
+
+For fast call set-up the network shall immediately send a SETUP message to the Mobile Station. Authentication and ciphering may not be performed or delayed by the network.]
+
+**SETUP:** Modified message with an indication of the priority level.
+
+**CALL\_CONF:** Standard message.
+
+**ASS\_REQ:** This standard message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from incoming set-up message. In addition, the eMLPP level is included as explicit information.
+
+**CHAN\_MOD\_MODIFY:** Standard message.
+
+**CHAN\_MOD\_MODIFY\_ACK:** Standard message.
+
+![Sequence diagram showing signalling information for called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is: 1. MSC sends SETUP (prec.) req. ind. to BSS. 2. BSS sends SETUP to MS. 3. MS sends CALL_CONF to BSS. 4. BSS sends CALL_CONF to MSC. 5. MS sends ALERT to BSS. 6. BSS sends ALERT to MSC. 7. MS sends HOLD to BSS. 8. BSS sends HOLD to MSC. 9. MSC sends HOLD_ACK to BSS. 10. BSS sends HOLD_ACK to MS. 11. MS sends CONNECT to BSS. 12. BSS sends CONNECT to MSC. 13. MSC sends CONN_ACK to BSS. 14. BSS sends CONN_ACK to MS.](8ed7f57cc317f6574bec781d01ae6ad2_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BSS
+    participant MSC
+    Note right of MSC: SETUP (prec.)  
+req. ind.
+    MSC->>BSS: SETUP
+    BSS->>MS: SETUP
+    MS->>BSS: CALL_CONF
+    BSS->>MSC: CALL_CONF
+    MS->>BSS: ALERT
+    BSS->>MSC: ALERT
+    MS->>BSS: HOLD
+    BSS->>MSC: HOLD
+    MSC->>BSS: HOLD_ACK
+    BSS->>MS: HOLD_ACK
+    MS->>BSS: CONNECT
+    BSS->>MSC: CONNECT
+    MSC->>BSS: CONN_ACK
+    BSS->>MS: CONN_ACK
+  
+```
+
+Sequence diagram showing signalling information for called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is: 1. MSC sends SETUP (prec.) req. ind. to BSS. 2. BSS sends SETUP to MS. 3. MS sends CALL\_CONF to BSS. 4. BSS sends CALL\_CONF to MSC. 5. MS sends ALERT to BSS. 6. BSS sends ALERT to MSC. 7. MS sends HOLD to BSS. 8. BSS sends HOLD to MSC. 9. MSC sends HOLD\_ACK to BSS. 10. BSS sends HOLD\_ACK to MS. 11. MS sends CONNECT to BSS. 12. BSS sends CONNECT to MSC. 13. MSC sends CONN\_ACK to BSS. 14. BSS sends CONN\_ACK to MS.
+
+**Figure 6: Signalling information required for the called-party pre-emption in case of an existing telephony call and subscription for HOLD**
+
+Call Waiting should always be subscribed together with eMLPP. If not, no called party pre-emption is possible for point-to-point calls.
+
+**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level.
+
+**SETUP:** Modified SETUP message with an indication of the priority level.
+
+**CALL\_CONF:** Standard message with cause user busy.
+
+On reception of the SETUP message a compatible Mobile Station decides on called party pre-emption. If called party pre-emption applies, the Mobile Station shall automatically accept the waiting call and put the other call on hold.
+
+A non compatible Mobile Station shall not be harmed by the priority information and shall perform Call Waiting functions as normal.
+
+**ALERT:** Standard message. ALERTING may be omitted in case of called party pre-emption.
+
+**HOLD:** Standard message.
+
+**HOLD\_ACK:** Standard message.
+
+**CONNECT:** Standard message.
+
+**CONN\_ACK:** Standard message.
+
+NOTE: In case of an incoming data call a mode modify procedure has to be performed which is not included in figure 6.
+
+![Sequence diagram showing signalling information for called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is: 1. An external SETUP (prec.) req. ind. message is received by the MSC from the right. 2. The MSC sends a SETUP message to the BSS. 3. The BSS sends a CALL_CONF message to the MS. 4. The BSS sends an ALERT message to the MSC. 5. The BSS sends a RELEASE_COM message to the MSC. 6. The BSS sends a CONNECT message to the MSC. 7. The MSC sends a CONN_ACK message to the BSS. 8. The BSS sends a response message (indicated by a left-pointing arrow) to the MS.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant BSS
+    participant MSC
+    Note right of MSC: SETUP (prec.) req. ind.
+    MSC->>BSS: SETUP
+    BSS->>MS: CALL_CONF
+    BSS->>MSC: ALERT
+    BSS->>MSC: RELEASE_COM
+    BSS->>MSC: CONNECT
+    MSC->>BSS: CONN_ACK
+    BSS-->>MS: 
+  
+```
+
+Sequence diagram showing signalling information for called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is: 1. An external SETUP (prec.) req. ind. message is received by the MSC from the right. 2. The MSC sends a SETUP message to the BSS. 3. The BSS sends a CALL\_CONF message to the MS. 4. The BSS sends an ALERT message to the MSC. 5. The BSS sends a RELEASE\_COM message to the MSC. 6. The BSS sends a CONNECT message to the MSC. 7. The MSC sends a CONN\_ACK message to the BSS. 8. The BSS sends a response message (indicated by a left-pointing arrow) to the MS.
+
+**Figure 7: Signalling information required for the called-party pre-emption in case of point-to-point data calls or no subscription for HOLD**
+
+Call Waiting should always be subscribed together with eMLPP. If not, no called party pre-emption is possible for point-to-point calls.
+
+**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level.
+
+**SETUP:** Modified SETUP message with an indication of the priority level.
+
+**CALL\_CONF:** Standard message with cause user busy.
+
+On reception of the SETUP message a compatible Mobile Station decides on called party pre-emption. If called party pre-emption applies, the Mobile Station shall automatically accept the waiting call and clear the existing data call.
+
+A non compatible Mobile Station shall not be harmed by the priority information and shall perform Call Waiting functions as normal.
+
+**ALERT:** Standard message. ALERTING may be omitted in case of called party pre-emption.
+
+**RELEASE\_COM:** Standard message which shall be send immediately after the ALERT with a new cause for called party pre-emption.
+
+**CONNECT:** Standard message.
+
+**CONN\_ACK:** Standard message.
+
+## 11.7 Overview of call independent signalling
+
+### 11.7.1 Registration
+
+At the beginning of registration subscription, provision of the supplementary service and sufficiency of registration information has to be checked.
+
+The default priority level has to be registered in the network.
+
+When the mobile subscriber registers eMLPP, the network shall attempt to register the service. The network will return notification of acceptance of the request. This notification will include the default priority level.
+
+If the system cannot accept a registration request, the network sends a notification that eMLPP registration was not successful to the served mobile subscriber.
+
+The information flow for registration of eMLPP is shown in figure 8.
+
+![Sequence diagram for Figure 8: Registration of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends a 'Register eMLPP' message to the MSC. The MSC sends a 'Register eMLPP' message to the VLR. The VLR sends a 'Register eMLPP' message to the HLR. The HLR sends an 'Acknowledge' message back to the VLR. The VLR sends an 'Acknowledge' message back to the MSC. The MSC sends an 'Acknowledge' message back to the MS.](d3b5eac55166fc428a223bba5c46961b_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    MS->>MSC: Register eMLPP
+    MSC->>VLR: Register eMLPP
+    VLR->>HLR: Register eMLPP
+    HLR-->>VLR: Acknowledge
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Acknowledge
+```
+
+Sequence diagram for Figure 8: Registration of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends a 'Register eMLPP' message to the MSC. The MSC sends a 'Register eMLPP' message to the VLR. The VLR sends a 'Register eMLPP' message to the HLR. The HLR sends an 'Acknowledge' message back to the VLR. The VLR sends an 'Acknowledge' message back to the MSC. The MSC sends an 'Acknowledge' message back to the MS.
+
+Figure 8: Registration of eMLPP
+
+### 11.7.2 Interrogation
+
+The mobile subscriber can request the status of the supplementary service, the maximum and default priority levels and be informed if the service is provided to him/her and on the actual maximum and default priority levels. This procedure is illustrated in figure 9.
+
+![Sequence diagram for Figure 9: Interrogation of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends a 'Interrogate eMLPP' message to the MSC. The MSC sends a 'Interrogate eMLPP' message to the VLR. The VLR sends an 'Acknowledge' message back to the MSC. The MSC sends an 'Acknowledge' message back to the MS. The HLR lifeline is present but not used in this sequence.](4412857e90dfaa9a3df8836bcbde534b_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    MS->>MSC: Interrogate eMLPP
+    MSC->>VLR: Interrogate eMLPP
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Acknowledge
+```
+
+Sequence diagram for Figure 9: Interrogation of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends a 'Interrogate eMLPP' message to the MSC. The MSC sends a 'Interrogate eMLPP' message to the VLR. The VLR sends an 'Acknowledge' message back to the MSC. The MSC sends an 'Acknowledge' message back to the MS. The HLR lifeline is present but not used in this sequence.
+
+Figure 9: Interrogation of eMLPP
+

marked/Rel-18/23_series/23101/raw.md

@@ -0,0 +1,406 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Universal Mobile Telecommunications System (UMTS) architecture (Release 18)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo features the letters '3GPP' in a stylized, bold, black font. The '3' is on the left, 'G' is in the center, 'P' is on the right, and 'P' is slightly behind the 'G'. Below the 'G' and 'P' is a red signal icon consisting of three curved lines of increasing height.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+# **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                      |           |
+|------------------------------------------------------|-----------|
+| Foreword .....                                       | 4         |
+| Introduction .....                                   | 4         |
+| 1 Scope.....                                         | 5         |
+| 2 References.....                                    | 5         |
+| 3 Definitions, symbols and abbreviations.....        | 5         |
+| 3.1 Definitions.....                                 | 5         |
+| 3.2 Symbols.....                                     | 5         |
+| 3.3 Abbreviations .....                              | 5         |
+| 4 General .....                                      | 6         |
+| 5 Domains in UMTS.....                               | 6         |
+| 5.1 Domain split.....                                | 7         |
+| 5.2 User equipment Domain.....                       | 7         |
+| 5.2.1 Mobile equipment Domain.....                   | 8         |
+| 5.2.2 USIM Domain .....                              | 8         |
+| 5.3 Infrastructure Domain .....                      | 8         |
+| 5.3.1 Access Network Domain.....                     | 8         |
+| 5.3.2 Core Network Domain .....                      | 9         |
+| 5.3.2.1 Serving Network Domain .....                 | 9         |
+| 5.3.2.2 Home Network Domain.....                     | 9         |
+| 5.3.2.3 Transit Network Domain .....                 | 9         |
+| 6 Functional Communication between UMTS domains..... | 9         |
+| 6.1 Transport stratum .....                          | 11        |
+| 6.2 Access Stratum.....                              | 12        |
+| 6.3 Serving Stratum.....                             | 12        |
+| 6.4 Home Stratum .....                               | 12        |
+| 6.5 Application Stratum .....                        | 13        |
+| <b>Annex A (informative): Change History.....</b>    | <b>14</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+UMTS will support a wide range of applications with different quality of service profiles. At present many of these applications are not possible to predict. Also the usage of the different applications are difficult to predict i.e. it is not possible to optimise UMTS to only one set of applications. One conclusion of this is that UMTS must be built in such a way that it is flexible and possible to evolve so it will have a long technical lifetime. Therefore a modular approach is recommended when defining the network parts of UMTS. This is in line with the recommendation from GMM. In this context a module represents a part of a UMTS network i.e. one or several physical network nodes that together implements some functionality. The modular approach should also make UMTS possible to implement efficiently in different environments.
+
+# --- 1 Scope
+
+This TS defines the basic physical and functional separation of UMTS. The contents of this specification is limited to those features that are common to all UMTS networks independent of their origin. It identifies and names the reference points and functional groupings appearing at this level.
+
+# --- 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] ETSI SR 001 687: ETSI Global Multimedia Mobility (GMM) report.
+- [2] UMTS 22.01: "Universal Mobile Telecommunications System (UMTS): Service aspects; Service principles".
+- [3] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+Terms introduced in this document:
+
+**Domain:** The highest-level group of physical entities. Reference points are defined between domains.
+
+**Stratum:** Grouping of protocols related to one aspect of the services provided by one or several domains.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|      |                                                                                         |
+|------|-----------------------------------------------------------------------------------------|
+| Cu   | Reference point between USIM and ME                                                     |
+| Iu   | Reference point between Access and Serving Network domains                              |
+| Uu   | Reference point between User Equipment and Infrastructure domains, UMTS radio interface |
+| [Yu] | Reference point between Serving and Transit Network domains                             |
+| [Zu] | Reference point between Serving and Home Network domains                                |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                                  |
+|------|--------------------------------------------------|
+| USIM | User Services Identity Module                    |
+| ME   | Mobile Equipment                                 |
+| MT   | Mobile Termination                               |
+| MExE | Mobile Station Application Execution Environment |
+
+TE Terminal Equipment
+
+# 4 General
+
+The general UMTS architecture is modelled, at a high level, from both physical and functional viewpoints. The physical aspects are modelled using the domain concept and the functional aspects are modelled using the strata concept.
+
+The two views are introduced separately and then the mapping between the views is discussed.
+
+This specification shows at a basic level physical and functional separations to allow a UMTS network to fit within the context of the IMT-2000 family of networks. It does not attempt to develop aspects of a UMTS network that are highly specific to that implementation.
+
+# 5 Domains in UMTS
+
+The following figure shows the basic domains in UMTS as described in this clause.
+
+![Diagram of UMTS domains and reference points. The diagram shows a horizontal sequence of components: USIM, Mobile Equipment (ME), Access Network (AN), Serving Network (SN), and Transit Network (TN). Reference points are marked between them: Cu (between USIM and ME), Uu (between ME and AN), Iu (between AN and SN), [Yu] (between SN and TN), and [Zu] (between SN and a Home Network Domain above the SN). The diagram is divided into three horizontal layers: 'User Equipment Domain' (containing USIM and ME), 'Infrastructure Domain' (containing AN, SN, and TN), and 'Core Network Domain' (containing SN and TN). Vertical dashed lines separate the domains, and horizontal double-headed arrows indicate the scope of each domain.](47e8c2042061e08a14e012472e9fdbaa_img.jpg)
+
+Diagram of UMTS domains and reference points. The diagram shows a horizontal sequence of components: USIM, Mobile Equipment (ME), Access Network (AN), Serving Network (SN), and Transit Network (TN). Reference points are marked between them: Cu (between USIM and ME), Uu (between ME and AN), Iu (between AN and SN), [Yu] (between SN and TN), and [Zu] (between SN and a Home Network Domain above the SN). The diagram is divided into three horizontal layers: 'User Equipment Domain' (containing USIM and ME), 'Infrastructure Domain' (containing AN, SN, and TN), and 'Core Network Domain' (containing SN and TN). Vertical dashed lines separate the domains, and horizontal double-headed arrows indicate the scope of each domain.
+
+NOTE: The domains identified in the figure will generally result from an evolution of existing network infrastructures. The core network domain may result from evolutions of existing network infrastructures, e.g., a GSM infrastructure, a N-ISDN infrastructure, a B-ISDN infrastructure or a PDN infrastructure. The evolution of these infrastructures may be performed via the use of IWUs, hidden within the domains shown in the figure.
+
+**Figure 1:UMTS domains and reference points**
+
+- Cu = Reference point between USIM and ME
+- Iu = Reference point between Access and Serving Network domains
+- Uu = Reference point between User Equipment and Infrastructure domains, UMTS radio interface
+- [Yu] = Reference point between Serving and Transit Network domains
+- [Zu] = Reference point between Serving and Home Network domains
+
+## 5.1 Domain split
+
+A basic architectural split is between the user equipment (terminals) and the infrastructure. This results in two domains: the **User Equipment Domain** and the **Infrastructure domain**.
+
+User equipment is the equipment used by the user to access UMTS services. User equipment has a radio interface to the infrastructure. The infrastructure consists of the physical nodes which perform the various functions required to terminate the radio interface and to support the telecommunication services requirements of the users. The infrastructure is a shared resource that provides services to all authorised end users within its coverage area.
+
+The reference point between the user equipment domain and the infrastructure domain is termed the "Uu" reference point (UMTS radio interface).
+
+NOTE: The description assumes an access interface based on UTRA. However, the physical and functional separation described in this document is general and is applicable also if other access technologies are used.
+
+## 5.2 User equipment Domain
+
+This domain encompasses a variety of equipment types with different levels of functionality. These equipment types are referred to as user equipment (terminals), and they may also be compatible with one or more existing access (fixed or radio) interfaces e.g. dual mode UMTS-GSM user equipment. The user equipment may include a removable smart card that may be used in different user equipment types. The user equipment is further sub-divided in to the **Mobile Equipment Domain (ME)** and the **User Services Identity Module Domain (USIM)**.
+
+The reference point between the ME and the USIM is termed the "Cu" reference point.
+
+For the purpose of UMTS Cellular networks the following definition applies:
+
+User Equipment is a device allowing a user access to network services. For the purpose of 3GPP specifications the interface between the UE and the network is the radio interface. A User Equipment can be subdivided into a number of domains, the domains being separated by reference points. Currently defined domains are the USIM and ME Domains. The ME Domain can further be subdivided into several components showing the connectivity between multiple functional groups. These groups can be implemented in one or more hardware devices. An example of such a connectivity is the TE - MT interface. Further, an occurrence of User Equipment is an MS for GSM as defined in TS 24.002 [3].
+
+The figure below shows the Functional Model for the User Equipment, UE.
+
+![Functional Model for the User Equipment diagram](4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg)
+
+The diagram illustrates the functional model for User Equipment (UE). A large outer rectangle is labeled "UE" in its bottom right corner. Inside this rectangle, on the left, is a box labeled "USIM". On the right, there is a box labeled "ME". Inside the "ME" box, there are two stacked boxes: the top one is labeled "MT" and the bottom one is labeled "TE".
+
+Functional Model for the User Equipment diagram
+
+**Figure 1a: Functional Model for the User Equipment**
+
+The 07- and 27-series refer to physical instances of this Functional Model. The figure below shows an example of a physical configuration as it could be used in these specifications. The boxes, in this figure, refer to physical elements. The names within brackets are just provided to map the functional blocks from the figure above onto physical elements.
+
+![Figure 1b: Example of physical configuration. A diagram showing a Handset (MT) containing a UICC (USIM) connected to a PC (TE) via a reference point R.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The diagram illustrates a physical configuration. A large rectangle labeled 'Handset (MT)' contains a smaller rectangle labeled 'UICC (USIM)'. A line extends from the right side of the 'Handset (MT)' rectangle to a smaller rectangle labeled 'PC (TE)'. This line is labeled with the letter 'R', representing a reference point.
+
+Figure 1b: Example of physical configuration. A diagram showing a Handset (MT) containing a UICC (USIM) connected to a PC (TE) via a reference point R.
+
+Figure 1b: Example of physical configuration
+
+### 5.2.1 Mobile equipment Domain
+
+The Mobile Equipment performs radio transmission and contains applications. The mobile equipment may be further sub-divided into several entities, e.g. the one which performs the radio transmission and related functions, **Mobile Termination**, MT, and the one which contains the end-to-end application or (e.g. laptop connected to a mobile phone), **Terminal Equipment**, TE. This separation is used in the description of the functional communication in figure 3 but no reference point is defined in this specification.
+
+### 5.2.2 USIM Domain
+
+The USIM contains data and procedures which unambiguously and securely identify itself. These functions are typically embedded in a stand alone smart card. This device is associated to a given user, and as such allows to identify this user regardless of the ME he uses.
+
+## 5.3 Infrastructure Domain
+
+The Infrastructure domain is further split into the **Access Network Domain**, which is characterised by being in direct contact with the User Equipment and the **Core Network Domain**. This split is intended to simplify/assist the process of de-coupling access related functionality from non-access related functionality and is in line with the modular principle adopted for the UMTS.
+
+The Access Network Domain comprises roughly the functions specific to the access technique, while the functions in the Core network domain may potentially be used with information flows using any access technique. This split allows for different approaches for the Core Network Domain, each approach specifying distinct types of Core Networks connectable to the Access Network Domain, as well as different access techniques, each type of Access Network connectable to the Core Network Domain.
+
+The reference point between the access network domain and the core network domain is termed the "Iu" reference point.
+
+NOTE: The split into the User Equipment Domain, the Access Network Domain and the Core Network Domain is consistent with the GMM report.
+
+### 5.3.1 Access Network Domain
+
+The Access Network Domain consists of the physical entities which manage the resources of the access network and provides the user with a mechanism to access the core network domain.
+
+Additional reference points within the access domain may be identified in other specifications.
+
+### 5.3.2 Core Network Domain
+
+The Core Network Domain consists of the physical entities which provide support for the network features and telecommunication services. The support provided includes functionality such as the management of user location information, control of network features and services, the transfer (switching and transmission) mechanisms for signalling and for user generated information.
+
+[Note: Much more could/should be written about the reference points between the core network and other networks].
+
+The core network domain is sub-divided into the **Serving Network Domain**, the **Home Network Domain** and the **Transit Network Domain**.
+
+The reference point between the serving network domain and the home network domain is termed the [Zu] reference point.
+
+The reference point between the serving network domain and the transit network domain is termed the [Yu] reference point.
+
+Additional sub-divisions and reference points within the core network domain may be identified in other specifications.
+
+#### 5.3.2.1 Serving Network Domain
+
+The serving network domain is the part of the core network domain to which the access network domain that provides the user's access is connected. It represents the core network functions that are local to the user's access point and thus their location changes when the user moves. The serving network domain is responsible for routing calls and transport user data/information from source to destination. It has the ability to interact with the home domain to cater for user specific data/services and with the transit domain for non user specific data/services purposes.
+
+#### 5.3.2.2 Home Network Domain
+
+The home network domain represents the core network functions that are conducted at a permanent location regardless of the location of the user's access point.
+
+The USIM is related by subscription to the home network domain. The home network domain therefore contains at least permanently user specific data and is responsible for management of subscription information. It may also handle home specific services, potentially not offered by the serving network domain.
+
+NOTE: Most of the functionality associated with the service provider role according to the UMTS role model (ref UMTS 22.01), is normally contained within the home network domain.
+
+#### 5.3.2.3 Transit Network Domain
+
+The transit network domain is the core network part located on the communication path between the serving network domain and the remote party. If, for a given call, the remote party is located inside the same network as the originating UE, then no particular instance of the transit domain is activated.
+
+# --- 6 Functional Communication between UMTS domains
+
+The following strata have been identified within UMTS:
+
+- Application stratum;
+- Home stratum;
+- Serving stratum and
+- Transport stratum
+
+The following figures show the interactions between the UMTS domains. Two figures are used to reflect the path diversion between the flows exchanged between serving and home domains on one side and between serving and transit on the other side.
+
+Figure 2 below shows the interactions between the USIM, MT/ME, Access Network, Serving Network and Home Network domains. Figure 3 shows the interactions between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party. The Home Stratum only involves domains from figure 2, the Application Stratum only involves domains from figure 3. The Serving and Transport Strata involve domains from figures 2 and 3, so part of them are duplicated in the two figures
+
+The direct flows between non-contiguous domains (i.e. between domains non directly interconnected) are transparently transported across all the domains and interfaces located on the communication path between these end domains. E.g. the USIM-Home Network flows are transparently transported through USIM-MT, MT-Access Network, Access Network-Serving Network and Serving Network-Home Network interfaces, and relayed without interpretation by MT, Access Network and Serving Network domains.
+
+The dotted lines indicates that the protocol used is not specific to UMTS, in some cases different protocols are possible. However, to provide easy roaming capabilities, it is desirable to agree upon the protocols used. The definition of these protocols is outside the scope of the UMTS specifications.
+
+![Figure 2: Functional flows between the USIM, MT/ME, Access Network, Serving Network and Home Network domains. The diagram illustrates three strata: Home Stratum, Serving Stratum, and Transport Stratum. The Home Stratum includes USIM-HN, USIM-MT, MT-SN, and SN-HN interfaces. The Serving Stratum includes USIM-MT and MT-SN interfaces. The Transport Stratum includes MT-AN and AN-SN interfaces, with the Access Stratum nested within it. Vertical lines represent the domains: USIM, MT/ME, Access Network Domain, Serving Network Domain, and Home Network Domain.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg)
+
+The diagram shows functional flows across three strata, represented by horizontal double-headed arrows, and five domains, represented by vertical lines.
+
+- Home Stratum:** The top stratum, containing flows:
+  - USIM - HN (between USIM and Home Network Domain)
+  - USIM - MT (between USIM and MT/ME)
+  - MT - SN (between MT/ME and Serving Network Domain)
+  - SN - HN (between Serving Network Domain and Home Network Domain)
+- Serving Stratum:** The middle stratum, containing flows:
+  - USIM - MT (between USIM and MT/ME)
+  - MT - SN (between MT/ME and Serving Network Domain)
+- Transport Stratum:** The bottom stratum, containing flows:
+  - MT - AN (between MT/ME and Access Network Domain)
+  - AN - SN (between Access Network Domain and Serving Network Domain)
+- Access Stratum:** A sub-stratum nested within the Transport Stratum, also containing MT - AN and AN - SN flows.
+
+Vertical lines from left to right represent the domains: **USIM**, **MT/ME**, **Access Network Domain**, **Serving Network Domain**, and **Home Network Domain**. Dotted lines extend from the USIM and Home Network Domain interfaces.
+
+Figure 2: Functional flows between the USIM, MT/ME, Access Network, Serving Network and Home Network domains. The diagram illustrates three strata: Home Stratum, Serving Stratum, and Transport Stratum. The Home Stratum includes USIM-HN, USIM-MT, MT-SN, and SN-HN interfaces. The Serving Stratum includes USIM-MT and MT-SN interfaces. The Transport Stratum includes MT-AN and AN-SN interfaces, with the Access Stratum nested within it. Vertical lines represent the domains: USIM, MT/ME, Access Network Domain, Serving Network Domain, and Home Network Domain.
+
+**Figure 2: Functional flows between the USIM, MT/ME, Access Network, Serving Network and Home Network domains**
+
+![Figure 3: Functional flow between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party. The diagram shows three stacked strata: Application Stratum, 'Serving Stratum', and 'Transport Stratum'. The 'Transport Stratum' contains the 'Access Stratum'. Arrows indicate data flow between TE, MT, AN, SN, and Remote Party across these strata.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+The diagram illustrates the functional flow of data across different network strata. It consists of three main horizontal layers (strata) stacked vertically, enclosed within a dashed vertical boundary on the right representing the 'Remote Party'.
+
+- Application Stratum (Top):** Contains the 'Application' data. A dashed horizontal line spans its width.
+- "Serving Stratum" (Middle):** Contains two segments: 'TE - MT' (between the Mobile Equipment Domain and Mobile Terminal) and 'MT - SN' (between the Mobile Terminal and the Serving Network Domain). A solid horizontal line spans this stratum from the left boundary to the 'Serving Network Domain' boundary.
+- "Transport Stratum" (Bottom):** Contains the 'Access Stratum' (a nested oval) and segments 'MT - AN' (between MT and Access Network) and 'AN - SN' (between Access Network and Serving Network). A dashed horizontal line spans the entire width of this stratum.
+
+Vertical lines on the left and right define the boundaries of the domains: **TE** (Mobile Equipment Domain), **MT** (Mobile Terminal), **Access Network Domain**, **Serving Network Domain**, **Transit Network Domain**, and **Remote Party**.
+
+Figure 3: Functional flow between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party. The diagram shows three stacked strata: Application Stratum, 'Serving Stratum', and 'Transport Stratum'. The 'Transport Stratum' contains the 'Access Stratum'. Arrows indicate data flow between TE, MT, AN, SN, and Remote Party across these strata.
+
+**Figure 3: Functional flow between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party**
+
+The "Remote Party" represents the remote end entity (user or machine) and is included in the figure to show the end-to-end character of the communication, the specification of the remote party is outside the scope of the UMTS specifications.
+
+## 6.1 Transport stratum
+
+This stratum supports the transport of user data and network control signalling from other strata through UMTS. The transport stratum includes consideration of the physical transmission format used for transmission and also:
+
+- mechanisms for error correction and recovery;
+- mechanisms to encrypt data over the radio interface and in the infrastructure part if required;
+- mechanisms for adaptation of data to use the supported physical format (if required); and
+- mechanisms to "transcode" data to make efficient use of, e.g., the radio interface (if required).
+
+It may also include resource allocation and routing local to the different interfaces.
+
+The **Access Stratum**, which is specific to UMTS, is the part of the transport stratum located between the edge node of the serving core network domain and the MT ('MT-Access Network' and 'Access Network-Serving Network' arrows in figure 2 and 3).
+
+## 6.2 Access Stratum
+
+This is the functional groupings consisting of the parts in the infrastructure and in the user equipment and the protocols between these parts being specific to the access technique (i.e. the way the specific physical media between the User Equipment and the Infrastructure is used to carry information). The access stratum provides services related to the transmission of data over the radio interface and the management of the radio interface to the other parts of UMTS.
+
+The access stratum includes the following protocols:
+
+- Mobile Termination - Access Network  
+This protocol supports transfer of detailed radio-related information to co-ordinate the use of radio resources between the MT and the access network.
+- Access Network - Serving Network  
+This protocol supports the access from the serving network to the resources provided by the access network. It is independent of the specific radio structure of the access network.
+
+## 6.3 Serving Stratum
+
+This stratum consists of protocols and functions to route and transmit data/information, user or network generated, from source to destination. The source and destination may be within the same or different networks. Functions related to telecommunication services and are located in this stratum.
+
+The serving stratum includes the following protocols:
+
+- USIM - Mobile Termination  
+This protocol supports access to subscriber-specific information for support of functions in the user equipment domain.
+- Mobile Termination - Serving Network  
+This protocol supports access from the MT to the services provided by the serving network domain.
+- Terminal Equipment- Mobile Termination  
+This protocol support exchange of control information between the TE and the MT.
+
+## 6.4 Home Stratum
+
+This stratum contains the protocols and functions related to the handling and storage of subscription data and possibly home network specific services. It also includes functions to allow domains other than the home network domain to act on behalf of the home network. Functions related to subscription data management, customer care, including billing and charging, mobility management and authentication are located in this stratum.
+
+The home stratum includes the following protocols:
+
+- USIM - Home Network  
+This protocol supports co-ordination of subscriber-specific information between the USIM and the home network.
+- USIM - MT  
+This protocol provides the MT with access to user specific data and resources necessary to perform actions on behalf of the home network.
+- MT - Serving Network  
+This protocol supports user specific data exchanges between the MT and the Serving Network.
+- Serving Network - Home Network  
+This protocol provides the serving network with access to home network data and resources necessary to perform its actions on behalf of the home network, e.g., to support the users communications, services and features (including VHE).
+
+## 6.5 Application Stratum
+
+This stratum represents the application process itself, provided to the end-user. It includes end-to-end protocols and functions which make use of services provided by the home, serving and transport strata and infrastructure to support services and/or value added services.
+
+The functions and protocols within the application stratum may adhere to GSM/UMTS standards such as MExE or may be outside the scope of the UMTS standards. However, the definition of the services provided by the other strata, and the interfaces to them, is within the scope of the standards
+
+End-to-end functions are applications which are consumed by users at the edge of/outside the overall network. The applications may be accessed by authenticated users who are authorised to access such applications. The users may access the applications by using any of the variety of available user equipment.
+
+# Annex A (informative): Change History
+
+| Change history |        |          |    |     |                                |        |        |
+|----------------|--------|----------|----|-----|--------------------------------|--------|--------|
+| Date           | TSG #  | TSG Doc. | CR | Rev | Subject/Comment                | Old    | New    |
+| 2004-12        | SA#26  |          |    |     | Created version 6.0.0          | 5.0.1  | 6.0.0  |
+| 2007-06        | SP-36  | -        | -  | -   | Update to Rel-7 version (MCC)  | 6.0.0  | 7.0.0  |
+| 2008-12        | SP-42  | -        | -  | -   | Update to Rel-8 version (MCC)  | 7.0.0  | 8.0.0  |
+| 2009-12        | SP-46  | -        | -  | -   | Update to Rel-9 version (MCC)  | 8.0.0  | 9.0.0  |
+| 2011-03        | SP-51  | -        | -  | -   | Update to Rel-10 version (MCC) | 9.0.0  | 10.0.0 |
+| 2012-09        | -      | -        | -  | -   | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 |
+| 2014-09        | SP-65  | -        | -  | -   | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 |
+| 2015-12        | -      | -        | -  | -   | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 |
+| 2017-03        | -      | -        | -  | -   | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 |
+| 2018-06        | SP-80  | -        | -  | -   | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 |
+| 2020-07        | SP-88E | -        | -  | -   | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 |
+| 2022-03        | SP-95E | -        | -  | -   | Update to Rel-17 version (MCC) | 16.0.0 | 17.0.0 |
+| 2024-03        | -      | -        | -  | -   | Update to Rel-18 version (MCC) | 17.0.0 | 18.0.0 |

marked/Rel-18/23_series/23108/raw.md

@@ -0,0 +1,1369 @@
+
+
+# 3GPP TS 23.108 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile radio interface layer 3 specification, Core network protocols; Stage 2 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                              |           |
+|------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                               | 4         |
+| Introduction .....                                                           | 4         |
+| 1 Scope.....                                                                 | 5         |
+| 1.1 Scope of the Technical Specification .....                               | 5         |
+| 1.2 Application to the interface structures .....                            | 5         |
+| 1.3 Structure of layer 3 procedures .....                                    | 5         |
+| 1.4 Test procedures .....                                                    | 5         |
+| 1.5 Use of logical channels .....                                            | 6         |
+| 1.6 Overview of control procedures.....                                      | 6         |
+| 1.6.1 List of procedures .....                                               | 6         |
+| 1.7 Applicability of implementations.....                                    | 8         |
+| 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS)..... | 8         |
+| 1.7.2 General Packet Radio Service (GPRS).....                               | 8         |
+| 2 References.....                                                            | 9         |
+| 2.1 Definitions and abbreviations.....                                       | 11        |
+| 2.1.1 Random values .....                                                    | 11        |
+| 2.2.2 Vocabulary .....                                                       | 11        |
+| 3 Radio Resource management procedures .....                                 | 12        |
+| 4 Elementary procedures for Mobility Management .....                        | 12        |
+| 5 Elementary procedures for circuit-switched Call Control .....              | 12        |
+| 6 Support for packet services.....                                           | 12        |
+| 7 Examples of structured procedures .....                                    | 12        |
+| 7.1 General .....                                                            | 12        |
+| 7.1.1 Paging request .....                                                   | 13        |
+| 7.1.2 Immediate assignment.....                                              | 13        |
+| 7.1.3 Service request and contention resolution.....                         | 13        |
+| 7.1.4 Authentication .....                                                   | 14        |
+| 7.1.5 Ciphering mode setting.....                                            | 14        |
+| 7.1.6 Transaction phase .....                                                | 14        |
+| 7.1.6.1 Channel mode modify.....                                             | 14        |
+| 7.1.7 Channel release.....                                                   | 15        |
+| 7.2 Abnormal cases .....                                                     | 15        |
+| 7.3 Selected examples .....                                                  | 15        |
+| 7.3.1 Location updating.....                                                 | 16        |
+| 7.3.2 Mobile originating call establishment .....                            | 17        |
+| 7.3.3 Mobile terminating call establishment .....                            | 20        |
+| 7.3.4 Call clearing.....                                                     | 22        |
+| 7.3.5 DTMF protocol control .....                                            | 24        |
+| 7.3.6 Handover .....                                                         | 24        |
+| 7.3.7 In-call modification .....                                             | 26        |
+| 7.3.8 Call re-establishment.....                                             | 26        |
+| 7.3.9 Network initiated mobile originating call \$(CCBS)\$.....              | 27        |
+| 8 Handling of unknown, unforeseen, and erroneous protocol data .....         | 31        |
+| 9 Message functional definitions and contents .....                          | 32        |
+| 10 General message format and information elements coding.....               | 32        |
+| 11 List of system parameters .....                                           | 32        |
+| <b>Annex A (informative): Change History.....</b>                            | <b>33</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document specifies the procedures used at the radio interface core network protocols within the 3<sup>rd</sup> generation mobile telecommunications system and the digital cellular telecommunications 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 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The present document includes references to features which are not part of the Phase 2+ Release 96 of the GSM Technical specifications. All subclauses which were changed as a result of these features contain a marker (see table below) relevant to the particular feature.
+
+# 1 Scope
+
+The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002 [15]) for Call Control (CC), Mobility Management (MM), and Session Management (SM).
+
+When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of this standard.
+
+These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPP TS 44.003 [16].
+
+The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007 [20].
+
+## 1.1 Scope of the Technical Specification
+
+The procedures currently described in the present document are for the call control of circuit-switched connections, session management for GPRS services, mobility management and radio resource management for circuit-switched and GPRS services.
+
+3GPP TS 24.010 [21] contains functional procedures for support of supplementary services.
+
+3GPP TS 24.011 [22] contains functional procedures for support of point-to-point short message services.
+
+3GPP TS 24.012 [23] contains functional description of short message - cell broadcast.
+
+3GPP TS 44.060 [76] contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels.
+
+3GPP TS 44.018 [80] contains the procedures for the RR protocol.
+
+3GPP TS 24.008 [81] contains the procedures for the CN protocols.
+
+3GPP TS 44.071 [23a] contains functional descriptions and procedures for support of location services.
+
+NOTE: "layer 3" includes the functions and protocols described in this Technical Specification. The terms "data link layer" and "layer 2" are used interchangeably to refer to the layer immediately below layer 3.
+
+## 1.2 Application to the interface structures
+
+The layer 3 procedures apply to the interface structures defined in 3GPP TS 44.003 [16]. They use the functions and services provided by layer 2 defined in 3GPP TS 44.005 [18] and 3GPP TS 44.006 [19]. 3GPP TS 24.007 [20] gives the general description of layer 3 including procedures, messages format and error handling.
+
+## 1.3 Structure of layer 3 procedures
+
+A building block method is used to describe the layer 3 procedures.
+
+The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer.
+
+Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences.
+
+## 1.4 Test procedures
+
+Test procedures of the GSM radio interface signalling are described in 3GPP TS 51.010 [39] and 3GPP TS 51.02x series.
+
+## 1.5 Use of logical channels
+
+The logical control channels are defined in 3GPP TS 45.002 [32]. In the following those control channels are considered which carry signalling information or specific types of user packet information:
+
+- i) Broadcast Control CHannel (BCCH): downlink only, used to broadcast Cell specific information;
+- ii) Synchronization CHannel (SCH): downlink only, used to broadcast synchronization and BSS identification information;
+- iii) Paging CHannel (PCH): downlink only, used to send page requests to Mobile Stations (MSs);
+- iv) Random Access CHannel (RACH): uplink only, used to request a Dedicated Control CHannel;
+- v) Access Grant CHannel (AGCH): downlink only, used to allocate a Dedicated Control CHannel;
+- vi) Standalone Dedicated Control CHannel (SDCCH): bi-directional;
+- vii) Fast Associated Control CHannel (FACCH): bi-directional, associated with a Traffic CHannel;
+- viii) Slow Associated Control CHannel (SACCH): bi-directional, associated with a SDCCH or a Traffic CHannel;
+- ix) Cell Broadcast CHannel (CBCH): downlink only used for general (not point to point) short message information.
+- x) Notification CHannel (NCH): downlink only, used to notify mobile stations of VBS (Voice Broadcast Service) calls or VGCS (Voice Group Call Service) calls.
+
+Two service access points are defined on signalling layer 2 which are discriminated by their Service Access Point Identifiers (SAPI) (see 3GPP TS 44.006 [19]):
+
+- i) SAPI 0: supports the transfer of signalling information including user-user information;
+- ii) SAPI 3: supports the transfer of user short messages.
+
+Layer 3 selects the service access point, the logical control channel and the mode of operation of layer 2 (acknowledged, unacknowledged or random access, see 3GPP TS 44.005 [18] and 3GPP TS 44.006 [19]) as required for each individual message.
+
+## 1.6 Overview of control procedures
+
+### 1.6.1 List of procedures
+
+The following procedures are specified in the Technical Specification:
+
+- a) Clause 4 specifies elementary procedures for Mobility Management:
+  - mobility management common procedures (subclause 4.3);
+    - TMSI reallocation procedure (subclause 4.3.1);
+    - authentication procedure (subclause 4.3.2);
+    - identification procedure (subclause 4.3.3);
+    - IMSI detach procedure (subclause 4.3.4);
+    - abort procedure (subclause 4.3.5);
+    - MM information procedure (subclause 4.3.6);
+  - mobility management specific procedures (subclause 4.4);
+    - location updating procedure (subclause 4.4.1);
+    - periodic updating (subclause 4.4.2);
+
+- IMSI attach procedure (subclause 4.4.3);
+  - generic location updating procedure (subclause 4.4);
+  - connection management sublayer service provision;
+  - mobility management connection establishment (subclause 4.5.1);
+  - mobility management connection information transfer phase (subclause 4.5.2);
+  - mobility management connection release (subclause 4.5.3);
+  - GPRS specific mobility management procedures (subclause 4.7);
+    - GPRS attach procedure (subclause 4.7.3);
+    - GPRS detach procedure (subclause 4.7.4);
+    - GPRS routing area updating procedure (subclause 4.7.5);
+  - GPRS common mobility management procedures (subclause 4.7);
+    - GPRS P-TMSI reallocation procedure (subclause 4.7.6);
+    - GPRS authentication and ciphering procedure (subclause 4.7.7);
+    - GPRS identification procedure (subclause 4.7.8);
+    - GPRS information procedure (subclause 4.7.12);
+- b) Clause 5 specifies elementary procedures for circuit switched Call Control comprising the following elementary procedures:
+- mobile originating call establishment (subclause 5.2.1);
+  - mobile terminating call establishment (subclause 5.2.2);
+  - signalling procedures during the active state (subclause 5.3);
+    - user notification procedure (subclause 5.3.1);
+    - call rearrangements (subclause 5.3.2);
+    - DTMF protocol control procedure (subclause 5.5.7);
+    - in-call modification (subclause 5.3.4);
+  - call clearing initiated by the mobile station (subclause 5.4.3);
+  - call clearing initiated by the network (subclause 5.4.4);
+  - miscellaneous procedures;
+    - in-band tones and announcements (subclause 5.5.1);
+    - status enquiry procedure (subclause 5.5.3);
+    - call re-establishment procedure (subclause 5.5.4);
+- d) Clause 6 specifies elementary procedures for session management:
+- GPRS session management procedures (subclause 6.1);
+    - PDP context activation (subclause 6.1.1);
+    - PDP context modification (subclause 6.1.2);
+    - PDP context deactivation (subclause 6.1.3);
+    - anonymous PDP context activation (subclause 6.1.4);
+
+- anonymous PDP context deactivation (subclause 6.1.5).
+
+The elementary procedures can be combined to form structured procedures. Examples of such structured procedures are given in clause 7. This part of the Technical Specification is only provided for guidance to assist implementations.
+
+Clause 8 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol.
+
+## 1.7 Applicability of implementations
+
+The applicability of procedures of this technical specification for the mobile station is dependent on the services and functions which are to be supported by a mobile station.
+
+### 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS)
+
+For mobile stations supporting the Voice Group Call Service or the Voice Broadcast Service, it is explicitly mentioned throughout this technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave.
+
+For VGCS and VBS, the following possible mobile station implementations exist:
+
+- support of listening to voice broadcast calls (VBS listening);
+- support of originating a voice broadcast call (VBS originating);
+- support of listening to voice group calls (VGCS listening);
+- support of talking in voice group calls (VGCS talking. This always includes the implementation for VGCS listening);
+- support of originating a voice group call (VGCS originating. This always includes the implementation for VGCS talking).
+
+Apart from the explicitly mentioned combinations, all possible combinations are optional and supported by this technical specification.
+
+The related terms are used in this technical specification, if information on these implementation options is required.
+
+### 1.7.2 General Packet Radio Service (GPRS)
+
+For mobile stations supporting the General Packet Radio Service (GPRS), it is explicitly mentioned throughout the technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave.
+
+A GPRS MS may operate in one of the following MS operation modes, see 3GPP TS 23.060 [74]:
+
+- MS operation mode A;
+- MS operation mode B; or
+- MS operation mode C.
+
+The MS operation mode depends on the services that the MS is attached to, i.e., only GPRS or both GPRS and non-GPRS services, and upon the MS's capabilities to operate GPRS and other GSM services simultaneously. Mobile stations that are capable to operate GPRS services are referred to as GPRS MSs.
+
+NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS class-A MS, GPRS class-B MS, and GPRS class-C MS.
+
+It should be noted that it is possible that for a GPRS MS, the GMM procedures currently described in the ETS do not support combinations of VGCS, VBS and GPRS. The possible interactions are not studied yet.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] Void.
+- [2] Void.
+- [2a] 3GPP TR 21.905 "Vocabulary for 3GPP Specifications"
+- [3] Void.
+- [4] Void.
+- [5] Void.
+- [6] Void.
+- [7] Void.
+- [8] Void.
+- [9] Void.
+- [10] Void.
+- [11] Void.
+- [12] Void.
+- [12a] Void.
+- [13] Void.
+- [14] Void.
+- [15] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) access reference configuration".
+- [16] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities".
+- [17] Void.
+- [18] 3GPP TS 44.005: "Data Link (DL) layer; General aspects".
+- [19] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification".
+- [20] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
+- [21] 3GPP TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General aspects".
+- [22] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
+
+- [23] 3GPP TS 24.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".
+- [23a] 3GPP TS 44.071: "Location Services (LCS); Mobile radio interface layer 3 specification".
+- [23b] Void.
+- [24] Void.
+- [25] Void.
+- [26] Void.
+- [27] Void.
+- [28] Void.
+- [29] Void.
+- [30] Void.
+- [31] Void.
+- [32] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
+- [33] Void.
+- [34] Void.
+- [35] Void.
+- [36] Void.
+- [37] Void.
+- [38] Void.
+- [39] 3GPP TS 51.010: "Mobile Station (MS) conformance specification".
+- [40] Void.
+- [41] Void.
+- [42] Void.
+- [43] Void.
+- [44] Void.
+- [45] Void.
+- [46] Void.
+- [47] Void.
+- [48] Void.
+- [49] Void.
+- [50] Void.
+- [51] Void.
+- [52] Void.
+- [53] Void.
+- [54] Void.
+- [55] Void.
+
+- [56] Void.
+- [57] Void.
+- [58] Void.
+- [59] Void.
+- [60] Void.
+- [61] Void.
+- [62] Void.
+- [63] Void.
+- [64] Void.
+- [65] Void.
+- [66] Void.
+- [67] Void.
+- [68] Void.
+- [69] Void.
+- [70] Void.
+- [71] Void.
+- [72] Void.
+- [73] Void.
+- [74] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2".
+- [75] Void.
+- [76] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".
+- [77] Void.
+- [78] Void.
+- [79] Void.
+- [80] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
+- [81] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
+
+## 2.1 Definitions and abbreviations
+
+For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [2a] apply.
+
+### 2.1.1 Random values
+
+For the RR protocol see 3GPP TS 44.018 and for the CN protocols see 3GPP TS 24.008 [81].
+
+### 2.2.2 Vocabulary
+
+For the RR protocol see 3GPP TS 44.018 [80] and for the CN protocols see 3GPP TS 24.008 [81].
+
+# 3 Radio Resource management procedures
+
+See 3GPP TS 44.018 [80].
+
+# 4 Elementary procedures for Mobility Management
+
+See 3GPP TS 24.008 [81].
+
+# 5 Elementary procedures for circuit-switched Call Control
+
+See 3GPP TS 24.008 [81].
+
+# 6 Support for packet services
+
+See 3GPP TS 24.008 [81].
+
+# 7 Examples of structured procedures
+
+Clause 7 is informative.
+
+## 7.1 General
+
+Clause 7 contains examples of how the network may group together the elementary procedures (i.e. the procedures defined in clauses 3 to 5) in order to provide normal service.
+
+The layer 3 signalling at the radio interface may be divided into so-called structured procedures which consist of specific combinations of elementary procedures. In subclause 7.3, selected examples of structured procedures are described. A structured procedure consists of (not necessarily all) components shown in figure 7.1. These components are characterized by the purpose of their use in structured procedures and their message flow in the following subclauses 7.1.1 to 7.1.7.
+
+![Diagram showing components of structured procedures grouped into RR connection establishment and RR connection release.](e787e02d9214556476d95941bda1d350_img.jpg)
+
+|                                                                                                                                                                                                                                                              |                                                                                                                                                                    |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| +-<br>     Paging request<br>     Immediate assignment<br>+-<br>     Service request and<br>     Contention resolution<br>+-<br>     Authentication<br>+-<br>     Ciphering mode setting<br>+-<br>     Transaction phase<br>+-<br>     Channel release<br>+- | +-<br>     RR connection<br>     establishment<br>+-<br>+-<br>+-<br>+-<br>+-<br>+-<br>+-<br>+-<br>+-<br>+-<br>+-<br>+-<br>     RR connection<br>     release<br>+- |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Diagram showing components of structured procedures grouped into RR connection establishment and RR connection release.
+
+Figure 7.1/3GPP TS 23.108: Components of structured procedures
+
+### 7.1.1 Paging request
+
+The paging procedure is used to locate a mobile station to which a connection shall be established.
+
+Upon receipt of a PAGING REQUEST message the addressed mobile station initiates the immediate assignment procedure.
+
+![Sequence diagram for Figure 7.2/3GPP TS 23.108: Paging request. It shows a 'Mobile Station' and a 'Network'. A 'PAGING REQUEST' message is sent from the Network to the Mobile Station, indicated by a dashed line with an arrow pointing left.](ddc7460821484f1ae2835c67955c554c_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Network
+    participant MS as Mobile Station
+    Note right of Network: PAGING REQUEST
+    Network-->>MS: 
+  
+```
+
+Sequence diagram for Figure 7.2/3GPP TS 23.108: Paging request. It shows a 'Mobile Station' and a 'Network'. A 'PAGING REQUEST' message is sent from the Network to the Mobile Station, indicated by a dashed line with an arrow pointing left.
+
+**Figure 7.2/3GPP TS 23.108: Paging request**
+
+### 7.1.2 Immediate assignment
+
+The immediate assignment procedure is always initiated by the mobile station. It may be triggered by a paging request or by a mobile originating service request.
+
+The mobile station sends a CHANNEL REQUEST message on the Random Access Channel. The network responds with an IMMEDIATE ASSIGNMENT message which causes the mobile station to seize the indicated dedicated channel.
+
+![Sequence diagram for Figure 7.3/3GPP TS 23.108: Immediate assignment. It shows a 'Mobile Station' and a 'Network'. A 'CHANNEL REQUEST' message is sent from the Mobile Station to the Network (dashed line with arrow pointing right). The Network responds with an 'IMMEDIATE ASSIGNMENT' message (dashed line with arrow pointing left).](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant Network
+    Note left of MS: CHANNEL REQUEST
+    MS-->>Network: 
+    Note right of Network: IMMEDIATE ASSIGNMENT
+    Network-->>MS: 
+  
+```
+
+Sequence diagram for Figure 7.3/3GPP TS 23.108: Immediate assignment. It shows a 'Mobile Station' and a 'Network'. A 'CHANNEL REQUEST' message is sent from the Mobile Station to the Network (dashed line with arrow pointing right). The Network responds with an 'IMMEDIATE ASSIGNMENT' message (dashed line with arrow pointing left).
+
+**Figure 7.3/3GPP TS 23.108: Immediate assignment**
+
+### 7.1.3 Service request and contention resolution
+
+The initial service request message (a PAGING RESPONSE, LOCATION UPDATING REQUEST, IMSI DETACH, CM SERVICE REQUEST, or CM RE-ESTABLISHMENT REQUEST message) is sent by the mobile station to the network piggy-backed in the L2 SABM frames establishing the main signalling link. Its purpose is:
+
+- to provide non-confidential information relevant to the service requested for the RR and MM sublayer in the network;
+- in particular to identify the user in the network without jeopardising the confidentiality of the user's identity; this is achieved by using as mobile identity the TMSI, which was never before transmitted un-encrypted over the radio interface;
+- to allow for contention resolution;
+- optionally, in the CM SERVICE REQUEST message to inform the network of the priority level associated with the call.
+
+Contention resolution provides a resolution process when more than one MS try to seize a channel allocated during the immediate assignment procedure (because they happened to use the same random reference at the same time during random access). This is achieved by the network including in a L2 UA frame the same information field as that one received in the L2 SABM frame to which the UA frame responds. By comparing the two information fields the MS can verify whether it was the originator of the L2 establishment, because the service request contains the mobile identity.
+
+![Sequence diagram for Figure 7.4/3GPP TS 23.108: Service request and contention resolution. It shows a 'Mobile Station' and a 'Network'. A 'SABM(service request)' message is sent from the Mobile Station to the Network (dashed line with arrow pointing right). The Network responds with a 'UA(service request)' message (dashed line with arrow pointing left).](3597664ae86918629ceabb89ae71669d_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant Network
+    Note left of MS: SABM(service request)
+    MS-->>Network: 
+    Note right of Network: UA(service request)
+    Network-->>MS: 
+  
+```
+
+Sequence diagram for Figure 7.4/3GPP TS 23.108: Service request and contention resolution. It shows a 'Mobile Station' and a 'Network'. A 'SABM(service request)' message is sent from the Mobile Station to the Network (dashed line with arrow pointing right). The Network responds with a 'UA(service request)' message (dashed line with arrow pointing left).
+
+**Figure 7.4/3GPP TS 23.108: Service request and contention resolution**
+
+### 7.1.4 Authentication
+
+The purpose of authentication is to validate the identity provided by the mobile station. It is initiated by the network. The authentication procedure also provides the mobile station with information from which a new ciphering key can be derived. The network decides whether or not to use authentication. This may depend on the context.
+
+![Sequence diagram for Authentication between Mobile Station and Network.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Mobile Station
+    participant Network
+    Note right of Network: AUTHentication REquest
+    Network->>Mobile Station: AUTHentication REquest
+    Note left of Mobile Station: AUTHentication RESponse
+    Mobile Station-->>Network: AUTHentication RESponse
+  
+```
+
+Sequence diagram for Authentication between Mobile Station and Network.
+
+Figure 7.5/3GPP TS 23.108: Authentication
+
+### 7.1.5 Ciphering mode setting
+
+Ciphering mode setting is initiated by the network. Its purpose is to instruct the mobile station whether or not to use ciphering and which algorithm to use.
+
+Where ciphering is used, this procedure synchronizes the start of ciphering at the mobile station and in the network.
+
+![Sequence diagram for Ciphering mode setting between Mobile Station and Network.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Mobile Station
+    participant Network
+    Note right of Network: CIPHer MODE CoMmanD
+    Network->>Mobile Station: CIPHer MODE CoMmanD
+    Note left of Mobile Station: CIPHer MODE COMplete
+    Mobile Station-->>Network: CIPHer MODE COMplete
+  
+```
+
+Sequence diagram for Ciphering mode setting between Mobile Station and Network.
+
+Figure 7.6/3GPP TS 23.108: Ciphering mode setting
+
+### 7.1.6 Transaction phase
+
+A variety of elementary procedures described in clauses 3 to 5 may be performed during the transaction phase. In this subclause, only the channel mode modify procedure is characterized.
+
+#### 7.1.6.1 Channel mode modify
+
+The channel mode modify procedure may be used when a traffic channel has been assigned e.g.:
+
+- during the in-call modification procedure in order that the channel mode of the TCH be changed to that one requested by call control;
+- during call establishment with very early assignment in order that the channel mode of the TCH be changed from signalling only to the mode requested by call control;
+- during the active phase of a data call in order that the speed of the data transmission be changed.
+
+The channel mode modify procedure is initiated by the network sending a CHANNEL MODE MODIFY message and completed by the mobile station changing the mode of the TCH and sending back a CHANNEL MODE MODIFY ACKNOWLEDGE message.
+
+![Sequence diagram for Channel mode modify between Mobile Station and Network.](c934b5f282326e30bbb158147ececa85_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Mobile Station
+    participant Network
+    Note right of Network: CHANNEL MODE MODIFY
+    Network->>Mobile Station: CHANNEL MODE MODIFY
+    Note left of Mobile Station: CHANNEL MODE MODIFY ACKNOWLEDGE
+    Mobile Station-->>Network: CHANNEL MODE MODIFY ACKNOWLEDGE
+  
+```
+
+Sequence diagram for Channel mode modify between Mobile Station and Network.
+
+Figure 7.7/3GPP TS 23.108: Channel mode change
+
+### 7.1.7 Channel release
+
+Once the transaction phase has been completed, the channel is released by the channel release procedure. The data link layer is released explicitly as described in 3GPP TS 44.006 [19]. After the channel release is completed, the radio resources which were in use may be reallocated by the network.
+
+![Diagram of Channel release procedure](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg)
+
+The diagram illustrates the channel release procedure between a Mobile Station and a Network. At the top, 'Mobile Station' is on the left and 'Network' is on the right. Below them, the text 'CHANNEL RELEASE' is centered. A dashed horizontal line with a left-pointing arrow is positioned below 'CHANNEL RELEASE', indicating the release message flow from the Network to the Mobile Station.
+
+Diagram of Channel release procedure
+
+**Figure 7.8/3GPP TS 23.108 Channel release**
+
+## 7.2 Abnormal cases
+
+Abnormal cases are not described in the examples of clause 7. They may arise from:
+
+- a) failure at a lower layer (e.g. loss of radio connection);
+- b) failure of an elementary procedure;
+- c) errors in an elementary procedure.
+
+## 7.3 Selected examples
+
+The following examples are considered:
+
+- location updating;
+- mobile originating call establishment;
+  - a) without OACSU (early assignment);
+  - b) with OACSU;
+  - c) with very early assignment;
+- mobile terminating call establishment;
+  - a) without OACSU (early assignment);
+  - b) with OACSU;
+- call clearing:
+  - a) network initiated;
+  - b) mobile initiated;
+- DTMF protocol control.
+- handover:
+  - a) between finely synchronized cells;
+  - b) between non-synchronized cells;
+  - c) handover failure, where reconnection of the old channel is possible;
+- in-call modification;
+- call re-establishment;
+- network initiated MO call, e.g. CCBS Recall \$(CCBS)\$:
+  - a) assignment before A party alerting;
+
+- b) assignment before B party alerting;
+- c) assignment after A and B party alerting.
+
+### 7.3.1 Location updating
+
+The location updating procedure is always initiated by the mobile station e.g. when it finds itself in a different location area from the one in which it was registered before. The cases where the procedure is triggered are described in clause 4.
+
+The procedure is shown in figure 7.9/3GPP TS 23.108. The network may decide whether to allocate a new TMSI during location updating, and this option is reflected in this example.
+
+The mobile station initiates immediate assignment, service request using the LOCATION UPDATING REQUEST message, and contention resolution.
+
+The network requires authentication (this again is an option).
+
+As the network intends to allocate a new TMSI, it should activate ciphering. The network includes the new TMSI in the LOCATION UPDATING ACCEPT message (it could also use the explicit TMSI reallocation procedure, see clause 4). The mobile station sends a TMSI REALLOCATION COMPLETE message to the network to acknowledge the receipt of the new TMSI. Upon receipt of the TMSI REALLOCATION COMPLETE message the network initiates the channel release if no further transactions are scheduled.
+
+![Sequence diagram of the location updating procedure between a Mobile Station and a Network.](f57a881fcbcaf494a7dedc4f61224991_img.jpg)
+
+```
+sequenceDiagram
+    participant MS as Mobile Station
+    participant NW as Network
+    Note right of NW: RR connection establishment (MO)
+    MS->>NW: CHANNEL REQUEST
+    NW-->>MS: IMMEDIATE ASSIGNMENT
+    Note right of NW: Service request
+    MS->>NW: LOCATION UPDATING REQUEST
+    Note right of NW: Authentication
+    NW-->>MS: AUTHENTICATION REQUEST
+    MS-->>NW: AUTHENTICATION RESPONSE
+    Note right of NW: Ciphering mode setting
+    NW-->>MS: CIPHER MODE COMMAND
+    MS-->>NW: CIPHER MODE COMPLETE
+    Note right of NW: RR connection release
+    NW-->>MS: LOCATION UPDATING ACCEPT
+    MS-->>NW: TMSI REALLOCATION COMPLETE
+    NW-->>MS: CHANNEL RELEASE
+```
+
+The diagram illustrates the sequence of messages for a successful location updating procedure. It starts with the Mobile Station sending a CHANNEL REQUEST to the Network. The Network responds with an IMMEDIATE ASSIGNMENT. Next, the Mobile Station sends a LOCATION UPDATING REQUEST, which is labeled as a 'Service request' on the Network side. The Network then initiates authentication with an AUTHENTICATION REQUEST, to which the Mobile Station responds with an AUTHENTICATION RESPONSE. The Network then sends a CIPHER MODE COMMAND, labeled as 'Ciphering mode setting' on the Network side, and the Mobile Station responds with a CIPHER MODE COMPLETE. The Network then sends a LOCATION UPDATING ACCEPT, and the Mobile Station responds with a TMSI REALLOCATION COMPLETE. Finally, the Network sends a CHANNEL RELEASE, which is labeled as 'RR connection release' on the Network side. The Mobile Station and Network lifelines are shown with vertical dashed lines and horizontal dashed arrows for message exchanges. Vertical tick marks on the lifelines indicate the sequence of events.
+
+Sequence diagram of the location updating procedure between a Mobile Station and a Network.
+
+Figure 7.9/3GPP TS 23.108: Location updating: successful case
+
+### 7.3.2 Mobile originating call establishment
+
+The mobile station initiates immediate assignment, service request using the CM SERVICE REQUEST message, and contention resolution. The network may initiate authentication and may start the ciphering mode setting.
+
+After sending the CIPHERING MODE COMPLETE message, the mobile station initiates call establishment by sending the SETUP message to the network. The network answers with a CALL PROCEEDING message.
+
+#### a) Non-OACSU option (early assignment):
+
+With this option the network allocates a traffic channel to the mobile station before it initiates call establishment in the fixed network.
+
+If call queuing is applied, it may cause variable delay in the traffic channel assignment.
+
+When user alerting has been initiated at the called side, an ALERTING message is sent to the mobile station. The network may optionally instruct the MS to attach the user connection at this stage of the call, by means of the progress indicator information element set to the value #1 or #8 (if the ringing tone will be sent by the remote end) in the ALERTING message. In that case, an alerting ringing tone has to be generated by the network.
+
+NOTE: The speech codec is transparent for supervisory tones.
+
+A CONNECT message and its acknowledgement CONNECT ACKNOWLEDGE complete the call establishment when the called party has answered.
+
+The mobile originating call setup with early assignment is shown in figure 7.10a/3GPP TS 23.108.
+
+#### b) OACSU option (late assignment):
+
+The network determines when the traffic channel is to be assigned. The assignment may be performed at any time after call establishment has been initiated in the fixed network. In the following the case is considered where the network will only allocate a traffic channel after the called party has answered the call (late assignment).
+
+As in a) an ALERTING message is sent to the mobile station when user alerting has been initiated at the called side. If the ringing tone is needed, it has to be generated locally at the mobile station as no traffic channel is allocated. When the called party has answered, the network will initiate the channel assignment procedure in order to allocate a traffic channel to the mobile station. If call queuing is applied, it may cause variable delay in the traffic channel assignment. Once the channel assignment has been completed the network will send a CONNECT message to the mobile station. The MS attaches then the user connection. The CONNECT ACKNOWLEDGE message will complete the call setup.
+
+The mobile originating call setup with late assignment is shown in figure 7.10b/3GPP TS 23.108.
+
+#### c) Very early assignment:
+
+The network assigns the traffic channel at the earliest possible moment, i.e. in the immediate assignment procedure. The mode of the traffic channel is changed from signalling only to the mode necessary for the call by means of the channel mode change procedure. An appropriate moment for that change is after the network has sent the CALL PROCEEDING message, when the call is established towards the called user.
+
+With this option, call queuing is never applied.
+
+The further establishment of the call is as in a).
+
+The mobile originating call setup with very early assignment is shown in figure 7.10c/3GPP TS 23.108.
+
+![Sequence diagram of mobile originating call establishment without OACSU (early assignment).](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+The diagram illustrates the sequence of messages for a mobile originating call establishment without OACSU (early assignment) between a Mobile Station and a Network. The sequence is as follows:
+
+- The Mobile Station sends a **CHANNEL REQUEST** to the Network. The Network responds with an **IMMEDIATE ASSIGNMENT**. This step is labeled **RR connection establishment (MO)**.
+- The Mobile Station sends a **CM SERVICE REQUEST** to the Network. This step is labeled **Service request**.
+- The Network sends an **AUTHENTICATION REQUEST** to the Mobile Station. The Mobile Station responds with an **AUTHENTICATION RESPONSE**. This step is labeled **Authentication**.
+- The Network sends a **CIPHER MODE COMMAND** to the Mobile Station. The Mobile Station responds with a **CIPHER MODE COMPLETE**. This step is labeled **Ciphering mode setting**.
+- The Mobile Station sends a **SETUP** message to the Network. The Network responds with a **CALL PROCEEDING**. This step is labeled **Call initiation**.
+- The Network sends an **ASSIGNMENT COMMAND** to the Mobile Station. The Mobile Station responds with an **ASSIGNMENT COMPLETE**. This step is labeled **Assignment of a traffic channel**.
+- The Network sends an **ALERTING** message to the Mobile Station. This step is labeled **User alerting**.
+- The Mobile Station sends a **CONNECT** message to the Network. The Network responds with a **CONNECT ACKNOWLEDGE**. This step is labeled **Call accepted**.
+
+Sequence diagram of mobile originating call establishment without OACSU (early assignment).
+
+Figure 7.10a/3GPP TS 23.108: Mobile originating call establishment without OACSU (early assignment)
+
+![Sequence diagram showing Mobile Station to Network interactions for call establishment. Steps include: CHANNEL REQUEST / IMMEDIATE ASSIGNMENT (RR connection establishment (MO)), CM SERVICE REQUEST (Service indication), AUTHENTICATION REQUEST / AUTHENTICATION RESPONSE (Authentication), CIPHER MODE COMMAND / CIPHER MODE COMPLETE (Ciphering mode setting), SETUP / CALL PROCEEDING (Call initiation), ALERTING (User alerting), ASSIGNMENT COMMAND / ASSIGNMENT COMPLETE (Assignment of a traffic channel), CONNECT / CONNECT ACKNOWLEDGE (Call accepted).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+The diagram illustrates the sequence of messages for a mobile originating call establishment with OACSU (late assignment). The interaction is between a Mobile Station (MS) and a Network (NW).
+
+- RR connection establishment (MO):** MS sends CHANNEL REQUEST to NW; NW responds with IMMEDIATE ASSIGNMENT.
+- Service indication:** MS sends CM SERVICE REQUEST to NW.
+- Authentication:** NW sends AUTHENTICATION REQUEST to MS; MS responds with AUTHENTICATION RESPONSE.
+- Ciphering mode setting:** NW sends CIPHER MODE COMMAND to MS; MS responds with CIPHER MODE COMPLETE.
+- Call initiation:** MS sends SETUP to NW; NW responds with CALL PROCEEDING.
+- User alerting:** NW sends ALERTING to MS.
+- Assignment of a traffic channel:** NW sends ASSIGNMENT COMMAND to MS; MS responds with ASSIGNMENT COMPLETE.
+- Call accepted:** MS sends CONNECT to NW; NW responds with CONNECT ACKNOWLEDGE.
+
+Sequence diagram showing Mobile Station to Network interactions for call establishment. Steps include: CHANNEL REQUEST / IMMEDIATE ASSIGNMENT (RR connection establishment (MO)), CM SERVICE REQUEST (Service indication), AUTHENTICATION REQUEST / AUTHENTICATION RESPONSE (Authentication), CIPHER MODE COMMAND / CIPHER MODE COMPLETE (Ciphering mode setting), SETUP / CALL PROCEEDING (Call initiation), ALERTING (User alerting), ASSIGNMENT COMMAND / ASSIGNMENT COMPLETE (Assignment of a traffic channel), CONNECT / CONNECT ACKNOWLEDGE (Call accepted).
+
+Figure 7.10b/3GPP TS 23.108: Mobile originating call establishment with OACSU (late assignment)
+
+![Sequence diagram of mobile originating call establishment with very early assignment. The diagram shows the interaction between a Mobile Station and a Network. The sequence of messages is: 1. CHANNEL REQUEST (MS to Network) - RR connection establishment (MO); 2. IMMEDIATE ASSIGNMENT (TCH) (Network to MS); 3. CM SERVICE REQUEST (MS to Network) - Service request; 4. AUTHentication REQuest (Network to MS) - Authentication; 5. AUTHENTICATION RESPONSE (MS to Network); 6. CIPHER MODE COMMAND (Network to MS) - Ciphering mode setting; 7. CIPher MODE Complete (MS to Network); 8. SETUP (MS to Network) - Call initiation; 9. CALL PROCeeding (Network to MS); 10. CHANNEL MODE MODIFY (Network to MS) - Transmission mode change; 11. CHANNEL MODE MODIFY ACKnowledge (MS to Network); 12. ALERTING (Network to MS) - User alerting; 13. CONNect (MS to Network) - Call accepted; 14. CONNect ACKnowledge (Network to MS).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant Network
+    Note right of Network: RR connection establishment (MO)
+    MS->>Network: CHANNEL REQUEST
+    Network-->>MS: IMMEDIATE ASSIGNMENT (TCH)
+    Note right of Network: Service request
+    MS->>Network: CM SERVICE REQUEST
+    Note right of Network: Authentication
+    Network-->>MS: AUTHentication REQuest
+    MS-->>Network: AUTHENTICATION RESPONSE
+    Note right of Network: Ciphering mode setting
+    Network-->>MS: CIPHER MODE COMMAND
+    MS-->>Network: CIPher MODE Complete
+    Note right of Network: Call initiation
+    MS->>Network: SETUP
+    Network-->>MS: CALL PROCeeding
+    Note right of Network: Transmission mode change
+    Network-->>MS: CHANNEL MODE MODIFY
+    MS-->>Network: CHANNEL MODE MODIFY ACKnowledge
+    Note right of Network: User alerting
+    Network-->>MS: ALERTING
+    Note right of Network: Call accepted
+    MS->>Network: CONNect
+    Network-->>MS: CONNect ACKnowledge
+  
+```
+
+Sequence diagram of mobile originating call establishment with very early assignment. The diagram shows the interaction between a Mobile Station and a Network. The sequence of messages is: 1. CHANNEL REQUEST (MS to Network) - RR connection establishment (MO); 2. IMMEDIATE ASSIGNMENT (TCH) (Network to MS); 3. CM SERVICE REQUEST (MS to Network) - Service request; 4. AUTHentication REQuest (Network to MS) - Authentication; 5. AUTHENTICATION RESPONSE (MS to Network); 6. CIPHER MODE COMMAND (Network to MS) - Ciphering mode setting; 7. CIPher MODE Complete (MS to Network); 8. SETUP (MS to Network) - Call initiation; 9. CALL PROCeeding (Network to MS); 10. CHANNEL MODE MODIFY (Network to MS) - Transmission mode change; 11. CHANNEL MODE MODIFY ACKnowledge (MS to Network); 12. ALERTING (Network to MS) - User alerting; 13. CONNect (MS to Network) - Call accepted; 14. CONNect ACKnowledge (Network to MS).
+
+Figure 7.10c/3GPP TS 23.108: Mobile originating call establishment with very early assignment
+
+### 7.3.3 Mobile terminating call establishment
+
+Mobile terminating call establishment is initiated by the network sending a PAGING REQUEST message (see figure 7.11a/3GPP TS 23.108). Upon receiving this message the mobile station initiates the immediate assignment procedure and responds to the network by sending the PAGING RESPONSE message within a layer 2 SABM frame. The network returns a layer 2 UA frame containing the same information field as was sent in the SABM frame.
+
+Authentication and ciphering are treated by the network in the same way as defined for the mobile originating call establishment (subclause 7.3.2). After ciphering has been started, the network sends a SETUP message to the mobile station. The capability of the mobile station (at that time) to accept the call is confirmed when the mobile station returns a CALL CONFIRMED message to the network.
+
+#### a) Non-OACSU option (early assignment):
+
+With this option the network initiates the assignment of a traffic channel upon receiving the CALL CONFIRMED message.
+
+The signal IE is not included in the SETUP message, therefore user alerting is initiated only after a traffic channel has been allocated. An ALERTING message will be sent to the network.
+
+When the called user answers, the mobile station sends a CONNECT message to the network. Upon receiving the CONNECT message the network completes the through connection of the communication path and sends a CONNECT ACK message to the mobile station.
+
+#### b) OACSU option (late assignment):
+
+In that option, the signalling IE is included in the SETUP message. Consequently, user alerting is initiated as soon as the MS has accepted the call.
+
+The network determines when the traffic channel is to be assigned. The assignment may be performed at any time after user alerting has been initiated. In the following the case is considered where the network will only allocate a traffic channel to the mobile station after having received the CONNECT message sent from the mobile station (see figure 7.11b).
+
+Upon receiving the ASSIGNMENT COMPLETE message from the mobile station, the network completes the through connection of the communication path and sends a CONNECT ACKNOWLEDGE message to the mobile station.
+
+![Sequence diagram showing mobile terminating call establishment without OACSU (early assignment).](73dff6b45b2b9ffd384bab3235f869af_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant NW as Network
+    Note over MS, NW: RR connection establishment (MT)
+    NW->>MS: PAGING REQUEST
+    MS->>NW: CHANNEL REQUEST
+    NW->>MS: IMMEDIATE ASSIGNMENT
+    Note over MS, NW: Service request
+    MS->>NW: PAGING RESPONSE
+    Note over MS, NW: Authentication
+    NW->>MS: AUTHENTICATION REQUEST
+    MS->>NW: AUTHENTICATION RESPONSE
+    Note over MS, NW: Ciphering mode setting
+    NW->>MS: CIPHER MODE COMMAND
+    MS->>NW: CIPHER MODE COMPLETE
+    Note over MS, NW: Call initiation
+    NW->>MS: SETUP
+    MS->>NW: CALL CONFIRMED
+    Note over MS, NW: Assignment of a traffic channel
+    NW->>MS: ASSIGNMENT COMMAND
+    MS->>NW: ASSIGNMENT COMPLETE
+    Note over MS, NW: User alerting information
+    MS->>NW: ALERTING
+    Note over MS, NW: Call accepted
+    MS->>NW: CONNECT
+    NW->>MS: CONNECT ACKNOWLEDGE
+
+```
+
+The sequence diagram illustrates the interaction between a Mobile Station (MS) and a Network (NW) for a mobile terminating call establishment without OACSU (early assignment). The process is divided into several phases: 
+1. **RR connection establishment (MT):** The Network sends a PAGING REQUEST to the MS. The MS responds with a CHANNEL REQUEST, and the Network replies with an IMMEDIATE ASSIGNMENT.
+2. **Service request:** The MS sends a PAGING RESPONSE to the Network.
+3. **Authentication:** The Network sends an AUTHENTICATION REQUEST, and the MS responds with an AUTHENTICATION RESPONSE.
+4. **Ciphering mode setting:** The Network sends a CIPHER MODE COMMAND, and the MS responds with a CIPHER MODE COMPLETE.
+5. **Call initiation:** The Network sends a SETUP message, and the MS responds with a CALL CONFIRMED.
+6. **Assignment of a traffic channel:** The Network sends an ASSIGNMENT COMMAND, and the MS responds with an ASSIGNMENT COMPLETE.
+7. **User alerting information:** The MS sends an ALERTING message to the Network.
+8. **Call accepted:** The MS sends a CONNECT message, and the Network responds with a CONNECT ACKNOWLEDGE.
+
+Sequence diagram showing mobile terminating call establishment without OACSU (early assignment).
+
+**Figure 7.11a/3GPP TS 23.108: Mobile terminating: call establishment without OACSU (early assignment)**
+
+![Sequence diagram showing Mobile Station (MS) and Network (NW) interaction for call establishment with OACSU (late assignment).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant NW as Network
+    Note right of NW: RR connection establishment (MT)
+    NW->>MS: PAGING REQUEST
+    MS-->>NW: CHANNEL REQUEST
+    NW-->>MS: IMMEDIATE ASSIGNMENT
+    Note right of NW: Service request
+    MS->>NW: PAGING RESPONSE
+    Note right of NW: Authentication
+    NW->>MS: AUTHENTICATION REQUEST
+    MS-->>NW: AUTHENTICATION RESPONSE
+    Note right of NW: Ciphering mode setting
+    NW->>MS: CIPHER MODE COMMAND
+    MS-->>NW: CIPHER MODE COMPLETE
+    Note right of NW: Call initiation
+    NW->>MS: SETUP
+    MS-->>NW: CALL CONFIRMED
+    Note right of NW: User alerting information
+    MS->>NW: ALERTING
+    MS->>NW: CONNECT
+    Note right of NW: Assignment of a traffic channel
+    NW->>MS: ASSIGNMENT COMMAND
+    MS-->>NW: ASSIGNMENT COMPLETE
+    MS-->>NW: CONNECT ACKNOWLEDGE
+  
+```
+
+Sequence diagram showing Mobile Station (MS) and Network (NW) interaction for call establishment with OACSU (late assignment).
+
+Figure 7.11b/3GPP TS 23.108: Mobile terminating: call establishment with OACSU (late assignment)
+
+### 7.3.4 Call clearing
+
+- a) initiated by the network
+
+The network initiates the clearing of a call by sending a DISCONNECT message to the mobile station (see also subclause 5.4.4).
+
+Upon receiving the DISCONNECT message from the network the mobile station sends a RELEASE message to the network.
+
+Upon receiving the RELEASE message from the mobile station, the network sends a RELEASE COMPLETE to the mobile station and, if the traffic channel is longer needed (e.g. last activity on the traffic channel), performs the channel release procedure as described in subclause 7.1.7.
+
+Upon receiving the RELEASE COMPLETE message and if the cleared call was the last activity on the traffic channel, the mobile station waits for the release of the channel which is always initiated by the network.
+
+When there exist multiple traffic channels in the Multicall environment the network does not release (i.e. retains) a traffic channel even if the cleared call was the last activity on the traffic channel under the condition as follows;
+
+- a waiting call exists and the mobile station does not indicates to the network which bearer will be used for accepting the waiting call yet; and
+- there exists no retained bearer for the waiting call.
+
+When the mobile station receives SETUP message with Signal IE indicating Call Waiting, which means the network cannot provide any additional traffic channel, then:
+
+- the MS shall not request a new SI value before releasing any other call (that leads to release any other bearers than the retained bearer);
+- If the mobile station indicates the different SI value from the retained bearer after releasing any other calls (that leads to release any other bearer than the retained bearer), the network allocates a new TCH for the call, and releases the retained bearer.
+
+Call clearing initiated by the network is shown in figure 7.12a.
+
+b) initiated by the mobile station:
+
+The mobile station initiates the clearing of a call by sending a DISCONNECT message to the network (see also subclause 5.4.3).
+
+Upon receiving the DISCONNECT message from the mobile station the network sends a RELEASE message to the mobile station.
+
+Upon receiving the RELEASE message from the network, the mobile station sends a RELEASE COMPLETE to the network, which, if the traffic channel is no longer needed (e.g. last activity on the traffic channel), performs the channel release procedure as described in subclause 7.1.6.
+
+When there exist multiple traffic channels in the Multicall environment the network does not release (i.e. retains) a traffic channel even if the cleared call was the last activity on the traffic channel under the condition as follows:
+
+- a waiting call exists and the mobile station does not indicates to the network which bearer will be used for accepting the waiting call yet; and
+- there exists no retained bearer for the waiting call.
+
+When the mobile station receives SETUP message with Signaling IE indicating Call Waiting, which means network cannot provide any additional traffic channel, then:
+
+- The MS shall not request a new SI value before releasing any other call (that leads to release any other bearers than the retained bearer);
+- If the mobile station indicates the different SI value from the retained bearer after releasing any other calls (that leads to release any other bearer than the retained bearer), the network allocates a new TCH for the call, and releases the retained bearer.
+
+Call clearing initiated by the mobile station is shown in figure 7.12b.
+
+![Sequence diagram showing call clearing initiated by the network. The Mobile Station sends DISCONNECT to the Network. The Network responds with RELEASE. The Mobile Station then sends RELEASE COMPLETE. This section is labeled 'Call clearing'. Below this, the Network sends CHANNEL RELEASE to the Mobile Station, labeled 'RR connection release'.](836008eb3303ade9e269f93c04dc0a2e_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant NW as Network
+    Note right of NW: Call clearing
+    MS->>NW: DISCONNECT
+    NW-->>MS: RELEASE
+    MS->>NW: RELEASE COMPLETE
+    Note right of NW: RR connection release
+    NW-->>MS: CHANNEL RELEASE
+
+```
+
+Sequence diagram showing call clearing initiated by the network. The Mobile Station sends DISCONNECT to the Network. The Network responds with RELEASE. The Mobile Station then sends RELEASE COMPLETE. This section is labeled 'Call clearing'. Below this, the Network sends CHANNEL RELEASE to the Mobile Station, labeled 'RR connection release'.
+
+a) Call clearing initiated by the network
+
+Figure 7.12a/3GPP TS 23.108: Call clearing
+
+a)
+
+![Sequence diagram showing call clearing initiated by the Network. The Mobile Station sends DISCONNECT and RELEASE messages to the Network. The Network responds with RELEASE COMPLETE and CHANNEL RELEASE messages. Labels on the right indicate 'Call clearing' and 'RR connection release'.](4b87467ad9642943235f48f7d4b59449_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant NW as Network
+    Note right of NW: Call clearing
+    MS->>NW: DISCONNECT
+    MS->>NW: RELEASE
+    NW-->>MS: RELEASE COMPLETE
+    NW-->>MS: CHANNEL RELEASE
+    Note right of NW: RR connection release
+  
+```
+
+Sequence diagram showing call clearing initiated by the Network. The Mobile Station sends DISCONNECT and RELEASE messages to the Network. The Network responds with RELEASE COMPLETE and CHANNEL RELEASE messages. Labels on the right indicate 'Call clearing' and 'RR connection release'.
+
+b) Call clearing initiated by the MS
+
+Figure 7.12b/3GPP TS 23.108: Call clearing
+
+### 7.3.5 DTMF protocol control
+
+Figure 7.13 shows the structured procedure for DTMF protocol control.
+
+![Sequence diagram showing DTMF protocol control. It starts with an 'active call'. The Mobile Station sends START DTMF to the Network, which responds with START DTMF ACKNOWLEDGE. The Network indicates 'DTMF generation started'. Then, the Mobile Station sends STOP DTMF to the Network, which responds with STOP DTMF ACKNOWLEDGE. The Network indicates 'DTMF generation stopped'. After some time (indicated by dots), the call returns to an 'active call' state.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant NW as Network
+    Note right of NW: active call
+    MS->>NW: START DTMF
+    NW-->>MS: START DTMF ACKNOWLEDGE
+    Note right of NW: DTMF generation started
+    MS->>NW: STOP DTMF
+    NW-->>MS: STOP DTMF ACKNOWLEDGE
+    Note right of NW: DTMF generation stopped
+    Note center: :
+    Note right of NW: active call
+  
+```
+
+Sequence diagram showing DTMF protocol control. It starts with an 'active call'. The Mobile Station sends START DTMF to the Network, which responds with START DTMF ACKNOWLEDGE. The Network indicates 'DTMF generation started'. Then, the Mobile Station sends STOP DTMF to the Network, which responds with STOP DTMF ACKNOWLEDGE. The Network indicates 'DTMF generation stopped'. After some time (indicated by dots), the call returns to an 'active call' state.
+
+Figure 7.13/3GPP TS 23.108: DTMF protocol control
+
+### 7.3.6 Handover
+
+Figure 7.14 shows the structured procedure for handover to a finely synchronized cell, successful case.
+
+Figure 7.15 shows the structured procedure for handover to a non-synchronized cell, successful case.
+
+Figure 7.16 shows the structured procedure for handover failure, and reconnection to the old traffic channel.
+
+![Sequence diagram for handover to a finely synchronized cell. The diagram shows a Mobile Station and a Network. The Network sends an 'RR connection established' message. The Network then initiates a 'handover' procedure, providing 'old channel, old cell' information. The Mobile Station responds with 'HANDOVER COMMAND'. The Network then sends multiple 'HANDOVER ACCESS' messages. Finally, the Mobile Station sends 'HANDOVER COMPLETE'.](26d664119ad25250780f554633444e54_img.jpg)
+
+```
+sequenceDiagram
+    participant MS as Mobile Station
+    participant N as Network
+    Note right of N: RR connection established
+    Note right of N: handover
+    Note right of N: old channel, old cell
+    MS->>N: HANDOVER COMMAND
+    Note right of N: new channel, new cell
+    N->>MS: HANDOVER ACCESS
+    N->>MS: HANDOVER ACCESS
+    N->>MS: HANDOVER ACCESS
+    N->>MS: HANDOVER ACCESS
+    MS->>N: HANDOVER COMPLETE
+```
+
+Sequence diagram for handover to a finely synchronized cell. The diagram shows a Mobile Station and a Network. The Network sends an 'RR connection established' message. The Network then initiates a 'handover' procedure, providing 'old channel, old cell' information. The Mobile Station responds with 'HANDOVER COMMAND'. The Network then sends multiple 'HANDOVER ACCESS' messages. Finally, the Mobile Station sends 'HANDOVER COMPLETE'.
+
+Figure 7.14/3GPP TS 23.108: Handover to a finely synchronized cell, successful case
+
+![Sequence diagram for handover to a non-synchronized cell. The diagram shows a Mobile Station and a Network. The Network sends an 'RR connection established' message. The Network then initiates a 'handover' procedure, providing 'old channel, old cell' information. The Mobile Station responds with 'HANDOVER COMMAND'. The Network then sends 'HANDOVER ACCESS' messages. Between the first and second 'HANDOVER ACCESS' message, there are vertical ellipsis dots. After the second 'HANDOVER ACCESS' message, the Network provides 'new channel, new cell' information. The Mobile Station then sends 'PHYSICAL INFORMATION' and 'HANDOVER COMPLETE'. At the end of the diagram, there are vertical ellipsis dots.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg)
+
+```
+sequenceDiagram
+    participant MS as Mobile Station
+    participant N as Network
+    Note right of N: RR connection established
+    Note right of N: handover
+    Note right of N: old channel, old cell
+    MS->>N: HANDOVER COMMAND
+    Note right of N: new channel, new cell
+    N->>MS: HANDOVER ACCESS
+    Note right of MS: .
+    Note right of MS: .
+    Note right of MS: .
+    N->>MS: HANDOVER ACCESS
+    Note right of N: new channel, new cell
+    MS->>N: PHYSICAL INFORMATION
+    MS->>N: HANDOVER COMPLETE
+    Note right of MS: .
+    Note right of MS: .
+    Note right of MS: .
+```
+
+Sequence diagram for handover to a non-synchronized cell. The diagram shows a Mobile Station and a Network. The Network sends an 'RR connection established' message. The Network then initiates a 'handover' procedure, providing 'old channel, old cell' information. The Mobile Station responds with 'HANDOVER COMMAND'. The Network then sends 'HANDOVER ACCESS' messages. Between the first and second 'HANDOVER ACCESS' message, there are vertical ellipsis dots. After the second 'HANDOVER ACCESS' message, the Network provides 'new channel, new cell' information. The Mobile Station then sends 'PHYSICAL INFORMATION' and 'HANDOVER COMPLETE'. At the end of the diagram, there are vertical ellipsis dots.
+
+Figure 7.15/3GPP TS 23.108: Handover to a non-synchronized cell, successful case
+
+![Sequence diagram for handover failure and reconnection to the old traffic channel between a Mobile Station and a Network.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+This sequence diagram illustrates the interaction between a Mobile Station (MS) and a Network (NW) during a handover failure. The timeline starts with 'RR connection established' on the Network side. The Network then initiates a 'handover' procedure, specifying the 'old channel, old cell'. A 'HANDOVER COMMAND' is sent from the Network to the MS. Upon receiving the command, the MS starts a timer 'T3124'. If 'T3124 expiry or lower layer failure' occurs, the MS sends a 'HANDOVER FAILURE' message back to the Network. In response, the Network reverts to the 'old channel, old cell'. Vertical ellipses indicate additional steps in the process.
+
+Sequence diagram for handover failure and reconnection to the old traffic channel between a Mobile Station and a Network.
+
+Figure 7.16/3GPP TS 23.108: Handover failure, reconnection to the old traffic channel
+
+### 7.3.7 In-call modification
+
+Figure 7.17/3GPP TS 23.108 shows the structured procedure for in-call modification.
+
+![Sequence diagram for in-call modification between a Mobile Station and a Network.](20136850feb70fd71c7d41cdae203ebb_img.jpg)
+
+This sequence diagram shows the procedure for in-call modification. It begins with an 'active call' on the Network side. The MS sends a 'MODIFY' message to the Network. The Network performs an 'in-call modification e.g. from speech to data' and a 'channel mode modify'. Finally, the Network sends a 'MODIFY COMPLETE' message back to the MS, and the call resumes as an 'active call'.
+
+Sequence diagram for in-call modification between a Mobile Station and a Network.
+
+Figure 7.17/3GPP TS 23.108: In-call modification
+
+### 7.3.8 Call re-establishment
+
+Figure 7.18/3GPP TS 23.108 shows the structured procedure for call re-establishment.
+
+![Sequence diagram illustrating Call re-establishment between a Mobile Station and a Network. The process starts with an active call, followed by a radio link failure. The Mobile Station sends a CHANNEL REQUEST, and the Network responds with IMMEDIATE ASSIGNMENT (MO). The Mobile Station then sends a CM RE-ESTABLISHMENT REQUEST, which the Network interprets as a Service request. The Network sends a CIPHER MODE COMMAND, and the Mobile Station responds with CIPHER MODE COMPLETE. The Network then sends an ASSIGNMENT COMMAND, and the Mobile Station responds with ASSIGNMENT COMPLETE, resulting in an active call.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant Network
+    Note right of Network: active call
+    Note right of Network: radio link failure
+    MS->>Network: CHANNEL REQUEST
+    Network-->>MS: IMMEDIATE ASSIGNMENT (MO)
+    MS->>Network: CM RE-ESTABLISHMENT REQUEST
+    Note right of Network: Service request
+    Network-->>MS: CIPHER MODE COMMAND
+    MS-->>Network: CIPHER MODE COMPLETE
+    Note right of Network: Ciphering mode setting
+    Network-->>MS: ASSIGNMENT COMMAND
+    MS-->>Network: ASSIGNMENT COMPLETE
+    Note right of Network: assignment of a traffic channel
+    Note right of Network: active call
+  
+```
+
+Sequence diagram illustrating Call re-establishment between a Mobile Station and a Network. The process starts with an active call, followed by a radio link failure. The Mobile Station sends a CHANNEL REQUEST, and the Network responds with IMMEDIATE ASSIGNMENT (MO). The Mobile Station then sends a CM RE-ESTABLISHMENT REQUEST, which the Network interprets as a Service request. The Network sends a CIPHER MODE COMMAND, and the Mobile Station responds with CIPHER MODE COMPLETE. The Network then sends an ASSIGNMENT COMMAND, and the Mobile Station responds with ASSIGNMENT COMPLETE, resulting in an active call.
+
+Figure 7.18/3GPP TS 23.108: Call re-establishment
+
+### 7.3.9 Network initiated mobile originating call \$(CCBS)\$
+
+Network initiated mobile originating call establishment (which is used, for example, for CCBS Service) is initiated by the network sending a PAGING REQUEST message. Upon receiving this message the mobile station initiates the immediate assignment procedure and responds to the network by sending the PAGING RESPONSE message within a layer 2 SABM frame. The network returns a layer 2 UA frame containing the same information field as was sent in the SABM frame.
+
+Authentication and ciphering are treated by the network in the same way as defined for the mobile originating call establishment (subclause 7.3.2). After ciphering has been started, the network sends a CM SERVICE PROMPT message, indicating that the CM protocol is to be started, to the mobile station. The basic capability of the mobile station to accept any form of recall service is confirmed when the mobile station returns a START CC message to the network.
+
+- a) assignment before A party alerting:
+
+With this option the network allocates a traffic channel to the mobile station before the mobile station alerts its user.
+
+The network responds to the START CC message with a CC-ESTABLISHMENT message. The MS answers with a CC-ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics. The network then initiates traffic channel assignment.
+
+When the traffic channel has been assigned, the network indicates a pending recall by sending a RECALL message.
+
+If the calling user accepts the recall, a SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and initiates call establishment in the fixed network.
+
+When user alerting has been initiated at the called side, an ALERTING message is sent to the mobile station. The network may optionally instruct the MS to attach the user connection at this stage of the call, by means of the progress indicator information element set to the value #1 or #8(if the ringing tone will be sent by the remote end) in the ALERTING message. In that case, an alerting ringing tone has to be generated by the network.
+
+NOTE 1: The speech codec is transparent for supervisory tones.
+
+A CONNECT message and its acknowledgement CONNECT ACKNOWLEDGE complete the call establishment when the called party has answered.
+
+The network initiated mobile originating call establishment with assignment before A part alerting is shown in figure 7.19/3GPP TS 23.108.
+
+#### b) assignment before B party alerting:
+
+With this option the network allocates a traffic channel to the mobile station after the mobile station has alerted its user and after its user has accepted the recall but before the network initiates call establishment in the fixed network.
+
+The network responds to the START CC message with a CC-ESTABLISHMENT message. The MS answers with a CC-ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics.
+
+The network indicates a pending recall by sending a RECALL message. If the calling user accepts the recall, a SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and initiates traffic channel assignment.
+
+When the traffic channel has been assigned, the network initiates call establishment in the fixed network.
+
+When user alerting has been initiated at the called side, an ALERTING message is sent to the mobile station. The network may optionally instruct the MS to attach the user connection at this stage of the call, by means of the progress indicator information element set to the value #1 or #8(if the ringing tone will be sent by the remote end) in the ALERTING message. In that case, an alerting ringing tone has to be generated by the network.
+
+NOTE 2: The speech codec is transparent for supervisory tones.
+
+A CONNECT message and its acknowledgement CONNECT ACKNOWLEDGE complete the call establishment when the called party has answered.
+
+The network initiated mobile originating call establishment with assignment before B party alerting is shown in figure 7.20/3GPP TS 23.108.
+
+#### c) assignment after A and B party alerting
+
+With this option, the network determines when the traffic channel is to be assigned. The assignment may be performed at any time after call establishment has been initiated in the fixed network. In the following, the case is considered where the network will only allocate a traffic channel after the called party has answered the call (late assignment).
+
+The network responds to the START CC message with a CC-ESTABLISHMENT. The MS answers with a CC-ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics.
+
+The network indicates a pending recall by sending a RECALL message. If the calling user accepts the recall, a SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and initiates call establishment in the fixed network.
+
+As in a) and b) an ALERTING message is sent to the mobile station when user alerting has been initiated at the called side. If the ringing tone is needed, it has to be generated locally at the mobile station as no traffic channel is allocated. When the called party has answered, the network will initiate the channel assignment procedure in order to allocate a traffic channel to the mobile station. Once the channel assignment has been completed the network will send a CONNECT message to the mobile station. The MS attaches then the user connection. The CONNECT ACKNOWLEDGE message will complete the call setup.
+
+The network initiated mobile originating call establishment with assignment after A and B party alerting is shown in figure 7.21/3GPP TS 23.108.
+
+![Sequence diagram showing network initiated mobile originating call establishment. The diagram illustrates the interaction between a Mobile Station and a Network, detailing steps such as Paging Request, Authentication, Ciphering mode setting, Service Request, Recall initiation, Assignment of a traffic channel, User notified about recall, Called user alerting information, and Call accepted.](28d75f39a24203712ee907b32cf0bbe5_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Mobile Station
+    participant Network
+    Note right of Network: RR connection establishment (MT)
+    Network->>Mobile Station: PAGING REQUEST
+    Mobile Station-->>Network: CHANNEL REQUEST
+    Network-->>Mobile Station: IMMEDIATE ASSIGNMENT
+    Note right of Network: Authentication
+    Network->>Mobile Station: AUTHENTICATION REQUEST
+    Mobile Station-->>Network: AUTHENTICATION RESPONSE
+    Note right of Network: Ciphering mode setting
+    Network->>Mobile Station: CIPHER MODE COMMAND
+    Mobile Station-->>Network: CIPHER MODE COMPLETE
+    Note right of Network: Service Request
+    Network->>Mobile Station: CM SERVICE PROMPT
+    Mobile Station-->>Network: START CC
+    Note right of Network: Recall initiation
+    Network->>Mobile Station: CC-ESTABLISHMENT
+    Mobile Station-->>Network: CC-ESTABLISHMENT CONFIRMED
+    Note right of Network: Assignment of a traffic channel.
+    Network->>Mobile Station: ASSIGNMENT COMMAND
+    Mobile Station-->>Network: ASSIGNMENT COMPLETE
+    Note right of Network: User notified about recall
+    Network->>Mobile Station: RECALL
+    Mobile Station-->>Network: SETUP
+    Note right of Network: Recall accepted and call initiation
+    Network-->>Mobile Station: CALL PROCEEDING
+    Note right of Network: Called user alerting information
+    Network->>Mobile Station: ALERTING
+    Note right of Network: Call accepted
+    Network-->>Mobile Station: CONNECT
+    Mobile Station-->>Network: CONNECT ACKNOWLEDGE
+  
+```
+
+β
+
+Sequence diagram showing network initiated mobile originating call establishment. The diagram illustrates the interaction between a Mobile Station and a Network, detailing steps such as Paging Request, Authentication, Ciphering mode setting, Service Request, Recall initiation, Assignment of a traffic channel, User notified about recall, Called user alerting information, and Call accepted.
+
+Figure 7.19/3GPP TS 23.108: Network initiated mobile originating call establishment with assignment before A party alerting
+
+![Sequence diagram showing network initiated mobile originating call establishment. The diagram illustrates the interaction between a Mobile Station and a Network, detailing steps such as RR connection establishment, Authentication, Ciphering mode setting, Service Request, Recall initiation, User notification, Assignment of a traffic channel, Called user alerting, and Call acceptance.](dd5771673aececa53d42ece89218299d_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS as Mobile Station
+    participant NW as Network
+    Note over MS,NW: RR connection establishment (MT)
+    NW->>MS: PAGING REQUEST
+    MS->>NW: CHANNEL REQUEST
+    NW->>MS: IMMEDIATE ASSIGNMENT
+    NW->>MS: PAGING RESPONSE
+    Note over MS,NW: Authentication
+    NW->>MS: AUTHENTICATION REQUEST
+    MS->>NW: AUTHENTICATION RESPONSE
+    Note over MS,NW: Ciphering mode setting
+    NW->>MS: CIPHER MODE COMMAND
+    MS->>NW: CIPHER MODE COMPLETE
+    Note over MS,NW: Service Request
+    NW->>MS: CM SERVICE PROMPT
+    MS->>NW: START CC
+    Note over MS,NW: Recall initiation
+    NW->>MS: CC-ESTABLISHMENT
+    MS->>NW: CC-ESTABLISHMENT CONFIRMED
+    Note over MS,NW: User notified about recall
+    NW->>MS: RECALL
+    MS->>NW: SETUP
+    Note over MS,NW: Recall accepted and call initiation
+    NW->>MS: CALL PROCEEDING
+    Note over MS,NW: Assignment of a traffic channel
+    NW->>MS: ASSIGNMENT COMMAND
+    MS->>NW: ASSIGNMENT COMPLETE
+    Note over MS,NW: Called user alerting information
+    NW->>MS: ALERTING
+    Note over MS,NW: Call accepted
+    NW->>MS: CONNECT
+    MS->>NW: CONNECT ACKNOWLEDGE
+    
+```
+
+The sequence diagram illustrates the network-initiated mobile originating call establishment process. It begins with the Network sending a PAGING REQUEST to the Mobile Station (MS). The MS responds with a CHANNEL REQUEST, and the Network replies with an IMMEDIATE ASSIGNMENT, initiating the RR connection establishment (MT). Next, the MS sends a PAGING RESPONSE. Then, the Network sends an AUTHENTICATION REQUEST, and the MS responds with an AUTHENTICATION RESPONSE. Following this, the Network sends a CIPHER MODE COMMAND, and the MS responds with a CIPHER MODE COMPLETE, completing the ciphering mode setting. The Network then sends a CM SERVICE PROMPT, and the MS responds with a START CC, initiating the Service Request. The Network sends a CC-ESTABLISHMENT, and the MS responds with a CC-ESTABLISHMENT CONFIRMED, initiating the recall. The Network sends a RECALL, and the MS responds with a SETUP, notifying the user about the recall. The Network then sends a CALL PROCEEDING, indicating the recall is accepted and call initiation. The Network sends an ASSIGNMENT COMMAND, and the MS responds with an ASSIGNMENT COMPLETE, assigning a traffic channel. The Network sends an ALERTING, indicating the called user alerting information. Finally, the Network sends a CONNECT, and the MS responds with a CONNECT ACKNOWLEDGE, accepting the call. The diagram ends with two beta symbols (β β) at the bottom right.
+
+Sequence diagram showing network initiated mobile originating call establishment. The diagram illustrates the interaction between a Mobile Station and a Network, detailing steps such as RR connection establishment, Authentication, Ciphering mode setting, Service Request, Recall initiation, User notification, Assignment of a traffic channel, Called user alerting, and Call acceptance.
+
+**Figure 7.20/3GPP TS 23.108: Network initiated mobile originating call establishment with assignment before B party alerting**
+
+![Sequence diagram showing network initiated mobile originating call establishment with assignment after A and B party alerting. The diagram shows interactions between a Mobile Station and a Network, including messages like PAGING REQUEST, CHANNEL REQUEST, IMMEDIATE ASSIGNMENT, PAGING RESPONSE, AUTHENTICATION REQUEST, AUTHENTICATION RESPONSE, CIPHER MODE COMMAND, CIPHER MODE COMPLETE, CM SERVICE PROMPT, START CC, CC-ESTABLISHMENT, CC-ESTABLISHMENT CONFIRMED, RECALL, SETUP, CALL PROCEEDING, ALERTING, ASSIGNMENT COMMAND, ASSIGNMENT COMPLETE, CONNECT, and CONNECT ACKNOWLEDGE. Annotations on the right side describe the protocol phases: RR connection establishment (MT), Authentication, Ciphering mode setting, Service Request, Recall initiation, User notified about recall, Recall accepted and call initiation, Called user alerting information, Assignment of a traffic channel, and Call accepted.](00504fc688ebcf131ccbeff94dfc9939_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Mobile Station
+    participant Network
+    Note right of Network: RR connection establishment (MT)
+    Network->>Mobile Station: PAGING REQUEST
+    Mobile Station-->>Network: CHANNEL REQUEST
+    Network-->>Mobile Station: IMMEDIATE ASSIGNMENT
+    Note right of Network: Authentication
+    Mobile Station-->>Network: PAGING RESPONSE
+    Network->>Mobile Station: AUTHENTICATION REQUEST
+    Mobile Station-->>Network: AUTHENTICATION RESPONSE
+    Note right of Network: Ciphering mode setting
+    Network->>Mobile Station: CIPHER MODE COMMAND
+    Mobile Station-->>Network: CIPHER MODE COMPLETE
+    Note right of Network: Service Request
+    Mobile Station-->>Network: CM SERVICE PROMPT
+    Network-->>Mobile Station: START CC
+    Note right of Network: Recall initiation
+    Mobile Station-->>Network: CC-ESTABLISHMENT
+    Network-->>Mobile Station: CC-ESTABLISHMENT CONFIRMED
+    Note right of Network: User notified about recall
+    Mobile Station-->>Network: RECALL
+    Note right of Network: Recall accepted and call initiation
+    Network->>Mobile Station: SETUP
+    Mobile Station-->>Network: CALL PROCEEDING
+    Note right of Network: Called user alerting information
+    Mobile Station-->>Network: ALERTING
+    Note right of Network: Assignment of a traffic channel
+    Network->>Mobile Station: ASSIGNMENT COMMAND
+    Mobile Station-->>Network: ASSIGNMENT COMPLETE
+    Note right of Network: Call accepted
+    Mobile Station-->>Network: CONNECT
+    Network-->>Mobile Station: CONNECT ACKNOWLEDGE
+  
+```
+
+β
+
+Sequence diagram showing network initiated mobile originating call establishment with assignment after A and B party alerting. The diagram shows interactions between a Mobile Station and a Network, including messages like PAGING REQUEST, CHANNEL REQUEST, IMMEDIATE ASSIGNMENT, PAGING RESPONSE, AUTHENTICATION REQUEST, AUTHENTICATION RESPONSE, CIPHER MODE COMMAND, CIPHER MODE COMPLETE, CM SERVICE PROMPT, START CC, CC-ESTABLISHMENT, CC-ESTABLISHMENT CONFIRMED, RECALL, SETUP, CALL PROCEEDING, ALERTING, ASSIGNMENT COMMAND, ASSIGNMENT COMPLETE, CONNECT, and CONNECT ACKNOWLEDGE. Annotations on the right side describe the protocol phases: RR connection establishment (MT), Authentication, Ciphering mode setting, Service Request, Recall initiation, User notified about recall, Recall accepted and call initiation, Called user alerting information, Assignment of a traffic channel, and Call accepted.
+
+Figure 7.21/3GPP TS 23.108: Network initiated mobile originating call establishment with assignment after A and B party alerting
+
+# 8 Handling of unknown, unforeseen, and erroneous protocol data
+
+For the RR protocol see 3GPP TS 44.018 [80] and for the CN protocols see 3GPP TS 24.008 [81].
+
+# --- 9 Message functional definitions and contents
+
+For the RR protocol see 3GPP TS 44.018 [80] and for the CN protocols see 3GPP TS 24.008 [81].
+
+# --- 10 General message format and information elements coding
+
+For the RR protocol see 3GPP TS 44.018 [80] and for the CN protocols see 3GPP TS 24.008 [81].
+
+# --- 11 List of system parameters
+
+For the RR protocol see 3GPP TS 44.018 [80] and for the CN protocols see 3GPP TS 24.008 [81].
+
+# Annex A (informative): Change History
+
+Based on 3GPP TS 04.08 version 7.1.1 and inclusion of CRs:
+
+| Tdoc      | SPEC   | CR   | REV | VERS   | SUBJECT                                                               | CAT | NEW_   |
+|-----------|--------|------|-----|--------|-----------------------------------------------------------------------|-----|--------|
+| P-99-510  | 24.008 | A371 | 2   | 7.1.0  | BCIE modifications due to EDGE                                        | B   | 8.0.0  |
+| P-99-523  | 24.008 | A515 | 1   | 7.1.0  | Split of 24.008 in RR and CN parts (Clause 7, "L3 stage2")            | F   | 8.0.0  |
+| P-99-388  | 24.008 | A562 |     | 7.1.0  | CR to 24.008 due to EDGE SMG2 EDGE WS                                 | B   | 8.0.0  |
+| P-99-523  | 24.008 | A567 | 1   | 7.1.0  | Split of 24.008 in RR and CN parts                                    | F   | 8.0.0  |
+| P-99-390  | 24.008 | A592 | 1   | 7.1.0  | GSM 400 and Mobile Station Classmark                                  | B   | 8.0.0  |
+| P-99-523  | 24.008 | A611 | 1   | 7.1.0  | Split of 24.008 in RR and CN parts                                    | F   | 8.0.0  |
+| P-99-523  | 24.008 | A613 | 1   | 7.1.0  | Split of 24.008 in RR and CN parts                                    | F   | 8.0.0  |
+| P-99-512  | 24.008 | A621 | 2   | 7.1.0  | IE Daylight saving time                                               | B   | 8.0.0  |
+| P-99-461  | 24.008 | A687 |     | 7.1.0  | Transfer of the LSA Information to the MS                             | B   | 8.0.0  |
+|           |        |      |     | 3.0.0  | Transferred to TSGN / June 1999                                       |     |        |
+| NP-99446  | 23.108 | 002  |     | 3.0.0  | mirror R99 LCS CR                                                     | A   | 3.1.0  |
+| NP-00095  | 23.108 | 004  |     | 3.1.0  | Clarification on timing to release TCH                                | C   | 3.2.0  |
+|           |        |      |     | 3.2.0  | NP-11: upgrade to Rel-4                                               |     | 4.0.0  |
+|           |        |      |     |        | NP-15: withdrawn                                                      |     |        |
+|           |        |      |     | 4.0.0  | NP-16: approved for Rel-5; MCC editorials & corrections to references |     | 5.0.0  |
+|           |        |      |     | 5.0.0  | Rel-6 published after CN#26                                           |     | 6.0.0  |
+|           |        |      |     | 6.0.0  | Upgraded to Rel-7 by MCC                                              |     | 7.0.0  |
+|           |        |      |     | 7.0.0  | Upgraded to Rel-8 by MCC                                              |     | 8.0.0  |
+|           |        |      |     | 8.0.0  | Upgraded to Rel-9 by MCC                                              |     | 9.0.0  |
+|           |        |      |     | 9.0.0  | Upgraded to Rel-10 by MCC                                             |     | 10.0.0 |
+| CP-110695 | 23.108 | 0005 |     | 10.0.0 | Refence update for TS 23.108                                          | F   | 11.0.0 |
+|           |        |      |     | 11.0.0 | Upgraded to Rel-12 by MCC                                             |     | 12.0.0 |
+|           |        |      |     | 12.0.0 | Upgraded to Rel-13 by MCC                                             |     | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 2017-03        | CT-75   | -    | -  | -   | -   | Update to Rel-14 version (MCC) | 14.0.0        |
+| 2018-06        | SA-80   | -    | -  | -   | -   | Update to Rel-15 version (MCC) | 15.0.0        |
+| 2020-07        | SA-88e  | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
+| 2022-03        | SA-95e  | -    | -  | -   | -   | Update to Rel-17 version (MCC) | <b>17.0.0</b> |
+| 2024-03        | -       | -    | -  | -   | -   | Update to Rel-18 version (MCC) | <b>18.0.0</b> |

marked/Rel-18/23_series/23700-64/raw.md

@@ -0,0 +1,715 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancements to application layer support for V2X services; Phase 2; (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'G' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+<keyword[, keyword]>
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+|                                                                                                                               |    |
+|-------------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                                                | 5  |
+| 1 Scope.....                                                                                                                  | 6  |
+| 2 References.....                                                                                                             | 6  |
+| 3 Definitions, symbols and abbreviations .....                                                                                | 7  |
+| 3.1 Definitions.....                                                                                                          | 7  |
+| 3.2 Abbreviations .....                                                                                                       | 7  |
+| 4 Key issues .....                                                                                                            | 7  |
+| 4.1 Key issue #1 – Support for high risk VRU zones .....                                                                      | 7  |
+| 4.2 Key issue #2 – Support for V2P communications .....                                                                       | 7  |
+| 4.3 Key issue #3 – V2X service deployment in edge data network.....                                                           | 8  |
+| 4.4 Key issue #4 – Enhancement to support non-simultaneous multiple service providers control for advanced V2X services ..... | 8  |
+| 4.5 Key issue #5 – Usage of network analytics.....                                                                            | 9  |
+| 4.6 Key issue #6 – Enhanced network monitoring to support advanced V2X services.....                                          | 9  |
+| 5 Architectural requirements.....                                                                                             | 9  |
+| 5.1 General requirements .....                                                                                                | 9  |
+| 5.2 VRU zone configuration requirements .....                                                                                 | 9  |
+| 5.2.1 Description .....                                                                                                       | 9  |
+| 5.2.2 Requirements.....                                                                                                       | 9  |
+| 5.3 V2P communications requirements .....                                                                                     | 10 |
+| 5.3.1 Description .....                                                                                                       | 10 |
+| 5.3.2 Requirements.....                                                                                                       | 10 |
+| 6 Solutions.....                                                                                                              | 10 |
+| 6.1 Solution #1 - VAE support for Energy Efficient V2P communications .....                                                   | 10 |
+| 6.1.1 Solution description.....                                                                                               | 10 |
+| 6.1.1.1 General.....                                                                                                          | 10 |
+| 6.1.1.2 Procedures.....                                                                                                       | 10 |
+| 6.1.1.2.1 Procedure for VAE client enabled V2P communication schedule configuration .....                                     | 11 |
+| 6.1.1.2.2 Procedure for VAE server enabled V2P communication schedule configuration .....                                     | 12 |
+| 6.1.2 Solution evaluation.....                                                                                                | 13 |
+| 6.2 Solution #2 - Support for VRU zone configuration and operation .....                                                      | 13 |
+| 6.2.1 Solution description.....                                                                                               | 13 |
+| 6.2.1.1 Procedure on VAL server - triggered VRU zone creation.....                                                            | 13 |
+| 6.2.2 Solution evaluation .....                                                                                               | 15 |
+| 6.3 Solution #3 - Deployment of V2X application layer with Edge Enabler Layer .....                                           | 15 |
+| 6.3.1 Solution description.....                                                                                               | 15 |
+| 6.3.2 Solution evaluation.....                                                                                                | 16 |
+| 6.4 Solution #4 - UE initiated request for VRU zones.....                                                                     | 16 |
+| 6.4.1 Solution description.....                                                                                               | 16 |
+| 6.4.1.1 General.....                                                                                                          | 16 |
+| 6.4.1.2 Procedure .....                                                                                                       | 17 |
+| 6.5 Solution #5 - Enhanced network monitoring .....                                                                           | 18 |
+| 6.5.1 Solution description.....                                                                                               | 18 |
+| 6.5.1.1 General.....                                                                                                          | 18 |
+| 6.5.1.2 Enhancements to subscription procedure in clause 9.7.3 .....                                                          | 19 |
+| 6.5.1.3 Enhancements to notification procedure in clause 9.7.4 .....                                                          | 19 |
+| 6.5.2 Solution evaluation .....                                                                                               | 19 |
+| 6.6 Solution #6 – Network situation enhanced with analytics .....                                                             | 19 |
+| 6.6.1 Solution description.....                                                                                               | 19 |
+| 6.6.1.1 General.....                                                                                                          | 19 |
+| 6.6.1.2 Enhancements to network monitoring by V2X UE .....                                                                    | 19 |
+| 6.6.1.3 Enhancements to monitoring and control of QoS for eV2X communications .....                                           | 19 |
+| 6.6.2 Solution evaluation.....                                                                                                | 19 |
+
+7 Overall evaluation..... 20  
+7.1 General ..... 20  
+7.2 Key issue and solution evaluation..... 20  
+7.3 Overall evaluation of key issue#1 ..... 20  
+7.4 Overall evaluation of key issue#2 ..... 21  
+7.5 Overall evaluation of key issue#3 ..... 21  
+7.6 Overall evaluation of key issue#4 ..... 21  
+7.7 Overall evaluation of key issue#5 ..... 21  
+7.8 Overall evaluation of key issue#6..... 21  
+8 Conclusions..... 22  
+**Annex A: Change history ..... 23**
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document is a technical report which identifies the enhancements to the application architecture to support V2X services specified in 3GPP TS 23.286 [6] considering advanced V2X services like V2P, ToD, etc and edge computing deployments for V2X services.
+
+The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to advanced V2X services and edge computing in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3], 3GPP TS 23.285 [5], 3GPP TS 23.287 [7], 3GPP TS 23.548 [10] and 3GPP TS 23.558 [11].
+
+The study also takes into consideration the V2X application specific services and recommendations specified by automotive industry bodies (5GAA, ETSI ITS and AECC) related to advanced V2X services for VRU, Haptics/ToD and edge deployments for V2X services.
+
+This document will provide recommendations for normative work.
+
+# 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 22.185: "Service requirements for V2X services; Stage 1".
+- [3] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1".
+- [4] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs".
+- [5] 3GPP TS 23.285: "Architecture enhancements for V2X services".
+- [6] 3GPP TS 23.286: "Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows".
+- [7] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
+- [8] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
+- [9] 3GPP TS 23.436: "Procedures for Application Data Analytics Enablement Service".
+- [10] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
+- [11] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
+- [12] 3GPP TR 23.700-36: "Study on Application Data Analytics Enablement Service".
+- [13] ETSI TS 103 300-2: "Intelligent Transport Systems (ITS); Vulnerable Road Users (VRU) awareness; Part 2: Functional Architecture and Requirements definition; Release 2".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+The terms and definitions as specified in 3GPP TS 23.286 [6] apply.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|      |                                                  |
+|------|--------------------------------------------------|
+| BSM  | Basic Safety Message                             |
+| CAM  | Cooperative Awareness Message                    |
+| CPM  | Collective Perception Message                    |
+| DENM | Decentralized Environmental Notification Message |
+| V2P  | Vehicle-to-Pedestrian                            |
+| V2X  | Vehicle-to-Everything                            |
+| VAE  | V2X Application Enabler                          |
+| VAM  | VRU awareness message                            |
+| VASS | V2X Application Specific Server                  |
+| VRU  | Vulnerable Road Users                            |
+| VRUP | Vulnerable Road User Protection                  |
+
+# 4 Key issues
+
+## 4.1 Key issue #1 – Support for high risk VRU zones
+
+In VRU high risk zones, drivers (or automated vehicles) are delivered warnings when they enter a high risk area where there is a likely presence of many VRUs. The high-risk area can be static (e.g. a school during arrival and leaving times), or dynamic (e.g. a school bus or mobile ice-cream vendor). Dedicated roadside infrastructure could play a vital role in disseminating warning messages to VRUs and vehicles as well.
+
+One issue at the scenario of the VRU high risk zone areas is how to configure the communication for the zones (which can include different types of interfaces and transmission modes) and how to translate the zone configurations (which are application driven) to network requirements and zone specific provisioning parameters considering both static and dynamic zones. Furthermore, another issue is how to assist the provisioning of zone specific parameters to the devices which can be potential VRUs and V2X-UEs and are expected to enter the zone. So, the key issue will study:
+
+- Whether and how to enhance VAE layer capabilities to support configuring the communication parameters for the zones.
+- Whether and how to enhance VAE layer capabilities to translate the zone configurations to network requirements and zone specific provisioning parameters.
+- Whether and how to assist the provisioning of zone specific parameters to the devices which can be potential VRUs and V2X-UEs.
+
+## 4.2 Key issue #2 – Support for V2P communications
+
+Vehicle to Pedestrian (V2P) is one of the V2X scenarios, which enables communication between vehicles and pedestrians for both safety and traffic efficiency related applications. One of the key V2P applications is the Vulnerable
+
+Road User Protection (VRUP) as specified in ETSI TS 103 300-2 [13]. VRUP provides warning to vehicles of the presence of vulnerable road users, e.g. pedestrian or cyclist, in case of dangerous situation. In VRUP, multiple V2X messages need to be exchanged between the pedestrian and the vehicular UEs, originating by one or more applications. Such messages can be standard VRU messages (e.g. VAM) and other V2X messages (CAM, DENM, BSM, CPM) and can be exchanged via different transmission modes (unicast, groupcast, broadcast).
+
+In such scenario, one challenge is that a pedestrian UE might have a lower battery capacity and limited radio capability, and therefore may have to work in a low power consumption mode, e.g. not being able to send/receive V2X messages with the same periodicity as a Vehicular UE. Continuous sending/receiving V2X messages by the pedestrian UE would affect UE power efficiency. A further challenge is that multiple applications related to VRU may be deployed, which may have differentiated traffic/QoS requirements as well as transmission/reception schedules.
+
+The VAE layer may provide support functionality for enabling V2P applications, by consolidating the V2P application requirements and aligning the communication traffic pattern with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles).
+
+So, the key issue will study:
+
+- Whether and how the VAE layer can support the V2P communications considering the UE situation (e.g. low battery power, weak radio signals)?
+- Whether and how the VAE layer can coordinate the alignment of the communication traffic patterns with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles)?
+
+## 4.3 Key issue #3 – V2X service deployment in edge data network
+
+The distributed deployment models for VAE layer are specified in clause 7.2.2 of 3GPP TS 23.286 [6]. It is possible that both VAE server and V2X application specific servers are deployed in the edge data network. Several industry bodies like 5GAA and AECC have studied the deployments of V2X services in edge computing domain.
+
+The edge enabler architecture is specified in 3GPP TS 23.558 [11] which supports Edge Application Servers (EAS) deployed at EDN with enabler capabilities like Application Context Relocation.
+
+It is required to investigate the impact of edge deployments of V2X application architecture considering the Edge enabler architecture. The following open issues can be studied:
+
+- a. Whether and how V2X application architecture supports the edge enabler architecture specified in 3GPP TS 23.558 [11].
+- b. Investigate the the impact on V2X enabler services for edge deployments.
+
+## 4.4 Key issue #4 – Enhancement to support non-simultaneous multiple service providers control for advanced V2X services
+
+Some capabilities (e.g. session oriented services) are specified in 3GPP TS 23.286 [6] which supports advanced V2X services (e.g. ToD service) controlled by a V2X application specific server operated by a V2X service provider. It is possible that a host vehicle can be controlled by multiple V2X service providers in different regions. Example: A host vehicle may be controlled by V2X service provider X in normal driving zone region and by V2X service provider Y in remote parking zone region. The multiple service providers may be utilizing the VAE services to support their ToD services. It can be investigated whether and how VAE services (e.g. Session oriented services) can support non-simultaneous multiple V2X service provider control for advanced V2X services (e.g. ToD).
+
+The following open issues can be studied:
+
+- a. Whether and how V2X enabler services (e.g. session oriented services) can support non-simultaneous multiple V2X service provider control for advanced V2X services.
+
+## 4.5 Key issue #5 – Usage of network analytics
+
+Exposure capabilities for various network analytics information (e.g. DN performance analytics) is specified in 3GPP TS 23.288 [8] via NWDAF (at network layer) and 3GPP TR 23.700-36 [12] via SEAL ADAE service (at application layer).
+
+Some capabilities (e.g. session oriented services) are specified in 3GPP TS 23.286 [5] which supports ToD service controlled by a V2X application specific server operated by a V2X service provider. These services require very good and stable network performance for successful service operation. It is hence required to study how network analytics (e.g. performance information or performance predictions) can be used to enhance the VAE capabilities which support advanced V2X services.
+
+The following open issue can be studied:
+
+- a. Whether and how V2X enabler services (e.g. session oriented services, V2X message delivery) can be enhanced to utilize the network analytics services specified in 3GPP TS 23.288 [8] and 3GPP TS 23.436 [9].
+
+## 4.6 Key issue #6 – Enhanced network monitoring to support advanced V2X services
+
+For advanced V2X scenarios the communication service situation is very important. The V2X UE should be able to choose the communication services (e.g. Uu or PC5) with another V2X UE or a group of V2X UEs considering the network situation towards the V2X UE(s) and/or the proximity of the V2X UEs within which the V2X UEs can communicate.
+
+In 3GPP TS 23.286 [6] clause 9.7, a V2X UE can subscribe for the network situation monitoring events in an area of interest. Once the V2X UE receives notification, it can further decide to switch between different modes of operations for V2X communications. However, it does not support network situation monitoring events for a specific V2X UE or a group of V2X UEs as required for advanced V2X applications (e.g. ToD, platooning).
+
+The open issue for the study is:
+
+- a. How to enhance the network monitoring procedures considering specific V2X UE information or group of V2X UE(s) information?
+
+# --- 5 Architectural requirements
+
+## 5.1 General requirements
+
+[AR-5.1-a] The V2X application architecture shall be able to support the V2X applications and V2X enabler services deployments in edge data network.
+
+## 5.2 VRU zone configuration requirements
+
+### 5.2.1 Description
+
+This subclause specifies the VRU zone configuration related requirements.
+
+### 5.2.2 Requirements
+
+[AR-5.2.2-a] The VAE capabilities shall support VRU zone configurations (e.g. distribution of VRU zone related configuration information) to the relevant V2X UEs.
+
+## 5.3 V2P communications requirements
+
+### 5.3.1 Description
+
+This subclause specifies the V2P communications related requirements.
+
+### 5.3.2 Requirements
+
+[AR-5.3.2-a] The VAE capabilities shall provide mechanisms (e.g. configurations) to support V2P communications.
+
+# --- 6 Solutions
+
+## 6.1 Solution #1 - VAE support for Energy Efficient V2P communications
+
+### 6.1.1 Solution description
+
+#### 6.1.1.1 General
+
+Vehicle to Pedestrian (V2P) is one of the V2X scenarios, which enables communication between vehicles and pedestrians for both safety and traffic efficiency related applications. One of the key V2P applications is the Vulnerable Road User Protection (VRUP) as specified in ETSI TS 103 300-2 [13]. VRUP provides warning to vehicles of the presence of vulnerable road users, e.g. pedestrian or cyclist, in case of dangerous situation. In VRUP, multiple V2X messages need to be exchanged between the pedestrian and the vehicular UEs, originating by one or more applications. Such messages can be standard VRU messages (e.g. VAM) and other V2X messages (CAM, DENM, BSM, CPM) and can be exchanged via different transmission modes (unicast, groupcast, broadcast).
+
+In such scenario, one challenge is that a pedestrian UE might have a lower battery capacity and limited radio capability, and therefore may have to work in a low power consumption mode, e.g. not being able to send/receive V2X messages with the same periodicity as a Vehicular UE. Continuous sending/receiving V2X messages by the pedestrian UE would affect UE power efficiency. A further challenge is that multiple applications related to VRU may be deployed, which may have differentiated traffic/QoS requirements as well as transmission/reception schedules.
+
+The VAE layer may provide support functionality for enabling V2P applications, by consolidating the V2P application requirements and aligning the communication traffic pattern with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles). Such alignment may be in the form of triggering the update of QoS / AS layer configuration based on application requirement (procedure is shown in clause 6.1.1.2.1 for client-triggered alignment and in clause 6.1.1.2.2 for VAE-server triggered alignment).
+
+The different procedures correspond to different solution variants to address different use cases.
+
+Clause 6.1.1.2.1 provides a VAE-client enabled V2P communication schedule configuration which could be applicable to off-network deployments and could be triggered by the application of the V2X UE (e.g. if UE battery drops while the V2P session is ongoing) based on prior configuration from the VAE server.
+
+On the other hand, clause 6.1.1.2.2 provides a VAE server enabled V2P communication schedule configuration, which could be applicable to use cases where the VAE server after receiving the VASS requirement, it configures/aligns the schedules for the V2X UEs (e.g. can be used within VRU zones to avoid flooding/interference by continuous sending/receiving V2X messages).
+
+#### 6.1.1.2 Procedures
+
+This subclause describes the procedures for V2P communication schedule configuration and update support by the VAE layer. This includes an off-network (VAE client enabled) and on-network (VAE server enabled) procedures for V2P communication schedule configuration.
+
+##### 6.1.1.2.1.1 Procedure for VAE client enabled V2P communication schedule configuration
+
+Figure 6.1.1.2.1-1 illustrates the procedure where the VAE client configures the traffic schedule for V2P communications based on application requirement; and triggers the translation to an AS layer/ QoS configurations update.
+
+Pre-conditions:
+
+1. VASS or VASC has subscribed to VAE layer to provide support for V2P communication.
+2. VAE client 1 has been configured by the VAE server to configure the communication schedule for V2P communications.
+3. V2X UE #1 and V2X UE#2 have discovered each other based upon V2P service and established a unicast connection using the V2X Service oriented Layer-2 link establishment procedure as specified in 3GPP TS 23.287 [7] clause 6.3.3.1
+
+![Sequence diagram illustrating the VAE client-enabled V2P communication schedule configuration procedure between V2X UE #1 and V2X UE #2.](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+The diagram shows the interaction between two User Equipment (UE) entities, V2X UE #1 (Pedestrian or Vehicle) and V2X UE #2 (Vehicle or Pedestrian). Each UE contains four internal components: V2X app specific client #2, V2X app specific client #1, VAE client, and V2X / AS layer.
+
+The sequence of messages is as follows:
+
+- 1. V2X application requirements:** Both V2X app specific client #1 and #2 in UE #1 send requirements to their respective VAE client.
+- 2. Generate communication schedule for UE#1:** The VAE client in UE #1 consolidates the requirements from both clients and generates a UE-level transmission schedule.
+- 3. V2P Communication schedule update:** The VAE client in UE #1 sends this update message to the VAE client in UE #2.
+- 4. Generate / Update communication schedule for UE#2:** The VAE client in UE #2 generates or updates its own schedule based on the received update.
+- 5. V2P Communication schedule update:** The VAE client in UE #2 sends a response or further update back to the VAE client in UE #1.
+- 6. Trigger AS layer / QoS adaptation:** Both VAE clients trigger adaptations in their respective V2X / AS layers.
+- 7. V2P communication schedule notification:** The V2X / AS layers in both UEs send notifications to their respective V2X app specific clients.
+
+The final state is labeled "V2P communication".
+
+Sequence diagram illustrating the VAE client-enabled V2P communication schedule configuration procedure between V2X UE #1 and V2X UE #2.
+
+**Figure 6.1.1.2.1-1: VAE client - enabled V2P communication schedule configuration**
+
+1. On V2X UE #1, the V2X application specific client 1 and 2 provide the V2X application requirements to the VAE client, including delay requirements, etc., for the PC5 communication. Here, this V2X Application specific client 1 may be requesting a groupcast communication and V2X Application specific client 2 may be requesting a unicast communication.
+2. V2X UE #1's VAE client consolidates requirements from both applications and generates a UE level transmission schedule, so that the off-duration is maximized. The determination of the transmission schedule can be determined based on the configuration on the UE (energy efficiency target) and the service KPIs.
+3. V2X UE #1's VAE client sends a V2P communication schedule update message which includes the generated UE level transmission schedule to other VAE client 2 (in vicinity, or in service-based group), in order to negotiate the optimal transmission pattern or inform on the expected reception pattern.
+4. V2X UE #2's VAE client either accepts or provides its transmission cycle or negotiates the traffic pattern.
+5. VAE clients of V2X UE #2 may optionally send a V2P communication schedule update message indicating the expected/generated UE #2 transmission pattern.
+6. V2X UE #1's and V2X UE #2's VAE clients (VAE clients are deployed at V2X application layer), provide the updated traffic pattern as V2X Application Requirements to V2X layer, also including QoS requirements such as delay requirements, priority, etc., for the PC5 communication for both applications, as specified in 3GPP TS 23.287 [7] clause 5.4.1.1. VAE client may also indicate the transmission mode (unicast, groupcast) per application. The V2X/AS layer of UE #1 and #2 applies/configures the DRX schedule for the corresponding
+
+V2X communication, based on the updated traffic pattern per cast type and/or destination Layer ID (as specified in 3GPP TS 23.287 [7] clause 5.9).
+
+**Editor's Note:** It is FFS to identify possible dependencies to RAN2/SA2 for the consideration of the Tx Profile which may impact the details of step 6.
+
+- VAE clients of V2X UEs #1 and #2 may send a notification to the V2X application specific client(s) to inform on the communication traffic pattern.
+
+##### 6.1.1.2.2 Procedure for VAE server enabled V2P communication schedule configuration
+
+Figure 6.1.1.2.2-1 illustrates the procedure where the VAE server configures the traffic schedule for V2P communications based on application requirement; and communicates with the VAE clients to trigger the translation to an AS layer/ QoS configurations update.
+
+Pre-conditions:
+
+- VASS has subscribed to VAE server to provide support for V2P communication.
+- VAE client of V2X UE #1 and V2X UE #2 are registered with VAE server.
+
+![Sequence diagram illustrating the VAE server-enabled V2P communication schedule configuration procedure. The diagram shows interactions between V2X UE #2, V2X UE #1 (containing V2X app specific client, VAE client, and V2X/AS layer), VAE server, and V2X app specific server. The steps are: 1. V2X application requirement from V2X app specific server to VAE server; 2. Generate communication schedule for V2X UE #1 and UE #2 from VAE server; 3. V2P Communication schedule configuration from VAE server to V2X UE #1; 4. Trigger AS layer / QoS adaptation from VAE client to V2X/AS layer; 5. Acknowledgement from V2X/AS layer to VAE server; 6. V2P communication schedule notification from VAE client to V2X app specific client. The process concludes with V2P communication.](af6be343f0c0a8f155f965dcf337b8af_img.jpg)
+
+```
+
+sequenceDiagram
+    participant V2X_UE_2 as V2X UE #2
+    subgraph V2X_UE_1 [V2X UE #1 (Pedestrian or Vehicle)]
+        V2X_app_client[V2X app specific client]
+        VAE_client[VAE client]
+        V2X_AS_layer[V2X / AS layer]
+    end
+    participant VAE_server as VAE server
+    participant V2X_app_server as V2X app specific server
+
+    Note right of V2X_app_server: 1. V2X application requirement
+    V2X_app_server->>VAE_server: 1. V2X application requirement
+    Note right of VAE_server: 2. Generate communication schedule for V2X UE #1 and UE #2
+    VAE_server->>VAE_client: 3. V2P Communication schedule configuration
+    Note right of VAE_client: 4. Trigger AS layer / QoS adaptation
+    VAE_client->>V2X_AS_layer: 4. Trigger AS layer / QoS adaptation
+    Note right of V2X_AS_layer: 5. Acknowledgement
+    V2X_AS_layer->>VAE_server: 5. Acknowledgement
+    Note right of VAE_client: 6. V2P communication schedule notification
+    VAE_client->>V2X_app_client: 6. V2P communication schedule notification
+    Note bottom of V2X_UE_1: V2P communication
+    V2X_UE_2->>V2X_UE_1: V2P communication
+  
+```
+
+Sequence diagram illustrating the VAE server-enabled V2P communication schedule configuration procedure. The diagram shows interactions between V2X UE #2, V2X UE #1 (containing V2X app specific client, VAE client, and V2X/AS layer), VAE server, and V2X app specific server. The steps are: 1. V2X application requirement from V2X app specific server to VAE server; 2. Generate communication schedule for V2X UE #1 and UE #2 from VAE server; 3. V2P Communication schedule configuration from VAE server to V2X UE #1; 4. Trigger AS layer / QoS adaptation from VAE client to V2X/AS layer; 5. Acknowledgement from V2X/AS layer to VAE server; 6. V2P communication schedule notification from VAE client to V2X app specific client. The process concludes with V2P communication.
+
+**Figure 6.1.1.2.2-1: VAE server - enabled V2P communication schedule configuration**
+
+- One or more V2X application specific servers provide the V2X application requirements to the VAE server, including application QoS requirements for the V2P applications and provisioning policies and parameters for the PC5 communication.
+- The VAE server generates a communication schedule for one or more involved V2X UEs, so that the off duration is maximized. The determination of the transmission schedule can be determined based on the V2P service KPIs. Such communication schedule may include the transmission/reception schedule for the application messages and may also include the DRX cycle configuration for out of coverage and groupcast/broadcast communications.
+- The VAE server sends a V2P communication schedule configuration message to the involved VAE clients. This includes the generated UE level transmission schedules and may also include the DRX cycle configuration for PC5 communication in out of coverage and groupcast/broadcast modes.
+- V2X UE #1's and V2X UE #2's VAE clients provide the updated traffic pattern as V2X Application Requirements to V2X layer, also including QoS requirements such as delay requirements, priority, etc., for the PC5 communication for both applications, as specified in 3GPP TS 23.287 [7] clause 5.4.1.1. VAE client may also indicate the transmission mode (unicast, groupcast) per application. The V2X layer of UEs #1 and #2
+
+process the requirements from VAE client and generates a UE level DRX schedule. The AS layer of UE #1 and #2 applies/configures the DRX schedule for the corresponding V2X communication.
+
+5. VAE clients of V2X UEs #1 and #2 may send an acknowledgement to the VAE server.
+6. VAE clients of V2X UEs #1 and #2 may send a notification to the V2X application specific client(s) to inform on the communication traffic pattern.
+
+### 6.1.2 Solution evaluation
+
+In this solution, the VAE layer provides a support functionality for enabling V2P applications, by consolidating the V2P application requirements and aligning the communication traffic pattern with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles). Such alignment may be in the form of triggering the update of QoS/AS layer configuration based on application requirement.
+
+There are two solution variants captured in this solution:
+
+- Client-triggered alignment in clause 6.1.1.2.1, has possible dependency on the SA2 work (for the consideration of the Tx Profile which may impact the details of step 6). Also, for this variant the relationship of service KPIs and energy efficiency target (as discussed in step 2) requires further consideration during the normative phase.
+- VAE-server triggered alignment in clause 6.1.1.2.2) has no dependencies to SA2 and is a viable technical solution to address key issue#2.
+
+## 6.2 Solution #2 - Support for VRU zone configuration and operation
+
+### 6.2.1 Solution description
+
+#### 6.2.1.1 Procedure on VAL server - triggered VRU zone creation
+
+This procedure supports the configuration and provisioning of the VRU high risk zone at the VAE layer based on a request from the VASS / VAL server.
+
+Figure 6.2.1.1-1 illustrates the procedure where the VAE client configures the VRU zone based on application requirement; and supports the run-time operation based on an expected UE entrance to the zone.
+
+Pre-conditions:
+
+1. VASS or VASC has subscribed to VAE layer to provide support for V2P communication.
+
+![Sequence diagram illustrating VAL server - triggered VRU zone creation. The diagram shows interactions between V2X UEs (at high risk area), UE #1 (Pedestrian or Vehicle candidate VRU) containing V2X/VRU app #1, VAE client, and V2X/ AS layer, SEAL LMS, VAE server, and VASS. The sequence of messages is: 1. VRU zone management subscription req from V2X/VRU app #1 to VAE server; 2. Processing subscription req and store subscription from VAE server; 3. VRU zone management subscription resp from VAE server to VASS; 4. Initiate Location tracking to detect UEs approaching VRU zone and UEs within zone from SEAL LMS to VAE server; 5. Notification of VRU zone information to the UEs (within the zone) from VAE server to V2X UEs; 6. SEAL LMS event notifications for VRU zone from SEAL LMS to VAE server; 7. Notification of UE1 approaching / leaving zone from VAE server to VASS; 8. Notification of UE1 approaching / leaving zone from VAE server to V2X UEs (dashed line).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+Sequence diagram illustrating VAL server - triggered VRU zone creation. The diagram shows interactions between V2X UEs (at high risk area), UE #1 (Pedestrian or Vehicle candidate VRU) containing V2X/VRU app #1, VAE client, and V2X/ AS layer, SEAL LMS, VAE server, and VASS. The sequence of messages is: 1. VRU zone management subscription req from V2X/VRU app #1 to VAE server; 2. Processing subscription req and store subscription from VAE server; 3. VRU zone management subscription resp from VAE server to VASS; 4. Initiate Location tracking to detect UEs approaching VRU zone and UEs within zone from SEAL LMS to VAE server; 5. Notification of VRU zone information to the UEs (within the zone) from VAE server to V2X UEs; 6. SEAL LMS event notifications for VRU zone from SEAL LMS to VAE server; 7. Notification of UE1 approaching / leaving zone from VAE server to VASS; 8. Notification of UE1 approaching / leaving zone from VAE server to V2X UEs (dashed line).
+
+**Figure 6.2.1.1-1: VAL server - triggered VRU zone creation**
+
+1. The V2X application specific server sends a subscription request to manage the creation and configuration of a new high-risk area zone, and requires the VAE server support to translate it to a network-related zone configuration and provisioning to the UEs within the requested area. The subscription request consists of the Requestor ID (VASS ID or App ID), the VRU zone type (based on the scenario, which type of UEs are to be considered), geographical area, time validity and initiation trigger, types of supported messages and requirements (e.g. requirements for VAM messages), application QoS requirement dedicated for the VRU zone (e.g. URLLC like), whether it is a dynamic or static zone, etc.
+
+NOTE: If the zone is dynamically changing based on an event (e.g. school bus mobility / route), such mobility/route information will be provided to the VAE server, or the VASS needs to provide new configuration every time the configuration changes.
+
+2. The VAE server processes the request and stores the subscription. The processing includes the translation of the zone requirement of step 1 and determines a set of network-related zone parameters which indicates the configuration parameters for example: the topological area for the zone (cell IDs, TAs), the QoS requirements within the zone, the exposure requirements within the zone, the value added services required within the zone (e.g. location tracking, V2X message bundling), the transmission modes (unicast, groupcast, broadcast) within the applications within the zone, the interface selection within the zone (Uu, PC5), the use of application relaying or not, whether the zone is dynamic or not, and if it is dynamic to take into account the configuration adaptation every time the configuration changes or to provide the planning (e.g. based on a school bus route) to allow the network to adapt the configuration.
+3. The VAE server sends a VRU zone creation subscription response to VASS.
+4. The VAE server initiates the SEAL LMS service for location tracking both for static location and dynamically changing location for all UEs within the VRU zone area. VAE server obtains and initiates tracking the V2X UEs location from the location management server 1 as specified in 3GPP TS 23.434 (clause 9.3.12).
+5. The VAE server sends a notification message including the VRU zone configuration parameters. Parameters can be based on the parameters provided in step 2. This configuration will be provided to the V2X-UEs (and pedestrians) within the area that will be covered by the VRU zone, and will also indicate when the zone will be activated, for how much time and if the zone configuration will be dynamically changing (e.g. where a school bus moves) and parameters related to the dynamicity (as discussed in steps 1, 2).
+6. The VAE server keeps monitoring the VRU zone area based on monitoring SEAL LMS events. This includes events on whether a UE (e.g. UE1) is moving in or out a target area of interest.
+
+The VAE server translates the UE1 mobility event to an expected entrance to a VRU high risk zone, and based on the configuration of the zone, it identifies when an action needs to be taken and when to communicate this with the involved application entities.
+
+7. The VAE server alerts the VASS that the UE1 is expected to move to the VRU zone area in X time and provides also information on its mobility as well as the UE1 capabilities (e.g. VRU capable). The notification / alert message may include the UE ID (GPSI, or external ID), the group ID (if it is a group of UEs), an expected start time of VRUP, an expected duration, expected mobility/speed/direction, etc. Alternatively, when UE is leaving the zone, a message can be sent to VASS to notify that the UE1 is expected to leave this area and the VRUP is no longer needed.
+8. The VAE server may also alert the VAE client (if deployed at the UE1) that it is expected to enter the VRU zone and requests the confirmation for allowing the push of VRU messages within the zone. Such notification / request will include zone area information and configuration parameters. Alternatively, when UE is leaving the zone, a message can be sent to VAE client to notify that the UE1 is expected to leave this area and the VRUP is no longer needed.
+
+### 6.2.2 Solution evaluation
+
+This solution addresses KI #1 on zone configuration and provisioning for VRUP applications. The solution supports the configuration and provisioning of the VRU high risk zone at the VAE layer based on a request from the VASS / VAL server. This solution enables distribution of zones and notifications related to those zones, but any usage of this information is up to the application as this information is not directly used by the VAE layer. This solution is technically viable.
+
+## 6.3 Solution #3 - Deployment of V2X application layer with Edge Enabler Layer
+
+### 6.3.1 Solution description
+
+This solution corresponds to key issue#3. The architecture for edge enabler layer is specified in 3GPP TS 23.558 [11]. This clause describes the deployment of V2X application layer services at Edge Data Network by utilizing the Edge Enabler Layer services.
+
+Figure 6.3.1-1 illustrates the edge deployment example for the V2X application layer. For simplicity, the reference points between enabler server and 5GS are omitted, and the reference points for inter-enabler server communication in the same enabler layer are also omitted. At UE side, V2X Application Specific client(s) and VAE client interact with the Edge Enabler Client (EEC) via EDGE-5 reference point. In an Edge Data Network (EDN), V2X Application Specific Server and VAE server assume the role of EAS (Edge Application Server) and interacts with the Edge Enabler Server (EES) via EDGE-3 reference point, for instance, to register its profile into the EES. Upon service provisioning, the EEC interacts with the EES via EDGE-1 reference point, for instance, to discover V2X Application Specific Server(s) and VAE Server and further the EEC provides the discovered V2X Application Specific Server(s) and VAE server to the V2X Application Specific client and VAE client respectively.
+
+![Figure 6.3.1-1: Deployment of V2X application layer with Edge Enabler Layer. The diagram shows a V2X UE on the left and an EDN on the right, connected via a 5GS. The V2X UE contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. The EDN contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. Various interfaces (V1, Vc, Vs, V1-AE, SEAL-C, SEAL-S, SEAL-UU, EDGE-1, EDGE-3, EDGE-4, EDGE-5, EDGE-6) are shown between components.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+The diagram illustrates the deployment of the V2X application layer with the Edge Enabler Layer. It is divided into two main entities: V2X UE (User Equipment) on the left and EDN (Edge Data Network) on the right, connected via a 5GS (5G System) in the center. The V2X UE contains several layers: V2X application specific layer (with V2X Application Specific Client(s)), VAE layer (with VAE client), SEAL layer (with SEAL clients), and EDGE Enabler layer (with Edge Enabler Client). The EDN contains corresponding layers: V2X application specific layer (with V2X Application Specific Server(s)), VAE layer (with VAE server), SEAL layer (with SEAL servers), and EDGE Enabler layer (with Edge Enabler Server and Edge Configuration Server). Interfaces are labeled as follows: V1 between V2X Application Specific Client(s) and V2X Application Specific Server(s); Vc and Vs between V2X Application Specific Client(s)/Server(s) and VAE client/server; V1-AE between VAE client and VAE server; SEAL-C and SEAL-S between VAE client/server and SEAL clients/servers; SEAL-UU between SEAL clients and SEAL servers; EDGE-1 between Edge Enabler Client and Edge Enabler Server; EDGE-3 between SEAL servers and Edge Enabler Server; EDGE-4 between Edge Enabler Client and Edge Configuration Server; EDGE-5 between Edge Enabler Client and SEAL clients; EDGE-6 between Edge Enabler Server and Edge Configuration Server.
+
+Figure 6.3.1-1: Deployment of V2X application layer with Edge Enabler Layer. The diagram shows a V2X UE on the left and an EDN on the right, connected via a 5GS. The V2X UE contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. The EDN contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. Various interfaces (V1, Vc, Vs, V1-AE, SEAL-C, SEAL-S, SEAL-UU, EDGE-1, EDGE-3, EDGE-4, EDGE-5, EDGE-6) are shown between components.
+
+**Figure 6.3.1-1: Deployment of V2X application layer with Edge Enabler Layer**
+
+In an EDN, there could be several EES(s) provided by the same or different ECSP. The V2X application specific server(s) and VAE server shall be able to discover and register into an appropriate EES. If CAPIF is used, this can be done by utilizing the AEF serving area and/or the AEF location as described in 3GPP TS 23.222 [4]; otherwise, local configuration of the EES endpoint may be used.
+
+Note that the services provided by EES over EDGE-3 are not re-exposed by the VAE server or SEAL servers to the V2X application specific server but are directly consumed by the SEAL servers, VAE server and V2X application specific server(s).
+
+### 6.3.2 Solution evaluation
+
+This solution addresses key issue#3 for "Whether and how V2X application architecture supports the edge enabler architecture specified in 3GPP TS 23.558 [11]" and provides a solution for the deployment of V2X application layer with Edge Enabler Layer.
+
+## 6.4 Solution #4 - UE initiated request for VRU zones
+
+### 6.4.1 Solution description
+
+#### 6.4.1.1 General
+
+A cyclist training for long-distance competitions is vulnerable to road collisions during the entire training route. The cyclist would like to create a protection zone that tracks their route for use as part of the services provided by the V2X service provider. The V2X infrastructure, including edge enabler servers, receives a request to create a protection zone and dynamically update the protection zone to follow the route of the cyclist. When an incoming vehicle is detected, the infrastructure can alert the vehicle and provision V2P communication configurations to enable the vehicle to communicate with the cyclist.
+
+The following solution is provided for key issues #1 and 2 and complements solution #1. This solution also enhances solution #2 by providing an option to employ the VAE layer to receive protection zone configuration requests from the UE and notify VASS. The two solutions can coexist in any deployment, with the VRU application determining whether solution#4 may be used based on a policy specifying whether:
+
+- Use of VAE service for protection zone notification is allowed; and
+- Protection zone requests initiated by UEs are allowed.
+
+#### 6.4.1.2 Procedure
+
+Pre-conditions:
+
+- VASS has subscribed to VAE server to provide support for V2P communication.
+- VAE clients of V2X cyclist UE and vehicular UE are registered with VAE server.
+- The VRU application (at VASS and Application client at the cyclist UE) are pre-configured so that:
+  - Use of VAE service for protection zone notification is allowed; and
+  - Protection zone requests be initiated by UEs are allowed.
+
+NOTE 1: Pre-condition 3 allows VAE server to determine that use of solution#4 mechanism is allowed.
+
+![Sequence diagram illustrating the UE request for protection zone procedure. The diagram shows interactions between Vehicular UE (VAE client), Pedestrian UE (App client and VAE client), 5GS, SEAL LMS, VAE Server, and VASS. The sequence starts with the Pedestrian UE sending a protection zone request to the VAE client, which then sends a request to the VAE server. The VAE server requests authorization from the VASS, which creates the protection zone and responds. The VAE server then configures subscriptions and sends a protection zone response to the Pedestrian UE. Finally, the VAE server sends UE mobility information and application context information to the 5GS, which updates the protection zone and notifies UEs, sending a notification alert to the Pedestrian UE.](29f586959675cafdf81cf934954908eb_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VUE as Vehicular UE  
+VAE client
+    participant PUE as Pedestrian UE  
+App client | VAE client
+    participant 5GS
+    participant SEAL as SEAL LMS
+    participant VAE as VAE Server
+    participant VASS
+
+    Note right of PUE: 1. Protection zone request
+    PUE->>VAE: 2. Protection zone request
+    VAE->>VASS: 3. Request authorization
+    VASS->>VAE: 4. Create protection zone
+    VASS->>VAE: 5. Authorization response
+    VAE->>5GS: 6. Configure subscriptions
+    VAE->>PUE: 7. Protection zone response
+    Note right of 5GS: 8. Protection zone response
+    Note right of 5GS: 9a. UE mobility information
+    Note right of 5GS: 9b. UE application context information
+    Note right of 5GS: 10. Update protection zone and notify UEs in the protectionzone
+    Note right of 5GS: 11. Notification alert
+    5GS->>PUE: 11. Notification alert
+  
+```
+
+Sequence diagram illustrating the UE request for protection zone procedure. The diagram shows interactions between Vehicular UE (VAE client), Pedestrian UE (App client and VAE client), 5GS, SEAL LMS, VAE Server, and VASS. The sequence starts with the Pedestrian UE sending a protection zone request to the VAE client, which then sends a request to the VAE server. The VAE server requests authorization from the VASS, which creates the protection zone and responds. The VAE server then configures subscriptions and sends a protection zone response to the Pedestrian UE. Finally, the VAE server sends UE mobility information and application context information to the 5GS, which updates the protection zone and notifies UEs, sending a notification alert to the Pedestrian UE.
+
+Figure 6.4.1.2-1: UE request for protection zone
+
+- Optionally, an application client on a cyclist UE makes a request to the VAE client to create a protection zone.
+- A VAE client sends a request to a VAE server to create a protection zone. The request may include V2X Service ID, UE ID, application ID, UE location and location reporting configuration, destination location, request for dynamic protection zone, V2P communication configuration, user consent for using user application context information, user activity, active applications, etc.
+- The VAE server sends a request to a VASS to authorize the creation of the protection zone for the cyclist UE and includes the information provided by the cyclist UE.
+
+4. The VASS authorizes the request and creates a protection zone based on information received from the VAE server. The VASS provides the VAE server with the protection zone and V2P communication configuration.
+5. The VASS responds with an authorization response to the VAE server. The response includes the status of the authorization, the protection zone type, geographical area, time validity and initiation trigger, types of supported messages and requirements (e.g. requirements for VAM messages), application QoS requirement dedicated for the protection zone (e.g. URLLC like), whether it is a dynamic or static zone, an expiration for the protection zone, V2P communication configuration information, etc.
+6. The VAE server configures subscriptions to obtain UE location from the 5G system. Sources of UE mobility information may come from SEAL LMS servers, EES, an analytics function (e.g. from ADAES or NWDAF), and the 5G core network. For V2X UEs location obtained from the location management server, the procedures specified in 3GPP TS 23.434 (clause 9.3.12) apply.
+7. The VAE server sends a response message to the cyclist UE with a status for the request, the information of the protection zone, and updated V2P communication configuration. The VAE server may also subscribe to receive notifications from the VAE client about application context events such as user activity, active applications, application notifications, navigation information, etc.
+8. Optionally, the VAE client returns a response to the application client.
+9. The VAE server receives UE mobility information from the 5G network and/or from the UEs. The cyclist UE and vehicular UE may also provide application context information to the VAE server, such as battery level, user activity, active applications, and routing information from a navigation app. The battery level of the UE may help the VAE server determine the V2P communication configuration to provide to UEs in the protection zone. For example, if the battery level of a cyclist UE is low, the VAE server may provide V2P communication configurations to vehicular UEs to align with when the cyclist UE is able to receive V2P communication. Alternatively, the VAE server can provide V2P communication parameters to vehicular UEs to communicate with nearby UEs instead.
+10. The VAE server updates the protection zone based on information the VAE server has obtained about the cyclist UE. For example, the protection zone may be updated due to a change in UE location. In addition, the VAE server may broadcast the new protection zone information to all the UEs in the protection zone.
+11. The VAE server detects that a vehicular UE is now in the updated protection zone and sends a notification alert to the vehicular UE and includes the V2P communication configuration for use by the vehicular UE to communicate directly with the cyclist UE.
+
+### 6.4.2 Solution evaluation
+
+This solution addresses KI #1 and aspects of KI #2 and provides a procedure for a VAL client on a cyclist UE to request the creation of a dynamic protection zone via the VAE client. The VAE server checks with a VASS to authorize the request and if authorized, the VASS creates a protection zone based on the information provided by the VAE client. After the creation of the protection zone, the VAE server monitors the UE's mobility information and updates the protection zone accordingly. If the VAE server detects the presence of other vehicular UEs in the updated protection zone, the VAE server sends a notification alert to the vehicular UE and includes V2P communication configuration information.
+
+Further agreement is needed for the scenario of this solution where UEs can initiate VRU protection zone creation.
+
+## 6.5 Solution #5 - Enhanced network monitoring
+
+### 6.5.1 Solution description
+
+#### 6.5.1.1 General
+
+This solution corresponds to key issue#6. The network monitoring subscription and notification procedures specified in clause 9.7 of 3GPP TS 23.286 [6] are enhanced to allow a V2X UE for subscription and notification of network situation monitoring events considering a single V2X UE or a group of V2X UE(s) in addition to area information.
+
+#### 6.5.1.2 Enhancements to subscription procedure in clause 9.7.3
+
+In step 1, the network monitoring information subscription request from VAE client to VAE server can include target V2X UE ID(s) in addition to area information.
+
+In step 2, the VAE server is enhanced to initiate network monitoring considering the requested information in step 1.
+
+#### 6.5.1.3 Enhancements to notification procedure in clause 9.7.4
+
+In step 1, the network monitoring of VAE server with 5GC is enhanced to include configuring and receiving network monitoring events for V2X UE ID(s) also as per the subscription.
+
+### 6.5.2 Solution evaluation
+
+This is a viable technical solution to address key issue#6.
+
+## 6.6 Solution #6 – Network situation enhanced with analytics
+
+### 6.6.1 Solution description
+
+#### 6.6.1.1 General
+
+This solution corresponds to key issue#5. The network situation monitoring procedures specified in clause 9.7 and clause 9.20 of 3GPP TS 23.286 [6] are enhanced to utilize the SEAL's ADAE services for application performance analytics and prediction.
+
+#### 6.6.1.2 Enhancements to network monitoring by V2X UE
+
+In clause 9.7.3, step 2 of 3GPP TS 23.286 [6], the VAE server is enhanced to utilize the SEAL's ADAE service for application performance analytics and prediction.
+
+In clause 9.7.4, step 1 of 3GPP TS 23.286 [6], the network monitoring also includes the SEAL's ADAE service. In step 2, the VAE server processes the information obtained from SEAL's ADAE service corresponding to the application session. In step 3, the VAE server provides the notification to the V2X UE about both network situation and the predicted network situation.
+
+#### 6.6.1.3 Enhancements to monitoring and control of QoS for eV2X communications
+
+In clause 9.20.3, step 2 of 3GPP TS 23.286 [6], the VAE server is enhanced to utilize the SEAL's ADAE service for application performance analytics and prediction.
+
+In clause 9.20.4, step 1 of 3GPP TS 23.286 [6], the monitoring reports also includes the SEAL's ADAE service. In step 2, the VAE server processes the information obtained from SEAL's ADAE service corresponding to the application session. In step 3, the VAE server provides the service requirement adaptation notification request to V2X application specific server about both network situation and the predicted network situation to initiate any application session adaptation (e.g. session oriented service update or terminate).
+
+### 6.6.2 Solution evaluation
+
+This is a viable technical solution to address key issue#5 for supporting utilization of improved analytics.
+
+# 7 Overall evaluation
+
+## 7.1 General
+
+The following subclauses contain an overall evaluation of the solutions presented in this technical report, and their applicability to the identified key issues.
+
+- Clause 7.2 lists the solutions for the key issues including impact on other working groups that will need consideration.
+
+## 7.2 Key issue and solution evaluation
+
+All the key issues and solutions specified in this technical report are listed in table 7.2-1. It includes the mapping of the key issues (clause 4) to the solutions and corresponding solution evaluations. Also it lists the impact on other working groups that will need consideration during the Release 18 normative phase.
+
+**Table 7.2-1: Key issue and solution evaluation**
+
+| Key issues                                                                                                          | Solution                                                                  | Evaluation (subclause reference) | Dependency on other working groups |
+|---------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|----------------------------------|------------------------------------|
+| Key issue #1 – Support for high risk VRU zones                                                                      | Solution #2 - Support for VRU zone configuration and operation            | Clause 6.2.2                     | SA2, RAN2                          |
+|                                                                                                                     | Solution #4 - UE initiated request for VRU zones                          | Clause 6.4.2                     | -                                  |
+| Key issue #2 – Support for V2P communications                                                                       | Solution #1 - VAE support for Energy Efficient V2P communications         | Clause 6.1.2                     | -                                  |
+|                                                                                                                     | Solution #4 - UE initiated request for VRU zones                          | Clause 6.4.2                     | -                                  |
+| Key issue #3 – V2X service deployment in edge data network                                                          | Solution #3 - Deployment of V2X application layer with Edge Enabler Layer | Clause 6.3.2                     | -                                  |
+| Key issue #4 – Enhancement to support non-simultaneous multiple service providers control for advanced V2X services | -                                                                         | -                                | -                                  |
+| Key issue #5 – Usage of network analytics                                                                           | Solution #6 – Network situation enhanced with analytics                   | Clause 6.6.2                     | -                                  |
+| Key issue #6 – Enhanced network monitoring to support advanced V2X services                                         | Solution #5: Enhanced network monitoring                                  | Clause 6.5.2                     | -                                  |
+
+## 7.3 Overall evaluation of key issue#1
+
+Key issue#1 on support for high risk VRU zones discussed the following open issues:
+
+- Whether and how to enhance VAE layer capabilities to support configuring the communication parameters for the zones.
+- Whether and how to enhance VAE layer capabilities to translate the zone configurations to network requirements and zone specific provisioning parameters.
+- Whether and how to assist the provisioning of zone specific parameters to the devices which can be potential VRUs and V2X-UEs.
+
+Solution#2 provides a solution for network initiated VRU zone configuration and operation. It addresses the open issues in a, b and c.
+
+Solution#4 provides a solution for UE initiated configuration and operation of protection zones.
+
+## 7.4 Overall evaluation of key issue#2
+
+Key issue#2 on support for V2P communications discussed the following open issues:
+
+- a. Whether and how the VAE layer can support the V2P communications considering the UE situation (e.g. low battery power, weak radio signals)?
+- b. Whether and how the VAE layer can coordinate the alignment of the communication traffic patterns with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles)?
+
+Solution#1 provides a solution for VAE support for energy efficient V2P communications. It addresses the open issues in a and b. The solution#1 is dependent on SA2 and RAN2.
+
+## 7.5 Overall evaluation of key issue#3
+
+Key issue#3 on V2X service deployment on edge data network discussed the following open issues:
+
+- a. Whether and how V2X application architecture supports the edge enabler architecture specified in 3GPP TS 23.558 [11].
+- b. Investigate the the impact on V2X enabler services for edge deployments.
+
+Solution#3 addresses the open issue a of key issue#3 which further enables the V2X service deployments to utilize edge enabler layer for V2X service deployments. No impact on V2X enabler services for edge deployments were identified as per open issue b.
+
+## 7.6 Overall evaluation of key issue#4
+
+Key issue#4 on enhancement to support non-simultaneous multiple service providers control for advanced V2X services discussed the following open issues:
+
+- a. Whether and how V2X enabler services (e.g. session oriented services) can support non-simultaneous multiple V2X service provider control for advanced V2X services.
+
+No solutions were proposed to address this key issue.
+
+## 7.7 Overall evaluation of key issue#5
+
+Key issue#5 on usage of network analytics discussed the following open issues:
+
+- a. Whether and how V2X enabler services (e.g. session oriented services, V2X message delivery) can be enhanced to utilize the network analytics services specified in 3GPP TS 23.288 [8] and 3GPP TS 23.436 [9].
+
+Solution#6 provides a solution for usage of network analytics offered by ADAE. It addresses the open issue a.
+
+## 7.8 Overall evaluation of key issue#6
+
+Key issue#6 on enhanced network monitoring to support advanced V2X services discussed the following open issues:
+
+- a. How to enhance the network monitoring procedures considering specific V2X UE information or group of V2X UE(s) information?
+
+Solution#5 provides a solution for enhanced network monitoring. It addresses the open issue a.
+
+# 8 Conclusions
+
+This technical report fulfills the objectives of the study on enhancements to application layer to support advanced V2X services like V2P, ToD, etc and edge computing deployments for V2X services. The study includes the following:
+
+- 1) Identification of key issues (clause 4) and corresponding architecture requirements (clause 5) for enhanced V2X application enabler capabilities.
+- 2) Individual solutions (clause 5) addressing the key issues.
+- 3) Overall evaluation (clause 7) of all the key issues and solutions.
+
+The results from the study will be considered for follow-up normative work in Release 18 as follows:
+
+- 1) The architecture requirements (in clause 5) will be considered as the basis for technical specification with necessary enhancements and additions;
+- 2) The following key issues (clause 4) and individual solutions (clause 6) are considered to be the candidate solutions with necessary enhancements as appropriate, according to the overall evaluation (clause 7):
+  - For key issue#1, solution#2 is considered and solution#4 can be considered based on the agreement on the use of protection zones.
+  - For key issue#2, solution#1 is considered subjected to capabilities enabled by SA2 and RAN2.
+  - For key issue#3, solution#3 is considered.
+  - For key issue#4, there is no solution proposed.
+  - For key issue#5, solution#6 is considered.
+  - For key issue#6, solution#5 is considered.
+
+# Annex A: Change history
+
+| Change history |              |           |      |     |     |                                                                                                             |             |
+|----------------|--------------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting      | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                             | New version |
+| 2021-10        | SA6#45-bis-e |           |      |     |     | TR skeleton as approved by SA6 in S6-212349                                                                 | 0.0.0       |
+| 2021-10        | SA6#45-bis-e |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-212397, S6-212398, S6-212435                       | 0.1.0       |
+| 2021-11        | SA6#46-e     |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-212661, S6-212758, S6-212800                       | 0.2.0       |
+| 2022-02        | SA6#47-e     |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-220103                                             | 0.3.0       |
+| 2022-04        | SA6#48-e     |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-220904, S6-220971                                  | 0.4.0       |
+| 2022-05        | SA6#49-e     |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-221439, S6-221495                                  | 0.5.0       |
+| 2022-06        | SA#96        | SP-220461 |      |     |     | Presentation for information at SA#96                                                                       | 1.0.0       |
+| 2022-07        | SA6#49-bis-e |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-221757, S6-221758, S6-221928                       | 1.1.0       |
+| 2022-08        | SA6#50-e     |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-222428, S6-222429, S6-222537, S6-222538            | 1.2.0       |
+| 2022-10        | SA6#51-e     |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-222650, S6-222839, S6-222840, S6-223021, S6-223022 | 1.3.0       |
+| 2022-11        | SA6#52       |           |      |     |     | Implementation of the following pCRs approved by SA6: S6-223390, S6-223633                                  | 1.4.0       |
+| 2022-12        | SA#98-e      | SP-221222 |      |     |     | Submitted for Approval at SA#98-e                                                                           | 2.0.0       |
+| 2022-12        | SA#98-e      | SP-221222 |      |     |     | MCC Editorial update for publication after TSG SA approval (SA#98-e)                                        | 18.0.0      |
+| 2023-03        | SA#99        | SP-230299 | 0001 | 1   | 2   | FS eV2XAPP2 solution #4 naming correction                                                                   | 18.1.0      |

marked/Rel-18/23_series/23958/raw.md

@@ -0,0 +1,615 @@
+
+
+# 3GPP TR 23.958 V18.0.0 (2023-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Edge Application Standards in 3GPP and Alignment with External Organizations; (Release 18)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring a stylized '5G' in black with three green curved lines above the '5'.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized black font with a red signal icon below the 'G'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                                           |           |
+|-------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                            | 4         |
+| Introduction .....                                                                        | 5         |
+| 1 Scope.....                                                                              | 6         |
+| 2 References.....                                                                         | 6         |
+| 3 Definitions of terms, symbols and abbreviations .....                                   | 7         |
+| 3.1 Terms.....                                                                            | 7         |
+| 3.2 Symbols.....                                                                          | 7         |
+| 3.3 Abbreviations .....                                                                   | 7         |
+| 4 Related work in other SDOs .....                                                        | 8         |
+| 4.1 General .....                                                                         | 8         |
+| 4.2 GSMA OPG .....                                                                        | 8         |
+| 4.3 ETSI ISG MEC .....                                                                    | 8         |
+| 5 Alignment of EDGEAPP with ETSI MEC .....                                                | 10        |
+| 5.1 General .....                                                                         | 10        |
+| 5.2 Relationship between EDGEAPP and ETSI MEC architectures .....                         | 10        |
+| 5.3 EDGE-3 and Mp1 reference points.....                                                  | 11        |
+| 5.3.1 EASProfile and AppInfo .....                                                        | 11        |
+| 5.4 EDGE-9 and Mp3 reference points.....                                                  | 12        |
+| 5.5 CAPIF and MEC service API management.....                                             | 13        |
+| 5.6 Support for Federation .....                                                          | 13        |
+| 5.6.1 EDGEAPP .....                                                                       | 13        |
+| 5.6.2 ETSI MEC .....                                                                      | 13        |
+| 6 Alignment of EDGEAPP with GSMA OP .....                                                 | 13        |
+| 6.1 General .....                                                                         | 13        |
+| 6.2 Relationship between EDGEAPP architecture and GSMA OPG reference architecture .....   | 13        |
+| 7 Deployment Considerations.....                                                          | 14        |
+| 7.1 General .....                                                                         | 14        |
+| 7.2 Deployment option of EDGEAPP and ETSI MEC using CAPIF.....                            | 15        |
+| 8 Conclusions.....                                                                        | 17        |
+| <b>Annex A: Mapping roles between EDGEAPP architecture and GSMA OPG architecture.....</b> | <b>19</b> |
+| <b>Annex B(informative): Change history .....</b>                                         | <b>21</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+**shall** indicates a mandatory requirement to do something
+
+**shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+**should** indicates a recommendation to do something
+
+**should not** indicates a recommendation not to do something
+
+**may** indicates permission to do something
+
+**need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+**can** indicates that something is possible
+
+**cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+
+**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+
+|                  |                                                                                                                                                                      |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>might</b>     | indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document     |
+| <b>might not</b> | indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document |
+
+In addition:
+
+|               |                                                                                   |
+|---------------|-----------------------------------------------------------------------------------|
+| <b>is</b>     | (or any other verb in the indicative mood) indicates a statement of fact          |
+| <b>is not</b> | (or any other negative verb in the indicative mood) indicates a statement of fact |
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- Introduction
+
+This TR provides recommendations on alignment and deployment aspects of EDGEAPP with ETSI MEC and GSMA Operator Platform (OP).
+
+# --- 1 Scope
+
+This TR provides the recommendations for the alignment of EDGEAPP architecture with ETSI MEC reference architecture and GSMA Operator Platform (OP) for the industry stakeholders.
+
+This document provides recommendations of using specifications from 3GPP, ETSI ISG MEC and GSMA OPG to deploy an aligned edge system.
+
+The present document is based on 3GPP TS 23.558 [2].
+
+# --- 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.558: "Architecture for enabling Edge Applications".
+- [3] GSMA PRD OPG.02 - "Operator Platform Telco Edge Requirements Version 5.0", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/07/OPG.02-v5.0-Operator-Platform-Requirements-and-Architecture.pdf>.
+- [4] ETSI GS MEC 003 (V3.1.1), "Multi-access Edge Computing (MEC); Framework and Reference Architecture".
+- [5] ETSI GS MEC 011 (V3.1.1), "Multi-access Edge Computing (MEC); Edge Platform Application Enablement ".
+- [6] ETSI GS MEC 040 (V3.1.1), "Multi-access Edge Computing (MEC); Federation enablement APIs ".
+- [7] ETSI GS MEC 021 (V2.2.1), "Multi-access Edge Computing (MEC); Application Mobility Service API".
+- [8] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management".
+- [9] ETSI GS MEC 010-2 (V2.2.1), "Multi-access Edge Computing (MEC); MEC Management; Part 2: Application lifecycle, rules and requirements management".
+- [10] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs ".
+- [11] ETSI GR MEC 031 (V3.1.1), "Multi-access Edge Computing (MEC); MEC 5G Integration ".
+- [12] GSMA PRD OPG.03 - "Southbound Interface Network Resources APIs Version 3.0 ", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/07/OPG.03-v3.0-Southbound-Interface-Network-Resources-APIs.pdf>.
+- [13] GSMA PRD OPG.04 - "East-Westbound Interface APIs Version 3.0 ", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/07/OPG.04-v3.0-GSMA-Operator-Platform-Group-East-Westbound-Interface-APIs-Version-3.0.pdf>.
+
+- [14] GSMA PRD OPG.05 - "User-Network Interface APIs Version 1.0 ", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/03/GSMA-Operator-Platform-Group-User-Network-Interface-APIs-v1.pdf>.
+- [15] 3GPP TS 23.501: "System architecture for the 5G System (5GS)".
+- [16] ETSI White Paper #36 – "Harmonizing standards for edge computing - A synergized architecture leveraging ETSI ISG MEC and 3GPP specifications", [https://www.etsi.org/images/files/ETSIWhitePapers/ETSI\\_wp36\\_Harmonizing-standards-for-edge-computing.pdf](https://www.etsi.org/images/files/ETSIWhitePapers/ETSI_wp36_Harmonizing-standards-for-edge-computing.pdf).
+- [17] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |               |
+|----------|---------------|
+| <symbol> | <Explanation> |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|       |                                                 |
+|-------|-------------------------------------------------|
+| AC    | Application Client                              |
+| AEF   | API Exposing Function                           |
+| AF    | Application Function                            |
+| AMF   | API Management Function                         |
+| API   | Application Program Interface                   |
+| APF   | API Publishing Function                         |
+| AS    | Application Server                              |
+| CAPIF | Common API Framework                            |
+| CCF   | CAPIF Core Function                             |
+| CER   | Capabilities Exposure Role                      |
+| EAS   | Edge Application Server                         |
+| ECS   | Edge Configuration Server                       |
+| ECSP  | Edge Computing Service Provider                 |
+| EDN   | Edge Data Network                               |
+| EEC   | Edge Enabler Client                             |
+| EEL   | Edge Enabler layer                              |
+| EES   | Edge Enabler Server                             |
+| ETSI  | European Telecommunications Standards Institute |
+| MEC   | Multi-access Edge Computing                     |
+| MEP   | MEC Platform                                    |
+| NaaS  | Network-as-a-Service                            |
+| NSaaS | Network Slice-as-a-Service                      |
+| OP    | Operator Platform                               |
+| OPG   | Operator Platform Group                         |
+
+|        |                                        |
+|--------|----------------------------------------|
+| SBI-NR | Southbound Interface-Network Resources |
+| SNMP   | Stand-Alone Non-Public Network         |
+| SRM    | Service Resource Manager               |
+| UC     | User Client                            |
+| UNI    | User-to-Network Interface              |
+
+# --- 4 Related work in other SDOs
+
+## 4.1 General
+
+This section provides an overview on the existing work in GSMA and ETSI MEC relevant to the EDGEAPP architecture describing the OP roles, existing mapping and alignment aspects provided by GSMA OP and ETSI MEC in clause 4.2 and clause 4.3 respectively.
+
+## 4.2 GSMA OPG
+
+The Operator Platform (OP) as defined by GSMA OPG in GSMA PRD OPG.02 [3], guides the industry to define a common solution for exposing network capabilities and edge compute resources to enterprise customers and developers allowing monetization of those capabilities. The technical requirements, functional blocks and interfaces characteristics of such a generic platform to facilitate access to the Edge Cloud capability of an operator or federation of operators and their partners are provided in GSMA PRD OPG.02 [3]. GSMA PRD OPG.02 [3] also provides mapping of these requirements and architectures to the specifications from certain SDOs.
+
+The integration of OP with the mobile network takes place using the Southbound Interface-Network Resources (SBI-NR) through the set of APIs specified in GSMA PRD OPG.03 [12] which is linked to the corresponding 3GPP-defined APIs. GSMA PRD OPG.04 [13] specifies the set of APIs for the interactions/operations over the East/West Bound Interface (E/WBI), which enables an OP to share network and edge capabilities with other OP(s). The E/WBI interactions enable the management of a federation (i.e. creation/update/removal), management of the application onboarding in the federation, edge node discovery, etc. The APIs for the interactions between OP and the User Client (UC) are provided in GSMA PRD OPG.05 [14]. The interactions between OP and the User Client (UC) are supported by the User-to-Network Interface (UNI), allowing the UC to discover the existence of an Edge Cloud service, to register to the OP's Service Resource Manager (SRM), to trigger the selection of a cloudlet (a point of presence for the Edge Cloud offering a set of resources at a particular location as specified in GSMA PRD OPG.02 [3]) by the OP, to trigger the instantiation of an application instance on the selected cloudlet.
+
+## 4.3 ETSI ISG MEC
+
+Figure 4.3-1 shows the MEC reference architecture as specified by ETSI ISG MEC. This reference architecture describes the functional elements that comprise the multi-access edge system and the reference points between them. It consists of MEC host and MEC management system necessary to run MEC Applications within an operator network or a subset of an operator network.
+
+The MEC platform is the collection of essential functionalities required to run MEC applications on a particular Virtualisation infrastructure and enable them to provide and consume MEC services.
+
+MEC applications are instantiated on the Virtualisation infrastructure of the MEC host based on configuration or requests validated by the MEC management. An already instantiated MEC application can optionally register with MEC platform. The application registration procedure allows an authorized MEC application instance to provide its information to the MEC platform [5].
+
+The Mp1 reference point between the MEC platform and the MEC applications provides service registration, service discovery, and communication support for services. It also provides other functionality such as application availability, session state relocation support procedures, traffic rules and DNS rules activation, access to persistent storage and time of day information, etc.
+
+The Mp3 reference point between MEC platforms is used for control communication between MEC platforms.
+
+ETSI ISG MEC also provides Multi-access system reference architecture variants for the deployment in an NFV environment and for MEC federation [4] as shown in Figure 4.3-2. In [6], ETSI ISG MEC specifies "Federation enablement APIs " that enable the shared usage of MEC services and applications across different systems (e.g., MEC system, Cloud system).
+
+![Figure 4.3-1: Multi-access Edge System reference architecture diagram showing the hierarchy from CFS portal and Device app down to MEC host and Virtualisation infrastructure manager.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+This diagram illustrates the Multi-access Edge System reference architecture. It is divided into two main levels: the **MEC system level** and the **MEC host level**.
+
+- MEC system level:**
+  - At the top, the **CFS portal** connects to the **Operations Support System** via the **Mx1** interface.
+  - A **Device app** connects to a **User app LCM proxy** via the **Mx2** interface.
+  - The **User app LCM proxy** connects to the **Operations Support System** via the **Mm8** interface and to the **MEC orchestrator** via the **Mm9** interface.
+  - The **Operations Support System** connects to the **MEC orchestrator** via the **Mm1** interface.
+- MEC host level:**
+  - The **MEC orchestrator** connects to the **MEC platform manager** via the **Mm2** and **Mm3** interfaces.
+  - The **MEC platform manager** connects to the **Virtualisation infrastructure manager** via the **Mm6** and **Mm4** interfaces.
+  - The **Virtualisation infrastructure manager** connects to the **MEC host** via the **Mm7** interface.
+  - The **MEC host** contains a **MEC platform** which includes a **Service registry**, **Traffic rules control**, and **DNS handling** components.
+  - On the **MEC platform**, there are three **MEC App** instances, one of which is labeled **Service MEC App**. These connect to the **Service registry** via the **Mp1** interface.
+  - The **MEC platform** also contains a **Data plane** component.
+  - The **Data plane** connects to the **Virtualisation infrastructure** via the **Mp2** interface.
+  - An **Other MEC platform** connects to the **MEC host** via the **Mp3** interface.
+
+Figure 4.3-1: Multi-access Edge System reference architecture diagram showing the hierarchy from CFS portal and Device app down to MEC host and Virtualisation infrastructure manager.
+
+Figure 4.3-1: Multi-access Edge System reference architecture
+
+![Figure 4.3-2: Multi-access Edge System reference architecture variant for MEC federation, adding MEC federator components and interfaces (Mfm, Mff) to the architecture.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+This diagram shows a variant of the reference architecture for MEC federation. It builds upon the structure of Figure 4.3-1 with additional components and interfaces:
+
+- The **MEC orchestrator** now connects to a **MEC federator** via the **Mfm** interface.
+- The **MEC federator** contains two sub-components: **MEC federation manager** and **MEC federation broker**.
+- The **MEC federator** connects to an **Other MEC federator** via the **Mff** interface.
+- The **Other MEC federator** is part of an **Other MEC system**.
+- All other interfaces and components remain consistent with Figure 4.3-1.
+
+Figure 4.3-2: Multi-access Edge System reference architecture variant for MEC federation, adding MEC federator components and interfaces (Mfm, Mff) to the architecture.
+
+Figure 4.3-2: Multi-access Edge System reference architecture variant for MEC federation
+
+# 5 Alignment of EDGEAPP with ETSI MEC
+
+## 5.1 General
+
+An early effort on alignment between 3GPP EDGEAPP and ETSI MEC was initiated during Rel-17, and a summary is available in a white paper published by ETSI - "Harmonizing standards for edge computing - A synergized architecture leveraging ETSI ISG MEC and 3GPP specifications" [16].
+
+Clause 5.2 provides the relationship between EDGEAPP and ETSI MEC architectures. Clause 5.3 provides the mapping of EAS Profile and AppInfo to allow application registration across the platforms. Clause 5.4 provides description for EDGE-9 and Mp3 reference points. Clause 5.5 provides the description for CAPIF and MEC service API management.
+
+## 5.2 Relationship between EDGEAPP and ETSI MEC architectures
+
+Figure 5.2-1 provides the relationship of ETSI ISG MEC architecture with EDGEAPP architecture.
+
+![Figure 5.2-1: Relationship between EDGEAPP and ETSI MEC architectures. The diagram shows the interaction between a UE (User Equipment) and a 3GPP Core Network, and an ETSI MEC architecture. The UE contains Application Clients(s) and an Edge Enabler Client (EEC). The 3GPP Core Network contains EAS (Edge Application Server) and MEC Application. The ETSI MEC architecture includes MEC Platform Manager, MEC Orchestrator, MEC Federator, User app LCM proxy, Operation Support System (OSS), Customer Facing Service (CFS) Portal, and Device app. Interfaces are labeled as EDGE-7, EDGE-1, EDGE-2, EDGE-6, EDGE-9/Mp3, EDGE-4, EDGE-8, EDGE-10, Mm5, Mm3, Mm2, Mm1, Mm8, Mm9, Mx1, Mx2, and Mff. A legend indicates that ellipses group two interfaces, EDGE* depicts 3GPP SA6 interfaces, and Mp*, Mx*, Mm* and Mf* depict ETSI MEC interfaces.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg)
+
+Figure 5.2-1: Relationship between EDGEAPP and ETSI MEC architectures. The diagram shows the interaction between a UE (User Equipment) and a 3GPP Core Network, and an ETSI MEC architecture. The UE contains Application Clients(s) and an Edge Enabler Client (EEC). The 3GPP Core Network contains EAS (Edge Application Server) and MEC Application. The ETSI MEC architecture includes MEC Platform Manager, MEC Orchestrator, MEC Federator, User app LCM proxy, Operation Support System (OSS), Customer Facing Service (CFS) Portal, and Device app. Interfaces are labeled as EDGE-7, EDGE-1, EDGE-2, EDGE-6, EDGE-9/Mp3, EDGE-4, EDGE-8, EDGE-10, Mm5, Mm3, Mm2, Mm1, Mm8, Mm9, Mx1, Mx2, and Mff. A legend indicates that ellipses group two interfaces, EDGE\* depicts 3GPP SA6 interfaces, and Mp\*, Mx\*, Mm\* and Mf\* depict ETSI MEC interfaces.
+
+**Figure 5.2-1: Relationship between EDGEAPP and ETSI MEC architectures**
+
+Details about MEC entities (MEC Platform, MEC Application, MEC Platform Manager, MEC Orchestrator, MEC Federator, OSS and CFS) can be found in ETSI GS MEC 003 [4].
+
+In ETSI MEC, MEC Applications and MEC Platform can expose services which can include network services, subject to their availability at the core or access network level.
+
+Both EAS and MEC application are application servers and can provide similar application specific functionalities. EAS utilizes the services of EES as specified in 3GPP TS 23.558 [2] whereas MEC application utilizes the services provided by MEC platform as specified in ETSI GS MEC 003 [4]. The EAS and MEC application can be aligned in an implementation.
+
+**NOTE 1:** The details of the functionalities of application servers are implementation specific.
+
+Both EES and MEC platform provide application support capabilities towards the application servers. The EES and MEC platform and their interfaces can be aligned in an implementation.
+
+The orchestration and management aspects of architecture for enabling edge applications are specified in 3GPP TS 28.538 [8].
+
+## 5.3 EDGE-3 and Mp1 reference points
+
+### 5.3.1 EASProfile and AppInfo
+
+Both EDGEAPP and ETSI MEC supports registration of EAS and MEC application instance with EES and MEC platform respectively. In order to support MEC application instance registration on EES, it is required that registration request includes at least the mandatory IEs that are required for EAS registration, i.e. EAS ID and EAS endpoint. On the other hand, according to ETSI GS MEC 011 [5] the application registration request must include appName.
+
+AppInfo is the data type describing the information exchanged by a MEC application instance at registration to a MEC platform. It is defined in clause 7.1.2.6 of ETSI GS MEC 011 [5] and includes appName as a mandatory IE and endpoint as an optional IE. However, endpoint is mandatory when the AppInfo IE isInsByMec is FALSE and, as stated above, would have to be provided for MEC application instance registration to an EES. The isInsByMec IE of the AppInfo, with type Boolean, indicates whether the application instance is instantiated by a MEC management system. The IE appName can be considered equivalent to EAS ID. Furthermore endpoint can be directly mapped to EAS endpoint and that mapping is explicitly stated in note 2 of Table 7.1.2.6-1 of ETSI GS MEC 011 [5].
+
+Table 5.3.1-1 provides a mapping of MEC attributes to those in the EAS Profile for MEC application registration with EES.
+
+**Table 5.3.1-1: Mapping with EASProfile for MEC application registration with EES**
+
+| Information element           | Status/ Cardinality | Description                                                                                                                                                                                     | Mapped with                                           |
+|-------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| EASID                         | M                   | The identifier of the EAS                                                                                                                                                                       | AppInfo<br>>appName                                   |
+| EAS Endpoint                  | M                   | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS. This information maybe discovered by EEC and exposed to ACs so that ACs can establish contact with the EAS. | AppInfo<br>>endpoint                                  |
+| ACID(s)                       | O                   | Identifies the AC(s) that can be served by the EAS                                                                                                                                              | Not available in case of MEC application registration |
+| EAS Provider Identifier       | O                   | The identifier of the ASP that provides the EAS.                                                                                                                                                | AppInfo<br>>appProvider                               |
+| EAS Type                      | O                   | The category or type of EAS (e.g. V2X)                                                                                                                                                          | AppInfo<br>>appCategory                               |
+| EAS description               | O                   | Human-readable description of the EAS                                                                                                                                                           | AppD<br>>appDescriptor                                |
+| EAS Schedule                  | O                   | The availability schedule of the EAS (e.g. time windows)                                                                                                                                        | Not available in case of MEC application registration |
+| EAS Geographical Service Area | O                   | The geographical service area that the EAS serves. ACs in UEs that are located outside that area shall not be served.                                                                           | Not available in case of MEC application registration |
+| EAS Topological Service Area  | O                   | The EAS serves UEs that are connected to the Core Network from one of the cells included in this service area. ACs in UEs that are located outside this area shall not be served. See possible  | Not available in case of MEC application registration |
+
+|                                         |   |                                                                                                                                                                                                                                                                                                                                       |                                                       |
+|-----------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+|                                         |   | formats in Table 8.2.7-1.                                                                                                                                                                                                                                                                                                             |                                                       |
+| EAS Service KPIs                        | O | Service characteristics provided by EAS, detailed in Table 8.2.5-1                                                                                                                                                                                                                                                                    | Not available in case of MEC application registration |
+| EAS service permission level            | O | Level of service permissions e.g. trial, gold-class supported by the EAS                                                                                                                                                                                                                                                              | Not available in case of MEC application registration |
+| EAS Feature(s)                          | O | Service features e.g. single vs. multi-player gaming service supported by the EAS                                                                                                                                                                                                                                                     | Not available in case of MEC application registration |
+| EAS Service continuity support          | O | Indicates if the EAS supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EAS.                                                                                                                                                                                                         | Not available in case of MEC application registration |
+| General context holding time duration   | O | The time duration that the EAS holds the context before the AC connects to the EAS in case of ACR for service continuity planning. It is an indication of the time the EAS holds the application context for a UE to move to its service area after receiving an ACR notification from the EES following an ACR request from the EEC. | Not available in case of MEC application registration |
+| List of EAS DNAI(s)                     | O | DNAI(s) associated with the EAS. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [15]. It is a subset of the DNAI(s) associated with the EDN where the EAS resides.                                                                                                                          | Not available in case of MEC application registration |
+| List of N6 Traffic Routing requirements | O | The N6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI.                                                                                                                                                                                                                                          | Not available in case of MEC application registration |
+| EAS Availability Reporting Period       | O | The availability reporting period (i.e. heartbeat period) that indicates to the EES how often it needs to check the EAS's availability after a successful registration.                                                                                                                                                               | Not available in case of MEC application registration |
+| EAS Status                              | O | The status of the EAS (e.g. enabled, disabled, etc.)                                                                                                                                                                                                                                                                                  | Not available in case of MEC application registration |
+
+## 5.4 EDGE-9 and Mp3 reference points
+
+EDGE-9 reference point in EDGEAPP architecture is used to provide target EAS discovery to support ACR in case of mobility of user from one EES to another EES. On the other hand, Mp3 reference point between MEC platforms is used for control communication between MEC platforms [4] with a separate application mobility service [7] being provided in support of mobility of users between MEC hosts within a MEC system. Currently, ETSI MEC has not specified APIs over Mp3.
+
+## 5.5 CAPIF and MEC service API management
+
+CAPIF is the Common API Framework for northbound APIs specified in 3GPP TS 23.222 [10]. The Edge Enabler Layer supports CAPIF for northbound API exposure of edge service APIs as specified in 3GPP TS 23.558 [2]. The MEC platform supports CAPIF in the form of MEC service management API as specified in ETSI GS MEC 011 [5]. The CAPIF APIs are similar to the MEC service management APIs and the mapping is described in ETSI GS MEC 011 [5].
+
+## 5.6 Support for Federation
+
+### 5.6.1 EDGEAPP
+
+EDGE-9 and EDGE-10 reference points are used to support federation functionalities as per clause 8.17 and clause 8.18 of 3GPP TS 23.558 [2]. EDGE-9 reference point in EDGEAPP architecture is used to discover EAS from the EES of the partner ECSP for edge node sharing. EDGE-10 reference point in EDGEAPP architecture is used for ECS registration, ECS discovery via ECS-ER and Service provisioning information retrieval from ECS-ER in order to provide support for roaming, federation and edge node sharing. EDN information is exchanged between ECSs/ECS-ERs using EDGE-10 reference point.
+
+Further, application life cycle management for federation is specified in 3GPP TS 28.538 [17]. Once application server is instantiated, it registers with EES, which in turn registers with ECS. The EDN information contains EDN connection information, list of EES along with EASIDs, provider's ID, endpoint information and other required details.
+
+### 5.6.2 ETSI MEC
+
+The MEC federator (MEF) as described in clause 7.1.9 of ETSI GS MEC 003 [4] enables a MEC federation between MEC systems. Mff reference point is defined between MEFs within the MEC federation for sharing information, such as MEC system information that includes MEC system ID, MEC system name, MEC system provider and MEF endpoint information. The federation enablement service is summarised in clause 5.2.1 of ETSI GS MEC 040 [6] and enables the shared usage of MEC services and applications across different systems.
+
+# --- 6 Alignment of EDGEAPP with GSMA OP
+
+## 6.1 General
+
+Clause 6 describes the alignment between 3GPP EDGEAPP and GSMA OP by illustrating the mapping relationship between 3GPP EDGEAPP architecture and GSMA OP architecture (which includes ECS, EES and Edge management system) as described in clause 6.2.
+
+## 6.2 Relationship between EDGEAPP architecture and GSMA OPG reference architecture
+
+Figure 6.2-1 illustrates the relationship between EDGEAPP architecture and GSMA OPG reference architecture [3].
+
+![Figure 6.2-1: Relationship between EDGEAPP architecture and GSMA OPG reference architecture. The diagram shows the interaction between a UE, 3GPP CN, and Operator platforms. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP CN is connected to the UE via EDGE-7 and to the Operator platform via EDGE-2 and EDGE-8. The Operator platform contains an Edge Enabler Server(s) and an Edge Configuration Server. The Edge Enabler Server(s) is connected to the UE via EDGE-1 and EDGE-4, and to the 3GPP CN via EDGE-3. The Edge Configuration Server is connected to the UE via EDGE-5 and to the 3GPP CN via EDGE-6. The ECSP Management system is connected to the Edge Enabler Server(s) via EDGE-9 and EDGE-10. The diagram also shows the relationship between the Operator platform and the ECSP Management system via the OP SBI-CR interface.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+Figure 6.2-1: Relationship between EDGEAPP architecture and GSMA OPG reference architecture. The diagram shows the interaction between a UE, 3GPP CN, and Operator platforms. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP CN is connected to the UE via EDGE-7 and to the Operator platform via EDGE-2 and EDGE-8. The Operator platform contains an Edge Enabler Server(s) and an Edge Configuration Server. The Edge Enabler Server(s) is connected to the UE via EDGE-1 and EDGE-4, and to the 3GPP CN via EDGE-3. The Edge Configuration Server is connected to the UE via EDGE-5 and to the 3GPP CN via EDGE-6. The ECSP Management system is connected to the Edge Enabler Server(s) via EDGE-9 and EDGE-10. The diagram also shows the relationship between the Operator platform and the ECSP Management system via the OP SBI-CR interface.
+
+**Figure 6.2-1: Relationship between EDGEAPP architecture and GSMA OPG reference architecture**
+
+EDGE-1 and EDGE-4 reference points can support similar function(s) as OP's User-Network interface (UNI), providing the Edge Enabler Client (corresponding to Edge/User Client in OP) with the information required to access the edge services. EDGE-1/EDGE-4 neither impact nor overlap with other existing 3GPP interfaces between the UE and the network, catering to the OP's requirements on UNI.
+
+EDGE-2 and EDGE-8 reference points can support similar function(s) as OP's Southbound interface (SBI), through which the edge enabler layer (corresponding to the operator platform) access the 3GPP network capabilities and services (e.g. SCEF/NEF). Specifically, EDGE-2 and EDGE-8 cater to the requirements of the SBI-NetworkResource interface. ECSP management system as specified in 3GPP TS 28.538 [8] caters to the requirements of OP's SBI-CloudResource interface.
+
+EDGE-3 reference point can support similar function(s) as OP's Northbound interface (NBI), exposing the capabilities of Edge Enabler Server to the Edge Application Servers (EAS) hosted on the edge. OP's NBI also expands capabilities exposure to ASPs, for example to on-board applications to be deployed as EASs based on specific criteria.
+
+EDGE-9 and EDGE-10 reference point can support similar function(s) as OP's East/Westbound interface (E/WBI), allowing the edge enabler layer to interact within and beyond its domains e.g., between operator platforms. OP's E/WBI focuses on use cases like user and application roaming or resource sharing across domains.
+
+# 7 Deployment Considerations
+
+## 7.1 General
+
+Figure 7.1-1 shows the EDGEAPP and ETSI MEC aligned Application Server and platform deployment. The depicted Edge platform consists of functionalities provided by both EES and MEC platform. The EES and MEC platform are functionally aligned in the implementation of the Edge platform. The depicted Application Server implements the functionalities of an Edge Application Server or MEC application instance or both.
+
+![Diagram of EDGEAPP and ETSI MEC aligned Application Server and platform deployment. Two Application Servers (EAS and/or MEC app instance) are connected to Edge platforms via CAPIF-1(e) & CAPIF-2(e) interfaces. The Edge platforms are interconnected via EDGE-9/Mp3 and CAPIF-6(e) interfaces.](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+The diagram illustrates a deployment scenario where two Application Servers (EAS and/or MEC app instance) are connected to Edge platforms. Each Application Server is connected to an Edge platform via a CAPIF-1(e) & CAPIF-2(e) interface, which is also labeled as EDGE-3/Mp1. The two Edge platforms are interconnected via an EDGE-9/Mp3 interface, which is also labeled as CAPIF-6(e).
+
+Diagram of EDGEAPP and ETSI MEC aligned Application Server and platform deployment. Two Application Servers (EAS and/or MEC app instance) are connected to Edge platforms via CAPIF-1(e) & CAPIF-2(e) interfaces. The Edge platforms are interconnected via EDGE-9/Mp3 and CAPIF-6(e) interfaces.
+
+**Figure 7.1-1: EDGEAPP and ETSI MEC aligned Application Server and platform deployment.**
+
+EDGE-3 is provided to Application Servers presenting themselves to the Edge platform as Edge Application Servers. Mp1 is provided for Application Servers presenting themselves to the Edge platform as MEC application instances.
+
+An Edge platform adopting the CAPIF framework could provide the capabilities offered by EDGE-3 and Mp1 through utilisation of CAPIF-1 (/CAPIF-1e) and CAPIF-2 (/CAPIF-2e) to provide a unified service. For instance, a mapping of the MEC service management API to the 3GPP CAPIF API is presented in Annex B of ETSI GS MEC 011 [5].
+
+EDGE-9 and Mp3 provide services required for interconnectivity between Edge platforms. EDGE-9 provides the interconnectivity required by Edge Enabler Servers, whilst Mp3 provides the interconnectivity required by MEC platforms.
+
+An Edge platform adopting the CAPIF framework could provide the capabilities offered by EDGE-9 and Mp3 through utilisation of CAPIF-6 (/CAPIF-6e) to provide a unified service.
+
+NOTE: APIs supported over Mp3 have not currently been specified by ETSI MEC.
+
+Management aspects relating to application server and platform management are captured in 3GPP TS 28.538 [8] (EDGEAPP entity specific) and ETSI GS MEC 010-2 [9] (MEC entity specific), where the commonality is that both specify ETSI NFV MANO for performing lifecycle management functions. Management related interfaces are not depicted in Figure 7.1-1.
+
+## 7.2 Deployment option of EDGEAPP and ETSI MEC using CAPIF
+
+3GPP provides a framework for supporting common capabilities for northbound APIs (e.g., onboarding, authentication, authorization, discovery, auditing, etc.) through the common API framework (CAPIF) as specified in 3GPP TS 23.222 [10]. The functional model of CAPIF enables an API invoker to access (and invoke) service APIs and supports API exposing functions in publishing the API towards the API invokers. To enable the common supporting capabilities among API invokers and API providers, the CCF is introduced as the functional entity in charge of, among other tasks, authenticating an API invoker, providing authorization for the API invoker prior to accessing the service API, publishing, storing, and supporting the discovery of service APIs information, etc.
+
+As from Annex A in TS 23.558 [2], an EAS may assume the role of:
+
+- API invoker: for accessing northbound APIs exposed by SCEF/NEF or consuming service APIs offered by other EASs or EES, or
+- API provider: exposing its service APIs for consumption by other API invokers,
+
+whereas the EES may act like AEF and CCF (the latter being dispensable if, e.g., a centralized instance of CCF is available, see Clause A.5.3 in 3GPP TS 23.558 [2]).
+
+Additionally, as from Annex B in ETSI GR MEC 031 [11], a MEC App may assume the role of:
+
+- API invoker: for accessing northbound APIs exposed by SCEF/NEF or consuming MEC services advertised by the MEP, or
+- API provider: registering (publishing) its service APIs and exposing them for consumption by other API invokers,
+
+whereas the MEP may assume the role of API provider, CCF, and API invoker. A MEC service produced by a MEC App or MEP can be mapped into the API provider domain in CAPIF.
+
+Since the different functional entities of both EDGEAPP and ETSI MEC may assume several roles, the number of scenario combinations is high. Therefore, rather than providing an exhaustive study of possible CAPIF-based deployments, some generic scenarios are presented in Figure 7.2-1.
+
+In Figure 7.2-1, it is assumed that:
+
+- Edge Platforms (e.g., complying with MEC platform and/or EDGEAPP) can co-exist in the network within the same PLMN trust domain,
+- API invokers want to access MEC services, or API invokers want to consume EDGEAPP services,
+- Extensible transport for service invocations (Different protocol and data formats including REST-HTTP are supported) is used.
+
+![Figure 7.2-1: Illustration of deployment option using CAPIF. The diagram shows a central (API invoker) e.g., EAS/MEC App at the top. Below it, two Edge platforms are shown. The left Edge platform contains CCF 1, which manages Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to EAS (Edge App Server) via CAPIF-3, CAPIF-4, and CAPIF-5. The right Edge platform contains CCF 2, which manages MEC Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to MEC App via CAPIF-2, CAPIF-3, CAPIF-4, and CAPIF-5. Both CCF 1 and CCF 2 connect to the central API invoker via CAPIF-2 and CAPIF-1. CCF 1 and CCF 2 are also connected via CAPIF-6. The entire system is within a PLMN trust domain.](b90144cfbb81a2d610d920240fda689d_img.jpg)
+
+Figure 7.2-1: Illustration of deployment option using CAPIF. The diagram shows a central (API invoker) e.g., EAS/MEC App at the top. Below it, two Edge platforms are shown. The left Edge platform contains CCF 1, which manages Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to EAS (Edge App Server) via CAPIF-3, CAPIF-4, and CAPIF-5. The right Edge platform contains CCF 2, which manages MEC Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to MEC App via CAPIF-2, CAPIF-3, CAPIF-4, and CAPIF-5. Both CCF 1 and CCF 2 connect to the central API invoker via CAPIF-2 and CAPIF-1. CCF 1 and CCF 2 are also connected via CAPIF-6. The entire system is within a PLMN trust domain.
+
+**Figure 7.2-1: Illustration of deployment option using CAPIF**
+
+On the left-hand side of Figure 7.2-1, the Edge Platform implements CCF 1 to manage the Service APIs exposed by EAS and EES. EAS implements the API Provider domain functions to expose EAS Service APIs to EASs (and ETSI MEC Applications acting as API invokers). The Edge Platform implements API Provider domain functions to expose EES Service APIs (e.g., UE location API, AC information exposure API, etc.) to API invokers (e.g., EASs, ETSI MEC Applications).
+
+On the right-hand side of Figure 7.2-1, the Edge Platform implements an instance of CCF (i.e., CCF 2) to manage the MEC Services exposed by MEP and MEC App. Both MEP and MEC App implement API Provider domain functions to expose MEC Services via CAPIF-2.
+
+CCF 1 and CCF 2 interact via CAPIF-6 reference point, which supports publishing the service APIs information and discovering the service APIs information on both platforms. The CCF 1 and the CCF 2 publish the service API provided by its connected API exposing function(s) and obtains the service API information provided by other CCF.
+
+An API invoker (e.g., EAS or MEC App) connected to the any of the CCF can discover and invoke service APIs provided by the API exposing function connected to the other CCF.
+
+In Figure 7.2-2, another possible deployment scenario (out-of-many) is illustrated in which:
+
+- Two ECSPs are present with different trust domains,
+- A PLMN operator (or SNPN provider) deploys API provider functions via the NEF to expose northbound APIs, as illustrated in Section B.2.2.3 in 3GPP TS 23.222 [10],
+- An API invoker wants to access MEC services or EES services or wants to consume network capabilities,
+
+Extensible for service invocations (Different protocol and data formats including REST-HTTP are supported) transport is used.
+
+![Figure 7.2-2: Illustration of deployment MEC using CAPIF across several trust domains. The diagram shows two Edge Service Providers (ECSP #1 and ECSP #2) connected via a central API invoker (MEC App). ECSP #1 contains an Edge platform with Service APIs, CAPIF APIs, and EAS Service APIs, connected to EDGE-3 and EDGE-9. ECSP #2 contains an Edge platform with MEC Service APIs, CAPIF APIs, and Service APIs, connected to EDGE-2 and EDGE-9. The API invoker connects to ECSP #1 via CAPIF-2e and to ECSP #2 via CAPIF-1e and CAPIF-2e. The NEF - 5GS is shown within the PLMN/SNPN trust domain, connected to EDGE-2 via CAPIF-7e.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg)
+
+The diagram illustrates a deployment scenario for MEC using CAPIF across multiple trust domains. At the top, an (API invoker) MEC App is shown. It has connections to two Edge Service Providers (ECSPs). ECSP #1 is on the left and contains an 'Edge platform' box. Inside this box, there are three groups: 'Service APIs' (with API exposing, publishing, and management functions), 'CAPIF APIs' (containing 'CCF 1'), and 'EAS Service APIs' (with API exposing, publishing, and management functions). This platform is connected to 'EDGE-3' and 'EDGE-9'. ECSP #2 is on the right and also contains an 'Edge platform' box. Inside, there are 'MEC Service APIs' (with API exposing, publishing, and management functions, connected to a 'MEC App'), 'CAPIF APIs' (containing 'CCF 2'), and 'Service APIs' (with API exposing, publishing, and management functions). This platform is connected to 'EDGE-2' and 'EDGE-9'. The API invoker connects to ECSP #1 via 'CAPIF-2e' and to ECSP #2 via 'CAPIF-1e' and 'CAPIF-2e'. Reference points 'Mp1' and 'Mp3' are indicated. Below ECSP #1, 'EDGE-2' is connected to a 'NEF - 5GS' box. The NEF contains 'Service APIs' (with API exposing, publishing, and management functions) and is connected to 'EDGE-2' via 'CAPIF-7e'. A vertical double-headed arrow labeled 'PLMN/SNPN trust domain' spans the NEF and EDGE-2 area.
+
+Figure 7.2-2: Illustration of deployment MEC using CAPIF across several trust domains. The diagram shows two Edge Service Providers (ECSP #1 and ECSP #2) connected via a central API invoker (MEC App). ECSP #1 contains an Edge platform with Service APIs, CAPIF APIs, and EAS Service APIs, connected to EDGE-3 and EDGE-9. ECSP #2 contains an Edge platform with MEC Service APIs, CAPIF APIs, and Service APIs, connected to EDGE-2 and EDGE-9. The API invoker connects to ECSP #1 via CAPIF-2e and to ECSP #2 via CAPIF-1e and CAPIF-2e. The NEF - 5GS is shown within the PLMN/SNPN trust domain, connected to EDGE-2 via CAPIF-7e.
+
+**Figure 7.2-2: Illustration of deployment MEC using CAPIF across several trust domains**
+
+In this scenario, Edge platform deployed by ECSP#1 acts as a proxy for accessing 5GS capabilities, enabling in that manner topology hiding for the API invoker accessing the service APIs from outside the PLMN/SNPN trust domain.
+
+NOTE: The details about CAPIF-related reference points within the same trust domains have been removed for the sake of readability.
+
+ECSP#1 applies topology hiding and provides the AEF details of the Edge platform for invocation of NEF services to ECSP#2. The API invoker onboarded on ECSP#2 is able to discover the NEF services offered by ECSP#1 (supported by CAPIF-1 and CAPIF-6e). The API invoker performs API invocation on the AEF in ECSP#1's Edge platform which further forwards or routes the API invocation to the NEF.
+
+# 8 Conclusions
+
+The following is the conclusion on the alignment of 3GPP Edge Enabler Layer, ETSI MEC and GSMA OP architectures:
+
+1. CAPIF framework is aligned between 3GPP EDGEAPP and ETSI MEC architectures. An Edge application acting as a CAPIF API invoker can discover and invoke Edge platform services from 3GPP EDGEAPP, and ETSI MEC.
+2. For Alignment of 3GPP EDGEAPP with ETSI MEC:
+
+- a) EAProfile and AppInfo are mapped for mandatory information elements. The mapping between EAProfile and AppInfo can be used for aligning EES and MEC platform and their interfaces in an implementation.
+  - b) Using mapping between EAProfile and AppInfo, MEC application instance can register to EES by providing mandatory IEs.
+  - c) 3GPP EDGEAPP architecture and ETSI MEC architecture are functionally aligned.
+3. For Alignment of 3GPP EDGEAPP with GSMA OP:
+- a) GSMA OPG specified edge computing related use cases, requirements (e.g. roaming, federation and edge node sharing) for Operator Platform can be realized by 3GPP EDGEAPP.
+
+# Annex A: Mapping roles between EDGEAPP architecture and GSMA OPG architecture
+
+GSMA Operator Platform Group has published their edge requirements in Operator Platform Telco Edge Requirements [3].
+
+Clause 3 of Operator Platform Telco Edge Requirements [3] provides the OP Roles and Interfaces Reference Architecture. Clause 3.2 of Operator Platform Telco Edge Requirements [3] defines roles along with their key functions.
+
+**Editor's note:** Inputs from 3GPP SA5 is FFS. Below mapping tables will be updated based on the input received from SA5.
+
+The three main roles in the GSMA OP architecture and their mapping with EDGEAPP architecture entity is as follows:
+
+- 1) Capabilities Exposure Role: It enables an Application Provider to operate their applications. Table A-1 shows the scenarios enabled by Capabilities exposure role as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture.
+
+**Table A-1: Capabilities exposure role**
+
+| Interface | Scenario                                    | Description                                                                                                                                                                                                                 | Mapping to 3GPP EDGEAPP   |
+|-----------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| NBI       | Edge Cloud Infrastructure Endpoint Exposure | The Application Provider uses an authenticated and authorized endpoint to carry out scenarios involving application instances on edge clouds;                                                                               |                           |
+|           | Application Onboarding                      | The Application Provider uses the NBI to provide application images and metadata to the OP Federation Broker/Manager Role                                                                                                   |                           |
+|           | Application Metadata/Manifest Submission    | The Application Provider uses the NBI and the metadata model to submit application metadata to the OP and follows defined procedures to extend the metadata model specification                                             |                           |
+|           | Application CI/CD Management DevOps         | The Application Provider integrates the CI/CD framework used to create an application with the OP via NBI APIs (which implies an integration between a CI/CD framework and Application Onboarding and Lifecycle Management) |                           |
+|           | Application Lifecycle Management            | The Application Provider observes and changes the operational state of application instances, including the geographical/network extent of the OP on which application instances may run;                                   |                           |
+|           | Application Resource Consumption Monitoring | The Application Provider observes resource consumption of application instances, using the resource data model                                                                                                              |                           |
+|           | Edge Cloud Resource Catalogue exposure      | The Application Provider inventories edge cloud resources nominally available to application instances                                                                                                                      |                           |
+|           | Network Capabilities exposure               | The Application Provider inventories network capabilities, like Network Analytics, nominally available to application instances                                                                                             | EES (as per clause 8.7.3) |
+
+- 2) Service Resource Manager Role: The Service Resource Manager role in the OP is responsible for managing Cloud and Network resources from the Edge Cloud(s) via the SBI and UNI interfaces. Table A-2 shows typical scenarios enabled by the Service Resource Manager role towards the different interfaces as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture.
+
+**Table A-2: Service Resource Manager Role**
+
+| Interface                                         | Scenario                                                                                                                                                                                    | Mapping to 3GPP EDGEAPP                                                                                                                         |
+|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| SBI                                               | Inventory, Allocation and Monitoring of Compute resources from Edge Cloud Infrastructure via the Southbound Interface – Cloud Resources (SBI-CR);                                           |                                                                                                                                                 |
+|                                                   | Orchestration of Application instances on the Edge Cloud Infrastructure via the SBI-CR interface                                                                                            |                                                                                                                                                 |
+|                                                   | Cloud resource reservation managed by the OP                                                                                                                                                |                                                                                                                                                 |
+|                                                   | Configuring UE traffic management policies to accomplish the application's requirements, or the UE's IP address shall be maintained                                                         |                                                                                                                                                 |
+|                                                   | Exposure of usage and monitoring information to operator's charging engine via the Southbound Interface – Charging functions (SBI-CHF) to enable operators to charge for the OP's services. |                                                                                                                                                 |
+| Southbound Interface – Network Resources (SBI-NR) | Fetch Cloudlet locations based on the mobile network data-plane breakout location                                                                                                           |                                                                                                                                                 |
+|                                                   | Subscribe and receive notifications on UE Mobility events from the network to assist applications                                                                                           | UE mobility events are exposed by NEF (TS 23.502) and EES and ECS subscribes to receive UE mobility notification to assist applications for ACR |
+|                                                   | Configure traffic steering in the Mobile Network towards Applications orchestrated in Edge Clouds                                                                                           | NEF exposes TrafficInfluence service (TS 23.502), EES uses the TrafficInfluence service to steer the traffic (related to traffic influence)     |
+|                                                   | Receive statistics/analytics, e.g. to influence Application placement or mobility decisions                                                                                                 |                                                                                                                                                 |
+|                                                   | Receive information related to the network capabilities, such as QoS, policy, network information, etc                                                                                      | NEF exposes events related to network capabilities, EES and ECS subscribes to receive network capability related information.                   |
+| UNI                                               | Application Instantiation/Termination, e.g. based on triggers from the UNI                                                                                                                  |                                                                                                                                                 |
+|                                                   | Application Endpoint exposure towards User Clients (UC) via the UNI                                                                                                                         | EES (clause 8.4.2 and clause 8.5)                                                                                                               |
+|                                                   | Application Placement decisions, e.g. based on measurements/triggers from the UNI                                                                                                           |                                                                                                                                                 |
+
+- 3) Federation Broker and Federation Manager Roles: The Federation Broker and Manager Roles in the OP are responsible for interfacing with other OPs via the East-West Bound Interface. Table A-3 shows typical scenarios enabled by the Federation Broker and Federation Manager Roles as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture.
+
+**Table A-3: Federation Broker and Federation Manager Roles**
+
+| Interface | Scenario                                                                 | Mapping to 3GPP EDGEAPP                                             |
+|-----------|--------------------------------------------------------------------------|---------------------------------------------------------------------|
+| EWBI      | Federation Interconnection Management                                    |                                                                     |
+|           | Edge Cloud Resource Exposure and Monitoring towards partner OPs          |                                                                     |
+|           | Network and Analytics Capabilities Exposure towards partner OPs          |                                                                     |
+|           | Application Images and Application metadata transfer towards partner OPs |                                                                     |
+|           | Application Instantiation/Termination towards partner OPs                |                                                                     |
+|           | Application Monitoring towards partner OPs                               |                                                                     |
+|           | Edge Cloud Resource Catalogue exposure                                   | EES (Exposing EAS profile) (See NOTE 1)                             |
+|           | Service Availability in visited networks                                 | ECS (Table 8.3.3.3-2 and clause 8.17.2.4 of TS 23.558) (See NOTE 2) |
+
+NOTE 1: Edge Cloud Resource Catalogue may contain information other than EAS profile which is within scope of SA5.  
+NOTE 2: EASIDs are considered as available services in partner ECSP and are exchanged between ECSs of home ECSP and partner ECSP.
+
+Based on the mapping tables in this clause, EES and ECS of 3GPP EDGEAPP architecture can be mapped to take responsibilities of the some roles as defined in GSMA OPG reference architecture.
+
+**Editor's note:** Alignment of EDGEAPP and GSMA OP for ECSP Management System is FFS and requires inputs from SA5.
+
+# Annex B(informative): Change history
+
+| Change history |          |           |    |     |     |                                                                                                                                                      |             |
+|----------------|----------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR | Rev | Cat | Subject/Comment                                                                                                                                      | New version |
+| 2022-08        | SA6#50-e |           |    |     |     | TR Initial Version                                                                                                                                   | 0.0.0       |
+| 2022-09        | SA6#50-e |           |    |     |     | TR Skeleton (as per TR template)                                                                                                                     | 0.0.1       |
+| 2022-09        | SA6#50-e |           |    |     |     | Implementation of the following pCRs approved by SA6: S6-222591, S6-222592                                                                           | 0.1.0       |
+| 2022-10        | SA6#51-e |           |    |     |     | Added Introduction through pCR: S6-222662                                                                                                            | 0.2.0       |
+| 2023-03        | SA6#53   |           |    |     |     | Added background and updated index through pCR: S6-231043 and S6-231078                                                                              | 0.3.0       |
+| 2023-03        | SA6#53   |           |    |     |     | Corrected the mistake in implementing S6-231043                                                                                                      | 0.3.1       |
+| 2023-04        | SA6#54-e |           |    |     |     | Implemented pCR: S6-231508                                                                                                                           | 0.4.0       |
+| 2023-08        | SA6#56   |           |    |     |     | Implemented pCRs: S6-232648, S6-232370, S6-232651, S6-232649, S6-232471, S6-232664, S6-232473                                                        | 0.6.0       |
+| 2023-09        | SA#101   | SP-230986 |    |     |     | Submitted to SA#101 for information                                                                                                                  | 1.0.0       |
+| 2023-10        | SA6#57   |           |    |     |     | Implemented pCRs: S6-233419, S6-233341, S6-233404, S6-233343, S6-233344                                                                              | 1.1.0       |
+| 2023-10        | SA6#57   |           |    |     |     | Editorial correction to add missing version v1.0.0 in the present history table                                                                      | 1.1.1       |
+| 2023-11        | SA6#58   |           |    |     |     | Implemented pCRs: S6-233988, S6-233960, S6-233990, S6-233991, S6-233490, S6-234032, S6-234099, S6-233997, S6-233998, S6-233698, S6-234066, S6-234070 | 1.2.0       |
+| 2023-12        | SA#102   | SP-231538 |    |     |     | Submitted to SA#102 for approval                                                                                                                     | 2.0.0       |
+| 2023-12        | SA#102   | SP-231538 |    |     |     | MCC Editorial update for publication after TSG SA approval (SA#102)                                                                                  | 18.0.0      |