Content for TS 28.317 Word version: 18.1.0
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
4 Concept and Background
4.1 Background
4.2 Network configuration data handling
4.3 Self-configuration
4.4 Self-configuration management
...
...
1 Scope p. 7
The present document describes the functionality for RAN NE self-configuration and network configuration data handling to enable RAN NE self-establishment, as well as requirements need to be met to support this functionality. The concepts, use cases, requirements, procedure and management service definition for RAN NE self-configuration management and network configuration data handling of RAN NEs are specified in the present document.
The NE within virtualization is not in the scope of the present document.
2 References p. 7
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 28.314: "Management and orchestration; Plug and Connect; Concepts and requirements".
[3]
TS 28.532: "Management and orchestration; Generic management services".
[4]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM); Integration Reference Point (IRP); Information Service (IS)".
[5]
Management and Orchestration APIs Stage3 repository, https://forge.3gpp.org/rep/sa5/MnS/-/tree/Tag_Rel18_SA103/ .
3 Definitions of terms, symbols and abbreviations p. 7
3.1 Terms p. 7
For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
RAN NE Self-Configuration:
The process which brings a RAN network element into service requiring minimal human operator intervention or none at all.
3.2 Symbols p. 8
Void.
3.3 Abbreviations p. 8
4 Concept and Background p. 8
4.1 Background p. 8
Establishment of a new RAN NE in network by an autonomous way can greatly improve the efficiency of RAN deployment. It refers to the procedure of a new RAN NE automatically establishing when it is powered up and connects to the IP network, which includes:
- Network configuration data handling
- Plug and connect to management system
- Self-Configuration
4.2 Network configuration data handling p. 8
Network configuration data handling refers to the procedures to make the network configuration data (i.e. additional data used to generate the complete RAN NE configuration data) available to the RANSC MnS producer, which may include network configuration data preparation, network configuration data transfer and network configuration data validation. This happens except all of the network configuration data for RAN NE can be generated by the RANSC MnS producer.
Network configuration data preparation: This makes the network configuration data ready in operator's network management system who provides the network configuration data. How to prepare the network configuration data in operator's network management system is out of scope of the present document.
Network configuration data transfer: This transfers the network configuration data from operator's network management system to the RANSC MnS producer.
Network configuration data validation: This validates the syntax and semantics of network configuration data. It takes place in the RANSC MnS producer.
4.3 Self-configuration p. 8
RAN NE can be taken to a state ready to carry traffic using self-configuration in an automated manner. Self-configuration may include following processes: generate the RAN NE configuration data, download and activate software, download and active configuration data, self-test and update network resource model, etc.
4.4 Self-configuration management p. 9
Self-configuration management capability is needed to monitor the self-configuration process and provide the operator with this information (e.g. progress information). In addition, it allows the operator to control the execution of the self-configuration process.
Figure 4.4-1: Example of deployment scenario for Self-configuration management
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
