Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  17.8.0

Top   Top   Up   Prev   Next
1…   5…   7…   7.4…   7.5…   8…   9…   10…   10.1.2…   10.1.3…   10.1.5…   10.2…   10.2.3…   10.2.5…   10.3…   10.7…   10.7.3…   10.7.3.7…   10.7.3.10…   10.8…   10.8.4…   10.9…   10.9.3…   10.9.3.8…   10.10…   10.11…   10.12…   10.13…   10.13.3…   10.14…   10.15…   10.15.3…   A…   B…

 

10.9  Location management (on-network)Word‑p. 175

10.9.1  GeneralWord‑p. 175

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

10.9.2  Information flows for location informationWord‑p. 175

10.9.2.1  Location reporting configurationWord‑p. 175

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 IDMIdentity of the MC service user group to which the location reporting configuration is targeted.
Requested non-emergency location informationO (see NOTE 1)Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts
Requested emergency location informationO (see NOTE 1)Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts
Triggering criteria in non-emergency casesO (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 casesOIdentifies when the location management client will store location information (e.g. never, off-network, IOPS)
Triggering criteria in not reporting location information casesO (see NOTE 2)Identifies the causes when the location management client will generate location information
Minimum time between consecutive reportsO (see NOTE 1)Defaults to 0 if absent and 0 for emergency calls, imminent peril calls and emergency alerts
Triggering criteria in emergency casesO (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.
Up

10.9.2.2  Location information reportWord‑p. 175

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 IDsMSet 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)OIdentity of the requesting MC service user.
Functional alias(es) (see NOTE 1)OFunctional alias that corresponds to the MC service ID.
MC service UE labelOGeneric name of the reporting MC service UE
Triggering event (see NOTE 3)MIdentity of the event that triggered the sending of the report
Location Information (see NOTE 2)MLocation 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.
Information element Status Description
Set of MC service IDsMSet of identities of the reporting MC service user on the MC service UE (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service IDMIdentity of the requesting MC service user.
Functional alias(es) (see NOTE 1)OFunctional alias that corresponds to the reporting MC service ID.
MC service UE labelOGeneric name of the reporting MC service UE
Triggering event (see NOTE 3)MIdentity of the event that triggered the sending of the report
Location Information (see NOTE 2)MLocation 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.
Information element Status Description
Set of MC service IDsMSet 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)OFunctional alias that corresponds to the MC service ID.
Triggering event (see NOTE 3)MIdentity of the event that triggered the sending of the report
Location Information (see NOTE 2)MLocation 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.
Up

10.9.2.3  Location information requestWord‑p. 177

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 listO (see NOTE)List of MC service users whose location information is requested
Functional aliasO (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.
Information element Status Description
MC service IDMIdentity of MC service user whose location information is requested
MC service IDOIdentity of the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional aliasOFunctional alias that corresponds to the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Information element Status Description
MC service IDMIdentity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID listO (see NOTE)List of MC service users whose location information is requested
Functional aliasOFunctional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional aliasO (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.
Up

10.9.2.4  Location reporting triggerWord‑p. 178

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 IDM (see NOTE 1)Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional aliasOFunctional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service IDO (see NOTE 1) (see NOTE 3)Identity of the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional aliasO (see NOTE 3)Functional alias that corresponds to the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID).
Immediate Report IndicatorO (see NOTE 2)Indicates whether an immediate location report is required
Requested non-emergency location informationO (see NOTE 2)Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts
Requested emergency location informationO (see NOTE 2)Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts
Triggering criteria in non- emergency casesO (see NOTE 2)Identifies when the client will send the location report in non-emergency cases
Triggering criteria in emergency casesO (see NOTE 2)Identifies when the client will send the location report in emergency cases
Minimum time between consecutive reportsO (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.
Up

10.9.2.5  Location information subscription requestWord‑p. 178

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 listMList of MC service users whose location information is requested
Time between consecutive reportsM (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.
Information element Status Description
MC service IDMIdentity of the requesting MC service user
MC service ID listMList of MC service users whose location information is requested
Time between consecutive reportsM (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.
Up

10.9.2.6  Location information subscription responseWord‑p. 179

Table 10.9.2.6-1 describes the information flow from the location management server to the MC service server or location management client for location information subscription response.
Information element Status Description
MC service IDMIdentity of the requesting MC service user
Subscription statusMIndicates the subscription result
Up

10.9.2.7  Location information notificationWord‑p. 179

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 IDMIdentity of the MC service user whose location information is being notified
Triggering eventMIdentity of the event that triggered the sending of the notification
Location Information (see NOTE)MLocation 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 IDMIdentity of the MC service user whose location information is being notified
MC service IDMIdentity of the MC service user subscribed to location information
Triggering eventMIdentity of the event that triggered the sending of the notification
Location Information (see NOTE)MLocation information
MC service UE labelOGeneric 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.
Up

10.9.2.8  Location information cancel subscription request |R16|Word‑p. 179

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 listMList 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)MIdentity of the requesting MC service user
MC service ID (see NOTE 2)OIdentity of the MC service user, whose subscription is to be cancelled
MC service ID listMList 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.
Up

10.9.2.9  Location information cancel subscription response |R16|Word‑p. 179

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 listMList of identities of MC service users, whose subscription has been requested to be cancelled
Subscription cancel responseMIndicates 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 IDMIdentity of the requesting MC service user
MC service ID (see NOTE)OIdentity of the MC service user, whose subscription has been requested to be cancelled
MC service ID listMList of identities of MC service users for whom location information is no longer required
Subscription cancel responseMIndicates the cancel subscription result
NOTE:
Only used with the authorized MC service user. Must be present, if used with the associated request.
Up

10.9.2.10  Location report response |R16|Word‑p. 180

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

10.9.2.11  Location information history status request |R17|Word‑p. 181

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 IDMIdentity of the MC service user from whom status is requested
MC service IDMIdentity 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 IDMIdentity 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 IDMIdentity of the MC service user from whom status is requested
MC service IDOIdentity of the MC service user, who has requested the status
Up

10.9.2.12  Location information history status report |R17|Word‑p. 182

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 listMList of identities (e.g. MCPTT ID, MCData ID, MCVideo ID) of the MC service user who reports the status
Number of stored reportsOIndicates either zero or the number of available reports
Start timeOFirst time of measurement of the available reports
End timeOLast time of measurement of the available reports
Triggered event list (see NOTE)MIdentifies 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 IDMIdentity of the MC service user who reports the status
MC service IDMIdentity of the MC service user to receive the status report
Number of stored reportsOIndicates either zero or the number of available reports
Start timeOFirst time of measurement of the available reports
End timeOLast time of measurement of the available reports
Triggered event list (see NOTE)MIdentifies 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 IDMIdentity of the MC service user who reports the status
Number of stored reportsOIndicates either zero or the number of available reports
Start timeOFirst time of measurement of the available reports
End timeOLast time of measurement of the available reports
Triggered event list (see NOTE)MIdentifies 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.
Up

10.9.2.13  Location information history request |R17|Word‑p. 183

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 IDMIdentity of the MC service user from whom reports are requested
MC service IDMIdentity of the MC service user who requests location information
Number of stored reports (see NOTE)OIndicates the number of requested reports
Start time (see NOTE)OIndicates to send reports having this time of measurement and newer
End time (see NOTE)OIndicates to send reports having this time of measurement and older
Triggered event list (see NOTE)OIdentifies the criteria when the location management client generated location information, while not reporting location information
Minimum time between consecutive reportsODefaults 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 IDMIdentity of the MC service user from whom reports are requested
Number of stored reports (see NOTE)OIndicates the number of requested reports
Start time (see NOTE)OIndicates to send reports having this time of measurement and newer
End time (see NOTE)OIndicates to send reports having this time of measurement and older
Triggered event list (see NOTE)OIdentifies the criteria when the location management client generated location information, while not reporting location information
Minimum time between consecutive reportsODefaults 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 IDMIdentity of the MC service user from whom reports are requested
Number of stored reports (see NOTE)OIndicates the number of requested reports
Start time (see NOTE)OIndicates to send reports having this time of measurement and newer
End time (see NOTE)OIndicates to send reports having this time of measurement and older
Triggered event list (see NOTE)OIdentifies the criteria when the location management client generated location information, while not reporting location information
Minimum time between consecutive reportsODefaults 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.
Up

10.9.2.14  Location information history report |R17|Word‑p. 184

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 listMList of identities of the reporting MC service user (e.g. MCPTT ID, MCData ID, MCVideo ID)
Triggered eventMIdentifies the criterion when the location management client generated location information, while not reporting location information
Location Information (see NOTE 1)MLocation information
MC service UE labelOGeneric name of the reporting MC service UE
History report (see NOTE 2)OLocation 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.
Information element Status Description
MC service IDMIdentity of the reporting MC service user
MC service IDMIdentity of the MC service user, who has requested location information
Triggered eventMIdentifies the criterion when the location management client generated location information, while not reporting location information
Location Information (see NOTE 1)MLocation information
MC service UE labelOGeneric name of the reporting MC service UE
History report (see NOTE 2)OLocation 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.
Information element Status Description
MC service IDMIdentity of the reporting MC service user
Triggered eventMIdentifies the criterion when the location management client generated location information, while not reporting location information
Location Information (see NOTE 1)MLocation information
History report (see NOTE 2)OLocation 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.
Up

10.9.2.15  Location information history cancel request |R17|Word‑p. 186

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 IDMIdentity of the reporting MC service user
MC service IDMIdentity of the MC service user, who has requested the cancellation
Cancellation typeOType 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 IDMIdentity 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 IDMIdentity of the reporting MC service user
MC service IDOIdentity of the MC service user, who has requested the cancellation
Up

10.9.2.16  Location information history cancel response |R17|Word‑p. 186

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 listMList 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 IDMIdentity of the reporting MC service user
ResponseMConfirm cancellation from reporting LMC, from LMS or from reporting LMC and LMS
Table 10.9.2.16-3 describes the information flow from the MC service server to the location management server for the cancellation response of location information history reporting.
Information element Status Description
MC service IDMIdentity of the reporting MC service user
Up

Up   Top   ToC