Content for TS 23.016 Word version: 18.0.0
4.5.4 Consistency of Supplementary Service data p. 16
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.
Figure 1: Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Figure 2: Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
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
$ Change history p. 32
