Acknowledged Transmission in a Wireless Communication System

Abstract

In some embodiments, a wireless device receives a downlink channel that is semi-persistently scheduled. The downlink channel is associated with a first uplink control channel indicated by feedback timing parameters of the semi-persistent scheduling. The wireless device determines that a channel occupancy duration associated with the downlink channel ends before the first uplink control channel. The wireless device determines a second uplink control channel different from the first uplink control channel and multiplexes feedback information of the downlink channel in the second uplink control channel.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 961,874, filed on January 16, 2020, and U.S. Provisional Patent Application No. 62 / 975,945, filed on February 13, 2020, the entire contents of each of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0004] Figure 1A and Figure 1B show an exemplary mobile communication network in which embodiments of the present disclosure may be implemented.

[0005] Figure 2A and Figure 2B show a New Radio (NR) user plane and control plane protocol stack, respectively.

[0006] Figure 3 show Figure 2A an example of services provided between protocol layers of the NR user plane protocol stack.

[0007] Figure 4A show Figure 2A an exemplary downlink data stream flowing through the NR user plane protocol stack.

[0008] Figure 4B show an exemplary format of a MAC sub - header in a MAC PDU.

[0009] Figure 5A and Figure 5B show the mapping between logical channels, transport channels, and physical channels for downlink and uplink, respectively.

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

[0011] Figure 7 show an exemplary configuration of an NR frame into which OFDM symbols are grouped.

[0012] Figure 8 show an exemplary configuration of time slots in the time and frequency domains of an NR carrier.

[0013] Figure 9 show an example of bandwidth adaptation using three configured BWPs of an NR carrier.

[0014] Figure 10AShows three carrier aggregation configurations with two component carriers.

[0015] Figure 10B Shows an example of how an aggregated cell can be configured into one or more PUCCH groups.

[0016] Figure 11A Shows an example of the SS / PBCH block structure and location.

[0017] Figure 11B Shows an example of CSI-RS mapped in the time and frequency domains.

[0018] Figure 12A and Figure 12B Show examples of three downlink and uplink beam management procedures, respectively.

[0019] Figure 13A 、 Figure 13B and Figure 13C Show a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure, respectively.

[0020] Figure 14A Shows an example of the CORESET configuration of a bandwidth part.

[0021] Figure 14B Shows an example of the CCE to REG mapping for DCI transmission on CORESET and PDCCH processing.

[0022] Figure 15 Shows an example of a wireless device communicating with a base station.

[0023] Figure 16A 、 Figure 16B 、 Figure 16C and Figure 16D Show an exemplary structure for uplink and downlink transmissions.

[0024] Figure 17 Shows an example of HARQ acknowledgement timing determination according to some embodiments.

[0025] Figure 18 Shows an example of signaling for configuration, activation, transmission, and deactivation of DL SPS according to some embodiments.

[0026] Figure 19 Shows an example of scheduling SPS PDSCH and the corresponding PUCCH according to some embodiments.

[0027] Figure 20Shows an example of SPS PDSCH scheduling according to some embodiments, where the corresponding PUCCH is not within the same channel occupancy.

[0028] Figure 21 Shows an example of SPS PDSCH scheduling according to some embodiments, where in addition to the SPS PDSCH, the corresponding PUCCH is scheduled for HARQ feedback transmission.

[0029] Figure 22 Shows an example of SPS PDSCH scheduling according to some embodiments, where the corresponding PUCCH is only scheduled for HARQ feedback transmission of the SPS PDSCH.

[0030] Figure 23 Shows an example of dynamic scheduling indicating a second PUCCH resource covering semi-persistent scheduling of a first PUCCH resource according to some embodiments.

[0031] Figure 24 Shows an example of dynamic scheduling indicating postponed HARQ feedback transmission before the SPS PDSCH covering semi-persistent scheduling of a first PUCCH resource for HARQ feedback transmission according to some embodiments.

[0032] Figure 25 Shows an example of dynamic scheduling indicating postponed HARQ feedback transmission after the SPS PDSCH covering semi-persistent scheduling of a first PUCCH resource for HARQ feedback transmission according to some embodiments.

[0033] Figure 26 Shows an example of postponing HARQ feedback transmission of the SPS PDSCH based on an indication of receiving a non-numerical timing value according to some embodiments.

[0034] Figure 27 Shows an example of postponing HARQ feedback transmission of the SPS PDSCH based on an indication of receiving a non-numerical timing value within the same COT as the SPS PDSCH according to some embodiments.

[0035] Figure 28 Shows an example of discarding pending HARQ feedback in a semi-static codebook due to BWP switching according to some embodiments.

[0036] Figure 29 Shows an example of discarding pending HARQ feedback in a dynamic / enhanced dynamic codebook due to BWP switching according to some embodiments.

[0037] Figure 30Shows another example of discarding pending HARQ feedback in a dynamic / enhanced dynamic codebook due to BWP switching according to some embodiments.

[0038] Figure 31 Shows an example of different behaviors regarding HARQ feedback with a dynamic / enhanced dynamic codebook due to BWP switching according to some embodiments.

[0039] Figure 32 Shows an example of cross-COT scheduling for DL data reception and HARQ feedback transmission in an unlicensed band according to some embodiments.

[0040] Figure 33 Shows an example of discarding pending HARQ-ACK associated with a non-numerical HARQ feedback timing indicator due to BWP switching before receiving a second DCI indicating a PUCCH resource for HARQ-ACK transmission according to some embodiments.

[0041] Figure 34 Shows an example of maintaining pending HARQ-ACK associated with a non-numerical HARQ feedback timing indicator in the case of BWP switching before receiving a second DCI indicating a PUCCH resource for HARQ-ACK transmission according to some embodiments.

[0042] Figure 35 Shows an example of extending the BWP inactivity timer based on a non-numerical HARQ feedback timing indicator according to some embodiments.

[0043] Figure 36 Shows an example of pausing the BWP inactivity timer based on a non-numerical HARQ feedback timing indicator according to some embodiments.

[0044] Figure 37 Shows an example of pausing the BWP inactivity timer of a cell in a self-carrier scheduling scenario based on a non-numerical HARQ feedback timing indicator according to some embodiments.

[0045] Figure 38 Shows an example of pausing the BWP inactivity timer of a cell in a cross-carrier scheduling scenario based on a non-numerical HARQ feedback timing indicator according to some embodiments. Detailed Description

[0046] In this disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in an environment and context. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the invention should not be limited by any of the described exemplary embodiments. The embodiments of the disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the disclosure. Any figures that highlight functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough such that it can be utilized in a manner different from that shown. For example, the actions listed in any flowchart can be reordered or used only optionally in some embodiments.

[0047] Embodiments can be configured to operate as needed. When certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanisms can be executed. Exemplary criteria can be at least partially based on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments can be applied. Thus, exemplary embodiments that selectively implement the disclosed protocol can be implemented.

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

[0049] In the present disclosure, "a", "an", and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase following the term "may" is an example of one of the various suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms "comprises" and "consists of" enumerate one or more components of the element being described. The term "comprises" is interchangeable with "includes" and does not exclude components not enumerated from being included in the element being described. In contrast, "consists 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, "only based on". As used herein, the term "and / or" represents any possible combination of the enumerated elements. For example, "A, B, and / or C" can represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0050] If A and B are sets and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is an example of one of the various 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 term "in response to" is an example of one of the various 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 term "depending on" is an example of one of the various suitable possibilities that may or may not be used in one or more different embodiments. The phrase "employ / use" (or equivalently "at least employ / use") indicates that the phrase following the term "employ / use" is an example of one of the various suitable possibilities that may or may not be used in one or more different embodiments.

[0051] The term "configured" can relate to the capabilities of a device, whether the device is in an operating state or a non-operating state. "Configured" can also mean specific settings within a device that affect the operating characteristics of the device, whether the device is in an operating state or a non-operating state. In other words, hardware, software, firmware, registers, memory values, etc. can be "configured" within a device to provide the device with specific characteristics, whether the device is in an operating state or a non-operating state. The term such as "control message induced in a device" can mean that the control message has parameters that can be used to configure specific characteristics in a device or parameters that can be used to implement certain actions in a device, whether the device is in an operating state or a non-operating state.

[0052] In the present disclosure, a parameter (or equivalently referred to as a field or information element: IE) can include one or more information objects, and an information object can 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 exemplary embodiment, when one or more messages include a plurality of parameters, it means that the parameters among the plurality of parameters are in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0053] Many of the features presented are described as optional by using "may" or by using parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by making a selection from the group of optional features. The present disclosure should be construed as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0054] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined herein as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or 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++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages (HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure the connections between the less-functional internal hardware modules on the programmable device. The technologies mentioned are often used in combination to achieve the result of a functional module.

[0055] 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. As Figure 1A shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and wireless devices 106.

[0056] The CN 102 may provide an interface to one or more data networks (DNs) (such as a public DN (e.g., the Internet), a private DN, and / or an operator-internal DN) to the wireless devices 106. As part of the interface function, the CN 102 may establish an end-to-end connection between the wireless devices 106 and one or more DNs, authenticate the wireless devices 106, and provide a charging function.

[0057] RAN 104 can connect CN 102 to wireless device 106 via radio communication over the 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 wireless device 106 over the air interface is referred to as the downlink, while the communication direction from wireless device 106 to RAN 104 over the air interface is referred to as the uplink. Frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques can be used to separate downlink transmissions from uplink transmissions.

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

[0059] RAN 104 can include one or more base stations (not shown). The term "base station" can 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 head (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 can include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0060] The base stations included in RAN 104 can include one or more sets of antennas for communicating with wireless device 106 over the air interface. For example, one or more of the base stations can include three sets of antennas to control three cells (or sectors) respectively. The size of a cell can 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 in the cell. The cells of the base stations can together provide radio coverage over a wide geographic area to support the movement of wireless device 106.

[0061] In addition to three-sector sites, other implementations of the base station are possible. For example, one or more of the base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more of the base stations in RAN 104 can be implemented as access points, baseband processing units coupled to a number of remote radio heads (RRHs), and / or repeaters or relay nodes for extending the coverage area of a 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. The repeater node can amplify and replay the radio signals received from the donor node. The relay node can perform the same / similar functions as the repeater node, but can decode the radio signals received from the donor node to eliminate noise before amplifying and replaying the radio signals.

[0062] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna patterns and similar high-level transmission powers. RAN 104 can 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 that overlap with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas with weak macrocell coverage. Examples of small cell base stations, in decreasing order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0063] The 3rd Generation Partnership Project (3GPP) was established in 1998 to provide global specification standardization for mobile communication networks similar to the mobile communication network 100 in Figure 1A So far, 3GPP has developed specifications for three generations of mobile networks: the 3rd generation (3G) network known as the Universal Mobile Telecommunications System (UMTS), the 4th generation (4G) network known as Long Term Evolution (LTE), and the 5th generation (5G) network known as the 5G System (5GS). The embodiments of the present disclosure are described with reference to the RAN of the 3GPP 5G network known as the Next Generation RAN (NG-RAN). These embodiments can be applicable to the RANs of other mobile communication networks, such as Figure 1A the RAN 104 in , the RANs of early 3G and 4G networks, and those of future networks not yet specified (e.g., the 3GPP 6G network). The NG-RAN implementation employs the 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.

[0064] Figure 1BFIG. 150 shows another exemplary mobile communication network in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. As shown in Figure 1B , 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 UEs 156). These components may be implemented and operated in the same or similar manner as the corresponding components described with respect to Figure 1A .

[0065] The 5G-CN 152 provides an interface to one or more DNs for the UEs 156, such as a public DN (e.g., the Internet), a private DN, and / or an operator-internal DN. As part of the interface function, the 5G-CN 152 may establish an end-to-end connection between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide a charging function. Compared with the CN of the 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes constituting the 5G-CN 152 may be defined as network functions that provide services to other network functions via interfaces. The network functions of the 5G-CN 152 may 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).

[0066] As shown in Figure 1B , the 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, which are shown as a single component AMF / UPF 158 for ease of illustration in Figure 1B . The UPF 158B may act as a gateway between the NG-RAN 154 and the one or more DNs. Functions that the UPF 158B may perform include, for example, packet routing and forwarding, packet inspection, and user plane policy rule enforcement, traffic usage reporting, support for uplink classification for routing traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may act as an anchor for mobility within / across radio access technologies (RATs), an external protocol (or packet) data unit (PDU) session point for interconnecting with the one or more DNs, and / or a pivot for supporting multi-homed PDU sessions. The UEs 156 may be configured to receive services via PDU sessions, which are logical connections between the UEs and the DNs.

[0067] The functions that the AMF 158A can perform include, for example: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, CN-inter node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, in-system and inter-system mobility support, access authentication, access authorization including roaming right verification, mobility management control (subscription and policy), network slice support, and / or session management function (SMF) selection. NAS can refer to the functions operating between the CN and the UE, and AS can refer to the functions operating between the UE and the RAN.

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

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

[0070] As Figure 1BAs shown, gNB 160 and / or ng-eNB 162 can be connected 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 direct physical connections and / or indirect connections via a potential transport network such as an Internet Protocol (IP) transport network. gNB 160 and / or ng-eNB 162 can be connected to UE 156 via the Uu interface. For example, as Figure 1B shown, gNB 160A can be connected to UE 156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces can be used by the Figure 1B network elements in to exchange data and signaling messages and can include two planes: a user plane and a control plane. The user plane can handle data of interest to the user. The control plane can handle signaling messages of interest to the network elements.

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

[0072] gNB 160 can provide NR user plane and control plane protocol termination to UE 156 via the Uu interface. For example, 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. 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 the 3GPP 4G radio access technology. For example, 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.

[0073] 5G-CN 152 is described as being configured to handle NR and 4G radio access. A person of ordinary skill in the art will understand that NR has the possibility to connect to a 4G core network in a mode referred to as "non-standalone operation". In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B only one AMF / UPF 158 is shown, a gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0074] As discussed, Figure 1B interfaces between network elements in

[0075] Figure 2A and Figure 2B can be associated with the protocol stacks used by the network elements to exchange data and signaling messages. The protocol stack can include two planes: the user plane and the control plane. The user plane can handle data of interest to the user, while the control plane can handle signaling messages of interest to the network elements. Figure 2A and Figure 2B show examples of the NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220, respectively. Figure 1B The protocol stacks shown in

[0076] Figure 2A and

[0077] Figure 3 can be the same as or similar to those for the Uu interface between UE156A and gNB 160A shown in Figure 2A and Figure 3Starting from the top, the SDAPs 215 and 225 can perform QoS flow processing. The UE 210 can receive services through a PDU session, which can be a logical connection between the UE 210 and the DN. The PDU session can have one or more QoS flows. The UPF in the CN (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). The 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 the QoS flow and the data radio bearer can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flow and the data radio bearer through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 can mark the downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between the QoS flow and the data radio bearer.

[0078] The PDCPs 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 the data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from the expected source. The PDCPs 214 and 224 can perform retransmission of undelivered packets, in-order delivery and reordering of packets, and removal of packets that are repeatedly received due to, for example, handover within the gNB. The PDCPs 214 and 224 can perform packet duplication to increase the likelihood of the packet being received, and remove any duplicate packets at the receiver. Packet duplication can be applicable to services that require high reliability.

[0079] Although Figure 3 not shown in the figure, the PDCPs 214 and 224 can perform mapping / demapping between the split radio bearer and the RLC channel in a dual-connectivity scenario. Dual-connectivity is a technology that allows the UE to be connected to two cells or more generally to two cell groups: the master cell group (MCG) and the secondary cell group (SCG). A split bearer is a split bearer when a single radio bearer (such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225) is handled by the cell groups in the dual-connectivity. The PDCPs 214 and 224 can map / demap the split radio bearer between the RLC channels belonging to the cell groups.

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

[0081] MAC 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing can include: multiplexing data units belonging to the one or more logical channels into / from transport blocks (TBs) delivered to / from PHY 211 and 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling can be performed in gNB 220 (at MAC 222) for both downlink and uplink. MAC 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 handling between logical channels of UE 210 by means of logical channel prioritization, and / or padding. MAC 212 and 222 can support one or more parameter sets and / or transmission timings. In an example, the mapping restrictions in logical channel prioritization can control which parameter set and / or transmission timing a logical channel can use. As Figure 3 shown, MAC 212 and 222 can provide logical channels as services to RLC 213 and 223.

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

[0083] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4AShows the downlink data flow of three IP packets (n, n+1, and m) flowing through the NR user plane protocol stack to generate two transport blocks (TBs) at the gNB 220. The uplink data flow flowing through the NR user plane protocol stack can be similar to the Figure 4A depicted downlink data flow.

[0084] Figure 4A The downlink data flow of starts when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A , the SDAP 225 maps IP packets n and n+1 to the first radio bearer 402, and maps IP packet m to the second radio bearer 404. An SDAP header (marked as "H" in Figure 4A ) is added to the IP packets. Data units from / to higher protocol layers are called service data units (SDUs) of lower protocol layers, and data units to / from lower protocol layers are called protocol data units (PDUs) of higher protocol layers. As shown in Figure 4A , the data unit from the SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of the SDAP 225.

[0085] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., regarding Figure 3 ), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 can perform IP header compression and encryption and forward its output to the RLC 223. The RLC 223 can optionally perform segmentation (e.g., as shown for IP packet m in Figure 4A ) and forward its output to the MAC 222. The MAC 222 can multiplex a number of RLC PDUs and can attach a MAC sub-header to the RLC PDUs to form transport blocks. In NR, the MAC sub-header can be distributed throughout the MAC PDU, as shown in Figure 4A . In LTE, the MAC sub-header can be entirely at the start of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be calculated before assembling the complete MAC PDU.

[0086] Figure 4BIllustrates an exemplary format of a MAC sub-header in a MAC PDU. The MAC sub-header includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU corresponding to the MAC sub-header; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to assist in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

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

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

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

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

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

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

[0093] - Dedicated Control Channel (DCCH), which is used to carry control messages to a specific UE / carry control messages from a specific UE to configure the UE; and

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

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

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

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

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

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

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

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

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

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

[0104] - Physical Downlink Control Channel (PDCCH), which is used to carry Downlink Control Information (DCI), and the DCI can include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

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

[0106] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, and the UCI can include HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

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

[0108] Similar to physical control channels, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figure 5A and Figure 5B , 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.

[0109] Figure 2B An exemplary NR control plane protocol stack is shown. As in Figure 2BAs shown, the NR control plane protocol stack may use the same / similar first four protocol layers as the exemplary 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 protocol 217 and 237 at the top of the NR control plane protocol stack.

[0110] NAS protocol 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 the CN. NAS protocol 217 and 237 can provide control plane functions between UE 210 and AMF 230 via signaling messages called NAS messages. There is no direct path through which NAS messages can be transmitted between UE 210 and AMF 230. The AS of the Uu and NG interfaces can be used to transmit NAS messages. NAS protocol 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0111] RRC 216 and 226 can provide control plane functions between UE 210 and gNB 220, or more generally between UE 210 and the RAN. RRC 216 and 226 can provide control plane functions between UE 210 and gNB 220 via signaling messages called RRC messages. Signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers can be used to transmit RRC messages between UE 210 and the RAN. MAC can multiplex control plane and user plane data into the same transport block (TB). Control plane functions that RRC 216 and 226 can provide include: broadcasting of system information related to the AS and NAS; paging initiated by the CN or RAN; establishment, maintenance, and release of the RRC connection between UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of the report; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS message transfer. As part of establishing the RRC connection, RRC 216 and 226 can establish an RRC context, which can involve configuring parameters for communication between UE 210 and the RAN.

[0112] Figure 6 is an example diagram showing the RRC state transition of a UE. The UE can be associated withFigure 1A the wireless device 106 depicted in Figure 2A and Figure 2B the UE 210 depicted in or any other wireless device described in the present disclosure. As Figure 6 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).

[0113] In RRC connected 602, the UE has an established RRC context and can have at least one RRC connection with a base station. The base station can be similar to one of the following: Figure 1A the one or more base stations included in the RAN 104 depicted in Figure 1B one of the gNB 160 or ng-eNB 162 depicted in Figure 2A and Figure 2B the gNB220 depicted in or any other base station described in the present disclosure. The base station connected to the UE can have an RRC context for the UE. The RRC context, referred to as the UE context, can include parameters for communication between the UE and the base station. These parameters can include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., related 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 connected 602, the mobility of the UE can be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE can measure the 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 serving base station of the UE can request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection deactivation procedure 610.

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

[0115] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows a quick transition to RRC Connected 602 with reduced signaling overhead compared to the transition from RRC Idle 604 to RRC Connected 602. While in RRC Inactive 606, the UE may be in a sleep state, and the mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 through a Connection Resumption Procedure 614, or to RRC Idle 604 through a Connection Release Procedure 616, which may be the same or similar to the Connection Release Procedure 608.

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

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

[0118] RAN areas can be used to track UEs at the RAN level. For a UE in the RRC inactive 606 state, a RAN notification area can be assigned to the UE. The RAN notification area can include a list of one or more cell identities, RAI, or TAI. In an example, a base station can belong to one or more RAN notification areas. In an example, a cell can belong to one or more RAN notification areas. If the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE can perform a notification area update to the RAN to update the UE's RAN notification area.

[0119] The base station that stores the RRC context for the UE or the last serving base station of the UE can be referred to as the anchor base station. The anchor base station can maintain the RRC context for the UE at least during the period when the UE stays in the RAN notification area of the anchor base station and / or during the period when the UE stays in the RRC inactive 606 state.

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

