Handling of buffered QOE data when QOE is deactivated in idle / inactive state UE

Abstract

A wireless communication device activates a quality of experience (QoE) configuration; after the QoE configuration is activated, accumulating the QoE data in the buffer when in a radio resource control inactivity (RRCINACTIVE) state or an RRCIDLE state; deactivating the QoE configuration; initiating an RRC connection establishment procedure from the RRCIDLE state or an RRC connection recovery procedure from the RRCINACTIVE state in response to both the presence of the QoE data in the buffer area and the deactivation of the QoE configuration; and transmitting the QoE data in the buffer to a network entity after entering an RRCCONNECTED state at the end of the RRC connection establishment process or the RRC connection recovery process. In one aspect, the wireless communication device ceases to accumulate the QoE data in response to determining to deactivate the QoE configuration, and stores parameters of the QoE configuration.

Description

Technical Field

[0001] The techniques discussed below relate generally to wireless communication networks including user equipment (UEs), and more particularly to handling buffered quality of experience (QoE) data in response to QoE configuration deactivation at a UE in an idle or inactive state. Background Art

[0002] In wireless communication systems, such as those specified under the standards for 5G New Radio (NR), Quality of Service (QoS) metrics can be based on measured key performance indicators. However, QoS metrics may not accurately reflect the quality of experience a user experiences using a wireless communication device in a wireless communication network. Therefore, Quality of Experience (QoE) metrics are measured by user equipment and provided to operations, administration, and maintenance (OAM) entities to assess the user experience. Summary of the Invention

[0003] The following presents an overview of one or more aspects of the present disclosure to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all anticipated features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form that serves as a prelude to the more detailed description presented later.

[0004] In one example, a wireless communication device is described. The wireless communication device includes a memory and a processor coupled to the memory. According to one aspect, the processor is configured to: activate a quality of experience (QoE) configuration; after activating the QoE configuration, while in a radio resource control inactive (RRC_INACTIVE) state or an RRC_IDLE state, accumulate QoE data in a buffer; deactivate the QoE configuration; in response to both the presence of the QoE data in the buffer and the deactivation of the QoE configuration, initiate an RRC connection establishment procedure from the RRC_IDLE state or initiate an RRC connection recovery procedure from the RRC_INACTIVE state; and after entering the RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure, transmit the QoE data in the buffer to a network entity. In one aspect, the processor is further configured to: stop accumulating the QoE data in response to determining to deactivate the QoE configuration; and store parameters of the QoE configuration.

[0005] In another example, a method for wireless communication at a wireless communication device is described. The method includes: activating a quality of experience (QoE) configuration; after activating the QoE configuration, accumulating QoE data in a buffer while in a radio resource control inactive (RRC_INACTIVE) state or an RRC_IDLE state; deactivating the QoE configuration; in response to both the presence of the QoE data in the buffer and the deactivation of the QoE configuration, initiating an RRC connection establishment procedure from the RRC_IDLE state or initiating an RRC connection recovery procedure from the RRC_INACTIVE state; and, after entering an RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure, transmitting the QoE data in the buffer to a network entity. In another aspect, the method for wireless communication at a wireless communication device includes: stopping accumulating the QoE data in response to determining to deactivate the QoE configuration; and storing parameters of the QoE configuration.

[0006] In another example, an apparatus configured for wireless communication is described. According to this example, the apparatus includes: means for activating a quality of experience (QoE) configuration; means for accumulating QoE data in a buffer while in a radio resource control inactive (RRC_INACTIVE) state or an RRC_IDLE state after activating the QoE configuration; means for deactivating the QoE configuration; means for initiating an RRC connection establishment procedure from the RRC_IDLE state or an RRC connection recovery procedure from the RRC_INACTIVE state in response to both the presence of the QoE data in the buffer and the deactivation of the QoE configuration; and means for transmitting the QoE data in the buffer to a network entity after entering the RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure. In another aspect, the apparatus configured for wireless communication further includes: means for stopping accumulating the QoE data in response to determining to deactivate the QoE configuration; and means for storing parameters of the QoE configuration.

[0007] In another example, a non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of a base station is disclosed. The instructions include: instructions for activating a quality of experience (QoE) configuration; instructions for accumulating QoE data in a buffer while in a radio resource control inactive (RRC_INACTIVE) state or an RRC_IDLE state after activating the QoE configuration; instructions for deactivating the QoE configuration; instructions for initiating an RRC connection establishment procedure from the RRC_IDLE state or an RRC connection recovery procedure from the RRC_INACTIVE state in response to both the presence of the QoE data in the buffer and the deactivation of the QoE configuration; and instructions for transmitting the QoE data in the buffer to a network entity after entering the RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure. In one aspect, the instructions further include: instructions for stopping accumulating the QoE data in response to determining to deactivate the QoE configuration; and instructions for storing parameters of the QoE configuration.

[0008] These and other aspects of the present disclosure will become more fully understood after studying the detailed description below. After reading the following description of specific, example embodiments of the present disclosure in conjunction with the accompanying drawings, other aspects, features and embodiments of the present disclosure will become apparent to those of ordinary skill in the art. Although features of the present disclosure may be discussed below with respect to certain embodiments and drawings, all embodiments of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used according to the various embodiments of the present disclosure discussed herein. In a similar manner, although example embodiments may be discussed below as device, system or method embodiments, it should be appreciated that such example embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a schematic diagram of a wireless communication system according to some aspects of the present disclosure.

[0010] Figure 2 is a schematic diagram of an example of a radio access network (RAN) according to some aspects of the present disclosure.

[0011] Figure 3 is a diagram of an example decomposed base station architecture according to some aspects of the present disclosure.

[0012] Figure 4is an expanded view of an example subframe illustrating an orthogonal frequency division multiplexing (OFDM) resource grid according to some aspects of the present disclosure.

[0013] Figure 5 is a schematic diagram of a 5G user plane protocol stack and a 5G control plane protocol stack according to some aspects of the present disclosure.

[0014] Figure 6 is a schematic diagram of state transitions between three radio resource control states in 5G according to some aspects of the present disclosure.

[0015] Figure 7 is a call flow diagram illustrating quality of experience measurement collection activation according to some aspects of the present disclosure.

[0016] Figure 8 is a call flow diagram illustrating quality of experience measurement reporting according to some aspects of the present disclosure.

[0017] Figure 9 is a call flow diagram illustrating deactivation or release of quality of experience measurement collection in accordance with some aspects of the present disclosure.

[0018] Figure 10 is a call flow diagram illustrating accumulation of quality of experience data in a buffer during RRC_INACTIVE and / or RRC_IDLE states, and reporting of the buffered quality of experience data in response to receiving a quality of experience measurement collection deactivation indication, according to some aspects of the present disclosure.

[0019] Figure 11 is a block diagram illustrating an example of a hardware implementation for a wireless communication device employing a processing system according to some aspects of the present disclosure.

[0020] Figure 12 is a flow chart illustrating an example process for wireless communications at a wireless communication device according to some aspects of the present disclosure.

[0021] Figure 13 is a flow chart illustrating an example process for wireless communications at a wireless communication device according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0022] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations with which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some examples, well-known structures and components are shown in block diagram form to avoid obscuring the concepts.

[0023] Although various aspects and examples are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses can be generated via integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. Specific implementations can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some actual settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or user equipment (UE)), end-user devices, etc.

[0024] Described herein are techniques for avoiding loss of QoE data in response to deactivation of a QoE configuration at a UE. After activating the QoE configuration and when the UE is in an RRC_INACTIVE state or an RRC_IDLE state, QoE data may be collected at the UE. The QoE data may be stored in a QoE data buffer of the UE. According to some aspects, when the QoE configuration is deactivated and in response to accumulation and buffering of QoE data in the QoE data buffer of the UE, the UE may initiate an RRC configuration establishment procedure or an RRC connection resumption procedure. Thus, upon being instructed to deactivate the QoE configuration or otherwise determining that deactivation is required and determining that QoE data is stored in the QoE buffer, the UE may initiate an RRC connection establishment procedure (if the UE is in an RRC_IDLE state) or an RRC connection resumption procedure (if the UE is in an RRC_INACTIVE state), and once the UE is in an RRC_CONNECTED state, the buffered QoE data may be sent, for example, to an operations, administration, and maintenance (OAM) entity via a network entity (e.g., NG-RAN). According to some aspects, in response to being instructed to deactivate a QoE configuration or otherwise determining that deactivation is necessary, the UE may store buffered QoE data and store the deactivated QoE configuration, but cease further QoE measurement collection. Storing the deactivated QoE configuration may reduce the time required to reactivate the QoE configuration if reactivation is necessary.

[0025] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 As an illustrative example and not a limitation, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0026] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, commonly referred to as 5G. As another example, the RAN 104 may operate in accordance with a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of this disclosure.

[0027] As illustrated, the RAN 104 includes multiple network entities 108 (e.g., base stations, gNBs, TRPs, scheduling entities). Broadly speaking, a network entity can be implemented in a converged or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and can include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some examples, a network entity can be a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a network entity may be referred to variously by those skilled in the art as a base station, a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a network access node, a Node B (NB), an eNode B (eNB), a gNode B (gNB), a transmit receive point (TRP), a scheduling entity, or some other suitable terminology. In some examples, the network entity 108 may include two or more TRPs that may or may not be co-located. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where the RAN 104 operates according to both LTE and 5G NR standards, one of the network entities may be an LTE network entity, while the other network entity may be a 5G NR network entity.

[0028] The RAN 104 is also illustrated as supporting wireless communications for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to them as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, a scheduled entity, or some other suitable terminology. A UE (e.g., UE 106) may be a device (e.g., a mobile device) that provides a user with access to network services.

[0029] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, but may be stationary. The term mobile device or mobile equipment refers broadly to a wide variety of devices and technologies. A UE may include a plurality of hardware structural components sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to one another. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems (e.g., corresponding to the "Internet of Things" (IoT)).

[0030] The mobile device may also be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart meter, etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electrical power (e.g., a smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment. Furthermore, the mobile device may provide connected medical or telemedicine support, such as healthcare at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be prioritized or given priority over other types of information, for example, in terms of priority access for the transmission of critical service data and / or associated QoS for the transmission of critical service data.

[0031] The wireless communication between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions from a network entity (e.g., network entity 108) to one or more UEs (e.g., similar to UE 106) over the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" can refer to point-to-multipoint transmissions originating at a network entity (e.g., network entity 108). Another way to describe this scenario can be to use the term "broadcast channel multiplexing." Transmissions from a UE (e.g., UE 106) to a network entity (e.g., network entity 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" can refer to point-to-point transmissions originating at a UE (e.g., UE 106).

[0032] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., network entity 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by a scheduling entity (e.g., network entity 108).

[0033] Network entities are not the only entities that can act as scheduling entities. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0034] like Figure 1 , a network entity 108 may broadcast downlink traffic 112 to one or more UEs 106 (e.g., one or more scheduled entities). Broadly speaking, a network entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more UEs 106 (e.g., one or more scheduled entities) to the network entity 108. On the other hand, a UE 106 (e.g., a scheduled entity) is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the network entity 108. The UE 106 may also send uplink control information 118 to the network entity 108, including, but not limited to, scheduling requests or feedback information or other control information.

[0035] In addition, uplink control information 118 and / or downlink control information 114 and / or uplink traffic 116 and / or downlink traffic 112 can be sent on a waveform that can be divided into frames, subframes, time slots and / or symbols. As used herein, a symbol can refer to a time unit in an orthogonal frequency division multiplexing (OFDM) waveform that carries one resource element (RE) per subcarrier. A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 ms. Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Within the present disclosure, a frame can refer to a predetermined duration (e.g., 10 ms) for wireless transmission, where each frame consists of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms can be utilized, and the various time divisions of a waveform can have any suitable duration.

