hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.4.1 Adding newly affiliated user to preconfigured group regroup
|
Figure 10.15.3.4.1-1 illustrates the procedure to add a newly affiliated user to an in-progress preconfigured MC service group regroup operation.
Pre-conditions:
- The MC service client is a member of a MC service group that is part of an in-progress preconfigured group regroup operation.
- The MC service group identity and group configuration for the preconfigured MC service group has been preconfigured in the MC service client, and the MC service client has received the relevant security related information to allow it to communicate in the MC service regroup group.
Figure 10.15.3.4.1-1: Procedure to add a newly affiliated user to a preconfigured group regroup
1. The MC service client affiliates to an MC service group that is currently part of an in-progress preconfigured group regroup. The affiliation follows the procedure in section 10.8.3.1 of this specification.
2. The MC service server retrieves 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.
3. The MC service server sends the preconfigured regroup request to the MC service client.
4. The MC service client notifies the user of the regrouping.
5. The MC service client 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.
6. The MC service server affiliates the regrouped MC service client to the regroup group.
Editor's note: It is FFS whether this procedure can be generalized to apply to both preconfigured and GMS-based group regrouping.
Editor's note: Affiliations of the MC service client to the regroup group in the MC service server and coordination to the MC System is FFS.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.4.2 Updating the MC service ID list in a preconfigured regroup group based on user regroup
|
Figure 10.15.3.4.2-1 illustrates the procedure to add or remove an MC service user based on the MC service user criteria known at the MC service server.
NOTE 1: This procedure applies to MC service users that have been added and are to be added to the preconfigured regroup group based on MC service user criteria known at the MC service server. If only the criteria are to be applied, then only the criteria are included in the request and the group and user lists are not included
Preconditions:
- A preconfigured regroup group has been established.
- The MC service server has selected MC service user 2 to participate in the preconfigured regroup group based on MC service user criteria known at the MC service server.
NOTE 2: Other participants of the preconfigured regroup group are not shown in figure 10.15.3.4.x-1 for simplicity.
Figure 10.15.3.4.2-1: Procedure to update the MC service ID list
1. The MC service server detects that MC service client 2, which has been earlier included in the preconfigured regroup group, no longer meets the MC service user criteria known at the MC service server.
2. The MC service sends MC service client 2 a preconfigured user regroup remove request.
3. The MC service client 2 notifies the MC service user of the preconfigured user regroup removal.
4. The MC service client 2 may send the MC service server a preconfigured user regroup remove response to acknowledge the preconfigured user regroup removal.
5. The MC service server updates the preconfigured regroup group (including the MC service user ID list) and potential group communication.
6. The MC service server detects that the MC service client 3 meets the MC service user criteria.
7. The MC service server sends the MC service client 3 a preconfigured regroup request.
8. The MC service client 3 notifies the MC service user of the preconfigured regroup request.
9. The MC service client 3 may send the MC service server a preconfigured regroup response.
10. The MC service server updates the preconfigured regroup group (including the MC service user ID list), and potential group communication.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.4.3 Adding a user to regroup group due to communication request to the group being regrouped
|
Figure 10.15.3.4.3-1 illustrates the procedure of adding a user to regroup group due to the user initiating a comunication request to the group involved in an in-progress preconfigured MC service group regroup.
Pre-conditions:
- The MC service client is an affiliated member of MC service group A that is part of an in-progress preconfigured group regroup with MC service groups B and C.
- MC servicec group D is being used as the regroup group.
- The MC service client has missed the preconfigured regroup request message (e.g. poor signalling conditions, race condition).
Figure 10.15.3.4.3-1: Procedure for communication request on MC service group during an in-progress group regroup
1. The MC service client attempts to start a communication on MC service group A. The MC service server identifies that the MC service group A is currently part of an in-progress preconfigured group regroup. In this case, the MC service server rejects the communication. The procedure of signalling interactions between the MC service client and the MC service server for MCPTT, MCVideo and MCdata is specified in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12], 3GPP TS 23.282 [13] accordingly.
2. The MC service server sends the preconfigured regroup request to the MC service client containing the MC service group ID of the preconfigured group, and the MC service group ID of the regroup group.
NOTE 1: This message should be sent over unicast.
3. The MC service client notifies the user of the regrouping procedure.
4. The MC service client sends the preconfigured regroup response to the MC service server to acknowledge the regrouping action.
5. The MC service server affiliates the regrouped MC service client into the regroup group.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.15.3.4.4 Regroup group cancel notification due to communication request to the cancelled regroup group
|
Figure 10.15.3.4.4-1 illustrates the procedure of notifying about the cancellation of the regroup group when a user initiates a communication to a regroup group after the MC service group regroup has been cancelled.
Pre-conditions:
- The MC service client is a member of MC service group A that was part of an in-progress preconfigured group regroup with MC service groups B and C that has been cancelled. MC service group D was used as the MC service regroup group.
- The MC service client has missed the preconfigured regroup cancel request message (e.g. poor signalling conditions, race condition).
Figure 10.15.3.4.4-1: Procedure for communication request to regroup group after the regrouping cancellation
1. The MC service client attempts to start a communication on MC service group D, which is the regroup group. The MC servce server identifies regroup group is no longer active or exist.
NOTE 1: The regroup group D can be a group in the MC service client's profile, and the MC service client can be a member of regroup group D.
2. The MC service server may send the preconfigured regroup cancel request to the MC service client.
NOTE 2: This message should be sent over unicast.
3. The MC service client may notify the user of the regrouping cancellation.
4. The MC service client may send the preconfigured regroup cancel response to the MC service server to acknowledge the regrouping cancellation.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16 Generic procedures for migration
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.1 General
|
Migration provides a means for an MC service user to obtain MC service directly from a partner MC system. This subclause describes generic procedures for migration which are variations of specific procedures detailed in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] and 3GPP TS 23.282 [13]. These procedures should be read in conjunction with specific procedures in those specifications.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.2 Migration during an ongoing group communication
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.2.1 General
|
This provides the capability for an MC service user to migrate to another MC system during an ongoing group communication and to continue the group communication in the other MC system.
Editor's note: Further study is needed for MCData services.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.2.2 Procedure
|
The procedure is based on the following existing procedures:
- MC service group de-affiliation procedure as described in clause 10.8.4.2, or
- De-affiliation from MC service group(s) defined in partner MC service system as described in clause 10.8.4.3.
- MC service user receiving MC service from a partner MC system as described in clause 10.1.4.3.2.
- MC service group affiliation procedure as described in clause 10.8.3.1, or
- Affiliation to MC service group(s) defined in partner MC system as described in clause 10.8.3.2 or clause 10.8.3.2a.
- Late entry MCPTT group call as described in 3GPP TS 23.379 [16] clause 10.6.2.3.1.1.4 (pre-arranged group call) and 3GPP TS 23.379 [16] clause 10.6.2.3.1.2.5 (chat group call).
- Late entry MCVideo group call as described in 3GPP TS 23.281 [12] clause 7.1.2.3.1.1.4 (pre-arranged) and 3GPP TS 23.281 [12] clause 7.1.2.3.1.2.6 (chat group call).
Pre-conditions:
1. The MC service client is a receiving party in one or more ongoing group calls in the primary MC system.
2. The MC service UE detects the need to change the MC system.
Figure 10.16.2.2-1: Migration to partner MC system during an ongoing group call
1. The MC service client requests de-affiliation from MC service groups. The MC service groups are either defined in the primary MC system (see clause 10.8.4.2) or the partner MC system (see clause 10.8.4.3).
2. After migration to the partner MC system, the configuration management client triggers retrieval of the MC service user profile used within the partner MC system (see clause 10.1.4.3.2).
NOTE: User authentication and service authorisation procedures are not shown.
3. The MC service client requests affiliation to MC service groups. The MCPTT groups are either defined in the primary MC system (see clause 10.8.3.1) or the partner MC system (see clause 10.8.3.2 or clause 10.8.3.2a).
4. If any of the received group calls are ongoing in the partner MC system, the partner MC system shall initiate a late-entry procedure towards the MC service client. If any of the received group calls are taken place in the primary MC system but not yet in the partner MC system, the affiliation by the migrated MC service UE triggers the late-entry procedure which then includes the MC service UE and the partner MC system into the group call.
The MC service client may indicate the successful migration of group communications to the MC service user.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.2.3 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.2.3.1 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.3 Private call using functional alias towards a partner MC system
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.3.1 General
|
This provides the possibility for an MC service user to initiate a private MC service call using a functional alias, defined in the partner MC system, as target address towards an MC service user in a partner MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.3.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.3.2.1 MC service functional alias resolution request
|
Table 10.16.3.2.1-1 describes the information flow MC service functional alias resolution request from the MC service server to the MC service functional alias controlling server and from the MC service functional alias controlling server to another MC service functional alias controlling server.
Table 10.16.3.2.1-1: MC service functional alias resolution request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the calling party
Functional alias
O
The functional alias of the calling party
Functional alias
M
The functional alias of the called party
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.3.2.2 MC service functional alias resolution response
|
Table 10.16.3.2.2-1 describes the information flow MC service functional alias resolution response from the MC service functional alias controlling server to another MC service functional alias controlling server, the MC service functional alias controlling server to the MC service server and the MC service server to the MC service client.
Table 10.16.3.2.2-1: MC service functional alias resolution response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the calling party
MC service ID
M
The corresponding MC service ID of the called functional alias. Return "NONE" if no one activates the targeted Functional Alias.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.3.3 Procedure
|
Figure 10.16.3.3-1 represents a generic MC service private call setup procedure to allow using the functional alias as called party address, i.e., the MC service ID address is resolved by the partner MC system through the primary MC service server and primary MC service functional alias controlling server.
Additional new pre-condition:
1. A secured connection has been established between the MC service functional alias controlling servers in different MC systems.
Figure 10.16.3.3-1: Private call setup in automatic commencement mode, users in multiple MC systems
1-2. Same as in 3GPP TS 23.379 [16] clause 10.7.2.2.3.1, 3GPP TS 23.281 [12] clause 7.2.2.3.1 or corresponding procedures in 3GPP TS 23.282 [13], but MC service private call request contains a functional alias of invited user.
3. If the MC service private call request contains a functional alias instead of an MC service ID as called party, the MC service server checks whether MC service client 1 can use the functional alias to setup a private call. If authorized, the MC service server 1 resolves the functional alias to the corresponding MC service ID for which the functional alias is active by using subsequent steps 4-7.
4. The MC service server 1 sends an MC service functional alias resolution request message to the MC service functional alias controlling server 1 to resolve the functional alias of the called party.
5. The MC service functional alias controlling server 1 determines that the functional alias belongs to the partner MC system and forwards the MC service functional alias resolution request message to MC service functional alias controlling server 2.
6. The MC service functional alias controlling server 2 resolves the functional alias and determines the corresponding MC service ID to terminate the call and returns it to the MC service functional alias controlling server 1 in the MC service functional alias resolution response message.
NOTE: Depending on implementation the MC service server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MC service ID(s) (e.g., whether the MC service ID is within the allowed area of the functional alias). If the MC service server detects that the functional alias used as the target of the private call request is simultaneously active for multiple MC service users, then the MC service server can proceed by selecting an appropriate MC service ID based on some selection criteria. The selection of an appropriate MC service ID is left to implementation. This selection criteria can include rejection of the call, if no suitable MC service ID is selected.
7. The MC service functional alias controlling server 1 returns the corresponding MC service ID to MC service server 1 in the MC service functional alias resolution response message. The MC service server 1 checks if MC service user at MC service client 1 is authorized to initiate the private call to the MC service user at MC service client 2. If not authorized stop the procedure, otherwise continue with step 8.
8. The MC service server 1 responds with a MC service functional alias resolution response message that contains the resolved MC service ID back to MC service client 1.
9. The MC service client 1 sends a new MC service private call request towards the resolved MC service ID according 3GPP TS 23.379 [16] clause 10.7.2.2.3.1, 3GPP TS 23.281 [12] clause 7.2.2.3.1 or corresponding procedures in 3GPP TS 23.282 [13].
10-14. Same as in 3GPP TS 23.379 [16] clause 10.7.2.2.3.1, 3GPP TS 23.281 [12] clause 7.2.2.3.1 or 3GPP TS 23.282 [13] clause 7.14.2.2.
15. The receiving MC service client 2 accepts the private call automatically, and an acknowledgement is sent to the MC service server 2.
16. The MC service server 2 forwards the MC service private call response message to MC service server 1.
17-18. Same as in 3GPP TS 23.379 [16] clause 10.7.2.2.3.1, 3GPP TS 23.281 [12] clause 7.2.2.3.1 or corresponding procedures in 3GPP TS 23.282 [13].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.4 Migration during an onging private communication
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.4.1 General
|
This subclause provides a generic guidance on the behaviour an MC service client follows to perform migration during an ongoing private communication, e.g., MCPTT private call. Once the MC service client detects the need to migrate during an ongoing private communication, it may initiate preparations and UE configuration which facilitate migration as mentioned in clause 10.1.1.2. The described procedure is applicable to the scenarios whether an MC service client is migrating into its primary MC system or a partner MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.4.2 Procedure
|
Figure 10.16.4.2-1 represents a generic procedure to be followed when migration is needed to be done during an ongoing private communication, such as MCPTT private call, or MCVideo private call.
Figure 10.16.4.2-1: Migration during ongoing private communication.
1. A private call takes place between MC service client 1 and MC service client 2, where the former is connected to MC system A and the latter to MC system B.
2. The MC service client 1 detects the need to migration into MC system C and MC service server 1 is notified to be prepared for possible service interruption. Furthermore, upon detection, MC service client 1 performs initial steps to be considered prior migration, e.g., UE configuration, authorization, and selection of user profile that permits migration, as described in clause 10.1.1.2
3. MC service client 1 releases the private communication towards the MC service client 2 as described in clause 10.7.2.2.3.1 of 3GPP TS 23.379 [16] for MCPTT private call, or in clause 7.2.2.3.3.1 of 3GPP TS 23.281 [12] for MCVideo private call. A call release reason IE "release due to migration" may be included so that MC service client 2 is informed.
4. Migration takes place and MC system C retrieves MC service client 1 profile:
4a. if MC system C is the primary MC system, retrieval of MC service client 1 profile takes place according to clause 10.1.4.3.1.
4b. if MC system C is a partner MC system, retrieval of MC service client 1 profile takes place according to clause 10.1.4.3.2.
5. Registration according to procedure in clause 10.6.1 takes place.
6. MC service client 1 initiates a new private communication toward MC service client 2 as described in clause 10.7.2.2.1 of 3GPP TS 23.379 [16] for MCPTT private call, or in clause 7.2.2.3.1 of 3GPP TS 23.281 [12] for MCVideo private call.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.5 Generic private call procedure towards a migrated MC service user
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.5.1 General
|
This subclause describes a generic private communication procedure towards a migrated MC service user at a partner MC system. This generic private communication can be an MCPTT private call, an MCVideo private call, or a one-to-one MCData communication. For the generic private call, this procedure is used in conjunction with the corresponding MCPTT, MCVideo and MCData procedures described in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12], or 3GPP TS 23.282 [13], respectively.
Once an MC service user is migrated, he or she will be assigned a new MC service ID by the migrated MC system and this MC service ID will be used for all his/her communications. When another MC service user communicates with the migrated MC service user using the newly assigned MC service ID, the private call request described in clause 10.7.2.1.1 in 3GPP TS 23.379 [16], in clause 7.2.2.2.1 in 3GPP TS.23.281 [12], or the corresponding procedures in 3GPP TS 23.282 [13] applies.
For callers that are not aware of the migrated MC service user`s new MC service ID, the migrated MC service user is also reachable by his/her MC service ID assigned by the primary MC system via redirection done by the primary MC system`s MC service server described in this procedure.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.5.2 Private call redirection
|
Table 10.16.5.2-1 describes the information flow of a private call redirection, which is sent from the MC service server to an MC service client initiating a private call towards a migrated MC service user.
Table 10.16.5.2-1: Private call redirection
Information element
Status
Description
MC service ID
M
The MC service ID of the MC service user initiating a private call, i.e., calling party. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
MC service ID
M
The MC service ID of the target MC service user (i.e., called party), which the MC service user has obtained from its primary MC system before migration. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
MC service ID
M
The MC service ID of the target MC service user, which the MC service user has obtained from its migrated MC system after Migration. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
KMS URI (NOTE)
O
The KMS URI associated with the MC service ID of the migrated MC service user.
Redirection reason
O
The MC service server informs the calling party that the target MC service user has migrated.
NOTE: If the KMS URI is not configured in the MC service user profile and is not included in the private call redirection message, then the MC service client shall obtain KMS URI using the KMS lookup procedure defined in 3GPP TS 33.180 [19].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.5.3 Procedure
|
Figure 10.16.5.4-1 presents a generic private communication procedure from MC service user 1 towards a migrated MC service user 2 where the MC system A is the primary MC system of MC service user 2 before migration, and the MC system B is the MC system that the MC service user 2 has migrated
Pre-conditions:
- MC system A and MC system B are interconnected.
- MC system A is the primary MC system of MC service user 2 before migration. MC system B is the MC system that MC service user 2 has migrated.
- The MC service server A is aware that MC service user 2 has migrated and is informed of its MC service ID provided by MC system B, as described in clause 10.6.3.3.
Figure 10.16.5.3-1: MC private call towards a migrated MC service user.
1. The MC service client 1 initiates a private call request towards MC service user 2 (MC service client 2) who has migrated to MC system B. The private call request includes among others the MC service ID of MC service user 2, which is provided by its primary MC system, as the target, i.e., called party. The private call request is described in clause 10.7.2.1.1 in 3GPP TS 23.379 [16], in clause 7.2.2.2.1 in 3GPP TS 23.281 [12], or the corresponding procedures in 3GPP TS 23.282 [13].
If the private call request contains a functional alias instead of an MC service ID as the target party, the MC service server A checks whether the MC service user 1 at the MC service client 1 is allowed to use functional alias during private call setup.
2. MC service server A checks that MC service user 2 has migrated to MC system B with a new MC service ID assigned by MC system B.
If the private call request contains a functional alias, and if the MC service user 1 at the MC service client 1 is authorized, the MC service server A resolves the functional alias to a corresponding MC service ID of the MC service user which has activated the functional alias. If the MC service server A determines that the corresponding MC service user of the resolved MC service ID is migrated, i.e., MC service user 2 at MC service client 2 is migrated, it checks whether the resolved MC service ID of the MC service user 2 is allowed to receive a private call from the MC service ID of the MC service user 1 using functional alias based on entries in the user profile of the MC service user 2 assigned by the primary system.
3. The MC service server A sends a private call redirection towards the MC service client 1, to inform MC service user 1 that the target MC service user, i.e., MC service user 2 has migrated and its new MC service ID of MC service user 2 assigned by the migrated MC system. The MC service client 1 releases the private call request at step 1.
4. The MC service client 1 initiates a private call towards MC service user 2, including the MC service ID of MC service user 2 obtained from MC system. The initiated private call can either be an MCPTT private call, an MCVideo private call, or a corresponding one-to-one MCData communication, and shall perform the procedures as described in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12], or 3GPP TS 23.282 [13], respectively.
NOTE: If end-to-end encryption is required, the migrated MC service user 2 is assumed to have the necessary security information needed to establish a protected call, as defined in 3GPP TS 33.180 [25].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.6 Ad hoc group call procedure towards a migrated MC service user
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.6.1 General
|
The following clauses specify the generic procedure for ad hoc group call towards a migrated MC service user that is utilised by all the MC services (i.e. MCPTT, MCVideo and MCData) in conjunction with the procedures as specified in the respective MC services in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12], and 3GPP TS 23.282 [13].
The ad hoc group calls can be initiated by using the participant list provided by an initiator of the call and the ad hoc group call will be hosted in the primary MC system of the initiator of the ad hoc group call. If one of the requested participant is migrated to a partner MC system then the call should be delivered to the partner MC system to which MC service user has migrated. The primary MC system of the migrated MC service user assists in redirecting the call to the partner MC system using partner MC system assigned MC service ID. The initiator of the call is not aware of the migration information of the requested participants, uses an MC service ID assigned by primary MC system of the migrated MC service user. The MC service server of the both primary and partner MC systems are involved in call redirection to deliver a call appropriately into the MC system.
If one of the requested participant is from an interconnected MC system and has migrated to another partner system, then the call should be delivered to the partner MC system to which participant is migrated. The primary MC system of the migrated MC service user assists in redirecting the ad hoc group call setup request by providing the another partner MC system the assigned MC service ID to the MC system where this ad hoc group call is hosted (focus MC service server of the caller's primary MC system). The primary MC system of the migrated MC service user receives the ad hoc group call setup request using the primary MC system assigned MC service ID when an initiator of the call not aware of the migration of the MC service user. The ad hoc group call hosting MC service server of the MC system further delivers the call to the migrated MC service user using another partner MC system assigned MC service ID.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.6.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.6.2.1 Ad hoc group call redirection notify
|
Table 10.16.6.2.1-1 describes the information flow of an ad hoc group call redirection notify, which is sent from the MC service server to MC service server and MC service server to an MC service client initiating an ad hoc group call towards a migrated MC service user.
Table 10.16.6.2-1: Ad hoc group call redirection notify
Information element
Status
Description
MC service ID
M
The MC service ID of the MC service user initiating an ad hoc group call, i.e., calling party. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
MC service ID
M
The MC service ID of the target MC service user (i.e., called party), which the MC service user has obtained from its primary MC system before migration. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
MC service ID
M
The MC service ID of the target MC service user, which the MC service user has obtained from its migrated MC system after Migration. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
Redirection reason
O
The called MC service user has migrated.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.6.3 Procedure
|
Figure 10.16.6.3-1 presents a generic ad hoc group call procedure for the MC service user 1 using MC service client 1 towards a MC service user 2 using MC service client 2, a migrated MC service user 3 using MC service client 3 and a migrated MC service user 4 using MC service client 4, where the MC system A is the primary MC system of MC service user 3 before migration, MC system B is the primary MC system of MC service user 4 before migration, the MC system B is the MC system that the MC service user 3 has migrated and the MC system C is the MC system that the MC service user 4 has migrated.
The procedure is based on the following existing procedures:
- The ad hoc group call setup procedures as described in clause 10.19.3.2.1 of 3GPP TS 23.379 [16], in clause 7.19.3.2.1 of 3GPP TS 23.281 [12], or in clause 7.17.3.2.1 of 3GPP TS 23.282 [13].
Pre-conditions:
- The MC system A, MC system B and MC system C are interconnected MC systems.
- The MC system A is the primary MC system of MC service user 1, MC service user 2 and the MC service user 3 The MC system B is the MC system that MC service user 3 has migrated.
- The MC system B is the primary MC system of MC service user 4. The MC system C is the MC system that MC service user 4 has migrated.
- The MC service server A is aware that MC service user 3 has migrated and is informed of its MC service ID provided by MC system B, as described in clause 10.6.3.3.
- The MC service server B is aware that MC service user 4 has migrated and is informed of its MC service ID provided by MC system C, as described in clause 10.6.3.3.
- The authorized MC service user 1 at MC service client 1 wants to invite MC service users at MC service client 2, MC service client 3 and MC service client 4 for the ad hoc group call.
- The ad hoc group call is hosted in the MC service server A of the MC system A.
Figure 10.16.6.3-1: Ad hoc group call towards migrated MC service users.
1. The MC service user 1 (at MC service client 1) initiates an ad hoc group call request towards MC service user 2 (at MC service client 2), MC service user 3 (at MC service client 3) who has migrated to MC system B, and MC service user 4 (at MC service client 4) who has migrated to MC system C. The initiator of the ad hoc group call includes the MC service ID of MC service users in an ad hoc group call request, which are obtained from their primary MC system.
2. The MC service server A of the MC system A invites the MC service client 2 to ad hoc group call and successfully establishes the ad hoc group call with the MC service client 2.
3. The MC service server A determine that MC service user 3 which has to be invited for ad hoc group call is migrated to MC system B with a new MC service ID assigned by MC system B.
4. The MC service server A may inform the MC service client 1 that ad hoc group call request towards MC service user 3 is redirected to MC system B (migrated MC system) by sending ad hoc group call redirection notify. The ad hoc group call redirection notify contains the information about MC service ID of the target MC service user 3 assigned by both MC system A and MC system B, and reason for the call redirection as user migration.
5. The MC service server A of the MC system A invites the MC service client 3 to ad hoc group call using MC service ID assigned by the MC system B and successfully establishes the ad hoc group call with the MC service client 3.
6. The MC service server A of the MC system A further initiates an ad hoc group call request towards the MC service client 4 of the MC system B. The ad hoc group call request is routed to the MC service client 4 via the MC service server B of the MC system B.
7. The MC service server B of the MC system B determine that MC service user 3 has to be invited for ad hoc group call is migrated to MC system C with a new MC service ID assigned by MC system C.
8. The MC service server B inform the MC service server A that initiation of ad hoc group call towards the MC service user 4 has migrated and assigned with a new MC service ID by MC system C (migrated MC system) by sending ad hoc group call redirection notify. The ad hoc group call redirection notify contains the information about MC service ID of the target MC service user 4 assigned by both MC system B and MC system C, and reason for the call redirection notify as user migration.
9. The MC service server A may inform the MC service client 1 that ad hoc group call request towards MC service user 4 is redirected to MC system C (migrated MC system) by sending ad hoc group call redirection notify. The ad hoc group call redirection notify contains the information about MC service ID of the target MC service user 4 assigned by both MC system B and MC system C, and reason for the call redirection as user migration.
10. The MC service server A of the MC system A invites the MC service client 4 to ad hoc group call using MC service ID assigned by the MC system C and successfully establishes the ad hoc group call with the MC service client 4.
11. The MC service server A of the MC system A provides an ad hoc group call response to the MC service client 1 upon receiving response to the corresponding ad hoc group call request in step 1. The ad hoc group call response will consist of the success or failure result and/or detailed reason information in case of failure.
12. Upon successful of an ad hoc group call setup, call is established amongst the multiple group members from MC system A, MC system B and MC system C. The media plane and floor control resources are established.
NOTE 1: The migrated MC system can choose to reject the ad hoc group call request originated towards the migrated MC service user based on the local policy.
NOTE 2: When an MC service user is added to the ad hoc group call, the authorized users (not shown in figure), who are configured to receive the participant's information of an ad hoc group call, are notified that the MC service user joined the ad hoc group call.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.7 Migration during Ad hoc group call procedure
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.7.1 General
|
The following clauses specify the generic procedure for MC service user to continue to participate in ad hoc group call when migrated to partner system that is utilised by all the MC services (i.e. MCPTT, MCVideo and MCData) in conjunction with the procedures as specified in the respective MC services in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12], and 3GPP TS 23.282 [13].
The ad hoc group call can be initiated by using the participant list or criteria (along with criteria or local policies at MC service server) provided by an initiator of the call and the ad hoc group call will be hosted in the primary MC system of the initiator of the ad hoc group call. During ongoing call, the participating MC service user can migrate to partner MC system. While migrating to partner MC system, the MC service user will leave the ongoing ad hoc group call by providing the reason for leaving the ad hoc group call is due to migration. After succesful migration, the MC service user will be invited again to continue the participation in an ongoing ad hoc group call. If the ad hoc group call is established using the participant list provided by the initiator of the call, then the MC service server where the ad hoc group call is hosted will invite the migrated MC service user using partner MC system assigned MC service ID. If the ad hoc group call is established using the criteria provided by the initiator of the call, then the MC service server where the ad hoc group call is hosted will invite the migrated MC service user using partner MC system assigned MC service ID only when it is informed about the migrated MC service user meeting the criteria and to be invited for ongoing ad hoc group call by partner MC system (migrated MC system).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.7.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.7.2.1 Ad hoc group call redirection notify
|
Table 10.16.7.2.1-1 describes the information flow of an ad hoc group call redirection notify, which is sent from the MC service server to MC service server and MC service server to an MC service client initiating an ad hoc group call towards a migrated MC service user.
Table 10.16.7.2.1-1: Ad hoc group call redirection notify
Information element
Status
Description
MC service ID
M
The MC service ID of the MC service user initiating an ad hoc group call, i.e., calling party. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
MC service ID
M
The MC service ID of the target MC service user (i.e., called party), which the MC service user has obtained from its primary MC system before migration. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
MC service ID
M
The MC service ID of the target MC service user, which the MC service user has obtained from its migrated MC system after Migration. The MC service ID can either be MCPTT ID, MCVideo ID, or MCData ID.
Redirection reason
O
The called MC service user has migrated.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.7.3 Procedure for participants list provided by the Initiator
|
Figure 10.16.7.3-1 presents a generic ad hoc group call procedure in which MC service user 3 using MC service client 3 and MC service user 4 using MC service client 4 migrates during the call, where the MC system A is the primary MC system of MC service user 3 before migration, MC system B is the primary MC system of MC service user 4 before migration, the MC system B is the MC system that the MC service user 3 has migrated and the MC system C is the MC system that the MC service user 4 has migrated. After the migration, the migrated MC service user 3 and MC service user 4 are re-invited to ongoing ad hoc group call and successfully added to the call.
The procedure is based on the following existing procedures:
- The ad hoc group call setup procedures as described in clause 10.19.3.2.1 of 3GPP TS 23.379 [16], in clause 7.19.3.2.4 of 3GPP TS 23.281 [12], or in clause 7.17.3.2.1 of 3GPP TS 23.282 [13].
- The migration of the MC service user to the partner MC system procedures as described in clause 10.6.3.
- The inviting a MC service user and adding to the ongoing ad hoc group call procedures steps (see steps 6 and 7) are as described in clause 10.19.3.2.1 of 3GPP TS 23.379 [16], in clause 7.19.3.2.4 of 3GPP TS 23.281 [12], or in clause 7.17.3.2.1 of 3GPP TS 23.282 [13].
Pre-conditions:
- The MC system A, MC system B and MC system C are interconnected MC systems.
- The MC system A is the primary MC system of MC service user 1, MC service user 2 and the MC service user 3. The MC system B is the MC system that MC service user 3 has migrated.
- The MC system B is the primary MC system of MC service user 4. The MC system C is the MC system that MC service user 4 has migrated.
- An ad hoc group call is ongoing among the MC service users at MC service client 1 (initiator), MC service client 2, MC service client 3 and MC service client 4 using the MC service ID which are obtained from their primary MC system, and the participants list provided by the originating MC service user while initiating the ad hoc group call.
- The ad hoc group call is hosted in the MC service server A of the MC system A.
Figure 10.16.7.3-1: Migration during ongoing ad hoc group call based on participants list.
1. The MC service client 3 determines the need to migrate to the MC system B and MC service user 3 is notified to be prepared for possible service interruption.
2a-2b. The MC service client 3 leaves the ad hoc group call by sending ad hoc group call leave request towards the MC service server A containing the ad hoc group ID and reason for the leaving the call as user migration.
3. The ongoing ad hoc group call is updated by removing MC service client 3 and call continues with remaining MC service clients.
4. The MC service client 3 migrates to the MC system B as described in the clause 10.6.3 and new MC service ID is assigned by the MC system B. The MC service server A of the MC system A, which is the primary MC system of the migrated MC service user 3, is informed about migrated MC service user's MC service ID obtained from the MC system B (i.e. a migrated MC system) along with successful MC service authorization at the MC system B.
4a. The MC service server A may inform the MC service client 1 that ad hoc group call request towards MC service user 3 is redirected to MC system B (migrated MC system) by sending ad hoc group call redirection notify. The ad hoc group call redirection notify contains the information about MC service ID of the target MC service user 3 assigned by both MC system A and MC system B, and reason for the call redirection as user migration.
5. The MC service server A of the MC system A determines that MC service user 3 has to be re-invited for ongoing ad hoc group call. The MC service server A of the MC system A invites the MC service client 3 to ad hoc group call using MC service ID assigned by the MC system B and successfully establishes the ad hoc group call with the MC service client 3.
NOTE 1: How the MC service server determining to re-invite the migrated MC service user is left to the implementation (e.g. timer, policy, on migration completion with periodically querying for the migration status information etc.).
6. The MC service client 4 determines the need to migrate to the MC system C and MC service user 4 is notified to be prepared for possible service interruption.
7a-7b. The MC service client 4 leaves the ad hoc group call by sending ad hoc group call leave request towards the MC service server A containing the ad hoc group ID and reason for the leaving the call as user migration.
8. The ongoing ad hoc group call is updated by removing MC service client 4 and call continues with remaining MC service clients.
9. The MC service client 4 migrates to the MC system C as described in the clause 10.6.3 and new MC service ID is assigned by the MC system C. The MC service server B of the MC system B, which is the primary MC system of the migrated MC service user 4, is informed about migrated MC service user's MC service ID obtained from the MC system C (i.e. a migrated MC system) along with successful MC service authorization at the MC system C.
10. The MC service server A of the MC system A determines that MC service user 4 has to be re-invited for ongoing ad hoc group call. The MC service server A of the MC system A initiates an ad hoc group call request towards the MC service client 4 of the MC system B (i.e. interconnected MC system) using MC service ID assigned by the MC system B (i.e. primary MC system). The ad hoc group call request is routed to the MC service client 4 via the MC service server B of the MC system B.
NOTE 2: How the MC service server determining to re-invite the migrated MC service user is left to the implementation (e.g. timer, policy etc).
11. The MC service server B of the MC system B determines that MC service user 4 has to be invited for ad hoc group call is migrated to MC system C with a new MC service ID assigned by MC system C.
12. The MC service server B inform the MC service server A that initiation of ad hoc group call towards the MC service user 4 has migrated and assigned with a new MC service ID by MC system C (migrated MC system) by sending ad hoc group call redirection notify. The ad hoc group call redirection notify contains the information about MC service ID of the target MC service user 4 assigned by both MC system B and MC system C, and reason for the call redirection notify as user migration.
13. The MC service server A may inform the MC service client 1 that ad hoc group call request towards MC service user 4 is redirected to MC system C (migrated MC system) by sending ad hoc group call redirection notify. The ad hoc group call redirection notify contains the information about MC service ID of the target MC service user 4 assigned by both MC system B and MC system C, and reason for the call redirection as user migration.
14. The MC service server A of the MC system A invites the MC service client 4 to ad hoc group call using MC service ID assigned by the MC system C and successfully establishes the ad hoc group call with the MC service client 4.
NOTE 3: The migrated MC system can choose to reject the ad hoc group call request originated towards the migrated MC service user based on the local policy.
NOTE 4: When an MC service user is added to the ad hoc group call, the authorized users (not shown in figure), who are configured to receive the participant's information of an ad hoc group call, are notified that the MC service user joined the ad hoc group call.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.16.7.4 Procedure for criteria provided by the Initiator
|
Figure 10.16.7.4-1 presents a generic ad hoc group call procedure in which MC service user 3 using MC service client 3 and MC service user 4 using MC service client 4 migrates during the call, where the MC system A is the primary MC system of MC service user 3 before migration, MC system B is the primary MC system of MC service user 4 before migration, the MC system B is the MC system that the MC service user 3 has migrated and the MC system C is the MC system that the MC service user 4 has migrated. After the migration, the migrated MC service user 3 and MC service user 4 are re-invited to ongoing ad hoc group call based on the criteria in the migrated MC system and successfully added to the call.
The procedure is based on the following existing procedures:
- The ad hoc group call setup procedures as described in clause 10.19.3.2.3 of 3GPP TS 23.379 [16], in clause 7.19.3.2.1 of 3GPP TS 23.281 [12], or in clause 7.17.3.2.3 of 3GPP TS 23.282 [13].
- The migration of the MC service user to the partner MC system procedures as described in clause 10.6.3.
- Inviting a MC service user meeting the criteria to the ongoing ad hoc group call procedure steps are as described in clause 10.19.3.2.4 of 3GPP TS 23.379 [16], in clause 7.19.3.2.2 of 3GPP TS 23.281 [12], or in clause 7.17.3.2.4 of 3GPP TS 23.282 [13].
Pre-conditions:
- The MC system A, MC system B and MC system C are interconnected MC systems and the criteria is shared among these interconnected systems.
- The MC system A is the primary MC system of MC service user 1, MC service user 2 and the MC service user 3. The MC system B is the MC system that MC service user 3 has migrated.
- The MC system B is the primary MC system of MC service user 4. The MC system C is the MC system that MC service user 4 has migrated.
- An ad hoc group call is ongoing among the MC service users at MC service client 1 (initiator), MC service client 2, MC service client 3 and MC service client 4 using the MC service ID which are obtained from their primary MC system, and the participants list determined using criteria provided by the originating MC service user while initiating the ad hoc group call.
- The ad hoc group call is hosted in the MC service server A of the MC system A.
Figure 10.16.7.4-1: Migration during ongoing ad hoc group call based on criteria.
1. The MC service client 3 determines the need to migrate to the MC system B and MC service user 3 is notified to be prepared for possible service interruption.
2a-2b. The MC service client 3 leaves the ad hoc group call by sending ad hoc group call leave request towards the MC service server A containing the ad hoc group ID and reason for the leaving the call as user migration.
3. The ongoing ad hoc group call is updated by removing MC service client 3 and call continues with remaining MC service clients.
4. The MC service client 3 migrates to the MC system B as described in the clause 10.6.3 and new MC service ID is assigned by the MC system B. The MC service server A of the MC system A, which is the primary MC system of the migrated MC service user 3, is informed about migrated MC service user's MC service ID obtained from the MC system B (i.e. a migrated MC system) along with successful MC service authorization at the MC system B.
5. The MC service server B of the MC system B determines that newly migrated MC service user 3 meets the criteria and notify the MC service server A of the MC system A to add the MC service user 3 to an on-going ad hoc group call. The MC service server A of the MC system A invites the MC service client 3 to ad hoc group call using MC service ID assigned by the MC system B and successfully establishes the ad hoc group call with the MC service client 3.
6. The MC service client 4 determines the need to migrate to the MC system C and MC service user 4 is notified to be prepared for possible service interruption.
7a-7b. The MC service client 4 leaves the ad hoc group call by sending ad hoc group call leave request towards the MC service server A containing the ad hoc group ID and reason for the leaving the call as user migration.
8. The ongoing ad hoc group call is updated by removing MC service client 4 and call continues with remaining MC service clients.
9. The MC service client 4 migrates to the MC system C as described in the clause 10.6.3 and new MC service ID is assigned by the MC system C. The MC service server B of the MC system B, which is the primary MC system of the migrated MC service user 4, is informed about migrated MC service user's MC service ID obtained from the MC system C (i.e. a migrated MC system) along with successful MC service authorization at the MC system C.
10. The MC service server C of the MC system C determines that newly migrated MC service user 4 meets the criteria and notify the MC service server A of the MC system A to add the MC service user 4 to an on-going ad hoc group call. The MC service server A of the MC system A invites the MC service client 4 to ad hoc group call using MC service ID assigned by the MC system C and successfully establishes the ad hoc group call with the MC service client 4.
NOTE: When an MC service user is added to the ad hoc group call, the authorized users (not shown in figure), who are configured to receive the participant's information of ad hoc group call, are notified that the MC service user joined the ad hoc group call.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17 Sharing administrative configuration between interconnected MC systems
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.1 General
|
Cooperation between MC systems encompasses a number of cases of mutual operation between them, e.g:
- Provisioning connectivity information of partner MC system(s) for MC service UE migration as specified in subclause 10.1.6.
- Migration of MC service users from an MC system considered as primary or home MC system to a partner MC system as specified in subclause 10.6.3
- Migration during ongoing group or private call communication as specified in subclause 10.16.
- Generic procedures for interconnection as specified in clause 10.14.
- Shared MC service groups which can be configured as described in clause 10.2.7.
The above scenarios in many cases require configurations in both the primary MC system and the partner MC system as precondition.
Sharing administrative configuration between interconnected MC systems enables MC administrators and authorized MC service users of the primary MC system and the MC administrators and authorized MC service users of the partner MC system to negotiate and and apply configuration changes between interconnected MC systems, in order to fullfil preconditions for the cooperation between interconnected MC systems.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.1 ACM data notification
|
Table 10.17.2.1 describes the information flow of the ACM data notification from the ACM server to the ACM client.
Table 10.17.2.1-1: ACM data notification
Information element
Status
Description
MC service ID
M
The identity of the MC service user towards the pending ACM data notification is sent
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.2 Get ACM data request
|
Table 10.17.2.2-1 describes the information flow of Get ACM data request from an ACM client to the ACM server.
Table 10.17.2.2-1: Get ACM data request
Information element
Status
Description
MC service ID
M
The identity of the MC service user requesting for the download of the pending ACM data
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.3 Get ACM data response
|
Table 10.17.2.3-1 describes the information flow of Get ACM data response from an ACM server to the ACM client.
Table 10.17.2.3-1: Get ACM data response
Information Element
Status
Description
MC service ID
M
The identity of the MC service user requesting for the download of the pending ACM data
ACM Data
M
Contains all ACM requests which are pending for this user.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.4 Group membership update request
|
Table 10.17.2.4-1 describes the information flow group membership update request from ACM client to ACM server in the primary MC system, from ACM server of primary MC system to ACM server of partner MC system and from ACM server to ACM client in partner MC system.
Table 10.17.2.4-1: Group membership update request
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the primary MC system who requests the information update
Functional alias
O
The functional alias of the MC service user at the primary MC system who requests the information update
MC service ID
O (see NOTE)
The identity of the MC service user at the partner MC system towards the information update is sent
Functional alias
O (see NOTE)
The functional alias of the MC service user at the partner MC system towards the information update is sent
MC service group ID
M
Identity of the MC service group
MC service ID list
M
List of identities of the MC service users that are affected by this operation
Operation
M
Add to or delete from the group
Urgency
O
Indicates the level of operational urgency of the group membership update request
NOTE: Either the MC service ID or the functional alias must be present.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.5 Group membership update response
|
Table 10.17.2.5-1 describes the information flow group membership update response from ACM client to ACM server in partner MC system, from ACM server in partner MC system to ACM server in primary MC system and from ACM server to ACM client in primary MC system.
Table 10.17.2.5-1: Group membership update response
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the partner MC system which handled the group membership update
Functional alias
O
The functional alias of the MC service user at the partner MC system which handled the group membership update
MC service ID
M
The identity of the authorized user in the primary MC system which is target of the response.
MC service group ID
M
Identity of the MC service group
Result
M
Indicates the acceptance or rejection to perform the operation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.6 Process indication
|
Table 10.17.2.6-1 describes the information flow of Process indication from ACM server in partner MC system to ACM server in primary MC system and from ACM server to ACM client in primary MC system.
Table 10.17.2.6-1: Process indication
Information Element
Status
Description
MC service ID
M
The identity of the MC service user requesting for an ACM operation at partner MC system
Acknowledgement
M
ACM request has been received, stored and processing is in progress
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.7 Interconnection group identity provision request
|
Table 10.17.2.7-1 describes the information flow of the interconnection group identity provision request sent from ACM client to ACM server in the primary MC system, from ACM server of primary MC system to ACM server of partner MC system and from ACM server to ACM client in partner MC system.
Table 10.17.2.7-1: Interconnection group information provision request
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the primary MC system which triggers the interconnection group identity provision request.
Functional alias
O
The functional alias of the MC service user at the primary MC system which triggers the interconnection group identity provision request.
MC service ID
O (see NOTE)
The identity of the MC service user at the partner MC system towards which the interconnection group identity provision request is sent
Functional alias
O (see NOTE)
The functional alias of the MC service user at the partner MC system towards which the interconnection group identity provision request is sent
MC service group ID list
M
A list of one or more interconnection MC service group IDs
Group description per MC service group ID
O
A text description indicating the intended operational use for every interconnection MC service group ID in the list
NOTE: Either the MC service ID or the functional alias must be present.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.8 Interconnection group identity provision response
|
Table 10.17.2.8-1 describes the information flow of the interconnection group identity provision response sent from ACM client to ACM server in the partner MC system, from ACM server in partner MC system to ACM server in primary MC system and from ACM server to ACM client in primary MC system.
Table 10.17.2.8-1: Interconnection group identity provision response
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the partner MC system who generates the interconnection group identity provision response.
Functional alias
O
The functional alias of the MC service user at the partner MC system who generates the interconnection group identity provision response.
MC service ID
M
The identity of the authorized user in the primary MC system which is target of the response.
Provision status
M
Indicates the provisioning result
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.9 Add user configuration request
|
Table 10.17.2.9-1 describes the information flow of the add user configuration request sent from ACM client to ACM server in the primary MC system, from ACM server of primary MC system to ACM server of partner MC system and from ACM server to ACM client in partner MC system.
Table 10.17.2.9-1: Add user configuration request
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the primary MC system which sends the request.
Functional alias
O
The functional alias of the MC service user at the primary MC system which sends the request.
MC service ID
O
(see NOTE)
The identity of the MC service user at the partner MC system towards which the request is sent
Functional alias
O
(see NOTE)
The functional alias of the MC service user at the partner MC system towards which the request is sent
MC service ID list
M
Set of identities of the migrating MC service user(s).
Request category
O
A set of request notification identifiers, e.g. high, medium, low for alerting partner MC system of specific urgencies.
Request duration
O
A set of time and date information for each MC service user to inform the partner MC system when the user is expected to attain service at the partner MC system and for how long that MC service user is expected to receive service(s).
Additional Information
O
Additional set of MC service user or UE identification information, such as labels, hardware UE identifiers or other identifying information, which may include device descriptions and user capability information. This information is linked to a particular MC service user of the MC service ID list provided.
NOTE: Either the MC service ID or the functional alias must be present.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.10 Add user configuration response
|
Table 10.17.2.10-1 describes the information flow of the add user configuration response sent from ACM client to ACM server in the partner MC system, from ACM server in partner MC system to ACM server in primary MC system and from ACM server to ACM client in primary MC system.
Table 10.17.2.10-1: Add user configuration response
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the partner MC system which handled the received add user configuration request.
Functional alias
O
The functional alias of the MC service user at the partner MC system which handled the received add user configuration request.
MC service ID
M
The identity of the authorized user in the primary MC system which is target of the response.
MC service ID list
M
Set of MC service IDs used in the primary MC system of the migrating MC service user(s)
MC service ID list
M
(see NOTE)
Set of MC service IDs of the migrating MC service user(s) created by the partner MC system of the migrating MC service user, corresponding to the MC service IDs above.
MC service user profile
M
Set of MC service user profiles that corresponds to each MC service ID in the list above.
The user profile contains the initial UE configuration to access the partner MC system as defined in table A.6-1 of 3GPP TS 23.280 [5], and limited information for migration for each MC service user.
Response
M
Result information of the add user configuration request.
NOTE: The primary MC system of the migrated MC service user keeps a mapping of the MC service IDs used by MC service user(s) in the partner MC system(s).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.11 Remove user configuration request
|
Table 10.17.2.11-1 describes the information flow of the remove user configuration request sent from ACM client to ACM server in the primary MC system, from ACM server of primary MC system to ACM server of partner MC system and from ACM server to ACM client in partner MC system.
Table 10.17.2.11-1: Remove user configuration request
Information element
Status
Description
MC service ID
M
The identity of the authorized user in the primary MC system which sends the request.
Functional alias
O
The functional alias of the MC service user at the primary MC system which sends request.
MC service ID
O (see NOTE)
The identity of the authorized user in the partner MC system which is target of the request.
Functional alias
O (see NOTE)
The functional alias of the MC service user at the partner MC system towards which the request is sent.
MC service ID list
M
The list of users in the partner MC system that are being requested to be removed from migration.
Additional information list
O
Additional information describing the reason for removing each requested user in the list for migration from the primary MC system to the partner MC system.
NOTE: Either the MC service ID or the functional alias must be present.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.12 Remove user configuration response
|
Table 10.17.2.12-1 describes the information flow of the remove user configuration response sent from ACM client to ACM server in the partner MC system, from ACM server in partner MC system to ACM server in primary MC system and from ACM server to ACM client in primary MC system.
Table 10.17.2.12-1: Remove user configuration response
Information element
Status
Description
MC service ID
M
The identity of the authorized user in the partner MC system which is sending the remove user configuration response.
Functional alias
O
The functional alias of the MC service user at the partner MC system which is sending the remove user configuration response.
MC service ID
M
The identity of the authorized user in the primary MC system which is target of the response.
MC service ID list
M
The list of users in the partner MC system that were requested to be removed from migration.
Response
M
Result information for each user in the list for removal. Success or fail.
Reason
O
Additional information that explains the response for each user in the list.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.13 Update MC service UE initial configuration request
|
Table 10.17.2.13-1 describes the information flow sent from ACM client to ACM server in the primary MC system, from ACM server of primary MC system to ACM server of partner MC system and from ACM server to ACM client in partner MC system for updating initial MC service UE configuration data information that is required by the partner MC system for preparing migrating MC service UEs.
Table 10.17.2.13-1: Update MC service UE initial configuration request
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the primary MC system which triggers the update request.
Functional alias
O
The functional alias of the MC service user at the primary MC system which triggers the update request.
MC service ID
O
(see NOTE 1)
The identity of the MC service user at the partner MC system towards which the update request is sent.
Functional alias
O
(see NOTE 1)
The functional alias of the MC service user at the partner MC system towards which the update request is sent.
MC service ID list
M
Set of MC service IDs of the migrating MC service users that belong to the primary MC system.
MC service UE initial configuration data
M
(see NOTE 2)
This information element contains the information as specified in table A.6-1 of 3GPP TS 23.280 corresponding to the MC service IDs above.
NOTE 1: Either the MC service ID or the functional alias must be present.
NOTE 2: The optional MC service UE label defined in TS 23.280, Annex 6 is sent as blank information. present.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.14 Update MC service UE initial configuration response
|
Table 10.17.2.14-1 describes the information flow sent from ACM client to ACM server in the partner MC system, from ACM server in partner MC system to ACM server in primary MC system and from ACM server to ACM client in primary MC system.
Table 10.17.2.14-1: Update MC service UE initial configuration response
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the partner MC system which handled the received update request.
Functional alias
O
The functional alias of the MC service user at the partner MC system which handled the received update request.
MC service ID
M
The identity of the authorized user in the primary MC system which is target of the response.
Result
M
Result information of the update MC service UE initial configuration.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.15 MC service user profile update request
|
Table 10.17.2.15-1 describes the information flow sent from ACM client to ACM server in the primary MC system, from ACM server of primary MC system to ACM server of partner MC system and from ACM server to ACM client in partner MC system.
Table 10.17.2.15-1: MC service user profile update request
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the primary MC system which triggers the request.
Functional alias
O
The functional alias of the MC service user at the primary MC system which triggers request.
MC service ID
O (see NOTE)
The identity of the MC service user at the partner MC system towards which the request is sent
Functional alias
O (see NOTE)
The functional alias of the MC service user at the partner MC system towards which the request is sent
MC service ID
M
MC service ID of MC service user permitted to migrate, created by the partner MC system.
MC service user profile
M
The suggested updated MC service user profile on the partner MC system.
Additional Information
O
Additional information regarding the suggested updated MC service user profile on the partner MC system.
NOTE: Either the MC service ID or the functional alias must be present.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.2.16 MC service user profile update response
|
Table 10.17.2.16-1 describes the information flow sent from ACM client to ACM server in the partner MC system, from ACM server in partner MC system to ACM server in primary MC system and from ACM server to ACM client in primary MC system.
Table 10.17.2.16-1: MC service user profile update response
Information element
Status
Description
MC service ID
M
The identity of the MC service user at the partner MC system which handled the received request.
Functional alias
O
The functional alias of the MC service user at the partner MC system which handled the received request.
MC service ID
M
The identity of the authorized user in the primary MC system which is target of the response.
MC service ID
M
MC service ID of MC service user permitted to migrate, created by the partner MC system.
Result
M
Result information of the MC service user profile update request,
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3 Common ACM procedures
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.0 Introduction
|
Processing of the incoming ACM commands can be handled by the ACM entities through one of the following methods:
- manually by an ACM client of an authorized user or an administrator as described under the pending requests method in 10.17.3.1
- automatically either by an ACM server, or by an automated ACM client as described under 10.17.3.2
Based on the local policy, rules can be defined for the use of these methods by the MC system for the execution of the different ACM transactions.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.1 Pending requests
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.1.1 General
|
This procedure provides the means to manage and respond to the incoming requests manually. It describes the manual option which is performed by the ACM client of an authorized MC service user or administrator.
This procedure provides the detailed description of the steps that are not included in other procedures for simplicity.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.1.2 Procedure
|
Upon receiving an ACM request the ACM server should forward the request to the authorized user at its MC system. Performing this process might require considerable waiting time if the target authorized user is not logged on.
In addition, when an ACM server receives a response to a previously sent ACM request, where the authorized user is not logged on, the ACM server should store the response and notify the authorized user when the user logs on again.
The common procedure for pending ACM request/response is shown in figure 10.17.3.1.2-1
Pre-conditions
- The ACM server has received an ACM request, or a response, and has stored it.
- The ACM server has received an ACM request that should be validated by an authorized user
- The targeted ACM authorized user is currently not logged on.
Figure 10.17.3.1.2-1: Pending requests Procedure
1. An authorized MC service user of the MC system logs on to the ACM client.
2. The ACM server notifies the ACM client of the pending ACM data.
3. The ACM client requests the ACM server to send the pending ACM data.
4. The ACM server sends the stored ACM data to the ACM client.
NOTE: When this procedure is referenced in other ACM procedures, the individual ACM request/response information flows are provided by the related procedures in details.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.2 Processing incoming requests automatically
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.2.1 General
|
This procedure provides the means to manage and respond to the incoming requests automatically. It describes the automation options performed in the ACM server or by an automated ACM client.
This procedure provides the detailed description of the steps that are not included in other procedures for simplicity.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.2.2 Automation performed by ACM server
|
The partner ACM server verifies the request and sends a response to the primary MC system. Automation performed by ACM server shown in Figure 10.17.3.2.2-1.
Figure 10.17.3.2.2-1: Automation performed by ACM server
The following applies:
- The partner ACM server audits the request and, based on local policy, decides to automatically apply the configurations.
- The partner ACM server takes whatever actions are needed to apply the configurations to the partner MC system. The actions within the partner MC system to apply the configurations, including the interaction with other servers, are outside the scope of the 3GPP specification.
- The partner ACM server provides the means for the authorized users in the partner MC system to update the automation rules, or to terminate this automation, if required.
- The partner ACM server provides a tracking mechanism for the authorized users in the MC system for all automatically performed actions.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.3.2.3 Automation performed by automated ACM client
|
The ACM server of the partner MC system sends the received ACM request to an automated ACM client for processing and sending a ACM response automatically to the primary MC system without human interaction, as shown figure 10.17.3.2.3-1.
Figure 10.17.3.2.3-1: Automation performed by an automated ACM client
The following applies:
- The automated ACM client is enabled/logged-in and connected to ACM server
- The ACM server audits and verifies the request and, based on local policy, decides to forward the ACM request to an automated ACM client.
- The automated ACM client takes whatever actions that are needed to apply the configurations to the partner MC system. The actions within the partner MC system to apply the configurations are outside the scope of the 3GPP specification.
- The MC system provides the possibility for the authorized users in the partner MC system to update the automation rules, or to terminate the automated ACM client, if required.
- The partner ACM server provides a tracking mechanism for the authorized users in the partner MC system for all automatically performed actions by an automated client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.4 ACM Group configuration management
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.4.1 ACM Group membership configuration
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.4.1.1 General
|
The procedures in this clause provide the means to:
- manage users from the primary system in an interconnection MC service group that is defined in a partner MC system; and
- inform a partner MC system about interconnection MC service groups in the primary MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.4.1.2 Procedure
|
10.17.4.1.2.1 Group membership update by authorized user from a partner MC system
The procedure for an authorized MC service user in a primary MC system to manage group membership in an interconnection group that is defined in a partner MC system is shown in figure 10.17.4.1.2.1-1.
Pre-conditions
- Primary MC system and partner MC system are interconnected
- Primary MC system and partner MC system have implemented an ACMS
- Partner MC system is the MC service group home system of an interconnection group
- The authorized MC service user of the primary MC system wants to modify the membership of MC users of the primary system in the interconnection group for which the partner MC system is the MC service group home system.
- When a functional alias is used as the target of the request by an ACM client in the primary MC system, it is required that the ACM server of the primary MC system has subscribed to the MC service functional alias controlling server within the primary MC system, and that the ACM server of partner MC system has subscribed to the MC service functional alias controlling server within the partner MC system.
Figure 10.17.4.1.2.1-1: Group membership update by authorized user from a primary MC system
1. The ACM client in primary MC system sends a group membership update request to the ACM server in his MC system, requesting to modify the membership of users from primary MC system in an interconnection group for which partner MC system is the MC service group home system.
2. The ACM server of the primary MC system checks whether the MC service user at the ACM client is authorized for the request.
3. The ACM server of the primary MC system sends the group membership update request to the ACM server of the partner MC system, the MC service group home system of the interconnection group.
4. The ACMS of the partner MC system sends a process indication to primary MC system, and stores, verifies and assesses the incoming request.
Based on local policy,
- the ACMS of the partner MC system may automatically handle the request as described in clause 10.17.3.2 and continues with step 8,
or
- the ACM server of the partner MC system requests verification by an ACM client: If the authorized user in the partner MC system is not logged on, the pending request procedure as described in clause 10.17.3.1 is followed. If the request targets a functional alias the ACM server of the partner MC system resolves the functional alias (based on the current state of the functional alias) and proceeds as follows:
- if the functional alias is active for one ACM client, the request is sent to the ACM client;
- if the functional alias is active for more than one ACM client, the ACM server sends the request to one of these ACM clients based on the local policy;
- if the functional alias is not currently active, the ACM server of the partner MC system stores the request.
5. The ACM server of the partner MC system sends the stored group membership update request to the ACM client of partner MC system.
6. The authorized MC service user of the partner MC system (manually) screens the content of the group membership update request and decides whether to approve it or not. The authorized user in the partner MC system takes whatever actions are needed to apply the group membership update. The actions within the partner MC system to apply these configurations are outside the scope of the 3GPP specifications.
7. The ACM client of the partner MC system sends a group membership update response to the ACM server of the partner MC system.
8. The ACM server of the partner MC system sends the group membership update response to the ACM server of the primary MC system.
9. The ACM server of primary MC system stores the group membership update response. If the ACM client of primary MC system is not logged on the ACMS of primary MC system it will follow the pending request procedure as described in clause 10.17.3.1.
10. The ACM server of primary MC system sends the group membership update response to the ACM client of the primary MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.4.2 Providing interconnection MC service group ID
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.4.2.1 General
|
The MC system where the interconnection MC service group is defined, the primary MC systems, has to provide the identity of the group to the interconnected partner MC system. The procedure specified in this clause shows how an authorized user of an ACM client in primary MC system can provide the ACM server of partner MC system, or an authorized ACM client of partner MC system with one or more new interconnection MC service group IDs.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.4.2.2 Providing identity of interconnection MC service group
|
The procedure, which enables an authorized MC service user of a primary MC system to provide a list of interconnection group ID(s) to a selected authorized user of a partner MC system, is shown in figure 10.17.4.2.2-1.
Pre-conditions:
- Primary MC system and partner MC system are interconnected.
- Both MC systems have implemented an ACM functionality.
- The primary MC system is the MC service group home system for one or more interconnection groups.
- An MC service user of the primary MC system is authorized to provide a list of interconnection group IDs to partner MC system.
- When a functional alias is used as the target of the request by an ACM client in the primary MC system, it is required that the primary ACM server has subscribed to the MC service functional alias controlling server within the primary MC system, and that the partner ACM server has subscribed to the MC service functional alias controlling server within the partner MC system.
Figure 10.17.4.2.2-1: Providing interconnection MC service group ID(s) to partner MC system
1. The ACM client in the primary MC system sends an interconnection group identity provision request to the ACM server in the primary MC system, providing a list of interconnection group IDs and the ID of the selected authorized user in the partner MC system.
2. The ACM server of the primary MC system checks whether the MC service user at ACM client is authorized for the request. If the authorization check fails, the procedure is stopped.
3. The ACM server of the primary MC system forwards the interconnection group identity provision request to the ACM server in the partner MC system.
4. The ACMS of the partner MC system sends a process indication to primary MC system, and stores, verifies and assesses the incoming request.
Based on local policy,
- the ACMS of the partner MC system may automatically handle the request as described in clause 10.17.3.2 and continues with step 8,
or
- the ACM server requests verification by an ACM client: If the authorized user in the partner MC system is not logged on, the pending request procedure as described in clause 10.17.3.1 is followed. If the request targets a functional alias, the ACM server of the partner MC system resolves the functional alias (based on the current state of the functional alias) and proceeds as follows:
- if the functional alias is active for one ACM client, the request is sent to the ACM client;
- if the functional alias is active for more than one ACM client, the ACM server sends the request to one of these ACM clients based on the local policy;
- if the functional alias is not currently active, the ACM server of the partner MC system stores the request.
5. The ACM server of the partner MC system forwards the stored interconnection group identity provision request to the ACM client of the partner MC system.
6. The selected authorized user of the partner MC System processes the interconnection group IDs, e.g. by saving the information for future use. The authorized user in the partner MC system takes whatever actions are needed to handle the request. The actions taken within the partner MC system are outside the scope of the 3GPP specifications.
7. The ACM client of the partner MC system sends a interconnection group identity provision response to the ACM server of the partner MC system.
8. The ACM server of the partner MC system forwards the interconnection group identity provision response to the ACM server in the primary MC system.
9. The ACM server of the primary MC system stores the interconnection group identity provision response. If the primary ACM client is not logged on, the primary ACM server will follow the pending request procedure as described in clause 10.17.3.1.
10. The ACM server of the primary MC system forwards the interconnection group identity provision response to the ACM client of primary MC system, informing the authorized user of the primary MC system that the list of interconnection group IDs has been provided to the selected authorized user of the partner MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.5 ACM user migration management
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.5.1 General
|
User migration management enables adding or removing of MC service users of the primary MC system for migration at a partner MC system. An authorized MC service user can request adding or removing MC service users of his primary MC system for migration at a partner MC system by means of his ACM client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.5.2 Adding users for migration to a partner MC system
|
The procedure for an authorized MC service user in a primary MC system to request a partner MC system to authorize a list of MC user IDs from its MC System to migrate to that partner MC System is shown in figure 10.17.5.2-1.
Pre-conditions:
- The primary MC system and the partner MC system are interconnected.
- The primary MC system and the partner MC system have implemented an ACMS.
- The MC service user at the ACM client of the primary MC system is authorized to request adding users for migration to the partner MC system.
- The MC service user at the ACM client of the partner MC system is authorized to respond to requests for adding a list of users for migration from the primary MC system.
- When a functional alias is used as the target of the request by an ACM client in the primary MC system, it is required that the primary ACM server has subscribed to the MC service functional alias controlling server within the primary MC system, and that the partner ACM server has subscribed to the MC service functional alias controlling server within the partner MC system.
Figure 10.17.5.2-1: Add user configuration request in partner MC system
1. The primary ACMC sends add user configuration request to the primary ACMS, requesting to authorize a list of MC users from the primary MC System to migrate to the partner MC System.
2. The primary ACMS performs an authorization check to verify that the MC service user is authorized to perform this action. If the authorization check fails, the procedure is stopped.
3. The primary ACMS sends the add user configuration request to the partner ACMS.
4. The ACMS of the partner MC system sends a process indication to primary MC system, and stores, verifies and assesses the incoming request.
Based on local policy,
- the ACMS of the partner MC system may automatically handle the request as described in clause 10.17.3.2 and continues with step 8,
or
- the ACM server requests verification by an ACM client: If the authorized user in the partner MC system is not logged on, the pending request procedure as described in clause 10.17.3.1 is followed. If the request targets a functional alias, the ACM server of the partner MC system resolves the functional alias (based on the current state of the functional alias) and proceeds as follows:
- if the functional alias is active for one ACM client, the request is sent to the ACM client;
- if the functional alias is active for more than one ACM client, the ACM server sends the request to one of these ACM clients based on the local policy;
- if the functional alias is not currently active, the ACM server of the partner MC system stores the request.
5. The partner ACMS sends the stored add user configuration request to the partner ACM client.
6. The authorized MC service user of partner MC system checks the content of the add user configuration request and decides whether to approve it or not. The authorized user in the partner MC system takes whatever actions are needed to apply the configurations. The actions within the partner MC system to apply the configurations are outside the scope of the 3GPP specifications.
7. The partner ACM client sends add user configuration response to the partner ACM server.
8. The partner ACM server sends add user configuration response to the primary ACM server.
9. The primary ACM server stores the add user configuration response. If the primary ACM client is not logged on the primary ACM server will follow the pending request procedure as described in clause 10.17.3.1.
10. The primary ACM server sends the add user configuration response to the primary ACM client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.5.3 Removing users for migration from a partner MC system
|
The procedure for an authorized MC service user in the primary MC system, that is sent to an authorized user in the partner MC system, to request that certain users be removed from migration access in the partner MC system is shown in figure 10.17.5.3-1.
Pre-conditions:
- The primary MC system and the partner MC system are interconnected.
- The primary MC system and the partner MC system have implemented an ACMS.
- The MC service user in the primary MC system is authorized to request a list of MC service users be removed from the partner MC system for migration from the primary MC system.
- When a functional alias is used as the target of the request by an ACM client in the primary MC system, it is required that the primary ACM server has subscribed to the MC service functional alias controlling server within the primary MC system, and that the partner ACM server has subscribed to the MC service functional alias controlling server within the partner MC system.
Figure 10.17.5.3-1: Remove user configuration request from a partner MC system
1. The ACM client in the primary MC system sends a remove user configuration request to the ACM server in the primary MC system. This request includes a list of MC service users to be removed for migration access in the partner MC system.
2. The ACM server in the primary MC system validates whether the MC service user is authorized for the request. If the authorization check fails, the procedure is stopped.
3. The ACM server in the primary MC system sends the remove user configuration request to the ACM server in the partner MC system.
4. The ACM server of the partner MC system sends a process indication to primary MC system, and stores, verifies and assesses the incoming request.
Based on local policy,
- the ACM server of the partner MC system may automatically handle the request as described in clause 10.17.3.2 and continues with step 8,
or
- the ACM server requests verification by an ACM client: If the authorized user in the partner MC system is not logged on, the pending request procedure as described in clause 10.17.3.1 is followed. If the request targets a functional alias, the ACM server of the partner MC system resolves the functional alias (based on the current state of the functional alias) and proceeds as follows:
- if the functional alias is active for one ACM client, the request is sent to the ACM client;
- if the functional alias is active for more than one ACM client, the ACM server sends the request to one of these ACM clients based on the local policy;
- if the functional alias is not currently active, the ACM server of the partner MC system stores the request.
5. The ACM server in the partner MC System sends the remove user configuration request to the ACM client in the partner MC system.
6. The authorized MC service user of partner MC system checks the content of the request and decides whether to approve it or not. The authorized MC service user in the partner MC system takes whatever actions are needed to remove the requested user from migration access to the partner MC system. The actions within the partner MC system to remove users are outside the scope of the 3GPP specifications.
7. The ACM client of the partner MC system sends a remove user configuration response to the ACM server in the partner MC system. The target of this response is the original MC service user in the primary MC system that sent the remove user configuration request.
8. The ACM server in the partner MC system sends the remove user configuration response to the ACM server in the primary MC system.
9. The ACM server in the primary MC system stores the remove user configuration response. If the primary ACM client is not logged on the primary ACM server will follow the pending request procedure as described in clause 10.17.3.1.
10. The ACM server in the primary MC system sends the remove user configuration response to the ACM client in the primary MC system.
11. The authorized MC service user in the primary MC system takes whatever actions are needed (if any) to update the user profiles in the primary MC system for those users that no longer have migration access to the partner MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.6 ACM updating MC service UE initial configuration for migration
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.6.1 General
|
MC service UE initial configuration for migration is essential to perform migration because this configuration contains connectivity information such as APN, server URIs and other connectivity information of the partner MC system. MC service users which had been added (clause 10.17.5.2) for migration to a partner MC system will have received user profiles containing this configuration (table A.6-1) which enables them to get connected to the partner MC system.
In case changes to the connectivity information occurs, the MC service UE initial configuration shall be updated.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.6.2 Procedure
|
The procedure for an authorized MC service user in a primary MC system to update initial MC service UE configuration data information in the partner MC system is shown in figure 10.17.6.2-1.
Pre-conditions:
- Primary MC system and partner MC system are interconnected.
- Both MC systems have implemented ACM functionality.
- The set of MC service IDs and the MC service UE initial configuration of the migrating MC service users have been already sent by the primary MC system to the partner MC system, as specified in clause 10.17.5 ACM user migration management (between interconnected MC systems).
- When a functional alias is used as the target of the request by an ACM client in the primary MC system, it is required that the primary ACM server has subscribed to the MC service functional alias controlling server within the primary MC system, and that the partner ACM server has subscribed to the MC service functional alias controlling server within the partner MC system.
Figure 10.17.6.2-1: Update MC service UE initial configuration
1. The primary ACM client sends an update MC service UE initial configuration request to the primary ACM server, providing the initial MC service UE configuration data as specified in 3GPP TS 23.280 [5], Annex 6 to the primary MC System.
2. The primary ACM server performs an authorization check to verify that the MC service user is authorized to perform this action. If the authorization check fails, the procedure is stopped.
3. The primary ACM server sends the update MC service UE initial configuration request to the partner ACM server.
4. The ACM server of the partner MC system sends a process indication to primary MC system, and stores, verifies and assesses the incoming request.
Based on local policy,
- the ACM server of the partner MC system may automatically handle the request as described in clause 10.17.3.2 and continues with step 8,
or
- the ACM server requests verification by an ACM client: If the authorized user in the partner MC system is not logged on, the pending request procedure as described in clause 10.17.3.1 is followed. If the request targets a functional alias, the ACM server of the partner MC system resolves the functional alias (based on the current state of the functional alias) and proceeds as follows:
- if the functional alias is active for one ACM client, the request is sent to the ACM client;
- if the functional alias is active for more than one ACM client, the ACM server sends the request to one of these ACM clients based on the local policy;
- if the functional alias is not currently active, the ACM server of the partner MC system stores the request.
5. The partner ACM server forwards the stored update MC service UE initial configuration request to the partner ACM client.
6. The authorized MC service user of partner MC system processes the received update MC service UE initial configuration request.
7. The partner ACM client sends update MC service UE initial configuration response to the partner ACM server.
8. The partner ACM server sends update MC service UE initial configuration response to the primary ACM server.
9. The primary ACM client stores the update MC service UE initial configuration response as described in clause 10.17.3.1.
10. The primary ACM server forwards the update MC service UE initial configuration response to the primary ACM client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.7 ACM updating MC service user profiles assigned from partner MC system
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.7.1 General
|
A primary MC system may request through ACM entities to add a list of its MC service users for migration to a connected partner MC system as specified in clause 10.17.5 ACM user migration management. In case the partner MC system agrees to accept these users for migration it will reply with a response containing assigned MC service user identities and MC service user profiles. Those will be applicable and valid while the requested primary MC service users are migrated into the partner MC system.
In case, the primary MC system may want to update the received MC service user profiles from the partner MC system it can send a request for updating those as described in this clause.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.17.7.2 Procedure
|
The procedure for an authorized MC service user in a primary MC system to request MC service user profile update from a partner MC system is shown in figure 10.17.7.2-1.
Pre-conditions:
- Primary MC system and partner MC system are interconnected.
- Both MC systems have implemented ACM functionality.
- When a functional alias is used as the target of the request by an ACM client in the primary MC system, it is required that the primary ACM server has subscribed to the MC service functional alias controlling server within the primary MC system, and that the partner ACM server has subscribed to the MC service functional alias controlling server within the partner MC system.
Figure 10.17.7.2-1: MC service user profile update
1. The primary ACMC sends MC service user profile update request to the primary ACMS providing the required changes for the MC service user that is migrated to the partner MC System.
2. The primary ACMS performs an authorization check to verify that the MC service user is authorized to perform this action. If the authorization check fails, the procedure is stopped.
3. The primary ACMS sends the MC service user profile update request to the partner ACMS.
4. The ACMS of the partner MC system sends a process indication to primary MC system, and stores, verifies and assesses the incoming request.
Based on local policy,
- the ACMS of the partner MC system may automatically handle the request as described in clause 10.17.3.2 and continues with step 8,
or
- the ACM server requests verification by an ACM client: If the authorized user in the partner MC system is not logged on, the pending request procedure as described in clause 10.17.3.1 is followed. If the request targets a functional alias, the ACM server of the partner MC system resolves the functional alias (based on the current state of the functional alias) and proceeds as follows:
- if the functional alias is active for one ACM client, the request is sent to the ACM client;
- if the functional alias is active for more than one ACM client, the ACM server sends the request to one of these ACM clients based on the local policy;
- if the functional alias is not currently active, the ACM server of the partner MC system stores the request.
5. The partner ACMS forwards the stored MC service user profile update request to the partner ACMC.
6. The authorized MC service user of partner MC system checks the content of the MC service user profile update request and decides whether to approve it or not. The authorized user in the partner MC system takes whatever actions are needed to apply the MC service user profile update. The actions within the partner MC system to apply this configuration are outside the scope of the 3GPP specifications.
7. The partner ACMC sends MC service user profile update response to the partner ACMS.
8. The partner ACMS sends MC service user profile update response to the primary ACMS.
9. The primary ACMS stores the MC service user profile update response. If the primary ACMC is not logged on the primary ACMS will follow the pending request procedure as described in clause 10.17.3.1.
10. The primary ACMS forwards the MC service user profile update response to the primary ACMC.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18 Recording and replay
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1 Service configuration
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.1 Service ID and user profile
|
A recording admin and/or replay user is identified by an MCRec ID. An MCRec ID is associated with one user profile. This is depicted in figure 10.18.1.1-1.
Figure 10.18.1.1-1: The relationship of MC service user, MCRec ID and Recording admin and replay service user profile
One MC service user (MC ID) may have one or zero MCRec ID.
An MC service user (MC ID), who is authorized to use recording admin and/or replay service, may be authorized to use also MC services (MCPTT, MCVideo, MCData). However, the MCRec ID cannot have the same value as the MC service IDs for the same MC service user.
The recording admin and/or replay service user profile is applicable only in the user’s home system. I.e. the user profile is not valid in a partner system even if the MC service user with active MC services would migrate.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.2 Recording admin service configuration
|
Depicted in figure 10.18.1.2-1 is a recording admin service configuration time sequence, representing the general lifecycle of a Recording admin UE using recording admin service.
Figure 10.18.1.2-1 Recording admin UE configuration time sequence and associated configuration data
The recording admin UE is provided with initial recording admin UE and/or replay UE configuration (see clause A.10) via a bootstrap procedure that provides the recording admin UE’s identity management client and configuration management client with critical information needed to connect to the MC system.
After user authentication and service authorization with IdMS (TS 33.180 clause 5.1.2) the CM client obtains the recording admin and/or replay service user profile (clause A.11) from the CMS (10.18.1.5.1).
The UE can now perform recording admin operations (set or modify target users and groups), see 10.18.2.
During the service the user may get notifications that its user profile data has been updated. After a notification the CM client shall obtain the updated profile data from CMS (10.18.1.5.2).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.3 Replay service configuration
|
Depicted in figure 10.18.1.3-1 is a replay service configuration time sequence, representing the general lifecycle of a Replay UE using replay service.
Figure 10.18.1.3-1 Replay UE configuration time sequence and associated configuration data
The replay UE is provided with initial recording admin UE and/or replay UE configuration (see clause A.10) via a bootstrap procedure that provides the Replay UE’s identity management client and configuration management client with critical information needed to connect to the MC system.
After user authentication and service authorization with IdMS (TS 33.180 clause 5.1.2) the CM client obtains the recording admin and/or replay service user profile (clause A.11) from the CMS (10.18.1.5.1).
The UE can now perform replay operations, see 10.18.4.
During the service the user may get notifications that its user profile data has been updated. After a notification the CM client shall obtain the updated profile data from CMS (10.18.1.5.2).
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.4 Information flows for recording admin and replay service user profiles
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.4.1 Get recording admin and replay service user profile request
|
Table 10.18.1.4.1-1 describes the information flow get recording admin and replay service user profile request from the configuration management client to the configuration management server.
Table 10.18.1.4.1-1: Get recording admin and replay service user profile request
Information element
Status
Description
MCRec ID
M
The MCRec ID of the recording admin and/or replay service user
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.4.2 Get recording admin and replay service user profile response
|
Table 10.18.1.4.2-1 describes the information flow get recording admin and replay service user profile response from the configuration management server to the configuration management client.
Table 10.18.1.4.2-1: Get recording admin and replay service user profile response
Information element
Status
Description
Recording admin and/or replay service user profile data
M
The recording admin and/or replay service user profile (clauses 10.18.1.1, A.11) associated with the MCRec ID provided in the associated get recording admin and replay service user profile request.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.4.3 Notification for recording admin and replay service user profile data update
|
Table 10.18.1.4.3-1 describes the information flow notification for recording admin and replay service user profile data update from the configuration management server to the configuration management client.
Table 10.18.1.4.3-1: Notification for recording admin and replay service user profile data update
Information element
Status
Description
Pointer to the modified recording admin and/or replay service user profile data.
M
Pointer to the modified recording admin and/or replay service user profile data.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.4.4 Get updated recording admin and replay service user profile data request
|
Table 10.18.1.4.4-1 describes the information flow get updated recording admin and replay service user profile data request from the configuration management client to the configuration management server.
Table 10.18.1.4.4-1: Get updated recording admin and replay service user profile data request
Information element
Status
Description
MCRec ID
M
The MCRec ID of the recording admin and/or replay service user
Pointer to the modified recording admin and/or replay service user profile data.
M
Pointer to the modified recording admin and/or replay service user profile data.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.4.5 Get updated recording admin and replay service user profile data response
|
Table 10.18.1.4.5-1 describes the information flow get updated recording admin and replay service user profile data response from the configuration management server to the configuration management client.
Table 10.18.1.4.5-1: Get updated recording admin and replay service user profile data response
Information element
Status
Description
Updated recording admin and/or replay service user profile data
M
Recording admin and/or replay service user profile data that has been modified.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.5 Procedures for recording admin and replay service user profiles
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.5.1 Get recording admin and replay service user profile
|
Pre-conditions:
- The recording admin and replay service user has performed user authentication in the identity management server.
- The UE has secure access to the configuration management server.
Figure 10.18.1.5.1-1: Recording admin and/or replay user obtains the user profile from the network
1. The configuration management client sends a get recording admin and replay service user profile request message to the configuration management server, which includes the MCRec ID.
2. The configuration management server obtains the recording admin and/or replay service user profile information.
3. The configuration management server sends get recording admin and replay service user profile response message to the configuration management client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.1.5.2 Get updated recording admin and replay service user profile data
|
Pre-conditions:
- The recording admin and replay service user has performed user authentication with the identity management server.
- The UE has secure access to the configuration management server.
- The UE has already obtained a recording admin and/or replay service user profile.
Figure 10.18.1.5.2-1: Recording admin and/or replay service user receives updated user profile data from the CMS
1. The configuration management server obtains updated recording admin and/or replay service user profile data.
2. The configuration management server sends a notification for recording admin and replay service user profile data update to the configuration management client.
3. The configuration management client sends a get updated recording admin and replay service user profile data request to the configuration management server, which includes the MCRec ID.
4. The configuration management server sends get updated recording admin and replay service user profile data response to the configuration management client which includes the updated user profile data.
NOTE: The updated recording admin and/or replay service user profile data could be for the whole user profile or a specific parameter (or parameters) in the user profile.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.2 Target group and target user configuration
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.2.1 Store target group configuration at the GMS
|
The procedure for store target group configurations at the group management server is described in figure 10.19.2.1-1.
A recording admin shall use this procedure to set/modify/remove target group(s) for recording.
Pre-conditions:
- The recording admin service user has performed user authentication and service authorization with the IdMS and downloaded its own service profile from CMS.
- The UE has secure access to the group management server.
Figure 10.18.2.1-1: Store target group configuration at group management server
1. The group management client – triggered by a recording admin user - sends a store target group configuration request to the group management server.
2. The group management server checks the authorization of the originator (MCRec ID) for this operation.
3. The group management server stores the updated group configuration data.
4. The group management server provides a store group configuration response indicating success or failure.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.2.2 Update target MC service user profile data to the CMS
|
The procedure for update target MC service user profile data to CMS is illustrated in figure 10.19.2.2-1.
A recording admin shall use this procedure to set/modify/remove target MC service user (s) for recording.
Pre-conditions:
- The recording admin service user has performed user authentication and service authorization with the IdMS and downloaded its own service profile from CMS.
- The UE has secure access to the configuration management server.
Figure 10.18.2.2-1: Update target MC service user profile data to the CMS
1. The configuration management client – triggered by a recording admin user - sends the update target MC service user profile data request to the configuration management server.
2. The configuration management server checks that the target MC service user is under the requestor’s (MCRec ID) authority.
3. The configuration management server stores the received target MC service user profile data. If this target MC service ID is associated with multiple MC service user profiles, the same update must be done by CMS to all these profiles.
4. The configuration management server sends update MC service user profile data response to the configuration management client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.3 Recording procedures
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.3.1 General
|
The MC recording procedures for MCPTT and MCVideo group and private communications utilize Session Recording Protocol [40]. The Session Recording Client (SRC) is located in the MC service server. Recording server represents the Session Recording Server (SRS) in the Session Recording Protocol architecture.
Recording of communication sessions involves delivering real-time media and metadata of an MC service user or MC service group from an MC service server to the recording server.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.3.2 Procedure for recording communication sessions of an MC service user
|
Figure 10.18.3.2-1 below illustrates the recording procedure for communication sessions of an MC service user (MCPTT ID, MCVideo ID).
Pre-conditions:
- The user (MCPTT ID or MCVideo ID) has been configured as a target for recording in the MC service user profile (see 3GPP TS 23.281 [12] clause A.3 and 3GPP TS 23.379 [16] clause A.3) and the user profile has been uploaded to the MC service server.
- The target MC service user has performed MC user authentication and service authorization (see 3GPP TS 33.180 [25], clause 5.1.1 and clause 5.1.2) and has fetched its user profile(s) from the configuration management server.
Figure 10.18.3.2-1: Recording procedure for a target MC service user
1. An MC communication session (MCPTT/MCVideo private call) involving the target user is initiated.
2. A Session Recording Client (SRC) in the MC service server starts a recording session (see IETF RFC 7866 [40]) with the recording server.
3. The MC communication session ends.
4. The recording session ends.
5. The recording server stores the recording session, and it is available for download and/or replay.
NOTE: Steps 1-5 are repeated as long as none of the conditions of step 6 is true.
6. When the user (MCPTT ID / MCVideo ID) is removed from the recording targets or the user logs off from the MC service or the UE is switched off, an ongoing recording session (if exists) is terminated.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.