[0121] In NR, physical signals and physical channels (regarding Figure 5A and Figure 5BThe data (discussed above) can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data over F orthogonal sub-carriers (or tones). Before transmission, the data can be mapped onto a series of complex symbols called source symbols (e.g., M-ary Quadrature Amplitude Modulation (M-QAM) symbols or M-ary Phase Shift Keying (M-PSK) symbols), and divided into F parallel symbol streams. The F parallel symbol streams can be considered as if they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of the F sine basis functions corresponding to the F orthogonal sub-carriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal sub-carriers. The F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be scrambled using an FFT block before being processed by the IFFT block. This operation results in a Discrete Fourier Transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the Peak-to-Average Power Ratio (PAPR). The inverse processing can be performed on the OFDM symbol at the receiver using an FFT block to recover the data mapped onto the source symbols.

[0122] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown. The NR frame can be identified by a System Frame Number (SFN). The SFN can repeat over a period of 1024 frames. As shown, the duration of one NR frame can be 10 milliseconds (ms) and can include 10 sub-frames with a duration of 1 ms each. A sub-frame can be divided into time slots, which include, for example, 14 OFDM symbols per time slot.

[0123] The duration of a time slot can depend on the parameter set of the OFDM symbol used for 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 sets in NR, the subcarrier spacing can be scaled by a power of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration can be scaled by a power of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following subcarrier spacing / cyclic prefix duration combinations: 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.

[0124] 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 The transmission structure of the time slot duration and time slots per subframe related to the parameter set is shown (for ease of illustration, Figure 7 the parameter set with a subcarrier spacing of 240 kHz is not shown). A subframe in NR can be used as a time reference independent of the parameter set, while a time slot can be used as a unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the time slot duration and start at any OFDM symbol and continue for as many symbols as required for transmission. These partial time slot transmissions can be referred to as mini-slots or sub-slot transmissions.

[0125] Figure 8 An exemplary configuration of a time slot in the time and frequency domains of an NR carrier is shown. The time slot includes 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 by one subcarrier in the frequency domain, as Figure 8 shown. An RB spans twelve consecutive REs in the frequency domain, as Figure 8 shown. An NR carrier can be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. If this limit is used, the NR carrier can be limited to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on a limit of 400 MHz bandwidth per carrier.

[0126] Figure 8Shows a single parameter set used across the entire bandwidth of an NR carrier. In other exemplary configurations, multiple parameter sets may be supported on the same carrier.

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

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

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

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

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

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

[0133] The base station may 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 for the UE, the default downlink BWP may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

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

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

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

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

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

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

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

[0141] In an example, up to 32 CCs can be aggregated. The aggregated CCs can have the same or different bandwidths, subcarrier spacings, and / or duplex schemes (TDD or FDD). The serving cells 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.

[0142] When using CA, one of the aggregated cells in the aggregated cells for a UE can be referred to as a primary cell (PCell). The PCell can be the serving cell to which the UE is initially connected at RRC connection establishment, re - establishment, and / or handover. The PCell can provide the UE with NAS mobility information and security inputs. 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 for the UE can be referred to as secondary cells (SCells). In an example, an SCell can be configured after the PCell is configured for the UE. For example, an SCell can be configured through the RRC connection re - configuration procedure. In the downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DLSCC). In the uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

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

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

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

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

[0147] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, the HARQ entity can operate on the serving cell. Transport blocks can be generated according to the assignment / grant for each serving cell. The transport block and potential HARQ retransmissions of the transport block can be mapped to the serving cell.

[0148] 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, as Figure 5A shown). In the uplink, the UE can transmit one or more RS to the base station (e.g., DMRS, PT-RS, and / or SRS, as Figure 5B shown). The PSS and SSS can be transmitted by the base station and used by the UE to synchronize the UE with the base station. The PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, SSS, and PBCH. The base station can periodically transmit bursts of SS / PBCH blocks.

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

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

[0151] The UE may not know the position of the SS / PBCH block in the time and frequency domains (e.g., in the case where 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 position 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 positions within the carrier, as indicated by the synchronization raster. If the PSS is found at a certain position in the time and frequency domains, the UE can determine the positions of the SSS and PBCH respectively based on the known structure of the SS / PBCH block. 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 raster. In the example, cell selection / search and / or reselection can be based on the CD-SSB.

[0152] 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 respectively based on the sequences of the PSS and SSS. The UE can determine the position of the frame boundary of the cell based on the position of the SS / PBCH block. For example, the SS / PBCH block can indicate that it has been transmitted according to a transmission pattern, where the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0153] The PBCH can use QPSK modulation and can use forward error correction (FEC). The FEC can use polar coding. One or more symbols spanned by the PBCH can carry one or more DMRSs for demodulating the PBCH. The PBCH can include an indication of the current system frame number (SFN) of the cell and / or the SS / PBCH block timing index. These parameters can assist the UE in time synchronization with the base station. The PBCH can include a master information block (MIB) for providing one or more parameters to the UE. The MIB can be used by the UE to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI can include system information block type 1 (SIB1). The SIB1 can contain the 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 include the SIB1. The parameters provided in the MIB can be used to decode the SIB1. The PBCH can indicate the non-existence of the SIB1. Based on the PBCH indicating the non-existence of the SIB1, the UE can point to a frequency. The UE can search for the SS / PBCH block at the frequency pointed to by the UE.

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

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

[0156] In an example, within the frequency range of a carrier, the base station can transmit multiple SS / PBCH blocks. In an example, the first physical cell identifier (PCI) of the first SS / PBCH block of the multiple SS / PBCH blocks can be different from the second PCI of the second SS / PBCH block of the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency positions can be different or the same.

[0157] CSI-RS can be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station can utilize one or more CSI-RSs 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-RSs to configure the UE. The UE can measure the one or more CSI-RSs. The UE can estimate the downlink channel state and / or generate a CSI report based on the measurement of the one or more downlink CSI-RSs. The UE can provide the CSI report to the base station. The base station can use the feedback (e.g., the estimated downlink channel state) provided by the UE to perform link adaptation.

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

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

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

[0161] 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 coherent 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 the pre-loaded DMRS mode. The pre-loaded DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE with the number of pre-loaded DMRS symbols (e.g., the maximum number) for the PDSCH. The DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration can support up to 4 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 the DMRS position, DMRS pattern, and / or scrambling sequence can be the same or different. The base station can transmit the downlink DMRS and the corresponding PDSCH using the same precoding matrix. The UE can use the one or more downlink DMRS for coherent demodulation / channel estimation of the PDSCH.

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

[0163] The PDSCH can include one or more layers. The UE can assume that at least one symbol with DMRS exists on a layer among the one or more layers of the PDSCH. The higher layer can configure up to 3 DMRS for the PDSCH.

[0164] The downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of the downlink PT-RS can depend on the RRC configuration. The presence and / or pattern of the downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters that can be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the downlink PT-RS can be associated with one or more DCI parameters including at least the MCS. The NR network can support multiple 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 employ the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS can be restricted to the scheduled time / frequency duration of the UE. The downlink PT-RS can be transmitted on symbols to assist in phase tracking at the receiver.

[0165] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. The uplink DM-RS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration can support the pre-loaded DMRS mode. The pre-loaded 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 pre-loaded DMRS symbols of PUSCH and / or PUCCH, and the UE can use the pre-loaded DMRS symbols to schedule single-symbol DMRS and / or double-symbol DMRS. The NR network can support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, where the DMRS position, DMRS pattern, and / or scrambling sequence of the DMRS can be the same or different.

[0166] The PUSCH can include one or more layers, and the UE can transmit at least one symbol with DMRS on the layer(s) present in one or more layers of the PUSCH. In an example, the higher layer can configure up to three DMRS for the PUSCH.

[0167] Depending on the RRC configuration of the UE, 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 pattern of the uplink PT-RS can be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI. When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least the MCS. The radio network may 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 may employ the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS may be restricted to the scheduled time / frequency duration of the UE.

[0168] The UE may 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 may allow the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station may use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission from the UE. The base station may configure the UE semi-statically with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. The SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when the higher layer parameter indicates beam management, the SRS resources in the one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) may be transmitted at a certain time (e.g., simultaneously). The UE may transmit one or more SRS resources in the SRS resource set. The NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, where the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be employed 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 an example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

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

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

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

[0172] 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 in [description] may represent resource blocks (RBs) within the bandwidth of a cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured for the CSI-RS resource configuration by higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameter, CSI-RS sequence parameter, code division multiplexing (CDM) type parameter, frequency density, transmission comb, quasi-co-location (QCL) parameter (e.g., QCL-scrambling identity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0173] Figure 11B The three beams shown can be configured for a UE in a UE-specific configuration. Figure 11B Three beams (beam #1, beam #2, and beam #3) are shown, and more or fewer beams may be configured. CSI-RS 1101 may be assigned to beam #1, which may be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS 1102 may be assigned to beam #2, which may be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS 1103 may be assigned to beam #3, which may be transmitted in one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station may use other subcarriers in the same RB (e.g., those not used for transmitting CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time division multiplexing (TDM), the beams for a UE may be configured such that the beams for a UE use symbols from the beams of other UEs.

[0174] CSI-RSs, such as Figure 11BThose shown in, for example, CSI-RS 1101, 1102, 1103 can be transmitted by a base station and used by a UE for one or more measurements. For example, the UE can measure the reference signal received power (RSRP) of a configured CSI-RS resource. The base station can configure the UE using a reporting configuration, and the UE can report the RSRP measurement to the network (e.g., via one or more base stations) based on the reporting configuration. In an example, the base station can determine one or more transmission configuration indicator (TCI) states including a plurality of reference signals based on the reported measurement results. In an 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 a downlink transmission having a receive (Rx) beam determined based on the one or more TCI states. In an 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 of a transmission (Tx) beam based on the spatial domain filter of the corresponding 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 of the Tx beam. The UE can perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured by the base station for the UE. The base station can select and indicate the uplink beam of the UE based on measurements of one or more SRS resources transmitted by the UE.

[0175] In a beam management procedure, the UE can evaluate (e.g., measure) one or more beam pair links, including the beam pair link of a transmission beam transmitted by the base station and the channel quality of the receive beam received by the UE. Based on the evaluation, the UE can transmit a beam measurement report indicating one or more beam pair quality parameters, the one or more beam pair 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).

[0176] Figure 12AShows examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 can enable UE measurements of the transmission (Tx) beam of a transmission reception 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 a set of beams (shown as ellipses rotating in the counterclockwise direction indicated by the dashed arrow in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ellipses rotating in the clockwise direction indicated by the dashed arrow in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of the Tx beam of the TRP (shown as an ellipse rotating in the counterclockwise direction indicated by the dashed arrow in the top row of P2). The UE and / or the base station can perform Procedure P2 using a smaller set of beams than the set of beams used in Procedure P1, or using beams that are narrower than the beams used in Procedure P1. This can be referred to as beam refinement. The UE can 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.

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

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

[0179] The UE may measure the quality of the beam pair link using one or more reference signals (RSs), the one or more reference signals including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam pair link may 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 received quality (RSRQ) value, and / or CSI value measured on an RS resource. The base station may indicate that an RS resource is quasi-co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, etc.). The one or more DMRSs of the RS resource and the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from a transmission via the RS resource to the UE are similar to or the same as the channel characteristics from a transmission via the channel to the UE.

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

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

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

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

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

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

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

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

[0188] Msg 2 1312 received by the UE may include an RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after the transmission of Msg 1 1311 or in response to that transmission. 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 has been received by the base station. Msg 2 1312 may include a timing alignment command that can be used by the UE 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 a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to start the time window based on the PRACH occasion used by the UE for transmitting the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH occasion starting from the end of the preamble transmission). The one or more symbols may be determined based on the parameter set. The PDCCH may be in a common search space configured by an RRC message (e.g., Type1-PDCCH common search space). The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events that initiate the random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH occasion in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on the following: OFDM symbol index; slot index; frequency domain index; and / or UL carrier indicator of the PRACH occasion. An example of the RA-RNTI may be as follows:

[0189] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id, where s_id may be the index of the first OFDM symbol of the PRACH occasion (e.g., 0 ≤ s_id < 14), t_id may be the index of the first slot of the PRACH occasion in the system frame (e.g., 0 ≤ t_id < 80), f_id may be the index of the PRACH occasion in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for the NUL carrier and 1 for the SUL carrier).

[0190] The UE may transmit Msg3 1313 in response to successfully receiving Msg 2 1312 (e.g., using the resources identified in Msg 2 1312). Msg 3 1313 may be used for, e.g., Figure 13A contention resolution in a contention-based random access procedure as shown in Figure 13A . In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide a RAR corresponding to the UE. If the multiple UEs decode the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) may be used to increase the likelihood that a UE does not incorrectly 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 Msg2 1312 and / or any other suitable identifier if a C-RNTI is assigned).

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

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

[0193] Figure 13B A two-step contention-free random access procedure is shown. Similar to Figure 13A the four-step contention-based random access procedure shown, the base station may transmit a configuration message 1320 to the UE before the procedure is initiated. The configuration message 1320 may be similar to the configuration message 1310 in some aspects. Figure 13B The procedure shown includes the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 may be similar to Figure 13A Msg 1 1311 and Msg2 1312 shown, respectively. As can be understood from Figure 13A and Figure 13B the contention-free random access procedure may not include messages similar to Msg 3 1313 and / or Msg 4 1314.

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

[0195] ​After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in the search space indicated by an RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. In Figure 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission is addressed to the C-RNTI, the UE may determine that the random access procedure is successfully completed. For example, if the UE receives an RAR that includes 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 may determine that the random access procedure is successfully completed. The UE may determine that the response is an indication of an acknowledgement of the SI request.

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

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

[0198] The UE may initiate a two-step random access procedure for licensed spectrum and / or unlicensed spectrum. The UE may determine whether to initiate the 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 RRC state of the UE; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factor. Figure 13C The UE may determine the radio resources and / or uplink transmission power of the preamble 1341 and / or the transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control of the preamble 1341 and / or the transport block 1342. Frequency-division multiplexing (FDM), time-division multiplexing (TDM), and / or code-division multiplexing (CDM) may be used to multiplex the time-frequency resources for the transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for the transmission of the transport block 1342 (e.g., PUSCH). The RACH parameters may enable the UE to determine the reception timing and the downlink channel for monitoring and / or receiving Msg B 1332.

[0199] The transport block 1342 may include data (e.g., delay-sensitive data), the identifier of the UE, security information, and / or device information (e.g., the 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 advance 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., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if any of the following conditions are met: 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., the transport block 1342).

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

[0201]

[0202] ​Downlink control signaling may include: downlink scheduling assignment; uplink scheduling grant 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 common PDCCH (GC-PDCCH) common to a group of UEs.

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

[0204] The DCI may be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as hexadecimal "FFFE". A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate the broadcast transmission of system information. The SI-RNTI may be predefined as hexadecimal "FFFF". A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or the triggering of PDCCH-ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate contention resolution (e.g., similar to Figure 13AThe Msg 3 of Msg 3 1313 shown). Other RNTIs configured by the base station for the UE may include: 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), interruption RNTI (INT-RNTI), time slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

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

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

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

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

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

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

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

[0212] There can be five PUCCH formats, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If the transmission is more than one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with a positive or negative SR is one or two, the wireless device can transmit the UCI in the PUCCH resource using PUCCH format 0. PUCCH format 1 can occupy a number between four and fourteen OFDM symbols and can include two or fewer bits. If the transmission is four or more symbols 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 include more than two bits. If the transmission is more than one or two symbols and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. If the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code, the UE can use PUCCH format 3. PUCCH format 4 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. If the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code, the UE can use PUCCH format 4.

[0213] The base station can transmit the configuration parameters of multiple PUCCH resource sets to the UE using, for example, RRC messages. The multiple PUCCH resource sets (e.g., up to four sets) can be configured on the uplink BWP of the cell. The PUCCH resource set can be configured with: a PUCCH resource set index; multiple PUCCH resources (e.g., pucch-Resourceid) having PUCCH resources identified by PUCCH resource identifiers; and / or multiple (e.g., 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 (e.g., HARQ-ACK, SR, and / or CSI) from the multiple PUCCH resource sets based on the total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE can select the first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE can select the 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 the 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 the fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0214] After determining the PUCCH resource set from the multiple PUCCH resource sets, the UE can determine the PUCCH resource for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The UE can determine the PUCCH resource based on the PUCCH resource indicator in the DCI (e.g., DCI format 1_0 or DCI for 1_1) received on the PDCCH. 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).

[0215] 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 can be part of a mobile communication network, such as Figure 1A the mobile communication network 100 shown,Figure 1B The mobile communication network 150 or any other communication network shown. Figure 15 Only one wireless device 1502 and one base station 1504 are shown, but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same or similar configurations as those shown. Figure 15 Those shown.

[0216] The base station 1504 can connect the wireless device 1502 to a core network (not shown) through radio communication via an air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 through the air interface 1506 is called the downlink, while the communication direction from the wireless device 1502 to the base station 1504 through the air interface is called the uplink. Frequency-division duplexing (FDD), time-division duplexing (TDD), and / or some combination of the two duplexing technologies can be used to separate downlink transmissions from uplink transmissions.

[0217] In the downlink, the data to be sent from the base station 1504 to the wireless device 1502 can be provided to the processing system 1508 of the base station 1504. This data can be provided to the processing system 1508, for example, through the core network. In the uplink, the data to be sent from the wireless device 1502 to the base station 1504 can be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 can implement layer 3 and layer 2 OSI functions to process the data for transmission. Layer 2 can include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer regarding Figure 2A , Figure 2B , Figure 3 and Figure 4A . Layer 3 can include the RRC layer regarding Figure 2B .

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

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

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

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

[0222] 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 gates and / or transistor logic, discrete hardware components, on-board 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.

