Handling outdated delayed reports

Abstract

A wireless device receives a configuration parameter indicating a threshold for a delay status report (DSR) of a logical channel group (LCG) associated with one or more data units. The wireless device triggers the DSR. The wireless device cancels the triggered DSR in response to discarding the one or more data units.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Application 63 / 457,185, filed April 5, 2023, which is incorporated herein by reference in its entirety. Attached Figure Description

[0002] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

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

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

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

[0006] Figure 4A It shows the flow through Figure 2A Example downlink data stream of the NR user plane protocol stack.

[0007] Figure 4B An example format of the MAC subheader in a Media Access Control (MAC) PDU is shown.

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

[0009] Figure 6 This is an example diagram illustrating the radio resource control (RRC) state transition of a user equipment (UE).

[0010] Figure 7 An example configuration of an NR frame in which Orthogonal Frequency Division Multiplexing (OFDM) symbols are grouped is shown.

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

[0012] Figure 9 An example of bandwidth adaptation using three configured bandwidth portions (BWP) of an NR carrier is shown.

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

[0014] Figure 10B An example of how aggregated cells can be configured as one or more groups of Physical Uplink Control Channels (PUCCHs) is shown.

[0015] Figure 11A An example of the structure and location of the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block is shown.

[0016] Figure 11B An example of a Channel State Information-Reference Signal (CSI-RS) mapped in the time and frequency domains is shown.

[0017] Figure 12A and Figure 12B Examples of three downlink and uplink beam management procedures are shown respectively.

[0018] Figure 13A , Figure 13B and Figure 13C Four-step contention-based random access procedures, two-step contention-free random access procedures, and another two-step random access procedure are shown respectively.

[0019] Figure 14A An example of the configuration of the control resource set (CORESET) for the bandwidth portion is shown.

[0020] Figure 14B An example of the control channel element to resource element group (CCE to REG) mapping for downlink control information (DCI) transmission and PDCCH processing on CORESET is shown.

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

[0022] Figure 16A , Figure 16B , Figure 16C and Figure 16D An example structure for uplink and downlink transmission is shown.

[0023] Figure 17 An example of an alternative for mapping Protocol (or Packet) Data Unit (PDU) sets / Quality of Service (QoS) streams / Data Radio Bearer (DRB) is shown.

[0024] Figure 18 This shows an example of an issue where triggered delay reports become outdated / invalid / unnecessary.

[0025] Figure 19 An example of a delayed report that was canceled is shown.

[0026] Figure 20An example of a delay report including time information is shown.

[0027] Figure 21 An example of a (validity) timer used for delay reporting is shown.

[0028] Figure 22 An example of no retransmission for delayed reporting is shown.

[0029] Figure 23 An example is shown where a scheduling request is triggered in response to a delayed report.

[0030] Figure 24 An example implementation of a delayed reporting is shown.

[0031] Figure 25 An example implementation of a delayed reporting is shown.

[0032] Figure 26 An example implementation of a delayed reporting is shown.

[0033] Figure 27 An example implementation of a delayed reporting is shown.

[0034] Figure 28 An example implementation of a delayed reporting is shown.

[0035] Figure 29 An example implementation of a delayed reporting is shown. Detailed Implementation

[0036] In this disclosure, various embodiments are presented as examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail can be made therein without departing from the scope of the invention. Indeed, alternative embodiments will be apparent to those skilled in the art upon reading the specification. Embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, any actions listed in any flowchart can be reordered or used only optionally in certain embodiments.

[0037] The implementation scheme can be configured to operate as needed. For example, in wireless devices, base stations, radio environments, networks, combinations thereof, etc., the disclosed mechanisms can be executed when certain criteria are met. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, combinations thereof, etc. Various example implementation schemes can be applied when one or more criteria are met. Therefore, example implementation schemes that selectively implement the disclosed protocols can be implemented.

[0038] A base station can communicate with a mixture of wireless devices. The wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have certain specific capabilities, depending on the type and / or capability of the wireless device. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure can refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure can mean multiple wireless devices having a given capability and in a given sector of a base station using a given LTE or 5G version. Multiple wireless devices in this disclosure can refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method; for example, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0039] In this disclosure, “a (a)” and “an (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 this disclosure, the term “may” is interpreted as “may, for example.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “consisting of” provides a complete enumeration of the one or more components of the element being described. As used herein, the term “based on” should be interpreted as “at least partially based on” rather than, for example, “based on only.” As used herein, the term “and / or” indicates any possible combination of the enumerated 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.

[0040] 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, 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 following the term “based on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “adopts / uses” (or equivalently “at least adopts / uses”) indicates that the phrase following the phrase “adopts / uses” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations.

[0041] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0042] In this disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include 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 implementation, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is present in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0043] Many of the proposed features are described as optional using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the group of optional features. This 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: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0044] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented as hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as software routines written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement modules using physical hardware incorporating 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 typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure connections between internal hardware modules with limited functionality on the programmable device. The aforementioned techniques are often used in combination to achieve the desired result of functional modules.

[0045] Figure 1A An example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 100 may, for example, be 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 a radio device 106.

[0046] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs) (such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs). As part of the interface functions, CN 102 can establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging functionality.

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

[0048] The term "wireless device" is used throughout this disclosure to mean and cover any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device can be a telephone, smartphone, tablet, computer, laptop computer, sensor, instrument, wearable device, Internet of Things (IoT) device, roadside unit (RSU) of a vehicle, relay node, automobile, and / or any combination thereof. The term "wireless device" also encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handheld device, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0049] 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: Node B (associated with UMTS and / or 3G standards); Evolved Node B (eNB, associated with E-UTRA and / or 4G standards); Remote Radio Header (RRH); Baseband Processing Unit coupled to one or more RRHs; Repeater Node or Relay Node for extending the coverage area of ​​the donor Node; Next Generation Evolved Node B (ng-eNB); First Generation Node B (gNB, associated with NR and / or 5G standards); 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).

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

[0051] Besides three-sector sites, other implementations of the base stations are also possible. For example, one or more base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units coupled to several remote radio heads (RRHs), and / or repeater or relay nodes for extending the coverage area of ​​the donor node. The baseband processing unit coupled to the RRH can be part of a centralized or cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. Repeater nodes can amplify and replay radio signals received from the donor node. Relay nodes can perform the same / similar functions as repeater nodes, but can decode radio signals received from the donor node to remove noise before amplifying and replaying the radio signals.

[0052] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna configurations and similar high-level transmission power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as areas overlapping with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas where macrocell coverage is weak. Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0054] Figure 1B Another example mobile communication network 150 in which embodiments of the present disclosure can be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown, 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). This can be compared with... Figure 1A These components are implemented and operated in the same or similar manner as the corresponding components described.

[0055] 5G-CN 152 provides UE 156 with interfaces to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of its interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functionality. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0056] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, in Figure 1BThese are shown as a single component, AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. Functions that UPF 158B can perform include: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the 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 authentication), 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 interconnecting with the one or more DNs, and / or a pivot point supporting multihomed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0057] The AMF 158A can perform functions such as: Non-Access Layer (NAS) signaling termination, NAS signaling security, Access Layer (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., paging retransmission control and execution), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the UE, and AS can refer to functions operating between the UE and the RAN.

[0058] 5G-CN 152 can be included for clarity. Figure 1B One or more additional network functions not shown in the diagram. 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 Open Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

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

[0060] like Figure 1B As shown, gNB 160 and / or ng-eNB 162 can connect to 5G-CN 152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces can be established using a direct physical connection and / or an indirect connection via an underlying transport network (such as an Internet Protocol (IP) transport network). gNB 160 and / or ng-eNB 162 can connect to UE 156 via the Uu interface. For example, as... Figure 1B As shown, the gNB 160A can connect to the UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface can be... Figure 1B The network elements in the system are used to exchange data and signaling messages, and can contain two planes: a user plane and a control plane. The user plane can handle data that is of interest to the user. The control plane can handle signaling messages that are of interest to the network elements.

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

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

[0063] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 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 The diagram shows only one AMF / UPF 158, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across those multiple AMF / UPF nodes.

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

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

[0066] Figure 2A The diagram illustrates a five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers and correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include Media Access Control (MAC) 212 and 222, Radio Link Control (RLC) 213 and 223, Packet Data Convergence Protocol (PDCP) 214 and 224, and Service Data Application Protocol (SDAP) 215 and 225. These four protocols together constitute Layer 2 of the OSI model, or the Data Link Layer.

[0067] Figure 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From Figure 2A and Figure 3 Starting from the top, SDAPs 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 the DN. The PDU session can have one or more QoS flows. The CN's UPF (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 latency, data rate, and / or error rate). SDAPs 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 QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can learn the mapping between QoS flows and data radio bearers through reflected mapping or control signaling received from gNB 220. For reflective mapping, the SDAP 225 at gNB 220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0068] PDCP 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from their intended source. PDCP 214 and 224 can perform retransmission of undelivered packets, reordering and repackaging of packets, and removal of duplicate packets received due to, for example, intra-gNB handover. PDCP 214 and 224 can perform packet duplication to increase the likelihood of packet reception and remove any duplicate packets at the receiver. Packet duplication can be suitable for services requiring high reliability.

[0069] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in dual connectivity scenarios. Dual connectivity is a technique 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). Split bearers are those that occur 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 / demapping split radio bearers between RLC channels belonging to a cell group.

[0070] RLCs 213 and 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222. RLCs 213 and 223 can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode the RLC is operating in, the RLC can perform one or more of the aforementioned functions. RLC configuration can be based on the logical channel, independent of the parameter set and / or Transmission Time Interval (TTI) duration. Figure 3 As shown, RLC 213 and 223 can provide RLC channels as services to PDCP 214 and 224, respectively.

[0071] MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing data units belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from PHYs 211 and 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority processing between UEs by means of dynamic scheduling. Scheduling can be performed for downlink and uplink in gNB 220 (at MAC 222). MACs 212 and 222 can be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority processing between logical channels of UE 210 by means of logical channel priority ordering, and / or padding. MACs 212 and 222 can support one or more parameter sets and / or transmission timing. In the example, the mapping constraints in logical channel priority ordering can control which set of parameters and / or transmission timing the logical channel can use. For example... Figure 3 As shown, MACs 212 and 222 can provide logical channels as services to RLCs 213 and 223.

[0072] PHYs 211 and 221 can perform transport-to-physical channel mapping and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHYs 211 and 221 can perform multi-antenna mapping. For example... Figure 3 As shown, PHYs 211 and 221 can provide one or more transport channels as services to MACs 212 and 222.

[0073] Figure 4A An example downlink data flow is shown that passes through the NR user plane protocol stack. Figure 4A The diagram shows three IP packets, each with a terabyte (TB), flowing through the NR user plane protocol stack to generate at the gNB 220. n , n+1 and m The downlink data stream. The uplink data stream flowing through the NR user plane protocol stack can be... Figure 4A The downlink data flow described in the text is similar.

[0074] Figure 4A The downlink data flow begins when SDAP 225 receives three IP packets from one or more QoS flows and maps those three packets to a radio bearer. Figure 4A In the middle, SDAP 225 will send IP packets n and n+1Mapped to the first wireless bearer 402, and the IP packet... m Mapped to the second wireless bearer 404. SDAP header (in Figure 4A Data units marked with "H" are added to IP packets. Data units originating from / going to a higher protocol layer are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to a lower protocol layer are called higher protocol layer Protocol Data Units (PDUs). Figure 4A As shown, the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225.

[0075] Figure 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). Figure 3 This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). Figure 4A Regarding IP packets m (As shown) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed across MAC PDUs, such as... Figure 4A As shown in the diagram. In LTE, the MAC sub-header 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 sub-header can be computed before the complete MAC PDU is assembled.

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

[0077] Figure 4B The diagram further illustrates a MAC control element (CE) inserted into the MAC PDU by a MAC (e.g., MAC 212 or MAC 222). For example, Figure 4B This shows two MAC CEs inserted into the MAC PDU. Downlink transmissions can be initiated at the beginning of the MAC PDU (e.g., ...). Figure 4B(As shown in the diagram) and a MAC CE is inserted at the end of the uplink transmission of the MAC PDU. MAC CEs 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 repeated detection, Channel State Information (CSI) reports, Sounding Reference Signal (SRS) transmissions, and activation / deactivation of previously configured components; Discontinuous Reception (DRX)-related MAC CEs; Timing Advancement MAC CEs; and random access-related MAC CEs. A MAC subheader with a format similar to that described with respect to the MAC SDU may precede the MAC CE, and the MAC CE may be identified by a reserved value in the LCID field indicating the type of control information contained in the MAC CE.

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

[0079] Figure 5A and Figure 5B The mappings between logical channels, transport channels, and physical channels are shown for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for 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: --Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level; --Broadcast Control Channel (BCCH), which carries system information messages in the form of Master Control Information Block (MIB) and several System Information Blocks (SIB), wherein the system information messages can be used by the UE to obtain information about how the cell is configured and how it operates within the cell; --Common Control Channel (CCCH), which is used to carry control messages and random access; --Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure the UE; and --Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0080] 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: --Paging Channel (PCH), which is used to carry paging messages originating from PCCH; --Broadcast channel (BCH), which is used to carry MIBs from the BCCH; --Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from BCCH; --Uplink Shared Channel (UL-SCH), used to carry uplink data and signaling messages; and --Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0081] The PHY can use physical channels to transfer information between processing levels of the PHY. A physical channel can be a set of associated time-frequency resources used to carry information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide this 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 the NR includes, for example: --Physical Broadcast Channel (PBCH), which is used to carry MIBs from the BCH; --Physical Downlink Shared Channel (PDSCH), which is used to carry downlink data and signaling messages from DL-SCH and paging messages from PCH; --Physical downlink control channel (PDCCH), which carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands; --The Physical Uplink Shared Channel (PUSCH) is used to carry uplink data and signaling messages from the UL-SCH, and in some cases carries uplink control information (UCI) as described below. --Physical Uplink Control Channel (PUCCH), which carries a UCI, the UCI including HARQ acknowledgment, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and --Physical Random Access Channel (PRACH), which is used for random access.

[0082] Similar to the physical control channel, the physical layer generates physical signals to support low-level physical layer operations. For example... Figure 5A and Figure 5B As shown, 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.

[0083] Figure 2B An example NR control plane protocol stack is shown. Figure 2B As shown, the NR control plane protocol stack can 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 has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

[0085] RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220, or more generally between UE 210 and RAN. RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220 via signaling messages known as RRC messages. RRC messages can be transmitted between UE 210 and RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC can multiplex control plane and user plane data into the same transport block (TB). RRC 216 and 226 can provide control plane functions such as: broadcasting system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of RRC connections 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 said reports; detection and recovery of radio link failures (RLFs); and / or NAS messaging. As part of establishing an RRC connection, RRC 216 and 226 can establish an RRC context, which may involve configuring parameters for communication between UE 210 and RAN.

[0086] Figure 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... Figure 1A The wireless device 106 depicted in the text Figure 2A and Figure 2B The UE 210 depicted herein is identical or similar to any other wireless device described in this disclosure. Figure 6 As shown, the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0087] 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 RAN 104 as depicted herein; Figure 1B One of gNB 160 or ng-eNB 162 described herein; Figure 2A and Figure 2BThe gNB 220 depicted in this disclosure; or any other base station described herein. 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 include 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., relating to 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 UE's mobility 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 the 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 a cell transfer to one of the neighboring base stations based on the reported measurements. The RRC state can be changed from RRC connection 602 to RRC idle 604 through connection release procedure 608, or to RRC inactive 606 through connection deactivation procedure 610.

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

[0089] In RRC inactivity 606, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactivity 606, the UE can be in a sleep state, and the UE's mobility can be managed by the UE via cell reselection. The RRC state can transition from RRC inactivity 606 to RRC connected 602 via connection resumption procedure 614, or to RRC idle 604 via connection release procedure 616, which can be the same as or similar to connection release procedure 608.

[0090] RRC states can be associated with mobility management mechanisms. 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 events via paging messages without having to broadcast paging messages across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 allow the network to track the UE at the cell group level, so that paging messages can be broadcast on the cells in the cell group where the UE currently resides, rather than across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 track the UE at the cell group level. These mobility management mechanisms can do this using groupings of different granularities. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

[0091] A tracking area can be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) can provide the UE with a list of TAIs associated with the UE's registration area. If the UE moves to a cell associated with a TAI that is not included in the list of TAIs associated with the UE's registration area via cell reselection, the UE can 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.

[0092] RAN areas can be used to track UEs at the RAN level. For a UE in an RRC inactive 606 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identifiers, a list of RAIs, or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in the RAN notification area assigned to that UE, the UE can perform a notification area update on the RAN to update the UE's RAN notification area.

[0093] The base station storing the RRC context for the UE, or the UE's last serving base station, 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 when the UE remains in the anchor base station's RAN notification area and / or during the period when the UE remains in RRC inactivity 606.

