Uplink transmission in new radio unlicensed band

Abstract

To improve indexing of a subset of CCEs within an RB set.SOLUTION: A wireless device receives configuration parameters of a bandwidth part comprising resource block (RB) sets, where control channel elements (CCEs) are across the RB sets and a subset of the CCEs, within each RB set of the RB sets, are indexed from a same initial value. Control information is received via one or more CCEs of a first subset, of the CCEs, within an RB set of the RB sets. The wireless device transmits a signal via an uplink resource based on an index of a CCE of the one or more CCEs.SELECTED DRAWING: Figure 28

Description

Background Art

[0001] Cross - reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 62 / 930,130, filed on November 4, 2019, which is hereby incorporated by reference in its entirety.

Summary of the Invention

Means for Solving the Problems

[0002] 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 releases of the same technology. A wireless device can have some specific capabilities depending on the category and / or capabilities of the wireless device. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure can refer to a subset of all wireless devices within a coverage area. This disclosure can refer to, for example, multiple wireless devices of a given LTE or 5G release that include a given capability and are in a given sector of the base station. The multiple wireless devices in this disclosure can refer to a selected multiple wireless devices and / or a subset of all wireless devices within a coverage area that are executed according to, for example, the disclosed method. There can be multiple base stations or multiple wireless devices in a coverage area that do not conform to the disclosed method. For example, those wireless devices or base stations are executed based on an older release of LTE or 5G technology.

Brief Description of the Drawings

[0003] Some examples of some embodiments of this disclosure are described herein with reference to the drawings.

[0004]

Figure 1

[0005]

Figure 2

[0006]

Figure 3

[0007]

Figure 4

[0008] Figure 4B shows an example of the format of the MAC sub-header in the MAC PDU.

[0009]

Figure 5

[0010]

Figure 6

[0011]

Figure 7

[0012]

Figure 8

[0013]

Figure 9

[0014]

Figure 10

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

[0016]

Figure 11

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

[0018]

Figure 12

[0019]

Figure 13

[0020]

Figure 14

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

[0022]

Figure 15

[0023]

Figure 16

[0024]

Figure 17

[0025]

Figure 18

[0026] Figure 18B shows an example of a UL MAC PDU.

[0027]

Figure 19

[0028]

Figure 20

[0029]

Figure 21

[0030]

Figure 22

[0031]

Figure 23

[0032]

Figure 24

[0033]

Figure 25

[0034] Figure 25B shows an example of PUCCH resource determination according to one aspect of the exemplary embodiments of the present disclosure.

[0035]

Figure 26

[0036]

Figure 27

[0037] Figure 27B shows an example of CORESET configuration in an NR-U system according to an aspect of the exemplary embodiments of the present disclosure.

[0038]

Figure 28

[0039]

Figure 29

[0040]

Figure 30

[0041]

Figure 31

[0042]

Figure 32

[0043]

Figure 33

[0044]

Figure 34

DETAILED DESCRIPTION OF THE INVENTION

[0045] In the present disclosure, various embodiments are presented as examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made without departing from the scope. Indeed, after reading the specification, methods of implementing alternative embodiments will become apparent to those skilled in the relevant art. The present embodiments should not be limited by any of the exemplary embodiments. Embodiments of the present disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of the present disclosure. Figures highlighting functions and advantages are shown for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, any action listed in any flowchart can be rearranged or used only as an option in some embodiments.

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

[0047] As used herein, the terms "a" and "an" and similar phrases are to be construed as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" should be construed as "at least one" and "one or more". As used herein, the term "may" is construed as "for example, may be". In other words, the term "may" indicates that the phrase following the term "may" is one example of a plurality of appropriate possibilities and may or may not be used by one or more of the various embodiments. As used herein, the terms "comprises" and "consists of" enumerate one or more components of the recited element. The term "comprises" is interchangeable with "includes" and does not exclude unrecited components included in the recited element. In contrast, "consists of" provides a complete enumeration of one or more components of the recited element. As used herein, the term "based on" should be construed as "at least in part based on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the recited elements. For example, "A, B, and / or C" may represent A, B, C, A and B, A and C, B and C, or A, B, and C.

[0048] If A and B are sets and all elements of A are also elements 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 = {cell 1, cell 2} are {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates one example of a number of suitable possibilities where the phrase following "based on" may or may not be used in one or more of the various embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates one example of a number of suitable possibilities where the phrase following "in response to" may or may not be used in one or more of the various embodiments. The phrase "in accordance with" (or equivalently "at least in accordance with") indicates one example of a number of suitable possibilities where the phrase following "in accordance with" may or may not be used in one or more of the various embodiments. The phrase "employed / used" (or equivalently "at least employed / used") indicates one example of a number of appropriate possibilities where the phrase following "employed / used" may or may not be used in one or more of the various embodiments.

[0049] The term "comprising" can relate to the capacity of a device, regardless of whether the device is in an operating state or a non-operating state. "Comprising" can also refer to specific settings of a device that affect the operating characteristics of the device, regardless of 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, regardless of whether the device is in an operating state or a non-operating state. Terms such as "control messages generated in a device" can mean that, regardless of whether the device is in an operating state or a non-operating state, the control messages can be used to configure specific characteristics in the device or can have parameters that can be used to implement specific actions in the device.

[0050] In the present disclosure, a parameter (or equivalently a field, or an information element: IE for short) 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, 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 among the plurality of parameters, the parameters are included in at least one of the one or more messages, but do not necessarily need to be included in each of the one or more messages.

[0051] Furthermore, many of the features presented above are described as being optional, either by the use of "may" or the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly describe every possible variation that could be obtained by selecting from the set of optional features. The present disclosure should be construed as disclosing all such variations explicitly. For example, a system described as having three optional features can be implemented in seven ways, namely, by only one of the three possible features, by any two of the three features, or by all three of the three features.

[0052] Many of the elements described in the disclosed embodiments can be implemented as modules. Here, a module is defined as an element that performs a defined function and has a defined interface to other elements. The modules described in the present disclosure may be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware having biological elements), or combinations thereof, which can be behaviorally equivalent. For example, a module can be implemented as a software routine described in a computer language configured to be executed on a hardware machine (such as C, C++, Fortran, Java®, Basic, Matlab, etc.) or in Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It may also be possible to implement a module 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), 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 a hardware description language (HDL) such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between internal hardware modules with fewer programmable device functions. To achieve the results of functional modules, the above techniques are often used in combination.

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

[0054] CN 102 can 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 device 106. As part of the interface function, CN 102 can set up an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide a charging function.

[0055] RAN 104 can connect CN 102 to the wireless device 106 via wireless communication on the air interface. As part of the wireless communication, RAN 104 can provide scheduling, radio resource management, and a retransmission protocol. The communication direction from RAN 104 to the wireless device 106 on the air interface is known as the downlink, and the communication direction from the wireless device 106 to RAN 104 on the air interface is known as the uplink. Downlink transmission can be separated from uplink transmission using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0056] The term "wireless device" is used throughout this disclosure to refer to and include any mobile or fixed (non-portable) device for which wireless communication is required or available. 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" includes other terms including, but not limited to, user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit / receive unit (WTRU), and / or wireless communication device.

[0057] RAN104 may include one or more base stations (not shown). The term "base station" can refer to and include, throughout this disclosure, 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), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, next-generation evolved Node B (ng-eNB), gNode B (gNB, associated with NR and / or 5G standards), access point (AP, e.g., associated with WiFi or other suitable wireless communication standards), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

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

[0059] In addition to the three-sector site, other implementations of the base station are possible. For example, one or more base stations of RAN104 may be implemented as a sector site having more than three or less than three sectors. One or more base stations of RAN104 may be implemented as an access point, as a baseband processing unit coupled to a plurality of remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. The baseband processing unit coupled to the RRH may be part of a centralized or cloud RAN architecture, and the baseband processing unit may be centralized within a pool of baseband processing units or may be virtualized. A repeater node may amplify and rebroadcast a wireless signal received from a donor node. A relay node may perform the same / similar functions as a repeater node, but may decode the wireless signal received from the donor node and remove noise before amplifying and rebroadcasting the wireless signal.

[0060] RAN104 can be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high-level transmission powers. RAN104 can be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, for example, coverage areas that overlap with the relatively large coverage areas provided by macrocell base stations. The 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 include microcell base stations, picocell base stations, and femtocell base stations or home base stations, in order of decreasing coverage area.

[0061] The Third Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of the specifications of mobile communication networks similar to the mobile communication network 100 of FIG. 1A. To date, 3GPP has produced the specifications for three generations of mobile networks: the third generation (3G) network known as the Universal Mobile Telecommunications System (UMTS), the fourth generation (4G) network known as Long-Term Evolution (LTE), and the fifth generation (5G) network known as the 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of the 3GPP 5G network, called the Next Generation RAN (NG-RAN). The embodiments may be applicable to the RANs of other mobile communication networks such as RAN104 of FIG. 1A, the RANs of previous 3G and 4G networks, and future networks not yet specified (e.g., 3GPP 6G networks). NG-RAN implements the 5G radio access technology known as New Radio (NR) and can be supplied to implement other radio access technologies including 4G radio access technology or non-3GPP radio access technology.

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

[0063] The 5G-CN 152 provides an interface for the UEs 156 to one or more DNs 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 can set up an end-to-end connection between the UEs 156 and one or more DNs, authenticate the UEs 156, and provide a charging function. Compared with the CN of the 3GPP 4G network, the base of the 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting the 5G-CN 152 can be defined as a network function that provides services via an interface to other network functions. The network functions of the 5G-CN 152 can be implemented in several ways, as network elements on dedicated or shared hardware, as software instances operating on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0064] As shown in FIG. 1B, 5G-CN152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which, for simplicity of explanation, are shown as a single component AMF / UPF158 in FIG. 1B. UPF158B may function as a gateway between NG-RAN154 and one or more DNs. UPF158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, reporting of traffic usage, uplink classification to support routing of traffic flows to 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. UPF158B may function as an anchor point for intra / inter radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branching point to support multi-home PDU sessions. UE156 may be configured to receive services via a PDU session, which is a logical connection between the UE and a DN.

[0065] AMF158A may perform functions such as termination of non-access stratum (NAS) signaling, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policy), support for network slicing, and / or selection of a Session Management Function (SMF). NAS may refer to functions operating between the CN and the UE, and AS may refer to functions operating between the UE and the RAN.

[0066] 5G-CN152 may include one or more additional network functions not shown in Figure 1B for clarity. For example, 5G-CN152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).

[0067] NG-RAN154 may connect 5G-CN 152 to UE156 via wireless communication on the air interface. NG-RAN154 may include one or more gNBs (collectively gNBs160) illustrated as gNB160A and gNB160B and / or one or more ng-eNBs (collectively ng-eNBs162) illustrated as ng-eNB162A and ng-eNB162B. gNBs160 and ng-eNBs162 may be more generally referred to as base stations. gNB160 and ng-eNB162 may include one or more sets of antennas for communicating with UE156 on the air interface. For example, one or more of gNB160 and / or one or more of ng-eNB162 may include three sets of antennas for controlling three cells (or sectors) respectively. Collectively, the cells of gNBs160 and ng-eNBs162 may provide wireless coverage to UE156 over a wide geographical area to support UE mobility.

[0068] As shown in FIG. 1B, gNB 160 and / or ng-eNB 162 may be connected to 5G-CN 152 via the NG interface and may be connected to other base stations via the Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network such as an Internet Protocol (IP) transport network. gNBs 160 and / or ng-eNBs 162 may be connected to UE 156 via the Uu interface. For example, as shown in FIG. 1B, gNB 160A may 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 may be used by the network elements in FIG. 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data of interest to the user. The control plane may process signaling messages of interest to the network elements.

[0069] gNB 160 and / or ng-eNB 162 may 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 may be connected to UPF 158B of AMF / UPF 158 via the NG user plane (NG-U) interface. The NG-U interface may provide the supply of user plane PDUs between gNB 160A and UPF 158B (e.g., non-guaranteed supply). gNB 160A can be connected to AMF 158A using the NG control plane (NG-C) interface. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, NAS message transfer, paging, PDU session management and configuration transfer and / or transmission of warning messages.

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

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

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

[0073] Figures 2A and 2B respectively show examples of the NR user plane and NR control plane protocol stacks for the Uu interface between UE210 and gNB220. The protocol stacks shown in Figures 2A and 2B may be the same as or similar to those used for the Uu interface between UE156A and gNB160A shown in Figure 1B.

[0074] Figure 2A shows an NR user plane protocol stack including five layers implemented in UE210 and gNB220. At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 may provide a transport service to the upper layers of the protocol stack and may correspond to layer 1 of the Open System Interconnection (OSI) model. The next four protocols above PHY211 and 221 include the media access control layers (MAC) 212 and 222, the radio link control layers (RLC) 213 and 223, the packet data convergence protocol layers (PDCP) 214 and 224, and the service data application protocol layers (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0075] FIG. 3 shows an example of services provided between protocol layers of an NR user plane protocol stack. Starting from the top of FIGS. 2A and 3, SDAPs 215 and 225 may perform QoS flow processing. UE 210 may receive services via a PDU session, which may be a logical connection between UE 210 and the DN. The PDU session may have one or more QoS flows. The CN's UPF (e.g., UPF 158B) may map IP packets to one or more QoS flows of the PDU session based on QoS requirements (e.g., regarding latency, data rate, and / or error rate). SDAPs 215 and 225 may perform mapping / demapping between one or more QoS flows and one or more data radio bearers. The mapping / demapping between the QoS flow and the data radio bearer may be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 may be notified of the mapping between the QoS flow and the data radio bearer via reflected mapping or control signaling received from gNB 220. For reflected mapping, SDAP 225 at gNB 220 may mark downlink packets with a QoS flow indicator (QFI) that can be observed by SDAP 215 of UE 210 to determine the mapping / demapping between the QoS flow and the data radio bearer.

[0076] PDCP214 and PDCP224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of the data transmitted over the air interface, and integrity protection (to ensure that control messages are sent from the intended source). PDCP214 and 224 may perform, for example, retransmission of unsent packets, in-sequence delivery and rearrangement of packets, and removal of duplicate packets received for gNB-internal handover. PDCP214 and 224 may perform packet duplication to improve the likelihood of received packets and to remove any duplicate packets at the receiver. Packet duplication may be useful for services that require high reliability.

[0077] Although not shown in Figure 3, PDCP214 and 224 may perform mapping / demapping between split radio bearers and RLC channels in a dual-connectivity scenario. Dual connectivity is a technology that enables a UE to connect to two cells, or more generally, two cell groups of a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one provided by PDCP214 and 224 as a service to SDAP215 and 225, is processed by cell groups in a dual-connectivity. PDCP214 and 224 may map / demap a split radio bearer between RLC channels belonging to a cell group.

[0078] RLC 213 and 223 can each perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222. 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 indicated functions. This RLC configuration can be per logical channel without depending on numerology and / or transmission time interval (TTI) duration. As shown in Figure 3, RLC 213 and 223 can each provide an RLC channel as a service to PDCP 214 and 224.

[0079] MAC212 and MAC222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from PHY211 and 221. MAC222 may be configured to perform scheduling, scheduling information reporting, and prioritization among UEs by dynamic scheduling. Scheduling may be performed at gNB220 (at MAC222) for downlink and uplink. MAC212 and 222 may be configured to perform error correction, prioritization among the logical channels of UE210 by logical channel prioritization, and / or padding through hybrid automatic repeat request (HARQ) (e.g., for carrier aggregation (CA), one HARQ entity per carrier). MAC212 and MAC222 may support one or more numerologies and / or transmission timings. In one embodiment, the mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As shown in Figure 3, MAC212 and 222 may provide logical channels to RLC213 and 223 as a service.

[0080] PHY211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions to transmit and receive information on the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY211 and 221 may perform multi-antenna mapping. As shown in Figure 3, PHY211 and 221 may provide one or more transport channels to MAC212 and 222 as a service.

[0081] FIG. 4A shows an example of downlink data flow through the NR user plane protocol stack. FIG. 4A shows the downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, and generates two TBs at gNB 220. The uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in FIG. 4A.

[0082] The downlink data flow in FIG. 4A starts when SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to the radio bearers. In FIG. 4A, SDAP 225 maps IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. An SDAP header (labeled "H" in FIG. 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 from / to lower protocol layers are called protocol data units (PDUs) of higher protocol layers. As shown in FIG. 4A, the data unit from AP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0083] The remaining protocol layers in FIG. 4A can perform related functions (e.g., with respect to FIG. 3), add corresponding headers, and transfer each output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption and transfer its output to RLC 223. RLC 223 can optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and transfer its output to MAC 222. MAC 222 may multiplex several RLC PDUs and attach a MAC sub-header to the RLC PDU to form a transport block. In NR, as shown in FIG. 4A, the MAC sub-header can be distributed over the entire MAC PDU. In LTE, the MAC sub-header can be placed entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and related latency because the MAC PDU sub-header can be calculated before the complete MAC PDU is assembled.

[0084] FIG. 4B shows an example format of the MAC sub-header in the MAC PDU. The MAC sub-header includes an SDU length field for indicating the length of the MAC SDU (such as in bytes) corresponding to the MAC sub-header, a logical channel identifier (LCD) field for identifying the logical channel from which the MAC SDU started to assist in the demultiplexing process, a flag (F) field for indicating the size of the SDU length field, and a reserved bit (R) field for future use.

[0085] Figure 4B further shows MAC control elements (CEs) inserted into the MAC PDU by a MAC such as MAC223 or MAC222. For example, Figure 4B shows two MAC CEs inserted into the MAC PDU. The MAC CE can be inserted at the start of the MAC PDU for downlink transmission (as shown in Figure 4B) and at the end of the MAC PDU for uplink transmission. The MAC CE can be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs such as buffer status reports and power headroom reports, activation / deactivation of PDCP duplication detection, channel state information (CSI) reports, sounding reference signal (SRS) transmission, and activation / deactivation MAC CEs for pre-configured components, discontinuous reception (DRX)-related MAC CEs, timing advance MAC CEs, and random access-related MAC CEs. The MAC CE may be preceded by a MAC sub-header in a format similar to that described for the MAC SDU and can be identified by a reserved value in an LCID field indicating the type of control information contained in the MAC CE.

[0086] Before describing the NR control plane protocol stack, the logical channels, transport channels, and physical channels, as well as the mapping between channel types, are first described. One or more channels can be used to perform functions related to the NR control plane protocol stack described below.

[0087] Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels for the downlink and uplink, respectively. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels that convey control and configuration information within the NR control plane or as traffic channels that convey data within the NR user plane. Logical channels can be classified as dedicated logical channels specific to a particular UE or as common logical channels that can be used by multiple UEs. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, - A paging control channel (PCCH) for displaying paging messages used to page UEs whose location is not known to the network at the cell level, and - A broadcast control channel (BCCH) for transmitting system information messages in the form of a master information block (MIB) and some system information blocks (SIBs), where the system information messages can be used by the UE to obtain information about how the cell is configured and how it operates within the cell, - A common control channel (CCCH) for transmitting control messages along with random access, and - A dedicated control channel (DCCH) for transmitting control messages between the MAC layer and the PHY layer, and - A dedicated traffic channel (DTCH) for transmitting user data between a particular UE and the network.