[0223] Processing system 1508 and / or processing system 1518 may be respectively connected to one or more peripheral devices 1516 and one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, frequency modulation (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 one or more peripheral devices described above. The processing system 1518 in the wireless device 1502 may receive power from a power supply and / or may be configured to distribute power to other components in the wireless device 1502. The power supply may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. Processing system 1508 and / or processing system 1518 may be respectively connected to GPS chipset 1517 and GPS chipset 1527. GPS chipset 1517 and GPS chipset 1527 may be configured to provide the geographical location information of wireless device 1502 and base station 1504 respectively.

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

[0225] Figure 16B An exemplary structure for modulating and upconverting a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal of an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. Filtering may be employed before transmission.

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

[0227] Figure 16D Another exemplary structure for modulating and upconverting a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued OFDM baseband signal of an antenna port. Filtering may be employed before transmission.

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

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

[0230] The hybrid ARQ mechanism in the MAC layer aims for very fast transmission. The wireless device can provide feedback to the base station regarding the success or failure of the downlink transmission after each received transport block. A very low error rate probability of obtaining HARQ feedback may be achievable, which may come at the cost of transmission resources (such as power). For example, a feedback error rate of 0.1 - 1% may be reasonable, which may result in a HARQ residual error rate of a similar order of magnitude. In many cases, this residual error may be low enough. In some services that require ultra-reliable data delivery with low latency (e.g., URLLC), this residual error rate may be intolerable. In such cases, the feedback error rate can be reduced, and the increased cost of feedback signaling can be accepted, and / or additional retransmissions can be performed without relying on feedback signaling, which results in reduced spectral efficiency.

[0231] The HARQ protocol can be the main way to handle retransmissions in a wireless technology (e.g., NR). In the case of a packet that is received incorrectly, a retransmission may be required. Although it may not be possible to decode the packet, the received signal may still contain information that may be lost by discarding the incorrectly received packet. HARQ with soft combining can overcome this drawback. In HARQ with soft combining, the wireless device stores the incorrectly received packet in a buffer memory and subsequently combines it with one or more retransmissions to obtain a single combined packet that may be more reliable than its components. The decoding of the error correction code operates on the combined signal.

[0232] The retransmission of a code block group (e.g., a part of a transport block) can be handled by the physical layer and / or the MAC layer. The basis of the HARQ mechanism consists of multiple stop-and-wait protocols, each operating on a single transport block. In the stop-and-wait protocol, the transmitter stops and waits for an acknowledgment after each transmitted transport block. This protocol requires a single bit indicating the positive or negative acknowledgment of the transport block; however, due to the wait after each transmission, the throughput is very low. Multiple stop-and-wait processes can operate in parallel. For example, while waiting for an acknowledgment from one HARQ process, the transmitter can transmit data for another HARQ process. These multiple parallel HARQ processes can form a HARQ entity, thus allowing continuous transmission of data. The wireless device can have one HARQ entity per carrier. The HARQ entity can support spatial multiplexing of more than four layers to a single device in the downlink, where two transport blocks can be transmitted in parallel on the same transport channel. The HARQ entity can have two sets of HARQ processes with independent HARQ acknowledgments.

[0233] Wireless technology can use an asynchronous HARQ protocol in the downlink and / or uplink. For example, the HARQ processes involved in downlink and / or uplink transmissions can be signaled explicitly and / or implicitly. For example, downlink control information (DCI) that schedules downlink transmissions can signal the corresponding HARQ process. Asynchronous HARQ operations can allow for dynamic TDD operation and may be more efficient when operating in unlicensed spectrum, where it may not be guaranteed that the scheduled radio resources are available at synchronous retransmission times.

[0234] Before encoding, a large transport block size can be segmented into multiple code blocks, each having its own CRC in addition to the total TB CRC. Errors on individual code blocks can be detected based on their CRCs and the total TB. The base station can configure retransmissions for the wireless device based on groups of code blocks (e.g., code block groups (CBGs)). If retransmissions for each CBG are configured, feedback for each CBG is provided. The TB can include one or more CBGs. The CBG to which a code block belongs can be determined based on the initial transmission and can be fixed.

[0235] In the downlink, retransmissions can be scheduled in the same way as new data. For example, retransmissions can be scheduled at any time and any frequency position within the downlink cell and / or BWP. The downlink scheduling assignment can contain the necessary HARQ-related control signaling, such as: HARQ process number; new data indicator (NDI); CBG transmission indicator (CBGTI) and CBG flush indicator (CBGFI) in the case where retransmissions for each CBG are configured; and / or information for handling the transmission of acknowledgments (ACK / NACK) in the uplink, such as timing and resource indication information.

[0236] Once the wireless device receives the scheduling assignment in the DCI, it attempts to decode the transport block (TB), e.g., after soft combining with a previous attempt. Transmissions and retransmissions can be scheduled in the same frame. The wireless device can determine whether a transmission is a new transmission or a retransmission based on the NDI field in the DCI. An explicit NDI can be included for the scheduled TB as part of the scheduling information in the downlink. The NDI field can include one or more NDI bits per TB (and / or CBG). The NDI bit can be toggled for a new transmission and not toggled for a retransmission. In the case of a new transmission, the wireless device flushes the soft buffer. In the case of a retransmission, the wireless device performs soft combining with the received data currently in the soft buffer for the corresponding HARQ process.

[0237] The time for transmitting the corresponding HARQ ACK / NACK received from downlink data can be fixed, e.g., multiple subframes / slots / symbols (e.g., 3 ms). Such a scheme with predefined timing moments for ACK / NACK may not integrate well with dynamic TDD and / or unlicensed operation. A more flexible scheme that can dynamically control the ACK / NACK transmission timing can be adopted. For example, the DL scheduling DCI can include a HARQ timing field to control / indicate the transmission timing of ACK / NACK in the uplink. The HARQ timing field in the DCI can be used as an index in a predefined and / or RRC-configured table that provides information on when the wireless device can transmit HARQ ACK / NACK relative to the reception of data (e.g., Physical DL Shared Channel (PDSCH)).

[0238] Figure 17 An example of HARQ acknowledgement timing determination is shown. In this example, three DCIs scheduling three downlink assignments are received in the same slot in slots S0, S1, and S3. In each downlink assignment, a different acknowledgement timing index is indicated, e.g., for S0: 3, for S1: 2, and for S3: 0. The indicated index (HARQ timing field) points to a HARQ timing table, e.g., for S0: T3 indicates that the transmission of uplink ACK / NACK points to S4, for S1: T2 indicates that the transmission of uplink ACK / NACK points to S4, and for S3: T0 indicates that the transmission of uplink ACK / NACK points to S4. As a result, all three downlink assignments are acknowledged in the same slot S4. The wireless device multiplexes these three acknowledgements in slot S4 and transmits them.

[0239] All wireless devices can support baseline processing time / capability. Some wireless devices can support additional aggressive / faster processing time / capability. The wireless device can report the processing capability to the base station, e.g., report per subcarrier spacing.

[0240] The wireless device can determine the resources for HARQ ACK / NACK transmission based on the location of the PDCCH scheduling the transmission, e.g., frequency resources and / or PUCCH format and / or code domain. The scheduling DCI can include a field indicating the resources for HARQ ACK / NACK transmission, e.g., the PUCCH Resource Indicator (PRI) field. The PRI field can be an index for selecting one resource set from multiple predefined and / or RRC-configured resource sets.

[0241] For example, in a carrier aggregation scenario and / or when retransmission for each CBG is configured, a wireless device may multiplex multiple acknowledgments scheduled for transmission in the uplink at the same time / slot. The UE may multiplex multiple ACK / NACK bits for multiple TBs and / or CBGs into a multi-bit acknowledgment message. A semi-static codebook and / or a dynamic codebook may be used to multiplex the multiple ACK / NACK bits. The RRC configuration may select between a semi-static codebook and a dynamic codebook.

[0242] The semi-static codebook may be regarded as a matrix including a time domain dimension and a component carrier (and / or CBG and / or MIMO layer) dimension, both of which may be semi-statically configured and / or predefined. The size of the time domain dimension may be given by the predefined HARQ ACK / NACK timing and / or the maximum and / or minimum HARQ ACK / NACK timings indicated in an RRC-configured table. The size of the component carrier domain may be given by the number of simultaneous TBs and / or CBGs across all component carriers. For the semi-static codebook, the codebook size may be fixed. The number of bits to be transmitted in the HARQ report may be determined based on the fixed codebook size. An appropriate format for uplink control signaling (e.g., PUCCH format) may be selected based on the number of bits. Each entry of the matrix may represent the decoding result of the corresponding transmission, e.g., a positive (ACK) or negative (NACK) acknowledgment. One or more entries of the codebook matrix may not correspond to a downlink transmission opportunity (e.g., a PDSCH occasion) reporting a NACK. For example, in the case of a lost downlink assignment, this may increase the codebook robustness, and the base station may schedule a retransmission of the lost TB / CBG. The size of the semi-static codebook may be very large.

[0243] The dynamic codebook may be used to address the potential large size of the semi-static codebook. With the dynamic codebook, only the ACK / NACK information for the scheduled assignments can be included in the report, e.g., not all carriers as in the semi-static codebook. The size of the dynamic codebook may vary dynamically, e.g., according to the number of scheduled carriers. To maintain the same understanding of the dynamic codebook size (which is error-prone in downlink control signaling), a downlink assignment index (DAI) may be included in the scheduling DCI. The DAI field may include a counter DAI (cDAI) and a total DAI (tDAI), e.g., in the case of carrier aggregation. The counter DAI in the scheduling DCI indicates the number of scheduled downlink transmissions up to the point of receiving the DCI in a carrier-first, time-second manner. The total DAI in the scheduling DCI indicates the total number of scheduled downlink transmissions across all carriers up to the point of receiving the DCI. The highest cDAI at the current time is equal to the tDAI at this time.

[0244] A wireless device may receive a downlink assignment from a base station. The wireless device may receive the downlink assignment on a Physical Downlink Control Channel (PDCCH). The downlink assignment may indicate that there is one or more transmissions on one or more Downlink Shared Channels (DL-SCH) for a particular MAC entity. The downlink assignment may provide Hybrid Automatic Repeat reQuest (HARQ) information for the one or more transmissions.

[0245] For each PDCCH occasion during which the UE monitors the PDCCH and for each serving cell, the UE may receive a downlink assignment for a C-RNTI or TC-RNTI of a MAC entity. The UE may consider that the NDI has been toggled, e.g., when this is the first downlink assignment for the TC-RNTI. The downlink assignment may be for the C-RNTI of the MAC entity, and the previous downlink assignment indicated to the HARQ entity of the same HARQ process may be a downlink assignment received for the CS-RNTI of the MAC entity and / or a configured downlink assignment (e.g., Semi-Persistent Scheduling (SPS)), and the UE may consider that the NDI has been toggled regardless of the value of the NDI. The MAC entity may indicate the presence of the downlink assignment and deliver the associated HARQ information (e.g., HARQ process number, NDI, etc.) to the HARQ entity.

[0246] The UE may receive a downlink assignment for a PDCCH occasion of a serving cell for the CS-RNTI of a MAC entity. The UE may consider that the NDI for the corresponding HARQ process has not been toggled, and may indicate the presence of the downlink assignment and deliver the associated HARQ information to the HARQ entity, e.g., when the NDI in the received HARQ information is 1.

[0247] The NDI in the received HARQ information may be 0, and the PDCCH content may indicate SPS deactivation. The UE may clear the configured downlink assignment for the serving cell (if any). A timer associated with the TAG of the serving cell that contains the HARQ feedback to be transmitted thereon (e.g., timeAlignmentTimer) may run, and the UE may indicate a positive acknowledgement (ACK) for the SPS deactivation to the PHY layer.

[0248] The NDI in the received HARQ information may be 0, and the PDCCH content may indicate SPS activation. The UE may store the downlink assignment and the associated HARQ information for the serving cell as a configured downlink assignment, and may initialize or re-initialize the configured downlink assignment for the serving cell to start within the associated PDSCH duration and occur according to the configured periodicity.

[0249] For each serving cell and each configured downlink assignment (e.g., SPS PDSCH), if configured and activated, the MAC entity may command the PHY layer to receive transport blocks on the DL-SCH during the PDSCH duration according to the configured downlink assignment and deliver them to the HARQ entity. For example, if the PDSCH duration does not overlap with the PDSCH duration of the downlink assignment for the serving cell received on the PDCCH. The MAC entity may set the HARQ process number / ID to the HARQ process ID associated with the PDSCH duration and may consider that the NDI bit for the corresponding HARQ process has been toggled. The MAC entity may indicate the presence of the configured downlink assignment (SPS PDSCH) and deliver the stored HARQ information to the HARQ entity.

[0250] The MAC entity may include a HARQ entity for each serving cell, which maintains multiple parallel HARQ processes. Each HARQ process may be associated with a HARQ process identifier / number. The HARQ entity directs the HARQ information and the associated TB / CBG received on the DL-SCH to the corresponding HARQ process. The number of parallel DL HARQ processes for each HARQ entity may be predefined or configured by RRC. When the physical layer is not configured for downlink spatial multiplexing, a HARQ process may support one TB. When the physical layer is configured for downlink spatial multiplexing, a HARQ process may support one or two TBs.

[0251] The MAC entity may be configured with repetition, e.g., pdsch-AggregationFactor (pdsch-aggregation factor) > 1, which provides the number of transmissions of TBs in a bundle of downlink assignments. The bundling operation may depend on the HARQ entity invoking the same HARQ process for each transmission that is part of the same bundle. After the initial transmission, pdsch-AggregationFactor – 1 HARQ retransmissions may follow within the bundle.

[0252] When a transmission is made for a HARQ process, one or two (in the case of downlink spatial multiplexing) TBs and the associated HARQ information may be received from the HARQ entity. For each received TB and the associated HARQ information, if the NDI (when provided) has been toggled compared to the value of the previously received transmission corresponding to the TB, and / or if this is the first received transmission for the TB (e.g., there was no previous NDI for the TB), then the HARQ process may consider the transmission to be a new transmission. Otherwise, the HARQ process may consider the transmission to be a retransmission.

[0253] The MAC entity may attempt to decode the data, e.g., if this is a new transmission. For example, when this is a retransmission and / or the data for the TB has not been successfully decoded, the MAC entity may command the PHY layer to combine the received data with the data for the TB currently in the soft buffer and attempt to decode the combined data. For example, when the data for the TB has been successfully decoded, the MAC entity may deliver the decoded MAC PDU to the upper layer and / or the disassembling and demultiplexing entity. For example, when the decoding is unsuccessful, the MAC entity may command the PHY layer to replace the data for the TB in the soft buffer with the data that the MAC entity attempts to decode. The MAC entity may receive retransmissions with a TB size that is the same as or different from the last TB size signaled for the TB.

[0254] The UE may receive a PDSCH without receiving the corresponding PDCCH (e.g., a configured downlink assignment and / or an SPS PDSCH), and / or receive a PDCCH indicating the release of the SPS PDSCH. The UE may generate the corresponding HARQ-ACK information bits. If the UE is not configured with retransmissions per CBG (e.g., the provided PDSCH-CodeBlockGroupTransmission (PDSCH-code block group transmission)), the UE may generate one HARQ-ACK information bit per transport block. For the HARQ-ACK information bits, e.g., if the UE detects a DCI format 1_0 that provides an SPS PDSCH release and / or correctly decodes the transport block, the UE may generate an ACK. For the HARQ-ACK information bits, if the UE does not correctly decode the transport block, the UE may generate a NACK. The UE may or may not expect to be instructed to transmit the HARQ-ACK information received for more than one SPS PDSCH in the same PUCCH.

[0255] The UE may multiplex UCI in a PUCCH transmission that overlaps with a PUSCH transmission. The UE may multiplex only the HARQ-ACK information (if any) from the UCI in the PUSCH transmission (e.g., piggyback), and may not transmit the PUCCH, e.g., if the UE multiplexes an aperiodic and / or semi-persistent CSI report in the PUSCH.

[0256] For example, if each of more than one PUSCH includes an aperiodic CSI report, the UE may not expect the PUCCH resources (if applicable) obtained from multiplexing the overlapping PUCCH resources to overlap with the more than one PUSCH.

[0257] For example, if the UE previously detected a DCI format scheduling a PUSCH transmission in a time slot, and if the UE multiplexes HARQ-ACK information in the PUSCH transmission, the UE may not expect to detect a DCI format scheduling PDSCH reception and / or SPS PDSCH release in that time slot and indicating the resources for PUCCH transmission with the corresponding HARQ-ACK information.

[0258] If the UE multiplexes aperiodic CSI in the PUSCH, and the UE will multiplex UCI including HARQ-ACK information in a PUCCH that overlaps with the PUSCH, and the timing condition for the overlapping PUCCH and PUSCH is met, the UE may multiplex only HARQ-ACK information in the PUSCH and may not transmit the PUCCH.

[0259] If the UE transmits multiple PUSCHs on the corresponding serving cell in a time slot, the multiple PUSCHs include a first PUSCH scheduled by DCI format 0_0 and / or DCI format 0_1 and a second PUSCH configured by the corresponding ConfiguredGrantConfig or semiPersistentOnPUSCH, and the UE will multiplex UCI in one of the multiple PUSCHs, and the multiple PUSCHs meet the conditions for UCI multiplexing, the UE may multiplex UCI in the PUSCH starting from the first PUSCH.

[0260] If the UE transmits multiple PUSCHs on the corresponding serving cell in a time slot, and the UE will multiplex UCI in one of the multiple PUSCHs, and the UE does not multiplex aperiodic CSI in any of the multiple PUSCHs, the UE may multiplex UCI in the PUSCH of the serving cell with the smallest ServCellIndex that meets the conditions for UCI multiplexing. If the UE transmits more than one PUSCH on the serving cell with the smallest ServCellIndex that meets the conditions for UCI multiplexing in a time slot, the UE may multiplex UCI in the earliest PUSCH transmitted by the UE in that time slot.

[0261] If the UE transmits the PUSCH over multiple time slots, and the UE is to transmit a PUCCH with HARQ-ACK and / or CSI information over a single time slot and in a time slot that overlaps with the PUSCH transmission in one or more of the multiple time slots, and the PUSCH transmission in the one or more time slots meets the conditions for multiplexing HARQ-ACK and / or CSI information, then the UE may multiplex the HARQ-ACK and / or CSI information in the PUSCH transmission in the one or more time slots. For example, if in the absence of PUSCH transmission, the UE would not transmit a single-time-slot PUCCH with HARQ-ACK and / or CSI information in one of the multiple time slots, then the UE may not multiplex the HARQ-ACK and / or CSI information in the PUSCH transmission in that time slot.

[0262] If the PUSCH transmission over the multiple time slots is scheduled by DCI format 0_1, the same value of the DAI field may apply to multiplexing HARQ-ACK information in the PUSCH transmission in any of the multiple time slots where the UE multiplexes HARQ-ACK information.

[0263] The HARQ-ACK information bit value 0 represents a negative acknowledgment (NACK), while the HARQ-ACK information bit value 1 represents a positive acknowledgment (ACK).

[0264] Dynamic scheduling can be an operating mode in a radio technology (e.g., NR). For each transmission time interval (TTI), such as a time slot and / or a subframe, a scheduler (e.g., a base station) can use control signaling to command a device to transmit or receive. It is flexible and can adapt to rapid changes in traffic behavior, but may require an increase in control signaling. The radio technology can support transmission schemes that do not rely on dynamic grants / assignments.

[0265] In the downlink, semi-persistent scheduling (SPS) can be supported. For SPS configuration, the base station can provide the period and / or offset of the SPS occasion via RRC signaling and / or MAC CE signaling. The base station can activate SPS by transmitting SPS activation DCI via PDCCH. In an example, the first SPS activation DCI can include the activation of one or more SPS configurations. The wireless device can use the first RNTI (e.g., CS-RNTI and / or C-RNTI) for the SPS activation DCI. The SPS activation DCI can carry resource allocation information, e.g., time domain allocation, frequency domain allocation, BWP indicator, PRB bundling size indicator, CSI-RS trigger, MCS, NDI, DAI, and one or more first parameters for HARQ-ACK feedback, e.g., PDSCH-to-HARQ-feedback (PDSCH to HARQ feedback) timing, CBGTI, and CBGFI, and one or more second parameters for supporting transmission, e.g., antenna port, TCI, SRS request, power control, etc.

[0266] Once the base station activates the SPS configuration at time m, the base station can transmit one or more data via PDSCH without going through the transmission occasion associated control channel / DCI / PDCCH, where the transmission occasion is determined based on the resource allocation information carried by the SPS activation DCI and the period and / or offset of the SPS occasion. The wireless device can apply the resource allocation, the one or more first parameters for HARQ-ACK feedback, and the one or more second parameters to subsequent data transmissions based on the SPS activation DCI and the SPS configuration. For example, the wireless device applies the same PDSCH-to-HARQ-feedback timing to each PDSCH transmitted via the SPS occasion. The base station can transmit a second SPS activation DCI to update one or more parameters, or can transmit an SPS release DCI to deactivate the SPS configuration.

[0267] The HARQ process number for each SPS PDSCH occasion can be derived from the time when the downlink data transmission via the corresponding SPS PDSCH occasion starts. For a configured downlink assignment, the HARQ process ID associated with the slot in which the DL transmission starts is derived from the following formula: HARQ Process ID = [floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))] modulo nrofHARQ - Processes, where CURRENT_slot = [(SFN×numberOfSlotsPerFrame)+slot number in the frame] and numberOfSlotsPerFrame refers to the number of consecutive slots per frame.

[0268] Once SPS is activated, the wireless device can receive downlink data transmissions (e.g., periodically) according to the period configured by RRC and using the transmission parameters indicated in the PDCCH (activation DCI) for the activation transmission. Thus, control signaling can be used once, and the signaling overhead can be reduced. After activating / enabling SPS, the wireless device can continue to monitor one or more candidate PDCCHs (e.g., search space sets) for uplink and downlink scheduling commands. The base station can dynamically schedule downlink assignments for HARQ retransmissions. For example, the base station can initially schedule the downlink transmission of the first TB via an SPS PDSCH occasion and dynamically schedule one or more retransmissions of the first TB via one or more downlink assignments.

[0269] The wireless device can verify the DL SPS assignment PDCCH for scheduling activation (e.g., SPS activation) and / or scheduling release (e.g., SPS release / deactivation). The wireless device can verify the SPS activation DCI and / or the SPS release / deactivation DCI. The SPS activation / deactivation DCI format can have a CRC scrambled with a first RNTI (e.g., CS - RNTI or C - RNTI). The base station can configure the first RNTI for the wireless device via RRC signaling, for example. The SPS activation / deactivation DCI can include a field indicating that the DCI format is for SPS activation / deactivation. For example, for an enabled transport block, the NDI field of the DCI format can be set to a predefined value, e.g., 0. The wireless device can determine that the received DCI format is for SPS activation / release based on the field indicating the predefined value.

[0270] If one or more fields of a DCI format are set to one or more predefined values, verification of the DCI format can be achieved. For example, the first field of the DCI format corresponding to the HARQ process number can be set to all "0". For example, the second field of the DCI format corresponding to the redundancy version can be set to all "0" (e.g., "00"). For example, the redundancy version of the TB enabled in the SPS activation DCI can be set to a predefined value, e.g., "00". For example, if the received DCI format includes the first and second fields set to predefined values, the wireless device can determine DL SPS activation. For example, in the DCI format for SPS release, the third field corresponding to the MCS can be set to all "1". For example, in the DCI format for SPS release, the fourth field corresponding to the frequency domain resource allocation can be set to all "1". For example, if the received DCI format includes the first, second, third, and fourth fields all set to predefined values, the wireless device can determine DL SPS release. For example, if verification is achieved, the wireless device can consider the information field in the DCI format as a valid activation and / or release of one or more DL SPSs. For example, if verification is not achieved, the wireless device can discard the information field in the DCI format.

[0271] The wireless device can provide / send HARQ-ACK information in response to receiving one or more DCIs indicating DL SPS activation and / or release. The wireless device can send HARQ-ACK information in response to an SPS PDSCH release (e.g., after a time offset starting from the last symbol of the PDCCH providing the SPS release). The time offset can be one or more (e.g., N) symbols. The time offset can be determined based on the UE processing capability for PDCCH reception and / or the subcarrier spacing.

[0272] The UE can receive one or more RRC messages from the base station, including parameters for HARQ configuration. For example, when the parameter pdsch-HARQ-ACK-Codebook (pdsch-HARQ-ACK codebook) = semi-static, the parameter can indicate the configuration of a semi-static codebook (e.g., Type-1 HARQ-ACK (type-1 HARQ-ACK) codebook). The UE can report HARQ-ACK information for the corresponding PDSCH reception (e.g., SPS PDSCH reception) and / or SPS PDSCH release in the HARQ-ACK codebook. The UE can transmit the HARQ-ACK codebook in the time slot indicated by the value of the PDSCH-to-HARQ feedback timing indicator field in the corresponding DCI format (e.g., DCI format 1_0 or DCI format 1_1). The UE can report the NACK value of the HARQ-ACK information bit in the semi-static HARQ-ACK codebook, and the UE transmits this semi-static HARQ-ACK codebook in the time slot not indicated by the value of the PDSCH-to-HARQ feedback timing indicator field in the corresponding DCI format.

[0273] The UE can be configured with repetition and / or slot aggregation. The UE can report HARQ-ACK information for the PDSCH reception that ends in the first time slot (e.g., time slot n) in the HARQ-ACK codebook, and the UE includes this HARQ-ACK codebook in the PUCCH or PUSCH transmission in the second time slot (e.g., time slot n + k). The second time slot can be indicated by an offset (e.g., k) from the first time slot. For example, the offset (e.g., k) can be the number of time slots indicated by the PDSCH-to-HARQ feedback timing indicator field in the corresponding DCI format. For example, the offset (e.g., k) can be the number of time slots provided by RRC signaling (e.g., by the parameter dl-DataToUL-ACK). For example, when there is no PDSCH-to-HARQ feedback timing indicator field in the DCI format, RRC signaling can be used. For example, when the UE reports HARQ-ACK information for the PDSCH reception in a time slot other than the second time slot (e.g., time slot n + k), the UE can set the value of each corresponding HARQ-ACK information bit to NACK.

[0274] The UE can determine a set of timings for candidate PDSCH receptions for one or more serving cells and one or more UL and / or DL BWPs (e.g., active UL BWP and / or active DL BWP). The UE can transmit HARQ-ACK information corresponding to the set of timings in the second time slot, e.g., in the PUCCH or PUSCH. This determination can be based on a set of time slot timing values (e.g., candidate K1 values). The set of time slot timing values can be associated with one or more active UL BWPs.

[0275] For example, when the UE is configured to monitor the PDCCH for a first DCI format (e.g., fallback DCI / DCI format 1_0) on the serving cell and is not configured to monitor the PDCCH for a second DCI format (e.g., non-fallback DCI / DCI format 1_1), the slot timing value K1 can be provided by a first set of slot timing values (e.g., a predefined set {1, 2, 3, 4, 5, 6, 7, 8}, or a set configured by RRC signaling). The first DCI format can indicate a first slot timing value K1 from the first set of slot timing values.