[0094] gNB, such as Figure 1BThe gNB 160 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 an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0095] In NR, physical signals and physical channels (about Figure 5A and Figure 5B The concepts discussed can be mapped to Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that uses... F Data is transmitted via orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM symbols or M-PSK symbols), and is divided into... F A parallel symbol stream. F The parallel symbol streams can be viewed as if they were in the frequency domain and used as input to blocks of Inverse Fast Fourier Transform (IFFT) symbols that transform them to the time domain. An IFFT block can take... F Source symbols (from) F (One source symbol is taken from each of the parallel symbol streams), and each source symbol is used to modulate the signal with... F Corresponding to each orthogonal subcarrier F The amplitude and phase of one of the sinusoidal basis functions. The output of the IFFT block can represent... F The sum of orthogonal subcarriers F Each time-domain sample. F Each time-domain sample can form a single OFDM symbol. After some processing (e.g., the addition of a cyclic prefix) and upconversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. F The parallel symbol streams can be mixed using an FFT block before being processed by an IFFT block. This operation produces OFDM symbols precoded with Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The OFDM symbols can be inversely processed at the receiver using an FFT block to recover the data mapped to the source symbols.

[0096] Figure 7An example configuration of NR frames in which OFDM symbols are grouped is shown. NR frames can be identified by a System Frame Number (SFN). SFNs can repeat at a period of 1024 frames. As shown, the duration of an NR frame can be 10 milliseconds (ms) and can contain 10 subframes with a duration of 1 ms. Subframes can be divided into time slots, which contain, for example, 14 OFDM symbols per time slot.

[0097] The duration of a time slot can depend on the set of parameters used for the OFDM symbols in that 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 mmWave range). The parameter set can be defined in terms of subcarrier spacing and cyclic prefix duration. For the parameter set in NR, the subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of two, and the cyclic prefix duration can be scaled down from a baseline cyclic prefix duration of 4.7 μs by powers of two. For example, NR defines parameter sets with the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

[0098] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter time slot durations and correspondingly more time slots per subframe. Figure 7 This illustrates the transmission structure of the time slot duration and per subframe time slot related to the parameter set (for ease of explanation). Figure 7 (A parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be separated from the time slot duration and begin at any OFDM symbol, continuing to transmit as many symbols as needed. These partial time slot transmissions can be referred to as micro-time slots or sub-time slot transmissions.

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

[0100] Figure 8 This illustrates a single set of parameters used across the entire bandwidth of an NR carrier. In other example configurations, multiple parameter sets can be supported on the same carrier.

[0101] NR can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth can be prohibitively expensive in terms of UE power consumption. In the example, to reduce power consumption and / or for other purposes, the UE can adjust the size of its receive bandwidth based on the amount of traffic it plans to receive. This is called bandwidth adaptation.

[0102] The NR defines a Bandwidth Component (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of consecutive Relay Buses (RBs) on a carrier. A UE can be configured (e.g., via the RRC layer) to have 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 can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0103] For unpaired spectrum, if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP, then the downlink BWP from the set of configured downlink BWPs can link with the uplink BWP from the set of configured uplink BWPs. For unpaired spectrum, the UE can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

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

[0105] For an uplink BWP in the set of configured uplink BWPs, the BS can configure one or more resource sets for the UE to transmit one or more PUCCHs. The UE can receive downlink reception (e.g., PDCCH or PDSCH) in the downlink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix duration) used for the downlink BWP. The UE can transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP based on the configured set of parameters (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0106] One or more BWP indicator fields may be provided in the downlink control information (DCI). The value of the BWP indicator field can indicate which BWP in the 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 can indicate the active uplink BWP for one or more uplink transmissions.

[0107] The base station can semi-statically configure a default downlink BWP for the UE within a 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 can be the initial active downlink BWP. The UE can determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0108] The base station can configure the BWP inactivity timer value for the UE using the PCell. The UE can start or restart the BWP inactivity timer at any appropriate time. For example, the UE can start or restart the BWP inactivity timer under 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 ( bWhen the UE detects a DCI (Distributed Indication Code) for unpaired spectrum operation, indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP, the UE can proceed as follows: If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can advance the BWP inactivity timer towards its expiration (e.g., by incrementing from zero to the BWP inactivity timer value, or decrementing from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE can switch from the active downlink BWP to the default downlink BWP.

[0109] In the example, the base station can semi-statically configure the UE using one or more BWPs. The UE can 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 the expiration of a BWP inactivity timer (e.g., in the case that the second BWP is the default BWP).

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

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

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

[0113] To provide higher data rates, carrier aggregation (CA) can be used to combine two or more carriers and transmit them simultaneously to / from the same UE. The aggregated carriers in CA can be referred to as component carriers (CCs). When using CA, there are multiple serving cells for the UE, with one serving cell per CC. A CC can have three configurations in the frequency domain.

[0114] Figure 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 located directly adjacent to each other within the band. In the intra-band discontinuous configuration 1004, the two CCs are aggregated in the same frequency band (band A) and separated by a certain gap within the band. In the inter-band configuration 1006, the two CCs are located in frequency bands (band A and band B).

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

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

[0117] The configured SCell for the 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 transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) Figure 4B The MAC CE is used to activate and deactivate configured SCells. For example, the MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells for the UE (e.g., in a subset of configured SCells) are activated or deactivated. Configured SCells can be deactivated in response to the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0118] Downlink control information for a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant; this is called self-scheduling. A cell's DCI can be transmitted on another cell; this is called cross-carrier scheduling. Uplink control information used for aggregation cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregation downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0119] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each contain one or more downlink CCs. Figure 10B In the example, PUCCH group 1010 contains three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example contains three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary SCells (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) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if Figure 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

[0120] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index can identify the cell's downlink carrier and / or uplink carrier, for example, depending on the context in which the physical cell ID is used. The physical cell ID can be determined using synchronization signals transmitted on the downlink component carriers. The cell index can be determined using RRC messages. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure relates to a first physical cell ID for a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell that includes the first downlink carrier. The same / similar concepts can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell including the first carrier is activated.

[0121] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In the example, the HARQ entity can operate on the serving cell. Transport blocks can be generated based on the assignment / authorization of each serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to the serving cell.

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

[0123] Figure 11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks can contain one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). Figure 11A (As shown in the diagram). Bursts can be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It should be understood that... Figure 11AThis is an example, and these parameters (the number of SS / PBCH blocks per burst, the periodicity of the burst, the burst location within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the cell's parameter set or subcarrier spacing; configuration performed by the network (e.g., using RRC signaling); or any other suitable factors. In this example, the UE can 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.

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

[0125] The UE may not know the location of the SS / PBCH block in the time and frequency domains (e.g., when the UE is searching for a cell). To find and select a cell, the UE can monitor the carrier of the PSS. For example, the UE can monitor the frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE can search for the PSS at different frequency locations within the carrier, as indicated by the synchronization grating. If the PSS is found at a certain location in the time and frequency domains, the UE can determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block can be a cell-defined SS block (CD-SSB). In the example, the primary cell can be associated with the CD-SSB. The CD-SSB can be located on the synchronization grating. In the example, cell selection / search and / or reselection can be based on the CD-SSB.

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

[0127] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH can contain an indication of the cell's current system frame number (SFN) and / or an SS / PBCH block timing index. These parameters can help the UE synchronize time with the base station. The PBCH can contain a Master Information Block (MIB) to provide one or more parameters to the UE. The MIB can be used by the UE to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI can contain System Information Block Type 1 (SIB1). SIB1 can contain information required for the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH that can be used to schedule the PDSCH. The PDSCH can contain SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH can indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency pointed to by the UE.

[0128] The UE may assume that one or more SS / PBCH blocks transmitted using 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 blocks transmitted with different SS / PBCH block indices.

[0129] 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 the example, the first SS / PBCH block can be transmitted in the first spatial direction using the first beam, and the second SS / PBCH block can be transmitted in the second spatial direction using the second beam.

[0130] In the example, within the carrier's frequency range, the base station can transmit multiple SS / PBCH blocks. In the example, the first PCI of the first SS / PBCH block among the multiple SS / PBCH blocks can be different from the second PCI of the second SS / PBCH block among the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations can be different or the same.

[0131] CSI-RS can be transmitted by the base station and used by the UE to acquire Channel State Information (CSI). The base station can utilize one or more CSI-RS to configure the UE for channel estimation or any other suitable purpose. The base station can utilize one or more of the same / similar CSI-RS to configure the UE. The UE can measure the one or more CSI-RS. The UE can estimate the downlink channel state and / or generate a CSI report based on the measurements of the one or more downlink CSI-RS. The UE can provide the CSI report to the base station. The base station can use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0132] The base station can semi-statically configure the UE using one or more CSI-RS resource sets. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the UE that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0133] The base station can configure the UE to report CSI measurements. 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 multiple CSI report timings and / or periods. For aperiodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reports. The base station can configure the UE using CSI-RS resource sets and CSI reports using RRC signaling.

[0134] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE can be configured to use the same OFDM symbols for both the downlink CSI-RS and the 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 block (PRB) configured for the CORESET. The UE can also be configured to use the same OFDM symbols for both the downlink CSI-RS and the SS / PBCH block when the downlink CSI-RS and SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0135] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on the one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE using the number (e.g., maximum number) of frontload DMRS symbols used for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where DMRS locations, DMRS types, and / or scrambling sequences can be the same or different. The base station can use the same precoding matrix to transmit downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS to perform consistent demodulation / channel estimation of the PDSCH.

[0136] In the example, the transmitter (e.g., a base station) can use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter can use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices can differ based on the first and second bandwidths being different. The UE can assume that the same precoder matrix is ​​used across the set of PRBs. The set of PRBs can be represented as a Precode Resource Block Group (PRG).

[0137] A PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS exists on one or more layers of the PDSCH. A higher layer may configure up to three DMRS for the PDSCH.

[0138] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on RRC configuration. The presence and / or type of downlink PT-RS can be configured UE-specifically using a combination of RRC signaling and / or association with one or more parameters (e.g., modulation and coding scheme (MCS)) indicated by the DCI for other purposes. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least one MCS. NR networks can support multiple PT-RS densities defined in the time and / or frequency domains. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can employ the same precoding for both 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. Downlink PT-RS can be limited to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0139] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS to perform consistent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE using one or more uplink DMRS configurations. At least one DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols of PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS type and / or scrambling sequence of the DMRS can be the same or different.

[0140] A PUSCH may include one or more layers, and a UE may transmit at least one symbol having DMRS on one or more layers present in the PUSCH. In the example, a higher layer may configure up to three DMRS for the PUSCH.

[0141] Depending on the UE's RRC configuration, the uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or type of the uplink PT-RS can be configured UE-specifically through a combination of RRC signaling and / or through one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least one 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 both 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 UE's scheduled time / frequency duration.

[0142] The UE can transmit SRS to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to assign one or more resource blocks to uplink PUSCH transmissions from the UE. The base station can semi-statically configure the UE using one or more SRS resource sets. For each SRS resource set, the base station can configure the UE using one or more SRS resources. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) can be transmitted at certain times (e.g., simultaneously). The UE can transmit one or more SRS resources from the SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can 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 the 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 the 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.

[0143] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); time slot, micro-time slot, and / or subframe level periodicity; offset of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiation OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0144] Antenna ports are defined such that a symbol on an antenna port, through the channel through which it is transmitted, can be inferred from another symbol on the same antenna port through the same channel. 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 transmit the second symbol on the antenna port from the channel used to transmit the first symbol on the antenna port. A first antenna port and a second antenna port can be referred to as quasi-co-located (QCLed) if one or more large-scale properties can be inferred from the channel through which the second symbol on the second antenna port is transmitted, and the channel through which the first symbol on the first antenna port is transmitted. 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.

[0145] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After establishing an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0146] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown can represent a resource block (RB) within the cell's bandwidth. The base station can transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters can be configured for CSI-RS resource configuration via 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 subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transport comb, and 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).

[0147] Figure 11B The three beams shown can be configured for use in a UE-specific configuration. Figure 11B The diagram shows three beams (beam #1, beam #2, and beam #3), with the possibility of configuring more or fewer beams. CSI-RS1101 can be assigned to beam #1, which can be transmitted on one or more subcarriers in the RB of the first symbol. CSI-RS1102 can be assigned to beam #2, which can be transmitted on one or more subcarriers in the RB of the second symbol. CSI-RS1103 can be assigned to beam #3, which can be transmitted on 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 (e.g., those not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time domain multiplexing (TDM), the beam for a UE can be configured such that the beam for the UE uses symbols from beams of other UEs.

[0148] CSI-RS, such as Figure 11BThose shown (e.g., CSI-RS 1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) configured with CSI-RS resources. The base station can configure the UE using a reporting configuration, and the UE can report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station can determine one or more Transmission Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurement results. In the example, the base station can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can receive downlink transmissions with a receive (Rx) beam determined based on the one or more TCI states. In the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE can determine the spatial domain filter for the transmit (Tx) beam based on the spatial domain filter corresponding to the Rx beam. If the UE does not have beam correspondence capability, the UE can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE can perform the uplink beam selection procedure based on one or more Sounding Reference Signal (SRS) resources configured for the UE by the base station. The base station can select and indicate the UE's uplink beam based on measurements of one or more SRS resources transmitted by the UE.

[0149] In the beam management procedure, the UE can assess (e.g., measure) the channel quality of one or more beampup links, including beampup links containing transmit beams transmitted by the base station, and receive beams received by the UE. Based on the assessment, the UE can transmit a beam measurement report indicating one or more beampup quality parameters, including, 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).

[0150] Figure 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurement of the transmission (Tx) beams of a Transport Receiver Point (TRP) (or multiple TRPs), for example, to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for the beam set (shown as an ellipse rotating counterclockwise in the top rows of P1 and P2, indicated by the dashed arrows). Beamforming at the UE can include Rx beam sweeping for the beam set (shown as an ellipse rotating clockwise in the bottom rows of P1 and P3, indicated by the dashed arrows). Procedure P2 can be used to enable UE measurement of the Tx beams of a TRP (shown as an ellipse rotating counterclockwise in the top row of P2, indicated by the dashed arrows). The UE and / or base station may perform procedure P2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that 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.

[0151] Figure 12B Examples of three 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 Tx beam of the UE, for example, to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, a Tx beam sweep from the beam set (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by the dashed arrow). Beamforming at the base station can include, for example, an Rx beam sweep from the beam set (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by the dashed arrow). 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 base station can perform procedure U2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This can be called beam refinement. The UE can execute procedure U3 to adjust its Tx beam when the base station is using a fixed Rx beam.

[0152] The UE can initiate a beam failure recovery (BFR) procedure based on the detection of a beam failure. The UE can initiate a BFR procedure by transmitting a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.). The UE can detect a beam failure based on the determination that the quality of the beam pair link in the associated control channel is unsatisfactory (e.g., an error rate higher than the error rate threshold, received signal power lower than the received signal power threshold, timer expiration, etc.).

[0153] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS). The quality of the beamp-link can be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station can indicate one or more DM-RS quasi-co-located (QCLed) RS resources and channels (e.g., control channels, shared data channels, etc.). The one or more DMRS of the RS resources and channels can be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from the transmission to the UE via the RS resources are similar to or the same as the channel characteristics from the transmission to the UE via the channels.

[0154] The network (e.g., gNB and / or the network's ng-eNB) and / or the UE can initiate a random access procedure. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate a random access procedure to request connection settings to the network. A UE can initiate a random access procedure from the RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). A UE can initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for beam failure recovery requests. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell additions.

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

[0156] 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 special 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 RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg1 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 receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0157] The one or more RACH parameters provided in configuration message 1310 can indicate one or more physical RACH (PRACH) timings that can be used to transmit Msg 11311. These one or more PRACH timings can be predefined. The one or more RACH parameters can indicate one or more available sets of one or more PRACH timings (e.g., prach- ConfigIndex The one or more RACH parameters may indicate the association between (a) one or more PRACH timings and (b) one or more reference signals. The one or more RACH parameters may indicate the 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 PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

[0158] The one or more RACH parameters provided in configuration message 1310 can 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 can indicate a reference power for preamble transmission (e.g., the received target power and / or the initial power of the preamble transmission). One or more power offsets indicated by the one or more RACH parameters may exist. For example, the one or more RACH parameters can indicate: power ramp step size; power offset between SSB and CSI-RS; power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or power offset values ​​between preamble groups. The one or more RACH parameters can indicate one or more thresholds upon which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier).

[0159] Msg 1 1311 may contain one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude 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 with an RSRP higher than the 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 can select at least one preamble associated with the one or more reference signals and / or a selected preamble group.

[0160] The UE can determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE can determine the preamble based on path loss measurement, RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters can indicate: the preamble format; the 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 can use the one or more RACH parameters to configure an 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 can determine the preamble contained in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH timings. The UE can use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting the preamble and for determining the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList This can indicate the correlation between the PRACH timing and the one or more reference signals.

