Configured grant hybrid automatic repeat request process

Abstract

A wireless device receives a configured grant (CG) configuration indicating a periodicity of the CG configuration and a number of consecutive slots of transmission occasions within the periodicity. The wireless device transmits uplink data via a first transmission occasion of the transmission occasions. A hybrid automatic repeat request (HARQ) process index (ID) for the transmission of the uplink data is based on at least one of the number of consecutive slots of transmission occasions within the periodicity or an offset of the first transmission occasion within the transmission occasions.

Description

[0001] Cross-referencing related applications

[0002] This application claims priority to U.S. Provisional Application 63 / 435,936, filed December 29, 2022, which is hereby incorporated in its entirety by reference. Attached Figure Description

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

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

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

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

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

[0008] Figure 4B An example format of the MAC subheader in a Media Access Control (MAC) protocol (or packet) data unit (PDU) is shown.

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

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

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

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

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

[0014] Figure 10AThree carrier aggregation configurations with two component carriers are shown.

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

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

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

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

[0019] 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.

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

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

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

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

[0024] Figure 17 An example of an alternative to the PDU set / QoS stream / DRB mapping is shown.

[0025] Figure 18 An example of multiple configured authorized (CG) PUSCH resource timings within a single CG configuration cycle is shown.

[0026] Figure 19An example of multiple transport blocks (TBs) being transferred via a single CG time (CGO) during a CG cycle is shown.

[0027] Figure 20 An example is shown for determining the Hybrid Automatic Repeat Request (HARQ) process ID for one CGO per CG cycle and multiple CGOs per CG cycle.

[0028] Figure 21 An example of HARQ process ID determination based on the new equation is shown.

[0029] Figure 22 An example of HARQ process ID determination based on the new equation is shown.

[0030] Figure 23 An example of determining the HARQ process ID based on the HARQ process ID used for the last transmission is shown.

[0031] Figure 24 An example of HARQ process ID determination based on the HARQ process ID used for the last transmission in the same CG cycle is shown.

[0032] Figure 25 An example of determining HARQ process IDs based on a new set of HARQ process IDs is shown.

[0033] Figure 26 An example of HARQ process ID determination is shown. Detailed Implementation

[0034] 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. The embodiments of the invention are not to 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 further embodiments within the scope of this disclosure. Any figures 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.

[0035] The embodiments 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 embodiments can be applied when one or more criteria are met. Therefore, example embodiments that selectively implement the disclosed protocols can be implemented.

[0036] 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.

[0037] 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.

[0038] 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 in one or more different embodiments. 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 in one or more different embodiments. The phrase "depending on" (or equivalently "at least depending on") indicates that the phrase following the phrase "depending on" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase "adopting / using" (or equivalently "at least adopting / using") indicates that the phrase following the phrase "adopting / using" is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments.

[0039] 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.

[0040] 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 embodiment, 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.

[0041] 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.

[0042] 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 the defined interface 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 a software routine 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 functional modules.

[0043] 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 be, for example, a Public Land Mobile Network (PLMN) operated by a network operator. Figure 1A As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a radio device 106.

[0044] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs) (e.g., public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs). As part of the interface functionality, 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.

[0045] 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.

[0046] 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.

[0047] 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 ​​a donor node; Next Generation Evolved Node B (ng-eNB); 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).

[0048] 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 the cells 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.

[0049] 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 the radio signals received from the donor node to remove noise before amplifying and replaying the radio signals.

[0050] 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 coverage 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 "hot spots") 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 femtocell base stations.

[0051] The Third Generation Partnership Project (3GPP) was established in 1998 to facilitate collaboration with... Figure 1AThe mobile communication network 100 in the text provides globally standardized specifications 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). 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.

[0052] 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.

[0053] 5G-CN 152 provides UE 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of the 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 functions. 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 the interface. 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).

[0054] 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.

[0055] 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.

[0056] 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).

[0057] 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.

[0058] 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.

[0059] 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.

[0060] The gNB 160 can provide NR user plane and control plane protocol termination to UE 156 via the Uu interface. For example, the gNB 160A can provide NR user plane and control plane protocol termination to 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 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 UE 156B via the Uu interface associated with the second protocol stack.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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, SDAP 225 at gNB 220 can mark downlink packets with QoS flow indicators (QFIs), which can be observed by SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0066] 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.

[0067] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. 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.

[0068] 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.

[0069] 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.

[0070] 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.

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

[0072] 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 SDAP 225, IP packets n and n+1 are mapped to the first radio bearer 402, and IP packet m is mapped to the second radio bearer 404. The SDAP header (in...) Figure 4AData 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 the PDU of SDAP 225.

[0073] 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 (As shown in the image regarding IP packet m) 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 throughout 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.

[0074] 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.

[0075] 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. These can be used at the beginning of downlink transmissions within 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) reporting, Sounding Reference Signal (SRS) transmission, 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.

[0076] 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.

[0077] 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:

[0078] --Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level;

[0079] --Broadcast Control Channel (BCCH), which carries system information messages in the form of a Master 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;

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

[0081] --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

[0082] --Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0083] 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:

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

[0085] --Broadcast channel (BCH), which is used to carry MIBs from the BCCH;

[0086] --Downlink Shared Channel (DL-SCH), which carries downlink data and signaling messages, including SIBs from BCCH;

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

[0088] --Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0089] 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 (called L1 / L2 control channels). The set of physical channels and physical control channels defined by the NR includes, for example:

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

[0091] --Physical Downlink Shared Channel (PDSCH), which carries downlink data and signaling messages from DL-SCH and paging messages from PCH;

[0092] --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;

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

[0094] --Physical Uplink Control Channel (PUCCH), which carries the UCI, which may include HARQ acknowledgment, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

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

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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).

[0101] 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.

[0102] 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 periodically wake up (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. UE 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 via connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0103] 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.

[0104] 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 is currently camped, rather than across the entire mobile network. Mobility management mechanisms for 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).

[0105] 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 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] In NR, physical signals and physical channels (about Figure 5A and Figure 5B The data discussed can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data via F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM or M-PSK symbols) and divided into F parallel symbol streams. These F parallel symbol streams can be treated as if they were in the frequency domain and used as input to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block takes F source symbols at a time (one source symbol from each of the F parallel symbol streams) and uses each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. These F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and upsampling, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This operation produces OFDM symbols precoded by Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse processing of the OFDM symbols at the receiver can be performed using the FFT block to recover the data mapped to the source symbols.

[0110] Figure 7 An 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, each containing, for example, 14 OFDM symbols per time slot.

[0111] 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.

[0112] 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 slot or sub-time slot transmissions.

[0113] 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 8 As 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 carriers can be limited to 50MHz, 100MHz, 200MHz, and 400MHz respectively for subcarrier spacing of 15kHz, 30kHz, 60kHz, and 120kHz, where the 400MHz bandwidth can be set based on a bandwidth limit of 400MHz per carrier.

[0114] Figure 8This 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.

[0115] NR can support wide carrier bandwidths (e.g., up to 400MHz for a subcarrier spacing of 120kHz). 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.

[0116] 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 Relays (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.

[0117] 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.

[0118] 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.

[0119] 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).

[0120] 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.

[0121] 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.

[0122] The base station can configure the BWP inactivity timer value for the UE for 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 when: (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can run the BWP inactivity timer toward its expiration (e.g., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE can switch from the active downlink BWP to the default downlink BWP.

[0123] 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).

[0124] 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.

[0125] 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 40MHz and a subcarrier spacing of 15kHz; BWP904 with a bandwidth of 10MHz and a subcarrier spacing of 15kHz; and BWP906 with a bandwidth of 20MHz and a subcarrier spacing of 60kHz. 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 9 In 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.

[0126] 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 BWPs 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 as the UE would use the timer values ​​and default downlink BWP of the primary cell.

[0127] 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.

[0128] 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).

[0129] 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.

[0130] 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).

[0131] 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).

[0132] 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 aggregated downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0133] 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 10BIn 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.

[0134] 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.

[0135] 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.

[0136] 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 contains PSS, SSS, and PBCH. The base station can periodically transmit bursts of SS / PBCH blocks.

[0137] 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 11A This 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.

[0138] 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.

[0139] 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.

[0140] 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 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.

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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.

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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).

[0151] 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.

[0152] 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 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. 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.

[0153] 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.

[0154] 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.

[0155] 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 based on the UE through a combination of RRC signaling and / or 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.

[0156] 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.

[0157] 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.

[0158] 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 channel through which it is transmitted. If a first symbol and a second symbol are transmitted on the same antenna port, a receiver can infer from the channel through which the first symbol on the antenna port is transmitted the channel (e.g., fading gain, multipath delay, etc.). 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 the channel through which the first symbol on the first antenna port is transmitted. The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0159] 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.

[0160] 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 may represent a resource block (RB) within the cell's bandwidth. The base station may 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, 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.

[0161] 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-RS1101) 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.

[0162] CSI-RS, such as Figure 11BThose shown (e.g., CSI-RS1101, 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.

[0163] 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).

[0164] Figure 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurement of the transmit (Tx) beams for a Transport Receive 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 for 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.

[0165] 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 UE's Tx beam, 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.

[0166] The UE can initiate a beam failure recovery (BFR) procedure based on the detection of beam failure. The UE can transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect 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.).

[0167] 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.

[0168] 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.

[0169] 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).

[0170] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. These one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 11311 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.

[0171] The one or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting Msg 11311. These one or more PRACH timings may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH timings and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

[0172] 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).

[0173] 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 an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0174] 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 1313. As another example, the one or more RACH parameters may 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 11311 based on the association. Msg 11311 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) can indicate the association between the PRACH timing and the one or more reference signals.

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

