4 General on handling of subscriber information

23.0163GPPRelease 17Stage 2Subscriber data managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

In general, the VLR and SGSN stores only a subset of the subscriber data available in the HLR. Similarly, the GGSN stores only a subset of the subscriber data available in the SGSN. Updating of subscriber information shall be done in a way to make available and to keep consistency of data shared between the HLR and the VLR, and between the HLR and the SGSN as appropriate.

Two different cases for the updating of subscriber data can be identified:

1. framed operation: during location update or restoration a complete set of the shared subscriber data needs to be inserted in the VLR or the SGSN;

2. stand-alone operation: whenever subscriber data are added, deleted or changed in the HLR, this may need partial insertion, deletion or change of shared subscriber data in the VLR or the SGSN.

Clauses 4.1 to 4.4 explain the actions of the HLR and the VLR or the SGSN within a framed or stand-alone dialogue on subscriber data handling.

4.1 Updating of the VLR or the SGSN in framed operation

For some services the VLR or the SGSN shall indicate in the subscriber data request to the HLR whether it supports the service, or (in case of a service with multiple phases) which phases it supports. Whether or not this indication is required for the service is defined in service specification.

If requested by the framing operation, the HLR shall send all relevant stored shared subscriber data to the VLR or the SGSN. This may be done with one or more messages within a single dialogue.

For services for which the VLR or the SGSN is required to indicate support of the service, the HLR shall send subscriber data to the VLR or the SGSN only if corresponding indication was received from the VLR or the SGSN in the subscriber data request. If both the originating entity and the HLR support the Super-Charger functionality the HLR may provide no subscriber data as part of the location update procedure, see 3GPP TS 23.116. For control of stand‑alone operation the HLR shall store the information for which of these services the subscriber data was sent.

For services for which the VLR or the SGSN is required to indicate supported phases of the service, the HLR shall send subscriber data to the VLR for at most one of the supported phases of service indicated in the subscriber data request. In this case the HLR may send also no data at all if none of the supported phases is suitable. For the case of stand-alone operation the HLR shall store the information for which phase of service the data was sent.

The HLR may send all stored shared subscriber data to the VLR or the SGSN with one or more messages within a single dialogue.

The VLR or the SGSN shall check the received messages, and:

a) if mandatory data is missing in a message:

– the VLR or the SGSN may immediately reject the message towards the HLR; or

– the VLR or the SGSN may acknowledge the message towards the HLR and wait for further data from the HLR.

NOTE: Which of the two options apply is either defined by the protocol specification or is an implementation option.

b) if unexpected data are received in a message:

– the VLR or the SGSN may reject the message towards the HLR; or

– in case of unexpected data not required in a given context, the VLR or the SGSN may acknowledge the message towards the HLR and ignore this unexpected data. All other data shall be stored by the VLR or the SGSN.

NOTE: Which of the two possibilities apply is an implementation option.

c) if data for unsupported services or features is received:

– the VLR or the SGSN shall respond towards the HLR to the message indicating these features and shall ignore all received data related to them. All other subscriber data shall be stored;

d) if cases a), b) and c) do not apply for a message, the VLR or SGSN shall store all subscriber data received.

If during the entire dialogue none of the messages was rejected by the VLR or the SGSN and at termination of the dialogue no mandatory subscriber data are missing, the VLR or the SGSN shall erase all previously stored data and shall store the data received from the HLR and mark the subscriber data as "confirmed by HLR". Otherwise the subscriber data shall remain marked as "not confirmed by HLR" (see TS 3GPP TS 23.007).

The HLR shall check all responses from the VLR or the SGSN, and:

a) if a message is rejected, no further updating of the VLR or the SGSN shall occur. The further action on the framing operation is out of scope of this specification;

b) if one or more unsupported features are indicated by the VLR or the SGSN, the HLR may:

– store subscriber data including replacement feature(s) locally;

– store and send subscriber data including replacement feature(s);

– ignore this indication.

NOTE: Which of the three options apply for which feature is out of scope of this specification

c) if a message is acknowledged by the VLR or the SGSN, this shall be recognized by the HLR.