[0161] If no response is received after the preamble transmission, the UE can perform a preamble retransmission. The UE can increase the uplink transmission power used for preamble retransmission. The UE can select the initial preamble transmission power based on path loss measurements and / or the target received preamble power configured by the network. The UE can determine the preamble to be retransmitted and can ramp up the uplink transmission power. The UE can receive one or more RACH parameters (e.g., indicating the ramp step size for preamble retransmission) indicating the ramp step size for preamble retransmission. PREAMBLE_POWER_RAMPING_STEP The ramp-up step size can be the amount by which the uplink transmission power used for retransmissions is incrementally increased. If the UE determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in previous preamble transmissions, the UE can ramp up the uplink transmission power. The UE can 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 configured by one or more of the RACH parameters (e.g., preambleTransMax If the UE determines that the random access procedure was not completed successfully, then the UE can be sure that the random access procedure was not completed successfully.

[0162] The Msg 2 1312 received by the UE may contain a RAR. In some scenarios, Msg 2 1312 may contain 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 was received by the base station. Msg 2 1312 may contain a time comparison command that the UE can use to adjust the UE's transmission timing, a scheduling grant for transmitting Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow The UE can monitor the PDCCH of Msg 21312. The UE can determine when to initiate a time window based on the PRACH timing in which it transmits the preamble. For example, the UE can initiate a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing starting from the end of the preamble transmission). The one or more symbols can be determined based on a set of parameters. The PDCCH can be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE can identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI can be used depending on one or more events that initiate a random access procedure. The UE can use a Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE can determine the RA-RNTI based on: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include: RA-RNTI= 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 ×ul_carrier_id, Where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carriers and 1 for SUL carriers).

[0163] The UE may transmit Msg 3 1313 in response to successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). Msg 3 1313 can be used for, for example... Figure 13A The diagram illustrates contention resolution in a contention-based random access procedure. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to each UE. A conflict may occur if the multiple UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE will 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., the TC-RNTI included in Msg 2 1312 if a C-RNTI is assigned, and / or any other suitable identifier).

[0164] Msg 4 1314 can be received after or in response to the transmission of Msg 3 1313. If Msg 3 1313 contains a C-RNTI, the base station will use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If Msg 3 1313 contains a TC-RNTI (e.g., if the UE is in RRC_IDLE state or 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 includes a UE contention resolution identity MAC CE that matches (e.g., is transmitted) the CCCH SDU sent in Msg 3 1313, the UE can determine that contention resolution was successful and / or the UE can determine that the random access procedure was successfully completed.

[0165] The UE can be configured with Supplemental Uplink (SUL) carriers and Normal Uplink (NUL) carriers. Initial access (e.g., random access procedure) can be supported on the uplink carriers. For example, the base station can configure two separate RACH configurations for the UE: one for the SUL carrier and another for the NUL carrier. To enable random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, the UE can determine the SUL carrier if the measured quality of one or more reference signals is below a broadcast threshold. Uplink transmissions during the random access procedure (e.g., Msg 1 1311 and / or Msg 3 1313) can be preserved on the selected carrier. In one or more cases, the UE can switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE can determine and / or switch uplink carriers for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (e.g., listen before speaking).

[0166] Figure 13B This illustrates a two-step contention-free random access procedure. (Compared to...) Figure 13A Similar to the four-step contention-based random access procedure shown, the base station can transmit configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The program shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... Figure 13A The Msg 1 1311 and Msg2 1312 are shown. (As from...) Figure 13A and Figure 13B It will be understood that a contention-free random access procedure may not contain messages such as Msg 3 1313 and / or Msg 4 1314.

[0167] It can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover. Figure 13B The contention-free random access procedure is shown. For example, the base station can indicate or assign a preamble to the UE for Msg 1 1321. The UE can receive the preamble indication from the base station via PDCCH and / or RRC (e.g., ra-PreambleIndex ).

[0168] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow To monitor the PDCCH of the RAR. In the event of a beam failure recovery request, the base station can search the space indicated by the RRC message (e.g., recoverySearchSpaceIdThe UE can be configured with a separate time window and / or a separate PDCCH. The UE can monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) in the search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure was 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 addresses to the C-RNTI, the UE can determine that the random access procedure was successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a preamble identifier, the UE can determine that the random access procedure was successfully completed. The UE can determine that the response is an indication of confirmation of the SI request.

[0169] Figure 13C Another two-step random access procedure is shown. (Compared to...) Figure 13A and Figure 13B Similar to the random access procedure shown, the base station can transmit configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The program shown includes the transmission of two messages: Msg A1331 and Msg B1332.

[0170] Msg A 1331 can be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... Figure 13A The content shown in Msg 3 1313 is similar to and / or equivalent to that of Msg 3 1313. Transport block 1342 may include UCIs (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 content similar to and / or equivalent to that shown in Msg 3 1313. Figure 13A and Figure 13B The Msg 2 1312 shown (e.g., RAR) and / or Figure 13A The content shown is similar to and / or equivalent to Msg 41314.

[0171] UE can initiate [activities] on licensed spectrum and / or unlicensed spectrum. Figure 13CThe two-step random access procedure is used in the UE. 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; cell size; the UE's RRC status; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

[0173] Transport block 1342 may include data (e.g., delay-sensitive data), a UE identifier, security information, and / or device information (e.g., 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 advanced command; a power control command; an uplink grant (e.g., 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 can determine that the two-step random access procedure was successfully completed if: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0174] The UE and the base station can 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.

[0175] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling authorization indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the 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-shared PDCCH (GC-PDCCH) common to the UE group.

[0176] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to the DCI to aid in the detection of transmission errors. When the DCI is intended for use with a UE (or a group of UEs), the base station can scramble the CRC parity bits with the UE's identifier (or the UE group's identifier). Scrambling the CRC parity bits with the identifier can include modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of the Radio Network Temporary Identifier (RNTI).

[0177] DCIs can be used for various 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 using a paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled using a cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled using a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13AThe Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the UE may include: the configured scheduling RNTI (CS-RNTI), transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0178] 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 can be used for PUSCH scheduling in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used for PUSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for PDSCH scheduling in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for PDSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide slot format indication to UE groups. DCI format 2_1 can be used to notify UE groups of physical resource blocks and / or OFDM symbols, where UEs may assume that transmission to UEs is not expected. DCI format 2_2 can be used to transmit Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. New DCI formats for new features can be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

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

[0180] Figure 14A An example of a CORESET configuration for the bandwidth portion is shown. A base station can transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources in which a UE attempts to decode the DCI using one or more search spaces. The base station can configure the CORESET in the time-frequency domain. Figure 14A In the example, the first CORESET 1401 and the second CORESET 1402 appear at the first symbol of 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 of the time slot. The fourth CORESET 1404 appears at the seventh symbol of the time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

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

[0182] The base station can transmit an RRC message to the UE containing configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can indicate: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring period and 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 can be predefined and known to the UE. The set of CCEs in the UE-specific search space set can be configured based on the UE's identifier (e.g., C-RNTI).

[0183] like Figure 14B As shown, the UE can determine the time-frequency resources of the CORESET based on RRC messages. The UE can determine the CCE-to-REG mapping of the CORESET (e.g., interleaved or non-interleaved and / or mapping parameters) based on the CORESET's configuration parameters. The UE can determine the number of search space sets configured on the CORESET (e.g., up to 10) based on RRC messages. The UE can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE can 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 locations, 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 can determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambling bits of the CRC parity bit of the DCI that match the RNTI value). The UE can process the information contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

[0184] The UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling transmission may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. 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 can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. 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 acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to transmit uplink control signaling via the PUCCH.

[0185] Five PUCCH formats can exist, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols transmitted in the UCI and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can contain two or fewer bits. If more than one or two symbols are transmitted and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE can use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can contain 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 can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can contain more than two bits. If more than one or two symbols are transmitted and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can contain more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not contain an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can contain more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource contains an orthogonal overlay code, the UE can use PUCCH format 4.

[0186] The base station can transmit configuration parameters for multiple PUCCH resource sets to the UE using, for example, RRC messages. These multiple PUCCH resource sets (e.g., up to four sets) can be configured on the cell's uplink BWP. A PUCCH resource set can be configured with: a PUCCH resource set index; and multiple PUCCH resources (e.g., PUCCH resource resources identified by PUCCH resource identifiers). pucch-Resourceid The UE can transmit multiple (e.g., a maximum number) UCI ​​information bits using one of the multiple PUCCH resources in a PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can 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 can select a 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 can select a second PUCCH resource set with 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 can select a third PUCCH resource set with 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 the third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

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

[0188] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. 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. Figure 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may contain more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

[0189] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 is referred to as the downlink, while the communication direction from wireless device 1502 to base station 1504 via air interface 1506 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using some combination of FDD, TDD, and / or two duplex technologies.

[0190] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 can be provided to processing system 1508 of base station 1504. The data can be provided to processing system 1508 via, for example, a core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 can be provided to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, information about… Figure 2A , Figure 2B , Figure 3 and Figure 4A The SDAP layer, PDCP layer, RLC layer, and MAC layer are included. Layer 3 may contain elements such as... Figure 2B The RRC layer.

[0191] After being processed by processing system 1508, data to be transmitted to wireless device 1502 can be provided to transmission processing system 1510 of base station 1504. Similarly, after being processed by processing system 1518, data to be transmitted to base station 1504 can be provided to transmission processing system 1520 of wireless device 1502. Transmission processing systems 1510 and 1520 can implement Layer 1 OSI functions. Layer 1 can include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For transmission processing, the PHY layer can perform operations such as forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing, etc.

[0192] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 can include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping of the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

[0193] like Figure 15 As shown, wireless device 1502 and base station 1504 may include multiple antennas. These multiple antennas can 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, wireless device 1502 and / or base station 1504 may have a single antenna.

[0194] Processing systems 1508 and 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 code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although Figure 15 Although not shown, the transmission processing system 1510, transmission processing system 1520, receiving processing system 1512 and / or receiving processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

[0195] Processing system 1508 and / or 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 devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and base station 1504 to operate in a wireless environment.

[0196] Processing system 1508 and / or 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 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or 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 aforementioned one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar panel, a fuel cell unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0197] Figure 16AAn example architecture for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. These functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulation symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports, etc. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In the example, when transform precoding is not enabled, it can be achieved through... Figure 16A Generate CP-OFDM signals for uplink transmission. These functions are shown as examples, and other mechanisms are expected to be implemented in various implementation schemes.

[0198] Figure 16B An example architecture for modulation and upsampling of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value SC-FDMA or CP-OFDM baseband signal from the antenna port and / or a complex-value Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0199] Figure 16C An example structure for downlink transmission is shown. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted over the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port, etc. These functions are shown as examples, and other mechanisms are expected to be implemented in various embodiments.

[0200] Figure 16D Another example architecture for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal at the antenna port. Filtering can be applied before transmission.

[0201] A wireless device can receive one or more messages (e.g., RRC messages) from a base station, including configuration parameters for multiple cells (e.g., primary cell, secondary cells). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via these 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, configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, etc. For example, 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.

[0202] A timer can begin running once started and continues running until it stops or expires. If the timer is not running, it can be started, or if it is running, it can be restarted. The timer can be associated with a value (e.g., a timer can start or restart from a certain value, or it can start from zero and expire once it reaches that value). The duration of the timer may not be updated until the timer stops or expires (e.g., due to BWP switching). The timer can be used to measure time periods / windows of a process. When the specification refers to embodiments and procedures relating 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 a timer can be used to measure time periods / windows of a process. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In the example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer restarts, the measurement process for the time window can be restarted. Other example embodiments for restarting the measurement of a time window can be provided.

[0203] Uplink Buffer State Reports (BSRs) may be required to provide support for QoS-aware packet scheduling. In NR, an Uplink Buffer State Report refers to data buffered for a set of Logical Channel Groups (LCGs) within the UE. It can be reported in the uplink using four formats: - A short format for reporting only one BSR (for a logical channel group (LCG)); - A flexible long format for reporting several BSRs (up to all eight LCGs). - An extended short format for reporting (one LCG) of a BSR; - An extended long format for reporting several BSRs (up to all 256 LCGs).