[0176] 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) to monitor the PDCCH for Msg 2 1312. 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: the OFDM symbol index; the time slot index; the frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include:

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

[0178] 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).

[0179] 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).

[0180] 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 an RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU 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.

[0181] 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).

[0182] 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 include messages such as Msg 3 1313 and / or Msg4 1314.

[0183] 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 illustrated. For example, the base station may indicate or assign a preamble to the UE for Msg 1 1321. The UE may receive the preamble indication (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0184] 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 configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor the PDCCH transmission of the Cell RNTI (C-RNTI) addressed to 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.

[0185] 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.

[0186] Msg A1331 can be transmitted by the UE in uplink transmission. Msg A1331 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 Msg3 1313 is similar to and / or equivalent to that of Msg3 1313. Transmit 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 Msg3 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.

[0187] UE can initiate [activities] on licensed spectrum and / or unlicensed spectrum. Figure 13C The 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.

[0188] The UE can determine the radio resources and / or uplink transmission power of the preamble 1341 and / or transport block 1342 contained in Msg A1331 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 B1332.

[0189] 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).

[0190] 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.

[0191] 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.

[0192] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to a Digital Cipher Interface (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 a Radio Network Temporary Identifier (RNTI).

[0193] 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 the Paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using the System Information RNTI (SI-RNTI) can indicate broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using the Random Access RNTI (RA-RNTI) can indicate a Random Access Response (RAR). A DCI with CRC parity bits scrambled using the 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 the 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.

[0194] 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.

[0195] 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).

[0196] 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 the 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.

[0197] 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.

[0198] 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).

[0199] 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.).

[0200] 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.

[0201] 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 for 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.

[0202] The base station can transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, an RRC message. 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; multiple PUCCH resources (e.g., pucch-Resourceid) having PUCCH resources identified by a PUCCH resource identifier; and / or multiple (e.g., a maximum number) UCI ​​information bits that the UE can transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can select one PUCCH resource set from the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). 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".

[0203] 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).

[0204] 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.

[0205] 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.

[0206] 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.

[0207] 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.

[0208] 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.

[0209] 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.

[0210] 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.

[0211] 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.

[0212] 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.

[0213] 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 the 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 embodiments.

[0214] 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.

[0215] 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 contemplated for implementation in various embodiments.

[0216] 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.

[0217] 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 cell). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. One or more messages (e.g., as part of the configuration parameters) can 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 can include parameters for configuring physical layer and MAC layer channels, bearers, etc. For example, configuration parameters can 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.

[0218] 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., the 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 the 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.

[0219] Using configured uplink grants, the NW can allocate uplink resources to the UE for initial HARQ transmissions and HARQ retransmissions. Two types of configured uplink grants can be defined:

[0220] - For type 1, RRC / NW can directly provide configured uplink grants (e.g., including periodicity).

[0221] - For type 2, RRC / NW can define the periodicity of configured uplink grants, and the PDCCH addressed to CS-RNTI can signal and / or activate the configured uplink grants, and / or deactivate the configured uplink grants; for example, the PDCCH addressed to CS-RNTI can indicate that the uplink grants can be implicitly reused according to the periodicity defined by RRC until deactivated.

[0222] A UE can be configured with up to 12 active configured uplink grants for a given BWP of the serving cell. When more than one is configured, the network can determine which of these configured uplink grants are active at a time (e.g., including all of them). Each configured uplink grant can be type 1 or type 2. For type 2, activation and deactivation of configured uplink grants may be independent between serving cells. When more than one type 2 configured grant is configured, each configured grant can be activated individually using DCI commands, and deactivation of type 2 configured grants can be performed using DCI commands. This can collectively deactivate a single configured grant configuration or multiple configured grant configurations.

[0223] When a SUL is configured, the network can ensure that activities on the SUL with configured uplink authorization do not overlap in time with activities on another UL with configured uplink authorization.

[0224] For both dynamic authorization and configured authorization, for a transport block, two or more repetitions can occur within a single time slot, or across time slot boundaries in consecutive available time slots, with each repetition occurring within a single time slot. For both dynamic authorization and configured authorization type 2, the number of repetitions can also be dynamically indicated in L1 signaling. If both are present, the dynamically indicated number of repetitions can override the RRC configured repetition number.

[0225] Without dynamic authorization, there are two types of transport:

[0226] -Configured authorization type 1, where uplink authorization can be provided by RRC and stored as configured uplink authorization.

[0227] -Configured authorization type 2, where uplink authorization can be provided by PDCCH and activated or deactivated based on L1 signaling indication, and stored or cleared as configured uplink authorization.

[0228] CG Type 1 and CG Type 2 can be configured by RRC for the serving cell of each BWP. Multiple configurations can be active simultaneously in the same BWP. For Type 2, activation and deactivation are independent between serving cells. For the same BWP, the UE / MAC entity can be configured with both Type 1 and Type 2.

[0229] When configured with Configurable Grant Type 1, RRC can configure the following parameters: cs-RNTI: CS-RNTI for retransmission; Periodicity: Periodicity of Configurable Grant Type 1; timeDomainOffset: Resource offset relative to SFN = timeReferenceSFN in the time domain; timeDomainAllocation: Allocating Configurable Uplink Grant in the time domain including startSymbolAndLength or startSymbol; nrofHARQ-Processes: Number of Configurable HARQ Processes; harq-ProcID-Offset: Configurable HARQ process offset with cg-RetransmissionTimer configured for shared spectrum channel access operations; harq-ProcID-Offset2: Configurable HARQ process offset without cg-RetransmissionTimer configured; timeReferenceSFN: SFN used to determine the resource offset in the time domain. The UE can determine the nearest SFN to the indicated number before receiving the Configurable Grant configuration.

[0230] When configured with license type 2, RRC can configure the following parameters: cs-RNTI: CS-RNTI used for activation, deactivation, and retransmission; periodicity: periodicity of license type 2; nrofHARQ-Processes: number of licensed HARQ processes; harq-ProcID-Offset: offset of licensed HARQ processes with cg-RetransmissionTimer configured for shared spectrum channel access operations; harq-ProcID-Offset2: offset of licensed HARQ processes without cg-RetransmissionTimer configured.

[0231] After configuring a configured grant type 1 for the BWP of the serving cell at the upper layer, the UE / MAC entity can store the uplink grant provided by the upper layer as the configured uplink grant of the indicated BWP of the serving cell; and / or initialize / reinitialize the configured uplink grant to start in the symbol according to timeDomainOffset, timeReferenceSFN and S (e.g., derived from SLIV or provided by startSymbol) and repeat periodically.

[0232] After uplink grants are configured for granted grant type 1 / type 2, the UE / MAC entity can sequentially consider the Nth (N>=0) uplink grant occurring in the symbol.

[0233] If cg-nrofPUSCH-InSlot or cg-nrofSlots is configured for configured authorization type 1 or type 2, the UE / MAC entity can consider which additional PUSCHs the uplink authorization occurs in.

[0234] When the configured uplink license is released by the upper layer / RRC / NW, all corresponding configurations can be released and all corresponding uplink licenses can be cleared.

[0235] For Configurable uplink authorization type 2, the UE / MAC entity can clear the Configurable Uplink Authorization immediately after the first transmission of a Configurable Uplink Authorization Confirmation MAC CE or multiple Configurable Uplink Authorization Confirmation MAC CEs that confirm the Configurable Uplink Authorization deactivation.

[0236] IE ConfiguredGrantConfig can be used to configure uplink transmissions without dynamic granting based on two possible schemes. In practice, uplink granting can be configured via RRC (Type 1) or provided via PDCCH (Addressed to CS-RNTI) (Type 2). Multiple ConfiguredGrantConfig settings can be configured in a single BWP of the serving cell.

[0237] PUSCH transmissions can be dynamically scheduled by UL grants in the DCI, or the transmissions can correspond to configured grant type 1 or type 2. Configured grant type 1 PUSCH transmissions can be semi-statically configured to operate upon receiving a higher-layer parameter `configuredGrantConfig` containing `rrc-ConfiguredUplinkGrant`, without detecting UL grants in the DCI. Configured grant type 2 PUSCH transmissions can be semi-persistently scheduled by UL grants in a valid active DCI after receiving a higher-layer parameter `configuredGrantConfig` that does not contain `rrc-ConfiguredUplinkGrant`. If `configuredGrantConfigToAddModList` is configured, more than one configured grant type 1 and / or configured grant type 2 configuration can be active simultaneously on the active BWP of the serving cell.

[0238] For the uplink, the UE can support 16 HARQ processes per cell, or, constrained by the UE's capabilities, a maximum of 32 HARQ processes per cell. The UE may assume that the maximum number of processes used for the uplink is configured to the UE for each cell by the higher-layer parameter nrofHARQ-ProcessesForPUSCH, and / or, when no configuration is provided, the UE may assume a default number of 16 processes.

[0239] When PUSCH resource allocation is semi-statically configured by the higher-level parameter `configuredGrantConfig` in the `BWP-UplinkDedicated` information element and the corresponding PUSCH transport with the configured grant, the following higher-level parameters can be applied during transport:

[0240] - For type 1PUSCH transports with configured grants, unless otherwise specified, the following parameters can be given in configuredGrantConfig:

[0241] ○ To determine the PUSCH repetition type, if the higher-level parameter pusch-RepTypeIndicator in rrc-ConfiguredUplinkGrant is configured and set to 'pusch-RepTypeB', then PUSCH repetition type B is applied;

[0242] Otherwise, apply PUSCH repeat type A;

[0243] For PUSCH repetition type A, the selection of the time domain resource allocation table follows the rule of DCI format 0_0 on the UE-specific search space.

