Content for TS 23.280 Word version: 19.1.0

1… 5… 5.2.8… 6 7… 7.3.2 7.4… 7.4.3… 7.5… 8… 9… 9.2.2… 9.2.2.2… 9.3… 10… 10.1.2… 10.1.3… 10.1.4.3… 10.1.4.5… 10.1.5… 10.1.6… 10.2… 10.2.3… 10.2.4.2… 10.2.4.3… 10.2.5… 10.2.7… 10.3… 10.6… 10.7… 10.7.3… 10.7.3.4… 10.7.3.7… 10.7.3.7.3 10.7.3.8… 10.7.3.10… 10.8… 10.8.4… 10.8.5… 10.9… 10.9.3… 10.9.3.5… 10.9.3.8… 10.9.3.9… 10.9.3.9.3… 10.9.3.9.4… 10.9.3.10… 10.9.3.10.4… 10.9.3.10.6… 10.10… 10.10.1.2.3… 10.10.2… 10.10.3… 10.10.3.3… 10.10.3.4… 10.11… 10.11.5… 10.12… 10.13… 10.13.3… 10.13.7… 10.13.10… 10.14… 10.15… 10.15.3… 10.15.3.3… 10.15.3.4… 10.16… 10.17… 11… 11.3… 11.5… 11.5.2… 11.5.3… 11.5.3.3.2A… 11.5.4… A… B… C…

10.9 Location management (on-network) p. 181

10.9.1 General p. 181

Location information of MC service user shall be provided by the location management client to the location management server. The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided.

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. 181

10.9.2.1 Location reporting configuration p. 181

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.

Table 10.9.2.1-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)	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.

10.9.2.2 Location information report p. 182

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.

Table 10.9.2.2-1: Location information report

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	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.

Table 10.9.2.2-2 describes the information flow from the location management server to the location management client for location information reporting.

Table 10.9.2.2-2: Location information report (LMS - LMC)

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	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.

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

Table 10.9.2.2-3: 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)	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.

Table 10.9.2.2-4: Location information report (LMS - LMS)

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	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.

10.9.2.3 Location information request p. 183

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.

Table 10.9.2.3-1: Location information request (MC service server to location management server)

Information element	Status	Description
MC service ID list	O (see NOTE)	List of MC service users whose location information is requested
Functional alias	O (see NOTE)	Location information of MC service users who have activated this functional alias is requested
NOTE: Either the MC service ID list or the functional alias must be present.

Table 10.9.2.3-2: Location information request (Location management server to location management client)

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)

Table 10.9.2.3-3: Location information request (Location management client to location management server)

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)	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)	Functional alias that corresponds to the requested MC service user(s) (e.g. MCPTT ID, MCVideo ID, MCData ID)
NOTE: Either the MC service ID list or the functional alias must be present.

Table 10.9.2.3-4 describes the information flow to support the handling of location information across MC systems.

Table 10.9.2.3-4: Location information request (Location management server to location management server)

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
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.

10.9.2.4 Location reporting trigger p. 184

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.

Table 10.9.2.4-1: Location reporting trigger

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	O (see NOTE 1) (see NOTE 3)	Identity of the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias	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)	Indicates whether an immediate location report is required
Requested non-emergency location information	O (see NOTE 2)	Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts
Requested emergency location information	O (see NOTE 2)	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)	Identifies when the client will send the location report in non-emergency cases
Triggering criteria in emergency cases	O (see NOTE 2)	Identifies when the client will send the location report in emergency cases
Minimum time between consecutive reports	O (see NOTE 2)	Defaults to 0 if absent and 0 for emergency calls, imminent peril calls and emergency alerts
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 functional alias must be present.

10.9.2.5 Location information subscription request p. 185

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.

Table 10.9.2.5-1: Location information subscription request (MC service server - LMS)

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)	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.
NOTE: 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.

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.

Table 10.9.2.5-2: Location information subscription request (LMC - LMS)

Information element	Status	Description
MC service ID	M	Identity of the requesting MC service user
MC service ID list	M	List of MC service users whose location information is requested
Time between consecutive reports	M (see NOTE)	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.
NOTE: 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.

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.

Table 10.9.2.5-3: Location information subscription request (LMS - LMS)

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
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.

