Content for TS 23.289 Word version: 20.1.0

0… 4… 4.7… 4.7.4… 4.8… 5… 5.4… 6… 6.3… 6.3.2… 7… 7.2.4… 7.3… 7.3.3… 7.3.3.2… 7.3.3.4… 7.3.3.5… 7.3.3.7… 7.3.3.8… 7.3.3.9… 7.3.3.10… 7.3.3.11… 7.3.3.12… 7.3.3.13… 7.4… 7.5… 7.6… A…

7.5 Enhancements for Location management over 5GS 7.5.1 General 7.5.2 Information flows for location information 7.5.2.1 General 7.5.2.2 Location reporting configuration 7.5.2.3 Location information report 7.5.3 Procedure 7.5.3.1 General 7.5.3.2 Event-triggered location reporting procedure
...

7.5 Enhancements for Location management over 5GS |R18| p. 102

7.5.1 General p. 102

In addition to the location management functions defined in TS 23.280, the location management system over 5GS shall support the following enhancement:

Inter-system RAT changes event triggering and report as described in clause 7.3.3.9.1.
Serving and neighbouring 5G NR Cell Global Identifiers (NCGI) as optional Location Information elements in the information flows of clause 10.9.2 of TS 23.280.
The MC service server can subscribe to the PCF related notification to obtain the MC service UE location information as described in TS 23.503.
The reference point between the location management server and the 5GS to obtain location information from the PLMN operator can either be the Le reference point or the N33 reference point indirectly via the NEF, as described in TS 23.273.

7.5.2 Information flows for location information p. 103

7.5.2.1 General p. 103

In this clause, only those information flows which requires enhancement to TS 23.280 for MC services over 5G specific are included.

7.5.2.2 Location reporting configuration p. 103

Table 7.5.2.2-1 describes the information flow from the location management server to the location management client for the location reporting configuration.

Compared to that is defined in TS 23.280, the following changes are made:

Allowing the location management server to configure location reporting by including inter-RAT trigger information.
Adding a new NOTE 3 to clarify the usage of triggering event for inter-RAT changes.

Table 7.5.2.2-1: Location reporting configuration

Information element	Status	Description
MC service ID	M	Identity of the MC service user to which the location reporting configuration is targeted.
Requested non-emergency location information	O (see NOTE 1)	Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts.
Requested emergency location information	O (see NOTE 1)	Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts.
Triggering criteria in non- emergency cases	O (see NOTE 1 and NOTE 3)	Identifies when the location management client will send the location report in non-emergency cases.
Handling criteria in not reporting location information cases	O	Identifies when the location management client will store location information (e.g. never, off-network, IOPS)
Triggering criteria in not reporting location information cases	O (see NOTE 2)	Identifies the causes when the location management client will generate location information.
Minimum time between consecutive reports	O (see NOTE 1)	Defaults to 0 if absent and 0 for emergency calls, imminent peril calls and emergency alerts.
Triggering criteria in emergency cases	O (see NOTE 1)	Identifies when the location management client will send the location report in emergency cases.
NOTE 1: If none of the information elements is present, this represents a cancellation for location reporting based on Triggering criteria in emergency and non-emergency cases, if configured. NOTE 2: If not present, location information is generated based on Triggering criteria in emergency and non-emergency cases, if configured. NOTE 3: Triggering criteria can contain the inter-RAT trigger information if the inter-system RAT changes information is expected from the LMC in case of LTE eMBMS and 5G MBS co-existence.

7.5.2.3 Location information report p. 104

Table 7.5.2.3-1 describes the information flow from the location management client to the location management server for the location information reporting.

Compared to that is defined in TS 23.280, the following changes are made:

Allowing the location management client to report the the inter-RAT information in the location information report;
Adding a new NOTE 5 to clarify the usage of triggering event for inter-RAT changes

Table 7.5.2.3-1: Location information report (LMC - LMS)

Information element	Status	Description
Set of MC service IDs	M	Set of identities of the reporting MC service user on the MC service UE (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID (see NOTE 4)	O	Identity of the requesting MC service user.
Functional alias(es) (see NOTE 1)	O	Functional alias that corresponds to the reporting MC service ID
MC service UE label	O	Generic name of the reporting MC service UE
Triggering event (see NOTE 3 and NOTE 5)	M	Identity of the event that triggered the sending of the report
Location Information (see NOTE 2 and NOTE 5)	M	Location information of the individual MC service user
NOTE 1: Each functional alias corresponds to an individual MC service ID. NOTE 2: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, eMBMS SAIs, MBS FSA ID(s), with at least one provided. NOTE 3: An on-demand request may be the triggering event. NOTE 4: In case of an on-demand request of an MC service user the MC service ID shall be provided. In case of an MC service server request or an event-triggered report, no MC service ID is provided. NOTE 5: Triggering event can contain the inter-RAT information if the inter-RAT changes information is expected from the LMC in case of LTE eMBMS and 5G MBS co-existence.

Table 7.5.2.3-2 describes the information flow from the location management server to the MC service server for location information reporting.

Compared to that is defined in TS 23.280, the following changes are made:

Adding a new NOTE 4 to clarify the usage of triggering event for inter-RAT changes.

Table 7.5.2.3-2: Location information report (LMS - MC service server)

Information element	Status	Description
Set of MC service IDs	M	Set of identities of the reporting MC service user on the MC service UE (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias(es) (see NOTE 1)	O	Functional alias that corresponds to the MC service ID.
Triggering event (see NOTE 3 and NOTE 4)	M	Identity of the event that triggered the sending of the report
Location Information (see NOTE 2 and NOTE 4)	M	Location information of the individual MC service user
NOTE 1: Each functional alias corresponds to an individual MC service ID. NOTE 2: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, MB FSA ID(s), with at least one provided. NOTE 3: An on-demand request may be the triggering event. NOTE 4: Triggering event can contain the inter-RAT information if the inter-RAT information is expected from the LMC in case of LTE eMBMS and 5G MBS co-existence.

7.5.3 Procedure p. 105

7.5.3.1 General p. 105

In this clause, only the procedure which requires enhancement to TS 23.280 for MC services over 5G specific are included.

7.5.3.2 Event-triggered location reporting procedure p. 105

The location management server provides location reporting configuration to the location management clients, indicating what information the location management server expects and what events will trigger the sending of this information to the location management server. For eMBMS and MBS co-existing, the MC service server needs to obtain the inter-RAT information. If the inter-RAT information report from the MC service UE is expected, the MC service server may obtain the inter-RAT information from the location management server, and the location management server then performs the procedure as described clause 10.9.3.1 of TS 23.280, clause 7.5.2.2 and 7.5.2.3. In addition to those trigger criteria defined in TS 23.280, the new inter-RAT triggers may include, the change of MBS FSA ID, inter-system RAT type changes. The location information report contains the inter- RAT information.

Similar to the usage of eMBMS bearer for transmitting of location reporting configuration defined in TS 23.280, the location reporting configuration message can also be sent over 5G MBS Session.