[0244] For PUSCH repetition type B, the time-domain resource allocation table can be selected as follows: If pusch-RepTypeIndicatorDCI-0-1 in pusch-Config is configured and set to 'pusch-RepTypeB', then pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config is used; otherwise, pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config is used. When neither pusch-RepTypeIndicatorDCI-0-1 nor pusch-RepTypeIndicatorDCI-0-2 in pusch-Config is set to 'pusch-RepTypeB', the time-domain resource allocation table can be used.

[0245] When setting 'pusch-RepTypeB', it is not expected that the pusch-RepTypeIndicator in rrc-ConfiguredUplinkGrant will be configured as 'pusch-RepTypeB'.

[0246] ○ The higher-level parameter timeDomainAllocation can provide a row index m+1 pointing to the determined time domain resource allocation table.

[0247] - For type 2PUSCH transports with configured authorization: resource allocation follows the higher-level configuration and the UL authorization received on the DCI.

[0248] The PUSCH repetition type and time-domain resource allocation table can be determined separately by the PUSCH repetition type and time-domain resource allocation table associated with the UL authorization received on the DCI. The value of Koffset is applied when determining the first transmission opportunity, if configured.

[0249] For PUSCH transports with type 1 or type 2 configured authorization, if numberOfRepetitions exists in the table, the index row in the time-domain resource allocation table provides the (nominal) number of repetitions K to be applied to the transport block being transported; otherwise, K is provided by the higher layer via the configuration parameter repK.

[0250] If a higher layer does not deliver a transport block to transmit on resources allocated for uplink transmission without authorization, the UE may not transmit anything on the resources configured by configuredGrantConfig.

[0251] A set of allowed periodicity P can be defined. The higher-layer parameter cg-nrofSlots can provide the number of consecutive time slots allocated within a configured grant period. The higher-layer parameter cg-nrofPUSCH-InSlot can provide the number of consecutive PUSCH allocations within a time slot, wherein the first PUSCH allocation follows the higher-layer parameter timeDomainAllocation or higher-layer configuration for type 1 PUSCH transmission, and the UL grant received on the DCI for type 2 PUSCH transmission, and the remaining PUSCH allocations have the same length and PUSCH mapping type, and are appended without any gaps after the previous allocation. The same combination of start symbol and length and PUSCH mapping type is repeated on consecutively allocated time slots.

[0252] Uplink grants can be dynamically received on the PDCCH in a random access response, semi-persistently configured by the RRC, or determined to be associated with the PUSCH resources of the MSGA. A UE / MAC entity can have uplink grants to be transmitted on the UL-SCH. To execute the requested transmission, the UE / MAC layer can receive HARQ information from the lower layer of the UE. An uplink grant addressed to a CS-RNTI with NDI=0 can be considered a configured uplink grant. An uplink grant addressed to a CS-RNTI with NDI=1 can be considered a dynamic uplink grant.

[0253] Within a bundle of dynamically granted, configured granted, or uplink granted packets received in MAC RAR, the maximum number of TB transmissions can be given by REPETITION_NUMBER, as shown below:

[0254] - For dynamic licensing, REPETITION_NUMBER can be set to a value provided by the underlying layer, as described in Clause 6.1.2.1 of TS 38.214;

[0255] - For configured authorization, REPETITION_NUMBER is set to a value provided by the lower layer, as described in Clause 6.1.2.3 of TS 38.214;

[0256] - For uplink grants received in the MAC RAR, REPETITION_NUMBER is set to a value provided by the lower layer, as described in Clause 6.1.2.1 of TS 38.214.

[0257] If REPETITION_NUMBER > 1, then a maximum of REPETITION_NUMBER – 1 HARQ retransmissions can occur within the bundle after the first transmission. For both dynamic granting and configured uplink granting, the uplink grant received in a MACRAR bundle operation can depend on the HARQ entity invoking the same HARQ process for each transmission that is part of the same bundle. Within the bundle, HARQ retransmissions can be triggered based on the dynamic granting or configured uplink granting or the REPETITION_NUMBER of the uplink grant received in MAC RAR without waiting for feedback from previous transmissions, unless they are terminated. Each transmission within the bundle can be a separate uplink grant delivered to the HARQ entity.

[0258] For each transmission within a bundle of dynamically licensed or uplink licensed packets received in MAC RAR, a redundancy sequence may be determined in accordance with Clause 6.1.2.1 of TS 38.214. For each transmission within a bundle of configured uplink licensed packets, a redundancy sequence may be determined in accordance with Clause 6.1.2.3 of TS 38.214.

[0259] When a timer (e.g., configuredGrantTimer, cg-RetransmissionTimer, or cg-SDT-RetransmissionTimer) is started or restarted by a PUSCH transmission, the timer can be started at the beginning of the first symbol of the PUSCH transmission.

[0260] For a configured uplink license that is neither configured with harq-ProcID-Offset2 nor with cg-RetransmissionTimer, the HARQ process ID can be associated with the first symbol of the UL transmission and can be derived from the following equation: HARQ process ID = [floor(CURRENT_symbol / periodicity)] mod nrofHARQ-Processes.

[0261] For a configured uplink grant with harq-ProcID-Offset2, the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following equation: HARQ process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + harq-ProcID-Offset2. Where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in the frame × numberOfSymbolsPerSlot + number of symbols in the slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively.

[0262] For configured uplink grants with cg-RetransmissionTimer configured, the UE implementation can select a HARQ process ID from the HARQ process IDs available for configuration grant configuration. If the UE / MAC entity is configured with intraCG-Prioritization, for HARQ process ID selection, the UE can prioritize the HARQ process ID with the highest priority based on mapping constraints, where the priority of the HARQ process is determined by the highest priority among the priorities of the multiplexed logical channels (e.g., the MAC PDU to be transmitted is already stored in the HARQ buffer) or by the MAC PDU containing data that can be multiplexed (e.g., the MAC PDU to be transmitted is not stored in the HARQ buffer).

[0263] If the MAC entity is configured with intraCG-Prioritization, the UE can prioritize retransmissions before the initial transmission for HARQ process ID selection between initial transmissions and retransmissions with equal priority. HARQ processes with no logical channel data multiplexed or potentially multiplexed in the MAC PDU have lower priority than HARQ processes with all logical channel data multiplexed or potentially multiplexed in the MAC PDU. If the UE / MAC entity is not configured with intraCG-Prioritization, the UE can prioritize retransmissions before the initial transmission for HARQ process ID selection. The UE can switch the NDI in the CG-UCI for new transmissions without switching the NDI in the CG-UCI during retransmissions.

[0264] CURRENT_symbol can refer to the symbol index of the first transmission timing of the configured uplink licensed bundle.

[0265] If configured uplink authorization is activated and the associated HARQ process ID is less than nrofHARQ-Processes, then a HARQ process can be configured for configured uplink authorization where neither harq-ProcID-Offset nor harq-ProcID-Offset2 is configured. If configured uplink authorization is activated and the associated HARQ process ID is greater than or equal to harq-ProcID-Offset2 and less than the sum of harq-ProcID-Offset2 and nrofHARQ-Processes configured for configured authorization, then a HARQ process can be configured for configured uplink authorization where harq-ProcID-Offset2 is configured.

[0266] The number of parallel UL HARQ processes per HARQ entity can be specified in TS 38.214.

[0267] Each HARQ process can support one TB. Each HARQ process can be associated with a HARQ process identifier. For UL transfers with UL authorization in the RA response or for UL transfers with MSGA payloads, use HARQ process identifier 0.

[0268] Each HARQ process can be associated with a HARQ buffer.

[0269] New transmissions can be performed on resources, and the MCS is indicated on the PDCCH, in the random access response (i.e., MACRAR or fallbackRAR), signaled in the RRC, or determined for the MSGA payload. Retransmissions are performed on resources, using the MCS indicated on the PDCCH, if available, or on the same resource and using the same MCS as the last transmission attempted within the bundle, or on the stored configured uplink licensed resource and using the stored MCS when cg-RetransmissionTimer or cg-SDT-RetransmissionTimer is configured. If cg-RetransmissionTimer is configured, retransmissions using the same HARQ process can be performed on any configured licensed configuration if the configured licensed configuration has the same TBS.

[0270] If the UE / HARQ entity requests a new transport for the TB, the UE / HARQ process may: store the MAC PDU in the associated HARQ buffer, store the uplink grant received from the HARQ entity, and / or generate the transport, as described below.

[0271] If the UE / HARQ entity requests a retransmission of the TB, the UE / HARQ process may: store the uplink grant received from the HARQ entity, and / or generate the transport, as described below.

[0272] 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:

[0273] 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 vision 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.

[0274] 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.

[0275] 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.

[0276] 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.

[0277] 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.

[0278] 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 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.

[0279] 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. In the prior art, it has been identified that current DRX configurations are unsuitable for (i) non-integer XR service periodicity, (ii) variable XR data rates, and (iii) quasi-periodic XR periodicity; therefore, enhancements in these areas may be beneficial.

[0280] 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.

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

[0282]

[0283] Table 1

[0284] 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 coding efficiency or viewport-dependent streaming arrangements.

[0285] 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 might 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 the target. Regarding bitrate, depending on frame rate, resolution, and codec efficiency, the expected bitrate for XR could be between 10 and 200 Mbps.

[0286] For audio, it can be a channel-based or object-based distinguishable representation:

[0287] 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.

[0288] 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.

[0289] 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 15ms (audio delay) and 5ms (audio advance), with absolute limits of 60ms (audio delay) and 40ms (audio advance) recommended for broadcast video.

[0290] 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 several hundred kbit / s if delivered over a network.

[0291] Attitude information must be transmitted with extremely high reliability; therefore, its performance is expected to be similar to URLLC, i.e., the uplink sensor data packet loss rate can be lower than 10E-4.