[0088] 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, - A paging channel (PCH) for transmitting paging messages sent from the PCCH, - A broadcast channel (BCH) for carrying the MIB from the BCCH, - A downlink shared channel (DL-SCH) for transmitting downlink data and signaling messages including the SIB from the BCCH - An uplink shared channel (UL-SCH) for transmitting uplink data and signaling messages, - A random access channel (RACH) that enables the UE to connect to the network without prior scheduling.

[0089] The PHY can pass information between processing levels of the PHY using physical channels. A physical channel can have a related set of time-frequency resources for carrying information of one or more transport channels. The PHY can generate control information to support the low-level operation of the PHY and provide control information to the low level of the PHY via a physical control channel known as the L1 / L2 control channel. The set of physical channels and physical control channels defined by NR is, for example, - A physical broadcast channel (PBCH) for carrying the MIB from the BCH, - A physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH, - A physical downlink control channel (PDCCH) for carrying downlink control information (DCI) that may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands, - A physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and, in some examples, uplink control information (UCI) as described below, - A physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgement responses, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR), and - A physical random access channel (PRACH) for random access, are included.

[0090] Similar to physical control channels, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in FIGS. 5A and 5B, the physical layer signals defined by NR include primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMSR), sounding reference signals (SRS), and phase tracking reference signals (PT-RS). These physical layer signals are described in more detail below.

[0091] FIG. 2B shows an example of the NR control plane protocol stack. In FIG. 2B, the NR control plane protocol stack may use the same / first four protocol layers similar to those of the NR user plane protocol stack example. These four protocol layers include PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224. Instead of having SDAP215 and 225 at the top of the stack like the NR user plane protocol stack, the NR control plane 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.

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

[0093] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220, or more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages called RRC messages. RRC messages may be sent between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data within the same transport block (TB). The RRCs 216 and 226 can provide control plane functions including broadcast 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 the UE 210 and the RAN, security functions including key management, establishment, configuration, maintenance, and release of signaling and data radio bearers, mobility functions, QoS management functions, UE measurement report and report control, detection and recovery of radio link failure (RLF), and / or NAS message transfer. As part of the establishment of the RRC connection, the RRCs 216 and 226 may establish an RRC context, which may involve setting parameters for communication between the UE 210 and the RAN.

[0094] FIG. 6 is an exemplary diagram showing the RRC state transition of a UE. The UE may be the same as or similar to the wireless device 106 shown in FIG. 1A, the UE 210 shown in FIGS. 2A and 2B, or any other wireless device described in the present disclosure. As shown in FIG. 6, the UE may be in at least one of three RRC states. That is, RRC connection 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0095] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be one of one or more base stations included in RAN 104 shown in FIG. 1A, one of gNB 160 or ng-eNB 162 shown in FIG. 1B, gNB 220 shown in FIGS. 2A and 2B, or any other base station similar to those described in the present disclosure. There may be an RRC context of the UE in the base station to which the UE is connected. The RRC context, called the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example, one or more AS contexts, one or more radio link configuration parameters, bearer configuration information (e.g., 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. In RRC connection 602, the mobility of the UE may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from the serving cell and adjacent cells and report these measurements to the base station currently providing service to the UE. The serving base station of the UE may request a handover to a cell of one of the adjacent base stations based on the reported measurements. The RRC state may transition from RRC connection 602 to RRC idle 604 via the connection release procedure 608, or may transition to RRC inactive 606 via the connection inactive procedure 610.

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

[0097] In RRC inactive 606, the previously established RRC context is maintained at the UE and the base station. This reduces the signaling overhead and enables a fast transition to RRC connected 602 compared to the transition from RRC idle 604 to RRC connected 602. In RRC inactive 606, the UE is in a sleep state and the mobility of the UE can be managed by the UE through cell reselection. The RRC state can transition from RRC inactive 606 to RRC connected 602 by a connection resume procedure 614, or to RRC idle 604 via a connection release procedure 616 that is the same as or similar to the connection release procedure 608.

[0098] The RRC state may be associated with a mobility management entity. 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 enable the network to notify the UE of events via paging messages without having to broadcast the paging messages across the entire mobile communication network. The mobility management entity used in RRC idle 604 and RRC inactive 606 may enable the network to track the UE at the cell group level such that paging messages can be broadcast on the cells of the cell group in which the UE is currently present instead of across the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE at the cell group level. They can do so using different granularities of grouping. For example, there can be three levels of granularity of cell grouping, namely, individual cells, cells within a RAN area identified by a RAN area identifier (RAI), and cells within a group of RAN areas called a tracking area and identified by a tracking area identifier (TAI).

[0099] The tracking area may be used to track the UE at the CN level. The CN (e.g., CN102 or 5G-CN152) may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area through cell reselection, the UE may perform a registration update with the CN so that the CN can update the UE's location and may provide the UE with a new UE registration area.

[0100] The RAN area can be used to track the UE 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 one or more cell identities, a list of RAI, or a list of TAI. In one embodiment, a base station can belong to one or more RAN notification areas. In one embodiment, a cell can belong to one or more RAN notification areas. When the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE can perform an update of the notification area in the RAN and update the RAN notification area of the UE.

[0101] The base station storing the RRC context for the UE, or the last serving base station of the UE, may be referred to as an anchor base station. The anchor base station can maintain the RRC context for the UE at least during the time the UE stays in the RAN notification area of the anchor base station and / or during the time the UE stays in RRRC inactive 606.

[0102] A gNB, such as gNB160 in Figure 1B, can be divided into two parts, namely 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 may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0103] In NR, physical signals and physical channels (Figs. 5A and 5B) 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 to a series of complex symbols (e.g., M quadrature amplitude modulation (M-QAM) or M phase shift keying (M-PSK) symbols), which are called source symbols and are split into an F parallel symbol stream. The F parallel symbol stream is treated as if they were in the frequency domain and can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain. The IFFT block can take one from each of the F parallel symbol streams at a time into an F source symbol and use each source symbol to modulate the amplitude and phase of one of the F sine wave 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 stream can be scrambled using an FFT block before being processed by the IFFT block. This process can generate an OFDM symbol that is pre-coded with a discrete Fourier transform (DFT) and can be used by a UE in the uplink to reduce the peak-to-average power ratio (PAPR). The reverse process can be performed on the OFDM symbol at the receiver using an FFT block to recover the data mapped to the source symbols.

[0104] Figure 7 shows a configuration example of an NR frame in which OFDM symbols are grouped. The NR frame can be identified by a system frame number (SFN). The SFN can be repeated over a period of 1024 frames. As shown in the figure, one NR frame may have a duration of 10 milliseconds (ms) or may include 10 subframes with a duration of 1 ms each. A subframe can be divided, for example, into slots each containing 14 OFDM symbols per slot.

[0105] The duration of a slot can depend on the numerology used for the OFDM symbols in the slot. In NR, flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies up to the maximum mmWave range to cells with carrier frequencies less than 1 GHz). Numerology can be defined with respect to the subcarrier spacing and the cyclic prefix duration. For numerology in NR, the subcarrier spacing may be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerology using the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 μs, 30 kHz / 2.3 μs, 60 kHz / 1.2 μs, 120 kHz / 0.59 μs, and 240 kHz / 0.29 μs.

[0106] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations, and correspondingly, more slots per subframe. FIG. 7 shows this numerology-dependent slot duration and slot transmission structure per subframe (for ease of illustration, the numerology with a 240 kHz subcarrier spacing is not shown in FIG. 7). Subframes within NR can be used as a numerology-independent time reference, while slots can be used as the units in which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR is separated from the slot duration and may start at any OFDM symbol and end with as many symbols as necessary for the transmission. These partial slot transmissions may be referred to as mini-slot transmissions or sub-slot transmissions.

[0107] FIG. 8 shows an example configuration of a slot in the time and frequency domains of an NR carrier. A slot contains 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 shown in FIG. 8. An RB spans 12 consecutive REs in the frequency domain, as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. These limitations, when used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, and a 400 MHz bandwidth may be set based on 400 MHz per carrier bandwidth limitation.

[0108] FIG. 8 shows a single numerology used across the full bandwidth of an NR carrier. In other exemplary configurations, multiple numerologies may be supported on the same carrier.

[0109] NR can support a wide carrier bandwidth (e.g., up to 400 MHz for a 120 kHz subcarrier spacing). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations, etc.). Also, receiving the full carrier bandwidth may be prohibited from the perspective of the UE's power consumption. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its receive bandwidth based on the amount of traffic the UE expects to receive. This is called bandwidth adaptation.

[0110] NR supports UEs that cannot receive the full carrier bandwidth and defines a bandwidth part (BWP) that supports bandwidth adaptation. In one embodiment, the 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 BWPs configured for a serving cell may be active. These one or more BWPs may be referred to as the active BWPs of the serving cell. When the serving cell is composed of a secondary uplink carrier, the serving cell may have one or more first active BWPs for the uplink carrier and one or more second active BWPs for the secondary uplink carrier.

[0111] For unpaired spectrum, if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the 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, the UE may expect that the center frequency of the downlink BWP is the same as the center frequency of the uplink BWP.

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

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

[0114] 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 one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0115] The base station may semi-statically configure the UE with the default downlink BWP within the 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.

[0116] The base station may configure the UE with the BWP Inactive timer value. The UE may start or restart the BWP Inactive timer at any appropriate time. For example, (a) when the UE detects DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation, or (b) when the UE detects DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation, the UE may start or restart the BWP Inactive timer. If the UE does not detect DCI for a certain period (e.g., 1 millisecond or 0.5 millisecond), the UE may run the BWP Inactive timer towards expiration (e.g., increment from zero to the BWP Inactive timer value or decrement from the BWP Inactive timer value to zero). When the BWP Inactive timer expires, the UE may be switched from the active downlink BWP to the default downlink BWP.

[0117] In one embodiment, the base station may semi-statically configure a UE having 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 the second BWP as the active BWP and / or in response to the expiration of the BWP Inactive timer (e.g., when the second BWP is the default BWP).

[0118] Downlink and uplink BWP switching (where BWP switching refers to switching from the currently active BWP to a non-currently active BWP) may be performed independently in a pair of spectrums. In non-pair spectrums, downlink and uplink BWP switching may be performed simultaneously. The switching between configured BWPs may occur based on RRC signaling, DCI, expiration of the BWP inactive timer, and / or the start of random access.

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

[0120] If the UE is configured for a secondary cell with a set of configured downlink BWPs and a default downlink BWP in terms of timer values, 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 may use the timer values and the default downlink BWP for the secondary cell in the same / similar manner as it uses these values for the primary cell.

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

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

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

[0124] When using CA, one of the UE's aggregated cells may be referred to as the Primary Cell (PCell). The PCell can be the serving cell to which the UE first connects in RRC connection establishment, re - establishment, and / or handover. The PCell can provide NAS mobility information and security inputs to the UE. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the Downlink Primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the Uplink Primary CC (UL PCC). The UE's other aggregated cells may be referred to as Secondary Cells (SCells). In one embodiment, an SCell can be configured after the PCell is configured for the UE. For example, an SCell can be configured via the RRC connection re - configuration procedure. In the downlink, the carrier corresponding to the SCell may be referred to as the Downlink Secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the Uplink Secondary CC (UL SCC).

[0125] The SCell configured for the UE can be activated and deactivated, for example, based on traffic and channel conditions. Deactivation of the SCell can mean that PDCCH and PDSCH reception on the SCell is stopped, and PUSCH, SRS, and CQI transmissions on the SCell are stopped. The configured SCell can be activated and deactivated using MAC CE with respect to Figure 4B. For example, the MAC CE can use a bitmap (e.g., 1 bit per SCell) to indicate which SCell (e.g., among a subset of the configured SCells) for the UE is 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).

[0126] Downlink control information such as cell scheduling assignment and scheduling grant can be transmitted on the cell corresponding to the assignment and grant, known as self-scheduling. The DCI for a cell can be transmitted on another cell known as cross-carrier scheduling. Uplink control information for an aggregation cell (e.g., HARQ acknowledgement responses and channel state feedback such as CQI, PMI, and / or RI) can be transmitted on the PUCCH of the PCell. If the number of aggregated downlink CCs is large, the PUCCH of the PCell may become overloaded. The cell may be divided into a plurality of PUCCH groups.

[0127] Figure 10B shows an example of how an aggregation cell can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. In the example of Figure 10B, UCCH group 1010 includes three downlink CCs of PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs of PCell 1051, SCell 1052, and SCell 1053 in this example. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary S cell (PSCell) 1061, SCell 1062, and SCell 1063. The uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 shown as UCI 1031, UCI 1032, and UCI 1033 can be transmitted on the uplink of PCell 1021. The uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 shown as UCI 1071, UCI 1072, and UCI 1073 can be transmitted on the uplink of PSCell 1061. In one example, if the aggregation cell depicted in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell and PCell for transmitting UCI related to the downlink CCs can be in an overloaded state. Overload can be prevented by splitting the transmission of UCI between PCell 1021 and PSCell 1061.

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

[0129] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In one embodiment, the HARQ entity can operate on the serving cell. A transport block can be generated per allocation / grant per serving cell. The transport block and potential HARQ retransmissions of the transport block can be mapped to the serving cell.

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

[0131] FIG. 11A shows an example of the structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). The burst may be transmitted periodically (e.g., every 2 frames or every 20 milliseconds). The burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 milliseconds). FIG. 11A is an example, and it will be understood that these parameters (the number of SS / PBCH blocks per burst, the periodicity of the burst, the position of the burst within the frame) may be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH block is transmitted, the numerology of the cell or the subcarrier spacing, network configuration (e.g., using RRC signaling), or any other suitable factor. In one embodiment, a UE may assume a subcarrier spacing for an SS / PBCH block based on the carrier frequency being monitored, except when the radio network has configured the UE to assume a different subcarrier spacing.

[0132] The SS / PBCH block may span one or more OFDM symbols within the time domain (e.g., four OFDM symbols as shown in the example of FIG. 11A), and may also span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first, e.g., over one OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., in the next two symbols), and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., over the next three OFDM symbols), and may span 240 subcarriers.

[0133] The position of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., when the UE is searching for a cell). To find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain period (e.g., 20 milliseconds), the UE may search for the PSS at different frequency positions within the carrier as indicated by the synchronization raster. When the PSS is found at its position in the time and frequency domains, the UE may determine the positions of the SSS and PBCH respectively based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). In one embodiment, the primary cell may be associated with the CD-SSB. The CD-SSB may be placed on the synchronization raster. In one embodiment, cell selection / search and / or reselection may be based on the CD-SSB.

[0134] The SS / PBCH block can be used by a UE to determine one or more parameters of a cell. For example, the UE may determine the physical cell identifier (PCI) of a cell based on each of the sequences of the PSS and SSS. The UE may determine the position of the frame boundary of a cell based on the position of the SS / PBCH block. For example, the SS / PBCH block may indicate that it was transmitted according to a transmission pattern, and the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0135] The PBCH may use QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or the SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include the master information block (MIB) used to provide one or more parameters to the UE. The MIB can be used by the UE to find the remaining minimum system information (RMSI) associated with the cell. The RMSI may include the system information block type 1 (SIB1). The SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which can be used to schedule the PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of the SIB1. Based on the PBCH indicating the absence of the SIB1, the UE may indicate a frequency. The UE may search for the SS / PBCH block at the frequency indicated by the UE.

[0136] 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 cannot assume that SS / PBCH blocks having different QCL for SS / PBCH block transmissions have different SS / PBCH block indexes.

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

[0138] In one embodiment, within the frequency span of a carrier, the base station can transmit multiple SS / PBCH blocks. In one embodiment, the first PCI of the first SS / PBCH block of the multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block of the multiple SS / PBCH blocks. The PCI of SS / PBCH blocks transmitted at different frequency positions may be different or the same.

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

[0140] The base station can semi-statically configure the UE with one or more CSI-RS resource sets. The CSI-RS resources may be associated with positions and periodicities within the time and frequency domains. 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 within the CSI-RS resource set are activated and / or deactivated.

[0141] The base station can configure the UE to report CSI measurement values. The base station can configure the UE to provide CSI reports periodically, irregularly, or semi-persistently. For periodic CSI reports, the UE can be configured with the timing and / or periodicity of multiple CSI reports. For irregular CSI reports, the base station can request a CSI report. For example, the base station can instruct the UE to measure the configured CSI-RS resources and provide a CSI report regarding the measurement values. For semi-persistent CSI reports, the base station can transmit periodic reports regularly and configure the UE to selectively activate or deactivate. The base station can configure the UE with CSI-RS resource sets and CSI reports using RRC signaling.

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

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

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

[0145] The PDSCH may include one or more layers. The UE may assume that at least one symbol having DMS is present on one or more layers of the PDSCH. The upper layer may configure up to three DMRSs for the PDSCH.

[0146] The downlink PT-RS may be transmitted by the base station and can be used by the UE for phase noise compensation. Whether the downlink PT-RS exists depends on the RRC configuration. The presence and / or pattern of the downlink PT-RS can be indicated by a combination of RRC signaling and / or DCI, and can be configured on a UE-specific basis in association with one or more parameters used 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 and / or frequency domain. The frequency domain density, if it exists, can be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DM-RS ports within the scheduled resources. The downlink PT-RS can be restricted to the UE's scheduled time / frequency period. The downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0147] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station may use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit uplink DMR on PUSCH and / or PUCCH. The uplink DM-RS may 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 may support a front-loaded DMRS pattern. The front-loaded DMRS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted in one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE using the number (e.g., the maximum number) of front-loaded DMRS symbols for PUSCH and / or PUCCH that the UE can use to schedule single-symbol DMRS and / or double-symbol DMRS. The NR network may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS position, DMRS pattern, and / or DMRS scrambling sequence may be the same or different.

[0148] PUSCH may include one or more layers, and the UE may transmit at least one symbol having DMS present on one or more layers of the PUSCH. In one embodiment, the upper layer may configure up to three DMRS for the PUSCH.

[0149] The uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist depending on the UE's RRC configuration. The presence and / or pattern of the uplink PT-RS can be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)) that can be indicated by RRC signaling and / or 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 can support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if it exists, can be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS ports and the PT-RS ports. The number of PT-RS ports may be less than the number of DM-RS ports within the scheduled resources. For example, the uplink PT-RS may be restricted to the UE's scheduled time / frequency period.

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

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