[0036] Generally speaking, the network entities 108 may include a backhaul interface for communicating with the backhaul portion 120 of the wireless communication system 100. The backhaul portion 120 may provide a link between the network entities 108 and the core network 102. Furthermore, in some examples, a backhaul network may provide interconnection between the respective network entities 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0037] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards, such as 5G Core (5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0038] Now refer to Figure 2 , by way of illustrative example and not limitation, a schematic illustration of an example of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 may be similar to the ones described above and in Figure 1 The same as the RAN 104 illustrated in FIG.

[0039] The geographic area covered by the RAN 200 may be divided into several cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or network entity within the geographic area. Figure 2Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same network entity. A radio link within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by multiple groups of antennas, each of which is responsible for communicating with UEs in a portion of the cell.

[0040] Various network entity arrangements can be utilized. For example, Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown controlling a remote radio head (RRH) 216 in cell 206. That is, the base stations may have integrated antennas or may be connected to antennas or RRHs 216 by feeder cables. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells having large sizes. Additionally, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a small cell, micro cell, pico cell, femto cell, home base station, home node B, home eNode B, etc.) because base station 218 supports cells having relatively small sizes. Cell size settings may be made based on system design and component constraints.

[0041] It should be understood that the RAN 200 may include any number of network entities (e.g., base stations, gNBs, TRPs, scheduling entities) and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The network entity 108 is the same as or similar to the network entity 108 illustrated in FIG.

[0042] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which can be a drone (e.g., a quadcopter, an octocopter, a remotely piloted aircraft, etc.). The UAV 220 can be configured to act as a base station, or more specifically, as a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as the UAV 220).

[0043] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may be in communication with base station 210, UEs 226 and 228 may be in communication with base station 212, UEs 230 and 232 may be in communication with base station 214 via RRH 216, UE 234 may be in communication with base station 218, and UE 236 may be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be in communication with the base stations described above and in Figure 1 In some examples, the UAV 220 may be a mobile network entity and may be configured to act as a UE. For example, the UAV 220 may operate within the cell 202 by communicating with the base station 210.

[0044] In another aspect of the RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communications can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) can communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 can each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) can also communicate sidelink signals 227 via a direct link (sidelink) without having to transmit the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communications.

[0045] In order to achieve a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel coding can be used. That is, wireless communications typically utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a codec) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message improves the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0046] Data decoding can be implemented in a variety of ways. In early 5G NR specifications, user data was decoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one for large code blocks and / or high code rates, and another for other cases. Polar decoding was used to decode control information and the Physical Broadcast Channel (PBCH) based on nested sequences. For these channels, rate matching was performed using puncturing, shortening, and repetition.

[0047] Aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of network entities and UEs may include suitable hardware and capabilities (eg, encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communications.

[0048] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. The various physical channels between the UE and the RAN 200 are generally established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may fully or partially manage security context for both control plane functions and user plane functions.

[0049] In various aspects of the present disclosure, RAN 200 can utilize either DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, a UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 224 can move from the geographic area corresponding to its serving cell 202 to the geographic area corresponding to neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 for a given amount of time, UE 224 can send a report message to its serving base station 210 indicating this. In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0050] In a network configured for UL-based mobility, the network may utilize a UL reference signal from each UE to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive carrier frequency and slot timing from these synchronization signals, and transmit uplink pilots or reference signals in response to the derived timing. The uplink pilot signals transmitted by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., base stations 210 and 214 / 216 and / or one or more of the central nodes within the core network) may determine a serving cell for UE 224. As UE 224 moves through RAN 200, RAN 200 may continue to monitor the uplink pilot signals sent by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, RAN 200 may hand over UE 224 from the serving cell to a neighboring cell with or without notifying UE 224.

[0051] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 may be uniform, the synchronization signals may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. The use of zones in 5G networks or other next-generation communication networks implements an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0052] In various implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. While some technical regulations generally still need to be adhered to to access unlicensed spectrum, generally any operator or device can gain access. Shared spectrum may fall between licensed and unlicensed spectrum, where technical regulations or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum may offer Licensed Shared Access (LSA) to share that spectrum with other parties (e.g., with appropriate licensee-determined conditions to gain access).

[0053] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0054] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0055] In view of the above aspects, unless otherwise specified, it should be understood that if the term "sub-6 GHz" is used in this document, it can be broadly referred to as less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specified, it should be understood that if the term "millimeter wave" is used in this document, it can be broadly referred to as less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specified, it should be understood that if the term "millimeter wave" is used in this document, it can be broadly referred to as less than 6 GHz, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0056] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other suitable multiple access schemes. Furthermore, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0057] The equipment in the radio access network 200 may also utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link in which two endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex emulation is often implemented for wireless links using time division duplexing (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, a channel is dedicated to transmissions in one direction, while at other times, the channel is dedicated to transmissions in the other direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation between the transmitter and receiver and suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links using frequency division duplexing (FDD) or space division duplexing (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication can be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplexing.

[0058] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network entity, a network element or network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

[0059] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0060] Base station type operation or network design can take into account the aggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which can enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0061] Figure 3 is a schematic diagram of an example disaggregated base station architecture 300 according to some aspects of the present disclosure. The disaggregated base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 342 via one or more radio frequency (RF) access links. In some implementations, a UE 342 may be served simultaneously by multiple RUs 340. For example, a UE 342 may be served by multiple RUs 340 in combination with a UE 342. Figure 1 and Figure 2 Any of the UEs or scheduled entities illustrated and described are the same or similar.

[0062] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interface of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more of the other units via the wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit signals, or both, to one or more of the other units via the wireless transmission medium.

[0063] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0064] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split, such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, the DU 330 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0065] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 342. In some implementations, both real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0066] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0067] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0068] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 325. This information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0069] Will refer to Figure 4 Various aspects of the present disclosure are described using schematically illustrated OFDM waveforms. Those skilled in the art will appreciate that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles can also be applied to SC-FDMA waveforms.

[0070] Now refer to Figure 4 , illustrates an expanded view of an exemplary subframe 402 showing an OFDM resource grid according to some aspects of the present disclosure. However, as those skilled in the art will readily appreciate, the physical (PHY) transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is measured in units of OFDM symbols in the horizontal direction; and frequency is measured in units of subcarriers of a carrier in the vertical direction.

[0071] Resource grid 404 can be used to schematically represent the time-frequency resources used for a given antenna port. That is, in a multiple-input, multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding number of resource grids 404 can be available for communication. Resource grid 404 is divided into multiple resource elements (REs) 406. An RE (which is 1 subcarrier x 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB), or more simply, a resource block (RB) 408, which can contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB can include any suitable number of consecutive OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to communication in a single direction (either transmission or reception for a given device).

[0072] A collection of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmissions may involve scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of resource grid 404. In some examples, an RB may be the smallest unit of resource that can be allocated to a UE. Therefore, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. RBs may be scheduled by a scheduling entity, such as a network entity (e.g., a base station, gNB, TRP, scheduling entity), or may be self-scheduled by the UE implementing D2D sidelink communication.

[0073] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, although this is only one possible example.

[0074] Each 1ms subframe 402 may be composed of one or more adjacent time slots. Figure 4In the example shown in FIG, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots (sometimes referred to as shortened transmit time intervals (TTIs)) with shorter durations (e.g., 1 to 3 OFDM symbols). These mini-slots or shortened transmit time intervals (TTIs) may, in some cases, be transmitted by occupying resources scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0075] An expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. Generally speaking, the control region 412 may carry a control channel, and the data region 414 may carry a data channel. Of course, a time slot may include all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The structure illustrated in is merely exemplary in nature, and different slot structures may be utilized, and these slot structures may include one or more regions in each of the control region and the data region.

[0076] Although Figure 4 Although not illustrated in the figure, various REs 406 within RB 408 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 406 within RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channels, which may enable coherent demodulation / detection of the control channel and / or data channel within RB 408.

[0077] In some examples, time slot 410 can be utilized for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications can refer to point-to-multipoint transmissions from one device (e.g., a network entity, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications can refer to point-to-point transmissions from one device to a single other device.

[0078] In the example of cellular communication on a cellular carrier via a Uu interface, for downlink transmissions, a scheduling entity (e.g., a network entity) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry downlink control information, including one or more downlink control channels, such as a physical downlink control channel (PDCCH). The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for downlink and uplink transmissions. The PDCCH may further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those skilled in the art, wherein the integrity of packet transmissions may be verified on the receiving side for accuracy, for example, using any suitable integrity checking mechanism, such as a checksum or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, while if it is not, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0079] The network entity may further allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS), a phase tracking reference signal (PT-RS), a channel state information (CSI) reference signal (CSI-RS), and a synchronization signal block (SSB). The SSBs may be broadcast at regular intervals based on a periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, or 160 ms). The SSBs include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS for radio frame, subframe, slot, and symbol synchronization in the time domain, for identifying the center of the channel (system) bandwidth in the frequency domain, and for identifying the physical cell identity (PCI) of the cell.

[0080] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding system information blocks (SIBs). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The network entity may also send other system information (OSI).

[0081] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 406 to a scheduling entity to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH). UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, UCI may include a scheduling request (SR), i.e., a request to a scheduling entity to schedule an uplink transmission. In this document, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other suitable UCI.

[0082] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data. Such data may be carried on one or more traffic channels, such as, for DL ​​transmissions, on the physical downlink shared channel (PDSCH); or for UL transmissions, on the physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS. In some examples, the PDSCH may carry multiple SIBs, not limited to SIB1 discussed above. For example, OSI may be provided in these SIBs (e.g., SIB2 and above).

[0083] In an example of sidelink communication on a sidelink carrier via a Proximity Services (ProSe) PC5 interface, the control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH), which includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., a Rx V2X device or other Rx UE). The data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH), which includes sidelink data transmitted by the initiating (transmitting) sidelink device within resources reserved by the transmitting sidelink device on the sidelink carrier via the SCI. Other information may also be transmitted via various REs 406 within the time slot 410. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 410. Additionally, one or more reference signals may be sent within slot 410, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0084] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of bits of information (e.g., the amount of bits of information), may be a controlled parameter.

[0085] Combined with the above Figures 1 to 4 The channels or carriers described are not necessarily all channels or carriers that can be used between the scheduling entity and the scheduled entity. A person skilled in the art will recognize that other channels or carriers (such as other service, control and feedback channels) may be used in addition to the channels or carriers illustrated.

[0086] Figure 55G user plane protocol stack 502 and 5G control plane protocol stack 504 according to some aspects of the present disclosure. User plane protocol stack 502 depicts a UE user plane protocol stack 506 and a network entity user plane protocol stack 508 (e.g., the network entity may be a gNB or NG-RAN). Both UE user plane protocol stack 506 and network entity user plane protocol stack 508 include the following layers: physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, internet protocol (IP) layer, and application layer 509. The functions of each of these layers are well known and will not be presented herein for the sake of brevity. Various layers are sometimes referred to individually or collectively as layer 1, layer 2, or layer 3. For example, the PHY layer is often referred to as layer 1, and the MAC layer, RLC layer, and PDCP layer are often referred to as layer 2. The SDAP layer may be referred to as layer 3.

[0087] The control plane protocol stack 504 depicts a UE control plane protocol stack 510, a network entity control plane protocol stack 512, and a next generation (NG) core control function protocol stack 514 (where the core control function may be, for example, an access and mobility management function (AMF)). The UE control plane protocol stack 510 includes the following layers: a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer 516, and a non-access stratum (NAS) layer 518. The network entity control plane protocol stack 512 includes the following layers: a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a radio resource control (RRC) layer 517. The NG core control function protocol stack 514 includes a non-access stratum (NAS) 519 layer. As with the user plane protocol stack 502, the functions of each layer in the control plane protocol stack 504 are well known and will not be presented herein for the sake of brevity. Similar to the user plane protocol stack 502, the PHY layer is referred to as layer 1, and the MAC layer, RLC layer, and PDCP layer are referred to as layer 2. The RRC layer and NAS layer may be referred to as layer 3. Figure 5As depicted, RRC layers 516 and 517 are present in the control plane protocol stack 504. The UE RRC layer 516 of the UE control plane protocol stack 510 interfaces with the network entity RRC layer 517 of the network entity control plane protocol stack 512. The interface may be a Uu interface (not shown). The UE NAS layer 518 interfaces with the NG core NAS layer 519. The RRC layer and NAS layer are not present in the user plane protocol stack 502. Operations within the RRC layer are governed by the current state of the UE RRC layer 516. The state of the UE RRC layer 516 can transition between RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE.

