Quality of experience measurement reporting

Abstract

A method may include transmitting, by a wireless device in a radio resource control (RRC) idle state or an RRC inactive state, a packet associated with a service. The method may also include transmitting, to a first base station, a radio resource control (RRC) message indicating that a measurement report associated with the service is available. The method may further include receiving, from the first base station, an information request message indicating the measurement report. The method may additionally include sending an information response message including the measurement report, the measurement report including a Quality of Experience (QoE) of the service.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 336,770, filed April 29, which is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Figure 1A and Figure 1B An example mobile communications network is shown in which embodiments of the present disclosure may be implemented.

[0004] Figure 2A and Figure 2B New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0005] Figure 3 Shown in Figure 2A An instance of the services provided between the protocol layers of the NR user plane protocol stack.

[0006] Figure 4A Shows the flow Figure 2A Figure 2. Example downlink data flow of the NR user plane protocol stack.

[0007] Figure 4B An example format of a MAC subheader in a MAC PDU is shown.

[0008] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels for downlink and uplink are shown respectively.

[0009] Figure 6 is an example diagram showing RRC state transition of a UE.

[0010] Figure 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown.

[0011] Figure 8 An example configuration of slots in the time and frequency domain of an NR carrier is shown.

[0012] Fig. 9 An example of bandwidth adaptation using three configured BWPs for NR carriers is shown.

[0013] Fig. 10A Three carrier aggregation configurations with two component carriers are shown.

[0014] Fig. 10B An example is shown of how aggregated cells may be configured into one or more PUCCH groups.

[0015] Fig.11A An example of SS / PBCH block structure and location is shown.

[0016] Fig. 11B An example of CSI-RS mapped in time and frequency domain is shown.

[0017] Fig. 12A and Fig. 12B Three examples of downlink and uplink beam management procedures are shown respectively.

[0018] Fig.13A , Fig. 13B and Fig. 13C A four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure are shown respectively.

[0019] Fig.14A An example of a CORESET configuration for the bandwidth portion is shown.

[0020] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown.

[0021] Fig.15 An example of a wireless device communicating with a base station is shown.

[0022] Fig.16A , Fig. 16B , Fig. 16C and Fig.16D Example structures for uplink and downlink transmissions are shown.

[0023] Fig.17 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0024] Fig.18 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0025] Fig.19 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0026] Fig. 20 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0027] Fig.21 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0028] Fig. 22 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0029] Fig.23 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0030] Fig.24 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0031] Fig.25 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0032] Fig.26 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0033] Fig. 27 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0034] Fig.28 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0035] Fig.29 is an exemplary diagram of an aspect of an embodiment of the present disclosure.

[0036] Fig.30 is an exemplary diagram of an aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0037] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited by any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Restrictions, features and / or elements from the disclosed example embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided for exemplary purposes only. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0038] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various example embodiments may be applied. Therefore, example embodiments that selectively implement the disclosed protocol may be implemented.

[0039] A base station may communicate with a mixture of wireless devices. A wireless device and / or base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device category and / or capabilities. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may refer to a subset of the total wireless devices in the coverage area. For example, the present disclosure may refer to multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed method, for example, these wireless devices or base stations may perform based on older versions of LTE or 5G technology.

[0040] In the present disclosure, "a" and "an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase after the term "may" is an example of one of a variety of suitable possibilities that may or may not be used for one or more of the various embodiments. As used herein, the terms "comprising" and "consisting of..." list one or more components of the element being described. The terms "comprising" and "including" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of..." provides a complete listing of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the listed elements. For example, “A, B and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0041] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopting / using" (or equivalently "at least adopting / using") indicates that the phrase after the phrase "adopting / using" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0042] The term configured may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may refer to a specific setting in a device that affects the operating characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. Terms such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0043] In the present disclosure, a parameter (or equivalently referred to as a field or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J. Then, for example, N includes K, and N includes J. In an example embodiment, when one or more messages include multiple parameters, it means that a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0044] Many of the features set forth are described as optional, either by the use of "may" or by the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by selecting from the set of optional features. The present disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, i.e., having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0045] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, all of which can be equivalent in behavior. For example, a module can be implemented as a software routine written in a computer language that is configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript). It is possible to implement a module using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs and CPLDs are often programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure the connections between internal hardware blocks with fewer functions on the programmable devices. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0046] 1. Network architecture

[0047] Figure 1A 1 shows an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) operated by a network operator. Figure 1A As shown, the mobile communication network 100 includes a core network (CN) 102 , a radio access network (RAN) 104 , and wireless devices 106 .

[0048] CN 102 may provide an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-carrier DNs, for wireless device 106. As part of the interface functionality, CN 102 may set up an end-to-end connection between wireless device 106 and one or more DNs, authenticate wireless device 106, and provide charging functionality.

[0049] The RAN 104 may connect the CN 102 to the wireless device 106 via radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The direction of communication from the RAN 104 to the wireless device 106 over the air interface is referred to as downlink, while the direction of communication from the wireless device 106 to the RAN 104 over the air interface is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0050] The term "wireless device" may be used throughout this disclosure to refer to and encompass any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device may be a phone, a smart phone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle roadside unit (RSU), a relay node, a car, and / or any combination thereof. The term "wireless device" encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0051] The RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: a Node B (associated with UMTS and / or 3G standards); an evolved Node B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a repeater node or relay node used to extend the coverage area of ​​a donor node; a next generation evolved Node B (ng-eNB); a generation Node B (gNB, associated with NR and / or 5G standards); an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0052] The base stations included in the RAN 104 may include one or more sets of antennas for communicating with the wireless devices 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to control three cells (or sectors) respectively. The size of a cell may be determined by the range at which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. The cells of the base stations may together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0053] In addition to three-sector sites, other implementations of the base station are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectorized site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, a baseband processing unit coupled to several remote radio heads (RRHs), and / or a repeater or relay node for extending the coverage area of ​​a donor node. The baseband processing unit coupled to the RRH may be part of a centralized or cloud RAN architecture, in which the baseband processing unit may be centralized in a baseband processing unit pool or virtualized. The repeater node may amplify and replay radio signals received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signal received from the donor node to eliminate noise before amplifying and replaying the radio signal.

[0054] The RAN 104 may be deployed as a homogeneous network of macrocell base stations with similar antenna types and similar high levels of transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, a small cell base station may be used to provide a small coverage area, such as a coverage area that overlaps with a relatively large coverage area provided by a macrocell base station. Small coverage areas may be provided in areas with high data traffic (or so-called "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0055] The Third Generation Partnership Project (3GPP) was established in 1998 to Figure 1A 3GPP provides global specification standardization for mobile communication networks similar to the mobile communication network 100 in the present invention. To date, 3GPP has developed specifications for three generations of mobile networks: the third generation (3G) network known as the Universal Mobile Telecommunications System (UMTS), the fourth generation (4G) network known as the Long Term Evolution (LTE), and the fifth generation (5G) network known as the 5G System (5GS). The embodiments of the present disclosure are described with reference to the RAN of the 3GPP 5G network known as the Next Generation RAN (NG-RAN). These embodiments may be applicable to the RAN of other mobile communication networks, such as Figure 1A The RAN 104 in 5G networks, the RAN of early 3G and 4G networks, and those of yet-to-be-specified future networks (e.g., 3GPP 6G networks). The NG-RAN implements the 5G radio access technology known as New Radio (NR) and may be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0056] Figure 1B Another example mobile communication network 150 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown in FIG. 1 , the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). Figure 1A The corresponding components described are implemented and operate in the same or similar manner.

[0057] 5G-CN 152 provides an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an operator's internal DN, to UE 156. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CN of the 3GPP 4G network, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 may be implemented in several ways, including as a network element on dedicated or shared hardware, as a software instance running on dedicated or shared hardware, or as a virtualized function instantiated on a platform (e.g., a cloud-based platform).

[0058] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. For ease of explanation, Figure 1BThey are shown as one component AMF / UPF 158 in FIG. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting routing of service flows to the one or more DNs, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement and uplink service verification), downlink packet buffering and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected with the one or more DNs, and / or a fulcrum for supporting multi-host PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

[0059] The AMF 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policy), network slicing support and / or session management function (SMF) selection. NAS may refer to functions operating between CN and UE, and AS may refer to functions operating between UE and RAN.

[0060] 5G-CN 152 may include Figure 1B , one or more additional network functions shown in . For example, 5G-CN 152 may include one or more of the following: session management function (SMF), NR repository function (NRF), policy control function (PCF), network exposure function (NEF), unified data management (UDM), application function (AF) and / or authentication server function (AUSF).

[0061] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via radio communications over an air interface. The NG-RAN 154 may include: one or more gNBs, shown as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, shown as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). The gNB 160 and ng-eNB 162 may be more generally referred to as base stations. The gNB 160 and ng-eNB 162 may include one or more groups of antennas for communicating with the UE 156 over an air interface. For example, one or more gNBs in the gNB 160 and / or one or more ng-eNBs in the ng-eNB 162 may include three groups of antennas to control three cells (or sectors), respectively. The cells of gNB 160 and ng-eNB 162 may together provide radio coverage to UE 156 over a wide geographic area to support UE mobility.

[0062] like Figure 1B As shown in FIG, gNB 160 and / or ng-eNB 162 may be connected to 5G-CN 152 via an NG interface and to other base stations via an Xn interface. NG and Xn interfaces may be established using direct physical connections and / or indirect connections through underlying transport networks such as Internet Protocol (IP) transport networks. gNB 160 and / or ng-eNB 162 may be connected to UE 156 via a Uu interface. For example, Figure 1B As shown in FIG. 1 , gNB 160A may be connected to UE 156A via a Uu interface. NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface may be composed of Figure 1B The network elements in a network are used to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data that the user is interested in. The control plane may process signaling messages that the network elements are interested in.

[0063] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of a NG user plane (NG-U) interface. The NG-U interface may provide delivery of user plane PDUs (e.g., non-guaranteed delivery) between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of a NG control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, delivery of NAS messages, paging, PDU session management, and configuration delivery and / or warning message transmission.

[0064] The gNB 160 may provide NR user plane and control plane protocol terminations to the UE 156 via a Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations to the UE 156A via a Uu interface associated with the first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the UE 156 via a Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations to the UE 156B via a Uu interface associated with the second protocol stack.

[0065] 5G-CN 152 is described as being configured to handle both NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to be connected to a 4G core network in a mode known as "non-standalone operation". In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B Only one AMF / UPF 158 is shown in the figure, but a gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0066] 2. Radio Protocol Architecture

[0067] As discussed, Figure 1B The interfaces between network elements in a network (e.g., Uu, Xn, and NG interfaces) may be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. The user plane may process data of interest to the user, while the control plane may process signaling messages of interest to the network elements.

[0068] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE 210 and gNB 220 are shown respectively. Figure 2A and Figure 2B The protocol stack shown in can be used with e.g. Figure 1B The protocol stacks of the Uu interface between UE156A and gNB 160A shown in are the same or similar.

[0069] 2.1 User Plane Protocol Stack

[0070] Figure 2A An NR user plane protocol stack including five layers implemented in a UE 210 and a gNB 220 is shown. At the bottom of the protocol stack, a physical layer (PHY) 211 and 221 may provide transport services to higher layers of the protocol stack and may correspond to layer 1 of the open system interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include a medium access control layer (MAC) 212 and 222, a radio link control layer (RLC) 213 and 223, a packet data convergence protocol layer (PDCP) 214 and 224, and a service data application protocol layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0071] Figure 3 An example of services provided between protocol layers of the NR user plane protocol stack is shown. Figure 2A and Figure 3Starting from the top of , SDAP 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and DN. A PDU session can have one or more QoS flows. The UPF of the CN (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate and / or error rate). SDAP 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping between the QoS flows and the data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0072] The PDCP 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, may perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and may perform integrity protection to ensure that control messages originate from the intended source. The PDCP 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets due to, for example, intra-gNB handovers. The PDCP 214 and 224 may perform packet repetition to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet repetition may be applicable to services that require high reliability.

[0073] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technology that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). A split bearer is a split bearer when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapped split radio bearers between RLC channels belonging to a cell group.

[0074] RLC 213 and 223 can perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222, respectively. RLC 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the functions described. RLC configuration can be based on each logical channel, independent of parameter sets and / or transmission time interval (TTI) duration. As shown in FIG. Figure 3 As shown in FIG. 1 , RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0075] The MAC 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to the one or more logical channels into / from a transport block (TB) delivered to / from the PHY 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs with the aid of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction by hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of the UE 210 with the aid of logical channel prioritization, and / or padding. The MAC 212 and 222 may support one or more parameter sets and / or transmission timing. In one example, mapping constraints in logical channel prioritization can control which parameter sets and / or transmission timings a logical channel can use. Figure 3 As shown, MAC 212 and 222 may provide logical channels as services to RLC 213 and 223 .

[0076] PHY 211 and 221 can perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY 211 and 221 can perform multi-antenna mapping. Figure 3 As shown in , PHY 211 and 221 may provide one or more transport channels as a service to MAC 212 and 222 .

[0077] Figure 4A An example downlink data flow through the NR user plane protocol stack is shown. Figure 4AThe downlink data flow of three IP packets (n, n+1, and m) flowing through the NR user plane protocol stack to generate two TBs at the gNB 220 is shown. The uplink data flow flowing through the NR user plane protocol stack can be the same as Figure 4A The downlink data flow is similar to that depicted in .

[0078] Figure 4A The downlink data flow of starts when SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to a radio bearer. Figure 4A In the SDAP header (in Figure 4A The data unit from / to a higher protocol layer is called a service data unit (SDU) of the lower protocol layer, and the data unit to / from a lower protocol layer is called a protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225 .

[0079] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., Figure 3 ), add the corresponding headers, and forward their corresponding outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A 222) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDU, as shown in FIG. Figure 4A In LTE, the MAC subheader can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU subheader can be calculated before assembling the complete MAC PDU.

[0080] Figure 4BAn example format of a MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0081] Figure 4B Further shown is a MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B Two MAC CEs are shown inserted into the MAC PDU. Figure 4B ) and inserting a MAC CE at the end of a MAC PDU for uplink transmission. MAC CE can be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those used for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader having a format similar to that described for MAC SDU may be present before the MAC CE, and the MAC CE may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0082] Before describing the NR control plane protocol stack, the mapping between logical channels, transport channels, and physical channels and channel types is first described. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack described later below.

