Content for TR 28.872 Word version: 19.0.0
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
4 Concepts and background
...
...
1 Scope p. 6
The present document contains a study on the management of planned configurations.
2 References p. 6
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.
3 Definitions of terms, symbols and abbreviations p. 6
3.1 Terms p. 6
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.
3.2 Symbols p. 6
Void.
3.3 Abbreviations p. 6
4 Concepts and background p. 6
A telecommunication network is represented for management purposes by a data node tree on a MnS producer. When configuration changes are applied to this data node tree it is expected that the data node tree and the represented resources are updated (in synchronous or asynchronous fashion). So far there is no concept of a place, where configuration plans can be maintained.
This study investigates possibilities to manage configuration plans. These plans are activated only on explicit request. This basic functionality can be complemented with additional features like the validation of configuration plans, the conditional activation of configuration plans, or the possibility to tag plans as alternative configurations (e.g. for weekdays and weekends), or to tag them as plans that need to be activated together (transactions).
