Quality of experience measurement in response to resumption procedure

Abstract

To provide a method that enables collection of Quality of Experience (QoE) measurements for different services, including streaming services.SOLUTION: User equipment (UE) receives a first radio resource control (RRC) message including a first configuration parameter of a first quality of experience (QoE) configuration and a second configuration parameter of a second QoE configuration, and then receives a RRC release message instructing transition of the UE from a RRC connected state to a RRC inactive state. The UE is in a connected state upon receiving the RRC release message. The UE further receives a RRC resume message from a second base station instructing transition of the UE from a RRC inactive state to a RRC connected state. The UE is in an inactive state when the RRC resume message is received, and releases the first QoE configuration and resumes the second QoE configuration in response to receiving the RRC resume message.SELECTED DRAWING: Figure 22

Description

[Technical field]

[0001] The present disclosure relates to a method for quality of experience (QoE) measurement and reporting. [Background technology]

[0002] Generally described, computing devices and communication networks can be used to exchange information. In a typical application, a computing device can request / send data to another computing device via a communication network. More specifically, a computing device can use a wireless communication network to exchange information or establish a communication channel.

[0003] A wireless communication network may include a wide variety of devices that include components for accessing or have access to the wireless communication network. Such devices may utilize the wireless communication network to facilitate interaction with other devices that may have access to the wireless communication network, or to facilitate interaction, via the wireless communication network, with devices that utilize other communication networks. Summary of the Invention

[0004] One embodiment of the present invention is a method for quality of experience (QoE) measurement and reporting, comprising the steps of receiving, by a user equipment (UE), a first Radio Resource Control (RRC) message including first configuration parameters of a first QoE configuration and second configuration parameters of a second QoE configuration, and receiving, by the UE, an RRC release message indicating a transition of the UE from an RRC connected state to an RRC inactive state, where the UE is in a connected state when the RRC release message is received; The method includes receiving, by the UE, an RRC resumption message from the second BS indicating a transition of the UE from an RRC inactive state to an RRC connected state, where the UE is in an inactive state when the RRC resumption message is received; and in response to receiving the RRC resumption message, releasing the first QoE configuration and resuming the second QoE configuration.

[0005] One embodiment of the present invention is a method for quality of experience (QoE) measurement and reporting, comprising the steps of: receiving, by a user equipment (UE), a first Radio Resource Control (RRC) message including configuration parameters for a QoE configuration, receiving an RRC release message indicating a transition of the UE from an RRC connected state to an RRC inactive state, receiving, by the UE, an RRC resume message indicating a transition of the UE from an RRC inactive state to an RRC connected state, and determining to discard or keep a QoE measurement report associated with the QoE configuration in response to the RRC resume message indicating that at least one first one of the configuration parameters has been updated.

[0006] One embodiment of the present invention is a method for quality of experience (QoE) measurement and reporting, the method including the steps of: transmitting, by a network, a first Radio Resource Control (RRC) message including first configuration parameters of a first QoE configuration and second configuration parameters of a second QoE configuration; transmitting, by the network, an RRC release message indicating a transition of a user equipment (UE) from an RRC connected state to an RRC inactive state, the UE being in a connected state when the RRC release message is received; and transmitting, by the network, from a second BS, an RRC resume message indicating a transition of the UE from an RRC inactive state to an RRC connected state, the UE being in an inactive state when the RRC resume message is received. In response to receiving the message, the first QoE configuration is released and the second QoE configuration is resumed.

[0007] One embodiment of the present invention is a method for quality of experience (QoE) measurement and reporting, the method including the steps of: transmitting, by a network, a first Radio Resource Control (RRC) message including configuration parameters of a QoE configuration, receiving an RRC release message indicating a transition of a user equipment (UE) from an RRC connected state to an RRC inactive state, and transmitting, by the network, an RRC resume message indicating a transition of the UE from an RRC inactive state to an RRC connected state, wherein the UE decides to discard or keep a QoE measurement report associated with the QoE configuration in response to the RRC resume message indicating that at least one first one of the configuration parameters has been updated. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of a mobile communication system in accordance with some aspects of various exemplary embodiments of the present disclosure. [Diagram 2] 2A and 2B illustrate example radio protocol stacks for the user plane and control plane in accordance with some aspects of various exemplary embodiments of the present disclosure. [Diagram 3] 3A, 3B, and 3C illustrate example mappings between logical channels and transport channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 4] 4A, 4B, and 4C are diagrams illustrating example mappings between transport channels and physical channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Diagram 5] 5A, 5B, 5C, and 5D are diagrams illustrating example radio protocol stacks for NR sidelink communications in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 6] FIG. 1 illustrates example physical signals in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 7] FIG. 2 illustrates an example of radio resource control (RRC) states and transitions between different RRC states in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 8] FIG. 2 illustrates an example frame structure and physical resources in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 9] 1A-1C are diagrams illustrating example component carrier configurations in different carrier aggregation scenarios in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 10] 1 illustrates an exemplary bandwidth portion configuration and switching in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 11] FIG. 1 illustrates an exemplary four-step contention-based and contention-free random access process in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 12] FIG. 1 illustrates an example two-step contention-based and contention-free random access process in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 13] FIG. 1 illustrates an example time and frequency structure of a synchronization signal and a physical broadcast channel (PBCH) block (SSB) in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 14] FIG. 1 illustrates an example SSB burst transmission according to some aspects of various exemplary embodiments of the present disclosure. [Figure 15]FIG. 1 illustrates example components of a user equipment and a base station for transmission and / or reception in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 16] FIG. 1 illustrates an example RRC connection release operation that was successful, in accordance with some aspects of various representative embodiments of the present disclosure. [Figure 17] FIG. 1 illustrates an example RRC connection resumption with successful operation in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 18] FIG. 1 illustrates an example RRC connection resumption fallback to a successfully operated RRC connection establishment, in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 19] FIG. 1 illustrates an example RRC connection resumption with subsequent network release that is successfully operated in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 20] FIG. 1 illustrates an example RRC connection resumption with successful operation and subsequent network interruption in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 21] FIG. 1 illustrates an example RRC connection resumption with network rejection, in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 22] FIG. 1 illustrates an example process according to some aspects of various exemplary embodiments of the present disclosure. [Figure 23] FIG. 1 illustrates an example process according to some aspects of various exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] 1 illustrates an example of a mobile communication system 100 according to some aspects of some of the various exemplary embodiments of the present disclosure. The mobile communication system 100 may be operated by a wireless communication system operator, such as a Mobile Network Operator (MNO), a private network operator, a Multi-System Operator (MSO), an Internet of Things (IOT) network operator, etc., and may provide services such as voice, data (e.g., wireless Internet access), messaging, vehicle communication services such as vehicle-to-everything (V2X) communication services, safety services, mission-critical services, services in residential, commercial, or industrial environments such as IoT, Industrial IOT (IIOT), etc.

[0010] The mobile communication system 100 can enable various types of applications with different requirements in terms of latency, reliability, throughput, etc. Examples of supported applications include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). eMBB can support stable connections with high peak data rates and moderate rates for cell-edge users. URLLC can support applications with stringent requirements in terms of latency and reliability, as well as moderate requirements in terms of data rates. An exemplary mMTC application includes a network of a large number of IoT devices that are only sporadically active and transmit small data payloads.

[0011] The mobile communication system 100 may include a radio access network (RAN) portion and a core network portion. In the example shown in FIG. 1, a Next Generation RAN (NG-RAN) 105 and a 5G 1, a 5G-Core Network (5GC) 110 is shown. Other examples of RAN and core network can be implemented without departing from the scope of this disclosure. Other examples of RAN include Evolved Universal Terrestrial Radio Access Network (EUTRAN), Universal Terrestrial Radio Access Network (UTRAN), etc. Other examples of core network include Evolved Packet Core (EPC), UMTS Core Network (UCN), etc. The RAN implements a radio access technology (RAT) and exists between the user equipment (UE) 125 and the core network. Examples of such RAT include New Radio (NR), Long Term Evolution (LTE), also known as Evolved Universal Terrestrial Radio Access (EUTRA), Universal Mobile Telecommunications System (UMTS), etc. The RAT of the example mobile communication system 100 may be NR. The core network exists between the RAN and one or more external networks (e.g., data networks) and is responsible for functions such as mobility management, authentication, session management, bearer setup, and application of different quality of service (QoS). The functional layer between the UE 125 and the RAN (e.g., the NG-RAN 105) may be referred to as an Access Stratum (AS), and the functional layer between the UE 125 and the core network (e.g., the 5GC 110) may be referred to as a Non-access Stratum (NAS).

[0012] The UE 125 may include wireless transmission and reception components for communicating with one or more nodes in the RAN, one or more relay nodes, or one or more other UEs, etc. Examples of UEs include, but are not limited to, smartphones, tablets, laptops, computers, wireless transmitting and / or receiving units in vehicles, V2X or vehicle-to-vehicle (V2V) devices, wireless sensors, IoT devices, IIOT devices, etc. Other names may be used for UEs, such as mobile stations (MSs), terminal equipment, terminal nodes, client devices, mobile devices, etc. Additionally, the UE 125 may also include components or subcomponents integrated into other devices, such as vehicles, to provide wireless communication capabilities with nodes in the RAN, other UEs, satellite communications, as described herein. Such other devices may have other functions or functions in addition to wireless communications. Thus, reference to a UE may include individual components that facilitate wireless communications, as well as the entire device incorporating components for facilitating wireless communications.

[0013] The RAN may include nodes (e.g., base stations) for communicating with UEs. For example, the NG-RAN 105 of the mobile communication system 100 may include nodes for communicating with the UE 125. Different names may be used for the RAN nodes depending, for example, on the RAT used for the RAN. The RAN nodes may be referred to as Node Bs (NBs) in a RAN using the UMTS RAT. The RAN nodes may be referred to as Evolved Node Bs (eNBs) in a RAN using the LTE / EUTRA RAT. In the illustrative example of the mobile communication system 100 of FIG. 1, the nodes of the NG-RAN 105 may be either Next Generation Node Bs (gNBs) 115 or Next Generation Evolved Node Bs (ng-eNBs) 120. In this specification, the terms base station, RAN node, gNB, and ng-eNB may be used interchangeably. The gNB 115 may provide NR user plane and control plane protocol terminations for the UE 125. The ng-eNB 120 may provide E-UTRA user plane and control plane protocol terminations for the UE 125. The interface between the gNB 115 and the UE 125 or between the ng-eNB 120 and the UE 125 may be referred to as a Uu interface. The Uu interface may be established using a user plane protocol stack and a control plane protocol stack. For the Uu interface, the direction from the base station (e.g., gNB 115 or ng-eNB 120) to the UE 125 may be referred to as a downlink, and the direction from the UE 125 to the base station (e.g., gNB 115 or ng-eNB 120) may be referred to as an uplink.

[0014] The gNB 115 and the ng-eNB 120 may be interconnected using an Xn interface. The Xn interface may include an Xn User Plane (Xn-U) interface and an Xn Control Plane (Xn-C) interface. The transport network layer of the Xn-U interface may be built on Internet Protocol (IP) transport, and GPRS Tunneling Protocol (GTP) may be used on User Datagram Protocol (UDP) / IP to carry user plane protocol data units (PDUs). Xn-U may provide non-guaranteed delivery of user plane PDUs and may support data forwarding and flow control. The transport network layer of the Xn-C interface may be built on Stream Control Transport Protocol (SCTP) on IP. The application layer signaling protocol may be referred to as Xn Application Protocol (XnAP). The SCTP layer may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission may be used to deliver the signaling PDUs. The Xn-C interface can support Xn interface management, UE mobility management including context transfer and RAN paging, and dual connectivity.

[0015] The gNB 115 and the ng-eNB 120 may also be connected to the 5GC 110 by an NG interface, more specifically to the Access and Mobility Management Function (AMF) 130 of the 5GC 110 by an NG-C interface, and to the User Plane Function (UPF) 135 of the 5GC 110 by an NG-U interface. The transport network layer of the NG-U interface may be built on IP transport and may carry user plane PDUs between the NG-RAN node (e.g., the gNB 115 or the ng-eNB 120) and the UPF 135 using the GTP protocol over UDP / IP. The NG-U may provide non-guaranteed delivery of user plane PDUs between the NG-RAN node and the UPF. The transport network layer of the NG-C interface may be built on IP transport. SCTP may be added on top of IP for reliable transmission of signaling messages. The application layer signaling protocol may be referred to as NG Application Protocol (NGAP). The SCTP layer may provide guaranteed delivery of application layer messages. For transport, IP layer point-to-point transmission may be used to deliver signaling PDUs. The NG-C interface can provide the following functions: NG interface management, UE context management, UE mobility management, forwarding of NAS messages, paging, PDU session management, configuration forwarding, and alert message transmission.

[0016] The gNB 115 or ng-eNB 120 provides the following functions: radio resource management functions such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in both uplink and downlink (e.g., scheduling), IP and Ethernet header compression of data, encryption and integrity protection, selection of the AMF at the UE attachment when routing to the AMF cannot be determined from information provided by the UE, routing of user plane data to the UPF, routing of control plane information to the AMF, connection setup and release, scheduling and transmission of paging messages, scheduling and transmission of system broadcast information (e.g., derived from the AMF), measurement and measurement reporting configuration for mobility and scheduling, transport level packet marking in the uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in RRC inactive state, NAS messages. The 5G LTE network may host one or more of the following functions: radio access network sharing, dual connectivity, close interaction between NR and E-UTRA, and maintaining security and radio configuration for user plane 5G system (5GS) Cellular IoT (CIoT) optimization.