The further action on the framing operation after all shared subscriber and replacement data have been sent (e.g. closing of the dialogue) is out of scope of this specification.

4.2 Updating of VLR and the SGSN in stand alone operation

If shared subscriber data are added, deleted or changed in the HLR, the HLR shall insert or delete this subscriber data in the VLR or the SGSN to keep consistency of data stored.

For services for which the VLR or the SGSN is required to indicate support of the service in the request, the HLR shall insert or delete this subscriber data in the VLR or the SGSN only if an appropriate indication is stored in the HLR (see clause 4.1).

For services for which the VLR or the SGSN is required to indicate supported phases of the service in the request, the HLR shall insert or delete subscriber data in the VLR or the SGSN only if it was added, deleted or changed for the phase of the service for which the data was sent to the VLR or the SGSN in the framed operation.

4.2.1 Insertion of data in the VLR or the SGSN

For the insertion of data, the HLR may send one or more messages in a single dialogue.

The VLR or the SGSN shall check the received data, and:

a) if mandatory data is missing in a message:

– the VLR or the SGSN may reject the message towards the HLR; or

– the VLR or the SGSN may acknowledge the message towards the HLR and wait for further data from HLR.

NOTE: Which of the two possibilities apply is either defined by the protocol specification or an implementation option.

b) if unexpected data are received:

– the VLR or the SGSN may reject the message towards the HLR; or

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 VLR or SGSN the response to the HLR.

4.2.3 Change of data in the VLR or in the SGSN

If existing data in the VLR or the SGSN is to be modified, the HLR may insert the replacing data, which overwrites the existing data according to the rules described in clause 4.4. Alternatively, the HLR may delete the existing data as described in clause 4.2.2 and then insert the replacing data as described in clause 4.2.1.

4.3 Order of information and distribution over message boundaries

4.3.1 Order of information sent by the HLR

The order of information is defined by the order in which the transfer syntax is generated by the HLR. This includes a sequence of messages as well as the syntax within a message (first to last message, component, operation, parameter, etc…).

With the above definitions, the following rules shall apply for non-GPRS subscriber data for the order of information within an HLR-VLR dialogue:

– Group A information (subscriber status) shall be sent first;

– Group B information shall be sent after Group A information and before any Group C, E, F, G, H, J, L, M or X information;

– Group D information shall be sent after Group A information and in any order with respect to Group B, C, E, F, G, H, J, K, L, M and X information;

– a specific order of Group C, E, F, G, H, J, K, L, M or X information is not required.

There is no requirement for the sending of subscriber information groups in the same message.

With the above definitions, the following rules shall apply for GPRS subscriber data for the order of information within a dialogue:

– Group P1 information (subscriber status) shall be sent first;

– Group P2 information shall be sent after P1 information and before P4 and P5 information;

– Group P3 information shall be sent after Group P1 information and in any order with respect to Group P2, P4, P5, P6, P6a, P7, P8, P11 and P12 information;

– a specific order of Group P4, P5, P6, P6a, P9, P10, P11 and P12 information is not required.

4.3.2 Order of information received by the VLR or the SGSN

Normally, the order of information sent and received shall be identical. However, if subscriber data are sent distributed over several messages within a dialogue in exceptional cases the order of these messages may change during transmission.

If the order of information received violates the rules given above, the VLR or the SGSN has the following options:

– the VLR or the SGSN rejects all messages which cannot be processed due to violation of these rules. In this case, checking of missing mandatory parameters is done for each message;

– the VLR or the SGSN processes and accepts all received messages although rules are violated. In this case, checking of missing mandatory parameters is done after the last message i.e. after termination of the dialogue.

Both options may be used in a single implementation. Missing parameters may be detected during the dialogue. For other parameters, the checking is done after termination of the dialogue between the HLR and the VLR or the SGSN.

The VLR or the SGSN is not required to handle received data in a specific order. As a consequence, any overlapping of data within a dialogue should be avoided to keep consistency of data between HLR and VLR or the SGSN. If the VLR or SGSN indicates that it does not support a feature or service, the HLR may send data for a feature or service to replace the unsupported one. If the data of that service or feature had already been sent, this shall not be regarded as overlapping data.

