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 33.128  Word version:  18.7.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.7…   6…   6.2.2.2A…   6.2.3…   6.2.3.2.7…   6.2.3.3…   6.2.4…   6.3…   6.3.2.2A…   6.3.3…   6.3.3.2…   6.3.3.2.4…   6.3.3.2A…   7…   7.3…   7.3.3…   7.3.3.2.21…   7.3.3.2.42…   7.3.3.2.63…   7.3.4…   7.4…   7.4.3.8…   7.5…   7.6…   7.7…   7.7.4…   7.8…   7.8.4…   7.9…   7.10…   7.10.4…   7.11…   7.12…   7.13…   7.13.3…   7.13.3.4…   7.14…   7.15…   8…   A…   D…   E…   M… 
7.3 Location  7.3.1 Lawful Access Location Services (LALS)  7.3.1.1 General description  7.3.1.2 Provisioning over LI_X1  7.3.1.2.1 Target positioning service  7.3.1.2.2 Triggered location service  7.3.1.3 Triggering over LI_T2  7.3.1.4 Generation of xIRI over LI_X2  7.3.1.5 Generation of IRI over LI_HI2  7.3.2 Cell database information reporting  7.3.2.1 General description  7.3.2.2 Delivery of cell site information over LI_HI2 
...

 

7.3  Location  p. 170

7.3.1  Lawful Access Location Services (LALS)  p. 170

7.3.1.1  General description  p. 170

The LALS architecture and functionality is specified in clause 7.3.3 of TS 33.127.

7.3.1.2  Provisioning over LI_X1  p. 170

7.3.1.2.1  Target positioning service  p. 170
For the LALS target positioning service (clause 7.3.3.2 of TS 33.127) the IRI-POI provided by the LI-LCS Client is directly provisioned over LI_X1 by the LIPF using the LI_X1 protocol as described in clause 5.2.2 with the TaskDetailsExtensions field of the ActivateTask message specifying the type of the target positioning request, immediate vs. periodic, and, in the latter case, the periodicity of the positioning requests.
Based on national regulatory requirements and CSP policy, the TaskDetailsExtensions may also include the QoS parameters (specified in OMA-TS-MLP-V3_5-20181211-C [20]) for the use on the Le interface towards the LCS Server/GMLC. Alternatively, the QoS parameters may be statically configured in the LI-LCS Client.
Table 7.3.1.2-1 shows the details of the LI_X1 ActivateTask message used for the LI-LCS Client provisioning for the target positioning service.
The LI_X1 DeactivateTask shall be issued by the LIPF to terminate the target positioning service and withdraw the associated provisioning data, except for the Immediate target positioning service in which case the LI_X1 DeactivateTask is not used.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF.M
TargetIdentifiers One of the following (see ETSI TS 103 221-1 [7]):
  • SUPIIMSI.
  • SUPINAI.
  • GPSIMSISDN.
  • GPSINAI.
  • IMSI.
  • MSISDN (E164Number target ID format, per ETSI TS 103 221-1 [7]).
  • IMPU.
M
DeliveryType Set to "X2Only". M
ListOfDIDs Delivery endpoints of LI_X2 interface. These delivery endpoints are configured in LI-LCS Client using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
TaskDetailsExtensions/ PositioningServiceType "Immediate" or "Periodic". M
TaskDetailsExtensions/ PositioningPeriodicityTime interval between the positioning requests in case of Periodic positioning, in seconds.C
TaskDetailsExtensions/ PositioningParameters Set of optional parameters for MLP SLIR message, per OMA-TS-MLP-V3_5-20181211-C [20]:
  • requested location type (clause 5.3.60).
  • requested response type (clause 5.3.112.1).
  • max location age (clause 5.3.65).
  • response timing required (clause 5.3.106).
  • response timer (clause 5.3.107).
  • horizontal accuracy with QoS class (clause 5.3.44).
  • altitude accuracy with QoS class (clause 5.3.6).
  • motion state request (clause 5.3.70).
O
Up
7.3.1.2.2  Triggered location service  p. 171
For the LALS triggered location service (clause 7.3.3.3 of TS 33.127) the LTF, as an IRI-TF, is provisioned by the LIPF using the LI_X1 protocol as described in clause 5.2.2. The "TaskDetailsExtensions" parameter of the ActivateTask message in this case will carry the address of LI-LCS Client to be used for the service and, optionally, the positioning parameters for use on the Le interface, similar to the target positioning provisioning.
Prior to issuing one or more "ActivateTask" requests towards an LTF, the LIPF shall provision the LTF with the LI_X2 destinations by using the "CreateDestination" operation(s), as per clause 5.2.2.
Table 7.3.1.2-2 defines the details of the LI_X1 ActivateTask message used for the LTF provisioning for the Triggered Location service.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF.M
TargetIdentifiers One or more of the following (see ETSI TS 103 221-1 [7]):
  • SUPIIMSI.
  • SUPINAI.
  • GPSIMSISDN.
  • GPSINAI.
  • IMSI.
  • MSISDN (E164Number target ID format, per ETSI TS 103 221-1 [7]).
  • IMPU.
