Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.271  Word version:  18.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… 
7 Signalling and Interfaces  7.1 LCS signalling between Access and Core Networks for GERAN and UTRAN access networks  7.1a LCS signalling between Access and Core Networks for E-UTRAN access networks  7.2 Um, Uu and Uu-LTE Interfaces  7.3 MAP Interfaces  7.4 Lpp interface  7.5 Lid interface  7.6 IMS related Interfaces  7.7 SLg Interface  7.8 SLs Interface  7.9 SLh Interface  7.10 SLm Interface  7.11 Lgd Interface 
...

 

7  Signalling and Interfaces  p. 46

7.1  LCS signalling between Access and Core Networks for GERAN and UTRAN access networks  p. 46

For GERAN and UTRAN access networks, the core network sends location requests to the access network, which then sends the corresponding responses back to the core network.
Communication between access and core networks is accomplished through Iu interface in UMTS whereas the A, Gb and Iu interfaces are used for the purpose in GSM (see TS 25.305 and TS 43.059).

7.1.1  Core network Location Request  p. 46

The core network request for a location estimate of a target UE shall contain sufficient information to enable location of the Target UE according to the required QoS using any positioning method supported by the PLMN and, where necessary, UE. For location services the core network may request the geographical co-ordinates and velocity of the Target UE.
In Iu mode the core network may also request in which Service Area the Target UE is located. The Service Area information may be used for routing of corresponding Emergency calls, or for CAMEL services.
In A/Gb mode this corresponds to the usage of Cell ID in the core network. It should be noted that the Service Area concept is different from the Localized Service Area concept used for SoLSA services.
When the location of a Target UE in Idle Mode is requested, the core network shall determine which RAN entity is associated with the Target UE.
Up

7.1.2  Location Report  p. 46

The access network reports the location of the Target UE to the core network entities. The location report may contain the following information as defined in the corresponding location request:
  • the geographical co-ordinates of the Target UE;
  • the positioning method used to obtain the location estimate if the access network is either GERAN in the A/Gb mode, GERAN in the Iu mode or UTRAN in the Iu mode.
  • the service area in which the Target UE is located;
  • achieved quality level of the location estimate;
  • velocity estimate of the Target UE, if available;
  • achieved quality level of the velocity estimate of the Target UE, if available.
Up

7.1a  LCS signalling between Access and Core Networks for E-UTRAN access networks |R9|  p. 47