[0152] An antenna port is defined such that the channel over which a symbol on the antenna port is transmitted can be inferred from the channel over which another symbol on the same antenna port is transmitted. When a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fade gain, multipath delay, and / or the like) for carrying the second symbol on the antenna port from the channel for carrying the first symbol on the antenna port. The first antenna port and the second antenna port may be said to be quasi-co-located (QCLed) if one or more large-scale characteristics of the channel over which the first symbol on the first antenna port is transmitted can be inferred from the channel over which the second symbol on the second antenna port is transmitted. The one or more large-scale properties may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (Rx) parameters.

[0153] In channels that use beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurements based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)) and generate a beam measurement report. The UE can perform the downlink beam measurement procedure after the RRC connection is set up at the base station.

[0154] Figure 11B shows an example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domains. The squares shown in Figure 11B may span resource blocks (RBs) within the cell bandwidth. The base station can transmit one or more RRC messages containing CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters can be set by upper layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration. CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions within a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission beam, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

[0157] In the beam management procedure, the UE may evaluate (e.g., measure) the channel quality of one or more beam pair links, the transmission beam transmitted by the base station, and the reception beam received by the UE. Based on the evaluation, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, including, for example, one or more beam identifications (e.g., beam index, reference signal index, or the like), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0158] Figure 12A shows examples of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements at the transmission (Tx) beam of the transmission and reception point (TRP) (or multiple TRPs) to support the selection of, for example, one or more base station Tx beams and / or UE Rx beams (each shown as an ellipse in the top and bottom rows of P1). Beamforming at the TRP may include a Tx beam sweep of a set of beams (as shown by the dashed arrows in the top row of P1 and P2, where the ellipse is shown rotating counterclockwise). Beamforming at the UE may include an Rx beam sweep for a set of beams (as shown in the lower rows of P1 and P3, where the ellipse rotates in a clockwise direction when shown by the dashed arrows). Using procedure P2, UE measurements at the Tx beam of the TRP can be enabled. (As shown by the dashed arrows in the top row of P2, the ellipse is shown rotating counterclockwise). The UE and / or the base station may perform procedure P2 using a set of beams smaller than those used in procedure P1 or using beams narrower than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0159] Figure 12B shows examples of three uplink beam management procedures, U1, U2, and U3. Using procedure U1, for example, the base station may be enabled to perform measurements on the UE's Tx beam to support the selection of, for example, one or more UE Tx beams and / or base station Rx beams (shown as ellipses at the top and bottom of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams. (Shown as ellipses rotated clockwise when indicated by dashed arrows below U1 and U3). Beamforming at the base station may include, for example, an Rx beam sweep from a set of beams. (Shown as ellipses rotated counterclockwise as indicated by dashed arrows in the top row of U1 and U2). Using procedure U2, the base station may be enabled to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a set of beams smaller than those used in procedure P1 or using beams narrower than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0160] The UE may initiate a beam failure recovery (BFR) procedure based on the detection of a beam failure. The UE may transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, and / or the like) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, expiration of a timer, and / or the like).

[0161] The UE may measure the quality of the beam pair link using one or more reference signals (RSs) 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 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 the RS resource. The base station may indicate that the RS resource is quasi-co-located (QCL) with one or more DM-RSs of a channel (e.g., control channel, shared data channel, and / or the like). The RS resource of the channel and the one or more DMRSs may be QCL when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fade, and / or the like) from the transmission to the UE via the RS resource are similar or identical to the channel characteristics from the transmission to the UE via the channel.

[0162] A network (e.g., a gNB and / or ng-eNB of the network) and / or a UE may initiate a random access procedure. A UE in the RRC_IDLE state and / or a UE in the RRC_INACTIVE state may initiate a random access procedure to request connection setup to the network. A UE may initiate a random access procedure from the RRC_CONNECTED state. A UE may initiate a random access procedure to request uplink resources (e.g., for SR uplink transmission when there are no available PUCCH resources) and / or to obtain uplink timing (e.g., when the uplink synchronization state is not synchronized). A 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, and / or the like). A UE may initiate a random access procedure for beam failure recovery request. The network may initiate a random access procedure for handover and / or to establish time alignment for SCell addition.

[0163] Figure 13A shows a 4-step contention-based random access procedure. Before the start of the procedure, the base station may send a configuration message 1310 to the UE. Figure 13A includes the transmission of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may include a preamble (or random access preamble) and / or may be called a preamble. Msg2 1312 may include a random access response (RAR) and / or may be called a random access response (RAR).

[0164] The constituent message 1310 can be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of general parameters (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-ConfigCommon), and / or dedicated parameters (e.g., RACH-configDedicated) for one or more random access procedures. The base station can broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages can 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 can determine the time-frequency resources and / or uplink transmission power for the transmission of Msg1 1311 and / or Msg3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE can determine the reception timing and downlink channels for receiving Msg2 1312 and Msg4 1314.

[0165] One or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of Msg1 1311. The one or more PRACH opportunities may be pre-defined. The one or more RACH parameters may indicate one or more available sets of the one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate the association between (a) the one or more PRACH opportunities and (b) the one or more reference signals. The one or more RACH parameters may indicate the association between (a) the one or more preambles and (b) the one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

[0166] Using one or more RACH parameters provided in the configuration message 1310, the uplink transmission power of Msg1 1311 and / or Msg3 1313 may be determined. For example, the one or more RACH parameters may indicate the reference power for preamble transmission (e.g., the received target power and / or the initial power of preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate the power ramping step, the power offset between the SSB and the CSI-RS, the power offset between the transmissions of Msg1 1311 and Msg3 1313, and / or the power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds for the UE to 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).

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

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

[0169] If the UE does not receive a response after preamble transmission, it may perform preamble retransmission. The UE may increase the uplink transmission power for preamble retransmission. The UE may select the initial preamble transmission power based on path loss measurement and / or target received preamble power configured by the network. The UE may decide to retransmit the preamble and may ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramping step for preamble retransmission. The ramping step may be the amount of incremental increase in uplink transmission power for retransmission. If the UE determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission, the UE may ramp up the uplink transmission power. The UE can count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_STATEER). The UE may decide that the random access procedure has failed and completed, for example, when the number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax).

[0170] The Msg2 1312 received by the UE may include an RAR. In some scenarios, the Msg2 1312 may include multiple RARs corresponding to multiple UEs. The Msg2 1312 may be received after or in response to the transmission of Msg1 1311. The Msg2 1312 is scheduled on the DL-SCH and may be indicated on the PDCCH using a Random Access Radio Network Temporary Identifier (RA-RNTI). The Msg2 1312 may indicate that the Msg1 1311 has been received by the base station. The Msg2 1312 may include a timing alignment command that the UE may use to adjust the UE's transmission timing, a scheduling grant for the transmission of Msg3 1313, and / or a Temporary Cell Radio Network Temporary Identifier (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg2 1312. The UE may determine when to start the time window based on the PRACH opportunity used by the UE to transmit the preamble. For example, the UE may start the time window after one or more symbols of the last symbol of the preamble (e.g., at the first PDCCH opportunity after the end of the preamble transmission). The one or more symbols may be determined based on numerology. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used in response to one or more events that initiate a random access procedure. The UE may use a Random Access Radio Network Temporary Identifier (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity used by the UE to transmit the preamble. For example, the UE may determine the RA-RNTI based on the OFDM symbol index, slot index, frequency domain index, and / or UL carrier indicator of the PRACH opportunity. Examples of RA-RNTI may be as follows. RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id In the formula, s_id may be the index of the first OFDM symbol of the PRACH opportunity (for example, 0 ≦ s_id < 14), t_id may be the index of the first slot of the PRACH opportunity within the system frame (for example, 0 ≦ t_id < 80), f_id may be the index of the PRACH opportunity in the frequency domain (for example, 0 ≦ f_id < 8), and ul_carrier_id may be the UL carrier used for preamble transmission (for example, 0 for the NUL carrier and 1 for the SUL carrier). In response to successful reception of Msg2 1312 (for example, using the resources identified in Msg2 1312), the UE may transmit Msg3 1313. Msg3 1313 may be used, for example, for contention resolution in the contention-based random access procedure shown in FIG. 13A. In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide the RAR corresponding to the UE. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Contention resolution (for example, the use of Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE does not accidentally use the identity of another UE. To perform contention resolution, the UE may include a device identifier (for example, if assigned, the C-RNTI, the TC-RNTI included in Msg2 1312, and / or any other appropriate identifier) in Msg3 1313.

[0171] Msg4 1314 can be received after or in response to the transmission of Msg3 1313. If the C-RNTI was included in Msg3 1313, the base station uses the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, it is determined that the random access procedure has been successfully completed. If the TC-RNTI is included in Msg3 1313 (e.g., if the UE is in the RRC_IDLE state or otherwise not connected to the base station), Msg4 1314 is received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU transmitted (e.g., sent) in Msg3 1313 or otherwise contains the corresponding UE contention resolution identity EtOAc CE, the UE can determine that contention resolution has been successful and / or the UE can determine that the random access procedure has been successfully completed.

[0172] The UE may be composed of 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 the UE with two separate RACH configurations, i.e., one for the SUL carrier and the other for the NUL carrier. For random access within the cell composed of the SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The UE may determine the SUL carrier, for example, when the measurement quality of one or more reference signals is lower than the broadcast threshold. The uplink transmission of the random access procedure (e.g., Msg1 1311 and / or Msg3 1313) can stay on the selected carrier. The UE may switch the uplink carrier during the random access procedure (e.g., between Msg1 1311 and Msg3 1313) in one or more cases. For example, the UE may determine and / or switch the uplink carrier of Msg1 1311 and / or Msg3 1313 based on the channel clear assessment (e.g., listen before talk).

[0173] Figure 13B shows a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure shown in Figure 13A, the base station may send a configuration message 1320 to the UE before the start of the procedure. The configuration message 1320 may be similar to the configuration message 1310 in some respects. Figure 13B includes the transmission of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar to Msg1 1311 and Msg2 1312 shown in Figure 13A respectively in some respects. As understood from Figures 13A and 13B, the contention-free random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

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

[0175] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of 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 within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor for PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. In the random access procedure without contention shown in FIG. 13B, the UE may determine that the random access procedure has completed successfully after or in response to the transmission of Msg1 1321 and the reception of the corresponding Msg2 1322. The UE may determine that the random access procedure has completed successfully, for example, if the PDCCH transmission is addressed to the C-RNTI. The UE may determine that the random access procedure has completed successfully if, for example, the UE receives an RAR that includes a preamble identifier corresponding to the preamble transmitted by the UE, and / or if the RAR includes a MAC sub-PDU that includes the preamble identifier. The UE may determine the response as an indicator of confirmation for the SI request.

[0176] FIG. 13C shows another two-step random access procedure. Similar to the random access procedures shown in FIGS. 13A and 13B, the base station may be able to transmit a configuration message 1330 to the UE before the start of the procedure. The configuration message 1330 may be similar in some respects to the configuration message 1310 and / or the configuration message 1320. FIG. 13C includes the transmission of two messages, namely, Msg A 1331 and Msg B 1332.

[0177] Msg A 1331 can be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of the preamble 1341 and / or one or more transmissions of the transport block 1342. The transport block 1342 may include content that is similar and / or equivalent to the content of Msg3 1313 shown in FIG. 13A. The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or the like). After or in response to the transmission of Msg A 1331, the UE may receive Msg B 1332. Msg B 1332 may include content that is similar and / or equivalent to the content of Msg 2 1312 (e.g., RAR) shown in FIGS. 13A and 13B, and / or the content of Msg4 1314 shown in FIG. 13A.

[0178] The UE can initiate the two-step random access procedure of FIG. 13C 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 in use (e.g., LTE, NR, and / or the like), whether the UE has a valid TA, cell size, the RRC state of the UE, the type of spectrum (e.g., licensed versus unlicensed), and / or any other appropriate factor.

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

[0180] The transport block 1342 may include data (e.g., delay-sensitive data), UE identifiers, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation 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 when the preamble identifier of Msg B 1332 matches the preamble transmitted by the UE and / or the UE identifier of Msg B 1332 matches the UE identifier of Msg A 1331 (e.g., the transport block 1342).

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

[0182] The downlink control signaling may include downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport formats, slot format information, preemption indication, power control commands, and / or any other suitable signaling. The UE may receive the downlink control signaling within 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.

[0183] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with the identifier of the UE (or the identifier of the group of UEs). Scrambling the CRC parity bits with the identifier may include 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).

[0184] The DCI can be used for different purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notification. The P-RNTI can be pre-defined as "FFFE" in hexadecimal. DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate the broadcast transmission of system information. The SI-RNTI can be pre-defined as "FFFE" in hexadecimal. DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate the unicast transmission of dynamic scheduling and / or the trigger for random access of the PDCCH order. DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). The encoding of other RNTIs configured by the base station for the UE includes Configured Scheduling RNTI (CS-RNTI), Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0185] Depending on the purpose and / or content of the DCI, the base station may transmit DCI in one or more DCI formats. For example, DCI format 0_0 can be used for scheduling PUSCH within a cell. DCI format 0_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 0_1 can be used for scheduling PUSCH within a cell (e.g., having more DCI payload than DCI format 0_0). DCI format 1_0 can be used for scheduling PDSCH within a cell. DCI format 1_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 1_1 can be used for scheduling PDSCH within a cell (e.g., having more DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide slot format indication to a group of UEs. DCI format 2_1 can be used to notify a group of UEs of physical resource blocks and / or OFDM symbols that are assumed not to be intended for transmission to the UE. DCI format 2_2 can be used for transmitting transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used for transmitting a group of TPC commands for SRS transmission by one or more UEs. New feature DCI formats may be defined in future releases. DCI formats may have different DCI sizes or share the same DCI size.

[0186] After scrambling the DCI with the RNTI, the base station may process the DCI using channel coding (e.g., polar coding), rate matching, scrambling and / or QPSK modulation. The base station may map the encoded and modulated DCI onto resource elements used 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 several 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 plurality (e.g., 6) of resource element groups (REGs). A REG may include resource blocks within an OFDM symbol. The mapping of the encoded and modulated DCI onto the resource elements may be based on the mapping of the CCEs and REGs (e.g., CCE~REG mapping).

[0187] FIG. 14A shows an example of a CORESET configuration for a bandwidth part. 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 for which the UE attempts to decode the DCI using one or more search spaces. The base station may configure the CORESET within the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur in the first symbol within a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs in the third symbol within the slot. A fourth CORESET 1404 occurs in the 7th symbol of the slot. The CORESET may have a different number of resource blocks in the frequency domain.

[0188] FIG. 14B shows an example of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing. The CCE-to-REG mapping can 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 control channels). The base station can perform different or the same CCE-to-REG mapping on different CORESETs. The CORESET may be associated with the CCE-to-REG mapping by RRC configuration. The CORESET can be configured with antenna port quasi-co-location (QCL) parameters. The QCL parameters of the antenna port can indicate the QCL information of the demodulation reference signal (DMRS) for PDCCH reception within the CORESET.

[0189] The base station can transmit an RRC message to the UE that includes configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can indicate the number of PDCCH candidates monitored per aggregation level, the PDCCH monitoring periodicity and pattern, one or more DCI formats 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 within the common search space set can be predefined and known to the UE. The set of CCEs within the UE-specific search space set can be configured based on the UE's identity (e.g., C-RNTI).

[0190] As shown in FIG. 14B, 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) for the CORESET based on the configuration parameters of the CORESET. The UE may determine the number of search space sets (e.g., up to 10) configured on the CORESET based on the RRC message. The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates within one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates of 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 having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs in the common search space, the number of PDCCH candidates, 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 a valid DCI for the UE in response to a CRC check (e.g., the scrambling bits for the CRC parity bits of the DCI that match 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, and / or the like).

[0191] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a hybrid automatic repeat request (HARQ) acknowledgment response for the received DL-SCH transport block. The UE may transmit the HARQ acknowledgment response after receiving the DL-SCH transport block. The uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. The base station may determine transmission format parameters (e.g., including multi-antenna and beamforming schemes) for downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is transmissible to the base station. The UE may 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 may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0192] 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 may have a length of one or two OFDM symbols and may contain 2 or fewer bits. The UE can use PUCCH format 0 to transmit the UCI on the PUCCH resource when the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two. PUCCH format 1 may occupy a number between 4 and 14 OFDM symbols and may contain 2 or fewer bits. The UE can use PUCCH format 1 when the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than 2 bits. The UE can use PUCCH format 2 when the transmission exceeds one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between 4 and 14 OFDM symbols and may contain more than 2 bits. The UE can use PUCCH format 3 when 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. PUCCH format 4 may occupy a number between 4 and 14 OFDM symbols and may contain more than 2 bits. The UE can use PUCCH format 4 when 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.

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

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

[0195] FIG. 15 shows an example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure. The wireless device 1502 and the base station 1504 may be part of a mobile communication network such as the mobile communication network 100 shown in FIG. 1A, the mobile communication network 150 shown in FIG. 1B, or other communication networks. Only one wireless device 1502 and one base station 1504 are shown in FIG. 15. However, it will be understood that the mobile communication network may include a plurality of UEs and / or a plurality of base stations having the same or similar configuration as that shown in FIG. 15.

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

[0197] In the downlink, data transmitted from the base station 1504 to the wireless device 1502 can be provided to the processing system 1508 of the base station 1504. The data can be provided to the processing system 1508, for example, by a core network. In the uplink, data transmitted 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 data for transmission. Layer 2 can include, for example, an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer with respect to FIGS. 2A, 2B, 3, and 4A. Layer 3 can include an RRC layer with respect to FIG. 2B.

[0198] After being processed by the processing system 1508, data transmitted 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, data transmitted 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 a PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For transmission processing, the PHY layer can perform, for example, forward error correction coding of a transport channel, interleaving, rate matching, mapping of the transport channel to a physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

[0199] At base station 1504, reception processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, reception processing system 1522 can receive downlink transmissions from base station 1504. Reception processing system 1512 and reception processing system 1522 can implement the OSI functions of layer 1. Layer 1 can include a PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For reception processing, the PHY layer can 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, and / or the like.

[0200] As shown in FIG. 15, wireless device 1502 and base station 1504 can include multiple antennas. The multiple antennas can be used to implement one or more MIMO or multi-antenna technologies such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other embodiments, wireless device 1502 and / or base station 1504 can have a single antenna.

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

[0202] 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 the one or more processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) 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 signal encoding / processing, data processing, power control, input / output processing, and / or any other function that may enable wireless device 1502 and base station 1504 to operate in a wireless environment.

[0203] Processing system 1508 and / or processing system 1518 can each be 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 can include software and / or hardware that provides features and / or functions, such as speakers, microphones, keypads, display devices, touch pads, 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 vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, optical sensors, cameras, and / or the like). Processing system 1508 and / or processing system 1518 can 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. The processing system 1518 within the wireless device 1502 can receive power from a power source and / or be configured to distribute power to other components within the wireless device 1502. The power source can 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 can each be connected to a GPS chipset 1517 and a GPS chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 can each be configured to provide geographical location information of the wireless device 1502 and the base station 1504.

