Content for TS 28.532 Word version: 18.3.0
1 Scope p. 17
The present document specifies the stage 2 and stage 3 of generic management services for mobile network.
2 References p. 17
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] Void
[3]
TS 28.541: "Management and orchestration ; 5G Network Resource Model (NRM); Stage 2 and stage3".
[4]
ITU-T Recommendation X.733 (02/92): "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function".
[5]
TS 28.531: "Management and orchestration ; Provisioning; ".
[6]
TS 28.554: "Management and orchestration ; 5G end to end Key Performance Indicators (KPI)".
[7] Void
[8] Void
[9] Void
[10] Void
[11]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[12] Void
[13]
TS 28.533: "Management and orchestration; Architecture framework"
[14] Void
[15]
TS 32.158: "Management and orchestration; Design rules for REpresentational State Transfer (REST) Solution Sets (SS)".
[16] Void
[17] Void
[18]
TS 28.552: "Management and orchestration; 5G performance measurements".
[19]
TS 32.401: "Telecommunication management; Performance Measurement (PM); Concept and requirements".
[20]
ISO 8601:2004: "Data elements and interchange formats - Information interchange - Representation of dates and times".
[21] Void.
[22] Void.
[23] Void.
[24] Void.
[25]
TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects ".
[26]
W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
[27]
W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
[28]
W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
[29]
W3C REC-xml-names-19990114: "Namespaces in XML".
[30] Void.
[31] Void.
[32]
RFC 6241 "Network Configuration Protocol (NETCONF)".
[33]
TS 32.160: " Management and orchestration; Management service template ".
[34]
RFC 7950 "The YANG 1.1 Data Modeling Language".
[35] Void
[36]
RFC 6902: "JavaScript Object Notation (JSON) Patch".
[37]
RFC 7396: "JSON Merge Patch".
[38]
TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[39]
TS 32.423: "Telecommunication management; Subscriber and equipment trace; Trace data definition and management".
[40]
RFC 6455: "The WebSocket Protocol".
[41]
RFC 793: "Transmission Control Protocol".
[42]
TS 28.550: "Management and orchestration; Performance assurance".
[43] Void
[44]
TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
[45]
Text Attribution: Creator: ONAP, under Creative Commons Attribution 4.0 International License, https://creativecommons.org/licenses/by/4.0/ , URI to access the text: https://github.com/onap/vnfrqts-requirements/blob/05f26fac2b941513a7d0e856b99fd8c61d688299/docs/Chapter8/ves7_1spec.rst#resource-structure .
[46] Void
[47]
TS 32.404: "Performance Management (PM); Performance measurements; Definitions and template".
[48] Void
[49]
RFC 8040: "RESTCONF protocol".
[50]
RFC 7951: " JSON Encoding of Data Modeled with YANG".
[51]
RFC 6243: "With-defaults Capability for NETCONF".
[52]
RFC 3339: " Date and Time on the Internet: Timestamps".
[53]
3GPP SA5 FORGE OpenAPI definitions: https://forge.3gpp.org/rep/sa5
[54]
TS 28.111: "Management and orchestration; Study on Network Slice Management Enhancement".
3 Definitions and abbreviations p. 19
3.1 Definitions p. 19
For the purposes of the present document, the terms and definitions given in TR 21.905 apply.
3.2 Abbreviations p. 19
4 Overview p. 19
The generic management services concept follows the management service concepts as defined in TS 28.533.
5 Void
6 Void
7 Void
8 Void
9 Void
10 Void