[0292] In both the uplink and downlink, XR awareness contributes to the optimization of gNB radio resource scheduling and relies at least on the concepts of PDU sets and data bursts (specified in TR 23.700): a PDU set can consist of one or more PDUs carrying a payload of a single information unit generated at the application level (e.g., a frame or video slice), while a data burst is a set of data PDUs generated and transmitted by an application within 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.

[0293] The CN can provide the following information to the RAN (specified in TR 23.700) to help process QoS flows and PDUs:

[0294] - Semi-static information (NGAP) of both UL and DL provided via the control plane:

[0295] ○ Periodicity of UL and DL services in QoS flows via TSCAI / TSCAC;

[0296] ○ Traffic jitter information (e.g., jitter range) associated with each period of the QoS flow;

[0297] ○ PDU set QoS parameters, PDU set error rate (PSER), PDU set delay budget (PSDB), PDU set integration indicator (PSII)

[0298] -Dynamic information of the DL provided by the user plane (GTP-U header):

[0299] ○PDU set serial number;

[0300] ○ PDU collection size, in bytes;

[0301] ○ PDU SN within the PDU set;

[0302] ○The last PDU in the PDU set;

[0303] ○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.

[0304] ○ The data burst end indication in the header of the last PDU in the data burst.

[0305] 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.

[0306] When an application layer is known to require a specific number of PDUs from the PDU set to use the corresponding information unit (e.g., due to the lack or limitation of error concealment techniques, see TR 26.926), once the number of known lost PDUs exceeds this number, the remaining PDUs in the PDU set are no longer needed by the application layer and may be discarded.

[0307] Depending on how PDU sets are mapped to QoS flows in NAS and how QoS flows are mapped to DRBs in AS, the following alternatives can be distinguished (e.g.) Figure 17 As shown):

[0308] -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.

[0309] -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.

[0310] -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.

[0311] -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.

[0312] When comparing these alternatives, QoS flows may not be mapped to multiple DRBs in the uplink, thus ruling out N1N as an alternative.

[0313] Additionally, the concept of PDU sets may not affect the granularity of the following items:

[0314] -SDAP SDU processing: SDAP still maps each incoming SDU to a single PDU of a single PDCP entity;

[0315] - Retransmission: HARQ still relies on MAC PDU and ARQ on RLC PDU.

[0316] The following enhancements can be suggested for transports based on configured authorization:

[0317] - Multiple CG PUSCH transmission opportunities within a single CG PUSCH configuration cycle;

[0318] - The UE dynamically indicates the timing of unused CG PUSCH based on UCI (e.g., CG-UCI or a new UCI).

[0319] To enhance the scheduling of uplink resources in XR, the following improvements can be considered:

[0320] - One or more additional BS tables to reduce quantization errors in the BSR report (e.g., for high bit rates);

[0321] - Delay knowledge of buffered data, such as remaining time, and how much data is buffered at which delay. It will be determined whether delay information is part of the BSR or as a new MAC CE report. How delay information is updated, taking into account factors such as scheduling and transmission delays, requires further investigation.

[0322] - Further research could be conducted on additional BSR triggering conditions that allow buffer status information to be available in a timely manner.

[0323] - Based on TSCAI, provide some supplementary 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 UE applications.

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

[0325] Data burst: 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.

[0326] PDU Set: A PDU set can consist of one or more PDUs carrying the payload of an information unit generated at the application level (e.g., a frame or video slice of the XRM service used in TR 26.926). In some implementations, the application layer requires all PDUs in the PDU set to use the corresponding information unit. In other implementations, the application layer can still recover some or all of the information units when some PDUs are lost.

[0327] PDU Set Error Rate (PSER): Defines the upper limit on the rate at which a set of PDUs has been processed by the sender of the link layer protocol but has not been successfully delivered to the upper layer by the corresponding receiver (specified in TR 23.700-60).

[0328] PDU Set Delay Budget (PSDB): Defines the time between the reception of the first PDU in the PDU set and the successful delivery of the last arriving PDU (see TR 23.700-60).

[0329] PDU Collection Integration Indicator (PSII): Defines whether the application layer needs all PDUs when using the PDU collection.

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

[0331] The terms “BS” and “NW” are used interchangeably.

[0332] The upper layer of a wireless device can be SDAP, RRC, PDCP, RRC, and / or MAC layers. The lower layer of a wireless device can be the PHY layer.

[0333] Data can be UL data and / or DL ​​data. Data can be PDUs, PDU sets, SDUs, and / or IP packets. PDUs can be SDAP PDUs, PDCP PDUs, RLC PDUs, or MAC PDUs. SDUs can be SDAP SDUs, PDCP SDUs, RLC SDUs, MACSDUs, or PHY SDUs (e.g., TBs).

[0334] The terms “periodic”, “periodicity”, “CG periodicity”, “CG periodicity”, and “CG periodicity” are used interchangeably.

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

[0336] The terms “determine” and “derive” are used interchangeably.

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

[0338] The terms “equation,” “formula,” and “predefined rule” are used interchangeably.

[0339] XR streams can have complex service patterns. For example, a video stream may consist of periodic bursts of PDUs rather than individual PDUs. Such new service patterns may require enhancements to traditional CG configurations and procedures, as a single CG with a traditional CG configuration may not effectively support XR services. Therefore, multiple CG PUSCH resources / transmission opportunities (e.g., referred to as multiple CGOs in the CG cycle of this application) may be required within a single CG PUSCH configuration cycle. Enhancements can be introduced for new CG configuration patterns that can match XR service patterns. For example, the wireless device can configure multiple / groups of CG (PUSCH) resource opportunities in each CG cycle / cycle. The periodicity of CG (PUSCH) resource opportunities within multiple / groups of CG (PUSCH) resource opportunities can be configured based on the arrival time of PDUs / PDU sets in the data burst and / or some latency requirements. The periodicity between multiple / groups of CG (PUSCH) resource opportunities can be configured based on the periodicity of PDU sets / data bursts.

[0340] To allocate multiple CG resource opportunities with a single CG configuration within a CG period, a (single) DCI scheduling multiple PUSCHs can be used. For example, the NW can transmit a DCI scheduling multiple PUSCH resource opportunities as the active DCI for the CG configuration. The multiple scheduled PUSCH resource opportunities can then be obtained as CG PUSCH resource opportunities in the first period, and the radio device can repeat those CG PUSCH resource opportunities in each CG period. The radio device can configure (e.g., indicate) the presence of multiple CG resource opportunities using (RRC) parameters, such as cg-nrofPUSCH-InSlot and / or cg-nrofSlots. Using these parameters, multiple PUSCH opportunities can be configured (e.g., indicated) within time slots, and such time slots can be configured (e.g., indicated) at the beginning of each period.

[0341] Multiple CG resource timings of different TBs can be allocated. As an example, and as... Figure 18 As shown, each CG PUSCH resource opportunity (CGO) within the same CG cycle can be used for a new transfer of a new TB.

[0342] As an example, such as Figure 19 As shown, each CGO within a CG cycle can be configured (e.g., indicated) via individual scheduling information (e.g., K2 (slot offset), SLIV (startSymbolAndLengh), repK, MCS, and / or PUSCH mapping type). For example, in a type 1 CG, NW / RRC can configure (e.g., indicated) multiple configuration parameters (e.g., timeDomainAllocation and / or timeDomainOffset) for multiple CGOs within a CG cycle, for example, via lists. For example, in a type 2 CG, RRC can configure (e.g., indicated) multiple lists of configuration parameter sets (e.g., timeDomainAllocation and / or timeDomainOffset), and DCI can indicate (e.g., indicated by the DCI TDRA field) one of the configured (e.g., indicated) lists to activate CG configuration for multiple CGOs within a CG cycle.

[0343] In some implementations, the HARQ process ID for CG transmissions can be determined / derived based on an equation, for example, HARQ process ID = [floor(CURRENT_symbol / periodicity)] mod nrofHARQ-Processes. Specifically, the HARQ process ID for CG transmissions can be determined / derived based on the first symbol of the CG transmission (e.g., based on time resources). Specifically, the HARQ process ID for CG transmissions can be determined / derived based on CURRENT_symbol. CURRENT_symbol can be referred to as the symbol index of the first transmission timing configured with uplink grants (bundles). Specifically, the HARQ process ID for CG transmissions can be determined / derived based on the periodicity of the CG. Specifically, nrofHARQ-Processes can be the number of configured HARQ processes. It can be applicable to both type 1 CG and type 2 CG.

[0344] In some implementations, the HARQ process ID of the CG can be determined / derived based on the UE implementation. For example, the UE implementation can select a HARQ process ID that can be used for configuration authorization configuration.

[0345] It should be noted that the HARQ process ID for a CG transmission can be determined based on the following equation: HARQ process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes. The denominator in determining the HARQ process ID is the periodicity (e.g., indicated by the corresponding CG configuration), which indicates that the wireless device can increment the HARQ process ID by one for the next CG period (e.g., regardless of which symbol / slot of the CG transmission occurs in).

[0346] refer to Figure 20In the prior art, for the case of one CGO per CG cycle, if the HARQ process ID of CGO 1 in CG cycle 1 is 1, then the HARQ process ID of CGO 2 in CG cycle 2 can be 2. When applying the prior art to the case of multiple CGOs per CG cycle, if the HARQ process ID of CGO 1 in CG cycle 1 is 1, then the HARQ process IDs of CGO2 and CGO3 can be 1, for example, because CGO2 and CGO3 are in the same CG cycle as CGO1 (e.g., CG cycle 1). If the HARQ process ID of CGO 4 in CG cycle 2 is 2, then the HARQ process IDs of CGO5 and CGO6 can be 2, for example, because CGO5 and CGO6 are in the same CG cycle as CGO2 (e.g., CG cycle 2). The purpose of configuring (e.g., instructing) multiple CGOs within the same CG cycle is to perform new transfers of different TBs via different CGOs within the same CG cycle. If the HARQ process ID is determined to be the same for different CGOs, the transfer time for each TB can be very short because the new TB may overwrite the HARQ buffer used for the same HARQ process ID in the previous TB. Therefore, there is a need in the art to provide a different HARQ process ID for each of the CGOs within the same CG cycle.