[0088] The non-access stratum is concerned with protocols between the UE and the core network that do not terminate at the Radio Access Network (RAN), exemplified here as a network entity. Figure 5 NAS messages may be passed transparently through the RAN (via the network entity control plane protocol stack 512) as illustrated in the control plane protocol stack 504 of FIG. The NAS layer may be used to establish a communication session and maintain continuous communication with the UE as the UE moves. A different layer, referred to as the access stratum (AS), may be responsible for carrying information over the radio portion of the network between the UE and the network entity. While NAS may be used for communication between the UE and the NG core (e.g., as in conjunction with Figure 1 The AS is used for dialogues between the UE and network entities (e.g., RAN, gNB) as shown and described.

[0089] The access stratum can be considered as a functional grouping that includes network entity infrastructure and parts within the UE, as well as protocols between these parts related to access technology (i.e., how a specific physical medium between the UE and the network entity is used to carry information). The access stratum provides services related to the transmission of data over the radio interface and the management of the radio interface. An access stratum connection can refer to a peer-to-peer access stratum connection between a UE and a network entity (e.g., NG-RAN, gNB) for 3GPP access. As used herein, an access stratum connection corresponds to an RRC connection via a Uu reference point or interface (not shown). Other access stratum connections are also within the scope of this disclosure.

[0090] Figure 66 is a diagram illustrating state transitions between three radio resource control (RRC) states 600 in 5G according to aspects of the present disclosure. In 5G NR, RRC has three states: RRC_CONNECTED 602, RRC_INACTIVE 604, and RRC_IDLE 606. A functionality is associated with each UE RRC state. For example, when in the RRC_IDLE 606 state, the UE may be configured for discontinuous reception (DRX), which may be a functionality configured to the UE by the NAS. In the RRC_IDLE 606 state, the UE's functionality may include paging (initiated by the core network). In the RRC_IDLE 606 state, the UE may have a core network ID (CN ID) that uniquely identifies the UE within a tracking area. However, in the RRC_IDLE 606 state, there is no RRC context associated with the UE stored in a network entity.

[0091] In the RRC_INACTIVE 604 state, the UE may also be configured for DRX; however, in the RRC_INACTIVE 604 state, DRX may be configured by the NAS or a network entity. Similarly, in the RRC_INACTIVE 604 state, the UE's functionality may include paging; however, in the RRC_INACTIVE 604 state, paging may be initiated by the core network or a network entity. In the RRC_INACTIVE 604 state, the network entity may identify the RAN-based Notification Area (RNA) to which the UE belongs. In the RRC_INACTIVE 604 state, the UE AS context is stored at both the UE and the network entity, and a 5GC to NG-RAN connection in both the control plane and the user plane is established for the UE. In general, in both the RRC_IDLE 606 state and the RRC_INACTIVE 604 state, UE-controlled mobility is based on network configuration (e.g., call reselection).

[0092] In the RRC_CONNECTED 602 ​​state, there is network-controlled mobility within the NR and network-controlled mobility to / from the eUTRAN. DRX can be configured by a network entity in the RRC_CONNECTED state. The UE can perform and report neighbor cell measurements, the network can send data to and / or receive data from the UE, and the NG-RAN can identify the cell to which the UE belongs. Generally speaking, in both the RRC_INACTIVE 604 state and the RRC_CONNECTED 602 ​​state, the UE and the NG-RAN store the UE AS context (e.g., RRC context) and establish a 5GC to NG-RAN connection in both the control plane and the user plane for the UE. In summary, in the RRC_INACTIVE state and the RRC_CONNECTED state, the UE and the NG-RAN store the AS inactive context and the AS context, respectively. In the RRC_IDLE state, the UE can be registered with the core network (CN), but does not store the AS context.

[0093] The UE can transition between three RRC states. For example, the RRC_IDLE to RRC_CONNECTED transition can occur via an RRC connection establishment procedure, which may include three messages: (UE-initiated) RRCSetupRequest, RRCSetup, and RRCSetupComplete (not shown).

[0094] The RRC_CONNECTED to RRC_IDLE transition may be via an RRC connection release procedure with a network-initiated RRCRelease message (not shown). Upper layers in the UE may also request a release. An RRC connection may also be released due to connection failures such as radio link failure, handover failure, or cell not meeting cell selection criteria.

[0095] The RRC_CONNECTED to RRC_INACTIVE transition may be network-initiated. The transition may be entered via an RRCRelease message with the suspendConfig information element (IE). The suspendConfig IE may not be configured when the UE is using a Dual Active Protocol Stack (DAPS) bearer or is redirected to an inter-RAT carrier frequency.

[0096] The network may trigger the RRC_INACTIVE to RRC_CONNECTED transition via RAN paging. The paged UE may begin with the RRC connection recovery procedure, which includes three messages: RRCResumeRequest, RRCResume (or RRCSetup), and RRCResumeComplete (or RRCSetupComplete) (not shown). The UE may also initiate this procedure for uplink transfer, including RNA update.

[0097] When the network responds to RRCResumeRequest with RRCRelease, the RRC_INACTIVE to RRC_IDLE transition may occur. Alternatively, the UE may be commanded or expected to remain in RRC_INACTIVE for a given amount of time. According to some aspects, the RRC_INACTIVE state may be a way for the UE RRC to achieve an always-on radio connection with the network.

[0098] Figure 7 7 is a call flow diagram 700 illustrating activation of QoE measurement collection (QMC) according to some aspects of the present disclosure. The call flow diagram 700 depicts a trace collection entity / measurement collection entity (TCE / MCE) 702, an OAM 704, a CN 706, an NG-RAN 708, a UE access stratum (UE AS) 710 (e.g., a UE RRC layer), and a UE application layer (UE App) 712. The UE may initially convey UE capability information 714 to the NG-RAN 708 via the UE AS 710.

[0099] Quality of Experience (QoE) is a measure that characterizes the human experience of a service delivered to an end user's device (e.g., UE, wireless communication device) over a network. QoE may be enhanced to support new service types such as augmented reality (AR), mixed reality (MR), extended reality (XR), multicast and broadcast services (MBS), and other service types that may be considered now or in the future in conjunction with, for example, video and streaming delivery of immersive media, including but not limited to delivery of such services in high mobility scenarios such as, but not limited to, high-speed trains. In accordance with some aspects, QoE may be enhanced to support the collection of QoE data when the UE is in RRC_INACTIVE or RRC_IDLE state. Such enhancements may be used, for example, in conjunction with multicast and broadcast services (MBS), or at least for broadcast services (where broadcasts continue even if the UE is in RRC_INACTIVE or RRC_IDLE state).

[0100] In QoE measurement, an application layer QoE measurement configuration may be received from an operation, administration, and maintenance (OAM) entity or a core network (CN). The application layer QoE measurement configuration may be encapsulated in a first transparent container, which may be forwarded to the UE App 712 layer (e.g., as combined with a downlink RRC message (e.g., in an RRCReconfiguration message)). Figure 5 UE application layer 509 shown and described). Although the first transparent container is forwarded by the RRC layer, the RRC layer does not unpack the container. In other words, the downlink message in the container is transparent to the RRC layer.

[0101] Thereafter, QoE measurements may be configured and activated, for example, in the application layer. Application layer measurements (e.g., QoE measurements) received from higher layers of the UE may then be encapsulated in a second transparent container (e.g., a transparent reporting container) and transmitted from the UE application layer to the CN 706 or OAM 704 via an uplink RRC message. Although the second transparent container is forwarded via the RRC layer (e.g., via the UE AS 710), the RRC layer does not unpack the container. In other words, the uplink message within the second transparent container is transparent to the RRC layer. According to some aspects, the QoE report may be transmitted via a signaling radio bearer (SRB), which may be separate from other SRBs because the QoE report may have a lower priority than other SRB transmissions.

[0102] The QoE measurement collection feature may enable the collection of application layer measurements from the UE. According to some aspects, supported service types include, but are not limited to: QoE measurement collection for streaming services; QoE measurement collection for multimedia telephony services over IP Multimedia Subsystem (MTSI) services; and QoE measurement collection for virtual reality (VR) services. As described above, enhancements to QoE measurement may include other services.

[0103] The QoE measurement collection feature can be activated in the NG-RAN 708 by signaling from the OAM 704 via the CN 706 (i.e., signaling-based 716 QoE measurement collection activation) or by direct configuration from the OAM 704 (i.e., management-based 722 QoE measurement collection activation). One or more QoE measurement collection jobs can be activated per service type at the UE. A QoE reference uniquely identifies each QoE measurement configuration.

[0104] For signaling-based 716 QoE measurement collection activation, OAM 704 may initiate QoE measurement activation for a specific UE via CN 706. For example, OAM 704 may transmit a Configure QoE Measurement Collection 718 message to CN 706. The Configure QoE Measurement Collection 718 message may carry QoE measurement configuration information.

[0105] In response to receiving the Configure QoE Measurement Collection 718 message, the CN 706 may transmit an Activate QoE Measurement Collection 720 message carrying the QoE measurement configuration data to the NG-RAN 708. The application layer QoE measurement configuration information received by the NG-RAN 708 from the OAM 704 or the CN 706 may be encapsulated in a transparent container, which is forwarded to the UE as an application layer configuration in an RRCReconfiguration 724 message (multiple configurations may be present in the same message).

[0106] For management-based activation of QoE measurement collection 722, OAM 704 may transmit one or more QoE measurement configurations to NG-RAN 708. The QoE measurement configurations for management-based activation of QoE measurement collection 722 may also include a list of application-layer QoE measurement configurations and corresponding information for QoE measurement collection. Each application-layer QoE measurement configuration may be encapsulated in a transparent container. For example, NG-RAN 708 may select one or more UEs that meet the required QoE measurement capabilities, area scope, and slice scope.

[0107] The NG-RAN 708 may receive one or more QoE measurement configurations via UE-associated signaling (from a signaling-based 716 QoE measurement collection activation or a management-based 722 QoE measurement collection activation). The QoE measurement configuration information may include an application layer QoE measurement configuration list and corresponding information for QoE measurement collection. The QoE measurement configuration information including the application layer QoE measurement configuration list and corresponding information for QoE measurement collection may be received by the NG-RAN 708 in a transparent container (e.g., a QoE measurement configuration container, such as the first transparent container described above). The QoE measurement configuration list in the transparent QMC configuration container (e.g., an Extensible Markup Language (XML) file) may include the following information: a QoE reference, a service type, an MCE IP address, a slice range, an area range, Minimization of Drive Tests (MDT) alignment information, and an indication of available RAN-visible QoE metrics.

[0108] In response to receiving the activate QoE measurement collection 720 message, the NG-RAN 708 may forward the corresponding QoE measurement configuration to the UE AS 710 (e.g., the UE RRC layer) in a downlink RRC message (e.g., the RRCReconfiguration 724 message). The RRCReconfiguration 724 message may include, for example, a QoE measurement configuration container (e.g., an XML document), a service type, and a measConfigAppLayerID. The mapping between the measConfigAppLayerID and the QoE reference may be maintained in the NG-RAN 708.

[0109] In response to receiving the RRCReconfiguration 724 message, the UE AS 710 (eg, the UE RRC layer) may transmit an attention (AT) command 726 to the UE app layer 712. The AT command 726 may include, for example, a QoE measurement configuration container, a service type, and a measConfigAppLayerID.

