name: OAM
full_form: Operation and Maintenance
context: The feature is activated in the gNB either by direct configuration from the OAM system (management-based activation), or by signalling from the OAM via the 5GC (signalling-based activation), containing UE-associated QoE configuration. One or more QoE measurement collection jobs can be activated at a UE per service type, and each QoE measurement configuration is uniquely identified by a QoE reference. For signalling-based QoE measurements, the OAM initiates the QoE measurement activation for a specific UE via the 5GC, and the gNB receives one or more QoE measurement configurations by means of UE-associated signalling. The QoE measurement configuration for signalling-based activation includes an application layer measurement configuration list and the corresponding information for QoE measurement collection, e.g., QoE reference, service type, MCE IP address, slice scope, area scope, MDT alignment information, the indication of available RAN visible QoE metrics and assistance information. For management-based QoE measurement activation, the OAM sends one or more QoE measurement configurations directly to the gNB. The QoE measurement configuration for management-based activation also includes an application layer measurement configuration list and the corresponding information for QoE measurement collection. The gNB selects UE(s) that meet the required QoE measurement capability, area scope and slice scope. Application layer measurement configuration received by the gNB from OAM or 5GC is encapsulated in a transparent container, which is forwarded to a UE as Application layer configuration in the RRCReconfiguration message (there can be multiple configurations in the same message). Application layer measurement reports received from UE's application layer are encapsulated in a transparent container and sent to the network in the MeasurementReportAppLayer message, as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ]  [12]. The UE can send multiple application layer measurement reports to the gNB in one MeasurementReportAppLayer message. In order to allow the transmission of application layer measurement reports which exceed the maximum PDCP SDU size, segmentation of the MeasurementReportAppLayer message may be enabled by the gNB. A measurement configuration application layer ID conveyed in the RRC signalling is used to identify the application layer measurement configuration and report between the gNB and the UE. The measurement configuration application layer ID is mapped to the QoE reference in the gNB, and the gNB forwards the application layer measurement report to MCE together with the QoE reference. The gNB can release one or multiple application layer measurement configurations from the UE in one RRCReconfiguration message at any time. The UE may additionally be configured by the gNB to report when a QoE measurement session starts or stops for a certain application layer measurement configuration.
description: Operation and Maintenance (OAM) is a critical network function in the context of 5G networks, responsible for managing and configuring various aspects of the network. In the provided context, OAM plays a key role in activating Quality of Experience (QoE) measurements at the UE (User Equipment), either through direct configuration or via signalling from the 5GC (5G Core). The OAM system initiates QoE measurement activation for specific UEs and sends QoE measurement configurations to the gNB (gNodeB), which then forwards these configurations to the UE. This process enables the collection of QoE metrics, allowing for better network optimization and service quality assurance.
explanation: OAM is classified as a Network Function because it serves as a central component in managing and maintaining the network's operational aspects, including the activation and configuration of QoE measurements. Its role in signalling and configuring UEs and gNBs aligns with the responsibilities typically associated with network functions within 3GPP specifications.
section_title: 21.2.1 QoE Measurement Collection Activation and Reporting
biotag_Context: O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,B-Network,O,O,O,O,B-Measurement,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,B-Measurement,O,O,O,B-Measurement,O,O,B-Miscellaneous,O,O,B-Measurement,O,O,O,O,O,B-Device,O,O,O,O,O,B-Network Function,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,B-Measurement,O,O,O,B-Network Function,B-Protocol,O,O,O,O,O,B-Technology,O,O,O,O,O,O,B-Network,O,B-Measurement,O,O,O,O,O,O,B-Measurement,O,O,O,B-Miscellaneous,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,B-Network Function,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Miscellaneous,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Measurement,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Measurement,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,B-Measurement,I-Measurement,I-Measurement,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Miscellaneous,O,O,B-Measurement,O,O,O,O,B-Device,O,O,B-Measurement,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O