[0347] In such Figure 21 In some of the embodiments shown, the wireless device can determine the HARQ process ID of the UL transmission of the CG based on an equation, wherein the equation can be based on the number of CGOs in the CG cycle and / or the order / sequence of the number of CGOs (modulo operation with the number of HARQ processes configured for the UL transmission of the CG).

[0348] In the example, if the wireless device is configured (e.g., indicated) to have multiple CGOs in the CG cycle, the wireless device can determine the HARQ process ID of the UL transmission of the CG based on the equation.

[0349] In the example, if the wireless device is configured (e.g., to receive) an IE (e.g., a configuration including one or more configuration parameters), the wireless device can determine the HARQ process ID for the UL transmission of the CG based on the equation. More specifically, the IE can indicate (e.g., it may include an enable / disable indicator, thereby indicating) whether the wireless device enables / disables determining the HARQ process ID for the UL transmission of the CG based on an equation (e.g., based on predetermined rules, methods, procedures, and / or determination).

[0350] In the example, the equation can be expressed as HARQ process ID = [floor(CURRENT_symbol / periodicity) × nofCGO + (CGO - offset - 1)] mod nofHARQ-Processes, where: nofCGO can be referred to as the number of CGOs in the CG period. The CGO offset can be referred to as the Nth CGO in the CG period. The CGO offset can be referred to as the order / sequence of the number of CGOs. CURRENT_symbol can be referred to as the symbol index of the first transmission timing with configured uplink grants (bundles). CURRENT_symbol can be derived based on (SFN × number of slots per frame × number of symbols per slot + number of slots in a frame × number of symbols per slot + number of symbols in a slot). The number of slots per frame can refer to the number of consecutive slots per frame. The number of symbols per slot can refer to the number of consecutive symbols per slot. Periodicity can be referred to as the periodicity of UL transmissions without UL grants for CG type 1 and CG type 2. Periodicity can be configured in the CG configuration. nrofHARQ-Processes can be referred to as the number of HARQ processes configured (for CG). It can apply to both CG type 1 and CG type 2. If the wireless device is configured with nrofHARQ-Processes-, the wireless device can ignore nrofHARQ-Processes (without the suffix).

[0351] In such Figure 21 In the example shown, the wireless device can determine the HARQ process ID of the UL transmission of a CG based on the number of CGOs in a CG cycle. Specifically, the number of CGOs in a CG cycle can indicate one or more CG resource opportunities configured for each CG cycle. One or more CG resource opportunities can be used for new transmissions of a new TB. Specifically, the wireless device can determine the number of CGOs in a CG cycle based on RRC configuration and / or DCI indications. Specifically, the wireless device can determine the number of CGOs in a CG cycle based on the presence of unused CGOs. If one or more unused CGOs exist (e.g., within a CG cycle and / or within a time interval determined by the wireless device), the wireless device can determine the number of CGOs in the CG cycle based on (the configured number of CGOs minus the unused CGOs). More specifically, the wireless device can indicate whether a CGO is available based on an indication (e.g., an unused CGO indication). If there are no unused CGOs, the wireless device can determine the number of CGOs in the CG cycle based on the configured number of CGOs.

[0352] In an alternative, the wireless device can determine the number of CGOs in the CG cycle based on the CGOs used in this CG cycle. Alternatively, the wireless device can determine the number of CGOs in the CG cycle based on the configured number of CGOs in this CG cycle (e.g., regardless of whether CGOs are used).

[0353] Specifically, the number of CGOs in a CG cycle can be configured by parameters included in the CG configuration (e.g., indications).

[0354] In such Figure 21 In the example shown, the wireless device can determine the HARQ process ID for the UL transmission of the CG based on the order / sequence of the number of CGOs. Specifically, the order / sequence of the number of CGOs can be referred to as the Nth CGO in the CG cycle. For example, if the wireless device is configured (e.g., indicated) to have three CGOs in the CG cycle, the Nth CGO in the CG cycle means the 1st, 2nd, and 3rd CGOs in the CG cycle. Specifically, the wireless device can determine the order / sequence of the number of CGOs based on the CGOs used for transmission.

[0355] In an alternative, the wireless device can determine the order / sequence of CGO quantities based on the CGOs used in this CG cycle. Alternatively, the wireless device can determine the order / sequence of CGO quantities based on the number of CGOs configured (e.g., indicated) in this CG cycle (e.g., regardless of whether CGOs are used).

[0356] Specifically, the wireless device can determine the order / sequence of the number of CGOs based on a counter. The counter can count the time CGOs are used for transmission. The counter can also count the time CGOs are configured for transmission. Specifically, the order / sequence of the number of CGOs can be configured (e.g., indicated) by parameters included in the CG configuration.

[0357] In such Figure 22In the example embodiment shown, it is assumed that: the periodicity is 42 symbols, i.e., 3 time slots. nrofHARQ-Processes is 8. numberOfSymbolsPerSlot is 14. numberOfSlotsPerFrame is 10. nofCGO is 3. The CGO offset is the Nth CGO in this period. CURRENT_symbol is (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of time slots in the frame × numberOfSymbolsPerSlot + number of symbols in the time slot). The HARQ process ID of CGO1 is 0, i.e., [floor(2 / 42) × 3 + (1-1)] modulo nrofHARQ-Processes. The HARQ process ID of CGO2 is 1, i.e., [floor(16 / 42) × 3 + (2-1)] modulo nrofHARQ-Processes. The HARQ process ID of CGO3 is 2, that is, [floor(34 / 42)×3+(3-1)] modulo nrofHARQ-Processes.

[0358] In such Figure 23 In some of the embodiments shown, the wireless device can determine the second HARQ process ID of the second UL transmission of the CG based on the first HARQ process ID of the first UL transmission for the CG (modulo operation with the number of HARQ processes configured for the UL transmission of the CG), wherein the second UL transmission can be performed after the first UL transmission.

[0359] In the example, if the wireless device is configured (e.g., indicated) to have multiple CGOs in the CG cycle, the wireless device can determine the second HARQ process ID of the second UL transmission of the CG based on the first HARQ process ID of the first UL transmission used for the CG.

[0360] In the example, if the wireless device is configured (e.g., indicated) to have an IE (e.g., a configuration including one or more configuration parameters), the wireless device can determine the second HARQ process ID for the second UL transmission of the CG based on the first HARQ process ID used for the first UL transmission of the CG. More specifically, the IE can instruct the wireless device whether to enable / disable determining the second HARQ process ID for the second UL transmission of the CG based on the first HARQ process ID used for the first UL transmission of the CG.

[0361] In the example, the first UL transmission and the second UL transmission of the CG can have a temporal relationship. Specifically, the first UL transmission of the CG can be transmitted before the second UL transmission of the CG. The second UL transmission of the CG can be transmitted after the first UL transmission of the CG. Specifically, the first UL transmission of the CG can use the last CG resource preceding the CG resource used for the second UL transmission of the CG. The second UL transmission of the CG can use the next CG resource following the CG resource used for the first UL transmission of the CG. Specifically, the second UL transmission can be a subsequent UL transmission of the first UL transmission. Specifically, the second UL transmission can be close to the first UL transmission in the time domain.

[0362] In such Figure 23 In the example shown, the second HARQ process ID can be incremented (e.g., by one) from the first HARQ process ID. More specifically, this value can be configured by the RRC. For example, if the first HARQ process ID is X, then the second HARQ process ID can be X plus one. Specifically, the radio device can record the first HARQ process ID based on UE variables and / or counters.

[0363] In the examples, the HARQ process ID of the (first) first CGO of the CG can be determined based on an equation. The HARQ process ID of the (first) first CGO of the CG can be determined based on the periodicity of the CG. The HARQ process ID of the (first) first CGO of the CG can be determined based on the CURRENT symbol transmitted by the UL.

[0364] The equation can be expressed as HARQ process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes. Specifically, the HARQ process ID for a CG transmission can be determined / derived based on the first symbol of the CG transmission (e.g., based on time resources). Specifically, the HARQ process ID for a CG transmission can be determined / derived based on CURRENT_symbol. CURRENT_symbol can be referred to as the symbol index of the first transmission timing configured with uplink grants (bundles). Specifically, the HARQ process ID for a CG transmission can be determined / derived based on the periodicity of the CG. Specifically, nrofHARQ-Processes can be the number of configured HARQ processes. It can be applicable to both type 1 CG and type 2 CG.

[0365] Specifically, the (first) first CGO of a CG can be a CGO configured as the first CGO after receiving / activating the CG configuration. Specifically, the (first) first CGO of a CG can be a CGO used for transmission after receiving / activating the CG configuration. Specifically, the (first) first CGO of a CG can be a CGO scheduled by DCI (used to activate the CG configuration). Specifically, the (first) first CGO of a CG can be the first CGO configured / used / transmitted among multiple CGOs in the same CG cycle.

[0366] In the example, if at least one of the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided), or with a symbol of an SS / PBCH block indexed by ssb-PositionsInBurst, then the HARQ process ID may not be incremented for untransmitted CGO / CG / PUSCH.

[0367] In the example, if at least one of the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided), or with a symbol of an SS / PBCH block indexed by ssb-PositionsInBurst, then the HARQ process ID may be incremented for an untransmitted CG / PUSCH.

