Content for TS 23.280 Word version: 19.5.1
1…
5…
6
7…
8…
9…
10…
10.1.5…
10.2…
10.2.6…
10.3…
10.6…
10.7…
10.7.3.8…
10.8…
10.9…
10.9.3.9…
10.10…
10.10.3
10.11…
10.12…
10.13…
10.14…
10.15…
10.16…
10.17…
10.18…
10.18.3…
11…
11.5…
A…
B…
C…
E…
10.9 Location management (on-network)
10.9.1 General
10.9.2 Information flows for location information
10.9.3 Procedure
10.9.3.1 Event-triggered location reporting procedure
10.9.3.2 On-demand location reporting procedure
10.9.3.3 Client-triggered location reporting procedure
10.9.3.4 Event-triggered location reporting cancel procedure
10.9.3.4a Client-triggered location reporting cancel procedure targeting MC service user(s)
10.9.3.4b Client-triggered location reporting cancel procedure targeting MC service group(s)
10.9.3.5 Location information subscription procedure
10.9.3.6 Usage of location information procedure
10.9.3.7 Location information cancel subscription procedure
10.9.3.8 Location management using functional alias
...
...
10.9 Location management (on-network) p. 189
10.9.1 General p. 189
Location information of MC service user shall be provided by the location management client to the location management server. The location information may also be provided by the 3GPP core network (i.e., via the PLMN operator). The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided.
An authorized MC service user may subscribe to event-triggered location information of one or more MC service users. By default a subscribed MC service user will receive location information based on the location reporting configuration in the user profile of the reporting MC service user.
An authorized and subscribed MC service user may initiate a trigger request procedure to modify the location reporting triggers for one or more reporting MC service users. The location management server aggregates trigger requests from the MC service servers and from location management clients towards the same target location management client and may adjust the location reporting triggers of the reporting MC service users as required.
When a subscribed MC service user cancels the subscription, the location management server stops delivering location reports to this MC service user and the location management server may adjust the aggregated location reporting triggers of the reporting MC service users as required.
The location information provided by the 3GPP core network can be obtained from the location services feature in EPS (i.e., LCS) as described in TS 23.271, or from the PCRF as part of the PCC mechanism once the MC service server subscribes to related notifications from the PCRF as described in TS 23.203.
The location management client can be configured to store location information while not reporting location information to the location management server. The location management client may report stored location information to the location management server.
In the information flows of clause 10.9.2, and procedures of clause 10.9.3:
- the term "requesting MC service user" is used to refer to the MC service user which sends a request to subscribe to location information reports, to trigger a location information report or to modify existing location information triggers from another MC service user;
- the term "requested MC service user" is used to refer to the MC service user whose location information is requested or existing location information triggers are to be modified; and
- the term "reporting MC service user" is used to refer to the MC service user which provides location related information based on on-demand request or trigger criteria.
10.9.2 Information flows for location information p. 190
10.9.2.1 Location reporting configuration p. 190
Table 10.9.2.1-1 describes the information flow from the location management server to the location management client for the 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) | 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 for emergency cases | O
(see NOTE 1) | Identifies the location update rate for emergency and imminent peril cases. Defaults to 0 if absent. |
| Minimum time between consecutive reports for non-emergency cases | O
(see NOTE 1) | Identifies the location update rate for non-emergency cases. |
| 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.
|
||
10.9.2.2 Location information report p. 191
Table 10.9.2.2-1 describes the information flow from the location management client to the location management server for the location information reporting.
| 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 MC service ID. |
| Functional alias | O | Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service UE label (see NOTE 5) | O | Generic name of the reporting MC service UE. |
| Triggering event (see NOTE 3) | M | Identity of the event that triggered the sending of the report. |
| Location Information (see NOTE 2) | 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, 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:
This information element shall be present in case the "MC service UE label" parameter in the initial MC service UE configuration data has a non-null value.
|
||
Table 10.9.2.2-2 describes the information flow from the location management server to the location management client for location information reporting.
| 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 | M | Identity of the requesting MC service user. |
| Functional alias(es) (see NOTE 1) | O | Functional alias that corresponds to the reporting MC service ID. |
| Functional alias | O | Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service UE label (see NOTE 4) | O | Generic name of the reporting MC service UE. |
| Triggering event (see NOTE 3) | M | Identity of the event that triggered the sending of the report. |
| Location Information (see NOTE 2) | 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, with at least one provided.
NOTE 3:
An on-demand request may be the triggering event.
NOTE 4:
This information element shall be present in case the "MC service UE label" parameter in the initial MC service UE configuration data has a non-null value.
|
||
Table 10.9.2.2-3 describes the information flow from the location management server to the MC service server for location information reporting.
| 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) | M | Identity of the event that triggered the sending of the report. |
| Location Information (see NOTE 2) | 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, with at least one provided.
NOTE 3:
An on-demand request may be the triggering event.
|
||
Table 10.9.2.2-4 describes the information flow to support the handling of location information across MC systems.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user at partner MC system. |
| Functional alias | O
(see NOTE 1) | Functional alias of the reporting MC service user at partner MC system. |
| MC service ID | M
(see NOTE 2) | Identity of the requesting MC service user at primary MC system. |
| Functional alias | O
(see NOTE 2) | Functional alias of the requesting MC service user at primary MC system. |
| MC service UE label (see NOTE 5) | O | Generic name of the reporting MC service UE at partner MC system. |
| Triggering event (see NOTE 3) | M | Identity of the event that triggered the sending of the report. |
| Location Information (see NOTE 4) | M | Location information of the individual MC service user at partner MC system. |
|
NOTE 1:
It shall be present if used with the Functional alias associated request.
NOTE 2:
Only present, if provided with the associated request.
NOTE 3:
An on-demand request may be the triggering event.
NOTE 4:
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, with at least one provided.
NOTE 5:
This information element shall be present in case the "MC service UE label" parameter in the initial MC service UE configuration data has a non-null value.
|
||
10.9.2.3 Location information request p. 193
Table 10.9.2.3-1, Table 10.9.2.3-2 and Table 10.9.2.3-3 describe the information flow from the MC service server to the location management server and from the location management server to the location management client and from location management client to location management server respectively for requesting an immediate location information report.
| Information element | Status | Description |
|---|---|---|
| MC service ID list | O
(see NOTE 1) | List of MC service users whose location information is requested. |
| Functional alias | O
(see NOTE 1) | Location information of MC service users who have activated this functional alias is requested. |
| Requested non-emergency location information | O
(see NOTE 2) | Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
| Requested emergency location information | O
(see NOTE 2) | Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
|
NOTE 1:
Either the MC service ID list or the functional alias must be present.
NOTE 2:
This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
||
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of MC service user whose location information is requested. |
| MC service ID | O | Identity of the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Functional alias | O | Functional alias that corresponds to the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Functional alias | O | Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Requested non-emergency location information | O
(see NOTE) | Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
| Requested emergency location information | O
(see NOTE) | Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
|
NOTE:
This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
||
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service ID list | O
(see NOTE 1) | List of MC service users whose location information is requested. |
| Functional alias | O | Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Functional alias | O
(see NOTE 1) | Functional alias that corresponds to the requested MC service user(s) (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Requested non-emergency location information | O
(see NOTE 2) | Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
| Requested emergency location information | O
(see NOTE 2) | Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
|
NOTE 1:
Either the MC service ID list or the functional alias must be present.
NOTE 2:
This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
||
Table 10.9.2.3-4 describes the information flow to support the handling of location information across MC systems.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M
(see NOTE 1) | Identity of the requesting authorized MC service user at primary MC system. |
| Functional alias | O
(see NOTE 1) | Functional alias that corresponds to the requesting MC service user at primary MC system. |
| MC service ID list | O
(see NOTE 2) | List of identities of those MC service users at partner MC system whose location information are requested. |
| Functional alias | O
(see NOTE 2) | Functional alias of those MC service users at partner MC system whose location information are requested. |
| Requested non-emergency location information | O
(see NOTE 3) | Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
| Requested emergency location information | O
(see NOTE 3) | Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
|
NOTE 1:
Only present if Location information client has initiated the request.
NOTE 2:
Either the MC service ID list or the functional alias must be present.
NOTE 3:
This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
||
10.9.2.4 Location reporting trigger p. 195
Table 10.9.2.4-1 describes the information flow from the location management client to the location management server for triggering a location reporting procedure.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M
(see NOTE 1) | Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Functional alias | O | Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service ID list | O
(see NOTE 1) (see NOTE 3) | Identity of the requested MC service users (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service group ID list | O
(see NOTE 3) | Group ID(s) that correspond to MC service user(s) whose location information is requested (e.g. MCPTT ID, MCVideo ID, MCData ID). This trigger is only for currently affiliated users to these group(s). |
| Functional alias list | O
(see NOTE 3) | Functional alias that corresponds to the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Immediate Report Indicator | O
(see NOTE 2) (see NOTE 4) | Indicates whether an immediate location report is required. |
| Requested non-emergency location information | O
(see NOTE 2) (see NOTE 4) | Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts. |
| Requested emergency location information | O
(see NOTE 2) (see NOTE 4) | Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts. |
| Triggering criteria in non- emergency cases | O
(see NOTE 2) (see NOTE 4) | Identifies when the client will send the location report in non-emergency cases. |
| Triggering criteria in emergency cases | O
(see NOTE 2) (see NOTE 4) | Identifies when the client will send the location report in emergency cases. |
| Minimum time between consecutive reports for emergency cases | O
(see NOTE 2) (see NOTE 4) | Identifies the location update rate for emergency and imminent peril cases. Defaults to 0 if absent. |
| Minimum time between consecutive reports for non-emergency cases | O
(see NOTE 2) (see NOTE 4) | Identifies the location update rate for non-emergency cases. |
| Location reporting trigger override indicator | O
(see NOTE 2, NOTE 6) | Indicates that the existing location reporting triggers at the reporting location management client are to be replaced by the triggers in this flow. |
| Location reporting trigger cancel override indicator | O
(see NOTE 2, NOTE 6, NOTE 7) | Indicates that location reporting trigger override of the reporting location management client is to be cancelled. |
| Reason for overriding location reporting triggers | O
(see NOTE 5) | A text description indicating the reason for override. |
|
NOTE 1:
The identity of the requesting MC service user and the requested MC service user shall belong to the same MC service. E.g. if requesting MC service user is using a MCPTT ID, then the requested MC service user identity shall be an MCPTT ID.
NOTE 2:
At least one of these rows shall be present.
NOTE 3:
Either the MC service ID or the MC service group ID list or the functional alias must be present.
NOTE 4:
This configuration could contain IEs for emergency reporting, for non-emergency reporting or for both cases. If this configuration contains only the emergency case, reporting for the non-emergency case shall happen as per the relevant parameters in the default configuration. If this configuration contains only the non-emergency case, reporting for the emergency case shall happen as per the relevant parameters in the default configuration. (see Table A.8-1).
NOTE 5:
This shall be present if the request is to override the location reporting trigger.
NOTE 6:
Location reporting trigger override indicator cannot occur together with Location reporting trigger cancel override indicator.
NOTE 7:
A location reporting trigger cancel override shall not contain requested location information, triggering criteria and minimum time between consecutive reports.
|
||
10.9.2.4a Location reporting trigger cancel |R19| p. 197
Table 10.9.2.4a-1 describes the information flow from the location management client to the location management server to stop triggering a location reporting procedure.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M
(see NOTE 1) | Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Functional alias | O | Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service ID list | O
(see NOTE 1) (see NOTE 2) | List of MC service users whose location information reporting is to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service group ID list | O
(see NOTE 2) | Group ID(s) that correspond MC service user(s) whose location reporting triggers are to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID). The location reporting triggers are cancelled only for currently affiliated users to these MC service group(s). |
| Functional alias | O
(see NOTE 2) | Functional alias that corresponds to the MC service users whose location information reporting is to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID). |
|
NOTE 1:
The identity of the requesting MC service user and the requested MC service user shall belong to the same MC service. E.g. if requesting MC service user is using a MCPTT ID, then the requested MC service user identity shall be an MCPTT ID.
NOTE 2:
At least one of these information elements shall be present.
|
||
10.9.2.5 Location information subscription request p. 197
Table 10.9.2.5-1 describes the information flow from the MC service server to the location management server for location information subscription request.
| Information element | Status | Description |
|---|---|---|
| MC service ID list | M | List of MC service users whose location information is requested. |
| Time between consecutive reports | M
(see NOTE 1) | Indicates the interval time between consecutive reports. The provided time is to be used for all MC service IDs provided in the MC service ID list. |
| Requested non-emergency location information | O
(see NOTE 2) | Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
| Requested emergency location information | O
(see NOTE 2) | Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
|
NOTE 1:
If the interval time has a value of zero then the location management server will send the Location information notification immediately the location information report is received from the MC service user in the MC service ID list.
NOTE 2:
This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
||
Table 10.9.2.5-2 describes the information flow from the location management client to the location management server for location information subscription request.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the requesting MC service user. |
| MC service ID list | O
(see NOTE 1) | List of MC service users whose location information is requested. |
| MC service group ID list | O
(see NOTE 1) | Group ID(s) that correspond MC service user(s) for whose location information subscription is requested (e.g. MCPTT ID, MCVideo ID, MCData ID). This request is only for currently affiliated users to these group(s). |
| Time between consecutive reports | M
(see NOTE 2) | Indicates the interval time between consecutive reports. The provided time is to be used for all MC service IDs provided in the MC service ID list. |
| Requested non-emergency location information | O
(see NOTE 3) | Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
| Requested emergency location information | O
(see NOTE 3) | Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
|
NOTE 1:
Either the MC service ID list or the MC service group ID list must be present.
NOTE 2:
If the interval time has a value of zero then the location management server will send the Location information notification immediately the location information report is received from the MC service user in the MC service ID list.
NOTE 3:
This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
||
Table 10.9.2.5-3 describes the information flow from the location management server in the primary MC system to the location management server in the partner MC system for the location information subscription request.
| Information element | Status | Description |
|---|---|---|
| MC service ID (see NOTE 1) | M | Identity of the requesting MC service user in the primary MC system. |
| MC service ID list | M | List of the identities of MC service users in the partner MC system whose location information are requested. |
| Time between consecutive location notifications (see NOTE 2) | M | Indicates the interval time between consecutive location notifications. |
| Requested non-emergency location information
(see NOTE 3) | O | Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
| Requested emergency location information
(see NOTE 3) | O | Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state. |
|
NOTE 1:
This element is only present when the request is originated by an MC service client.
NOTE 2:
If the interval time has a value of zero then the location management server will send the location information notification immediately after the location information update is received from the MC service user in the MC service ID list.
NOTE 2:
This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
||
10.9.2.6 Location information subscription response p. 199
Table 10.9.2.6-1 describes the information flow from the location management server to the MC service server or location management client and from the location management server in the partner MC system to the location management server in the primary MC system for the location information subscription response.
| Information element | Status | Description |
|---|---|---|
| MC service ID (see NOTE 1) | M | Identity of the requesting MC service user. |
| Subscription status (see NOTE 2) | M | Indicates the subscription result. |
|
NOTE 1:
This element is only present when the associated request was originated by an MC service client.
NOTE 2:
The subscription status provides the status for each MC service ID listed with the associated request.
|
||
10.9.2.7 Location information notification p. 199
Table 10.9.2.7-1 and Table 10.9.2.7-2 describe the information flows from the location management server to the MC service server and from the location management server to the location management client.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user whose location information is being notified. |
| Triggering event | M | Identity of the event that triggered the sending of the notification. |
| Location Information (see NOTE) | M | Location information. |
|
NOTE:
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, with at least one provided.
|
||
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user whose location information is being notified. |
| Functional alias | O | Functional alias that corresponds to the MC service user whose location information is being notified. |
| MC service ID | M | Identity of the MC service user subscribed to location information. |
| Triggering event | M | Identity of the event that triggered the sending of the notification. |
| Location Information (see NOTE 1) | M | Location information. |
| MC service UE label (see NOTE 2) | O | Generic name of the reporting MC service UE. |
|
NOTE 1:
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, with at least one provided.
NOTE 2:
This information element shall be present in case the "MC service UE label" parameter in the initial MC service UE configuration data has a non-null value.
|
||
Table 10.9.2.7-3 describes the information flow from the location management server in the partner MC system to the location management server in the primary MC system.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user whose location information is being notified. |
| Functional alias | O | Functional alias that corresponds to the MC service user whose location information is being notified. |
| Triggering event | M | Identity of the event that triggered the sending of the notification. |
| Location Information (see NOTE 1) | M | Location information. |
| MC service UE label (see NOTE 2) | O | Generic name of the reporting MC service UE. |
|
NOTE 1:
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, with at least one provided.
NOTE 2:
This information element shall be present in case the "MC service UE label" parameter in the initial MC service UE configuration data has a non-null value.
|
||
10.9.2.8 Location information cancel subscription request |R16| p. 200
Table 10.9.2.8-1 describes the information flow from the MC service server to the location management server for location information cancel subscription request.
| Information element | Status | Description |
|---|---|---|
| MC service ID list | M | List of identities of the MC service users for whom location information is no longer required. |
Table 10.9.2.8-2 describes the information flow from the location management client to the location management server for location information cancel subscription request.
| Information element | Status | Description |
|---|---|---|
| MC service ID
(see NOTE 1) | M | Identity of the requesting MC service user. |
| MC service ID
(see NOTE 2) | O | Identity of the MC service user, whose subscription is to be cancelled. |
| MC service ID list | O
(see NOTE 3) | List of identities of the MC service users for whom location information is no longer required. |
| MC service group ID list | O
(see NOTE 3) | Group ID(s) that correspond MC service user(s) whose location information subscriptions are to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID). This request is only for currently affiliated users to these group(s). |
|
NOTE 1:
Authorized or subscribed MC service user.
NOTE 2:
Only used with the authorized MC service user.
NOTE 3:
Either the MC service ID list or the MC service group ID list must be present.
|
||
Table 10.9.2.8-3 describes the information flow from the location management server in the primary MC system to the location management server in the partner MC system for the location information cancel subscription request.
| Information element | Status | Description |
|---|---|---|
| MC service ID (see NOTE 1) | M | Identity of the requesting MC service user in the primary MC system. |
| MC service ID (see NOTE 2) | O | Identity of the MC service user in the partner MC system, whose subscription is to be cancelled. |
| MC service ID list | M | List of the identities of MC service users in the partner MC system for whom location information is no longer required. |
|
NOTE 1:
Authorized or subscribed MC service user and only present when the request was originated by an MC service client.
NOTE 2:
Only used with the authorized MC service user.
|
||
10.9.2.9 Location information cancel subscription response |R16| p. 201
Table 10.9.2.9-1 describes the information flow from the location management server to the MC service server for location information cancel subscription response.
| Information element | Status | Description |
|---|---|---|
| MC service ID list | M | List of identities of MC service users, whose subscription has been requested to be cancelled. |
| Subscription cancel response | M | Indicates the cancel subscription result. |
Table 10.9.2.9-2 describes the information flow from the location management server to the location management client for location information cancel subscription response.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the requesting MC service user. |
| MC service ID (see NOTE) | O | Identity of the MC service user, whose subscription has been requested to be cancelled. |
| MC service ID list | M | List of identities of MC service users for whom location information is no longer required. |
| Subscription cancel response | M | Indicates the cancel subscription result. |
|
NOTE:
Only used with the authorized MC service user. Must be present, if used with the associated request.
|
||
Table 10.9.2.9-3 describes the information flow from the location management server in the partner MC system to the location management server in the primary MC system for location information cancel subscription response.
| Information element | Status | Description |
|---|---|---|
| MC service ID (see NOTE 1) | M | Identity of the requesting MC service user in the primary MC system. |
| MC service ID (see NOTE 2) | O | Identity of the MC service user in the partner MC system, whose subscription has been requested to be cancelled. |
| MC service ID list | M | List of identities of MC service users in the partner MC system for whom location information is no longer required. |
| Subscription cancel response (see NOTE 3) | M | Indicates the cancel subscription result. |
|
NOTE 1:
This element is only present when the associated request was originated by an MC service client.
NOTE 2:
Only used with the authorized MC service user. Must be present, if used with the associated request.
NOTE 3:
Provides the status for each MC service ID listed with the associated request.
|
||
10.9.2.10 Void
10.9.2.11 Location information history status request |R17| p. 202
Table 10.9.2.11-1 describes the information flow from the location management client to the location management server to request the status of stored location information, following a return to report location information to the location management server.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user from whom status is requested. |
| MC service ID | M | Identity of the MC service user, who has requested the status. |
Table 10.9.2.11-2 describes the information flow from the location management server to the location management client to request the status of stored location information, following a return to report location information to the location management server.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user from whom status is requested. |
Table 10.9.2.11-3 describes the information flow from the MC service server to the location management server to request the status of stored location information, following a return to report location information to the location management server.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user from whom status is requested. |
| MC service ID | O | Identity of the MC service user, who has requested the status. |
10.9.2.12 Location information history status report |R17| p. 203
The location management client stored location information, while not reporting location information to the location management server, and subsequently the reporting may start following the reestablishment of a communication link between the location management client and the location management server.
Table 10.9.2.12-1 describes the information flow from the location management client to the location management server to report the status of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID list | M | List of identities (e.g. MCPTT ID, MCData ID, MCVideo ID) of the MC service user who reports the status. |
| Number of stored reports | O | Indicates either zero or the number of available reports. |
| Start time | O | First time of measurement of the available reports. |
| End time | O | Last time of measurement of the available reports. |
| Triggered event list (see NOTE) | M | Identifies the criteria when the location management client generated location information, while not reporting location information. |
|
NOTE:
Each triggered criterion is shown once with either the associated Number of stored reports, or with the associated Start time, or with the associated Start time and End time or with the associated End time.
|
||
Table 10.9.2.12-2 describes the information flow from the location management server to the location management client to report the status of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user who reports the status. |
| MC service ID | M | Identity of the MC service user to receive the status report. |
| Number of stored reports | O | Indicates either zero or the number of available reports. |
| Start time | O | First time of measurement of the available reports. |
| End time | O | Last time of measurement of the available reports. |
| Triggered event list (see NOTE) | M | Identifies the criteria when the location management client generated location information, while not reporting location information. |
|
NOTE:
Each triggered criterion is shown once with either the associated Number of stored reports, or with the associated Start time, or with the associated Start time and End time or with the associated End time.
|
||
Table 10.9.2.12-3 describes the information flow from the location management server to the MC service server to report the status of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user who reports the status. |
| Number of stored reports | O | Indicates either zero or the number of available reports. |
| Start time | O | First time of measurement of the available reports. |
| End time | O | Last time of measurement of the available reports. |
| Triggered event list (see NOTE) | M | Identifies the criteria when the location management client generated location information, while not reporting location information. |
|
NOTE:
Each triggered criterion is shown once with either the associated Number of stored reports, or with the associated Start time, or with the associated Start time and End time or with the associated End time.
|
||
10.9.2.13 Location information history request |R17| p. 204
The location management client stored location information, while not reporting location information to the location management server, and subsequently the reporting may start following the reestablishment of a communication link between the location management client and the location management server. Either all or a subset of the stored location information may be requested prior to the location information history reporting.
Table 10.9.2.13-1 describes the information flow from the location management client to the location management server for the location information history request of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user from whom reports are requested. |
| MC service ID | M | Identity of the MC service user who requests location information. |
| Number of stored reports (see NOTE) | O | Indicates the number of requested reports. |
| Start time (see NOTE) | O | Indicates to send reports having this time of measurement and newer. |
| End time (see NOTE) | O | Indicates to send reports having this time of measurement and older. |
| Triggered event list (see NOTE) | O | Identifies the criteria when the location management client generated location information, while not reporting location information. |
| Minimum time between consecutive reports | O | Defaults to 0 if absent. |
|
NOTE:
If none of these information elements is present, all stored location information shall be reported. Information elements may combined to request a subset of the available location information.
|
||
Table 10.9.2.13-2 describes the information flow from location management server to the location management client for the location information history request of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user from whom reports are requested. |
| Number of stored reports (see NOTE) | O | Indicates the number of requested reports. |
| Start time (see NOTE) | O | Indicates to send reports having this time of measurement and newer. |
| End time (see NOTE) | O | Indicates to send reports having this time of measurement and older. |
| Triggered event list (see NOTE) | O | Identifies the criteria when the location management client generated location information, while not reporting location information. |
| Minimum time between consecutive reports | O | Defaults to 0 if absent. |
|
NOTE:
If none of these information elements is present, all stored location information shall be reported. Information elements may combined to request a subset of the available location information.
|
||
Table 10.9.2.13-3 describes the information flow from the MC service server to the location management server for the location information history request of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user from whom reports are requested. |
| Number of stored reports (see NOTE) | O | Indicates the number of requested reports. |
| Start time (see NOTE) | O | Indicates to send reports having this time of measurement and newer. |
| End time (see NOTE) | O | Indicates to send reports having this time of measurement and older. |
| Triggered event list (see NOTE) | O | Identifies the criteria when the location management client generated location information, while not reporting location information. |
| Minimum time between consecutive reports | O | Defaults to 0 if absent. |
|
NOTE:
If none of these information elements is present, all stored location information shall be reported. Information elements may combined to request a subset of the available location information.
|
||
10.9.2.14 Location information history report |R17| p. 205
The location management client stored location information, while not reporting location information to the location management server, and subsequently the reporting may start following the reestablishment of a communication link between the location management client and the location management server.
Table 10.9.2.14-1 describes the information flow from the location management client to the location management server for the location information history reporting of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID list | M | List of identities of the reporting MC service user (e.g. MCPTT ID, MCData ID, MCVideo ID). |
| Triggered event | M | Identifies the criterion when the location management client generated location information, while not reporting location information. |
| Location Information (see NOTE 1) | M | Location information. |
| MC service UE label (see NOTE 3) | O | Generic name of the reporting MC service UE. |
| History report (see NOTE 2) | O | Location information history report indicator. |
|
NOTE 1:
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, with at least one provided.
NOTE 2:
Only present, if triggering criteria in emergency cases or triggering criteria in non-emergency cases used.
NOTE 3:
This information element shall be present in case the "MC service UE label" parameter in the initial MC service UE configuration data has a non-null value.
|
||
Table 10.9.2.14-2 describes the information flow from the location management server to the location management client for the location information history reporting of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user. |
| MC service ID | M | Identity of the MC service user, who has requested location information. |
| Triggered event | M | Identifies the criterion when the location management client generated location information, while not reporting location information. |
| Location Information (see NOTE 1) | M | Location information. |
| MC service UE label (see NOTE 3) | O | Generic name of the reporting MC service UE. |
| History report (see NOTE 2) | O | Location information history report indicator. |
|
NOTE 1:
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, with at least one provided.
NOTE 2:
Only present, if triggering criteria in emergency cases or triggering criteria in non-emergency cases used.
NOTE 3:
This information element shall be present in case the "MC service UE label" parameter in the initial MC service UE configuration data has a non-null value.
|
||
Table 10.9.2.14-3 describes the information flow from the location management server to the MC service server for the location information history reporting of stored location information.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user. |
| Triggered event | M | Identifies the criterion when the location management client generated location information, while not reporting location information. |
| Location Information (see NOTE 1) | M | Location information. |
| History report (see NOTE 2) | O | Location information history report indicator. |
|
NOTE 1:
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, with at least one provided.
NOTE 2:
Only present, if triggering criteria in emergency cases or triggering criteria in non-emergency cases used.
|
||
10.9.2.15 Location information history cancel request |R17| p. 207
Table 10.9.2.15-1 describes the information flow from the location management client to the location management server for the cancellation request of location information history reporting.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user. |
| MC service ID | M | Identity of the MC service user, who has requested the cancellation. |
| Cancellation type | O | Type of cancellation (e.g. from reporting LMC, from LMS, from LMC and LMS). |
Table 10.9.2.15-2 describes the information flow from the location management server to the location management client for the cancellation request of location information history reporting.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user. |
Table 10.9.2.15-3 describes the information flow from the MC service server to the location management server for the cancellation request of location information history reporting.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user. |
| MC service ID | O | Identity of the MC service user, who has requested the cancellation. |
10.9.2.16 Location information history cancel response |R17| p. 207
Table 10.9.2.16-1 describes the information flow from the location management client to the location management server for the cancellation response of location information history reporting.
| Information element | Status | Description |
|---|---|---|
| MC service ID list | M | List of identities (e.g. MCPTT ID, MCData ID, MCVideo ID) of the reporting MC service user. |
Table 10.9.2.16-2 describes the information flow from the location management server to the location management client for the cancellation response of location information history reporting.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user. |
| Response | M | Confirm cancellation from reporting LMC, from LMS or from reporting LMC and LMS. |
Table 10.9.2.16-3 describes the information flow from the location management server to the MC service server for the cancellation response of location information history reporting.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the reporting MC service user. |
10.9.2.17 Location reporting temporary configuration request |R18| p. 208
Table 10.9.2.17-1 describes the information flow from the location management client and location management server in the primary MC system to the location management server and location management client in the partner MC system for the location reporting temporary configuration request.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the authorized and configuring MC service user located in the primary MC system. |
| Functional alias | O | Functional alias that corresponds to the authorized and configuring MC service user located in the primary MC system. |
| MC service ID | M | Identity of the MC service user located in the partner MC system whose location reporting has to be configured. |
| Functional alias | O | Functional alias that corresponds to MC service user located in the partner MC system whose location reporting has to be configured. |
| MC service UE label | O | Generic name of the to be configured MC service UE. |
| Temporary location reporting configuration (see NOTE 1) | M | Provides set of location reporting parameters to be used temporarily. |
| Configuration expiration criteria (see NOTE 2) | O | Criteria for restoration of original location reporting parameters (e.g. timer). |
|
NOTE 1:
All or a subset of the location reporting parameters described in clause 10.9.2.1 of the present document are used. If empty the original location reporting parameters are used, immediately.
NOTE 2:
Ignored with an empty Temporary location reporting configuration.
|
||
10.9.2.18 Location reporting temporary configuration response |R18| p. 208
Table 10.9.2.18-1 describes the information flow from the location management client and location management server in the partner MC system to the location management server and location management client in the primary MC system for the location reporting temporary configuration response.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the authorized and configuring MC service user located in the primary MC system. |
| Functional alias | O | Functional alias that corresponds to the authorized and configuring MC service user located in the primary MC system. |
| MC service ID | M | Identity of the MS service user located in the partner MC system whose location reporting has been configured. |
| Functional alias | O | Functional alias that corresponds to the MS service user located in the partner MC system whose location reporting has been configured. |
| MC service UE label | O | Generic name of the configured MC service UE. |
| Result | M | Indicates the status of each configuration parameter. |
10.9.2.19 Restrict location information dissemination request |R18| p. 209
Table 10.9.2.19-1 describes the information flow from the location management client to the location management server for restricting the location information dissemination further.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Restrict Location Information Dissemination | M | Indicates to enable or disable the location information dissemination. |
| List of users
(see NOTE 1, NOTE 2) | O | Indicates that the restriction of the location information dissemination is applicable for the list of users. |
| Functional Alias
(see NOTE 1, NOTE 2, NOTE 3) | O | Indicates that the restriction of the location information dissemination is applicable for the list of users who have activated this functional alias. |
|
NOTE 1:
If not present, restricting of the location information dissemination is applicable to any users. Dissemination restriction to a particular set of users is not possible if the LMC client applies local restrictions to stop providing location information per local policies.
NOTE 2:
Either the MC service ID list or the functional alias must be present.
NOTE 3:
The LMS track the users activating and de-activating functional alias so that associated restriction record can be updated accordingly.
|
||
10.9.2.20 Restrict location information dissemination response |R18| p. 209
Table 10.9.2.20-1 describes the information flow from the location management server to the location management client for response to restricting the location information dissemination request.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Restrict Location Information Dissemination status | M | Indicates the result of restricting the location information dissemination. |
10.9.2.21 Restrict location information dissemination notification |R18| p. 210
Table 10.9.2.21-1 and Table 10.9.2.21-2 describes the information flow from the location management server to the location management client and from the location management server to the MC service server for notifying about restricting the location information dissemination of another location management client.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user whose location information dissemination retriction information is being notified (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service ID | M | Identity of the MC service user subscribed to location information. |
| Location Information Dissemination information | M | Indicates whether the dissemination of another MC service user's location information is enabled or disabled. |
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user whose location information dissemination retriction information is being notified (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Location Information Dissemination information | M | Indicates whether the dissemination of another MC service user's location information is enabled or disabled. |
10.9.2.22 Location reporting trigger override indication |R19| p. 210
Table 10.9.2.22-1 describes the information flow from the location management server to the location management client for indicating a location reporting trigger override.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the overriding MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| Functional alias | O | Functional alias that corresponds to the overriding MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID). |
| MC service ID list | M | List of identities of the MC service users for who triggers are overridden. |
| Functional alias list | O | Functional alias that corresponds to the MC service users for who triggers are overridden. |
| Reason for override | O | A text description indicating the reason for override. |
10.9.2.23 Location reporting cancel trigger override indication |R19| p. 211
Table 10.9.2.23-1 describes the information flow from the location management server to the location management client for indicating a location reporting cancel trigger override.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | Identity of the MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) who cancels the override. |
| Functional alias | O | Functional alias that corresponds to the MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) who cancels the override. |
| MC service ID list | M | List of identities of the MC service users for who trigger override is cancelled. |
| Functional alias | O | Functional alias that corresponds to the MC service users for who trigger override is cancelled. |
10.9.3 Procedure p. 211
10.9.3.1 Event-triggered location reporting procedure p. 211
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. The decision to report location information can be triggered at the location management client by different conditions. The conditions could include, for example, the reception of the location reporting configuration, initial registration, distance travelled, elapsed time, cell change, MBMS SAI change, MBMS session change, leaving a specific MBMS bearer service area, tracking area change, PLMN change, call initiation, or other types of events such as emergency alert, emergency call or imminent peril calls. The location report can include information described as time of measurement, accuracy, longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs.
Step 1.
The location management server sends location reporting configuration message to the location management client(s) containing the initial configuration (or a subsequent update) for reporting the location of the MC service UE. This message can be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time.
Step 2.
A location reporting event occurs, triggering step 3.
Step 3.
The location management client sends a location information report to the location management server, containing location information identified by the location management server and available to the location management client.
Step 4.
Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client. If the location information report contains an optional MC service UE label, the location management server stores it together with the location information for the reporting location management client.
10.9.3.2 On-demand location reporting procedure p. 212
The location management server can request MC service UE location information at any time by sending a location information request to the location management client, which may trigger location management client to immediately send the location report.
Step 1.
Based on configurations such as periodical location information timer, or location information request from other entities (e.g., another location management client of an authorized MC user whose MC service ID is among the list of MC service users which sharing location information of the target (requested) MC service user is authorised,, MC service server), location management server initiates the immediate request of location information to be sent from the location management client.
Step 2.
The location management server sends a location information request to the location management client.
Step 3.
The location management client immediately responds to the location management server with a report containing location information identified by the location management server and available to the location management client.
Step 4.
Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client, the location management server just stores the reporting location information for that location management client. If the location information report contains an optional MC service UE label, the location management server stores it together with the location information for the reporting location management client.
10.9.3.3 Client-triggered location reporting procedure p. 213
Pre-conditions:
- If the trigger involves an MC service group ID (list), the LMS has previously subscribed to group dynamic data from the MC service server, as per clause 10.1.5.6.4.1.
Step 1.
Location management client 2 (authorized MC service user) sends a location reporting trigger to the location management server to start a location reporting procedure for obtaining the location information. The location reporting trigger request contains MC service ID list or MC service group ID list or Functional alias list to obtain the the location information. Location management server checks whether location management client 2 has subscribed to and is authorized to send a location reporting trigger for location management client 1's location information.
Step 2.
If step (1) involves an MC service group ID list:
Step 3.
- The MC service server notifies group affiliation status to the LMS as per clause 10.1.5.6.4.2. The LMS will update the list of currently affiliated users.
If the location reporting trigger request contains MC service ID list or Functional alias list, depending on the information specified by the location reporting trigger and aggregation of other trigger requests towards the same target location management client, location management server initiates an on-demand location reporting procedure or an event-triggered location reporting procedure for the location of location management client 1.
If the location reporting trigger request contains MC service group ID list, the location management server initiates an event-triggered location reporting procedure. The LMS will trigger location reports for only the currently affiliated users of the group, based on the last notification from the MC service server, as per step 2. The LMS will cancel the current location reporting trigger for the users who have de-affiliated from the service group ID lists(s).
10.9.3.4 Event-triggered location reporting cancel procedure p. 214
The event-triggered location reporting cancel procedure reuses the information flow of location reporting configuration.
Pre-conditions:
- The location management client has been provided with location reporting configuration information.
Step 1.
The location management server sends location reporting configuration without any information element to the location management client to stop location reporting from the MC service UE.
Step 2.
The location management client stops sending location information reports to the location management server.
10.9.3.4a Client-triggered location reporting cancel procedure targeting MC service user(s) |R19| p. 215
Figure 10.9.3.4a-1 illustrates the high level procedure of client-triggered location reporting cancel procedure.
Pre-conditions:
- The location management client 1 has provided the location reporting trigger for the location management client 2.
Step 1.
Location management client 1 (authorized MC service user) sends a location reporting trigger cancel request to the location management server to deactivate a location reporting procedure for obtaining the location information of location management client 2.
Step 2.
Location management server checks whether location management client 1 is authorized to send a location reporting trigger cancel request for location management client 2's location information. If authorized, location management server initiates event-triggered location reporting cancel procedure for the location management client 2 as specified in the clause 10.9.3.4.
10.9.3.4b Client-triggered location reporting cancel procedure targeting MC service group(s) |R19| p. 216
Figure 10.9.3.4b-1 illustrates the high level procedure of client-triggered location reporting cancel procedure targeted to the MC service group(s).
Pre-conditions:
- The location management client 2 has provided the location reporting trigger for the MC service group(s).
- The location management server has subscribed to the dynamic data associated with the target MC service group(s).
Step 1.
Location management client 2 (authorized MC service user) sends a location reporting trigger cancel request to the location management server to deactivate a location reporting procedure for obtaining the location information from the affiliated members of the MC service group(s).
Step 2.
Location management server checks whether location management client 2 is authorized to send a location reporting trigger cancel request for MC service group(s). If authorized, the location management server initiates the event-triggered location reporting cancel procedure as specified in the clause 10.9.3.4 for the location management client(s) of the MC service user(s) affiliated to the MC service group(s) received in step 1.
10.9.3.5 Location information subscription procedure p. 216
Figure 10.9.3.5-1 illustrates the high level procedure of location information subscription request. The same procedure can be applied for location management client and other entities that would like to subscribe to MC service user location information.
Step 1.
MC service server or location management client sends a location information subscription request to the location management server to subscribe location information of one or more MC service users. The request will contain the MC service ID list or the MC service group ID list.
Step 2.
The location management server checks if the location management client is authorized to initiate the location information subscription request.
Step 3.
If step (1) involves an MC service group ID list, the LMS subscribes to group dynamic data request as per clause 10.1.5.6.4.1, to obtain group affiliation data from the MC service server. The MC service server provides the response to this LMS request, as per clause 10.1.5.6.4.1.
Step 4.
The location management server replies with a location information subscription response indicating the subscription status.
Step 5.
If step (1) involves an MC service group ID list:
Step 6.
- If the response in 3b) indicates success, the MC service server notifies group affiliation status of each MC service ID to the LMS as per clause 10.1.5.6.4.2, whenever there is a change in group affiliations.
- The LMS will maintain and update a list of currently affiliated users inline with 5a) as the target user list to provide location information to the location management client as per this subscription.
If required, the location management server shall update the location reporting configuration of the target location management clients in order to provide the requested location information received in step 1.
10.9.3.6 Usage of location information procedure p. 218
10.9.3.6.1 Event-trigger location information notification procedure p. 218
Figure 10.9.3.6.1-1 illustrates the high level procedure of event-trigger usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of MC service user.
Pre-condition:
- The MC service server or location management client has subscribed to the location information of a target MC service user.
Step 1.
Based on configuration, e.g., subscription, periodical location information timer, the location management server is triggered to report the latest user location information of the target MC service user to the subscribed MC service server or subscribed location management client. The location management server has verified that the subscribed MC service server or subscribed location management client is authorized to receive the user location information of the target MC service user.
Step 2.
The location management server sends the location information notification including the latest location information of one MC service user to the MC service server or to the location management client. The latest location information is derived from the location report procedure as described in clause 10.9.3.1, or from PLMN operator (e.g. LCS network). If the optional MC service UE label is present, the location management server sends it, as part of the location information notification, to the MC service user. If the location management client has subscribed to location information through a MC service group ID, the location management server will report back location information only for currently affiliated members to this MC service group.
10.9.3.6.2 On-demand usage of location information procedure p. 218
The MC service server or the location management client can request location information at any time by sending a location information request to the location management server, which may trigger location management server to send the location information report immediately.
Pre-conditions:
- Requested location management clients has been provided with the location reporting configuration information.
Step 1.
MC service server or location management client send a location information request to the location management server.
Step 2.
The location management server checks if the location management client is authorized to request the location information. Furthermore, it checks whether the requested location management client is authorised to share its location information with the requesting location management client.
Step 3.
The location management server acquires the latest location of the location management clients being requested, by triggering an on-demand location report procedure as described in clause 10.9.3.2 depending on the requested location information (if any) in the location information request from the location management client or MC service server, or from PLMN operator (e.g. LCS network).
Step 4.
Then, location management server immediately sends the location information report including the latest location information acquired of one MC service user to the MC service server or to the location management client. If the optional MC service UE label is present, the location management server sends it, as part of the location information report, to the MC service user.
10.9.3.7 Location information cancel subscription procedure |R16| p. 219
Figure 10.9.3.7-1 illustrates the high level procedure of location information cancel subscription request. The MC service server or the location management client can request the cancellation of location information subscriptions at any time from the location management server.
Pre-conditions:
- The authorized MC service user is in possession of the MC service ID of the MC service user as well as the location information subscriptions of this MC service ID.
Step 1.
MC service server or location management client sends a location information cancel subscription request to the location management server to cancel the subscription for location information of one or more MC service users. The request will contain the MC service ID list or the MC service group ID list.
Step 2.
The location management server checks the authorization of this request.
Step 3.
If step (1) involves an MC service group ID, the LMS issues a group dynamic data cancel request to MC service server, as per clause 10.1.5.6.1.5. The MC service server will issue the response as per clause 10.1.5.6.1.6.
Step 4.
The location management server replies with a location information cancel subscription response indicating the cancel subscription status.
Step 5.
If step (1) involves an MC service group ID list, the LMS will delete the list of affiliated group members for the group ID(s).
Step 6.
The associated location reporting triggers (from the same authorized user or the MC service server to the same target MC service client(s) or group(s)) will be cancelled, as per procedure 10.9.3.4a.
10.9.3.8 Location management using functional alias |R16| p. 220
10.9.3.8.1 Client-triggered one-time location information report p. 220
Figure 10.9.3.8.1-1 illustrates the procedure when a location management client requests one-time location information from other location management clients for location information reporting using functional alias, which can be shared between several MC service users. Under this condition, the actual location of all MC service users sharing the same functional alias are reported.
Pre-conditions:
- MC service client 2 and MC service client 3 share the same functional alias.
- MC service client 2 and MC service client 3 activated the functional alias.
- MC service client 1 may have an activated functional alias.
- The location management server has subscribed to the functional alias controlling MC service server within the MC system for functional alias activation/de-activation updates.
Step 1.
Location management client 1 sends a location reporting trigger, limited to one MC service at the time, to the location management server to activate a one-time location report procedure which shall retrieve the location information of the MC service users that may share the contained functional alias. Location management client 1 may include its own activated functional alias.
Step 2.
Location management server resolves the target functional alias and checks whether location management client 1 is authorized to send a location reporting trigger for location information of location management clients 2 and 3. Furthermore, it checks whether each MC service user included in the location reporting trigger is authorized to share their location information with the requesting location management client, i.e., location management client 1.
Step 3a, 3b.
The location management server uses on-demand location reporting procedures. The location information request contains the functional alias provided by the location management client 1 to address location management client 2 and location management client 3.
Step 4.
Upon receiving the reports, the location management server updates location of the reporting location management clients. If the location management server does not have location information of a reporting location management client before, then just stores the reporting location information for that location management client.
Step 5.
The location management server sends location information reports to location management client 1 containing the provided location information for each location management client using the given functional alias. If the optional MC service UE label is present, the location management server sends it, as part of the location report response to location management client 1. If not all location management clients immediately respond to the location management server, i.e. other reports some time later, subsequent location reporting responses may be sent.
10.9.3.8.2 Client-triggered periodic location information report p. 221
Figure 10.9.3.8.2-1 illustrates the procedure when a location management client requests periodic location information from other location management clients for location information reporting using functional aliases which may be shared between several MC service users. Under this condition, the actual location of all MC service users sharing the same functional alias are reported.
Pre-conditions:
- MC service client 2 and MC service client 3 share the same functional alias.
- MC service client 2 and MC service client 3 activated the functional alias.
- MC service client 1 may have an activated functional alias.
- The location management server has subscribed to the functional alias controlling MC service server within the MC system for functional alias activation/de-activation updates.
- MC service client 2 has subscribed to location information from the functional alias that is shared by MC service client 2 and 3 as described in clause 10.9.3.5.
Step 1.
Location management client 1 sends a location reporting trigger, limited to one MC service at the time, to the location management server to activate a periodic location reporting procedure which shall retrieve the location information of the MC service users sharing the contained functional alias. Location management client 1 may include its own activated functional alias.
Step 2.
Location management server resolves the target functional alias and checks whether location management client 1 is authorized to send a location reporting trigger for location information for location management clients 2 and 3 that have activated the functional alias.
Step 3a, 3b.
Depending on the information given by the location reporting trigger and aggregation of other trigger requests towards the same target location management clients, the location management server uses event-triggered location information procedure to the location management clients that have activated the functional alias requested by the location management client 1.
Step 4.
Upon receiving the reports, the location management server updates location of the reporting location management clients.
Step 5.
The location management server checks whether location management client 2 and location management client 3 are authorized to share their location information with location management client 1.
Step 6.
Based on the received location information reports and the subscription by location management client 1, the location management server will periodically issue location information notifications, one at a time for each location management client for which location management client 1 is authorized to receive location information, encompassing the MC service ID, the associated functional alias, the individual location information of the addressed MC service ID and the optional MC service UE label, if present.
10.9.3.8.3 Client-triggered location reporting cancel procedure targeting functional alias(es) |R19| p. 223
Figure 10.9.3.8.3-1 illustrates the procedure where a location management client requests to cancel the location reporting triggers targeted to the functional aliases which may be shared between several MC service users.
Pre-conditions:
- MC service users at location management client 2 and location management client 3 share the same functional alias.
- MC service users at location management client 2 and location management client 3 activated the functional alias.
- MC service user at location management client 1 may have an activated functional alias.
- The location management server has subscribed to the functional alias controlling MC service server within the MC system for functional alias activation/de-activation updates.
Step 1.
Location management client 1 (authorized MC service user) sends a location reporting trigger cancel request, limited to one MC service at the time, to the location management server to deactivate a periodic location reporting procedure which shall retrieve the location information of the MC service users sharing the contained functional alias. Location management client 1 may include its own activated functional alias.
Step 2.
Location management server checks whether location management client 1 is authorized to send a location reporting trigger cancel request for location information of the location management clients that have activated the functional alias. The location management server determines the functional alias to a corresponding list of related MC service IDs of location management client 2 and location management client 3 who have activated the functional alias.
Step 3a-3b.
Location management server initiates event-triggered location reporting cancel procedure for the location management client 2 and location management client 3 as specified in the clause 10.9.3.4