[0017] The AMF130 may host one or more of the following functions: NAS signaling termination, NAS signaling security, AS security control, CN inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including validation of roaming rights, mobility management control (subscription and policy), support for network slicing, Session Management Function (SMF) selection, and 5GS CIoT optimization selection.

[0018] The UPF 135 may host one or more of the following functions: anchor point for intra / inter-RAT mobility (if applicable), external PDU session point of interconnection to data network, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, traffic usage reporting, uplink classifier supporting routing of traffic flows to data network, branching point to support multi-homed PDU sessions, QoS processing for user plane, e.g., packet filtering, gating, UL / DL rate enforcement, uplink traffic validation (Service Data Flow (SDF) to QoS flow mapping), and downlink packet buffering and downlink data notification triggering.

[0019] As shown in FIG. 1, the NG-RAN 105 may support a PC5 interface between two UEs 125 (e.g., UE 125A and UE 125B). In the PC5 interface, the direction of communication between the two UEs (e.g., from UE 125A to UE 125B or vice versa) may be referred to as a sidelink. Sidelink transmission and reception over the PC5 interface may be supported when the UE 125 is within the NG-RAN 105 coverage and when the UE is outside the NG-RAN 105 coverage, regardless of which RRC state the UE 125 is in. Support for V2X services over the PC5 interface may be provided by NR sidelink communication or V2X sidelink communication.

[0020] PC5-S signaling may be used for unicast link establishment with direct communication request / accept messages. A UE may self-assign a source Layer-2 ID for a PC5 unicast link, for example based on the V2X service type. During the unicast link establishment procedure, a UE may send its source Layer-2 ID for a PC5 unicast link to a peer UE, for example a UE for which a destination ID was received from a higher layer. The source Layer-2 ID and destination Layer-2 ID pair may uniquely identify a unicast link. A receiving UE may verify that said destination ID belongs to it and may accept the unicast link establishment request from the source UE. During the PC5 unicast link establishment procedure, PC5-RRC procedures on the access layer may be invoked for the purpose of UE sidelink context establishment as well as for AS layer configuration, capability exchange, etc. PC5-RRC signaling may enable the exchange of UE capabilities and AS layer configurations such as Sidelink radio bearer configurations between a pair of UEs for which a PC5 unicast link is established.

[0021] NR sidelink communication is based on the pairing of source Layer 2 ID and destination Layer 2 ID in an AS. For the RLC, one of three types of transmission modes (e.g., unicast transmission, groupcast transmission, and broadcast transmission) may be supported. The unicast transmission mode may be characterized by supporting one PC5-RRC connection between peer UEs for a pair, transmitting and receiving control information and user traffic between peer UEs in the sidelink, supporting sidelink HARQ feedback, supporting sidelink transmit power control, supporting RLC acknowledged mode (AM), and detecting radio link failure for the PC5-RRC connection. The groupcast transmission may be characterized by transmitting and receiving user traffic between UEs belonging to a group in the sidelink, and supporting sidelink HARQ feedback. The broadcast transmission may be characterized by transmitting and receiving user traffic between UEs in the sidelink.

[0022] For NR sidelink communication, a source Layer-2 ID, a destination Layer-2 ID, and a PC5 link identifier may be used. The source Layer-2 ID may be a link layer identity that identifies a device or group of devices that is the recipient of the sidelink communication frame. The destination Layer-2 ID may be a link layer identity that identifies a device that originates the sidelink communication frame. In some examples, the source Layer-2 ID and the destination Layer-2 ID may be assigned by a management function in the core network. The source Layer-2 ID may identify the source of the data in the NR sidelink communication. The source Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer, one bit string may be the LSB portion (8 bits) of the source Layer-2 ID and may be forwarded to the sender's physical layer. This may identify the source of the intended data in the sidelink control information and may be used for filtering the packets at the receiver's physical layer, and the second bit string may be the MSB portion (16 bits) of the source Layer-2 ID and may be carried in the medium access control (MAC) header. This may be used for filtering packets at the receiver's MAC layer. The destination Layer 2 ID may identify the target of the data in the NR sidelink communication. For NR sidelink communication, the destination Layer 2 ID may be 24 bits long and may be split into two bit strings at the MAC layer, one bit string may be the LSB part (16 bits) of the destination Layer 2 ID and may be forwarded to the sender's physical layer. This may identify the target of the intended data in the sidelink control information and may be used for filtering packets at the receiver's physical layer, and the second bit string may be the MSB part (8 bits) of the destination Layer 2 ID and may be carried in the MAC header. This may be used for filtering packets at the receiver's MAC layer. The PC5 link identifier may uniquely identify the PC5 unicast link in the UE for the lifetime of the PC5 unicast link.The PC5 link identifier may be used to indicate the PC5 unicast link for which a sidelink Radio Link Failure (RLF) declaration has been made and the PC5-RRC connection has been released.

[0023] 2A and 2B illustrate example radio protocol stacks for the user plane and control plane, respectively, according to some aspects of some of the various exemplary embodiments of the present disclosure. As shown in FIG. 2A, the protocol stack for the user plane of the Uu interface (between the UE 125 and the gNB 115) includes Service Data Adaptation Protocol (SDAP) 201 and SDAP 211, Packet Data Convergence Protocol (PDCP) 202 and PDCP 212, Radio Link Control (RLC) 203 and RLC 213, MAC 204 and MAC 214, and sublayers of Layer 2 and Physical (PHY) 205 and PHY 215 layers (Layer 1 is also referred to as L1).

[0024] The PHY 205 and PHY 215 provide a transport channel 244 to the MAC 204 and MAC 214 sublayers. , providing logical channels 243 to the RLC 203 and RLC 213 sublayers. The RLC 203 and RLC 213 sublayers provide RLC channels 242 to the PDCP 202 and PCP 212 sublayers. The PDCP 202 and PDCP 212 sublayers provide radio bearers 241 to the SDAP 201 and SDAP 211 sublayers. The radio bearers may be classified into two groups: Data Radio Bearers (DRBs) for user plane data and Signaling Radio Bearers (SRBs) for control plane data. The SDAP 201 and SDAP 211 sublayers provide QoS flows 240 to the 5GC.

[0025] The main services and functions of the MAC204 or MAC214 sublayer include mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC Service Data Units (SDUs) belonging to one or different logical channels to / from Transport Blocks (TBs) passed to / from the physical layer on the transport channels, scheduling information reporting, error correction with Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)), priority handling between UEs with dynamic scheduling, priority handling between logical channels of one UE with Logical Channel Prioritization (LCP), priority handling between overlapped resources of one UE, and padding. A single MAC entity may support multiple numerologies, transmission timings, and cells. Mapping restrictions in logical channel prioritization that control which numerologies, cells, and transmission timings a logical channel can use.

[0026] The HARQ function can ensure delivery between peer entities at Layer 1. If the physical layer is not configured for downlink / uplink spatial multiplexing, a single HARQ process can support one TB, and if the physical layer is configured for downlink / uplink spatial multiplexing, a single HARQ process can support one or multiple TBs.

[0027] The RLC 203 or RLC 213 sublayer can support three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC configuration may be per logical channel independent of the numerology and / or transmission time, and the Automatic Repeat Request (ARQ) may operate with any of the numerologies and / or transmission times for which the logical channel is configured.

[0028] The main services and functions of the RLC203 or RLC213 sublayer depend on the transmission mode (e.g., TM, UM, or AM) and may include transport of higher layer PDUs, sequence numbers independent of the PDCP sequence numbers (UM and AM), error correction with ARQ (AM only), segmentation (AM and UM) and resegmentation (AM only) of RLC SDUs, reassembly of SDUs (AM and UM), duplicate detection (AM only), RLC SDU discard (AM and UM), RLC re-establishment, and protocol error detection (AM only).

[0029] The automatic repeat request in the RLC 203 or RLC 213 sublayer may have the following characteristics: ARQ retransmits RLC SDUs or RLC SDU segments based on RLC status reports, polling for RLC status notification may be used if required by RLC, and the RLC receiver may also trigger an RLC status notification after detecting a missing RLC SDU or RLC SDU segment.

[0030] The main services and functions of the PDCP202 or PDCP212 sublayer are forwarding data (user plane or control plane), maintaining the PDCP sequence number (SN), , header compression and decompression using the Robust Header Compression (ROHC) protocol, header compression and decompression using the EHC protocol, encryption and decryption, integrity protection and integrity verification, timer-based SDU discard, split bearer routing, duplication, reordering and in-order delivery, out-of-order delivery, and duplicate discard.

[0031] The main services and functions of the SDAP 201 or SDAP 211 include mapping between QoS flows and data radio bearers, and marking QoS Flow IDs (QFIs) in both downlink and uplink packets. A single protocol entity of the SDAP may be configured for each individual PDU session.

[0032] As shown in FIG. 2B, the control plane protocol stack of the Uu interface (between UE 125 and gNB 115) includes the PHY layer (Layer 1), the MAC, RLC and PDCP sublayers of Layer 2, and further the RRC 206 and RRC 216 sublayers, as described above. The main services and functions of the RRC206 and RRC216 sublayers on the Uu interface include broadcasting of system information related to AS and NAS, paging initiated by 5GC or NG-RAN, establishment, maintenance and release of RRC connection between UE and NG-RAN (including adding, modifying and releasing carrier aggregation, and adding, modifying and releasing dual connectivity between NR or E-UTRA and NR), security functions including key management, establishment, configuration, maintenance and release of SRB and DRB, mobility functions (including handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, and inter-RAT mobility), QoS management functions, UE measurement reporting and reporting control, radio link failure detection and recovery, and forwarding of NAS messages between NAS and UE. The NAS207 and NAS227 layers are control protocols (terminated in the AMF on the network side) that perform functions such as authentication, mobility management, security control, etc.

[0033] Sidelink specific services and functions of the RRC sublayer over the Uu interface include configuration of sidelink resource allocation via system information or dedicated signaling, reporting of UE sidelink information, sidelink related measurement configuration and reporting, and reporting of UE assistance information for SL traffic patterns.

[0034] 3A, 3B, and 3C show example mappings between logical channels and transport channels in the downlink, uplink, and sidelink, respectively, according to some aspects of some of the various exemplary embodiments of the present disclosure. Different types of data transfer services may be provided by the MAC. Each logical channel type may be defined by what type of information is transferred. The logical channels may be classified into two groups: control channels and traffic channels. The control channels may be used only for transfer of control plane information. The Broadcast Control Channel (BCCH) is a downlink channel for broadcasting system control information. The Paging Control Channel (PCCH) is a downlink channel that carries paging messages. The Common Control Channel (CCCH) is a channel for transmitting control information between the UE and the network. This channel may be used for UEs that do not have an RRC connection with the network. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional channel that transmits dedicated control information between the UE and the network, and may be used by UEs that have an RRC connection. The traffic channels may be used only for transfer of user plane information. A Dedicated Traffic Channel (DTCH) is a point-to-point channel dedicated to one UE for transferring user information. A DTCH can exist in both the uplink and downlink. A Sidelink Control Channel (SCCH) is a channel used to transmit control information (e.g., PC5-RRC messages) from one UE to another UE. The Sidelink Traffic Channel (STCH) is a sidelink channel for transmitting user information from one UE to other UEs. The Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel for broadcasting sidelink system information from one UE to other UEs.

[0035] Downlink transport channel types include the Broadcast Channel (BCH), the Downlink Shared Channel (DL-SCH), and the Paging Channel (PCH). The BCH may be characterized by a fixed, predefined transport format and the need to be broadcast throughout the coverage area of ​​a cell, either as a single message or by beamforming different BCH instances. The DL-SCH may be characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmit power, the possibility of being broadcast throughout the cell, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for UE discontinuous reception (DRX) to enable UE power savings. The DL-SCH may be characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmit power, the possibility of being broadcast throughout the cell, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for UE discontinuous reception (DRX) to enable UE power savings. The PCH may be characterized by support for UE Discontinuous Reception (DRX) to enable UE power saving (DRX cycle indicated by the network to the UE), a requirement to be broadcast throughout the coverage area of ​​a cell, either as a single message or by beamforming different BCH instances, as well as being mapped to physical resources that can also be dynamically used for traffic / other control channels.

[0036] In the downlink, the following connections may exist between logical channels and transport channels: BCCH may be mapped to BCH, BCCH may be mapped to DL-SCH, PCCH may be mapped to PCH, CCCH may be mapped to DL-SCH, DCCH may be mapped to DL-SCH, and DTCH may be mapped to DL-SCH.

[0037] Uplink transport channel types include the Uplink Shared Channel (UL-SCH) and the Random Access Channel (RACH). The UL-SCH may be characterized by the possibility of using beamforming, support for dynamic link adaptation by varying transmit power and potentially modulation and coding, support for HARQ, and support for both dynamic and quasi-static resource allocation. The RACH may be characterized by limited control information and collision risk.

[0038] In the uplink, the following connections may exist between logical channels and transport channels: CCCH may be mapped to UL-SCH, DCCH may be mapped to UL-SCH, and DTCH may be mapped to UL-SCH.