[0204] MAC signaling can be used to transmit uplink buffer status reports. When a BSR is triggered (e.g., when new data arrives in the UE's transmission buffer), the UE can transmit a scheduling request (SR) (e.g., when no resources are available to transmit a BSR).

[0205] The Buffer Status Report (BSR) procedure can be used to provide the service gNB with information about the amount of UL data in a MAC entity.

[0206] RRC can be configured with the following parameters to control BSR: periodicBSR-Timer; retxBSR-Timer; logicalChannelSR-DelayTimerApplied; logicalChannelSR-DelayTimer; logicalChannelSR-Mask; logicalChannelGroup.

[0207] Each logical channel can be assigned to an LCG using logicalChannelGroup.

[0208] The UE / MAC entity can determine the amount of UL data available for the logical channel based on the data volume calculation procedures in TS 38.322 and 38.323.

[0209] A BSR can be triggered if any of the following events occur for an active cell group: - UL data for a logical channel belonging to an LCG becomes available to the MAC entity; and this UL data belongs to a logical channel with a higher priority than any logical channel containing available UL data belonging to any LCG; or belongs to none of the logical channels of an LCG containing any available UL data. In this case, the BSR may be referred to below as a 'regular BSR'.

[0210] A BSR can be triggered if any of the following events occur for an active cell group: - UL resources can be allocated, and the number of padding bits is equal to or greater than the size of the Buffer Status Report MAC CE plus its subheadings. In this case, the BSR is referred to below as the 'Padding BSR'. When the -retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains SL data, the BSR will be referred to as 'regular BSR' below. -periodicBSR-Timer expires, in which case the BSR will be referred to below as 'periodic BSR'.

[0211] When a regular BSR trigger event occurs simultaneously for multiple logical channels, a separate regular BSR is triggered for each logical channel.

[0212] For a standard BSR, the UE / MAC entity can be determined as follows: 1> If a BSR is triggered for a logical channel configured by the upper layer with a true logicalChannelSR-DelayTimerApplied value, and the SDT procedure is not in progress according to clause 5.27: 2> Start or restart logicalChannelSR-DelayTimer.

[0213] 1> Otherwise, if a BSR is triggered for a logical channel configured by the upper layer with a true logicalChannelSR-DelayTimerApplied value, and the SDT procedure is in progress according to clause 5.27: 2> Start or restart logicalChannelSR-DelayTimer with the value configured by sdt-LogicalChannelSR-DelayTimer.

[0214] 1> Otherwise: 2> If it is running, stop logicalChannelSR-DelayTimer.

[0215] For regular and periodic BSRs, the MAC entity can be determined as follows: 1> If, when creating a MAC PDU containing a BSR, more than one LCG has data available for transmission: 2> For all LCGs with data available for transmission, report a long BSR.

[0216] 1> Otherwise: 2> Report a short BSR.

[0217] For regular and periodic BSRs, the MAC entity can be determined as follows: 1> If, when creating a MAC PDU containing a BSR, more than one LCG has data available for transmission: 2> If the maximum LCG ID in the configured LCG is 7 or lower: 3> For all LCGs with data available for transmission, report a long BSR.

[0218] 2> Otherwise: 3> For all LCGs with data available for transmission, report an extended long BSR.

[0219] 1> Otherwise: 2> Report extended short BSR.

[0220] For filling BSRs, the MAC entity can be determined as follows: 1> If the number of padding bits is equal to or greater than the size of the short BSR plus its subheadings, but less than the size of the long BSR plus its subheadings: 2> If, when establishing a BSR, more than one LCG has data available for transmission: 3> If the number of padding bits equals the short BSR plus the size of its sub-header: 4> Report a short-truncated BSR with an LCG that has the highest priority logical channel available for data transmission.

[0221] 3> Otherwise: 4> Following the descending order of the highest priority logical channel in each of these LCGs (with or without data available for transmission), and in the case of equal priority, reporting the long truncated BSR of the LCG with logical channels having data available for transmission in ascending order of LCGID.

[0222] 2> Otherwise: 3> Report a short BSR.

[0223] 1> If the number of padding bits is equal to or greater than the length of the BSR plus the size of its subheadings: 2> For all LCGs with data available for transmission, report a long BSR.

[0224] For filling BSRs, the MAC entity can be determined as follows: 1> If the number of padding bits is equal to or greater than the size of the extended short BSR plus its subheadings, but less than the size of the extended long BSR plus its subheadings: 2> If, when establishing a BSR, more than one LCG has data available for transmission: 3> If the number of padding bits is less than the size of an extended-length truncated BSR with a zero-buffer size plus the size of its subheader: 4> Report an extended short truncated BSR with an LCG that has the highest priority logical channel available for data transmission.

[0225] 3> Otherwise: 4> Following the descending order of the highest priority logical channel in each of these LCGs (with or without data available for transmission), and in the case of equal priority, reporting the extended long truncated BSR of the LCG with logical channels with data available for transmission in ascending order of LCGID.

[0226] 2> Otherwise: 3> Report extended short BSR.

[0227] 1> Otherwise, if the number of padding bits is equal to or greater than the extended length BSR plus the size of its subheadings: 2> For all LCGs with data available for transmission, report an extended long BSR.

[0228] For a BSR triggered by the expiration of the retxBSR-Timer, the MAC entity considers that the logical channel that triggered the BSR is the highest priority logical channel with data available for transmission.

[0229] The UE / MAC entity can be determined as follows: 1> If the buffer status reporting procedure determines that at least one BSR has been triggered and not canceled: 2> If, due to logical channel priority ordering, the UL-SCH resource is available for a new transmission and the UL-SCH resource can accommodate the SL-BSR MAC CE plus its sub-header: 3> Instructions to use multiplexing and assembly procedures to generate BSR MAC CE; 3> Start or restart periodicBSR-Timer unless all generated BSRs are long or short truncated or extended long or short truncated BSRs; 3> Start or restart retxBSR-Timer.

[0230] 2> If a regular BSR has been triggered and the logicalChannelSR-DelayTimer is not running: 3> If no UL-SCH resource is available for the new transmission; or 3> If the MAC entity has configured uplink grant and the logical channel SR-Mask is set to false, a regular BSR is triggered; or 3> If the UL-SCH resources available for new transmission do not meet the LCP mapping constraints of the logical channel configured to trigger BSR (see Clause 5.4.3.1): 4> Trigger a scheduling request.

[0231] If a MAC entity has configured, received, or confirmed an uplink grant, the UL-SCH resource can be considered available. However, if a MAC entity determines that a UL-SCH resource is available at a given point in time, this does not necessarily mean that the UL-SCH resource is available at that point in time.

[0232] Even when multiple events have triggered a BSR, a MAC PDU can contain at most one BSR MAC CE. Regular BSRs and periodic BSRs should take precedence over filling BSRs.

[0233] The MAC entity can restart the retxBSR-Timer after receiving authorization to transmit new data on any UL-SCH.

[0234] When the UL authorization accommodates all pending data available for transmission, but is insufficient to accommodate an additional BSR MAC CE plus its sub-header, all triggered BSRs can be cancelled. When a MAC PDU is transmitted and this PDU contains a long, extended long, short, or extended short BSR MAC CE, all BSRs triggered before the MAC PDU assembly should be cancelled, whereby the BSR MAC CE contains a buffer state up to (and including) the last event that triggered the BSR before the MAC PDU assembly.

[0235] MAC PDU assembly can occur at any point between uplink granted reception and the actual transmission of the corresponding MAC PDU. BSR and SR can be triggered after the assembly of a MAC PDU containing a BSR MAC CE, but before the transmission of that MAC PDU. Alternatively, BSR and SR can be triggered during MAC PDU assembly.

[0236] If the HARQ process is configured with a cg-RetransmissionTimer and if the BSR is already included in the MAC PDU for transmission over the configured license via this HARQ process, but has not yet been transmitted over the lower layer, how the BSR content is handled depends on the UE implementation scheme.

[0237] Buffer Status Report (BSR) MAC CE consists of any of the following: - Short BSR format (fixed size); or - Extended short BSR format (fixed size); or - Long BSR format (variable size); or - Extended long BSR format (variable size); or - Short truncated BSR format (fixed size); or - Extended short truncated BSR format (fixed size); or - Long truncated BSR format (variable size); or - Extended long truncated BSR format (variable size).

[0238] Fields in BSR MAC CE can be defined as follows: -LCG ID: The Logical Channel Group ID field identifies the group of the logical channel reporting buffer status. For short BSR and short truncated BSR formats, the field length is 3 bits, and for extended short BSR and extended short truncated BSR formats, the field length is 8 bits. -LCGi: For long BSR format, extended long BSR format, pre-empted BSR format, and extended pre-empted BSR format, this field indicates the presence of the buffer size field for logical channel group i. An LCGi field set to 1 indicates that the buffer size field for logical channel group i is reported. An LCGi field set to 0 indicates that the buffer size field for logical channel group i is not reported. For long truncated BSR format and extended long truncated BSR format, this field indicates whether logical channel group i has available data. An LCGi field set to 1 indicates that logical channel group i has available data. An LCGi field set to 0 indicates that logical channel group i does not have available data. - Buffer Size: After the MAC PDU has been established (i.e., after the logical channel priority sorting procedure, which may result in a zero value for the buffer size field), the buffer size field identifies the total amount of available data across all logical channels in the logical channel group according to the data volume calculation procedure in TS 38.322 and 38.323. The data volume is indicated in bytes. The sizes of the RLC header and MAC subheader are not considered in the buffer size calculation. This field is 5 bits long for the short BSR format and short truncated BSR format. This field is 8 bits long for the extended short BSR format and extended short truncated BSR format. This field is 8 bits long for the long BSR format, long truncated BSR format, extended long BSR format, and extended long truncated format. Values ​​for the 5-bit and 8-bit buffer size fields are used respectively. For the long BSR format, long truncated BSR format, extended long BSR format, and extended long truncated format, the buffer size field is included in ascending order based on LCGi. For both long truncated BSR and extended long truncated formats, the number of buffer size fields is maximized while not exceeding the number of padding bits.

[0239] The UE has uplink rate control (RRC) functionality, which manages the sharing of uplink resources among logical channels. RRC controls the uplink rate control function by assigning priority, priority bit rate (PBR), and buffer size duration (BSD) to each logical channel. The signaling notification value does not need to be related to the value signaled to the gNB via the NG. Additionally, mapping restrictions can be configured.

[0240] The uplink rate control function ensures that the UE serves logical channels in the following order: - All relevant logical channels are arranged in descending priority order, up to their PBR; - For the remaining resources assigned by the authorization, all relevant logical channels are arranged in descending priority order.

[0241] With all PBRs set to zero, the first step is skipped, and logical channels are served in a strict priority order: the UE maximizes the transmission of higher priority data.

[0242] Mapping restrictions tell the UE which logical channels are associated with the received license. If no mapping restrictions are configured, all logical channels are considered.

[0243] If more than one logical channel has the same priority, the UE can serve them equally.

[0244] Whenever a new transmission is performed, the Logical Channel Priority (LCP) procedure can be applied.

[0245] RRC can control the scheduling of uplink data through signaling for each logical channel per MAC entity. - Priority, where an increased priority value indicates a lower priority; -prioritisedBitRate sets the priority bit rate (PBR). -bucketSizeDuration sets the duration of the bucket size (BSD).

[0246] RRC can control the LCP procedure by configuring mapping limits for each logical channel: -allowedSCS-List, which sets the allowed subcarrier spacing for transmission; -maxPUSCH-Duration sets the maximum PUSCH duration allowed for transmission; -configuredGrantType1Allowed sets whether the configured grant type 1 can be used for transport; -allowedServingCells, which sets the allowed cells for transmission; -allowedCG-List, which sets the allowed permissions for transmission; -allowedPHY-PriorityIndex sets the allowed PHY priority index for dynamic authorization of transport; -allowedHARQ-mode sets the allowed uplinkHARQ mode for transmission.

[0247] The following UE variable can be sorted by logical channel priority procedure: Bj, which is maintained for each logical channel j.

[0248] When establishing a logical channel, the UE / MAC entity should initialize the logical channel's Bj value to zero.

[0249] For each logical channel j, the MAC entity can: 1> Before each instance of the LCP program, increment Bj by the product PBR×T, where T is the time elapsed since the last increment of Bj; 1> If the value of Bj is greater than the bucket size (i.e., PBR × BSD): 2> Set Bj to the bucket size.

[0250] As long as Bj is up-to-date when LCP processing authorization is performed, the exact timing at which the UE updates Bj between LCP procedures can depend on the UE implementation scheme.

[0251] When executing a new transfer, the MAC entity can: 1> Select a logical channel for each UL license that meets all of the following conditions: 2> If configured, the set of allowed subcarrier spacing index values ​​in the allowedSCS-List contains subcarrier spacing indices associated with UL authorization; and 2> If configured, maxPUSCH-Duration is greater than or equal to the PUSCH transmission duration associated with UL authorization; and 2> If configured, `configuredGrantType1Allowed` is set to true if the SL license is of the configured license type 1; and 2> If configured, allowedServingCells contain cell information associated with UL authorization. When CA replication is deactivated for this DRB in this MAC entity, it does not apply to logical channels associated with DRBs configured with PDCP replication (i.e., CA replication) within the same MAC entity; and 2> If configured, the allowedCG-List contains an index of the configured authorizations associated with the UL authorization; and 2> If configured, allowedPHY-PriorityIndex contains a priority index associated with dynamic UL authorization; and 2> If configured, allowedHARQ-mode includes the uplinkHARQ mode of the HARQ process associated with UL authorization.

[0252] Subcarrier spacing index, PUSCH transmission duration, cell information, and priority index can be included in the uplink transmission information received from the lower layer for corresponding scheduling of uplink transmissions.

[0253] When performing a new transmission, the UE / MAC entity can: 1> The resources are allocated to the logical channel as follows: 2> Select logical channels for UL grants of Bj>0 and allocate resources in descending priority order. If the PBR of a logical channel is set to infinity, the MAC entity should allocate resources for all data available for transmission on the logical channel before satisfying the PBR of lower priority logical channels; 2> Decrease Bj by the total size of the MAC SDU serving the above logical channel j; 2. If any resources remain, all selected logical channels are served in a strictly descending priority order (regardless of the value of Bj) until the data or SL grants (whichever occurs first) for said logical channel are exhausted. Logical channels configured with equal priorities should be served equally.

[0254] The value of Bj can be negative.

[0255] If the requesting MAC entity transmits multiple MAC PDUs simultaneously, or if the MAC entity receives multiple UL grants within one or more overlapping PDCCH moments (i.e., on different serving cells), the order in which the grants are processed may depend on the UE implementation scheme.

[0256] The UE may also follow the following rules during the above scheduling procedure: - If the entire SDU (or a partially transmitted SDU or a retransmitted RLC PDU) is fitted into the remaining resources of the associated MAC entity, the UE should not segment the RLC SDU (or a partially transmitted SDU or a retransmitted RLC PDU). - If the UE segments the RLC SDU from the logical channel, it can maximize the size of the segment to fill the authorization of the associated MAC entity as much as possible; -UE can maximize data transmission; - If a MAC entity is provided with a UL license size equal to or greater than 8 bytes (when not using eLCID) or 10 bytes (when using eLCID), and has data that can be used and is permitted for transmission, the MAC entity should not transmit only padding BSR and / or padding.

[0257] The MAC entity can be identified as follows: 1> If the MAC entity is configured with enhancedSkipUplinkTxDynamic having a true value and the grant indicated to the HARQ entity is addressed to C-RNTI, or if the MAC entity is configured with enhancedSkipUplinkTxConfigured having a true value and the grant indicated to the HARQ entity is the configured uplink grant: 2> If there is no UCI for multiplexing on this PUSCH transport, as specified in TS 38.213; and 2> If there is no non-periodic CSI for this PUSCH transfer request, as specified in TS 38.212; and 2> If the MAC PDU contains zero MAC SDUs; and 2> If the MAC PDU contains only periodic BSRs and there is no data available for any LCG, or the MAC PDU contains only padding BSRs: 3> Do not generate MAC PDUs for HARQ entities.

[0258] 1> Otherwise, if the MAC entity is configured with skipUplinkTxDynamic with a true value, and the grant indicated to the HARQ entity is addressed to C-RNTI, or the grant indicated to the HARQ entity is the configured uplink grant: 2> If there is no non-periodic CSI for this PUSCH transfer request, as specified in TS 38.212; and 2> If the MAC PDU contains zero MAC SDUs; and 2> If the MAC PDU contains only periodic BSRs and there is no data available for any LCG, or the MAC PDU contains only padding BSRs: 3> Do not generate MAC PDUs for HARQ entities.

[0259] Extended reality (XR) can refer to all real-virtual combinations of environments and human-computer interactions generated by computer technology and wearable devices. XR can be a general term encompassing different types of reality: Virtual reality (VR) can be a rendered version of a delivered visual and audio scene. The rendering can be designed to simulate real-world visual and auditory sensory stimuli as naturally as possible as an observer or user moves within application-defined constraints. Virtual reality typically, but not necessarily, requires the user to wear a head-mounted display (HMD) that completely replaces the user's field of view with simulated visual components, and headphones to provide accompanying audio. Some form of head and motion tracking for the user in VR also typically needs to allow for updates to the simulated visual and audio components to ensure that objects and sound sources remain consistent with the user's movement from the user's perspective.

[0260] Augmented reality (AR) is providing users with additional information or artificially generated objects or content overlaid on their current environment. This additional information or content will typically be visual and / or audible, and the observation of their current environment can be direct, without intermediate sensing, processing, and rendering, or it can be indirect, where the perception of their environment is relayed via sensors and can be augmented or processed.

[0261] Mixed Reality (MR) can be a higher form of AR, in which some virtual elements are inserted into the physical scene to provide the illusion that these elements are part of the real scene.

[0262] Other terms used in the context of XR are immersion (the feeling of being surrounded by a virtual environment) and presence (the feeling of being physically and spatially present in a virtual environment). Presence provides meaningful minimum performance requirements for various technologies such as tracking, latency, persistence, resolution, and optics.

[0263] This application may use the abbreviation XR throughout to refer to devices, applications, and functions used in VR, AR, and MR. Examples include, but are not limited to, HMDs for VR, optical see-through glasses and camera-based see-through HMDs for AR and MR, and mobile devices with position tracking and cameras. They can all provide a degree of spatial tracking, and spatial tracking leads to interaction to view some form of virtual content.

[0264] Many XR and CG use cases are characterized by quasi-periodic services with high data rates (potentially jittery) in DL (i.e., video streaming) combined with frequent UL (i.e., attitude / control updates) and / or UL video streaming. Both DL and UL services are also characterized by relatively tight packet delay budgets (PDB). Therefore, it is necessary to investigate and potentially specify possible solutions to better support this challenging service, namely, by better matching the non-integer periodicity of the service, such as 60 / 90 / 120 frames per second, with NR signaling.

[0265] Many end-user XR and CG devices are expected to be mobile and small-scale, thus having limited battery power resources. Therefore, additional power enhancements may be needed to reduce overall UE power consumption and thus extend effective UE battery life when operating XR and CG services. From the Release 17 research project on “XR Evaluation,” it was identified that the current DRX configuration is unsuitable for (i) non-integer XR service periodicity, (ii) variable XR data rates, and (iii) quasi-periodic XR periodicity; therefore, enhancements in these areas would be beneficial.

[0266] The anticipated set of XR and CG services exhibits a degree of diversity, and the characteristics of the data stream (i.e., video) may change "dynamically" as the services operate on NR. Therefore, additional information regarding the operating services from higher layers may be beneficial in facilitating the informed selection of radio parameters.

[0267] Table 1 shows the characteristics of XR services.

[0268] Table 1

[0269] XR content can be represented in different formats, such as panoramas or spheres depending on the capabilities of the capture system. Since modern video coding standards are not designed to handle spherical content, projection is used to convert spherical (or 360°) video into two-dimensional rectangular video before the encoding stage. After projection, the resulting two-dimensional rectangular image can be divided into regions that can be rearranged to generate “packed” frames (e.g., front, right, left, back, top, bottom), thereby improving encoding efficiency or viewport-dependent streaming layout.

[0270] XR video frame rates range from 15 frames per second to 90 or even 120 frames per second, with VR typically having a minimum of 60. The known latency of the corner eye reflex or rotational vestibular reflex is approximately 10 ms or in the range of 7-15 ms, and it seems reasonable that this should represent the performance target for XR systems. This results in a motion-to-photon latency of less than 20 ms, with 10 ms given as a target. Regarding bit rate, depending on frame rate, resolution, and codec efficiency, the expected bit rate for XR can be between 10 and 200 Mbps.

[0271] For audio, it can be divided into channel-based representation and object-based representation: Channel-based representation, which uses multiple microphones to capture sound from different directions and employs post-processing techniques, is well-known in the industry because it has been the standard for decades.

[0272] Object-based representations depict complex auditory scenes as a collection of individual audio elements, each consisting of an audio waveform and a set of associated parameters or metadata. The metadata embodies artistic intent by specifying the transformation of each audio element into its final playback by the reproduction system. Sound objects are typically monotracks recorded or synthesized through a sound design process. These sound elements can be further manipulated to position themselves in a horizontal plane around the monitor or, using positional metadata, in the entire three-dimensional space.

[0273] Because sound travels at a relatively slower speed than light, users are naturally more accustomed to and therefore more tolerant of a relative delay between sound and video components, rather than sound arriving earlier than video components. Recent research suggests a synchronization accuracy between 15 ms (audio delay) and 5 ms (audio advance), with absolute limits of 60 ms (audio delay) and 40 ms (audio advance) recommended for broadcast video.

[0274] To maintain reliable registration between the virtual and real worlds, and to ensure accurate tracking of XR viewer pose, XR applications require highly accurate, low-latency tracking of the device at a sampling frequency of approximately 1 kHz. The size of the time-dependent XR viewer pose typically generates packets ranging from 30 to 100 bytes in size, resulting in data volumes of approximately hundreds of kbit / s if transmitted over a network with latency requirements in the range of 10 to 20 milliseconds.

[0275] Repeatedly providing XR viewer poses within the same display time may not necessarily return the same results (predictions become more accurate as information gets closer to the time of prediction), and there is a trade-off between providing several XR viewer poses within a display time and using the same XR viewer pose over several consecutive display times. However, it can be assumed that one XR viewer pose aligned with the frame rate of the video being sent and rendered may be sufficient, for example, at 60fps.

[0276] When pose is used for pre-rendering in networks (edge / cloud), accurate and up-to-date pose information is preferred.

[0277] Attitude information must be transmitted with extremely high reliability; therefore, performance similar to that of Ultra Reliable and Low Latency Communication (URLLC) is expected, i.e., a packet loss rate of less than 10E-4 for uplink sensor data.

[0278] In both the uplink and downlink, XR awareness helps optimize gNB radio resource scheduling and relies at least on the concepts of PDU sets and data bursts: a PDU set can consist of one or more PDUs carrying a payload (e.g., a frame or video slice) of an information unit generated at the application level, while a data burst is a set of data PDUs generated and transmitted by the application in a short time period. A data burst can consist of multiple PDUs belonging to one or more PDU sets. A PDU set can be considered successfully delivered when all PDUs in the set are successfully delivered. During a data burst, periods of inactive data transmission should not be assumed. Although the duration of a data burst can vary, it can be assumed to remain within the same order of magnitude. Furthermore, the arrival time of the first packet of a data burst cannot be provided by the 5G core network (5GC).

[0279] The CN can provide the RAN with the following information to help process QoS flows and PDUs: - Semi-static information per QoS flow: ○ Periodicity of UL and DL services in QoS streams; ○ DL service jitter information (e.g., jitter range) associated with each period of the QoS flow; ○ The set of PDUs for a QoS flow (i.e., the set of all PDUs applicable to a QoS flow).

[0280] --PDU set information and identifiers (in the GTP-U header) are dynamic information provided by the user plane for the DL: ○PDU set serial number; ○ PDU collection size, in bytes; ○ PDU SN within the PDU set; ○The last PDU in the PDU set; ○PDU Set Importance: This parameter can be used to identify the importance of a PDU set within a QoS flow. The RAN can use it for PDU set-level packet dropping in the event of congestion. ○ The data burst end indication in the header of the last PDU in the data burst.

[0281] For uplink XR services, the UE may need to be able to dynamically identify PDU sets and data bursts, but does not need to perform in-band marking on the Uu of the PDU.

[0282] When it is known that the application layer requires a specific number of PDUs in the PDU set to use the corresponding information unit (for example, due to the lack or limitation of error concealment technology, PSIHI sets for QoS flows that once the number of a known lost PDU in the PDU set exceeds this number, the remaining PDUs in the PDU set can be considered no longer needed by the application layer and may undergo data discarding).

[0283] Depending on how the PDU set is mapped to QoS streams in the NAS and how the QoS streams are mapped to the Data Radio Bearer (DRB) in the AS, the following alternatives can be distinguished (e.g.) Figure 17 (as depicted in the text) -111: One-to-one mapping between PDU set types and QoS flows in NAS and one-to-one mapping between QoS flows and DRBs in AS.

[0284] -NN1: A one-to-one mapping between PDU set types and QoS flows in the NAS, and the possible multiplexing of QoS flows in a DRB in the AS.

[0285] -N11: Possible multiplexing of the PDU set type in a QoS flow in NAS and a one-to-one mapping between QoS flows and DRBs in AS.

[0286] -N1N: Possible multiplexing of a PDU set type in a QoS flow within a NAS and demultiplexing of a PDU set type in a QoS flow across multiple DRBs in an AS.

[0287] When comparing these alternatives, it was agreed that QoS flows could not be mapped to multiple DRBs in the uplink, thus ruling out N1N as an alternative.

[0288] Additionally, the concept of PDU sets may not affect the granularity of the following items: -SDAP SDU processing: SDAP still maps each incoming SDU to a single PDU of a single PDCP entity; - Retransmission: HARQ still relies on MAC PDU and ARQ on RLC PDU.

[0289] The following enhancements can be suggested for transports based on configured authorization: - Multiple CG PUSCH transmission opportunities within a single CG PUSCH configuration cycle; - The UE dynamically indicates the timing of unused CG PUSCH based on UCI (e.g., CG-UCI or a new UCI).

[0290] To enhance the scheduling of uplink resources in XR, the following improvements can be envisioned: - One or more additional base station (BS) tables used to reduce quantization errors in BSR reports (e.g., for high bit rates); - This involves understanding the latency of buffered data, such as remaining time, and distinguishing how much data is buffered at which latency. It will be determined whether latency information is reported as part of the Buffer Status Report (BSR) or as a new MAC Control Element (CE). Furthermore, how up-to-date the latency information can be, considering factors such as scheduling and transmission latency, requires further investigation.

[0291] - Further research could be conducted on additional BSR triggering conditions to allow for the timely availability of buffer state information.

[0292] - To deliver some auxiliary information (e.g., periodicity). Further consideration can be given to whether additional mechanisms are needed, assuming that all information may not always be available in the UE application.

[0293] - Signal UL service arrival information from the UE to the gNB, for example, to deal with jitter in network sharing situations.

[0294] For PDCP drop operations in the uplink, timer-based drop operations (when configured) should be applied to all SDUs / PDUs belonging to the same PDU set. Furthermore, for PDU sets in a QoS flow with PSIHI configured, when the number of lost or associated PDUs in the PDU set exceeds a threshold, all remaining PDUs in the PDU set can be dropped at the transmitter to free up radio resources.

[0295] In congested conditions, PSI can be used for PDU set discarding, and in the uplink, a PDU set discarding mechanism that takes PSI into account can be introduced.

[0296] Data can be UL data and / or DL ​​data. Data can be one or more PDUs, one or more sets of PDUs, one or more SDUs, one or more IP packets and / or data bursts. PDUs can be SDAP PDUs, PDCP PDUs, RLCP PDUs, or MAC PDUs. SDUs can be SDAP SDUs, PDCP SDUs, RLC SDUs, MAC SDUs, or PHY SDUs (e.g., TBs).

[0297] Multimodal data can be defined as input data from different types of devices / sensors or output data required for the same task or application to different types of destinations (e.g., one or more UEs). Multimodal data consists of more than one unimodal data, and there may be strong dependencies between each unimodal data. Unimodal data can be considered as one type of data.

[0298] A data burst can be a collection of multiple PDUs generated and sent by an application within a short period of time. A data burst can consist of one or more PDU sets.

[0299] A PDU set can consist of one or more PDUs, each carrying a payload (e.g., a frame or video slice from an Extended Reality and Media (XRM) service) of an information unit generated at the application level. In an exemplary embodiment, the application layer requires all PDUs in the PDU set to use the corresponding information unit. In other embodiments, the application layer can still recover some or all of the information units when some PDUs are lost.

[0300] The PDU set error rate (PSER) defines an upper limit on the non-congestion-related PDU set loss rate between the RAN and the UE. A PDU set is considered successfully delivered only when all PDUs in the set are successfully delivered, and if PSER is available, its use replaces the use of PER.

[0301] The PDU set delay budget (PSDB) can be defined as the time between the reception of the first PDU (at the UPF in the DL, and at the UE in the UL) and the successful delivery of the last arriving PDU in the PDU set (at the UE in the DL, and at the UPF in the UL). PSDB can be an optional parameter and, when provided, PSDB replaces PDB.

[0302] PDU Collection Integration Processing Indicator (PSIHI) can indicate whether the application layer needs all PDUs to use the PDU collection.

[0303] PDU set importance (PSI) identifies the relative importance of a PDU set compared to other PDU sets within a QoS flow. The RAN can use it for PDU set-level packet dropping in the event of congestion.

[0304] The terms “UE” and “wireless device” are used interchangeably.

[0305] The terms “gNB”, “eNB”, “BS”, and “NW” are used interchangeably.

[0306] The upper layer of the UE can be SDAP, RRC, PDCP, RLC and / or MAC layer. The lower layer of the UE can be PHY layer.

[0307] The terms “ID”, “index”, and “identifier” are used interchangeably.

[0308] The terms “determine,” “derive,” “detect,” and “consider” are used interchangeably.

[0309] The terms “configuration” and “instruction” are used interchangeably.

[0310] The terms "delay information" and "remaining time" are used interchangeably. Remaining time can be associated with the delay budget. Remaining time can be associated with the remaining PDB. Remaining time can be associated with the remaining PSDB.

[0311] In the example, delay information / remaining time can be associated with a PDU, a PDU set, a logical channel (LCH), and / or a logical channel group (LCG). In the example, delay information / remaining time can be the time remaining until the delay budget of data (e.g., a PDU or a PDU set) in the UE buffer is exceeded. In the example, delay information / remaining time can be the remaining latency, for example, the data delay budget minus queuing / buffering time.

[0312] In the example, delay information / remaining time can be the result of the difference (e.g., buffer time) between the delay budget and the data already in the buffer (e.g., PDUs or a set of PDUs). In the example, delay information / remaining time can be defined as the residual delay budget of the data (e.g., PDUs or a set of PDUs), such as the duration from the current time to the delay deadline. The delay deadline for a PDU in a set of PDUs can be defined as the time of the first received PDU in the set plus the PSDB of the corresponding QoS stream. For other types of PDUs, the delay deadline can be defined as the arrival time of the PDU plus the PDB of its associated QoS stream. In the example, delay information / remaining time can be the duration between the time the transmission delay is reported and the delay deadline of the corresponding data. In the example, delay information / remaining time can be based on the amount of time the data has been queued in the buffer. If the buffered data includes multiple packets arriving at different times, the delay information / remaining time to be reported can be the longest queue time among the packets in the buffer.

[0313] In the example, the delay information / remaining time can be based on the amount of time remaining until the delivery deadline of the data in the buffer. If the buffered data includes multiple packets with different remaining times, the delay information to be reported can be the shortest remaining time until the delivery deadline of the packet in the buffer. In the example, the delay information / remaining time can be based on a binary flag indicating whether the buffered data is considered "urgent" or "non-urgent". For example, if the queuing time exceeds a certain threshold, the data in the LCH / LCG buffer can be considered urgent.

[0314] In the example, the UE can determine the remaining time included in the delay report when triggering / generating / transmitting the delay report.

[0315] In the examples, delay information / remaining time can be determined based on the timing of triggering / generating / transmitting delay reports. In the examples, delay information / remaining time can be the difference between the delay budget and buffer time for one or more data items. In the examples, delay information / remaining time can be the difference between the time of transmitting / triggering / generating delay reports and the delay deadline for one or more data items. In the examples, delay information / remaining time for one or more data items can be the minimum / shortest remaining time for the data among one or more data items. In the examples, delay information / remaining time for one or more data items can be the maximum / highest remaining time for the data among one or more data items.

[0316] In the example, the delay deadline of a PDU in the PDU set can be defined as the time of the first received PDU in the PDU set plus the PSDB of the associated QoS flow. In the example, the delay deadline of other PDUs can be defined as the arrival time of the PDU plus the PDB of its associated QoS flow.

[0317] The terms “delay report,” “delay information report,” and “delay status report” are used interchangeably.

[0318] Delay Report / DIR / DSR can be referred to as Delay Status Report (DSR) or Delay Information Report (DIR).

[0319] Delay Reports (DIR / DSR) can be used to provide information about the remaining time of one or more data items. Delay Reports (DIR / DSR) can also provide information about the remaining time and amount of data (e.g., buffer size) for one or more data items.

[0320] Delay Reports / DIRs / DSRs may include the remaining time for one or more data points. Delay Reports / DIRs / DSRs may include the delay budget for one or more data points. Delay Reports / DIRs / DSRs may include time information (e.g., absolute time / UTC time / due date of the delay report).

[0321] Delay reports ( / DIR / DSR) can be transmitted via MAC CE. Delay reports ( / DIR / DSR) can also be transmitted via Buffer Status Reports (BSR).

[0322] BSR can be an extension of XR. BSR can be at least one of short BSR, long BSR, regular BSR, periodic BSR, short truncated BSR, long truncated BSR, extended short BSR, extended long BSR, extended short truncated BSR, and extended long truncated BSR.

[0323] The UE can report latency information for each PDU, PDU set, LCH, LCG, and / or data burst. In the example, the UE can report latency information for a PDU. In the example, the UE can report latency information for a PDU set. In the example, the UE can report latency information for a data burst. In the example, the UE can report latency information for a logical channel. For example, the UE can report latency information for the PDU / PDU set with the shortest remaining time. In the example, the UE can report latency information for an LCG. For example, the UE can report latency information for the PDU / PDU set that is most urgently transmitted within the LCG.

[0324] In the example, if delay information reporting is configured, delay information and buffer status of queued data can be reported via different MAC CEs.

[0325] In the example, if delay information reporting is configured, delay information and buffer status of queued data can be reported using the same extended BSR (e.g., the new BSR format).

[0326] In the example, latency information for the oldest / newest set of PDUs / PDUs (and / or the set of PDUs / PDUs with the least / highest remaining time) can be reported.

[0327] In the example, the latency information to be reported for an LCH / LCG can be determined based on the latency information of the oldest / newest set of PDUs / PDUs (and / or the set of PDUs / PDUs with the least / highest remaining time) of this LCH / LCG.

[0328] In XR services, it may be necessary to provide latency information and / or buffer size information to the gNB for reporting purposes. For traditional BSRs, buffer size information of the LCG of available data is reported via a BSR MAC CE. In the case of XR reporting formats, various mechanisms can be considered. One approach is to report latency and buffer size information together in a MAC CE. In this case, a new MAC CE (e.g., latency reporting) may need to be designed for the XR service. Alternatively, latency and buffer size information can be reported separately by two independent UL MAC CEs. In this case, buffer size information can be included in one MAC CE, while latency information can be included in another. Since buffer size and latency information can be closely linked, MAC CEs for latency information and buffer size can be reported to the gNB simultaneously. Furthermore, the relationship between two MAC CEs can be conveyed to the gNB, for example, by associating the two MAC CEs using latency / buffer size granularity of LCH, LCG, PDU, and / or PDU sets. For example, if one MAC CE reports the buffer size change for each LCH, while another MAC CE reports the remaining time for the buffer size change for each LCH, then gNB can obtain the buffer size change for each LCH and the remaining time for the buffer size change through the LCH ID.

[0329] If delay information / remaining time needs to be reported, the gNB can instruct the UE when to allow this information. This can be based on whether the UE has a delay reporting configuration configured. Alternatively, this can be achieved through a configuration parameter (e.g., delayReportEnabled), and some new triggering conditions for delay reporting can be introduced. In the case of data in the UL buffer, the UE can calculate the remaining time of the data based on the data's delay budget. By configuring this parameter (e.g., delayReportEnabled), the gNB can enable or disable the feature on a per DRB, per LCH, per LCG, per MAC entity, per cell, or per cell group basis.

[0330] In existing technologies, it should be noted that the content of delay reports, which may include data delay information / remaining time, can be time-sensitive. This means that if the delay report is transmitted too late after it is triggered / generated, the delay information included in the delay report may be outdated. For example, such as... Figure 18As described, after data arrives in the UE's buffer, the UE can trigger a delay report based on certain criteria associated with the remaining time of the data, delay budget, and / or elapsed time. After triggering the delay report, the UE can wait for UL authorization to generate / transmit the delay report. However, before receiving UL authorization and / or before transmitting the delay report using UL authorization, the delay information / remaining time of the data included / generated in the delay report may become outdated / invalid / unnecessary. In this case, transmitting the delay report is unnecessary, and doing so would result in a waste of UL resources. This disclosure provides techniques for preventing the transmission of such outdated / invalid / unnecessary delay reports.

[0331] In an exemplary embodiment, even when multiple events have triggered delayed reports, the MAC PDU contains at most one delayed report MAC CE. The delayed report MAC CE can be generated based on the latest event from a previous delayed report assembled from the MAC PDU.

[0332] After one or more data arrives at the UE's buffer (e.g., one or more data become available), the UE can trigger a Delay Report / DIR / DSR (e.g., a reporting procedure) based on certain criteria, such as the remaining time and / or delay budget of the one or more data. When a Delay Report / DIR / DSR (e.g., a reporting procedure) has been triggered and not canceled, the UE can determine whether UL-SCH resources are available for new transmissions (e.g., whether UL grants have been received and / or whether the configured grants are available) and / or whether UL-SCH resources can accommodate a Delay Report / DIR / DSR (MACCE) plus its sub-header due to logical channel priority ordering. Specifically, one or more data may be associated with one or more specific LCH / LCGs. Specific LCH / LCGs may be configured with configuration parameters for delay reporting and / or for enabling delay reporting.

[0333] In an exemplary embodiment, if a delay report becomes outdated / invalid / unnecessary, the UE can cancel the triggered delay report / DIR / DSR (e.g., reporting procedure). If the UE cancels the triggered delay report / DIR / DSR (e.g., reporting procedure) before transmission, the UE can avoid transmitting outdated / invalid / unnecessary delay reports, thereby preventing the waste of UL resources.

[0334] In an exemplary embodiment, such as Figure 19 As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, the UE can cancel the triggering of a delay report / DIR / DSR (e.g., a reporting procedure) based on one or more criteria.

[0335] In an exemplary embodiment, such as Figure 19 As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, if the second remaining time for one or more data items is shorter than or equal to a threshold, the UE can cancel the triggering of the delay report / DIR / DSR (e.g., the reporting procedure). For example, one or more data items may exhaust the delay budget. The UE can trigger a delay report based on the first remaining time for one or more data items. The remaining time (e.g., the first remaining time and / or the second remaining time) may gradually decrease over time. The second remaining time may be shorter than the first remaining time. The UE can trigger a delay report / DIR / DSR for data and / or a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or enabled for delay reporting. The UE can determine the first remaining time when triggering a delay report. The first remaining time can be at least one of the following: the difference between the delay budget and buffer time for one or more data items, the difference between the time of triggering the delay report and the delay deadline (or end time) for one or more data items, the minimum / shortest remaining time for data in one or more data items, and / or the maximum / highest / longest remaining time for data in one or more data items. The second remaining time can be at least one of the following: the difference between the delay budget and buffer time for one or more data sets, the difference between the time that triggers the delay report and the delay deadline (or end time) for one or more data sets, the minimum / shortest remaining time for data in one or more data sets, and / or the maximum / highest / longest remaining time for data in one or more data sets. The first remaining time and / or the second remaining time can be associated with the delay budget. The first remaining time and / or the second remaining time can be associated with the remaining PDB / PSDB.

[0336] In an exemplary embodiment, such as Figure 19As shown, after triggering a Delay Report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a Delay Report / DIR / DSR, if data from one or more data items has already been discarded / discarded, the UE can cancel the triggered Delay Report / DIR / DSR (e.g., a reporting procedure). The data can be one or more data items. The data can be associated with a specific LCH / LCG. The specific LCH / LCG can be configured with configuration parameters for delay reporting and / or enabled for delay reporting. The UE can trigger a Delay Report / DIR / DSR for the data and / or the specific LCH / LCG. The data can be one or more PDUs from a PDU set. The data can be data with high importance (e.g., based on PSI). If the remaining time of the data is less than or equal to a threshold, the UE can discard / discard the data. If the buffer time of the data is higher than or equal to a second threshold, the UE can discard / discard the data. The UE can discard / discard data based on the importance information of one or more data items. The importance information can be based on the PDU set importance (PSI). PSI can identify the relative importance of a PDU set compared to other PDU sets within a QoS flow.

[0337] In an exemplary embodiment, such as Figure 19 As shown, after a Delay Report / DIR / DSR (e.g., a reporting procedure) is triggered and / or before a Delay Report / DIR / DSR is generated / transmitted, if one or more data have already been (successfully) transmitted, the UE can cancel the triggered Delay Report / DIR / DSR (e.g., a reporting procedure).

[0338] In an exemplary embodiment, when a MAC PDU is transmitted and this PDU contains a delay report (MAC CE), all triggered delay reports can be cancelled. The UE can determine that one or more data items have been transmitted based on whether one or more data items are already included in the TB / PDU for transmission via UL resources. The UE can determine that one or more data items have been transmitted based on whether feedback (e.g., ACK) for one or more data items is received from the NW. The UE can determine that one or more data items have been transmitted based on whether a new transmission schedule for the (HARQ) buffer used for transmitting one or more data items is received. One or more data items can be associated with a specific LCH / LCG. The specific LCH / LCG can be configured with configuration parameters for delay reporting and / or enabling delay reporting. The UE can trigger delay reports / DIR / DSR for one or more data items and / or a specific LCH / LCG.

[0339] In an exemplary embodiment, such as Figure 19As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, if the UL authorization can accommodate all pending data available for transmission but is insufficient to accommodate an additional delay report (plus the delay report's subheader), the UE can cancel the triggering of the delay report / DIR / DSR (e.g., the reporting procedure). In an exemplary embodiment, if the UL authorization can accommodate one or more data but is insufficient to accommodate an additional delay report (plus the delay report's subheader), the UE can cancel the triggering of the delay report / DIR / DSR (e.g., the reporting procedure). One or more data may be associated with a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or enabled for delay reporting. The UE can trigger a delay report / DIR / DSR for one or more data and / or a specific LCH / LCG.

[0340] In an exemplary embodiment, such as Figure 19 As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, if a delay report / DIR / DSR has already been generated, the UE can cancel the triggering of the delay report / DIR / DSR (e.g., a reporting procedure). If a delay report has been triggered and not canceled; and / or if UL resources are available for a new transmission and / or UL resources can accommodate a delay report (plus a sub-header of the delay report), the UE can generate a delay report. The UE can generate a delay report based on a multiplexing and assembly procedure.

[0341] In an exemplary embodiment, such as Figure 19 As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, if the delay report / DIR / DSR has already been (successfully) transmitted, the UE can cancel the triggering of the delay report / DIR / DSR (e.g., the reporting procedure).

[0342] In an exemplary embodiment, such as Figure 19As shown, after triggering a Delay Report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a Delay Report / DIR / DSR, if a (MAC) PDU is transmitted and the PDU contains a delay report with a delay state up to (and including) the last event that triggered the delay report before the (MAC) PDU assembly, the UE can cancel the triggered Delay Report / DIR / DSR (e.g., a reporting procedure). In the example, when the MAC PDU is transmitted, all delay reports triggered before the MAC PDU assembly can be canceled, and this PDU contains a delay report with a delay state up to (and including) the last event that triggered the delay report before the MAC PDU assembly.

[0343] In an exemplary embodiment, such as Figure 19 As shown, after triggering a Delay Report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a Delay Report / DIR / DSR, if the UE receives an indication from the NW, the UE can cancel the triggered Delay Report / DIR / DSR (e.g., the reporting procedure). The indication can instruct the UE to cancel the triggered delay report. The indication can also instruct the UE to disable / deconfigure delay reporting.

[0344] In an exemplary embodiment, such as Figure 19 As shown, after triggering a Delay Report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a Delay Report / DIR / DSR, if the UE's MAC layer receives an indication from the UE's upper layer (e.g., the PDCP / RLC layer), the UE can cancel the triggered Delay Report / DIR / DSR (e.g., the reporting procedure). The indication may indicate an operation to discard / discard one or more data items. The indication may indicate an operation regarding the remaining time (e.g., a notification that the remaining time is less than a threshold). The indication may instruct the UE to cancel the triggered delay report. The indication may instruct the UE to disable / deconfigure delay reporting.

[0345] In an exemplary embodiment, such as Figure 19 As shown, after triggering a Delay Report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a Delay Report / DIR / DSR, if a response to the Delay Report / DIR / DSR has already been received from the NW, the UE can cancel the triggered Delay Report / DIR / DSR (e.g., a reporting procedure). The response can be received via a PDCCH addressed with a specific RNTI. The response can be feedback on the delay report from the NW (e.g., ACK / NACK).

[0346] In an exemplary embodiment, such as Figure 19As shown, if the UE resets the MAC after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, the UE can cancel the triggered delay report / DIR / DSR (e.g., a reporting procedure).

[0347] In an exemplary embodiment, such as Figure 19 As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, upon receiving an RRC (re)configuration for the delay report, the UE can cancel the triggering of the delay report / DIR / DSR (e.g., a reporting procedure).

[0348] In an exemplary embodiment, such as Figure 19 As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, if the BWP / cell (associated with the delay report) is deactivated, the UE can cancel the triggered delay report / DIR / DSR (e.g., a reporting procedure).

[0349] In an exemplary embodiment, such as Figure 19 As shown, after triggering a delay report / DIR / DSR (e.g., a reporting procedure) and / or before generating / transmitting a delay report / DIR / DSR, the UE can cancel the triggered delay report / DIR / DSR (e.g., a reporting procedure) when the time alignment timer expires.

[0350] After one or more data arrives at the UE's buffer (e.g., one or more data become available), the UE can trigger a delay report / DIR / DSR (e.g., a reporting procedure) based on certain criteria, such as the remaining time and delay budget of the one or more data. When a delay report / DIR / DSR (e.g., a reporting procedure) has been triggered and not canceled, the UE can generate a delay report / DIR / DSR (MAC CE) if UL-SCH resources are available for new transmissions (e.g., if a UL grant is received and / or the configured grant is available) and if the UL-SCH resources can accommodate the delay report / DIR / DSR (MAC CE) plus its sub-header due to logical channel priority ordering. Specifically, one or more data may be associated with one or more specific LCH / LCGs. Specific LCH / LCGs may be configured with configuration parameters for delay reporting and / or enabling delay reporting.

[0351] In an exemplary embodiment, if a delay report becomes outdated / invalid / unnecessary, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. If the generated delay report / DIR / DSR can be discarded / discarded before transmission, outdated / invalid / unnecessary delay reports will not be transmitted, thereby preventing the waste of UL resources.

[0352] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR based on one or more criteria.

[0353] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, if the second remaining time for one or more data items is less than or equal to a threshold, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. For example, one or more data items exhaust the delay budget. The UE may trigger a delay report based on the first remaining time for one or more data items. The remaining time may gradually decrease over time. The second remaining time may be shorter than the first remaining time. The UE may trigger a delay report / DIR / DSR for data and / or a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or enabled for delay reporting. The UE may determine the first remaining time when triggering a delay report. The first / second remaining time may be the difference between the delay budget and buffer time for one or more data items. The first / second remaining time can be the difference between the time that triggers the delay report and the delay deadline (or end time) of one or more data points. The first / second remaining time for one or more data points can be the minimum / shortest remaining time for the data among those data points. The first / second remaining time for one or more data points can be the maximum / highest remaining time for the data among those data points. The first / second remaining time can be associated with the delay budget. The first / second remaining time can be associated with the remaining PDB / PSDB.

[0354] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, if data from one or more data items has already been discarded / discarded, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The data may be one or more data items. The data may be associated with a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or enabled for delay reporting. The UE may trigger a delay report / DIR / DSR for the data and / or the specific LCH / LCG. The data may be one or more PDUs from a PDU set. The data may be data with high importance (e.g., based on PSI). If the remaining time of the data is less than or equal to a threshold, the UE may discard / discard the data. If the buffer time of the data is greater than or equal to a second threshold, the UE may discard / discard the data. The UE can discard / remove data based on the importance information of one or more data sets. Importance information can be based on PDU set importance (PSI). PSI identifies the relative importance of a PDU set compared to other PDU sets within a QoS flow.

[0355] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, if one or more data have been (successfully) transmitted, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The UE may determine that one or more data have been transmitted based on whether one or more data have been included in the TB / PDU for transmission via UL resources. The UE may determine that one or more data have been transmitted based on whether feedback (e.g., ACK) for one or more data has been received from the NW. The UE may determine that one or more data have been transmitted based on whether a new transmission schedule for the (HARQ) buffer used to transmit one or more data has been received. One or more data may be associated with a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or for enabling delay reporting. The UE can trigger a delay report / DIR / DSR for one or more data and / or a specific LCH / LCG.

[0356] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, if the UE receives an indication from the NW, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The indication may instruct the UE to cancel the triggered delay report. The indication may also instruct the UE to disable / unconfigure delay reports.

[0357] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, if the UE's MAC layer receives an indication from the UE's upper layer (e.g., the PDCP / RLC layer), the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The indication may indicate the operation of discarding / discarding one or more data items. The indication may indicate the operation of remaining time (e.g., notification that the remaining time is less than a threshold). The indication may indicate that the UE cancels the triggered delay report. The indication may indicate that the UE disables / unconfigures delay reporting.

[0358] In an exemplary embodiment, if the UE resets the MAC after generating the delay report / DIR / DSR and / or before transmitting the delay report / DIR / DSR, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0359] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, and after receiving an RRC (re)configuration for the delay report, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0360] In an exemplary embodiment, after the generation of the delay report / DIR / DSR and / or before the transmission of the delay report / DIR / DSR, if the BWP / cell (associated with the delay report) is deactivated, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0361] In an exemplary embodiment, after the generation of the delay report / DIR / DSR and / or before the transmission of the delay report / DIR / DSR, when the time alignment timer expires, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0362] After one or more data arrives at the UE's buffer (e.g., one or more data become available), the UE can trigger a delay report / DIR / DSR (e.g., a reporting procedure) based on certain criteria, such as the remaining time and delay budget of the one or more data. When a delay report / DIR / DSR (e.g., a reporting procedure) has been triggered and not canceled, the UE can generate a delay report / DIR / DSR (MAC CE) if UL-SCH resources are available for new transmissions (e.g., if a UL grant is received and / or a configured grant is available) and UL-SCH resources can accommodate the delay report / DIR / DSR (MAC CE) plus its sub-header due to logical channel priority ordering. The UE can transmit the delay report / DIR / DSR (MAC CE) via UL-SCH resources. Specifically, one or more data may be associated with one or more specific LCH / LCGs. Specific LCH / LCGs may be configured with configuration parameters for delay reporting and / or enabling delay reporting.

