hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.3.5 Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert
|
During an ongoing ad hoc group emergency alert, an authorized user modifies the criteria for determining the list of participants of the ad hoc group emergency alert. The MC service server checks whether additional MC service users meet the modified conditions or whether other MC service users don’t meet the conditions any longer.
As illustrated in Figure 10.10.3.3.5-1 MC service client 2 is added to the ad hoc group as the MC service client 2 meets the modified criteria for receiving an ongoing ad hoc group emergency alert, whereas MC service client 3 is removed from the ad hoc group as the MC service client 3 does not meet the modified criteria for receiving the ongoing ad hoc group emergency alert.
Pre-conditions:
1. The MC service user on MC service client 1 is authorized to modify the criteria for determining the list of participants by the MC service server.
2. Both the MC service server and the MC service client 1 are aware of the criteria related to the ongoing ad hoc group emergency alert.
Figure 10.10.3.3.5-1: Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert
1. The MC service user at the MC service client 1 is authorized and wishes to modify the criteria for determining the list of ad hoc group emergency alert participants.
2. The MC service server receives the ad hoc group emergency alert modify request.
3. The MC service server checks whether MC service client 1 is authorized to modify the criteria which determines the list of ad hoc group participants.
4. The MC service server sends the ad hoc group emergency alert modify request return to MC service client 1 containing the result of whether modifying the criteria for determining the participants of the ad hoc group is authorized or not. If the ad hoc group emergency alert modify request is not authorized, the MC service server and the MC service client 1 shall not proceed with the rest of the steps.
5. The MC service server analyses the modified criteria and identifies that MC service client 3 does not meet the modified criteria while MC service client 2 meets the modified criteria. The ad hoc group is updated with the determined user list as a member of the group.
6. The MC service server sends an ad hoc group emergency alert modify response back to MC service client 1, which indicates whether the modify request was successful.
7a. MC service server sends an ad hoc group emergency alert request towards MC service client 2.
7b. The MC service user 2 is notified of entering an ongoing ad hoc group emergency alert.
7c. MC service client 2 sends an ad hoc group emergency alert response towards MC service server.
7d. MC service server sends an ad hoc group emergency alert cancel request towards MC service client 3.
7e. The MC service user 3 is notified of leaving an ongoing ad hoc group emergency alert.
7f. MC service client 3 sends an ad hoc group emergency alert cancel response towards MC service server.
8. The authorized user on MC service client 1 is notified with the MC service IDs of those MC service users who are currently in the ad hoc group including the new criteria. This notification may be sent to the authorised MC service user by the MC service server more than once during the alert when MC service users join or leave the ad hoc group.
9. The MC service server adds MC service client 2 to the ad hoc group emergency alert and removes MC service client 3 from the ad hoc group emergency alert.
The MC service server continuously checks whether other MC service clients meet or if participating MC service clients no longer meet the criteria for the ad hoc group emergency alert.
NOTE: If the ad hoc group emergency alert is associated with an ad hoc group call and the change of criteria caused the modification of the ad hoc group emergency alert participant list then the ongoing ad hoc group call is modified accordingly.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.4 Procedures within multiple MC systems
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.4.1 Ad hoc group emergency alert initiation
|
Figure 10.10.3.4.1-1 illustrates the procedure for initiating of ad hoc emergency alert within multiple MC systems.
Preconditions:
- The MC service user 1 belonging to MC system A initiates an ad hoc group emergency alert that involves MC service users from MC system A and MC system B.
- The MC system A and MC system B are interconnected.
Figure 10.10.3.4.1-1: Ad hoc group emergency alert initiation between multiple MC systems
1. The MC service user 1 at the MC service client 1 initiates an ad hoc group emergency alert to an ad hoc group with participants satisfying specific criteria. The MC service user may add additional information describing the reason for sending the alert.
2. The MC service client 1 sends an ad hoc group emergency alert request containing the details of the criteria to be applied by the MC service server A for determining the participants list. The MC service client 1 may set its MC service emergency state. The MC service user at the MC service client 1 may select a functional alias used for the MC service group emergency alert. If the MC service client 1 is in an MC service emergency state, the MC service emergency state is retained by the MC service client 1 until explicitly cancelled.
3. The MC service server A checks whether the MC service user of MC service client 1 is authorized for initiation of ad hoc group emergency alert and whether the request is supported. The MC service server checks whether the provided functional alias, if present, can be used and has been activated for the user.
4. The MC service server A sends the ad hoc group emergency alert request return to the MC service user 1 containing the result of whether the ad hoc group emergency alert is authorized or not. If the ad hoc group emergency alert request is not authorized, the MC service server and the MC service client 1 shall not proceed with the rest of the steps.
5. The MC service server A determines that the partner MC system B is to be involved in the initiated ad hoc group emergency alert based on the information elements provided by the MC service client 1. The MC service server A determines the list of participants within MC system A to be invited for the ad hoc group emergency alert based on the information elements provided by the MC service client 1. This information element could carry either criteria or indicator identifying the pre-defined criteria or combination of both. Furthermore, The MC service server A adds the ad hoc group ID (generated by the MC service server A in the case when the MC service ad hoc group ID created by the MC service client 1 is not acceptable or the case where the MC service ad hoc group ID was not provided by the MC service client 1) to be associated with the ad hoc group emergency alert. The MC service server A stores the ad hoc group ID together with the list of participants for the duration of the ad hoc group emergency alert.
NOTE 1: The content of the Criteria for determining the participants information element, the details of the pre-defined criteria, and the way how their MC service server determines the list of participants are left to implementation.
6. The MC service server A sends an ad hoc group emergency alert get userlist request to MC service server B including the criteria to determine the list of participants from the MC system B.
7. The MC service server B sends an ad hoc group emergency alert get userlist response to MC service server A including the list of participants within MC system B. The MC service server B may apply local policies if any while determining the participants satisfying the criteria.
8. The MC service server A compiles the list of participants from both MC system A and the partner MC system B to be involved in the ad hoc group emergency alert. The MC service server A considers MC service client 2, MC service client 3 and MC service client 4 implicitly affiliated to the ad hoc group associated to the emergency alert.
9. The MC service server A sends the MC service client 1 an ad hoc group emergency alert response to confirm that the request is granted.
10. The MC service server A sends an ad hoc group emergency alert request towards MC service client 2 within the partner MC system A and, MC service client 3, MC service client 4 within the partner MC system B.
11. The MC service user 2, MC service user 3 and MC service user 4 are notified of the ad hoc group emergency alert.
12. The MC service client 2, MC service client 3 and MC service client 4 send an ad hoc group emergency alert response back to MC service server A.
13. It is configured, whether any MC service client may setup a subsequent ad hoc group communication, using the ad hoc group ID from the ad hoc group emergency alert, according to 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] or 3GPP TS 23.282 [13].
NOTE 2: MC service client 1 may start the subsequent ad hoc group call after step 9.
NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state.
NOTE 4: Sending the emergency alert does not put the other participants in the group into an MC service emergency state.
The MC service server continuously checks whether other MC service clients meet or if participating MC service clients no longer meet the criteria for the ad hoc group emergency alert.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.4.2 Updating the participant list of an ongoing ad hoc group emergency alert
|
Figure 10.10.3.4.2-1 illustrates updating the participant list of an ongoing ad hoc group emergency alert within multiple MC systems. This includes scenario of MC service users entering and leaving an ongoing ad hoc emergency alert.
Preconditions:
- An ad hoc group emergency alert has been initiated by MC service user 1 within MC system A, and a related ad hoc group exists.
- The MC service server A and MC service server B are aware of the criteria sent by MC service client 1 related to the ongoing ad hoc group emergency alert.
- MC system A and MC system B are interconnected.
Figure 10.10.3.4.2-1: Updating the participant list of an ongoing ad hoc group emergency alert between multiple MC systems
1. An ad hoc group emergency alert has been established based on a set of criteria sent by MC service client 1 upon initiating the ad hoc emergency alert. The MC service server A considers MC service client 3 implicitly affiliated to the ad hoc group associate to the emergency alert.
2. MC service server B detects that MC service client 3 meets the criteria of the ongoing ad hoc group emergency alert initiated at MC system A.
3. MC service server B sends an ad hoc group emergency alert add user notification including the identity of MC service client 3 to be added to the ad hoc group associated to the ongoing emergency alert.
4. The MC service server A sends an ad hoc group emergency alert request to MC service client 3.
5. The MC service user 3 is notified of entering an ongoing ad hoc group emergency alert.
6. The MC service client 3 sends the MC service server A an ad hoc group emergency alert response.
7. The MC service server A updates the participant list of the MC service group associated with the ongoing ad hoc group emergency alert. The MC service server A may send a notification to authorized users indicating the addition of MC service client 3 to the ad hoc group.
8. The MC service server B detects that MC service client 4 no longer meets the criteria of the ongoing ad hoc group emergency alert. The MC service server A deaffiliates the MC service client 4 from the ad hoc group associated to the emergency alert.
9. The MC service server B sends the MC service server A an ad hoc group emergency remove user notification.
10. MC service server A sends the MC service client 4 an ad hoc group emergency alert cancel request.
11. The MC service user 4 is notified of leaving an ad hoc group emergency alert.
12. The MC service client 4 sends the MC service server A an ad hoc emergency alert cancel response.
13. The ad hoc group associated with the ongoing ad hoc emergency alert is updated. The MC service server A may send a notification to authorized users indicating the removal of the MC service client 4.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.4.3 Ad hoc group emergency alert cancel
|
Figure 10.10.3.4.3-1 illustrates the procedure once an MC service client cancels an ongoing ad hoc group emergency alert.
Preconditions:
- An ad hoc group emergency alert is ongoing with participants within MC system A and MC system B.
- MC system A and MC system B are interconnected.
Figure 10.10.3.4.3-1: Ad hoc group emergency alert cancel between multiple MC systems
1. The MC service user 1 decides to cancel an ongoing ad hoc group emergency alert.
2. MC service client 1 sends the MC service server A an ad hoc group emergency alert cancel request. If the cancel request is sent for another MC service user that initiated this emergency alert, that user`s MC service ID shall be included in the cancel request.
3. MC service server A checks whether the MC service client 1 is authorized to cancel an ongoing ad hoc group emergency alert. The MC service server A checks whether the provided functional alias, if present, can be used and has been activated for the user.
4. The MC service server A sends the ad hoc group emergency cancel alert request return to the MC service user 1 containing the result of whether the ad hoc group emergency cancel request is authorized or not. If the ad hoc group emergency cancel alert request is not authorized, the MC service server and the MC service client 1 shall not proceed with the rest of the steps.
5. The MC service server A sends an ad hoc emergency alert cancel notification to the MC service server B at the partner MC system B.
6. The MC service server A sends MC service client 2, MC service client 3 and MC service client 4 ad hoc group emergency alert cancel request.
7. The MC service user 2, MC service user 3 and MC service user 4 are notified of the ad hoc group emergency alert cancellation.
8. The MC service client 2, MC service client 3 and MC service client 4 sends ad hoc group emergency alert cancel response to the MC service server A. If there is no other communication in the ad hoc group or once the communication in the ad hoc group is terminated, the ad hoc group ceases to exist.
9. The MC service server A sends an ad hoc group emergency alert cancel response to MC service client 1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.4.4 Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert
|
Figure 10.10.3.4.4-1 illustrates when the alerting user modifies the criteria for determining the list of participants of an ongoing ad hoc group emergency alert between multiple MC systems. This includes a scenario of MC service users entering and leaving an ongoing ad hoc emergency alert.
Preconditions:
- The MC service user at the MC service client 1 is authorized to modify the criteria.
- The MC service server A and MC service server B are aware of the criteria related to the ongoing ad hoc group emergency alert.
- MC system A and MC system B are interconnected.
Figure 10.10.3.4.4-1: Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert between multiple MC systems
1. An ad hoc group emergency alert has been established based on criteria sent by an authorized MC service client upon initiating the ad hoc emergency alert.
2. The MC service user at the MC service client 1 is authorized and wishes to modify the criteria for determining the list of ad hoc group emergency alert participants.
3. The MC service server A receives the ad hoc group emergency alert modify request.
4. The MC service server A checks whether MC service client 1 is authorized to modify the criteria which determines the list of ad hoc group participants.
5. The MC service server A sends the ad hoc group emergency alert modify request return to MC service client 1 containing the result of whether modifying the criteria for determining the participants of the ad hoc group is authorized or not. If the ad hoc group emergency alert modify request is not authorized, the MC service server and the MC service client 1 shall not proceed with the rest of the steps.
6. If MC service server A identifies that the criteria require to add participants from another MC system then MC service server A sends an ad hoc group emergency alert request to MC service server B at MC system B.
7a/b. The MC service server A receives the ad hoc group emergency alert modify response and forwards the response to MC service client 1 in MC system A.
8. MC service server B detects that MC service client 3 meets the criteria for the ongoing ad hoc group emergency alert initiated at MC system A.
8a. MC service server B sends an ad hoc group emergency add user notification message towards MC service server A.
8b. MC service server A sends an ad hoc group emergency alert request towards MC service client 3.
8c. The MC service user 3 is notified of entering an ongoing ad hoc group emergency alert.
8d. MC service client 3 sends an ad hoc group emergency alert response towards MC service server A.
8e. MC service server B sends an ad hoc group emergency remove user notification message towards MC service server A.
8f. MC service server A sends an ad hoc group emergency alert cancel request towards MC service client 4.
8g. The MC service user 4 is notified of leaving an ongoing ad hoc group emergency alert.
8h. MC service client 4 sends an ad hoc group emergency alert cancel response towards MC service server A.
9. The authorized user on MC service client 1 is notified with the MC service IDs of those MC service users who are currently in the ad hoc group. This notification may be sent to the authorised MC service user by the MC service server A more than once during the call when MC service users join or leave the ad hoc group.
10. The MC service server A adds MC service client 3 to the ad hoc group emergency alert and removes MC service client 4 from the ad hoc group emergency alert.
The MC service servers continuously check whether other MC service clients meet or if participating MC service clients no longer meet the criteria for the ad hoc group emergency alert.
NOTE: If the ad hoc group emergency alert is associated with an ad hoc group call and the change of criteria caused the modification of the ad hoc group emergency alert participant list then the ongoing ad hoc group call is modified accordingly.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11 MC service resource management (on-network)
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.1 General
|
The following subclauses specify the procedures for resource management for mission critical services. The procedures 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]).
The MC service server sets up media bearers and may need to modify the bearers for an already established MC communication.
Media characteristics that may need to be modified include:
- activation and deactivation of the bearer;
- modification of the QoS characteristics of the bearer (e.g. bearer priority adjustment); and
- modification of GBR due to media codec change
NOTE 1: A group call can consist of both unicast and multicast bearers which can all need modification due to the same event.
NOTE 2: The MC service server can retry the establishment of a media bearer upon failure based on information received, or other conditions.
The information elements associated to the resources management procedures in this clause are derived from the respective communication setup procedures in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] and 3GPP TS 23.282 [13].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.2 Request for unicast resources at session establishment – SIP core based
|
The procedure defined in this subclause specifies how network resources are requested at session establishment. If concurrent sessions are used the MC service server may utilize the capability of resource sharing specified in 3GPP TS 23.203 [8]. The request for resources is sent to the PCRF on the Rx reference point and includes media type, bandwidth, priority, application identifier and resource sharing information.
The procedure is generic to any type of session establishment that requires requests for network resources.
Procedures in figure 10.11.2-1 are the signalling procedures for the requesting resource at session establishment.
Figure 10.11.2-1: Resource request at session establishment – SIP core based
1. MC service client sends a session establishment request.
2. MC service server evaluates the need for network resources and the use of media resource sharing.
3. MC service server send a session progress request containing request for resources.
4. PCC procedures (as defined in 3GPP TS 23.203 [8]) initiated from SIP core local inbound/outbound proxy over Rx.
5. The SIP core local inbound / outbound proxy forwards the call control protocol request to the MC service client.
6. The MC service client acknowledges the session progress request with an OK message.
7. The SIP core local inbound / outbound proxy forwards the OK message to the MC service server.
8. The MC service session is established and resources have been allocated.
10.11.2a Request for unicast resources at session establishment – MC service server based
10.11.2a.1 General
The procedure defined in this clause specifies how network resources are requested at session establishment from the MC service server. The request for resources is sent to the PCRF via the Rx reference point from the MC service server and includes media type, bandwidth, priority, application identifier and resource sharing information. If concurrent sessions are used, the MC service server may utilize the capability of resource sharing specified in 3GPP TS 23.203 [8].
For the request of network resources by the MC service server via the Rx reference point, the MC service client provides to the MC service server the final access resource details (e.g. IP addresses and ports) of the MC service client and the media anchoring points.
This procedure is generic to any type of session establishment with the MC service server requesting network resources.
10.11.2a.2 Procedure
Figure 10.11.2a.2-1 describes the procedure for the request of resources at session establishment from the MC service server.
Figure 10.11.2a.2-1: Resource request at session establishment – MC service server based
1. The MC service client sends a session establishment request. The request includes, apart from the SDP offer, access resource details, e.g. IP addresses and ports of the MC service client related to the media session.
2. The MC service server evaluates the need of network resources and use of media resource sharing.
3. The MC service server sends a session progress request to the SIP core.
NOTE: The session progress request does not include a request for network resources to be performed by the SIP core.
4. The SIP core local inbound / outbound proxy forwards the session progress request to the MC service client.
5. The MC service client acknowledges the session establishment to the MC service server. This message contains the final negotiated media access parameters, e.g. IP addresses and ports related to the media anchoring points received in the SDP answer from the SIP core.
6. The MC service server sends a request for media resources to the PCRF over Rx (as defined in 3GPP TS 23.203 [8]).
7. The MC service session is established, and resources have been allocated.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.3 Request for modification of unicast resources
|
To modify unicast media bearers, the MC service server shall send a resource modification request containing the parameters to be modified, using the call control protocol via the SIP core to the UE.
Possible scenarios when this procedure may be used are:
- Modify the allocation and retention priority for unicast resources;
- Release and resume resources in-between MC service calls when using the chat model; or
- Release and resume resources when a UE is able to receive the MC service call over multicast transmission
Releasing resources for the media plane should give the option to allow the SIP session to either be torn down or continue.
Procedures in figure 10.11.3-1 are the signalling procedures for the modification of a unicast:
Pre-conditions:
- An MC service session is already in progress;
Figure 10.11.3-1: Bearer modification request
1. MC service server decides to modify the parameters of a unicast bearer (e.g. a request to upgrade the existing MC service call to an MC service emergency or imminent-peril call).
2. MC service server sends a session update which includes a resource modification request containing the modified parameters of the unicast bearer.
3. PCC procedures (as defined in 3GPP TS 23.203 [8]) initiated from SIP core local inbound/outbound proxy over Rx.
4. The SIP core local inbound / outbound proxy forwards the session update request to the MC service client.
5. The MC service client acknowledges the call control protocol request with an OK message.
6. The SIP core local inbound / outbound proxy forwards the OK message to the MC service server.
7. The MC service session continues with the modified unicast resources.
NOTE 1: If the MC service call is transferred to multicast transmission, the unicast resources could be temporarily released.
NOTE 2: If multiple audio streams are sent to the UE, additional bearer resources could be required during an established session. Pre-allocation of additional bearer resources already at session establishment could be useful.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.4 Management of multicast media bearers
|
To activate the multicast media bearers the MC service server shall use the Activate MBMS Bearer procedure specified in 3GPP TS 23.468 [18] with the MC service server performing the GCS AS function. The MC service server shall activate MBMS bearers in broadcast areas where eMBMS capable UEs are or are expected to be located. For that, the MC service server shall use the MBMS SAI(s) and/or cell id(s) information to construct the MBMS broadcast area parameter in the Activate MBMS Bearer procedure.
To deactivate the multicast media bearers the MC service server shall use the Deactivate MBMS Bearer procedure specified in 3GPP TS 23.468 [18] with the MC service server performing the GCS AS function.
To modify multicast media bearers the MC service server shall use the Modify MBMS Bearer procedure specified in 3GPP TS 23.468 [18] with the MC service server performing the GCS AS function.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.5 Request for resources with shared priority
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.5.1 General
|
An MC service server that supports simultaneous sessions may need to share a common priority on the EPS bearer for several MC service group calls that may use different priorities on the application level. This is achieved by including information for priority sharing on the request of resources over Rx reference point to PCRF. All sessions associated with the same priority sharing information will be handled by one EPS bearer, which will have a priority based on the highest requested priority among the sessions.
The use of the procedure defined in subclause 10.11.5.2 is dependent on operator policy.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.5.2 Procedure
|
Pre-conditions:
- All previous resource requests from the MC service have included a priority sharing information.
Figure 10.11.5.2-1: Resource request including priority sharing information
1. The MC service server decides based on a request from the MC service client that the priority of an ongoing call must be adjusted.
2. The MC service server requests a session update to the SIP core. This request will contain information of priority sharing.
3. PCC update procedures (as defined in 3GPP TS 23.203 [8]) initiated from SIP core local inbound/outbound proxy over Rx. PCC updates the bearer priority for the bearer that contains the SDFs associated with the same priority sharing information. The priority is set to highest priority (lowest ARP) among those SDFs. No additional bearer is created. Also, the default bearer priority is updated accordingly.
4. The session update is forwarded to the MC service client.
NOTE 1: The procedure defined above requires a PCC enhancement and is subject to implementation in EPC and IMS and can therefore only be used if supported by EPC and IMS.
NOTE 2: If the EPC and IMS does not support the priority sharing from MC system, no shared priority treatment applies, and a new EPS bearer will be setup based on QCI/ARP combination.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.6 Request for media resources from MC service server
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.6.1 General
|
The procedure in this sub clause specify how request for resource for floor control (or transmission control in MCVideo and MCData) and for the media plane can be handled independently. This procedure utilizes the Rx reference point both between from the MC service server to the PCRF and from the SIP core to the PCRF.
Resource for the transmission control is requested at session establishment, in this case the IMS standard procedures as specified in 3GPP TS 23.228 [9] are used. The session description shall in this procedure include bandwidth information applicable for the transmission control traffic requirement. At group call setup the request for resources for the media plane is triggered. This request is sent directly from the MC service server to the PCRF.
The procedure is optional and is suitable when the procedures for pre-established sessions are used, it may also be used to setup and tear down the media plane used by between consecutive group calls in one communication session using the chat call model.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.11.6.2 Procedure
|
The figure below illustrates the procedure for resource reservation
Figure 10.11.6.2-1: Request for resources for transmission control and media plane
1. The MC service client sends a request for group affiliation.
2. The MC service client sends a request to the MC service server for establishment of a communication session.
3. The MC service server answers the session establishment request and adjusts the bandwidth information in the session description. The requested bandwidth shall be minimized to cover the bandwidth requirements for floor control signalling (or transmission control for MCVideo or MCData).
4. The SIP core requests resources towards the PCRF according to the session establishment request.
5. The session establishment request is completed and a response is sent towards the MC service client.
6. The MC service client sends a call setup message according to existing procedures.
7. The MC service server sends a session establishment request for resources for the media plane to PCRF, and the media plane is by that established. This request includes media description relevant for the media plane.
8. Group call is ongoing on the group communication session.
9. The MC service serve sends a release of media resources to PCRF, and the media plane is by that terminated.
10. The PCRF performs session termination procedure according to 3GPP TS 23.203 [8].
11. The PCRF sends a session release response back to the MC service server.
NOTE 1: The resources for transmission control are retained.
NOTE 2: Step 6-9 can be repeated several times within the life cycle of one communication session.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.12 Priority Management
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.12.1 General
|
Mission critical priority and QoS management is situational. The MC Services provides a real-time priority and QoS experience for the MC users, who have significant dynamic operational requirements that determine their priority. For example, the type of incident a responder is serving or the responder's overall shift role needs to strongly influence a user's ability to obtain resources from the LTE system.
Priority treatment applies on both application layer as well as on transport layer. The details on how the priority level is evaluated and used is outside the scope of this specification. What is specified is the necessary mechanisms to apply the priority and QoS and map different priority parameters between different entities, for example to map application layer priority to transport layer priority.
One of the requirements for MC communication services is to coordinate the use of priority levels between the different MC service servers. This priority coordination is used to mitigate and manage the risk for network congestion situations.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.12.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.12.2.1 MC priority request
|
Table 10.12.1.1-1 describes the information flow MC priority request from one MC service server to an MC service server taking the priority arbitration role.
Table 10.12.1.1-1: MC priority request
Information element
Status
Description
Priority
M
Requested priority
Priority area
M
The geographical area for which the requested priority is required.
Type of service
O
The MC service type e.g. MCVideo, MCPTT or MCData
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.12.3 Procedure for priority coordination between multiple MC service servers
|
In deployment scenarios with multiple MC service servers of different or the same type it is required to coordinate the priorities used by the different servers. The procedure defined below provides the necessary coordination between MC service servers to manage high priority levels. One of the involved MC service servers is assigned the role of being a priority arbitrator among a group of MC service servers serving the same geographical area. The priority arbitrator may also compete for the same limited network resources. Prior to using this procedure all MC service servers need to be configured with information about which MC service server will act as the priority arbitrator and under what conditions (e.g. priority level) the priority arbitrator should be used. The use of this procedure is not mandated. MC systems that support priority coordination between multiple MC service servers should support this procedure.
Pre-condition:
1. One of the MC service servers is assigned the role of the priority arbitrator.
2. It is assumed that all MC service servers are part of the same trusted domain.
3. A MC communication session is ongoing or is about to commence. The operational situation together with static and dynamic attributes requires the use of elevated priority for network resources.
Editor's note: It is FFS if enforcement of the granted priority can be applied to MC service servers outside of the same trusted domain
Editor's note: It is FFS how the MC service server 2 (priority arbitrator) knows about ongoing traffic.
Figure 10.12.3-1: Priority arbitration between multiple MC service servers
1. A need for high priority level is identified by the MC service server 1. The priority level identified is above the level of priority that the MC service server 1 can utilise without centralized priority arbitration.
2. The MC service server 1 sends a MC priority request to the MC service server being assigned the priority arbitrator role. The request includes the geographical area, duration, the priority level, service type and needed capacity.
3. The priority arbitrator determines whether to grant, reject or queue the request for elevated priority.
NOTE 1: How the priority arbitrator makes this determination is out of scope of the present document.
NOTE 2: One source of information for the priority arbitrator to evaluate the priority request, could be information received at the resource reservations over the Rx reference point. Example of such information is resource request failure and Retry-Interval AVP which could be an indication of RAN user plane congestion, see reference 3GPP TS 29.214 [27].
4. The priority arbitrator grants MC service server 1 the elevated priority
5. The priority arbitrator notifies other MC service servers about the elevated priority granted to other services.
NOTE 3: The behaviour of the MC service servers that receive this information is implementation specific. The MC service server may take this information into account when performing priority evaluations for the MC service clients managed by this MC service server.
6. The MC service server utilizes the elevated priority when requesting resources for new or existing MC service communication.
NOTE 4: The priority level granted to the MC service server 1 can be mapped to an applicable SIP priority header or a reservation priority AVP (when the MC service server use the Rx reference point directly).
7a-c. A priority notification may be sent to the MC service clients in the geographical area in which the priority was granted. Messages to MC service clients need to be sent from the MC service server serving each MC user. This message is preferably sent over a multicast bearer.
Editor's note: How the clients could utilize such notifications is FFS.
8. The MC service server 1 identifies that the elevated priority is not needed.
9. The requested MC Priority is released from the MC service server 1.
10. The MC service server 2 (priority arbitrator) informs other MC servers that the elevated priority is released.
Editor's note: It is FFS to include procedure for MC priority revoking.
Editor's note: It is FFS to include procedure for MC priority queueing.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13 Functional alias management (on-network)
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.1 General
|
Functional alias management procedures apply to on-network MC service only.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2 Information flows for functional alias management
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.1 Active functional alias information user query request
|
Table 10.13.2.1-1 describes the information flow for the active functional alias information user query request from the MC service client to the MC service server.
Table 10.13.2.1-1: Active functional alias information user query request
Information element
Status
Description
MC service ID
M
The identity of the MC service user who performs the query.
MC service ID(s)
M
The identity of the MC service user(s) to be queried.
10.13.2.1a Active functional alias information usage query request
Table 10.13.2.1a-1 describes the information flow for the active functional alias information usage query request from the MC service client to the MC service server.
Table 10.13.2.1a-1: Active functional alias information usage query request
Information element
Status
Description
MC service ID
M
The identity of the MC service user who performs the query.
Functional alias(es)
M
A list of functional alias(es) to be queried.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.2 Active functional alias information user query response
|
Table 10.13.2.2-1 describes the information flow for the active functional alias information user query response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.13.2.2-1: Active functional alias information user query response
Information element
Status
Description
MC service ID
M
The identity of the MC service user who performs the query.
MC service ID(s)
M
The identity of the MC service user(s) to be queried.
Query result
M
The active functional alias information retrieved from the MC service server for each of the MC service user(s) queried; or Null if no functional alias is active for the MC service user.
10.13.2.2a Active functional alias information usage query response
Table 10.13.2.2a-1 describes the information flow for the active functional alias information usage query response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.13.2.2a-1: Active functional alias information usage query response
Information element
Status
Description
MC service ID
M
The identity of the MC service user who performs the query.
Functional alias(es)
M
The functional alias(es) to be queried.
Query result
M
The list of MC service ID(s) of the MC service user(s) who have activated the functional alias being queried; or Null if this functional alias is not active for any user.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.3 Functional alias activation request
|
Table 10.13.2.3-1 describes the information flow functional alias activation request from the MC service client to the MC service server.
Table 10.13.2.3-1: Functional alias activation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias activation request.
Functional alias list
M
A list of one or more functional aliases which the originator intends to activate.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.4 Functional alias activation response
|
Table 10.13.2.4-1 describes the information flow functional alias activation response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.13.2.4-1: Functional alias activation response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias activation request.
Functional alias list
M
A list of one or more functional aliases which the originator intends to activate.
Activation status per functional alias
M
Indicates the activation result for each functional alias in the list (activated, rejected, can be taken over).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.5 Functional alias de-activation request
|
Table 10.13.2.5-1 describes the information flow functional alias de-activation request from the MC service client to the MC service server.
Table 10.13.2.5-1: Functional alias de-activation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias de-activation request.
Functional alias list
M
A list of one or more functional aliases which the originator intends to de-activate.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.6 Functional alias de-activation response
|
Table 10.13.2.6-1 describes the information flow functional alias de-activation response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.13.2.6-1: Functional alias de-activation response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias de-activation request.
Functional alias list
M
A list of one or more functional aliases which the originator intends to de-activate.
De-activation status per functional alias
M
Indicates the de-activation result for every functional alias in the list.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.7 Functional alias status notification
|
Table 10.13.2.7-1 describes the information flow functional alias notification from the MC service server to the MC service client. This information flow may be sent individually addressed or group addressed on unicast or multicast (see subclause 10.7.3.4.1).
Table 10.13.2.7-1: Functional alias status notification
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias activation, de-activation or take over request.
Functional alias list
M
A list of one or more functional aliases.
Operations
M
Activation, de-activation or take over status per functional alias.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.8 Functional alias take over request
|
Table 10.13.2.8-1 describes the information flow functional alias take over request from the MC service client to the MC service server.
Table 10.13.2.8-1: Functional alias take over request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias take over request.
Functional alias list
M
A list of one or more functional alias which the originator intends to take over.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.9 Functional alias take over response
|
Table 10.13.2.9-1 describes the information flow functional alias take over response from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.13.2.9-1: Functional alias take over response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias take over request.
Functional alias list
M
A list of one or more functional alias which the originator intends to take over.
Take over status per functional alias
M
Indicates the take over request result (accepted, rejected).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.10 Functional alias revoke notification
|
Table 10.13.2.10-1 describes the information flow functional revoke notification from the MC service server to the MC service client. This information flow is sent individually addressed on unicast or multicast.
Table 10.13.2.10-1: Functional alias revoke notification
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias take over request.
Functional alias
M
The functional alias which is revoked.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.11 Subscribe functional alias request
|
Table 10.13.2.11-1 describes the information flow subscribe functional alias request from the MC service server to the functional alias controlling MC service server, and from the location management server to the functional alias controlling MC service server.
Table 10.13.2.11-1: Subscribe functional alias request
Information element
Status
Description
Functional alias
M
The functional alias for which subscription is requested.
Subscription type
M
Indicates the subscription is for one-time notification or continuous notification.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.12 Subscribe functional alias response
|
Table 10.13.2.12-1 describes the information flow subscribe functional alias response from the functional alias controlling MC service server to the MC service server, and from the functional alias controlling MC service server to the location management server.
Table 10.13.2.12-1: Subscribe functional alias response
Information element
Status
Description
Functional alias
M
The functional alias for which subscription is requested.
Status
M
Success or failure of the request
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.13 Notify functional alias request
|
Table 10.13.2.13-1 describes the information flow notify functional alias request from the functional alias controlling MC service server to the MC service server, and from the functional alias controlling MC service server to the location management server.
Table 10.13.2.13-1: Notify functional alias request
Information element
Status
Description
Functional alias
M
The functional alias for which subscription is requested.
List of MC service IDs
(see NOTE)
M
The list of MC service IDs that is activated for the functional alias
NOTE: The MC service ID list can be an empty list.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.14 Notify functional alias response
|
Table 10.13.2.14-1 describes the information flow notify functional alias response from the MC service server to the functional alias controlling MC service server, and from the location management server to the functional alias controlling MC service server.
Table 10.13.2.14-1: Notify functional alias response
Information element
Status
Description
Functional alias
M
The functional alias for which a list of MC service users who activate the functional alias is requested.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.15 Unsubscribe functional alias request
|
Table 10.13.2.15-1 describes the information flow unsubscribe functional alias request from the MC service server to the functional alias controlling MC service server, and from the location management server to the functional alias controlling MC service server.
Table 10.13.2.15-1: Unsubscribe functional alias request
Information element
Status
Description
Functional alias
M
The functional alias for which subscription is requested to be cancelled.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.16 Unsubscribe functional alias response
|
Table 10.13.2.16-1 describes the information flow subscribe functional alias response from the functional alias controlling MC service server to the MC service server, and from the functional alias controlling MC service server to the location management server.
Table 10.13.2.16-1: Unsubscribe functional alias response
Information element
Status
Description
Functional alias
M
The functional alias for which subscription is requested to be cancelled.
Status
M
Success or failure of the request
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.17 Functional alias to group binding request
|
Table 10.13.2.17-1 describes the information flow functional alias to group binding request from the MC service client to the MC service server.
Table 10.13.2.17-1: Functional alias to group binding request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias to group binding request.
MC service group ID to functional alias bindings
M
A list of MC service group IDs to functional alias bindings. One MC service group ID can be bound only to one functional alias. The same functional alias can be bound to multiple MC service group IDs.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.18 Functional alias to group binding response
|
Table 10.13.2.18-1 describes the information flow functional alias to group binding response from the MC service client to the MC service server.
Table 10.13.2.18-1: Functional alias to group binding response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias to group binding request.
Result
M
Indicates the success or failure for the result
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.19 Functional alias to group unbinding request
|
Table 10.13.2.19-1 describes the information flow functional alias to group unbinding request from the MC service client to the MC service server.
Table 10.13.2.19-1: Functional alias to group unbinding request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias to group unbinding request.
MC service group ID list
M
A list of MC service group IDs to which the originator requests the functional alias to group unbinding.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.2.20 Functional alias to group unbinding response
|
Table 10.13.2.20-1 describes the information flow functional alias to group unbinding response from the MC service client to the MC service server.
Table 10.13.2.20-1: Functional alias to group unbinding response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator who triggers the functional alias to group unbinding request.
Result
M
Indicates the success or failure for the result
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.3 Authorised MC service user retrieves active functional alias(es) for certain MC service user(s)
|
An authorised MC service user can request the active functional alias(es) for one or more MC service users.
Figure 10.13.3-1 below illustrates the active functional alias list query for the MC service user(s).
Figure 10.13.3-1: Active functional alias list query for the user
1. The MC service client of the MC service user requests the list(s) of active functional aliases for each MC service user(s) from the MC service server by sending an active functional alias information user query request. The MC service ID(s) to be queried is included.
2. The MC service server checks whether the MC service user is authorized to perform the query. If authorized, then the MC service server retrieves the requested active functional alias information based on the MC service ID(s).
3. The MC service server sends an active functional alias information user query response including the functional alias information to the MC service client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.4 MC service user activates functional alias(es) within an MC system
|
The procedure for MC service user activates functional alias(es) within an MC system is illustrated in figure 10.13.4-1.
Pre-conditions:
1. MC service client has already been provisioned (statically or dynamically) with the functional alias(es) information that the MC service client is allowed to activate.
2. MC service server may have retrieved the user profile and functional alias policy from the functional alias configuration e.g. which user(s) are authorized to activate to what functional alias, priority, and other configuration data.
3. MC service client may have indicated to the functional alias management server that it wishes to receive updates of functional alias data for the functional aliases for which it is authorized.
4. The MC service client triggers the functional alias activation procedure. This is an explicit activation caused either by the MC service user or determined by a trigger event such as the MC service UE coming within a permitted geographic operational area of a functional alias.
Figure 10.13.4-1: Functional alias activation procedure within an MC system
1. MC service client of the MC service user requests the MC service server to activate a functional alias or a set of functional aliases.
NOTE 1: If the MC service server is not the one that performs the functional alias controlling role, the MC service server will forward the request to the MC service server that performs the functional alias controlling role.
2. The MC service server checks if there are any conflicts with active functional alias(es).
3. If the user of the MC service client is authorised to activate the requested functional alias(es) then the MC service server stores the functional alias(es) status of the requested functional alias(es).
If a certain functional alias(es) can be simultaneously active for multiple MC service users and the upper limit of number of simultaneous MC service users is not reached, the MC service shall activate the functional alias(es) for the MC service user and inform all other MC service user(s) with sharing the same functional alias(es) (step 5). If the limit of number of simultaneous MC service users is reached or the functional alias is not allowed to be shared, the request is rejected and the MC service user is notified (step 4).
If the functional alias(es) is (are) already used by another MC service user(s), an authorized MC service user gets an offer to take over the functional alias from the MC service user currently using the functional alias(es).
NOTE 2: The functional alias status is notified to other servers (e.g. MC service servers) within the MC system that have subscribed to functional alias status.
4. MC service server sends a functional alias(es) activation response to the MC service client.
5. The MC service server informs all other MC service user(s) sharing the same functional alias(es).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.5 MC service user de-activates functional alias(es) within an MC system
|
The procedure for MC service user de-activates functional alias(es) within an MC system is illustrated in figure 10.13.5-1.
When an MC service user does not want to use a functional alias(es) anymore, then the MC service user can de-activate functional alias(es).
Pre-conditions:
1. MC service server has already subscribed to the functional alias(es) information from the functional alias management server and has stored the data of the functional alias(es) a MC service user has activated.
2. The MC service client triggers the functional alias(es) de-activation procedure. This is an explicit de-activation request either by the MC service user or determined by a trigger event such as the MC service UE moving outside a permitted geographic operational area of a functional alias.
Figure 10.13.5-1: Functional alias de-activation procedure within an MC system
1. MC service client requests the MC service server to de-activate a functional alias or a set of functional aliases.
NOTE 1: If the MC service server is not the one that performs the functional alias controlling role, the MC service server will forward the request to the MC service server that performs the functional alias controlling role.
2. Based on the MC service user profile and stored functional alias policy from the functional alias configuration, the MC service server checks if the MC service user of the MC service client is authorized to de-activate from the requested functional alias(es) and if the MC service user of the MC service client has activated to the requested functional alias(es).
3. If the MC service user is authorized to de-activate from the requested functional alias(es) then the MC service server updates the functional alias activation status of the MC service user.
NOTE 2: The functional alias status is notified to other servers (e.g. MC service servers) within the MC system that have subscribed to functional alias status.
4. MC service server provides to the MC service client the functional alias de-activation response.
5. The MC service server informs all other MC service user(s) sharing the same functional alias(es).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.6 Authorised MC service user takes over functional alias(es) within an MC system
|
The procedure for MC service user takes over functional alias(es) within an MC system is illustrated in figure 10.13.6-1.
During functional alias(es) activation, if the functional alias(es) is (are) already used by another MC service user(s), an authorized MC service user may get an offer to take over the functional alias(es) from the MC service user currently using the functional alias(es).
Pre-conditions:
1. MC service client 1 has performed the functional alias(es) activation procedure as described in subclause 10.13.4.
2. As result of the functional alias(es) activation procedure, the MC service user of MC service client 1 is aware which functional alias(es) are already used but can be taken over.
3. The MC service user of MC service client 1 decides to take over a functional alias.
Figure 10.13.6-1: Functional alias taking over procedure within an MC system
1. MC service client 1 of the MC service user 1 requests the MC service server to take over a functional alias by sending a functional alias take over request.
NOTE 1: If the MC service server is not the one that performs the functional alias controlling role, the MC service server will forward the request to the MC service server that performs the functional alias controlling role.
NOTE 2: For the sake of brevity takeover of single functional alias is shown in this procedure. If MC service user 1 decides to take over multiple functional aliases, then the Functional alias take over request in step 1 carries a list of those functional aliases.
2. The MC service server checks if there are any conflicts taking over the functional alias.
3. If the user of the MC service client 1 is authorised to take over the requested functional alias then the MC service server sends a functional alias revoke notification to inform MC service client 2 that the functional alias has been revoked and is not any longer active for the user of MC service client 2.
4. The MC service server stores the functional alias status of the requested functional alias.
NOTE 3: The functional alias status is notified to other servers (e.g. MC service servers) within the MC system that have subscribed to functional alias status.
5. MC service server sends a functional alias take over response to the MC service client.
6. The MC service server informs all other MC service user(s) sharing the same functional alias.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.7 Authorised MC service user retrieves MC service user(s) for certain active functional alias(es)
|
An authorised MC service user can request the MC service user(s) who have activated the functional alias being queried, for one or more functional aliases.
Figure 10.13.7-1 below illustrates the query of usage of the active functional alias(es) procedure.
Figure 10.13.7-1: Query of usage of the active functional alias(es)
1. The MC service client of the MC service user requests the list(s) of MC service user(s) who have actived the functional alias being queried, by sending an active functional alias information usage query request. The functional alias(es) to be queried are included.
2. The MC service server checks whether the MC service user is authorized to perform the query. If authorized, then the MC service server retrieves the requested MC service user(s) information for those MC service users who have actived the functional alias being queried.
3. The MC service server sends an active functional alias information usage query response including the MC service user information to the MC service client.
10.13.8 Automatic activation of functional alias(es) within an MC system
The MC Service Server can automatically activate functional aliases that can be specified by internal or external triggers such as location dependency, schedule, or timer.
The procedure for automatic activation of functional alias(es) within an MC system is illustrated in figure 10.13.8-1. The MC service client(s) get(s) notified by the MC service server at the time when a functional alias has been activated by the MC service server.
Pre-conditions:
1. MC service server may have retrieved the MC service user profile and functional alias policy from the functional alias configuration, for example, which MC service user(s) are authorized to activate which functional alias(es), to use corresponding priorities and other configuration data associated with the functional alias.
2. MC service server has already been provisioned with the functional alias(es) information that the MC service client is allowed to activate.
Figure 10.13.8-1: Automatic functional alias activation within an MC system
1. The condition e.g. timer or current location of the MC service user for automatic functional alias(es) activation is met.
2. The MC service server checks if there are any conflicts with current active functional alias(es).
a.) If a certain functional alias(es) can be simultaneously active for multiple MC service users and the upper limit of simultaneous MC service users is not reached, the MC service server shall activate the functional alias(es) for the corresponding MC service user and inform all other MC service user(s) that are sharing the same functional alias(es) (step 5).
b.) If the limit of simultaneous MC service users is reached or the functional alias is not allowed to be shared then the MC service server does not proceed with the functional alias(es) activation procedure or the MC service server can reassign the functional alias, i.e. takeover, from the MC service user currently using the functional alias(es) to the new MC service client.
3. MC service server notifies the MC service client about the activation of the functional alias(es).
4. The MC service server stores the functional alias(es) status for the functional alias(es), including date and time of activation.
5. The MC service server informs all other MC service user(s) sharing the same functional alias(es).
10.13.9 Automatic deactivation of functional alias(es) within an MC system
The MC Service Server can automatically activate functional aliases that can be specified by internal or external triggers such as location dependency, schedule, or timer.
The procedure for automatic deactivation of functional alias(es) within an MC system is illustrated in figure 10.13.9-1. The MC service client(s) get(s) notified by the MC service server at the time when a functional alias has been deactivated by the MC service server.
Pre-conditions:
1. MC service server has already retrieved the relevant functional alias(es) information from the configuration (functional alias) management server and has stored the data of the concerning functional alias(es) a MC service user has activated.
Figure 10.13.9-1: Automatic functional alias deactivation within an MC system
1. The condition e.g. timer or current location of the MC service user for automatic functional alias(es) deactivation is met. The trigger for deactivation may be done by the MC system or by an authorized external system attached to the MC system.
2. MC service server notifies the MC service client about the deactivation of the functional alias(es).
3. The MC service server stores the status, e.g. deactivated, of the concerned functional alias(es) and the corresponding MC service ID(s).
4. The MC service server informs all other MC service user(s) sharing the same functional alias(es).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.10 Subscription and notification for functional alias
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.10.1 General
|
The subscriber (e.g. MC service server, location management server) obtains the list of MC service users who have activated a functional alias from the functional alias controlling MC service server via subscription and notification mechanisms.
10.13.10.2 Subscription for functional alias procedure
The procedure for subscription for functional alias is described in figure 10.13.10.2-1.
Pre-conditions:
- The functional alias controlling MC service server holds a list of MC service users who has activated the functional alias.
Figure 10.13.10.2-1: Subscription for functional alias
1. The subscriber sends a subscribe functional alias request to the functional alias controlling MC service server in order to receive notifications about the list of MC service users who has activated the function alias.
2. The functional alias controlling MC service server provides a subscribe functional alias response to the subscriber indicating success or failure of the request.
10.13.10.3 Notification for functional alias procedure
The procedure for notification for functional alias as shown in figure 10.13.10.3-1 is used by the functional alias controlling MC service server to inform the subscriber about MC service users who has activated the functional alias.
Pre-conditions:
- The subscriber has subscribed to the functional alias
- The list of MC service users who has activated the functional alias is changed at functional alias controlling MC service server due to activation, deactivation or taken over.
Figure 10.13.10.3-1: Notification for the functional alias
1. The functional alias controlling MC service server provides the list of MC service users who has activated the functional alias in the notify functional alias request to the subscriber.
2. The subscriber provides a notify functional alias response to the functional alias controlling MC service server.
10.13.10.4 Unsubscription for functional alias procedure
The procedure for unsubscription for functional alias is described in figure 10.13.10.4-1.
Pre-conditions:
- The functional alias controlling MC service server holds a list of MC service users who has activated the functional alias.
Figure 10.13.10.4-1: Unsubscription for functional alias
1. The subscriber sends a unsubscribe functional alias request to the functional alias controlling MC service server in order to stop receiving notifications about the list of MC service IDs who has activated the function alias.
2. The functional alias controlling MC service server provides a subscribe functional alias response to the subscriber indicating success or failure of the request.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.11 Functional alias to group binding
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.11.1 General
|
The MC service client creates a functional alias to group binding association to be stored within the group controlling MC server. Once a functional alias is bound to a group it is bound till the functional alias is unbound to the group. After an MC service log-off the user's functional alias to group bindings are deleted.
NOTE: Affiliation and de-affiliation procedures do not change the functional alias to group binding.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.11.2 Functional alias to group binding
|
The procedure for binding a functional alias with a group is described in figure 10.13.11.2-1.
Pre-conditions:
- The MC service server has subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.13.11.2-1: Functional alias to group binding procedure
1. The MC service client sends a functional alias to group binding request to the group controlling MC service server to bind functional aliases to groups to be used for communications within those groups.
2. The group controlling MC service server provides a functional alias to group binding response to the MC service client indicating success or failure of the request.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.13.11.3 Functional alias to group unbinding
|
The procedure for unbinding a functional alias with a group is described in figure 10.13.11.3-1.
Pre-conditions:
- The MC service server has subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.13.11.3-1: Functional alias to group unbinding procedure
1. The MC service client sends a functional alias to group unbinding request to the group controlling MC service server to unbind functional aliases from groups which are not used for communications within those groups anymore.
2. The group controlling MC service server provides a functional alias to group unbinding response to the MC service client indicating success or failure of the request. The MC service server also checks whether the MC service client is the last client who has bound a certain functional alias to a group which may prevent unbinding that functional alias from the group.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14 Generic procedures for interconnection
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.1 General
|
Interconnection provides a means for communication between different MC systems with differing levels of trust between those MC systems. This subclause describes generic procedures for interconnection which are variations of specific procedures detailed in 3GPP TS 23.379 [16] and 3GPP TS 23.281 [12]. These procedures should be read in conjunction with specific procedures in those specifications.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.2 Generic call procedure with topology hiding
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.2.1 General
|
The procedure in this subclause applies to MC service group calls and private calls made between multiple MC systems where topology hiding is required. An MC gateway server in an MC system is used to route calls to and from partner MC systems, and by doing so hides the topology of the MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.2.2 Procedure for calls with topology hiding
|
Figure 10.14.2.2-1 shows the procedure where an MC service client initiates an MC service group call to an MC service group where the primary MC system of that MC service group is an interconnected MC system, or where an MC service client initiates an MC service private call to an MC service user where the primary MC system of that MC service user is an interconnected partner MC system. In this procedure, both MC systems make use of topology hiding.
NOTE 1: This procedure does not illustrate the case where the target MC service client has migrated, and where further forwarding of the call request is required.
Pre-conditions:
1. MC service client 1 is receiving MC service in a different MC system to the primary MC system of the target MC service group or MC service user, and the MC systems are interconnected.
NOTE 2: MC service client 1 may be receiving service in the primary MC system of MC service client 1, or may have successfully migrated to a partner MC system.
2. If the call to be originated by MC service client 1 is an MC service group call, MC service client 1 has affiliated to the MC service group.
3. If the call to be originated by MC service client 1 is an MC service private call, the target MC service client, MC service client 2, is receiving service from the primary MC system of that MC service client.
Figure 10.14.2.2-1: Call to target in interconnected MC system
1. MC service client 1 initiates a call request to a target MC service user or MC service group, where the primary MC system of that MC service user or MC service group is an interconnected partner MC system.
2. The serving MC service server of MC service client 1 determines that the call has a target in a different MC system, and that the MC gateway server is the correct next hop for the call.
3. The serving MC service server of MC service client 1 forwards the call request to the MC gateway server of the serving MC system.
4. The MC gateway server identifies the correct partner MC system which is the primary MC system for the target of the call.
NOTE 3: The MC gateway server of the serving MC system of MC service client 1 will contain configuration to allow it to route the call request over the signalling plane to the MC gateway server in the partner MC system.
5. The MC gateway server of the primary MC system of MC service client 1 forwards the call request to the MC gateway server of the partner MC system.
6. The MC gateway server of the partner MC system determines the MC service server which is the primary MC service server for the target MC service user or MC service group.
NOTE 4: The MC gateway server of the partner MC system will contain configuration allowing it to make use of the target MC service ID or MC service group ID to identify the primary MC service server of the target MC service user or MC service group.
7. The call request is forwarded to the partner MC service server which is the primary MC service server of the target MC service user or MC service group.
8. The partner MC service server which is the primary MC service server of the target MC service user or MC service group checks that the call is authorized to be made. The authorization process checks that the call origin is permissible (i.e. from the serving MC system of calling MC service user, and from that calling MC service user) for a call to the target MC service user or MC service group.
9. Providing that the authorization in step 8 is successful, the call request is sent to MC service client 2.
10. MC service client 2 sends a call response to the call request.
11. The partner MC service server, which is the primary MC service server of the target MC service user or MC service group, sends a call response to the MC gateway server in the partner MC system.
12. The MC gateway server in the partner MC system sends the call response to the MC gateway server in the primary MC system of MC service client 1.
13. The MC gateway server in the primary MC system sends the call response to the serving MC service server of MC service client 1.
14. The serving MC service server sends the call response to MC service client 1.
NOTE 5. Steps 9 and 10 may occur at any time after step 8 and prior to step 15, provided that step 9 always take place before step 10. If the authorization in step 8 has failed, then steps 9 and 10 do not occur.
15.If the call response was successful, floor control and media paths are established for the call.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.3 Generic call procedure for enforcement of local MC service group configuration
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.3.1 General
|
The procedure in the following subclauses apply to MC service group calls made between multiple MC systems where the partner MC system applies local configuration to the MC service group configuration which has been provided by the primary MC system of the MC service group. The serving MC server of the MC service group members, that is a participating server for the MC service group, applies enforcement of local MC service group configuration.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.3.2 MC service group call initiated in the partner MC system of the MC service group
|
Figure 10.14.3.2-1 shows the procedure where an MC service group call is initiated by an MC service client receiving MC service in the partner MC system of the MC service group.
NOTE 1: Any topology hiding by the primary or partner MC system of the MC service group is not shown within this procedure.
Pre-conditions:
1. MC service client 1 is receiving MC service in a partner MC system of the MC service group, and the MC systems are interconnected.
NOTE 2: MC service client 1 can be receiving service in the primary MC system of MC service client 1, or can have successfully migrated to a partner MC system.
2. MC service client 1 has affiliated to the MC service group.
Figure 10.14.3.2-1: Enforcement of local configuration with call originated in partner MC system of MC service group
1. MC service client 1 initiates a group call request to the MC service group, where the primary MC system of that MC service group is an interconnected partner MC system.
2. The serving MC service server of MC service client 1 authorizes the group call request using local group configuration information.
3. If the group call request authorization by the serving MC service server of MC service client 1 is successful, the serving MC service server forwards the group call request to the group host MC service server in the primary MC system of the MC service group.
4. The primary MC service server of the MC service group checks that the call is authorized to be made. The authorization process checks that the call origin is permissible (i.e. from the serving MC system of calling MC service user, and from that calling MC service user) for a call to that MC service group.
5. Providing that authorization in step 4 is successful, the group call response is sent to the serving MC service server of MC service client 1.
6. The serving MC service server sends the MC service group call response to MC service client 1.
7. Floor control or transmission control and media paths are established for the MC service group call.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.3.3 MC service group call request received from the primary MC system of the MC service group
|
Figure 10.14.3.3-1 shows the procedure where an MC service group call request is received from the primary MC system of the MC service group, which includes an MC service group member MC service client 1 that is receiving service within the partner MC system of the MC service group. Any topology hiding by the primary or partner MC system of the MC service group is not shown within this procedure.
Pre-conditions:
1. MC service client 1 is receiving MC service in a partner MC system of the MC service group, and the MC systems are interconnected.
NOTE: MC service client 1 can be receiving service in the primary MC system of MC service client 1, or can have successfully migrated to a partner MC system.
2. MC service client 1 has affiliated to the MC service group.
Figure 10.14.3.3-1: Enforcement of local configuration where group call request is received from primary MC system of MC service group
1. A group call request is received from the group host MC service server in the primary MC system of the MC service group.
2. The serving MC service server of MC service client 1 authorizes the group call request using local group configuration information.
3. If the group call request authorization by the serving MC service server of MC service client 1 is successful, the serving MC service server sends the group call request to MC service client 1.
4. MC service client 1 responds to the group call request with a group call response.
5. The group call response is sent to the group host MC service server of the MC service group.
6. Floor control or transmission control and media paths are established for the MC service group call.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.4 Generic call procedure for media replication in participating MC system in MC service group calls
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.4.1 General
|
The procedure in the following subclause applies to MC service group calls made between multiple MC systems where the partner MC system carries out media replication to served MC service group members.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.14.4.2 Media replication in the partner MC system of the MC service group
|
Figure 10.14.4.2-1 shows the procedure where an MC service group call is initiated by an MC service client receiving MC service in the primary MC system of the MC service group, and media replication takes place in the partner MC system.
NOTE 1: Any topology hiding by the primary or partner MC system of the MC service group is not shown within this procedure.
Pre-conditions:
1. MC service client 1 is receiving MC service in the primary MC system of the MC service group, and the MC systems are interconnected.
2. MC service clients 2, 3 and n are receiving MC service in the partner MC system of the MC service group.
NOTE 2: MC service clients 2,3 and n can be receiving MC service in the primary MC system of MC clients 2, 3 and n, or one or more of MC service clients 2, 3 and n can have successfully migrated to a partner MC system.
3. MC service clients 1, 2, 3 and n have affiliated to the MC service group.
Figure 10.14.4.2-1: Media replication in partner MC system of MC service group
1. An MC service group call is set up and floor or transmission control and media paths are established, and MC service client 1 requests permission to transmit media to the MC service group.
2. The group host MC service server grants the requested floor or transmission permission to MC service client 1.
3a. MC service client 1 transmits a media stream to the group host MC service server.
3b. The group host MC service server sends a single media stream to the serving MC service server of MC service clients 2, 3 and n in the partner MC system of the MC service group.
3c. The serving MC service server of MC service clients 2, 3 and n replicates and distributes the media to MC service clients 2, 3 and n.
NOTE 3: Media distribution to MC service clients 2, 3 and n may be using unicast or multicast bearers.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15 Preconfigured regrouping
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.1 General
|
The following subclauses specify the information flows and procedures for group and user regrouping using preconfigured groups for 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])
- MCData (as specified in 3GPP TS 23.282 [13])
MC service specific pre-requisites and resultant behaviour by functional entities in performing these procedures are specified in the respective MC service TSs as listed above.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2 Information flows for preconfigured regrouping
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.1 Preconfigured regroup request (MC service client – MC service server)
|
Table 10.15.2.1-1 describes the information flow preconfigured regroup request from the MC service client to the MC service server.
Table 10.15.2.1-1 Preconfigured regroup request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester
MC service group ID
O
MC service group ID of the regroup group
MC service group ID
M
MC service group ID of the MC service group from which configuration is to be taken
MC service group ID list
O
(see NOTE 1)
List of MC service groups to be regrouped into the group regroup group
MC service user ID list
O
(see NOTE 1)
List of MC service users to be regrouped into the user regroup group
MC service user criteria
O
(see NOTE 1, NOTE 2)
Carries the details of criteria which will be used by the MC service server for determining the participants. For example, it can be a location based criteria to determine the MC service user ID list in a particular area, or it could be tags (e.g. "fire", "medical", "police", etc.), or a combination of tags and location, which is left to implementation.
NOTE 1: One and only one of these shall be present.
NOTE 2: This information element is used only for the user regroup procedures
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.2 Preconfigured regroup request (MC service server – MC service client)
|
Table 10.15.2.2-1 describes the information flow preconfigured regroup request from the MC service server to the MC service client.
Table 10.15.2.2-1 Preconfigured regroup request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the target MC service group member
MC service group ID
M
MC service group ID of the regroup group
MC service group ID
M
MC service group ID of the MC service group from which configuration is to be taken
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.3 Preconfigured regroup request (MC service server – MC service server)
|
Table 10.15.2.3-1 describes the information flow preconfigured regroup request from the MC service server to the MC service server.
Table 10.15.2.3-1 Preconfigured regroup request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester
MC service group ID
M
MC service group ID of the regroup group
MC service group ID
M
MC service group ID of the MC service group from which configuration is to be taken
MC service group ID list
O
List of MC service groups to be regrouped into the group regroup group
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.4 Preconfigured regroup response (MC service client – MC service server)
|
Table 10.15.2.4-1 describes the information flow preconfigured regroup response from the MC service client to the MC service server.
Table 10.15.2.4-1 Preconfigured regroup response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the responding MC service client
MC service group ID
M
MC service group ID of the regroup group
Result
M
Result of the regrouping operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.5 Preconfigured regroup response (MC service server – MC service client)
|
Table 10.15.2.5-1 describes the information flow preconfigured regroup response from the MC service server to the MC service client.
Table 10.15.2.5-1 Preconfigured regroup response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of the regrouping operation
MC service group ID
M
MC service group ID of the regroup group
Result
M
Result of the regrouping operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.6 Preconfigured regroup response (MC service server – MC service server)
|
Table 10.15.2.6-1 describes the information flow preconfigured regroup response from the MC service server to the MC service server.
Table 10.15.2.6-1 Preconfigured regroup response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the responding MC service client
MC service group ID
M
MC service group ID of the regroup group
Result
M
Result of the regrouping operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.7 Preconfigured regroup cancel request (MC service client – MC service server)
|
Table 10.15.2.7-1 describes the information flow preconfigured regroup cancel request from the MC service client to the MC service server.
Table 10.15.2.7-1 Preconfigured regroup cancel request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester
MC service group ID
M
MC service group ID of the regroup group
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.8 Preconfigured regroup cancel request (MC service server – MC service client)
|
Table 10.15.2.8-1 describes the information flow preconfigured regroup cancel request from the MC service server to the MC service client.
Table 10.15.2.8-1 Preconfigured regroup cancel request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the target MC service user or MC service group member
MC service group ID
M
MC service group ID of the regroup group
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.9 Preconfigured regroup cancel request (MC service server – MC service server)
|
Table 10.15.2.9-1 describes the information flow preconfigured regroup cancel request from the MC service server to the MC service server.
Table 10.15.2.9-1 Preconfigured regroup cancel request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester
MC service group ID
M
MC service group ID of the regroup group
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.10 Preconfigured regroup cancel response (MC service client – MC service server)
|
Table 10.15.2.10-1 describes the information flow preconfigured regroup cancel response from the MC service client to the MC service server.
Table 10.15.2.10-1 Preconfigured regroup cancel response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the responding MC service client
MC service group ID
M
MC service group ID of the regroup group
Result
M
Result of the regrouping operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.11 Preconfigured regroup cancel response (MC service server – MC service client)
|
Table 10.15.2.11-1 describes the information flow preconfigured regroup cancel response from the MC service server to the MC service client.
Table 10.15.2.11-1 Preconfigured regroup cancel response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of the regroup removal
MC service group ID
M
MC service group ID of the regroup group
Result
M
Result of the regrouping operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.12 Preconfigured regroup cancel response (MC service server – MC service server)
|
Table 10.15.2.12-1 describes the information flow preconfigured regroup cancel response from the MC service server to the MC service server.
Table 10.15.2.12-1 Preconfigured regroup cancel response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of the regroup removal
MC service group ID
M
MC service group ID of the regroup group
Result
M
Result of the regroup removal operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.13 Preconfigured regroup reject (MC service server – MC service client)
|
Table 10.15.2.13-1 describes the information flow preconfigured regroup reject from the MC service server to the MC service client.
Table 10.15.2.13-1 Preconfigured regroup reject information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of the regrouping
MC service group ID
M
MC service group ID of the regroup group
Reject reason
M
Reason for rejecting the regrouping operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.14 Preconfigured regroup reject (MC service server – MC service server)
|
Table 10.15.2.14-1 describes the information flow preconfigured regroup reject from the MC service server to the MC service server.
Table 10.15.2.14-1 Preconfigured regroup reject information elements
Information Element
Status
Description
MC service group ID
M
MC service group ID of the regroup group
Reject reason
M
Reason for rejecting the regrouping operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.15 Preconfigured user regroup remove request (MC service server – MC service client)
|
Table 10.15.2.15-1 describes the information flow preconfigured user regroup remove request from the MC service server to MC service client.
Table 10.15.2.15-1 Preconfigured user regroup remove request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the MC service user to be removed from the regroup group
MC service group ID
M
MC service group ID of the regroup group from which the MC service user is to be removed
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.16 Preconfigured user regroup remove response (MC service client – MC service server)
|
Table 10.15.2.16-1 describes the information flow preconfigured user regroup remove response from the MC service client to the MC service server.
Table 10.15.2.16-1 Preconfigured user regroup remove response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the MC service user to be removed from the preconfigured regroup
Result
M
Result of the preconfigured user regroup removal operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.2.17 Preconfigured regroup request return (MC service server – MC service client)
|
Table 10.15.2.17-1 describes the information flow preconfigured regroup request return from the MC service server to the MC service client.
Table 10.15.2.17-1 Preconfigured regroup request return information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the calling party
MC service group ID
O
The MC service group ID to be associated with the preconfigured regroup group call which is either provided by the group call initiator or assigned by the MC service server. This information element shall be present if the authorization result is success.
Authorization result
M
Indicate if authorization is success or failure
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3 Regroup with preconfigured group
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.1 General
|
A group regroup may be achieved by regrouping MC service groups into a new MC service regroup group which uses the configuration of a separate preconfigured MC service group. The MC service regroup group configuration needs to be provided to the relevant MC service group members of the MC service groups that will be regrouped in advance of the regrouping operation.
A user regroup may be achieved by regrouping MC service users into a new MC service regroup group which uses the configuration of a separate preconfigured MC service group. The MC service regroup group configuration needs to be provided to the relevant MC service users who will be regrouped in advance of the regrouping operation.
NOTE 1: A preconfigured group which is intended only to provide configuration for the preconfigured regroup process is identified by a parameter in group configuration described in this specification.
NOTE 2: The configuration may alternatively be taken from any MC service group that has been configured in the user profile of all the relevant MC service users who will be regrouped.
NOTE 3: Regroup groups may be defined according to the organizational structure of a mission critical organization, or by some other means which allows the MC service client of an authorized user to be aware of an appropriate regroup group for sets of MC service groups or MC service users that will be regrouped together.
The preconfigured MC service group that provides the configuration is not used as the MC service regroup group itself, it only provides configuration for one or more MC service regroup groups. The MC service group ID of the regroup group is provided by the authorized user when the preconfigured regrouping is carried out.
The MC service regroup group can be specified to be a broadcast or non-broadcast type according to the configuration of the MC service group whose configuration is specified by the regroup request. The broadcast type of regroup is used for one-way communication where only an authorized MC service user is allowed to transmit and all other regroup members are only allowed to receive the communication (e.g. a call from a dispatcher to all regroup members). The non-broadcast type is used for two-way communication where all regroup members can transmit and receive (i.e, the regroup group call behaves like a normal non-broadcast group call).
For group regrouping, if the MC service server has been notified by the group management server that one of the MC service groups that has been requested for regrouping by means of these procedures has already been regrouped, the MC service server shall reject the request for regrouping described in the following procedures.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.2 Preconfigured regroup procedures in a single MC system
|
The following subclauses define group and user regroup procedures using preconfigured groups within a single MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.2.1 Preconfigured Group Regroup formation in a single MC system
|
Figure 10.15.3.2.1-1 illustrates the procedure to initiate a group regroup using a preconfigured MC service group. The procedure takes place prior to the establishment of a group call to the MC service regroup group.
Pre-conditions:
- MC service client 2 is an affiliated member of MC service group 1 and MC service client 3 is an affiliated member of MC service group 2.
- The MC service group identity and group configuration for the preconfigured MC service group have been preconfigured in MC service clients 2 and 3, and MC service clients 2 and 3 have received the relevant security related information to allow them to communicate in the MC service regroup group.
- MC service client 1 is authorized to initiate a preconfigured group regroup procedure.
- MC service client 1 is aware of a suitable preconfigured MC service group whose configuration has been preconfigured in the MC service UEs of the group members who will be regrouped.
- In order to be aware whether a group is currently regrouped, the MC service server is subscribed to the group configuration in the GMS.
- The GMS has subscribed to group dynamic data from the MC service server using the procedures defined in subclause 10.1.5.6.
Figure 10.15.3.2.1-1: Regroup procedure using preconfigured group in a single MC system
1. The authorized user of MC service client 1 initiates the group regroup procedure, specifying the list of MC service groups to be regrouped (MC service groups 1 and 2), the MC service group ID of the regroup group (if available) and the MC service group ID of the group from which configuration information for the regroup group is to be taken.
2. MC service client 1 sends the preconfigured regroup request to the MC service server.
3. The MC service server checks that MC service client 1 is authorized to initiate a preconfigured group regroup procedure, and resolves the group identities of the MC service groups requested in step 1. The MC service server also checks which group members are affiliated to MC service groups 1 and 2. The MC service server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MC service server. The MC service server also checks that none of the MC service groups that are requested for regrouping are already regrouped by any mechanism. If the preconfigured regroup request is authorized, the MC service server assigns a MC service group ID for this regroup group if:
i. one is not provided in the request or
ii. the one provided in the request is not accepted.
NOTE 1: This procedure does not require that that the authorized user of MC service client 1 is a group member of MC service groups 1 or 2, or that the authorized user of MC service client 1 is an affiliated group member of MC service groups 1 or 2.
NOTE 2: The list of groups included in the group regroup is held in dynamic data in the MC service server, and is not used to update group configuration information in the group management server.
4a. If the MC service server determines that any of the groups requested for regrouping, including the regroup group, have been regrouped by other group regrouping procedures, the MC service server then sends a preconfigured regroup reject back to MC service client 1 with a reject reason indicating that one of the groups has already been regrouped, and this procedure terminates.
4b. The MC service server shall send the preconfigured regroup request return message to MC service client 1 containing the below:
i. result of whether the preconfigured regroup is authorized or not; and
ii. the MC service group ID if authorized
5. If the preconfigured regroup request is not authorized, MC service client 1 shall not proceed with the rest of the steps and this procedure terminates.
5a/b. The MC service server sends the preconfigured regroup requests to MC service clients 2 and 3.
NOTE 3: Only group members that are affiliated to the MC service groups that are to be regrouped are sent a preconfigured regroup request.
6a/b. MC service clients 2 and 3 notify their users of the regrouping.
7a/b. MC service clients 2 and 3 may send the preconfigured regroup response to the MC service server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request.
8. The MC service server affiliates the regrouped MC service clients to the regroup group.
9. The MC service server sends a preconfigured regroup response to MC service client 1.
After the group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.15.3.2.3.
MC service client participation in the ongoing regroup persists until the MC service client is no longer affiliated to any of the regrouped groups (group 1 or 2 in this procedure).
MC service client affiliation to the regroup group may cease when the UE's MC service ceases, e.g. when the UE is powered down, or by performing a log-off operation.
Editor's note: Data persistence in the MC service client following a user log-off or power down needs further study.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.2.2 Preconfigured User Regroup formation in a single MC system
|
Figure 10.15.3.2.2-1 illustrates the procedure to initiate a user regroup procedure using a preconfigured MC service group. The procedure takes place prior to the establishment of a group call to the MC service regroup group.
Pre-conditions:
- MC service clients 2 and 3 are registered with the MC service server.
- The preconfigured MC service group have been preconfigured in MC service clients 2 and 3, and MC service clients 2 and 3 have received the relevant security related information to allow them to communicate in the MC service user regroup group.
- MC service client 1 is authorized to initiate a user regroup using the preconfigured user regroup procedure.
- MC service client 1 is aware of a suitable preconfigured MC service group whose configuration has been preconfigured in the MC service UEs of the MC service users who will be regrouped.
Figure 10.15.3.2.2-1: User regroup procedure using preconfigured group in a single MC system
1. The authorized user of MC service client 1 initiates the user regroup procedure, specifying the list of MC service users to be regrouped (MC service clients 2 and 3), the MC service group ID of the regroup group (if available), and the MC service group ID of the group from which configuration information for the regroup group is to be taken. Alternatively, the MC service client 1 can provide the criteria which allows the MC service server to determine the list of MC service users to be regrouped.
2. MC service client 1 sends the preconfigured regroup request to the MC service server. The request indicates the list of users to be included in the regroup operation.
3. The MC service server checks that MC service client 1 is authorized to initiate a preconfigured user regroup procedure. If the preconfigured regroup request is authorized, the MC service server assigns a MC service group ID for this regroup group call if:
i. one is not provided in the request or
ii. the one provided in the request is not accepted.
NOTE 1: MC service clients can be involved in multiple user and group regroups simultaneously.
4. The MC service server shall send the preconfigured regroup request return message to MC service client 1 containing the below:
i. result of whether the preconfigured regroup is authorized or not; and
ii. the MC service group ID if authorized
If the preconfigured regroup request is not authorized, MC service client 1 shall not proceed with the rest of the steps and this procedure terminates.
5a/b. The MC service server sends the preconfigured regroup requests to MC service clients 2 and 3.
NOTE 2: When using multicast, the MC service server can periodically rebroadcast the preconfigured regroup request.
6a/b. MC service clients 2 and 3 notify their users of the regrouping.
7a/b. MC service clients 2 and 3 may send the preconfigured regroup response to the MC service server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request.
8. The MC service server affiliates the regrouped MC service clients to the regroup group.
9. The MC service server sends a preconfigured regroup response to MC service client 1.
NOTE 3: After the user regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.15.3.2.3.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.2.3 Preconfigured regroup cancellation in a single MC system
|
Figure 10.15.3.2.3-1 illustrates the procedure to cancel a group or user regroup that uses a preconfigured MC service group.
Pre-conditions:
- MC service clients 2 and 3 have been regrouped into a MC service regroup group that uses the configuration of a preconfigured MC service group.
- MC service client 1 is authorized to cancel a group or user regroup that uses a preconfigured MC service group.
- The GMS has subscribed to group dynamic data from the MC service server using the procedures defined in subclause 10.1.5.6.
Figure 10.15.3.2.3-1: Cancel preconfigured regroup procedure in a single MC system
1. The authorized user of MC service client 1 initiates the cancellation of the regrouping that uses a preconfigured MC service group.
2. MC service client 1 sends the preconfigured regroup cancel request to the MC service server, specifying the MC service group ID of the regroup group.
3. The MC service server checks that MC service client 1 is authorized to cancel a regrouping that used a regroup procedure with preconfigured groups.
4. The MC service server sends the preconfigured regroup cancel request to MC service clients 2 and 3 (steps 4a and 4b respectively).
5. MC service clients 2 and 3 notify their users of the cancellation of the regrouping in steps 5a and 5b respectively.
6. MC service clients 2 and 3 may send the preconfigured regroup cancel response to the MC service server to acknowledge the cancellation of the regrouping function. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup cancel request.
7. The MC service server deaffiliates MC service clients 2 and 3 from the MC service regroup group.
8. The MC service server sends a preconfigured regroup cancel response to MC service client 1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.3 Preconfigured regroup procedures in multiple MC systems
|
The following subclauses define group and user regroup procedures using preconfigured groups in multiple MC systems.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.3.1 Preconfigured Group Regroup formation in multiple MC systems
|
Figure 10.15.3.3.1-1 illustrates the procedure to initiate a group regroup procedure using a preconfigured MC service group, where at least one of the groups to be regrouped is configured in a partner MC system. The primary MC system where the preconfigured group regrouping is initiated does not need to be aware of the list of group members belonging to groups whose group home system is the partner MC system. If the group management server in the primary MC system of the MC service regroup group shares the necessary security related parameters together with the group configuration of the preconfigured MC service group with the group management server in the partner MC system and the group management server in the partner MC system distributes this configuration including those security parameters to its served MC service users according to the procedures in subclause 10.2.7, the primary MC system does not need to be aware of the list of group members of the MC service regroup group that are receiving service in the partner MC system.
The procedure takes place prior to the establishment of a group call to the MC service regroup group.
In this procedure, any gateway MC servers in the primary or partner MC systems are not shown.
Pre-conditions:
- MC service client 1 is authorized to initiated a preconfigured regroup procedure, and is receiving MC service in the primary MC system of MC service client 1.
- MC service client 2 is an affiliated member of MC service group 1 where MC service group 1 is defined in the partner MC system and MC service client 2 is receiving service in the partner MC system of MC service client 1.
- The preconfigured MC service group have been preconfigured in MC service client 2, and MC service client 2 has received the relevant security related information to allow communication in the MC service regroup group.
- In order to be aware whether the group is regrouped, the MC service server is subscribed to the group configuration in the GMS.
- The GMS has subscribed to group dynamic data from the MC service server within the same MC system using the procedures defined in subclause 10.1.5.6
Figure 10.15.3.3.1-1: Group regroup procedure using preconfigured group in multiple MC systems
1. The authorized user of MC service client 1 initiates the group regroup procedure, specifying the list of MC service groups to be regrouped including MC service group 1, the MC service group ID of the regroup group (if available) and the MC service group ID of the group from which configuration information for the regroup group is to be taken.
2. MC service client 1 sends the preconfigured regroup request to the MC service server.
3. The MC service server checks that MC service client 1 is authorized to initiate a preconfigured group regroup procedure, and resolves the group identities of the MC service groups requested in step 1. The MC service server also checks which group members are affiliated to the requested MC service groups that are homed in the primary MC system. The MC service server identifies any partner systems which are the group home systems for MC service groups identified in the list of groups to be regrouped. The MC service server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MC service server. The MC service server also checks that none of the MC service groups that are homed in the primary MC system and that are requested for regrouping are already regrouped by any mechanism. If the preconfigured regroup request is authorized, the MC service server assigns a MC service group ID for this regroup group if:
i. one is not provided in the request, or
ii. the one provided in the request is not accepted.
NOTE 1: This procedure does not require that that the authorized user of MC service client 1 is a group member of the MC service groups listed in the regroup request, or that the authorized user of MC service client 1 is an affiliated group member of any of the listed MC service groups.
4a. If the MC service server determines that any of the groups requested for regrouping, including the regroup group, have been regrouped by other group regrouping procedures, the MC service server then sends a preconfigured regroup reject back to MC service client 1 with a reject reason indicating that one of the groups has already been regrouped, and this procedure terminates.
4b. The MC service server shall send the preconfigured regroup request return message to MC service client 1 containing the below:
i. result of whether the preconfigured regroup is authorized or not; and
ii. the MC service group ID if authorized
If the preconfigured regroup request is not authorized, MC service client 1 shall not proceed with the rest of the steps and this procedure terminates.
5. The MC service server sends the preconfigured regroup requests to the MC service server in the partner MC system.
6. The partner MC service server checks the status of any MC service groups hosted by that partner MC service server, and identifies affiliated group members of any of the identified MC service groups (both MC service groups that are hosted in the primary MC system and MC service groups that are hosted in the partner MC system) that are receiving MC service service in the partner MC system, which include MC service client 2.
7. The partner MC service server sends the preconfigured regroup request to MC service client 2.
NOTE 2: Only group members that are affiliated to the MC service groups that are to be regrouped are sent a preconfigured regroup request.
8. MC service client 2 notifies the user of the regrouping.
9. MC service client 2 may send the preconfigured regroup response to the partner MC service server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the preconfigured regroup request.
10. The partner MC service server affiliates the regrouped MC service client 2 to the regroup group.
11. The partner MC service server sends a preconfigured regroup response to the primary MC service server.
12. The primary MC service server sends the preconfigured regroup response to MC service client 1.
After the group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.15.3.3.3.
MC service client participation in the ongoing regroup persists until the MC service client is no longer affiliated to any of the regrouped groups (group 1 or 2 in this procedure).
MC service client affiliation to the regroup group may cease when the UE's MC service ceases, e.g. when the UE is powered down, or by performing a log-off operation.
Editor's note: Data persistence in the MC service client following a user log-off or power down needs further study.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.3.2 Preconfigured User Regroup formation in multiple MC systems
|
Figure 10.15.3.3.2-1 illustrates the procedure to initiate a user regroup procedure using a preconfigured MC service group, where at least one of the MC service users to be regrouped is homed in a partner MC system. It is assumed that the group management server in the primary MC system of the MC service regroup group shares the necessary security related parameters together with the group configuration of the preconfigured MC service group with the group management server in the partner MC system and the group management server in the partner MC system distributes this configuration including those security parameters to its served MC service users according to the procedures in subclause 10.2.7.
The procedure takes place prior to the establishment of a group call to the MC service regroup group.
In this procedure, any gateway MC servers in the primary or partner MC systems are not shown.
Pre-conditions:
- MC service client 1 is homed in the primary MC system and is receiving service in the primary MC system.
- MC service client 2 is homed in the partner MC system and is receiving service in the partner MC service system of MC client 1.
- The MC service group identity and group configuration for the preconfigured MC service group have been preconfigured in MC service client 2, and MC service client 2 has received the relevant security related information to allow communication in the MC service regroup group.
- MC service client 1 is authorized to initiate a preconfigured user regroup procedure.
- MC service client 1 is aware of a suitable preconfigured group whose configuration has been preconfigured in the MC service UEs of the MC service users who will be regrouped.
Figure 10.15.3.3.2-1: User regroup procedure using preconfigured group in multiple MC systems
1. The authorized user of MC service client 1 initiates the user regroup procedure, specifying the list of MC service users to be regrouped including MC service client 2, the MC service group ID of the regroup group, and the MC service group ID of the group from which configuration information for the regroup group is to be taken.
2. MC service client 1 sends the preconfigured regroup request to the primary MC service server. The request indicates the list of users to be included in the regroup operation.
3. The primary MC service server checks that MC service client 1 is authorized to initiate a preconfigured user regroup procedure.
NOTE 1: MC service clients can be involved in multiple user and group regroups simultaneously.
4. The primary MC service server sends the preconfigured regroup requests to the MC service server in the partner MC system.
5. The partner MC service server checks that the primary MC service server is authorized to include MC service users homed in the partner system.
6. The partner MC service server sends the preconfigured regroup request to MC service client 2.
7. MC service client 2 notifies the user of the regrouping.
8. MC service client 2 may send the preconfigured regroup response to the partner MC service server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the preconfigured regroup request.
9. The partner MC service server affiliates the regrouped MC service client 2 to the regroup group.
10. The partner MC service server sends a preconfigured regroup response to the primary MC service server.
11. The primary MC service server sends the preconfigured regroup response to MC service client 1.
NOTE 2: After the user regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.15.3.3.3.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.3.3 Preconfigured regroup cancellation in multiple MC systems
|
Figure 10.15.3.3.3-1 illustrates the procedure to cancel a group or user regroup that uses a preconfigured MC service group where multiple MC systems were involved in the regrouping.
Pre-conditions:
- MC service client 2 has been regrouped into the MC service regroup group, and is receiving service in the partner MC system of the regroup group.
- MC service client 1 is authorized to cancel a regrouping that uses a preconfigured MC service group, and is receiving service in the primary MC system of the regroup group.
- The GMS has subscribed to group dynamic data from the MC service server within the same MC system using the procedures defined in subclause 10.1.5.6.
Figure 10.15.3.3.3-1: Cancel preconfigured regroup procedure in multiple MC systems
1. The authorized user of MC service client 1 initiates the cancellation of the regrouping that uses a preconfigured MC service group.
2. MC service client 1 sends the preconfigured regroup cancel request to the MC service server, specifying the MC service group ID of the regroup group.
3. The MC service server checks that MC service client 1 is authorized to cancel a regrouping that uses a preconfigured group regroup procedure.
4. The primary MC service server sends the regroup cancel request to the partner MC service server.
5. The partner MC service server sends the preconfigured regroup cancel requests to MC service client 2.
6. MC service client 2 notifies the user of the cancellation of the group regrouping.
7. MC service client 2 may send the preconfigured regroup cancel response to the partner MC service server to acknowledge the cancellation of the regrouping function. This acknowledgement is not sent in response to a multicast transmission of the preconfigured regroup cancel request.
8. The partner MC service server deaffiliates MC service client 2 from the MC service regroup group.
9. The partner MC service server sends the preconfigured regroup cancel response to the primary MC service server.
10. The primary MC service server sends a preconfigured regroup cancel response to MC service client 1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.3.4 Preconfigured group regroup rejection in multiple MC systems
|
Figure 10.15.3.3.4-1 illustrates the case where the procedure to initiate a group regroup with multiple MC systems using a preconfigured MC service group described in subclauses 10.15.3.3.1 commences, but where the request for the regroup is rejected by the partner MC service server. The rejection can occur, for example because one of the groups hosted by the partner MC service server is already regrouped by other group regrouping procedures.
In this procedure, any gateway MC servers in the primary or partner MC systems are not shown.
Pre-conditions:
- MC service client 1 is authorized to initiated a preconfigured regroup procedure, and is receiving MC service in the primary MC system of MC service client 1.
- In order to be aware whether the group is regrouped, the MC service server within the same MC system is subscribed to the group configuration in the GMS.
Figure 10.15.3.3.4-1: Regroup rejection using preconfigured group in multiple MC systems
1. The authorized user of MC service client 1 initiates the group regroup procedure, specifying the list of MC service groups to be regrouped including MC service group 1, the MC service group ID of the regroup group and the MC service group ID of the group from which configuration information for the regroup group is to be taken.
2. MC service client 1 sends the preconfigured regroup request to the MC service server.
3. The MC service server checks that MC service client 1 is authorized to initiate a preconfigured group regroup procedure, and resolves the group identities of the MC service groups requested in step 1. The MC service server also checks which group members are affiliated to the requested MC service groups that are homed in the primary MC system. The MC service server identifies any partner systems which are the group home systems for MC service groups identified in the list of groups to be regrouped. The MC service server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MC service server. The MC service server also checks that none of the MC service groups that are homed in the primary MC system and that are requested for regrouping are already regrouped by any mechanism.
NOTE 1: This procedure does not require that that the authorized user of MC service client 1 is a group member of the MC service groups listed in the regroup request, or that the authorized user of MC service client 1 is an affiliated group member of any of the listed MC service groups.
4. The MC service server sends the preconfigured regroup requests to the MC service server in the partner MC system.
5. The partner MC service server checks the status of any MC service groups hosted by that partner MC service server, and determines that one or more requested MC service groups has already been regrouped by another group regrouping procedure.
6. The partner MC service server sends a preconfigured regroup reject to the primary MC service server, indicating the reason for rejection.
7. The primary MC service server sends a preconfigured regroup reject to MC service client 1, indicating the reason for rejection.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.4 Other preconfigured regroup procedures
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.