[0110] Figure 8 is a call flow diagram 800 illustrating QoE measurement reporting according to some aspects of the present disclosure. Figure 7 middle, Figure 8 Call flow diagram 800 includes TCE / MCE 802, OAM 804, CN 806, NG-RAN 808, UE AS 810 (e.g., UE RRC layer), and UE App layer 812. UE App layer 812 can handle QoE measurement collection. For example, application layer measurement reports received from higher layers of the UE can be encapsulated in a transparent container in a MeasurementReportAppLayer RRC message over SRB4. The UE can transmit multiple application layer measurement reports to the gNB in ​​one MeasurementReportAppLayer message. measConfigAppLayerId can be used to identify an application layer measurement configuration and report between NG-RAN 808 and the UE (e.g., UE AS 810, UE RRC layer). The application layer measurement report can be forwarded to OAM along with a QoE reference.

[0111] To allow sending application layer measurement reports that exceed the maximum PDCP SDU size, the gNB may enable segmentation of the MeasurementReportAppLayer message. Segmentation may allow sending application layer measurement reports that exceed the maximum PDCP SDU size. Existing RRC segmentation mechanisms may apply.

[0112] The measConfigAppLayerId signaled in RRC signaling can be used to identify application layer measurement configurations and reports between the gNB and the UE. The RRC identifier can be mapped to a QoE reference in the gNB. The application layer measurement report can be forwarded to the OAM along with the QoE reference. A network entity (e.g., NG-RAN 708, gNB, base station) can release one or more application layer measurement configurations from the UE at any time in an RRCReconfiguration724 message. The UE can also be configured by the network entity to report when a QoE measurement session starts or stops for a particular application layer measurement configuration.

[0113] As indicated, the UE App layer 812 may send a QoE measurement report to the UE AS 810 in a transparent reporting container. The UE AS 810 may send the transparent reporting container including the QoE measurement report (i.e., QoE measurement results) to the NG-RAN 808 in an uplink RRC message. In more detail, the UE App layer 812 may transmit an AT command 814 (with the QoE measurement report) to the UE AS 810 (e.g., the UE RRC layer). At 816, in response to receiving the AT command 814, the UE AS 810 may forward the measurement report for each application layer to the NG-RAN 810. The QoE measurement report may be encapsulated in a QoE report container and may include a measConfigAppLayerID for each app layer. The QoE report container may be transparent to the UE AS 810. At 818 , the NG-RAN 808 may send the QoE measurement report in a QoE transparent reporting container and the corresponding QoE reference ID to the OAM 804 and / or TCE / MCE 802 .

[0114] QoE measurement collection is handled by application layer measurement configuration and measurement reporting, and is currently only supported in the RRC_CONNECTED state. However, this document describes features that facilitate measurement reporting to continue in either or both of the RRC_INACTIVE and RRC_IDLE states.

[0115] Figure 9 is a call flow diagram 900 illustrating deactivation or release of QoE measurement collection (QMC) according to some aspects of the present disclosure. Figure 7 and Figure 8 middle, Figure 9 The call flow diagram 900 includes TCE / MCE 902, OAM 904, CN 906, NG-RAN 908, UE AS 910 (e.g., UE RRC layer) and UE App layer 912.

[0116] The following conditions may result in the deactivation or release of a QoE measurement collection job. In one example, the OAM 904 may send a Configure QoE Deactivate 914 message, which may trigger the deactivation of a list of QoE measurement collection jobs. In some examples, the deactivation of QoE measurement collection may be achieved by providing a list of QoE reference values. In another example, the NG-RAN 908 may release one or more application layer measurement configurations from the UE in an RRCReconfiguration 918 message at any time. According to some aspects, if the UE enters the RRC_IDLE state, the UE may release all QoE measurement configurations. In one example, upon receiving a release command at the UE, if a QoE measurement configuration is released, the UE AS 910 (e.g., the UE RRC layer) may notify upper layers (e.g., the UE App layer 912) to release the QoE measurement configuration.

[0117] In more detail, OAM 904 may send a Configure QoE Deactivation 914 message to CN 906. The Configure QoE Deactivation 914 message may include a deactivation indication and a QoE reference. CN 906 may, in turn, send a Disable QoE Measurement 916 message to NG-RAN 908. The Disable QoE Measurement 916 message may include a deactivation indication and a QoE reference. NG-RAN 908 may, in turn, send an RRCReconfiguration 918 message to UE AS 910 (e.g., UE RRC layer). The RRCReconfiguration 918 message may include a deactivation indication and measConfigAppLayerID. The network may replace one configuration with another by deactivating the existing measurement and configuring another measurement of the same configuration type.

[0118] For broadcast communication services, the same service and the same specific content data are provided simultaneously to all UEs in a geographic area (i.e., all UEs authorized to receive data in the broadcast service area). Broadcast communication services are delivered to UEs using broadcast sessions. UEs can receive broadcast communication services in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. UEs can receive MBS configurations for broadcast sessions (e.g., parameters required for Multicast Traffic Channel (MTCH) reception) via a Multicast Configuration Channel (MCCH) in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. Parameters required for receiving the MCCH may be provided via system information.

[0119] In one aspect, a first QoE configuration may be activated at the UE. In one example, the UE may transition from the RRC_CONNECTED state to the RRC_IDLE or RRC_INACTIVE state. Currently, when a UE in the RRC_IDLE or RRC_INACTIVE state collects QoE data for a broadcast service, the UE buffers the collected QoE data. However, the UE will not trigger an RRC connection procedure or an RRC recovery procedure for QoE reporting purposes. Therefore, the UE transmits QoE data only after the UE enters the RRC_CONNECTED state for other reasons (i.e., reasons unrelated to QoE reporting). However, when the QoE configuration is deactivated, currently, the UE deletes the buffered QoE data, and thus the buffered QoE data is lost.

[0120] According to various aspects herein, features are described for avoiding data loss for buffered data collected in the RRC_IDLE and / or RRC_INNACTIVE states in response to receiving a command to deactivate the current QoE configuration. According to one aspect, when a given QoE configuration is deactivated, the UE initiates an RRC connection establishment procedure or an RRC connection resumption procedure. Thus, when the UE determines to deactivate the QoE configuration, the UE initiates an RRC connection establishment procedure or an RRC connection resumption procedure and enters the RRC_CONNECTED state to report QoE data buffered while the UE was in the RRC_IDLE and / or RRC_INACTIVE states.

[0121] According to another aspect, when the UE determines to deactivate the QoE configuration, the UE buffers the QoE data (ie, saves the buffered QoE data) but stops QoE measurement. In addition, the UE may retain (eg, store, maintain in memory) the deactivated QoE configuration.

[0122] Figure 10 1000 is a call flow diagram illustrating accumulating quality of experience (QoE) data in a buffer during RRC_INACTIVE and / or RRC_IDLE states, and reporting the buffered QoE data in response to receiving a QoE measurement collection (QMC) deactivation indication, according to some aspects of the present disclosure. Figure 7 、 Figure 8 and Figure 9 middle, Figure 10 The call flow diagram 1000 includes OAM 1004, CN 1006, NG-RAN 1008, UE AS 1010 (eg, UE RRC layer), and UE App layer 1012. To avoid cluttering the drawing, TCE / MCE are not illustrated.

[0123] exist Figure 10In the example of FIG, the UE has entered the RRC_CONNECTED state 1014 before being configured with the QoE measurement configuration information. However, this is merely an example presented for ease of illustration. The UE may enter the RRC_CONNECTED state before or after being configured with the QoE measurement configuration information.

[0124] Figure 10 Describes signaling-based QoE measurement collection activation (e.g., similar to Figure 7 716 QoE measurement collection activation based on signaling). However, the depiction of QoE measurement collection activation based on signaling is not intended to be limiting. Signaling-based QoE measurement collection activation or management-based QoE measurement collection activation (e.g., similar to that in conjunction with Figure 7 The illustrated and described management-based 722 QoE Measurement Collection Activation) may be used to configure and activate QoE Measurement Collection (QMC) at a UE.

[0125] exist Figure 10 In the example of FIG. 1 , OAM 1004 may transmit a Configure QoE Measurement Collection 718 message to CN 1006. Configure QoE Measurement Collection 1018 message may carry QoE measurement configuration information.

[0126] In response to receiving the Configure QoE Measurement Collection 1018 message, the CN 1006 may transmit an Activate QoE Measurement Collection 1020 message carrying the QoE measurement configuration data to the NG-RAN 708. The application layer QoE measurement configuration information received by the NG-RAN 1008 from the OAM 1004 (e.g., in signaling-based QoE measurement collection activation) or the CN 1006 (e.g., in measurement-based QoE measurement collection activation, not shown) may be encapsulated in a transparent container, which may be forwarded to the UE as application layer QoE measurement configuration data in an RRCReconfiguration 1024 message (multiple configurations may be present in the same message).

[0127] In response to receiving the RRCReconfiguration 1024 message, the UE AS 710 (eg, the UE RRC layer) may transmit an AT command 1026 to the UE App layer 1012. The AT command 726 may include, for example, a QoE measurement configuration container, a service type, and a measConfigAppLayerID.

[0128] Thereafter, while in the RRC_CONNECTED state and as generally indicated at 1030, the UE may, for example, Figure 8Aspects of the call flow diagram 800 are shown and described to collect and report QoE measurement data (included in a QoE measurement report).

[0129] Subsequently, at 1032, the UE may have transitioned from the RRC_CONNECTED state to the RRC_INACTIVE state (e.g., with an RRC release command with a pause) or the RRC_IDLE state (with an RRC release command), both transitions being combined. Figure 6 When in the RRC_INACTIVE state or the RRC_IDLE state, the UE (eg, at the UE App layer 1012) may accumulate QoE data in a buffer.

[0130] During or at a certain point in time relative to the ongoing measurement and accumulation of QoE data in the buffer 1034, the OAM 1004 may send a Configure QoE Disable 1036 message to the CN 1006. The Configure QoE Disable 1036 message may carry information such as the following: Figure 9 Deactivation indication and QoE reference shown and described.

[0131] In response to receiving the Configure QoE Disable 1036 message, CN 1006 may transmit a Disable QoE Measurement 1038 message to NG-RAN 1008. The Disable QoE Measurement 1038 message may carry the information in conjunction with Figure 9 Deactivation indication and QoE reference shown and described.

[0132] In response to receiving the Deactivate QoE Measurement 1038 message, the NG-RAN 1008 may transmit an RRCReconfiguration 1040 message including a deactivation indication and measConfigAppLayerID to the UE AS 1010 (e.g., the UE RRC layer). The UE AS 1010 may transmit the deactivation indication and measConfigAppLayerID to the UE App layer 1012 in a first AT command 1042.

[0133] In response to receiving the first AT command 1042, the UE App layer 1012 may collect QoE data from the buffer and package the data in a report. The UE App layer 1012 may include the report in a transparent report container. The UE App layer 1012 may transmit the transparent report container (including the accumulated QoE data from the buffer in the report) and the measConfigAppLayerID to the UE AS 1010 in a second AT command 1044.

[0134] In response to receiving the second AT command 1044, or in response to receiving the RRCReconfiguration 1040 message, the UE AS 1010 may transition to a new RRC_CONNECTED state. Thereafter, the UE AS 1010 may transmit a MeasurementReportAppLayer 1048 message including a transparent report container and measConfigAppLayerID to the NG-RAN 1008.

[0135] exist Figure 10 In the example of FIG, in response to receiving the MeasurementReportAppLayer 1048 message, the NG-RAN 1008 transmits an OAM interface 1050 message including a transparent reporting container and a QoE reference to the OAM 1004. According to some aspects, the transparent reporting container and the QoE reference can be transmitted from the OAM 1004 or from the NG-RAN 1008 to the TCE / MCE (not shown).

[0136] Thus, aspects described herein may avoid loss of buffered QoE data collected by a UE while in RRC_INACTIVE state or RRC_IDLE state by reporting such data when QoE configuration is disabled while the UE is in RRC_INACTIVE state or RRC_IDLE state, rather than erasing such data.