[0039] Sidelink transport channel types include Sidelink Broadcast Channel (SL-BCH) and Sidelink Shared Channel (SL-SCH). The SL-BCH may be characterized by a predefined transport format. The SL-SCH supports unicast, groupcast, and broadcast transmissions, supports both UE autonomous resource selection and scheduled resource allocation by the NG-RAN, and is used when the UE is assigned resources by the NG-RAN. It may be characterized by support for both dynamic and semi-static resource allocation, support for HARQ, and support for dynamic link adaptation by varying transmit power, modulation, and coding.

[0040] In the sidelink, the following connections may exist between logical channels and transport channels: SCCH may be mapped to SL-SCH, STCH may be mapped to SL-SCH, and SBCCH may be mapped to SL-BCH.

[0041] 4A, 4B, and 4C illustrate example mappings between transport channels and physical channels in the downlink, uplink, and sidelink, respectively, according to some aspects of some of the various exemplary embodiments of the present disclosure. The physical channels in the downlink include a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), and a physical broadcast channel (PBCH). The PCH and DL-SCH transport channels are mapped to the PDSCH. The BCH transport channel is mapped to the PBCH. No transport channels are mapped to the PDCCH, and downlink control information (DCI) is transmitted via the PDCCH.

[0042] The physical channels in the uplink include the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). The UL-SCH transport channel may be mapped to the PUSCH, and the RACH transport channel may be mapped to the PRACH. No transport channel is mapped to the PUCCH, and uplink control information (UCI) is transmitted via the PUCCH.

[0043] The sidelink physical channels include the physical sidelink shared channel (PSSCH), the physical sidelink control channel (PSCCH), the physical sidelink feedback channel (PSFCH), and the physical sidelink broadcast channel (PSBCH). The physical sidelink control channel (PSCCH) may indicate the resources and other transmission parameters used by the UE for the PSSCH. The physical sidelink shared channel (PSSCH) may transmit TBs of the data itself, as well as control information such as HARQ procedures and CSI feedback triggers. At least six OFDM symbols in a slot may be used for PSSCH transmission. The physical sidelink feedback channel (PSFCH) may carry HARQ feedback over the sidelink from the UE that is the intended recipient of the PSSCH transmission to the UE that performed the transmission. The PSFCH sequence may be transmitted in one PRB repeated across two OFDM symbols near the end of the sidelink resources in the slot. The SL-SCH transport channel may be mapped to the PSSCH. The SL-BCH may be mapped to the PSBCH. Transport channels are not mapped to the PSFCH, but sidelink feedback control information (SFCI) may be mapped to the PSFCH. Transport channels are not mapped to the PSCCH, but sidelink control information (SCI) may be mapped to the PSCCH.

[0044] 5A, 5B, 5C, and 5D illustrate examples of radio protocol stacks for NR sidelink communications, according to some aspects of some of the various exemplary embodiments of the present disclosure. The AS protocol stack for the user plane in the PC5 interface (i.e., for STCH) may consist of SDAP, PDCP, RLC and MAC sublayers, and a physical layer. The user plane protocol stack is shown in FIG. 5A. For SBCCH in the PC5 interface, The AS protocol stack may consist of the RRC, RLC, MAC sublayers, and physical layer, as shown below in Figure 5B. To support the PC5-S protocol, PC5-S is placed above the PDCP, RLC, and MAC sublayers, and physical layer in the control plane protocol stack for SCCH for PC5-S, as shown in Figure 5C. The AS protocol stack for the control plane for SCCH for RRC in the PC5 interface consists of the RRC, PDCP, RLC, and MAC sublayers, and physical layer. The control plane protocol stack for SCCH for RRC is shown in Figure 5D.

[0045] Sidelink Radio Bearers (SLRBs) can be categorized into two groups: Sidelink Data Radio Bearers (SL DRBs) for user plane data and Sidelink Signalling Radio Bearers (SL SRBs) for control plane data. Separate SL SRBs using different SCCHs can be configured for PC5-RRC and PC5-S signalling, respectively.

[0046] The MAC sublayer can provide the following services and functions over the PC5 interface: radio resource selection, packet filtering, priority handling between uplink and sidelink transmissions for a given UE, and sidelink CSI reporting. Due to the restriction of logical channel prioritization in the MAC, only sidelink logical channels belonging to the same destination can be multiplexed into the MAC PDU for each unicast, groupcast, and broadcast transmission that may be associated with the destination. For packet filtering, a SL-SCH MAC header containing both source and destination Layer-2 ID parts may be added to the MAC PDU. The logical channel identifier (LCID) included within the MAC subheader can uniquely identify a logical channel within the combination of source Layer-2 ID and destination Layer-2 ID.

[0047] The services and functions of the RLC sublayer may be supported for the sidelink. Both RLC unacknowledged mode (UM) and acknowledged mode (AM) may be used for unicast transmission, while only UM may be used for groupcast or broadcast transmission. For UM, only one-way transmission may be supported for groupcast and broadcast.

[0048] The services and functions of the PDCP sublayer for the Uu interface may be supported for the sidelink with some restrictions: out-of-order delivery may only be supported for unicast transmission and may not support duplication over the PC5 interface.

[0049] The SDAP sublayer can provide the following services and functions over the PC5 interface: mapping between QoS flows and sidelink data radio bearers: There can be one SDAP entity per destination for one of unicast, groupcast and broadcast associated with the destination.

[0050] The RRC sublayer may provide the following services and functions over the PC5 interface: forwarding PC5-RRC messages between peer UEs, maintaining and releasing a PC5-RRC connection between two UEs, and detecting sidelink radio link failure for a PC5-RRC connection based on an indication from MAC or RLC. A PC5-RRC connection may be a logical connection between two UEs for a pair of source Layer-2 ID and destination Layer-2 ID that may be considered established after a corresponding PC5 unicast link is established. There may be a one-to-one correspondence between PC5-RRC connections and PC5 unicast links. A UE may establish a PC5-RRC connection for different pairs of source Layer-2 ID and destination Layer-2 ID. A peer UE may have multiple PC5-RRC connections with one or multiple UEs for the same sidelink. Separate PC5-RRC procedures and messages may be used for the UE to transfer UE capabilities and sidelink configuration, including the SL-DRB configuration, to the peer UE. Both peer UEs may exchange their UE capabilities and sidelink configuration using separate bidirectional procedures in both sidelink directions.

[0051] FIG. 6 illustrates example physical signals in the downlink, uplink, and sidelink according to some aspects of some of the various exemplary embodiments of the present disclosure. Demodulation reference signals (DM-RS) may be used in the downlink, uplink, and sidelink and may be used for channel estimation. DM-RS is a UE-specific reference signal that may be transmitted with the downlink, uplink, or sidelink physical channel and may be used for channel estimation and coherent detection of the physical channel. Phase tracking reference signals (PT-RS) may be used in the downlink, uplink, and sidelink and may be used to track phase and mitigate performance loss due to phase noise. PT-RS may be primarily used to estimate and minimize the impact of common phase error (CPE) on system performance. Due to phase noise characteristics, PT-RS signals may have low density in the frequency domain and high density in the time domain. PT-RS may occur when PT-RS is configured to exist in combination with DM-RS. Positioning reference signals (PRS) may be used in the downlink for positioning with different positioning techniques. The PRS may be used to measure the delay of the downlink transmission by correlating the received signal from the base station with a local replica in the receiver. The Channel State Information Reference Signal (CSI-RS) may be used in the downlink and the sidelink. The CSI-RS may be used for, among other things, channel state estimation, Reference Signal Received Power (RSRP) measurement for mobility and beam management, time / frequency tracking for demodulation. The CSI-RS may be configured UE-specific, but multiple users may share the same CSI-RS resource. The UE may determine the CSI reports and transmit these in the uplink to the base station using the PUCCH or PUSCH. The CSI reports may be carried in the sidelink MAC CE. The Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) may be used for radio frame synchronization. The PSS and SSS may be used for cell search procedures during initial attach or for mobility purposes.A Sounding Reference Signal (SRS) may be used in the uplink for uplink channel estimation. Similar to CSI-RS, the SRS can serve as a QCL reference for other physical channels, such that it may be configured to be transmitted quasi-collocated with the SRS. Sidelink PSS (S-PSS) and Sidelink SSS (S-SSS) may be used in the sidelink for sidelink synchronization.

[0052] FIG. 7 illustrates an example of radio resource control (RRC) states and transitions between different RRC states according to some aspects of some of the various exemplary embodiments of the present disclosure. A UE may be in one of three RRC states: an RRC connected state 710, an RRC idle state 720, and an RRC inactive state 730. After powering on, the UE may be in the RRC idle state 720, and the UE may use initial access to establish a connection with the network via an RRC connection establishment procedure to perform data transfer and / or voice calls. Once the RRC connection is established, the UE may be in the RRC connected state 710. The UE can transition from the RRC idle state 720 to the RRC connected state 710 or from the RRC connected state 710 to the RRC idle state 720 using an RRC connection establishment / release procedure 740.

[0053] To reduce the signaling load and latency resulting from frequent transitions from the RRC connected state 710 to the RRC idle state 720 when the UE transmits frequent small data. To achieve this, an RRC inactive state 730 may be used. In the RRC inactive state 730, the AS context may be stored by both the UE and the gNB. This may result in a faster state transition from the RRC inactive state 730 to the RRC connected state 710. The UE may transition from the RRC inactive state 730 to the RRC connected state 710 or from the RRC connected state 710 to the RRC inactive state 730 using an RRC connection resume / deactivation procedure 760. The UE may transition from the RRC inactive state 730 to the RRC idle state 720 using an RRC connection release procedure 750.

[0054] FIG. 8 illustrates an example frame structure and physical resources according to some aspects of some of the various exemplary embodiments of the present disclosure. Downlink or uplink or sidelink transmissions may be organized into frames with a 10 ms duration consisting of ten 1 ms subframes. Each subframe may consist of 1, 2, 4, ... slots, and the number of slots per subframe may depend on the subcarrier spacing of the carrier on which the transmission takes place. The slot duration may be 14 symbols with a normal cyclic prefix (CP) and 12 symbols with an extended CP, and may be scaled in time depending on the subcarrier spacing used such that there is an integer number of slots in a subframe. FIG. 8 illustrates a resource grid in the time and frequency domain. Each element of the resource grid containing one symbol in time and one subcarrier in frequency is called a resource element (RE). A resource block (RB) may be defined as 12 consecutive subcarriers in the frequency domain.

[0055] In some examples, with non-slot-based scheduling, the transmission of a packet may occur over a portion of a slot, e.g., during 2, 4, or 7 OFDM symbols, which may also be referred to as a minislot. Minislots may be used for low latency applications such as URLLC and operation in unlicensed bands. In some embodiments, minislots may also be used for fast flexible scheduling of services (e.g., preemption of URLLC for eMBB).

[0056] FIG. 9 illustrates examples of component carrier configurations in different carrier aggregation scenarios according to some aspects of some of the various exemplary embodiments of the present disclosure. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A UE may receive or transmit simultaneously on one or more CCs depending on its capabilities. CA may be supported for both contiguous and non-contiguous CCs in the same band or different bands as illustrated in FIG. 9. The gNB and the UE may communicate using a serving cell. The serving cell may be associated with at least one downlink CC (e.g., may be associated with only one downlink CC or may be associated with a downlink CC and an uplink CC). The serving cell may be a primary cell (PCell) or a secondary cCell (SCell).

[0057] The UE can adjust the timing of its uplink transmission using an uplink timing control procedure. The timing advance (TA) can be used to adjust the uplink frame timing relative to the downlink frame timing. The gNB can determine a desired timing advance setting and provide it to the UE. The UE can use the provided TA to determine its uplink transmit timing relative to the UE's observed downlink receive timing.

[0058] In the RRC connected state, the gNB may be responsible for maintaining the timing advance to keep L1 synchronized. Serving cells that have uplinks to which the same timing advance applies and that use the same timing reference cell are grouped together in a timing advance group ( The serving cells are grouped into TAGs (primary TAGs). A TAG may contain at least one serving cell with a configured uplink. The mapping of serving cells to TAGs may be configured by RRC. For primary TAG, the UE may use the PCell as the timing reference cell, except for shared spectrum channel access where the SCell may possibly also be used as the timing reference cell. For secondary TAG, the UE may use any of the activated SCells of this TAG as the timing reference cell and may not need to change this unless necessary.

[0059] Timing advance updates may be signaled by the gNB to the UE via a MAC CE command. Such a command may restart a TAG-specific timer that may indicate whether L1 may be synchronized or not; when the timer is running, L1 may be considered synchronized, otherwise L1 may be considered unsynchronized (uplink transmissions may only occur on the PRACH in this case).

[0060] A UE with single timing advance capability for CA may simultaneously receive and / or transmit multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into one TAG) sharing the same timing advance. A UE with multiple timing advance capability for CA may simultaneously receive and / or transmit multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into multiple TAGs) with different timing advances. NG-RAN may ensure that each TAG contains at least one serving cell. A non-CA capable UE may receive on a single CC and transmit on a single CC corresponding to only one serving cell (one serving cell in one TAG).

[0061] The multi-carrier property of the physical layer in case of CA may be exposed to the MAC layer, and one HARQ entity may be required per serving cell. If CA is configured, the UE may have one RRC connection with the network. In RRC connection establishment / re-establishment / handover, one serving cell (e.g., PCell) may provide NAS mobility information. Depending on the UE capabilities, the SCell may be configured to form a set of serving cells together with the PCell. The set of serving cells configured for the UE may consist of one PCell and one or multiple SCells. Reconfiguration, addition, and removal of SCells may be performed by RRC.