[0083] Figure 5A and Figure 5BThe mapping between logical channels, transport channels and physical channels is shown for downlink and uplink respectively. Information is passed through channels between RLC, MAC and PHY of the NR protocol stack. Logical channels can be used between RLC and MAC and can be classified as control channels that carry control and configuration information in the NR control plane, or as traffic channels that carry data in the NR user plane. Logical channels can be classified as dedicated logical channels dedicated to a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0084] - Paging Control Channel (PCCH), which is used to carry paging messages used to page UEs whose location is unknown to the network at cell level;

[0085] - Broadcast Control Channel (BCCH), which is used to carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which can be used by UEs to obtain information about how a cell is configured and how it operates within the cell;

[0086] - Common Control Channel (CCCH), which is used to carry control messages and random access;

[0087] - a dedicated control channel (DCCH) used to carry control messages to / from a specific UE to configure the UE; and

[0088] - Dedicated Traffic Channel (DTCH), which is used to carry user data to / from a specific UE.

[0089] Transport channels are used between the MAC layer and the PHY layer and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

[0090] - Paging Channel (PCH), which is used to carry paging messages originating from PCCH;

[0091] - Broadcast Channel (BCH), which is used to carry the MIB from the BCCH;

[0092] - Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from BCCH;

[0093] - Uplink Shared Channel (UL-SCH), which is used to carry uplink data and signaling messages; and

[0094] - Random Access Channel (RACH), which is used to allow a UE to contact the network without any previous scheduling.

[0095] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have a set of associated time-frequency resources for carrying information of one or more transport channels. The PHY may generate control information to support low-level operation of the PHY and provide control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

[0096] - Physical Broadcast Channel (PBCH), which is used to carry the MIB from the BCH;

[0097] - Physical Downlink Shared Channel (PDSCH), which is used to carry downlink data and signaling messages from DL-SCH and paging messages from PCH;

[0098] - Physical Downlink Control Channel (PDCCH), which is used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0099] - Physical Uplink Shared Channel (PUSCH), which is used to carry uplink data and signaling messages from the UL-SCH, and in some cases uplink control information (UCI) as described below;

[0100] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI) and scheduling request (SR); and

[0101] - Physical Random Access Channel (PRACH), which is used for random access.

[0102] Similar to the physical control channel, the physical layer generates physical signals to support the lower-level operations of the physical layer. Figure 5A and Figure 5B As shown in , the physical layer signals defined by NR include: primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS) and phase tracking reference signal (PT-RS). These physical layer signals will be described in more detail below.

[0103] 2.2 Control Plane Protocol Stack

[0104] Figure 2B An example NR control plane protocol stack is shown. Figure 2B As shown in , the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack instead has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0105] The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 (e.g., AMF 158A) or more generally between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 via signaling messages referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which NAS messages may be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0106] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 or more generally between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transported between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 may provide control plane functions such as: broadcast of system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance and release of RRC connection between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of the reporting; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS message delivery. As part of establishing an RRC connection, RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between UE 210 and RAN.

[0107] Figure 6 is an example diagram showing the RRC state transition of the UE. The UE can Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG. 1 and any other wireless device described in the present disclosure may be the same or similar. Figure 6 As shown in , the UE may be in at least one of three RRC states: RRC connected 602 (eg, RRC_CONNECTED), RRC idle 604 (eg, RRC_IDLE), and RRC inactive 606 (eg, RRC_INACTIVE).

[0108] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in the RAN 104 depicted in FIG. Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG. Figure 2A and Figure 2B ; or any other base station described in the present disclosure. A base station connected to a UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may contain parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., involving data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in RRC connection 602, the mobility of the UE may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from a serving cell and neighboring cells, and report these measurements to the base station currently serving the UE. The UE's serving base station may request handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 via a connection release procedure 608 , or to RRC inactive 606 via a connection deactivation procedure 610 .

[0109] In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with a base station. When in RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to save battery power). The UE may wake up periodically (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0110] In RRC inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows a quick transition to RRC connected 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. When in RRC inactive 606, the UE may be in a sleep state, and the mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection recovery procedure 614, or to RRC idle 604 through a connection release procedure 616, which may be the same or similar to the connection release procedure 608.

[0111] The RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to notify the UE of an event via a paging message without broadcasting the paging message over the entire mobile communication network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE at a cell group level, so that the paging message may be broadcast over a cell in the cell group in which the UE currently resides instead of over the entire mobile communication network. The mobility management mechanism used for RRC idle 604 and RRC inactive 606 tracks the UE at a cell group level. These mobility management mechanisms may do so using groups of different granularities. For example, there may be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

[0112] Tracking areas may be used to track UEs at the CN level. A CN (e.g., CN 102 or 5G-CN 152) may provide a list of TAIs associated with UE registration areas to a UE. If a UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with a UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0113] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC Inactive 606 state, a RAN notification area may be assigned to the UE. The RAN notification area may contain one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update on the RAN to update the RAN notification area of ​​the UE.

[0114] The base station storing the RRC context for the UE or the last serving base station of the UE may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or during the period of time that the UE remains in RRC inactivity 606.

[0115] gNB, such as Figure 1B The gNB 160 in the example can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using the F1 interface. The gNB-CU can include RRC, PDCP, and SDAP. The gNB-DU can include RLC, MAC, and PHY.

[0116] 3.Transmission structure

[0117] In NR, physical signals and physical channels (about Figure 5A and Figure 5BDiscussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols) and divided into F parallel symbol streams. The F parallel symbol streams can be treated as if they are in the frequency domain and used as input to the inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal subcarriers. The F time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. The operation produces a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the peak to average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbol at the receiver to restore the data mapped to the source symbol.

[0118] Figure 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame may be identified by a system frame number (SFN). The SFN may repeat in a period of 1024 frames. As shown, a NR frame may have a duration of 10 milliseconds (ms) and may include 10 subframes of duration 1 ms. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.

[0119] The duration of a time slot may depend on the parameter set of the OFDM symbol used for the time slot. In NR, flexible parameter sets are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mm-wave range). Parameter sets may be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 microseconds. For example, NR defines parameter sets with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 microseconds; 30 kHz / 2.3 microseconds; 60 kHz / 1.2 microseconds; 120 kHz / 0.59 microseconds; and 240 kHz / 0.29 microseconds.

[0120] A slot may have a fixed number of OFDM symbols (eg, 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 The transmission structure of the time slot duration and each subframe time slot associated with the parameter set is shown (for ease of explanation, Figure 7 Parameter sets with subcarrier spacing of 240kHz are not shown in Figure 1). Subframes in NR can be used as a time reference independent of the parameter set, while slots can be used as the unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the slot duration and start at any OFDM symbol and continue to transmit as many symbols as needed. These partial slot transmissions can be called mini-slots or sub-slot transmissions.

[0121] Figure 8 An example configuration of time slots in the time and frequency domains of an NR carrier is shown. The time slots include resource elements (REs) and resource blocks (RBs). REs are the smallest physical resources in NR. REs span one OFDM symbol in the time domain through one subcarrier in the frequency domain, such as Figure 8 As shown in Figure 1. RB spans twelve consecutive REs in the frequency domain, as Figure 8 As shown. The NR carrier can be limited to a width of 275 RBs or 275×12=3300 subcarriers. If this restriction is used, the NR carrier can be limited to 50MHz, 100MHz, 200MHz and 400MHz for subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively, where the 400MHz bandwidth can be set based on the 400MHz bandwidth limit per carrier.

[0122] Figure 8A single parameter set is shown used across the entire bandwidth of the NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

[0123] 4. Transmission and reception technology

[0124] 4.1 Bandwidth

[0125] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, the UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

[0126] NR defines bandwidth parts (BWPs) to support UEs that cannot receive the full carrier bandwidth and supports bandwidth adaptation. In one instance, a BWP may be defined by a subset of contiguous RBs on a carrier. The UE may be configured (e.g., via the RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for the serving cell may be active. The one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0127] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP. For unpaired spectrum, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0128] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), the base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domain where a UE can look for control information. A search space may be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, a base station may configure a common search space for a UE on a PCell or a primary secondary cell (PSCell) in an active downlink BWP.

[0129] For an uplink BWP in the set of configured uplink BWPs, the BS may configure one or more resource sets for one or more PUCCH transmissions for the UE. The UE may receive downlink receptions (e.g., PDCCH or PDSCH) in the downlink BWP according to the configured parameter set (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP according to the configured parameter set (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0130] One or more BWP indicator fields may be provided in downlink control information (DCI). The value of the BWP indicator field may indicate which BWP in a set of configured BWPs is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0131] The base station may semi-statically configure a default downlink BWP for the UE within the set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP to the UE, the default downlink BWP may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0132] The base station may configure the BWP inactivity timer value for the PCell for the UE. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer in the following circumstances: (a) when the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0133] In one example, the base station may semi-statically configure the UE with one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating that the second BWP is the active BWP and / or in response to expiration of a BWP inactivity timer (e.g., when the second BWP is the default BWP).

[0134] Downlink and uplink BWP switching can be performed independently in paired spectrum (where BWP switching refers to switching from a currently active BWP to a non-currently active BWP). In unpaired spectrum, downlink and uplink BWP switching can be performed simultaneously. Switching between configured BWPs can occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or initiation of random access.

[0135] Fig. 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown. A UE configured with the three BWPs may switch from one BWP to another at a switching point. Fig. 9 In the example shown, the BWPs include: BWP 902, which has a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 904, which has a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 906, which has a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. The UE may switch between BWPs at a switching point. Fig. 9In the example of , the UE may switch from BWP 902 to BWP 904 at switch point 908. The switch at switch point 908 may occur for any suitable reason, such as in response to expiration of a BWP inactivity timer (indicating a switch to a default BWP) and / or in response to receiving a DCI indicating that BWP 904 is an active BWP. The UE may switch from active BWP 904 to BWP 906 at switch point 910 in response to receiving a DCI indicating that BWP 906 is an active BWP. The UE may switch from active BWP 906 to BWP 904 at switch point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is an active BWP. The UE may switch from active BWP 904 to BWP 902 at switch point 914 in response to receiving a DCI indicating that BWP 902 is an active BWP.

[0136] If the UE is configured for a secondary cell with a default downlink BWP and timer values ​​from the set of configured downlink BWPs, the UE procedures for switching the BWP on the secondary cell may be the same / similar to those on the primary cell. For example, the UE may use the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values ​​for the primary cell.

[0137] 4.2 Carrier Aggregation

[0138] To provide higher data rates, two or more carriers may be aggregated and transmitted to / from the same UE simultaneously using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CC). When CA is used, there are many serving cells for the UE, one serving cell per CC. CCs may have three configurations in the frequency domain.

[0139] Fig. 10A Three CA configurations with two CCs are shown. In the intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (Band A) and are located directly adjacent to each other in the frequency band. In the intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (Band A) and are separated by a gap in the frequency band. In the inter-band configuration 1006, the two CCs are located in the frequency bands (Band A and Band B).

[0140] In one example, up to 32 CCs may be aggregated. Aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplex schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may optionally be configured for the serving cell. For example, the ability to aggregate more downlink carriers than uplink carriers may be useful when the UE has more data traffic in the downlink than in the uplink.

[0141] When CA is used, one of the aggregated cells for the UE may be referred to as a primary cell (PCell). The PCell may be a serving cell to which the UE initially connects at RRC connection establishment, reestablishment and / or handover. The PCell may provide NAS mobility information and security input to the UE. The UE may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as a downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as an uplink primary CC (UL PCC). Other aggregated cells for the UE may be referred to as secondary cells (SCells). In one example, the SCell may be configured after the PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as an uplink secondary CC (UL SCC).

[0142] The configured SCell for a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Figure 4B The MAC CE may be used to activate and deactivate the configured SCells. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) are activated or deactivated for the UE. The configured SCells may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0143] The downlink control information of a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, which is called self-scheduling. The DCI of a cell can be transmitted on another cell, which is called cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ confirmation and channel state feedback, such as CQI, PMI and / or RI) can be transmitted on the PUCCH of the PCell. For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. The cell can be divided into multiple PUCCH groups.

[0144] Fig. 10B 10 shows an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Fig. 10B 1014. In the example of , PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) may be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) may be transmitted in the uplink of PSCell 1061. In one example, if Fig. 10B If the aggregated cell depicted in FIG. 1 is not divided into PUCCH group 1010 and PUCCH group 1050 , a single uplink PCell transmits UCI associated with a downlink CC, and the PCell may become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061 , overload can be prevented.

[0145] A physical cell ID and a cell index may be assigned to a cell comprising a downlink carrier and an optional uplink carrier. The physical cell ID or cell index may identify a downlink carrier and / or an uplink carrier of a cell, for example, depending on the context in which the physical cell ID is used. The physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. The cell index may be determined using an RRC message. In the present disclosure, the physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. For example, when the present disclosure relates to a first physical cell ID of a first downlink carrier, the present disclosure may mean that the first physical cell ID is used for a cell comprising the first downlink carrier. The same / similar concepts may apply, for example, to carrier activation. When the present disclosure indicates that a first carrier is activated, the present specification may mean that a cell comprising the first carrier is activated.

[0146] In CA, the multi-carrier nature of the PHY may be exposed to the MAC. In one example, the HARQ entity may operate on a serving cell. A transport block may be generated based on the assignment / grant of each serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.

[0147] 5. Reference signal

[0148] In the downlink, the base station may transmit (e.g., unicast, multicast and / or broadcast) one or more reference signals (RS) to the UE (e.g., PSS, SSS, CSI-RS, DMRS and / or PT-RS, such as Figure 5A In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. Figure 5B ). The PSS and SSS may be transmitted by a base station and used by a UE to synchronize the UE with the base station. The PSS and SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, SSS, and PBCH. The base station may periodically transmit bursts of SS / PBCH blocks.

[0149] Fig.11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as Fig.11A As shown). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts may be limited to half a frame (e.g., the first half frame with a duration of 5 ms). It should be understood that Fig.11Aare examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, burst position within a frame) may be configured based on, for example: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; a parameter set or subcarrier spacing for the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume the subcarrier spacing of the SS / PBCH blocks based on the carrier frequency being monitored unless the radio network configures the UE to assume a different subcarrier spacing.