4.4 Abstract data structure of shared subscriber data

Figure 1 shows the general organization of the shared non-GPRS subscriber data stored in the HLR and VLR. Figure 2 shows the overall organization of subscriber data stored in HLR and SGSN. The figures 3 to 25 show the organization of the shared subscriber data stored in the HLR and VLR or in the HLR and SGSN. This structure is only valid for data stored in the registers and is not identical with the structure in the protocol, defining how data are transferred.

NOTE: This description is only a model for the logical structure and does not define the specific implementation of the data storage.

With this structure, the following general rules for the handling of subscriber data are defined:

– the root of this data tree is always the IMSI which identifies the subscriber;

– to address a specific parameter within this hierarchical tree, it is necessary to start from the IMSI and to go through the branches until the parameter is reached. The list of parameters met on the way defines the address of the parameter within the data structure;

– to delete or insert a specific parameter, the complete address information is required;

– if a parameter is inserted, all parameters in the address and the parameter itself shall be marked as present. A parameter value is stored irrespective of whether a value was already stored;

– if a parameter is deleted, all parameters connected to it in the sub-branches are also deleted i.e. they are marked as not present;

– if a parameter is overwritten with a new value, parameters connected to it in the sub-branches shall be set according to the rules of the individual service specification.

In addition to the general rules given above, special rules apply to certain specific subscriber data. This is out of scope of this specification (see references in the notes in figures 1 to 25).

4.5 Handling of supplementary service data with respect to basic service data

Some supplementary service data is qualified by Elementary Basic Service Group (EBSG) data. This part of the service data is below the parameter "BSG" in the abstract data hierarchy, and is referred to as the "EBSG-related SS data". This clause provides special rules for handling of EBSG-related SS data.

The internal representation of EBSGs and EBSG-related SS data in the HLR and VLR is outside the scope of this specification. For simplicity this description uses a model where all EBSG-related SS data is stored against individual EBSGs. Implementations may use alternative internal data structures.

4.5.1 General

EBSG-related SS data shall be stored in the HLR and VLR for all EBSGs that meet all the following criteria:

– at least one basic service in the EBSG is supported; and

– the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and

– the subscriber has a subscription to at least one (possibly different) basic service in the EBSG.

EBSG-related SS data shall not be stored for any other EBSGs.

For each service for which the HLR sends EBSG-related SS data to the VLR, the HLR shall send the data for all EBSGs that meet all the following criteria:

– at least one basic service in the EBSG is supported at the HLR; and

– the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and

– the subscriber has a subscription to at least one (possibly different) basic service in the EBSG.

At any time, if the HLR has to send identical EBSG-Related SS data for several EBSGs, then it may be able to represent a set of EBSGs by a collective basic service group (CBSG), or by omitting the EBSG information altogether. This is specified in detail in 3GPP TS 29.002.

4.5.2 Changes to basic service subscription

Changes to the basic service subscription can impact EBSG-related SS data.

If a new basic service is provisioned, and this is the first basic service to be provisioned for this subscriber in a particular EBSG, then the HLR shall update supplementary service data in the VLR if necessary. The HLR shall insert in the VLR EBSG-related SS data for the new EBSG for all supplementary services that:

– have EBSG-related SS data; and

– are applicable to at least one basic service in the new EBSG; and

– are in a state where the VLR should receive data (normally this means the service must be provisioned).

If a new basic service is provisioned, and this is not the first basic service provisioned for this subscriber in a particular EBSG, then the HLR is not required to send any new supplementary service data as a result.

If a basic service is withdrawn, and this was the last remaining basic service provisioned for this subscriber in a particular EBSG, then when they are informed about the withdrawal of the basic service the HLR and VLR shall locally delete any supplementary service data relating to that EBSG.

If a basic service is withdrawn, and this was not the last remaining basic service provisioned for this subscriber in a particular EBSG, then the HLR and VLR shall not make any changes to supplementary service data as a result.