M
DeliveryType Set to "X2Only". M
ListOfDIDs Delivery endpoints for LI-LCS Client LI_X2. These delivery endpoints are configured in LTF using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
TaskDetailsExtensions/ LILCSClientAddressThe IP address of the LI-LCS Client for triggering.M
TaskDetailsExtensions/ PositioningParameters Set of optional parameters for MLP SLIR message, per OMA-TS-MLP-V3_5-20181211-C [20]:
  • requested location type (clause 5.3.60).
  • requested response type (clause 5.3.112.1).
  • max location age (clause 5.3.65).
  • response timing required (clause 5.3.106).
  • response timer (clause 5.3.107).
  • horizontal accuracy with QoS class (clause 5.3.44).
  • altitude accuracy with QoS class (clause 5.3.6).
  • motion state request (clause 5.3.70).
O
Up

7.3.1.3  Triggering over LI_T2  p. 172

An LTF, as an IRI-TF, provisioned as described in clause 7.3.1.2.2, triggers the LI-LCS Client (which plays the role of a triggered IRI-POI) using the LI_T2 protocol as described in clause 5.2.4. The "TaskDetailsExtensions" in the LI_T2 "ActivateTask" message carries the positioing parameters mapped from information the LTF receives from the ADMF over the LI_X1. The LI_T2 "ActivateTask" message header may include a correlation ID from the triggering xIRI, if available.
Prior to issuing one or more "ActivateTask" requests towards an LI-LCS Client, the LTF shall provision the LI-LCS Client with the LI_X2 destinations by using the "CreateDestination" operation(s), as per clause 5.2.2. The LI-LCS Client shall deactivate the task on its own upon issuing the final xIRI for the trigger. There is no DeactivateTask operation on the LI_T2 for the LI-LCS Client.
Table 7.3.1.3-1 shows the details of the LI_T2 ActivateTask message used by the LTF to trigger LI-LCS Client for the triggered location service.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDThe same value as in the LTF provisioning (clause 7.3.3.2.2).M
TargetIdentifiers One of the following (see ETSI TS 103 221-1 [7]):
  • SUPIIMSI.
  • SUPINAI.
  • GPSIMSISDN.
  • GPSINAI.
  • IMSI.
  • MSISDN (E164Number target ID format, per ETSI TS 103 221-1 [7]).
  • IMPU.
M
DeliveryType Set to "X2Only". M
ListOfDIDs Delivery endpoints for LI-LCS Client LI_X2. These delivery endpoints are configured in LI-LCS Client by the LTF using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
CorrelationIDCorrelates the requested location to the triggering xIRI, if available.C
TaskDetailsExtensions/ PositioningParameters Set of optional parameters for MLP SLIR message, per OMA-TS-MLP-V3_5-20181211-C [20]:
  • requested location type (clause 5.3.60).
  • requested response type (clause 5.3.112.1).
  • max location age (clause 5.3.65).
  • response timing required (clause 5.3.106).
  • response timer (clause 5.3.107).
  • horizontal accuracy with QoS class (clause 5.3.44).
  • altitude accuracy with QoS class (clause 5.3.6).
  • motion state request (clause 5.3.70).
O
Up

7.3.1.4  Generation of xIRI over LI_X2  p. 173

The IRI-POI provided by the LI-LCS client shall deliver the target location reports to respective MDF(s) as xIRI over the LI_X2 interface.
Field name Type Cardi­nality Description M/C/O
sUPISUPI0..1SUPI of the target, if used for the service (see NOTE).C
deprecatedPEIPEI0..1No longer used in present version of this specification.C
gPSIGPSI0..1GPSI of the target, if used for the service (see NOTE).C
locationLocation0..1Location of the target, if obtained successfully.
Encoded as a Location.positioningInfo parameter. Both the Location.positioningInfo.positionInfo parameter and the Location.positioningInfo.rawMLPResponse.mLPPositionData parameter are present in the case of successful positioning. In the case of positioning failure only the Location.positioningInfo.rawMLPResponse.mLPErrorCode parameter is present.		C
iMPUIMPU0..1IMPU of the target, if used for the service (see NOTE).C
iMSIIMSI0..1IMSI of the target, if used for the service (see NOTE).C
mSISDNMSISDN0..1MSISDN of the target, if used for the service (see NOTE).C
NOTE:
One and only one of SUPI, GPSI, IMSI, MSISDN, IMPU shall be present and it shall correspond to the target identifier included in the respective ActivateTask message for the LI-LCS Client.
The LI-LCS Client generating an xIRI containing an LALSReport record shall set the Payload Direction field in the PDU header to not applicable (Direction Value 5, see ETSI TS 103 221-2 [8] clause 5.2.6).
The LI_X2 header (as per clause 5.3.2) of the LALSReport record presented in Table 7.3.1.4-1 shall contain the correlation ID (if provided) from a respective LI_T2 ActivationTask message.
Up