[0363] In an exemplary embodiment, if a delay report becomes outdated / invalid / unnecessary, the UE can refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. If the buffer used for transmitting the TB / SDU / PDU containing the delay report / DIR / DSR can be refreshed, waste of UL resources can be prevented.

[0364] In an exemplary embodiment, after the transmission delay report / DIR / DSR, the UE may refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR based on one or more criteria.

[0365] In an exemplary embodiment, after a transmission delay report / DIR / DSR, if the second remaining time for one or more data items is shorter than or equal to a threshold, the UE may refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. For example, one or more data items may have exhausted their delay budget. The UE may trigger a delay report based on the first remaining time for one or more data items. The remaining time may gradually decrease over time. The second remaining time may be shorter than the first remaining time. The UE may trigger a delay report / DIR / DSR for data and / or a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or enabled for delay reporting. The UE may determine the first remaining time when triggering a delay report. The first / second remaining time may be the difference between the delay budget and buffer time for one or more data items. The first / second remaining time may be the difference between the time the delay report is triggered and the delay deadline (or end time) for one or more data items. The first / second remaining time for one or more data items may be the minimum / shortest remaining time for the data in one or more data items. The first / second remaining time for one or more data items may be the maximum / highest remaining time for the data in one or more data items. The first / second remaining time can be associated with the delay budget. The first / second remaining time can be associated with the remaining PDB / PSDB.