[0368] In the example, the wireless device can transmit a HARQ process ID via the UCI (via the CGO) to indicate the HARQ process ID used for the CGO. Specifically, the wireless device can transmit the HARQ process ID via the UCI of the (first) first CGO of the CG. Specifically, the wireless device can transmit the HARQ process ID via the UCI of the first CGO in each CG cycle. Specifically, the wireless device can transmit the HARQ process ID via the UCI of the last CGO in each CG cycle. Specifically, the wireless device can transmit the HARQ process ID via the UCI of each CGO used for transmission. Specifically, the wireless device can periodically (e.g., based on configured periodicity, based on a timer, and / or based on CG periodicity) via the UCI.

[0369] In the example, the wireless device can determine the HARQ process ID for each CGO, for example, regardless of whether the CGO is used for transmission. For instance, if the wireless device indicates an indication (e.g., an unused CGO indication) to indicate that one or more CGOs are not used, the wireless device can skip using those CGOs. In this case, the wireless device can still determine and / or increment the HARQ process ID for each CGO, for example, regardless of whether the CGO is used.

[0370] In the example, the wireless device can determine the HARQ process ID for each CGO used for transmission. For instance, if the wireless device indicates an indication (e.g., an unused CGO indication) to indicate that one or more CGOs are not used, the wireless device can skip using those CGOs. In this case, the wireless device may not determine and / or not increment the HARQ process ID of CGOs not used for transmission.

[0371] In such Figure 24 In some implementations shown, the wireless device may determine a first HARQ process ID for a first UL transmission of multiple CGOs within a CG cycle based on an equation / predefined rule (modulo operation with the number of HARQ processes configured for UL transmissions in the CG), and / or the wireless device may determine a second HARQ process ID for a second UL transmission of multiple CGOs within a CG cycle based on incrementing the first HARQ process ID by a value (e.g., one) (modulo operation with the number of HARQ processes configured for UL transmissions in the CG). The first UL transmission may use a first CG resource, and the second UL transmission may use a second CG resource, wherein the first CG resource and the second CG resource are in the same CG cycle.

[0372] In the example, if the wireless device is configured (e.g., indicated) to have multiple CGOs in the CG cycle, the wireless device can determine the first HARQ process ID for the first UL transmission of the multiple CGOs in the CG cycle based on an equation, and / or the wireless device can determine the second HARQ process ID for the second UL transmission of the multiple CGOs in the CG cycle based on incrementing the first HARQ process ID by a certain value (e.g., one).

[0373] In the example, if the wireless device is configured (e.g., indicated) to have an IE (e.g., a configuration including one or more configuration parameters), the wireless device can determine a first HARQ process ID for first UL transmissions of multiple CGOs in a CG cycle based on an equation, and / or the wireless device can determine a second HARQ process ID for second UL transmissions of multiple CGOs in a CG cycle based on incrementing the first HARQ process ID by a value (e.g., a). More specifically, the IE can instruct the wireless device whether to enable / disable determining the first HARQ process ID for first UL transmissions of multiple CGOs in a CG cycle based on an equation, and / or the wireless device can determine the second HARQ process ID for second UL transmissions of multiple CGOs in a CG cycle based on incrementing the first HARQ process ID by a value (e.g., a).

[0374] In the example, the first UL transmission and the second UL transmission of a CG can have a temporal relationship. Specifically, the first UL transmission of multiple CGOs is the (earliest) first UL transmission of multiple CGOs in a CG cycle. The second UL transmission of multiple CGOs is one of the subsequent UL transmissions of multiple CGOs in a CG cycle. Specifically, the first UL transmission of a CG can be transmitted before the second UL transmission of a CG. The second UL transmission of a CG can be transmitted after the first UL transmission of a CG. Specifically, the first UL transmission of a CG can use the last CG resource preceding the CG resource used for the second UL transmission of a CG. The second UL transmission of a CG can use the next CG resource following the CG resource used for the first UL transmission of a CG. Specifically, the second UL transmission can be one or more subsequent UL transmissions following the first UL transmission. Specifically, the second UL transmission can be close to the first UL transmission in the time domain.

[0375] In such Figure 24 In the example shown, the second HARQ process ID can be incremented (e.g., by one) from the first HARQ process ID. More specifically, the value can be configured by the RRC (e.g., indicated). For example, if the first HARQ process ID is X, then the second HARQ process ID can be X plus one. Specifically, the radio device can record the first HARQ process ID based on UE variables and / or counters.

[0376] In the examples, the HARQ process ID of the (first) first CGO in each CG cycle can be determined based on an equation. The HARQ process ID of the (first) first CGO in each CG cycle can be determined based on the CG periodicity. The HARQ process ID of the (first) first CGO in each CG cycle can be determined based on the CURRENT symbol transmitted in the UL.

[0377] The equation can be expressed as HARQ process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes. Specifically, the HARQ process ID for a CG transmission can be determined / derived based on the first symbol of the CG transmission (e.g., based on time resources). Specifically, the HARQ process ID for a CG transmission can be determined / derived based on CURRENT_symbol. CURRENT_symbol can be referred to as the symbol index of the first transmission timing configured with uplink grants (bundles). Specifically, the HARQ process ID for a CG transmission can be determined / derived based on the periodicity of the CG. Specifically, nrofHARQ-Processes can be the number of configured HARQ processes. It can be applicable to both type 1 CG and type 2 CG.

[0378] Specifically, the (first) first CGO in each CG cycle can be the first CGO configured as the first CGO after receiving / activating the CG configuration in each CG cycle. Specifically, the (first) first CGO of a CG can be the first CGO used for transmission after receiving / activating the CG configuration in each CG cycle. Specifically, the (first) first CGO of a CG can be the first CGO scheduled by DCI in each CG cycle (used to activate the CG configuration). Specifically, the (first) first CGO of a CG can be the first CGO configured / used / transmitted among multiple CGOs in the same CG cycle. Specifically, the (first) first CGO in each CG cycle can be the CGO that first appears in a given CG cycle.

[0379] In the example, if at least one of the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided), or with a symbol of an SS / PBCH block indexed by ssb-PositionsInBurst, then the HARQ process ID may not be incremented for untransmitted CGO / CG / PUSCH.

[0380] In the example, if at least one of the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided), or with a symbol of an SS / PBCH block indexed by ssb-PositionsInBurst, then the HARQ process ID may be incremented for an untransmitted CG / PUSCH.

[0381] In such Figure 25 In some implementations shown, the wireless device can determine the HARQ process ID for the UL transmission of the CG based on a combination of a first value (from a first set of HARQ process IDs) and / or a second value (from a second set of HARQ process IDs) modulo the number of HARQ processes configured for the UL transmission of the CG. The HARQ process ID derived for the UL transmission of the CG can be the first value plus the second value. The HARQ process ID derived for the UL transmission of the CG can be based on two dimensions, such as a first value in a first dimension and a second value in a second dimension.

[0382] In the example, if the wireless device determines the first value of the HARQ process ID transmitted by the UL as "-(1)" based on the equation, and the wireless device determines the second value of the HARQ process ID transmitted by the UL as "-(1)" based on the order / sequence of the number of CGOs, then the HARQ process ID transmitted by the UL can be 1-1.

[0383] In the example, if the wireless device is configured with multiple CGOs in the CG cycle, the wireless device can determine the HARQ process ID of the UL transmission of the CG based on a combination of a first value and / or a second value.

[0384] In the example, if the wireless device is configured with multiple CGOs during the CG cycle (e.g., a configuration including one or more configuration parameters), the wireless device can determine the HARQ process ID for the UL transmission of the CG based on a combination of a first value and / or a second value. More specifically, the IE can instruct the wireless device whether to enable / disable determining the first HARQ process ID for the first UL transmission of the multiple CGOs in the CG cycle based on an equation, and / or

[0385] In such Figure 25 In the examples shown, the first value can be derived (e.g., determined) based on an equation of the HARQ process ID. The first value can be derived (determined) based on the CG periodicity. The first value can be derived (determined) based on the CURRENT symbol transmitted by the UL.

[0386] The equation can be expressed as HARQ process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes. Specifically, the HARQ process ID for a CG transmission can be determined / derived based on the first symbol of the CG transmission (e.g., based on time resources). Specifically, the HARQ process ID for a CG transmission can be determined / derived based on CURRENT_symbol. CURRENT_symbol can be referred to as the symbol index of the first transmission timing configured with uplink grants (bundles). Specifically, the HARQ process ID for a CG transmission can be determined / derived based on the periodicity of the CG. Specifically, nrofHARQ-Processes can be the number of configured HARQ processes. It can be applicable to both type 1 CG and type 2 CG.

[0387] In the example, a second value (from the second set of HARQ process IDs) can be derived based on the number of CGOs and / or the order / sequence of the number of CGOs in the CG cycle. The order / sequence of the number of CGOs can be referred to as the Nth CGO in the CG cycle.

[0388] In the example, the wireless device can determine the HARQ process ID of the UL transmission of the CG based on a first set of HARQ process IDs and / or a second set of HARQ process IDs.

[0389] When the UE is configured with a CG configuration, a first set of HARQ process IDs can be used. The number of HARQ process IDs in the first set can be configured by nrofHARQ-Processes (e.g., indicated). Specifically, nrofHARQ-Processes can be the number of configured HARQ processes. It can be applied to both Type 1 CG and Type 2 CG.

[0390] When a UE is configured (e.g., indicated) to have multiple CGOs in a CG cycle, a second set of HARQ process IDs can be used. The number of HARQ process IDs in the second set can be configured by the number of CGOs in the CG cycle.

