Add files using upload-large-folder tool

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

@@ -0,0 +1,655 @@
+
+
+
+
+
+
+# --- 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 |
+| Annex A (informative): Change history.....                                                | 24 |
+
+# --- 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 subclause 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 subclause 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 |
+
+|                               | P bit | R bit | A bit | Q bit |
+|-------------------------------|-------|-------|-------|-------|
+| HLR Induction State "Induced" | 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. It starts with an 'idle' state, followed by an 'SS request'. A 'general SS_request_handling' block (see sheets 2 and 3) follows. An 'error' decision point leads to an 'error' state if yes, or to 'split request to EBSG' if no. A loop follows: 'take request of first EBSG' (connector 1), 'specific SS_request_handling' (see sheet 4), and 'last EBSG' decision. If 'last EBSG' is no, 'take request of next EBSG' leads back to 'specific SS_request_handling'. If 'last EBSG' is yes, a 'successful for any EBSG' decision follows. If 'successful for any EBSG' is no, an 'error' state is reached. If 'successful for any EBSG' is yes, a 'partial acceptance' state is reached. Both 'partial acceptance' and 'error' states lead to an 'idle' state (connector 1).](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+**Process SS\_REQUEST\_WITH\_BS\_GROUP** 311\_211(1)
+
+```
+graph TD; idle1([idle]) --> SS_request[/SS request/]; SS_request --> general[general SS_request_handling]; general -.-> S23[see sheets 2 and 3]; general --> error1{error}; error1 -- yes --> error2[error]; error1 -- no --> split[split request to EBSG]; split --> take1[take request of first EBSG]; take1 --> specific[specific SS_request_handling]; specific -.-> S4[see sheet 4]; specific --> lastEBSG{last EBSG}; lastEBSG -- yes --> successful{successful for any EBSG}; lastEBSG -- no --> takeNext[take request of next EBSG]; takeNext --> specific; take1 -- 1 --> specific; successful -- yes --> partial[partial acceptance]; successful -- no --> error2; partial --> idle2([idle]); error2 --> idle2; idle2 -- 1 --> idle1;
+```
+
+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.
+
+Flowchart for Process SS\_REQUEST\_WITH\_BS\_GROUP. It starts with an 'idle' state, followed by an 'SS request'. A 'general SS\_request\_handling' block (see sheets 2 and 3) follows. An 'error' decision point leads to an 'error' state if yes, or to 'split request to EBSG' if no. A loop follows: 'take request of first EBSG' (connector 1), 'specific SS\_request\_handling' (see sheet 4), and 'last EBSG' decision. If 'last EBSG' is no, 'take request of next EBSG' leads back to 'specific SS\_request\_handling'. If 'last EBSG' is yes, a 'successful for any EBSG' decision follows. If 'successful for any EBSG' is no, an 'error' state is reached. If 'successful for any EBSG' is yes, a 'partial acceptance' state is reached. Both 'partial acceptance' and 'error' states lead to an 'idle' state (connector 1).
+
+**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 an oval connector, followed by a series of decision diamonds: 'SS supported by this entity', 'required parameter missing', 'irrelevant parameter value', 'request applicable for this SS', 'interrogation', and 'SS provisioned'. 'Yes' paths lead to connector '1'. 'No' paths lead to error boxes: 'set error unexpected data value', 'set error data missing', 'set error unexpected data value', 'set error illegal SS operation', and 'set error SS error status', all of which lead to connector '2'. Notes on the right define BS, BSG, and SS, and mention 'Handling of the entire request'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+Procedure general\_SS\_request\_handling
+
+311\_212(2)
+
+```
+graph TD; Start([ ]) --> D1{SS supported by this entity}; D1 -- yes --> D2{required parameter missing}; D1 -- no --> E1[set error unexpected data value]; 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 -- yes --> D5{interrogation}; D4 -- no --> E4[set error illegal SS operation]; D5 -- yes --> C1((1)); D5 -- no --> D6{SS provisioned}; D6 -- yes --> C1; D6 -- no --> E5[set error SS error status]; 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 an oval connector, followed by a series of decision diamonds: 'SS supported by this entity', 'required parameter missing', 'irrelevant parameter value', 'request applicable for this SS', 'interrogation', and 'SS provisioned'. 'Yes' paths lead to connector '1'. 'No' paths lead to error boxes: 'set error unexpected data value', 'set error data missing', 'set error unexpected data value', 'set error illegal SS operation', and 'set error SS error status', all of which lead to connector '2'. Notes on the right define BS, BSG, and SS, and mention 'Handling of the entire request'.
+
+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 with a decision 'any BS provisioned within the BSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'any BS applicable within the same EBSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS requiring password or password registration'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS_request' (To process PW1 as specified in TS GSM 03.11). Then 'Wait_for_PW' (Waiting for indications from process PW1, PW2, PW3 or PW4 as specified in TS GSM 03.11). A parallel block contains 'SS Get Password', 'SS Get New Password', 'SS Get New Password Again', 'SS User Errors', 'SS Password Changed', and 'SS Acknowledge'. 'SS User Errors' leads to 'Set ERROR'. 'SS Get Password' leads to 'SS Get Password' (diamond), then 'Wait for password', then 'SS Get Password_Ack', then 'SS Receive Password' (To processes PW1, PW2, PW3 or PW4 specified in TS GSM 03.11), then 'Wait_for_PW'. All paths lead to a final circle with an X.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg)
+
+Procedure general\_SS\_request\_handling
+
+311\_213(2)
+
+```
+graph TD
+    Start((1)) --> D1{any BS provisioned within the BSG}
+    D1 -- no --> Error1[set error BS Not Provisioned]
+    D1 -- yes --> D2{any BS applicable within the same EBSG}
+    D2 -- no --> Error1
+    D2 -- yes --> D3{SS requiring password or password registration}
+    D3 -- no --> Error1
+    D3 -- yes --> SS_request[/SS_request / To process PW1 as specified in TS GSM 03.11/]
+    SS_request --> Wait_for_PW1([Wait_for_PW / Waiting for indications from process PW1, PW2, PW3 or PW4 as specified in TS GSM 03.11./])
+    Wait_for_PW1 --> ParallelBlock
+    subgraph ParallelBlock [ ]
+        direction TB
+        P1[SS Get Password]
+        P2[SS Get New Password]
+        P3[SS Get New Password Again]
+        P4[SS User Errors]
+        P5[SS Password Changed]
+        P6[SS Acknowledge]
+    end
+    P4 --> Set_ERROR[Set ERROR]
+    P1 --> D4{SS Get Password}
+    D4 --> Wait_for_password([Wait for password])
+    Wait_for_password --> P7[SS Get Password_Ack]
+    P7 --> P8[/SS Receive Password / To processes PW1, PW2, PW3 or PW4 specified in TS GSM 03.11./]
+    P8 --> Wait_for_PW2([Wait_for_PW])
+    Error1 --> End((2))
+    Set_ERROR --> End
+    P6 --> End
+    Wait_for_PW2 --> End
+```
+
+Flowchart for general\_SS\_request\_handling procedure. It starts with a decision 'any BS provisioned within the BSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'any BS applicable within the same EBSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS requiring password or password registration'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS\_request' (To process PW1 as specified in TS GSM 03.11). Then 'Wait\_for\_PW' (Waiting for indications from process PW1, PW2, PW3 or PW4 as specified in TS GSM 03.11). A parallel block contains 'SS Get Password', 'SS Get New Password', 'SS Get New Password Again', 'SS User Errors', 'SS Password Changed', and 'SS Acknowledge'. 'SS User Errors' leads to 'Set ERROR'. 'SS Get Password' leads to 'SS Get Password' (diamond), then 'Wait for password', then 'SS Get Password\_Ack', then 'SS Receive Password' (To processes PW1, PW2, PW3 or PW4 specified in TS GSM 03.11), then 'Wait\_for\_PW'. All paths lead to a final circle with an X.
+
+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. It starts with a connector, checks if any BS is provisioned within the EBSG. If no, it checks if any SS is applicable. If yes, it performs an interrogation. If no, it executes the requested procedure. If interrogation is yes, it sets SS info for EBSG. If interrogation is no, it checks for incompatibility. If incompatible, it sets an error. Finally, all paths lead to an exit 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([ ]) --> Q1{any BS provisioned within the EBSG}; Q1 -- no --> Q2{no SS applicable for any BS within this EBSG}; Q1 -- yes --> Q2; Q2 -- no --> Q3{interrogation}; Q2 -- yes --> P1[execute requested procedure]; Q3 -- yes --> P2[set SS info for EBSG]; Q3 -- no --> Q4{incompatible with other SS for this EBSG}; Q4 -- yes --> P3[set error $S incompatibility]; Q4 -- no --> P1; P1 --> End([X]); P2 --> End; P3 --> End;
+```
+
+Flowchart for handling call independent SS procedures. It starts with a connector, checks if any BS is provisioned within the EBSG. If no, it checks if any SS is applicable. If yes, it performs an interrogation. If no, it executes the requested procedure. If interrogation is yes, it sets SS info for EBSG. If interrogation is no, it checks for incompatibility. If incompatible, it sets an error. Finally, all paths lead to an exit 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'. These merge at a decision 'PW option control by subscriber'. If 'yes', it goes to 'get password' then 'wait for old password'. If 'no', it goes to 'WPA <= 3'. If 'yes', it goes to 'error SS subscription violation'. If 'no', it goes to 'error number of PW attempts violation'. Both error states lead to an 'idle' state.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+Process PW1
+
+311\_31(1)
+
+PW: Password.
+
+```
+graph TD; Start([ ]) --> Idle1([idle]); Idle2([idle]) --> Register[/register password/]; Idle2 --> Activate[/activate protected SS/]; Idle2 --> Deactivate[/deactivate protected SS/]; Register --> Merge(( )); Activate --> Merge; Deactivate --> Merge; Merge --> Decision1{PW option control by subscriber}; Decision1 -- yes --> GetPassword[/get password/]; GetPassword --> WaitOldPassword([wait for old password]); Decision1 -- no --> Decision2{WPA <= 3}; Decision2 -- yes --> ErrorSS[/error SS subscription violation/]; Decision2 -- no --> ErrorWPA[/error number of PW attempts violation/]; ErrorSS --> Idle3([idle]); ErrorWPA --> Idle3;
+```
+
+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'. These merge at a decision 'PW option control by subscriber'. If 'yes', it goes to 'get password' then 'wait for old password'. If 'no', it goes to 'WPA <= 3'. If 'yes', it goes to 'error SS subscription violation'. If 'no', it goes to 'error number of PW attempts violation'. Both error states lead to an 'idle' state.
+
+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', it sets 'WPA := 0' and then checks 'register password'. 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', it increments 'WPA := WPA + 1' and checks 'WPA > 3'. If 'yes', it 'set subscription option control by SP', then '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]) --> Recv[/receive password/]; Recv --> OK{password OK}; OK -- yes --> WPA0[WPA := 0]; OK -- no --> WPAinc[WPA := WPA + 1]; WPA0 --> Reg{register password}; Reg -- yes --> NewPW[/get new password/]; NewPW --> WaitNew([wait for new password]); Reg -- no --> Ack[/acknowledge/]; Ack --> Idle1([idle]); WPAinc --> WPAgt3{WPA > 3}; WPAgt3 -- yes --> SetSub[set subscription option control by SP]; SetSub --> Error[/error PW attempts violation/]; Error --> Idle2([idle]); WPAgt3 -- no --> NegCheck[/negative password check/]; NegCheck --> 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', it sets 'WPA := 0' and then checks 'register password'. 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', it increments 'WPA := WPA + 1' and checks 'WPA > 3'. If 'yes', it 'set subscription option control by SP', then '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; A([wait for new password]) --> B[/receive new password/]; B --> C{format OK}; C -- yes --> D[/get new password again/]; D --> E([wait for new password again]); C -- no --> F[/error password registration failure (invalid format)/]; F --> G([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'. A decision 'password twice identical' follows. If 'yes', it goes to 'password changed'. If 'no', it goes to 'error password registration failure (new Passwords Mismatch)'. Both paths lead to 'idle'.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+Process PW4
+
+311\_34(1)
+
+```
+graph TD; Start([wait for new password again]) --> Input[/receive new password/]; Input --> Decision{password twice identical}; Decision -- yes --> Success{password changed}; Decision -- no --> Failure{error password registration failure (new Passwords Mismatch)}; Success --> End([idle]); Failure --> End;
+```
+
+Flowchart for Process PW4: Check of new password (HLR). The process starts with 'wait for new password again', followed by 'receive new password'. A decision 'password twice identical' follows. If 'yes', it goes to 'password changed'. If 'no', it goes to 'error password registration failure (new Passwords Mismatch)'. Both paths 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. Annotations PW1, PW2, and PW3 indicate password handling programs at the HLR.](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
+    MS-->>MSC: \ 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. Annotations PW1, PW2, and PW3 indicate password handling programs at the HLR.
+
+**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 between MS, MSC, VLR, and HLR.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+
+    Note right of HLR: PW1
+    MS->>MSC: Activate SS
+    MSC->>VLR: Activate SS
+    VLR->>HLR: Activate SS
+    HLR-->>VLR: Get password
+    VLR-->>MSC: Get password
+    MSC-->>MS: Password
+    MS->>MSC: Release complete
+    Note right of MS: \ Facility
+    MSC->>VLR: Password
+    VLR->>HLR: Password
+    Note right of HLR: PW2 ICH
+    HLR-->>VLR: Acknowledge
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Release complete
+    Note right of MS: \ Facility
+```
+
+The diagram illustrates the sequence of messages for activating a protected supplementary service. It involves four lifelines: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The process begins with the MS sending an 'Activate SS' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. The HLR responds with a 'Get password' message to the VLR, which is passed back to the MSC and then to the MS. The MS replies with a 'Password' message to the MSC. The MSC passes this password to the VLR, which then sends it to the HLR. The HLR performs checks (PW2 ICH) and sends an 'Acknowledge' message back through the VLR and MSC to the MS. Finally, the MS sends a 'Release complete' message to the MSC, which is passed back to the MS. A note '\ Facility' is associated with the 'Release complete' message.
+
+Sequence diagram showing the activation of a protected supplementary service between MS, MSC, VLR, and HLR.
+
+**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 subclause 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. Lifelines: MS, MSC, VLR, HLR. The process involves: 1. MS sends 'Deactivate SS' to MSC. 2. MSC sends 'Deactivate SS' to VLR. 3. VLR sends 'Deactivate SS' to HLR. 4. HLR responds with 'Get password' (PW1) to VLR. 5. VLR sends 'Get password' to MSC. 6. MSC sends 'Get password' to MS. 7. MS responds with 'Password' to MSC. 8. MSC sends 'Password' to VLR. 9. VLR sends 'Password' (PW2) to HLR. 10. HLR sends 'Acknowledge' to VLR. 11. VLR sends 'Acknowledge' to MSC. 12. MSC sends 'Release complete \ Facility' to MS.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    Note right of HLR: PW1
+    Note right of HLR: PW2
+    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
+    HLR-->>VLR: Acknowledge
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Release complete \ Facility
+  
+```
+
+Sequence diagram showing the deactivation of a protected supplementary service. Lifelines: MS, MSC, VLR, HLR. The process involves: 1. MS sends 'Deactivate SS' to MSC. 2. MSC sends 'Deactivate SS' to VLR. 3. VLR sends 'Deactivate SS' to HLR. 4. HLR responds with 'Get password' (PW1) to VLR. 5. VLR sends 'Get password' to MSC. 6. MSC sends 'Get password' to MS. 7. MS responds with 'Password' to MSC. 8. MSC sends 'Password' to VLR. 9. VLR sends 'Password' (PW2) to HLR. 10. HLR sends 'Acknowledge' to VLR. 11. VLR sends 'Acknowledge' to MSC. 12. MSC sends 'Release complete \ Facility' to MS.
+
+**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:
+
+- subclause x.1 Functions and information flows;
+- subclause x.2 Information stored in HLR;
+- subclause x.3 Information stored in VLR and SGSN;
+- subclause x.4 Handover.
+
+# Annex A (informative): Change history
+
+| Change history |        |         |     |     |         |     |         |                                                   |
+|----------------|--------|---------|-----|-----|---------|-----|---------|---------------------------------------------------|
+| TSG CN#        | Spec   | Old Ver | CR  | Rev | <Phase> | Cat | New Ver | Subject/Comment                                   |
+| Apr 1999       | 03.11  | 6.0.0   |     |     | R97     |     |         | Transferred to 3GPP CN1                           |
+| CN#03          | 23.011 |         |     |     | R99     |     | 3.0.0   | Approved at CN#03                                 |
+|                | 23.011 | 3.0.0   |     |     | R99     |     | 3.0.1   | List of references updated from 2G to 3G          |
+| CN#09          | 23.011 | 3.0.1   | 002 | 1   | R99     | F   | 3.1.0   | SDL refresh                                       |
+| CN#11          | 23.011 | 3.1.0   |     |     | Rel-4   |     | 4.0.0   | Release 4 after CN#11                             |
+| CN#15          | 23.011 | 4.0.0   |     |     | Rel-4   |     | 4.0.1   | References updated                                |
+| CN#16          | 23.011 | 4.0.1   |     |     | Rel-5   |     | 5.0.0   | Release 5 after CN#16                             |
+| CN#19          | 23.011 | 5.0.0   |     |     | Rel-6   |     | 6.0.0   | Introduction of Call Barring for SMS in PS domain |
+| CT#36          | 23.011 | 6.0.0   |     |     | Rel-7   |     | 7.0.0   | Upgraded unchanged from Rel-6                     |
+| CT#42          | 23.011 | 7.0.0   |     |     | Rel-8   |     | 8.0.0   | Upgraded unchanged from Rel-7                     |
+| 2009-12        | -      | 8.0.0   | -   | -   | Rel-9   |     | 9.0.0   | Update to Rel-9 version (MCC)                     |
+| 2011-03        | -      | 9.0.0   | -   | -   | Rel-10  |     | 10.0.0  | Update to Rel-10 version (MCC)                    |
+| 2012-09        | -      | 10.0.0  | -   | -   | Rel-11  |     | 11.0.0  | Update to Rel-11 version (MCC)                    |
+| 2014-09        | -      | 11.0.0  | -   | -   | Rel-12  |     | 12.0.0  | Update to Rel-12 version (MCC)                    |
+| 2015-12        | -      | 12.0.0  | -   | -   | Rel-13  |     | 13.0.0  | Update to Rel-13 version (MCC)                    |
+| 2017-03        | -      | 13.0.0  | -   | -   | Rel-14  |     | 14.0.0  | Update to Rel-14 version (MCC)                    |
+| 2018-06        | -      | 14.0.0  | -   | -   | Rel-15  | -   | 15.0.0  | Update to Rel-15 version (MCC)                    |
+| 2020-07        | -      | -       | -   | -   | -       | -   | 16.0.0  | Update to Rel-16 version (MCC)                    |

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

@@ -0,0 +1,1382 @@
+
+
+
+
+
+
+# --- 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 |
+| Annex A (informative): Change history.....                                          | 32 |
+
+# --- 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 subclause 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.
+
+Subclauses 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 subclause 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 subclause 4.4. Alternatively, the HLR may delete the existing data as described in subclause 4.2.2 and then insert the replacing data as described in subclause 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)
+
+```
+graph TD; IMSI --- Basic_MSISDN[Basic MSISDN]; IMSI --- Category[Category]; IMSI --- Basic_Service_List[Basic Service List]; IMSI --- Forwarding_Info[Forwarding Info]; IMSI --- Call_Barring_Info[Call Barring Info]; IMSI --- CUG_Info[CUG Info]; IMSI --- SS_Data[SS Data]; IMSI --- ODB_Data[ODB Data for non-GPRS services]; IMSI --- Roaming_Restriction_Data[Roaming Restriction Data in the VLR]; IMSI --- Regional_Subscription_Data[Regional Subscription Data]; IMSI --- VBS_VGCS_Data[VBS, VGCS Data]; IMSI --- CAMEL_Subscription_Info[CAMEL Subscription Info]; IMSI --- NAEA_Prefered_Carrier_Id[NAEA, Preferred Carrier Id]; IMSI --- LSA_Data[LSA Data]; IMSI --- IST_Data[IST Data]; IMSI --- LMU_Indicator[LMU Indicator]; IMSI --- LCS_Information[LCS Information]; IMSI --- Super_Charger_Information[Super Charger Information]; IMSI --- Bearer_Service_Priority_Data[Bearer Service Priority Data]; IMSI --- Administrative_Restriction_Information[Administrative Restriction Information];
+```
+
+The diagram illustrates the abstract data structure of non-GPRS Subscriber Data sent to the VLR. It is a hierarchical tree structure starting with IMSI at the root. The data is organized into several categories, some of which are grouped into boxes. The categories are: Basic MSISDN, Category, Basic Service List, Forwarding Info, Call Barring Info, CUG Info, SS Data, ODB Data for non-GPRS services, Roaming Restriction Data in the VLR, Regional Subscription Data, VBS, VGCS Data, CAMEL Subscription Info, NAEA, Preferred Carrier Id, LSA Data, IST Data, LMU Indicator, LCS Information, Super Charger Information, Bearer Service Priority Data, and 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). The diagram shows a hierarchical list of data elements under the root 'IMSI'.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+```
+
+graph LR
+    IMSI --- AM[Access Mode]
+    IMSI --- BM[Basic MSISDN]
+    IMSI --- BSL[Basic Service List]
+    IMSI --- CBI[Call Barring Info]
+    IMSI --- ODB[ODB Data for GPRS services]
+    IMSI --- RR[Roaming Restriction Data in the SGSN]
+    IMSI --- RSD[Regional Subscription Data]
+    IMSI --- GSD[GPRS subscription Data]
+    IMSI --- ESD[EPS subscription Data]
+    IMSI --- SCS[SGSN CAMEL subscription information]
+    IMSI --- LD[LSA Data]
+    IMSI --- SCI[Super-Charger Information]
+    IMSI --- CI[Charging Information]
+    IMSI --- LI[LCS Information]
+    IMSI --- ARI[Administrative Restriction Information]
+    
+```
+
+Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN). The diagram shows a hierarchical list of data elements under the root 'IMSI'.
+
+**Figure 2: Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN)**
+
+![Basic Service List diagram showing Teleservices and Bearer Services categories.](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+```
+
+graph LR
+    Root --- TS[Teleservices]
+    TS --- TS1[TS (1)]
+    TS --- TSDots[...]
+    TS --- TSn[TS (n)]
+    Root --- BS[Bearer Services]
+    BS --- BS1[BS (1)]
+    BS --- BSDots[...]
+    BS --- BSn[BS (n)]
+    style Root width:0px,height:0px
+    
+```
+
+Basic Service List diagram showing Teleservices and Bearer Services categories.
+
+NOTE: For detailed information see 3GPP TS 22.001, 3GPP TS 22.002, 3GPP TS 22.003 and 3GPP TS 29.002.
+
+**Figure 3: Basic Service List**
+
+![A hierarchical tree diagram showing the structure of Forwarding Information (FI) for various call forwarding scenarios. The root branches into five main call forwarding types: CFU, CFB, CFNRc, CFNRy, and CD. Each type has a set of common parameters (Subscription Options, Provisioning State) and specific parameters (BSG entries with Activation/Registration states, Forwarded-to Number, Subaddress, or No Reply Condition Timer).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+```
+graph TD
+    Root[ ] --- 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_SO[Subscription Options]
+    CFU --- CFU_PS[Provisioning State]
+    CFU --- CFU_BSG1[BSG(1)]
+    CFU --- CFU_Dots1[.....]
+    CFU --- CFU_BSGn[BSG(n)]
+
+    CFU_BSG1 --- CFU_BSG1_AS[Activation State]
+    CFU_BSG1 --- CFU_BSG1_RS[Registration State]
+
+    CFU_BSGn --- CFU_BSGn_AS[Activation State]
+    CFU_BSGn --- CFU_BSGn_RS[Registration State]
+
+    CFB --- CFB_SO[Subscription Options]
+    CFB --- CFB_PS[Provisioning State]
+    CFB --- CFB_BSG1[BSG(1)]
+    CFB --- CFB_Dots1[.....]
+    CFB --- CFB_BSGn[BSG(n)]
+
+    CFB_BSG1 --- CFB_BSG1_AS[Activation State]
+    CFB_BSG1 --- CFB_BSG1_RS[Registration State]
+    CFB_BSG1 --- CFB_BSG1_FTN[Forwarded-to Number]
+    CFB_BSG1_FTN --- CFB_BSG1_FTN_SA[Subaddress]
+
+    CFB_BSGn --- CFB_BSGn_AS[Activation State]
+    CFB_BSGn --- CFB_BSGn_RS[Registration State]
+    CFB_BSGn --- CFB_BSGn_FTN[Forwarded-to Number]
+    CFB_BSGn_FTN --- CFB_BSGn_FTN_SA[Subaddress]
+
+    CFNRc --- CFNRc_SO[Subscription Options]
+    CFNRc --- CFNRc_PS[Provisioning State]
+    CFNRc --- CFNRc_BSG1[BSG(1)]
+    CFNRc --- CFNRc_Dots1[.....]
+    CFNRc --- CFNRc_BSGn[BSG(n)]
+
+    CFNRc_BSG1 --- CFNRc_BSG1_AS[Activation State]
+    CFNRc_BSG1 --- CFNRc_BSG1_RS[Registration State]
+    CFNRc_BSG1 --- CFNRc_BSG1_FTN[Forwarded-to Number]
+    CFNRc_BSG1_FTN --- CFNRc_BSG1_FTN_SA[Subaddress]
+
+    CFNRc_BSGn --- CFNRc_BSGn_AS[Activation State]
+    CFNRc_BSGn --- CFNRc_BSGn_RS[Registration State]
+    CFNRc_BSGn --- CFNRc_BSGn_FTN[Forwarded-to Number]
+    CFNRc_BSGn_FTN --- CFNRc_BSGn_FTN_SA[Subaddress]
+
+    CFNRy --- CFNRy_SO[Subscription Options]
+    CFNRy --- CFNRy_PS[Provisioning State]
+    CFNRy --- CFNRy_BSG1[BSG(1)]
+    CFNRy --- CFNRy_Dots1[.....]
+    CFNRy --- CFNRy_BSGn[BSG(n)]
+
+    CFNRy_BSG1 --- CFNRy_BSG1_AS[Activation State]
+    CFNRy_BSG1 --- CFNRy_BSG1_RS[Registration State]
+    CFNRy_BSG1 --- CFNRy_BSG1_NRCT[No Reply Condition Timer]
+    CFNRy_BSG1 --- CFNRy_BSG1_FTN[Forwarded-to Number]
+    CFNRy_BSG1_FTN --- CFNRy_BSG1_FTN_SA[Subaddress]
+
+    CFNRy_BSGn --- CFNRy_BSGn_AS[Activation State]
+    CFNRy_BSGn --- CFNRy_BSGn_RS[Registration State]
+    CFNRy_BSGn --- CFNRy_BSGn_NRCT[No Reply Condition Timer]
+    CFNRy_BSGn --- CFNRy_BSGn_FTN[Forwarded-to Number]
+    CFNRy_BSGn_FTN --- CFNRy_BSGn_FTN_SA[Subaddress]
+
+    CD --- CD_SO[Subscription Options]
+    CD --- CD_PS[Provisioning State]
+```
+
+A hierarchical tree diagram showing the structure of Forwarding Information (FI) for various call forwarding scenarios. The root branches into five main call forwarding types: CFU, CFB, CFNRc, CFNRy, and CD. Each type has a set of common parameters (Subscription Options, Provisioning State) and specific parameters (BSG entries with Activation/Registration states, Forwarded-to Number, Subaddress, or No Reply Condition Timer).
+
+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](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+This hierarchical tree diagram represents the 'Call Barring Info' structure. It branches into three main categories: 'Barring of All Outgoing Calls (BAOC)', 'Barring of Outgoing International Calls (BOIC)', and 'Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)'. Each category has a 'Provisioning State' sub-element. The 'BOIC' and 'BOIC-exHC' categories further branch into multiple 'BSG' (Barring Service Group) elements, labeled 'BSG(1)' through 'BSG(n)', each with its own 'Activation State' sub-element. The 'BAOC' category also has 'BSG(1)' through 'BSG(n)' elements, but they are not explicitly shown with 'Activation State' sub-elements in this diagram.
+
+Hierarchical tree diagram for Call Barring Info
+
+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](2eb23c2210154279f8013a1594fbcc5a_img.jpg)
+
+This hierarchical tree diagram represents the 'CUG Info' structure. It starts with 'Closed User Group (CUG)', which branches into 'Interlock(1)' and 'Interlock(m)'. Each 'Interlock' element has 'CUG Index', 'Intra CUG Restrictions', and multiple 'BSG' (Barring Service Group) elements labeled 'BSG(1)' through 'BSG(n)'. Below the 'Interlock' elements, there are 'BSG(1)' and 'BSG(n)' elements, each with 'Preferential CUG' and 'Inter CUG Accessibility' sub-elements.
+
+Hierarchical tree diagram for CUG Info
+
+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 the structure of LCS (Location Services) 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 Class' branches into 'Universal', 'Call Session Related', 'Call Session Unrelated', 'PLMN Operator', and 'Service Type'. The 'MO-LR Class' branches into 'Basic Self Location', 'Autonomous Self Location', and 'Transfer To Third Party'. Each class has sub-states: 'Provisioning State', 'Activation State', and 'Registration State' (where applicable).](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 --- LPE_C[ ]
+    LPE_C --- LPE_CU[LCS Privacy Exception Class Universal]
+    LPE_C --- LPE_CSR[LCS Privacy Exception Class Call Session Related]
+    LPE_C --- LPE_CSU[LCS Privacy Exception Class Call Session Unrelated]
+    LPE_C --- LPE_CPO[LCS Privacy Exception Class PLMN Operator]
+    LPE_C --- LPE_CST[LCS Privacy Exception Class Service Type]
+    LPE_CU --- PS_U[Provisioning State]
+    LPE_CU --- AS_U[Activation State]
+    LPE_CU --- Reg_U[Registration State]
+    LPE_CSR --- PS_R[Provisioning State]
+    LPE_CSR --- AS_R[Activation State]
+    LPE_CSR --- Reg_R[Registration State]
+    LPE_CSU --- PS_S[Provisioning State]
+    LPE_CSU --- AS_S[Activation State]
+    LPE_CSU --- Reg_S[Registration State]
+    LPE_CPO --- PS_Op[Provisioning State]
+    LPE_CPO --- AS_Op[Activation State]
+    LPE_CPO --- Reg_Op[Registration State]
+    LPE_CST --- PS_T[Provisioning State]
+    LPE_CST --- AS_T[Activation State]
+    LPE_CST --- Reg_T[Registration State]
+    Root --- MO_LR_C[ ]
+    MO_LR_C --- MO_LR_CBSL[MO-LR Class Basic Self Location]
+    MO_LR_C --- MO_LR_CASL[MO-LR Class Autonomous Self Location]
+    MO_LR_C --- MO_LR_CTT[MO-LR Class Transfer To Third Party]
+    MO_LR_CBSL --- PS_BSL[Provisioning State]
+    MO_LR_CBSL --- AS_BSL[Activation State]
+    MO_LR_CBSL --- Reg_BSL[Registration State]
+    MO_LR_CASL --- PS_ASL[Provisioning State]
+    MO_LR_CASL --- AS_ASL[Activation State]
+    MO_LR_CASL --- Reg_ASL[Registration State]
+    MO_LR_CTT --- PS_TT[Provisioning State]
+    MO_LR_CTT --- AS_TT[Activation State]
+    MO_LR_CTT --- Reg_TT[Registration State]
+```
+
+A hierarchical tree diagram showing the structure of LCS (Location Services) 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 Class' branches into 'Universal', 'Call Session Related', 'Call Session Unrelated', 'PLMN Operator', and 'Service Type'. The 'MO-LR Class' branches into 'Basic Self Location', 'Autonomous Self Location', and 'Transfer To Third Party'. Each class has sub-states: 'Provisioning State', 'Activation State', and 'Registration State' (where applicable).
+
+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 tree diagram representing Regional Subscription Data. It starts with a root node 'ZoneCode(1)', followed by an ellipsis '.....', and ending 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 Voice Group Call Data structure](171115f072e42b379238ed0dd438e9d7_img.jpg)
+
+```
+└VGCS membership List
+├Group-Id(1)
+├.....
+└Group-Id (n)
+```
+
+A hierarchical tree diagram representing Voice Group Call Data. It starts with a root node 'VGCS membership List', followed by 'Group-Id(1)', an ellipsis '.....', and 'Group-Id (n)'.
+
+Diagram of Voice Group Call Data structure
+
+NOTE: For detailed information see 3GPP TS 43.068 and 3GPP TS 29.002.
+
+**Figure 13: Voice Group Call Data**
+
+![Diagram of Voice Broadcast Call Data structure](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg)
+
+```
+└VBS membership List
+├Group-Id(1)
+│└Broadcast Call Initiation Entitlement
+├.....
+└Group-Id (n)
+└Broadcast Call Initiation Entitlement
+```
+
+A hierarchical tree diagram representing Voice Broadcast Call Data. It starts with a root node 'VBS membership List', followed by 'Group-Id(1)' which has a child node 'Broadcast Call Initiation Entitlement', an ellipsis '.....', and 'Group-Id (n)' which also has a child node 'Broadcast Call Initiation Entitlement'.
+
+Diagram of Voice Broadcast Call Data 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] --> Originating[Originating CAMEL Subscription Info]
+    Root --> Dialled[Dialled Service CAMEL Subscription Info]
+    Root --> VMS[VMS C Terminating CAMEL Subscription Info]
+    Root --> SS[SS Invocation Notification CAMEL Subscription Info]
+
+    Originating --> TDPList1[TDP Data List]
+    TDPList1 --> OBCSM1[O-BCSM CAMEL TDP Data (1)]
+    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]
+    OBCSM1 --> OBCSM1_6[.....]
+    TDPList1 --> OBCSMn[O-BCSM CAMEL TDP Data (n)]
+    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]
+    Originating --> CAMELCap1[CAMEL Capability Handling]
+
+    Dialled --> DPCriteriaList[DP Criteria List]
+    DPCriteriaList --> DPCriterion1[DP Criterion (1)]
+    DPCriterion1 --> DPCriterion1_1[Service Key]
+    DPCriterion1 --> DPCriterion1_2[gsmSCF Address]
+    DPCriterion1 --> DPCriterion1_3[Default Call Handling]
+    DPCriterion1 --> DPCriterion1_4[.....]
+    DPCriteriaList --> DPCriterionn[DP Criterion (n)]
+    DPCriterionn --> DPCriterionn_1[Service Key]
+    DPCriterionn --> DPCriterionn_2[gsmSCF Address]
+    DPCriterionn --> DPCriterionn_3[Default Call Handling]
+    Dialled --> CAMELCap2[CAMEL Capability Handling]
+
+    VMS --> TDPList2[TDP Data List]
+    TDPList2 --> VTBCSM1[VT-BCSM CAMEL TDP Data (1)]
+    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]
+    VTBCSM1 --> VTBCSM1_6[.....]
+    TDPList2 --> VTBCSMn[VT-BCSM CAMEL TDP Data (n)]
+    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]
+    VMS --> CAMELCap3[CAMEL Capability Handling]
+
+    SS --> NotificationCriterion[Notification Criterion]
+    SS --> gsmSCFAddress1[gsmSCF Address]
+    SS --> ActivationFlag1[Activation Flag]
+    SS --> NotificationFlag1[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. From this line, four horizontal branches extend to the right. The first branch is 'Notify on Change of Subscriber Data Flag'. The second branch is 'Translation Information Flag CAMEL Subscription Information'. The third branch is 'MO SMS CAMEL Subscription Info'. The fourth branch is 'MT SMS CAMEL Subscription Info'. From the 'MT SMS CAMEL Subscription Info' branch, four more horizontal branches extend to the right: 'Mobility Management Event Notification CAMEL Subscription Info', 'Mobility Trigger List', 'Service Key', and 'gsmSCF Address'.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+```
+graph LR; Root[ ] --- N[Notify on Change of Subscriber Data Flag]; Root --- T[Translation Information Flag CAMEL Subscription Information]; Root --- MO[MO SMS CAMEL Subscription Info]; Root --- MT[MT SMS CAMEL Subscription Info]; MT --- M[Mobility Management Event Notification CAMEL Subscription Info]; MT --- L[Mobility Trigger List]; MT --- K[Service Key]; MT --- A[gsmSCF Address]; style Root fill:none,stroke:none
+```
+
+A hierarchical tree diagram showing CAMEL subscription information. The root is a vertical line. From this line, four horizontal branches extend to the right. The first branch is 'Notify on Change of Subscriber Data Flag'. The second branch is 'Translation Information Flag CAMEL Subscription Information'. The third branch is 'MO SMS CAMEL Subscription Info'. The fourth branch is 'MT SMS CAMEL Subscription Info'. From the 'MT SMS CAMEL Subscription Info' branch, four more horizontal branches extend to the right: '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**
+
+![Hierarchical tree diagram of LCS Information structure](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)
+
+```
+
+Hierarchical tree diagram of LCS Information structure
+
+![Diagram showing LCS Information structure with Notification to MS User and Service Type Identity (n) components.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+```
+graph TD
+    subgraph LCS_Information [LCS Information]
+        direction TB
+        L1[Notification to MS User] --> L1_1[GMLC restriction]
+        L1_2[....]
+        L2[Service Type Identity (n)] --> L2_1[Notification to MS User]
+        L2_1 --> L2_2[GMLC restriction]
+    end
+```
+
+Diagram showing LCS Information structure with Notification to MS User and Service Type Identity (n) components.
+
+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)
+
+```
+graph TD
+    subgraph PDP_Context_List [PDP Context List]
+        direction TB
+        L1[PDP Context (1)] --> L1_1[PDP Context Identifier]
+        L1_2[PDP Type]
+        L1_3[PDP Address]
+        L1_4[VPLMN Address Allowed]
+        L1_5[Quality of Service Subscribed]
+        L1_6[Access Point Name]
+        L1_7[PDP Context Charging Characteristics]
+        L1_8[....]
+        L2[PDP Context (n)]
+    end
+```
+
+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)
+
+```
+graph TD
+    subgraph APN_Configuration_List [APN Configuration List]
+        direction TB
+        L1[Default Context]
+        L2[APN Configuration (1)] --> L2_1[Context Identifier]
+        L2_2[PDN Type]
+        L2_3[Served Party IPv4 Address]
+        L2_4[APN]
+        L2_5[EPS QoS Subscribed]
+        L2_6[PDN GW Identity]
+        L2_7[PDN GW Allocation Type]
+        L2_8[VPLMN Address Allowed]
+        L2_9[Charging Characteristics]
+        L2_10[AMBR]
+        L2_11[Specific APN Info List]
+        L2_12[Served Party IPv6 Address]
+        L2_13[....]
+        L3[APN Configuration (n)]
+    end
+```
+
+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 showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with 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 showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with 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 showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with Identity, Attributes, and Active Mode Indicator.](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 showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with Identity, Attributes, and Active Mode Indicator.
+
+NOTE: For detailed information see 3GPP TS 23.073 and 3GPP TS 29.002.
+
+**Figure 19: LSA data in the SGSN**
+
+![Diagram showing a single entry for IST Alert Timer.](e9b43ac020435f8121e8592f31afdc52_img.jpg)
+
+```
+
+|—IST Alert Timer
+
+```
+
+Diagram showing a single entry for 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 Figure 21: Super-Charger Information. The root is 'SGSN CAMEL subscription information', which branches into 'GPRS CAMEL Subscription Information', 'MO SMS CAMEL Subscription Info', 'MT SMS CAMEL Subscription Info', and 'Mobility Management Event for GPRS Notification CAMEL Subscription Info'. 'GPRS CAMEL Subscription Information' further branches into 'TDP Data List', 'CAMEL Capability Handling', and 'GPRS CAMEL TDP Data (1)' through '(n)'. Each 'GPRS CAMEL TDP Data' entry contains 'GPRS TDP', 'Service Key', 'gsmSCF Address', and 'Default GPRS Handling'.](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 Figure 21: Super-Charger Information. The root is 'SGSN CAMEL subscription information', which branches into 'GPRS CAMEL Subscription Information', 'MO SMS CAMEL Subscription Info', 'MT SMS CAMEL Subscription Info', and 'Mobility Management Event for GPRS Notification CAMEL Subscription Info'. 'GPRS CAMEL Subscription Information' further branches into 'TDP Data List', 'CAMEL Capability Handling', and 'GPRS CAMEL TDP Data (1)' through '(n)'. Each 'GPRS CAMEL TDP Data' entry contains 'GPRS TDP', 'Service Key', 'gsmSCF Address', and 'Default GPRS Handling'.
+
+**Figure 22: SGSN CAMEL subscription info**
+
+![Hierarchical tree diagram for Figure 23a: MO SMS CAMEL Subscription Info. The root is 'MO SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' further branches into 'MO SMS CAMEL TDP Data (1)' through '(n)'. Each 'MO SMS CAMEL TDP Data' entry contains 'MO SMS TDP', 'Service Key', 'gsmSCF Address', and 'Default SMS 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 Figure 23a: MO SMS CAMEL Subscription Info. The root is 'MO SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' further branches into 'MO SMS CAMEL TDP Data (1)' through '(n)'. Each 'MO SMS CAMEL TDP Data' entry contains 'MO SMS TDP', 'Service Key', 'gsmSCF Address', and 'Default SMS Handling'.
+
+**Figure 23a: MO SMS CAMEL Subscription Info**
+
+![Figure 23b: MT SMS CAMEL Subscription Info. A hierarchical tree diagram showing the structure of MT SMS CAMEL Subscription Info. The root is 'MT SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' branches into 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'. 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)' both branch into 'MT SMS TDP', 'DP Criteria', 'Service Key', 'gsmSCF Address', and 'Default SMS Handling'. There is an ellipsis between 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'.](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. A hierarchical tree diagram showing the structure of MT SMS CAMEL Subscription Info. The root is 'MT SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' branches into 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'. 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)' both branch into 'MT SMS TDP', 'DP Criteria', 'Service Key', 'gsmSCF Address', and 'Default SMS Handling'. There is an ellipsis between 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'.
+
+**Figure 23b: MT SMS CAMEL Subscription Info**
+
+![Figure 24: Bearer Service Priority Data in the VLR. A tree diagram showing 'CS Allocation/Retention priority'.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg)
+
+```
+└ CS Allocation/Retention priority
+```
+
+Figure 24: Bearer Service Priority Data in the VLR. A tree diagram showing 'CS Allocation/Retention priority'.
+
+NOTE: For detailed information see 3GPP TS 23.008.
+
+**Figure 24: Bearer Service Priority Data in the VLR**
+
+![Figure 25: Charging Information. A tree diagram showing 'Subscribed Charging Characteristics'.](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg)
+
+```
+└ Subscribed Charging Characteristics
+```
+
+Figure 25: Charging Information. A tree diagram showing 'Subscribed Charging Characteristics'.
+
+NOTE: For detailed information see 3GPP TS 23.060.
+
+**Figure 25: Charging Information.**
+
+![Figure 26: Administrative Restriction Information in the VLR. A tree diagram showing 'Access Restriction Data'.](ca5dc5fde2061d0ca2051ef7840fc842_img.jpg)
+
+```
+└ Access Restriction Data
+```
+
+Figure 26: Administrative Restriction Information in the VLR. A tree diagram showing 'Access Restriction Data'.
+
+NOTE: For detailed information see 3GPP TS 23.012 [34].
+
+**Figure 26: Administrative Restriction Information in the VLR**
+
+# Annex A (informative): Change history old
+
+| Change history |           |         |       |         |             |                                                                                        |
+|----------------|-----------|---------|-------|---------|-------------|----------------------------------------------------------------------------------------|
+| TSG CN#        | Spec      | Version | CR    | <Phase> | New Version | Subject/Comment                                                                        |
+| Apr 1999       | GSM 03.16 | 7.0.0   |       |         |             | Transferred to 3GPP CN1                                                                |
+| CN#03          | 23.016    |         |       |         | 3.0.0       | Approved at CN#03                                                                      |
+| CN#04          | 23.016    | 3.0.0   | 001   | R99     | 3.1.0       | Introduction of TIF-CSI for Call Deflection                                            |
+| CN#04          | 23.016    |         | 002r1 | R99     | 3.1.0       | Missing SS-CSI in description of CAMEL Subscription                                    |
+| CN#05          | 23.016    | 3.1.0   | 003r1 | R99     | 3.2.0       | Non-CAMEL IST implementation                                                           |
+| CN#06          | 23.016    | 3.2.1   | 004r3 | R99     | 3.3.0       | Introduction of the Super-Charger Concept in TS 23.016                                 |
+| CN#06          | 23.016    | 3.2.1   | 006   | R99     | 3.3.0       | Support of Subscriber Data Management in the HLR and VLR for LCS                       |
+| CN#06          | 23.016    | 3.2.1   | 009   | R99     | 3.3.0       | Correction of VLR subscription Data                                                    |
+| CN#06          | 23.016    | 3.2.1   | 008r1 | R99     | 3.3.0       | Introduction of CAMEL phase 3                                                          |
+| CN#07          | 23.016    | 3.3.0   | 010   | R99     | 3.4.0       | Correction of LSA Information                                                          |
+| CN#07          | 23.016    | 3.3.0   | 011r1 | R99     | 3.4.0       | The addition of priority information                                                   |
+| CN#07          | 23.016    | 3.3.0   | 012r2 | R99     | 3.4.0       | Introduction of subscriber data for Multicall                                          |
+| CN#08          | 23.016    | 3.4.0   | 013r1 | R99     | 3.5.0       | Addition of information related to charging                                            |
+| CN#08          | 23.016    | 3.4.0   | 014   | R99     | 3.5.0       | Clarifications on GSM vs. UMTS specific parts                                          |
+| CN#08          | 23.016    | 3.4.0   | 015   | R99     | 3.5.0       | Addition of charging characteristics per PDP context                                   |
+| CN#09          | 23.016    | 3.5.0   | 016   | R99     | 3.6.0       | Correction to Delete Subscriber Data                                                   |
+| CN#11          | 23.016    | 3.6.0   | 018   | R99     | 3.7.0       | Alignment about Notification to MS User between 29.002 , 23.171(LCS Stage2) and 23.016 |
+| CN#11          | 23.016    | 3.7.0   |       | Rel-4   | 4.0.0       | Version increased from R99 to Rel-4 after CN#11                                        |
+| CN#11          | 23.016    | 3.7.0   | 017r1 | Rel-4   | 4.0.0       | Add three subscriber statuses to the ODB Data for GPRS services                        |
+| CN#11          | 23.016    | 3.7.0   | 019r2 | Rel-4   | 4.0.0       | Extension of call related privacy class for LCS Release 4                              |
+| CN#11          | 23.016    | 3.7.0   | 020r1 | Rel-4   | 4.0.0       | PS domain support for LCS Release 4                                                    |
+| CN#15          | 23.016    | 4.0.0   | 023r2 | Rel-4   | 4.1.0       | Clarification on overlapping data                                                      |
+| CN#15          | 23.016    | 4.0.0   |       | Rel-4   | 4.1.0       | References updated                                                                     |
+| CN#15          | 23.016    | 4.1.0   | 021   | Rel-5   | 5.0.0       | Collective CR on 23.016                                                                |
+| CN#16          | 23.016    | 5.0.0   | 025   | Rel-5   | 5.1.0       | Clarification of introducing Session related and unrelated class                       |
+| CN#16          | 23.016    | 5.0.0   | 026   | Rel-5   | 5.1.0       | LCS: Codeword and Service Type                                                         |
+| CN#17          | 23.016    | 5.1.0   | 029   | Rel-5   | 5.2.0       | Introduction of Call Deflection                                                        |
+| CN#19          | 23.016    | 5.2.0   | 030r1 | Rel-6   | 6.0.0       | Introduction of Call Barring for SMS in PS domain                                      |
+| CN#23          | 23.016    | 6.0.0   | 034r2 | Rel-6   | 6.1.0       | Correction to SS data for LCS SS                                                       |
+| CN#23          | 23.016    | 6.0.0   | 035r1 | Rel-6   | 6.1.0       | Include administrative restriction subscription parameter                              |
+| CT#36          | 23.016    | 6.1.0   |       | Rel-7   | 7.0.0       | Upgraded unchanged from Rel-6                                                          |
+| CT#42          | 23.016    | 7.0.0   |       | Rel-8   | 8.0.0       | Upgraded unchanged from Rel-7                                                          |
+| CT#46          | 23.016    | 8.0.0   | -     | Rel-9   | 9.0.0       | Update to Rel-9 version (MCC)                                                          |
+| CT#47          | 23.016    | 9.0.0   | 0037  | Rel-9   | 9.1.0       | Addition of EPS Subscription Information                                               |
+| 2011-03        | 23.016    | 9.1.0   | -     | Rel-10  | 10.0.0      | Update to Rel-10 version (MCC)                                                         |
+| 2012-09        | 23.016    | 10.0.0  | -     | Rel-11  | 11.0.0      | Update to Rel-11 version (MCC)                                                         |
+| 2014-09        | 23.016    | 11.0.0  | -     | Rel-12  | 12.0.0      | Update to Rel-12 version (MCC)                                                         |
+| 2015-12        | 23.016    | 12.0.0  | -     | Rel-13  | 13.0.0      | Update to Rel-13 version (MCC)                                                         |
+| 2017-03        | 23.016    | 13.0.0  | -     | Rel-14  | 14.0.0      | Update to Rel-14 version (MCC)                                                         |
+| 2018-06        | 23.016    | 14.0.0  | -     | Rel-15  | 15.0.0      | Update to Rel-15 version (MCC)                                                         |
+| 2020-07        | -         | -       | -     | -       | 16.0.0      | Update to Rel-16 version (MCC)                                                         |