[0062] In a dual connectivity scenario, a UE may be configured with multiple cells including a Master Cell Group (MCG) for communicating with a master base station, a Secondary Cell Group (SCG) for communicating with a secondary base station, and two MAC entities, one for the MCG for communicating with the master base station and one for the SCG for communicating with the secondary base station.

[0063] FIG. 10 illustrates an example bandwidth portion configuration and switching according to some aspects of some of the various exemplary embodiments of the present disclosure. A UE may be configured with one or more bandwidth portions (BWPs) 1010 in a given component carrier. In some examples, one of the one or more bandwidth portions may be active at a time. The active bandwidth portion may define the UE's operating bandwidth within the operating bandwidth of the cell. For initial access, an initial bandwidth portion 1020 determined from system information may be used until a configuration of the UE in the cell is received. In bandwidth adaptation (BA), for example, by BWP switching 1040, the UE's receiving and transmitting bandwidths may not be as large as the cell's bandwidth and may be adjusted. For example, the widths may be ordered to change (e.g., shrink during low activity periods to save power), the positions may be moved in the frequency domain (e.g., to increase scheduling flexibility), the subcarrier spacing may be changed, and so on. The first active BWP 1020 may be the active BWP upon RRC (re)configuration of the PCell or activation of the SCell.

[0064] For a downlink BWP or an uplink BWP in a set of downlink or uplink BWPs, respectively, the UE may be provided with the following configuration parameters: subcarrier spacing (SCS), cyclic prefix, common RBs and a number of consecutive RBs, an index in the set of downlink or uplink BWPs by the respective BWP-Id, a set of BWP common parameters and a set of BWP-specific parameters. The BWP may be associated with an OFDM numerology according to the subcarrier spacing and cyclic prefix configured for the BWP. For the serving cell, the UE may be provided with a default downlink BWP among the configured downlink BWPs. If the UE is not provided with a default downlink BWP, the default downlink BWP may be the initial downlink BWP.

[0065] A downlink BWP may be associated with a BWP inactivity timer. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is configured, the UE may perform a BWP switch to the default BWP. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is not configured, the UE may perform a BWP switch to an initial downlink BWP.

[0066] FIG. 11 illustrates an exemplary 4-step contention-based and contention-free random access process according to some aspects of various exemplary embodiments of the present disclosure. FIG. 12 illustrates an exemplary 2-step contention-based and contention-free random access process according to some aspects of various exemplary embodiments of the present disclosure. The random access procedure can be triggered by several events, such as initial access from an RRC idle state, an RRC connection re-establishment procedure, downlink or uplink data arrival during an RRC connected state when the uplink synchronization state is "unsynchronized", uplink data arrival during an RRC connected state when there are no PUCCH resources available for a Scheduling Request (SR), an SR failure, a request by RRC upon synchronization reconfiguration (e.g., handover), a transition from an RRC inactive state, establishing time alignment of the secondary TAG, a request for other system information (SI), beam failure recovery (BFR), and a consistent uplink listen-before-talk (LBT) failure on the PCell.

[0067] Two types of random access (RA) procedures can be supported: a four-step RA type with MSG1 and a two-step RA type with MSGA. Both types of RA procedures can support contention-based random access (CBRA) and contention-free random access (CFRA), as shown in Figures 11 and 12.

[0068] The UE may select a type of random access at the start of a random access procedure based on the network configuration. If CFRA resources are not configured, the RSRP threshold may be used by the UE to select between a 2-step RA type and a 4-step RA type. If CFRA resources for a 4-step RA type are configured, the UE may perform random access using the 4-step RA type. If CFRA resources for a 2-step RA type are configured, the UE may perform random access using the 2-step RA type.

[0069] MSG1 of the 4-step RA type may consist of a preamble in the PRACH. After MSG1 transmission, the UE may monitor for a response from the network within a configured window. In the case of CFRA, a dedicated preamble for MSG1 transmission is assigned by the network, and upon receiving a random access response (RAR) from the network, the UE may terminate the random access procedure as illustrated in FIG. 11. In the case of CBRA, upon receiving the random access response, the UE may transmit MSG3 using the uplink grant scheduled in the random access response and may monitor contention resolution as illustrated in FIG. 11. If contention resolution is not successful after MSG3 (re)transmission, the UE may return to MSG1 transmission.

[0070] The MSGA of the two-step RA type may include a preamble in the PRACH and a payload in the PUSCH. After the MSGA transmission, the UE may monitor for a response from the network within a configured window. In the case of CFRA, a dedicated preamble and PUSCH resources may be configured for the MSGA transmission, and upon receiving a network response, the UE may terminate the random access procedure as shown in FIG. 12. In the case of CBRA, if the contention resolution is successful upon receiving the network response, the UE may terminate the random access procedure as shown in FIG. 12, while if a fallback indication is received in the MSGB, the UE may perform an MSG3 transmission using the uplink grant scheduled with the fallback indication and monitor the contention resolution. If the contention resolution is not successful after the MSG3 (re)transmission, the UE may return to the MSGA transmission.

[0071] FIG. 13 illustrates an example time and frequency structure of a synchronization signal and a physical broadcast channel (PBCH) block (SSB) according to some aspects of some of the various exemplary embodiments of the present disclosure. The SS / PBCH block (SSB) may consist of a primary synchronization signal and a secondary synchronization signal (PSS, SSS), each occupying one symbol and 127 subcarriers (e.g., subcarrier numbers 56 to 182 in FIG. 13), and a PBCH that spans three OFDM symbols and 240 subcarriers, but leaves an unused portion in the middle for the SSS on one symbol as shown in FIG. 13. The possible time positions of the SSBs within a half frame may be determined by the subcarrier spacing, and the periodicity of the half frame in which the SSBs are transmitted may be configured by the network. During a half frame, different SSBs may be transmitted in different spatial directions (i.e., using different beams spanning the coverage area of ​​the cell).

[0072] The PBCH may be used to carry a Master Information Block (MIB) used by the UE during cell search and initial access procedures. The UE may first decode the PBCH / MIB to receive other system information. The MIB may provide the UE with the parameters required to acquire System Information Block 1 (SIB1), more specifically, the information required to monitor the PDCCH for scheduling the PDSCH carrying SIB1. In addition, the MIB may indicate cell barring status information. The MIB and SIB1 may be collectively referred to as Minimum System Information (SI), and SIB1 may be referred to as Remaining Minimum System Information (RMSI). The other System Information Blocks (SIBs) (e.g., SIB2, SIB3, ..., SIB10, and SIBpos) may be referred to as other SIs. Other SI may be broadcast periodically on the DL-SCH, may be broadcast on demand on the DL-SCH (e.g., upon request from a UE in RRC idle, RRC inactive, or RRC connected state), or may be sent in a dedicated manner to RRC connected UEs on the DL-SCH (e.g., upon request, if configured by the network, from a UE in RRC connected state, or if the UE has an active BWP for which a common search space is not configured).

[0073] FIG. 14 is a block diagram of a system for storing a plurality of exemplary embodiments of the present disclosure according to some aspects of the present disclosure. 1 illustrates an exemplary SSB burst transmission. The SSB burst may include N SSBs, and each SSB of the N SSBs may correspond to a beam. The SSB burst may be transmitted according to a periodicity (e.g., SSB burst period). During a contention-based random access process, the UE may perform a random access resource selection process, in which the UE first selects an SSB before selecting an RA preamble. The UE may select an SSB with an RSRP above a configured threshold. In some embodiments, the UE may select any SSB if an SSB with an RSRP above a configured threshold is not available. A set of random access preambles may be associated with the SSB. After selecting the SSB, the UE may select a random access preamble from the set of random access preambles associated with the SSB, and may transmit the selected random access preamble to initiate the random access process.

[0074] In some embodiments, a beam among the N beams may be associated with a CSI-RS resource. The UE may measure the CSI-RS resource and select a CSI-RS with an RSRP above a configured threshold. The UE may select a random access preamble corresponding to the selected CSI-RS and transmit the selected random access process to initiate the random access process. If there is no random access preamble associated with the selected CSI-RS, the UE may select a random access preamble corresponding to an SSB quasi-co-located with the selected CSI-RS.

[0075] In some embodiments, based on the UE measurements of CSI-RS resources and the UE CSI report, the base station can determine a transmission configuration indication (TCI) state and can indicate the TCI state to the UE, and the UE can use the indicated TCI state for reception of downlink control information (e.g., via PDCCH) or data (e.g., via PDSCH). The UE can use the indicated TCI state to use an appropriate beam for reception of data or control information. The indication of the TCI state may be using an RRC configuration or a combination of RRC signaling and dynamic signaling (e.g., via a MAC Control Element (MAC CE) and / or based on the value of a field in the downlink control information that schedules the downlink transmission). The TCI state can indicate a quasi-co-location (QCL) relationship between a downlink reference signal, such as a CSI-RS, and a DM-RS associated with a downlink control or data channel (e.g., PDCCH or PDSCH, respectively).

[0076] In some embodiments, the UE may be configured with a list of up to M TCI-state configurations using a physical downlink shared channel (PDSCH) configuration parameter to decode the PDSCH according to the detected PDCCH with DCI for the UE and a given serving cell, where M may depend on the UE capabilities. Each TCI-State may include parameters to configure a QCL relationship between one or two downlink reference signals and a DM-RS port of the PDSCH, a DM-RS port of the PDCCH, or a CSI-RS port of the CSI-RS resource. The quasi-collocation relationship may be configured by one or more RRC parameters. The quasi-collocation type corresponding to each DL RS may take one of the following values: "QCL-TypeA": {Doppler shift, Doppler spread, average delay, delay spread}, "QCL-TypeB": {Doppler shift, Doppler spread}, "QCL-TypeC": {Doppler shift, average delay}, "QCL-TypeD": {Spatial Rx parameters}. The UE may receive an activation command (eg, MAC CE) used to map the TCI state to a codepoint in the DCI field.

[0077] FIG. 15 illustrates example components of user equipment and base stations for transmission and / or reception in accordance with some aspects of some of the various exemplary embodiments of the present disclosure. In one embodiment, the example components of FIG. 15 can be considered to be illustrative of the functional blocks of an example base station 1505. In another embodiment, the example components of FIG. 15 can be considered to be illustrative of the functional blocks of an example user equipment 1500. Thus, the components illustrated in FIG. 15 are not necessarily limited to either user equipment or base stations.

[0078] The antenna 1510 may include one or more antenna elements and may enable different input / output antenna configurations including a multiple-input multiple-output (MIMO), a multiple-input single-output (MISO) and a single-input multiple-output (SIMO) configuration. In some embodiments, the antenna 150 may enable a massive MIMO configuration having tens or hundreds of antenna elements. The antenna 1510 may enable other multi-antenna techniques such as beamforming. In some examples, depending on the capabilities of the UE 1500 or the type of the UE 1500 (e.g., a low complexity UE), the UE 1500 may support only a single antenna.

[0079] The transceiver 1520 can communicate bidirectionally over wireless links as described herein via the antenna 1510. For example, the transceiver 1520 may represent a wireless transceiver in a UE and may communicate bidirectionally with a wireless transceiver in a base station, or vice versa. The transceiver 1520 can include a modem for modulating packets, providing the modulated packets to the antenna 1510 for transmission, and demodulating packets received from the antenna 1510.

[0080] The memory 1530 can include RAM and ROM. The memory 1530 can store computer readable computer executable code 1535 including instructions that, when executed, cause the processor to perform various functions described herein. In some examples, the memory 1530 can include a basic input / output system (BIOS) that can control basic hardware or software operations such as interaction with peripheral components or devices, among other things.

[0081] The processor 1540 may include a hardware device having processing capabilities (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some examples, the processor 1540 may be configured to operate a memory using a memory controller. In other examples, the memory controller may be integrated into the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1530) to cause the UE 1500 or the base station 1505 to perform various functions.

[0082] A central processing unit (CPU) 1550 may perform basic arithmetic, logic, control, and input / output (I / O) operations specified by computer instructions in memory 1530. User equipment 1500 and / or base station 1505 may include additional peripheral components such as a graphics processing unit (GPU) 1560 and a global positioning system (GPS) 1570. GPU 1560 is dedicated circuitry for rapid manipulation and modification of memory 1530 to accelerate processing performance of user equipment 1500 and / or base station 1505. GPS 1570 may be used to enable location-based services or other services, for example, based on the geographic location of user equipment 1500.

[0083] In some examples, the purpose of the connection release procedure may be to release the RRC connection. Illustratively, this may include the release of established radio bearers, BH RLC channels, as well as all radio resources. Furthermore, in some embodiments, this may include the suspension of established radio bearers, and in case of SRB2 and at least one DRB, or IAB, may include suspending the RRC connection only if SRB2 is set up. An example of an RRC connection release with normal operation is shown in FIG. 16.

[0084] In some examples, the network may initiate an RRC connection release procedure to transition a UE in RRC_CONNECTED to RRC_IDLE. In other examples, the network may initiate an RRC connection release procedure to transition a UE in RRC_CONNECTED to RRC_INACTIVE only if SRB2 and at least one DRB, or in case of IAB, SRB2 is set up in RRC_CONNECTED. In yet another example, the network may initiate an RRC connection release procedure to transition a UE in RRC_INACTIVE back to RRC_INACTIVE when the UE is about to resume. Still further, in yet another example, the network may initiate an RRC connection release procedure to transition a UE in RRC_INACTIVE to RRC_IDLE when the UE is about to resume. In some examples, this procedure may be used to release and redirect a UE to another frequency.