[0276] The slot timing value K1 can be provided by a second set of slot timing values. For example, the base station can configure the second set via RRC signaling (e.g., via the parameter dl-DataToUL-ACK), which can include one or more values from a predefined set of numbers (e.g., 0 to 15). When the UE is configured to monitor the PDCCH for the second DCI format (e.g., non-fallback DCI / DCI format 1_1), the second set can be used. The second DCI format can indicate a second slot timing value K1 from the second set of slot timing values.

[0277] The UE can receive the PDSCH (e.g., SPS PDSCH) in a first slot and transmit HARQ-ACK information corresponding to the PDSCH in a second slot, e.g., via the PUCCH and / or PUSCH. The second slot can be K1 slots after the first slot. The value of K1 can be indicated via DCI scheduling / activation of the PDSCH.

[0278] Once the UE determines the PUCCH and / or PUSCH resources for HARQ-ACK codebook transmission, the UE bases one or more HARQ-ACK bits of one or more PDSCHs mapped to the PUCCH and / or PUSCH resources on the PDSCH HARQ-ACK codebook multiplexing. The PDSCH HARQ-ACK codebook can be configured by RRC signaling. For example, the parameter pdsch-HARQ-ACK-codebook can be configured as a semi-static (type 1) or dynamic (type 2) codebook.

[0279] The position of the HARQ-ACK information corresponding to an SPS PDSCH release in the HARQ-ACK codebook (e.g., type 1 / semi-static HARQ-ACK codebook) can be the same as that for the corresponding SPS PDSCH reception. The position of the SPS PDSCH reception in the HARQ-ACK codebook can be fixed and determined based on the timing of the SPS PDSCH reception. The position of the SPS PDSCH release in the HARQ-ACK codebook can be fixed and determined based on the timing of the PDCCH reception indicating the SPS PDSCH release. The UE may not expect to receive an SPS PDSCH release and a unicast PDSCH in the same time slot.

[0280] The UE can receive one or more RRC messages from the base station, including parameters for HARQ configuration. For example, when the parameter pdsch-HARQ-ACK codebook = dynamic, the parameter can indicate the configuration of the dynamic codebook (e.g., type-1 HARQ-ACK codebook). The UE can determine the monitoring occasion of the PDCCH with a DCI format (e.g., DCI format 1_0 or DCI format 1_1) for scheduling, for example, PDSCH reception (e.g., SPS PDSCH reception) and / or SPS PDSCH release on the active DL BWP of the serving cell. The UE can transmit HARQ-ACK information corresponding to the PDSCH reception and / or SPS PDSCH release in a time slot, e.g., in the PUCCH or PUSCH. The UE can determine the time slot based on a field in the DCI format (e.g., the PDSCH-to-HARQ feedback timing indicator field value for PUCCH transmission).

[0281] A set of PDCCH monitoring occasions for one or more DCI formats (e.g., DCI format 1_0 or DCI format 1_1) used for scheduling PDSCH reception and / or SPS PDSCH release can be defined as the union of PDCCH monitoring occasions across the active DL BWPs of the configured serving cells. The PDCCH monitoring occasions in the set can be sorted in ascending order of the start time of the search space set associated with the PDCCH monitoring occasion. The cardinality of the set of PDCCH monitoring occasions defines the total number M of PDCCH monitoring occasions. The value of the counter downlink assignment indicator (cDAI) field of the DCI format can represent, for example, the cumulative count of {serving cell, PDCCH monitoring occasion} pairs (in which there is PDSCH reception or SPS PDSCH release associated with the DCI format) up to the current serving cell and the current PDCCH monitoring occasion, for example, first in ascending order of the serving cell index and then in ascending order of the PDCCH monitoring occasion index. The total DAI value of the DCI format (e.g., DCI format 1_1), when present, can represent, for example, the total number of {serving cell, PDCCH monitoring occasion} pairs (in which there is PDSCH reception or SPS PDSCH release associated with the DCI format) up to the current PDCCH monitoring occasion. The tDAI value can be updated from PDCCH monitoring occasion to PDCCH monitoring occasion.

[0282] For example, when a dynamic codebook is configured, the UE may multiplex (e.g., append) HARQ-ACK information bits associated with SPS PDSCH reception at the end of the HARQ-ACK codebook. The UE can determine the position of the HARQ-ACK information bits associated with the SPS PDSCH release based on the cDAI and tDAI in the PDCCH indicating the SPS PDSCH release.

[0283] In an example, with bandwidth adaptation (BA), the receive and transmit bandwidths of a wireless device may not be as large as the bandwidth of the cell. The receive bandwidth and / or transmit bandwidth of the wireless device can be adjusted. In an example, the width of the receive bandwidth and / or transmit bandwidth can be commanded to change (e.g., shrink during a low activity period to save power). In an example, the position of the receive bandwidth and / or transmit bandwidth can be moved in the frequency domain (e.g., to increase scheduling flexibility). In an example, the subcarrier spacing of the receive bandwidth and / or transmit bandwidth can be commanded to change (e.g., to allow different services). A subset of the total cell bandwidth of the cell can be referred to as a bandwidth part (BWP). BA can be achieved by configuring the wireless device with one or more BWPs and informing the wireless device which one of the configured one or more BWPs is the current active BWP.

[0284] A base station (gNB) may configure a wireless device (UE) with an uplink (UL) BWP and a downlink (DL) BWP to enable BA on the PCell. If carrier aggregation is configured, the gNB may configure the UE using at least the DL BWP (e.g., there may be no UL BWP in the UL) to enable BA on the SCell.

[0285] For the PCell, the initial BWP may be the BWP for initial access. In an example, during initial access, the wireless device may operate on the initial BWP (e.g., the initial UL / DL BWP).

[0286] For the SCell, the initial BWP may be the BWP configured such that when the SCell is activated, the UE first operates at the SCell. In an example, in response to the SCell being activated, the wireless device may operate on the initial BWP.

[0287] In an example, the base station may configure the wireless device with one or more BWPs. In paired spectrum (e.g., FDD), the wireless device may independently switch the first DL BWP and the first UL BWP of one or more BWPs. In unpaired spectrum (e.g., TDD), the wireless device may simultaneously switch the second DL BWP and the second UL BWP of one or more BWPs. The switch between the configured one or more BWPs may occur via DCI or an inactivity timer (e.g., the BWP inactivity timer). In an example, when an inactivity timer is configured for a serving cell, the expiration of the inactivity timer associated with that cell may switch the active BWP of the serving cell to the default BWP. The default BWP may be configured by the network.

[0288] In an example, for an FDD system, when configured with BA, in an active serving cell, one UL BWP and one DL BWP for each uplink carrier (e.g., SUL, NUL) may be active simultaneously. BWPs other than the one UL BWP and one DL BWP that the UE may be configured with may be deactivated.

[0289] In an example, for a TDD system, in an active serving cell, one DL / UL BWP pair may be active simultaneously. BWPs other than the one DL / UL BWP pair that the UE may be configured with may be deactivated.

[0290] In an example, operating on one UL BWP and that one DL BWP (or one DL / UL pair) may achieve reasonable UE battery consumption. On a deactivated BWP, the UE may not monitor the PDCCH and may not transmit on the PUCCH, PRACH, and UL-SCH.

[0291] In an example, when configured with BA, the wireless device may monitor the first PDCCH on the active BWP of the serving cell. In an example, the wireless device may not monitor the second PDCCH over the entire DL frequency / bandwidth of the cell. In an example, the wireless device may not monitor the second PDCCH on a deactivated BWP. In an example, the BWP inactivity timer may be used to switch the active BWP to the default BWP of the serving cell. In an example, in response to successful PDCCH decoding on the serving cell, the wireless device may (re)start the BWP inactivity timer. In an example, the wireless device may switch to the default BWP in response to the expiration of the BWP inactivity timer.

[0292] In an example, the wireless device may be configured with one or more BWPs for a serving cell (e.g., PCell, SCell). In an example, the serving cell may be configured with at most a first number (e.g., four) of BWPs. In an example, for an active serving cell, there may be one active BWP at any point in time.

[0293] In an example, BWP switching for a serving cell may be used to simultaneously activate an inactive BWP and deactivate an active BWP. In an example, BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink grant. In an example, BWP switching may be controlled by an inactivity timer (e.g., bwp-InactivityTimer). In an example, BWP switching may be controlled by the MAC entity in response to starting a random access procedure. In an example, BWP switching may be controlled by RRC signaling.

[0294] In an example, in response to RRC (re)configuration of the firstActiveDownlinkBWP-Id (e.g., included in RRC signaling) and / or firstActiveUplinkBWP-Id (e.g., included in RRC signaling) of a serving cell (e.g., SpCell), the wireless device may activate the DL BWP indicated by the firstActiveDownlinkBWP-Id and / or the UL BWP indicated by the firstActiveUplinkBWP-Id, respectively, without receiving a PDCCH indicating a downlink assignment or an uplink grant. In an example, in response to activation of an SCell, the wireless device may activate the DL BWP indicated by the firstActiveDownlinkBWP-Id and / or the UL BWP indicated by the firstActiveUplinkBWP-Id, respectively, without receiving a PDCCH indicating a downlink assignment or an uplink grant.

[0295] In an example, the active BWP for a serving cell can be indicated by RRC signaling and / or PDCCH. In an example, for unpaired spectrum (e.g., time division duplex (TDD)), the DL BWP can be paired with the UL BWP, and the BWP switch can be common (e.g., simultaneous) for the UL BWP and the DL BWP.

[0296] In an example, for the active BWP of an active serving cell (e.g., PCell, SCell) configured with one or more BWPs, the wireless device can perform at least one of the following on the active BWP: transmit on the UL-SCH on the active BWP; transmit on the RACH on the active BWP if a PRACH occasion is configured; monitor the PDCCH on the active BWP; transmit the PUCCH on the active BWP if configured; report the CSI of the active BWP; transmit the SRS on the active BWP if configured; receive the DL-SCH on the active BWP; (re)initialize any suspended configured uplink grant of configured grant type 1 on the active BWP according to the stored configuration, and start with a symbol based on certain procedures.

[0297] In an example, for a deactivated BWP of an active serving cell configured with one or more BWPs, the wireless device may not perform at least one of the following: transmit on the UL-SCH on the deactivated BWP; transmit on the RACH on the deactivated BWP; monitor the PDCCH on the deactivated BWP; transmit the PUCCH on the deactivated BWP; report the CSI of the deactivated BWP; transmit the SRS on the deactivated BWP; receive the DL-SCH on the deactivated BWP. In an example, for a deactivated BWP of an active serving cell configured with one or more BWPs, the wireless device can clear any configured downlink assignment and configured uplink grant of configured grant type 2 on the deactivated BWP; and can suspend any configured uplink grant of configured type 1 on the deactivated (or inactive) BWP.

[0298] In an example, the wireless device can initiate a random access procedure (e.g., contention-based random access, contention-free random access) on a serving cell (e.g., PCell, SCell).

[0299] In an example, the base station may configure a PRACH occasion for the active UL BWP of the serving cell of the wireless device. In an example, the active UL BWP may be identified by an uplink BWP ID (e.g., bwp-Id configured by the higher layer (RRC)). In an example, the second cell may be a SpCell. In an example, the active DL BWP of the serving cell of the wireless device may be identified by a downlink BWP ID (e.g., bwp-Id configured by the higher layer (RRC)). In an example, the uplink BWP ID may be different from the downlink BWP ID. In an example, when the wireless device initiates a random access procedure and the base station configures a PRACH occasion for the active UL BWP and the serving cell is a SpCell, in response to the downlink BWP ID of the active DL BWP being different from the uplink BWP ID of the active UL BWP, the MAC entity of the wireless device may switch from the active DL BWP to the DL BWP identified by a second downlink BWP ID of the serving cell. In an example, the switch from the active DL BWP to the DL BWP may include setting the DL BWP to the second active DL BWP of the serving cell. In an example, the second downlink BWP ID may be the same as the uplink BWP ID. In response to the switch, the MAC entity may perform a random access procedure on the DL BWP (e.g., the second active DL BWP) of the serving cell (e.g., SpCell) and the active UL BWP of the serving cell. In an example, in response to initiating a random access procedure, the wireless device may stop (if running) the BWP inactivity timer (e.g., bwp-InactivityTimer configured by the higher layer (RRC)) associated with the DL BWP of the serving cell.

[0300] In an example, the base station may configure a PRACH occasion for the active UL BWP of the serving cell of the wireless device. In the example, the serving cell may not be a SpCell. In the example, the serving cell may be an SCell. In the example, when the wireless device initiates a random access procedure and the base station configures a PRACH occasion for the active UL BWP and the serving cell is not a SpCell, the MAC entity of the wireless device may perform the random access procedure on the first active DL BWP (e.g., PCell) of the SpCell and the active UL BWP of the serving cell. In the example, in response to initiating the random access procedure, the wireless device may stop (if running) the second BWP inactivity timer associated with the second active DL BWP of the serving cell (e.g., bwp-InactivityTimer configured by the higher layer (RRC)). In the example, in response to initiating the random access procedure and the serving cell being an SCell, the wireless device may stop (if running) the first BWP inactivity timer associated with the first active DL BWP of the SpCell (e.g., bwp-InactivityTimer configured by the higher layer (RRC)).

[0301] In an example, the base station may not configure a PRACH opportunity for the active UL BWP of the serving cell of the wireless device. In the example, when the wireless device initiates a random access procedure on the serving cell, in response to there being no PRACH opportunity configured for the active UL BWP of the serving cell, the MAC entity of the wireless device may switch from the active UL BWP to the uplink BWP (initial uplink BWP) of the serving cell. In the example, the uplink BWP may be indicated by RRC signaling (e.g., initialUplinkBWP). In the example, the switch from the active UL BWP to the uplink BWP may include setting the uplink BWP to the current active UL BWP of the serving cell. In the example, the second cell may be a SpCell. In the example, when the wireless device initiates a random access procedure on the serving cell and there is no PRACH opportunity configured for the active UL BWP of the serving cell, in response to the serving cell being a SpCell, the MAC entity may switch from the active DL BWP of the serving cell to the downlink BWP (e.g., initial downlink BWP) of the serving cell. In the example, the downlink BWP may be indicated by RRC signaling (e.g., initialDownlinkBWP). In the example, the switch from the active DL BWP to the downlink BWP may include setting the downlink BWP to the current active DL BWP of the serving cell. In response to this switch, the MAC entity may perform a random access procedure on the uplink BWP of the serving cell and the downlink BWP of the serving cell. In the example, in response to initiating a random access procedure, the wireless device may stop (if running) the BWP inactivity timer (e.g., bwp-InactivityTimer configured by the higher layer (RRC)) associated with the downlink BWP (e.g., the current active DL BWP) of the serving cell.

[0302] In an example, the base station may not configure a PRACH occasion for the active UL BWP of the serving cell of the wireless device (e.g., SCell). In an example, when the wireless device initiates a random access procedure on the serving cell, in response to there being no PRACH occasion configured for the active UL BWP of the serving cell, the MAC entity of the wireless device may switch from the active UL BWP to the uplink BWP of the serving cell (initial uplink BWP). In an example, the uplink BWP may be indicated by RRC signaling (e.g., initialUplinkBWP). In an example, the switch from the active UL BWP to the uplink BWP may include setting the uplink BWP to the currently active UL BWP of the serving cell. In an example, the serving cell may not be a SpCell. In an example, the serving cell may be an SCell. In an example, in response to the serving cell not being a SpCell, the MAC entity may perform a random access procedure on the uplink BWP of the serving cell and the active downlink BWP of the SpCell. In an example, in response to initiating a random access procedure, the wireless device may stop (if running) the second BWP inactivity timer associated with the second active DL BWP of the serving cell (e.g., bwp-InactivityTimer configured by the higher layer (RRC)). In an example, in response to initiating a random access procedure and the serving cell being an SCell, the wireless device may stop (if running) the first BWP inactivity timer associated with the active DL BWP of the SpCell (e.g., bwp-InactivityTimer configured by the higher layer (RRC)).

[0303] In an example, the MAC entity of the wireless device may receive a PDCCH for BWP switching (e.g., UL BWP and / or DL BWP switching) of the serving cell. In an example, when the MAC entity receives the PDCCH, there may be no ongoing random access procedure associated with the serving cell. In an example, when the MAC entity receives a PDCCH for BWP switching of the serving cell, in response to there not being an ongoing random access procedure associated with the serving cell, the MAC entity may perform a BWP switch to the BWP indicated by the PDCCH for the serving cell.

[0304] In an example, a MAC entity of a wireless device may receive a PDCCH for a BWP switch (e.g., UL BWP and / or DL BWP switch) of a serving cell. In an example, the PDCCH may be addressed to the C-RNTI of the wireless device. In an example, there may be an ongoing random access procedure associated with the serving cell. In an example, in response to receiving the PDCCH addressed to the C-RNTI, the wireless device may (successfully) complete the ongoing random access procedure associated with the serving cell. In an example, in response to (successfully) completing the ongoing random access procedure associated with the serving cell, the MAC entity may perform a BWP switch to the BWP indicated by the PDCCH for the serving cell.

[0305] In an example, a MAC entity of a wireless device may receive a PDCCH for a BWP switch (e.g., UL BWP and / or DL BWP switch) of a serving cell. In an example, when the MAC entity receives the PDCCH, there may be an ongoing random access procedure associated with the serving cell in the MAC entity. In an example, when the MAC entity receives a PDCCH for a BWP switch of a serving cell, in response to an ongoing random access procedure associated with the serving cell, it may be determined by the UE implementation whether to perform a BWP switch or ignore the PDCCH for the BWP switch.

[0306] In an example, the MAC entity may perform a BWP switch (except for successful contention resolution of a random access procedure) in response to receiving a PDCCH for a BWP switch. In an example, performing a BWP switch may include switching to the BWP indicated by the PDCCH. In an example, in response to performing a BWP switch, the MAC entity may stop the ongoing random access procedure and may initiate a second random access procedure after performing the BWP switch.

[0307] In an example, the MAC entity may ignore a PDCCH for a BWP switch. In an example, in response to ignoring the PDCCH for a BWP switch, the MAC entity may continue the ongoing random access procedure on the serving cell.

[0308] In an example, a base station may configure an active serving cell of a wireless device with a BWP inactivity timer.

[0309] In an example, the base station may configure the wireless device with a default DL BWP ID of an active serving cell (e.g., via RRC signaling including a defaultDownlinkBWP-Id parameter). In an example, the active DL BWP of the active serving cell may not be the BWP indicated by the default DL BWP ID.

[0310] In an example, the base station may not configure the wireless device with the default DL BWP ID of the active serving cell (e.g., via RRC signaling including the defaultDownlinkBWP-Id parameter). In an example, the active DL BWP of the active serving cell may not be the initial downlink BWP of the active serving cell (e.g., via RRC signaling including the initialDownlinkBWP parameter).

[0311] In an example, when the base station configures the wireless device with the default DL BWP ID and the active DL BWP of the active serving cell is not the BWP indicated by the default DL BWP ID; or when the base station does not configure the wireless device with the default DL BWP ID and the active DL BWP is not the initial downlink BWP, the wireless device may start or restart a BWP inactivity timer associated with the active DL BWP of the active serving cell in response to receiving a PDCCH indicating a downlink assignment or an uplink grant on the active DL BWP. In an example, the PDCCH may be addressed to a C-RNTI. In an example, the PDCCH may be addressed to a CS-RNTI.

[0312] In an example, when the base station configures the wireless device with the default DL BWP ID and the active DL BWP of the active serving cell is not the BWP indicated by the default DL BWP ID; or when the base station does not configure the wireless device with the default DL BWP ID and the active DL BWP is not the initial downlink BWP, the wireless device may start or restart a BWP inactivity timer associated with the active DL BWP of the active serving cell in response to receiving a PDCCH indicating a downlink assignment or an uplink grant for the active DL BWP. In an example, the PDCCH may be addressed to a C-RNTI. In an example, the PDCCH may be addressed to a CS-RNTI.

[0313] In an example, the wireless device may receive a PDCCH when there is no ongoing random access procedure associated with the active serving cell. In an example, when there is an ongoing random access procedure associated with the active serving cell and the ongoing random access procedure is successfully completed in response to receiving a PDCCH addressed to the C-RNTI of the wireless device, the wireless device may receive a PDCCH.

[0314] In an example, when the base station configures the wireless device with a default DL BWP ID and the active DL BWP of the active serving cell is not the BWP indicated by the default DL BWP ID; or when the base station does not configure the wireless device with a default DL BWP ID and the active DL BWP is not the initial downlink BWP, the wireless device may start or restart a BWP inactivity timer associated with the active DL BWP of the active serving cell in response to transmitting a first MAC PDU in a configured uplink grant or receiving a second MAC PDU in a configured downlink assignment.

[0315] In an example, when there is no ongoing random access procedure associated with the active serving cell, the wireless device may transmit a first MAC PDU and / or receive a second MAC PDU.

[0316] In an example, the BWP inactivity timer associated with the active DL BWP of the active serving cell may expire.

[0317] In an example, the base station may configure the wireless device with a default DL BWP ID. In an example, when the base station configures the wireless device with a default DL BWP ID, in response to the expiration of the BWP inactivity timer, the MAC entity of the wireless device may perform a BWP handover to the BWP indicated by the default DL BWP ID.

[0318] In an example, the base station may not configure the wireless device with a default DL BWP ID. In an example, when the base station does not configure the wireless device with a default DL BWP ID, in response to the expiration of the BWP inactivity timer, the MAC entity of the wireless device may perform a BWP handover to the initial downlink BWP (e.g., initialDownlinkBWP in RRC signaling).

[0319] In an example, the wireless device may initiate a random access procedure on a secondary cell (e.g., SCell). In an example, the wireless device may monitor a random access response of the random access procedure on the SpCell. In an example, when the wireless device initiates a random access procedure on a secondary cell, in response to monitoring the random access response to the SpCell, the secondary cell and the SpCell may be associated with the random access procedure.