[0391] In the example, the wireless device can determine a second value of the HARQ process ID for each CGO (from a second set of HARQ process IDs), for example, regardless of whether the CGO is used for transmission. For instance, if the wireless device indicates an indication (e.g., an unused CGO indication) to indicate that one or more CGOs are not used, the wireless device can skip using those CGOs. In this case, the wireless device can still determine a second value of the HARQ process ID for each CGO (from a second set of HARQ process IDs), for example, regardless of whether the CGO is used.

[0392] In the example, the wireless device can determine a second value of the HARQ process ID for each CGO used for transmission (from a second set of HARQ process IDs). For example, if the wireless device indicates an indication (e.g., an unused CGO indication) to indicate that one or more CGOs are not used, the wireless device can skip using those CGOs. In this case, the wireless device may not need to determine a second value of the HARQ process ID for CGOs not used for transmission (from a second set of HARQ process IDs).

[0393] In the example, the wireless device may transmit the HARQ process ID via the UCI (via the CGO) to indicate a first and / or second value of the HARQ process ID used for the CGO. Specifically, the wireless device may transmit the HARQ process ID via the UCI of the (first) first CGO of the CG. Specifically, the wireless device may transmit the HARQ process ID via the UCI of the first CGO in each CG cycle. Specifically, the wireless device may transmit the HARQ process ID via the UCI of the last CGO in each CG cycle. Specifically, the wireless device may transmit the HARQ process ID via the UCI of each CGO used for transmission. Specifically, the wireless device may periodically (e.g., based on configured periodicity, based on a timer, and / or based on CG periodicity) via the UCI.

[0394] In the example, the radio device can receive a first value and a second value via DCI from the BS to indicate the HARQ process ID for scheduling. For example, when the radio device receives the first and second values, the UE can determine the HARQ process ID. The UE can then perform a transmission based on the HARQ process ID.

[0395] In example embodiments (e.g., such as) Figure 21 As shown, the wireless device can receive one or more configuration parameters indicating: a periodicity associated with a Configuration Authorization (CG) configuration; and / or the number of resources in the periodicity. The wireless device can transmit uplink (UL) data based on the CG configuration and / or the Hybrid Automatic Repeat Request (HARQ) process index, wherein the HARQ process index can be based on the number of resources in the periodicity.

[0396] In example embodiments (e.g., such as) Figure 21 As shown), the wireless device can receive one or more configuration parameters indicating the following: a periodicity associated with a configuration authorized (CG) configuration; and / or multiple resources in the periodicity; the wireless device can transmit uplink (UL) data based on a Hybrid Automatic Repeat Request (HARQ) process index for the CG configuration and / or via resources in the multiple resources, for example, where the HARQ process index may be based on the number of multiple resources in the periodicity.

[0397] According to an example embodiment, the HARQ process index can be based on the order of the number of resources used in the periodicity for transmitting UL data.

[0398] According to an example embodiment, the order may be the Nth of the number of resources in a periodicity.

[0399] According to an example embodiment, the HARQ process index can be based on CURRENT_symbol. According to an example embodiment, the HARQ process index can be based on periodicity. According to an example embodiment, the HARQ process index can be based on modulo operation of nrofHARQ-Processes.

[0400] According to an example embodiment, CURRENT_symbol can be based on the first symbol of the UL transmission of UL data. According to an example embodiment, CURRENT_symbol can be based on (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in the frame × numberOfSymbolsPerSlot + number of symbols in the slots), where numberOfSlotsPerFrame is the number of consecutive slots per frame, and numberOfSymbolsPerSlot is the number of consecutive symbols per slot.

[0401] According to the example embodiment, nrofHARQ-Processes can be the number of HARQ processes configured for CG configuration.

[0402] According to an example embodiment, the HARQ process index can be associated with a first symbol used for transmitting UL data.

[0403] According to an example embodiment, the number of resources in a periodicity can indicate multiple PUSCH resources in a periodicity.

[0404] According to the example embodiment, the parameters can be included in the CG configuration.

[0405] According to an example embodiment, the resource can be a UL resource. According to an example embodiment, the resource can be a PUSCH resource. According to an example embodiment, the resource can be a CG resource timing.

[0406] According to the example embodiment, the CG configuration can be type 1 CG. According to the example embodiment, the CG configuration can be type 2 CG.

[0407] In example embodiments (e.g., such as) Figure 21As shown), the wireless device can receive: a Configurable Grant (CG) configuration indicating periodicity; and / or a parameter indicating the number of PUSCH resources in the periodicity; the wireless device can determine multiple UL grants for multiple UL transmissions in the periodicity based on the CG configuration and the parameter; the wireless device can determine the HARQ process ID of the UL transmissions in the multiple UL transmissions based on an equation, wherein the equation can be: HARQ process ID = [floor(CURRENT_symbol / periodicity) × number of PUSCH resources + (offset - 1)] mod nrofHARQ-Processes, where CURRENT_symbol can be determined based on the first symbol of the UL transmission; the offset can be based on the order of the UL transmissions in the multiple UL transmissions; nrofHARQ-Processes can be the number of HARQ processes configured for the CG configuration; and / or the wireless device can perform UL transmissions based on the HARQ process ID.

[0408] In example embodiments (e.g., such as) Figure 21 As shown, the wireless device can receive: a configured authorization (CG) configuration indicating periodicity; and / or a parameter indicating the number of resources in the periodicity; the wireless device can determine multiple UL authorizations for multiple UL transmissions in the periodicity based on the CG configuration and the parameter; the wireless device can determine the HARQ process ID of the UL transmission in the multiple UL transmissions based on the number of resources; and / or the wireless device can perform the UL transmission based on the HARQ process ID.

[0409] In example embodiments (e.g., such as) Figure 23 As shown), the wireless device can receive a configured authorized (CG) configuration indicating a first resource and a second resource, wherein the first resource is the last resource preceding the second resource; the wireless device can transmit first uplink (UL) data via the first resource based on a first hybrid automatic repeat request (HARQ) process index; and / or the wireless device can transmit second UL data via the second resource based on a second HARQ process index, wherein the second HARQ process index can be based on the first HARQ process index.

[0410] In example embodiments (e.g., such as) Figure 23 As shown), the wireless device can receive a configured authorized (CG) configuration indicating two consecutive resources; and / or the wireless device can transmit first uplink (UL) data via a first resource of the two consecutive resources based on a first hybrid automatic repeat request (HARQ) process index; and / or the wireless device can transmit second UL data via a second resource of the two consecutive resources based on a second HARQ process index, wherein the second HARQ process index can be based on the first HARQ process index.

[0411] According to the example embodiment, the second HARQ process index is based on incrementing the first HARQ process index by a certain value. According to the example embodiment, the value can be one (1).

[0412] According to the example embodiment, the second HARQ process ID can be based on the modulo operation of nrofHARQ-Processes.

[0413] According to the example embodiment, nrofHARQ-Processes can be the number of HARQ processes configured for CG configuration.

[0414] According to an example embodiment, the wireless device may maintain the value of the first HARQ process index through a UE variable or a counter.

[0415] According to the example implementation, the second HARQ process index can be based on an incrementing UE variable or a counter.

[0416] In example embodiments (e.g., such as) Figure 23 As shown), the wireless device can receive parameters indicating a periodic configured authorization (CG) configuration; and / or an indication of the number of PUSCH resources in the periodicity. The wireless device can determine a first UL authorization for a first UL transmission in the periodicity based on the CG configuration and parameters, wherein the first UL transmission may be the first first UL transmission configured by the CG configuration; the wireless device can determine a first HARQ process ID for the first UL transmission based on an equation, wherein the equation may be: HARQ process ID = [floor(CURRENT_symbol / periodicity)] mod nrofHARQ-Processes, wherein: CURRENT_symbol may be determined based on a first symbol of the first UL transmission; nrofHARQ-Processes may be the number of HARQ processes configured for the CG configuration. The wireless device can determine a second UL authorization for a second UL transmission in the periodicity based on the CG configuration and parameters. The wireless device can determine a second HARQ process ID for the second UL transmission by incrementing the first HARQ process ID by one (1). The wireless device can perform the first UL transmission based on the first HARQ process ID. The wireless device can perform a second UL transmission based on a second HARQ process ID after performing the first UL transmission.

[0417] According to an example embodiment, the wireless device can determine the third UL authorization for a periodic third UL transmission based on CG configuration and parameters. The wireless device can determine the third HARQ process ID for the third UL transmission by incrementing the second HARQ process ID by one (1). The wireless device can perform the third UL transmission based on the third HARQ process ID after performing the second UL transmission.

[0418] In example embodiments (e.g., such as) Figure 23 As shown, the wireless device can receive: a configured authorization (CG) configuration indicating periodicity; and / or parameters indicating the number of resources in the periodicity. The wireless device can determine a first UL authorization for a first UL transmission in the periodicity based on the CG configuration and parameters, wherein the first UL transmission is the first UL transmission configured by the CG configuration. The wireless device can determine a second UL authorization for a second UL transmission based on the CG configuration and parameters. The wireless device can determine a first HARQ process ID for the first UL transmission based on an equation determined by the HARQ process ID. The wireless device can determine a second HARQ process ID for the second UL transmission based on the first HARQ process ID. The wireless device can perform the first UL transmission based on the first HARQ process ID. The wireless device can perform the second UL transmission based on the second HARQ process ID after performing the first UL transmission.

[0419] In example embodiments (e.g., such as) Figure 23 As shown, the wireless device can receive: a configured authorization (CG) configuration indicating periodicity; and / or parameters indicating the number of resources in the periodicity. The wireless device can determine the UL authorization for a periodic UL transmission based on the CG configuration and parameters. The wireless device can determine the first HARQ process ID for the UL transmission: if the UL transmission is the first UL transmission configured by the CG, then it is determined based on an equation based on the HARQ process ID; and / or based on incrementing the second HARQ process ID of the last UL transmission to be used for the UL transmission by a certain value. The wireless device can perform the UL transmission based on the first HARQ process ID.