[0150] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Fig.11A ) and may span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., spanning the next 3 OFDM symbols) and may span 240 subcarriers.

[0151] The UE may not know the location of the SS / PBCH blocks in the time and frequency domains (for example, when the UE is searching for cells). In order to find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain duration (for example, 20ms), the UE may search for the PSS at different frequency positions within the carrier, as indicated by the synchronization raster. If the PSS is found at a certain position in the time and frequency domains, the UE may determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block may be a cell definition SS block (CD-SSB). In one instance, the primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. In one instance, cell selection / search and / or reselection may be based on the CD-SSB.

[0152] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine the physical cell identifier (PCI) of the cell based on the sequence of the PSS and SSS, respectively. The UE may determine the location of the frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted according to a transmission pattern, wherein the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0153] The PBCH may use QPSK modulation and may use forward error correction (FEC). FEC may use polarity coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulating the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters may contribute to the time synchronization of the UE with the base station. The PBCH may include a master information block (MIB) for providing one or more parameters to the UE. The MIB may be used by the UE to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1). SIB1 may contain information required for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH that may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE may point to a frequency. The UE may search for SS / PBCH blocks at the frequency to which the UE is pointing.

[0154] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices.

[0155] SS / PBCH blocks (e.g., those within a half-frame) can be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​the cell). In one example, a first SS / PBCH block can be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block can be transmitted in a second spatial direction using a second beam.

[0156] In one example, within the frequency range of a carrier, a base station may transmit multiple SS / PBCH blocks. In one example, a first PCI of a first SS / PBCH block in the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block in the multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted in different frequency positions may be different or the same.

[0157] The CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more CSI-RSs of the same / similar CSI-RS. The UE may measure the one or more CSI-RSs. The UE may estimate the downlink channel state and / or generate a CSI report based on the measurement of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0158] The base station may semi-statically configure the UE with one or more CSI-RS resource sets. The CSI-RS resources may be associated with positions and periodicity in the time and frequency domains. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the UE that the CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0159] The base station can configure the UE to report CSI measurement values. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with the timing and / or period of multiple CSI reports. For aperiodic CSI reporting, the base station can request a CSI report. For example, the base station can command the UE to measure the configured CSI-RS resources and provide a CSI report related to the measurement value. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reporting. The base station can configure the UE with a CSI-RS resource set and CSI reporting using RRC signaling.

[0160] The CSI-RS configuration may contain one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH blocks.

[0161] The downlink DMRS may be transmitted by the base station and used by the UE for channel estimation. For example, the downlink DMRS may be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a frontload DMRS pattern. The frontload DMRS may be mapped on the one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PDSCH. The DMRS configuration may support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. The radio network may (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, in which the DMRS position, DMRS pattern, and / or scrambling sequence may be the same or different. The base station may use the same precoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE may use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

[0162] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used throughout a set of PRBs. The set of PRBs may be represented as a precoding resource block group (PRG).

[0163] The PDSCH may contain one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. Higher layers may configure up to 3 DMRS for the PDSCH.

[0164] The downlink PT-RS may be transmitted by a base station and used by a UE for phase noise compensation. Whether a downlink PT-RS exists may depend on an RRC configuration. The presence and / or type of a downlink PT-RS may be configured based on a UE-specific configuration using a combination of RRC signaling and / or an association with one or more parameters for other purposes (e.g., a modulation and coding scheme (MCS)) that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters containing at least an MCS. The NR network may support multiple PT-RS densities defined in time and / or frequency domains. When present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS may be limited to the scheduled time / frequency duration of the UE. The downlink PT-RS may be transmitted on a symbol to facilitate phase tracking at the receiver.

[0165] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS to consistently demodulate one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS mode. The front-loaded DMRS may be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of front-loaded DMRS symbols of the PUSCH and / or PUCCH, and the UE may use the front-loaded DMRS symbols to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS positions, DMRS patterns, and / or scrambling sequences of the DMRS may be the same or different.

[0166] The PUSCH may contain one or more layers, and the UE may transmit at least one symbol having a DMRS present on a layer in the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

[0167] Depending on the RRC configuration of the UE, an uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or type of the uplink PT-RS can be configured based on UE-specific configuration through a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters containing at least the MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be limited to the scheduled time / frequency duration of the UE.

[0168] The UE may transmit an SRS to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE may allow the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station may use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. The applicability of the SRS resource set may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, the SRS resources in the SRS resource set in the one or more SRS resource sets (e.g., having the same / similar time domain behavior, periodic, non-periodic, etc.) may be transmitted at a certain time (e.g., at the same time). The UE may transmit one or more SRS resources in the SRS resource set. The NR network may support non-periodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In one example, at least one DCI format may be used for the UE to select at least one configured SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In one example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0169] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or non-periodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slots of periodic and / or non-periodic SRS resources; the number of OFDM symbols in the SRS resources; the start OFDM symbol of the SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0170] 6. Beamforming

[0171] The antenna ports are defined so that the channel through which a symbol on the antenna port is communicated can be inferred from the channel through which another symbol on the same antenna port is communicated. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port. If one or more large-scale properties of the channel through which the first symbol on the first antenna port is communicated can be inferred from the channel through which the second symbol on the second antenna port is communicated, the first antenna port and the second antenna port can be referred to as quasi-co-located (QCLed). The one or more large-scale properties can include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0172] Channels using beamforming require beam management. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurements and generate beam measurement reports based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)). After setting up an RRC connection with a base station, the UE may perform a downlink beam measurement procedure.

[0173] Fig. 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Fig. 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may transmit one or more RRC messages containing CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters may be configured for the CSI-RS resource configuration through higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid) and / or other radio resource parameters.

[0174] Fig. 11B The three beams shown may be configured for a UE in a UE-specific configuration. Fig. 11B Three beams (beam #1, beam #2, and beam #3) are shown in the figure, and more or fewer beams can be configured. CSI-RS1101 can be allocated to beam #1, which can be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS1102 can be allocated to beam #2, which can be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS1103 can be allocated to beam #3, which can be transmitted in one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (for example, those subcarriers not used to transmit CSI-RS1101) to transmit another CSI-RS associated with the beam of another UE. By using time domain multiplexing (TDM), the beam for the UE can be configured so that the beam for the UE uses symbols from the beams of other UEs.

[0175] CSI-RS, such as Fig. 11BThose shown in (e.g., CSI-RS1101, 1102, 1103) may be transmitted by a base station and used by a UE for one or more measurement values. For example, a UE may measure a reference signal received power (RSRP) of a configured CSI-RS resource. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurement value to the network (e.g., via one or more base stations) based on the reporting configuration. In one instance, the base station may determine one or more transmission configuration indication (TCI) states containing multiple reference signals based on the reported measurement results. In one instance, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE may receive a downlink transmission having a receive (Rx) beam determined based on the one or more TCI states. In one instance, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE may determine the spatial domain filter of the transmit (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam-corresponding capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate the uplink beam of the UE based on measurements of one or more SRS resources transmitted by the UE.

[0176] In the beam management procedure, the UE may assess (e.g., measure) the channel quality of one or more beam pair links, beam pair links comprising a transmission beam transmitted by a base station, and a reception beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, wherein the one or more beam pair quality parameters include, for example, one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI) and / or rank indicator (RI).

[0177] Fig. 12AThree examples of downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurements of transmit (Tx) beams of a transmit reception point (TRP) (or multiple TRPs), for example to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of Tx beams of TRPs (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or the base station may perform procedure P2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0178] Fig. 12B Three examples of uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, for example, to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, Tx beam sweeping from a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or the base station may perform procedure U2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0179] The UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam-pair link of the associated control channel is unsatisfactory (e.g., having an error rate above an error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0180] The UE may measure the quality of a beam pair link using one or more reference signals (RS), the one or more reference signals comprising one or more SS / PBCH blocks, one or more CSI-RS resources and / or one or more demodulation reference signals (DMRS). The quality of a beam pair link may be based on one or more of the following: a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value and / or a CSI value measured on an RS resource. The base station may indicate that the RS resource is quasi-co-located (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, etc.). When the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from the transmission to the UE via the RS resource are similar or identical to the channel characteristics from the transmission to the UE via the channel, the RS resource and the one or more DMRS of the channel may be QCLed.

[0181] 7. Random Access

[0182] The network (e.g., gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in RRC_IDLE state and / or RRC_INACTIVE state may initiate a random access procedure to request a connection setup to the network. The UE may initiate a random access procedure from the RRC_CONNECTED state. The UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no available PUCCH resources) and / or to obtain uplink timing (e.g., when the uplink synchronization state is not synchronized). The UE may initiate a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). The UE may initiate a random access procedure for a beam failure recovery request. The network may initiate a random access procedure for handover and / or for establishing time alignment for SCell addition.

[0183] Fig.13A A four-step contention-based random access procedure is shown.Before initiating the procedure, the base station may transmit a configuration message 1310 to the UE. Fig.13AThe illustrated procedure involves the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0184] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or the RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the reception timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0185] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that can be used to transmit Msg 11311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between: (a) one or more PRACH opportunities, and (b) one or more reference signals. The one or more RACH parameters may indicate an association between: (a) one or more preambles, and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

[0186] The one or more RACH parameters provided in the configuration message 1310 may be used to determine the uplink transmission power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters may indicate a reference power for preamble transmission (e.g., a received target power and / or an initial power for preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramp step size; a power offset between SSB and CSI-RS; a power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplementary uplink (SUL) carrier).

[0187] Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may contain one or more preambles. The UE may determine the preamble group based on the path loss measurement value and / or the size of Msg 3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the UE may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0188] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use the one or more RACH parameters to configure the association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE may determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting a preamble and for determining a PRACH opportunity. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and the one or more reference signals.

[0189] If no response is received after the preamble transmission, the UE may perform a preamble retransmission. The UE may increase the uplink transmission power for the preamble retransmission. The UE may select the initial preamble transmission power based on the path loss measurement and / or the target received preamble power configured by the network. The UE may determine to retransmit the preamble and may ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramp-up step size for the preamble retransmission. The ramp-up step size may be the amount of incremental increase in the uplink transmission power for retransmission. If the UE determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission, the UE may ramp up the uplink transmission power. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds a threshold (eg, preambleTransMax) configured by the one or more RACH parameters, the UE may determine that the random access procedure was not successfully completed.

[0190] Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 is received by the base station. Msg 2 1312 may include a time alignment command that may be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to start the time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events that initiate a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. Examples of RA-RNTIs may be as follows:

[0191] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0192] Wherein s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≤s_id<14), t_id may be the index of the first time slot of the PRACH opportunity in the system frame (e.g., 0≤t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for the NUL carrier and 1 for the SUL carrier).

[0193] The UE may transmit Msg 3 1313 in response to successfully receiving Msg 2 1312 (e.g., using the resources identified in Msg 2 1312). Msg 3 1313 may be used, for example, Fig.13A Contention resolution in a contention-based random access procedure as shown in . In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UE. If the multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) may be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., if a C-RNTI is assigned, the TC-RNTI included in Msg 2 1312 and / or any other suitable identifier).

[0194] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If a C-RNTI is included in Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If a unique C-RNTI of the UE is detected on the PDCCH, it is determined that the random access procedure is successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in an RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU contains a UE contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0195] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., a random access procedure) may be supported in an uplink carrier. For example, a base station may configure two separate RACH configurations for a UE: one for a SUL carrier and the other for a NUL carrier. For random access in a cell configured with a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. For example, if the measured quality of one or more reference signals is below a broadcast threshold, the UE may determine the SUL carrier. The uplink transmission of the random access procedure (e.g., Msg 1 1311 and / or Msg 3 1313) may remain on the selected carrier. In one or more cases, the UE may switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE may determine and / or switch an uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (eg, listen before talk).

[0196] Fig. 13B The two-step contention-free random access procedure is shown in FIG. Fig.13A Similar to the four-step contention-based random access procedure shown, the base station may transmit a configuration message 1320 to the UE before the procedure is initiated. The configuration message 1320 may be similar to the configuration message 1310 in some aspects. Fig. 13B The illustrated procedure involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 may be similar in some respects to Fig.13A As shown in Msg 1 1311 and Msg 2 1312. Fig.13A and Fig. 13B It will be appreciated that the contention-free random access procedure may not include messages similar to Msg 3 1313 and / or Msg 4 1314 .

[0197] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Fig. 13B For example, the base station may indicate or assign a preamble to be used for Msg 1 1321 to the UE. The UE may receive an indication of the preamble (eg, ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0198] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. Fig. 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission is addressed to the C-RNTI, the UE may determine that the random access procedure is successfully completed. For example, if the UE receives a RAR containing a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR contains a MAC sub-PDU with the preamble identifier, the UE may determine that the random access procedure is successfully completed. The UE may determine that the response is an indication of a confirmation of the SI request.

[0199] Fig. 13C Another two-step random access procedure is shown. Fig.13A and Fig. 13B Similar to the random access procedure shown, the base station may transmit a configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar to configuration message 1310 and / or configuration message 1320 in some aspects. Fig. 13C The procedure shown involves the transmission of two messages: Msg A 1331 and Msg B 1332.

[0200] Msg A 1331 may be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. Transport block 1342 may include Fig.13A The transmission block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include the same content as the content of Msg 3 1313 shown in FIG. Fig.13A and Fig. 13B Msg 2 1312 (eg, RAR) and / or Fig.13A The content of Msg 4 1314 shown is similar and / or identical.

[0201] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Fig. 13C The UE may determine whether to initiate a two-step random access procedure based on one or more factors. The one or more factors may be: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; the cell size; the RRC state of the UE; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0202] The UE may determine the radio resources and / or uplink transmission power of the preamble 1341 and / or the transport block 1342 included in the Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control of the preamble 1341 and / or the transport block 1342. The time-frequency resources (e.g., PRACH) used for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel for monitoring and / or receiving the Msg B 1332.

[0203] Transport block 1342 may include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing high-level command; a power control command; an uplink grant (e.g., a radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the following conditions exist: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., transport block 1342).

[0204] 8. Physical layer control signaling