[0137] In some examples, when the UE determines to deactivate the QoE configuration, if there is buffered QoE data, the UE may initiate an RRC connection establishment procedure or an RRC connection recovery procedure. In some examples, if there is buffered QoE when the QoE configuration is deactivated, the UE initiates an RRC connection establishment procedure or an RRC connection recovery procedure.

[0138] According to some aspects, there may be a criterion configured or preconfigured in the UE to assist the UE in determining whether to initiate an RRC connection establishment procedure or an RRC connection recovery procedure. By way of example and not limitation, the criterion may be one or a combination of: a data volume threshold (e.g., if the buffered QoE data is above (or below) the data volume threshold, the UE initiates an RRC connection establishment procedure or an RRC connection recovery procedure), a time threshold (or duration) against which a time for buffering or measuring QoE data may be established (e.g., if the duration for measuring or buffering QoE data is shorter than (or longer than) the time threshold, the UE initiates an RRC connection establishment procedure or an RRC connection recovery procedure), or configured QoE information (e.g., where the QoE information may be, but is not limited to, a service type, a slice, a QoE reference, an MBS session, or a QoE configuration RRC ID). As an example, if the QoE information of the buffered data corresponds to one or more of the configured QoE information, the UE may initiate an RRC connection establishment procedure or an RRC connection recovery procedure.

[0139] According to some aspects, the criteria may be configured to the AS layer (e.g., the RRC layer of the UE), and the AS layer may determine whether to initiate an RRC connection establishment procedure or an RRC connection recovery procedure, or the criteria may be configured to the application layer (e.g., the application layer of the UE), and the application layer may determine whether to deliver the buffered data to the AS layer. According to some aspects, the network may provide the criteria via an RRC message (e.g., an RRCReconfiguration or an RRCRelease message).

[0140] According to some examples, the RRC connection recovery procedure may also include a procedure for the UE to initiate a small data transfer (SDT) in the RRC_INACTIVE state. In addition, according to some aspects, when the QoE configuration is deactivated at the network, the UE may release the QoE configuration at the UE.

[0141] According to some aspects, when the UE determines to deactivate the QoE configuration, the UE may buffer QoE data but stop (or suspend) QoE measurement. According to some examples, when the UE determines to deactivate the QoE configuration, the UE may continue to buffer the collected QoE data, and the UE AS layer may instruct the UE application layer to suspend (temporarily stop) QoE measurement. In some examples, the UE application layer may continue the ongoing QoE measurement session but may not start a new QoE measurement session. In some examples, when the QoE configuration is deactivated, the UE may maintain (e.g., store, retain in memory) the current or current QoE configuration. In some examples, the UE may be configured with a timer by the network or pre-configured by the OEM. The timer may be used to determine when to discard the deactivated QoE configuration and the corresponding QoE data associated with the deactivated configuration. For example, and not limitation, if the timer expires, the UE may delete the QoE configuration and the corresponding QoE data, or the UE may initiate the RRC connection establishment procedure or RRC connection recovery procedure as described above.

[0142] In some examples, the UE may consider the QoE configuration to be deactivated under one or more of the following conditions: the QoE configuration validity timer expires, or the UE moves out of the range of the QoE area.

[0143] In some examples, the UE may reactivate the deactivated QoE configuration under one or more of the following conditions: the UE re-enters the QoE area range, or the UE receives a command from the network to reactivate the deactivated QoE configuration when entering the RRC_CONNECTED state.

[0144] Figure 11 is a block diagram illustrating an example of a hardware implementation of a wireless communication device 1100 (e.g., user equipment, scheduled entity) employing a processing system 1102 in accordance with some aspects. The wireless communication device 1100 may be similar to, for example, Figure 1 、 Figure 2 、 Figure 3 、 Figure 5 、 Figure 7 、 Figure 8 、 Figure 9 and / or Figure 10 Any of the wireless communication device, UE or scheduled entity.

[0145] According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1102 that includes one or more processors, such as a processor 1104. Examples of processor 1104 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic component, a discrete hardware circuit, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, the wireless communication device 1100 may be configured to perform any one or more of the functions described herein. That is, the processor 1104 as utilized in the wireless communication device 1100 may be used to implement, for example, Figure 6 、 Figure 7 、 Figure 8 、 Figure 9 and / or Figure 10 Any one or more of the methods or processes described and exemplified in the.

[0146] In this example, the processing system 1102 can be implemented using a bus architecture (generally represented by bus 1105). Bus 1105 can include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1102 and the overall design constraints. Bus 1105 communicatively couples various circuits including one or more processors (generally represented by processor 1104), memory 1110, and computer-readable media (generally represented by computer-readable media 1106). Bus 1105 can also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0147] The bus interface 1108 provides an interface between the bus 1105, the transceiver 1112, and one or more antenna arrays 1114. The transceiver 1112 can be, for example, a wireless transceiver. The transceiver 1112 provides a component for communicating with various other devices via a transmission medium (e.g., an air interface). The transceiver 1112 can be coupled to one or more antenna arrays 1114. The bus interface 1108 further provides an interface between the bus 1105 and a user interface 1116 (e.g., a keypad, display, touch screen, speaker, microphone, control features, etc.). Of course, such a user interface 1116 is optional and can be omitted in some examples.

[0148] One or more processors, such as processor 1104, may be responsible for managing bus 1105 and general processing, including executing software stored on computer-readable media 1106. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on computer-readable media 1106. When executed by processor 1104, the software causes the processing system 1102 to perform the various processes and functions described herein for any particular apparatus.

[0149] Computer-readable medium 1106 may be a non-transient computer-readable medium and may be referred to as a computer-readable storage medium or a non-transient computer-readable medium. Non-transient computer-readable medium may store computer executable code (e.g., processor executable code). Computer executable code may include a code for causing a computer (e.g., a processor) to implement one or more of the functions described herein. Non-transient computer-readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memories (RAMs), read-only memories (ROMs), programmable ROMs (PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1106 may reside in processing system 1102, be located outside processing system 1102, or be distributed across multiple entities including processing system 1102. Computer-readable medium 1106 may be embodied in a computer program product or article of manufacture. As an example, a computer program product or article of manufacture may include a computer-readable medium in packaging materials. In some examples, computer-readable medium 1106 may be part of memory 1110. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system. Computer-readable medium 1106 and / or memory 1110 may also be used to store data manipulated by processor 1104 when executing software. For example, memory 1110 may include a QoE data buffer 1120 that can accumulate QoE data while wireless communication device 1100 is in the RRC_INACTIVE state or the RRC_IDLE state. As another example, memory 1110 may store QoE configuration parameters 1122 that can be used to configure wireless communication device 1100 in conjunction with QoE measurement collection. Furthermore, memory 1110 may store timer values ​​1124 and / or thresholds 1126 as described herein.

[0150] In some aspects of the present disclosure, processor 1104 may include communication and processing circuitry 1141 configured for various functions, including, for example, communicating with a network entity (e.g., a gNB, a base station, a scheduled entity), a network core (e.g., a 5G core network), another wireless communication device (e.g., a UE, a scheduled entity), or any other entity (e.g., a local infrastructure or an entity communicating with the wireless communication device 1100 via the Internet (e.g., a network provider). In some examples, communication and processing circuitry 1141 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). Communication and processing circuitry 1141 may be further configured to execute communication and processing instructions 1151 (e.g., software) stored on computer-readable medium 1106 to implement one or more functions described herein.

[0151] In some aspects of the present disclosure, the processor 1104 may include a QoE measurement collection configuration circuit 1142 configured for various functions, including, for example, receiving AT commands (e.g., similar to the QoE measurement collection configuration circuit 1142 in conjunction with the QoE measurement collection configuration circuit 1142). Figure 10 AT command 1026 shown and described), and configuring the protocol layer of the wireless communication device according to the application layer QoE measurement configuration (e.g., as combined with Figure 10 UE App layer 1012 shown and described). The QoE measurement collection configuration circuit 1142 may also be configured to configure the container (e.g., as combined with Figure 10 1026). In some aspects, the QoE measurement collection configuration circuitry 1142 may be configured to, in response to determining to deactivate the QoE configuration message, stop accumulating QoE data in a buffer (e.g., in the QoE data buffer 1120 of the memory 1110) and store parameters associated with the QoE configuration (e.g., the application layer QoE measurement configuration received with the AT command). In one example, the QoE configuration may be stored in the QoE configuration parameters 1122 portion of the memory 1110. The QoE measurement collection configuration circuitry 1142 may be further configured to execute QoE measurement collection configuration instructions 1152 (e.g., software) stored on the computer-readable medium 1106 to implement one or more functions described herein.

[0152] In some aspects of the present disclosure, processor 1104 may include QoE measurement collection activation / deactivation / pause circuitry 1143 configured for various functions, including, for example, activating a Quality of Experience (QoE) configuration (e.g., the application-layer QoE measurement configuration described above in conjunction with QoE measurement collection configuration circuitry 1142). For example, the QoE configuration may be activated at the application layer of wireless communication device 1100. QoE measurement collection activation / deactivation / pause circuitry 1143 may also be configured for additional functions, such as reactivating the QoE configuration based on stored parameters of the QoE configuration in response to expiration of a timer. In another example, reactivating the QoE configuration may be responsive to determining at wireless communication device 1100 that the wireless communication device 1100 has moved into a predetermined QoE area after having been outside of the area, or receiving an indication from a network entity to reactivate the QoE configuration upon entering a new RRC_CONNECTED state. The stored parameters of the QoE configuration may be stored, for example, in QoE configuration parameters 1122 of memory 1110. The timer may be implemented, for example, using communication and processing circuitry 1141. The timer value may be stored, for example, in a timer value 1124 portion of memory 1110. In some examples, the timer or another timer may be started in response to deactivating a QoE configuration.

[0153] The QoE measurement collection activation / deactivation / pause circuit 1143 may also be configured for additional functionality, such as deactivating a QoE configuration and / or performing additional deactivation of a QoE configuration after an earlier reactivation of the QoE configuration. According to some aspects, the QoE measurement collection activation / deactivation / pause circuit 1143 may be configured such that, in response to receiving an indication from a network entity to deactivate the QoE configuration, the wireless communication device 1100 releases the QoE configuration. According to some aspects, deactivating the QoE configuration may occur in response to at least one of the following: expiration of a QoE configuration validity timer at the wireless communication device 1100, or a determination at the wireless communication device 1100 that the wireless communication device 1100 has moved outside of a predetermined QoE zone. According to one aspect, the QoE measurement collection activation / deactivation / pause circuit 1143 may be configured to start a timer in response to deactivating the QoE configuration (i.e., in response to receiving a deactivate QoE configuration message), and to delete the QoE configuration (e.g., stored in the QoE configuration parameters 1122 portion of the memory 1110) and the corresponding QoE data in the buffer (e.g., in the QoE data buffer 1120 of the memory 1110) in response to expiration of the timer.

[0154] The QoE measurement collection activation / deactivation / pause circuit 1143 may also be configured for additional functionality, such as conveying an indication to suspend QoE measurements from the RRC layer to the application layer of the wireless communication device 1100. The QoE measurement collection activation / deactivation / pause circuit 1143 may be further configured to execute QoE measurement collection activation / deactivation / pause instructions 1153 (e.g., software) stored on the computer-readable medium 1106 to implement one or more functions described herein.

[0155] In some aspects of the present disclosure, the processor 1104 may include an RRC connection establishment and RRC connection recovery circuit 1144 configured for various functions, including, for example, determining a transition between an RRC_CONNECTED state, an RRC_INACTIVE state, and an RRC_IDLE state of the wireless communication device 1100. According to some aspects, the RRC connection establishment and RRC connection recovery circuit 1144 may be configured for other functions, such as initiating an RRC connection establishment procedure from the RRC_IDLE state or initiating an RRC connection recovery procedure from the RRC_INACTIVE state in response to both having QoE data in a buffer (e.g., the QoE data buffer 1120 of the memory 1110) and deactivating the QoE configuration (i.e., obtaining a QoE deactivation message). In some aspects, the RRC connection establishment process and RRC connection recovery process circuit 1144 may be further configured to initiate a new RRC connection establishment process from a new RRC_IDLE state or a new RRC connection recovery process from a new RRC_INACTIVE state in response to both the presence of QoE data in a buffer (e.g., the QoE data buffer 1120 of the memory 1110) and an additional deactivation of the QoE configuration (i.e., obtaining an additional QoE deactivation message).