[0085] In some examples, an RRC release message may be used to command the release of an RRC connection or the suspension of an RRC connection. In some examples, the field / IE suspend configuration may indicate the configuration of an RRC_INACTIVE state. The network may not configure the suspend configuration if the network redirects the UE to an inter-RAT carrier frequency or if the UE is configured with a DAPS bearer. In some examples, the field / IE ran-NotificationAreaInfo may be used by the network to ensure that a UE in RRC_INACTIVE always has a valid ran-NotificationAreaInfo. In some examples, the field / IE ran-PagingCycle may refer to a UE-specific cycle for RAN initiated paging. The field t380 may refer to a timer that triggers a periodic RNAU procedure in the UE.

[0086] In some examples, the purpose of the RRC connection resumption procedure may be to resume an interrupted RRC connection, including resuming SRBs and DRBs, or performing an RNA update.

[0087] In some examples, the UE may initiate this procedure when higher layers or the AS (when responding to RAN paging, when triggering an RNA update while the UE is in RRC_INACTIVE, or for NR sidelink / V2X sidelink communications) may request resumption of an interrupted RRC connection.

[0088] The UE may ensure that it has valid and up-to-date required system information before initiating this procedure. An exemplary RRC connection resumption with successful operation is shown in Figure 17. An exemplary RRC connection resumption fallback to RRC connection establishment with normal operation is shown in Figure 18. An exemplary RRC connection resumption followed by network release with successful operation is shown in Figure 19. An exemplary RRC connection resumption followed by network interruption with successful operation is shown in Figure 20. An exemplary RRC connection resumption with network rejection is shown in Figure 21.

[0089] In some examples, an RRC resume message may be used to resume a suspended RRC connection. The RRC resume message may illustratively be used in accordance with one or more aspects of the present application. The field / IE may include information to be utilized accordingly. The field / IE masterCellGroup may be used for configuration of the master cell group. The field / IE Radio Bearer Configuration may be used for configuration of radio bearers (DRB, SRB) including SDAP / PDCP. The field / IE Radio Bearer Configuration 2 may be used for configuration of radio bearers (DRB, SRB) including SDAP / PDCP. This field may be used if the UE supports NR-DC or NE-DC. The field / IE restoreMCG-SCell, if stored, may indicate that the UE can restore MCG SCell from the UE inactive AS context. The field / IE restoreSCG, if stored, may indicate that the UE can restore SCG configuration from the UE inactive AS context.

[0090] In some examples, the RRC resumption complete message may be used to confirm that the RRC connection resumption has been successfully completed.

[0091] In some examples, the RRC Resume Request message may be used to request the resumption of a suspended RRC connection or to perform an RNA update. The field / IE resume cause may provide a resume cause for the RRC connection resume request provided by higher layers or the RRC. The network may not be expected to reject the RRC resume request due to an unknown cause value being used by the UE. The field / IE resumeIdentity may indicate a UE identity to facilitate UE context lookup at the gNB. The field / IE resumeMAC-I may indicate an authentication token to facilitate UE authentication at the gNB. The 16 least significant bits of the MAC-I may be calculated using the AS security configuration.

[0092] In some examples, the RRC Resume Request 1 message may be used to request the resumption of a suspended RRC connection or to perform an RNA update. The field / IE resume cause may provide the resume cause of the RRC Resume Request 1 provided by higher layers or the RRC. The gNB may not be expected to reject the RRC Resume Request 1 since an unknown cause value is used by the UE. The field / IE resumeIdentity may indicate a UE identity to facilitate UE context lookup at the gNB. The field / IE resumeMAC-I may indicate an authentication token to facilitate UE authentication at the gNB. The 16 least significant bits of the MAC-I may be calculated using the AS security configuration.

[0093] In some examples, an RRC Setup message may be used to establish SRB1. The fields / IE Master Cell Group may be used by the network to configure only the RLC bearers for SRB1, mac-cell group configuration, physical cell group configuration, and sp cell configuration. The fields / IE Radio Bearer Configuration and SRB1 may be configured in the RRC setup.

[0094] In some examples, an RRC configuration request message may be used to request establishment of an RRC connection. The field / IE Establishment Cause may provide the establishment cause of the RRC configuration request according to information received from higher layers. The gNB may not be expected to reject the RRC configuration request because an unknown cause value is used by the UE. The field / IE UE-Identity may indicate the UE identity, which is included to facilitate contention resolution by lower layers.

[0095] Exemplary embodiments can enable quality of experience (QoE) measurement collection for different services, including streaming services. Exemplary QoE management can collect experience parameters for streaming services as well as Augmented Reality / Virtual Reality (AR / VR) and URLLC. It can be collected.

[0096] In some exemplary embodiments, the QoE measurements may enable collection of user KPI information, such as end-to-end (E2E) reliability statistical indicators.

[0097] In some examples, different types of UEs may have different QoE requirements. In some examples, QoE parameters may be defined as UE-specific and service-related. In some examples, QoE may be used as a criterion for evaluating network quality. In the past, there have been QoE metrics related to throughput, capacity, and coverage for performance evaluation of network solutions. Exemplary embodiments may enable triggering, configuration, and reporting mechanisms for QoE measurement collection, including relevant entities (e.g., UE, network entities).

[0098] In some examples, signaling-based and management-based mechanisms may be used for QoE-related signaling. In some examples, application layer measurement configurations received from the OAM or CN may be encapsulated in transparent containers that may be forwarded to the UE in downlink RRC messages. Application layer measurements received from higher layers in the UE may be encapsulated in transparent containers and sent to the network in uplink RRC messages.

[0099] In some instances, the RAN may release an ongoing QoE measurement / reporting configuration, for example when handing over to a network that does not support this.

[0100] In some examples, regions may be defined and / or configured for QoE measurement and / or reporting. In some examples, for region handling, the network may track if the UE is inside or outside the region and configure / release the configuration accordingly. In some examples, the network may track if the UE is in or out of the region and the UE may manage QoE start / stop accordingly. In some examples, the UE may do a region check (the UE may have a region configuration) and manage QoE start / stop accordingly.

[0101] In some examples, QoE measurement in an RRC inactive state may be supported for an MBS. In some examples, QoE measurement in an RRC idle state may be supported for an MBS.

[0102] In some examples, the management-based QoE configuration may not override the signaling-based QoE configuration.

[0103] In some examples, the QoE report may be transmitted over another SRB (apart from the current SRB) in NR, since this report may have a lower priority than other SRB transmissions.

[0104] In some examples, configuration and reporting for multiple simultaneous QoE measurements for a UE may be supported.

[0105] In some examples, RRC signaling may be used by the gNB to instruct the UE to suspend or resume QoE reporting.

[0106] In some instances, the pause / resume may be for all QoE reports. Alternatively, it may be for each QoE configuration.

[0107] In some examples, the QoE measurements may be configured in an RRC reconfiguration message.

[0108] In some examples, the configuration of the QoE measurements may be within other configuration information elements in the RRC reconfiguration message.

[0109] In some examples, the configuration of QoE measurements may be by list (eg, RRC list parameter) to allow configuration of multiple simultaneous measurements.

[0110] In some examples, in the case of RRC, an ID may be used to identify the measurement. In some examples, this ID may be a QoE Reference ID.

[0111] In some examples, SRB4 may be used for transmitting QoE reports in NR.

[0112] In some examples, the measurement report application layer of an RRC message may be used for transmitting QoE reports in NR.

[0113] In some examples, QoE support in NR may include RRC procedures supporting activation through trace capabilities, both signaling and management-based configuration, and application layer configuration and reporting.

[0114] In some examples, the UE may follow the gNB commands and the NG-RAN may release the application layer measurement configuration towards the UE via RRC at any time, e.g., as needed due to loading or other reasons.

[0115] In some examples, the UE inactive access stratum (AS) context may include UE AS configuration for QoE (eg, may not be released when the UE becomes inactive).

[0116] In some examples, a "QoE pause" indication from the network may be used to temporarily stop QoE reports from being sent from the UE to the network.

[0117] In some examples, for handling QoE reporting during RAN overload via a "QoE Report Pause Indication", the application layer may be responsible for storing the QoE report when the UE receives the QoE Pause Indication.

[0118] In some examples, for handling QoE reporting during RAN overload via a "QoE Report Pause Indication", the AS layer may be responsible for storing the QoE report when the UE receives the QoE Pause Indication.

[0119] In some examples, in case of QoE reporting processing during RAN overload via "QoE Reporting Pause Indication", the QoE container received from the application layer may be discarded during the pause.

[0120] In some examples, the application layer measurement collection function may enable collection of application layer measurements from the UE. An example of a supported service type may be QoE measurement collection for services such as streaming services. Both signaling-based and management-based initiation cases may be used. In the signaling-based case, application layer measurement collection is performed by receiving a notification from the CN node to a specific UE. E, and if management based, application layer measurement collection may be initiated from OAM targeting a domain (e.g., without targeting a specific UE).

[0121] Application layer measurement configurations received from the OAM or CN may be encapsulated in transparent containers that can be forwarded to the UE in downlink RRC messages. Application layer measurements received from higher layers in the UE may be encapsulated in transparent containers and sent to the network in uplink RRC messages. The network can release application layer measurement configurations towards the UE at any time.

[0122] In some instances, for URLLC services, E2E latency is important and operators may want to monitor and guarantee latency measurements.

[0123] In some examples, the QoE management framework may exist in two flavors: signaling-based QoE and management-based QoE. In signaling-based QoE, a QoE measurement configuration (QMC) can be distributed to RAN nodes. The QMC can specify the area scope for the measurement, which can be defined via a list or cell / TA / TAI / PLMN. In management-based QoE, the OAM can distribute the QMC to the RAN nodes.

[0124] In some examples, a threshold-based mechanism may be used to trigger the start and stop of QoE measurement collection. In some examples, time-based events may be used for QoE measurement activation, allowing flexibility in activating QoE measurements within a predefined period of time.

[0125] In some examples, upon receiving a "pause" instruction from the network, the UE may stop QoE reporting but may continue QoE measurements.

[0126] In some examples, a "QoE pause" indication from the network may be used to temporarily stop QoE reports from being sent to the network, but may not affect QoE measurement collection at the UE. For example, the UE may continue with ongoing QoE measurements and may trigger new QoE measurements at the application layer (e.g., according to a QoE configuration stored in the UE).

[0127] In some examples, if there is an overload in the RAN, the base station can temporarily stop reporting from the UE by sending an RRC message (e.g., an RRC Connection Reconfiguration message) to the associated UE. The RRC Connection Reconfiguration message may include a measurement configuration application layer configured to temporarily stop application layer measurement reporting in other configurations. In some examples, the access layer can send a command to the application with a pause request. The application can stop reporting and stop recording further information once the data in the reporting container is used. The recorded data may then be kept until it is reported or when the UE request session ends.

[0128] In some examples, when the overload situation in the RAN ends, the base station can resume reporting from the UE by sending an RRC message (e.g., an RRC Connection Reconfiguration message) to the associated UE. The RRC Connection Reconfiguration message may include a measurement configuration application layer set to resume application layer measurement reporting in another configuration. The access layer can send a command to the application with a reactivation request. The application can resume reporting and recording if it was stopped. It can be opened.

[0129] In some examples, the RAN may release an existing QoE measurement configuration when the session for which the QoE measurements were reported is completed or when the UE is handing over to a network that does not support QoE measurements. The NG-RAN node may issue a release of the UE's QoE measurement configuration that was previously configured for QoE measurement reporting if the session for which the QoE measurements were reported is completed. In some examples, for example, when handing over to a network that does not support this, the RAN may need to release an ongoing QoE measurement configuration or QoE reporting configuration.

[0130] In some examples, the RAN may release existing QoE measurement configurations in case of RAN overload. In some examples, in case of RAN overload in a standalone connection, the RAN may stop new QoE measurement configurations, release existing QoE measurement configurations, and suspend QoE measurement reporting. In some examples, RRC signaling may be used by the gNB to instruct the UE to suspend or resume QoE reporting. In some examples, the suspend / resume may be for all QoE reports, or the suspend / resume may be per QoE configuration. In some examples, the UE may store the reports (e.g., for a predetermined or configurable period). In some examples, there may be a limit on the stored report size.

[0131] In some examples, the RAN may release a QoE configuration from the UE at any time, including when an associated QoE measurement session is ongoing. In some examples, when the RAN commands the UE to release a QoE configuration, the UE may release the QoE configuration and may stop reporting (including available reports and not yet transmitted reports) for this QoE configuration.

[0132] In some examples, the RAN may stop new QoE measurement configurations, release existing QoE measurement configurations, and suspend QoE measurement reporting in case of RAN overload. In some examples, if the UE is configured with multiple QoE configurations, the network may suspend reporting for only some of the configurations. In some examples, to temporarily suspend QoE reporting from the UE, e.g., during RAN overload, the RAN may send a QoE reporting suspend command to the UE (e.g., using MAC CE or in a DL RRC message), which may indicate the QoE configuration(s) for which reporting is suspended. In some examples, once the UE suspends QoE reporting, the UE may continue measurement collection. The UE may continue generating QoE measurement results.

[0133] In some examples, the pause and resume commands for QoE configuration may be forwarded by the UE to the application layer, which may stop sending reports to the RRC layer after receiving a pause instruction from the UE and may continue to do so after receiving a resume instruction from the UE.