[0366] In an exemplary embodiment, after a transmission delay report / DIR / DSR, if data from one or more data sets has been discarded, the UE may refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The data may be one or more data sets. The data may be associated with a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or enabling delay reporting. The UE may trigger a delay report / DIR / DSR for the data and / or the specific LCH / LCG. The data may be one or more PDUs from a PDU set. The data may be data with high importance (e.g., based on PSI). If the remaining time of the data is less than or equal to a threshold, the UE may discard / discard the data. If the buffer time of the data is greater than or equal to a second threshold, the UE may discard / discard the data. The UE may discard / discard data based on importance information for one or more data sets. The importance information may be based on PDU set importance (PSI). PSI can identify the relative importance of a PDU set compared to other PDU sets within a QoS flow.

[0367] In an exemplary embodiment, after a transmission delay report / DIR / DSR, if one or more data items have been (successfully) transmitted, the UE may refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The UE may determine that one or more data items have been transmitted based on whether they are included in the TB / PDU for transmission via UL resources. The UE may determine that one or more data items have been transmitted based on whether feedback (e.g., ACK) for one or more data items has been received from the NW. The UE may determine that one or more data items have been transmitted based on whether a new transmission schedule for the (HARQ) buffer used for transmitting one or more data items has been received. One or more data items may be associated with a specific LCH / LCG. The specific LCH / LCG may be configured with configuration parameters for delay reporting and / or enabling delay reporting. The UE may trigger a delay report / DIR / DSR for one or more data items and / or a specific LCH / LCG.

[0368] In an exemplary embodiment, after a transmission delay report / DIR / DSR, if the UE receives an indication from the NW, the UE can refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The indication may instruct the UE to cancel the triggered delay report. The indication may also instruct the UE to disable / deconfigure delay reporting.

[0369] In an exemplary embodiment, after a transmission delay report / DIR / DSR, if the UE's MAC layer receives an indication from the UE's upper layer (e.g., PDCP / RLC layer), the UE can refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The indication may indicate an operation to discard / discard one or more data items. The indication may indicate an operation regarding the remaining time (e.g., notification that the remaining time is less than a threshold). The indication may indicate that the UE cancels the triggered delay report. The indication may indicate that the UE disables / unconfigures delay reporting.

[0370] In an exemplary embodiment, if the UE resets the MAC after the transmission delay report / DIR / DSR, the UE can refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0371] In an exemplary embodiment, after generating a delay report / DIR / DSR and / or before transmitting a delay report / DIR / DSR, and after receiving an RRC (re)configuration for the delay report, the UE may discard / discard the generated delay report / DIR / DSR and / or discard / discard the TB / SDU / PDU containing the delay report / DIR / DSR and / or refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0372] In an exemplary embodiment, after a transmission delay report / DIR / DSR, if the BWP / cell (associated with the delay report) is deactivated, the UE can refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0373] In an exemplary embodiment, after the transmission delay report / DIR / DSR, when the time alignment timer expires, the UE may refresh the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR.

[0374] After one or more data arrives at the UE's buffer (e.g., one or more data become available), the UE can trigger a delay report / DIR / DSR (e.g., a reporting procedure) based on certain criteria, such as the remaining time and delay budget of the one or more data. When a delay report / DIR / DSR (e.g., a reporting procedure) has been triggered and not canceled, the UE can generate a delay report / DIR / DSR (MAC CE) if UL-SCH resources are available for new transmissions (e.g., if a UL grant is received and / or a configured grant is available) and UL-SCH resources can accommodate the delay report / DIR / DSR (MAC CE) plus its sub-header due to logical channel priority ordering. The UE can transmit the delay report / DIR / DSR (MAC CE) via UL-SCH resources. Specifically, one or more data may be associated with one or more specific LCH / LCGs. Specific LCH / LCGs may be configured with configuration parameters for delay reporting and / or enabling delay reporting.