[0156] According to some aspects of the present disclosure, the RRC connection establishment process and RRC connection restoration process circuitry 1144 may be further configured to, for example, obtain criteria for determining whether to initiate an RRC connection establishment process or an RRC connection restoration process. In some examples, the criteria may be configured for the wireless communication device or may be preconfigured in the wireless communication device. In some examples, the criteria may include at least one of: a first threshold, with which the amount of QoE data in the buffer is compared; a second threshold, with which the time elapsed since the start of QoE data measurement or the start of accumulation of QoE data in the buffer is compared; or receiving QoE data associated with QoE information from a predetermined set of QoE information. In some examples, satisfying any one or more of the criteria may cause the wireless communication device to initiate an RRC connection establishment process or an RRC connection restoration process.

[0157] An example of a buffer may be a QoE data buffer 1120 in memory 1110. In some examples, the elapsed time may be measured by the communication and processing circuitry 1141, and a first threshold value compared to the amount of QoE data in the buffer and a second threshold value compared to the time elapsed since the start of QoE data measurement or the start of accumulation of QoE data in the buffer may be stored in a threshold value 1126 portion of memory 1110. In some examples, the predetermined set of QoE information may include at least one of the following: a service type, a slice range, a QoE reference, a multicast and broadcast service (MBS) session, or a QoE configuration RRC identifier. In some examples, the criteria may be configured to an RRC layer of the wireless communication device 1100, and the wireless communication device may be configured to obtain the criteria from the RRC layer and utilize the criteria by the RRC layer to determine whether to initiate an RRC connection establishment procedure or an RRC connection recovery procedure.

[0158] In some aspects, the criteria may be configured to an application layer of the wireless communication device 1100. The wireless communication device 1100 may be configured to obtain the criteria from the application layer and utilize the criteria by the application layer to determine whether to deliver the QoE data in the buffer to the RRC layer of the wireless communication device 1100. In some aspects, the wireless communication device 1100 may obtain the criteria via an RRC message received from a network entity. In some examples, the RRC connection recovery process includes initiating a small data transmission (SDT) during an RRC_INACTIVE state, and the SDT may be used to transmit the QoE data in the buffer (e.g., the QoE data buffer 1120 of the memory 1110) to the network entity. The RRC connection establishment process and RRC connection recovery process circuitry 1144 may be further configured to execute RRC connection establishment process and RRC connection recovery process instructions 1154 (e.g., software) stored on the computer-readable medium 1106 to implement one or more functions described herein.

[0159] In some aspects of the present disclosure, the processor 1104 may include a QoE data accumulation circuit 1145 configured for various functions, including, for example, accumulating QoE data in a buffer (e.g., the QoE data buffer 1120 of the memory 1110) while in a radio resource control (RRC) inactive state or an RRC_IDLE state after activating a QoE configuration, and accumulating new QoE data in a buffer while in a new RRC_INACTIVE state or a new RRC_IDLE state after reactivating a QoE configuration. The QoE data accumulation circuit 1145 may be further configured to transmit the QoE data in the buffer to a network entity after entering the RRC_CONNECTED state at the end of an RRC connection establishment procedure or an RRC connection recovery procedure, and further configured to transmit the new QoE data in the buffer to the network entity after entering a new RRC_CONNECTED state at the end of a new RRC connection establishment procedure or a new RRC connection recovery procedure. The QoE data accumulation circuitry 1145 may be further configured to execute QoE data accumulation instructions 1155 (eg, software) stored on the computer-readable medium 1106 to implement one or more functions described herein.

[0160] Figure 12 is a flow chart illustrating an example process 1200 (e.g., a method) for wireless communication at a wireless communication device according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some illustrated features may not be required for implementations of all embodiments. In some examples, the process 1200 may be performed by, for example, combining Figure 11 The wireless communication device 1100 may be similar to, for example, Figure 1 、 Figure 2 、 Figure 3 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 8 、 Figure 9 and / or Figure 10 In some examples, process 1200 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0161] At block 1202, the wireless communication device may activate a quality of experience (QoE) configuration. Figure 11 The illustrated and described QoE measurement collection activation / deactivation / pause circuitry 1143 may provide means for activating quality of experience (QoE) configuration.

[0162] At block 1204, the wireless communication device may accumulate QoE data in a buffer after activating the QoE configuration while in the radio resource control inactive (RRC_INACTIVE) state or the RRC_IDLE state. Figure 11 The illustrated and described QoE data accumulation circuit 1145 may provide means for accumulating QoE data in a buffer while in the RRC_INACTIVE state or the RRC_IDLE state after activation of a QoE configuration.

[0163] At block 1206, the wireless communication device may deactivate the QoE configuration. Figure 11 The illustrated and described QoE measurement collection activation / deactivation / pause circuit 1143 may provide means for deactivating a QoE configuration. In some examples, deactivating the QoE configuration occurs in response to at least one of the following: expiration of a QoE configuration validity timer at the wireless communication device, or a determination at the wireless communication device that the wireless communication device has moved outside of a predetermined QoE zone.

[0164] At block 1208, the wireless communication device may initiate an RRC connection establishment procedure from the RRC_IDLE state or an RRC connection recovery procedure from the RRC_INACTIVE state in response to both the presence of QoE data in the buffer and the deactivation of the QoE configuration. Figure 11 The illustrated and described RRC connection establishment and RRC connection recovery circuitry 1144 may provide means for initiating an RRC connection establishment procedure from an RRC_IDLE state or an RRC connection recovery procedure from an RRC_INACTIVE state in response to both having QoE data in the buffer and deactivating the QoE configuration.

[0165] According to some aspects, the wireless communication device may be further configured to obtain criteria for determining whether to initiate an RRC connection establishment procedure or an RRC connection recovery procedure. Figure 11The illustrated and described RRC connection establishment and RRC connection recovery circuitry 1144 may provide means for obtaining criteria for determining whether to initiate an RRC connection establishment or an RRC connection recovery procedure. According to some aspects, the criteria may be configured for the wireless communication device or may be preconfigured in the wireless communication device. In some examples, the criteria is at least one of: a first threshold to which the amount of QoE data in the buffer is compared; a second threshold to which the time elapsed since the start of QoE data measurement or the start of accumulation of QoE data in the buffer is compared; or receiving QoE data associated with QoE information in a predetermined set of QoE information, and satisfying any one or more of the criteria causes the wireless communication device to initiate an RRC connection establishment or an RRC connection recovery procedure. In some examples, the predetermined set of QoE information may include at least one of: a service type, a slice range, a QoE reference, a multicast and broadcast service (MBS) session, or a QoE configuration RRC identifier.

[0166] In some examples, the criterion is configured to the RRC layer of the wireless communication device, and the wireless communication device may also: obtain the criterion by the RRC layer; and use the criterion by the RRC layer to determine whether to initiate an RRC connection establishment process or an RRC connection recovery process. Figure 11 The illustrated and described RRC connection establishment procedure and RRC connection recovery procedure circuitry 1144 may provide means for obtaining criteria by the RRC layer and utilizing the criteria by the RRC layer to determine whether to initiate an RRC connection establishment procedure or an RRC connection recovery procedure.

[0167] In some examples, the criterion is configured to an application layer of a wireless communication device, and the wireless communication device is further configured to obtain the criterion from the application layer and use the criterion by the application layer to determine whether to deliver the QoE data in the buffer to the RRC layer of the wireless communication device. Figure 11 The illustrated and described RRC connection establishment process and RRC connection recovery process circuitry 1144 may provide means for obtaining criteria by the application layer and means for the application layer to utilize the criteria to determine whether to deliver QoE data in the buffer to the RRC layer of the wireless communication device.

[0168] In some aspects, the wireless communication device obtains the criteria via an RRC message received from a network entity. In some aspects, the RRC connection recovery process includes initiating a small data transmission (SDT) during an RRC_INACTIVE state, the SDT being used to transmit the QoE data in the buffer to the network entity. In some aspects, the wireless communication device releases the QoE configuration in response to receiving an indication from the network entity to deactivate the QoE configuration. For example, the RRC connection establishment process and RRC connection recovery process circuitry 1144 may provide means for releasing the QoE configuration in response to receiving an indication from the network entity to deactivate the QoE configuration.

[0169] At block 1210, the wireless communication device may transmit the QoE data in the buffer to the network entity after entering the RRC_CONNECTED state at the end of the RRC connection establishment process or the RRC connection recovery process. Figure 11 The illustrated and described QoE data accumulation circuit 1145 may provide means for transmitting the QoE data in the buffer to the network entity after entering the RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure.

[0170] Figure 13 is a flow chart illustrating an example process 1300 (e.g., a method) for wireless communication at a wireless communication device according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some illustrated features may not be required for implementations of all embodiments. In some examples, process 1300 may be performed by, for example, combining Figure 11 The wireless communication device 1100 may be similar to, for example, Figure 1 、 Figure 2 、 Figure 3 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 8 、 Figure 9 and / or Figure 10 In some examples, process 1300 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0171] At block 1302, the wireless communication device may activate a Quality of Experience (QoE) configuration. Figure 11 The illustrated and described QoE measurement collection activation / deactivation / pause circuitry 1143 may provide means for activating quality of experience (QoE) configuration.

[0172] At block 1304, the wireless communication device may accumulate QoE data in a buffer after activating the QoE configuration while in the radio resource control inactive (RRC_INACTIVE) state or the RRC_IDLE state. Figure 11 The QoE data accumulation circuit 1145 shown and described may provide means for accumulating QoE data in a buffer when in a radio resource control (RRC) inactive state or RRC_IDLE state after activation of the QoE configuration.

[0173] At block 1306, the wireless communication device may deactivate the QoE configuration. Figure 11 The illustrated and described QoE measurement collection activation / deactivation / pause circuit 1143 may provide means for deactivating a QoE configuration.

[0174] At block 1308, the wireless communication device may stop accumulating QoE data in response to determining to deactivate the QoE configuration. Figure 11 The illustrated and described QoE measurement collection activation / deactivation / pause circuitry 1143 may provide means for stopping accumulation of QoE data in a buffer in response to a determination to deactivate the QoE configuration.

[0175] At block 1310, the wireless communication device may store parameters of the QoE configuration. Figure 11 The QoE measurement collection configuration circuitry 1142 shown and described in conjunction with the QoE configuration parameters 1122 portion of the memory 1110 may provide a means for storing parameters for QoE configurations.

[0176] In some examples, the wireless communication device can transmit an indication to suspend QoE measurement from the RRC layer of the wireless communication device to the application layer. Figure 11 The illustrated and described QoE measurement collection activation / deactivation / pause circuitry 1143 may provide means for conveying an indication to suspend QoE measurements from the RRC layer to the application layer of the wireless communication device.

[0177] In some examples, the wireless communication device may start a timer in response to deactivating the QoE configuration and delete the QoE configuration and the corresponding QoE data in the buffer in response to the expiration of the timer. Figure 11 The illustrated and described QoE measurement collection activation / deactivation / pause circuitry 1143 may provide means for starting a timer in response to deactivating a QoE configuration, and means for deleting the QoE configuration and corresponding QoE data in the buffer in response to expiration of the timer.