10.9.2.6 Location information subscription response p. 186

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.

Table 10.9.2.6-1: 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. 186

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.

Table 10.9.2.7-1: Location information notification (LMS to MC service server)

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.

Table 10.9.2.7-2: Location information notification (LMS to LMC)

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)	M	Location information
MC service UE label	O	Generic name of the reporting MC service UE
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.

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.

Table 10.9.2.7-3: Location information notification (LMS to LMS)

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)	M	Location information
MC service UE label	O	Generic name of the reporting MC service UE
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.

10.9.2.8 Location information cancel subscription request |R16| p. 186

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.

Table 10.9.2.8-1: Location information cancel subscription request (MC service server to location management server)

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.

Table 10.9.2.8-2: Location information cancel subscription request (Location management client to location management server)

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	M	List of identities of the MC service users for whom location information is no longer required
NOTE 1: Authorized or subscribed MC service user. NOTE 1: Only used with the authorized MC service user.

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.

Table 10.9.2.8-3: Location information cancel subscription request (Location management server to location management server)

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. 187

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.

Table 10.9.2.9-1: Location information cancel subscription response (Location management server to MC service server)

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.

Table 10.9.2.9-2: Location information cancel subscription response (Location management server to location management client)

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.

Table 10.9.2.9-3: Location information cancel subscription response (Location management server to location management server)

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 Location report response |R16| p. 189

Table 10.9.2.10-1 describes the information flow from the location management server to the requesting location management client for the location information reporting when using functional alias.

Table 10.9.2.10-1: Location report response

Information element	Status	Description
MC service ID	M	Identity of the reporting MC service user whose location information is requested
MC service ID	M	Identity of the MC service user who requested the location information based on a provided functional alias
Functional alias	O	Functional alias that corresponds to the MC service ID of the reporting MC service user
Triggering event	M	Identity of the event that triggered the sending of the report
Location Information (see NOTE)	M	Location information for the corresponding functional alias and its MC service ID
MC service UE label	O	Generic name of the reporting MC service UE
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.

10.9.2.11 Location information history status request |R17| p. 189

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.

Table 10.9.2.11-1: Location information history status request (LMC - LMS)

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.

Table 10.9.2.11-2: Location information history status request (LMS - LMC)

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.

Table 10.9.2.11-3: Location information history status request (MC service server - LMS)

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. 190

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.

Table 10.9.2.12-1: Location information history status report (LMC - LMS)

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.

Table 10.9.2.12-2: Location information history status report (LMS - LMC)

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.

Table 10.9.2.12-3: Location information history status report (LMS - MC service server)

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. 191

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.

Table 10.9.2.13-1: Location information history request (LMC - LMS)

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.

Table 10.9.2.13-2: Location information history request (LMS - LMC)

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.

Table 10.9.2.13-3: Location information history request (MC service server - LMS)

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. 193

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.

Table 10.9.2.14-1: Location information history report (LMC - LMS)

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	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.

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.

Table 10.9.2.14-2: Location information history report (LMS - LMC)

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	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.

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.

Table 10.9.2.14-3: Location information history report (LMS - MC service server)

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. 194

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.

Table 10.9.2.15-1: Location information history cancel request (LMC - LMS)

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.

Table 10.9.2.15-2: Location information history cancel request (LMS - LMC)

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.

Table 10.9.2.15-3: Location information history cancel request (MC service server - LMS)

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. 195

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.

Table 10.9.2.16-1: Location information history cancel response (LMC - LMS)

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.

Table 10.9.2.16-2: Location information history cancel response (LMS - LMC)

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.

Table 10.9.2.16-3: Location information history cancel response (LMS - MC service server)

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. 195

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.

Table 10.9.2.17-1: 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. 196

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.

Table 10.9.2.18-1: 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. 196

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.

Table 10.9.2.19-1: Restrict location information dissemination request information elements

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. 197

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.

Table 10.9.2.20-1: Restrict location information dissemination response information elements

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. 197

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.

Table 10.9.2.21-1: Restrict location information dissemination notification information elements (LMS to LMC)

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

Table 10.9.2.21-2: Restrict location information dissemination notification information elements (LMS to MC service server)

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