hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 S... |
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 har... |
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-R... |
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... |
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... |
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 sessio... |
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 (2... |
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.... |
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: ... |
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 1... |
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 wi... |
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... |
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... |
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 <ses... |
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 S... |
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... |
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... |
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 co... |
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 T... |
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... |
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 readin... |
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 stndDefin... |
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 al... |
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 ... |
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 ... |
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 Assu... |
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 Notif... |
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... |
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 a... |
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 supp... |
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 N... |
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... |
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 ope... |
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 qu... |
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 specif... |
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 det... |
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 defin... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4 Trace Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.0 Overview | Trace management services allow a Trace MnS Provider to report file-based or streaming trace records to the Trace MnS Consumer. Trace Control provides the ability for the Trace Consumer to start a trace session by configuring a Trace Job via the Trace Control IOC or by establishing a trace session that propagates trace... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1 Call Trace |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.