4.5.3 Special rules for BS61 and BS81 "alternate" and "followed-by" services

There is no EBSG-related SS data for the groups BS61 and BS81 ("alternate" and "followed-by"). Instead, supplementary services related to these basic services are handled according to the bearer service group BS2x or BS3x corresponding to the data part of the "alternate" and "followed by" bearer service (see 3GPP TS 22.004). This means that special rules are required for subscribers with subscriptions to BS61 or BS81.

For the handling of EBSG-related SS data, a subscription to BS61 or BS81 shall be treated in the same way as a subscription to a basic service in each of the groups "all data circuit asynchronous" and "all data circuit synchronous" (BS2x and BS3x). If a user subscribes to BS61 or BS81 then the HLR shall send any relevant EBSG-related SS data to the VLR for the groups BS2x and BS3x even if the subscriber does not subscribe to any basic services in the groups BS2x and BS3x.

Examples:

– if a user who does not subscribe to any basic services in BS2x or BS3x is given a subscription to BS81 then the HLR updates the VLR with any relevant EBSG-related SS data for the groups BS2x and BS3x. If the subscription to BS81 is then withdrawn, the VLR locally deletes all EBSG-related SS data for BS2x and BS3x.

– if a user who has a subscription to BS21, but not to any basic services in BS3x is given a subscription to BS81 then the HLR updates the VLR with any relevant EBSG-related SS data for the group BS3x. If the subscription to BS81 is then withdrawn, the VLR locally deletes all EBSG-related SS data for BS3x (though not for BS2x).

EBSG-related SS data shall not be qualified by the groups BS61 or BS81.

4.5.4 Consistency of Supplementary Service data

In some cases, the protocol used between the HLR and VLR encodes some data that is not EBSG-related SS data with an EBSG qualifier. In this case, the HLR shall ensure that when this data is sent it is always the same for all EBSGs. If this data is modified, the HLR must send the supplementary service data to the VLR for all EBSGs which meet all the following criteria:

– at least one basic service in the EBSG is supported; and

– the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and

– the subscriber has a subscription to at least one (possibly different) basic service in the EBSG.

IMSI
│
├─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 │
│ └───────────────────────────────┘
│ ┌──────────────────────────────────────┐
├─┤Administrative Restriction Information│
│ └──────────────────────────────────────┘

Figure 1: Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR)

IMSI
│
├─Access Mode
│
├─Basic MSISDN
│
│ ┌──────────────────┐
├─┤Basic Service List│
│ └──────────────────┘
│ ┌─────────────────┐
├─┤Call Barring Info│
│ └─────────────────┘
│ ┌──────────────────────────┐
├─┤ODB Data for GPRS services│
│ └──────────────────────────┘
│ ┌────────────────────────────────────┐
├─┤Roaming Restriction Data in the SGSN│
│ └────────────────────────────────────┘
│ ┌──────────────────────────┐
├─┤Regional Subscription Data│
│ └──────────────────────────┘
│ ┌──────────────────────────────┐
├─┤GPRS subscription Data │
│ └──────────────────────────────┘
│ ┌──────────────────────────────┐
├─┤EPS subscription Data │
│ └──────────────────────────────┘
│ ┌────────────────────────────────────┐
├─┤SGSN CAMEL subscription information │
│ └────────────────────────────────────┘
│ ┌───────────────────────────────┐
├─┤LSA Data │
│ └───────────────────────────────┘
│ ┌───────────────────────────────┐
├─┤Super-Charger Information │
│ └───────────────────────────────┘

│ ┌───────────────────────────────┐
├─┤Charging Information │
│ └───────────────────────────────┘

│ ┌───────────────────────────────┐
└─┤LCS Information │
└───────────────────────────────┘

│ ┌──────────────────────────────────────┐
├─┤Administrative Restriction Information│
│ └──────────────────────────────────────┘

Figure 2: Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN)

│
├─Teleservices
│ ├─TS(1)
│ ├─…..
│ └─TS(n)
│
└─Bearer Services
├─BS(1)
├─…..
└─BS(n)

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

