hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.1 Trace Data Reporting | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.1.1 Description | Trace Data can be reported from the Trace Provider to the Trace Consumer via trace files or via a streaming interface. For management-based activation, Trace Data is collected after the TraceJob is configured on the Trace Provider, the Trace Session is activated, and the triggering event occurs. For signaling-based act... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.1.2 Requirements | Requirements for Trace data specified in 3GPP TS 32.421 [11], clause 5.2 shall apply to both file-based and streaming trace. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.1.3 Procedures | Trace Data is binary encoded and reported in Trace Records. The procedures for reporting data are specified in 3GPP TS 32.422 [12], clause 7. File-based trace reporting procedures are found in 3GPP TS 32.422 [12], clauses 7.1.1 and 7.2.1. Streaming trace reporting procedures are found in 3GPP TS 32.422 [12], clauses 7.... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.2 Trace Session Activation | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.2.1 Description | A trace session starts on a provider configured to support a TraceJob via management or signaling-based activation. Management-based trace session activation is initiated from the Provisioning Management Service Consumer to activate a TraceJob which has been configured on the provider. See clause 6.4.5 of the present d... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.2.2 Requirements | Requirements for Trace Session Activation for file-based and streaming trace specified in 3GPP TS 32.421 [11], clause 5.3.1 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.2.3 Procedures | Procedures for activating a Trace Session via management-based control are found in 3GPP TS 32.422 [12], clause 4.1.1.1 for general procedures and 3GPP TS 32.422 [12], clause 4.1.1.9 for NGRAN specific procedures. Procedures for activating a Trace Session via signaling are found in 3GPP TS 32.422 [12], clauses 4.1.2.1 ... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.3 Trace Session Deactivation | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.3.1 Description | A Trace Session is terminated/deactivated when any of the defined stop triggering events occur as specified in 3GPP TS 32.421 [11], such as a timer expiring, or the TraceJob Session is deactivated via management control. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.3.2 Requirements | Requirements for Trace Session Deactivation specified in 3GPP TS 32.421 [11], clause 5.4.1 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.3.3 Procedures | Procedures for Trace Session Deactivation are found in 3GPP TS 32.422 [12], clause 4.1.3.10 for management-based trace deactivation and clause 4.1.4.1.2 for signalling-based trace deactivation. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 37 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.4 Trace Recording Session Activation | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.4.1 Description | A trace recording session is a specific instance of the data specified to be collected for a particular trace session, for example, a specific call. For management-based activation, the trace recording session starts on a provider configured with an active trace session when a triggering event occurs, such as a new cal... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.4.2 Requirements | Requirements for Trace Recording Session Activation specified in 3GPP TS 32.421 [11], clause 5.3.2 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.4.3 Procedures | Procedures for starting a Trace Recording Session are found in 3GPP TS 32.422 [12], clause 4.2.1 for general requirements. 3GPP TS 32.422 [12], clause 4.2.2.10 has requirements for management-based trace session activation and clause 4.2.3.12 has requirements when the trace session was activated via signaling. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.5 Trace Recording Session Termination | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.5.1 Description | A Trace Recording Session is terminated when any of the defined stop triggering events occur or the Trace Session is deactivated. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.5.2 Requirements | Requirements for Trace Recording Session Termination specified in 3GPP TS 32.421 [11], clause 5.4.2 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.1.5.3 Procedures | Procedures for Trace Recording Session Termination are found in 3GPP TS 32.422 [12], clauses 4.2.4.10 and 4.2.5.13. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.2 Minimization of Drive Testing (MDT) | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.2.1 Description | ETSI TS 137 320 [i.9] provides an overall description for MDT. An O-RAN network function may support Immediate and Logged MDT as described in ETSI TS 137 320 [i.9]. Logged MDT is always file-based. Immediate MDT may be configured to be file-based or streaming. MDT measurements are described in ETSI TS 137 320 [i.9]. 3G... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.2.2 Requirements | Requirements for managing MDT specified in 3GPP TS 32.421 [11], clause 6 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.2.3 Procedures | Procedures for Trace Session Activation are the same for MDT as for Call Trace and are found in 3GPP TS 32.422 [12], clause 4.1. Procedures for specifying MDT Trace selection conditions are found in 3GPP TS 32.422 [12], clause 4.1.5. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 38 Procedures for Trace Recording Sessions star... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.3 Radio Link Failure (RLF) | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.3.1 Description | Radio Link Failure (RLF) reporting is a special Trace Session which provides the detailed information when a UE experiences an RLF event, and the reestablishment is successful to the source gNB. 3GPP TS 32.421 [11], 3GPP TS 32.422 [12] and 3GPP TS 32.423 [13] describe the management of RLF. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.3.2 Requirements | Requirements for RLF specified in 3GPP TS 32.421 [11], clause 7 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.3.3 Procedures | Procedures for Trace session activation and deactivation for RLF reporting are found in 3GPP TS 32.422 [12], clauses 4.3.1 and 4.3.2. Procedures for specifying the RLF reporting job type when configuring the RLF reporting session are found in 3GPP TS 32.422 [12], clause 5.9a. Procedures for RLF reporting follow standar... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.4 RRC Connection Establishment Failure (RCEF) | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.4.1 Description | Radio Resource Control (RRC) Connection Establishment Failure (RCEF) is activated on the gNB as a special Trace Session where the job type indicates RCEF reporting only. The records are produced when a UE experiences an RCEF event and the RRC establishment is successful to the same gNB. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.4.2 Requirements | Requirements for RCEF specified in 3GPP TS 32.421 [11], clause 7 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.4.3 Procedures | Procedures for trace session activation of RCEF are found in 3GPP TS 32.422 [12], clause 4.8.1. Procedures for trace session deactivation for RCEF reporting are found in 3GPP TS 32.422 [12], clause 4.8.2. Procedures for specifying the job type for RCEF are found in 3GPP TS 32.422 [12], clause 5.9a. Procedures for RCEF ... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.5 Trace Control | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.5.1 Description | Starting with 3GPP Release 16, Management-based Trace Control is supported with IOCs with attributes that can be read and/or set using generic provisioning mechanisms in the Trace Control Service. For Trace Control, this includes operations such as Create TraceJob, Activate TraceJob, Deactivate TraceJob, and Query Trac... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.5.2 Requirements | Management-based activation and deactivation shall be done via the TraceJob IOC defined in ETSI TS 128 622 [7] clause 4.30. Requirements for TraceJob Activation specified in 3GPP TS 32.421 [11], clause 5.3.1 and requirements for TraceJob deactivation specified in 3GPP TS 32.421 [11], clause 5.4.1 shall apply for both M... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.5.3 Procedures | Management-based activation and deactivation accomplished using CRUD operations specified in clause 6.1 of the present document. The attributes of the TraceJob are specified in ETSI TS 128 622 [7], clause 4.3.30.2. Constraints on these attributes are specified in ETSI TS 128 622 [7], clause 4.3.30.3. Trace Control IOC ... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.6 Streaming Trace | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.6.0 Overview | A NF can be configured to deliver trace data via a file or via a streaming interface. The streaming capability was introduced in 3GPP Release 16. The additional requirements and procedures supported for streaming trace are provided in this clause. An example of the configuration, activation, recording and termination o... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.6.1 Streaming Trace Requirements and Procedures | As noted above, trace session and recording activation and deactivation, as well as the content of the trace record, are the same for file-based and streaming trace. The requirements for streaming trace delivery specified in 3GPP TS 32.421 [11], clause 5.5 shall apply. Operations for establishing the streaming connecti... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.7 UE Identifiers for Trace Records | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.4.7.1 Description | The contents of the Trace Records are specified in 3GPP TS 32.423 [13], clause 4 and Trace Record Header in 3GPP TS 32.423 [13], clause 5.2.2. The Trace Record containing protocol related messages may contain 3GPP defined UE identifiers corresponding to the protocol. These UE identifiers are a part of protocol messages... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5 File Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.0 Overview | File management services allow a File Management MnS Consumer to get notification of new available files; query available files and request the transfer of files between the File Management MnS Provider and the File Management MnS Consumer. Relevant 3GPP specifications for file transfer are ETSI TS 128 537 [4], ETSI TS... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.1 File Ready Notification | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.1.1 Description | The File Ready Notification notifies a File Management MnS Consumer that a file is available for retrieval from the File Management MnS Provider. In general, File Management MnS Provider sends a notifyFileReady notification for files that the File Management MnS Consumer has configured the File Management MnS Provider ... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.1.2 Requirements | The notifyFileReady notification shall be as specified in ETSI TS 128 532 [3], clause 11.6.1.1. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.1.3 Procedures | File Management MnS Consumer configures a File Management MnS Provider to collect data files with specific characteristics that the File Management MnS Consumer desires, such as file-based Trace Data or PM Measurement Reports described in the Performance Assurance clause of the present document. After configuration, th... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.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 File Ready 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 "d... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.1.5 File Types Supported | File Type requirements are documented in ETSI TS 132 341 [8], clause 5.2. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.1.6 File Naming Requirements | Unless explicitly stated in the present document for particular File Types, the File Naming Convention specified in ETSI TS 132 342 [9] Annex A shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.2 List Available Files | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.2.1 Description | File Management MnS Consumer queries the File Management MnS Provider to identify files that are available on the File Management MnS Provider. Upon receipt of the available files and their locations, the File Management MnS Consumer can determine the next appropriate action. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.2.2 Requirements | Requirements on the types of files specified in clause 5.2 of ETSI TS 132 341 [8] shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.2.3 Procedures | List Available Files Use Case allows the File Management MnS Consumer to obtain a list of available files and their locations by reading the AvailableFileList IOC as specified in ETSI TS 132 342 [9]. A File Management MnS Consumer may use this management service in scenarios where the File Management MnS Provider is co... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.3 File Transfer to and from File Management MnS Provider | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.3.1 Description | The File Transfer by File Management MnS Consumer Use Case provides the capability for a File Management MnS Consumer to transfer files from or to the File Management MnS Provider. In this use case, File Management MnS Consumer is the client and File Management MnS Provider is the file server. The File Management MnS C... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.3.2 Requirements | File Transfer Requirements specified in clause 7.1.3 of ETSI TS 128 537 [4] shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.3.3 Procedures | Case 1: File Management MnS Consumer determines that a file needs to be transferred from the the location provided by the File Management MnS Provider as a result of receiving a notifyFileReady notification from the File Management MnS Provider (described in clause 6.5.1). Case 2: File Management MnS Consumer determine... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.4 Download File from remote file server | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.4.1 Description | The File Management MnS Consumer has a file that needs to be downloaded to the File Management MnS Provider such as: - Software file to upgrade software version executed on the File Management MnS Provider - Beamforming configuration file (Opaque Vendor specific data) ETSI ETSI TS 104 043 V11.0.0 (2024-06) 45 - Machine... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.4.2 Requirements | General File Download requirements specified in clause 7.4.3 of ETSI TS 128 537 [4] shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.4.3 Procedures | @startuml skin rose Title File Download autonumber "[0]" participant "File Management MnS Consumer" as NMS participant "File Management MnS Provider" as ME Participant "File Server" as FS NMS <-> ME : Establish Netconf Session NMS -> ME: NETCONF <rpc><file-download><remote-file-path> ME --> NMS: NETCONF <rpc-reply><fil... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.4.4 Operations and Notifications | A File Download notification shall be in one of the following formats: - SDO O1 format: - Either a 3GPP-specified notifyFileDownload or an O-RAN-specified o1NotifyFileDownload notification should be defined. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.5 File push from a MnS producer to a MnS consumer | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.5.1 Description | Refer to ETSI TS 128 537 [4] clause 7.3.1. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.5.2 Requirements | Requirements specified in ETSI TS 128 537 [4] clause 7.3.3 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.5.3 Procedures | @startuml skin rose participant "File Management MnS Consumer" as consumer participant "File Management MnS Producer" as producer participant "file server" as fs autonumber 1 consumer <--> producer: Establish NETCONF session consumer --> producer: NETCONF <rpc><file-push><remote-file-path> consumer <-- producer: NETCON... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.5.5.4 Operations and Notifications | A File Pushed notification shall be in one of the following formats: - SDO O1 format: - Either a 3GPP-specified notifyPush or an O-RAN-specified o1NotifyFilePush notification should be defined. - VES O1 format: - A Harmonized VES event, as specified in the VES Event Listener Specification [18], containing stndDefinedFi... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6 Heartbeat Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.0 Overview | Heartbeat MnS allow a Heartbeat MnS Provider to send heartbeats to the Heartbeat MnS Consumer and allow the Heartbeat MnS Consumer to configure the heartbeat services on the Heartbeat MnS Provider. Stage 1 Heartbeat MnS is specified in ETSI TS 128 537 [4]. This 3GPP specification is aligned with the Services Based Mana... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.1 Heartbeat Notification | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.1.1 Description | Heartbeat MnS Provider sends asynchronous heartbeat notifications to Heartbeat MnS Consumer at a configurable frequency to allow Heartbeat MnS Consumer to supervise the connectivity to the Heartbeat MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.1.2 Requirements | Requirements for heartbeat notifications specified in ETSI TS 128 537 [4], clause 4.2.2.2 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.1.3 Procedures | Procedures for heartbeat notifications are specified in ETSI TS 128 537 [4], clauses 4.3.2 and 4.3.3. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.1.4 Operations and Notifications | A Heartbeat notification shall be in one of the following formats: - SDO O1 format: - An O1-supported 3GPP-specified notifyHeartbeat 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.6.2 Heartbeat Control | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.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 Heartbeat MnS, a Heartbeat Control IOC is specified in ETSI TS 128 622 [7] that includes attributes to Get/Set Heartbeat Peri... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.2.2 Requirements | Requirements for heartbeat control specified in ETSI TS 128 537 [4], clause 4.2.2.1 shall apply. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 49 HeartbeatControl IOC definition shall be as specified in ETSI TS 128 622 [7], clause 4.3. YANG solution set for HeartbeatControl IOC shall be as in ETSI TS 128 623 [23], clause D.2.... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.2.3 Procedures | Procedures for heartbeat control are specified in ETSI TS 128 537 [4], clauses 4.3.1 and 4.3.2. NETCONF protocol and YANG data models are used to read and configure the heartbeatNtfPeriod and triggerHeartbeatNtf in the HeartbeatControl IOC. Refer to the Provisioning management services clause for procedures to read MOI... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.6.2.4 Void | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7 PNF Startup and Registration Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.0 Overview | PNF Startup and Registration management services allow a physical PNF Startup and Registration MnS Provider to acquire its network layer parameters either via static procedures (pre-configured in the element) or via dynamic procedures (Plug-n-Connect) during startup. During this process, the PNF Startup and Registratio... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.1 PNF Plug-n-Connect | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.1.1 Description | PNF Plug-n-Connect (PnC) scenario enables a PNF Startup and Registration MnS Provider to obtain the necessary start-up configuration to allow it to register with a PNF Startup and Registration MnS Consumer for subsequent management. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.1.2 Requirements | Specification requirement for Plug and Connect specified in ETSI TS 128 314 [1], clause 6.2.1 shall apply. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.1.3 Procedures | Functional elements involved in Plug and Connect Mns Service, for example, IP Autoconfiguration services, DNS server, Certification Authority server, Security gateway and Software and Configuration Server (SCS) are described in ETSI TS 128 315 [2], clause 4.2. Plug-and-Connect and related procedures are specified in ET... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.2 PNF Registration | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.2.1 Description | PNF Startup and Registration MnS Provider sends an asynchronous pnfRegistration or o1NotifyPNFRegistration event to a PNF Startup and Registration MnS Consumer after PnC to notify PNF Startup and Registration MnS Consumer of new PNF Startup and Registration MnS Provider to be managed. ETSI ETSI TS 104 043 V11.0.0 (2024... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.2.2 Requirements | REQ-PNFR-FUN-1: The PNF Startup and Registration MnS Provider shall support sending the PNF Registration Notifications (see clause 6.7.2.4) upon PNF reset and/or registration events resulting in O1 connection re-establishment. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.2.3 Procedures | PNF Registration procedures are illustrated by Figure 6.7.2.3-1. @startuml skin rose Title PNF Registration Notification Autonumber participant "PNF Startup and Registration MnS Consumer" as NMS participant " PNF Startup and Registration MnS Provider" as ME Note over ME : PnC completes ME ->> NMS : <<HTTP/TLS>> pnfRegi... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.7.2.4 Operations and Notifications | A PNF Registration notification can be either an o1NotifyPNFRegistration or a pnfRegistration event. They shall be in one of the following formats: o1NotifyPNFRegistration: - SDO O1 format: - The O-RAN-specified o1NotifyPnfRegistration notification defined in Table 6.7.2.4-1. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 51 T... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8 PNF Software Management Services | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.0 Overview | Software management services allow a PNF Software MnS Consumer to request a physical PNF Software MnS Provider to download, install, validate and activate a new software package and allow a physical PNF Software MnS Provider to report its software versions. ETSI ETSI TS 104 043 V11.0.0 (2024-06) 52 |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.1 Software Package Naming and Content | PNF Software Package naming, content and format are vendor specific and do not require standardization in O-RAN. A PNF Software Package contains one or more files. Some of the files in the Software Package are optional for the PNF (example: a file that has not changed version). The PNF is aware of the content and forma... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.2 Software Inventory | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.2.1 Description | The PNF Startup and Registration MnS Consumer sends a Software Inventory Request and retrieves information about the software packages on the PNF Software MnS Provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.2.2 Requirements | REQ-SWI-FUN-1: The PNF software management service provider shall have the capability to provide its authorized consumer information about the software packages on the PNF software management service provider. |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.2.3 Procedures | @startuml Title Software Inventory autonumber "[0]" participant "PNF Software MnS Consumer" as NMS participant "PNF Software MnS Provider" as ME NMS <-> ME : Establish NETCONF Session NMS -> ME: NETCONF <rpc> <get><filter> Note over ME : Retrieve Software Inventory Information ME --> NMS: NETCONF <rpc-reply> <data> NMS... |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.3 Software Download | |
3c44d6b4e93165c24c893e9e439c2e16 | 104 043 | 6.8.3.1 Description | Software Download triggers the download of a specific software package to the PNF Software MnS Provider. This download service includes integrity checks on the downloaded software and the installation of the software into the software slot corresponding to the softwarePackage MOI. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.