[0320] In an example, a wireless device may receive a PDCCH for BWP switching (e.g., UL and / or DL BWP switching). In an example, in response to receiving the PDCCH, a MAC entity of the wireless device may switch from a first active DL BWP of an active serving cell to a BWP (e.g., DL BWP) of the active serving cell. In an example, the switch from the first active DL BWP to the BWP may include setting the BWP as the current active DL BWP of the active serving cell. In an example, the wireless device may deactivate the first active DL BWP in response to the switch.

[0321] In an example, a base station may configure the wireless device with a default DL BWP ID. In an example, the BWP may not be indicated (or identified) by the default DL BWP ID. In an example, when the base station configures the wireless device with a default DL BWP ID and the MAC entity of the wireless device switches from a first active DL BWP of an active serving cell to a BWP, the wireless device may start or restart a BWP inactivity timer associated with the BWP (e.g., the current active DL BWP) in response to the BWP not being the default DL BWP (or the BWP not being indicated by the default DL BWP ID).

[0322] In an example, the base station may not configure the wireless device with a default DL BWP ID. In an example, the BWP may not be the initial downlink BWP of the active serving cell. In an example, when the base station does not configure the wireless device with a default DL BWP ID and the MAC entity of the wireless device switches from a first active DL BWP of an active serving cell to a BWP, the wireless device may start or restart a BWP inactivity timer associated with the BWP (e.g., the current active DL BWP) in response to the BWP not being the initial downlink BWP.

[0323] In an example, when carrier aggregation (CA) is configured, the base station may configure the wireless device with a secondary cell (e.g., SCell). In an example, the wireless device may receive an SCell activation / deactivation MAC CE for activating the secondary cell. In an example, the secondary cell may be deactivated before receiving the SCell activation / deactivation MAC CE. In an example, when the wireless device receives the SCell activation / deactivation MAC CE for activating the secondary cell, the wireless device may activate the downlink BWP of the secondary cell and activate the uplink BWP of the secondary cell in response to the secondary cell being deactivated before receiving the SCell activation / deactivation MAC CE. In an example, the downlink BWP may be indicated by firstActiveDownlinkBWP-Id. In an example, the uplink BWP may be indicated by firstActiveUplinkBWP-Id.

[0324] In an example, the base station may configure the wireless device with a BWP inactivity timer for an activated secondary cell. In an example, the sCellDeactivationTimer associated with the activated secondary cell may expire. In an example, in response to the sCellDeactivationTimer expiring, the wireless device may stop the BWP inactivity timer associated with the activated secondary cell. In an example, in response to the sCellDeactivationTimer expiring, the wireless device may deactivate the active downlink BWP associated with the activated secondary cell (e.g., as well as the active UL BWP, if present).

[0325] In an example, when configured to operate in a bandwidth part (BWP) of a serving cell, a wireless device (e.g., a UE) may be configured by a higher layer with parameter BWP - Downlink with a first set of BWPs (e.g., up to four BWPs) for reception by the UE (e.g., a DL BWP set) in the downlink (DL) bandwidth of the serving cell.

[0326] In an example, when configured to operate in a bandwidth part (BWP) of a serving cell, a wireless device (e.g., a UE) may be configured by a higher layer with parameter BWP - Uplink with a second set of BWPs (e.g., up to four BWPs) for transmission by the UE (e.g., a UL BWP set) in the uplink (UL) bandwidth of the serving cell.

[0327] In an example, the base station may not provide the wireless device with the higher layer parameter initialDownlinkBWP. In response to not providing the wireless device with the higher layer parameter initialDownlinkBWP, the initial active DL BWP may be defined, for example, by the position and number of consecutive PRBs and the subcarrier spacing (SCS) and cyclic prefix for PDCCH reception in a control resource set (CORESET) for a type 0 - PDCCH common search space (CSS) set. In an example, the consecutive PRBs may start from the first PRB with the lowest index among the PRBs of the CORESET for the type 0 - PDCCH CSS set.

[0328] In an example, the base station may provide the wireless device with the higher layer parameter initialDownlinkBWP. In an example, the initial active DL BWP may be provided by the higher layer parameter initialDownlinkBWP in response to the provision.

[0329] In an example, for operations on a cell (e.g., a primary cell, a secondary cell), the base station may provide an initial active UL BWP to the wireless device by a higher layer parameter (e.g., initialUplinkBWP). In an example, when a supplementary uplink carrier (SUL) is configured, the base station may provide a second initial active uplink BWP to the wireless device on the supplementary uplink carrier by a second higher layer parameter (e.g., initialUplinkBWP in supplementaryUplink).

[0330] In an example, the wireless device may have a dedicated BWP configuration.

[0331] In an example, in response to the wireless device having a dedicated BWP configuration, the wireless device may be provided by a higher layer parameter (e.g., firstActiveDownlinkBWP-Id). The higher layer parameter may indicate a first active DL BWP for reception.

[0332] In an example, in response to the wireless device having a dedicated BWP configuration, the wireless device may be provided by a higher layer parameter (e.g., firstActiveUplinkBWP-Id). The higher layer parameter may indicate a first active UL BWP for transmission on a carrier (e.g., SUL, NUL) of a serving cell (e.g., a primary cell, a secondary cell).

[0333] In an example, for a DL BWP in a first set of BWPs or a UL BWP in a second set of BWPs, the base station may configure the wireless device of the serving cell with at least one of the following: a subcarrier spacing provided by a higher layer parameter subcarrierSpacing, a cyclic prefix provided by a higher layer parameter cyclicPrefix, an index in the first set of BWPs or in the second set of BWPs provided by a higher layer parameter bwp-Id (e.g., bwp-Id); a third set of BWP-common and a fourth set of BWP-dedicated parameters provided by higher layer parameters bwp-Common and bwp-Dedicated, respectively. In an example, the base station may also configure the wireless device of the serving cell with a common RB RB and a number of consecutive RBs provided by a higher layer parameter locationAndBandwidth In an example, the higher layer parameter locationAndBandwidth may indicate an offset RB start and a length L RB as a resource indicator value (RIV), set and the value O provided by the higher layer parameter offsetToCarrier for the higher layer parameter subcarrierSpacing carrier .

[0334] In an example, for unpaired spectrum operation, when the DL BWP index of the DL BWP is the same as the UL BWP index of the UL BWP, the DL BWP having the DL BWP index provided by the higher layer parameter bwp-Id (e.g., bwp-Id) from the first set of BWPs can be linked to the UL BWP having the UL BWP index provided by the higher layer parameter bwp-Id (e.g., bwp-Id) from the second set of BWPs.

[0335] In an example, the DL BWP index of the DL BWP can be the same as the UL BWP index of the UL BWP. In an example, for unpaired spectrum operation, in response to the DL BWP index of the DL BWP being the same as the UL BWP index of the UL BWP, the wireless device may not expect to receive a configuration (e.g., RRC configuration) where the first center frequency of the DL BWP is different from the second center frequency of the UL BWP.

[0336] In an example, for the DL BWP in the first set of BWPs on a serving cell (e.g., the primary cell), the base station can configure the wireless device with one or more control resource sets (CORESET) for each type of common search space (CSS) set and for the UE-specific search space (USS). In an example, in the active DL BWP, the wireless device may not expect to be configured without a common search space set on the primary cell (or on the PSCell).

[0337] In an example, the base station can provide the wireless device with the higher layer parameter controlResourceSetZero and the higher layer parameter searchSpaceZero in the higher layer parameter PDCCH-ConfigSIB1 or the higher layer parameter PDCCH-ConfigCommon. In an example, in response to this provision, the wireless device can determine the CORESET of the search space set according to the higher layer parameter controlResourcesetZero, and can determine the corresponding PDCCH monitoring occasion. The active DL BWP of the serving cell may not be the initial DL BWP of the serving cell. When the active DL BWP is not the initial DL BWP of the serving cell, the wireless device can determine the PDCCH monitoring occasion of the search space set within the active DL BWP and the active DL BWP having the same SCS configuration and the same cyclic prefix as the initial DL BWP in response to the bandwidth of the CORESET.

[0338] In an example, for a UL BWP in a second set of BWPs of a serving cell (e.g., a primary cell or a PUCCH SCell), the base station may configure the wireless device with one or more resource sets (e.g., time-frequency resources / timings) for PUCCH transmission.

[0339] In an example, the UE may receive PDCCH and PDSCH in the DL BWP according to the configured subcarrier spacing and the CP length for the DL BWP.

[0340] In an example, the UE may transmit PUCCH and PUSCH in the UL BWP according to the configured subcarrier spacing and the CP length for the UL BWP.

[0341] In an example, the bandwidth part indicator field may be configured in a DCI format (e.g., DCI format 1_1). In an example, the value of the bandwidth part indicator field may indicate, for one or more DL receptions, the active DL BWP from the first set of BWPs. In an example, the bandwidth part indicator field may indicate a DL BWP different from the active DL BWP. In an example, in response to the bandwidth part indicator field indicating a DL BWP different from the active DL BWP, the wireless device may set the DL BWP to the current active DL BWP. In an example, setting the DL BWP to the current active DL BWP may include activating the DL BWP and deactivating the active DL BWP.

[0342] In an example, the bandwidth part indicator field may be configured in a DCI format (e.g., DCI format 0_1). In an example, the value of the bandwidth part indicator field may indicate, for one or more UL transmissions, the active UL BWP from the second set of BWPs. In an example, the bandwidth part indicator field may indicate a UL BWP different from the active UL BWP. In an example, in response to the bandwidth part indicator field indicating a UL BWP different from the active UL BWP, the wireless device may set the UL BWP to the current active UL BWP. In an example, setting the UL BWP to the current active UL BWP may include activating the UL BWP and deactivating the active UL BWP.

[0343] In an example, the DCI format (e.g., DCI format 1_1) indicating a change in the active DL BWP may include a time domain resource assignment field. The time domain resource assignment field may provide a slot offset value for PDSCH reception. In an example, the slot offset value may be less than the latency required by the wireless device for a change in the active DL BWP. In an example, in response to the slot offset value being less than the latency required by the wireless device for a change in the active DL BWP, the wireless device may not expect to detect the DCI format indicating a change in the active DL BWP.

[0344] In an example, a DCI format (e.g., DCI format 0_1) indicating an active UL BWP change may include a time domain resource assignment field. The time domain resource assignment field may provide a slot offset value for PUSCH transmission. In an example, the slot offset value may be less than the latency required by the wireless device for an active UL BWP change. In an example, in response to the slot offset value being less than the latency required by the wireless device for an active UL BWP change, the wireless device may not expect to detect the DCI format indicating the active UL BWP change.

[0345] In an example, the wireless device may receive a PDCCH in a slot of a scheduling cell. In an example, the wireless device may detect, in the PDCCH of the scheduling cell, a DCI format (e.g., DCI format 1_1) indicating an active DL BWP change of a serving cell. In an example, the DCI format may include a time domain resource assignment field. The time domain resource assignment field may provide a slot offset value for PDSCH transmission. In an example, the slot offset value may indicate a second slot. In an example, in response to detecting the DCI format indicating the active DL BWP change, during the duration from the end of the third symbol of the slot until the start of the second slot, the wireless device may not be required to receive or transmit in the serving cell.

[0346] In an example, the wireless device may receive a PDCCH in a slot of a scheduling cell. In an example, the wireless device may detect, in the PDCCH of the scheduling cell, a DCI format (e.g., DCI format 0_1) indicating an active UL BWP change of a serving cell. In an example, the DCI format may include a time domain resource assignment field. The time domain resource assignment field may provide a slot offset value for PUSCH transmission. In an example, the slot offset value may indicate a second slot. In an example, in response to detecting the DCI format indicating the active UL BWP change, during the duration from the end of the third symbol of the slot until the start of the second slot, the wireless device may not be required to receive or transmit in the serving cell.

[0347] In an example, when the corresponding PDCCH detecting the detected DCI format 0_1 or the detected DCI format 1_1 is received within the first 3 symbols of a slot, the UE may expect to detect the DCI format 0_1 indicating an active UL BWP change / handover, or the DCI format 1_1 indicating an active DL BWP change / handover. In an example, if the corresponding PDCCH is received after the first 3 symbols of the slot, the UE may not expect to detect the DCI format 0_1 indicating an active UL BWP change / handover, or the DCI format 1_1 indicating an active DL BWP change / handover.

[0348] In an example, an active DL BWP change may include a handover from an active DL BWP of a serving cell to a DL BWP of the serving cell. In an example, a handover from an active DL BWP to a DL BWP may include setting the DL BWP as the current active DL BWP and deactivating the active DL BWP.

[0349] In an example, an active UL BWP change may include a handover from an active UL BWP of a serving cell to a UL BWP of the serving cell. In an example, a handover from an active UL BWP to a UL BWP may include setting the UL BWP as the current active UL BWP and deactivating the active UL BWP.

[0350] In an example, for a serving cell (e.g., a PCell, an SCell), the base station may provide a higher layer parameter defaultDownlinkBWP-Id to the wireless device. In an example, the higher layer parameter defaultDownlinkBWP-Id may indicate a default DL BWP in a first set of (configured) BWPs of the serving cell.

[0351] In an example, the base station may not provide the higher layer parameter defaultDownlinkBWP-Id to the wireless device. In response to not being provided with the higher layer parameter defaultDownlinkBWP-Id, the wireless device may set an initial active DL BWP as the default DL BWP. In an example, in response to not being provided with the higher layer parameter defaultDownlinkBWP-Id, the default DL BWP may be the initial active DL BWP.

[0352] In an example, the base station may provide a higher layer parameter BWP-InactivityTimer to the wireless device. In an example, the higher layer parameter BWP-InactivityTimer may indicate a BWP inactivity timer having a timer value for a serving cell (e.g., a primary cell, a secondary cell). In an example, when the higher layer parameter BWP-InactivityTimer is provided and the BWP inactivity timer is running, in response to not restarting the BWP inactivity timer during an interval of a subframe in frequency range 1 or a half-subframe interval in frequency range 2, the wireless device may decrement the BWP inactivity timer at the end of a subframe in frequency range 1 (e.g., FR1, below 6 GHz) or at the end of a half-subframe in frequency range 2 (e.g., FR2, millimeter wave).

[0353] In an example, the wireless device may perform an active DL BWP change of a serving cell in response to the expiration of a BWP inactivity timer associated with the serving cell. In an example, during a duration starting from half of a subframe in frequency range 1 or a subframe in frequency range 2, the wireless device may not need to receive or transmit in the serving cell. This duration may start after / immediately after the expiration of the BWP inactivity timer and may continue until the start of a time slot in which the wireless device can receive and / or transmit.

[0354] In an example, the base station may provide the wireless device with a higher layer parameter firstActiveDownlinkBWP-Id of a serving cell (e.g., a secondary cell). In an example, the higher layer parameter firstActiveDownlinkBWP-Id may indicate the DL BWP on the serving cell (e.g., a secondary cell). In an example, in response to being provided by the higher layer parameter firstActiveDownlinkBWP-Id, the wireless device may use the DL BWP as the first active DL BWP on the serving cell.

[0355] In an example, the base station may provide the wireless device with a higher layer parameter firstActiveUplinkBWP-Id on a carrier (e.g., SUL, NUL) of a serving cell (e.g., a secondary cell). In an example, the higher layer parameter firstativeuplinkwp-Id may indicate the UL BWP. In an example, in response to being provided by the higher layer parameter firstActiveUplinkBWP-Id, the wireless device may use the UL BWP as the first active UL BWP on the carrier of the serving cell.

[0356] In an example, for paired spectrum operation, if the UE changes its active UL BWP on the primary cell between the time of detecting DCI format 1_0 or DCI format 1_1 and the time of the corresponding PUCCH transmission with HARQ-ACK information, the UE may not be expected to transmit the PUCCH with HARQ-ACK information on the PUCCH resource indicated by DCI format 1_0 or DCI format 1_1.

[0357] In an example, when the UE performs RRM measurements on a bandwidth that is not within the UE's active DL BWP, the UE may monitor the PDCCH.

[0358] In an example, the DL BWP index (ID) can be an identifier of the DL BWP. One or more parameters in the RRC configuration can use the DL BWP-ID to associate one or more parameters with the DL BWP. In the example, DL BWP ID = 0 can be associated with the initial DL BWP.

[0359] In an example, the UL BWP index (ID) can be an identifier of the UL BWP. One or more parameters in the RRC configuration can use the UL BWP-ID to associate one or more parameters with the UL BWP. In the example, UL BWP ID = 0 can be associated with the initial UL BWP.

[0360] If the higher layer parameter firstActiveDownlinkBWP-Id is configured for the SpCell, the higher layer parameter firstActiveDownlinkBWP-Id indicates the ID of the DL BWP to be activated after reconfiguration is performed.

[0361] If the higher layer parameter firstActiveDownlinkBWP-Id is configured for the SCell, the higher layer parameter firstActiveDownlinkBWP-Id indicates the ID of the DL BWP to be used after MAC activation of the SCell.

[0362] If the higher layer parameter firstActiveUplinkBWP-Id is configured for the SpCell, the higher layer parameter firstActiveUplinkBWP-Id indicates the ID of the UL BWP to be activated after reconfiguration is performed.

[0363] If the higher layer parameter firstActiveUplinkBWP-Id is configured for the SCell, the higher layer parameter firstActiveUplinkBWP-Id indicates the ID of the UL BWP to be used after MAC activation of the SCell.

[0364] In an example, to perform reconfiguration with synchronization, the wireless device can consider the uplink BWP indicated in the higher layer parameter firstActiveUplinkBWP-Id as the active uplink BWP.

[0365] In an example, to perform reconfiguration with synchronization, the wireless device can consider the downlink BWP indicated in the higher layer parameter firstActiveDownlinkBWP-Id as the active downlink BWP.

[0366] Over the next many years, the amount of data traffic carried over cellular networks is expected to increase. The number of users / devices is increasing, and each user / device accesses an increasing number and variety of services, such as video delivery, large files, images. This requires not only a high capacity of the network but also the provision of very high data rates to meet the customers' expectations for interactivity and responsiveness. Therefore, cellular operators may need more spectrum to meet the growing demand. Given the users' expectations for high data rates and seamless mobility, it is beneficial to make more spectrum available for the deployment of macro cells as well as small cells of the cellular system.

[0367] To meet the market demand, operators are increasingly interested in using unlicensed spectrum to deploy some complementary access to meet the traffic growth. This is illustrated by the Wi-Fi networks deployed by a large number of operators and the 3GPP standardization of the interworking solutions with Wi-Fi (e.g., LTE / WLAN interworking). This interest indicates that unlicensed spectrum can be an effective complement to the licensed spectrum of cellular operators when available, to address the traffic explosion in some scenarios such as hotspots. For example, Licensed-Assisted Access (LAA) and / or New Radio on Unlicensed (NR-U) can provide alternatives for operators to utilize unlicensed spectrum while managing a radio network, thus providing new possibilities for optimizing network efficiency.

[0368] In an exemplary implementation, Listen-Before-Talk (LBT) can be implemented for transmissions in unlicensed cells. Unlicensed cells can be referred to as LAA cells and / or NR-U cells. Unlicensed cells can operate non-independently with an anchor cell in a licensed band or independently without an anchor cell in a licensed band. LBT can include Clear Channel Assessment (CCA). For example, in an LBT procedure, a device can apply CCA before using an unlicensed cell or channel. CCA can include energy detection to determine the presence of other signals on the channel (e.g., the channel is occupied) or the absence of other signals on the channel (e.g., the channel is idle). National regulations may affect the LBT procedure. For example, European and Japanese regulations require the use of LBT in unlicensed bands such as the 5 GHz unlicensed band. In addition to regulatory requirements, carrier sensing via LBT can be a way to fairly share unlicensed spectrum among different devices and / or networks attempting to utilize unlicensed spectrum.

[0369] In an exemplary embodiment, discontinuous transmissions with a limited maximum transmission duration on an unlicensed frequency band can be implemented. Some of these functions can be supported by one or more signals to be transmitted at the start of a discontinuous downlink transmission in the unlicensed frequency band. After or in response to obtaining channel access based on successful LBT operation, channel reservation can be enabled by signal transmission by an NR-U node. Other nodes can receive signals (e.g., signals transmitted for channel reservation) having an energy level higher than a specific threshold at which the channel can be sensed to be occupied. Functions that may need to be supported by one or more signals for operation in an unlicensed frequency band with discontinuous downlink transmissions can include one or more of the following: detection of downlink transmissions (including cell identification) in the unlicensed frequency band by a wireless device; time and frequency synchronization of the wireless device.

[0370] In an exemplary embodiment, downlink transmissions and frame structure design for operation in an unlicensed frequency band can adopt subframe, (micro)slot, and / or symbol boundary alignment according to the timing relationship between serving cells aggregated by a carrier set. This may not mean that base station transmissions start at subframe, (micro)slot, and / or symbol boundaries. For example, according to LBT, when not all OFDM symbols are available for transmission in a subframe, unlicensed cell operation (e.g., LAA and / or NR-U) can support the transmission of PDSCH. The necessary control information for delivering PDSCH can also be supported.

[0371] The LBT procedure can be used for fair and friendly coexistence of 3GPP systems (e.g., LTE and / or NR) with other operators and technologies operating in the unlicensed spectrum. For example, a node attempting to transmit on a carrier in the unlicensed spectrum can perform CCA as part of the LBT procedure to determine whether the channel is available for use. The LBT procedure can involve energy detection to determine whether the channel is in use. For example, in some regions, such as in Europe, regulatory requirements specify an energy detection threshold such that if a node receives energy greater than the threshold, the node assumes the channel is in use and not idle. While a node can follow such regulatory requirements, the node can optionally use an energy detection threshold lower than the energy detection threshold specified by the regulatory requirements. Radio access technologies (e.g., LTE and / or NR) can adopt a mechanism for adaptively changing the energy detection threshold. For example, NR-U can adopt a mechanism for adaptively reducing the energy detection threshold from an upper limit. The adaptive mechanism does not exclude static or semi-static settings of the threshold. In an example, a Category 4 LBT (CAT4·LBT) mechanism or other types of LBT mechanisms can be implemented.