[0205] The UE and the base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). The control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0206] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling grant indicating uplink radio resources and / or transport format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) common to a group of UEs.

[0207] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with the identifier may include a Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of a radio network temporary identifier (RNTI).

[0208] DCI can be used for different purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notification. The P-RNTI can be predefined as hexadecimal "FFFE". A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as hexadecimal "FFFF". A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or the triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to Fig.13AThe other RNTIs configured by the base station to the UE may include: a configured scheduling RNTI (CS-RNTI), a transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), a transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmission power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0209] Depending on the purpose and / or content of the DCI, the base station may transmit DCI with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling of PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a UE group. DCI format 2_1 may be used to notify a UE group of physical resource blocks and / or OFDM symbols, where the UE may assume that no transmission to the UE is expected. DCI format 2_2 may be used to transmit a transmission power control (TPC) command for PUCCH or PUSCH. DCI formats 2_3 may be used to transmit a set of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

[0210] After scrambling the DCI with the RNTI, the base station may process the DCI with channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI on resource elements used for and / or configured for PDCCH. Based on the payload size of the DCI and / or the coverage of the base station, the base station may transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. CCE may include the number of resource element groups (REGs) (e.g., 6). REG may include resource blocks in an OFDM symbol. The mapping of coded and modulated DCI on resource elements may be based on the mapping of CCEs and REGs (e.g., CCE to REG mapping).

[0211] Fig.14A An example of a CORESET configuration for a bandwidth portion is shown. A base station may transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET may contain time-frequency resources in which a UE attempts to decode DCI using one or more search spaces. A base station may configure a CORESET in the time-frequency domain. Fig.14A In the example of , the first CORESET 1401 and the second CORESET 1402 appear at the first symbol in the time slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 appears at the third symbol in the time slot. The fourth CORESET 1404 appears at the seventh symbol in the time slot. The CORESETs can have different numbers of resource blocks in the frequency domain.

[0212] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown. The CCE to REG mapping can be an interlaced mapping (e.g., for the purpose of providing frequency diversity) or a non-interlaced mapping (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). The base station can perform different or the same CCE to REG mapping for different CORESETs. A CORESET can be associated with the CCE to REG mapping through RRC configuration. A CORESET can be configured with antenna port quasi-co-location (QCL) parameters. The antenna port QCL parameters can indicate the QCL information of the demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0213] The base station may transmit an RRC message containing configuration parameters of one or more CORESETs and one or more search space sets to the UE. The configuration parameters may indicate an association between a search space set and a CORESET. The search space set may contain a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: the number of PDCCH candidates to be monitored for each aggregation level; the PDCCH monitoring period and the PDCCH monitoring type; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0214] like Fig. 14B As shown, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE to REG mapping of the CORESET based on the configuration parameters of the CORESET (e.g., interlaced or non-interlaced and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET based on the RRC message (e.g., up to 10). The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space) and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE may determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambled bits of the CRC parity bits of the DCI matching the RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indications, downlink preemption, etc.).

[0215] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling transmission may include a hybrid automatic repeat request (HARQ) confirmation for the received DL-SCH transport block. The UE may transmit the HARQ confirmation after receiving the DL-SCH transport block. The uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station may determine the transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ confirmation (HARQ-ACK), CSI report, SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0216] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. If the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE may use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may include two or fewer bits. If four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two, the UE may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. If the transmission exceeds one or two symbols and the number of UCI bits is two or more, the UE may use PUCCH format 2. PUCCH format 3 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not include orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources include orthogonal cover codes, the UE may use PUCCH format 4.

[0217] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, an RRC message. The multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. The PUCCH resource set may be configured with: a PUCCH resource set index; multiple PUCCH resources having PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid); and / or multiple (e.g., maximum number) UCI ​​information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE may select one of the multiple PUCCH resource sets (e.g., HARQ-ACK, SR, and / or CSI) based on the total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE may select the first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

[0218] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine PUCCH resources for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The UE may determine the PUCCH resources based on a PUCCH resource indicator in a DCI (e.g., a DCI format 1_0 or a DCI for 1_1) received on the PDCCH. The three-bit PUCCH resource indicator in the DCI may indicate one PUCCH resource in eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may use the PUCCH resources indicated by the PUCCH resource indicator in the DCI to transmit UCI (HARQ-ACK, CSI, and / or SR).

[0219] 9. Base station and UE implementation plan

[0220] Fig.151 shows an example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as Figure 1A The mobile communication network 100 shown, Figure 1B The mobile communication network 150 shown or any other communication network. Fig.15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same Fig.15 Configurations the same or similar to those shown.

[0221] The base station 1504 may connect the wireless device 1502 to a core network (not shown) by radio communication via an air interface (or radio interface) 1506. The direction of communication from the base station 1504 to the wireless device 1502 over the air interface 1506 is referred to as downlink, while the direction of communication from the wireless device 1502 to the base station 1504 over the air interface is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0222] In the downlink, data to be sent from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 via, for example, a core network. In the uplink, data to be sent from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement layer 3 and layer 2 OSI functions to process data for transmission. Layer 2 may include, for example, information about Figure 2A , Figure 2B , Figure 3 and Figure 4A Layer 3 may include the following: Figure 2B RRC layer.

[0223] After processing by processing system 1508, data to be transmitted to wireless device 1502 may be provided to transmission processing system 1510 of base station 1504. Similarly, after processing by processing system 1518, data to be transmitted to base station 1504 may be provided to transmission processing system 1520 of wireless device 1502. Transmission processing system 1510 and transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4AFor transmission processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0224] At base station 1504, receive processing system 1512 may receive uplink transmissions from wireless device 1502. At wireless device 1502, receive processing system 1522 may receive downlink transmissions from base station 1504. Receive processing system 1512 and receive processing system 1522 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4A For reception processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, etc.

[0225] like Fig.15 As shown, the wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0226] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or codes that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Fig.15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or codes that may be executed to perform one or more of their respective functions.

[0227] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal encoding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0228] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touch pad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from the power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as batteries, solar cell units, fuel cell units, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to the GPS chipset 1517 and the GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0229] Fig.16AAn example structure for uplink transmission is shown. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of the following: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulated symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and the like. In one instance, when transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one instance, when transform precoding is not enabled, the uplink transmission may be performed by Fig.16A Generate a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0230] Fig. 16B An example structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0231] Fig. 16C An example structure for downlink transmission is shown. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0232] Fig.16D Another example structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex valued OFDM baseband signal at an antenna port. Filtering may be employed prior to transmission.

[0233] The wireless device may receive one or more messages (e.g., RRC messages) containing configuration parameters of multiple cells (e.g., primary cells, secondary cells) from a base station. The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the wireless device at the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, and RRC layer. For example, the configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, and the like. For example, the configuration parameters may include parameters indicating the values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0234] Once started, a timer can start running and continue running until it stops or until it expires. If the timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or can start from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). A timer can be used for a time period / window of a measurement process. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing the timer can be used for a time period / window of a measurement procedure. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In an example, instead of starting and expiring a random access response window timer, a time difference between two timestamps can be used. When the timer is restarted, the measurement process of the time window can be restarted. Other example implementations can be provided to restart the measurement of the time window.

[0235] The network can provide services for various vertical industries and various users. Existing quality of service (QoS) requirements may not be sufficient to provide a good user experience to meet all user requirements. Therefore, in 5G networks, it is necessary to collect user key performance indicator (KPI) information, such as application layer end-to-end reliability statistics indicators, etc. For example, KPIs for characterizing insufficient video streaming performance (e.g., as perceived by users) include initial stagnation of broadcast; periods of stagnation and freezing of video during playback; interruptions of audio during playback; low encoding quality presented as blur, macroblocking or mosquito artefacts; and / or variable encoding quality during playback. KPIs and other information can be collected (e.g., by the network, a measurement collection entity (MCE) of the network, etc.). The collected information can be used to determine and / or manage the user's quality of experience (QoE). QoE support can be used for any service type, such as streaming services, multimedia telephony services for IMS (MTSI), multimedia broadcast and multicast services (MBMS), augmented reality (AR), virtual reality (VR), extended reality (XR), video streaming services, etc. In addition to QoE metrics, radio related measurements and information are also considered to assist NR QoE management functions.

[0236] New Radio (NR) and Long Term Evolution (LTE) support an application layer measurement collection function for QoE. This function enables the collection of application layer measurements from a user equipment (UE) or one or more UEs in a region. The collected information is transmitted to a collection center (e.g., MCE) where it can be analyzed.

