Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.271  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.2…   7…   8…   9…   9.1.1A…   9.1.2…   9.1.5…   9.1.6…   9.1.8…   9.1.9…   9.1.12…   9.1.13…   9.1.15…   9.1.19…   9.2…   9.2.2…   9.2.3…   9.3…   9.4…   9.5…   9.6…   10…   11…   A…   B…   E   F…

 

B (Normative)  Presence of LCS client ID Components in MT-LRWord‑p. 176

The LCS client identity is composed of one or more than one of the following components: LCS client type, external identity, internal identity, call/session related identity, APN-NI, client name and Requestor Identity. For Value added LCS client type it may contain also Client name and Requestor ID type indicator. The LCS client type shall always be present and for each LCS client type the presence of the other components are defined as follows:
Component External identity Internal identity Call/session related identity Client name Requestor Identity
LCS Client type
EmergencyON.A.N.A.N.A.N.A.
Value addedMN.A.O [Note]MO
PLMN operatorN.A.MN.A.N.A.N.A.
Lawful InterceptN.A.N.A.N.A.N.A.N.A.
Up

C  Pseudo external ID |R5|Word‑p. 177

In case that UE's privacy profile is stored and is checked in the GMLC (H-GMLC) or in the PPR, a pseudo-external identity may be selected as a result of the privacy check in GMLC/PPR.
The pseudo-external identities may be set in the external LCS client list of the HLR privacy exception list shown in Table 10.2. The pseudo-external identity is not the identity of real external LCS client but the identity which is used for notifying SGSN/MSC of the location request class (call/session related or non-related) and the required type of indication for each class. Operator allocates E.164 addresses for the pseudo-external identities. The pseudo-external identities are used for interworking with pre Rel-6 serving nodes.
Fourteen pseudo-external identities shall be defined. The pseudo-external identities are summarized in the Table C.1.
Pseudo-external identity Privacy setting for Call/Session related class Privacy setting for Call/Session unrelated class
Pseudo-external identity 1 N.A.Location allowed without notification
Pseudo-external identity 2 N.A.Location allowed with notification
Pseudo-external identity 3 N.A.Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 4 N.A.Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 5 Location with notification and privacy verification; location restricted if no responseLocation not allowed
Pseudo-external identity 6 Indicator 6Location with notification and privacy verification; location allowed if no responseLocation not allowed
Pseudo-external identity 7 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 8 Location allowed with notificationLocation not allowed
Pseudo-external identity 9 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 10 Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 11 Location allowed without notificationLocation not allowed
Pseudo-external identity 12 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 13 Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 14 Location allowed with notification
If the UE subscribes to the universal or PLMN class, H-GMLC/PPR sends the pseudo external identity 1 to the serving nodes.
Usage of the pseudo-external identities are as follows:
  • The pseudo-external identities are registered in SLPP of the HLR/HSS.
  • The SLPP is sent to the serving nodes, during the Insert Subscriber Data procedures.
  • After the privacy check in the H-GMLC/PPR, the H-GMLC/PPR selects an appropriate pseudo-external identity according to the required privacy related actions (i.e. checking the on-going call/session and/or notification/verification procedures) in the serving node.
  • H-GMLC sends Provide Subscriber Location message to the serving node, which includes the pseudo-external identity instead of the real external client identity. The real external client identity may be included in the additional information element and is sent to serving node. The pseudo-external identity is sent to the serving node directly from H-GMLC or via V-GMLC.
Table C.2 and Table C.3 shows how the pseudo-external identities are set in the SLPP in HLR/HSS.
Pseudo-external identity Privacy Setting
Pseudo-external identity 1 Location allowed without notification
Pseudo-external identity 2 Location allowed with notification
Pseudo-external identity 3 Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 4 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 5 Location not allowed
Pseudo-external identity 6 Location not allowed
Pseudo-external identity 7 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 8 Location not allowed
Pseudo-external identity 9 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 10 Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 11 Location not allowed
Pseudo-external identity 12 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 13 Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 14 Location allowed with notification
Pseudo-external identity Privacy Setting
Pseudo-external identity 5 Location with notification and privacy verification; location restricted if no response
Pseudo-external identity 6 Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 7 Location with notification and privacy verification; location allowed if no response
Pseudo-external identity 8 Location allowed with notification
Pseudo-external identity 9 Location allowed with notification
Pseudo-external identity 10 Location allowed with notification
Pseudo-external identity 11 Location allowed without notification
Pseudo-external identity 12 Location allowed without notification
Pseudo-external identity 13 Location allowed without notification
Pseudo-external identity 14 Location allowed without notification
The selection of pseudo-external identity is based on the result of the privacy check in the H-GMLC/PPR. Table C.4 shows the relation between privacy check result and the pseudo-external identities.
Privacy related actions as a result of privacy check Pseudo-external identity
Location request is allowed without notification, regardless of on-going call/session.Pseudo-external identity 1
Location request is allowed with notification, regardless of on-going call/session.Pseudo-external identity 2
Location request is allowed with notification and privacy verification, regardless of on-going call/session. Location request is allowed even if there is no response from UE.Pseudo-external identity 3
Location request is allowed with notification and privacy verification, regardless of on-going call/session. Location request is restricted if there is no response from UE. Pseudo-external identity 4
If there is call/session with the client, location request is allowed with notification and privacy verification. Location request is restricted if there is no response from UE.
If there is no call/session with the client, location request is restricted.
Pseudo-external identity 5
If there is call/session with the client, location request is allowed with notification and privacy verification. Location request is allowed even if there is no response from UE.
If there is no call/session with the client, location request is restricted.
Pseudo-external identity 6
If there is call/session with the client, location request is allowed with notification and privacy verification. Location request is allowed even if there is no response from UE.
If there is no call/session with the client, location request is allowed with notification and privacy verification. Location request is restricted if no response.
Pseudo-external identity 7
If there is call/session with the client, location request is allowed with notification.
If there is no call/session with the client, location request is restricted.
Pseudo-external identity 8
If there is call/session with the client, location request is allowed with notification.
If there is no call/session with the client, location request is with notification and privacy verification. Location request is restricted if no response.
Pseudo-external identity 9
If there is call/session with the client, location request is allowed with notification.
If there is no call/session with the client, location request is allowed even if there is no response from UE.
Pseudo-external identity 10
If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is restricted.
Pseudo-external identity 11
If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is with notification and privacy verification. Location request is restricted if no response.
Pseudo-external identity 12
If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is allowed even if there is no response from UE.
Pseudo-external identity 13
If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is allowed with notification.
Pseudo-external identity 14
Up

D (Normative)  including Requestor identity to LCS client name |R6|Word‑p. 181

In case the MSC/SGSN or the UE is pre Rel-5 then there is no possibility to send the Requestor identity to the UE in a new separate parameter. To obtain this backward compatibility the GMLC can add the Requestor identity to LCS client name.
In order to offer best possible service for the end user the UE should be able to differentiate LCS client name and Requestor ID when they are included in to a same parameter. Also it is important that the LCS client name and the Requestor ID are separated with a consistent manner. Therefore there is a need to define a rule how the GMLC should separate LCS client name and Requestor identity. In the box below is described the practice how the LCS client name and Requestor identity should be separated.
LCS clientName==RequestorIdentity
LCS client name and Requestor identity are separated with two equal signs.
Up

Up   Top   ToC