[0204] FIG. 16A shows an exemplary structure for uplink transmission. The baseband signal representing the physical uplink shared channel can perform one or more functions. These one or more functions can include at least one of scrambling, modulation of scrambling bits to generate complex-valued symbols, mapping of the complex-valued modulated symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding of the complex-valued symbols, mapping of the precoded complex-valued symbols to resource elements, generation of a complex-valued time-domain single-carrier frequency-division multiple access (SC-FDMA) or CP-OFDM signal to an antenna port, and / or the like. In one embodiment, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In one embodiment, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission can be generated according to FIG. 16A. These functions are shown by way of example, and it is expected that other mechanisms can be implemented in various embodiments.

[0205] FIG. 16B shows an exemplary structure for modulation of a baseband signal to a carrier frequency and upconversion. The baseband signal can be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port. Filtering can be used before transmission.

[0206] Figure 16C shows an exemplary structure of downlink transmission. The baseband signal representing the physical downlink channel can perform one or more functions. These one or more functions can include scrambling of the encoded bits within the codeword to be transmitted on the physical channel, modulation of the scrambled bits to generate complex-valued modulation symbols, mapping of the complex-valued modulation symbols onto one or several transmission layers, precoding of the complex-valued modulation symbols on the layer for transmission on the antenna port, mapping of the complex-valued modulation symbols of the antenna port onto resource elements, generation of the complex-valued time-domain OFDM signal for each antenna port, and / or the like. These functions are shown by way of example, and it is expected that other mechanisms can be implemented in various embodiments.

[0207] Figure 16D shows another exemplary structure for modulation and upconversion of the baseband signal to the carrier frequency. The baseband signal can be a complex-valued OFDM baseband signal for the antenna port. Filtering can be used before transmission.

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

[0209] When the timer is started, execution begins and can continue until stopped or until expiration. The timer can be started when not running or restarted when running. The timer may be associated with a value (e.g., the timer may start or resume from a certain value, or start from zero and expire when the value is reached). The duration of the timer cannot be updated (e.g., by BWP switching) until the timer stops or expires. Timers can be used to measure the duration / window of a process. When this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways to implement one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer can be used to measure the duration / window of a procedure. For example, a random access response window timer can be used to measure the window time for receiving a random access response. In one embodiment, instead of starting and expiring a random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the process for measuring the time window can be restarted. Other exemplary implementations can be provided to restart the measurement of the time window.

[0210] The gNB can transmit one or more MAC PDUs to the wireless device. In one embodiment, the MAC PDU can be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). In one embodiment, the bit string can be represented by a table where the most significant bit is the leftmost bit of the first row of the table and the least significant bit is the rightmost bit of the last row of the table. More generally, the bit string is read from left to right and then in the order of row reading. In one embodiment, the bit order of the parameter field within the MAC PDU is represented by the first most significant bit of the leftmost bit and the last least significant bit of the rightmost bit.

[0211] In one embodiment, the MAC SDU can be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). In one embodiment, the MAC SDU can be included in the MAC PDU after the first bit. In one embodiment, the MAC CE can be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). In one embodiment, the MAC sub-header can be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). In one embodiment, the MAC sub-header can be placed immediately before the corresponding MAC SDU, MAC CE, or padding. The MAC entity can ignore the value of the reserved bits of the DL MAC PDU.

[0212] In one embodiment, the MAC PDU can include one or more MAC sub-PDUs. The MAC sub-PDUs among the one or more MAC sub-PDUs can include only the MAC sub-header (including padding), the MAC sub-header and the MAC SDU, the MAC sub-header and the MAC CE, and / or the MAC sub-header and the padding. The size of the MAC SDU can be variable. The MAC sub-header can correspond to the MAC SDU, the MAC CE, or the padding.

[0213] In one embodiment, when the MAC sub-header corresponds to the MAC SDU, the variable-size MAC CE, or the padding, the MAC sub-header can include a 1-bit long R field, a 1-bit long F field, a multi-bit long LCID field, and / or a multi-bit long L field.

[0214] FIG. 17A shows an example of a MAC sub-header including an R field, an F field, an LCID field, and an L field. In the exemplary MAC sub-header of FIG. 17A, the LCID field can be 6 bits in length and the L field can be 8 bits in length. FIG. 17B shows an example of a MAC sub-header including an R field, an F field, an LCID field, and an L field. In the exemplary MAC sub-header of FIG. 17B, the LCID field can be 6 bits in length and the L field can be 16 bits in length. When the MAC sub-header corresponds to a fixed-size MAC CE or padding, the MAC sub-header can include a 2-bit long R field and a multi-bit long LCID field. FIG. 17C shows an example of a MAC sub-header including an R field and an LCID field. In the exemplary MAC sub-header of FIG. 17C, the LCID field can be 6 bits in length and the R field can be 2 bits in length.

[0215] FIG. 18A shows an example of a DL MAC PDU. A plurality of MAC CEs such as MAC CE 1 and 2 can be arranged together. The MAC sub-PDU including the MAC CE can be arranged before any MAC sub-PDU including a MAC SDU or a MAC sub-PDU including padding. FIG. 18B shows an example of a UL MAC PDU. A plurality of MAC CEs such as MAC CE 1 and 2 can be arranged together. The MAC sub-PDU including the MAC CE can be arranged after all MAC sub-PDUs including a MAC SDU. Further, the MAC sub-PDU can be arranged before a MAC sub-PDU including padding.

[0216] In one embodiment, the MAC entity of the gNB can send one or more MAC CEs to the MAC entity of the wireless device. FIG. 19 shows an example of a plurality of LCIDs that can be associated with one or more MAC CEs. The one or more MAC CEs include at least one of a SP ZP CSI-RS resource set activation / stop MAC CE, a PUCCH spatial relation activation / stop MAC CE, a SP SRS activation / stop MAC CE, a SP CSI report activation / stop MAC CE for PUCCH, a TCI state indication MAC CE for UE-specific PDCCH, a TCI state indication MAC CE for UE-specific PDSCH, an aperiodic CSI trigger state sub-selection MAC CE, a SP CSI-RS / CSI-IM resource set activation / stop MAC CE, a UE contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a long DRX command MAC CE, a SCell activation / stop MAC CE (1 octet), a SCell activation / stop MAC CE (4 octets), and / or a duplicate activation / stop MAC CE. In one embodiment, a MAC CE such as a MAC CE sent by the MAC entity of the gNB to the MAC entity of the wireless device can have an LCID in the MAC sub-header corresponding to the MAC CE. Different MAC CEs can have different LCIDs in the MAC sub-header corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC sub-header can indicate that the MAC CE associated with the MAC sub-header is a long DRX command MAC CE.

[0217] In one embodiment, the MAC entity of the wireless device can send one or more MAC CEs to the MAC entity of the gNB. FIG. 20 shows an embodiment of one or more MAC CEs. The one or more MAC CEs can include at least one of a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single entry PHR MAC CE, a multiple entry PHR MAC CE, a short blocked BSR, and / or a long blocked BSR. In one embodiment, the MAC CE can have an LCID in the MAC sub-header corresponding to the MAC CE. Different MAC CEs can have different LCIDs in the MAC sub-header corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC sub-header can indicate that the MAC CE associated with the MAC sub-header is a short blocked command MAC CE.

[0218] In carrier aggregation (CA), two or more component carriers (CCs) can be aggregated. The wireless device can use the CA technology to receive or transmit simultaneously on one or more CCs according to the functions of the wireless device. In one embodiment, the wireless device can support CA for adjacent CCs and / or non-adjacent CCs. The CCs can be organized into cells. For example, the CCs can be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, the wireless device can have one RRC connection with the network. During the establishment / re-establishment / handover of the RRC connection, the cell providing the NAS mobility information can be the serving cell. During the re-establishment / handover procedure of the RRC connection, the cell providing the security input can be the serving cell. In one embodiment, the serving cell can indicate the PCell. In one embodiment, the gNB can send one or more messages including the configuration parameters of one or more SCells to the wireless device according to the functions of the wireless device.

[0219] When configured using CA, the base station and / or the wireless device may use the SCell activation / deactivation mechanism to improve the battery or power consumption of the wireless device. When the wireless device is configured using one or more SCell, the gNB can activate or deactivate at least one of the one or more SCell. When configuring the SCell, the SCell can be deactivated unless the SCell state associated with the SCell is set to "activated" or "suspended".

[0220] The wireless device can activate / deactivate the SCell in response to receiving the SCell activation / deactivation MAC CE. In one embodiment, the gNB may send one or more messages including an SCell timer (e.g., sCellDeactivationTimer) to the wireless device. In one embodiment, the wireless device can deactivate the SCell in response to the expiration of the SCell timer.

[0221] When the wireless device receives the SCell activation / deactivation MAC CE to activate the SCell, the wireless device can activate the SCell. In response to the activation of the SCell, the wireless device may perform operations including SRS transmission on the SCell, CQI / PMI / RI / CRI reporting for the SCell, PDCCH monitoring on the SCell, PDCCH monitoring for the SCell, and / or PUCCH transmission on the SCell. In response to the activation of the SCell, the wireless device may start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in the slot when the SCell activation / deactivation MAC CE to activate the SCell is received. In one embodiment, in response to the activation of the SCell, the wireless device can (re)initialize one or more interrupted configured uplink grants of configured grant type 1 associated with the SCell according to the stored configuration. In one embodiment, in response to the activation of the SCell, the wireless device may trigger the PHR.

[0222] When a wireless device receives an SCell activation / deactivation MAC CE for deactivating an activated SCell, the wireless device may deactivate the activated SCell. In one embodiment, when a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires, the wireless device may deactivate the activated SCell. In response to the deactivation of the activated SCell, the wireless device may stop a first SCell timer associated with the activated SCell. In one embodiment, in response to the deactivation of the activated SCell, the wireless device may clear one or more configured downlink allocations and / or one or more configured uplink grants of configured uplink grant type 2 associated with the activated SCell. In one embodiment, in response to the deactivation of the activated SCell, the wireless device may interrupt one or more configured uplink grants of configured uplink grant type 1 associated with the activated SCell and / or may flush the HARQ buffer associated with the activated SCell.

[0223] When the SCell is deactivated, the wireless device may not perform operations including transmitting SRS on the SCell, reporting CQI / PMI / RI / CRI of the SCell, transmitting on the UL-SCH on the SCell, transmitting on the RACH on the SCell, monitoring at least one first PDCCH on the SCell, monitoring at least one second PDCCH of the SCell, and / or transmitting PUCCH on the SCell. When at least one first PDCCH on the activated SCell indicates an uplink grant or a downlink assignment, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In one embodiment, when at least one second PDCCH on a serving cell (e.g., a PCell or an SCell configured using PUCCH, i.e., a PUCCH SCell) that is scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In one embodiment, when the SCell is deactivated and there is an ongoing random access procedure on the SCell, the wireless device may abort the ongoing random access procedure on the SCell.

[0224] FIG. 21A shows an example of a 1-octet SCell activation / deactivation MAC CE. A first MAC PDU subheader having a first LCID (e.g., "111010" as shown in FIG. 19) can identify a 1-octet SCell activation / deactivation MAC CE. The size of the 1-octet SCell activation / deactivation MAC CE can be constant. The 1-octet SCell activation / deactivation MAC CE may include a single octet. The single octet can include a first number of C fields (e.g., 7) and a second number of R fields (e.g., 1). FIG. 21B shows an example of a 4-octet SCell activation / deactivation MAC CE. A second MAC PDU subheader having a second LCID (e.g., "111001" as shown in FIG. 19) can identify a 4-octet SCell activation / deactivation MAC CE. The size of the 4-octet SCell activation / deactivation MAC CE can be constant. The 4-octet SCell activation / deactivation MAC CE can include 4 octets. The four octets can include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., 1).

[0225] In FIG. 21A and / or FIG. 21B, when a SCell having a SCell index i is configured, the C i field may indicate the activation / deactivation status of the SCell having the SCell index i. In one embodiment, when the C i field is set to 1, the SCell having the SCell index i can be activated. In one embodiment, when the C i field is set to zero, the SCell having the SCell index i can be deactivated. In one embodiment, if there is no SCell configured using the SCell index i, the wireless device may ignore the C i field. In FIG. 21A and FIG. 21B, the R field may indicate reserved bits. The R field can be set to zero.

[0226] The base station (gNB) can configure the wireless device (UE) using the uplink (UL) bandwidth part (BWP) and the downlink (DL) BWP to enable bandwidth adaptation (BA) on the primary cell (PCell). When carrier aggregation is configured, the gNB can further configure the UE using at least the DL BWP to enable BA on the secondary cell (SCell) (i.e., there may be no UL BWP for UL). For the PCell, the initial active BWP can be the first BWP used for initial access. For the SCell, the first active BWP can be the second BWP configured for the UE to operate on the SCell when the SCell is activated. In paired spectrum (e.g., FDD), the gNB and / or the UE can switch the DL BWP and the UL BWP individually. In unpaired spectrum (e.g., TDD), the gNB and / or the UE can switch the DL BWP and the UL BWP simultaneously.

[0227] In one embodiment, the gNB and / or UE can switch between BWPs configured by a DCI or a BWP Inactive Timer. When the BWP Inactive Timer is configured for a serving cell, the gNB and / or UE can switch the active BWP to the default BWP in response to the expiration of the BWP Inactive Timer associated with the serving cell. The default BWP can be configured by the network. In one embodiment, in the case of an FDD system, when configured by BA, one UL BWP and one DL BWP for each uplink carrier can be active simultaneously in an active serving cell. In one embodiment, in the case of a TDD system, one DL / UL BWP pair can be active simultaneously in an active serving cell. Operating with one UL BWP and one DL BWP (or one DL / UL pair) can improve the battery consumption of the UE. BWPs other than one active UL BWP and one active DL BWP that the UE can operate on can be stopped. In a stopped BWP, the UE may not need to monitor the PDCCH and / or may not need to transmit on the PUCCH, PRACH, and UL-SCH.

[0228] In one embodiment, the serving cell may be composed of up to a first number (e.g., four) of BWPs. In one embodiment, for an activated serving cell, there may be one active BWP at any given time. In one embodiment, BWP switching can be used to activate an inactive BWP and deactivate the active BWP at once for the serving cell. In one embodiment, BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink grant. In one embodiment, BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). In one embodiment, BWP switching may be controlled by a MAC entity in response to the start of a random access procedure. When adding a SpCell or activating an SCell, one BWP may first become active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP of the serving cell can be indicated by RRC and / or PDCCH. In one embodiment, for unpaired spectrum, a DL BWP can be paired with a UL BWP, and BWP switching can be common to both UL and DL.

[0229] FIG. 22 shows an example of BWP switching on a SCell. In one example, the UE can receive an RRC message including the parameters of the SCell and one or more BWP configurations associated with the SCell. The RRC message can include an RRC connection reconfiguration message (e.g., RRCReconfiguration), an RRC connection re-establishment message (e.g., RRCRestablishment), and / or an RRC connection setup message (e.g., RRCSetup). Among the one or more BWPs, at least one BWP can be configured as a first active BWP (e.g., BWP1), and one BWP can be configured as a default BWP (e.g., BWP0). The UE can receive a MAC CE and activate the SCell in the nth slot. The UE can start a SCell deactivation timer (e.g., sCellDeactivationTimer), start CSI-related actions for the SCell, and / or start CSI-related actions for the first active BWP of the SCell. In response to activating the SCell, the UE can start monitoring the PDCCH on BWP1.

[0230] In one example, in response to receiving a DCI indicating a DL assignment on BWP1, the UE can start / restart a BWP inactivity timer (e.g., bwp-InactivityTimer) in the mth slot. In the s-th slot, if the BWP deactivation timer expires, the UE can switch back to the default BWP (e.g., BWP0) as the active BWP. When the sCellDeactivationTimer expires, the UE can stop the SCell and / or stop the BWP inactivity timer.

[0231] In one embodiment, the MAC entity can apply normal operations, including transmitting on the UL-SCH, transmitting on the RACH, monitoring the PDCCH, transmitting on the PUCCH, receiving the DL-SCH, and / or (re)initializing, if any, the configured uplink grant of permitted type 1 interrupted according to the stored configuration, on the active BWP of the activated serving cell configured by the BWP.

[0232] In one embodiment, on the inactive BWP of each activated serving cell configured by the BWP, the MAC entity may not transmit on the RACH, may not monitor the PDCCH, may not transmit on the PUCCH, may not transmit the SRS, may not receive the DL-SCH, may clear any configured downlink allocation and configured uplink grant of permitted type 2, and / or may interrupt any configured uplink grant of type 1.

[0233] In one embodiment, when the MAC entity receives a PDCCH for BWP switching of a serving cell, the UE may perform the BWP switching to the BWP indicated by the PDCCH while the random access procedure associated with this serving cell is not in progress. In one embodiment, when the bandwidth part indicator field is configured with DCI format 1_1, the bandwidth part indicator field value can indicate the active DL BWP from the configured DL BWP set for DL reception. In one embodiment, when the bandwidth part indicator field is configured with DCI format 0_1, the bandwidth part indicator field value can indicate the active UL BWP from the configured UL BWP set for UL transmission.

[0234] In one embodiment, for a primary cell, the UE may be provided with the default DL BWP among the DL BWPs configured for the UE by the higher layer parameter Default-DL-BWP. In one embodiment, if the default DL BWP is not provided to the UE by the higher layer parameter Default-DL-BWP, the default DL BWP may be the initial active DL BWP. In one embodiment, the UE may be provided by the higher layer parameter bwp-InactivityTimer, which is the timer value of the primary cell. When configured, the UE can increment the timer every 1 millisecond interval in frequency range 1 and every 0.5 millisecond interval in frequency range 2 when it is running, which is the case when the UE cannot detect DCI format 1_1 for the paired spectrum operation, or when the UE cannot detect DCI format 1_1 or DCI format 0_1 for the unpaired spectrum operation during the interval.

[0235] In one embodiment, when the UE is configured for a secondary cell using the higher layer parameter Default-DL-BWP that indicates the default DL BWP among the configured DL BWPs, and the UE is configured using the higher layer parameter bwp-InactivityTimer that indicates the timer value, the UE procedure on the secondary cell may be the same as that on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0236] In one embodiment, when the UE is configured on a secondary cell or carrier by the higher layer parameter Active-BWP-DL-SCell, which is the first active DL BWP, and by the higher layer parameter Active-BWP-UL-SCell, which is the first active UL BWP, the UE can use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or on the carrier.