│
├─Call Forwarding Unconditional (CFU)
│ ├─Provisioning State
│ ├─BSG(1)
│ │ ├─Activation State
│ │ └─Registration State
│ ├─…..
│ │
│ └─BSG(n)
│ ├─Activation State
│ └─Registration State
│
├─Call Forwarding on mobile subscriber Busy (CFB)
│ ├─Subscription Options
│ ├─Provisioning State
│ ├─BSG(1)
│ │ ├─Activation State
│ │ ├─Registration State
│ │ └─Forwarded-to Number
│ │ └─Subaddress
│ ├─…..
│ │
│ └─BSG(n)
│ ├─Activation State
│ ├─Registration State
│ └─Forwarded-to Number
│ └─Subaddress
│
├─Call Forwarding on mobile subscriber Not Reachable (CFNRc)
│ ├─Subscription Options
│ ├─Provisioning State
│ ├─BSG(1)
│ │ ├─Activation State
│ │ ├─Registration State
│ │ └─Forwarded-to Number
│ │ └─Subaddress
│ ├─…..
│ │
│ └─BSG(n)
│ ├─Activation State
│ ├─Registration State
│ └─Forwarded-to Number
│ └─Subaddress
│
├─Call Forwarding on No Reply (CFNRy)
│ ├─Subscription Options
│ ├─Provisioning State
│ ├─BSG(1)
│ │ ├─Activation State
│ │ ├─Registration State
│ │ ├─No Reply Condition Timer
│ │ └─Forwarded-to Number
│ │ └─Subaddress
│ ├─…..
│ │
│ └─BSG(n)
│ ├─Activation State
│ ├─Registration State
│ ├─No Reply Condition Timer
│ └─Forwarded-to Number
│ └─Subaddress
│
└─Call Deflection (CD)
├─Subscription Options
└─Provisioning State

NOTE: For detailed information see 3GPP TS 23.072, 3GPP TS 23.082 and 3GPP TS 29.002.

Figure 4: Forwarding Info

├─Barring of All Outgoing Calls (BAOC)
│ ├─Provisioning State
│ ├─BSG(1)
│ │ └─Activation State
│ ├─…..
│ │
│ └─BSG(n)
│ └─Activation State
│
├─Barring of Outgoing International Calls (BOIC)
│ ├─Provisioning State
│ ├─BSG(1)
│ │ └─Activation State
│ ├─…..
│ │
│ └─BSG(n)
│ └─Activation State
│
└─Barring of Outgoing International Calls except
those directed to the Home PLMN Country (BOIC-exHC)
├─Provisioning State
├─BSG(1)
│ └─Activation State
├─…..
│
└─BSG(n)
└─Activation State

NOTE: For detailed information see 3GPP TS 23.088 and 3GPP TS 29.002.

Figure 5: Call Barring Info

└─Closed User Group (CUG)
├─Interlock(1)
│ ├─CUG Index
│ ├─Intra CUG Restrictions
│ ├─BSG(1)
│ ├─…..
│ └─BSG(n)
├─…..
│
├─Interlock(m)
│ ├─CUG Index
│ ├─Intra CUG Restrictions
│ ├─BSG(1)
│ ├─….
│ └─BSG(n)
│
├─BSG(1)
│ ├─Preferential CUG
│ └─Inter CUG Accessibility
├─…..
│
└─BSG(n)
├─Preferential CUG
└─Inter CUG Accessibility

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

│
├─Completion of Calls to Busy Subscriber (CCBS)- originating NW
│ ├─Provisioning State
│ └─Activation State
│
├─Completion of Calls to Busy Subscriber (CCBS)- destination NW
│ ├─Provisioning State
│ └─Activation State
├─LCS Privacy Exception Class Universal
│ ├─Provisioning State
│ ├─Activation State
│ └─Registration State
│
├─LCS Privacy Exception Class Call Session Related
│ ├─Provisioning State
│ ├─Activation State
│ └─Registration State
│
├─LCS Privacy Exception Class Call Session Unrelated
│ ├─Provisioning State
│ ├─Activation State
│ └─Registration State
│
├─LCS Privacy Exception Class PLMN Operator
│ ├─Provisioning State
│ ├─Activation State
│ └─Registration State
│
├─LCS Privacy Exception Class Service Type
│ ├─Provisioning State
│ ├─Activation State
│ └─Registration State
│
├─MO-LR Class Basic Self Location
│ ├─Provisioning State
│ ├─Activation State
│ └─Registration State
│
├─MO-LR Class Autonomous Self Location
│ ├─Provisioning State
│ ├─Activation State
│ └─Registration State
│
└─MO-LR Class Transfer To Third Party
├─Provisioning State
├─Activation State
└─Registration State

