hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.4 Preconfigured regroup response (MC service client – MC service server)
| Table 10.15.2.4-1 describes the information flow preconfigured regroup response from the MC service client to the MC service server.
Table 10.15.2.4-1 Preconfigured regroup response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the responding MC service client
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.5 Preconfigured regroup response (MC service server – MC service client)
| Table 10.15.2.5-1 describes the information flow preconfigured regroup response from the MC service server to the MC service client.
Table 10.15.2.5-1 Preconfigured regroup response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of the regrouping op... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.6 Preconfigured regroup response (MC service server – MC service server)
| Table 10.15.2.6-1 describes the information flow preconfigured regroup response from the MC service server to the MC service server.
Table 10.15.2.6-1 Preconfigured regroup response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the responding MC service client
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.7 Preconfigured regroup cancel request (MC service client – MC service server)
| Table 10.15.2.7-1 describes the information flow preconfigured regroup cancel request from the MC service client to the MC service server.
Table 10.15.2.7-1 Preconfigured regroup cancel request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester
MC serv... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.8 Preconfigured regroup cancel request (MC service server – MC service client)
| Table 10.15.2.8-1 describes the information flow preconfigured regroup cancel request from the MC service server to the MC service client.
Table 10.15.2.8-1 Preconfigured regroup cancel request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the target MC service ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.9 Preconfigured regroup cancel request (MC service server – MC service server)
| Table 10.15.2.9-1 describes the information flow preconfigured regroup cancel request from the MC service server to the MC service server.
Table 10.15.2.9-1 Preconfigured regroup cancel request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester
MC serv... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.10 Preconfigured regroup cancel response (MC service client – MC service server)
| Table 10.15.2.10-1 describes the information flow preconfigured regroup cancel response from the MC service client to the MC service server.
Table 10.15.2.10-1 Preconfigured regroup cancel response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the responding MC ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.11 Preconfigured regroup cancel response (MC service server – MC service client)
| Table 10.15.2.11-1 describes the information flow preconfigured regroup cancel response from the MC service server to the MC service client.
Table 10.15.2.11-1 Preconfigured regroup cancel response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of t... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.12 Preconfigured regroup cancel response (MC service server – MC service server)
| Table 10.15.2.12-1 describes the information flow preconfigured regroup cancel response from the MC service server to the MC service server.
Table 10.15.2.12-1 Preconfigured regroup cancel response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of t... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.13 Preconfigured regroup reject (MC service server – MC service client)
| Table 10.15.2.13-1 describes the information flow preconfigured regroup reject from the MC service server to the MC service client.
Table 10.15.2.13-1 Preconfigured regroup reject information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the requester of the regrouping
MC ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.14 Preconfigured regroup reject (MC service server – MC service server)
| Table 10.15.2.14-1 describes the information flow preconfigured regroup reject from the MC service server to the MC service server.
Table 10.15.2.14-1 Preconfigured regroup reject information elements
Information Element
Status
Description
MC service group ID
M
MC service group ID of the regroup group
Reject re... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.15 Preconfigured user regroup remove request (MC service server – MC service client)
| Table 10.15.2.15-1 describes the information flow preconfigured user regroup remove request from the MC service server to MC service client.
Table 10.15.2.15-1 Preconfigured user regroup remove request information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the MC service... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.16 Preconfigured user regroup remove response (MC service client – MC service server)
| Table 10.15.2.16-1 describes the information flow preconfigured user regroup remove response from the MC service client to the MC service server.
Table 10.15.2.16-1 Preconfigured user regroup remove response information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the MC s... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.2.17 Preconfigured regroup request return (MC service server – MC service client)
| Table 10.15.2.17-1 describes the information flow preconfigured regroup request return from the MC service server to the MC service client.
Table 10.15.2.17-1 Preconfigured regroup request return information elements
Information Element
Status
Description
MC service ID
M
The MC service ID of the calling party
M... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3 Regroup with preconfigured group
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.1 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.2 Preconfigured regroup procedures in a single MC system
| The following subclauses define group and user regroup procedures using preconfigured groups within a single MC system.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.2.1 Preconfigured Group Regroup formation in a single MC system
| Figure 10.15.3.2.1-1 illustrates the procedure to initiate a group regroup using a preconfigured MC service group. The procedure takes place prior to the establishment of a group call to the MC service regroup group.
Pre-conditions:
- MC service client 2 is an affiliated member of MC service group 1 and MC service cl... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.2.2 Preconfigured User Regroup formation in a single MC system
| Figure 10.15.3.2.2-1 illustrates the procedure to initiate a user regroup procedure using a preconfigured MC service group. The procedure takes place prior to the establishment of a group call to the MC service regroup group.
Pre-conditions:
- MC service clients 2 and 3 are registered with the MC service server.
- T... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.2.3 Preconfigured regroup cancellation in a single MC system
| Figure 10.15.3.2.3-1 illustrates the procedure to cancel a group or user regroup that uses a preconfigured MC service group.
Pre-conditions:
- MC service clients 2 and 3 have been regrouped into a MC service regroup group that uses the configuration of a preconfigured MC service group.
- MC service client 1 is autho... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.2.4 Preconfigured ad hoc group regroup formation in a single MC system
| Figure 10.15.3.2.4-1 illustrates the procedure to initiate an ad hoc group regroup using a preconfigured MC service group based on a request from an authorised MC service user.
NOTE: The upper limit of the number of ad hoc groups to be regrouped is up to implementation.
Pre-conditions:
- An ad hoc group communicati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.3 Preconfigured regroup procedures in multiple MC systems
| The following subclauses define group and user regroup procedures using preconfigured groups in multiple MC systems.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.3.1 Preconfigured Group Regroup formation in multiple MC systems
| Figure 10.15.3.3.1-1 illustrates the procedure to initiate a group regroup procedure using a preconfigured MC service group, where at least one of the groups to be regrouped is configured in a partner MC system. The primary MC system where the preconfigured group regrouping is initiated does not need to be aware of the... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.3.2 Preconfigured User Regroup formation in multiple MC systems
| Figure 10.15.3.3.2-1 illustrates the procedure to initiate a user regroup procedure using a preconfigured MC service group, where at least one of the MC service users to be regrouped is homed in a partner MC system. It is assumed that the group management server in the primary MC system of the MC service regroup group ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.3.3 Preconfigured regroup cancellation in multiple MC systems
| Figure 10.15.3.3.3-1 illustrates the procedure to cancel a group or user regroup that uses a preconfigured MC service group where multiple MC systems were involved in the regrouping.
Pre-conditions:
- MC service client 2 has been regrouped into the MC service regroup group, and is receiving service in the partner MC ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.3.4 Preconfigured group regroup rejection in multiple MC systems
| Figure 10.15.3.3.4-1 illustrates the case where the procedure to initiate a group regroup with multiple MC systems using a preconfigured MC service group described in subclauses 10.15.3.3.1 commences, but where the request for the regroup is rejected by the partner MC service server. The rejection can occur, for exampl... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.15.3.4 Other preconfigured regroup procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 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 ide... |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 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-prog... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16 Generic procedures for migration
| |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.2 Migration during an ongoing group communication
| |
6d5e4a70e9f91968db9c2f826133800a | 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.
|
6d5e4a70e9f91968db9c2f826133800a | 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.2.3 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.2.3.1 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.3 Private call using functional alias towards a partner MC system
| |
6d5e4a70e9f91968db9c2f826133800a | 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.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.3.2 Information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 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: ... |
6d5e4a70e9f91968db9c2f826133800a | 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 t... |
6d5e4a70e9f91968db9c2f826133800a | 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.4 Migration during an onging private communication
| |
6d5e4a70e9f91968db9c2f826133800a | 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 configurati... |
6d5e4a70e9f91968db9c2f826133800a | 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, or MCData one-to-one communication and IPcon point-to-point communication.
Figure 10.16.4.2-1: Migration during ongoing p... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.5 Generic private call procedure towards a migrated MC service user
| |
6d5e4a70e9f91968db9c2f826133800a | 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 conjunctio... |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 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 sys... |
6d5e4a70e9f91968db9c2f826133800a | 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.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.6.2 Information flows
| 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... |
6d5e4a70e9f91968db9c2f826133800a | 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 pri... |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.16.7.2 Information flows
| 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... |
6d5e4a70e9f91968db9c2f826133800a | 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 M... |
6d5e4a70e9f91968db9c2f826133800a | 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 M... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17 Sharing administrative configuration between interconnected MC systems
| |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.2 Information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 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
|
6d5e4a70e9f91968db9c2f826133800a | 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
|
6d5e4a70e9f91968db9c2f826133800a | 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
... |
6d5e4a70e9f91968db9c2f826133800a | 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
In... |
6d5e4a70e9f91968db9c2f826133800a | 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
Info... |
6d5e4a70e9f91968db9c2f826133800a | 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 M... |
6d5e4a70e9f91968db9c2f826133800a | 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: Interc... |
6d5e4a70e9f91968db9c2f826133800a | 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: Inter... |
6d5e4a70e9f91968db9c2f826133800a | 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 r... |
6d5e4a70e9f91968db9c2f826133800a | 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 configuratio... |
6d5e4a70e9f91968db9c2f826133800a | 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 configu... |
6d5e4a70e9f91968db9c2f826133800a | 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 config... |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 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
Informa... |
6d5e4a70e9f91968db9c2f826133800a | 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 eleme... |
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.3 Common ACM procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 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 d... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.3.1 Pending requests
| |
6d5e4a70e9f91968db9c2f826133800a | 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 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 t... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.3.2 Processing incoming requests automatically
| |
6d5e4a70e9f91968db9c2f826133800a | 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.
|
6d5e4a70e9f91968db9c2f826133800a | 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... |
6d5e4a70e9f91968db9c2f826133800a | 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 fo... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.4 ACM Group configuration management
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.4.1 ACM Group membership configuration
| |
6d5e4a70e9f91968db9c2f826133800a | 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.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.4.1.2 Procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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 syste... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.4.2 Providing interconnection MC service group ID
| |
6d5e4a70e9f91968db9c2f826133800a | 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 M... |
6d5e4a70e9f91968db9c2f826133800a | 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 ha... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.5 ACM user migration management
| |
6d5e4a70e9f91968db9c2f826133800a | 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.
|
6d5e4a70e9f91968db9c2f826133800a | 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 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 syst... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.6 ACM updating MC service UE initial configuration for migration
| |
6d5e4a70e9f91968db9c2f826133800a | 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 sy... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.