[0237] In one embodiment, a set of PDCCH candidates for a wireless device to monitor is defined from the perspective of a PDCCH search space set. The search space set includes a CSS set or a USS set. The wireless device monitors PDCCH candidates in one or more of the following search space sets.A set of Type0-PDCCHCSS configured by pdcch-ConfigSIB1 in MIB, or searchSpaceSIB1 in PDCCH-ConfigCommon, or searchSpaceZero in PDCCH-ConfigCommon for DCI format, having a CRC scrambled by SI-RNTI in the MCG primary cell; a set of Type0A-PDCCHCSS configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for DCI format, having a CRC scrambled by SI-RNTI in the MCG primary cell; a set of Type1-PDCCHCSS configured by ra-SearchSpace in PDCCH-ConfigCommon for DCI format, having a CRC scrambled by RA-RNTI or TC-RNTI in the primary cell; a set of Type2-PDCCHCSS configured by pagingSearchSpace in PDCCH-ConfigCommon for DCI format, having a CRC scrambled by P-RNTI in the MCG primary cell; a set of Type3-PDCCHCSS configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI format, having a CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, and in the case of the primary cell only, C-RNTI, MCS-C-RNTI, or CS-RNTI; and a set of USS configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI format, having a CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI.

[0238] In one embodiment, the wireless device determines PDCCH monitoring opportunities on an active DL BWP based on one or more PDCCH configuration parameters including PDCCH monitoring periodicity, PDCCH monitoring offset, and PDCCH monitoring pattern within a slot. For a search space set (SSs), the wireless device determines that the PDCCH monitoring opportunity exists within a slot having

Number

Number

Number

Number

Number

[0239] In an embodiment, for a search space set s associated with CORESETp, [Number] as the carrier indicator field value n CI the slot of the active DL BWP of the serving cell corresponding to [Number] the PDCCH candidates of the search space set within [Number] determine the CCE index of aggregation level L corresponding to. Here, for any CSS [Number] for USS [Number] for pmod3 = 0, A p = 39827, for pmod3 = 1, A p = 39829, for pmod3 = 2, A p = 39839, and D = 65537; i = 0,..., L - 1; N CCE,p is the number of CCEs numbered from 0 to N p in CORESET CCE,p - 1; n CI is the carrier indicator field value when the wireless device is configured by the carrier indicator field in the CrossCarrierSchedulingConfig of the serving cell where the PDCCH is monitored; otherwise, for any CSS, n CI = 0 is included; [Number] wherein, [Number] is the number of PDCCH candidates configured to monitor for a given aggregation level L of a search space set s of serving cells corresponding to n CI ; for any CSS

Number

Number

Number

[0240] In one example, the UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set that includes multiple search spaces (SS). The UE may monitor a set of PDCCH candidates within one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in a common SS, and / or number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding.

[0241] FIG. 23 shows an embodiment of the configuration of the SS. In one embodiment, one or more SS configuration parameters of the SS may include at least one of the SS ID (searchSpaceId), control resource set ID (controlResourceSetId), monitoring slot periodicity and offset parameter (monitoringSlotPeriodicityAndOffset), value of the SS period (period), monitoring symbols within the slot (monitoringSymbolsWithinSlot), number of candidates for aggregation level two (nrofCandidates), and / or SS type (searchSpaceType) indicating a common SS type or UE-specific SS type. The monitoring slot periodicity and offset parameter may indicate the slot (e.g., within a radio frame) and slot offset (e.g., related to the start of the radio frame) for PDCCH monitoring. The monitoring symbols within the slot may indicate which symbols of the slot the radio device may monitor the PDCCH on the SS. The control resource set ID may identify the control resource set where the SS may be located.

[0242] FIG. 24 shows an example of the configuration of a control resource set (CORESET). In one example, the base station can send one or more configuration parameters of the CORESET to the wireless device. The configuration parameters can include at least one of a CORESET ID that identifies the CORESET, a frequency resource indication, a period parameter indicating the number of symbols of the CORESET, a CCE-REG mapping type indicator, a plurality of TCI states, an indicator indicating whether the TCI is present in the DCI, and the like. The frequency resource indication including the number of bits (e.g., 45 bits) indicates the frequency domain resources, each bit of the indication corresponds to a group of 6 RBs, and the grouping starts from the first RB group in the BWP of the cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit corresponds to the first RB group of the BWP, and so on. A bit set to 1 indicates that the RB group corresponding to that bit belongs to the frequency domain resources of this CORESET. Bits corresponding to RB groups that are not fully included in the BWP in which the CORESET is configured are set to zero.

[0243] FIG. 25A shows an example of a flowchart of data reception in a wireless device. In one example, the wireless device receives one or more RRC messages including the configuration parameters of the cell, and the cell includes one or more BWPs. The configuration parameters indicate one or more CORESETs and / or one or more search spaces (SS) configured on a BWP having one or more BWPs. The one or more CORESETs and / or the one or more SSs can be implemented as the examples in FIG. 23 and / or FIG. 24.

[0244] As shown in FIG. 25A, based on one or more RRC messages, a wireless device may monitor PDCCH candidates on one or more SSs of one or more CORESETs of an active BWP to detect DCI indicating a downlink allocation for the PDSCH. Monitoring of PDCCH candidates on an SS may include attempting to decode the DCI content of the PDCCH candidates having one or more PDCCH monitoring positions, one or more CCEs based on an aggregation level, a plurality of PDCCH candidates, and one or more DCI formats. The one or more RRC messages may indicate the number of PDCCH candidates for each aggregation level on the SS. The wireless device may determine the number of CCEs for each aggregation level for detecting DCI. In one embodiment, the wireless device may determine one CCE for detecting DCI when the aggregation level is 1, two CCEs when the aggregation level is 2, four CCEs when the aggregation level is 4, eight CCEs when the aggregation level is 8, and 16 CCEs when the aggregation level is 16. FIG. 25B shows an example of CCEs and REGs on a BWP.

[0245] In one embodiment, the wireless device determines that the PDCCH monitoring opportunity is

Number

Number

Number

Number

Number

[0246] As shown in Figure 25A, when monitoring PDCCH candidates on the SS, the wireless device may receive (or successfully decode) DCI on one or more CCEs. One or more CCEs may start from the starting CCE index. The DCI may include a time resource indicator for downlink allocation, a frequency resource indicator for downlink allocation, a PUCCH resource indicator (PRI), and a PDSCH-to-HARQ_feedback timing indicator.

[0247] In response to receiving the DCI, the wireless device may receive symbols of a transport block (TB) via the downlink allocation. The wireless device may attempt to decode the TB based on the received symbols. The wireless device may generate an acknowledgement (ACK) in response to successful decoding. The wireless device may generate a negative acknowledgement (NACK) in response to unsuccessful decoding.

[0248] In one embodiment, the wireless device may transmit ACK / NACK via the PUCCH resource at a time determined based on the value of the PDSCH-to-HARQ_feedback timing indicator. The wireless device may determine the PUCCH resource based on the PRI of the DCI, the starting CCE index of the one or more CCEs on which the wireless device receives the DCI, the cell index of the cell in which the wireless device monitors the PDCCH candidate, and the RNTI value for receiving the DCI.

[0249] Figure 25B shows an example of PUCCH resource determination. In one example, a wireless device can receive one or more RRC messages including configuration parameters of a BWP with a bandwidth, including the BWP of the cell and one or more wireless resource units (e.g., RBs as shown in FIG. 8). The configuration parameters may indicate the resource allocation of one or more CORESETs. The CORESET is within the frequency domain

Number

Number

Number

[0250] In one embodiment, the wireless device may monitor PDCCH candidates of SSs on one or more CCEs having the RBG of the CORESET on the active BWP. A CCE may include a plurality (e.g., 6) of resource element groups (REGs). A REG may include one RB in one OFDM symbol. The REGs within the CORESET are numbered in ascending order in a first-in-time manner starting from 0 with respect to the first OFDM symbol and the resource block with the smallest number within the CORESET. In one embodiment, the CORESET is composed of one CCE-REG mapping indicator.

[0251] In one embodiment, the CCE-REG mapping of the CORESET may be interleaved or non-interleaved and is described by a REG bundle: - REG bundle i is

Number

Number

Number

[0252] In one embodiment, for non-interleaved CCE-REG mapping, L = 6 and f (x) = x. In one embodiment, for interleaved CCE-REG mapping,

Number

Number

Number

Number

Number

Number

[0253] In one embodiment, the set of PDCCH candidates for the UE to be monitored is defined with respect to the PDCCH search space set. The search space set can be a CSS set or a USS set. The UE monitors PDCCH candidates in one or more of the following search space sets: - For DCI formats having CRC scrambled by SI-RNTI on the primary cell of the MCG, the Type0-PDCCH PDCCH CSS set configured by pdcch-ConfigSIB1 in the MIB, or by searchSpaceSIB1 in PDCCH-ConfigCommon, or by searchSpaceZero in PDCCH-ConfigCommon; - For DCI formats having CRC scrambled by SI-RNTI on the primary cell of the MCG, the Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon; - For DCI formats having CRC scrambled by RA-RNTI or TC-RNTI on the primary cell, the Type1-PDCCH PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon; - For a DCI format having a CRC scrambled by a P-RNTI on the primary cell of the MCG, a Type2-PDCCH PDCCH CSS set configured by the packingSearchSpace within PDCCH-ConfigCommon; - For a DCI format having a CRC scrambled by an INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, and only for the primary cell, a C-RNTI, MCS-C-RNTI, RNTI, or CS-RNTI, a Type3-PDCCH CSS set configured by the SearchSpace within PDCCH-Config with searchSpaceType = common, and - For a DCI format having a CRC scrambled by a C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI, a USS set configured by the SearchSpace within PDCCH-Config with searchSpaceType = ue-Specific.

[0254] In an embodiment, a wireless device, for a search space set s associated with CORESETp,

Number

Number

Number

Number

Number

Number

Number

Number

Number

[0255] FIG. 25B shows that the BWP of a cell may include M RBGs indexed from RBG 0 to RBG M-1. The CORESET configured on the BWP may occupy a plurality of RBGs of the M RBGs based on a bitmap (e.g., frequencyDomain Resources). Bit 0, which corresponds to RBG 0 and is set to 1, may indicate that RBG 0 belongs to a CORESET or the like, and the same applies hereinafter. The radio resources of the number of RBGs may be mapped to the number of CCEs indexed from CCE0 to CCE(N-1) based on a plurality of CCEs and a CCE~REG mapping indicator (e.g., CCE~REG-MappingType). The radio device may monitor PDCCH candidates of SS on a subset of the number of CCEs, including, for example, CCE2, CCE4, CCE6, etc.

[0256] In one embodiment, the radio device may receive DCI on the SS starting from CCE2 based on the above equation. The radio device may determine a PUCCH resource for HARQ-ACK feedback based on the PRI value of the DCI and the starting CCE index (e.g., CCE2 in the example of FIG. 25B).

[0257] In one embodiment, the radio device may not have a dedicated PUCCH resource configuration. The radio device may determine a PUCCH resource set based on a pre-defined PUCCH resource table to transmit HARQ-ACK information on the PUCCH. The PUCCH resource set includes 16 resources, each corresponding to a PUCCH format, a starting symbol, a period, a PRB offset, and a periodic shift index set for PUCCH transmission.

[0258] In one embodiment, the radio device may determine a PUCCH resource having an index r PUCCH where 0≦r

Number

[0259] In one embodiment, the wireless device can be configured with a dedicated PUCCH resource configuration by a higher layer. In one embodiment, the PUCCH resource can include a PUCCH resource index (e.g., provided by the pucch - resource ID), the index of the first PRB before frequency hopping by startingPRB, or without frequency hopping, the index of the first PRB after frequency hopping by secondHopPRB, indication of intra - slot frequency hopping by intraSlotFrequencyHopping, and / or the configuration for the PUCCH format, through PUCCH format 0 to PUCCH format 4.

[0260] In one embodiment, when the wireless device transmits HARQ - ACK information on the PUCCH in response to the detection of the last DCI (e.g., DCI format 1_0 or DCI format 1_1) in PDCCH reception among a plurality of DCIs having the value of the PDSCH - to - HARQ_feedback timing indicator field indicating the same slot for PUCCH transmission, the wireless device determines the PUCCH resource from the set of PUCCH resources (the first set when composed of a plurality of sets of PUCCH resources) as PUCCH , 0 ≦ r PUCCH ≦ R PUCCH −1.

Number

[0261] In one embodiment, the wireless device may transmit one or more uplink control information (UCI) to the base station via one or more PUCCH resources. The one or more UCI may include at least one of HARQ-ACK information, scheduling request (SR), and / or CSI report. In one embodiment, the PUCCH resource may be identified at least by a frequency position (e.g., starting PRB) and / or a PUCCH format. The PUCCH format may be configured using an initial periodic shift value of a base sequence and a time domain position parameter (e.g., starting symbol index). In one embodiment, the PUCCH format may be at least one of PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, or PUCCH format 4. PUCCH format 0 has a length of 1 or 2 OFDM symbols and may be 2 bits or less. PUCCH format 1 occupies 4 to 14 OFDM symbols and may be 2 bits or less. PUCCH format 2 occupies 1 or 2 OFDM symbols and may be greater than 2 bits. PUCCH format 3 occupies 4 to 14 OFDM symbols and may be greater than 2 bits. PUCCH format 4 occupies 4 to 14 OFDM symbols and may be greater than 2 bits. The PUCCH resource may be configured on the PCell or on the PUCCH secondary cell.

[0262] In one embodiment, when composed of a plurality of UL BWPs, the base station may transmit, to the wireless device, one or more RRC messages including configuration parameters of one or more PUCCH resource sets (e.g., 1, 2, 3, 4, or greater than 4), on the UL BWP of the plurality of UL BWPs. Each PUCCH resource set may be configured using a PUCCH resource set index, a list of PUCCH resources where each PUCCH resource is identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the maximum number of UCI information bits that the wireless device can use to transmit using one of the lists of a plurality of PUCCH resources within the PUCCH resource set.

[0263] In one embodiment, when configured using one or more PUCCH resource sets, the wireless device may select one of the one or more PUCCH resource sets based on the bit length of the UCI information bits (e.g., HARQ-ARQ bits, SR, and / or CSI) that the wireless device can transmit. In one embodiment, when the bit length of the UCI information bits is 2 or less, the wireless device may select a first PUCCH resource set having a PUCCH resource set index equal to "0". In one embodiment, when the bit length of the UCI information bits is greater than 2 and less than or equal to a first configured value, the wireless device may select a second PUCCH resource set having a PUCCH resource set index equal to "1". In one embodiment, when the bit length of the UCI information bits is greater than the first configured value and less than or equal to a second configured value, the wireless device may select a third PUCCH resource set having a PUCCH resource set index equal to "2". In one embodiment, when the bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1706), the wireless device may select a fourth PUCCH resource set having a PUCCH resource set equal to "3".

[0264] In one embodiment, the wireless device may determine a PUCCH format from a plurality of PUCCH formats including PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, and / or PUCCH format 4 based on the number of uplink symbols for UCI transmission and the number of UCI bits. In one embodiment, if the transmission is more than 1 symbol or 2 symbols and the number of HARQ-ACK information bits having positive or negative SR (HARQ-ACK / SR bits) is 1 or 2, the wireless device may transmit UCI on a PUCCH using PUCCH format 0. PUCCH format 0 may be based on DFT-spread OFDM, for example, to reduce cubic meters. In one embodiment, if the transmission is more than 4 symbols and the number of HARQ-ACK / SR bits is 1 or 2, the wireless device may transmit UCI on a PUCCH using PUCCH format 1. PUCCH format 1 may be based on DFT-spread OFDM, for example, to reduce cubic meters. In one embodiment, if the transmission is more than 1 symbol or 2 symbols and the number of UCI bits is more than 2, the wireless device may transmit UCI on a PUCCH using PUCCH format 2. PUCCH format 2 may be based on OFDM. In one embodiment, if the transmission is more than 4 symbols, the number of UCI bits is more than 2, and the PUCCH resource does not include an orthogonal cover code, the wireless device may transmit UCI on a PUCCH using PUCCH format 3. PUCCH format 3 may be based on DFT-spread OFDM, for example, to reduce cubic meters. In one embodiment, if the transmission is more than 4 symbols, the number of UCI bits is more than 2, and the PUCCH resource includes an orthogonal cover code, the wireless device may transmit UCI on a PUCCH using PUCCH format 4. PUCCH format 4 may be based on DFT-spread OFDM, for example, to reduce the cube.

[0265] In one embodiment, to transmit HARQ-ACK information on a PUCCH resource, a wireless device may determine a PUCCH resource from a PUCCH resource set. The PUCCH resource set may be determined as described above. The wireless device may determine the PUCCH resource based on a PUCCH resource indicator field in DCI received by PDCCH (for example, having DCI for DCI format 1_0 or 1_1). The 3-bit PUCCH resource indicator field in the DCI may indicate one of eight PUCCH resources within the PUCCH resource set. The wireless device may transmit HARQ-ACK information on the PUCCH resource indicated by the 3-bit PUCCH resource indicator field of the DCI.

[0266] FIG. 26 shows an example of mapping of PUCCH resource indication (PRI) field values to PUCCH resources in a PUCCH resource set (for example, having up to eight PUCCH resources). In one embodiment, when the PUCCH resource indicator of DCI (for example, DCI format 1_0 or 1_1) is '000', the wireless device may determine the PUCCH resource identified by a PUCCH resource identifier (for example, pucch-Resourdceid) having the first value in the PUCCH resource list of the PUCCH resource set. When the PUCCH resource indicator in DCI (for example, DCI format 1_0 or 1_1) is '001', the wireless device may determine the PUCCH resource identified by a PUCCH resource identifier (for example, pucch-Resourdceid) having the second value in a PUCCH resource list such as the PUCCH resource set. Similarly, to transmit HARQ-ACK information, SR and / or CSI multiplexed on the PUCCH, the wireless device may determine the PUCCH resource from a list of PUCCH resource sets, based at least on the PUCCH resource indicator of DCI (for example, DCI format 1_0 / 1_1).

[0267] In an exemplary embodiment, Listen-before-talk (LBT) can be implemented for transmission in a cell configured in an unlicensed band (for convenience, it is called, for example, an LAA cell and / or an NR-U cell. An LAA cell and an NR-U cell can be compatible and refer to any cell operating in an unlicensed band. The cell can operate as a non-standalone with an anchor cell in a licensed band, or as a standalone without an anchor cell in a licensed band.). LBT can include a clear channel assessment. For example, in the LBT procedure, a device can apply a clear channel assessment (CCA) check before using the channel. For example, CCA can include at least energy detection to determine the presence (e.g., the channel is occupied) or absence (e.g., the channel is clear) of other signals on the channel. Regulations in a certain country may affect the LBT procedure. For example, in the regulations of Europe and Japan, the use of LBT in an unlicensed band, such as the unlicensed band of 5 GHz, is mandatory. Apart from regulatory requirements, carrier sensing via LBT is one way to fairly share unlicensed spectrum.