NOTE: For detailed information see 3GPP TS 23.067, 3GPP TS 23.081, 3GPP TS 23.083, 3GPP TS 23.084, 3GPP TS 23.086, 3GPP TS 23.091, 3GPP TS 23.093, 3GPP TS 23.096, 3GPP TS 23.135, 3GPP TS 29.002 and 3GPP TS 23.071.

The codes below are used for the single purpose of enabling the visited network to notify the home network whether or not the particular Supplementary Service is supported. These codes are also included in the LCS Information parameter and the visited network shall use the codes in the LCS Information parameter, and only this parameter, to obtain the information needed for the LCS Supplementary Service.

– LCS Privacy Exception Class Universal

– LCS Privacy Exception Class Call Session Related

– LCS Privacy Exception Class Call Session Unrelated

– LCS Privacy Exception Class PLMN Operator

– LCS Privacy Exception Class Service Type

– MO-LR Class Basic Self Location

– MO-LR Class Autonomous Self Location

– MO-LR Class Transfer To Third Party

Figure 7: SS Data

└─Subscriber Status
├─all OG-Calls Barred
├─international OG-Calls Barred
├─international OG-Calls Not To HPLMN Country Barred
├─inter-zonal OG-Calls Barred
├─inter-zonal OG-Calls Not To HPLMN Country Barred
├─international OG-Calls Not To HPLMN Country AND
inter-zonal OG-Calls Barred
├─Premium Rate Information OG-Calls Barred
├─Premium Rate Entertainment OG-Calls Barred
├─SS Access Barred
├─all call transfers Barred
├─chargeable call transfers Barred
├─international call transfers Barred
├─inter-zonal call transfers Barred
├─doubly chargeable call transfers Barred
├─multiple call transfers Barred
├─PLMN-Specific Barring Type 1
├─PLMN-Specific Barring Type 2
├─PLMN-Specific Barring Type 3
└─PLMN-Specific Barring Type 4

NOTE: For detailed information see 3GPP TS 23.015 and 3GPP TS 29.002.

Figure 8: ODB Data for non-GPRS services

├─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

├─ZoneCode(1)
│
├─…..
│
└─ZoneCode(k)

NOTE: For detailed information see 3GPP TS 29.002.

Figure 12: Regional Subscription Data

└─VGCS membership List
│
├─Group-Id(1)
│
├─…..
│
└─Group-Id (n)

NOTE: For detailed information see 3GPP TS 43.068 and 3GPP TS 29.002.

Figure 13: Voice Group Call Data

└─VBS membership List
│
├─Group-Id(1)
│ └─Broadcast Call Initiation Entitlement
│
├─…..
│
└─Group-Id (n)
└─Broadcast Call Initiation Entitlement

NOTE: For detailed information see 3GPP TS 43.069 and 3GPP TS 29.002.

Figure 14: Voice Broadcast Call Data