[0372] Various exemplary LBT mechanisms can be implemented. In an example, for some signals, in some implementation scenarios, in some cases, and / or in some frequencies, the transmitting entity may not perform the LBT procedure. In an example, Category 1 (CAT1, e.g., without LBT) can be implemented in one or more cases. For example, a channel in an unlicensed band can be reserved by a first device (e.g., a base station performing DL transmission), and a second device (e.g., a wireless device) takes over the transmission without performing CAT1 LBT. In an example, Category 2 (CAT2, e.g., LBT without random backoff and / or one-shot LBT) can be implemented. Determining the duration for which the channel is idle can be decisive (e.g., through modulation). The base station can transmit an uplink grant indicating the LBT type (e.g., CAT2 LBT) to the wireless device. CAT1 LBT and CAT2 LBT can be used for channel occupancy time (COT) sharing. For example, the base station (wireless device) can transmit an uplink grant (in response to uplink control information) including one type of LBT. For example, CAT1 LBT and / or CAT2 LBT (or uplink control information) in the uplink grant can be indicated to the receiving device (e.g., the base station and / or the wireless device) to trigger COT sharing. In an example, Category 3 (CAT3, e.g., LBT with random backoff with a fixed-size contention window) can be implemented. The LBT procedure can have a following procedure as one of its components. The transmitting entity can extract a random number N within the contention window. The size of the contention window can be specified by the minimum and maximum values of N. The size of the contention window can be fixed. The random number N can be employed in the LBT procedure to determine the duration for which the channel is sensed idle before the transmitting entity transmits on the channel. In an example, Category 4 (CAT4, e.g., LBT with random backoff with a variable-size contention window) can be implemented. The transmitting entity can extract a random number N within the contention window. The size of the contention window can be specified by the minimum and maximum values of N. When the random number N is drawn, the transmitting entity can change the size of the contention window. The random number N can be used in the LBT procedure to determine the duration for which the channel is sensed idle before the transmitting entity transmits on the channel.

[0373] In an example, the wireless device can employ uplink (UL) LBT. UL LBT can be different from downlink (DL) LBT (e.g., by using different LBT mechanisms or parameters), e.g., because NR-U UL can be based on scheduled access that affects the channel contention opportunity of the wireless device. Other considerations that contribute to different UL LBT include, but are not limited to, multiplexing multiple wireless devices in a subframe (time slot and / or mini-slot).

[0374] In an example, a DL transmission burst can be a continuous (unicast, multicast, broadcast, and / or a combination thereof) transmission by a base station (e.g., to one or more wireless devices) on a carrier component (CC). A UL transmission burst can be a continuous transmission from one or more wireless devices to the base station on the CC. In an example, DL transmission bursts and UL transmission bursts on the CC in an unlicensed spectrum can be scheduled in a TDM manner on the same unlicensed carrier. Switching between a DL transmission burst and a UL transmission burst may require LBT (e.g., CAT1 LBT, CAT2 LBT, CAT3 LBT, and / or CAT4 LBT). For example, a certain moment can be part of a DL transmission burst or a UL transmission burst.

[0375] Channel Occupancy Time (COT) sharing can be adopted in NR-U. COT sharing can be a mechanism for one or more wireless devices to share a channel sensed as idle by at least one of the one or more wireless devices. For example, one or more first devices can occupy a channel via LBT (e.g., the channel is sensed as idle based on CAT4 LBT), and one or more second devices can share the channel using LBT within a Maximum COT (MCOT) limit (e.g., 25us LBT). For example, the MCOT limit can be given according to a priority level, logical channel priority, and / or a specific wireless device. COT sharing can allow obtaining a concession for UL in the unlicensed band. For example, a base station can transmit an uplink grant to a wireless device for UL transmission. For example, the base station can occupy a channel and transmit a control signal indicating that the one or more wireless devices can use the channel to the one or more wireless devices. For example, the control signal can include an uplink grant and / or a specific LBT type (e.g., CAT1 LBT and / or CAT2 LBT). The one or more wireless devices can determine COT sharing based at least on the uplink grant and / or the specific LBT type. The wireless device can perform UL transmission with dynamic grant and / or configured grant (e.g., type 1, type 2, autonomous UL) using a specific LBT (e.g., CAT2 LBT, such as 25us LBT) during a configured period (e.g., if COT sharing is triggered). COT sharing can be triggered by a wireless device. For example, a wireless device performing UL transmission based on a configured grant (e.g., type 1, type 2, autonomous UL) can transmit uplink control information indicating COT sharing (UL-DL handover within (M)COT). The start time of the DL transmission in COT sharing triggered by a wireless device can be indicated in one or more ways. For example, one or more parameters in the uplink control information indicate the start time. For example, the resource configuration of the configured grant configured / activated by the base station can indicate the start time. For example, the base station can be allowed to perform DL transmission after or in response to UL transmission on a configured grant (e.g., type 1, type 2, and / or autonomous UL). There may be a delay between the uplink grant and the UL transmission (e.g., at least 4ms). The delay can be predefined by the base station, configured semi-statically (via RRC message), and / or indicated dynamically by the base station (e.g., via the uplink grant). The delay is not counted into the COT duration.

[0376] In an example, it is possible to support the switching of single and multiple DL to UL and UL to DL within a shared COT. Exemplary LBT requirements for single or multiple switching points may include: for gaps less than 16 us: LBT may not be used; for gaps greater than 16 us but not exceeding 25 us: one-shot LBT may be used; for a single switching point, for gaps greater than 25 us for DL to UL transmission: one-shot LBT may be used; for multiple switching points, for gaps greater than 25 us for DL to UL transmission, one-shot LBT may be used.

[0377] In an example, signals that facilitate their detection with low complexity can be used for power saving of wireless devices, improving coexistence, spatial reuse at least within the same operator network, serving cell transmission burst acquisition, etc. In an example, radio access technologies (e.g., LTE and / or NR) can use signals that at least include SS / PBCH block burst set transmission. Other channels and signals can be transmitted together as part of the signal. In an example, the signal can be a Discovery Reference Signal (DRS). There may be no gap within the time span during which the signal is transmitted at least within a beam. In an example, a gap can be defined for beam switching. In an example, block-interleaving based PUSCH can be employed. In an example, the same interleaving structure can be used for PUCCH and PUSCH. In an example, interleaving-based PRACH can be used.

[0378] In an example, the initial active DL / UL BWP can be approximately 20 MHz for the first unlicensed band, e.g., in the 5 GHz unlicensed band. For example, if similar channelization (e.g., through modulation) is used in one or more unlicensed bands, the initial active DL / UL BWP in those one or more unlicensed bands can be similar (e.g., approximately 20 MHz in the 5 GHz and / or 6 GHz unlicensed spectrum).

[0379] In an example, HARQ acknowledgments and negative acknowledgments (A / N) for corresponding data can be transmitted in a shared COT (e.g., using CAT2 LBT). In some examples, HARQ A / N can be transmitted in a separate COT (e.g., a separate COT may require CAT4 LBT). In an example, when transmitting UL HARQ feedback on an unlicensed band, radio access technologies (e.g., LTE and / or NR) can support flexible triggering and multiplexing of HARQ feedback for one or more DL HARQ processes. HARQ process information can be defined independently of the transmission timing (e.g., time and / or frequency resources). In an example, UCI on PUSCH can carry HARQ process ID, NDI, RVID. In an example, Downlink Feedback Information (DFI) can be used to transmit HARQ feedback for configured grants.

[0380] In an example, CBRA and CFRA can be supported on the SpCell. CFRA can be supported on the SCell. In an example, the RAR can be transmitted via the SpCell, for example, in a non-standalone scenario. In an example, the RAR can be transmitted via the SpCell and / or the SCell, for example, in a non-standalone scenario. In an example, a pre-defined HARQ process ID is used for the RAR.

[0381] In an example, carrier aggregation between an authorized band NR (PCell) and NR-U (SCell) can be supported. In an example, the NR-U SCell can have both DL and UL, or can have only DL. In an example, dual connectivity between an authorized band LTE (PCell) and NR-U (PSCell) can be supported. In an example, standalone NR-U can be supported, where all carriers are in one or more unlicensed bands. In an example, an NR cell with DL in an unlicensed band and UL in a licensed band (and vice versa) can be supported. In an example, dual connectivity between an authorized band NR (PCell) and NR-U (PSCell) can be supported.

[0382] In an example, the operating bandwidth of a radio access technology (e.g., LTE and / or NR) can be an integer multiple of 20 MHz, for example, in cases where it cannot be guaranteed (e.g., by regulation) that there is no Wi-Fi in the unlicensed band (e.g., below 5 GHz, 6 GHz, and / or 7 GHz) in which the radio access technology (e.g., LTE and / or NR) operates. In an example, a wireless device can perform one or more LBTs in units of 20 MHz. In an example, receiver-assisted LBT (e.g., an RTS / CTS type of mechanism) and / or on-demand receiver-assisted LBT (e.g., receiver-assisted LBT enabled only when needed) can be employed. In an example, techniques for enhanced spatial reuse can be used.

[0383] In operations in an unlicensed band (e.g., LTE eLAA / feLAA and / or NR-U), a wireless device can measure the (average) received signal strength indicator (RSSI) and / or can determine the channel occupancy (CO) of one or more channels. For example, the wireless device can report the channel occupancy and / or RSSI measurements to the base station. Reporting a metric representing the channel occupancy and / or medium contention can be beneficial. The channel occupancy can be defined as the fraction (e.g., percentage) of time during which the RSSI is measured above a configured threshold. The RSSI and CO measurement reports can help the base station detect hidden nodes and / or implement load-balanced channel access to reduce channel access conflicts.

[0384] Channel congestion may lead to LBT failures. For example, if a wireless device selects a cell / BWP / channel with the lowest channel congestion or load, the probability of successful LBT for random access and / or for data transmission can be increased. For example, a channel occupancy aware RACH procedure can be considered to reduce LBT failures. For example, the random access backoff time of a wireless device can be adjusted based on channel conditions (e.g., based on channel occupancy rate and / or RSSI measurements). For example, a base station can transmit (semi-statically and / or dynamically) a random access backoff. For example, the random access backoff can be predefined. For example, the random access backoff can be incremented after and in response to one or more random access response reception failures corresponding to one or more random access preamble attempts.

[0385] In unlicensed operation (e.g., NR-U), it may be beneficial for a UE to transmit HARQ ACK / NACK for corresponding data in the same shared COT. For example, a UE can receive DL transmissions (e.g., PDCCH and / or PDSCH) in a COT and can transmit HARQ ACK / NACK for the DL transmission in the COT. For example, a base station can obtain / initiate a COT by performing one or more LBT procedures. If possible, taking into account the UE processing time required between the received DL transmission and the HARQ ACK / NACK transmission, the UE can transmit one or more HARQ ACK / NACK information for one or more corresponding DL transmissions (e.g., PDCCH and / or PDSCH) in the same shared COT. A gap (e.g., up to 16 us) can be allowed between the end of the DL transmission and the immediate transmission of the HARQ feedback to accommodate the hardware turnaround time. The base station can schedule UL / DL transmissions (e.g., CSI reports or SRS, or other PUSCH, or CSI-RS, or other PDSCH) within the time between a DL transmission for a UE and the corresponding UL transmission for HARQ feedback for the same UE in the shared COT. For example, to reduce signaling overhead, the UL / DL transmissions scheduled in the time gap can be preconfigured and / or predetermined transmissions.

[0386] The UE may transmit one or more HARQ feedbacks of one or more DL transmissions in a COT (e.g., a second COT) separate from the COT (e.g., the first COT) in which the corresponding DL transmission is received. The base station may configure / signal a non-numerical value (e.g., a K1 value) of the PDSCH to HARQ feedback timing indicator in the DCI scheduling the PDSCH and / or the DCI releasing the DL SPS. The non-numerical value indicates to the UE that the timing and resources for HARQ-ACK feedback transmission for the corresponding PDSCH / PDCCH will be determined later. The first DCI format (e.g., DCI format 1_0) may not support signaling a non-numerical value of the PDSCH to HARQ feedback timing indicator.

[0387] In unlicensed operations, e.g., due to LBT failures, one or more HARQ ACK / NACK transmission opportunities of one or more given HARQ processes may be missed / lost. The base station may provide multiple and / or supplementary time-domain and / or frequency-domain transmission opportunities to enhance the HARQ feedback mechanism. The base station may trigger / request and / or enable multiplexing of one or more HARQ feedbacks of one or more DL HARQ processes. One or more HARQ feedbacks of one or more DL transmissions corresponding to a channel occupancy (COT) may be reported in the same channel occupancy. One or more HARQ feedbacks of DL transmissions corresponding to a channel occupancy may be reported outside of that channel occupancy.

[0388] The base station may request / trigger one or more HARQ feedbacks of one or more DL transmissions, where the one or more DL transmissions may be from one or more earlier COTs. For example, one or more DL transmissions may be scheduled in COT x, and one or more corresponding HARQ feedbacks may be scheduled / triggered in COT x + y, where y may be equal to or greater than 1, and x may be the index of the COT. For example, the DCI indicating the COT structure information may indicate the index of the COT.

[0389] The UE may be configured to report one or more HARQ feedbacks of one or more DL transmissions from one or more earlier COTs, e.g., with or without an explicit request / trigger from the base station.

[0390] The PDSCH-to-HARQ feedback timing indicator (K1 value) in the DCI for scheduling PDSCH can indicate UL resources (e.g., PUCCH and / or PUSCH) in the next COT. For example, the UE can receive PDSCH / PDCCH in the first COT and transmit the corresponding HARQ feedback in the second COT, e.g., based on the PDSCH-to-HARQ feedback timing indicator (K1 value) in the DCI. For example, the second COT can be the next COT after the first COT (e.g., cross-COT HARQ-ACK feedback). The second DCI can provide the UE with HARQ feedback timing and resource information. The second DCI can indicate the LBT category for transmitting the HARQ feedback in the second COT. The second DCI can be received before or after the first DCI.

[0391] The base station (BS) can configure a non-numerical value for HARQ feedback timing via RRC signaling, e.g., dl-DataToUL-ACK, which can be signaled by the scheduling DCI, e.g., via the parameter PDSCH-to-HARQ feedback timing indicator. The non-numerical value can indicate that the UE can store / defer the HARQ A / N feedback result for the corresponding PDSCH / PDCCH and can not provide any timing for the transmission of the HARQ A / N feedback result.

[0392] The HARQ feedback timing parameter (e.g., PDSCH-to-HARQ feedback timing indicator) in the DCI can indicate multiple timing values for multiple candidate HARQ feedback transmission opportunities. The UE can select one of the multiple HARQ feedback transmission opportunities and transmit the HARQ feedback through that opportunity.

[0393] The BS can configure the UE with an enhanced dynamic codebook for HARQ feedback operations. For example, in enhanced dynamic codebook operations, the BS can trigger a group of DL transmissions (e.g., PDSCH). For example, one or more fields in the DCI can indicate one or more PDSCH / PDCCH to be acknowledged via the indicated UL resources. For example, the group of DL transmissions can include one or more HARQ processes and / or can overlap with one or more time slots / sub-frames and / or can be derived from a dynamic time window. The DCI can carry DL scheduling assignments and / or UL grants and / or a DCI without a scheduling grant. The DCI can include one or more HARQ feedback timing values indicating the UL resources.