[0268] In an exemplary embodiment, discontinuous transmission on an unlicensed carrier with a limited maximum transmission duration may be enabled. Some of these features may be supported by one or more signals transmitted from the start of discontinuous downlink transmission in an unlicensed band, and channel reservation may be enabled by transmission of a signal by an NR-U node after obtaining channel access based on a successful LBT operation or in response thereto. Other nodes may receive a signal (e.g., transmitted for channel reservation) at an energy level above a specific threshold at which they can sense that the channel is occupied. Features that need to be supported by one or more signals for operation in an unlicensed band with discontinuous downlink transmission may include one or more of the following. Detection of downlink transmission in an unlicensed band (including cell identification) by a wireless device, time and frequency synchronization of the wireless device.

[0269] In an exemplary embodiment, for DL transmission and frame structure design for operation in an unlicensed band, subframe, (mini) slot, and / or symbol boundary alignment may be employed according to the carrier aggregation timing relationship across the serving cells aggregated by CA. This does not necessarily mean that the base station's transmission starts at subframe, (mini) slot, and / or symbol boundaries. License-free cell operation (e.g., LAA and / or NR-U) may support PDSCH transmission, for example, when not all OFDM symbols can be transmitted in a subframe according to LBT. Delivery of control information required for PDSCH may also be supported.

[0270] The LBT procedure can be adopted for fair and friendly coexistence between 3GPP systems (such as LTE and NR) and other operators and technologies operating in unlicensed spectrum. For example, a node attempting to transmit on an unlicensed spectrum carrier can perform a clear channel assessment to determine whether the channel is available for use (e.g., as part of one or more LBT procedures). The LBT procedure may include at least energy detection to determine whether the channel is being used. For example, regulatory requirements in some regions such as Europe specify an energy detection threshold such that when a node receives energy above this threshold, the node assumes the channel is not idle. The node may comply with such regulatory requirements and optionally use a threshold lower than the threshold specified by the regulatory requirements for energy detection. Radio access technologies (e.g., LTE and / or NR) may adopt a mechanism to adaptively change the energy detection threshold. For example, NR-U can adopt a mechanism to adaptively lower the energy detection threshold from an upper limit. The adaptation mechanism may not prevent static or semi-static setting of the threshold. In one embodiment, a Category 4 LBT (CAT4 LBT) mechanism or other type of LBT mechanism can be implemented.

[0271] Various examples of LBT mechanisms can be implemented. In one embodiment, for some signals, in some implementation scenario cases, in some situations, and / or at some frequencies, the LBT procedure may not be executed by the transmitting entity. In one embodiment, Category 1 (CAT1, e.g., without LBT) can be implemented in one or more cases. For example, a channel in an unlicensed band may be held by a first device (e.g., a base station for DL transmission), and a second device (e.g., a wireless device) may take over for transmission without performing CAT1 LBT. In one embodiment, Category 2 (CAT2, e.g., LBT without random backoff and / or one-shot LBT) can be implemented. The period for determining that the channel is idle can be decisive (e.g., by regulation). The base station may send an uplink grant indicating a type of LBT (e.g., CAT2 LBT) to the wireless device. CAT1 LBT and CAT2 LBT can be used for COT sharing. For example, the base station may send an uplink grant (respiratory uplink control information) including the type of LBT. For example, CAT1 LBT and / or CAT2 LBT in the uplink grant (or uplink control information) may indicate to the receiving device (e.g., the base station and / or the wireless device) to trigger COT sharing. In one embodiment, Category 3 (CAT3, e.g., LBT with random backoff using a fixed-size contention window) can be implemented. The LBT procedure can have the following procedure as one of its components. The transmitting entity can draw 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 used in the LBT procedure to determine the duration for which the channel is detected to be idle before the transmitting entity transmits on the channel. In one embodiment, Category 4 (CAT4, e.g., LBT with random backoff using a variable-size contention window) can be implemented.The transmitting entity can draw 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 transmitting entity can change the size of the contention window when drawing the random number N. The random number N is used in the LBT procedure to determine the duration during which the channel is sensed to be idle before the transmitting entity transmits on the channel.

[0272] In an unlicensed band, the type of LBT (CAT1, CAT2, CAT3, and / or CAT4) can be configured via control messages (RRC, MAC CE, and / or DCI) per cell. In one embodiment, the type of LBT (CAT1, CAT2, CAT3, and / or CAT4) can be configured via control messages (RRC, MAC CE, and / or DCI) per BWP. For example, the type of LBT (CAT1, CAT2, CAT3, and / or CAT4) can be determined based on at least the numerology configured in the BWP. In this case, BWP switching can change the type of LBT.

[0273] In one embodiment, the wireless device can employ uplink (UL) LBT. UL LBT may be different from, for example, downlink (DL) LBT (e.g., by using different LBT mechanisms or parameters). This is because NR-U UL may be based on scheduled access that affects the channel contention opportunities of the wireless device. Other considerations that motivate different UL LBTs include, but are not limited to, multiplexing of multiple wireless devices within a subframe (slot and / or mini-slot).

[0274] In one embodiment, the DL transmission burst can be a continuous (unicast, multicast, broadcast, and / or combinations thereof) transmission by a base station (e.g., one or more radio devices) on a carrier component (CC). The UL transmission burst can be a continuous transmission from one or more radio devices to a base station on the CC. In one embodiment, the DL transmission burst and the UL transmission burst on the CC in the unlicensed spectrum can be scheduled in a TDM manner on the same unlicensed carrier. To switch between the DL transmission burst and the UL transmission burst, LBT (e.g., CAT1 LBT, CAT2 LBT, CAT3 LBT, and / or CAT4 LBT) may be required. For example, at a certain moment, it can be part of the DL transmission burst or the UL transmission burst.

[0275] Channel Occupancy Time (COT) sharing can be adopted in radio access technologies (e.g., LTE and / or NR). COT sharing can be a mechanism for one or more wireless devices to share a channel sensed as idle by at least one of one or more wireless devices. For example, one or more first devices occupy a channel of LBT (e.g., based on CAT4 LBT, the channel is sensed as idle), and one or more second devices share it using LBT (e.g., 25us LBT) within the maximum COT (MCOT) limit. For example, the MOCT limit can be given for each priority class, logical channel priority, and / or wireless device specific. COT sharing can enable UL concessions in unlicensed bands. For example, the base station can send an uplink grant to a wireless device for UL transmission. For example, the base station can occupy a channel and send a control signal to one or more wireless devices indicating that the one or more wireless devices can use the channel. For example, the control signal may include an uplink grant and / or a specific LBT type (e.g., CAT1 LBT and / or CAT2 LBT). One or more wireless devices can determine COT sharing based on at least the uplink grant and / or a specific LBT type. The wireless device can perform UL transmission with a specific LBT (e.g., CAT2 LBT such as 25 us LBT) and dynamic grant and / or configured grant (e.g., type 1, Type2, autonomous UL) during a set period, for example, when 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, Type2, autonomous UL) can send uplink control information indicating COT sharing ((M)COT UL-DL switching). The start time of DL transmission in COT sharing triggered by a wireless device can be indicated by one or more methods. For example, one or more parameters in the uplink control information indicate the start time.For example, the resource configuration of the configured / activated grant by the base station may indicate a start time. For example, the base station may be permitted to perform a DL transmission after or in response to a UL transmission on the configured grant (e.g., type 1, type 2, and / or autonomous UL). There may be a delay (e.g., at least 4 milliseconds) between the uplink grant and the UL transmission. The delay may be predefined, semi-statically configured by the base station (via an RRC message), and / or dynamically indicated by the base station (e.g., via the uplink grant). The delay may not be considered during the COT period.

[0276] In one embodiment, the initial active DL / UL BWP may be, for example, 20 MHz (or approximately) for the first unlicensed band in an unlicensed band at 5 GHz. The initial active DL / UL BWP in one or more unlicensed bands may be similar (e.g., approximately 20 MHz in the unlicensed spectrum of 5 GHz and / or 6 GHz) if similar channelization is used in one or more unlicensed bands (e.g., by regulation). In the wideband case, the base station may configure a wideband having one or more BWPs. For example, in the case of 80 MHz, the base station may configure four BWPs, and each BWP may be configured with approximately 20 MHz. The active BWPs (DL and / or UL) may be switched between each other based at least on the BWP switching mechanism. For example, when the cell includes a single BWP, the base station may configure a wideband having one or more subbands. For example, in the case of 80 MHz, the base station may configure four subbands, and each subband may be configured with approximately 20 MHz. For example, the wireless device may perform LBT subbands by subbands and may transmit data via scheduled resources on one or more subbands where LBT indicates an idle state.

[0277] In one embodiment, carrier aggregation between a PCell composed of a licensed band and an SCell composed of an unlicensed band may be supported. In one embodiment, the SCell can have both DL and UL, or DL only. In one embodiment, dual connectivity between a PCell (e.g., an LTE cell) configured on a licensed band and a PSCell (e.g., an NR-U cell) configured on an unlicensed band may be supported. In one embodiment, stand-alone operation in an unlicensed band where all carriers are in one or more unlicensed bands may be supported. In one embodiment, a cell with DL of an unlicensed band and UL of a licensed band, or vice versa, may be supported. In one embodiment, dual connectivity between a PCell (e.g., an NR cell) on a licensed band and a PSCell (e.g., an NR-U cell) on an unlicensed band may be supported.

[0278] In one embodiment, the radio access technology (e.g., LTE and / or NR) operating bandwidth can be an integer multiple of 20 MHz if, for example, the absence of Wi-Fi in an unlicensed band (e.g., 5 GHz, 6 GHz, and / or sub-7 GHz) where the radio access technology (e.g., LTE and / or NR) is operating cannot be guaranteed (e.g., by regulation). In one embodiment, the wireless device can perform one or more LBTs in units of 20 MHz. In one embodiment, receiver-assisted LBT (e.g., an RTS / CTS type mechanism) and / or on-demand receiver-assisted LBT (e.g., a receiver-assisted LBT that is only enabled when necessary, for example) can be used. In one embodiment, techniques for enhancing spatial reuse can be used.

[0279] In one embodiment, a wideband carrier having a plurality of channels (sub-bands, SBs, RB sets, etc.) is supported in an unlicensed band. In one embodiment, there can be one active BWP within a carrier. A channel (sub-band, RB set, etc.) may include a plurality of RBs within the BWP for data / control signal transmission. In this specification, a channel may also be referred to as a sub-band, SB, RB set, etc. In one embodiment, a BWP with one or more channels can be activated. In one embodiment, when Wi-Fi absence cannot be guaranteed (e.g., due to regulations), LBT can be performed in 20 MHz units. In this case, there may be multiple parallel LBT procedures for this BWP. The actual transmission bandwidth can be affected by the SBs in the LBT success that can result in dynamic bandwidth transmission within this active wideband BWP.

[0280] In one embodiment, one or more active BWPs can be supported. To improve BWP utilization efficiency, the BWP bandwidth can be the same as the bandwidth of the SBs for LBT. For example, LBT can be performed on each BWP. The network can activate / deactivate the BWP based on the amount of data to be transmitted. In one embodiment, one or more non-overlapping BWPs can be activated for a wireless device within a wide component carrier that can be similar to carrier aggregation. To improve BWP utilization efficiency, the BWP bandwidth can be the same as the bandwidth of the SBs for LBT, i.e., LBT can be a carrier out on each BWP. When LBT on multiple SBs is successful, it is required that the wireless device has the ability to support one or more narrow RFs or wide RFs that may include one or more activated BWPs.

[0281] In one embodiment, a single wideband BWP can be activated for a wireless device within a component carrier. The bandwidth of the wideband BWP can be in units of the SB of LBT. For example, if the SB of LBT is 20 MHz in the 5 GHz band, the wideband BWP bandwidth may include a plurality of 20 MHz. The actual transmission bandwidth can be affected by the SB of LBT as a result of dynamic bandwidth transmission within this active wideband BWP and can be successful in LBT.

[0282] In one embodiment, in a wideband (e.g., 80 MHz) configuration on the BWP, the frequency resources of the SS (or CORESET) can be spread (or traversed) within the BWP. The frequency resources of the SS (or CORESET) can be limited within the SB of the BWP. The SB can be, for example, in units of 20 MHz for the LBT procedure in an NR-U cell. FIGS. 27A and 27B show two SS / CORESET configurations in the frequency domain of a BWP with multiple BWPs of a cell or a cell (in the case of a single BWP configured on the cell).

[0283] FIG. 27A shows an example of an SS / CORESET configuration in a BWP. In one embodiment, the frequency resource indication of the first SS or the first CORESET configuration can indicate the frequency resource dispersion on a plurality of RB groups within the BWP. The plurality of RB groups is not limited to or within the SB (e.g., 20 MHz) of the BWP. By dispersing the frequency resources within the BWP, the base station may be able to flexibly allocate PDCCH resources for different UEs or different signaling purposes (e.g., common or UE-specific).

[0284] FIG. 27B shows an example of an SS / CORESET configuration in a BWP. In one example, the frequency resource indication of the first SS or the first CORESET configuration indicates that the frequency resource is limited to the bandwidth (e.g., 20 MHz) of the first SB (SB0 in FIG. 27B) of the BWP. To maintain the capabilities of a UE with the same (or a similar) CORESET / SS configuration (e.g., up to 40 SS per cell, or up to 12 or 20 CORESETs per cell) as when operating in a licensed cell, the CORESET identified by the CORESET ID may be allocated with the same number of RBs (or RB groups) in each SB of the BWP. The same number of RBs (or RB groups) may be located at the same frequency position (e.g., relative to the start frequency position of each SB) in each SB of the BWP. As shown above, the pattern of mapping the CORESET to the RBs of an SB may be replicated for the mapping of the CORESET to other SBs of the BWP.

[0285] In one example, the BWP may include a plurality (e.g., 4) of LBT SBs (SBs, or sets of RBs), and each LBT SB occupies a plurality of RBs (or RB groups) of the BWP. The first LBT SB may overlap in the frequency domain with the second LBT SB. The first LBT SB may not overlap in the frequency domain with the second LBT SB.

[0286] In response to the frequency resources of the first CORESET being limited to the bandwidth of the SB of the BWP and being replicated to each SB of the BWP, the wireless device may monitor the PDCCH on the first SS of the first CORESET of one or more SBs (e.g., SB0, SB1 in FIG. 27B) of the plurality of SBs of the BWP based on configured or predefined rules. By confining the frequency resources of the CORESET within the bandwidth of the SB of the BWP, the robustness of signal transmission can be increased and / or the power consumption of the wireless device can be saved. In one embodiment, the base station may perform the LBT procedure according to the SB of the BWP. In response to the LBT procedure succeeding on one of the SBs of the BWP, the base station may transmit DCI via PDCCH on one of the SBs of the BWP. In response to the LBT procedure succeeding on a plurality of SBs of the BWP, the base station may transmit DCI via PDCCH on a plurality of SBs of the BWP, or the base station may transmit a plurality of DCIs via PDCCH on a plurality of SBs of the BWP, and each DCI may be transmitted on a corresponding one of the plurality of SBs.

[0287] In one embodiment, the base station can allocate physical resource blocks (PRBs) confined within one of the SBs of the BWP corresponding to the CORESET for a search space set configuration associated with a plurality of monitoring positions in the frequency domain for the CORESET (e.g., in the high-layer parameter frequencyDomainResources of the CORESET in the RRC message as shown in FIG. 24). Within the search space set associated with the CORESET, each of the plurality of monitoring positions in the frequency domain corresponds to (and / or is limited to) the SB of the SB. Each of the plurality of monitoring positions may have a frequency domain resource allocation pattern replicated from the pattern configured by the CORESET. In an embodiment, CORESET parameters other than the frequency domain resource allocation pattern may be the same for each of the plurality of monitoring positions in the frequency domain.

[0288] In one embodiment, before receiving DCI, the wireless device does not need to recognize which SBs the base station can succeed in the LBT procedure on (for example, when the LBT procedure indicates that the channel is clear on the SB), and does not need to recognize which SBs the base station can transmit DCI on. When configured with a plurality of LBT SBs on the BWP, the wireless device may monitor the PDCCH on a plurality of SBs for receiving DCI.

[0289] In one embodiment, the base station may send one or more RRC messages including configuration parameters of the search space to the wireless device, and these configuration parameters indicate one or more SBs on which the wireless device can monitor the PDCCH candidates of the search space. The wireless device may monitor the PDCCH candidates associated with the search space on one or more SBs based on the configuration parameters.

[0290] In the existing technology, as shown in Figure 25B, the wireless device can index the CCEs from the first initial number (for example, 0) to the second number (for example, the maximum / total number set in the CORESET) of the radio resources of the CORESET on the BWP (or the cell if no BWP is set for the cell). The CCEs span the frequency resources of the BWP. The wireless device may monitor the PDCCH candidates of the SS for detecting DCI on one or more CCEs. The wireless device may receive DCI on at least one CCE among the one or more CCEs. The wireless device may determine the starting CCE of at least one CCE based on the CCE index, such as the starting CCE having the lowest CCE index among at least one CCE. The wireless device may determine the PUCCH resources for HARQ-ACK feedback based on at least one of the CCE index of the starting CCE of at least one CCE on which the wireless device receives DCI, the total number of CCEs, and the PRI of the DCI.

[0291] In an NR-U cell (or a BWP of a cell), a wireless device may monitor SS on one or more SBs of the BWP (or monitor PDCCH candidates of SS). In one embodiment, when the wireless device is permitted to transmit at most one DCI for data scheduling in the BWP, it may receive a DCI of one of the one or more SBs based on the LBT procedure at the base station. The wireless device can determine different PUCCH resources for UCI transmission when receiving DCI on different SBs of the BWP by introducing existing techniques. The wireless device can determine the PUCCH resources for UCI transmission such that the base station needs to allocate (or reserve) more PUCCH resources than the wireless device actually uses for UCI transmission by implementing existing techniques. This may reduce the system throughput and / or reduce the uplink resource utilization efficiency. Existing techniques may result in collisions of UCI transmissions on PUCCH (within the same wireless device or between different wireless devices), reduction of system throughput, increase of uplink transmission delay, and / or increase of power consumption. Therefore, it is necessary to improve the PUCCH resource allocation method for broadband NR-U in order to improve uplink resource utilization efficiency, system throughput, reduction of UCI transmission collisions, reduction of power consumption, etc.

[0292] In one of the exemplary embodiments, for each RB set of the BWP, the wireless device may index the CCEs of the CORESET starting from the same initial value (e.g., 0). In one example, the wireless device may index the CCEs of the CORESET in the first RB set of the BWP from 0 to N - 1, where N is the total number of CCEs of the CORESET in the RB set. The wireless device may index the CCEs of the CORESET in the second RB set of the BWP from 0 to N - 1. Based on indexing the CCEs of the CORESET from the same initial value for different RB sets of the BWP, the wireless device may determine the PUCCH resource based on the DCI, the PUCCH resource index indicated by the DCI for the wireless device, and the CCE index of the starting CCE of one or more CCEs that the wireless device receives, which is the total number of CCEs of the CORESET. Based on the exemplary embodiment, the wireless device may select / determine the same PUCCH resource regardless of which RB the wireless device receives the DCI on. The exemplary embodiment enables the base station to reduce the PUCCH resource allocation / reservation for the wireless device, and thus, can improve the uplink resource utilization efficiency.

