Content for TS 23.280 Word version: 19.3.1
1…
5…
5.2.8…
6
7…
7.3.2
7.4…
7.4.3…
7.5…
8…
9…
9.2.2…
9.2.2.2…
9.3…
10…
10.1.2…
10.1.3…
10.1.4.3…
10.1.4.5…
10.1.5…
10.1.6…
10.2…
10.2.3…
10.2.4.2…
10.2.4.3…
10.2.5…
10.2.7…
10.3…
10.6…
10.7…
10.7.3…
10.7.3.4…
10.7.3.7…
10.7.3.7.3
10.7.3.8…
10.7.3.10…
10.8…
10.8.4…
10.8.5…
10.9…
10.9.3…
10.9.3.5…
10.9.3.8…
10.9.3.9…
10.9.3.9.3…
10.9.3.9.4…
10.9.3.10…
10.9.3.10.4…
10.9.3.10.6…
10.10…
10.10.1.2.3…
10.10.2…
10.10.3…
10.10.3.3…
10.10.3.4…
10.11…
10.11.5…
10.12…
10.13…
10.13.3…
10.13.7…
10.13.10…
10.14…
10.15…
10.15.3…
10.15.3.3…
10.15.3.4…
10.16…
10.17…
10.17.3…
10.17.5…
11…
11.3…
11.5…
11.5.2…
11.5.3…
11.5.3.3.2A…
A…
B…
C…
E…
10.17 Sharing administrative configuration between interconnected MC systems
10.17.1 General
10.17.2 Information flows
10.17.2.1 ACM data notification
10.17.2.2 Get ACM data request
10.17.2.3 Get ACM data response
10.17.2.4 Group membership update request
10.17.2.5 Group membership update response
10.17.2.6 Process indication
10.17.2.7 Interconnection group identity provision request
10.17.2.8 Interconnection group identity provision response
10.17.2.9 Add user configuration request
10.17.2.10 Add user configuration response
10.17.2.11 Remove user configuration request
10.17.2.12 Remove user configuration response
10.17.2.13 Update MC service UE initial configuration request
10.17.2.14 Update MC service UE initial configuration response
10.17.2.15 MC service user profile update request
10.17.2.16 MC service user profile update response
...
...
10.17 Sharing administrative configuration between interconnected MC systems |R19| p. 312
10.17.1 General p. 312
Cooperation between MC systems encompasses a number of cases of mutual operation between them, e.g:
- Migration during ongoing group or private call communication as specified in subclause 10.16.
- Generic procedures for interconnection as specified in clause 10.14.
- Migration of MC service users from an MC system considered as primary or home MC system to an partner MC system as specified in subclause 10.6.3.
- Provisioning connectivity information of partner MC system(s) for MC service UE migration as specified in subclause 10.1.6.
- Shared MC service groups which can be configured as described in clause 10.2.7.
10.17.2 Information flows p. 312
10.17.2.1 ACM data notification p. 312
Table 10.17.2.1-1 describes the information flow of the ACM data notification from the ACM server to the ACM client.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | The identity of the MC service user towards the pending ACM data notification is sent. |
10.17.2.2 Get ACM data request p. 312
Table 10.17.2.2-1 describes the information flow of Get ACM data request from an ACM client to the ACM server.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | The identity of the MC service user requesting for the download of the pending ACM data. |
10.17.2.3 Get ACM data response p. 312
Table 10.17.2.3-1 describes the information flow of Get ACM data response from an ACM server to the ACM client.
| 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. |
10.17.2.4 Group membership update request p. 313
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.
| 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.
|
||
10.17.2.5 Group membership update response p. 313
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.
| 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. |
10.17.2.6 Process indication p. 313
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.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | The identity of the MC service user requesting for Group membership update and any other valid ACM request sent to partner MC system. |
| MC service group ID | M | Identity of the MC service group. |
| Acknowledgement | M | ACM request has been received, stored and processing is in progress. |
10.17.2.7 Interconnection group identity provision request p. 314
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.
| 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.
|
||
10.17.2.8 Interconnection group identity provision response p. 314
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.
| 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. |
10.17.2.9 Add user configuration request p. 315
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.
| 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.
|
||
10.17.2.10 Add user configuration response p. 315
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.
| 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 TS 23.280, 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).
|
||
10.17.2.11 Remove user configuration request p. 316
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.
| 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.
|
||
10.17.2.12 Remove user configuration response p. 316
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.
| 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. |
10.17.2.13 Update MC service UE initial configuration request p. 317
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.
| 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 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 Annex A.6 is sent as blank information. present.
|
||
10.17.2.14 Update MC service UE initial configuration response p. 317
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.
| 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. |
10.17.2.15 MC service user profile update request p. 318
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.
| 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.
|
||
10.17.2.16 MC service user profile update response p. 318
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.
| 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. |