└─CAMEL Subscription Information
│
├─ Originating CAMEL Subscription Info
│ │
│ ├─ TDP Data List
│ │ │
│ │ ├─ O-BCSM CAMEL TDP Data (1)
│ │ │ │
│ │ │ ├─ O-BCSM TDP
│ │ │ ├─ DP Criteria
│ │ │ ├─ Service Key
│ │ │ ├─ gsmSCF Address
│ │ │ ├─ Default Call Handling
│ │ │
│ │ ├─…..
│ │ │
│ │ ├─ O-BCSM CAMEL TDP Data (n)
│ │ │
│ │ ├─ O-BCSM TDP
│ │ ├─ DP Criteria
│ │ ├─ Service Key
│ │ ├─ gsmSCF Address
│ │ ├─ Default Call Handling
│ │
│ ├─ CAMEL Capability Handling
│
│
├─ Dialled Service CAMEL Subscription Info
│ │
│ ├── DP Criteria List
│ │ │
│ │ ├── DP Criterion (1)
│ │ │ │
│ │ │ ├── Service Key
│ │ │ ├── gsmSCF Address
│ │ │ ├── Default Call Handling
│ │ │
│ │ ├──…..
│ │ │
│ │ ├── DP Criterion (n)
│ │ │
│ │ ├── Service Key
│ │ ├── gsmSCF Address
│ │ ├── Default Call Handling
│ │
│ ├── CAMEL Capability Handling
│
│
├─- VMSC Terminating CAMEL Subscription Info
│ │
│ ├── TDP Data List
│ │ │
│ │ ├─ VT-BCSM CAMEL TDP Data (1)
│ │ │ │
│ │ │ ├─ VT-BCSM TDP
│ │ │ ├─ DP Criteria
│ │ │ ├─ Service Key
│ │ │ ├─ gsmSCF Address
│ │ │ ├─ Default Call Handling
│ │ │
│ │ ├─…..
│ │ │
│ │ ├─ VT-BCSM CAMEL TDP Data (n)
│ │ │
│ │ ├─ VT-BCSM TDP
│ │ ├─ DP Criteria
│ │ ├─ Service Key
│ │ ├─ gsmSCF Address
│ │ ├─ Default Call Handling
│ │
│ ├─ CAMEL Capability Handling
│
│
├─ SS Invocation Notification CAMEL Subscription Info
│ │
│ ├─ Notification Criterion
│ ├─ gsmSCF Address
│ ├─ Activation Flag
│ ├─ Notification Flag
│ ├─ Notify on Change of Subscriber Data Flag
│
│
├─ Translation Information Flag CAMEL Subscription

│ Information
│
│
├─ MO SMS CAMEL Subscription Info
│ ¦
│
├─ MT SMS CAMEL Subscription Info
│ ¦
│ ├─ Mobility Management Event Notification CAMEL

│ Subscription Info
│
├─ Mobility Trigger List
├─ Service Key
├─ 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

└─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)
…│..│…├─Notification to MS User
│ │ │ └─GMLC restriction
│ │ │
│ │ ├─….
│ │ │
│ │ ├─Service Type Identity (n)
…│..│…│…├─Notification to MS User
│ │ │ └─GMLC restriction

NOTE: For detailed information see 3GPP TS 23.271 and 3GPP TS 29.002.

Figure 16: LCS Information

└─PDP Context List
│
├─PDP Context (1)
│ ├─PDP Context Identifier
│ ├─PDP Type
│ ├─PDP Address
│ ├─VPLMN Address Allowed
│ ├─Quality of Service Subscribed
│ ├─Access Point Name
│ └─PDP Context Charging Characteristics
│
├─ ….
│
└─PDP Context (n)

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

└─APN Configuration List
│

…├─Default Context
├─APN Configuration (1)
│ ├─Context Identifier
│ ├─PDN Type
│ ├─Served Party IPv4 Address
│ ├─APN
│ ├─EPS QoS Subscribed
│ ├─PDN GW Identity
│ ├─PDN GW Allocation Type
│ ├─VPLMN Address Allowed
│ ├─Charging Characteristics
│ ├─AMBR
│ ├─Specific APN Info List
│ └─Served Party IPv6 Address
│
├─ ….
│
└─APN Configuration (n)

Figure 17a: EPS subscription data

├─LSA Only Access Indicator
└─LSA Data List
│
├─LSA Data (1)
│ ├─LSA Identity
│ ├─LSA Attributes
│ ├─LSA Active Mode Indicator
│
├─ ….
│
└─LSA Data (n)

NOTE: For detailed information see 3GPP TS 23.073 and 3GPP TS 29.002.

Figure 18: LSA data in the VLR

