Content for  TS 23.280  Word version:  19.2.0

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.

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.

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.

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.

The following applies:

• The partner ACM server audits the request and decides whether to apply the configurations or not.
• 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 tracking mechanism for the authorized users in the MC system for all automatically performed actions.

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 in Figure 10.17.3.2.3-1.

The following applies:

• The automated ACM client is enabled/logged-in and connected to ACM server
• The automated ACM client audits and verifies the request to decide whether to apply the configurations or not.
• The automated ACM client 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 are outside the scope of the 3GPP specification
• The MC system provides the possibility for the authorized users to update the automation rules, or to terminate the automated ACM client and accordingly the process automation, if required.
• The partner ACM server provides tracking mechanism for the authorized users in the partner MC system for all automatically performed actions by an automated client.

This clause address the following aspects:

• The second precondition in clause 10.2.7.2 of TS 23.280: One or more MC service group members are defined in the partner MC system.
• ACM entities can be used to manage/change memberships of interconnected MC service groups in partner MC systems.

The MC system where the interconnection MC service goup is set up, here the primary MC sytems, has to provide the identity of the group to the interconnected partner MC system. The specified procedure 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.

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.