For E-UTRAN access networks, the MME sends location requests to the E-SMLC via the SLs interface (see clause 7.8). The E-SMLC then sends core network measurement requests, as described in clause 7.1a.1, to the access network via the MME. The access network sends corresponding network measurement reports, as described in clause 7.1a.2, back to the E-SMLC, again via the MME.
Communication between access and core networks is accomplished through S1 interface in E-UTRAN (see TS 36.305.
Up

7.1a.1  Core network Measurement Request  p. 47

The core network request for network measurements shall contain sufficient information to enable the desired measurements to be provided by the access network.
The core network shall determine which RAN entities are associated with the Target UE.

7.1a.2  Location Measurement Report  p. 47

The access network reports measurements pertaining to the Target UE back to the E-SMLC as defined in the corresponding core network measurement request.

7.2  Um, Uu and Uu-LTE Interfaces  p. 47

The Um, Uu and Uu-LTE interfaces are used to communicate among the LCS entities associated with the BSC, RNC, the UE and the stand-alone (Type A) Location Measurement Units (LMU). The Um, Uu and Uu-LTE interfaces are also used to communicate between the LCS entities in the core network and the UE.
The Um/Uu/Uu-LTE interfaces may pass measurement requests and results to and from UE or the stand-alone LMU.
The Um/Uu/Uu-LTE interfaces may also pass location requests from internal or external LCS Clients (Applications) at the UE. Note that these requests may require the services of the LCS entities associated with the core network to authenticate clients and subscriber subscriptions to aspects of the LCS.
The Um/Uu/Uu-LTE interfaces may also be used for broadcast of information that may be used by the UE or stand-alone LMU for their LCS operations. This may, for example, include timing information about nearby Node-B/BTS transmissions that may assist the UE or LMU in making their measurements. In UTRAN code information may be included.
The Um, Uu and Uu-LTE interfaces may also pass messages relating to changes or reporting of the data associated with the Location System Operations Function (LSOF) in the UE or the remote LMU.
UTRAN Stage 2 specification TS 25.305 specifies LCS signalling over the Uu interface and GERAN Stage 2 specification TS 43.059 specifies LCS signalling over the Um interface correspondingly. E-UTRAN Stage 2 specification TS 36.305 specifies LCS signalling over the Uu-LTE interface.
Message segmentation is specified in GERAN LCS Stage 2, TS 43.059.
Up

7.3  MAP Interfaces  p. 48

The following interfaces are based on MAP in LCS.
  • Lh interface: interface between GMLC and HSS. This interface is used by the GMLC to request the address of the H-GMLC, and/or the address of the visited MSC or SGSN for a particular target UE whose location has been requested
  • Lg interface: interface between GMLC MSC and GMLC - SGSN. This interface is used by the GMLC to convey a location request to the MSC or SGSN currently serving a particular target UE whose location was requested. The interface is used by the MSC or SGSN to return location results to the GMLC.
  • Lc interface: interface between GMLC and gsmSCF, CAMEL. This interface is used to get location information for CAMEL based services.
The following MAP services are defined for LCS.
  • MAP-SEND-ROUTING-INFO-FOR-LCS Service.
This service is used between the GMLC and the HLR/HSS to retrieve the routing information needed for routing a location service request to the serving VMSC , SGSN. The service may be used in GMLC - HSS interface to retrieve routing information in order to route the location service request to the correct VMSC, SGSN and MSC Server.
In case the service is used between the R-GMLC and the HSS, the H-GMLC address of the target UE to be located is retrieved. The address of the V-GMLC associated with the serving node and PPR may also be retrieved.
  • MAP-PROVIDE-SUBSCRIBER-LOCATION Service.
This service is used by a GMLC to request the location and optionally, velocity, of a target UE from the visited MSC, SGSN or MSC Server at any time.
  • MAP-SUBSCRIBER-LOCATION-REPORT Service.
This service is used by a VMSC, SGSN or MSC Server to provide the location of a target UE to a GMLC when a request for location is either implicitly administered or made at some earlier time.
The MAP Subscriber Location Report could also be used to send information about location and, if requested and available, velocity of the Target UE (for MO LR) to an external client.
Up

7.4  Lpp interface |R6|  p. 48

Lpp is the interface between H-GMLC and PPR. If the UE subscribers LCS privacy information is kept in the PPR this interface is used by the H-GMLC to request the PPR to perform a privacy check. The Lpp interface shall conform to the protocol as specified in (reference to be added) and the procedures defined in clause 9 of this specification.

7.4.1  LCS Authorisation Request  p. 48

Via the LCS Authorisation Request, the H-GMLC can request the PPR to perform the privacy check. There exist two types of LCS Authorisation Request:
  • LCS Authorisation Request without location estimate (send by H-GMLC before location request);
  • LCS Authorisation Request with location estimate (to check location related privacy settings).
The following attributes are identified for LCS Authorisation Request information flow:
  • Target UE identity, (one or both of MSISDN and IMSI), if needed;
  • If PPR contains PMD functionality the LCS Authorisation Request may contain the same information as the LCS Identity request, i.e. the pseudonym of the target UE, if needed.
  • Indication on call/session related MT-LR;
  • LCS Client identity, i.e. LCS client external identity or internal identity;
  • LCS Client type, (i.e. Value added, Emergency, PLMN operator or Lawful interception);
  • LCS Client name, if needed (and type of LCS client name if available);
  • Service type, if needed;
  • Codeword, if needed;
  • Requestor identity, if needed (and type of Requestor identity if available);
  • Type of location, i.e. "current location", "current or last known location" or "initial location";
  • Velocity of the UE, if needed;
  • LCS capability sets of serving nodes, if needed;
  • Location estimate, if needed and available (This is only relevant for LCS Authorisation Request with location estimate);
  • Type of Deferred Location Request, if needed (i.e. UE available, Change of Area, Motion or Periodic Location);
  • Geographic area for change of area event, if needed;
  • Parameters for Periodic Location event, if needed (i.e. reporting interval, total number of reports, request for MO-LR short circuit).
  • Parameters for change of area event, if needed (i.e. type of area event, indication of single or multiple reports, minimum interval between reports, whether location estimates are requested, duration, maximum interval between reports, maximum sampling interval);
  • Parameters for motion event, if needed (i.e. linear distance threshold, indication of single or multiple reports, minimum interval between reports, whether location estimates are requested, duration, maximum interval between reports, maximum sampling interval).
Up

7.4.2  LCS Authorisation Response  p. 49

The LCS Authorisation Response is sent by the PPR to the H-GMLC as the result for the LCS Authorisation Request.
The following attributes are identified for the LCS Authorisation Response information flow:
  • Indicator for location request is to be barred, if needed. If this is set, no other indicators shall be included in the response;
  • Indicator for call/session related class of privacy check related actions, if needed;
    • positioning not allowed;
    • positioning allowed without notifying the UE user;
    • positioning allowed with notification to the UE user;
    • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification;
    • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user.
  • Indicator for call/session unrelated class of privacy check related actions, if needed;
    • positioning not allowed;
    • positioning allowed without notifying the UE user;
    • positioning allowed with notification to the UE user;
    • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification;
    • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user.
  • Pseudo external ID, if needed (see Annex C);
  • Indicator on additional privacy check with location estimate, if needed;
  • Indicator on additional notification/verification by the UE user without positioning (existing location estimate to be returned to the LCS Client if this is successful), if needed;
  • Same information as in the LCS Identity Response, in case the PMD is integrated in PPR, if needed;
  • Indicator for MO-LR short circuit allowed/not allowed, if needed.
Up

7.4.3  LCS Privacy Profile Update notification  p. 50

The LCS Privacy Profile Update notification is sent to the H-GMLC from the PPR in order to notify the H-GMLC about the change of UEs privacy profile.
  • Target UE identity, (one or both of MSISDN and IMSI);
  • Indication on the changed UEs privacy profile

7.4.4  LCS Privacy Profile Update notification ack  p. 50

The LCS Privacy Profile Update notification ack. is sent to the PPR as the result of the LCS Privacy Profile Update Request by H-GMLC.
  • Acknowledgement

7.5  Lid interface |R6|  p. 50

Lid is the interface between H-GMLC and PMD. If the UE subscribers pseudonym can be mapped or decrypted to the corresponding verinym in the standalone PMD. The Lid interface shall conform to the protocol as specified in (reference to be added) and the procedures defined in clause 9 of this specification.

7.5.1  LCS Identity Request  p. 50

Via the LCS Identity Request, the H-GMLC can request the PMD to retrieve the verinym of the subscriber.
The following attribute is identified for the LCS Identity Request:
  • Pseudonym;

7.5.2  LCS Identity Response  p. 50

The PMD sends the LCS Identity Response to the H-GMLC as a result of the LCS Identity Request by the H-GMLC.
The following attribute is identified for the LCS Identity Response information flow:
  • Target UE identity, (one or both of MSISDN and IMSI);

7.6  IMS related Interfaces |R6|  p. 50

7.6.1  Dh Interface  p. 50

Dh is the interface between LIMS-IWF and SLF. The purpose of this interface is to retrieve the address of the correct HSS serving the user. Dh is an optional interface.

7.6.2  Sh Interface  p. 51

Sh is the interface between LIMS-IWF and HSS. The purpose of this interface is to retrieve the user's MSISDN.

7.6.3  Ml Interface |R9|  p. 51

Ml is the interface between the E-CSCF and LRF. For details, refer to TS 23.167.

7.7  SLg Interface |R9|  p. 51

SLg is the interface that is used by the GMLC to convey a location request to the MME currently serving a particular target UE whose location was requested. The interface is also used by the MME to return location results to the GMLC.

7.8  SLs Interface |R9|  p. 51

SLs is the interface between the MME and the E-SMLC. This interface is used to convey location requests from the MME to the E-SMLC and to convey corresponding location reports back from the E-SMLC to the MME.
It is also used for tunnelling core network measurement requests from the E-SMLC to the RAN, using RAN specified protocols transparent to the MME as described in TS 36.305.

7.9  SLh Interface |R9|  p. 51

SLh is the Diameter based interface between the HSS and the GMLC as described in TS 29.173.

7.10  SLm Interface |R11|  p. 51

SLm is the interface between the E-SMLC and the LMU. This interface allows the E-SMLC to exchange measurement information with the LMU for the purpose of UTDOA positioning as described in TS 36.305.

7.11  Lgd Interface |R12|  p. 51

Lgd is the interface that is used by the GMLC to convey a location request to the SGSN currently serving a particular target UE whose location was requested. The interface is also used by the SGSN to return location results to the GMLC. This interface is applicable only for an SGSN supporting EPS based interfaces and protocols.

Up   Top   ToC