[0134] In some examples, network controlled mobility may be applied to UEs in RRC_CONNECTED and may be categorized into two types of mobility: cell level mobility and beam level mobility.

[0135] In some examples, the gNB may release a list of QoE measurement configurations in one RRCConfiguration message. In some examples, if the QoE measurement configurations are released, the RRC layer may notify higher layers to release the QoE measurement configurations. In some examples, when the UE enters an IDLE state, the UE may release all of the QoE measurement configurations. In some examples, the QoE configurations and reports may be encapsulated in a transparent container in the RRC message. In some examples, When the network sets up QoE measurements to the UE, the service type and RRC level ID (reference ID or short ID) may be included for each QoE configuration in the RRCConfiguration message along with the corresponding QMC configuration container. In some examples, at least the RRC level ID (reference ID or short ID) along with the corresponding QMC report container may be included in the MeasReportAppLayer message for QoE reporting. In some examples, QoE configuration changes may not need to be supported from a RAN2 signaling perspective (in RRC). In some examples, multiple QoE measurement configurations may be configured for a particular service type. In some examples, a maximum container size of 1000 bytes for QoE measurement configurations may be used.

[0136] In some examples, upon receipt of the QoE release, the UE may discard any pending QoE reports corresponding to the released QoE configuration. In some examples, the pause-resume process may affect all configurations. In some examples, the pause-resume process may operate selectively on a per-configuration basis.

[0137] In some examples, the QoE reference may not be transmitted between the UE in the RRC signaling for QoE measurements in RRC_CONNECTED. In some examples, the RRC ID MeasConfigAppLayerId may be sufficient to identify the QoE configuration between the UE and the gNB. In some examples, the gNB may maintain a mapping between MeasConfigAppLayerId and QoE Reference. The mapping may be transmitted to the target gNB as part of the QoE configuration and information at handover. In some examples, the RRC layer may forward the MeasConfigAppLayerId to the application layer along with the QoE configuration. In some examples, the maximum number of QoE configurations per UE may be eight. In some examples, when the UE resumes a connection at a gNB that supports QoE, the target gNB may explicitly indicate, for example in an RRC resume message, which QoE measurement configurations should be retained by the UE during the RRC resume procedure. The UE may release the QoE measurement configurations that are not indicated by the gNB for restoration. In some examples, during handover to a target gNB that supports QoE, the target gNB may decide which QoE configurations to keep and which QoE configurations to release during handover based on QoE configuration information received from the source gNB, e.g., in Xn / Ng signaling including RRC container. In some examples, the UE may discard reports received from the application layer if the associated QoE configuration is not configured. In some examples, the gNB may need to know the QoE configurations with ongoing QoE sessions, e.g., to enable QoE configuration processing during mobility. In some examples, if the UE resumes a connection in a gNB that does not support QoE, the UE may release all QoE measurement configurations.

[0138] Quality of Experience (QoE) measurement and reporting is an important feature for various services and applications, including streaming, virtual / augmented reality (VR / AR) and URLLC applications. A UE in an RRC inactive state may store a UE context including one or more QoE configurations and associated QoE configuration parameters. In response to an RRC resume procedure, the existing UE context restoration process may result in inefficiencies in QoE measurement and / or reporting. Example embodiments may enhance QoE measurement / reporting in response to an RRC resume procedure.

[0139] In an example embodiment, the UE may have an RRC connection with the first gNB (i.e., the UE may be in an RRC connected state). The UE may receive one or more RRC messages including configuration parameters from the first gNB. In some examples, The one or more RRC messages may include an RRC reconfiguration message. For example, the configuration parameters may include configuration parameters of one or more cells. In some examples, the configuration parameters may include configuration parameters of one or more cells provided by the first gNB. In some examples, in case of dual connectivity, the configuration parameters may include configuration parameters of one or more cells provided by the first gNB (as the master gNB) and the secondary gNB. The configuration parameters may further include QoE configuration parameters used by the UE for QoE measurement and / or QoE reporting. The UE may utilize the QoE configuration parameters to perform QoE measurement and QoE reporting while in the RRC connected state.

[0140] In the exemplary embodiment illustrated in FIG. 22, the QoE configuration parameters may be associated with a plurality of QoE configurations including a first QoE configuration and a second QoE configuration. The QoE configuration parameters may include a first configuration parameter of the first QoE configuration and a second configuration parameter of the second QoE configuration. The UE may receive an RRC release message. The RRC release message may indicate a transition of the UE from an RRC connected state to an RRC inactive state. The RRC release message includes a suspend configuration IE that indicates a transition of the UE from an RRC connected state to an RRC inactive state. The suspend configuration IE may include a plurality of parameters for UE operation during the RRC inactive state. The plurality of parameters may include a parameter indicating one or more RNTIs, a parameter indicating a RAN paging cycle, a parameter indicating a RAN notification area, one or more timer values, etc. The UE may transition from an RRC connected state to an RRC inactive state in response to receiving the RRC release message.

[0141] The UE may receive an RRC Resume message from the second gNB. For example, the UE may move from a coverage area of ​​the first gNB to a coverage area of ​​the second gNB. The RRC Resume message may indicate a transition of the UE from an RRC inactive state to an RRC connected state. The RRC Resume message may indicate restoring / resume a suspended RRC connection, e.g., at least a portion of the UE context. In some examples, receipt of the RRC Resume message may be in response to the UE transmitting an RRC Resume Request message to the second gNB. In response to receiving the RRC Resume message, the UE may release the first QoE configuration and may resume a second configuration parameter of the second QoE configuration. The second gNB may support QoE measurements and / or reporting associated with the second QoE configuration and may not support QoE measurements and / or reporting associated with the first QoE configuration. In some examples, the release of the first QoE configuration and the resumption of the second QoE configuration may be dependent or at least partially based on the second gNB supporting QoE measurement / reporting associated with the second QoE configuration. The release of the first QoE may be further dependent or based on the UE not supporting QoE measurement / reporting associated with the first QoE configuration.

[0142] In some examples, the UE may discard one or more first measurement reports associated with the first QoE configuration. The UE can discard the one or more first measurement reports based on the first QoE configuration not being supported by the second gNB.

[0143] In some examples, the second gNB may transmit an indication to the UE that the second gNB supports QoE measurement / reporting associated with the second QoE configuration and / or that the second gNB does not support QoE measurement / reporting associated with the first QoE configuration. In some examples, the indication may be provided via an RRC resume message. For example, the RRC resume message may include one or more information elements (e.g., In some examples, the information may be received via system information (e.g., received via one or more broadcast messages). In some examples, the indication may be received via a system information block (SIB, e.g., a QoE-related SIB). The SIB (e.g., a QoE-related SIB) may include information indicating that the second gNB supports QoE measurements / reporting associated with the second QoE configuration and that the second gNB does not support QoE measurements / reporting associated with the first QoE configuration.

[0144] In some examples, the information may be based on a bitmap. The bitmap may include a plurality of bits, including a first bit associated with a first QoE configuration and a second bit associated with a second QoE configuration. In some examples, the indication may be based on an association of a QoE configuration identifier(s) with a value indicating whether the second gNB supports or does not support the corresponding QoE configuration(s). The particular values ​​of the bits and the interpreted meanings associated with the particular values ​​(e.g., whether or not the QoE configuration is supported) may vary with respect to being positively supported, negatively supported, or a combination thereof.

[0145] In some examples, while in an RRC connected state (e.g., before receiving an RRC release message), the UE may perform QoE measurements and QoE reporting for both the first and second QoE configurations. In response to receiving an RRC resume message, based on the second gNB not supporting QoE measurements / reporting corresponding to the second QoE configuration, the UE may perform QoE measurements and QoE reporting for the second QoE configuration instead of the first QoE configuration. The UE may report a QoE measurement report (e.g., transmit a measurement report) based on one or more RRC messages. The one or more RRC messages used to transmit the QoE report may be associated with a signaling radio bearer (SRB), such as a QoE-related SRB, such as SRB4. In some examples, the QoE-related SRB (e.g., SRB4) may have a lower priority than a second SRB associated with an uplink common control channel logical channel. The one or more RRC messages used to transmit the QoE report may include a measurement report application layer IE that includes the QoE report. In some examples, the QoE report may include a QoE identifier associated with the QoE configuration.

[0146] In the exemplary embodiment shown in FIG. 23, a QoE configuration parameter may be associated with the QoE configuration. The UE may receive an RRC release message. The RRC release message may indicate a transition of the UE from an RRC connected state to an RRC inactive state. The RRC release message includes a suspend configuration IE that indicates a transition of the UE from an RRC connected state to an RRC inactive state. The suspend configuration IE may include multiple parameters for UE operation during the RRC inactive state. The multiple parameters may include a parameter indicating one or more RNTIs, a parameter indicating a RAN paging cycle, a parameter indicating a RAN notification area, one or more timer values, etc. The UE may transition from an RRC connected state to an RRC inactive state in response to receiving the RRC release message.

[0147] The UE may receive an RRC Resume message from the second gNB. For example, the UE may move from a coverage area of ​​the first gNB to a coverage area of ​​the second gNB. The RRC Resume message may indicate a transition of the UE from an RRC inactive state to an RRC connected state. The RRC Resume message may indicate restoring / resume a suspended RRC connection, e.g., at least a portion of the UE context. In some examples, receipt of the RRC Resume message may be in response to the UE sending an RRC Resume Request message to the second gNB. The RRC Resume message may indicate that at least one first QoE configuration parameter of the QoE configuration parameters has been updated. The UE may decide to discard or maintain the QoE measurement report based on the at least one first configuration parameter updated in response to the RRC resumption message (e.g., based on a type of the at least one first configuration parameter). In response to the decision to discard the QoE measurement report, the UE may discard the measurement report. In response to the decision to maintain the QoE measurement report, the UE may maintain the QoE measurement report.

[0148] In some examples, while in an RRC connected state (e.g., before receiving an RRC release message), the UE may perform QoE measurements and QoE reporting associated with the QoE configuration. In response to receiving an RRC resume message, the UE may perform QoE measurements and / or reporting. The UE may report a QoE measurement report (e.g., transmit a measurement report) based on one or more RRC messages. The one or more RRC messages used to transmit the QoE report may be associated with a signaling radio bearer (SRB), such as a QoE-related SRB, such as SRB4. In some examples, the QoE-related SRB (e.g., SRB4) may have a lower priority than a second SRB associated with an uplink common control channel logical channel. The one or more RRC messages used to transmit the QoE report may include a measurement report application layer IE that includes the QoE report. In some examples, the QoE report may include a QoE identifier associated with the QoE configuration.

[0149] In an exemplary embodiment, an apparatus, such as a user equipment (UE), may receive a first radio resource control (RRC) message from a first base station (BS) including a first configuration parameter of a first QoE configuration and a second configuration parameter of a second QoE configuration. The UE may receive an RRC release message indicating a transition of the UE from an RRC connected state to an RRC inactive state. The UE may receive an RRC resume message from a second BS indicating the UE transitions from an RRC inactive state to an RRC connected state. In response to receiving the RRC resume message, the UE may release the first QoE configuration and resume the second QoE configuration.

[0150] In some examples, the second base station (BS) may support a second quality of experience (QoE) configuration and may not support the first QoE configuration.

[0151] In some examples, the step of releasing the first QoE configuration and resuming the second QoE configuration may be based on the second base station (BS), i.e., supporting the second QoE configuration and not supporting the first QoE configuration.

[0152] In some examples, the UE may receive an indication from a second base station (BS) that the second BS supports a second quality of experience (QoE) configuration and does not support the first QoE configuration. In some examples, the indication may be based on a bitmap including a plurality of bits. A first bit of the plurality of bits may be associated with the first quality of experience (QoE) configuration. A second bit of the plurality of bits may be associated with the second QoE configuration. A first value of the first bit may indicate that the second base station (BS) does not support the first QoE configuration. A second value of the second bit may indicate that the second BS supports the second QoE configuration. In some examples, the indication may be based on at least one of a first identifier of the first quality of experience (QoE) configuration and a second identifier of the second QoE configuration. In some examples, the indication may be based on a radio resource control (RRC) resume message. In some examples, the radio resource control (RRC) resume message may include one or more information elements (IEs) indicating that the second base station (BS) supports a second quality of experience (QoE) configuration and does not support the first QoE configuration. In some examples, the UE may receive system information, and the indication may be based on the system information. In some examples, one or more of the system information The one or more values ​​of the field may indicate that the second base station (BS) supports the second quality of experience (QoE) configuration and does not support the first QoE configuration. In some examples, the first system information block (SIB) may include system information. In some examples, the first SIB may be a quality of experience (QoE) related SIB.

[0153] In some examples, the first radio resource control (RRC) message may be an RRC reconfiguration message.

[0154] In some examples, a radio resource control (RRC) release message may include a suspend configuration information element (IE) that indicates a transition of a user equipment (UE) from an RRC connected state to an RRC inactive state. In some examples, the suspend configuration information element (IE) may include at least one of one or more radio network temporary identifiers (RNTIs), a first parameter indicating a radio access network (RAN) paging cycle, a second parameter indicating a RAN notification area, and one or more timer values.

[0155] In some examples, a radio resource control (RRC) resume message may indicate restoring one or more configuration parameters for a user equipment (UE) after transitioning to an RRC connected state.

[0156] In some examples, the UE may discard one or more first measurement reports associated with a first quality of experience (QoE) configuration in response to receiving a radio resource control (RRC) resume message. In some examples, discarding the one or more first quality of experience (QoE) measurement reports may be based on a second base station (BS) not supporting the first QoE configuration.

[0157] In some examples, the UE may perform at least one of quality of experience (QoE) measurements and QoE measurement reporting associated with the first and second QoE configurations in response to receiving an RRC release message while in a radio resource control (RRC) inactive state. The UE may perform QoE measurements and QoE measurement reporting associated with the second QoE configuration in response to receiving an RRC resume message. In some examples, the quality of experience (QoE) measurement reporting may be via one or more radio resource control (RRC) messages. In some examples, the quality of experience (QoE) measurement reporting may be associated with a QoE-related signaling radio bearer (SRB). In some examples, the quality of experience (QoE)-related signaling radio bearer (SRB) may be SRB4. In some examples, the quality of experience (QoE)-related signaling radio bearer (SRB) may have a lower priority than a second SRB associated with an uplink common control channel logical channel. In some examples, one or more Resource Control (RRC) messages may include a Measurement Report Application Layer Information Element (MeasReportappLayer IE) that includes a QoE measurement report. In some examples, the Quality of Experience (QoE) measurement report may include an identifier associated with a corresponding QoE configuration.

[0158] In an example embodiment, a user equipment (UE) may receive a first radio resource control (RRC) message from a first base station (BS) including configuration parameters for a QoE configuration. The UE may receive an RRC release message indicating a transition of the UE from an RRC connected state to an RRC inactive state. The UE may receive an RRC resume message from a second BS indicating the UE transitions from an RRC inactive state to an RRC connected state. The UE may decide to discard or keep a QoE measurement report associated with the QoE configuration in response to the RRC resume message indicating that at least one first one of the configuration parameters has been updated.

[0159] In some examples, the UE may discard a quality of experience (QoE) measurement report based on a decision to discard the QoE measurement report.

[0160] In some examples, the UE may maintain quality of experience (QoE) measurement reports based on a determination to maintain the QoE measurement reports.

[0161] In some examples, determining to discard or keep the Quality of Experience (QoE) measurement report may be based on at least one first configuration parameter that is updated.

[0162] In some examples, the UE may discard a quality of experience (QoE) measurement report regardless of the type of the at least one first configuration that is updated.

[0163] In some examples, the quality of experience (QoE) measurement reporting may be based on QoE measurements performed during an RRC inactive state.

[0164] In some examples, a radio resource control (RRC) release message may include a suspend configuration information element (IE) that indicates a transition of a user equipment (UE) from an RRC connected state to an RRC inactive state. In some examples, the suspend configuration information element (IE) includes at least one of one or more radio network temporary identifiers (RNTIs), a first parameter indicating a radio access network (RAN) paging cycle, a second parameter indicating a RAN notification area, and one or more timer values.

[0165] In some examples, a radio resource control (RRC) resume message may indicate restoring one or more configuration parameters for a user equipment (UE) after transitioning to an RRC connected state.

[0166] In some examples, the UE may perform at least one of a quality of experience (QoE) measurement and a QoE measurement report associated with the QoE configuration while in a radio resource control (RRC) inactive state and in response to receiving an RRC release message. In some examples, the quality of experience (QoE) measurement report may be via one or more radio resource control (RRC) messages. In some examples, the quality of experience (QoE) measurement report may be associated with a QoE-related signaling radio bearer (SRB). In some examples, the quality of experience (QoE)-related signaling radio bearer (SRB) may be an SRB4. In some examples, the quality of experience (QoE)-related signaling radio bearer (SRB) may have a lower priority than a second SRB associated with an uplink common control channel logical channel. In some examples, the one or more resource control (RRC) messages may include a measurement report application layer information element (MeasReportappLayer IE) including the QoE measurement report. In some examples, a quality of experience (QoE) measurement report may include an identifier associated with a corresponding QoE configuration.

[0167] The exemplary blocks and modules described in this disclosure with respect to various exemplary embodiments may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Examples of general purpose processors include, but are not limited to, a microprocessor, any conventional processor, controller, microcontroller, or state machine. In some examples, a processor may be a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, The present invention may be implemented using a digital signal processor (DSC), a digital multiplier, ...

[0168] The functions described in this disclosure may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Instructions or codes may be stored or transmitted to a computer-readable medium to implement the functions. Other examples for implementing the functions disclosed herein are also within the scope of this disclosure. Implementation of the functions may be via physically co-located or distributed elements (e.g., at various locations), including being distributed such that some of the functions are implemented in different physical locations.

[0169] Computer-readable media includes, but is not limited to, non-transitory computer storage media. Non-transitory storage media may be accessed by general-purpose or special-purpose computers. Examples of non-transitory storage media include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage, and the like. Non-transitory media may be used to carry or store desired program code means (e.g., instructions and / or data structures) and may be accessed by general-purpose or special-purpose computers or general-purpose or special-purpose processors. In some examples, the software / program code may be transmitted from a remote source (e.g., a website, a server, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, microwave, and the like. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, and the like, are within the definition of media. Combinations of the above examples are also within the scope of computer-readable media.

[0170] As used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. A list of items can begin with a phrase such as "at least one" or "one or more." For example, a list of at least one of A, B, or C includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A and B and C). Also, as used in this disclosure, the phrase "based on" preceding a list of conditions should not be interpreted as "based only on" the set of conditions, but rather as "based at least in part on" the set of conditions. For example, a result described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure.

[0171] As used herein, the terms "comprise", "include" or "contain" may be used interchangeably, have the same meaning, and should be construed as inclusive and open-ended. The terms "comprise", "include" or "contain" may be used before a list of elements to indicate that at least all of the listed elements in the list are present, but other elements not in the list may also be present. For example, if A contains B and C, then both {B, C} and {B, C, D} are within the scope of A.

[0172] The present disclosure describes exemplary configurations in conjunction with the accompanying drawings, which do not represent all examples that may be implemented or all configurations within the scope of the present disclosure. The term "exemplary" should not be interpreted as "preferred" or "advantageous compared to other examples," but rather as "an example, instance, or example." By reading this disclosure, including the description of the embodiments and drawings, one skilled in the art will understand that the technology disclosed herein may be implemented using alternative embodiments. One skilled in the art will be able to combine the embodiments, or specific features of the embodiments described herein, into yet other embodiments for implementing the technology described in this disclosure. It will be understood that the present disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0173] Clause 1. A method for quality of experience (QoE) measurement and reporting, comprising: receiving, by a user equipment (UE), a first radio resource control (RRC) message including first configuration parameters of a first QoE configuration and second configuration parameters of a second QoE configuration; receiving, by the UE, an RRC release message indicating a transition of the UE from an RRC connected state to an RRC inactive state, the UE being in a connected state when the RRC release message is received; receiving, by the UE, from a second BS, an RRC resumption message indicating a transition of the UE from an RRC inactive state to an RRC connected state, where the UE is in an inactive state when the RRC resumption message is received; in response to receiving the RRC resumption message, releasing the first QoE configuration and resuming the second QoE configuration.

