Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  17.5.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  General

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 information

10.9.2.1  Location reporting configuration

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
Up

10.9.2.2  Location information report

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)
Functional alias(es) (see NOTE 1)OFunctional alias that corresponds to the MC service ID.
Triggering eventMIdentity of the event that triggered the sending of the report
Location Information (see NOTE 2)MLocation information of the individual MC service user
Up

10.9.2.3  Location information requestWord‑p. 176
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
 
Information element Status Description
MC service IDMIdentity of MC service user whose location information is requested
MC service IDOIdentity of the requested 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)
Up

10.9.2.4  Location reporting triggerWord‑p. 177
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
Up

10.9.2.5  Location information subscription request

Table 10.9.2.5-1 describes the information flow from the MC service server or 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
Up

10.9.2.6  Location information subscription response

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. 178
Table 10.9.2.7-1 describes the information flow from the location management server to the MC service server.
Information element Status Description
MC service ID listMList of the MC service IDs (e.g. MCPTT ID, MCData ID, MCVideo ID) of the MC service users whose location information needs to be notified
MC service IDMIdentity of the MC service user subscribed to location information of another MC service user (see NOTE 1)
Triggering eventMIdentity of the event that triggered the sending of the notification
Location Information (see NOTE 2)MLocation information
Up

10.9.2.8  Location information cancel subscription request |R16|

Table 10.9.2.8-1 describes the information flow from the MC service server or location management client to the location management server for location information cancel subscription request.
Information element Status Description
MC service IDMIdentity of the requesting MC service user
MC service ID listMList of MC service IDs (e.g. MCPTT ID, MCData ID, MCVideo ID) of the MC service users for whom location information is no longer required.
Up

10.9.2.9  Location information cancel subscription response |R16|

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

10.9.2.10  Location report response |R16|

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. This information flow combines individually recorded location information reports of the all involved location management clients.
Information element Status Description
Combined set of MC service IDsMList of identities of the reporting MC service users (e.g. MCPTT ID, MCVideo ID, MCData ID).
Functional aliasOFunctional alias that corresponds to the MC service IDs.
Triggering eventMIdentity of the event that triggered the sending of the report.
Set of Location Information (see NOTE 1, see NOTE 2)MList of location information for the corresponding functional alias and its MC service ID.
Up

10.9.2.11  Location information history status request |R17|Word‑p. 179
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|

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

10.9.2.13  Location information history request |R17|Word‑p. 181
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
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
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
MC service IDOIdentity of the MC service user, who has requested 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
Up

10.9.2.14  Location information history 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.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
History report (see NOTE 2)OLocation information history report indicator
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
History report (see NOTE 2)OLocation information history report indicator
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
Up

10.9.2.15  Location information history cancel request |R17|Word‑p. 183
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. 184
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