[0293] FIG. 28 shows an exemplary embodiment of a PUCCH resource allocation / determination method for a wideband NR-U cell.

[0294] In one embodiment, the base station can send one or more RRC messages including the configuration parameters of a cell (e.g., a PCell or an SCell) to the wireless device. The cell may include multiple BWPs. The cell may include a single BWP. In one embodiment, a BWP may include multiple (e.g., 4) LBT SBs (a set of SBs or RBs that may be equally referred to herein), and each SB occupies multiple RBs (or RB groups) of the BWP. As shown in FIG. 28, the SBs of the BWP include SB0, SB1, SB2, etc. The configuration parameters may indicate multiple CORESETs configured on the BWP. The configuration parameters may indicate that for multiple CORESETs, the frequency resources of the CORESET are limited to the bandwidth of the SB of the BWP. The frequency resource mapping pattern of the CORESET on the first SB (e.g., which resource blocks of the first SB the CORESET is included in, as indicated by frequencyDomainResources in FIG. 24) is replicated to the remaining SBs of the BWP. The configuration parameters may indicate that multiple SSs are configured on the CORESET. For each SS of the multiple SSs, the configuration parameters may include a monitoring frequency position parameter (e.g., the bitmap shown in FIG. 28, or the monitoring position indication) indicating on which SB the monitoring frequency position of the SS is configured. As shown in FIG. 28, the monitoring position indication of the SS (e.g., SS i ) includes the bit string "110..." indicating the monitoring frequency positions including SB0 and SB1. In response to the monitoring frequency position including SB0 and SB1, the wireless device may monitor the SS i on SB0 and SB1, and may not monitor the SS i on the remaining SBs (e.g., SB2 and SB3).

[0295] In one embodiment, in response to monitoring the SS i on SB0 and SB1, the wireless device may monitor the DCI on the CCE of the SS i on SB0 and / or the SS iIt may attempt to detect DCI on the CCEs of the BWP (e.g., simultaneously or sequentially). The wireless device may index the CCEs on different SBs of the BWP from the same initial value (e.g., 0) to N - 1 (e.g., N is the total number of CCEs in the SB). Based on the indexing of the CCEs, the wireless device may attempt to detect the first DCI on CCE2, CCE4, CCE6,... in SB0 and the second DCI on CCE2, CC4, CCE6,... in SB1. Here, CCE2, CCE4, CCE6,... are determined for SS i as shown in the example of FIG. 25B.

[0296] In one embodiment, the wireless device may receive the first DCI on the CCEs of SS i on SB0 of the BWP. The wireless device may receive the second DCI on the CCEs of SS i on SB1 of the BWP. The wireless device may receive the first DCI and / or the second DCI based on the LBT procedure performed by the base station on SB0 and SB1. In one embodiment, the base station may transmit the first DCI on SB0 when the base station determines that the channel is clear on SB0 based on the LBT procedure performed on SB0. The base station may transmit the second DCI on SB1 when the base station determines that the channel is clear on SB1 based on the LBT procedure performed on SB1. Based on indexing the CCEs from the same initial value on different SBs, the wireless device may determine that the first start CCE on SB0 where the first DCI is received may have the same CCE index as the second start CCE on SB1 where the second DCI is received. The first DCI may indicate the same PRI value as the second DCI.

[0297] In response to receiving DCI (first DCI or second DCI), the wireless device may attempt to detect a TB based on the downlink allocation of the DCI. The wireless device may determine acknowledgment response information for the reception of the TB based on the detection of the TB. In one embodiment, the wireless device may determine that the acknowledgment response information includes an affirmative acknowledgment response (ACK) for the reception of the TB in response to detecting that the TB is successful. In one embodiment, the wireless device may determine that the acknowledgment response information includes a negative acknowledgment response (NACK) for the reception of the TB in response to detecting that the TB is not successful.

[0298] In one embodiment, the wireless device can determine a PUCCH resource for transmitting acknowledgment response information based on the starting CCE and the PR of the DCI by implementing the above exemplary embodiment with respect to FIGS. 25A and / or 25B. As shown in FIG. 28, the starting CCE may have a CCE index equal to 2 regardless of the SB in which the wireless device receives the DCI. By implementing the exemplary embodiment, the wireless device may determine the PUCCH resource based on the CCE index of the starting CCE, where the CCEs within the SB are indexed from the same initial value for each SB of the BWP. The wireless device may determine the PUCCH resource based on the CCE index of the starting CCE regardless of the SB in which the wireless device receives the DCI (first DCI or second DCI). Otherwise, based on the existing technology, the wireless device may determine different starting CCE indexes when receiving DCI on different SBs. Therefore, the wireless device may determine different PUCCH resources for the transmission of UCI based on different starting CCE indexes. The exemplary embodiment enables the base station to reduce the PUCCH resource allocation / reservation for the wireless device, and thus can improve the uplink resource utilization efficiency.

[0299] In an NR-U cell (or a BWP of a cell), a wireless device may monitor SS on one or more SBs of the BWP (or monitor PDCCH candidates of SS). The wireless device may receive multiple DCIs on multiple SBs of one or more SBs, and each DCI is received via a search space of a CORESET on each of the one or more SBs. The wireless device may receive multiple DCIs on multiple SBs when the base station succeeds in the LBT procedure for multiple SBs. When receiving multiple DCIs on multiple SBs, for example, when each DCI schedules a respective TB, the system throughput may increase. Based on existing technologies, the wireless device may determine the same PUCCH resource for HARQ-ACK transmission for different TBs scheduled by multiple DCIs. This may cause collisions of HARQ-ACK transmissions for different TBs. Therefore, existing technologies may result in collisions of UCI transmissions on PUCCH (within the same wireless device or between different wireless devices), a decrease in system throughput, an increase in uplink transmission delay, and / or an increase in power consumption. Therefore, it is necessary to improve the PUCCH resource allocation method for broadband NR-U in order to improve uplink resource utilization efficiency, system throughput, reduction of UCI transmission collisions, reduction of power consumption, etc.

[0300] FIG. 29 shows an example of a PUCCH resource determination mechanism when multiple PDCCH monitoring frequency positions on multiple SBs of a BWP are supported. In one example, the base station can send one or more RRC messages including configuration parameters of a cell (e.g., a PCell or an SCell) to the wireless device. The cell can include multiple BWPs. The cell may include a single BWP. In one example, a BWP may include multiple (e.g., 4) SBs, and each SB occupies multiple RBs (or RB groups) of the BWP. As shown in FIG. 29, the SBs of the BWP include SB0, SB1, etc. The configuration parameters may indicate multiple CORESETs configured on the BWP. The configuration parameters may indicate that the frequency resources of the CORESET are limited to the bandwidth of the SB of the BWP. The configuration parameters may indicate that multiple SSs are configured on the CORESET. For each SS of the multiple SSs, the configuration parameters may include a monitoring frequency position parameter (e.g., the bitmap or monitoring position indication shown in FIG. 29) indicating on which SB the monitoring frequency position of the SS is configured. As shown in FIG. 29, the monitoring position indication of the SS (e.g., SS i ) includes a bit string "110..." indicating the monitoring frequency positions including SB0, SB1, and each bit of the bit string indicates whether the corresponding SB should be monitored by the wireless device for the SS. In response to the monitoring frequency positions including SB0, SB1, the wireless device may monitor the SS i on SB0 and SB1 and may not monitor the SS i on other SBs of the BWP.

[0301] In one embodiment, the wireless device may index the CCEs of each CCE of the SB based on at least one of the SB index and the total number of CCEs of the CORESET. In one embodiment, the CORESET on SB0 may include the same total number of CCEs as on SB1. In the example of FIG. 29, the total number of CCEs of the CORESET is N. The wireless device may index the CCEs of the CORESET on SB0 from CCE0 (or CCE1) to CCEN-1 (or CCEN). The wireless device may index the i-th CCE of the CCEs of the CORESET on SBj as follows. When i starts from zero, N*(j - 1) + i. The wireless device may index the i-th CCE of the CCEs of the CORESET on SBj as follows. When i starts from 1, N*(j - 1) + i - 1. In one embodiment, the i-th CCE of the CCEs on SB0 and the i-th CCE of the CCEs on SBj may have different CCE indexes. If there are different CCE indexes for different SBs, the wireless device may be able to reduce the collision of PUCCH resources.

[0302] In one embodiment, the base station may transmit to the wireless device one or more RRC messages including configuration parameters of a BWP including a plurality of SBs. The configuration parameters indicate a CCE index offset (e.g., SB-specific) for each SB of the plurality of SBs with respect to a CCE. In one embodiment, the configuration parameters may indicate a first CCE_index_offset for a first SB, a second CCE_index_offset for a second SB, and so on. Based on the configuration parameters, the wireless device may index the i-th CCE on the first SB as the first CCE_index_offset + i, and may index the i-th CCE on the second SB as the second CCE_index_offset + i, and so on. The CCE index offset of each SB may be a cell-specific parameter or a UE-specific parameter. The base station may transmit the CCE index offset in the system information in response to the CCE index offset being a cell-specific parameter. The base station may transmit the CCE index offset in a UE-specific cell configuration message in response to the CCE index offset being a UE-specific parameter.

[0303] As shown in FIG. 29, the wireless device may attempt to detect DCI on the CCEs on SB0 and SB1. In one embodiment, the wireless device may attempt to detect a first DCI on CCE2, CCE4, CCE6,... on SB0, where CC2, CC4, CC6,... are determined with respect to SS i by implementing the embodiment of FIG. 25B. Based on monitoring CCE2, CCE4, CCE6,..., the wireless device may attempt to detect a second DCI on CCE(N + 2), CC(N + 4), CCE(N + 6),... on SB1.

[0304] As shown in FIG. 29, the wireless device may receive a first DCI on the CCE of SS i on SB0 of the BWP. The wireless device may receive SS iIt may receive a second DCI on the CCE. The first starting CCE of the CCEs on SB0 where the first DCI is received may have a first CCE index (e.g., 2 shown in FIG. 29). The second starting CCE of the CCEs on SB1 where the second DCI is received may have a second CCE index (e.g., N+2 shown in FIG. 29). The first starting CCE and the second starting CCE at the same location, in the order of the CCE indices on SB0 and SB1, may have different CCE indices. In one embodiment, the first DCI may indicate the same PRI value as the second DCI.

[0305] In response to receiving the first DCI, the wireless device may attempt to detect a first TB based on the first downlink assignment of the first DCI. The wireless device may determine first acknowledgment response information for the reception of the first TB based on the detection of the first TB. In one embodiment, the wireless device may determine that the first acknowledgment response information includes an acknowledgment (ACK) for the reception of the first TB in response to detecting that the first TB is successful. In one embodiment, the wireless device may determine that the first acknowledgment response information includes a negative acknowledgment (NACK) for the reception of the first TB in response to detecting that the first TB is not successful.

[0306] In response to receiving the second DCI, the wireless device may attempt to detect a second TB (or the first TB in the case of repetition) based on the second downlink assignment of the second DCI. The wireless device may determine second acknowledgment response information for the reception of the second TB based on the detection of the second TB. In one embodiment, the wireless device may determine that the second acknowledgment response information includes an ACK for the reception of the second TB in response to detecting that the second TB is successful. In one embodiment, the wireless device may determine that the second acknowledgment response information includes a NACK for the reception of the second TB in response to detecting that the second TB is not successful.

[0307] In one embodiment, the wireless device may determine a first PUCCH resource for transmitting first acknowledgment response information based on a first starting CCE and a first PRI of a first DCI. The wireless device may determine a second PUCCH resource for transmitting second acknowledgment response information based on a second starting CCE and a second PRI of the first DCI.

[0308] In one embodiment, if the wireless device does not have a dedicated PUCCH resource configuration, the wireless device may determine a first PUCCH resource, r PUCCH as

Number

[0309] As shown in FIG. 29, the wireless device may determine a second PUCCH resource, r PUCCH as

Number

[0310] In one embodiment, when the wireless device has a dedicated PUCCH resource configuration, the wireless device, based on the first starting CCE and the first PRI of the first DCI, selects the first PUCCH resource, r PUCCH (e.g., 0 ≦ r PUCCH ≦ R PUCCH −1), from

Number

[0311] In one embodiment, the wireless device, based on the second starting CCE and the second PRI of the second DCI, selects the second PUCCH resource, r PUCCH (e.g., 0 ≦ r PUCCH ≦ R PUCCH −1), from

Number

[0312] As shown in FIG. 29, the wireless device may determine different PUCCH resources for ACK / NACK transmission for different TBs. According to an exemplary embodiment, the wireless device may reduce PUCCH transmission collisions and improve uplink transmission delay and system throughput.

[0313] In one example, the wireless device may index the CCEs of a certain SB among multiple SBs on the BWP independently and separately. The CCE index may be reused in different SBs. In one example, the wireless device may index the CCEs of the first SB from CCE0 to CCE(N - 1) and the CCEs of the second SB from CCE0 to CCE(N - 1). Reusing the CCE index on different SBs may improve the implementation complexity of the UE and / or backward compatibility.

[0314] In one example, when the wireless device reuses the CCE index in different SBs, the wireless device determines the PUCCH resource r based on the starting CCE, the SB index of the SB (e.g., SB0 or SB1), and the PRI of the DCI received in the SB. PUCCH as

Number

[0315] In one embodiment, when the wireless device re-uses the CCE index on different SBs, the wireless device is based on the starting CCE, the SB index of the SB (e.g., SB0 or SB1), and / or the PRI of the DCI received on the SB. A PUCCH resource is selected from a set of PUCCH resources (e.g., the first set when composed of a set of multiple PUCCH resources), r PUCCH , (e.g., 0 ≦ r PUCCH ≦ R PUCCH -1). In one embodiment, the wireless device sets r PUCCH to

Number

[0316] Wherein, N’ CCE,p = K * N CCE,p , N CCE,p is the total number of CCEs in CORESETp on the SB, K is the total number of SBs configured for the wireless device to monitor, n CCE,p is the CCE index of the starting CCE in CORESETp for receiving DCI on the SB, SB_index is the SB index of the SB on which the wireless device receives DCI, and Δ PRI is the value of the PRI field in the DCI. In one embodiment, when the total number of SBs is greater than 2, SB_index is

Number

[0317] FIG. 30 shows a flowchart of an example of a PUCCH resource determination mechanism. In one embodiment, the base station can transmit one or more RRC messages including cell configuration parameters to the wireless device (not shown in FIG. 30). The cell may include a plurality of BWPs. One of the plurality of BWPs may include a plurality of SBs. In one embodiment, the base station can transmit a command (e.g., DCI) indicating activation of a BWP to the wireless device. In response to receiving the command, the wireless device can activate the BWP. In response to activation of the BWP, the wireless device can monitor the SS of the CORESET on the first SB and the second SB, and can monitor the first SB and the second SB indicated by the configuration parameters. The base station can perform the LBT procedure for the first SB and the second SB sequentially or simultaneously.

[0318] In one embodiment, the base station may determine that the LBT procedure on the first SB indicates a clear channel on the first SB. In response to the LBT procedure indicating a clear channel on the first SB, the base station may transmit a first DCI to the wireless device via the first SB, and the first DCI may indicate a first downlink radio resource for downlink allocation for transmission of the first TB, and a first PUCCH resource for ACK / NACK transmission of the first TB. In one embodiment, the base station may determine that the LBT procedure on the second SB indicates a clear channel on the second SB. In response to the LBT procedure indicating a clear channel on the second SB, the base station may transmit a second DCI to the wireless device via the second SB, and the second DCI may indicate a second downlink radio resource for downlink allocation for transmission of the second TB (or the first TB in case of repetition) and a second PUCCH resource for ACK / NACK transmission of the second TB.

[0319] In one embodiment, the wireless device may receive a first DCI while monitoring the SS of the CORESET on the first SB, and receive a second DCI while monitoring the SS of the CORESET on the second SB. The wireless device may detect a first TB via a first downlink radio resource on the first SB based on the reception of the first DCI, and determine first acknowledgment response information for detecting the first TB. The wireless device may detect a second TB via a second downlink radio resource on the second SB based on the reception of the second DCI, and determine second acknowledgment response information for detecting the second TB.

[0320] In one embodiment, the wireless device may determine a first PUCCH resource for transmitting the first acknowledgment response information based on a first CCE index of a starting CCE of a CORESET for receiving the first DCI, an SB index of the first SB, and / or a PRI value indicated by the first DCI. In one embodiment, the wireless device may determine a second PUCCH resource for transmitting the second acknowledgment response information based on a second CCE index of a starting CCE of a CORESET for receiving the second DCI, an SB index of the second SB, and / or a PRI value indicated by the second DCI. The wireless device may determine the first PUCCH resource and / or the second PUCCH resource by implementing the example of FIG. 29. The wireless device may transmit a first acknowledgment response for the reception of the first TB via the first PUCCH resource. The wireless device may transmit a second acknowledgment response for the reception of the second TB via the second PUCCH resource.

[0321] FIG. 31 shows an example of PUCCH configuration when a plurality of SBs are supported in an NR-U system. In one embodiment, the base station can send one or more RRC messages including configuration parameters of a cell (e.g., a PCell or an SCell) to the wireless device. The cell may include a plurality of BWPs. The cell may include a single BWP. In one embodiment, a BWP may include a plurality (e.g., 4) of SBs, and each SB occupies a plurality of RBs (or RB groups) of the BWP. As shown in FIG. 31, the SBs of the BWP include SB0, SB1, SB2, etc. The configuration parameters may indicate a plurality of CORESETs configured on the BWP. The configuration parameters may indicate that the frequency resources of the CORESET are limited to the bandwidth of the SB of the BWP. The configuration parameters may indicate that a plurality of SSs are configured on the CORESET. For each SS of the plurality of SSs, the configuration parameters may include a monitoring frequency position parameter (e.g., the bitmap or monitoring position indication shown in FIG. 31) indicating on which SB the monitoring frequency position of the SS is configured. As shown in FIG. 31, the monitoring position indication of an SS (e.g., SS i ) includes a bit string "110..." indicating the monitoring frequency positions including SB0 and SB1. In response to the monitoring frequency position including SB0 and SB1, the wireless device may monitor the SS i on SB0 and SB1, and may not monitor the SS i on other SBs of the BWP.

[0322] In one embodiment, the wireless device may index the CCEs of a certain SB among the plurality of SBs on the BWP independently and separately. The CCE index may be reused in different SBs. In one embodiment, the wireless device can index the CCEs of the first SB (e.g., SB0) from CCE0 to CCE(N - 1) and the CCEs of the second SB (e.g., SB1) from CCE0 to CCE(N - 1). Reusing the CCE index on different SBs can improve the complexity of UE implementation and / or backward compatibility.