[0420] In example embodiments (e.g., such as) Figure 24 As shown, the wireless device can receive one or more Configurable Authorized (CG) configuration parameters, which indicate: a periodicity associated with the CG configuration; and / or multiple resources within the periodicity. The wireless device can transmit uplink (UL) data via resources among the multiple resources based on a Hybrid Automatic Repeat Request (HARQ) process index, wherein the HARQ process index can be based on the order of the resources among the one or more resources.

[0421] In example embodiments (e.g., such as) Figure 24As shown, the wireless device can receive one or more Configurable Authorized (CG) configuration parameters, which indicate: a periodicity associated with the CG configuration; and / or one or more resources within the periodicity. The wireless device can transmit uplink (UL) data via resources within one or more resources based on a Hybrid Automatic Repeat Request (HARQ) process index, wherein the HARQ process index can be based on the order of resources within one or more resources.

[0422] According to an example embodiment, the order may be the Nth of the number of resources in a periodicity.

[0423] In example embodiments (e.g., such as) Figure 24 As shown, the wireless device can receive a Configuration Grant (CG) configuration; and / or a periodicity associated with the CG configuration, wherein the CG configuration indicates a first resource in a time interval associated with the periodicity and a second resource in the time interval. The wireless device can transmit first uplink (UL) data via the first resource based on a first Hybrid Automatic Repeat Request (HARQ) process index, wherein the HARQ process index is based on an equation. The wireless device can transmit second UL data via a second resource based on a second HARQ process index, wherein the second HARQ process index may be based on the first HARQ process index.

[0424] According to an example embodiment, the second HARQ process index may be based on incrementing the first HARQ process index by a certain value. According to an example embodiment, the value may be one (1).

[0425] According to the example embodiment, the time interval can be a periodicity of the CG configuration.

[0426] According to the example embodiment, the second HARQ process ID can be based on the modulo operation of nrofHARQ-Processes.

[0427] According to the example embodiment, nrofHARQ-Processes can be the number of HARQ processes configured for CG configuration.

[0428] According to an example embodiment, the wireless device may maintain the value of the first HARQ process index through a UE variable or a counter.

[0429] According to the example implementation, the second HARQ process index can be based on an incrementing UE variable or a counter.

[0430] According to an example embodiment, the equation can be used to determine the HARQ process index. According to an example embodiment, the equation can be based on CURRENT_symbol. According to an example embodiment, the equation can be based on periodicity. According to an example embodiment, the equation can be based on modulo operations of nrofHARQ-Processes.

[0431] According to an example embodiment, CURRENT_symbol can be based on the first symbol of the UL transmission of UL data. According to an example embodiment, CURRENT_symbol can be based on (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in the frame × numberOfSymbolsPerSlot + number of symbols in the slots), where numberOfSlotsPerFrame is the number of consecutive slots per frame, and numberOfSymbolsPerSlot is the number of consecutive symbols per slot.

[0432] According to the example implementation, nrofHARQ-Processes is the number of HARQ processes configured for CG configuration.

[0433] In example embodiments (e.g., such as) Figure 24 As shown), the wireless device can receive parameters indicating a periodic configured authorization (CG) configuration; and / or an indication of the number of PUSCH resources in a periodicity. The wireless device can determine a first UL authorization for a first UL transmission in a first period of the CG based on the CG configuration and / or parameters, wherein the first UL transmission may be the first UL transmission in the first period. The wireless device can determine a first HARQ process ID for the first UL transmission based on an equation used for HARQ process ID determination. The wireless device can determine a second UL authorization for a second UL transmission in the first period of the CG based on the CG configuration and / or parameters. The wireless device can determine a second HARQ process ID for the second UL transmission based on incrementing the first HARQ process ID by one (1). The wireless device can determine a third UL authorization for a third UL transmission in the second period of the CG based on the CG configuration and / or parameters, wherein the third UL transmission may be the first first UL transmission in the second period. The wireless device can determine a third HARQ process ID for the third UL transmission based on the equation. The wireless device can determine a fourth UL authorization for a fourth UL transmission in the second period of the CG based on the CG configuration and / or parameters. The wireless device can determine the fourth HARQ process ID of the fourth UL transmission by incrementing the third HARQ process ID by one (1).

[0434] According to an example embodiment, the wireless device may perform a first UL transmission based on a first HARQ process ID. The wireless device may perform a second UL transmission based on a second HARQ process ID after performing the first UL transmission. The wireless device may perform a third UL transmission based on a third HARQ process ID after performing the second UL transmission. The wireless device may perform a fourth UL transmission based on a fourth HARQ process ID after performing the third UL transmission.

[0435] Figure 26 An example embodiment is illustrated. At 2601, the wireless device receives one or more configuration parameters indicating a periodicity associated with a Configuration Authorization (CG) configuration and the number of resources within that periodicity. At 2602, the wireless device transmits uplink (UL) data based on the CG configuration and a Hybrid Automatic Repeat Request (HARQ) process index, wherein the HARQ process index is based on the number of resources within the periodicity.

Claims

1. A wireless device comprising: One or more processors; as well as A memory storing instructions that, when executed by the one or more processors, cause the wireless device to: Receive the configured and authorized CG configuration, wherein the CG configuration indicates: The period of the CG configuration; and The number of consecutive time slots during multiple transmission opportunities within the period; and Uplink data is transmitted via one of the plurality of transmission opportunities, wherein the Hybrid Automatic Repeat Request (HARQ) process index ID used for the transmission of the uplink data is based on: The number of consecutive time slots of the plurality of transmission opportunities within the period; and The offset of the transmission timing among the plurality of transmission timings within the period, wherein the offset is based on the order of the transmission timings among the plurality of transmission timings within the period.

2. The wireless device of claim 1, wherein the HARQ process ID is associated with a first symbol of the transmission of the uplink data.

3. The wireless device of claim 1, wherein the HARQ process ID is identical to the number of HARQ processes indicated by the CG configuration.

4. The wireless device of claim 1, wherein the instructions further cause the wireless device to: Based on one or more criteria, a second transmission opportunity is determined that does not occur within the plurality of transmission opportunities during the period; and Based on the determination that transmission will not occur during the second transmission timing, the HARQ process ID will not be incremented.

5. The wireless device of claim 4, wherein the one or more standards include at least one of the following: The second transmission timing conflicts with the downlink DL symbol indicated by the Time Division Duplex (TDD) common configuration or TDD dedicated configuration; or The second transmission timing conflicts with the symbol of the SSB, which has an index provided by the synchronization signal and the physical broadcast channel block SSB configuration.

6. The wireless device of claim 1, wherein the offset is based on the Kth transmission opportunity among the plurality of transmission opportunities within the period.

7. The wireless device of claim 1, wherein the HARQ process ID is determined in response to the CG configuration indicating the Multiple Physical Uplink Shared Channel (PUSCH CG) in the period.

8. The wireless device according to claim 1, wherein: Of the plurality of transmission opportunities, the transmission opportunity occurs earliest within the period; and The offset value at the time of transmission is zero.

9. The wireless device of claim 1, wherein for a third transmission opportunity occurring after the second transmission opportunity within the period, the third value of the offset is based on incrementing the second value of the offset of the second transmission opportunity by one.

10. A base station, comprising: One or more processors; as well as A memory storing instructions that, when executed by the one or more processors, cause the base station to: Transmit the configured and authorized CG configuration to the wireless device, the CG configuration indicating: The period of the CG configuration; and The number of consecutive time slots during multiple transmission opportunities within the period; and Uplink data is received via one of the plurality of transmission opportunities, wherein the Hybrid Automatic Repeat Request (HARQ) process index ID used for transmitting the uplink data is based on: The number of consecutive time slots of the plurality of transmission opportunities within the period; and The offset of the transmission timing among the plurality of transmission timings within the period, wherein the offset is based on the order of the transmission timings among the plurality of transmission timings within the period.

11. The base station of claim 10, wherein the HARQ process ID is associated with a first symbol of the transmission of the uplink data.

12. The base station of claim 10, wherein the HARQ process ID is identical to the number of HARQ processes indicated by the CG configuration.

13. The base station according to claim 10, wherein the instructions further cause the base station to: Based on one or more criteria, reception is determined to occur during a second transmission opportunity that is not among the plurality of transmission opportunities within the said period; and Based on the determination that reception will not occur during the second transmission timing, the HARQ process ID will not be incremented.

14. The base station of claim 13, wherein the one or more standards include at least one of the following: The second transmission timing conflicts with the downlink DL symbol indicated by the Time Division Duplex (TDD) common configuration or TDD dedicated configuration; or The second transmission timing conflicts with the symbol of the SSB, which has an index provided by the synchronization signal and the physical broadcast channel block SSB configuration.

15. The base station of claim 10, wherein the offset is based on the Kth transmission timing among the plurality of transmission timings within the period.

16. The base station of claim 10, wherein the HARQ process ID is based on the CG configuration indicating the multi-physical uplink shared channel (PUSCH CG) within the period.

17. The base station according to claim 10, wherein: Of the plurality of transmission opportunities, the transmission opportunity occurs earliest within the period; and The offset value at the time of transmission is zero.

18. 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: Receive the configured and authorized CG configuration, wherein the CG configuration indicates: The period of the CG configuration; and The number of consecutive time slots during multiple transmission opportunities within the period; and Uplink data is transmitted via one of the plurality of transmission opportunities, wherein the Hybrid Automatic Repeat Request (HARQ) process index ID used for the transmission of the uplink data is based on: The number of consecutive time slots of the plurality of transmission opportunities within the period; and The offset of the transmission timing among the plurality of transmission timings within the period, wherein the offset is based on the order of the transmission timings among the plurality of transmission timings within the period.

Images