hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.13 Use of MBMS bearer for group status
| The MC service server, e.g., MCPTT server, may use the MBMS bearer to inform the status of a group communication (indicating the group call is on-going or not) when the group call is set up on unicast bearers. The affiliated clients that will perform late entry chat group calls or rejoin calls may use this group status... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8 Affiliation and de-affiliation to/from MC service group(s)
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.1 General
| The following subclauses specify the procedures for affiliation and de-affiliation to a single MC service, and which are utilised by the following MC services:
- MCPTT (as specified in 3GPP TS 23.379 [16]);
- MCVideo (as specified in 3GPP TS 23.281 [12]); and
- MCData (as specified in 3GPP TS 23.282 [13]).
MC servi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2 Information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.1 MC service group affiliation request
| Table 10.8.2.1-1 describes the information flow MC service group affiliation request from the MC service client to the MC service server.
Table 10.8.2.1-1: MC service group affiliation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the MC service g... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.2 MC service group affiliation request (MC service server – MC service server)
| Table 10.8.2.2 -1 describes the information flow MC service group affiliation request between the MC service servers.
Table 10.8.2.2-1: MC service group affiliation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the MC service group affiliation req... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.3 MC service group affiliation response
| Table 10.8.2.3-1 describes the information flow MC service group affiliation response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.8.2.3-1: MC service group affiliation response
Information element
Status
Description
MC ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.4 MC service group affiliation response (MC service server – MC service server)
| Table 10.8.2.4-1 describes the information flow MC service group affiliation response between the MC service servers.
Table 10.8.2.4-1: MC service group affiliation response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the MC service group affiliation re... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.5 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.6 MC service group de-affiliation request
| Table 10.8.2.6-1 describes the information flow MC service group de-affiliation request from the MC service client to the MC service server.
Table 10.8.2.6-1: MC service group de-affiliation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the MC ser... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.7 MC service group de-affiliation request (MC service server – MC service server)
| Table 10.8.2.7-1 describes the information flow MC service group de-affiliation request between the MC service servers.
Table 10.8.2.7-1: MC service group de-affiliation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the MC service group de-affilia... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.8 MC service group de-affiliation response
| Table 10.8.2.8-1 describes the information flow MC service group de-affiliation response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.8.2.8-1: MC service group de-affiliation response
Information element
Status
Descriptio... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.9 MC service group de-affiliation response (MC service server – MC service server)
| Table 10.8.2.9-1 describes the information flow MC service group de-affiliation response between MC service servers.
Table 10.8.2.9-1: MC service group de-affiliation response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the MC service group de-affiliati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.10 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.11 MC service group affiliation change request
| Table 10.8.2.11-1 describes the information flow MC service group affiliation change request from the MC service client to the MC service server.
Table 10.8.2.11-1: MC service group affiliation change request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.12 MC service group affiliation change response
| Table 10.8.2.12-1 describes the information flow MC service group affiliation change response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.8.2.12-1: MC service group affiliation change response
Information element
Status
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.13 MC service group de-affiliation notification
| Table 10.8.2.13-1 describes the information flow MC service group de-affiliation notification from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.8.2.13-1: MC service group de-affiliation notification
Information element
Status
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.2.14 Notify group dynamic data request
| Table 10.8.2.14-1 describes the information flow notify group dynamic data request from the MC service server to the group management server.
Table 10.8.2.14-1: Notify group dynamic data request
Information element
Status
Description
MC service group ID
M
The MC service group ID to which the GMS has subscribed a... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.3 Affiliation
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.3.1 MC service group affiliation procedure
| Procedure for affiliation to MC service group(s) for a single MC service is described in figure 10.8.3.1-1.
Pre-conditions:
1. MC service client has already been provisioned (statically or dynamically) with the group information, or a pointer to the group information, that the MC service client is allowed to be affil... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.3.2 Affiliation to MC service group(s) defined in partner MC system without topology hiding
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.3.2.1 Functional description
| When an MC service client wants to affiliate to MC service group(s) which is defined in a partner MC system for a single MC service and where topology hiding is not required, it shall be subject to authorization from the partner MC system where the MC service group(s) is defined, and whether it subjects to authorizatio... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.3.2.2 Procedure
| The procedure for affiliation to MC service group(s) which is defined in a partner MC system where topology hiding is not required for a single MC service is described in figure 10.8.3.2.2-1.
Pre-conditions:
1. The MC service client has already been provisioned (statically or dynamically) with the group information, ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.4 De-affiliation from MC service group(s)
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.4.1 General
| When an MC service user does not want to communicate with an MC service group anymore for a single MC service, then the MC service user can revoke its affiliation to the MC service group.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.4.2 MC service group de-affiliation procedure
| The procedure for revoking the affiliation with an MC service group for a single MC service is described in figure 10.8.4.2-1.
Pre-conditions:
1. MC service server has already subscribed to the MC service group information from group management server and has stored the data of MC service group(s) to which the MC ser... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.4.3 De-affiliation from MC service group(s) defined in partner MC system
| The procedure for de-affiliation from affiliated MC service group(s) which is defined in partner MC system for a single MC service is described in figure 10.8.4.3-1.
Pre-conditions:
1. The primary/partner MC service servers have already subscribed to the group information from group management server and stored the d... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.4.4 MC server initiated group de-affiliation procedure
| The procedure for the MC service server to trigger a de-affiliation with an MC service group is described in figure 10.8.4.4-1.
Pre-conditions:
1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affiliation;
2. Following a relevant trigg... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.4.5 MC server initiated group de-affiliation from group defined in partner MC system
| The procedure for the MC service server to trigger a de-affiliation from an MC service group which is defined in partner MC system is described in figure 10.8.4.5-1.
Pre-conditions:
1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affil... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.5 Remote change of affiliation
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.5.1 Remote change of affiliation for groups defined in primary MC system
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.5.1.1 Authorized user remotely changes another MC service user's affiliated MC service group(s) – mandatory mode
| The procedure for an authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service without requiring the target user's approval is described in figure 10.8.5.1.1-1.
Pre-conditions:
1. The MC service client 1 (authorized user 1) has already been provisioned (static... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.5.1.2 Authorized user remotely changes another MC service user's affiliated MC service group(s) – negotiated mode
| The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service with the target MC service user's approval is described in figure 10.8.5.1.2-1.
Pre-conditions:
- The MC service client 1 (authorized user 1) has already been provisioned (statica... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.5.2 Remote change of affiliation for groups defined in partner MC system
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.8.5.2.1 Authorized user remotely changes another MC service user's affiliated MC service group(s) defined in partner MC system – mandatory mode
| The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) defined in partner MC systems for a single MC service without requiring the target user's approval is described in figure 10.8.5.2.1-1.
Pre-conditions:
1. The MC service client 1 (authorized user) has alr... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9 Location management (on-network)
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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 may also be provided by the 3GPP core network (i.e., via the PLMN operator). The location information reporting triggers are based on the location reporting configurati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2 Information flows for location information
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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.
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 l... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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.
Table 10.9.2.2-1: Location information report (LMC – LMS)
Information element
Status
Description
Set of MC service IDs
M
Set of identities of the reporting... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.3 Location information request
| Tables 10.9.2.3-1, 10.9.2.3-2 and 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 loc... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.4 Location reporting trigger
| 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 authori... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.5 Location information subscription request
| 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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 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.
Tabl... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.7 Location information notification
| 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
Descr... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.8 Location information cancel subscription request
| 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
Descripti... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.9 Location information cancel subscription response
| 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
Descrip... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.10 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.11 Location information history status request
| 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 reques... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.12 Location information history status report
| 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.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.13 Location information history request
| 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.14 Location information history report
| 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.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.15 Location information history cancel request
| 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.16 Location information history cancel response
| 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 servi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.17 Location reporting temporary configuration request
| 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.18 Location reporting temporary configuration response
| 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.19 Restrict location information dissemination request
| 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
M... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.20 Restrict location information dissemination response
| 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
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.21 Restrict location information dissemination notification
| 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.
Ta... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.22 Location reporting trigger override indication
| Table 10.9.2.22-1 describes the information flow from the location management server to the location management client for indicating a location reporting trigger override.
Table 10.9.2.22-1: Location reporting trigger override indication
Information element
Status
Description
MC service ID
M
Identity of the ove... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.2.23 Location reporting cancel trigger override indication
| Table 10.9.2.23-1 describes the information flow from the location management server to the location management client for indicating a location reporting cancel trigger override.
Table 10.9.2.23-1: Location reporting trigger override indication
Information element
Status
Description
MC service ID
M
Identity of ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3 Procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.1 Event-triggered location reporting procedure
| NOTE 1: This procedure is valid for single MC system operation only.
The location management server provides location reporting configuration to the location management clients, indicating what information the location management server expects and what events will trigger the sending of this information to the locati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.2 On-demand location reporting procedure
| NOTE: This procedure is valid for single MC system operation only.
The location management server can request MC service UE location information at any time by sending a location information request to the location management client, which may trigger location management client to immediately send the location report.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.3 Client-triggered location reporting procedure
| NOTE 1: This procedure is valid for single MC system operation only.
Figure 10.9.3.3-1 illustrates the high level procedure of client-triggered location reporting.
Pre-conditions:
1. If the trigger involves an MC service group ID (list), the LMS has previously subscribed to group dynamic data from the MC service ser... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.4 Event-triggered location reporting cancel procedure
| NOTE: This procedure is valid for single MC system operation only.
The event-triggered location reporting cancel procedure reuses the information flow of location reporting configuration.
Pre-conditions:
- The location management client has been provided with location reporting configuration information.
Figure... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.5 Location information subscription procedure
| NOTE 1: This procedure is valid for single MC system operation only.
Figure 10.9.3.5-1 illustrates the high level procedure of location information subscription request. The same procedure can be applied for location management client and other entities that would like to subscribe to MC service user location informat... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.6 Usage of location information procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.6.1 Event-trigger location information notification procedure
| NOTE 1: This procedure is valid for single MC system operation only.
Figure 10.9.3.6.1-1 illustrates the high level procedure of event-trigger usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of MC s... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.6.2 On-demand usage of location information procedure
| NOTE 1: This procedure is valid for single MC system operation only.
The MC service server or the location management client can request location information at any time by sending a location information request to the location management server, which may trigger location management server to send the location inform... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.7 Location information cancel subscription procedure
| NOTE: This procedure is valid for single MC system operation only.
Figure 10.9.3.7-1 illustrates the high level procedure of location information cancel subscription request. The MC service server or the location management client can request the cancellation of location information subscriptions at any time from the ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.8 Location management using functional alias
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.8.1 Client-triggered one-time location information report
| Figure 10.9.3.8.1-1 illustrates the procedure when a location management client requests one-time location information from other location management clients for location information reporting using functional alias, which can be shared between several MC service users. Under this condition, the actual location of all ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.8.2 Client-triggered periodic location information report
| Figure 10.9.3.8.2-1 illustrates the procedure when a location management client requests periodic location information from other location management clients for location information reporting using functional aliases which may be shared between several MC service users. Under this condition, the actual location of all... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.8.3 Client-triggered location reporting cancel procedure targeting functional alias(es)
| Figure 10.9.3.8.3-1 illustrates the procedure where a location management client requests to cancel the location reporting triggers targeted to the functional aliases which may be shared between several MC service users.
Pre-conditions:
1. MC service users at location management client 2 and location management clien... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9 Usage of location history reporting procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.1 General
| The location management client may get into a state where it cannot report location information to the location management server at any time after the initial location reporting configuration was provided by the location management server. If any location information trigger criterion applies, while not reporting loca... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.2 Report location history procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.2.1 On-demand report location history procedure (LMC – LMS)
| The location management server can request stored location information at any time from the location management client, following a return to report location information to the location management server.
Figure 10.9.3.9.2.1-1 illustrates the procedure for the on-demand based usage of location information history repo... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.2.2 On-demand report location history procedure
| The location management server can request stored location information at any time from the location management client, following a return to report location information to the location management server. The MC service server or the location management client may initiate the request of stored location information.
F... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.3 Usage of status location history reporting procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.3.1 Status location history reporting procedure (LMC – LMS)
| The location management client can report the status of stored location information at any time to the location management server, following a return to report location information to the location management server.
Figure 10.9.3.9.3.1-1 illustrates the procedure for the usage of the status reporting from the location... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.3.2 On-demand status location history reporting procedure (LMS – LMC)
| The location management server can request the status of stored location information at any time from the location management client, following a return to report location information to the location management server.
Figure 10.9.3.9.3.2-1 illustrates the procedure for the on-demand based usage of requesting the stat... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.3.3 On-demand status location history reporting procedure
| The MC service server or the location management client can request the status of stored location information at any time, following a return to report location information to the location management server.
Figure 10.9.3.9.3.3-1 illustrates the procedure for the on-demand based usage of the status location history re... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.4 Usage of cancel location history reporting procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.4.1 General
| The location management server can request cancellation of the transmission of location information history reports at any time following the start of transmission by sending a location information history cancel request to the reporting location management client. The MC service server or location management client co... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.4.2 Cancel location history reporting procedure (LMS – LMC)
| Figure 10.9.3.9.4.2-1 illustrates the procedure for the cancellation on location history reporting from the location management server to the location management client.
Pre-conditions:
1. The location management client has returned to report location information and has stored location information reports.
Figure... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.9.4.3 Cancel location history reporting procedure
| Figure 10.9.3.9.4.3-1 illustrates the procedure for the cancellation on location history reporting from the MC service server or location management client to the location management server.
Pre-conditions:
1. The location management client 1 has returned to report location information and has stored location informa... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.10 Usage of location information across MC systems procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.10.1 General
| Interconnected MC systems in either the same security domain or different security domains share location information either through the direct connection of the location management servers or through the connected MC gateway servers.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.10.2 On-demand request of location information procedure
| The MC service server or location management client in the primary MC system can request MC service user's location information, which is in the partner MC system, at any time by sending a location information request to the location management server at primary MC system.
Figure 10.9.3.10.2-1 illustrates the high lev... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.10.3 Event-triggered location information notification procedure
| The location management client in the partner MC system provides, based on configuration, periodic location information, which will be also forwarded to the subscribed entities.
Figure 10.9.3.10.3-1 illustrates the high level procedure of event-triggered sharing of location information.
Pre-conditions:
1. The locati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.10.4 Location information subscription procedure
| The location management client in the partner MC system provides, based on configuration, event triggered location information, which will be also forwarded to the subscribed entities.
Figure 10.9.3.10.4-1 illustrates the high level procedure of subscription to location information between interconnected MC systems.
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.10.5 Location information cancel subscription procedure
| The location management client in the primary MC system receives location information updates according to the subscriptions requested in the partner MC system. Those subscriptions can be cancelled anytime from the primary MC system.
Figure 10.9.3.10.5-1 illustrates the high level procedure of the subscription cancell... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.10.6 Location reporting temporary configuration procedure
| An authorized MC service user in the primary MC system in charge of MC service users either currently completely or partially operating in a partner MC system is able to configure event-based location information for the involved MC service users at any time by sending configuration parameters. Those configuration para... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.11 Restrict location information dissemination procedure
| The location management client can control the location information dissemination at any time by sending a restrict location information dissemination request to the location management server, which will indicate to the location management server whether the location information can be disseminated further or not.
F... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.12 Location reporting trigger override
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.12.1 General
| For operational/technical reasons (e.g., in order to reduce the signalling load in a cell) an authorized user can override the aggregated trigger configuration for one or more reporting location management clients.
The location reporting trigger override procedures only affect the triggers configured by requesting MC... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.12.2 Location reporting trigger override procedure
| NOTE: This procedure is valid for single MC system operation only.
Figure 10.9.3.12.2-1 illustrates the high level procedure of trigger override.
Pre-conditions:
1. MC service client 3 has subscribed to MC service client 1 as described in clause 10.9.3.5 and has applied location reporting triggers in MC service clie... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.9.3.12.3 Cancel location reporting trigger override procedure
| NOTE: This procedure is valid for single MC system operation only.
Figure 10.9.3.12.3-1 illustrates the high level procedure of cancel trigger override.
Pre-conditions:
1. MC service client 3 has subscribed to MC service client 1 as described in clause 10.9.3.5 and has applied location reporting triggers in MC servi... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.