hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 4 General Requirements | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 4.1 Service Management and Orchestration (SMO) | REQ-SMO-FUN-1: O-RAN compliant SMOs shall support the O1 interfaces as defined in the present document. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 4.2 Transport Layer Security (TLS) | TLS requirements specified in O-RAN Security Protocol Specifications [16] clauses 4.2, 4.3 and 4.4 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 4.3 HyperText Transfer Protocol (HTTP) | REQ-HTP-FUN-1: Management Service providers and consumers that use HTTP shall support HTTP v1.1 or higher. REQ-HTP-FUN-2: Management Service providers and consumers that use HTTP should support HTTP v2.0. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 4.4 Secure Shell (SSH) | SSH requirements specified in O-RAN Security Protocol Specifications [16] clause 4.1 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 4.5 Least Privilege Access Control | Least privilege access control requirements specified in O-RAN Security Requirements Specification [17] clause 5.2.2 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 4.6 Confidentiality, Integrity and Authenticity | Confidentiality, integrity and authenticity requirements specified in O-RAN Security Requirements Specification [17] clause 5.2.2 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 5 O1 Notifications | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 5.1 General | An O1 notification is a JSON encoded asynchronous notification sent from a MnS provider to a MnS consumer over the O1 interface using REST/HTTPS. An O1 notification shall be in one of the following formats: - SDO O1 format - VES O1 format An SDO O1 format notification is an O1 notification formatted as specified by a Standards Defining Organization (SDO). Currently, O1 supports SDO O1 format notifications that are either 3GPP-specified or O-RAN-specified. SDO O1 format notifications are formatted as specified by the SDO and sent without a VES header. 3GPP-specified O1 notifications are specified in ETSI TS 128 532 [3], clause 11 and clause 12. O-RAN-specified O1 notifications are specified in the O-RAN Information Model and Data Models Specification [i.14]. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 15 O-RAN-specified O1 notifications should follow 3GPP naming and format where possible to reduce the number of variants that need to be supported. Specifically, O-RAN-specified O1 notifications should: - be named "o1NotifyXxx"; - include the common 3GPP notification fields objectClass, objectInstance, notificationId, notificationType, eventTime and systemDN; - include an additionalText and/or additionalInformation field when appropriate. A VES O1 format notification is an O1 notification formatted as specified by VES Event Listener Specification [18], consisting of a common event header and domain-specific event fields. VES O1 format notifications are categorized into 2 types, based on domain: - Harmonized VES - Legacy VES Harmonized VES refers to the stndDefined VES event specified in VES Event Listener Specification [18] that allows a VES event to carry, as its payload, a notification specified by an SDO. In the case of O-RAN O1 Interface Specification, a harmonized stndDefined VES event carries either a 3GPP-specified O1 notification or an O-RAN specified O1 notification as its payload. Legacy VES refers to any VES event specified in the VES Event Listener Specification [18], except for stndDefined. Legacy VES events are fully defined in [18] and do not rely on an SDO to specify the content of the payload. The Legacy VES events supported by O1 Interface Specification is PNF Registration. Legacy VES events are supported for backward compatibility. However, harmonized VES events are preferred. Use of harmonized VES events results in less notification variants for the providers and the consumers because a harmonized VES O1 format notification is effectively an SDO O1 format notification wrapped in a VES common event header. Two attributes are used to communicate the notification format between MnS provider and MnS consumer: - o1NotifyFormatCapabilities indicates whether the MnS provider supports the capability to send notifications in SDO O1 format, VES O1 format or both. This attribute is set by the MnS provider at the Managed Element level, meaning the capability is for all O1 notifications sent by that MnS provider. It is not per notification type. This attribute is read-only for the MnS consumer. - o1NotifyFormatConfig indicates whether the MnS consumer wants to receive notifications in SDO O1 format or VES O1 format. This attribute is optional to be supported by MnS provider. This attribute is configured by the MnS consumer at the Managed Element level, meaning the configuration is for all O1 notifications sent by that MnS provider. It is not per notification type. If the MnS provider supports both formats, the MnS provider sets the value for this attribute to the default value of VES O1 format when the MOI is created and the MnS consumer is permitted to change the value to SDO O1 format if desired. Otherwise, if the MnS provider only supports one notification format, this attribute is absent. Configuration attributes are specified in the O-RAN Information Model and Data Models Specification [i.14]. It is not necessary to have an attribute to indicate whether harmonized VES or legacy VES is sent for VES format because the domain of the event is provided in the VES common event header and the schema of the event is provided by the Network Function at onboarding time. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 5.2 O-RAN Defined O1 Notification | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 5.2.1 Requirements | REQ-ON-FUN-1: O-RAN defined O1 PNF and VNF registration notification shall be JSON encoded for sending via REST/HTTPS. REQ-ON-FUN-2: Schema for O-RAN defined O1 notification shall be specified using OpenAPI. REQ-ON-FUN-3: If VES O1 format is configured to be used, O-RAN defined O1 notification shall be presented in harmonized VES format and schemaReference shall refer to O-RAN defined schema in O-RAN public repository when it is available. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 16 NOTE 1: O-RAN public repository is not created yet. NOTE 2: Before the schema for the O-RAN defined notification is available in the O-RAN public repository, the schemaReference in the VES O1 format for O-RAN defined O1 notification does not need to be a path to the public repository. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 5.2.2 stndDefinedNamespace name space for O-RAN | O-RAN defines following name space for VES O1 format-harmonized VES format: OR-PnfRegistration. For O-RAN defined performance measurements, the short form of measurement name has prefix "OR.". The source of the definition is clear, so there is no need to have a separate O-RAN name space for performance measurement. O-RAN defined performance measurements should use 3GPP-PerformaceMeasurement name space and refer to 3GPP schema. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6 Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1 Provisioning Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.0 Overview | Provisioning management services allow a Provisioning MnS Consumer to configure attributes of managed objects on the Provisioning MnS Provider that modify the Provisioning MnS Provider's capabilities in its role in end-to-end network services and allows a Provisioning MnS Provider to report configuration changes to the Provisioning MnS Consumer. NETCONF is used for the Provisioning Management Services to Create Managed Object Instance, Delete Managed Object Instance, Modify Managed Object Instance Attributes and Read Managed Object Instance Attributes. A RESTful/HTTP notification with data modelled using YANG is used to notify the Provisioning MnS subscribed Consumers when a configuration change occurs. Stage 1 Provisioning management services are specified in 3GPP TS 28.531 [i.3] clause 6.3. Stage 2 Provisioning operations and notifications are specified in ETSI TS 128 532 [3] clause 11.1.1. Stage 3 Provisioning operations for YANG/NETCONF solution set are specified in ETSI TS 128 532 [3] clause 12.1.3. Stage 3 Provisioning notifications for "YANG/Netconf-based- solution set" with data modelled using YANG in a RESTful notification is specified in ETSI TS 128 532 [3] clause 12.1.3. For the VES header support, refer to ETSI TS 128 532 [3] clause 12.1.2. The media type of the notification, as specified by the "Content-Type" header in the HTTP POST request, shall be "application/json". NOTE: In the payload, the data is encoded according to ETSI TS 128 532 [3] clause 12.1.3.2.5 (except for the content type in the header). Consumption of the payload is implementation dependent. IETF reference documents for NETCONF and YANG include IETF RFC 6241 [20] and IETF RFC 7950 [21]. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.1 General NETCONF Requirements | REQ-GNC-FUN-1: The provisioning management service provider and consumer shall support the following NETCONF operations as specified in IETF RFC 6241 [20]: - get - get-config - edit-config - lock - unlock ETSI ETSI TS 104 043 V11.0.0 (2024-06) 17 - close-session - kill-session Other operations are optional. REQ-GNC-FUN-2: The provisioning management service provider and consumer shall support the following NETCONF capabilities: - writable-running - rollback-on-error - validate - xpath Other capabilities are optional. REQ-GNC-FUN-3: The provisioning management service provider and consumer shall support a running datastore for NETCONF. Support for a candidate datastore is optional. REQ-GNC-FUN-4: The provisioning management service provider and consumer shall support YANG1.1, defined in IETF RFC 7950 [21], including coexistence with YANG Version 1 as specified therein. REQ-GNC-FUN-5: The provisioning management service provider shall have the capability to establish a NETCONF session with its authorized consumer upon request from the consumer. REQ-GNC-FUN-6: The provisioning management service provider shall support an established NETCONF session until the authorized consumer terminates the session. NOTE: The consumer may want to perform multiple provisioning management services operations during a single NETCONF Session. REQ-GNC-FUN-7: The provisioning management service provider shall have the capability to terminate a NETCONF session with its authorized consumer when requested to do so by the authorized consumer. REQ-GNC-FUN-8: The provisioning management service provider shall have the capability to make provisioning operation results persistent over a reset. REQ-GNC-FUN-9: The provisioning management service provider and consumer shall support NETCONF over SSH or NETCONF over TLS. REQ-GNC-FUN-10: The provisioning management service provider shall support /netconf-state/schemas subtree and <get-schema> RPC defined in IETF RFC 6022 [19] for all supported YANG modules. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.2 Create Managed Object Instance | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.2.1 Description | Provisioning MnS Consumer sends a synchronous provisioning update request to the Provisioning MnS Provider to create a Managed Object Instance (MOI) on the Provisioning MnS Provider and set its attribute values. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.2.2 Requirements | The mapping of operations specified in ETSI TS 128 532 [3], clauses 12.1.3.1.1 and 12.1.3.1.2 shall apply. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 18 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.2.3 Procedures | @startuml Title Create MOI autonumber "[0]" participant "Provisioning MnS Consumer" as NMS participant "Provisioning MnS Provider" as ME NMS –> ME: NETCONF edit-config create Note over ME : Create MOI ME --> NMS: NETCONF rpc-reply <OK> or <rpc-error> @enduml Figure 6.1.2.3-1: Create MOI Pre-Conditions: - NETCONF session has been established with Provisioning MnS Provider. NETCONF session has authorized privileges into the identified section of the data store. - Optionally, target data store has been locked. Procedure: 1) Provisioning MnS Consumer sends NETCONF edit-config create operation to Provisioning MnS Provider: a) Provisioning MnS Provider creates the MOI(s) in the target data store as specified in the edit-config operation. 2) Provisioning MnS Provider returns NETCONF response. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.3 Modify Managed Object Instance Attributes | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.3.1 Description | Provisioning MnS Consumer sends synchronous provisioning updates to the Provisioning MnS Provider to modify the attributes of a MOI on the Provisioning MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.3.2 Requirements | The mapping of operations specified in ETSI TS 128 532 [3] clauses 12.1.3.1.1 and 12.1.3.1.4 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.3.3 Procedures | @startuml Title Modify MOI Attributes autonumber "[0]" participant "Provisioning MnS Consumer" as NMS participant "Provisioning MnS Provider" as ME NMS –> ME: NETCONF edit-config create, replace or delete Note over ME : Modify MOI ME --> NMS: NETCONF rpc-reply <OK> or <rpc-error> @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 19 Figure 6.1.3.3-1: Modify MOI Attributes Pre-Conditions: - NETCONF session has been established with Provisioning MnS Provider. NETCONF session has authorized privileges into the identified section of the data store. - Optionally, target data store has been locked. Procedure: 1) Provisioning MnS Consumer sends NETCONF edit-config create, replace, or delete operation to Provisioning MnS Provider: a) Provisioning MnS Provider modifies the MOI(s) in the target data store as specified in the edit-config operation. 2) Provisioning MnS Provider returns NETCONF response. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.4 Delete Managed Object Instance | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.4.1 Description | Provisioning MnS Consumer sends synchronous provisioning updates to the Provisioning MnS Provider to delete a MOI and its children on the Provisioning MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.4.2 Requirements | The mapping of operations specified in ETSI TS 128 532 [3] clauses 12.1.3.1.1 and 12.1.3.1.5 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.4.3 Procedures | @startuml Title Delete MOI autonumber "[0]" participant "Provisioning MnS Consumer" as NMS participant "Provisioning MnS Provider" as ME NMS –> ME: NETCONF edit-config delete or remove Note over ME : Delete MOI ME --> NMS: NETCONF rpc-reply <OK> or <rpc-error> @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 20 Figure 6.1.4.3-1: Delete MOI Pre-Conditions: - NETCONF session has been established with Provisioning MnS Provider. NETCONF session has authorized privileges into the identified section of the data store. - Optionally, target data store has been locked. Procedure: 1) Provisioning MnS Consumer sends NETCONF edit-config delete or remove operation to Provisioning MnS Provider: a) Provisioning MnS Provider deletes the MOI(s) in the target data store as specified in the edit-config operation. 2) Provisioning MnS Provider returns NETCONF response. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.5 Read Managed Object Instance Attributes | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.5.1 Description | Provisioning MnS Consumer sends synchronous provisioning request to the Provisioning MnS Provider to return the values of attributes of its MOI(s) on the Provisioning MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.5.2 Requirements | The mapping of operations specified in ETSI TS 128 532 [3] clauses 12.1.3.1.1 and 12.1.3.1.3 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.5.3 Procedures | @startuml Title Read MOI Attributes autonumber "[0]" participant "Provisioning MnS Consumer" as NMS participant "Provisioning MnS Provider" as ME NMS -> ME : NETCONF get or get-config Note over ME : Retrieve config ME --> NMS: NETCONF rpc-reply <data> @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 21 Figure 6.1.5.3-1: Read MOI Attributes Pre-Conditions: - NETCONF session has been established with Provisioning MnS Provider. NETCONF session has authorized privileges into the identified section of the data store. Procedure: 1) Provisioning MnS Consumer sends NETCONF get or get-config operation to Provisioning MnS Provider: a) Provisioning MnS Provider retrieves the MOI(s) and its attributes from the target data store as specified in the get or get-config operation. 2) Provisioning MnS Provider returns the data in the NETCONF response. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.6 Notify Managed Object Instance Changes | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.6.1 Description | Provisioning MnS Provider sends an asynchronous notifyMOIChanges Notification to the Provisioning MnS Consumer to report configuration changes to one or more MOIs on the Provisioning MnS Provider. Refer to ETSI TS 128 532 [3], clause 12.1.3.2.5 for details. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.6.2 Requirements | The mapping of notifications specified in ETSI TS 128 532 [3], clause 11.1.1.11 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.6.3 Procedures | @startuml Title Notify Managed Object Instance Changes Autonumber participant "Provisioning MnS Consumer" as NMS participant "Provisioning MnS Provider" as ME Note over ME : One or more config changes occur ME ->> NMS : <<HTTP/TLS>> notifyMOIChanges Notification Note over NMS : Reconcile Database @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 22 Figure 6.1.6.3-1: Notify Managed Object Instance Changes Pre-conditions: - One or more MOIs are created, deleted or modified in the running data store of the Provisioning MnS Provider. - Provisioning MnS Consumer has subscribed for notifyMOIChanges notifications. Procedure: 1) Provisioning MnS Provider sends notifyMOIChanges notification to the Provisioning MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. Post-condition: - Provisioning MnS Consumer reconciles its copy of the Provisioning MnS Provider configuration database with the change. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.6.4 Operations and Notifications | A Provisioning MnS notification shall be in one of the following formats: - SDO O1 format: - An O1supported 3GPP-specified Provisioning notification, as specified in ETSI TS 128 532 [3]. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing stndDefinedFields with a "data" element that contains an O1supported 3GPP-specified Provisioning notification, as specified in ETSI TS 128 532 [3]. The O1-supported 3GPP-specified CM notification is: - notifyMOIChanges A single notifyMOIChanges notification can report one or more MOI creations, MOI deletions and/or MOI attribute value changes in one notification. The attribute name value pairs in the CM notifications are provided using YANG 1.1 encoded in JSON format as specified in IETF RFC 7951 [22]. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 23 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.7 Subscription Control | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.7.1 Description | Subscription Control allows a MnS Consumer to subscribe to notifications emitted by a MnS Provider. Starting with 3GPP Release 16, dedicated operations for Management Services Use Cases are supported by IOCs with attributes that can be read and/or set using generic provisioning mechanisms. For Subscription Control, the Subscribe and Unsubscribe operations are replaced with a NtfSubscriptionControl IOC as specified in ETSI TS 128 622 [7]. NtfSubscriptionControl IOC contains attributes that allow a MnS Consumer to set the recipient address for the notifications and identify the scope of notifications desired. Optionally, the types of notifications desired, and notification filtering may also be provided. If filtering of the notifications is supported, only those notifications that match the specified value would be sent. For example, notifyNewAlarm notifications can be filtered to send only those with severity set to major or critical. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.7.2 Requirements | NtfSubscriptionControl IOC definition shall be as specified in ETSI TS 128 622 [7], clause 4.3.22 with attribute definitions specified in ETSI TS 128 622 [7], clause 4.4.1. YANG models for NtfSubscriptionControl shall be as specified in ETSI TS 128 623 [23], clause D.2.6a. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.7.3 Procedures | NtfSubscriptionControl instances may be created and deleted by the system or pre-installed. Optionally, the NtfSubscriptionControl MOIs can be created and deleted, and attributes modified using NETCONF/YANG by the management service consumer following the procedures described in this Provisioning MnS clause. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.7.4 Operations and Notifications | Subscription Control can be used to subscribe to alarm notifications specified in ETSI TS 128 622 [7], clause 4.4.1 notificationTypes. Subscription Control can be used to subscribe to heartbeat notifications as specified in ETSI TS 128 622 [7], Figure 4.2.1-5; i.e. by creating the HeartbeatControl MOI as a child of the NtfSubscriptionControl MOI. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.8 NETCONF Session Establishment | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.8.1 Description | Provisioning MnS Consumer uses the NETCONF Session Establishment procedure to establish a NETCONF session on the Provisioning MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.8.2 Requirements | Requirements for NETCONF session establishment specified in IETF RFC 6241 [20] shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.8.3 Procedure | The procedure to establish a NETCONF session is shown below. @startuml Title NETCONF Session Establishment autonumber "[0]" participant "Provisioning MnS Consumer" as SMO participant "Provisioning MnS Provider" as ME SMO <-> ME : SSH or TLS session establishment SMO -> ME : NETCONF Hello ME --> SMO : NETCONF Hello <sessionId> <capabilitiesList> @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 24 Figure 6.1.8.3-1: NETCONF Session Establishment |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.9 NETCONF Session Termination | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.9.1 Description | Provisioning MnS Consumer uses the NETCONF Session Termination procedure to gracefully terminate a NETCONF session on a Provisioning MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.9.2 Requirements | NETCONF session termination shall be as specified in IETF RFC 6241 [20], section 7.8. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.9.3 Procedure | The procedure to terminate a NETCONF session is shown below. @startuml Title NETCONF Session Termination autonumber "[0]" participant "Provisioning MnS Consumer" as SMO participant "Provisioning MnS Provider" as ME SMO -> ME : NETCONF close-session ME --> SMO : NETCONF rpc-reply <OK> @enduml Figure 6.1.9.3-1: NETCONF Session Termination ETSI ETSI TS 104 043 V11.0.0 (2024-06) 25 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.10 Lock Data Store | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.10.1 Description | Provisioning MnS Consumer uses the Lock Data Store procedure to lock a target data store on a Provisioning MnS Provider. This procedure is optional, but recommended, to prevent unpredictable behavior during configuration changes. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.10.2 Requirements | NETCONF lock data store should be as specified in IETF RFC 6241 [20], section 7.5. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.10.3 Procedure | The procedure to lock a data store is shown below. @startuml Title Lock Data Store autonumber "[0]" participant "Provisioning MnS Consumer" as SMO participant "Provisioning MnS Provider" as ME SMO -> ME : NETCONF lock <targetDS> Note over ME : Lock target DS ME --> SMO : NETCONF rpc-reply <OK> @enduml Figure 6.1.10.3-1: Lock Data Store |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.11 Unlock Data Store | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.11.1 Description | Provisioning MnS Consumer uses the Unlock Data Store procedure to unlock a target data store on a Provisioning MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.11.2 Requirements | NETCONF unlock data store should be as specified in IETF RFC 6241 [20], section 7.6. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 26 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.11.3 Procedure | The procedure to unlock a data store is shown below. @startuml Title Unlock Data Store autonumber "[0]" participant "Provisioning MnS Consumer" as SMO participant "Provisioning MnS Provider" as ME SMO -> ME : NETCONF unlock <target DS> Note over ME : Unlock target DS ME --> SMO : NETCONF rpc-reply <OK> @enduml Figure 6.1.11.3-1: Unlock Data Store |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.12 Commit | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.12.1 Description | Provisioning MnS Consumer uses the Commit procedure to commit a configuration change to the running data store of the Provisioning MnS Provider. This is necessary to make the configuration change effective if it was made in the candidate data store. If the configuration change was made in the running data store, the commit procedure is not used. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.12.2 Requirements | Requirements for NETCONF commit specified in IETF RFC 6241 [20], section 8.4 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.1.12.3 Procedure | The procedure to commit a configuration change is shown below. @startuml Title Commit autonumber "[0]" participant "Provisioning MnS Consumer" as SMO participant "Provisioning MnS Provider" as ME SMO -> ME : NETCONF commit Note over ME : Commit change to running DS ME --> SMO: NETCONF rpc-reply <OK> @enduml ETSI ETSI TS 104 043 V11.0.0 (2024-06) 27 Figure 6.1.12.3-1: Commit |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2 Fault Supervision Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.0 Overview | Fault supervision management services allow a Fault Supervision MnS Provider to report errors and events to a Fault Supervision MnS Consumer and allows a Fault Supervision MnS Consumer to perform fault supervision operations on the Fault Supervision MnS Provider, such as get alarm list. Stage 1 Fault Supervision MnS is specified in ETSI TS 128 545 [5]. Stage 2 Fault Supervision notifications are specified in ETSI TS 128 532 [3]. Stage 2 AlarmList IOC and AlarmRecord data type are specified in ETSI TS 128 622 [7]. Stage 3 Solution Sets for XML, JSON and YANG are specified in ETSI TS 128 623 [23]. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.1 Fault Notification | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.1.1 Description | Fault Supervision MnS Provider sends asynchronous Fault notification event to Fault Supervision MnS Consumer when an alarm occurs, is cleared, or changes severity. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.1.2 Requirements | The following fault supervision data report service requirements specified in ETSI TS 128 545 [5] clause 5.2.5 shall apply: - REQ-FSDR_NF-FUN-1 for sending alarm notifications - REQ-FSDR_NF-FUN-3 for alarm notification subscription - REQ-FSDR_NF-FUN-4 for alarm notification unsubscription - REQ-FSDR_NF-FUN-6 for reading the alarm list - REQ-FSDR_NF-FUN-8 for reading the alarm list with a filter - REQ-FSDR_NF-FUN-9 for sending changed alarm notifications - REQ-FSDR_NF-FUN-10 for sending cleared alarm notifications - REQ-FSDR_NF-FUN-11 for sending new alarm notifications ETSI ETSI TS 104 043 V11.0.0 (2024-06) 28 - REQ-FSDR_NF-FUN-12 for sending alarm list rebuilt notification The following requirements from ETSI TS 128 545 [5] clause 5.2.5 may apply: - REQ-FSDR_NF-FUN-5 for filtering the alarm notifications that are reported NOTE: Filtering is best done at the SMO level. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.1.3 Procedures | Procedures are defined in ETSI TS 128 545 [5] clause 9.1. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.1.4 Operations and Notifications | A Fault Supervision MnS notification shall be in one of the following formats: - SDO O1 format: - An O1-supported 3GPP-specified Fault Supervision notification, as specified in ETSI TS 128 532 [3]. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing stndDefinedFields with a "data" element that contains an O1-supported 3GPP-specified Fault notification, as specified in ETSI TS 128 532 [3]. The O1-supported 3GPP-specified Fault Supervision notifications are: - notifyNewAlarm - notifyChangedAlarmGeneral and/or notifyChangedAlarm - notifyClearedAlarm - notifyAlarmListRebuilt NotifyChangedAlarm only supports reporting the severity change. NotifyChangedAlarmGeneral permits the producer to report the severity change and any other attribute changes associated with this alarm in a single notification. The other 3GPP Fault Supervision notifications specified in ETSI TS 128 532 [3] are optional. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.2 Fault Supervision Control | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.2.1 Description | Starting with 3GPP Release 16, dedicated operations for Management Services Use Cases are supported by IOCs with attributes that can be read and/or set using generic provisioning mechanisms. For Fault Supervision, an AlarmList IOC is specified in ETSI TS 128 622 [7] that represents the capability to store and manage alarm records. There is one AlarmList per Fault Supervision MnS Provider, created by the Provider. The AlarmList contains one AlarmRecord for each active alarm. The AlarmRecords in the AlarmList can be read by the Fault Supervision MnS Consumer, with an optional filter to retrieve selected AlarmRecords based on the value of attributes in the AlarmRecord. For example, Fault Supervision MnS Consumer is able to retrieve only those AlarmRecords with perceivedSeverity = CRITICAL. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.2.2 Requirements | The following fault supervision data control service requirements from ETSI TS 128 545 [5], clause 5.2.6 may apply to the Fault Supervision MnS Provider: - REQ-FSDC_NF-FUN-1 to support alarm acknowledgement. NOTE 1: There is no Use Case that requires a NF to acknowledge an alarm. This operation is best done at the SMO level. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 29 - NF that does not support the alarm acknowledgement from the MnS Consumer shall consider cleared alarms as automatically acknowledged so that they may be removed from the AlarmList. - REQ-FSDC_NF-FUN-2 to support manual alarm clearing. NOTE 2: Manual clearing of alarms is only for ADMC (Automatically Detected, Manually Cleared) alarms. - NF that supports ADMC alarms should support the manual alarm clearing operation. - REQ-FSDC_NF-FUN-4 to support acknowledgement state change notifications. NOTE 3: There is no Use Case that requires a NF to acknowledge an alarm. This operation is best done at the SMO level. - NF that supports the alarm acknowledgement should support the acknowledgement state change notifications. AlarmList IOC definition shall be as specified in ETSI TS 128 622 [7], clauses 4.3.26 and 4.3.27 with attribute definitions in specified in ETSI TS 128 622 [7], clause 4.4.1. YANG solution set for AlarmList IOC shall be as specified in ETSI TS 128 623 [23], clause D.2.9. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.2.3 Procedures | NETCONF protocol and YANG data models are used to get and set the attributes of the AlarmRecords in the AlarmList. Refer to Provisioning management services clause for procedures to read MOI attributes and modify MOI attributes using NETCONF. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.2.2.4 Void | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3 Performance Assurance Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.0 Overview | Performance Assurance Management Services allow a Performance Assurance MnS Provider to report file-based (bulk) and/or streaming (real time) performance data to a Performance Assurance MnS Consumer and allows a Performance Assurance MnS Consumer to perform performance assurance operations on the Performance Assurance MnS Provider, such as selecting the measurements to be reported and setting the frequency of reporting. Use cases are specified in ETSI TS 128 550 [6], clause 5.1. Stage 2 notifyFileReady notification is specified in ETSI TS 128 532 [3]. Stage 2 PerfMetricJob IOC is specified in ETSI TS 128 622 [7]. Stage 3 Solution Sets for XML, JSON and YANG are specified in ETSI TS 128 623 [23]. Stage 2 and 3 for streaming data reporting service are specified in ETSI TS 128 532 [3]. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1 Performance Data File Reporting | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.1 Description | Performance Assurance MnS Provider sends asynchronous FileReady notification event to Performance Assurance MnS Consumer when PM File(s) is ready for retrieval. The FileReady notification contains information needed to retrieve the file such as filename and the location where the file can be retrieved. Performance Assurance MnS Consumer retrieves the PM File(s) from the location specified in the notifyFileReady notification. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 30 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.2 Requirements | Requirements specified in ETSI TS 128 550 [6], clause 5.2.2 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.3 Procedures | Procedure is specified in ETSI TS 128 550 [6], clause 5.1.1.2. @startuml Title PM Data File Reporting and Retrieval participant "Performance Assurance MnS Consumer" as NMS participant "Performance Assurance MnS Provider" as ME Note over ME : 1 New PM data file available ME ->> NMS : 2 <<HTTP/TLS>> notifyFileReady Notification NMS -> ME : 3 <<Secure File Transfer Protocol>> Get PM File(s) @enduml Figure 6.3.1.3-1: PM Data File Reporting and Retrieval Pre-condition: - Performance Assurance MnS Consumer has subscribed to File Ready notifications. Procedure: 1) A new PM data file is available on the Performance Assurance MnS Provider. 2) Performance Assurance MnS Provider sends notifyFileReady notification to Performance Assurance MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. 3) Performance Assurance MnS Consumer sets up a secure file transfer protocol connection to the location specified in the notifyFileReady notification and gets the PM data file(s). Secure file transfer protocols are specified in ETSI TS 128 537 [4], clause 7.1.3. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.4 Operations and Notifications | A File Ready notification shall be in one of the following formats: - SDO O1 format: - An O1-supported 3GPP-specified notifyFileReady notification, as specified in ETSI TS 128 532 [3]. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing stndDefinedFields with a "data" element that contains an O1-supported 3GPP-specified File Ready notification, as specified in ETSI TS 128 532 [3]. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 31 The O1-supported 3GPP-specified File Ready notification is: - notifyFileReady. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.5 PM File Generation and Reporting | PM file generation and reporting shall be as specified in ETSI TS 128 532 [3], clause 11.6. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.6 PM File Content | PM file content shall be as specified in ETSI TS 128 532 [3], clause 11.3.2.1.2. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.7 PM File Naming | PM file naming shall be as specified in ETSI TS 128 532 [3], clause 11.3.2.1.4. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.8 PM File XML Format | PM file XML format shall be as specified in ETSI TS 128 532 [3], clause 12.3.2 and/or in ETSI TS 132 432 [14], clause 4.1. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.1.9 5G Performance Measurements | 3GPP defined 5G performance measurements are specified in 3GPP TS 28.552 [i.5]. In addition to the 3GPP-defined measurements, it is possible to have O-RAN defined measurements and vendor supplied measurements. Clause 6.3.4 provides requirements for O-RAN defined measurements. O-RAN defined measurements are named with an "OR." prefix. Vendor supplied measurements are named with a "VS." prefix. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.2 Performance Data Streaming | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.2.1 Description | Performance Assurance MnS Provider steams high volume asynchronous streaming performance measurement data to Performance Assurance MnS Consumer at a configurable frequency. A secure WebSocket connection is established between the Performance Assurance Provider and the Performance Assurance Consumer. The connection supports the transmission of one or more streams of PM data. Each stream of PM data is configured as a PerfMetricJob (see clause 6.3.3 of the present document). The provider supplies information about the supported streams to the consumer during the connection establishment. The connection may be established to support one or more streams. Streams can be added or removed from the connection as the PerfMetricJobs are added or deleted. The connectionID that carries the streaming PM data is provided to the Performance Assurance Provider during the establishment of the WebSocket connection by the Performance Assurance Consumer. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.2.2 Requirements | Requirements for Streaming PM specified in ETSI TS 128 550 [6], clause 5.2.3 shall apply. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 32 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.2.3 Procedures | Use Cases for Streaming PM are specified in ETSI TS 128 550 [6], clause 5.1.1.3. Operations and notifications specified in ETSI TS 128 532 [3], clause 11.5 are applicable to both Streaming PM and Streaming Trace. @startuml Title Performance Data Streaming Autonumber participant "Performance Assurance MnS Consumer" as NMS participant "Performance Assurance MnS Provider" as ME Note over ME : Performance Data Streaming Job Configured ME ->> NMS : <<HTTP/TLS>> establish Streaming Connection NMS ->> ME : <<HTTP/TLS>> Connection Established loop (while performance job is active) ME ->> NMS : <<WebSocket>> report stream data via performance data stream unit End ||| @enduml Figure 6.3.2.3-1: Perf Data Streaming Connection Establishment and Data Transmission Pre-condition: - Performance Assurance MnS Provider is configured to produce PerfMetricJob to be delivered via streaming PM to the Performance Assurance Consumer. Procedure: 1) Performance Assurance MnS Provider requests to establish a WebSocket connection to begin streaming PM data and provides MetaData about the streams that are to be sent on the connection. 2) Performance Assurance Consumer accepts the request to upgrade the connection to a WebSocket. 3) Performance Assurance MnS Provider transmits binary encoded data to consumer while performance job is active. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.2.4 Operations and Notifications | ETSI TS 128 532 [3], clause 11.5.1 defines the following operations that an O-RAN compliant NF that supports streaming PM shall support. These are the same operations as listed for streaming trace in clause 6.4.6.1 of the present document. They are repeated here, as it is possible that a NF may support different levels of streaming for trace and performance assurance: - establishStreamingConnection operation is specified in ETSI TS 128 532 [3], clause 11.5.1.1. Establishing the streaming connection is initiated via an HTTPS POST followed by an HTTP GET (upgrade) to establish the WebSocket connection. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 33 - terminateStreamingConnection operation is specified in ETSI TS 128 532 [3], clause 11.5.1.2. This operation is accomplished via a WebSocket Close Frame to tear down the streaming connection when all stream jobs on this connection have been terminated. The delivery of WebSocket Close Frame is provided by the underlying TCP. - reportStreamData operation is specified in ETSI TS 128 532 [3], clause 11.5.1.3. The streamData field contains the streaming PM data which is encoded according to the format defined in ETSI TS 128 550 [6] Annex G which provides the ASN.1 definition of the Performance Data Stream Units. The delivery of WebSocket Close Frame is provided by the underlying TCP. If O-RAN NF supports the capability of sending multiple PM streams across the WebSocket connection, the following operations shall be supported: - addStream operation is specified in ETSI TS 128 532 [3], clause 11.5.1.4. This operation is used when a new Performance Assurance Stream (PM job started) is added on the Performance Assurance Provider to be delivered to this consumer and the NF supports multiple streams per connection. The addStream operation is accomplished via an HTTP POST. - deleteStream operation is specified in ETSI TS 128 532 [3], clause 11.5.1.5. This operation is used when a Performance Assurance Stream (PM job stopped) is deleted from the connection between the Performance Assurance Provider and the Performance Assurance Consumer. The deleteStream operation is accomplished via an HTTP DELETE. The following operations specified in ETSI TS 128 532 [3], clause 11.5.1 may be supported by O-RAN NFs: - getConnectionInfo operation is specified in ETSI TS 128 532 [3], clause 11.5.1.6. This operation allows the performance data streaming service provider to get information from the performance data streaming service consumer on the streams active on the connection. - getStreamInfo operation is specified in ETSI TS 128 532 [3], clause 11.5.1.7. This operation allows the performance data streaming service provider to get the information for one or more streams from the streaming consumer (i.e. stream target). No notifications have been defined for Performance Data Streaming. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.2.5 PM Streaming Data Generation and Reporting | ETSI TS 128 550 [6], Annex C lists all the Performance Data Stream Unit Content Items. Annex C of the present document provides a description of the establishment of the WebSocket connection and the subsequent operations provided as part of the data streaming service. The example utilizes the trace service, but the operations around the establishment and tear down of the connection are the same for streaming PM and streaming Trace. The WebSocket connection remains until all streams configured to be provided between the PA Provider and the PA Consumer have been terminated. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.2.6 PM Streaming Data Format | PM Streaming data shall be delivered according to the format specified in the input parameters of the establishStreamConnection operation specified in ETSI TS 128 532 [3], clause 11.5.1.1.2. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.3 Measurement Job Control | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.3.1 Description | Starting with 3GPP Release 16, Performance Assurance Control supported by IOCs with attributes that can be read and/or set using generic provisioning mechanisms in the Measurement Job Control Service. Measurement jobs can be created and terminated by creating and deleting a PerfMetricJob MOI. Measurement jobs can be queried by getting the attributes of a PerfMetricJob MOI. Measurement jobs can be temporarily suspended or resumed by modifying the administrativeState attribute of a PerfMetricJob MOI to LOCKED or UNLOCKED. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 34 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.3.2 Requirements | Requirements for measurement job control specified in ETSI TS 128 550 [6], clause 5.2.1 shall apply. PerfMetricJob IOC definition shall be as specified in ETSI TS 128 622 [7], clause 4.3.31 with attribute definitions in specified in ETSI TS 128 622 [7], clause 4.4.1. SupportedPerfMetricGroup datatype shall be as specified in ETSI TS 128 622 [7], clause 4.3.32. ReportingCtrl shall be as specified in ETSI TS 128 622 [7], clause 4.3.33. YANG solution set for PerfMetricJob IOC shall be as specified in ETSI TS 128 623 [23], clause D.2.4. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.3.3 Procedures | Procedures for measurement job creation, termination, query, suspend and resume are specified in ETSI TS 128 622 [7], clause 4.3.31. NETCONF protocol and YANG data models are used to create MOI, delete MOI, modify attributes and get attributes of a PerfMetricJob. Refer to Provisioning management services clause for detailed procedures on how to perform these operations using NETCONF. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.3.4 Void | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.4 O-RAN Defined Performance Measurements | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.3.4.1 Requirements | REQ-OPM-FUN-1: O-RAN specific measurements shall be defined using the template specified in ETSI TS 132 404 [10]. REQ-OPM-FUN-2: The Measurement Name for O-RAN defined measurements shall not exceed 64 characters in length and should be constrained to 32 characters maximum. REQ-OPM-FUN-3: Measurement Name of O-RAN defined measurements shall begin with OR prefix to indicate that O-RAN is the source of the measurement. When a measurement is accepted in 3GPP, the OR prefix shall be deleted. REQ-OPM-FUN-4: Short form of the measurement name in the Measurement Type for an O-RAN defined measurement shall begin with "OR." to indicate that O-RAN is the source of the measurement definition. When a measurement is accepted in 3GPP, the OR prefix shall be deleted. REQ-OPM-FUN-5: In case O-RAN extends the definition of an existing 3GPP measurement, a new O-RAN measurement shall be defined. 3GPP measurement name shall be part of new defined O-RAN measurement name. 3GPP definition for the measurement which new O-RAN measurement is based on shall be referred when possible. NOTE: Informative Annex A provides examples of how O-RAN O-DU measurements could be specified following the template in ETSI TS 132 404 [10]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.