[0323] In one embodiment, the base station may transmit one or more RRC messages to the wireless device, including configuration parameters of the PUCCH resource configuration on the first BWP on the PCell or PUCCH SCell. In one embodiment, the configuration parameters of the PUCCH resource configuration may indicate a plurality of PUCCH resource sets. Each PUCCH resource set of the plurality of PUCCH resource sets may include a plurality of PUCCH resources. In one embodiment, the configuration parameters may indicate that a first subset of the number of PUCCH resources in a PUCCH resource set corresponds to a first SB of a plurality of SBs of the BWP of the cell (e.g., PCell or SCell), a second subset of the number of PUCCH resources corresponds to a second SB of the plurality of SBs of the BWP of the cell, and so on. As shown in FIG. 31, the PUCCH resources of a PUCCH resource set may include PUCCH resources having PUCCH resource indices 0, 1, 2, 3, 4,..., K−1, K+1,..., and M, where K may be the total number of PUCCH resources for the first SB. M may be the total number of PUCCH resources within the PUCCH resource set. K and / or M may be indicated in one or more RRC messages. In an embodiment, the configuration parameters may indicate that the PUCCH resources having PUCCH resource indices 0, 1,..., K−1 correspond to (or are associated with) the first SB. The configuration parameters may indicate that the PUCCH resources having PUCCH resource indices K, K+1,..., 2K−1 correspond to (or are associated with) the second SB. In one embodiment, the total number of PUCCH resources for the first SB (e.g., K) may be different from the total number of PUCCH resources for the second SB (e.g., J), where K and J are indicated in one or more RRC messages or set to predetermined values (e.g., 8, 16, 32, and any number greater than zero).

[0324] In one embodiment, the base station may transmit one or more RRC messages to the wireless device, including configuration parameters of the PUCCH resource configuration on the first BWP on the PCell or PUCCH SCell. In one embodiment, the configuration parameters of the PUCCH resource configuration may indicate a plurality of PUCCH resource sets. Each PUCCH resource set of the plurality of PUCCH resource sets may include a plurality of PUCCH resources. In one embodiment, the configuration parameters may indicate that the first PUCCH resource index offset corresponds to the first SB of the plurality of SBs of the BWP of the cell (e.g., PCell or SCell), the second PUCCH resource index offset corresponds to the second SB of the plurality of SBs of the BWP of the cell, and so on. In one embodiment, based on the reception of one or more RRC messages, the wireless device may determine the first PUCCH resource for the first acknowledgment response information for receiving the first TB via the first SB based on at least one of the first PUCCH resource index offset, the CCE index of the starting CCE for receiving the first DCI, and the PRI value indicated in the first DCI. In one embodiment, based on the reception of one or more RRC messages, the wireless device may determine the second PUCCH resource for the second acknowledgment response information for receiving the second TB via the second SB based on at least one of the second PUCCH resource index offset, the CCE index of the starting CCE of the CCE for receiving the second DCI, and the PRI value indicated in the second DCI.

[0325] As shown in FIG. 31, the wireless device may attempt to detect DCI on the CCEs on SB0 and SB1. In one embodiment, the wireless device may attempt to detect the first DCI on CCE2, CCE4, CCE6,... on SB0, where CC2, CC4, CC6,... implement the embodiment of FIG. 25B to determine for SS i with respect to. Based on the monitoring of CCE2, CCE4, CCE6,..., the wireless device may attempt to detect the second DCI on CCE2, CC4, CCE6,... on SB1.

[0326] As shown in FIG. 31, the wireless device may receive a first DCI on a CCE of an SS on SB0 of a BWP. i The wireless device may receive a second DCI on a CCE of an SS on SB1 of the BWP. The first starting CCE of the CCEs on SB0 where the first DCI is received may have the same CCE index (e.g., 2 as shown in FIG. 31) as the second starting CCE of the CCEs on SB1 where the second DCI is received. The first starting CCE of the CCEs on SB0 where the first DCI is received may have a different CCE index from the second starting CCE of the CCEs on SB1 where the second DCI is received. In one embodiment, the first DCI may indicate the same PRI value as the second DCI. i In one embodiment, based on the reception of the first DCI, the wireless device may detect a first TB via a first downlink radio resource on a first SB and determine first acknowledgment response information for detecting the first TB. Based on the reception of the second DCI, the wireless device may detect a second TB via a second downlink radio resource on a second SB and determine second acknowledgment response information for detecting the second TB.

[0327]

[0328] ​In one embodiment, the wireless device may determine a first PUCCH resource from a first subset of PUCCH resources (e.g., PUCCH resources having PUCCH resource indexes 0, 1, 2, ..., K-1 as shown in FIG. 31) corresponding to a first SB of a PUCCH resource set to transmit first acknowledgment response information based on a first starting CCE and a first PRI of a first DCI. The wireless device may determine a second PUCCH resource from a second subset of PUCCH resources (e.g., PUCCH resources having PUCCH resource indexes K, K+1, K+2, ..., 2*K-1 as shown in FIG. 31) corresponding to a second SB of the PUCCH resource set to transmit second acknowledgment response information based on a second starting CCE and a second PRI of the first DCI. The wireless device may determine the first PUCCH resource from the first subset of PUCCH resources by implementing the exemplary embodiment of FIG. 25B. The wireless device may determine the second PUCCH resource from the second subset of PUCCH resources by implementing the exemplary embodiment of FIG. 25B.

[0329] As shown in FIG. 31, the wireless device may determine different PUCCH resources from different subsets of PUCCH resources corresponding to different SBs for ACK / NACK transmissions for different TBs. By the exemplary embodiment, the wireless device may reduce PUCCH transmission collisions and improve uplink transmission delay and system throughput.

[0330] The exemplary embodiments of FIGS. 28, 29, and / or 31 can be implemented based on the configuration. In one example, when the wireless device and the base station support at most one DCI for data scheduling on a plurality of RB sets of a BWP, the base station and the wireless device may implement a PUCCH resource determination method based on the embodiment of FIG. 28. When the wireless device and the base station support a plurality of DCIs for data scheduling on a plurality of RB sets of a BWP and an uplink channel, and the uplink channel has a high load, the base station and the wireless device may implement a PUCCH resource determination method based on the example of FIG. 29. When the wireless device and the base station support a plurality of DCIs for data scheduling on a plurality of RB sets of a BWP and an uplink channel, and the uplink channel does not have a high load, the base station and the wireless device may implement a PUCCH resource determination method based on the example of FIG. 31.

[0331] In one example, the first DL SB of the plurality of DL SBs may be connected to the first UL SB of the plurality of UL SBs. The plurality of DL SBs may be included in the DL BWP of the cell. The plurality of UL SBs may be included in the UL BWP of the cell. In one example, the wireless device may receive DCI via the first DL SB of the plurality of DL SBs. The wireless device may determine the PUCCH resource on the first UL SB for ACK / NACK transmission based on the linkage between the first DL SB and the first UL SB.

[0332] In one example, the first wireless device may select the first UL SB from the plurality of UL SBs of the BWP for PUCCH transmission of ACK / NACK based on a selection priority. The selection priority may be indicated by an RRC message. The selection priority may be predefined. The selection priority may indicate the order of UL SB selection from the plurality of UL SBs. In one example, different UEs may be configured with different selection priorities. By setting different selection priorities, PUCCH collisions can be improved.

[0333] In one embodiment, the wireless device may monitor PDCCH on a CCE of an SB having a plurality of SBs of the BWP of the cell. The wireless device may receive DCI including a wireless resource indication and a PUCCH resource index via PDCCH on one or more CCEs of the CCE. The wireless device may receive a TB via the wireless resources indicated by the wireless resource indication. The wireless device may determine a PUCCH resource based on at least one of the PUCCH resource index, the SB index of the SB, and / or the CCE index of the starting CCE of one or more CCEs. The wireless device may transmit acknowledgment response information for receiving the TB via the PUCCH resource. The wireless device may further receive one or more RRC messages including configuration parameters of a cell including a plurality of BWPs, and each of the plurality of BWPs includes a plurality of SBs. Each of the plurality of SBs may be identified by its respective SB index. The configuration parameters of the cell further include first configuration parameters of a BWP having a plurality of BWPs, and the first configuration parameters include one or more wireless resource configuration parameters of a CORESET. One or more wireless resource configuration parameters of the CORESET may indicate that the frequency resources of the CORESET are limited to the bandwidth of the SB of the BWP. One or more wireless resource configuration parameters may indicate that the search space associated with the CORESET is configured with one or more monitoring frequency position indications. Each frequency position indication corresponding to each SB of one or more SBs of the plurality of SBs may indicate whether the wireless device monitors PDCCH for the search space on the SB. The frequency resources of the CORESET on the SB may include a plurality of CCEs, and each of the plurality of CCEs is identified by a CCE index. The CCE index of the first CCE of the plurality of CCEs may start from a first predetermined value (for example, 0 or 1).

[0334] In one embodiment, the wireless device may monitor PDCCH on the search space on the SB of the plurality of SBs in response to a monitoring frequency position indication corresponding to the SB indicating PDCCH monitoring on the SB for the search space.

[0335] In one embodiment, one or more RRC messages may further indicate a plurality of PUCCH resource sets, and each of the PUCCH resource sets includes a plurality of PUCCH resources. Each of the plurality of PUCCH resources may be identified by its respective PUCCH resource index. The wireless device may determine a PUCCH resource from among the plurality of PUCCH resources of one of the plurality of PUCCH resource sets.

[0336] In one embodiment, the acknowledgment information may include an acknowledgment (ACK) in response to successful reception of the TB. The acknowledgment information may include a negative acknowledgment (NACK) in response to unsuccessful reception of the TB.

[0337] In one embodiment, the wireless device may monitor a second PDCCH on a CCE of a second SB among the plurality of SBs. The wireless device may receive a second DCI including a second radio resource indication and a second PUCCH resource index via the second PDCCH on one or more of the CCEs. The wireless device may receive a second TB via the second radio resource indicated by the second radio resource indication. The wireless device may determine a second PUCCH resource based on at least one of the second PUCCH resource index, a second SB index of the second SB, and / or a second CCE index of a second start CCE of one or more CCEs. The wireless device may transmit second acknowledgment information for reception of the second TB via the second PUCCH resource.

[0338] In one embodiment, the second PUCCH resource may be different from the PUCCH resource. The second SB index may be different from the SB index.

[0339] In one embodiment, the wireless device may monitor PDCCH on the CCE of an SB having a plurality of SBs. The wireless device may receive DCI including a radio resource indication and a PUCCH resource index via PDCCH on one or more CCEs of the CCE. The wireless device may receive a TB via the radio resources indicated by the radio resource indication. The wireless device may determine a PUCCH resource based on at least one of a PUCCH resource index, a PUCCH resource index offset associated with the SB, and / or a CCE index of a starting CCE of one or more CCEs. The wireless device may transmit acknowledgement response information for receiving the TB via the PUCCH resource.

[0340] In one embodiment, the wireless device may receive configuration parameters indicating respective CCE index offsets for corresponding SBs of a plurality of SBs. The wireless device may monitor PDCCH on the CCEs of a plurality of SBs. The wireless device may receive DCI including a radio resource indication and a PUCCH resource index via PDCCH on one or more CCEs of the CCE. The wireless device may receive a TB via the radio resources indicated by the radio resource indication. The wireless device may determine a PUCCH resource based on at least one of a PUCCH resource index, respective CCE index offsets corresponding to the SBs, and a CCE index of a starting CCE of one or more CCEs. The wireless device may transmit acknowledgement response information for receiving the TB via the PUCCH resource.

[0341] FIG. 32 shows a flowchart according to one aspect of an exemplary embodiment of the present disclosure. At 3210, the wireless device may receive configuration parameters of a BWP including an RB set, where the CCEs of the CORESET of the BWP span the RB set, and subsets of CCEs within each RB set of the RB set are indexed from the same initial value. At 3220, the wireless device may receive DCI via one or more CCEs of a subset of CCEs within an RB set of the RB set. At 3230, the wireless device may determine the CCE index of the starting CCE of one or more CCEs based on indexing a subset of CCEs from the initial value within the RB set. At 3240, the wireless device may transmit an uplink signal via an uplink resource determined based on the CCE index.

[0342] FIG. 33 shows a flowchart according to one aspect of an exemplary embodiment of the present disclosure. At 3310, the wireless device may receive configuration parameters of a BWP including an RB set, where the CCEs span the RB set, and subsets of CCEs within each RB set of the RB set are indexed from the same initial value. At 3320, the wireless device may receive control information via one or more CCEs of a subset of CCEs within an RB set of the RB set. At 3330, the wireless device may transmit an uplink signal via an uplink resource based on the index of a CCE of one or more CCEs.

[0343] According to an exemplary embodiment, the wireless device may receive one or more RRC messages including second configuration parameters of the cell, where the cell includes a plurality of bandwidth parts including a bandwidth part.

[0344] According to an exemplary embodiment, the initial value may be zero. The control information may be DCI via PDCCH on one or more CCEs.

[0345] According to an exemplary embodiment, each CCE of the CCEs may include a plurality of resource element groups, and the resource element groups include RBs in a symbol.

[0346] According to an exemplary embodiment, each RB set of the RB sets may include one or more RBs of a bandwidth part. Each RB of the one or more RBs may include a plurality of resource elements of the bandwidth part. The first RB set may include one or more RBs that do not overlap with the second RB set of the RB sets.

[0347] According to an exemplary embodiment, the configuration parameter may indicate that the control resource set of the bandwidth part includes CCEs. The configuration parameter may indicate that the frequency domain resource allocation pattern of the control resource set is replicated for each RB set of the RB sets of the bandwidth part, and the physical radio resources of the CCEs of the control resource set are mapped to each RB set. The wireless device may further determine uplink resources based on the total number of the first subset of CCEs in the first RB set associated with the control resource set.

[0348] According to an exemplary embodiment, the configuration parameter may indicate one or more RB sets including the first RB set from the RB sets of the bandwidth part for a search space associated with the control resource set. The search space may include one or more CCEs of the first subset of CCEs associated with the control resource set in the first RB set. The search space associated with the control resource set may include one or more monitoring frequency position indications, and each frequency position indication corresponds to each RB set of the RB sets of the bandwidth part. The wireless device may monitor the downlink control channel on the search space on the first RB set in response to the monitoring frequency position indication corresponding to the first RB set indicating downlink control channel monitoring on the first RB set. The wireless device may receive control information during monitoring of the downlink control channel of the search space.

[0349] According to an exemplary embodiment, the uplink resource may be a Physical Uplink Control Channel (PUCCH) resource.

[0350] According to an exemplary embodiment, the configuration parameter may indicate a plurality of PUCCH resources. Each of the plurality of PUCCH resources may be identified by its respective PUCCH resource index. Each of the plurality of PUCCH resources may be associated with an RB set index of a certain RB set of the RB sets. The wireless device may transmit a signal via an uplink resource associated with the first RB set. The control information may include a PUCCH resource indication field indicating the PUCCH resource index. The wireless device may further determine the uplink resource based on the PUCCH resource index indicated by the control information.

[0351] According to an exemplary embodiment, the wireless device may determine the uplink resource based on the PUCCH resource index indicated by the control information and a PUCCH resource index offset determined based on the index of the CCE.

[0352] According to an exemplary embodiment, the control information may include a downlink allocation of downlink radio resources for transmitting a transport block. The wireless device may receive the transport block via the downlink radio resources based on the control information.

[0353] According to an exemplary embodiment, the signal may include acknowledgement response information corresponding to a transport block scheduled by the control information. The acknowledgement response information may include an acknowledgement (ACK) in response to successful reception of the transport block. The acknowledgement response information may include a negative acknowledgement (NACK) in response to unsuccessful reception of the transport block.

[0354] According to an exemplary embodiment, the CCE can be the starting CCE of one or more CCEs (e.g., having the lowest CCE index) based on indexing a first subset of CCEs from an initial value within a first RB set. The wireless device can determine an uplink resource based on a PUCCH resource indicator in downlink control information and a PUCCH resource offset determined based on the index of the starting CCE.

[0355] FIG. 34 shows a flowchart according to one aspect of an exemplary embodiment of the present disclosure. At 3410, the wireless device can monitor a downlink control channel on control channel elements (CCEs) of a resource block (RB) set of a bandwidth part. At 3420, the wireless device can receive downlink control information including a physical uplink control channel (PUCCH) resource index on one or more CCEs. At 3430, the wireless device can transmit an uplink signal via a PUCCH resource determined based on the PUCCH resource index, the RB set index of the RB set, and the CCE index of the starting CCE of one or more CCEs.

Claims

1. A wireless device, the wireless device comprising: receiving configuration parameters for a set of control resources in a bandwidth portion (BWP); the control resource set comprises control channel elements (CCEs) spanning a first set of resource blocks (RBs) of the BWP and a second set of RBs of the BWP; the first RB set has a first subset of the CCEs, and a first index value of the first subset starts from a first initial value; the second RB set has a second subset of the CCEs, and second index values ​​of the second subset start from a second initial value that is the same as the first initial value; The wireless device further comprises: receiving control information via one or more CCEs of the first subset; transmitting a signal over an uplink resource based on an index of a CCE among the one or more CCEs of the first subset; The index is determined based on the first index values ​​of the first subset starting from the first initial value which is the same as the second initial value.

2. 2. The wireless device of claim 1, wherein the first initial value and the second initial value are zero, and the first index value of the first subset and the second index value of the second subset are in ascending order.

3. 2. The wireless device of claim 1, wherein the configuration parameters indicate that a frequency domain resource allocation pattern of the control resource set is replicated for each of the first RB set and the second RB set, and physical radio resources of the CCEs of the control resource set are mapped to the first RB set and the second RB set.

4. The wireless device of claim 1 , wherein the configuration parameters indicate one or more RB sets, including the first RB set, for a search space associated with the control resource set.

5. The wireless device of claim 4 , wherein the search space includes the one or more CCEs of the first subset of the CCEs associated with the control resource set in the RB set.

6. 5. The wireless device of claim 4, wherein the search space associated with the control resource set is comprised of one or more monitored frequency location indications, each frequency location indication corresponding to a respective one of the RB sets of the BWP, the RB sets including the first RB set and the second RB set.

7. The uplink resource is: A physical uplink control channel (PUCCH) resource index indicated by the control information; and A PUCCH resource index offset determined based on the index of the CCE; The wireless device of claim 1 , wherein the determination is based on:

8. 2. The wireless device of claim 1, wherein the CCE is a starting CCE after the one or more CCEs.

9. the wireless device further comprising: receiving second control information via one or more second CCEs of the second subset of CCEs in the second RB set; transmit a second signal over a second uplink resource based on a second index of a CCE among the one or more second CCEs of the second subset; the second index is determined based on the second index values ​​of the second subset starting from the second initial value which is the same as the first initial value. The wireless device of claim 1 .

Images