[0178] In some examples, the wireless communication device may start a timer in response to deactivating the QoE configuration; accumulate new QoE data in a buffer while in a new RRC_INACTIVE state or a new RRC_IDLE state; and in response to expiration of the timer: release the QoE configuration and the QoE data in the buffer, or, in response to both having the QoE data in the buffer and additional deactivation of the QoE configuration, initiate a new RRC connection establishment procedure from the new RRC_IDLE state or initiate a new RRC connection recovery procedure from the new RRC_INACTIVE state, and after entering a new RRC_CONNECTED state at the end of the new RRC connection establishment procedure or the new RRC connection recovery procedure, transmit the new QoE data in the buffer to the network entity. For example, as in conjunction with Figure 11 The QoE measurement collection activation / deactivation / pause circuit 1143 shown and described may provide means for starting a timer in response to deactivating a QoE configuration. Figure 11 The QoE data accumulation circuit 1145 shown and described may provide means for accumulating new QoE data in a buffer when in a new RRC_INACTIVE state or a new RRC_IDLE state after reactivation of the QoE configuration. Figure 11 The QoE measurement collection activation / deactivation / pause circuit 1143 shown and described may provide means for performing additional deactivation of the QoE configuration. Figure 11 The illustrated and described RRC connection establishment procedure and RRC connection recovery procedure circuit 1144 may provide means for initiating a new RRC connection establishment procedure from a new RRC_IDLE state or a new RRC connection recovery procedure from a new RRC_INACTIVE state in response to both the presence of QoE data in the buffer and the additional deactivation of the QoE configuration, and provide means for transmitting the new QoE data in the buffer to the network entity after entering a new RRC_CONNECTED state at the end of the new RRC connection establishment procedure or the new RRC connection recovery procedure.

[0179] In some examples, the wireless communication device may reactivate the QoE configuration according to the stored parameters of the QoE configuration in response to determining at the wireless communication device that the wireless communication device has moved into a predetermined QoE area after having been outside the predetermined QoE area, or receiving an indication from a network entity to reactivate the QoE configuration upon entering a new RRC_CONNECTED state. For example, the QoE measurement collection activation / deactivation / pause circuit 1143 may provide a component for reactivating the QoE configuration according to the stored parameters of the QoE configuration in response to determining at the wireless communication device that the wireless communication device has moved into a predetermined QoE area after having been outside the predetermined QoE area, or receiving an indication from a network entity to reactivate the QoE configuration upon entering a new RRC_CONNECTED state.

[0180] At block 1312, the wireless communication device may initiate an RRC connection establishment procedure from the RRC_IDLE state or an RRC connection recovery procedure from the RRC_INACTIVE state in response to both having QoE data in the buffer and deactivating the QoE configuration. Figure 11 The illustrated and described RRC connection establishment and RRC connection recovery circuitry 1144 may provide means for initiating an RRC connection establishment procedure from an RRC_IDLE state or an RRC connection recovery procedure from an RRC_INACTIVE state in response to both having QoE data in the buffer and deactivating the QoE configuration.

[0181] At block 1314, the wireless communication device may transmit the QoE data in the buffer to the network entity after entering the RRC_CONNECTED state at the end of the RRC connection establishment process or the RRC connection recovery process. Figure 11 The illustrated and described QoE data accumulation circuit 1145 may provide means for transmitting the QoE data in the buffer to the network entity after entering the RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure.

[0182] Of course, in the above example, including Figure 11 The circuits in the processor 1104 are provided as examples only. Other components for performing the described processes or functions may be included in various aspects of the present disclosure, including but not limited to storage in Figure 11 Computer readable medium 1106 or Figure 1 、 Figure 2 、 Figure 3 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 8 、 Figure 9 、 Figure 10 and / or Figure 11 In any of the other suitable devices or components described in any of and utilizing, for example, Figure 12 and / or Figure 13 Instructions for the described processes and / or algorithms.

[0183] The following provides an overview of various aspects of the disclosure:

[0184] Aspect 1: A wireless communication device, comprising: a memory; and a processor coupled to the memory, the processor configured to: activate a quality of experience (QoE) configuration; after activating the QoE configuration, accumulate QoE data in a buffer while in a radio resource control (RRC) inactive state or an RRC_IDLE state; deactivate the QoE configuration; in response to both having the QoE data in the buffer and deactivating the QoE configuration, initiate an RRC connection establishment procedure from the RRC_IDLE state or initiate an RRC connection recovery procedure from the RRC_INACTIVE state; and after entering the RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure, transmit the QoE data in the buffer to a network entity.

[0185] Aspect 2: The wireless communication device according to aspect 1, wherein the processor is further configured to: stop accumulating the QoE data in response to determining to deactivate the QoE configuration; and store parameters of the QoE configuration.

[0186] Aspect 3: The wireless communication device according to aspect 1 or 2, wherein the processor is further configured to: transmit an indication of suspending QoE measurement from the RRC layer of the wireless communication device to the application layer.

[0187] Aspect 4: A wireless communication device according to any one of aspects 1 to 3, wherein the processor is further configured to: start a timer in response to deactivating the QoE configuration; and delete the QoE configuration and corresponding QoE data in the buffer in response to expiration of the timer.

[0188] Aspect 5: A wireless communication device according to any one of aspects 1 to 3, wherein the processor is further configured to: start a timer in response to deactivating the QoE configuration; accumulate new QoE data in the buffer when in a new RRC_INACTIVE state or a new RRC_IDLE state; and in response to expiration of the timer: release the QoE configuration and the QoE data in the buffer, or in response to both the presence of the new QoE data in the buffer and the additional deactivation of the QoE configuration, initiate a new RRC connection establishment procedure from the new RRC_IDLE state, or initiate a new RRC connection recovery procedure from the new RRC_INACTIVE state, and after entering a new RRC_CONNECTED state at the end of the new RRC connection establishment procedure or the new RRC connection recovery procedure, transmit the new QoE data in the buffer to the network entity.

[0189] Aspect 6: A wireless communication device according to any one of Aspects 1 to 5, wherein the processor is further configured to: reactivate the QoE configuration according to the stored parameters of the QoE configuration in response to the processor being configured to perform the following operations: determining at the wireless communication device that the wireless communication device has moved into the predetermined QoE area after being outside the predetermined QoE area, or receiving an indication from the network entity to reactivate the QoE configuration when entering a new RRC_CONNECTED state.

[0190] Aspect 7: The wireless communication device according to any one of aspects 1 to 6, wherein the processor is further configured to: obtain a criterion for determining whether to initiate the RRC connection establishment procedure or the RRC connection recovery procedure.

[0191] Aspect 8: The wireless communication device according to aspect 7, wherein the criterion is configured to the wireless communication device or is preconfigured in the wireless communication device.

[0192] Aspect 9: A wireless communication device according to any one of Aspects 1 to 8, wherein the criterion includes at least one of the following: a first threshold, the amount of the QoE data in the buffer is compared with the first threshold; a second threshold, the time elapsed since the start of QoE data measurement or the start of accumulation of the QoE data in the buffer is compared with the second threshold; or receiving QoE data associated with QoE information in a predetermined set of QoE information, and satisfying any one or more of the criteria further configures the processor to initiate the RRC connection establishment process or the RRC connection recovery process.

[0193] Aspect 10: A wireless communication device according to aspect 9, wherein the predetermined set of QoE information includes at least one of the following: service type, slice range, QoE reference, multicast and broadcast service (MBS) session, or QoE configuration RRC identifier.

[0194] Aspect 11: A wireless communication device according to any one of Aspects 1 to 10, wherein the criterion is configured to the RRC layer of the wireless communication device, and the processor is further configured to: obtain the criterion by the RRC layer; and use the criterion by the RRC layer to determine whether to initiate the RRC connection establishment process or the RRC connection recovery process.

[0195] Aspect 12: A wireless communication device according to any one of Aspects 1 to 11, wherein the criterion is configured to an application layer of the wireless communication device, and the processor is further configured to: obtain the criterion by the application layer; and use the criterion by the application layer to determine whether to deliver the QoE data in the buffer to the RRC layer of the wireless communication device.

[0196] Aspect 13: The wireless communication apparatus of any one of aspects 1 to 12, wherein the processor is configured to obtain the criterion via an RRC message received from the network entity.

[0197] Aspect 14: The wireless communication device according to any one of aspects 1 to 13, wherein in response to receiving an indication from the network entity to deactivate the QoE configuration, the processor is further configured to release the QoE configuration.

[0198] Aspect 15: A wireless communication device according to any one of aspects 1 to 14, wherein the processor is configured to deactivate the QoE configuration in response to at least one of the following: expiration of a QoE configuration validity timer at the wireless communication device, or a determination at the wireless communication device that the wireless communication device has moved outside a predetermined QoE area range.

[0199] Aspect 16: A method for performing wireless communications at a wireless communication device, the method comprising: activating a quality of experience (QoE) configuration; after activating the QoE configuration, accumulating QoE data in a buffer while in a radio resource control (RRC) inactive state or an RRC_IDLE state; deactivating the QoE configuration; in response to both having the QoE data in the buffer and deactivating the QoE configuration, initiating an RRC connection establishment procedure from the RRC_IDLE state or initiating an RRC connection recovery procedure from the RRC_INACTIVE state; and after entering the RRC_CONNECTED state at the end of the RRC connection establishment procedure or the RRC connection recovery procedure, transmitting the QoE data in the buffer to a network entity.

[0200] Aspect 17: The method according to aspect 16, further comprising: stopping accumulating the QoE data in response to determining to deactivate the QoE configuration; and storing parameters of the QoE configuration.

[0201] Aspect 18: The method according to aspect 16 or 17, further comprising: transmitting an indication to suspend QoE measurement from the RRC layer of the wireless communication device to the application layer.

[0202] Aspect 19: The method according to any one of aspects 16 to 18, further comprising: starting a timer in response to deactivating the QoE configuration; and deleting the QoE configuration and the corresponding QoE data in the buffer in response to expiration of the timer.

[0203] Aspect 20: The method according to any one of aspects 16 to 19, further comprising: starting a timer in response to deactivating the QoE configuration; accumulating new QoE data in the buffer when in a new RRC_INACTIVE state or a new RRC_IDLE state; and in response to expiration of the timer: releasing the QoE configuration and the QoE data in the buffer, or in response to both the presence of the new QoE data in the buffer and the additional deactivation of the QoE configuration, initiating a new RRC connection establishment procedure from the new RRC_IDLE state, or initiating a new RRC connection recovery procedure from the new RRC_INACTIVE state, and after entering a new RRC_CONNECTED state at the end of the new RRC connection establishment procedure or the new RRC connection recovery procedure, transmitting the new QoE data in the buffer to the network entity.

[0204] Aspect 21: According to the method of any one of Aspects 16 to 20, the method further includes: reactivating the QoE configuration according to the stored parameters of the QoE configuration in response to performing the following operations: determining at the wireless communication device that the wireless communication device has moved into the predetermined QoE area after being outside the predetermined QoE area, or receiving an indication from the network entity to reactivate the QoE configuration when entering a new RRC_CONNECTED state.

[0205] Aspect 22: According to the method according to any one of aspects 16 to 21, the method further includes: obtaining a criterion for determining whether to initiate the RRC connection establishment procedure or the RRC connection recovery procedure.

[0206] Aspect 23: The method according to aspect 22, wherein the criteria are configured to the wireless communication device or preconfigured in the wireless communication device.

[0207] Aspect 24: A method according to any one of aspects 16 to 23, wherein the criteria include at least one of the following: a first threshold, the amount of the QoE data in the buffer is compared with the first threshold; a second threshold, the time elapsed since the start of QoE data measurement or the start of accumulation of the QoE data in the buffer is compared with the second threshold; or receiving QoE data associated with QoE information in a predetermined set of QoE information, and satisfying any one or more of the criteria causes the wireless communication device to initiate the RRC connection establishment procedure or the RRC connection recovery procedure.

[0208] Aspect 25: The method according to Aspect 24, wherein the predetermined set of QoE information includes at least one of the following: service type, slice range, QoE reference, multicast and broadcast service (MBS) session, or QoE configuration RRC identifier.

[0209] Aspect 26: A method according to any one of Aspects 16 to 25, wherein the criterion is configured to the RRC layer of the wireless communication device, and the method further includes: obtaining the criterion by the RRC layer; and using the criterion by the RRC layer to determine whether to initiate the RRC connection establishment process or the RRC connection recovery process.