[0174] Clause 2. The method of clause 1, wherein the second base station (BS) supports a second quality of experience (QoE) configuration.

[0175] Clause 3. The method of clause 2, wherein the second BS does not support the first QoE configuration.

[0176] Clause 4. The method of clause 3, wherein the step of releasing the first quality of experience (QoE) configuration and resuming the second QoE configuration occurs when the second base station (BS) supports the second QoE configuration and does not support the first QoE configuration.

[0177] Clause 5. The method of clause 1, further comprising receiving information regarding support of at least one of the first QoE configuration or the second QoE configuration from a second base station (BS).

[0178] Clause 6. The method of clause 5, wherein the information includes a bitmap including a plurality of bits, a first bit of the plurality of bits being associated with a first Quality of Experience (QoE) configuration, and a second bit of the plurality of bits being associated with a second QoE configuration.

[0179] Clause 7. The method of clause 6, wherein a value of a first bit indicates information indicating support for a first QoE configuration.

[0180] Clause 8. The method of clause 6, wherein a value of the second bit indicates support for a second QoE configuration.

[0181] Clause 9. The method of clause 5, wherein the information includes at least one of a first identifier of a first Quality of Experience (QoE) configuration and a second identifier of a second QoE configuration.

[0182] Clause 10. The method of clause 5, wherein the information is included in a Radio Resource Control (RRC) resumption message.

[0183] Clause 11. The method of clause 5, further comprising the step of receiving system information, the information being based on the system information.

[0184] Clause 12. The system information includes a first system information block (SIB), The method described.

[0185] Clause 13. The method of clause 12, wherein the first SIB is a Quality of Experience (QoE) related SIB.

[0186] Clause 14. The method of clause 1, wherein the first radio resource control (RRC) message is an RRC reconfiguration message.

[0187] Clause 15. The method of clause 1, wherein the radio resource control (RRC) release message includes a suspend configuration information element (IE) indicating a transition of the user equipment (UE) from an RRC connected state to an RRC inactive state.

[0188] Clause 16. The suspend configuration information element (IE) one or more Radio Network Temporary Identifiers (RNTIs); and a first parameter indicative of a Radio Access Network (RAN) paging cycle; a second parameter indicating a RAN notification area; and one or more timer values.

[0189] Clause 17. The method of clause 1, wherein a radio resource control (RRC) resumption message indicates restoration of one or more configuration parameters for the user equipment (UE) after transition to an RRC connected state.

[0190] Clause 18. The method of clause 1, further comprising discarding one or more first measurement reports associated with the first Quality of Experience (QoE) configuration in response to receiving a Radio Resource Control (RRC) resume message.

[0191] Clause 19. The method of clause 18, wherein the step of discarding the one or more first Quality of Experience (QoE) measurement reports occurs if the second base station (BS) does not support the first QoE configuration.

[0192] Clause 20. In response to receiving a Radio Resource Control (RRC) release message while a user equipment (UE) is in an RRC inactive state, performing at least one Quality of Experience (QoE) measurement; reporting at least one of a QoE measurement associated with the first QoE configuration and the second configuration; performing QoE measurements in response to receiving an RRC resumption message; reporting a QoE measurement report associated with the second QoE configuration; 2. The method of claim 1, further comprising:

[0193] Clause 21. The method of clause 20, wherein the Quality of Experience (QoE) measurement reporting is via one or more Radio Resource Control (RRC) messages.

[0194] Clause 22. The method of clause 21, wherein the Quality of Experience (QoE) measurement report is associated with a QoE-related Signaling Radio Bearer (SRB).

[0195] Clause 23. The method of clause 22, wherein the Quality of Experience (QoE) related signaling radio bearer (SRB) is an SRB4.

[0196] Clause 24. Quality of Experience (QoE) related signalling Radio Bearer (SRB) 23. The method of claim 22, wherein the first SRB has a lower priority than a second SRB associated with the second common control channel logical channel.

[0197] Clause 25. One or more Resource Control (RRC) messages may contain a measurement report application layer information element (MeasReportappLayer IE).

[0198] Clause 26. The method of clause 20, wherein the Quality of Experience (QoE) measurement report includes an identifier associated with a corresponding QoE configuration.

[0199] Clause 27. Quality of Experience (QoE) measurement and reporting method, comprising: receiving, by a user equipment (UE), a first radio resource control (RRC) message including configuration parameters for a QoE configuration; receiving an RRC release message indicating a transition of the UE from an RRC connected state to an RRC inactive state; receiving, by the UE, an RRC resumption message indicating a transition of the UE from an RRC inactive state to an RRC connected state; and in response to an RRC resumption message indicating that at least a first one of the configuration parameters has been updated, determining to discard or maintain QoE measurement reports associated with the QoE configuration.

[0200] Clause 28. The method of clause 27, further comprising discarding the Quality of Experience (QoE) measurement report based on the decision to discard the QoE measurement report.

[0201] Clause 29. The method of clause 27, further comprising maintaining a quality of experience (QoE) measurement report based on the decision to maintain the QoE measurement report.

[0202] Clause 30. The method of clause 27, wherein the decision to discard or retain the Quality of Experience (QoE) measurement report is based on at least one updated first configuration parameter.

[0203] Clause 31. The method of clause 27, further comprising discarding Quality of Experience (QoE) measurement reports regardless of a type of the updated at least one first configuration.

[0204] Clause 32. The method of clause 26, wherein the Quality of Experience (QoE) measurement reporting is based on QoE measurements performed during a Radio Resource Control (RRC) inactive state.

[0205] Clause 33. The method of clause 26, wherein the radio resource control (RRC) release message includes a suspend configuration information element (IE) indicating a transition by the user equipment (UE) from an RRC connected state to an RRC inactive state.

[0206] Clause 34. The suspend configuration information element (IE) one or more Radio Network Temporary Identifiers (RNTIs); and a first parameter indicative of a Radio Access Network (RAN) paging cycle; a second parameter indicating a RAN notification area; and one or more timer values.

[0207] Clause 35. The method of clause 27, wherein a radio resource control (RRC) resumption message indicates restoration of one or more configuration parameters for the user equipment (UE) after transition to an RRC connected state.

[0208] Clause 36. The method of clause 27, further comprising, while in a radio resource control (RRC) inactive state, performing at least one of a quality of experience (QoE) measurement and reporting a QoE measurement associated with a QoE configuration in response to receiving an RRC release message.

[0209] Clause 37. The method of clause 36, wherein the Quality of Experience (QoE) measurement reporting is via one or more Radio Resource Control (RRC) messages.

[0210] Clause 38. The method of clause 37, wherein the Quality of Experience (QoE) measurement report is associated with a QoE-related signaling radio bearer (SRB).

