Location Request Parameter | Difference | Comments |
---|---|---|
Target UE Identity |
GPSI, SUPI or pseudonym in this TS
MSISDN, IMSI or pseudonym in TS 23.271 | |
LCS QoS | None | |
Supported GAD shapes | None | |
LCS Client type | None | |
Called Party Number | Not supported in this TS | If provided, this parameter should be ignored by a GMLC |
APN NI | Not supported in this TS | If provided, this parameter should be ignored by a GMLC |
Service Identity | None | |
Codeword | None | |
Service coverage information | None | |
Requestor Identity | Not supported in this TS | If provided, this parameter should be ignored by a GMLC |
Type of Requestor Identity | Not supported in this TS | If provided, this parameter should be ignored by a GMLC |
Type of a deferred location request | None | |
Periodic Location parameters | None | |
Area Event parameters | None | |
Motion Event parameters | None |
Information Storage Item(s) | Difference | Comments |
---|---|---|
UE Privacy Universal Class | Not supported in this TS | This privacy class should not be supported for 5GC capable UEs on the EPS side to avoid differences in LCS privacy support between EPS access and 5GS access for the same UE. (Note 1) |
UE Location Privacy Indication | Not supported in TS 23.271 | This indication can create differences between LCS client access to a UE which has 5GS access versus EPS access. (Note 1) |
UE Privacy Call/Session related Class | Not supported in this TS | This privacy class should not be supported for 5GC capable UEs on the EPS side to avoid differences in LCS privacy support between EPS access and 5GS access for the same UE. (Note 1) |
UE Privacy Call/Session unrelated Class | Supported as defined in TS 23.271 with the following differences: | This privacy class can create differences between LCS client access to a UE which has 5GS access versus EPS access. (Note 1) |
UE Privacy PLMN Operator Class | None | |
UE LCS Mobile Originating Data | None | |
NOTE 1:
A PLMN operator can avoid any difference in UE privacy support for EPS access versus 5GS access by only storing information for UE privacy (in the UE LCS privacy profile) in a UDR (and UDM) and not in an HSS or GMLC.
|
Information Storage Item(s) | Difference | Comments |
---|---|---|
LCS Client Type | None | |
External identity | None | |
Authentication data | None | |
Call/session related identity | Not supported in this TS | This information item can create differences between LCS client access to a UE which has 5GS access versus EPS access. (Note 1) |
Internal identity | None | |
Client name | None | |
Client name type | No difference except that this TS adds a Client Name type in the form of a GPSI. |
A GPSI can be an MSISDN or External Identifier in the form of "username@realm" as defined in TS 23.003.
TS 23.271 allows an MSISDN but the External Identifier is not included. |
Override capability | None | |
Authorized UE List | None | |
Priority | None | |
QoS parameters | None | |
Service Coverage | None | |
Allowed LCS + Request Types |
TS 23.271 includes the following items which are not in this TS:
| This TS should take precedence (Note 1) |
Local Co-ordinate System | None | |
Access Barring List(s) | TS 23.271 includes a list of MSISDNs.
This TS includes a list of SUPIs | This TS can take precedence (Note 1) |
Service Identities | None | |
Maximum Target UE Number | None | |
NOTE 1:
A PLMN operator can avoid any difference in LCS Client support for a target UE with EPS access versus 5GS access by only storing information for an LCS Client in a GMLC as defined in this TS.
|
UE LCS Privacy Feature | Difference | Comments |
---|---|---|
Privacy Override Indicator (POI) | None | |
UE Privacy Universal Class | Not supported in this TS | This class allows a UE to subscribe to location by any LCS client. For such a UE, a 5GC GMLC will not support such location. |
Location Privacy Indication | Not supported in TS 23.271 | |
UE Privacy Call/Session related Class | Not supported in this TS | This class permits location by LCS clients to which the UE has established a PS session. A 5GC GMLC will not allow such location. However, the location can be allowed as part of the Call/Session unrelated class. |
UE Privacy Call/Session unrelated Class | Supported as defined in TS 23.271 with the following differences: An optional valid time period is added. An optional valid geographic area is added | The optional valid time period and valid geographic area allow more precise control of location reporting. For example, tracking of employees by an employer can be restricted to a work location and/or normal work hours. |
UE Privacy PLMN Operator Class | Supported as defined in TS 23.271 |