[0210] Aspect 27: A method according to any one of Aspects 16 to 26, wherein the criterion is configured to the application layer of the wireless communication device, and the method further includes: obtaining the criterion by the application layer; and using the criterion by the application layer to determine whether to deliver the QoE data in the buffer to the RRC layer of the wireless communication device.

[0211] Aspect 28: The method according to any one of aspects 16 to 27, wherein the wireless communication device obtains the criterion via an RRC message received from the network entity.

[0212] Aspect 29: The method according to any one of aspects 16 to 28, wherein in response to receiving an indication from the network entity to deactivate the QoE configuration, the wireless communication device releases the QoE configuration.

[0213] Aspect 30: A method according to any one of aspects 16 to 29, wherein deactivating the QoE configuration occurs in response to at least one of the following: expiration of a QoE configuration validity timer at the wireless communication device, or determining at the wireless communication device that the wireless communication device has moved outside of a predetermined QoE area range.

[0214] Aspect 31: The method according to any one of aspects 16 to 30, wherein the RRC connection recovery procedure includes initiating a small data transmission (SDT) during the RRC_INACTIVE state, the SDT being used to transmit the QoE data in the buffer to the network entity.

[0215] Aspect 32: A wireless communication device according to any one of aspects 1 to 15, wherein the RRC connection recovery process includes initiating a small data transmission (SDT) during the RRC_INACTIVE state, the SDT being used to transmit the QoE data in the buffer to the network entity.

[0216] Aspect 33: An apparatus configured for wireless communication, the apparatus comprising at least one component for performing the method according to any one of aspects 16 to 31.

[0217] Aspect 34: A non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of a base station to perform the method according to any one of aspects 16 to 31.

[0218] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0219] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA 2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0220] Within this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or preferred over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered coupled to each other, even if they are not in direct physical contact with each other. For example, a first object can be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The term "circuitry" is used broadly, and is intended to include both hardware implementations of electronic devices and conductors (wherein these electronic devices and conductors, when connected and configured, enable the performance of the functions described in this disclosure, without limitation as to the type of electronic circuitry) and software implementations of information and instructions (wherein these information and instructions, when executed by a processor, enable the performance of the functions described in this disclosure).

[0221] Figures 1 to 13 One or more of the components, steps, features, and / or functions illustrated herein may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 13 The apparatus, device and / or components illustrated in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0222] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The accompanying method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically stated herein. Although some of the examples illustrated herein depict only the time domain and the frequency domain, additional domains such as the spatial domain are also contemplated in this disclosure.

[0223] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein, but rather to the full scope consistent with the text of the claims, wherein, unless expressly stated otherwise, reference to an element in the singular is not intended to mean "one and only one," but rather "one or more." Unless otherwise specified, the term "some" refers to one or more. A phrase referring to "at least one" of a list of items refers to any combination of those items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a; b; c; a and b; a and c; b and c; and a, b, and c. Structures A and / or B are intended to encompass: A; B; and A and B. As used herein, the word "obtain" may mean, for example, to obtain, calculate, construct, derive, determine, receive, and / or retrieve. The foregoing list is exemplary and non-restrictive. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element should be construed under 35 U.S.C. §112(f) unless the element is explicitly recited using the phrase “means for” or, in the case of a method claim, the phrase “step for.”

Claims

1. A wireless communication device, comprising: Memory; and a processor coupled to the memory, the processor being configured to: Activate Quality of Experience (QoE) configuration; After activating the QoE configuration, accumulating QoE data in a buffer while in a radio resource control inactive (RRC_INACTIVE) state or an RRC_IDLE state; Deactivating the QoE configuration; In response to both the presence of the QoE data in the buffer and the deactivation of the QoE configuration, initiating an RRC connection establishment procedure from the RRC_IDLE state, or initiating an RRC connection recovery procedure from the RRC_INACTIVE state; as well as After entering the RRC_CONNECTED state at the end of the RRC connection establishment process or the RRC connection recovery process, the QoE data in the buffer is transmitted to a network entity.

2. The wireless communication device of claim 1 , wherein the processor is further configured to: stopping accumulating the QoE data in response to determining to deactivate the QoE configuration; and Storing parameters of the QoE configuration.

3. The wireless communication device of claim 2 , wherein the processor is further configured to: An indication to suspend QoE measurement is transmitted from the RRC layer of the wireless communication device to the application layer.

4. The wireless communication device of claim 2 , wherein the processor is further configured to: In response to deactivating the QoE configuration, starting a timer; and The QoE configuration and corresponding QoE data in the buffer are deleted in response to expiration of the timer.

5. The wireless communication device of claim 2 , wherein the processor is further configured to: starting a timer in response to deactivating the QoE configuration; When in a new RRC_INACTIVE state or a new RRC_IDLE state, accumulating new QoE data in the buffer; and; In response to the timer expiring: releasing the QoE configuration and the new QoE data in the buffer, or In response to both the presence of the new QoE data in the buffer and the additional deactivation of the QoE configuration, initiating a new RRC connection establishment procedure from the new RRC_IDLE state or initiating a new RRC connection recovery procedure from the new RRC_INACTIVE state, and After entering a new RRC_CONNECTED state at the end of the new RRC connection establishment process or the new RRC connection recovery process, the new QoE data in the buffer is transmitted to the network entity.

6. The wireless communication device of claim 2, wherein the processor is further configured to: In response to the processor being configured to: reactivate the QoE configuration according to the stored parameters of the QoE configuration; determining at the wireless communication device that the wireless communication device has moved into a predetermined QoE area after having been outside the predetermined QoE area, or An indication is received from the network entity to reactivate the QoE configuration upon entering a new RRC_CONNECTED state.

7. The wireless communication device of claim 1 , wherein the processor is further configured to: A criterion for determining whether to initiate the RRC connection establishment procedure or the RRC connection recovery procedure is obtained.

8. The wireless communication device according to claim 7, wherein the criterion is configured to the wireless communication device or is preconfigured in the wireless communication device.

9. The wireless communication device of claim 7, wherein the criteria comprises at least one of the following: a first threshold, the amount of the QoE data in the buffer being compared with the first threshold, a second threshold, the time elapsed since the start of QoE data measurement or the start of accumulation of the QoE data in the buffer being compared with the second threshold, or receiving QoE data associated with QoE information in a predetermined set of QoE information, and Satisfying any one or more of the criteria further configures the processor to initiate the RRC connection establishment procedure or the RRC connection recovery procedure.

10. The wireless communication device of claim 9, wherein the predetermined set of QoE information comprises at least one of: a service type, a slice range, a QoE reference, a multicast and broadcast service (MBS) session, or a QoE configuration RRC identifier.

11. The wireless communication device of claim 7 , wherein the criterion is configured to an RRC layer of the wireless communication device, and the processor is further configured to: obtaining the criteria by the RRC layer; and The RRC layer uses the criterion to determine whether to initiate the RRC connection establishment procedure or the RRC connection recovery procedure.

12. The wireless communication device of claim 7 , wherein the criteria are configured to an application layer of the wireless communication device, and the processor is further configured to: obtaining the criteria by the application layer; and The application layer uses the criteria to determine whether to deliver the QoE data in the buffer to the RRC layer of the wireless communication device.

13. The wireless communication device of claim 7, wherein the processor is configured to obtain the criterion via an RRC message received from the network entity.

14. The wireless communication device of claim 1, wherein in response to receiving an indication from the network entity to deactivate the QoE configuration, the processor is further configured to release the QoE configuration.

15. The wireless communication device of claim 1 , wherein the processor is configured to deactivate the QoE configuration in response to at least one of: The QoE configuration validity timer at the wireless communication device expires, or It is determined at the wireless communication device that the wireless communication device has moved outside of a predetermined QoE area.

16. A method of performing wireless communication at a wireless communication device, the method comprising: Activate Quality of Experience (QoE) configuration; After activating the QoE configuration, accumulating QoE data in a buffer while in a radio resource control inactive (RRC_INACTIVE) state or an RRC_IDLE state; Deactivating the QoE configuration; In response to both the presence of the QoE data in the buffer and the deactivation of the QoE configuration, initiating an RRC connection establishment procedure from the RRC_IDLE state, or initiating an RRC connection recovery procedure from the RRC_INACTIVE state; as well as After entering the RRC_CONNECTED state at the end of the RRC connection establishment process or the RRC connection recovery process, the QoE data in the buffer is transmitted to a network entity.

17. The method according to claim 16, further comprising: stopping accumulating the QoE data in response to determining to deactivate the QoE configuration; as well as Storing parameters of the QoE configuration.

18. The method according to claim 17, further comprising: An indication to suspend QoE measurement is transmitted from the RRC layer of the wireless communication device to the application layer.

19. The method according to claim 17, further comprising: starting a timer in response to deactivating the QoE configuration; as well as The QoE configuration and corresponding QoE data in the buffer are deleted in response to expiration of the timer.

20. The method according to claim 17, further comprising: starting a timer in response to deactivating the QoE configuration; When in a new RRC_INACTIVE state or a new RRC_IDLE state, accumulating new QoE data in the buffer; and; In response to the timer expiring: releasing the QoE configuration and the new QoE data in the buffer, or In response to both the presence of the new QoE data in the buffer and the additional deactivation of the QoE configuration, initiating a new RRC connection establishment procedure from the new RRC_IDLE state or initiating a new RRC connection recovery procedure from the new RRC_INACTIVE state, and After entering a new RRC_CONNECTED state at the end of the new RRC connection establishment process or the new RRC connection recovery process, the new QoE data in the buffer is transmitted to the network entity.

21. The method according to claim 17, further comprising: reactivating the QoE configuration according to the stored parameters of the QoE configuration in response to: determining at the wireless communication device that the wireless communication device has moved into a predetermined QoE area after having been outside the predetermined QoE area, or An indication is received from the network entity to reactivate the QoE configuration upon entering a new RRC_CONNECTED state.

22. The method according to claim 16, further comprising: A criterion for determining whether to initiate the RRC connection establishment procedure or the RRC connection recovery procedure is obtained.

23. The method of claim 22, wherein the criteria are configured to the wireless communication device or are preconfigured in the wireless communication device.

24. The method of claim 22, wherein the criteria include at least one of the following: a first threshold, the amount of the QoE data in the buffer being compared with the first threshold, a second threshold, the time elapsed since the start of QoE data measurement or the start of accumulation of the QoE data in the buffer being compared with the second threshold, or receiving QoE data associated with QoE information in a predetermined set of QoE information, and Satisfaction of any one or more of the criteria causes the wireless communication device to initiate the RRC connection establishment procedure or the RRC connection recovery procedure.

25. The method of claim 24, wherein the predetermined set of QoE information comprises at least one of: a service type, a slice range, a QoE reference, a multicast and broadcast service (MBS) session, or a QoE configuration RRC identifier.

26. The method of claim 22, wherein the criteria are configured to an RRC layer of the wireless communication device, and the method further comprises: Obtaining the criterion by the RRC layer; as well as The RRC layer uses the criterion to determine whether to initiate the RRC connection establishment procedure or the RRC connection recovery procedure.

27. The method of claim 22, wherein the criteria are configured to an application layer of the wireless communication device, and further comprising: Obtaining the criteria by the application layer; as well as The application layer uses the criteria to determine whether to deliver the QoE data in the buffer to the RRC layer of the wireless communication device.

28. The method of claim 22, wherein the wireless communication device obtains the criteria via an RRC message received from the network entity.

29. The method of claim 16, wherein the wireless communication device releases the QoE configuration in response to receiving an indication from the network entity to deactivate the QoE configuration.

30. The method of claim 16, wherein deactivating the QoE configuration occurs in response to at least one of: The QoE configuration validity timer at the wireless communication device expires, or It is determined at the wireless communication device that the wireless communication device has moved outside of a predetermined QoE area.

Images