├─LSA Only Access Indicator
└─LSA Data List
│
├─LSA Data (1)
│ ├─LSA Identity
│ ├─LSA Attributes
│ ├─LSA Active Mode Indicator
│
├─ ….
│
└─LSA Data (n)

NOTE: For detailed information see 3GPP TS 23.073 and 3GPP TS 29.002.

Figure 19: LSA data in the SGSN

└─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

├─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
│

Figure 22: SGSN CAMEL subscription info

├─ 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

Figure 23a: MO SMS CAMEL Subscription Info

├─ 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

└─CS Allocation/Retention priority

NOTE: For detailed information see 3GPP TS 23.008.

Figure 24: Bearer Service Priority Data in the VLR

└─Subscribed Charging Characteristics

NOTE: For detailed information see 3GPP TS 23.060.

Figure 25: Charging Information.

└─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

Change history
Date	Meeting	TDoc	CR	Rev	Cat	Subject/Comment	New version
Apr 1999						Transferred to 3GPP CN1
CN#03						Approved at CN#03	3.0.0
CN#04			001			Introduction of TIF-CSI for Call Deflection	3.1.0
CN#04			002r1			Missing SS-CSI in description of CAMEL Subscription	3.1.0
CN#05			003r1			Non-CAMEL IST implementation	3.2.0
CN#06			004r3			Introduction of the Super-Charger Concept in TS 23.016	3.3.0
CN#06			006			Support of Subscriber Data Management in the HLR and VLR for LCS	3.3.0
CN#06			009			Correction of VLR subscription Data	3.3.0
CN#06			008r1			Introduction of CAMEL phase 3	3.3.0
CN#07			010			Correction of LSA Information	3.4.0
CN#07			011r1			The addition of priority information	3.4.0
CN#07			012r2			Introduction of subscriber data for Multicall	3.4.0
CN#08			013r1			Addition of information related to charging	3.5.0
CN#08			014			Clarifications on GSM vs. UMTS specific parts	3.5.0
CN#08			015			Addition of charging characteristics per PDP context	3.5.0
CN#09			016			Correction to Delete Subscriber Data	3.6.0
CN#11			018			Alignment about Notification to MS User between 29.002 , 23.171(LCS Stage2) and 23.016	3.7.0
CN#11						Version increased from R99 to Rel-4 after CN#11	4.0.0
CN#11			017r1			Add three subscriber statuses to the ODB Data for GPRS services	4.0.0
CN#11			019r2			Extension of call related privacy class for LCS Release 4	4.0.0
CN#11			020r1			PS domain support for LCS Release 4	4.0.0
CN#15			023r2			Clarification on overlapping data	4.1.0
CN#15						References updated	4.1.0
CN#15			021			Collective CR on 23.016	5.0.0
CN#16			025			Clarfication of introducing Session related and unrelated class	5.1.0
CN#16			026			LCS: Codeword and Service Type	5.1.0
CN#17			029			Introduction of Call Deflection	5.2.0
CN#19			030r1			Introduction of Call Barring for SMS in PS domain	6.0.0
CN#23			034r2			Correction to SS data for LCS SS	6.1.0
CN#23			035r1			Include administrative restriction subscription parameter	6.1.0
CT#36						Upgraded unchanged from Rel-6	7.0.0
CT#42						Upgraded unchanged from Rel-7	8.0.0
CT#46			–			Update to Rel-9 version (MCC)	9.0.0
CT#47			0037			Addition of EPS Subscription Information	9.1.0
2011-03			–			Update to Rel-10 version (MCC)	10.0.0
2012-09			–			Update to Rel-11 version (MCC)	11.0.0
2014-09			–			Update to Rel-12 version (MCC)	12.0.0
2015-12						Update to Rel-13 version (MCC)	13.0.0
2017-03			–			Update to Rel-14 version (MCC)	14.0.0
2018-06			–			Update to Rel-15 version (MCC)	15.0.0
2020-07			–			Update to Rel-16 version (MCC)	16.0.0
2022-03						Update to Rel-17 version (MCC)	17.0.0