7.3.1.5  Generation of IRI over LI_HI2  p. 174

The LALSReport payload, defined in clause 7.3.1.4, shall be used as the payload of the respective LALSReport record, no payload mediation is required.
A LALSReport message shall be assigned the same CIN (see ETSI TS 102 232-1 [9] clause 5.2.4) as the IRI message that triggered the LALS reporting, if that triggering IRI message is assigned a CIN. Otherwise, i.e. when the LALSReport is a result of the LALS Target Positioning, or the triggering IRI message has no CIN assigned, the CIN in the LALSReport shall be omitted.
Up

7.3.2  Cell database information reporting  p. 174

7.3.2.1  General description  p. 174

When the location information present within an xIRI includes the cell identity, the MDF2 that receives the xIRI may retrieve the cell site information and associated cell radio related information for that cell from a CSP database and deliver the same to the LEMF either within the IRI message generated from the received xIRI or in a separate IRI message containing the MDFCellSiteReport record.
For each intercept, if the MDF2 reports the cell site information, then it shall provide such information at least on the initial appearance of the cell identity in the related xIRI.
If the reported cell site information is for a cell with mobility, the MDF2 should report the current information (e.g. physical location of the cell) with every related xIRI.
Up

7.3.2.2  Delivery of cell site information over LI_HI2  p. 174

The cell site information is encoded as the cellSiteInformation ASN.1 parameter and delivered either within the location field of an IRI message carrying the respective cell identity, or in a stand-alone IRI message containing the MDFCellSiteReport record.
The cell radio related information is encoded as the cellRadioRelatedInformation ASN.1 parameter and delivered with the cell information parameter.
The MDF2 shall use the IRI message containing the MDFCellSiteReport record to convey cell site information and cell radio related information retrieved asynchronously with the sending of the IRI message that caused the retrieval. The MDFCellSiteReport record shall be delivered as an IRI REPORT (see ETSI TS 102 232-1 [9] clause 5.2.10) and allocated the same CIN, if any, as the IRI message that caused the retrieval.
When the cell site information and cell radio related information are readily available at MDF2 or are retrieved synchronously (i.e. blocking the sending of the IRI message until the retrieval is complete), the cell site information shall be conveyed within the location field of the IRI message that caused the retrieval.
The cell site information and associated cell radio related information for multiple cell identities can be delivered to the LEMF within an IRI message that carries the respective cell identities or within the IRI message containing the MDFCellSiteReport record (see Annex A).
The MDF2 generating the IRI message MDFCellSiteReport shall set the Payload Direction field in the PDU header to not applicable (Direction Value 5, see ETSI TS 103 221-2 [8] clause 5.2.6).
The MDFCellSiteReport consists of a sequence of cellInformation as described in the following tables.
Field name Type Cardi­nality Description M/C/O
rANCGIRANCGI1The RAN CGI for the cell being reported.M
cellSiteInformationCellSiteInformation0..1Contains location information for the cell site being reported. Shall be present if known at the NF where the POI is located or at the MDF.C
timeOfLocationTimestamp0..1The time the cell site information was determined.C
cellRadioRelatedInformationCellRadioRelatedInformation0..1Radio Information of reported cell to include either NG Information or F1 Information.C
BandRFBand0..1RFBand of reported cell.C
Field name Type Cardi­nality Description M/C/O
geographicalCoordinatesGeographicalCoordinates1The coordinates for the cell site being reported.M
azimuthINTEGER (0..359)0..1Contains the center azimuth for the sector being reported. Shall be present if known.C
operatorSpecificInformationUTF8String0..1Information specific to the operator reporting the cell site information.C
Field name Type Description
nGInformationNGInformation Information pertaining to the set up of the NG Interface. See clause 9.2.6.1 of TS 38.413 and 9.2.6.2.
f1InformationF1Information Information pertaining to the set up of the F1 Interface. See clause 9.2.1.4 of TS 38.473 and 9.2.1.5.
Up

Up   Top   ToC