[0394] The DCI that schedules a DL assignment (e.g., PDSCH) can associate the PDSCH with a group. For example, the DCI can include a field indicating a group index. For example, the PDSCH scheduled by a first DCI format (e.g., DCI format 1_0) can be associated with a predefined group (e.g., PDSCH group #0). For example, an SPS PDSCH occasion can be associated with a predefined group. For example, an SPS PDSCH occasion can be associated with a first group, where the activation DCI indicates the index of the first group. For example, an SPS release PDCCH can be associated with a predefined group. For example, an SPS release PDCCH can indicate the index of the group.

[0395] The base station can schedule a first PDSCH with a PDSCH-to-HARQ feedback timing (e.g., K1 value) in a COT having a first group index. The PDSCH-to-HARQ feedback timing can have a non-numeric value. The BS can schedule one or more PDSCHs after the first PDSCH in the same COT and can assign the first group index to the one or more PDSCHs. At least one of the one or more PDSCHs can be scheduled with a numeric K1 value.

[0396] The DCI can indicate a new ACK feedback group indicator (NFI) for each PDSCH group. The NFI can operate as a toggle bit. For example, the UE can receive a DCI indicating that the NFI has been toggled for a PDSCH group. The UE can discard one or more HARQ feedbacks for one or more PDSCHs in the PDSCH group. One or more PDSCHs can be associated with / scheduled using one or more non-numeric K1 values and / or numeric K1 values. The UE may expect to reset the DAI value of the PDSCH group.

[0397] The UE can be configured with an enhanced dynamic codebook. The UE receives a first DCI format (e.g., DCI format 1_0) that schedules one or more PDSCHs. One or more PDSCHs can be associated with a PDSCH group (e.g., a predefined PDSCH group, such as group #0). The first DCI format may not indicate the NFI value of the PDSCH group. The UE can determine the NFI value based on a second DCI format (e.g., DCI format 1_1) that indicates the NFI value of the PDSCH group. The UE can detect the second DCI format since the last scheduled PUCCH and before the PUCCH occasion, where the second PUCCH occasion can include HARQ feedback corresponding to the PDSCH scheduled by the first DCI format. The last scheduled PUCCH can include HARQ feedback for the PDSCH group. The UE can not detect the second DCI that indicates the NFI value of the PDSCH group, and the UE can assume that one or more PDSCHs scheduled by the first DCI format do not belong to any PDSCH group, and the UE can report the HARQ feedback of at least one PDSCH scheduled by the first DCI format since the latest PUCCH occasion.

[0398] The DCI can request / trigger HARQ feedback for one or more groups of PDSCHs via the same PUCCH / PUSCH resource, for example. The HARQ feedback for multiple DL transmissions (e.g., PDSCHs) in the same group can be transmitted / multiplexed in the same PUCCH / PUSCH resource. The counter DAI and the total DAI value can be incremented / accumulated within the PDSCH group.

[0399] The UE can postpone the transmission of HARQ-ACK information corresponding to the PDSCH in the PUCCH by a value of K1, which results in a time T that is less than the processing time required for PUCCH transmission, where the time T is the time between the last symbol of the PDSCH and the start symbol of the PUCCH.

[0400] The UE may receive downlink signals (e.g., RRC and / or DCI) for scheduling the PDSCH. The UE may be configured with enhanced dynamic codebook HARQ feedback operations. The PDSCH may be scheduled with a non-numerical value (e.g., K1) for PDSCH-to-HARQ feedback timing. The UE may derive / determine the HARQ-ACK timing information of the PDSCH through the next / subsequent DCI. The next DCI may be a DL DCI that schedules one or more PDSCHs. The next DCI may include a numerical K1 value that indicates one or more PUCCH / PUSCH resources for HARQ feedback transmission for one or more DL transmissions including the PDSCH. The next DCI may trigger HARQ feedback transmission for one or more PDSCH groups of a group including the PDSCH. The UE may derive / determine the HARQ-ACK timing information of the PDSCH through the previous / former DCI.

[0401] The UE may receive a first DCI that schedules the PDSCH with a non-numerical K1 value. For the (non-enhanced) dynamic HARQ-ACK codebook, the UE may determine / derive the HARQ-ACK timing of the PDSCH scheduled with the non-numerical value K1 through a second DCI. The second DCI may schedule a second PDSCH with a numerical K1 value. The UE may receive the second DCI after the first DCI.

[0402] The base station may transmit a DCI that requests / triggers HARQ feedback for a HARQ-ACK codebook that contains one or more or all DL HARQ processes (e.g., a one-shot feedback request). The one-shot feedback request may be for one or more or all component carriers configured for the UE. The one-shot feedback may be configured separately from the HARQ-ACK codebook configuration. For example, the one-shot feedback may apply to a semi-static HARQ-ACK codebook and / or a (non-enhanced) dynamic HARQ-ACK codebook and / or an enhanced dynamic HARQ-ACK codebook.

[0403] The UE may transmit HARQ feedback for one or more PDSCHs in response to receiving the one-shot feedback request. The last / latest PDSCH for which an acknowledgement has been reported in response to receiving the one-shot feedback request may be determined as the last PDSCH within the UE's processing time capability (e.g., baseline capability, N1). The UE may report HARQ-ACK feedback for one or more earlier PDSCHs scheduled with a non-numerical K1 value. The one-shot feedback may be requested in a UE-specific DCI. The one-shot feedback may request reporting HARQ feedback in the PUCCH. The HARQ feedback may be piggybacked (e.g., appended) on the PUSCH.

[0404] The UE can be configured to monitor feedback requests for one-shot HARQ-ACK codebook feedback. The feedback can be requested in a DCI format (e.g., DCI format 1_1). The DCI format may or may not schedule a DL transmission (e.g., PDSCH). The DCI format can include a first field (e.g., frequency domain resource allocation field) indicating a first value. In response to the first field indicating the first value, the UE can determine that the DCI format does not schedule the PDSCH. The UE can ignore / discard one or more second fields (e.g., HARQ process number and / or NDI field) of the DCI format in response to this determination. The UE can be scheduled to report one-shot feedback and one or more other HARQ-ACK feedbacks in the same time slot / subframe / resource, and the UE can report only the one-shot feedback.

[0405] In a one-shot codebook, for each of one or more TBs, one or more NDI bits can follow one or more HARQ-ACK information bits. The HARQ-ACK information bits and the corresponding NDI can be sorted in the one-shot codebook as follows: first, in ascending order of CBG index; second, in ascending order of TB index; third, in ascending order of HARQ process ID; fourth, in ascending order of serving cell index.

[0406] The UE can be configured with one or more active SPS PDSCH configurations in DL.

[0407] In some embodiments, the wireless device and the base station must have a common understanding of the HARQ-ACK codebook size, which, for a semi-static codebook, depends on the number of timings of candidate PDSCH receptions on a set of downlink time slots associated with PUCCH transmissions on the active UL BWP. When there is a BWP switch, the parameter set (time slot duration) of the BWP can change, and / or one or more PDSCH-HARQ feedback timing values (K1) configured for the BWP can change, and / or the PDSCH time domain allocation associated with the PDSCH configuration of the BWP can change. For example, when there is a PDSCH reception with pending HARQ-ACK information, this can complicate the determination of the HARQ-ACK codebook size. Thus, in the prior art, the pending HARQ-ACK information is discarded and not considered in the HARQ-ACK codebook determination. For example, when the wireless device switches the BWP (e.g., DL BWP and / or UL BWP) after one or more PDSCH timings and / or SPS PDSCH releases and after / coinciding with the corresponding PUCCH / PUSCH time slot, the wireless device can discard / skip / not report / report the NACK of the HARQ-ACK information for one or more PDSCH timings and / or SPS PDSCH releases in the semi-static codebook.

[0408] In some embodiments, a wireless device may transmit HARQ-ACK for a PDSCH that is scheduled with a non-numerical K1 value via one-shot HARQ feedback. The wireless device may not include the HARQ-ACK for the PDSCH that is scheduled with a non-numerical K1 value in a semi-static codebook. The wireless device may include the HARQ-ACK for the PDSCH that is scheduled with a non-numerical K1 value in a semi-static codebook. With the semi-static codebook, the HARQ-ACK timing for the PDSCH scheduled with a non-numerical K1 value may be derived based on the next DL DCI that schedules the PDSCH with a numerical K1 value. The wireless device may report the HARQ-ACK in an additional bit container. With the dynamic codebook, the HARQ-ACK timing for the PDSCH scheduled with a DCI indicating a non-numerical K1 value may be derived based on the next DCI that schedules the PDSCH with a numerical K1 value. The wireless device may expect that the DAI is reset for a PDSCH that is transmitted later than N1 symbols before a PUCCH transmission.

[0409] The non-numerical value of K1 may be configured for a dynamic / semi-static codebook, an enhanced dynamic codebook, and / or a one-shot codebook. For the dynamic codebook, the HARQ-ACK timing for the PDSCH scheduled with a non-numerical value of K1 may be derived from the next DCI that schedules the PDSCH with a numerical K1 value. To complete the codebook design, the associated DAI values may be accumulated accordingly. For the semi-static codebook, the HARQ-ACK timing for the PDSCH scheduled with a non-numerical value of K1 may be derived from the DCI that schedules the PDSCH with a numerical K1 value. The valid HARQ-ACK for the PDSCH with a non-numerical value of K1 may be reported in the PUCCH / PUSCH according to the PDSCH time-domain resources, e.g., if the PDSCH is in a candidate PDSCH occasion of the PUCCH / PUSCH. For example, if the PDSCH is earlier than the first candidate PDSCH occasion, additional HARQ-ACK bits for the PDSCH may be appended to the semi-static codebook of the candidate PDSCH occasion. Considering that there is no auxiliary information in the semi-static codebook to identify misdetected PDSCHs outside the candidate PDSCH occasion, the reserved bits for the PDSCH with non-numerical K1 may always exist. The set of K1 may be configured according to the UL BWP instead of according to the DL CC. Reserved HARQ-ACK bits for the PDSCH with a non-numerical value of K1 may be added for each configured DL CC. In addition, to avoid any confusion about the "latest PDSCH with non-numerical K1", the base station may ensure that each DL CC has at most one additional PDSCH outside the candidate PDSCH occasion.

[0410] The serving cell may be configured with one or more BWPs. BWP switching for the serving cell can be used to activate an inactive BWP and deactivate the active BWP simultaneously. BWP switching can be controlled by a PDCCH indicating a downlink assignment and / or an uplink grant. BWP switching can be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). BWP switching can be controlled by RRC signaling. BWP switching can be controlled by the MAC entity itself when initiating a random access procedure. At the RRC (re)configuration of the first active DL BWP (e.g., firstActiveDownlinkBWP-Id) and / or the first active UL BWP (e.g., firstActiveUplinkBWP-Id) for the SpCell or an activated SCell, the DL BWP and / or the UL BWP indicated by firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id can be active respectively without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP for the serving cell can be indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP can be paired with the UL BWP, and the BWP switching of the DL BWP can change the paired UL BWP, and / or the BWP switching of the UL BWP can change the paired DL BWP.

[0411] The serving cell may be configured with a BWP inactivity timer (e.g., having a duration of 2 ms, 3 ms, …, or 1920 ms). The running BWP inactivity timer may expire. When the BWP inactivity timer expires, the wireless device may perform a BWP switch to the BWP indicated as the default DL BWP (if configured). When the BWP inactivity timer expires, the wireless device may perform a BWP switch to the BWP indicated as the initial DL BWP (e.g., if the default DL BWP is not configured). In response to receiving DCI via the PDCCH, the wireless device may perform a BWP switch to the BWP indicated by the DCI (e.g., switch the active DL BWP) via the PDCCH, where the DCI includes a BWP index. For example, when the wireless device switches the active DL BWP that is not indicated as the default DL BWP or the initial DL BWP, the wireless device may start / restart the BWP inactivity timer of the serving cell. In response to receiving scheduling DCI of the serving cell, the wireless device may start / restart the BWP inactivity timer of the serving cell, where the scheduling DCI includes a resource assignment for downlink or uplink data. In response to receiving scheduling DCI via the serving cell, the wireless device may start / restart the BWP inactivity timer of the serving cell, where the scheduling DCI includes a resource assignment for downlink / uplink data of the serving cell or another serving cell.

[0412] The wireless device may be configured with a semi-static codebook (e.g., a type 1 HARQ-ACK codebook). The wireless device may determine a set of candidate PDSCH reception and / or SPS PDSCH release timing for the serving cell c, the active downlink BWP, and the active uplink BWP. The wireless device may use the codebook in the uplink channel to transmit HARQ-ACK information for the candidate PDSCH reception and / or SPS PDSCH release. The uplink channel may be a PUCCH or a PUSCH. The position of the HARQ-ACK information in the type 1 HARQ-ACK codebook for a single SPS PDSCH release may be the same as that for the corresponding SPS PDSCH reception. The position of the HARQ-ACK information in the type-1 HARQ-ACK codebook for multiple SPS PDSCH releases indicated by a single DCI format may be the same as that for the corresponding SPS PDSCH reception with the lowest SPS configuration index among the multiple SPS PDSCH releases.

[0413] The wireless device may transmit HARQ-ACK information in slot n U . The wireless device may skip PDSCH timing and / or SPS release in the semi-static HARQ-ACK codebook. For example, when the scheduling slot for HARQ-ACK transmission coincides with the slot n in which the active DL BWP changesU Simultaneously or thereafter, e.g., when starting on serving cell c, the wireless device may skip PDSCH occasions and / or SPS releases. For example, when the scheduling time slot for HARQ-ACK transmission coincides with the time slot n in which the active UL BWP changes U Simultaneously or thereafter, e.g., when starting on the PCell, the wireless device may skip PDSCH occasions and / or SPS releases. For example, when corresponding to UL time slot n U when the DL time slot is before the time slot in which the active DL BWP changes on serving cell c, the wireless device may skip PDSCH occasions and / or SPS releases. For example, when corresponding to UL time slot n U when the DL time slot is before the time slot in which the active UL BWP changes on the PCell, the wireless device may skip PDSCH occasions and / or SPS releases.

[0414] Figure 18 Illustrates an example of signaling for the configuration, activation, transmission, and deactivation of SPS PDSCH according to some embodiments. The UE may receive RRC signaling that includes configuration parameters of the SPS PDSCH configuration, such as the periodicity l. The UE may receive DCI in time slot n indicating the activation of the SPS PDSCH configuration. The activation DCI may indicate parameters for scheduling SPS PDSCH occasions, such as the time offset m, and / or the corresponding PUCCH occasion for HARQ feedback transmission for the SPS PDSCH occasion, such as the timing offset k1. The UE may determine the first SPS PDSCH occasion in time slot n+m and may or may not receive the first PDSCH. The UE may determine the first PUCCH / PUSCH resource in time slot n+m+k1 to transmit the first HARQ feedback corresponding to the first SPS PDSCH occasion. The UE may determine the second SPS PDSCH occasion based on the periodicity in time slot n+m+l and may or may not receive the second PDSCH. The UE may determine the second PUCCH / PUSCH resource in time slot n+m+l+k1 to transmit the second HARQ feedback corresponding to the second SPS PDSCH occasion, and so on. The UE may receive a second DCI in time slot p indicating the deactivation / release of the SPS PDSCH configuration. Based on the scheduling of the SPS PDSCH configuration and the activation DCI, the UE may stop receiving DL data via the PDSCH. The active duration of the SPS PDSCH configuration may be from time slot n to time slot p.

[0415] The UE may receive a first DCI format (e.g., fallback DCI, DCI format 1_0) that activates the SPS PDSCH configuration. For example, when an enhanced dynamic codebook is configured, the UE may report HARQ-ACK feedback for the PDSCH occasion of the SPS PDSCH configuration as part of a first PDSCH group. The first PDSCH group may be predefined (e.g., group #0) and / or configured via RRC signaling.

[0416] The UE may receive a first DCI format (e.g., non-fallback DCI, DCI format 1_1) that activates the SPS PDSCH configuration. For example, when an enhanced dynamic codebook is configured, the UE may report HARQ-ACK feedback for the PDSCH occasion of the SPS PDSCH configuration as part of a PDSCH group indicated by the activating DCI (first DCI format).

[0417] The HARQ feedback corresponding to the SPS PDSCH may be requested / triggered one or more times, e.g., via an enhanced dynamic codebook and / or a one-shot feedback codebook. In the enhanced dynamic codebook, the SPS PDSCH may belong to a default PDSCH group (e.g., group #0). The UE may determine the NFI corresponding to the SPS PDSCH from the NFI indicated in a second DCI (e.g., the most recent DCI). For example, the second DCI may be a first DCI format (e.g., non-fallback DCI, DCI format 1_1) that schedules one or more PDSCHs of the same PDSCH group and / or triggers HARQ-ACK feedback for the same PDSCH group. For example, when HARQ-ACK feedback for a PDSCH group is requested / triggered, the UE may report one or more HARQ-ACK feedbacks corresponding to one or more SPS PDSCH occasions since the most recent transition corresponding to the NFI of the PDSCH group. The UE may append (e.g., piggyback) one or more HARQ-ACK bits corresponding to one or more SPS PDSCH occasions to the HARQ-ACK codebook of other DL transmissions (e.g., PDSCH dynamically scheduled via PDCCH) including the same PDSCH group.

[0418] In the enhanced dynamic codebook, the SPS PDSCH may not belong to any PDSCH group, e.g., a PDSCH group index / ID associated with the SPS PDSCH may not be defined. For example, when only one or more HARQ-ACK bits corresponding to the SPS PDSCH are scheduled in a slot of the PUCCH, the UE may use a first PUCCH format (e.g., PUCCH format 0 / 1) for HARQ feedback transmission. One-shot feedback may be used to retransmit one or more HARQ-ACK bits of the SPS PDSCH.

[0419] Other group-based HARQ-ACK bits may conflict with the HARQ-ACK bits corresponding to SPS PDSCH. The UE may multiplex all HARQ-ACK bits in one PUCCH and map the HARQ-ACK bits corresponding to SPS PDSCH to the end of the HARQ-ACK codebook. For example, when the multiplexed group-based HARQ-ACK is triggered for retransmission, the UE may retransmit the HARQ-ACK bits corresponding to SPS PDSCH.

[0420] The UE may not expect to receive a DL DCI that activates SPS PDSCH indicating a non-numerical K1 value.

[0421] The first PDSCH group index indicated in the first DCI that activates the SPS PDSCH configuration may be the same as the second PDSCH group index indicated in the second DCI that deactivates / releases the SPS PDSCH configuration.

[0422] The UE may append (e.g., piggyback) one or more HARQ feedback bits for one or more SPS PDSCH and / or one or more SPS releases at the end of the HARQ codebook. The one or more HARQ feedback bits may not belong to any PDSCH group defined by the enhanced dynamic codebook. The one or more HARQ feedback bits may not be retransmitted. If the UE receives a one-shot feedback request / trigger, the UE may retransmit the one or more HARQ feedback bits.

[0423] The UE may be configured with a semi-static HARQ-ACK codebook. For example, when the UE is configured with a non-numerical K1 value for at least one PUCCH configuration of the configured DL component carrier (e.g., included in the configuration of the higher layer parameter dl-DataToUL-ACK), the UE may append additional bits at the end of the HARQ-ACK bits of the corresponding DL component carrier in the semi-static HARQ-ACK codebook for each TB / CBG. For example, when the semi-static HARQ-ACK codebook includes the timing of the candidate PDSCH reception corresponding to the PDSCH scheduled with the non-numerical K1, the UE may use one or more bits of the semi-static HARQ-ACK codebook to report the HARQ-ACK value corresponding to the PDSCH scheduled with the non-numerical K1. For example, when the semi-static HARQ-ACK codebook does not include the timing of one or more PDSCHs, the UE may use the additional bits at the end of the semi-static HARQ-ACK codebook to report the HARQ-ACK feedback of the latest PDSCH of one or more PDSCHs scheduled with the non-numerical value K1. The UE may not expect to receive more than one PDSCH scheduled with the non-numerical K1 value for which the semi-static HARQ-ACK codebook may not include the bits / locations corresponding to the PDSCH. For example, if there is no PDSCH scheduled with the non-numerical K1 value to be reported in the semi-static HARQ-ACK codebook, the UE may report a NACK of one or more additional bits (e.g., per TB / CBG) at the end of the semi-static HARQ-ACK codebook. For example, when the non-numerical value K1 is not configured for any PUCCH configuration of the component carrier (e.g., not included in the configuration of the higher layer parameter dl-DataToUL-ACK) and the UE is configured with a semi-static HARQ-ACK codebook, the UE may not include any additional bits at the end of the semi-static HARQ-ACK codebook.

[0424] The UE may exclude one or more time slots other than the gNB-initiated COT from the DL association set that determines the semi-static HARQ-ACK codebook size.

[0425] In the prior art, for SPS configuration, the base station can indicate a numerical value or a reserved non-numerical value for the PDSCH to HARQ feedback timing for HARQ feedback transmission in the unlicensed band via the activation DCI of the SPS configuration or via RRC signaling. The non-numerical value indicates to the UE that the timing and resources for the HARQ-ACK feedback transmission for the corresponding PDSCH / PDCCH will be determined later. When the PDSCH to HARQ feedback timing is a numerical value, it directly indicates the UL channel for the HARQ-ACK feedback transmission, and the wireless device can attempt to transmit the HARQ-ACK feedback for each SPS occasion based on this numerical value. This may be inefficient in an unlicensed band and / or a TDD system, where the semi-static uplink transmission for SPS HARQ-ACK feedback may conflict / overlap with unavailable time resources (e.g., DL time slots / symbols based on the TDD UL-DL configuration and / or time slots requiring the LBT procedure where the LBT may fail). If the uplink transmission (e.g., PUCCH including SPS HARQ-ACK) conflicts with a symbol that cannot be used for uplink transmission, the wireless device may discard the uplink transmission. The wireless device may succeed or fail in LBTs, which may reduce the reliability of the HARQ-ACK feedback. For example, when the wireless device cannot transmit the HARQ-ACK feedback due to a conflict with DL / flexible symbols and / or LBT failure, the base station may not know whether the DL transmission has been successfully received and whether a retransmission is required, and thus may perform unnecessary retransmissions.

[0426] For example, due to the failure of the LBT, the base station may not transmit any PDSCH in one or more SPS occasions. In such a case, transmitting the HARQ-ACK feedback may not be beneficial. If the DL SPS is configured with a numerical timing value for HARQ feedback transmission, many instances of the corresponding UL channel (e.g., PUCCH) may happen to be outside the channel occupancy. It may require additional UL transmissions and / or LBT procedures with reduced success probability because the base station cannot reserve the UL channel for HARQ feedback transmission yet. This method may not be efficient and may lead to a reduction in the reliability of additional UL transmissions and a reduction in the possibility of accessing the UL channel.

[0427] Based on the prior art, if the PUCCH transmission conflicts with one or more symbols that cannot be used for uplink transmission, the wireless device may discard / not transmit the PUCCH including DL SPS HARQ-ACK. The one or more symbols may be DL symbols. The one or more symbols may be flexible symbols. For example, a semi-static TDD configuration (e.g., TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated) may indicate that the one or more symbols are DL symbols and / or flexible symbols. For example, DCI including Slot Format Indication (SFI) may indicate that the one or more symbols are DL symbols and / or flexible symbols. For PDSCH and corresponding PUCCH resources with dynamic scheduling for HARQ-ACK, the network can dynamically determine the time slots and symbols of the PUCCH so as to avoid conflicts with DL / flexible symbols. However, for SPS PDSCH with PUCCH resources having periodic and semi-static configurations, conflicts may be inevitable. In unpaired spectrum, DL reconfiguration and / or multiple SPS configurations may result in frequent discarding of SPS HARQ-ACK, which may waste resources, delay data communication, and degrade system performance. By avoiding the discarding of SPS HARQ-ACK for TDD due to conflicts between PUCCH and DL / flexible symbols, system performance can be enhanced.

[0428] In an example, the PUCCH resources can be scheduled by the digital PDSCH to HARQ feedback timing value for DL SPS configuration. The pre-configured / semi-static-configured / fixed feedback timing value may result in multiple separate PUCCH resources for transmitting multiple HARQ-ACK information, which may also be combined in a single PUCCH transmission. For example, the semi-static-configured PUCCH resources for SPS PDSCH occasions may not be effective uplink resources for the base station to schedule other HARQ-ACK information transmissions on the same PUCCH resources. For example, the PUCCH resources may not be within the COT duration. For example, the PUCCH resources may be scheduled only for HARQ-ACK information of SPS PDSCH occasions, rather than other HARQ-ACK information or any other uplink control information including CSI-report and / or SR. The base station may prefer to schedule a second PUCCH resource different from the PUCCH resources for SPS PDSCH for the dynamic scheduling of PDSCH HARQ-ACK transmissions. This may result in multiple / separate HARQ-ACK transmissions, which increases the UL overhead.

[0429] In the prior art, when a UE receives an SPS PDSCH after a first PDSCH, where the first PDSCH is scheduled / assigned in a corresponding first DCI format with an inapplicable feedback timing value, the UE may not transmit / multiplex the HARQ-ACK information of the first PDSCH in a PUCCH transmission scheduled for HARQ-ACK transmission of the SPS PDSCH. This means that even if the semi-static PUCCH resources for the SPS PDSCH already exist, it may not be an effective resource for transmitting other HARQ-ACK information. Therefore, if the HARQ-ACK information of the SPS PDSCH is quite important (e.g., some critical data is transmitted and / or is not a NACK), the semi-statically configured PUCCH resources may not be efficient / reliable for the transmission of the HARQ-ACK information of the SPS PDSCH.

[0430] On the other hand, if the DL SPS is configured with a non-numerical timing value for HARQ feedback transmission, this may lead to an increase in downlink (DCI) signaling and / or an increase in the waiting time in HARQ feedback transmission. For example, sometimes the UL channel (e.g., PUCCH) can be used for a corresponding PDSCH (e.g., the corresponding PDSCH is transmitted in a COT, and the resources of the UL channel are within the COT, or the resources of the UL channel do not overlap with DL / flexible symbols). For a fixed non-numerical value of HARQ-ACK feedback, even if the wireless device has uplink resources available for HARQ-ACK feedback, the wireless device may defer HARQ-ACK feedback transmission until it receives a DCI indicating a numerical timing value that schedules another UL channel. This method may not be effective or flexible.

[0431] It is necessary to avoid discarding the HARQ feedback transmission of the DL SPS (e.g., by dynamically and flexibly controlling its timing) due to, for example, the unavailability of UL resources and / or the special characteristics of traffic dynamics and communication (e.g., COT, channel access in an unlicensed band, and / or DL / flexible symbols in TDD operation). Embodiments may enable a wireless device to defer / postpone the HARQ feedback transmission of an SPS PDSCH occasion / reception in response to the unavailability of corresponding PUCCH resources (e.g., due to LBT failure and / or COT expiration and / or TDD DL / flexible conflict).

[0432] The prior art updates one or more parameters of SPS by transmitting DCI via SPS activation, thereby changing the PDSCH-to-HARQ feedback timing between a digital value and a non-digital value. For example, when the base station cannot acquire the channel, this method may be infeasible. In such an instance, the base station may not be able to transmit any DCI to the wireless device to adjust the timing of PDSCH-to-HARQ feedback. Additionally, this method requires a high DCI overhead to maintain the SPS configuration and may not scale with the number of SPS configurations.

[0433] Embodiments of the present disclosure achieve flexible control of the timing of HARQ feedback transmission for DL SPS in an unlicensed band without relying on SPS-activated DCI by determining the HARQ feedback timing value based on some criteria. For example, by enabling the wireless device to select between a first digital timing value and a second non-digital timing value or a third digital timing value based on, for example, second downlink control information or third downlink control information and / or channel occupancy timing. Embodiments of the present disclosure can reduce the waiting time in HARQ feedback transmission, and at the same time, can increase the likelihood of HARQ feedback transmission, and can also reduce the wireless device overhead for transmitting HARQ feedback for DL SPS.

[0434] In an example, the wireless device may adjust / temporarily adapt the second PDSCH-to-HARQ feedback timing of the SPS PDSCH / SPS occasion by using the first PDSCH-to-HARQ feedback timing of the previous or next DCI scheduling the PDSCH. For example, if the previous DCI scheduling the PDSCH close to the SPS PDSCH / SPS occasion indicates that the first PDSCH-to-HARQ feedback timing is a non-numerical value, the wireless device may apply this non-numerical value to the SPS PDSCH / SPS occasion to determine the second PDSCH-to-HARQ feedback timing. For example, if the previous DCI scheduling the PDSCH close to the SPS PDSCH / SPS occasion indicates, by means of the first PDSCH-to-HARQ feedback timing as a numerical value, a first UL channel (e.g., PUCCH) different from the second UL channel indicated by the second PDSCH-to-HARQ feedback timing of the SPS PDSCH / SPS occasion, the wireless device may override / discard the second UL channel and / or the second PDSCH-to-HARQ feedback timing for the SPS PDSCH / SPS occasion, and may use the first UL channel to transmit the HARQ-ACK feedback for the SPS PDSCH. In an example, the wireless device may receive a numerical value of the PDSCH-to-HARQ feedback timing configured for SPS. For an SPS-configured SPS PDSCH / SPS occasion, when the resource of the PUCCH carrying the HARQ-ACK feedback of the SPS PDSCH / SPS occasion belongs to the COT, the wireless device may apply the numerical value to the PDSCH-to-HARQ feedback timing (e.g., the wireless device may not need to perform Cat 4 LBT). For example, the COT may include an SPS PDSCH transmission. Otherwise, the wireless device may apply the non-numerical value to the PDSCH-to-HARQ feedback timing.

[0435] In an example, a wireless device may receive a numerical value of the PDSCH-to-HARQ feedback timing configured for SPS. The wireless device may determine that a resource of an uplink carrying HARQ-ACK feedback corresponding to the SPS PDSCH or SPS occasion belongs to the same channel occupancy time (COT) as the COT of the SPS PDSCH or SPS occasion, based on the PDSCH-to-HARQ feedback timing value. In response to this determination, the wireless device may transmit an uplink carrying the HARQ-ACK feedback corresponding to the SPS PDSCH. Otherwise, the wireless device may not transmit the HARQ-ACK feedback. For example, when the SPS PDSCH or SPS occasion does not belong to any COT, the wireless device may not transmit the HARQ-ACK feedback. For example, when the resource of the uplink determined based on the PDSCH-to-HARQ feedback timing belongs to a COT different from the COT of the SPS PDSCH or SPS occasion or may not belong to any COT, the wireless device may not transmit the HARQ-ACK feedback.

[0436] The wireless device may not transmit HARQ feedback of a DL transmission via a UL channel that is not within the same channel occupancy as the DL transmission. The wireless device may not transmit HARQ feedback of a DL transmission via a UL channel that is only scheduled for DL transmission.

[0437] According to an exemplary embodiment of the present disclosure, a UE may receive one or more RRC messages that include parameters of one or more semi-persistent scheduling (e.g., SPS PDSCH) configurations and / or one or more uplink control channel (e.g., PUCCH) configurations. The UE may determine PUCCH resources of one or more PUCCH configurations for HARQ feedback information for transmitting SPS PDSCH opportunities. For example, the UE may receive DCI that activates an SPS PDSCH configuration. For example, one or more RRC messages may indicate the periodicity of SPS PDSCH opportunities (e.g., 10 ms or 20 ms or 32 ms or... 640 ms) and / or the number of HARQ processes for data transmission (e.g., transport blocks). For example, parameters of one or more SPS configurations may indicate the periodicity of SPS PDSCH opportunities. The activating DCI may include scheduling information of the SPS PDSCH configuration. For example, the activating DCI may include one or more first fields indicating the time / frequency resources of the SPS PDSCH opportunity (e.g., offset and / or number of symbols / resource blocks), where the SPS PDSCH opportunity repeats in each period based on the indicated time / frequency resources. The activating DCI may further include one or more second fields that indicate UL resources for HARQ feedback transmission for the SPS PDSCH opportunity. For example, one or more second fields may include a PDSCH-to-HARQ feedback timing (e.g., K1) value. The K1 value may indicate the time offset from each SPS PDSCH opportunity in each period to the corresponding PUCCH resource for HARQ feedback transmission for that SPS PDSCH opportunity. For example, the time offset may be the number of slots / symbols / sub-frames. For example, the UE may apply the time offset indicated by the K1 value to the previous time instance (e.g., slot) of the SPS PDSCH opportunity (e.g., slot n) to determine the time instance of the PUCCH (e.g., slot n + K1). The UE may use one or more pre-configured information (e.g., PUCCH format and / or dl-DataToUL-ACK, etc.) and / or one or more information fields in the activating DCI (e.g., PUCCH resource indicator (PRI)) to determine the PUCCH resources in the PUCCH slot. The SPS PDSCH opportunity may correspond to any instance of the periodic SPS, such as at any period after activation and before deactivation.

[0438] The UE may receive DCI (e.g., DCI format 2_0), which includes one or more fields indicating COT structure information (e.g., COT length and / or remaining channel occupancy duration of the serving cell). For example, the UE may be configured / provided with one or more RRC parameters (e.g., CO-DurationPerCell-r16 and / or CO-DurationList-r16). The DCI may indicate the number of remaining symbols and / or time slots from the reception of the DCI (e.g., from the time slot where the DCI is received / detected) to the end of the COT. In an example, the UE may not be configured / provided with one or more RRC parameters (e.g., CO-DurationPerCell-r16 and / or CO-DurationList-r16). The UE may determine the end and / or remaining duration of the COT of the serving cell based on one or more time slot format indications in one or more DCI (e.g., DCI format 2_0). For example, one or more DCI may include one or more fields indicating one or more time slot format indications. For example, one or more time slot format indications (SFI) may indicate the time slot format of multiple symbols (e.g., UL or DL or flexible direction). For example, the remaining channel occupancy duration may be multiple time slots and / or symbols, starting from the time slot where the UE detects the DCI, and one or more SFI indicate / provide the corresponding time slot format.

[0439] The UE may determine that once configured and activated, the first SPS PDSCH occasion / instance of the first SPS PDSCH configuration (e.g., at the first period) overlaps with one or more symbols of one or more time slots of the first COT duration. For example, the BS may initiate the first COT by performing one or more LBT procedures indicating an idle / available channel. The UE may receive COT information, such as the remaining COT duration, via the detected DCI. The UE may determine one or more symbols of one or more time slots associated with the remaining COT duration. For example, according to the parameter set of the active DL BWP of the serving cell, the remaining COT duration may include one or more symbols of one or more time slots. The first SPS PDSCH occasion may include one or more first symbols. One or more first symbols may be indicated by one or more scheduling parameters in the SPS activation DCI, such as the time domain resource allocation (TDRA) field. The UE may determine that the first SPS PDSCH occasion is scheduled in the first COT, for example, by determining that one or more symbols of the first COT include at least one of / overlap with one or more symbols of the first SPS PDSCH occasion.

[0440] The UE may determine a first PUCCH resource associated with a first SPS PDSCH occasion. For example, the activation DCI may include a first HARQ feedback timing value, such as a K1 value. The K1 value may indicate the time offset from the first SPS PDSCH occasion to the first PUCCH resource / slot. For example, the time offset may include the number of slots and / or symbols and / or frames and / or subframes. For example, the time offset may be in milliseconds. The first PUCCH resource may include one or more second symbols. The UE may determine one or more second symbols of the first PUCCH resource based on one or more RRC configuration parameters (e.g., PPUCCH-Config, PUCCH-Resource, PUCCH-format0 / 1 / 2 / 3 / 4, dl-DataToUL-ACK, etc.) and / or one or more information fields of the activation DCI (e.g., PRI and / or PDSCH to HARQ feedback timing indicator (K1 value)).

[0441] The UE may determine that one or more second symbols of the first PUCCH resource associated with the first SPS PDSCH occasion overlap (e.g., partially or fully) with one or more symbols of one or more slots of the first COT duration. The first SPS PDSCH occasion may be scheduled in the first COT, e.g., may overlap with the first COT duration. The first PUCCH resource may be scheduled in the first COT, e.g., overlap with the first COT duration. The UE may transmit HARQ feedback information for the first SPS PDSCH occasion via the first PUCCH resource, e.g., in the same COT duration as the corresponding PDSCH. The UE may report an ACK (e.g., positive bit) of the HARQ feedback information of the successfully received / decoded data of the CBG / TB received via the first SPS PDSCH occasion. The UE may report a NACK (e.g., negative bit) of the HARQ feedback information of the unsuccessfully received / decoded data of the CBG / TB for the first SPS PDSCH occasion, e.g., the UE may not detect the PDSCH in the first SPS PDSCH occasion.

[0442] Figure 19Shows an example of SPS PDSCH and corresponding PUCCH resource scheduling according to some embodiments. A UE (wireless device) receives RRC signaling including DL SPS configuration and / or PUCCH configuration. The DL SPS configuration may include SPS PDSCH periodicity. The PUCCH configuration may include parameters indicating PUCCH resources, such as PUCCH-Config, PUCCH-Resource, PUCCH-format0 / 1 / 2 / 3 / 4, dl-DataToUL-ACK (a set of available K1 values), etc. The UE may receive a first DCI, such as an SPS activation DCI, which includes scheduling information for the SPS PDSCH and the corresponding PUCCH resources. The activation DCI includes a PDSCH to HARQ feedback timing K1 value (from a set of RRC-configured K1 values), which indicates a numerical value as the time offset from the SPS PDSCH to the corresponding PUCCH resource. The UE receives a second DCI indicating COT structure information (e.g., remaining COT duration). The UE determines that the SPS PDSCH occasion and the corresponding PUCCH resources indicated by the numerical value K1 value are within / overlap with the remaining COT duration (e.g., fully or partially overlap). The UE may or may not receive DL data via the SPS PDSCH occasion. The UE transmits HARQ feedback information regarding DL data reception in the SPS PDSCH occasion via the corresponding PUCCH resources.

[0443] The UE may determine a first PUCCH resource associated with a first SPS PDSCH occasion based at least on the K1 value in the activation DCI. The K1 value may be numerical. The UE may determine that one or more second symbols of the first PUCCH resource associated with the first SPS PDSCH occasion do not overlap (e.g., partially or fully overlap) with one or more symbols of one or more time slots of the first COT duration. The first SPS PDSCH occasion may be scheduled within / inside the first COT, e.g., may overlap with the first COT duration. The first PUCCH resource may be scheduled outside the first COT, e.g., overlapping with the first COT duration. The UE may transmit HARQ feedback information for the first SPS PDSCH occasion without using the first PUCCH resource, e.g., outside the COT duration of the SPS PDSCH.

[0444] Figure 20Shows an example of SPS PDSCH and corresponding PUCCH resource scheduling according to some embodiments. A UE (wireless device) receives RRC signaling including DL SPS configuration and / or PUCCH configuration. The UE may receive a first DCI, such as an SPS activation DCI, which includes scheduling information for the SPS PDSCH and the corresponding PUCCH resources. The activation DCI includes a PDSCH to HARQ feedback timing K1 value, which indicates a numerical value as the time offset from the SPS PDSCH to the corresponding PUCCH resource. The UE receives a second DCI indicating COT structure information (e.g., remaining COT duration). The UE determines that the SPS PDSCH occasion is scheduled / lies within and / or overlaps with (e.g., fully or partially overlaps) the remaining COT duration. The UE determines that the corresponding PUCCH resource indicated by the numerical K1 value is scheduled / lies outside the remaining COT duration, e.g., does not overlap with the COT duration. Because the COT duration expires before the PUCCH resource. The UE may or may not receive DL data via the SPS PDSCH occasion. The UE may transmit HARQ feedback information regarding the reception / detection of DL data in the SPS PDSCH occasion via the corresponding PUCCH resource outside the COT of the SPS PDSCH occasion.

[0445] For example, in response to determining that the PUCCH resource is not within the same COT as the corresponding SPS PDSCH occasion, the UE may discard the PUCCH resource indicated by the numerical K1 value in the SPS activation DCI. In response to determining that the corresponding PUCCH resource is not within the same COT as the SPS PDSCH occasion, the UE may discard the HARQ feedback information for the SPS PDSCH occasion. In response to determining that the HARQ feedback information includes an ACK (e.g., positive acknowledgment), the UE may transmit the HARQ feedback information for the SPS PDSCH occasion via the corresponding PUCCH resource that is not within the same COT as the SPS PDSCH occasion. In response to determining that the HARQ feedback information includes a NACK (e.g., negative acknowledgment), the UE may transmit the HARQ feedback information for the SPS PDSCH occasion via the corresponding PUCCH resource that is not within the same COT as the SPS PDSCH occasion.

[0446] For example, when the COT of the SPS PDSCH occasion expires before the corresponding PUCCH resource, the base station may determine an implicit ACK in response to not receiving HARQ feedback information via the scheduled PUCCH resource corresponding to the SPS PDSCH occasion. For example, when the COT of the SPS PDSCH occasion expires before the corresponding PUCCH resource, the base station may determine an implicit NACK in response to not receiving HARQ feedback information via the scheduled PUCCH resource corresponding to the SPS PDSCH occasion.

[0447] For example, in response to determining that the corresponding PUCCH resource is outside the COT including the SPS PDSCH occasion, the base station may not transmit DL data via the SPS PDSCH occasion. For example, in response to determining that the COT of the SPS PDSCH occasion expires before the corresponding PUCCH resource, the base station may not transmit DL data via the SPS PDSCH occasion. For example, in response to determining that the COT of the SPS PDSCH occasion expires before the corresponding PUCCH resource, the BS may schedule other transmissions that may overlap with the SPS PDSCH occasion. In response to determining that the COT of the SPS PDSCH occasion expires before the corresponding PUCCH resource, the BS may re-schedule the DL data corresponding to the SPS PDSCH occasion, for example, may transmit the DL data via a second PDSCH.

[0448] For example, in response to determining that the COT of the SPS PDSCH occasion expires before the corresponding PUCCH resource, the UE may not receive / detect DL data transmission via the SPS PDSCH occasion.

[0449] According to an exemplary embodiment of the present disclosure, a UE may receive one or more RRC messages, which include configuration parameters of one or more DL SPS configurations and / or one or more PUCCH configurations. One or more PUCCH resource configurations may indicate, for example, a set of available HARQ feedback timing values (one or more K1 values) via a parameter dl-DataToUL-ACK. The UE may receive a first DCI, such as an SPS activation DCI. The SPS activation DCI may schedule / indicate an SPS PDSCH occasion. The SPS activation DCI may include a first numerical HARQ feedback timing value (K1 value), which indicates a first PUCCH resource for transmitting HARQ feedback corresponding to the SPS PDSCH occasion. The UE may receive one or more DL DCIs that schedule one or more DL transmissions, such as one or more first PDSCHs. One or more DL DCIs may include one or more second HARQ feedback timing values (K1 values). One or more second HARQ feedback timing values may be numerical values. One or more second HARQ feedback timing values may indicate the first PUCCH resource. The UE may be scheduled / configured to transmit one or more uplink control information (UCI) via the first PUCCH resource. For example, the UE may be configured via RRC to have one or more semi-static (e.g., periodic) transmissions of a scheduling request (SR). For example, the UE may transmit one or more SR information via the first PUCCH resource. For example, the UE may transmit one or more CSI reports (e.g., semi-persistent CSI reports and / or periodic / aperiodic CSI reports) via the first PUCCH resource. The UE may transmit a HARQ-ACK codebook via the first PUCCH resource. The HARQ-ACK codebook may include HARQ feedback information for the SPS PDSCH occasion and / or HARQ feedback information for one or more first PDSCHs scheduled via one or more DL DCIs and / or HARQ feedback information for one or more SPS release PDCCHs. The UE may multiplex HARQ-ACK information (e.g., the HARQ-ACK codebook) and / or one or more SR information bits and / or one or more CSI reports in the first PUCCH resource.

[0450] Figure 21Shows an example of SPS PDSCH and corresponding PUCCH resource scheduling according to some embodiments. A UE (wireless device) receives RRC signaling including DL SPS configuration and / or PUCCH configuration. The DL SPS configuration may include SPS PDSCH periodicity. The PUCCH configuration may include parameters indicating PUCCH resources, such as PUCCH-Config, PUCCH-Resource, PUCCH-format0 / 1 / 2 / 3 / 4, dl-DataToUL-ACK (set of available K1 values), etc. The UE may receive a first DCI, such as an SPS activation DCI, which includes scheduling information for the SPS PDSCH and the corresponding PUCCH resource. The SPS activation DCI may schedule an SPS PDSCH occasion. The SPS activation DCI may include a first PDSCH to HARQ feedback timing K1-SPS value (set from the RRC configuration of K1 values), which indicates a numerical value as the time offset from the SPS PDSCH to the corresponding PUCCH resource (e.g., the first PUCCH resource). The UE receives a second DCI, such as DL DCI-1, which schedules a first PDSCH, such as PDSCH-1. DL DCI-1 may indicate a second PDSCH to HARQ feedback timing K1-1 value (set from the RRC configuration of K1 values), which indicates a numerical value as the time offset from PDSCH-1 to the first PUCCH resource. The UE receives a third DCI, such as DL DCI-2, which schedules a second PDSCH, such as PDSCH-2. DL DCI-2 may indicate a third PDSCH to HARQ feedback timing K1-2 value (set from the RRC configuration of K1 values), which indicates a numerical value as the time offset from PDSCH-2 to the first PUCCH resource. The UE may transmit HARQ feedback information for the SPS PDSCH occasion and / or PDSCH-1 and / or PDSCH-2 via the first PUCCH resource.

[0451] Figure 22Shows an example of SPS PDSCH and corresponding PUCCH resource scheduling according to some embodiments. A UE (wireless device) receives RRC signaling including DL SPS configuration and / or PUCCH configuration. The UE may receive a first DCI, such as an SPS activation DCI, which includes scheduling information for the SPS PDSCH and the corresponding PUCCH resources. The SPS activation DCI may schedule an SPS PDSCH occasion. The SPS activation DCI may include a first PDSCH to HARQ feedback timing K1-SPS value (from a set of RRC-configured K1 values), which indicates a numerical value as the time offset from the SPS PDSCH occasion to the corresponding PUCCH resource (e.g., PUCCH-SPS). The UE receives a second DCI, such as a DL DCI-1, which schedules a first PDSCH, such as PDSCH-1. The DL DCI-1 may indicate a second PDSCH to HARQ feedback timing K1-1 value (from a set of RRC-configured K1 values), which indicates a second numerical value as the time offset from PDSCH-1 to a second PUCCH resource (e.g., PUCCH-1). The UE receives a third DCI, such as a DL DCI-2, which schedu...

Claims

1. A method for transmitting feedback information, which comprises: receiving, by a wireless device (106), a semi-persistent scheduled downlink channel from a base station (160), wherein the downlink channel is associated with a first uplink control channel indicated by the feedback timing parameter of the semi-persistent scheduling; determining, based on at least one symbol of the first uplink control channel, that the first uplink control channel is not available for transmitting feedback information of the downlink channel; determining a second uplink control channel after the first uplink control channel, wherein the second uplink control channel is available for the transmission; and transmitting, via the second uplink control channel, feedback information multiplexed in the second uplink control channel.

2. The method for transmitting feedback information according to claim 1, further comprising receiving one of the following: downlink control information (DCI) indicating the second uplink control channel; or a radio resource control (RRC) message indicating the second uplink control channel, wherein the second uplink control channel is associated with the semi-persistent scheduling, and the semi-persistent scheduling is associated with the downlink channel.

3. The method for transmitting feedback information according to claim 1, which further comprises: receiving an RRC message, the RRC message including a configuration parameter indicating the transmission direction of a plurality of symbols including the at least one symbol, wherein the transmission direction of the symbol is uplink or downlink or undetermined.

4. The method for transmitting feedback information according to claim 3, wherein the determining step based on the at least one symbol further comprises: determining, based on the configuration parameter, that the transmission direction of the at least one symbol of the radio resource allocated to the first uplink control channel is downlink.

5. The method for transmitting feedback information according to claim 3, which further comprises: determining, based on a configuration parameter, that the transmission direction of the symbols of the radio resource allocated to the second uplink control channel is uplink or flexible.

6. A wireless device, the wireless device includes one or more processors and a memory storing instructions, the instructions when executed by the one or more processors cause the wireless device to execute the method for transmitting feedback information according to any one of claims 1 to 5.

7. A non-transitory computer-readable medium including instructions, the instructions when executed by one or more processors cause the one or more processors to execute the method for transmitting feedback information according to any one of claims 1 to 5.

8. A method for receiving feedback information, which comprises: transmitting, by a base station (160), a semi-persistent scheduled downlink channel to a wireless device (106), wherein the downlink channel is associated with a first uplink control channel indicated by the feedback timing parameter of the semi-persistent scheduling; determining, based on at least one symbol of the first uplink control channel, that the first uplink control channel is not available for transmitting feedback information of the downlink channel; and Receiving, from the wireless device, feedback information multiplexed in the second uplink control channel, where the second uplink control channel is determined by the wireless device to be after the first uplink control channel, and where the second uplink control channel is available for the transmission.

9. The method for receiving feedback information according to claim 8, further comprising transmitting one of the following: Downlink control information (DCI) indicating the second uplink control channel; or A radio resource control (RRC) message indicating the second uplink control channel, where the second uplink control channel is associated with the semi-persistent scheduling, and the semi-persistent scheduling is associated with the downlink channel.

10. The method for receiving feedback information according to claim 8, further comprising: Receiving an RRC message, the RRC message including a configuration parameter indicating the transmission direction of a plurality of symbols including the at least one symbol, where the transmission direction of the symbol is uplink or downlink or undetermined.

11. The method for receiving feedback information according to claim 10, where the determining step based on the at least one symbol further comprises: Determining that the transmission direction of the at least one symbol of the radio resources allocated to the first uplink control channel is downlink based on the configuration parameter.

12. The method for receiving feedback information according to claim 10, further comprising: Determining that the transmission direction of the symbols of the radio resources allocated to the second uplink control channel is uplink or flexible based on the configuration parameter.

13. A base station, the base station comprising one or more processors and a memory storing instructions, the instructions when executed by the one or more processors cause the base station to perform the method for receiving feedback information according to any one of claims 8 to 12.

14. A non-transitory computer-readable medium including instructions, the instructions when executed by one or more processors cause the one or more processors to perform the method for receiving feedback information according to any one of claims 8 to 12.

15. A system for providing feedback information, comprising: A base station (160), the base station comprising one or more first processors and a first memory storing first instructions, the first instructions when executed by the one or more first processors cause the base station to perform: Transmitting a downlink channel of semi-persistent scheduling, where the downlink channel is associated with a first uplink control channel indicated by the feedback timing parameter of the semi-persistent scheduling; and A wireless device (106), the wireless device comprising: one or more second processors and a second memory storing instructions, the instructions when executed by the one or more second processors cause the wireless device to perform: Receiving the downlink channel of semi-persistent scheduling from the base station; Based on at least one symbol of the first uplink control channel, determine that the first uplink control channel is not available for transmitting feedback information of the downlink channel; Determine a second uplink control channel after the first uplink control channel, wherein the second uplink control channel is available for the transmission; and Transmit the feedback information multiplexed in the second uplink control channel via the second uplink control channel.

Images