[0211] Clause 39. The method of clause 38, wherein the Quality of Experience (QoE) related signaling radio bearer (SRB) is an SRB4.

[0212] Clause 40. The method of clause 39, wherein a Quality of Experience (QoE) related signaling radio bearer (SRB) has a lower priority than a priority of a second SRB associated with an uplink common control channel logical channel.

[0213] Clause 41. The method according to clause 37, wherein one or more Radio Resource Control (RRC) messages include a Measurement Report Application Layer Information Element (MeasReportappLayer IE) including a Quality of Experience (QoE) measurement report.

[0214] Clause 42. The method of clause 37, wherein the Quality of Experience (QoE) measurement report includes an identifier associated with a corresponding QoE configuration.

[0215] Article 43. Apparatus for use in radio communication, comprising: an antenna used for transmitting electromagnetic signals; a memory for maintaining computer readable code; and a processor for executing computer readable code, the computer readable code configuring the apparatus to: receiving a first radio resource control (RRC) message including first configuration parameters of a first QoE configuration and second configuration parameters of a second QoE configuration; receiving an RRC release message indicating a transition of the device from an RRC connected state to an RRC inactive state, the device being in a connected state when the RRC release message is received; receiving an RRC resumption message from the second BS, the RRC resumption message indicating a transition of the device from an RRC inactive state to an RRC connected state, the device being in the inactive state when the RRC resumption message is received; The apparatus, in response to receiving an RRC resume message, releases the first QoE configuration and resumes the second QoE configuration.

[0216] Clause 44. The apparatus of clause 43, wherein the second base station (BS) supports a second quality of experience (QoE) configuration.

[0217] Clause 45. The apparatus of clause 44, wherein the second BS does not support the first QoE configuration.

[0218] Clause 46. The apparatus of clause 45, wherein the step of releasing the first quality of experience (QoE) configuration and resuming the second QoE configuration occurs when the second base station (BS) supports the second QoE configuration and does not support the first QoE configuration.

[0219] Clause 47. The apparatus of clause 43, wherein the apparatus is further configured to receive information regarding support of at least one of the first QoE configuration or the second QoE configuration from a second base station (BS).

[0220] Clause 48. The apparatus of clause 47, wherein the information includes a bitmap including a plurality of bits, a first bit of the plurality of bits being associated with a first quality of experience (QoE) configuration, and a second bit of the plurality of bits being associated with a second QoE configuration.

[0221] Clause 49. The apparatus of clause 48, wherein a value of the first bit indicates information indicating support for a first QoE configuration.

[0222] Clause 50. The apparatus of clause 48, wherein a value of the second bit indicates support for a second QoE configuration.

[0223] Clause 51. The apparatus of clause 47, wherein the information includes at least one of a first identifier of a first Quality of Experience (QoE) configuration and a second identifier of a second QoE configuration.

[0224] Clause 52. The apparatus of clause 47, wherein the information is included in a Radio Resource Control (RRC) resumption message.

[0225] Clause 53. The apparatus of clause 47, wherein the apparatus is further configured to receive system information, the information being based on the system information.

[0226] Clause 54. The apparatus of clause 51, wherein the system information includes a first system information block (SIB).

[0227] Clause 55. The apparatus of clause 54, wherein the first SIB is a Quality of Experience (QoE) related SIB.

[0228] Clause 56. The apparatus of clause 43, wherein the first radio resource control (RRC) message is an RRC reconfiguration message.

[0229] Clause 57. The apparatus of clause 43, wherein the Radio Resource Control (RRC) release message includes a suspend configuration information element (IE) indicating a transition of the user equipment (apparatus) from an RRC connected state to an RRC inactive state.

[0230] Clause 58. The suspend configuration information element (IE) one or more Radio Network Temporary Identifiers (RNTIs); and a first parameter indicative of a Radio Access Network (RAN) paging cycle; a second parameter indicating a RAN notification area; and one or more timer values.

[0231] Clause 59. The apparatus of clause 43, wherein a Radio Resource Control (RRC) Resume message indicates restoration of one or more configuration parameters for the user equipment (apparatus) after transition to an RRC connected state.

[0232] Clause 60. The apparatus of clause 43, further comprising discarding one or more first measurement reports associated with the first quality of experience (QoE) configuration in response to receiving a radio resource control (RRC) resume message.

[0233] Clause 61. The apparatus of clause 60, wherein discarding the one or more first Quality of Experience (QoE) measurement reports occurs if the second base station (BS) does not support the first QoE configuration.

[0234] Article 62. The device: performing at least one quality of experience (QoE) measurement in response to receiving a radio resource control (RRC) release message while the device is in an RRC inactive state; reporting at least one of a QoE measurement associated with the first QoE configuration and the second configuration; In response to receiving the RRC resumption message, perform QoE measurements; The apparatus of clause 43, further configured to report a QoE measurement report associated with the second QoE configuration.

[0235] Clause 63. The apparatus of clause 62, wherein the quality of experience (QoE) measurement reporting is via one or more radio resource control (RRC) messages.

[0236] Clause 64. The apparatus of clause 63, wherein the quality of experience (QoE) measurement report is associated with a QoE-related signaling radio bearer (SRB).

[0237] Clause 65. The apparatus of clause 64, wherein the Quality of Experience (QoE) related signaling radio bearer (SRB) is an SRB4.

[0238] Clause 66. The apparatus of clause 64, wherein a quality of experience (QoE) related signaling radio bearer (SRB) has a lower priority than a second SRB associated with an uplink common control channel logical channel.

[0239] Clause 67. One or more Resource Control (RRC) messages may contain a measurement report application layer information element (MeasReportappLayer IE).

[0240] Clause 68. The apparatus of clause 62, wherein the quality of experience (QoE) measurement report includes an identifier associated with a corresponding QoE configuration.

[0241] Article 69. Apparatus for use in radio communication, an antenna used for transmitting electromagnetic signals; a memory for maintaining computer readable code; and a processor for executing computer readable code, the computer readable code configuring the apparatus to: Receiving a first radio resource control (RRC) message including configuration parameters for a QoE configuration; receiving an RRC release message indicating a transition of the device from an RRC connected state to an RRC inactive state; causing the device to receive an RRC resumption message indicating a transition from an RRC inactive state to an RRC connected state; 11. The apparatus, in response to an RRC resumption message indicating that at least a first one of the configuration parameters has been updated, determining to discard or maintain a QoE measurement report associated with the QoE configuration.

[0242] Clause 70. The apparatus of clause 69, wherein the apparatus is further configured to evaluate a Quality of Experience (QoE) measurement report based on a decision to discard the QoE measurement report.

[0243] Clause 71. The apparatus of clause 69, wherein the apparatus is further configured to maintain a Quality of Experience (QoE) measurement report based on the decision to maintain the QoE measurement report.

[0244] Clause 72. The apparatus of clause 69, wherein the decision to discard or retain the Quality of Experience (QoE) measurement report is based on at least one updated first configuration parameter.

[0245] Clause 73. The apparatus of clause 69, wherein the apparatus is further configured to discard Quality of Experience (QoE) measurement reports regardless of a type of the updated at least one first configuration.

[0246] Clause 74. The apparatus of clause 69, wherein the quality of experience (QoE) measurement reporting is based on QoE measurements performed during a radio resource control (RRC) inactive state.

[0247] Clause 75. The apparatus of clause 69, wherein the radio resource control (RRC) release message includes a suspend configuration information element (IE) indicating a transition by the user equipment (apparatus) from an RRC connected state to an RRC inactive state.

[0248] Clause 76. The suspend configuration information element (IE) one or more Radio Network Temporary Identifiers (RNTIs); and a first parameter indicative of a Radio Access Network (RAN) paging cycle; a second parameter indicating a RAN notification area; and one or more timer values.

[0249] Clause 77. The apparatus of clause 69, wherein a Radio Resource Control (RRC) Resume message indicates restoration of one or more configuration parameters for the user equipment (apparatus) after transition to an RRC connected state.

[0250] Clause 78. The apparatus of clause 69, wherein the apparatus is further configured to perform at least one of quality of experience (QoE) measurements and reporting QoE measurements associated with a QoE configuration in response to receiving a radio resource control (RRC) release message while the apparatus is in an RRC inactive state.

[0251] Clause 79. The apparatus of clause 78, wherein the quality of experience (QoE) measurement reporting is via one or more radio resource control (RRC) messages.

[0252] Clause 80. The apparatus of clause 49, wherein the quality of experience (QoE) measurement report is associated with a QoE-related signaling radio bearer (SRB).

[0253] Clause 81. The apparatus of clause 80, wherein the quality of experience (QoE) related signaling radio bearer (SRB) is an SRB4.

[0254] Clause 82. The apparatus of clause 81, wherein a quality of experience (QoE) related signaling radio bearer (SRB) has a lower priority than a priority of a second SRB associated with an uplink common control channel logical channel.

[0255] Clause 83. One or more Radio Resource Control (RRC) messages may include a Measurement Report application layer information element (MeasReport 79. The apparatus of claim 79, comprising:

[0256] Clause 84. The apparatus of clause 79, wherein the quality of experience (QoE) measurement report includes an identifier associated with a corresponding QoE configuration.

[0257] Clause 85. A method for quality of experience (QoE) measurement and reporting, comprising: transmitting, by the network, a first Radio Resource Control (RRC) message including first configuration parameters of the first QoE configuration and second configuration parameters of the second QoE configuration; sending, by the network, an RRC release message indicating a transition of a user equipment (UE) from an RRC connected state to an RRC inactive state, the UE being in a connected state when the RRC release message is received; sending, by the network, from the second BS, an RRC resumption message indicating a transition of the UE from an RRC inactive state to an RRC connected state, where the UE is in an inactive state when the RRC resumption message is received; The method, wherein in response to receiving an RRC resume message, the first QoE configuration is released and the second QoE configuration is resumed.

[0258] Clause 86. A method for quality of experience (QoE) measurement and reporting, comprising: transmitting, by a network, a first Radio Resource Control (RRC) message including configuration parameters for a QoE configuration; receiving an RRC release message indicating a transition of a user equipment (UE) from an RRC connected state to an RRC inactive state; sending, by the network, an RRC resumption message indicating a transition of the UE from an RRC inactive state to an RRC connected state, wherein the UE decides to discard or keep QoE measurement reports associated with the QoE configuration in response to the RRC resumption message indicating that at least a first one of the configuration parameters has been updated.

[0259] Article 87. Apparatus for use in radio communication, an antenna used for transmitting electromagnetic signals; a memory for maintaining computer readable code; and a processor for executing computer readable code, the computer readable code configuring the apparatus to: transmitting a first radio resource control (RRC) message including first configuration parameters of the first QoE configuration and second configuration parameters of the second QoE configuration; transmitting an RRC release message indicating a transition of the device from an RRC connected state to an RRC inactive state, the device being in a connected state when the RRC release message is received; sending an RRC resumption message from a second BS, the RRC resumption message instructing the device to transition from an RRC inactive state to an RRC connected state, the device being in an inactive state when the RRC resumption message is received; The apparatus, in response to receiving an RRC resume message, wherein in response to receiving the RRC resume message, the first QoE configuration is released and the second QoE configuration is resumed.

[0260] Article 88. Apparatus for use in radio communication, comprising: an antenna used for transmitting electromagnetic signals; a memory for maintaining computer readable code; and a processor for executing computer readable code, the computer readable code configuring the apparatus to: Send a first Radio Resource Control (RRC) message containing configuration parameters for the QoE configuration. Believe, causing the device to transmit an RRC release message indicating a transition from an RRC connected state to an RRC inactive state; An apparatus, causing a network to transmit an RRC resumption message indicating a transition of the apparatus from an RRC inactive state to an RRC connected state, and in response to the RRC resumption message indicating that at least one first configuration parameter of the configuration parameters has been updated, the apparatus decides to discard or maintain QoE measurement reports associated with the QoE configuration.

[0261] This application is based on the "QUALITY OF EXPERIENCE MEASUREMENT This application claims the benefit of U.S. Provisional Application No. 63 / 246,564, filed September 21, 2021, entitled "IN RESPONSE TO A RESUME PROCEDURE," which is incorporated herein by reference.

Claims

1. A method for quality of experience (QoE) measurement and reporting, comprising: receiving, by a user equipment (UE), a radio resource control (RRC) message including an application layer measurement configuration; receiving, by the UE, an RRC resumption message indicating a transition of the UE from an RRC inactive state to an RRC connected state; and the UE discarding application layer measurement reports associated with the application layer measurement configuration based on information included in the RRC resumption message.

2. The method of claim 1 , further comprising the UE suspending application layer measurement reporting associated with the application layer measurement configuration based on information included in the RRC resumption message.

3. 2. The method of claim 1, wherein the discarding of the application layer measurement report occurs if a base station (BS) that sent the RRC resumption message does not support the application layer measurement configuration.

4. A method for quality of experience (QoE) measurement and reporting, comprising: transmitting, by a base station (BS), an RRC resumption message indicating a transition of a user equipment (UE) from an RRC inactive state to an RRC connected state; The UE discards application layer measurement reports associated with an application layer measurement configuration received by the UE based on information included in the RRC resumption message.

5. The method of claim 4 , wherein the UE suspends application layer measurement reporting associated with the application layer measurement configuration based on information included in the RRC resumption message.

6. The method of claim 4 , wherein discarding the application layer measurement report occurs if the BS does not support the application layer measurement configuration.

Images