[0375] In an exemplary embodiment, the UE may include time information (e.g., the absolute time / UTC time / deadline of the delay report) in the delay report. When the NW receives a delay report with time information, the NW may be able to understand the timing of triggering / generating / transmitting the delay report based on the time information. The NW may be able to understand the start time / end time / deadline of the delay report based on the time information. The NW may be able to understand the start time / end time / deadline of one or more dates based on the time information. The NW may determine whether the delay report is invalid / outdated / unnecessary based on the time information.

[0376] In an exemplary embodiment, such as Figure 20 As shown, the UE can include time information in the Delay Report / DIR / DSR (MAC CE) for transmission. The fields in the Delay Report / DIR / DSR (MAC CE) can indicate time information. The UE can include time information in the first type of Delay Report / DIR / DSR (MAC CE). The UE can choose not to include time information in the second type of Delay Report / DIR / DSR (MAC CE).

[0377] Time information can differ from remaining time / delay information. Time information can be a timestamp (e.g., YYMMDDhhmmss). Timestamps can be based on configuration parameters (e.g., locationTimestamp). Time information can be UTC time. Time information can be absolute time. Time information can indicate the time when a delay report is triggered / generated / transmitted. Time information can indicate the time when remaining time / delay information (included in the delay report) is determined. Time information can indicate the start time of a delay report. Time information can indicate the end time of a delay report. Time information can indicate the deadline for a delay report. Time information can indicate the deadline for one or more data items.

[0378] Time information can indicate the time when the (first / last) data in one or more data sets arrives in the buffer. Data in one or more data sets can be the first / last data to arrive in the buffer. Data in one or more data sets can be data with the minimum / shortest remaining time. Data in one or more data sets can be data with the minimum / shortest delay budget. Data in one or more data sets can be data with the minimum / shortest delay deadline. Data in one or more data sets can be data with the maximum / highest remaining time. Data in one or more data sets can be data with the maximum / highest delay budget. Data in one or more data sets can be data with the maximum / highest delay deadline.

[0379] Time information can indicate the start time (for transmission) of one or more data items. The start time can be the arrival time of the first / last data item among one or more data items. The start time can be the arrival time of data with the minimum / shortest remaining time. The start time can be the arrival time of data with the minimum / shortest delay budget. The start time can be the arrival time of data with the minimum / shortest delay deadline. The start time can be the arrival time of data with the maximum / highest remaining time. The start time can be the arrival time of data with the maximum / highest delay budget. The start time can be the arrival time of data with the maximum / highest delay deadline.

[0380] Time information can indicate the end time (for transmission) of one or more data items. The end time can be the arrival time of the first / last data item among one or more data items plus a delay budget. The end time can be the arrival time of the data item with the least / shortest remaining time plus a delay budget. The end time can be the arrival time of the data item with the most / highest remaining time plus a delay budget.

[0381] After one or more data arrives at the UE's buffer (e.g., one or more data become available), the UE can trigger a delay report / DIR / DSR (e.g., a reporting procedure) based on certain criteria, such as the remaining time and delay budget of the one or more data. When a delay report / DIR / DSR (e.g., a reporting procedure) has been triggered and not canceled, the UE can generate a delay report / DIR / DSR (MAC CE) if UL-SCH resources are available for new transmissions (e.g., if a UL grant is received and / or a configured grant is available) and UL-SCH resources can accommodate the delay report / DIR / DSR (MAC CE) plus its sub-header due to logical channel priority ordering. The UE can transmit the delay report / DIR / DSR (MAC CE) via UL-SCH resources. Specifically, one or more data may be associated with one or more specific LCH / LCGs. Specific LCH / LCGs may be configured with configuration parameters for delay reporting and / or enabling delay reporting.

[0382] In an exemplary embodiment, the UE may use a (validity) timer to determine whether a delay report is outdated / invalid / unnecessary.

[0383] In an exemplary embodiment, such as Figure 21As shown, when a delay report / DIR / DSR is triggered / generated / transmitted, the UE can (re)start a (validity) timer. If the (validity) timer expires, the UE can cancel the triggered delay report / DIR / DSR (e.g., reporting procedure). If the (validity) timer expires, the UE can discard / abandon the generated delay report / DIR / DSR and / or discard / abandon the TB / SDU / PDU containing the delay report / DIR / DSR. If the (validity) timer expires, the UE can flush the (HARQ) buffer associated with the TB / SDU / PDU containing the delay report / DIR / DSR. The UE can trigger / generate / transmit a second delay report in response to the expiration of the (validity) timer. The UE can trigger a scheduling request in response to the expiration of the (validity) timer.

[0384] The (Validity) timer can be used to determine whether a delay report is outdated / invalid / unnecessary. When the (Validity) timer is running, the UE can consider the triggered / generated / transmitted delay report to be valid.

[0385] When / after a delay report is triggered (e.g., a reporting procedure), the UE can start or restart the (validity) timer.