[0237] The initiation of measurement value collection can be signaling-based or management-based. For the signaling-based case (an example of which is shown in Fig.17 In the case of management-based (an example of which is shown in FIG. 1 ), application layer measurement collection is initiated from a core network (CN) node (e.g., mobility management function, AMF, MME, SMF, etc.) to the UE. Fig.18 The collection of application layer measurements is initiated from Operation, Administration and Maintenance (OAM). OAM can target a region (e.g., containing any number of UEs) instead of targeting a specific UE. The received application layer measurement configuration can be encapsulated in a transparent container, which is forwarded to the UE in a downlink RRC message. The application layer measurements received from the higher layers of the UE are encapsulated in a transparent container and sent to the network in an uplink RRC message.

[0238] Fig.17An example of a signaling-based activation and deactivation procedure is shown. In the signaling-based activation procedure, the QoE measurement value is intended for a specific subscriber. OAM and CN can select the UE based on the UE's subscription information and the UE's capabilities. CN can initiate the activation of QoE measurements configured by OAM and can send QoE measurement configurations to base stations (e.g., NG-Radio Access Network (NG-RAN), gNB, eNB, etc.).

[0239] The base station may send a QoE measurement configuration to the UE. The QoE measurement configuration may be sent in a radio resource control (RRC) message. The QoE measurement configuration may be received by an access stratum (AS) layer of the UE. The AS layer of the UE may send the QoE measurement configuration to the application layer of the UE. Configuration and reporting of multiple simultaneous QoE measurements of the UE may be supported.

[0240] The UE may perform one or more measurements based on the QoE measurement configuration. For example, the UE may perform QoE measurements including average throughput, initial broadcast delay, buffer level status, and playback period list (playlist) for streaming and VR services. The UE may perform QoE measurements including continuous loss of real-time transport protocol packets, frame rate, jitter duration, synchronization loss duration, round-trip time, average codec bit rate, and call setup time for MTSI services. The UE may additionally perform QoE measurements including viewport switching delay of comparable quality for VR services and a list of rendered viewports during media presentation. One or more results of the measurements may be used to generate a QoE report.

[0241] The UE application layer can send a QoE report to the UE AS layer. The UE AS layer can send a QoE report to the base station. The QoE report can be sent in an RRC message. The QoE report can be sent via a separate SRB in NR. The base station can transmit the QoE report to the configured destination, for example, the measurement collection entity (MCE). The transmission of the QoE report may require RRC segmentation, and any potential solution requires detailed technical specifications of procedures. Management-based QoE configuration should not override signaling-based QoE configuration.

[0242] In the signaling-based deactivation procedure, the deactivation of QoE measurements is configured by OAM and triggered by CN. CN may initiate the deactivation of QoE measurements as configured by OAM, and may send a deactivation indication to the NG-RAN node to indicate which QoE measurements should be deactivated. The NG-RAN node may send a deactivation indication to the UE AS layer, and then the UE AS layer may send a deactivation indication to the UE application layer.

[0243] Fig.18An example of management-based activation and deactivation procedures is shown. In the management-based activation procedure, the QoE measurement configuration is used to activate the QoE measurement configured and triggered by OAM. OAM can send the QoE measurement configuration to the NG-RAN node. NG-RAN can find multiple qualified UEs that meet the criteria (for example, the NG-RAN node selects UEs that meet the required QoE measurement capabilities, area range, slice range, etc.). The NG-RAN node can send the QoE measurement configuration to the UE or the AS layer of each qualified UE. The UE AS layer can send the QoE measurement configuration to the UE application layer. When the session starts, the application layer in the UE can check the criteria (for example, cell list, service type, etc.), and if the criteria are met, QoE measurement and reporting can be started.

[0244] In the management-based activation procedure, the measurement and reporting aspects may be similar to the signaling-based activation procedure described above.

[0245] In the management-based deactivation procedure, the deactivation of QoE measurement is configured and triggered by OAM. OAM can send a deactivation configuration to the base station to indicate which QoE measurement should be deactivated. If the NG-RAN node receives an indication to deactivate the QoE measurement configuration, the NG-RAN node can send a deactivation indication to the UE AS layer, and the UE AS layer can send the deactivation indication to the application layer in the UE.

[0246] In one example, QoE measurement triggering and stopping can be implemented using time-based and / or threshold-based criteria configured by OAM.Threshold-based QoE measurement triggering and stopping allows starting and stopping QoE measurements when a given threshold is passed.

[0247] In one example, the NG-RAN node may release a version of the QoE measurement configuration of the UE that was previously configured for QoE measurement reporting, provided that the session for reporting QoE measurements has completed. For example, if a handover is made to a network that does not support the ongoing QoE measurement configuration or QoE reporting configuration, the RAN may need to release the ongoing QoE measurement configuration or QoE reporting configuration.

[0248] In one example, the NG-RAN node may release a version of the QoE measurement configuration of the UE that was previously configured for QoE measurement reporting, provided that the session for reporting QoE measurements has completed. For example, if a handover is made to a network that does not support the ongoing QoE measurement configuration or QoE reporting configuration, the RAN may need to release the ongoing QoE measurement configuration or QoE reporting configuration.

[0249] In one example, in the case of overload in a standalone connection, the RAN may stop new QoE measurement configurations, may release existing QoE measurement configurations, and may suspend QoE measurement reporting. The gNB may use RRC signaling to instruct the UE to suspend or resume QoE reporting.

[0250] In one example, seamless mobility may be a key functionality in NR and its impact should be measurable at the application layer. To enable measurement of the impact of mobility on the QoE of applications and users, it may be necessary to support QoE measurement report continuity in intra-RAT intra-node and inter-node mobility scenarios within the system: intra-node mobility for both management-based and signaling-based QoE. At least signaling-based QoE also supports this case in the case of inter-node mobility.

[0251] In one instance, to support QoE measurements in LTE mobility scenarios, the QoE configuration may be forwarded from the source eNB to the target eNB inside the Trace Activation IE over the X2 interface. When the X2 interface is not established between the source and the target, the same information for the mobility scenario may be sent over the S1 interface. In NR, to support mobility of QoE measurements in the RRC CONNECTED state, transmission of QoE measurement configurations over the Xn and NG interfaces within the Trace Activation IE as part of the UE Application Layer Measurement Configuration IE may be supported, and the UE Application Layer Measurement Configuration IE may contain multiple QoE configurations for multiple service types. For MBS, QoE measurements in RRC IDLE and RRC INACTIVE states may be supported. To support maintaining the QoE measurement configuration in RRC INACTIVE state mobility, the UE's QoE measurement configuration may be obtained from the node hosting the UE context.

[0252] In addition, the requirements for QoE measurements specify that the client can check the QoE configuration at the start of a session. This means that the client can continue QoE measurements for an ongoing session even if the UE moves out of the configured area. These requirements are RAT independent and can therefore also be applied to mobility solutions for QoE measurements in NR. QoE measurement report continuity in intra-system inter-RAT mobility scenarios can be supported. QoE measurement report continuity in inter-system mobility scenarios can also be supported.

[0253] In one instance, the RAN (eNB or gNB) may not understand or use the old QoE metrics because they are assembled by OAM, sent inside a container and are intended to be processed by the measurement value collection entity in the network. If the eNB or gNB needs to use the QoE concept, it may be required that the QoE information should be visible to the eNB or gNB. RAN-visible QoE information is simplified QoE information extracted by the UE from the QoE metrics, which the eNB or gNB can use for various types of enhancements. RAN-visible QoE can be used for all services. The RAN may be responsible for assembling the RAN-visible QoE measurement configuration. The RAN may be responsible for triggering, i.e., activating, the RAN-visible QoE measurements. The RAN may be able to autonomously configure the RAN-visible QoE for a given service type if application layer QoE for the same service type has already been configured. The RAN-visible QoE value may be generated by the UE and the QoE server. The RAN that generates the RAN-visible QoE value may require the RAN to read the XML-formatted QoE report.

[0254] Fig.19 An example of a message flow for RAN visible QoE information reporting is shown. The NG-RAN node may assemble and send to the UE a RAN visible QoE configuration, which may be sent along with a QoE measurement configuration container transmitted from the OAM directly or via the CN.

[0255] The UE may receive and apply a RAN-visible QoE configuration and / or a QoE measurement configuration container. The RAN-visible QoE configuration may be such that the corresponding RAN-visible QoE information reported may be a unique value or a combination of values ​​reflecting a QoE metric (e.g., buffer level) available to the RAN. The RAN-visible report may be provided from the UE's application layer to the UE's RRC layer by means of an AT command. The UE's RRC layer may then include the RAN-visible report as well as the QoE report container, but the RAN-visible report may be a separate IE in the MeasReportAppLayer IE and may be sent to the RAN. The NG-RAN node may read the RAN-visible QoE information and / or may forward the (old) QoE report container to the QoE server accordingly. Alternatively, the OAM server may generate a RAN-visible QoE report and may send it to the RAN.

[0256] In one instance, the RAN may also trigger radio-related measurements for a specific UE so that the network can further evaluate and improve QoE based on the QoE measurement configuration received from the OAM. In order to trigger the measurement, an existing mechanism may be used. The collection of radio-related measurement values ​​may be accomplished by existing methods such as Minimization of Drive-Tests (MDT). Radio-related QoE measurement values ​​of all types of supported services may be reported, which may include additional measurement values ​​related to the radio interface. If NR QoE management requires new radio-related measurements currently specified in the MDT, these additional radio-related QoE measurements may be performed as part of the MDT measurements. Application-related QoE measurement values ​​may be collected while an application session is ongoing. If these radio-related measurement values ​​are used to assist application-related QoE measurements, they are effective in the case where measurement value collection and reporting can start at the same time. If, for example, the same trace reference and alignment time (e.g., based on a timestamp) are configured together, the correlation of the results may be accomplished by post-processing. In addition to the radio-related measurement results, radio-related information may also be reported. Radio-related information may be reported even when radio-related measurements are not triggered by the radio. Both radio related measurements and radio related information may be collated and correlated with the QoE report.

[0257] Fig. 20 An example of UEs with the same service type being served by different slices is shown. Fig. 20 As shown, UE1 is served by slice #1 and UE2 is served by slice #2. If the service level agreements (SLAs) of slice #1 and slice #2 are different, the QoE of UE1 and UE2 may be different for the same service type. For each slice QoE measurement, three scenarios are considered. Scenario 1: The case where different slices are used for different service types. Scenario 2: The case where the same slice is used for different service types. Scenario 3: The case where different slices are used for the same service type.

[0258] In one instance, the OAM / CN may transmit a QoE measurement configuration to the NG-RAN node, including a slice range (a list of single network slice selection assistance information (S-NSSAI)). The NG-RAN node may map the slice range to a list of ongoing PDU sessions and may send the QoE measurement configuration with the PDU session list to the UE. The UE may receive the QoE measurement configuration and may send it to the corresponding application layer based on the PDU session list. The UE may send a QoE report with a PDU session ID to the NG-RAN node. The NG-RAN node may remap the PDU session ID back to a slice ID (S-NSSAI) and attach it to the QoE report. The NG-RAN node may forward the QoE report with the slice ID to the MCE.

[0259] In one instance, the OAM or CN may transmit a QoE measurement configuration to the NG-RAN node, including a slice range. The NG-RAN node may check the slice range and the ongoing PDU session and may send a QoE measurement configuration with a qualified PDU session including the slice range to the UE. The UE may receive the QoE measurement configuration and may send it to the corresponding application layer according to the slice range. The mapping may be performed in the application layer or the access layer (AS) layer. The UE may send a QoE report with a slice ID to the NG-RAN node. The NG-RAN node may forward the QoE report with the slice ID to the MCE.

[0260] In one instance, the OAM or CN may transmit the QoE measurement configuration (including the associated slice ID) to the NG-RAN node outside the QoE configuration container, i.e. visible to the RAN. The NG-RAN node may check the slice ID for the ongoing PDU session and send the QoE measurement configuration with the qualified PDU session including the slice ID to the UE. The UE may receive the QoE measurement configuration and perform QoE measurements. The UE may send a QoE report to the NG-RAN node and may add the slice ID outside the QoE report container. The NG-RAN node may forward the QoE report with the slice ID to the MCE.

[0261] In the prior art, a wireless device (e.g., UE) measures the quality of experience (QoE) of a service and may report the measured QoE to a network. The network may improve the quality of the service based on the reported QoE measurement results. In one example, when the wireless device is in an RRC idle state and / or an RRC inactive state, the wireless device may measure the QoE of the service. When the wireless device is able to report (e.g., after transitioning to an RRC connected state; based on a small data transmission procedure, etc.), the wireless device may report the QoE measured in the RRC idle state and / or the RRC inactive state to the network. In one example, as Fig.21 and / or Fig.25 As shown, the location where the wireless device measures the QoE of the service may be different from the location where the wireless device reports the QoE of the service to the network. In one example, the time when the wireless device measures the QoE of the service may be different from the time when the wireless device reports the QoE of the service to the network. The network that receives the measured QoE of the service from the wireless device may consider that the measurement of the QoE is performed at the location where the wireless device reports the QoE and / or at the time when the wireless device reports the QoE. The network may adjust the configuration parameters of the service at the current location and time based on the QoE measured at the previous location and / or time. Adjusting the configuration parameters of the service at the current location and / or time based on the QoE measured at different locations and / or times may be inappropriate for the wireless device using the service at the current location and / or time. Implementations of the prior art may increase ineffective configurations of wireless devices and / or reduce the quality of service.

[0262] Example embodiments may enable a wireless device to send to a network information about an area in which the wireless device measures the QoE of a service and / or information about a time at which the wireless device measures the QoE of a service. The network may determine configuration parameters for the service based on the measured QoE of the service and information about the area and / or time associated with measuring the QoE. In an example, the network may adjust configuration parameters for the area and / or time associated with the reported QoE measurement to improve the quality of the service. Example embodiments may improve configuration efficiency and / or service quality of the wireless device.

[0263] Example embodiments may support a wireless device sending a message to a network indicating whether a QoE measurement result / report is available. Based on the indication, the network may determine whether to request a QoE measurement result / report from the wireless device, and / or may request a QoE measurement result / report from the wireless device based on the determination. If the wireless device indicates that the QoE measurement result is available, the network may request the QoE measurement result / report from the wireless device. If the network requests the QoE measurement result / report, the wireless device may send the QoE measurement result / report to the network. Example embodiments may reduce unnecessary signaling between the wireless device and the network. Example embodiments may increase signaling efficiency.

[0264] In one example, if Fig. 22 and / or Fig.26As shown, a wireless device (e.g., user equipment, UE, drone, vehicle, handset, VR device, media playback device, etc.) can communicate with a network (e.g., base station, gNB, eNB, access node, access device, access point, etc.). The wireless device can transmit packets associated with the service together with the network. When the wireless device is in an RRC idle state and / or an RRC inactive state, the wireless device can transmit packets associated with the service together with the network. The wireless device can transmit packets associated with the service together with the network before the wireless device experiences a connection failure (e.g., radio link failure, handover failure, etc.). The wireless device can select a cell and / or access cell of a first base station (BS1; e.g., gNB, eNB, access node, access device, access point, etc.) based on the selection cell. The first base station can be a base station of the network that transmits packets associated with the service together with the wireless device.

[0265] In one example, if Fig.24 and / or Fig.28 As shown, the first base station (BS1) may be different from the base station (BS2) of the network with which the wireless device communicates packets associated with the service. Fig.24 and / or Fig.28 In the present invention, the wireless device can communicate with a second base station (BS2; for example, gNB, eNB, access node, access device, access point, etc.) of the network.

[0266] In one example, if Fig.23 and / or Fig. 27 As shown, a base station (BS; for example, a first base station or a second base station) that transmits packets associated with a service together with a wireless device may include a central unit of a base station (BS-CU) and a distributed unit of a base station (BS-DU). The central unit of the base station may include a central unit control plane of a base station (BS-CU-CP) and / or a central unit user plane of a base station (BS-CU-UP). The distributed unit of the base station may provide at least one of the following: a physical layer, a MAC layer, an RLC layer, etc. The central unit control plane of the base station may provide at least one of the following: a PDCP layer, an RRC layer, etc. The central unit user plane of the base station may provide at least one of the following: a PDCP layer, an SDAP layer, etc.

[0267] In one example, if Fig. 22As shown, the wireless device may transmit a packet associated with the service (e.g., in an RRC idle state, an RRC inactive state, an RRC connected state, etc.). The wireless device may determine a quality of experience (QoE) of the service based on the transmitted packet. The wireless device may send a measurement report to the first base station (e.g., when the wireless device is in an RRC connected state). The measurement report may include the QoE of the service. The measurement report may include at least one of the following: area information associated with the QoE of the service and / or time information associated with the QoE of the service.

[0268] In one example, if Fig.26 As shown, the wireless device may transmit a packet associated with the service. The wireless device may determine the QoE of the service based on the transmitted packet. The wireless device may send an RRC completion message to the first base station confirming that the configuration of the RRC connection is complete. The RRC completion message may include a field indicating that a measurement report associated with the service is available. The wireless device may receive an information request message indicating the measurement report from the first base station. In response to receiving the information request message, the wireless device may send an information response message including a measurement report, the measurement report including the QoE of the service.

[0269] In one example, the first base station may transmit a packet associated with the service with the wireless device in the RRC idle state or the RRC inactive state. The first base station may receive a measurement report including the QoE of the service from the wireless device (e.g., directly and / or indirectly via another base station). When the wireless device is in the RRC idle state or the RRC inactive state, the wireless device may measure the QoE of the service. The measurement report may include at least one of the following: area information associated with the QoE of the service; time information associated with the QoE of the service, etc.

[0270] The wireless device may receive at least one RRC message, the at least one RRC message including resource configuration parameters of one or more packet flows (e.g., one or more bearers, one or more logical channels, one or more QoS flows, one or more PDU sessions, etc.) associated with a service. The at least one RRC message may include at least one of the following: an RRC reconfiguration message, an RRC resume message, an RRC setup message, an RRC release message, etc. The wireless device may receive from a first base station (e.g., Fig. 22 , Fig.23 , Fig.26 and / or Fig. 27 BS in), a second base station (eg, Fig.24 and / or Fig.28 The resource configuration parameter may include an identifier of the service.

[0271] The wireless device may receive at least one configuration message including measurement configuration parameters. The at least one configuration message may include at least one of the following: an RRC reconfiguration message, an RRC recovery message, an RRC setup message, an RRC release message, a logged measurement configuration message, etc. The wireless device may receive at least one configuration message including measurement configuration parameters from a first base station (e.g., Fig. 22 , Fig.23 , Fig.26 and / or Fig. 27 BS in), a second base station (eg, Fig.24 and / or Fig.28 The measurement configuration parameter may include an identifier of the service.

[0272] In an example, the measurement configuration parameters may include area configuration information, the area configuration information including at least one of the following: at least one identifier of at least one cell; at least one identifier of at least one tracking area; at least one identifier of at least one registration area; at least one identifier of at least one multicast / broadcast single frequency network (MBSFN) area; information of at least one carrier frequency (e.g., ARFCN of a carrier frequency associated with a service), etc. The measurement configuration parameters may include time configuration information, the time configuration information including at least one of the following: at least one time for measuring the QoE of the service (e.g., an absolute time based on a time zone); at least one duration for measuring the QoE of the service; at least one time for using the service; at least one duration for using the service, etc.

[0273] In one example, the measurement configuration parameter may include threshold information, the threshold information including a threshold to initiate a measurement report of the QoE of the service. In one example, the threshold may include at least one of the following: a threshold buffer level (e.g., a buffer level of an application layer associated with the service); a threshold throughput (e.g., an average throughput); a threshold playout delay; a threshold playlist; a threshold packet loss rate; a threshold frame rate; a threshold jitter duration; a threshold synchronization loss duration; a threshold round trip time (RTT) (e.g., a signal transmission delay time from the wireless device to the device providing the service and a signal transmission delay time to the device providing the service to the wireless device); a threshold codec bit rate; a threshold call setup time; a threshold viewport switching delay, etc. In one example, if the QoE of the service meets / satisfies one or more of the thresholds, the wireless device may send a measurement report including the QoE of the service to the network (e.g., including the first base station, the second base station, etc.). The sending of the measurement report by the wireless device to the first base station may be based on the threshold information.

[0274] In one example, the measurement configuration parameter may include a reporting periodicity (e.g., a time period, one or more system frame numbers, one or more subframe numbers, milliseconds, etc.) to report the measurement result of the QoE of the service. The sending of the measurement report by the wireless device to the first base station may be based on the reporting periodicity. The wireless device may periodically report the measurement result of the QoE of the service, for example, after each time period indicated by the reporting periodicity.

[0275] In one example, if Fig. 22 and / or Fig.26 As shown, the wireless device may transmit a packet associated with the service (e.g., in an RRC idle state, an RRC inactive state, an RRC connected state, etc.). In one example, the first base station may transmit a packet associated with the service together with the wireless device in the RRC idle state or the RRC inactive state. The packet associated with the service may include at least one of the following: an application layer packet, an IP layer packet, an SDAP layer packet of a PDU session and / or a QoS flow associated with the service, a PDCP layer packet of a bearer (e.g., a data radio bearer) associated with the service, an RLC layer packet of a logical channel associated with the service, a MAC layer packet of a logical channel associated with the service, one or more transport blocks, etc.

[0276] In one example, transmitting the packet associated with the service may include transmitting the packet when the wireless device is in an RRC idle state or an RRC inactive state. In one example, transmitting the packet associated with the service may include transmitting the packet when the wireless device is in an RRC connected state.

[0277] The wireless device may transmit a packet associated with the service at a first area. The first area may include at least one of the following: a location of the wireless device; a cell; a tracking area; a registration area; a multicast / broadcast single frequency network (MBSFN) area; an area covered by a carrier frequency (e.g., an ARFCN of a carrier frequency associated with the service), etc. The wireless device may transmit a packet associated with the service at a certain time (e.g., a first time).

[0278] In one example, a service associated with a packet transmitted by a wireless device may include a service type, wherein the service type includes at least one of the following: streaming media (e.g., DASH streaming media); multimedia telephony service (MTSI) for Internet Protocol (IP) multimedia subsystem (IMS); virtual reality (VR); extended reality (XR), etc. In one example, the service may include a multimedia broadcast service (MBS) and / or a multimedia broadcast multicast service (MBMS). In one example, the service may include a network slice, wherein the network slice includes at least one of the following: eMBB (e.g., a slice suitable for handling 5G enhanced mobile broadband); URLLC (e.g., a slice suitable for handling ultra-reliable low latency communication (URLLC)); MIoT (e.g., a slice suitable for handling massive IoT); V2X (e.g., a slice suitable for handling V2X services); HMTC (e.g., a slice suitable for handling high-performance machine type communications), etc.

[0279] In one example, the wireless device may determine the QoE of the service based on the transmitted packets. When the wireless device is in an RRC idle state or an RRC inactive state, the wireless device may measure the QoE of the service. When the wireless device is in an RRC connected state, the wireless device may measure the QoE of the service. The application layer of the wireless device may monitor the packets and / or may measure the QoE of the service. The application layer of the wireless device may send the QoE of the service to a lower layer (e.g., an RRC layer, etc.) of the wireless device.

[0280] In an example, the wireless device may measure the QoE of the service at a first area. The first area may include at least one of the following: a location of the wireless device; a cell; a tracking area; a registration area; a multicast / broadcast single frequency network (MBSFN) area; an area covered by a carrier frequency (e.g., an ARFCN of a carrier frequency associated with the service), etc. The wireless device may measure the QoE of the service at a certain time (e.g., a first time).

[0281] In one instance, the QoE of a service may include at least one of the following: buffer level status (e.g., the buffer level of the application layer associated with the service); throughput (e.g., average throughput); playout delay; playlist; packet loss rate; frame rate; jitter duration; synchronization loss duration; round-trip time (RTT) (e.g., signal transmission delay time from a wireless device to a device providing the service and signal transmission delay time to a device providing the service to the wireless device); codec bit rate; call setup time; viewport switching delay, etc.

[0282] In one example, the QoE of a service may include average throughput, playout latency, buffer level status, and / or a playback period list (playlist) of a streaming service and / or a VR service (e.g., a service). In one example, the QoE of a service may include continuous loss of real-time transport protocol packets, frame rate, jitter duration, synchronization loss duration, round trip time (RTT), average codec bit rate, and / or call setup time of an MTSI service (e.g., a service). In one example, the QoE of a service may include a viewport switching latency of comparable quality for a VR service (e.g., a service) and / or a list of viewports rendered during media presentation.

[0283] In one example, the wireless device may send a measurement report to the first base station. The measurement report may include the QoE of the service. The measurement report may include at least one of the following: area information associated with the QoE of the service; time information associated with the QoE of the service, etc. The first base station may receive a measurement report including the QoE of the service from the wireless device (e.g., directly and / or indirectly via another base station). In one example, when the wireless device is in an RRC connected state, the wireless device may send a measurement report to the first base station. In one example, when the wireless device is in an RRC inactive state or an RRC idle state, the wireless device may send a measurement report to the first base station using a small data transmission procedure. Sending a measurement report to the first base station may include sending a measurement message via at least one of the following: a measurement report message, an MCG failure information message, an SCG failure information message, an RRC recovery completion message, an RRC setup completion message, an RRC reconstruction completion message, a UE information response message, etc.

[0284] In one example, the wireless device may send an RRC completion message to the first base station confirming that the configuration of the RRC connection is complete. In one example, the RRC completion message may include at least one of the following: an RRC recovery completion message, an RRC setup completion message, an RRC reestablishment completion message, etc. The RRC completion message may include a field indicating that a measurement report associated with the service is available. In one example, the RRC completion message may include a field indicating that a QoE measurement is available. In one example, the RRC completion message may include a field indicating that a QoE measurement is available for the service. The first base station may determine to request a measurement report and / or QoE of the service from the wireless device based on the RRC completion message (e.g., based on a field indicating that a measurement report and / or QoE measurement of the service is available). The wireless device may receive an information request message (e.g., a UE information request message) indicating / requesting a measurement report and / or QoE of the service from the first base station. In one example, the information request message may include a field indicating a QoE measurement. In response to receiving the information request message, the wireless device may send an information response message (e.g., a UE information response message) containing a measurement report to the first base station, wherein the measurement report contains the QoE of the service.

[0285] In one example, the wireless device may select a cell of the first base station. The wireless device may perform a random access procedure via the cell. The wireless device may send an RRC request message requesting an RRC connection to the first base station. The RRC request message may include at least one of the following: an RRC setup request message, an RRC recovery request message, an RRC reconstruction request message, etc. In response to sending the RRC request message, the wireless device may receive an RRC response message from the first base station. The RRC response message may include at least one of the following: an RRC setup message, an RRC recovery message, an RRC reconstruction message, etc. Sending an RRC completion message confirming that the configuration of the RRC connection is complete (e.g., indicating that the measurement report and / or the QoE measurement of the service is available) may be based on receiving the RRC response message from the first base station. In one example, the wireless device may send an RRC request message requesting an RRC connection via the cell of the first base station without a random access procedure (e.g., no rach and / or skip rach access).

[0286] In one example, a wireless device in an RRC connected state may determine a connection failure (e.g., radio link failure, RLF, handover failure, HOF, etc.). When the wireless device is in an RRC connected state, the wireless device may transmit packets of a service and / or measure the QoE of the service. The wireless device may perform an RRC reestablishment procedure with the first base station (e.g., via a cell of the first base station). The RRC reestablishment procedure may include: sending an RRC reestablishment request message to the first base station; in response to sending the RRC reestablishment request message, receiving an RRC reestablishment message from the first base station; in response to receiving an RRC reestablishment message confirming that the configuration of the RRC connection is complete, sending an RRC completion message including an RRC reestablishment completion message to the first base station, etc. The RRC completion message may include at least one of the following: a field indicating that a measurement report associated with the service is available; a field indicating that QoE measurement is available; a field indicating that QoE measurement of the service is available, etc.

[0287] In an example, the measurement report may include region information associated with the QoE of the service. The region information may indicate a first region in which the wireless device transmits packets associated with the service and / or in which the wireless device measures the QoE of the wireless device. The region information may include parameters indicating a first region in which the wireless device transmits packets associated with the service and / or in which the wireless device measures the QoE of the wireless device. The parameters indicating the first region may include at least one of the following: information of a location (e.g., geographic location, latitude, longitude, etc.) of the wireless device; an identifier of a cell; an identifier of a tracking area; an identifier of a registration area; an identifier of a RAN region; an identifier of a multicast / broadcast single frequency network (MBSFN) region; information of a carrier frequency (e.g., an ARFCN of a carrier frequency associated with the service), etc.

[0288] In an example, the measurement report may include time information associated with the QoE of the service. The time information may indicate a time (e.g., a first time) when the wireless device transmits a packet associated with the service and / or when the wireless device measures the QoE of the wireless device. The time information may include at least one of the following: a time when the QoE of the service is measured (e.g., an absolute time based on a time zone, a time elapsed since the QoE was measured, etc.); a duration of measuring the QoE of the service; a time when the service is used (e.g., an absolute time based on a time zone, a time elapsed since the service is used, etc.); a duration of using the service, etc.

[0289] In one instance, the measurement report may include at least one of the following: a field indicating a reference signal received power (RSRP) of at least one cell / carrier or at least one reference signal associated with transmitting packets associated with the service; a field indicating a reference signal received quality (RSRQ) of at least one cell / carrier or at least one reference signal associated with transmitting packets associated with the service; a field indicating a block error rate (BLER) of data and / or signaling (e.g., for each channel used for the service); a field indicating a block error rate (BER) of data and / or signaling (e.g., for each channel used for the service), etc.

[0290] In an example, the measurement report may include an identifier of the service. The measurement report may include an identifier of a service type, the service type including at least one of the following: streaming media (e.g., DASH streaming), MTSI, VR, XR, etc. The measurement report may include at least one of the following: an identifier of a streaming media (e.g., DASH streaming) service; an identifier of an MTSI service; an identifier of a VR service; an identifier of an XR service, etc. The measurement report may include at least one of the following: an identifier of an MBS (or MBMS) service, an identifier of a network slice (e.g., including at least one of the following: eMBB, URLLC, MIoT, V2X, HMTC, etc.), etc. The identifier of the network slice may include network slice selection assistance information (NSSAI), single network slice selection assistance information (S-NSSAI), etc. The S-NSSAI may include a slice / service type (SST), which may refer to an expected network slice behavior in terms of features and services), and / or a slice differentiator (SD), which may be optional information that supplements the slice / service type to distinguish multiple network slices of the same slice / service type.

[0291] In one example, if Fig. 22 and / or Fig.26As shown, the first base station may determine the configuration parameters associated with the service based on the QoE of the service. The first base station may transmit a packet associated with the service together with the wireless device. The configuration parameters determined based on the QoE of the service may be associated with a first area indicated by the area information of the measurement report associated with the QoE of the service. The configuration parameters determined based on the QoE of the service may be used to provide the service in the first area indicated by the area information of the measurement report associated with the QoE of the service. The configuration parameters determined based on the QoE of the service may be associated with the time indicated by the time information of the measurement report associated with the QoE. The configuration parameters determined based on the QoE of the service may be used to provide the service at the time indicated by the time information of the measurement report associated with the QoE (e.g., afternoon, morning, between 9 am and 12 noon, between 1 pm and 6 pm, overnight, between 10 pm and 6 am, etc.). In an example, the first base station may send the configuration parameters associated with the service to one or more wireless devices (e.g., via one or more RRC messages). The first base station may transmit a second packet associated with the service together with the one or more wireless devices based on the configuration parameters associated with the service.

[0292] In one example, if Fig.24 and / or Fig.28As shown, the second base station may receive a message containing a measurement report from the first base station, the measurement report containing the QoE of the service. The second base station may transmit a packet associated with the service together with the wireless device. The second base station may receive a message containing a measurement report via an interface between the first base station and the second base station (e.g., a direct interface: Xn interface, X2 interface, etc.; and / or an indirect interface including at least one of the following: NG interface, N2 interface, S1 interface, AMF, MME, SMF, etc.), the measurement report containing the QoE of the service, regional information, time information, etc. The second base station may determine the configuration parameters associated with the service based on the QoE of the service. The configuration parameters determined based on the QoE of the service (e.g., by the second base station) may be associated with the first area indicated by the regional information of the measurement report associated with the QoE of the service. The configuration parameters determined based on the QoE of the service (e.g., by the second base station) may be used to provide the service in the first area indicated by the regional information of the measurement report associated with the QoE of the service. The configuration parameters determined based on the QoE of the service (e.g., by the second base station) may be associated with the time indicated by the time information of the measurement report associated with the QoE. Configuration parameters determined based on the QoE of the service (e.g., by the second base station) may be used to provide the service at a time indicated by time information of a measurement report associated with the QoE (e.g., afternoon, morning, between 9 a.m. and 12 noon, between 1 p.m. and 6 p.m., overnight, between 10 p.m. and 6 a.m., etc.). The second base station may send the configuration parameters associated with the service to one or more wireless devices (e.g., via one or more RRC messages). The second base station may transmit a second packet associated with the service with the one or more wireless devices based on the configuration parameters associated with the service.

[0293] In one example, if Fig.23 and / or Fig. 27As shown, sending an information response message by the wireless device to the first base station may include sending a measurement report to the central unit of the first base station. In one example, the distributed unit of the first base station may receive a message containing a measurement report from the central unit of the first base station, and the measurement report includes the QoE of the service. The distributed unit of the first base station may transmit a packet associated with the service together with the wireless device. In one example, the distributed unit of the first base station may receive a message containing a measurement report from the central unit of the first base station via an interface (e.g., an F1 interface) between the central unit of the first base station and the distributed unit of the first base station, and the measurement report includes the QoE of the service. The distributed unit of the first base station may determine a configuration parameter associated with the service based on the QoE of the service. The configuration parameter determined based on the QoE of the service (e.g., by the distributed unit of the first base station) may be associated with a first area indicated by the area information of the measurement report associated with the QoE of the service. The configuration parameter determined based on the QoE of the service (e.g., by the distributed unit of the first base station) may be used to provide the service in the first area indicated by the area information of the measurement report associated with the QoE of the service. The configuration parameters determined based on the QoE of the service (e.g., by the distributed unit of the first base station) may be associated with a time indicated by the time information of the measurement report associated with the QoE. The configuration parameters determined based on the QoE of the service (e.g., by the distributed unit of the first base station) may be used to provide the service at a time indicated by the time information of the measurement report associated with the QoE (e.g., afternoon, morning, between 9 a.m. and 12 noon, between 1 p.m. and 6 p.m., overnight, between 10 p.m. and 6 a.m., etc.). The distributed unit of the first base station may send the configuration parameters associated with the service to the central unit of the first base station. The central unit of the first base station may send the configuration parameters received from the distributed unit of the first base station to one or more wireless devices (e.g., via one or more RRC messages). The distributed unit of the first base station may transmit a second packet associated with the service together with the one or more wireless devices based on the configuration parameters associated with the service.

[0294] In one example, the first base station may send a measurement report containing the QoE of the service to a mobility management function (e.g., AMF, MME, etc.). The mobility management function may send the measurement report to an operation, administration, and maintenance (OAM) and / or QoE server. In one example, the first base station may send a measurement report containing the QoE of the service to the OAM and / or QoE server. The OAM and / or QoE server may adjust one or more service configuration parameters of the service based on the measurement report. The OAM and / or QoE server may send the adjusted service configuration parameters to an application server providing the service.

[0295] In one example, if Fig. 22 and / or Fig.29As shown, the wireless device may transmit a packet associated with the service in an RRC idle state or an RRC inactive state. The wireless device may determine the quality of experience (QoE) of the service based on the transmitted packet. The wireless device may send a measurement report to the first base station (e.g., when the wireless device is in an RRC connected state). The measurement report may include at least one of the following: the QoE of the service and regional information associated with the QoE of the service.

[0296] In an example, transmitting a packet associated with the service may include transmitting the packet at a first area. The area indication may indicate the first area. The area information may include at least one of: information about a location of the wireless device; an identifier of a cell; an identifier of a tracking area; an identifier of a registration area; an identifier of a multicast / broadcast single frequency network (MBSFN) area; information about a carrier frequency (e.g., an ARFCN of a carrier frequency associated with the service), etc.

[0297] In one example, if Fig. 22 As shown, the wireless device may transmit a packet associated with a service in an RRC idle state or an RRC inactive state. The wireless device may determine the quality of experience (QoE) of the service based on the transmitted packet. The wireless device may send a measurement report to the first base station (e.g., when the wireless device is in an RRC connected state). The measurement report may include at least one of the following: the QoE of the service and time information associated with the QoE of the service. In an example, the time information may include at least one of the following: the time when the QoE of the service is measured (e.g., an absolute time based on a time zone, a time elapsed since the QoE was measured, etc.); the duration of measuring the QoE of the service; the time of using the service (e.g., an absolute time based on a time zone, a time elapsed since the service was used, etc.); the duration of using the service, etc.

[0298] In one example, if Fig.26 As shown, the wireless device may transmit a packet associated with the service. The wireless device may determine a quality of experience (QoE) of the service based on the transmitted packet. The wireless device may send a radio resource control (RRC) completion message to the first base station confirming that the configuration of the RRC connection is complete. The RRC completion message may include a field indicating that a measurement report associated with the service is available. The wireless device may receive an information request message indicating the measurement report from the first base station. In response to receiving the information request message, the wireless device may send an information response message including a measurement report, the measurement report including the QoE of the service.

[0299] In one example, the service may include a service type, wherein the service type includes at least one of the following: streaming media (e.g., DASH streaming media); multimedia telephony service (MTSI) for Internet Protocol (IP) multimedia subsystem (IMS); virtual reality (VR); extended reality (XR), etc. In one example, the service may include multimedia broadcast service (MBS) and / or multimedia broadcast multicast service (MBMS). In one example, the service may include a network slice, wherein the network slice includes at least one of the following: eMBB (e.g., a slice suitable for handling 5G enhanced mobile broadband); URLLC (e.g., a slice suitable for handling ultra-reliable low latency communication (URLLC)); MIoT (e.g., a slice suitable for handling massive IoT); V2X (e.g., a slice suitable for handling V2X services); HMTC (e.g., a slice suitable for handling high-performance machine type communications), etc.

[0300] In one example, the measurement report may include area information associated with the QoE of the service. The area information may include at least one of the following: information about the location of the wireless device; an identifier of a cell; an identifier of a tracking area; an identifier of a registration area; an identifier of a multicast / broadcast single frequency network (MBSFN) area; information about a carrier frequency (e.g., an ARFCN of a carrier frequency associated with the service), etc.

[0301] In an example, the measurement report may include time information associated with the QoE of the service. The time information may include at least one of the following: the time when the QoE of the service is measured (e.g., absolute time based on the time zone, time elapsed since the QoE was measured, etc.); the duration of measuring the QoE of the service; the time when the service is used (e.g., absolute time based on the time zone, time elapsed since the service is used, etc.); the duration of using the service, etc.

[0302] In one instance, the measurement report may include at least one of the following: a field indicating a reference signal received power (RSRP) of at least one cell / carrier or at least one reference signal associated with transmitting packets associated with the service; a field indicating a reference signal received quality (RSRQ) of at least one cell / carrier or at least one reference signal associated with transmitting packets associated with the service; a field indicating a block error rate (BLER) of data and / or signaling (e.g., for each channel used for the service); a field indicating a block error rate (BER) of data and / or signaling (e.g., for each channel used for the service), etc.

[0303] In one example, the RRC Complete message may include a field indicating that QoE measurements are available. In one example, the Information Request message may include a field indicating QoE measurements.

[0304] In one example, the RRC completion message may include at least one of the following: an RRC recovery completion message, an RRC setup completion message, an RRC re-establishment completion message, and the like.

[0305] In one instance, the QoE of a service may include at least one of the following: buffer level status (e.g., the buffer level of the application layer associated with the service); throughput (e.g., average throughput); playout delay; playlist; packet loss rate; frame rate; jitter duration; synchronization loss duration; round-trip time (RTT) (e.g., signal transmission delay time from a wireless device to a device providing the service and signal transmission delay time to a device providing the service to the wireless device); codec bit rate; call setup time; viewport switching delay, etc.

[0306] In one example, the QoE of a service may include average throughput, playout latency, buffer level status, and / or a playback period list (playlist) of a streaming service and / or a VR service (e.g., a service). In one example, the QoE of a service may include continuous loss of real-time transport protocol packets, frame rate, jitter duration, synchronization loss duration, round trip time (RTT), average codec bit rate, and / or call setup time of an MTSI service (e.g., a service). In one example, the QoE of a service may include a viewport switching latency of comparable quality for a VR service (e.g., a service) and / or a list of viewports rendered during media presentation.

[0307] In one example, if Fig.26 As shown, transmitting a packet associated with the service may include transmitting the packet when the wireless device is in an RRC idle state or an RRC inactive state.

[0308] In one example, the wireless device may determine that the connection fails (e.g., radio link failure, RLF, handover failure, HOF, etc.). The wireless device may perform an RRC reestablishment procedure with the first base station. The RRC reestablishment procedure may include: sending an RRC reestablishment request message to the first base station; in response to sending the RRC reestablishment request message, receiving an RRC reestablishment message from the first base station; in response to receiving an RRC reestablishment message confirming that configuration of the RRC connection is complete, sending an RRC completion message including an RRC reestablishment completion message to the first base station, etc.

[0309] In one example, the wireless device may select a cell of the first base station. The wireless device may perform a random access procedure via the cell. The wireless device may send an RRC request message to the first base station requesting an RRC connection. In response to sending the RRC request message, the wireless device may receive an RRC response message from the first base station. Sending the RRC completion message may be based on receiving the RRC response message.

[0310] In an example, the wireless device may receive at least one configuration message including measurement configuration parameters. The measurement configuration parameters may include area information, the area information including at least one of the following: at least one identifier of at least one cell; at least one identifier of at least one tracking area; at least one identifier of at least one registration area; at least one identifier of at least one multicast / broadcast single frequency network (MBSFN) area; information of at least one carrier frequency (e.g., ARFCN of a carrier frequency associated with a service), etc. The measurement configuration parameters may include time information, the time information including at least one of the following: at least one time for measuring the QoE of the service (e.g., an absolute time based on a time zone); at least one duration for measuring the QoE of the service; at least one time for using the service; at least one duration for using the service, etc.

[0311] In one example, if Fig. 22 and / or Fig.26 As shown, the first base station may determine a configuration parameter associated with the service based on the QoE of the service. The first base station may transmit a packet associated with the service together with the wireless device. The configuration parameter determined based on the QoE of the service may be associated with a first area indicated by area information associated with the QoE of the service. The configuration parameter determined based on the QoE of the service may be used to provide the service in the first area indicated by the area information associated with the QoE of the service. In an example, the first base station may send the configuration parameter associated with the service to one or more wireless devices. The first base station may transmit a second packet associated with the service together with the one or more wireless devices based on the configuration parameter associated with the service.

[0312] In one example, if Fig.23 and / or Fig. 27As shown, sending an information response message to the first base station may include sending a measurement report to the central unit of the first base station. In an example, the distributed unit of the first base station may receive a message including the QoE of the service from the central unit of the first base station. The distributed unit of the first base station may transmit a packet associated with the service together with the wireless device. The distributed unit of the first base station may determine a configuration parameter associated with the service based on the QoE of the service. The configuration parameter of the service determined based on the QoE of the service may be associated with a first area indicated by the area information associated with the QoE of the service. The configuration parameter of the service determined based on the QoE of the service may be used to provide the service in the first area indicated by the area information associated with the QoE of the service. The distributed unit of the first base station may send the configuration parameter associated with the service to the central unit of the first base station. The central unit of the first base station may send the configuration parameter received from the distributed unit of the first base station to one or more wireless devices. The distributed unit of the first base station may transmit a second packet associated with the service together with the one or more wireless devices based on the configuration parameter associated with the service.

[0313] In one example, if Fig.24 and / or Fig.28 As shown, the second base station may receive a message including the QoE of the service from the first base station. The second base station may transmit a packet associated with the service together with the wireless device. The second base station may determine a configuration parameter associated with the service based on the QoE of the service. The second base station may send the configuration parameter associated with the service to one or more wireless devices. The second base station may transmit a second packet associated with the service together with the one or more wireless devices based on the configuration parameter associated with the service.

[0314] In one example, the first base station may send a measurement report including the QoE of the service to a mobility management function (eg, AMF, MME, etc.) In one example, the first base station may send a measurement report including the QoE of the service to operations, administration, and maintenance (OAM).

[0315] In one example, if Fig.30 As shown, the first base station may transmit a packet associated with a service together with a wireless device in an RRC idle state or an RRC inactive state. The first base station may receive a measurement report containing a quality of experience (QoE) of the service from the wireless device (e.g., directly and / or indirectly via another base station). When the wireless device is in an RRC idle state or an RRC inactive state, the wireless device may measure the QoE of the service. The measurement report may include at least one of the following: area information associated with the QoE of the service; time information associated with the QoE of the service, etc.

Claims

1. A method comprising: selecting, by the wireless device, a cell of the first base station; performing a random access procedure via the cell; Sending an RRC request message requesting a radio resource control RRC connection to the first base station; In response to sending the RRC request message, receiving an RRC response message from the first base station; transmitting, by the wireless device in an RRC idle state or an RRC inactive state, a packet associated with a service; determining a quality of experience (QoE) of the service based on the transmitting the packet; sending an RRC completion message to the first base station confirming that configuration of the RRC connection is complete, wherein the RRC completion message includes a field indicating that a measurement report associated with the service is available, wherein the sending of the RRC completion message is performed based on the receiving of the RRC response message; receiving, from the first base station, an information request message indicating the measurement report; In response to receiving the information request message, sending an information response message including the measurement report, the measurement report including the QoE of the service; determining, by the wireless device, that the connection has failed; and Execute an RRC re-establishment procedure with the first base station, wherein the RRC re-establishment procedure comprises: Sending an RRC reestablishment request message to the first base station; In response to sending the RRC re-establishment request message, receiving an RRC re-establishment message from the first base station; and in response to receiving the RRC re-establishment message, sending the RRC completion message including an RRC re-establishment completion message to the first base station.

2. The method according to claim 1, in: The RRC Complete message includes a field indicating that QoE measurement is available; or The information request message includes a field indicating the QoE measurement.

3. The method according to claim 1 or claim 2, further comprising: determining, by the first base station and based on the QoE of the service, configuration parameters associated with the service, wherein the first base station transmits the packets associated with the service with the wireless device; sending, by the first base station, the configuration parameters associated with the service to one or more wireless devices; as well as A second packet associated with the service is transmitted by the first base station together with the one or more wireless devices based on the configuration parameters associated with the service. 4 . The method according to claim 1 , wherein the connection failure comprises at least one of a radio link failure (RLF) or a handover failure (HOF).

5. A method comprising: transmitting a packet associated with the service by a wireless device in a radio resource control (RRC) idle state or an RRC inactive state; determining a quality of experience (QoE) of the service based on the transmitting the packet; sending an RRC complete message to the first base station confirming that configuration of the RRC connection is complete, wherein the RRC complete message includes a field indicating that a measurement report associated with the service is available; receiving, from the first base station, an information request message indicating the measurement report; In response to receiving the information request message, sending an information response message including the measurement report, the measurement report including the QoE of the service; determining, by the wireless device, that the connection is failed; Execute an RRC re-establishment procedure with the first base station, wherein the RRC re-establishment procedure comprises: Sending an RRC reestablishment request message to the first base station; In response to sending the RRC re-establishment request message, receiving an RRC re-establishment message from the first base station; and in response to receiving the RRC re-establishment message, sending the RRC completion message including an RRC re-establishment completion message to the first base station.

6. The method according to claim 5, in: The RRC Complete message includes a field indicating that QoE measurement is available; or The information request message includes a field indicating the QoE measurement.

7. The method according to claim 5 or claim 6, further comprising: determining, by the first base station and based on the QoE of the service, configuration parameters associated with the service, wherein the first base station transmits the packets associated with the service with the wireless device; sending, by the first base station, the configuration parameters associated with the service to one or more wireless devices; as well as A second packet associated with the service is transmitted by the first base station together with the one or more wireless devices based on the configuration parameters associated with the service.

8. The method according to any one of claims 5 to 7, wherein the sending the information response message to the first base station comprises sending the measurement report to a central unit of the first base station.

9. The method according to any one of claims 5 to 8, further comprising sending, by the first base station, the measurement report comprising the QoE of the service to a mobility management function.

10. The method according to any one of claims 5 to 9, further comprising sending, by the first base station, the measurement report comprising the QoE of the service to an Operation, Administration and Maintenance (OAM).

11. A method comprising: transmitting a packet associated with the service by a wireless device in a radio resource control (RRC) idle state or an RRC inactive state; sending a radio resource control (RRC) message to the first base station indicating that a measurement report associated with the service is available; receiving, from the first base station, an information request message indicating the measurement report; as well as An information response message including the measurement report is sent, where the measurement report includes the quality of experience (QoE) of the service.

12. The method of claim 11, wherein the measurement report includes area information associated with the QoE of the service, the area information including at least one of the following: information on the location of the wireless device; an identifier of the cell; an identifier of the tracking area; The identifier of the registration zone; Identifier of a Multicast / Broadcast Single Frequency Network MBSFN area; Carrier frequency information; or The Absolute Radio Frequency Channel Number (ARFCN) of the carrier frequency associated with the service.

13. The method of claim 11 or claim 12, wherein the measurement report includes time information associated with the QoE of the service, the time information including at least one of the following: measuring the time of the QoE of the service; measuring a duration of the QoE of the service; the time of use of the said service; or The duration of use of the said service.

14. The method according to any one of claims 11 to 13, wherein the measurement report comprises at least one of the following: a field indicating a reference signal received power RSRP of at least one cell / carrier or at least one reference signal associated with transmitting said packet associated with said service; a field indicating a reference signal received quality RSRQ of at least one cell / carrier or at least one reference signal associated with transmitting said packet associated with said service; A field indicating the block error rate of the data; or A field indicating the signaled block error rate.

15. The method according to any one of claims 11 to 14, in: The RRC message includes a field indicating that QoE measurement is available; or The information request message includes a field indicating the QoE measurement.

16. The method of any one of claims 11 to 15, wherein the transmitting the packet associated with the service comprises transmitting the packet when the wireless device is in an RRC idle state or an RRC inactive state.

17. The method according to any one of claims 11 to 16, further comprising: determining, by the wireless device, that the connection has failed; and Execute an RRC re-establishment procedure with the first base station, wherein the RRC re-establishment procedure comprises: Sending an RRC reestablishment request message to the first base station; In response to sending the RRC reestablishment request message, receiving an RRC reestablishment message from the first base station; and In response to receiving the RRC re-establishment message, sending the RRC message including an RRC re-establishment completion message to the first base station.

18. The method according to any one of claims 11 to 17, further comprising receiving, by the wireless device, at least one configuration message, the at least one configuration message comprising a measurement configuration parameter indicating at least one of: Area information, the area information including at least one of the following: an identifier of the cell; an identifier of the tracking area; The identifier of the registration zone; The identifier of the multicast / broadcast single frequency network area; or the Absolute Radio Frequency Channel Number (ARFCN) of the carrier frequency associated with the service; and Time information, the time information comprising at least one of the following: measuring the time of the QoE of the service; measuring a duration of the QoE of the service; the time of use of the said service; or The duration of use of the said service.

19. The method according to any one of claims 11 to 18, wherein the service comprises at least one of the following: A service type, wherein the service type includes at least one of the following: Streaming; Multimedia Telephony Service MTSI for Internet Protocol IP Multimedia Subsystem IMS; or Virtual Reality (VR); or Extended Reality XR; multimedia broadcasting services; or A network slice, wherein the network slice comprises at least one of the following: Suitable for processing slices of 5G enhanced mobile broadband (EMBB); Suitable for processing slices of ultra-reliable low-latency communications (URLLC); Slices suitable for processing large-scale IoT (IoT) and MIoT; Slices suitable for handling vehicle to everything (V2X) services; or Slices suitable for handling high-performance machine type communications (HMTC).

20. The method according to any one of claims 11 to 19, wherein the RRC message comprises at least one of the following: RRC recovery complete message; RRC Setup Complete message; or RRC re-establishment complete message.

21. The method according to any one of claims 11 to 20, wherein the QoE of the service comprises at least one of the following: Buffer level status; Throughput; broadcast delay; Playlists; Packet loss rate; Frame rate; Jitter duration; duration of synchronization loss; Round Trip Time (RTT); Codec bitrate; Call to set the time; or Viewport switching delay.

22. The method according to any one of claims 11 to 21, wherein the QoE of the service comprises at least one of the following: Average throughput, playout latency, buffer level status and / or playback time slot lists (playlists) for streaming and VR services; The continuous loss of real-time transport protocol packets, frame rate, jitter duration, synchronization loss duration, round trip time, average codec bit rate and / or call setup time for the MTSI service; or Comparable quality viewport switching latency for VR services, list of viewports rendered during media presentation.

23. The method according to any one of claims 11 to 22, further comprising: selecting, by the wireless device, a cell of the first base station; performing a random access procedure via the cell; Sending an RRC request message to the first base station requesting the RRC connection; and In response to sending the RRC request message, receiving an RRC response message from the first base station, wherein the sending of the RRC message is performed based on the receiving of the RRC response message.

24. The method according to any one of claims 11 to 23, further comprising: determining, by the first base station and based on the QoE of the service, configuration parameters associated with the service, wherein the first base station transmits the packets associated with the service with the wireless device; sending, by the first base station, the configuration parameters associated with the service to one or more wireless devices; as well as A second packet associated with the service is transmitted by the first base station together with the one or more wireless devices based on the configuration parameters associated with the service.

25. The method according to any one of claims 11 to 24, wherein the sending the information response message to the first base station comprises sending the measurement report to a central unit of the first base station.

26. The method of claim 25, further comprising: receiving, by a distributed unit of the first base station from the central unit of the first base station, a message including the QoE of the service, wherein the distributed unit of the first base station transmits the packet associated with the service with the wireless device; determining, by the distributed unit of the first base station and based on the QoE of the service, configuration parameters associated with the service; sending, by the distributed unit of the first base station, the configuration parameters associated with the service to the central unit of the first base station; as well as A second packet associated with the service is transmitted by the distributed unit of the first base station together with one or more wireless devices based on the configuration parameters associated with the service.

27. The method according to any one of claims 11 to 26, further comprising: receiving, by a second base station from the first base station, a message including the QoE of the service, wherein the second base station transmits the packet associated with the service with the wireless device; determining, by the second base station and based on the QoE of the service, configuration parameters associated with the service; sending, by the second base station, the configuration parameters associated with the service to one or more wireless devices; as well as A second packet associated with the service is transmitted by the second base station together with the one or more wireless devices based on the configuration parameters associated with the service.

28. The method of any one of claims 11 to 27, further comprising sending, by the first base station to a mobility management function, the measurement report comprising the QoE of the service.

29. The method according to any one of claims 11 to 28, further comprising sending, by the first base station, the measurement report comprising the QoE of the service to Operation, Administration and Maintenance (OAM).

30. The method of any one of claims 11 to 29, further comprising determining a QoE of the service based on the transmitting the packet.

31. The method according to any one of claims 11 to 30, wherein the RRC message indicates that the RRC procedure is complete.

32. The method according to any one of claims 11 to 31, wherein the RRC message confirms completion of configuration of the RRC connection.

33. The method according to any one of claims 11 to 32, wherein the RRC message contains a field indicating that the measurement report associated with the service is available.

34. The method according to any one of claims 11 to 33, wherein said sending said information response message is performed in response to receiving said information request message.

35. A method comprising: transmitting a packet associated with the service by a wireless device in a radio resource control (RRC) idle state or an RRC inactive state; determining a quality of experience (QoE) of the service based on the transmitting the packet; Sending a measurement report to the first base station, where the measurement report includes: the QoE of the service; as well as Regional information associated with the QoE of the service.

36. The method of claim 35, wherein the transmitting the packet associated with the service comprises transmitting the packet at a first region. The method of claim 36 , wherein the region indication indicates the first region.

38. The method according to any one of claims 35 to 37, wherein the region information comprises at least one of the following: information on the location of the wireless device; an identifier of the cell; an identifier of the tracking area; The identifier of the registration zone; An identifier of a Multicast / Broadcast Single Frequency Network (MBSFN) area; or Carrier frequency information.

39. A method comprising: transmitting a packet associated with the service by a wireless device in a radio resource control (RRC) idle state or an RRC inactive state; determining a quality of experience (OoE) of the service based on transmitting the packet; Sending a measurement report to the first base station, where the measurement report includes: the QoE of the service; and Temporal information associated with the QoE of the service.

40. The method of claim 39, wherein the time information comprises at least one of the following: measuring the time of the QoE of the service; measuring a duration of the QoE of the service; the time of use of the said service; or The duration of use of the said service.

41. A method comprising: transmitting, by the first base station, a packet associated with the service together with the wireless device in a radio resource control RRC idle state or an RRC inactive state; and Receive a measurement report from the wireless device, the measurement report comprising: a quality of experience (OoE) of the service, wherein when the wireless device is in the RRC idle state or the RRC inactive state, the wireless device measures the QoE of the service; and regional information associated with said QoE of said service; or Temporal information associated with the QoE of the service.

42. A method comprising: receiving a packet associated with the service from a wireless device in a radio resource control (RRC) idle state or an RRC inactive state; receiving, by the first base station, from the wireless device a radio resource control (RRC) message indicating that a measurement report associated with the service is available; sending, from the first base station to the wireless device, an information request message indicating the measurement report; as well as An information response message including the measurement report is received by the first base station, where the measurement report includes the quality of experience (QoE) of the service.

43. The method of claim 42, wherein the measurement report includes regional information associated with the QoE of the service, the regional information including at least one of: information on the location of the wireless device; an identifier of the cell; an identifier of the tracking area; The identifier of the registration zone; Identifier of a Multicast / Broadcast Single Frequency Network MBSFN area; Carrier frequency information; or The Absolute Radio Frequency Channel Number (ARFCN) of the carrier frequency associated with the service.

44. The method of claim 42 or claim 43, wherein the measurement report includes time information associated with the QoE of the service, the time information including at least one of: measuring the time of the QoE of the service; measuring a duration of the QoE of the service; the time of use of the said service; or The duration of use of the said service.

45. The method according to any one of claims 42 to 44, wherein the measurement report comprises at least one of the following: a field indicating a reference signal received power RSRP of at least one cell / carrier or at least one reference signal associated with transmitting said packet associated with said service; a field indicating a reference signal received quality RSRQ of at least one cell / carrier or at least one reference signal associated with transmitting said packet associated with said service; A field indicating the block error rate of the data; or A field indicating the signaled block error rate.

46. ​​The method according to any one of claims 42 to 45, in: The RRC message includes a field indicating that QoE measurement is available; or The information request message includes a field indicating the QoE measurement.

47. The method of any one of claims 42 to 47, further comprising sending at least one configuration message to the wireless device, the at least one configuration message comprising a measurement configuration parameter indicating at least one of: Area information, the area information including at least one of the following: an identifier of the cell; an identifier of the tracking area; The identifier of the registration zone; The identifier of the multicast / broadcast single frequency network area; or the Absolute Radio Frequency Channel Number (ARFCN) of the carrier frequency associated with the service; and Time information, the time information comprising at least one of the following: measuring the time of the QoE of the service; measuring a duration of the QoE of the service; the time of use of the said service; or The duration of use of the said service.

48. The method of any one of claims 42 to 47, wherein the service comprises at least one of the following: A service type, wherein the service type includes at least one of the following: Streaming; Multimedia Telephony Service MTSI for Internet Protocol IP Multimedia Subsystem IMS; or Virtual Reality (VR); or Extended Reality XR; multimedia broadcasting services; or A network slice, wherein the network slice comprises at least one of the following: Suitable for processing slices of 5G enhanced mobile broadband (EMBB); Suitable for processing slices of Ultra-Reliable Low Latency Communications (URLLC); Slices suitable for processing large-scale IoT (IoT) and MIoT; Slices suitable for handling vehicle to everything (V2X) services; or Slices suitable for handling high-performance machine type communications (HMTC).

49. The method according to any one of claims 42 to 48, wherein the RRC message comprises at least one of the following: RRC recovery complete message; RRC Setup Complete message; or RRC re-establishment complete message.

50. The method of any one of claims 42 to 49, wherein the QoE of the service comprises at least one of: Buffer level status; Throughput; broadcast delay; Playlists; Packet loss rate; Frame rate; Jitter duration; duration of synchronization loss; Round Trip Time (RTT); Codec bitrate; Call to set the time; or Viewport switching delay.

51. The method of any one of claims 42 to 50, wherein the QoE of the service comprises at least one of the following: Average throughput, playout latency, buffer level status and / or playback time slot lists (playlists) for streaming and VR services; The continuous loss of real-time transport protocol packets, frame rate, jitter duration, synchronization loss duration, round trip time, average codec bit rate and / or call setup time for the MTSI service; or Comparable quality viewport switching latency for VR services, list of viewports rendered during media presentation.

52. The method of any one of claims 42 to 51, wherein the RRC message indicates that the RRC procedure is complete.

53. A method according to any one of claims 42 to 52, wherein the RRC message confirms completion of configuration of the RRC connection.

54. The method of any one of claims 42 to 53, wherein the RRC message includes a field indicating that the measurement report associated with the service is available.

55. A method according to any one of claims 42 to 54, wherein the information response message is in response to receiving the information request message.

56. An apparatus comprising: one or more processors; and A memory storing instructions which, when executed by the one or more processors, cause the apparatus to perform a method according to any one of claims 1 to 55.

57. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors of a device, cause the device to perform the method of any one of claims 1 to 55.

58. A computer readable medium encoding instructions for performing the method of any one of claims 1 to 55.

59. An apparatus comprising: means for performing the method according to any one of claims 1 to 55.

Images