[0386] When / after generating a delay report (MAC CE), the UE can start or restart the (validity) timer. The UE can generate a delay report if it has already been triggered and not canceled; and / or if UL resources are available for new transmissions and / or UL resources can accommodate the delay report (plus the delay report's sub-header). The UE can generate the delay report based on the multiplexing and assembly procedure.

[0387] During / after a delay report is transmitted, the UE can start or restart (validate) a timer. During / after a MAC PDU is transmitted, the UE can start or restart (validate) a timer, and this PDU contains a delay report (MAC CE). The UE can determine that one or more data items have been transmitted based on whether one or more data items are already included in the TB / PDU for transmission via UL resources. The UE can determine that one or more data items have been transmitted based on whether feedback (e.g., ACK) for one or more data items is received from the NW. The UE can determine that one or more data items have been transmitted based on whether a new transmission schedule for the (HARQ) buffer used for transmitting one or more data items is received. One or more data items can be associated with a specific LCH / LCG. A specific LCH / LCG can be configured with configuration parameters for delay reporting and / or enabling delay reporting. The UE can trigger a delay report / DIR / DSR for one or more data items and / or a specific LCH / LCG.

[0388] After determining that the triggered delay report is invalid / outdated / unnecessary, the UE can stop the (validity) timer. The UE can stop the (validity) timer when / after canceling the triggered delay report. The UE can stop the (validity) timer when / after transmitting the (MAC) PDU, and the PDU contains a delay report containing the delay status up to (and including) the last event that triggered the delay report before the (MAC) PDU assembly.

[0389] When / after the UE receives an indication from the NW, the UE can stop (validate) the timer. The indication can instruct the UE to cancel triggered delay reporting. The indication can also instruct the UE to disable / unconfigure delay reporting.

[0390] The UE can stop (validate) the timer when / after the second remaining time for one or more data items is less than or equal to a threshold. The UE can trigger a delay report based on the first remaining time for one or more data items. The remaining time can gradually decrease over time. The second remaining time can be shorter than the first remaining time. The UE can trigger delay reports / DIR / DSR for data and / or a specific LCH / LCG. A specific LCH / LCG can be configured with configuration parameters for delay reporting and / or enabled for delay reporting. The UE can determine the first remaining time when triggering a delay report. The first / second remaining time can be the difference between the delay budget and buffer time for one or more data items. The first / second remaining time can be the difference between the time the delay report is triggered and the delay deadline (or end time) for one or more data items. The first / second remaining time for one or more data items can be the minimum / shortest remaining time for the data in one or more data items. The first / second remaining time for one or more data items is the maximum / highest remaining time for the data in one or more data items. The first / second remaining time can be associated with the delay budget. The first / second remaining time can be associated with the remaining PDB / PSDB.

[0391] The UE can stop the (validity) timer after / once data from one or more data sets has been discarded. Data can be one or more data sets. Data can be associated with a specific LCH / LCG. A specific LCH / LCG can be configured with configuration parameters for delay reporting and / or enabling delay reporting. The UE can trigger delay reporting / DIR / DSR for data and / or a specific LCH / LCG. Data can be one or more PDUs in a PDU set. Data can be data with high importance (e.g., based on PSI). If the remaining time of the data is less than or equal to a threshold, the UE can discard / discard the data. If the buffer time of the data is greater than or equal to a second threshold, the UE can discard / discard the data. The UE can discard / discard data based on the importance information of one or more data sets. Importance information can be based on PDU set importance (PSI). PSI can identify the relative importance of a PDU set compared to other PDU sets within a QoS flow.

[0392] The UE can stop the (validity) timer after one or more data have been transmitted.

[0393] The UE can stop the (validity) timer when / after generating a delay report. The UE can generate a delay report if it has been triggered and not canceled; and / or if UL resources are available for new transmissions and / or UL resources can accommodate a delay report (plus a sub-header for the delay report). The UE can generate a delay report based on a multiplexing and assembly procedure.

[0394] The UE can stop (validate) the timer during / after the transmission of a delay report. The UE can stop (validate) the timer during / after the transmission of a MAC PDU, and this PDU contains a delay report (MAC CE). The UE can determine that one or more data items have been transmitted based on whether one or more data items are already included in the TB / PDU for transmission via UL resources. The UE can determine that one or more data items have been transmitted based on whether feedback (e.g., ACK) for one or more data items has been received from the NW. The UE can determine that one or more data items have been transmitted based on whether a new transmission schedule for the (HARQ) buffer used for transmitting one or more data items has been received. One or more data items can be associated with a specific LCH / LCG. A specific LCH / LCG can be configured with configuration parameters for delay reporting and / or enabling delay reporting. The UE can trigger a delay report / DIR / DSR for one or more data items and / or a specific LCH / LCG.

[0395] When / after the UE receives an indication from the NW, the UE can stop (validate) the timer. The indication can instruct the UE to cancel triggered delay reporting. The indication can also instruct the UE to disable / unconfigure delay reporting.

[0396] When / after the UE's MAC layer receives an indication from the UE's upper layer (e.g., PDCP / RLC layer), the UE can stop the (validity) timer. The indication can indicate the discarding / discarding of one or more data items. The indication can indicate the operation on the remaining time (e.g., notification that the remaining time is less than a threshold). The indication can indicate that the UE cancels triggered delay reporting. The indication can indicate that the UE disables / unconfigures delay reporting.

[0397] When / after the UE resets the MAC, the UE can stop the (validity) timer.

[0398] Upon receiving the RRC (re)configuration for delay reporting, the UE can stop the (validity) timer.

[0399] If the BWP / cell (associated with delay reporting) is deactivated, the UE can stop the (validity) timer.

[0400] When the time alignment timer expires, the UE can stop the (validity) timer.

[0401] After one or more data arrives at the UE's buffer (e.g., one or more data become available), the UE can trigger a delay report / DIR / DSR (e.g., a reporting procedure) based on certain criteria, such as the remaining time and delay budget of the one or more data. When a delay report / DIR / DSR (e.g., a reporting procedure) has been triggered and not canceled, the UE can generate a delay report / DIR / DSR (MAC CE) if UL-SCH resources are available for new transmissions (e.g., if a UL grant is received and / or a configured grant is available) and UL-SCH resources can accommodate the delay report / DIR / DSR (MAC CE) plus its sub-header due to logical channel priority ordering. The UE can transmit the delay report / DIR / DSR (MAC CE) via UL-SCH resources. Specifically, one or more data may be associated with one or more specific LCH / LCGs. Specific LCH / LCGs may be configured with configuration parameters for delay reporting and / or enabling delay reporting.

[0402] In an exemplary embodiment, the UE / NW may disable retransmission of delay reports to avoid retransmission delays. If a new transmission of a delay report fails, it is expected that the retransmission of the delay report will be delayed. Delays may cause delay reports to become invalid / outdated / unnecessary.

[0403] In an exemplary embodiment, such as Figure 22As shown, for transmitting delay reports / DIR / DSR, the UE can select a HARQ process / buffer (ID) configured with HARQ mode A, HARQ mode B, no retransmission, and / or retransmission disabled. The UE can transmit delay reports / DIR / DSR via the selected HARQ process / buffer (ID). The UE can also transmit delay reports / DIR / DSR without using a HARQ process / buffer (ID) that is not configured with HARQ mode A, HARQ mode B, no retransmission, and / or retransmission disabled.

[0404] The UE can be configured with configuration parameters (e.g., uplinkHARQ mode) to set HARQmodeA or HARQmodeB according to the UL HARQ process. In the example, for transmitting delay reports / DIR / DSR, the UE can select a HARQ process / buffer (ID) configured with HARQ mode A. The UE can transmit delay reports / DIR / DSR via the selected HARQ process / buffer (ID). In the example, for transmitting delay reports / DIR / DSR, the UE can select a HARQ process / buffer (ID) configured with HARQ mode B. The UE can transmit delay reports / DIR / DSR via the selected HARQ process / buffer (ID).

[0405] In an exemplary embodiment, such as Figure 22 As shown, for the transmission delay report (DIR / DSR), the UE can select the UL resource for the new transmission. The UE can transmit the delay report (DIR / DSR) via the UL resource used for the new transmission. The UE can also transmit the delay report (DIR / DSR) without using the UL resource used for retransmission. The UL resource can be a configured grant. The UL resource can be indicated by the configured grant. The UL resource can be indicated by a PDCCH scrambled by a specific RNTI.

[0406] In some implementations, the UE can refresh the (HARQ) buffer used for transmission delay reporting (DIR / DSR) after the transmission delay report (DIR / DSR).

[0407] In some implementations, after transmitting the delay report / DIR / DSR, the UE may discard / discard the delay report / DIR / DSR and / or the TB / PDU / SDU containing the delay report / DIR / DSR.

[0408] After one or more data arrives at the UE's buffer (e.g., one or more data become available), the UE can trigger a delay report / DIR / DSR (e.g., a reporting procedure) based on certain criteria, such as the remaining time and delay budget of the one or more data. When a delay report / DIR / DSR (e.g., a reporting procedure) has been triggered and not canceled, the UE can generate a delay report / DIR / DSR (MAC CE) if UL-SCH resources are available for new transmissions (e.g., if a UL grant is received and / or a configured grant is available) and UL-SCH resources can accommodate the delay report / DIR / DSR (MAC CE) plus its sub-header due to logical channel priority ordering. The UE can transmit the delay report / DIR / DSR (MAC CE) via UL-SCH resources. Specifically, one or more data may be associated with one or more specific LCH / LCGs. Specific LCH / LCGs may be configured with configuration parameters for delay reporting and / or enabling delay reporting.

[0409] In an exemplary embodiment, the UE may trigger a scheduling request (SR) to notify the NW that the UE has triggered a transmission delay report, or to inform the NW that a scheduling UL authorization is required.

[0410] In an exemplary embodiment, such as Figure 23 As shown, the UE can trigger an SR when / after a delay report is triggered. In the example, if the delay reporting procedure determines that at least one delay report has been triggered and not canceled, the UE can trigger the SR if the configuration parameter of the SR used for delay reporting (e.g., delayreportSR) is configured with an enabled value. The configuration parameter of the SR used for delay reporting can be configured in the delay reporting configuration.

[0411] In the example, if the delay reporting procedure determines that at least one delay report has been triggered and not canceled, the UE can trigger an SR if no UL-SCH resource is available for the new transmission.

[0412] In the example, if the delay reporting procedure determines that at least one delay report has been triggered and not canceled, the UE can trigger an SR if the available UL-SCH resources are insufficient to accommodate the delay report (plus its sub-header) due to logical channel priority ordering.

[0413] In the example, if the delay reporting procedure determines that at least one delay report has been triggered and not canceled, the UE can trigger an SR if the UE is configured with a configured uplink grant and the delay report is triggered for a logical channel where logicalChannelSR-Mask is set to false.

[0414] In the example, if the delay reporting procedure determines that at least one delay report has been triggered and not canceled, the UE can trigger an SR if the UL-SCH resources available for new transmission do not meet the LCP mapping constraints configured for the logical channel that triggered the delay report.

[0415] In the example, when / after the UE triggers a delay report, the UE can trigger an SR when the (validity) timer expires.

[0416] In an exemplary embodiment, an SR may be associated with a specific SR configuration used for delay reporting. In the example, an SR may be associated with a specific SR ID used for delay reporting.

[0417] In an exemplary embodiment, such as Figure 24 As shown, the wireless device can trigger a delay report based on the remaining time associated with a delay budget for one or more data points. The wireless device can cancel the triggered delay report in response to one or more conditions being met before the delay report is transmitted.

[0418] According to an exemplary embodiment, one or more conditions may include at least one of the following: remaining time is less than or equal to a threshold; one or more data are discarded / discarded; one or more data are transmitted; (validity) timer expires; and / or a delay report is generated.

[0419] According to an exemplary embodiment, the wireless device may trigger a second delay report. The wireless device may transmit the second delay report via UL resources in response to the second delay report not being canceled.

[0420] According to an exemplary embodiment, the wireless device may transmit a UL signal without a delay report in response to the cancellation of a second delay report.

[0421] According to an exemplary embodiment, the wireless device may transmit a UL signal with a delay report in response to the second delay report not being canceled.

[0422] In an exemplary embodiment, such as Figure 25 As shown, the wireless device can trigger a delay report based on the remaining time associated with a delay budget for one or more data items. The wireless device can cancel the triggered delay report in response to at least one of the following: the remaining time is less than or equal to a threshold; one or more data items are discarded / discarded; one or more data items are transmitted; a delay report is generated; a delay report is transmitted; and / or a (validity) timer expires.

[0423] According to an exemplary embodiment, the wireless device may cancel a triggered buffer status report (BSR) in response to at least one of the following: the triggered delay report is canceled; and / or the triggered delay report is invalidated.

[0424] According to an exemplary embodiment, the wireless device may cancel a triggered buffer status report (BSR) without responding to at least one of the following: the triggered delay report is canceled; and / or the triggered delay report is invalid.

[0425] According to an exemplary embodiment, the wireless device may transmit the BSR via UL resources in response to the BSR not being cancelled.

[0426] In an exemplary embodiment, such as Figure 26 As shown, the wireless device can determine a first value of the remaining time for one or more data items at a first time, where the remaining time is the difference between the latency budget and buffer time for the one or more data items. The wireless device can trigger a latency report based on the first value of the remaining time, where the latency report indicates the first value. The wireless device can determine a second value of the remaining time for the one or more data items at a second time, where the second time occurs after the first time. The wireless device can cancel the triggered latency report in response to determining that the second value of the remaining time is shorter than or equal to a threshold.

[0427] In an exemplary embodiment, the wireless device may trigger a latency report based on the remaining time associated with a latency budget for one or more data points. The wireless device may trigger a buffer status report (BSR). The wireless device may cancel the triggered latency report in response to determining that the triggered latency report is invalid. The wireless device may also cancel the triggered BSR without responding to the determination.

[0428] According to an exemplary embodiment, the wireless device may discard / discard one or more data points in response to the remaining time of one or more data points being less than or equal to a first threshold. According to an exemplary embodiment, the wireless device may discard / discard one or more data points in response to the buffer time of one or more data points being greater than or equal to a second threshold. According to an exemplary embodiment, the wireless device may discard / discard one or more data points in response to the unsuccessful transmission of multiple (or all) of one or more data points. According to an exemplary embodiment, the wireless device may discard / discard one or more data points in response to the successful transmission of multiple (or all) of one or more data points. According to an exemplary embodiment, the wireless device may discard / discard one or more data points based on importance information of one or more data points.

[0429] According to an exemplary embodiment, the importance information is based on PDU set importance (PSI). According to an exemplary embodiment, PSI identifies the relative importance of a PDU set compared to other PDU sets within a QoS flow.

[0430] According to an exemplary embodiment, one or more data are transmitted based on at least one of the following: the UL authorization can accommodate one or more data, but is insufficient to accommodate a delay report (plus a sub-header of the delay report); and / or the wireless device receives a response / feedback / ACK for one or more (or all) data.

[0431] According to an exemplary embodiment, the wireless device may generate a delay report in response to at least one of the following: a delay report has been triggered and not canceled; UL resources are available for a new transmission; and / or UL resources can accommodate a delay report (plus a sub-header of the delay report).

[0432] According to an exemplary embodiment, a delay report is transmitted in response to at least one of the following: transmitting a PDU, wherein the PDU contains a delay report containing a delay state up to (and including) the last event that triggered the delay report before the PDU is assembled; and / or the wireless device receives a response / feedback / ACK for the delay report.

[0433] According to an exemplary embodiment, the (validity) timer is used to determine whether a delay report is valid or invalid.

[0434] According to an exemplary embodiment, the wireless device may start or restart a (validity) timer in response to triggering / generating / transmission delay reports.

[0435] According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to canceling a triggered delay report. According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to determining that a triggered delay report is invalid. According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to one or more data items having a remaining time less than or equal to a threshold. According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to discarding / discarding one or more data items. According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to transmitting one or more data items. According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to generating a delay report. According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to transmitting a delay report. According to an exemplary embodiment, the wireless device may stop (validate) the timer in response to receiving a response / feedback / ACK for a delay report.

[0436] According to an exemplary embodiment, the wireless device may trigger / generate / transmit a second delay report in response to the expiration of a (validity) timer.

[0437] According to an exemplary embodiment, a threshold is used to determine whether the remaining time for one or more data items is shorter than the delay budget. According to an exemplary embodiment, the threshold is based on the delay budget (value / unit). According to an exemplary embodiment, the threshold is based on a specific value, where the specific value is zero (0). According to an exemplary embodiment, the threshold is indicated via a (RRC) configuration parameter.

[0438] According to an exemplary embodiment, the threshold is indicated by a delay report configuration. According to an exemplary embodiment, the threshold is indicated by a logical channel configuration.

[0439] According to an exemplary embodiment, the delay report is referred to as a Delay Status Report (DSR) or a Delay Information Report (DIR).

[0440] According to an exemplary embodiment, a delay report is used to provide information about the remaining time for one or more data items. According to an exemplary embodiment, a delay report is used to provide information about the remaining time and amount of data for one or more data items.

[0441] According to an exemplary embodiment, the delay report includes the remaining time for one or more data points. According to an exemplary embodiment, the delay report includes time information.

[0442] According to an exemplary embodiment, the delay report is transmitted via MAC CE. According to an exemplary embodiment, the delay report is transmitted by a Buffer Status Report (BSR).

[0443] According to an exemplary embodiment, the BSR is at least one of a short BSR, a long BSR, a regular BSR, a periodic BSR, a short truncated BSR, a long truncated BSR, an extended short BSR, an extended long BSR, an extended short truncated BSR, and an extended long truncated BSR.

[0444] According to an exemplary embodiment, the wireless device can determine the remaining time included in the delay report when triggering / generating / transmitting the delay report.

[0445] According to an exemplary embodiment, the remaining time is determined based on the timing of triggering / generating / transmitting a delay report. According to an exemplary embodiment, the remaining time is the difference between the delay budget and buffer time for one or more data items. According to an exemplary embodiment, the remaining time is the difference between the time of transmitting / triggering / generating a delay report and the delay deadline (or end time) for one or more data items. According to an exemplary embodiment, the remaining time for one or more data items is the minimum / shortest remaining time for the data among the one or more data items.

[0446] According to an exemplary embodiment, the remaining time for one or more data items is the maximum / highest remaining time for the data among the one or more data items. According to an exemplary embodiment, the remaining time is associated with a delay budget. According to an exemplary embodiment, the remaining time is associated with the remaining PDB. According to an exemplary embodiment, the remaining time is associated with the remaining PSDB.

[0447] According to an exemplary embodiment, one or more data are UL data or DL ​​data. According to an exemplary embodiment, one or more data are at least one of one or more PDUs, one or more PDU sets, one or more SDUs, one or more IP packets, and one or more data bursts. According to an exemplary embodiment, a PDU is at least one of SDAP PDU, PDCP PDU, RLC PDU, and MAC PDU. According to an exemplary embodiment, an SDU is at least one of SDAP SDU, PDCP SDU, RLC SDU, MAC SDU, and PHY SDU. According to an exemplary embodiment, a PDU set includes one or more PDUs carrying a payload of an information unit generated at the application level. According to an exemplary embodiment, a data burst is a collection of multiple PDUs generated and transmitted by an application within a short time period. According to an exemplary embodiment, a data burst includes one or more PDU sets.

[0448] According to an exemplary embodiment, the delay budget is the PDU set delay budget (PSDB), where PDSB is the time between the reception of the first PDU in the PDU set and the successful delivery of the last arriving PDU. According to an exemplary embodiment, the delay budget is the packet delay budget (PDB), where the PDB defines an upper limit on the time a packet is delayed between the UE and the N6 termination point at the UPF.

[0449] According to an exemplary embodiment, the buffering time for one or more data is the duration during which one or more data arrives in the buffer / is stored in the buffer but has not yet been transmitted.

[0450] In an exemplary embodiment, such as Figure 27 As shown, the wireless device can trigger a delay report based on the remaining time of one or more data, wherein the delay report includes the remaining time and time information.

[0451] In an exemplary embodiment, such as Figure 28 As shown, the wireless device can determine the remaining time for one or more data items, where the remaining time is the difference between the latency budget and buffer time for the one or more data items in a first time. The wireless device can trigger a latency report based on the remaining time. The wireless device can generate / transmit a latency report including the remaining time and time information, where the time information indicates the time at which the latency report was triggered / generated / transmitted.

[0452] According to an exemplary embodiment, the time information indicates the time at which a delay report is triggered / generated / transmitted. According to an exemplary embodiment, the time information indicates the time at which data from one or more data sets arrives in the buffer. According to an exemplary embodiment, the time information indicates the time remaining.

[0453] According to an exemplary embodiment, the data arriving in one or more data sets is the first / last data to arrive in the buffer. According to an exemplary embodiment, the data in one or more data sets is the data with the least / shortest remaining time. According to an exemplary embodiment, the data in one or more data sets is the data with the most / highest remaining time. According to an exemplary embodiment, time information indicates the start time (for transmission) of one or more data sets.

[0454] According to an exemplary embodiment, the start time is the arrival time of the first / last data among one or more data sets. According to an exemplary embodiment, the start time is the arrival time of the data with the least / shortest remaining time. According to an exemplary embodiment, the start time is the arrival time of the data with the most / highest remaining time.

[0455] According to an exemplary embodiment, the time information indicates the end time (for transmission) of one or more data. According to an exemplary embodiment, the end time is the arrival time of the first / last data among the one or more data, plus a delay budget. According to an exemplary embodiment, the end time is the arrival time of the data with the least / shortest remaining time, plus a delay budget. According to an exemplary embodiment, the end time is the arrival time of the data with the most / highest remaining time, plus a delay budget.

[0456] According to an exemplary embodiment, the time information is based on a timestamp. According to an exemplary embodiment, the time information is based on UTC time. According to an exemplary embodiment, the time information is based on absolute time.

[0457] Figure 29 An example embodiment is shown. At 2901, the wireless device triggers a delay report based on the remaining time associated with the delay budget for one or more data points. At 2902, the wireless device cancels the triggered delay report in response to one or more conditions being met before the transmission delay report.

Claims

1. A method comprising: Configuration parameters are received by the wireless device, the configuration parameters indicating the threshold for Delay Status Report (DSR) for Logical Channel Group (LCG); For the LCG, the DSR is triggered based on the shortest remaining time of one or more remaining times of one or more data units associated with the LCG being shorter than the threshold, wherein each of the one or more remaining times indicates when to discard the corresponding data unit in the one or more data units; and The triggered DSR is cancelled in response to at least one of the following: Discard all or more data units associated with the DSR; The transmission includes a MAC protocol data unit (PDU) comprising a DSR (Media Access Control) MAC control element (CE), wherein the DSR MAC CE includes delay information for all one or more data units associated with the DSR; Transmit all one or more data units associated with the DSR via uplink resources, wherein the uplink resources do not include a DSR MAC CE; or Reset the MAC entity of the wireless device.

2. A method comprising: Delay Status Report (DSR) of a Logical Channel Group (LCG) associated with one or more data units is triggered by a wireless device. as well as The DSR is canceled in response to the discarding of one or more data units.

3. The method of claim 2, further comprising receiving configuration parameters for the DSR, wherein the triggering is based on the configuration parameters.

4. The method of claim 3, wherein the configuration parameter indicates a threshold for the DSR.

5. The method according to any one of claims 3 to 4, further comprising receiving a message including the configuration parameters.

6. The method according to any one of claims 2 to 5, wherein the triggering is directed at the LCG.

7. The method according to any one of claims 2 to 6, wherein the triggering is based on the remaining time of one or more remaining times of the one or more data units.

8. The method according to any one of claims 2 to 7, wherein the triggering is based on the remaining time of the data unit being the shortest remaining time among one or more remaining times of the one or more data units.

9. The method according to any one of claims 2 to 8, wherein the triggering is based on the shortest remaining time of one or more remaining times of the one or more data units being shorter than a threshold.

10. The method of claim 9, wherein each of the one or more remaining times indicates when a corresponding data unit in the one or more data units is discarded.

11. The method according to any one of claims 1 to 10, wherein the cancellation of the triggered DSR is a Media Access Control (MAC) control element (CE) further responsive to transmitting delay information indicating the one or more data units.

12. The method of any one of claims 1 to 11, wherein canceling the triggered DSR is further in response to transmitting the one or more data units via uplink resources, wherein the uplink resources do not include a MAC CE.

13. The method of any one of claims 1 to 12, wherein canceling the triggered DSR is further in response to resetting the MAC entity of the wireless device.

14. The method according to any one of claims 1 to 13, wherein the MAC CE is a DSR MAC CE.

15. The method according to any one of claims 1 to 14, wherein transmitting the MAC CE comprises transmitting a MAC protocol data unit (PDU) including the MAC CE.

16. The method according to any one of claims 1 to 15, wherein the one or more data units comprise one or more Service Data Units (SDUs).

17. The method according to any one of claims 1 to 16, wherein the one or more data units are all of the one or more data units associated with the LCG.

18. The method according to any one of claims 1 to 17, wherein the one or more data units are all of the one or more data units associated with the DSR.

19. The method according to any one of claims 1 to 18, wherein the one or more data units are associated with the DSR.

20. The method according to any one of claims 1 to 19, wherein the one or more data units associated with the DSR are based on: The DSR is triggered in response to the LCG; and The one or more data units are associated with the LCG.

21. The method according to any one of claims 1 to 20, further comprising triggering a buffer status report (BSR) for the LCG.

22. The method according to any one of claims 1 to 21, further comprising transmitting a BSR MAC CE in response to triggering the BSR.

23. The method according to any one of claims 1 to 22, wherein the BSR MAC CE indicates buffer size information of the LCG.

24. The method according to any one of claims 1 to 23, wherein the BSR is used to provide data volume information to the base station.

25. The method of any one of claims 1 to 24, wherein the triggered DSR is a pending DSR prior to the cancellation.

26. The method according to any one of claims 1 to 25, wherein the DSR is used to provide delay information to the base station.

27. The method according to any one of claims 1 to 26, wherein the DSR is used to provide the base station with the delay information of the LCG.

28. The method according to any one of claims 1 to 27, wherein the MAC CE comprises a DSR MAC CE and a subheader of the DSR MAC CE.

29. The method according to any one of claims 1 to 28, wherein the DSR MAC CE further includes a subheader of the DSR MAC CE.

30. The method according to any one of claims 1 to 29, wherein the MAC CE indicates at least one of the following: The identifier of the LCG; The remaining time of the LCG; or The buffer size of the LCG.

31. The method according to any one of claims 1 to 30, wherein the DSR MAC CE indicates at least one of the following: The identifier of the LCG; The remaining time of the LCG; or The buffer size of the LCG.

32. The method according to any one of claims 1 to 31, wherein the discarding comprises discarding a data unit in the one or more data units based on at least one of the following: The remaining time of the data unit; The timer associated with the data unit expires; The data unit is associated with a set of protocol data units; or Protocol Data Unit Set Importance (PSI) configuration.

33. The method according to any one of claims 1 to 32, wherein the cancellation of the triggered DSR occurs after the transmission of the one or more data units.

34. The method according to any one of claims 1 to 33, wherein the cancellation of the triggered DSR occurs after the transmission of the MAC protocol data unit (PDU) including the Media Access Control (MAC) control element (CE).

35. The method according to any one of claims 1 to 34, wherein the cancellation of the triggered DSR occurs after the transmission of the MAC Protocol Data Unit (PDU) including the DSR Media Access Control (MAC) Control Element (CE).

36. The method according to any one of claims 1 to 35, wherein the configuration parameter is a DSR configuration parameter.

37. The method according to any one of claims 1 to 36, wherein the configuration parameter is an LCG configuration parameter.

38. The method according to any one of claims 1 to 37, wherein the configuration parameter indicates an identifier of the LCG.

39. The method according to any one of claims 1 to 38, wherein the configuration parameter indicates the threshold.

40. The method of any one of claims 1 to 39, wherein the threshold is associated with a remaining time threshold.

41. The method according to any one of claims 1 to 40, wherein the unit of the threshold is milliseconds.

42. The method according to any one of claims 1 to 41, wherein the LCG comprises one or more logical channels.

43. The method according to any one of claims 1 to 42, wherein the one or more data units comprise one or more uplink data units.

44. The method according to any one of claims 1 to 43, wherein the one or more data units comprise one or more Service Data Units (SDUs).

45. The method according to any one of claims 1 to 44, wherein the one or more data units comprise one or more protocol data units (PDUs).

46. ​​The method according to any one of claims 1 to 45, wherein the one or more data units comprise one or more Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs).

47. The method according to any one of claims 1 to 46, wherein the one or more data units comprise one or more Media Access Control (MAC) Service Data Units (SDUs).

48. The method according to any one of claims 1 to 47, wherein the delay information is associated with the LCG.

49. The method according to any one of claims 1 to 48, wherein the delay information includes the remaining time of the LCG.

50. The method according to any one of claims 1 to 49, wherein the delay information includes the buffer size of the LCG.

51. A wireless device, comprising: One or more processors; as well as A memory for storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method according to any one of claims 1 to 50.

52. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to perform the method according to any one of claims 1 to 50.

Images