Uplink transmission in the new radio unlicensed band

Abstract

Improve indexing of subsets of CCEs within RB sets. [Solution] The wireless device receives configuration parameters for a bandwidth portion, which includes a set of resource blocks (RBs). Control channel elements (CCEs) are present across the RB sets, and a subset of CCEs within each RB set is indexed from the same initial value. Control information is received via one or more CCEs in a first subset of CCEs within a given RB set. The wireless device transmits a signal over the uplink resource based on the index of one or more CCEs.

Description

[Background technology]

[0001] Cross-reference of related applications This application claims the interests of U.S. Provisional Patent Application No. 62 / 930,130, filed on 4 November 2019, which is incorporated herein by reference in its entirety. [Overview of the project] [Means for solving the problem]

[0002] A base station can communicate with a mixture of radio devices. Radio devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Radio devices may have certain capabilities depending on the category and / or capabilities of the radio device. Where this disclosure refers to a base station communicating with multiple radio devices, this disclosure may refer to a subset of all radio devices in a coverage area. This disclosure may refer, for example, to multiple radio devices of a given LTE or 5G release that have a given capability and are located in a given sector of a base station. Multiple radio devices in this disclosure may refer to a selection of multiple radio devices and / or a subset of all radio devices in a coverage area that operate according to the disclosed method, etc. Multiple base stations or multiple radio devices may exist in a coverage area that cannot comply with the disclosed method. For example, those radio devices or base stations may be running on an older release of LTE or 5G technology. [Brief explanation of the drawing]

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

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

[0005] [Figure 2] Figures 2A and 2B show the new radio (NR) user plane and control plane protocol stacks, respectively.

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

[0007] [Figure 4] Figure 4A shows an exemplary downlink data flow through the NR user plane protocol stack shown in Figure 2A.

[0008] Figure 4B shows an example of the MAC subheader format in a MAC PDU.

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

[0010] [Figure 6] Figure 6 is an illustrative diagram showing the RRC state transitions of the UE.

[0011] [Figure 7] Figure 7 shows an example of an NR frame structure where OFDM symbols are grouped together.

[0012] [Figure 8] Figure 8 shows an example of slot configuration in the time and frequency domains of the NR carrier.

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

[0014] [Figure 10]Figure 10A shows three carrier aggregation configurations, each having two component carriers.

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

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

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

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

[0019] [Figure 13] Figures 13A, 13B, and 13C show a 4-step competition-based random access procedure, a 2-step competition-free random access procedure, and another 2-step random access procedure, respectively.

[0020] [Figure 14] Figure 14A shows an example of a CORESET configuration for the bandwidth portion.

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

[0022] [Figure 15] Figure 15 shows an example of a wireless device that communicates with a base station.

[0023] [Figure 16] Figures 16A, 16B, 16C, and 16D show exemplary structures for uplink and downlink transmission.

[0024] [Figure 17] Figures 17A, 17B, and 17C show examples of MAC subheaders.

[0025] [Figure 18] Figure 18A shows an example of a DL MAC PDU.

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

[0027] [Figure 19] Figure 19 shows an example of multiple LCIDs for a downlink according to one embodiment of the exemplary embodiments of the present disclosure.

[0028] [Figure 20] Figure 20 shows an example of multiple LCIDs in an uplink according to one embodiment of the exemplary embodiments of the present disclosure.

[0029] [Figure 21] Figures 21A and 21B show an example of a SCell startup / shutdown MAC CE according to one embodiment of the exemplary embodiments of the present disclosure.

[0030] [Figure 22] Figure 22 shows an example of BWP management according to one embodiment of the exemplary embodiments of this disclosure.

[0031] [Figure 23] Figure 23 shows an example of a search space configuration according to one embodiment of the exemplary embodiments of this disclosure.

[0032] [Figure 24] Figure 24 shows an example of a control resource set configuration according to one embodiment of the exemplary embodiments of this disclosure.

[0033] [Figure 25] Figure 25A is a flowchart of a downlink transport block supply according to one embodiment of the exemplary embodiments of the present disclosure.

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

[0035] [Figure 26] Figure 26 shows an example of PUCCH resource display according to one embodiment of the exemplary embodiments of this disclosure.

[0036] [Figure 27] Figure 27A shows an example of a control resource set (CORESET) configuration according to one embodiment of the exemplary embodiments of this disclosure.

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

[0038] [Figure 28] Figure 28 shows an example of PUCCH resource selection according to one embodiment of the exemplary embodiments of this disclosure.

[0039] [Figure 29] Figure 29 shows an example of PUCCH resource selection according to one embodiment of the exemplary embodiments of this disclosure.

[0040] [Figure 30] Figure 30 shows an example of PUCCH resource selection according to one embodiment of the exemplary embodiments of this disclosure.

[0041] [Figure 31] Figure 31 shows an example of PUCCH resource selection according to one embodiment of the exemplary embodiments of this disclosure.

[0042] [Figure 32] Figure 32 is a flowchart of PUCCH resource selection according to one embodiment of the exemplary embodiments of the present disclosure.

[0043] [Figure 33]Figure 33 is a flowchart of PUCCH resource selection according to one embodiment of the exemplary embodiments of this disclosure.

[0044] [Figure 34] Figure 34 is a flowchart of PUCCH resource selection according to one embodiment of the exemplary embodiments of this disclosure. [Modes for carrying out the invention]

[0045] In this disclosure, various embodiments are presented as examples of how the disclosed technology may be implemented and / or practiced in various environments and scenarios. It will be apparent to those skilled in the art that various modifications of form and detail can be made without departing from the scope. Indeed, after reading the specification, it will be apparent to those skilled in the art that alternative embodiments can be implemented. These embodiments should not be limited by any of the exemplary embodiments. Embodiments in this 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 this disclosure. Figures highlighting features and benefits are shown for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable to be available in ways other than those shown. For example, any action listed in any flowchart can be rearranged in some embodiments or used only as an optional.

[0046] The embodiments may be configured to operate as needed. The disclosed mechanisms may be executed, for example, in a wireless device, base station, wireless environment, network, or a combination thereof, when certain criteria are met. Illustrative criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system configuration, packet size, traffic characteristics, or a combination thereof. Various exemplary embodiments can be applied when one or more criteria are met. Therefore, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols.

[0047] In this specification, “a” and “an” and similar phrases are interpreted as “at least one” and “one or more.” Similarly, any term ending in the suffix “(s)” should be interpreted as “at least one” and “one or more.” In this specification, the term “may” is interpreted as “for example, may be.” In other words, the term “may” indicates that the phrase following the term “may” is one embodiment of several suitable possibilities, which may or may not be used by one or more of the various embodiments. Where used herein, the terms “comprises” and “consists of” enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unlisted components included in the element being described. In contrast, “consists of” provides a complete enumeration of one or more components of the element being described. Where used herein, the term “based on” should be interpreted as “at least partially based” rather than, for example, “based only on.” As used herein, the term "and / or" represents any possible combination of the enumerated elements. For example, "A, B, and / or C" could mean A, B, C, A and B, A and C, B and C, or A, B, and C.

[0048] If A and B are a set 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, 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 that the phrase following the term "based on" is an embodiment of one of many preferred possibilities, in which one or more different embodiments may or may not be used. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is an embodiment of one of many preferred possibilities, in which one or more different embodiments may or may not be used. The phrase "according to" (or equivalently "at least in accordance with") indicates that the phrase following the phrase "according to" is an embodiment of one of many preferred possibilities, in which one or more different embodiments may or may not be used. The phrase “adopt / use” (or equivalently “at least adopt / use”) indicates that the phrase following the phrase “adopt / use” is an embodiment of one of many appropriate possibilities, in which one or more of the various embodiments may or may not be used.

[0049] The term “configured” can relate to the capacity of a device, regardless of whether the device is operational or non-operating. “Configured” can also refer to specific settings of a device that affect its operational characteristics, regardless of whether the device is operational or non-operating. In other words, hardware, software, firmware, registers, memory values, etc., can be “configured” within a device, regardless of whether the device is operational or non-operating, in order for the device to provide certain characteristics. Terms such as “control messages generated in the device” may mean that, regardless of whether the device is operational or non-operating, control messages have parameters that can be used to configure certain characteristics in the device or to implement certain actions in the device.

[0050] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, parameter (IE)M contains parameter (IE)K, and parameter (IE)K contains parameter (information element)J, then for example, N contains K and N contains J. In exemplary embodiments, when one or more messages contain multiple parameters, it means that one of the multiple parameters is contained in at least one of the one or more messages, but not in each of the one or more messages.

[0051] Furthermore, many of the features presented above are described as optional by the use of "may" or parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe all possible changes that may result from selecting from a set of optional features. This disclosure should be construed as explicitly disclosing all such changes. For example, a system described as having three optional features can be embodied in seven ways: by just one of the three possible features, by any two of the three features, or by three of the three features.

[0052] Many of the elements described in the disclosed embodiments can be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. Modules described in this disclosure may be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, and they can be behaviorally equivalent. For example, a module may be implemented in a hardware machine (such as C, C++, Fortran, Java®, Basic, Matlab) or in software routines written in a computer language configured to run in Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Modules may also be implemented using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and complex-programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs) such as VHSIC (VHDL) or Verilog, which constitute connections between internal hardware modules with limited functionality in the programmable device. These techniques are often used in combination to achieve the results of the functional modules.

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

[0054] CN102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interface function, CN102 may set up an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging capabilities.

[0055] RAN104 can connect CN102 to radio device 106 via radio communication over the air interface. As part of the radio communication, RAN104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN104 to radio device 106 over the air interface is known as the downlink, and the communication direction from radio device 106 to RAN104 over the air interface is known as the uplink. Downlink transmissions can be isolated from uplink transmissions using frequency division duplication (FDD), time division duplication (TDD), and / or some combination of the two duplication techniques.

[0056] The term "wireless device" may be used throughout this disclosure to mean and include any mobile or fixed (non-portable) device that requires or is capable of wireless communication. For example, a wireless device could be a telephone, 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" also includes other terms, including user equipment (UE), user terminal (UT), access terminal (AT), portable station, handset, wireless transceiver unit (WTRU), and / or wireless communication device.

[0057] RAN104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to include and encompass Node B (associated with UMTS and / or 3G standards), evolved Node B (associated with eNB, E-UTRA and / or 4G standards), remote radio head (RRH), baseband processing unit coupled to one or more RRHs, repeater or relay node used to extend the coverage area of ​​a donor node, next-generation evolved Node B (ng-eNB), generating Node B (associated with gNB, NR and / or 5G standards), access point (AP, associated with e.g., WiFi or other appropriate 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] A base station included in RAN104 may include one or more sets of antennas for communicating with the radio device 106 over an air interface. For example, one or more base stations may include three sets of antennas, each for controlling three cells (or sectors). The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a radio device transmitter) operating in the cell. Together, the base station cells may provide radio coverage to the radio device 106 over a wide geographical area to support radio device mobility.

[0059] In addition to the three sector sites, other implementations of base stations are possible. For example, one or more base stations in RAN104 may be implemented as sector sites with more or fewer than three sectors. One or more base stations in RAN104 may be implemented as access points, as baseband processing units coupled to multiple remote radio heads (RRHs), and / or as repeaters or relay nodes used to extend the coverage area of ​​a donor node. Baseband processing units coupled to RRHs may be part of a centralized or cloud RAN architecture, and baseband processing units may be centralized or virtualized within a pool of baseband processing units. Repeater nodes may amplify and rebroadcast radio signals received from donor nodes. Relay nodes may perform the same / similar functions as repeater nodes, but may decode radio signals received from donor nodes and remove noise before amplifying and rebroadcasting the radio signals.

[0060] RAN104 can be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high-level transmit power. RAN104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide smaller coverage areas, for example, overlapping with the relatively large coverage areas provided by macrocell base stations. Smaller coverage areas can be provided in areas with high data traffic (or so-called hotspots) or in areas with weak macrocell coverage. Examples of small cell base stations, in order of decreasing coverage area, include microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0062] Figure 1B shows a mobile communications network 150 of another embodiment in which embodiments of the present disclosure may be implemented. The mobile communications network 150 may be, for example, a PLMN operated by a network operator. As shown in Figure 1B, the mobile communications network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UE156A and UE156B (collectively referred to as UE156). These components may be implemented and operated in the same or similar manner as the corresponding components described with respect to Figure 1A.

[0063] 5G-CN152 provides UE156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of its interface function, 5G-CN152 may set up end-to-end connectivity between UE156 and one or more DNs, authenticate UE156, and provide charging capabilities. Compared to the CNs of 3GPP 4G networks, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN152 may be defined as network functions that provide services through interfaces to other network functions. The network functions of 5G-CN152 may be implemented in several ways: as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0064] As shown in Figure 1B, the 5G-CN152 includes Access and Mobility Management Function (AMF) 158A and User Plane Function (UPF) 158B, as shown in Figure 1B as a single component AMF / UPF158, for brevity of explanation. UPF158B can function as a gateway between NG-RAN154 and one or more DNs. UPF158B can perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic utilization reporting, uplink classification supporting routing of traffic flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggering. UPF158B can support multi-homed PDU sessions by functioning 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 branch point. UE156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0065] The AMF158A can perform functions such as termination of non-access layer (NAS) signaling, NAS signaling security, access layer (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), registered area management, intra-system and inter-system mobility support, access authentication, access permissions including roaming privilege checks, mobility management controls (subscriptions and policies), network slicing support, and / or selection of session management functions (SMF). NAS may refer to functions operating between CN and UE, and AS may refer to functions operating between UE and RAN.

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

[0067] NG-RAN154 can connect 5G-CN 152 to UE156 via radio communication over 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 more generally be referred to as base stations. gNB160 and ng-eNB162 may include one or more sets of antennas for communicating with UE156 over the air interface. For example, one or more gNB160s and / or one or more ng-eNB162s may include three sets of antennas for controlling three cells (or sectors), each. In addition, the gNBs160 and ng-eNBs162 cells can provide wireless coverage to the UE156 over a wide geographical area to support UE mobility.

[0068] As shown in Figure 1B, gNB160 and / or ng-eNB162 may be connected to 5G-CN152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces may be established on an underlying transport network, such as an Internet Protocol (IP) transport network, using direct physical and / or indirect connections. gNBs160 and / or ng-eNBs162 may be connected to UE156 via the Uu interface. For example, as shown in Figure 1B, gNB160A may be connected to UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with an interface may be used by the network elements in Figure 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] The gNB160 and / or ng-eNB162 may be connected to one or more AMF / UPF functions of the 5G-CN152, such as the AMF / UPF158, by one or more NG interfaces. For example, the gNB160A may be connected to the UPF158B of the AMF / UPF158 by an NG user plane (NG-U) interface. The NG-U interface may provide the supply of user plane PDUs between the gNB160A and the UPF158B (e.g., unguaranteed supply). The gNB160A may be connected to the AMF158A using an NG control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, NAS message forwarding, paging, PDU session management and configuration forwarding, and / or sending warning messages.

[0070] The gNB160 may provide NR user plane and control plane protocol termination to UE156 on a Uu interface. For example, the gNB160A may provide NR user plane and control plane protocol termination to UE156A on a Uu interface associated with a first protocol stack. The ng-eNBs162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE156 on a Uu interface, where E-UTRA refers to 3GPP 4G radio access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocol termination to UE156B on a Uu interface associated with a second protocol stack.

[0071] The 5G-CN152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that it may be possible for NR to connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although only one AMF / UPF158 is shown in Figure 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load shares across multiple AMF / UPF nodes.

[0072] As will be discussed, in Figure 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack may include two planes, 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 elements.

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

[0074] Figure 2A shows the NR user plane protocol stack, which includes five layers, implemented in the UE210 and gNB220. At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 may provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The following four protocols above PHYs 211 and 221 include the Media Access Control Layer (MAC) 212 and 222, the Radio Link Control Layer (RLC) 213 and 223, the Packet Data Convergence Protocol Layer (PDCP) 214 and 224, and the Service Data Application Protocol Layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0075] Figure 3 shows an example of services provided between the protocol layers of the NR user plane protocol stack. Starting from the top of Figures 2A and 3, SDAP215 and 225 may perform QoS flow processing. UE210 may receive services via a PDU session, which may be a logical connection between UE210 and DN. A PDU session may have one or more QoS flows. CN's UPF (e.g., UPF158B) may map IP packets to one or more QoS flows in the PDU session based on QoS requirements (e.g., with respect to delay, data rate, and / or error rate). SDAP215 and 225 may perform mapping / unmapping between one or more QoS flows and one or more data radio bearers. Mapping / unmapping between QoS flows and data radio bearers may be determined by SDAP225 at gNB220. SDAP215 at UE210 may be notified about the mapping between QoS flows and data radio bearers via reflected mapping or control signaling received from gNB220. Regarding reflection mapping, the SDAP225 on the gNB220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP215 on the UE210 to determine mapping / unmapping between QoS flows and data radio bearers.

[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 data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCP214 and 224 may perform, for example, retransmission of unsent packets, intra-sequence delivery and rearrangement of packets, and removal of duplicate received packets for handover within gNB. 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 requiring high reliability.

[0077] Although not shown in Figure 3, PDCP214 and 224 can perform mapping / unmapping between split radio bearers and RLC channels in a dual-connection scenario. Dual-connection is a technique that allows a UE to connect to two cells, or more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split radio bearer is when a single radio bearer, such as one of the radio bearers provided by PDCP214 and 224 as a service to SDAP215 and 225, is handled by a cell group in a dual-connection. PDCP214 and 224 can map / unmap split radio bearers between RLC channels belonging to the cell group.

[0078] RLC213 and 223 can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of replicated data units received from MAC212 and 222, respectively. RLC213 and 223 can support three transmission modes: Transparent Mode (TM), Unacknowledged Response Mode (UM), and Acknowledged Response 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, independent of numerology and / or transmission time interval (TTI) duration. As shown in Figure 3, RLC213 and 223 can provide RLC channels as a service to PDCP214 and 224, respectively.

[0079] MAC212 and MAC222 may perform logical channel multiplexing / demultiplexing and / or mapping between logical channels and transport channels. 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 priority processing between UEs by dynamic scheduling. Scheduling may be performed by gNB220 (on MAC222) for downlink and uplink. MAC212 and 222 may be configured to perform error correction, priority processing between logical channels of UE210 by logical channel prioritization, and / or padding through Hybrid Automatic Repeating Requests (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)). MAC212 and MAC222 may support one or more numerology and / or transmit timings. In one embodiment, mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As shown in Figure 3, MACs 212 and 222 may provide logical channels to RLCs 213 and 223 as a service.

[0080] PHY211 and 221 can perform transport channel mapping to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY211 and 221 can 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] Figure 4A shows an example of downlink data flow through the NR user plane protocol stack. Figure 4A shows the downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs on the gNB220. Uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in Figure 4A.

[0082] The downlink data flow in Figure 4A begins when SDAP225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A, SDAP225 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 Figure 4A) is added to the IP packets. Data units from / to higher protocol layers are called service data units (SDUs) at lower protocol layers, and data units to / from lower protocol layers are called protocol data units (PDUs) at higher protocol layers. As shown in Figure 4A, the data unit from AP225 is an SDU at the lower protocol layer PDCP224 and a PDU at SDAP225.

[0083] The remaining protocol layers in Figure 4A may perform relevant functions (e.g., with respect to Figure 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, PDCP224 may perform IP header compression and encryption and forward its output to RLC223. RLC223 may optionally perform segmentation (e.g., as shown for IP packet m in Figure 4A) and forward its output to MAC222. MAC222 may multiplex several RLC PDUs and attach MAC subheaders to the RLC PDUs to form transport blocks. In NR, as shown in Figure 4A, MAC subheaders may be distributed throughout the MAC PDU. In LTE, MAC subheaders may be placed entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated delays because the MAC PDU subheaders may be computed before the complete MAC PDU is assembled.

[0084] Figure 4B shows an example of the MAC subheader format in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (in bytes, etc.) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCD) field to identify the logical channel initiated by the MAC SDU to assist in the multiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0085] Figure 4B further illustrates MAC control elements (CEs) inserted into a MAC PDU by MACs such as MAC223 or MAC222. For example, Figure 4B shows two MAC CEs inserted into a MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmission (as shown in Figure 4B) and at the end of a MAC PDU for uplink transmission. MAC CEs may 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, on / off MAC CEs for PDCP duplicate detection on / off, channel status information (CSI) reports, sounding reference signal (SRS) transmission, and pre-configured components, discontinuous receive (DRX)-related MAC CEs, timing progression MAC CEs, and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader in a format similar to that described for MAC SDUs and may be identified by a reserved value in the LCID field, which indicates the type of control information contained in the MAC CE.

[0086] Before describing the NR control plane protocol stack, we will first explain the logical channels, transport channels, and physical channels, as well as the mapping between channel types. One or more channels can be used to perform functions related to the NR control plane protocol stack, which will be discussed later.

[0087] Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels for 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 transmit control and configuration information within the NR control plane, or as traffic channels that transmit data within the NR user plane. Logical channels can be classified as dedicated logical channels for 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, - A broadcast control channel (BCCH) for transmitting system information messages in the form of master information blocks (MIBs) and several system information blocks (SIBs), wherein the system information messages are 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 sending control messages along with random access, - To configure the UE, a dedicated control channel (DCCH) is provided for sending control messages to and from a specific UE. - Includes a dedicated traffic channel (DTCH) for transmitting user data to and from a specific UE.

[0088] A transport channel is used between the MAC layer and the PHY layer and can be defined by how they transmit the information they send over the air interface. The set of transport channels defined by NR includes, for example, - A paging channel (PCH) for sending paging messages originating from the PCCH, - Broadcast Channel (BCH) for carrying MIBs from BCCH, - Downlink Shared Channel (DL-SCH) for sending downlink data and signaling messages, including SIBs from BCCH. - Uplink Shared Channel (UL-SCH) for transmitting uplink data and signaling messages, - Includes Random Access Channels (RACH) that allow UEs to connect to the network without prior scheduling.

[0089] A PHY can pass information between its processing levels using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information from one or more transport channels. The PHY may generate control information to support its low-level operation and provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR is, for example, - A physical broadcast channel (PBCH) for carrying MIBs 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), which may include downlink scheduling commands, uplink scheduling authorization, and uplink power control commands. - UL-SCH and, in some examples, a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from uplink control information (UCI), as described below. - A physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgment responses, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR), - Includes a physical random access channel (PRACH) for random access.

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

[0091] Figure 2B shows an embodiment of the NR control plane protocol stack. In Figure 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as in the example of the NR user plane protocol stack. 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, as in the NR user plane protocol stack, the NR control plane stack has Radio Resource Control (RRC)216 and 226, and NAS protocols217 and 237 at the top of the NR control plane protocol stack.

[0092] NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 (e.g., AMF158A), or more generally, between the UE210 and the CN. NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 via signaling messages called NAS messages. There is no direct path between the UE210 and the AMF230 to send NAS messages. NAS messages can be sent using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0093] RRC216 and 226 may provide control plane functionality between UE210 and gNB220, or more generally, between UE210 and RAN. RRC216 and 226 may provide control plane functionality between UE210 and gNB220 via signaling messages called RRC messages. RRC messages may be transmitted between UE210 and RAN using a signaling radio bearer and identical / similar PDCP, RLC, MAC, and PHY protocol layers. MAC may multiplex control plane and user plane data within the same transport block (TB). The RRC216 and 226 can provide control plane functions such as broadcasting system information related to the AS and NAS, paging initiated by the CN or RAN, establishing, maintaining, and releasing RRC connections between the UE210 and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers, mobility functions, QoS management functions, UE measurement reporting and reporting control, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing the RRC connection, the RRC216 and 226 can establish an RRC context, which may involve setting parameters for communication between the UE210 and the RAN.

[0094] Figure 6 is an exemplary diagram illustrating the RRC state transitions of a UE. The UE may be identical or similar to the wireless device 106 shown in Figure 1A, the UE 210 shown in Figures 2A and 2B, or any other wireless device described herein. As shown in Figure 6, the UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[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 or more base stations included in RAN104 shown in Figure 1A, one of gNB160 or ng-eNB162 shown in Figure 1B, gNB220 shown in Figures 2A and 2B, or any other base station similar to any other base station described herein. The base station to which the UE is connected may have the UE's RRC context. 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 UE's mobility may be managed by the RAN (e.g., RAN104 or NG-RAN154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and adjacent cells and report these measurements to the base station currently serving the UE. Based on the reported measurements, the UE's serving base station may request a handover to one of the adjacent base stations' cells. The RRC state may transition from RRC connection 602 to RRC idle 604 via connection release procedure 608, or to RRC inactive 606 via connection deactivation procedure 610.

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

[0097] In RRC inactive 606, the previously established RRC context is maintained at the UE and base station. This reduces signaling overhead compared to the transition from RRC idle 604 to RRC connected 602, enabling a faster transition to RRC connected 602. In RRC inactive 606, the UE is in a sleep state, and the UE's mobility can be managed by the UE through cell reselection. The RRC state can transition from RRC inactive 606 to RRC connected 602 via connection restart procedure 614, or to RRC idle 604 via connection release procedure 616, which is identical or similar to connection release procedure 608.

[0098] The RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to enable the network to notify the UE of events via paging messages without broadcasting paging messages across the entire mobile communications network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 may enable the network to track the UE at the cell group level so that paging messages can be broadcast on the cells of the cell group in which the UE currently resides, instead of across the entire mobile communications network. The mobility management mechanisms in RRC idle 604 and RRC inactive 606 track the UE at the cell group level. They can do so using grouping at different granularities. For example, there may be three levels of granularity for cell grouping: 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, identified by a Tracking Area Identifier (TAI).

[0099] A tracking area can be used to track a 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 in the CN so that the CN can update the UE's location and provide the UE with a new UE registration area.

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

[0101] A base station that stores the RRC context for a UE, or the last serving base station of the UE, may be called an anchor base station. The anchor base station can maintain the RRC context for the UE for at least the duration that the UE remains in the anchor base station's RAN notification area and / or the duration that the UE remains in an RRRC inactive 606.

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

[0103] In NR, physical signals and physical channels (Figures 5A and 5B) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) or M phase shift keying (M-PSK) symbols) called source symbols, which are divided into F parallel symbol streams. The F parallel symbol streams can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain as if they were in the frequency 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 sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be an F time domain sample representing the sum of the F orthogonal subcarriers. The F time domain sample can form a single OFDM symbol. After some processing (e.g., adding cyclic prefixes) and upconversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface on the carrier frequency. The parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This process generates OFDM symbols pre-encoded with a discrete Fourier transform (DFT), which can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse process can be performed at the receiver using an FFT block on the OFDM symbols to reconstruct the data mapped to the source symbols.

[0104] Figure 7 shows an example of the structure of an NR frame in which OFDM symbols are grouped. An NR frame can be identified by a system frame number (SFN). An SFN may repeat over a period of 1024 frames. As shown in the figure, a single NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes, each with a duration of 1 millisecond. A subframe may be divided into slots, for example, each containing 14 OFDM symbols.

[0105] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. NR supports flexible numerology to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to a maximum of mm-wavelengths). Numerology can be defined with respect to subcarrier spacing and 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 ums. ​​For example, NR defines numerology using the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 ums, 30 kHz / 2.3 ums, 60 kHz / 1.2 ums, 120 kHz / 0.59 ums, and 240 kHz / 0.29 ums.

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

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

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

[0109] NR can support a wide range of carrier bandwidths (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). Also, receiving the full carrier bandwidth may be prohibited from a power consumption perspective for the UE. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its receiving bandwidth based on the amount of traffic the UE is expected to receive. This is called bandwidth adaptation.

[0110] NR supports UEs that cannot receive the entire carrier bandwidth and defines a Bandwidth Portion (BWP) that supports bandwidth adaptation. In one embodiment, a BWP may be defined by a subset of consecutive RBs on the carrier. A UE may consist of 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) (e.g., via the RRC layer). 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 called the active BWPs of the serving cell. When a serving cell consists of a secondary uplink carrier, the serving cell may have one or more primary active BWPs on the uplink carrier and one or more secondary active BWPs on the secondary uplink carrier.

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

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

[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 may receive downlink receptions (e.g., PDCCH or PDSCH) within the downlink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix duration). The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) within the uplink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0114] One or more BWP indicator fields may be provided to the Downlink Control Information (DCI). The value of a BWP indicator field may indicate which BWP in the configured set 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 in 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 can 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] A base station can configure the UE with a PCell BWP inactive timer value. The UE can start or restart the BWP inactive timer at any appropriate time. For example, the UE may start or restart the BWP inactive timer when (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for a paired spectral operation, or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for a non-paired spectral operation. If the UE does not detect a DCI for a certain period (e.g., 1 millisecond or 0.5 milliseconds), the UE may run the BWP inactive timer toward expiration (e.g., increasing from zero to the BWP inactive timer value, or decreasing from the BWP inactive timer value to zero). When the BWP inactive timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0117] In one embodiment, a base station can semi-statically configure a UE having one or more BWPs. The UE can switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating the second BWP as the active BWP, and / or in response to the expiration of a BWP inactivity timer (for example, if the second BWP is the default BWP).

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

[0119] Figure 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier. The UE, consisting of the 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 can switch between BWPs at a switching point. In the example in Figure 9, the UE may switch from BWP902 to BWP904 at switching point 908. The switch at switching point 908 may occur for any suitable reason, for example, in response to the expiration of a BWP inactive timer (indicating a switch to the default BWP) and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP906 at switching point 910 in response to receiving a 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 a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP902 at switching point 914 in response to receiving a DCI indicating BWP902 as the active BWP.

[0120] If a UE is configured for a secondary cell with a set of configured downlink BWPs and a default downlink BWP in the timer value, the UE procedure for switching the BWP on the secondary cell may be identical / similar to that for the primary cell. For example, the UE may use the timer value and default downlink BWP for the secondary cell in the same / similar manner that the UE uses these values ​​for the primary cell.

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

[0122] Figure 10A shows three CA configurations with two CCs. In the in-band, continuous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are positioned directly adjacent to each other within that frequency band. In the in-band, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and separated into frequency bands 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 may be aggregated. Aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplication schemes (TDD or FDD). A serving cell of a UE using a CA may have downlink CCs. For FDD, one or more uplink CCs may optionally be configured for the serving cell. Aggregating more downlink carriers than uplink carriers may be useful, for example, when a UE has more data traffic on the downlink than on the uplink.

[0124] When using a Carrier Aggregation (CA), one of the aggregation cells of the UE may be called the Primary Cell (PCell). The PCell may be the serving cell to which the UE first connects during RRC connection establishment, re-establishment, and / or handover. The PCell may provide the UE with NAS mobility information and security inputs. The UE may have different PCells. On the downlink, the carrier corresponding to the PCell may be called the Downlink Primary CC (DL PCC). On the uplink, the carrier corresponding to the PCell may be called the Uplink Primary CC (UL PCC). Other aggregation cells of the UE may be called Secondary Cells (SCells). In one embodiment, the SCell may be configured after the PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. On the downlink, the carrier corresponding to the SCell may be called the Downlink Secondary CC (DL SCC). On the uplink, the carrier corresponding to the SCell may be called the Uplink Secondary CC (UL SCC).

[0125] SCells configured for a UE can be started and stopped, for example, based on traffic and channel conditions. Stopping a SCell may mean that PDCCH and PDSCH reception on the SCell is stopped, and PUSCH, SRS, and CQI transmission on the SCell is stopped. Configured SCells can be started and stopped using MAC CEs with respect to Figure 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., from a subset of configured SCells) for the UE are started or stopped. Configured SCells can be stopped in response to the expiration of a SCell stop timer (e.g., one SCell stop timer per SCell).

[0126] Downlink control information, such as cell scheduling assignments and scheduling authorizations, may be transmitted on the cell corresponding to the assignment and authorization, known as self-scheduling. DCIs for a cell may be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) may be transmitted on the PCell's PUCCH. A large number of aggregated downlink CCs may overload the PCell's PUCCH. A cell may be divided into multiple PUCCH groups.

[0127] Figure 10B shows an example of how an aggregation cell may be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 may each include one or more downlink CCs. In the example in Figure 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050, in this example, includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary S cells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CC of PUCCH group 1010, indicated as UCI1031, UCI1032, and UCI1033, may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050, indicated as UCI1071, UCI1072, and UCI1073, may be transmitted on the uplink of PSCell 1061. In one embodiment, 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 downlink CC may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

[0128] A cell containing a downlink carrier and an optional uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may, depending on the context in which the physical cell ID is used, identify the downlink carrier and / or uplink carrier of the cell. The physical cell ID may be determined using synchronization signals transmitted on the downlink component carrier. The cell index may be determined using RRC messages. In this disclosure, the physical cell ID may be referred to as the carrier ID. The cell index may be referred to as the carrier index. For example, if this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for the cell containing the first downlink carrier. The same concept may apply, for example, to carrier activation. If this disclosure indicates that a first carrier is activated, this specification may mean that the cell containing the first carrier is activated.

[0129] In a CA, the multi-carrier nature of the PHY may be exposed to MAC. In one embodiment, HARQ entities may operate on a serving cell. Transport blocks may be generated per allocation / authorization per serving cell. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to serving cells.

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

[0131] Figure 11A shows an embodiment 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 Figure 11A). Bursts may be transmitted periodically (e.g., every two frames or every 20 milliseconds). Bursts may be limited to half frames (e.g., the first half frame having a duration of 5 milliseconds). Figure 11A is an example, and it will be understood that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, location of bursts within a frame) may be configured based on, for example, the carrier frequency of the cell from which the SS / PBCH block is transmitted, the cell's numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), or any other appropriate factor. In one embodiment, the UE may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the radio network is configured to assume a different subcarrier spacing.

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

[0133] The location of the SS / PBCH block in the time and frequency domains is not 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 a different frequency position within the carrier, as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine the locations of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defining SS block (CD-SSB). In one embodiment, the primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In one embodiment, cell selection / search and / or reselection may be based on the CD-SSB.

[0134] SS / PBCH blocks can be used by the 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 the PSS and SSS sequences, respectively. The UE may determine the position of a cell's frame boundary 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 at a known distance from the frame boundary.

[0135] The PBCH may use QPSK modulation and may use forward error correction (FEC). FEC may use polarity coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulation of the PBCH. The PBCH may include a representation of the cell's current system frame number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a 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 (RSSI) associated with the cell. The RMSI may include System Information Block Type 1 (SIB1). SIB1 may contain 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 may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may point to a frequency. The UE may then search for the SS / PBCH block at the frequency to which the UE points.

[0136] A UE can assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index will be quasi-identical (QCL) (e.g., have the same / similar Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial Rx parameters). A UE cannot assume that QCL for SS / PBCH block transmissions will have different SS / PBCH block indices.

[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's 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 carrier frequency span, a base station may 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. PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or identical.

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

[0140] A base station can semi-statically configure a UE with one or more sets of CSI-RS resources. CSI-RS resources may be associated with location and periodicity within the time and frequency domains. A base station can selectively activate and / or deactivate CSI-RS resources. A base station can indicate to the UE that CSI-RS resources within a set of CSI-RS resources are being activated and / or deactivated.

[0141] A base station can configure a UE to report CSI measurements. The base station can configure a UE to provide CSI reports periodically, irregularly, or semi-permanently. For periodic CSI reports, the UE can consist of multiple CSI reports with varying timing and / or periodicity. For irregular CSI reports, the base station can request the CSI report. For example, the base station can instruct a UE to measure configured CSI-RS resources and provide a CSI report on the measurements. For semi-permanent CSI reports, the base station can configure a UE to periodically send periodic reports and selectively start or stop resources. The base station can use RRC signaling to configure a UE with CSI-RS resource sets and CSI reports.

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

[0143] Downlink DMRS may be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A 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 of front-loaded DMRS symbols (e.g., maximum number) of the PDSCH. A DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, a DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. A wireless network can support a common DMRS structure for downlink and uplink (e.g., at least for CP-OFDM). The DMRS location, DMRS pattern, and / or scrambling sequence may be the same or different. A base station may transmit downlink DMS and the corresponding PDSCH using the same precoding matrix. A UE may 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 portion 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 and second precoder matrices may differ based on the fact that the first bandwidth is different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. A set of PRBs may be represented as a precoding resource block group (PRG).

[0145] A PDSCH may include one or more layers. The UE may assume that at least one symbol having a DMS exists on one or more layers of the PDSCH. The upper layers may constitute up to three DMRSs with respect to the PDSCH.

[0146] Downlink PT-RS may be transmitted by the base station and may be used by the UE for phase noise compensation. Whether downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. If configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters, including at least the MCS. An NR network may support multiple PT-RS densities defined in the time and / or frequency domains. Frequency domain densities, if present, can be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS may be limited to the UE's scheduled time / frequency period. Downlink PT-RS may 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. A 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 transmit on one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for PUSCH and / or PUCCH that the UE can use to schedule single-symbol DMRS and / or dual-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 location, DMRS pattern, and / or DMRS scramble array may be identical or different.

[0148] PUSCH may include one or more layers, and UE may transmit at least one symbol having a DMS present on one or more layers of PUSCH. In one embodiment, the upper layers may constitute up to three DMRSs relative to PUSCH.

[0149] Uplink PT-RS (which may be used by base stations for phase tracking and / or phase noise compensation) may or may not be present depending on the UE's RRC configuration. The presence and / or pattern of 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)) which may be indicated by RRC signaling and / or DCI. If configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters, including at least the MCS. A radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, can be associated with at least one configuration of the scheduled bandwidth. A UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS may be limited to the UE's scheduled time / frequency period.

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

[0151] A base station can quasi-statistically configure a UE using one or more SRS configuration parameters that indicate at least one of the following: SRS resource configuration identifier, number of SRS ports, time-domain behavior of the SRS resource configuration (e.g., representation of periodic, semi-persistent, or aperiodic SRS), slots, minislots, and / or subframe-level periodicity, offsets for periodic and / or aperiodic SRS resources, number of OFDM symbols in the SRS resource, starting OFDM symbol of the SRS resource, SRS bandwidth, frequency-hopping bandwidth, cyclic shift, and / or SRS sequence ID.

[0152] Antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. When a first and second symbol are transmitted on the same antenna port, a receiver can infer the channel for carrying the second symbol on the antenna port (e.g., fade gain, multipath delay, and / or similar) from the channel for carrying the first symbol on the antenna port. The first and second antenna ports may be said to be quasi-coordinated (QCL) if one or more large-scale properties of the channel on which the first symbol on the first antenna port is transmitted can be inferred from the channel on which the second symbol on the second antenna port is transmitted. One or more large-scale properties may include at least one of delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial receive (Rx) parameters.

[0153] In channels using beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam display. The beam may be associated with one or more reference signals. For example, the beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurement based on a downlink reference signal (e.g., Channel Status Information Reference Signal (CSI-RS)) and generate a beam measurement report. The UE can perform downlink beam measurement procedures 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 to time and frequency domains. The square shown in Figure 11B may span resource blocks (RBs) within the cell bandwidth. A base station can transmit one or more RRC messages containing CSI-RS resource configuration parameters that indicate one or more CSI-RSs. One or more of the following parameters can be set by higher-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., position of symbols and resource elements (REs) 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, transmit comb, quasi-identical 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 Figure 11B can be configured for a UE with a UE-specific configuration. Three beams are shown in Figure 11B (beam #1, beam #2, and beam #3), and more or fewer beams can be configured. Beam #1 may be assigned as CSI-RS1101 transmitted on one or more subcarriers within the RB of a first symbol. Beam #2 may be assigned as CSI-RS1102 transmitted on one or more subcarriers within the RB of a second symbol. Beam #3 may be assigned as CSI-RS1103 transmitted on one or more subcarriers within the RB of a third symbol. By using frequency division multiplexing (FDM), a base station may transmit another CSI-RS associated with another UE's beam using other subcarriers within the same RB (e.g., those not used to transmit CSI-RS1101). By using time-domain multiplexing (TDM), the beam used for a UE may be configured so that the UE's beam uses symbols from other UEs' beams.

[0156] The CSI-RS (e.g., CSI-RS1101, 1102, 1103) shown in Figure 11B may be transmitted by a base station and used by a UE for one or more measurements. For example, a UE may measure the reference signal received power (RSRP) of a configured CSI-RS resource. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurements 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 transmit configuration indication (TCI) states, including several 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 a downlink transmission with a received (Rx) beam determined based on one or more TCI states. In one embodiment, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, it 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 capability, it may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and display an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE.

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

[0158] Figure 12A shows embodiments of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements on the transmit (Tx) beam of a transmit-receive point (TRP) (or multiple TRPs) to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP may include a Tx beam sweep of the beam set (shown as ellipses rotating counterclockwise, as indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE may include an Rx beam sweep for the beam set (shown as ellipses rotating counterclockwise, as indicated by dashed arrows, as shown in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements on the Tx beam of a TRP (shown as ellipses rotating counterclockwise, as indicated by dashed arrows in the top row of P2). The UE and / or base station may perform step P2 using a smaller set of beams than those used in step P1, or using a narrower beam than those used in step P1. This may be called beam refinement. The UE may perform step 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 embodiments of three uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used to allow a base station to perform measurements on a UE's Tx beam to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams (shown as ellipses rotated around a measurement, indicated by dashed arrows in the bottom rows of 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 rows of U1 and U2). Procedure U2 may be used to allow a base station to adjust its Rx beam when the UE is using a fixed Tx beam. The UE and / or base station may perform procedure U2 using a smaller set of beams than used in procedure P1, or using a narrower beam than the beam used in procedure P1. This can also be called beam refinement. The UE can perform procedure U3 to adjust the Tx beam when the base station is using a fixed Rx beam.

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

[0161] A UE may measure the quality of a beampair link using one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulated reference signals (DMRS). The quality of a beampair 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 values ​​measured on the RS resources. A base station may indicate that an RS resource is quasi-coordinated (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, and / or similar). An RS resource and one or more DMRS of a channel may be QCLed if the channel characteristics from a transmission to the UE via the RS resource (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameter, fade, and / or similar) are similar to or identical to the channel characteristics from a transmission to the UE via the channel.

[0162] A network (e.g., the network's gNB and / or ng-eNB) and / or UE may initiate a random access procedure. A UE in the RRC_IDLE state and / or the RRC_INACTIVE state may initiate a random access procedure to request network connection setup. 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 uplink transmission of SR when no PUCCH resources are available) and / or obtain uplink timing (e.g., if 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., SIB2, SIB3, and / or other system information such as similar ones). A UE may initiate a random access procedure for beam fault recovery requests. A network may initiate a random access procedure to establish time alignment for handover and / or SCell addition.

[0163] Figure 13A shows a four-step competition-based random access procedure. Before the procedure begins, the base station may send a configuration message 1310 to the UE. Figure 13A includes the sending 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 referred to as a preamble. Msg2 1312 may include a random access response (RAR) and / or may be referred to as a random access response (RAR).

[0164] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. One or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. One or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-configCommon), and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast one or more RRC messages to one or more UEs. One or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). Based on one or more RACH parameters, the UE may determine the time-frequency resources and / or uplink transmit power for transmitting Msg1 1311 and / or Msg3 1313. Based on one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg2 1312 and Msg4 1314.

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

[0166] One or more RACH parameters provided in configuration message 1310 may be used to determine the uplink transmit power for Msg1 1311 and / or Msg3 1313. For example, one or more RACH parameters may indicate reference power for preamble transmission (e.g., received target power and / or initial power for preamble transmission). One or more power offsets may be indicated by one or more RACH parameters. For example, one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between transmissions of Msg1 1311 and Msg3 1313, and / or a power offset value between preamble groups. 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 uplink carriers (e.g., normal uplink (NUL) carrier and / or complementary uplink (SUL) carrier).

[0167] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). RRC messages may be used to constitute one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble groups 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, for example, select at least one preamble to be associated with one or more reference signals and / or the selected preamble group, if the association between one or more preambles and at least one reference signal is constituted by an RRC message.

[0168] The UE may determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE may determine the preamble based on path loss measurements, RSRP measurements, and / or the size of Msg3 1313. In another embodiment, one or more RACH parameters may indicate the preamble format, the maximum number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use one or more RACH parameters to configure the UE with associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). If associations are configured, the UE may determine, based on the associations, to include the preamble in Msg1 1311. 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] The UE may perform a preamble retransmission if no response is received after a preamble transmission. The UE may increase the uplink transmit power for preamble retransmission. The UE may select an initial preamble transmit power based on path loss measurements and / or target received preamble power configured by the network. The UE may decide to retransmit the preamble and ramp up the uplink transmit 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 transmit power for retransmission. The UE may ramp up the uplink transmit power if it determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_STATEER). The UE may determine that a random access procedure has failed and completed if, for example, the number of preamble transmissions exceeds a threshold determined by one or more RACH parameters (e.g., preambleTransMax).

[0170] Msg2 1312 received by the UE may include RARs. In some scenarios, Msg2 1312 may include multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and displayed on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 has been received by the base station. Msg2 1312 may include time alignment commands that the UE can use to adjust the UE's transmission timing, scheduling permission for the transmission of Msg3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg2 1312. A UE may determine when to start a time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, a UE may start a time window after one or more symbols of the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of preamble transmission). One or more symbols may be determined based on numerology. PDCCH may be in a common lookup space composed of RRC messages (e.g., a Type1-PDCCH common lookup space). A UE may identify a RAR based on a Radio Network Temporary Identifier (RNTI). An RNTI may be used in response to one or more events that initiate a Random Access Procedure. A UE may use a Random Access RNTI (RA-RNTI). An RA-RNTI may be associated with a PRACH opportunity that the UE uses to transmit the preamble. For example, a UE may determine an RA-RNTI based on the OFDM symbol index, slot index, frequency domain index, and / or UL carrier indicators of the PRACH opportunity. An example of an 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 (e.g., 0 ≤ s_id < 14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0 ≤ t_id < 80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier, 1 for a SUL carrier). A UE may send Msg3 1313 in response to the successful reception of Msg2 1312 (for example, using the resources identified in Msg2 1312). Msg3 1313 may be used for conflict resolution in a conflict-based random access procedure, for example, as shown in Figure 13A. In some scenarios, multiple UEs may send the same preamble to a base station, and the base station may provide a RAR corresponding to the UEs. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Conflict resolution (e.g., using Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To implement conflict resolution, a UE may include a device identifier in Msg3 1313 (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other appropriate identifier).

[0171] Msg4 1314 may be received after or in response to the transmission of Msg3 1313. If a 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 found on the PDCCH, the random access procedure is determined to have completed successfully. If a 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 in Msg3 1313 (e.g., transmitted) or otherwise contains the corresponding UE conflict resolution identity .'' CE, the UE may determine that conflict resolution was successful, and / or the UE may determine that the random access procedure has completed successfully.

[0172] A UE may consist of a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedures) may be supported on the uplink carrier. For example, a base station may configure a UE with two separate RACH configurations, i.e., one for the SUL carrier and the other for the NUL carrier. For random access within a cell configured with SUL carriers, the network may indicate which carrier (NUL or SUL) to use. A UE may determine the SUL carrier, for example, if the measured quality of one or more reference signals is below the broadcast threshold. Uplink transmissions of random access procedures (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. In one or more instances, a UE may switch uplink carriers during a random access procedure (e.g., between Msg1 1311 and Msg3 1313). For example, the UE may determine and / or switch the uplink carrier for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (e.g., listening before speaking).

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

[0174] The uncontested random access procedure shown in Figure 13B may be initiated for beam fault recovery, other SI requests, SCell additions, and / or handovers. For example, the base station may display or assign the preamble to be used for Msg1 1321 to the UE. The UE may receive a display of the preamble (e.g., ra-PreambleIndex) from the base station via the PDCCH and / or RRC.

[0175] After sending the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the RAR's PDCCH. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor for PDCCH transmissions addressed to Cell RNTI (C-RNTI) in the search space. In the uncontested random access procedure shown in Figure 13B, the UE may determine that the random access procedure has completed successfully after sending Msg1 1321 and receiving the corresponding Msg2 1322, or in response to it. The UE may determine that the random access procedure has completed successfully, for example, if a PDCCH transmission is addressed to C-RNTI. The UE may determine that the random access procedure has completed successfully, for example, if the UE receives a RAR containing a preamble identifier corresponding to the preamble sent by the UE, and / or if the RAR contains a MAC sub-PDU containing the preamble identifier. The UE may determine the response as an indicator of confirmation for the SI request.

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

[0177] Msg A 1331 may be transmitted by the UE via 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. Transport block 1342 may include content similar to and / or equivalent to the content of Msg 3 1313 shown in Figure 13A. Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The UE may receive Msg B 1332 after transmitting Msg A 1331 or in response to such transmission. Msg B 1332 may include content similar to and / or equivalent to the content of Msg 2 1312 (e.g., RAR) shown in Figures 13A and 13B, and / or Msg 4 1314 shown in Figure 13A.

[0178] A UE may initiate the two-step random access procedure shown in Figure 13C for licensed and / or unlicensed spectra. The UE may decide whether to initiate the two-step random access procedure based on one or more factors. One or more factors may be the radio access technology in use (e.g., LTE, NR, and / or similar), whether the UE has a valid TA, cell size, the UE's RRC status, the type of spectrum (e.g., licensed versus unlicensed), and / or any other appropriate factors.

[0179] The UE may determine the radio resources and / or uplink transmit power for the transport block 1342 contained in the preamble 1341 and / or Msg A 1331 based on the two-step RACH parameters contained in configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources for transmitting the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmitting 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 receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0180] Transport block 1342 may include data (e.g., latency-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier, timing advance commands, power control commands, uplink authorization (e.g., radio resource allocation and / or MCS), a UE identifier for conflict resolution, and / or RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure has been successfully completed if the preamble identifier in Msg B 1332 matches a preamble sent by the UE, and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0181] UEs and base stations may exchange control signaling. Control signaling may also be called L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). 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] Downlink control signaling may include downlink scheduling assignments, uplink scheduling authorizations indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or other appropriate signaling. A UE may receive downlink control signaling in a payload transmitted by a base station on a physical downlink control channel (PDCCH). The payload transmitted on a PDCCH may be called downlink control information (DCI). In some scenarios, the PDCCH may be a group-common PDCCH (GC-PDCCH) common to a group of UEs.

[0183] A base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate the detection of transmission errors. If the DCI is intended for a UE (or group of UEs), the base station may scramble the CRC parity bits with the UE identifier (or identifier of the group of UEs). Scrambling the CRC parity bits with an identifier may involve a Modulo-2 append (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] DCIs can be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notifications. A P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. A SI-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of a dynamic schedule and / or a random access trigger for a PDCCH sequence. A DCI with a scrambled CRC parity bit in a temporary cell RNTI (TC-RNTI) may exhibit conflict resolution (e.g., Msg3 similar to Msg3 1313 shown in Figure 13A). Other RNTI encodings configured in the UE by the base station include 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 similar.

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

[0186] After scrambling the DCI with 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 coded and modulated DCI onto resource elements used and / or configured for the PDCCH. Based on the DCI payload size and / or base station coverage, the base station may transmit the DCI over a PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (called the aggregate level) can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may contain multiple (e.g., 6) resource element groups (REGs). A REG may contain resource blocks within OFDM symbols. Mapping the coded and modulated DCI onto resource elements may be based on mappings of CCEs and REGs (e.g., CCE-REG mappings).

[0187] Figure 14A shows an embodiment of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources that the UE attempts to decode the DCI using one or more lookup spaces. A base station may configure a CORESET within a time-frequency domain. In the embodiment of Figure 14A, the first CORESET 1401 and the second CORESET 1402 occur in the first symbol in the slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 occurs in the third symbol in the slot. The fourth CORESET 1404 occurs in the seventh symbol in the slot. A CORESET may have a different number of resource blocks within its frequency domain.

[0188] Figure 14B shows an example of CCE-REG mapping for DCI transmissions on CORESET and PDCCH processing. CCE-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment and / or frequency-selective transmission of control channels). A base station may perform different or identical CCE-REG mappings on different CORESETs. A CORESET may be associated with CCE-REG mappings in an RRC configuration. A CORESET may consist of antenna port quasi-identical location (QCL) parameters. The antenna port QCL parameters may indicate QCL information for demodulated reference signals (DMRS) for PDCCH reception within the CORESET.

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

[0190] As shown in Figure 14B, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE~REG mapping to the CORESET (e.g., interleaved or non-interleaved, and / or mapping parameters) based on the CORESET configuration parameters. The UE may determine the number of search space sets configured on the CORESET (e.g., up to 10) based on the RRC message. The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs in a common search space, the number of PDCCH candidates, and / or the number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. Decoding may be called blind decoding. The UE may determine a valid DCI for the UE in response to a CRC check (e.g., a scramble bit against the CRC parity bit of a DCI that matches an RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink permission, power control, slot format indication, downlink preemption, and / or similar).

[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 for a received DL-SCH transport block. After receiving the DL-SCH transport block, the UE may transmit a HARQ acknowledgment. The uplink control signaling may include channel status information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station may determine the transmission format parameters for downlink transmission (e.g., including multi-antenna and beamforming schemes). The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) over the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0192] Five PUCCH formats are possible, and a UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols and the number of UCI bits in the UCI transmission). PUCCH format 0 may have the length of one or two OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 0 to transmit a UCI on a PUCCH resource if the transmission exceeds one or two symbols and has one or two HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits). PUCCH format 1 may occupy a number between 4 and 14 OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 1 if the transmission consists of four or more symbols and has one or two HARQ-ACK / SR bits. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than two bits. A UE may use PUCCH format 2 if the transmission exceeds one or two symbols and has two or more UCI bits. PUCCH format 3 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 3 if the transmission consists of four or more symbols, has two or more UCI bits, and the PUCCH resource does not contain orthogonal cover codes. PUCCH format 4 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 4 if the transmission consists of four or more symbols, has two or more UCI bits, and the PUCCH resource contains orthogonal cover codes.

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

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

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

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

[0197] In the downlink, data transmitted from base station 1504 to radio device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 by, for example, the core network. In the uplink, data transmitted from radio device 1502 to base station 1504 may be provided to processing system 1518 of radio device 1502. Processing systems 1508 and 1518 may process the data for transmission by implementing OSI functions of layers 3 and 2. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include the RRC layer with respect to Figure 2B.

[0198] Data that has been processed by processing system 1508 and is to be transmitted to radio device 1502 may be provided to the transmission processing system 1510 of base station 1504. Similarly, data that has been processed by processing system 1518 and is to be transmitted to base station 1504 may be provided to the transmission processing system 1520 of radio device 1502. Transmission processing systems 1510 and 1520 may implement the OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For transmission processing, the PHY layer may perform, for example, forward error correction coding of the 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 similar.

[0199] At base station 1504, receiving processing system 1512 may receive uplink transmissions from radio device 1502. At radio device 1502, receiving processing system 1522 may receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 may implement OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For receiving processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or similar.

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

[0201] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-temporary computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although not shown in Figure 15, transmitting processing systems 1510, 1520, receiving processing system 1512, and / or receiving processing system 1522 may be coupled to memories (e.g., one or more non-temporary computer-readable media) that store 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. One or more controllers and / or 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, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and base station 1504 to operate in a wireless environment.

[0203] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and / or one or more peripheral devices 1526, respectively. One or more peripheral devices 1516 and / or one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functions, such as speakers, microphones, keypads, display devices, touchpads, power supplies, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, internet browsers, electronic control units (e.g., for vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, and / or similar). Processing system 1508 and / or processing system 1518 may receive user input data from one or more peripheral devices 1516 and / or 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 may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to GPS chipsets 1517 and 1527, respectively. The GPS chipsets 1517 and 1527 may be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0204] Figure 16A shows an exemplary structure for uplink transmission. A baseband signal representing a physical uplink shared channel can perform one or more functions. These functions may include scrambling, modulating scrambled bits to generate complex-valued symbols, mapping complex-valued modulated symbols onto one or more transmit layers, conversion precoding to generate complex-valued symbols, precoding of complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, generation of complex-valued time-domain single-carrier frequency-division multiplexed access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or at least one of the same. In one embodiment, if conversion precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one embodiment, if conversion precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by Figure 16A. These functions are shown as examples, and it is expected that other mechanisms can be implemented in various embodiments.

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

[0206] Figure 16C shows an exemplary structure of a downlink transmit. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include scrambling the encoded bits in the codeword to be transmitted over the physical channel, modulating the scrambled bits to generate a complex-valued modulation symbol, mapping the complex-valued modulation symbol to one or more transmit layers, precoding the complex-valued modulation symbol on the layer for transmission over the antenna port, mapping the complex-valued modulation symbol to resource elements at the antenna port, generating a complex-valued time-domain OFDM signal for each antenna port, and / or similar. These functions are shown as examples, and it is expected that other mechanisms can be implemented in various embodiments.

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

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

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

[0210] A gNB can transmit one or more MAC PDUs to a wireless device. In one embodiment, a MAC PDU may be a bit string of byte-aligned length (e.g., a multiple of 8 bits). In one embodiment, the bit string may 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, then in the reading order of the rows. In one embodiment, the bit order of the parameter fields in 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 may be a bit string of byte-aligned length (e.g., a multiple of 8 bits). In one embodiment, the MAC SDU may be contained within the MAC PDU from the first bit onward. In one embodiment, the MAC CE may be a bit string of byte-aligned length (e.g., a multiple of 8 bits). In one embodiment, the MAC subheader may be a bit string of byte-aligned length (e.g., a multiple of 8 bits). In one embodiment, the MAC subheader may be placed immediately before the corresponding MAC SDU, MAC CE, or padding. MAC entities may ignore the values ​​of reserved bits in the DL MAC PDU.

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

[0213] In one embodiment, if the MAC subheader corresponds to a MAC SDU, a variable-size MAC CE, or padding, the MAC subheader may include a 1-bit R field, a 1-bit F field, a multi-bit LCD field, and / or a multi-bit L field.

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

[0215] Figure 18A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, can be placed together. A MAC sub-PDU containing MAC CEs can be placed before any MAC sub-PDU containing a MAC SDU or a MAC sub-PDU containing padding. Figure 18B shows an example of a UL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, can be placed together. A MAC sub-PDU containing MAC CEs can be placed after all MAC sub-PDUs containing MAC SDUs. Furthermore, a MAC sub-PDU can be placed before a MAC sub-PDU containing padding.

[0216] In one embodiment, the MAC entity of a gNB can transmit one or more MAC CEs to the MAC entity of a wireless device. Figure 19 shows an embodiment of several LCIDs that may be associated with one or more MAC CEs. One or more MAC CEs include at least one of the following: SP ZP CSI-RS resource set start / stop MAC CE, PUCCH spatial relationship start / stop MAC CE, SP SRS start / stop MAC CE, SP CSI report start / stop MAC CE for PUCCH, UE-specific PDCCH TCI status display MAC CE, UE-specific PDSCH TCI status display MAC CE, non-periodic CSI trigger state subselection MAC CE, SP CSI-RS / CSI-IM resource set start / stop MAC CE, UE conflict resolution identity MAC CE, timing advance command MAC CE, DRX command MAC CE, long DRX command MAC CE, SCell start / stop MAC CE (1 octet), SCell start / stop MAC CE (4 octets), and / or duplicate start / stop MAC CE. In one embodiment, a MAC CE, such as a MAC CE transmitted by the MAC entity of a gNB to the MAC entity of a wireless device, may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheaders corresponding to them. For example, an LCID given by 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0217] In one embodiment, the MAC entity of a wireless device may send one or more MAC CEs to the MAC entity of a gNB. Figure 20 shows an embodiment of one or more MAC CEs. One or more MAC CEs may include at least one of the following: a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured authorization confirmation MAC CE, a single-entry PHR MAC CE, a multi-entry PHR MAC CE, a short-block BSR, and / or a long-block BSR. In one embodiment, a MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheaders corresponding to the MAC CEs. For example, an LCID given by 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short-block command MAC CE.

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

[0219] When configured with CA, base stations and / or radio devices may use the SCell start / stop mechanism to improve the radio device's battery or power consumption. When a radio device is configured with one or more SCells, the gNB can start or stop at least one of the one or more SCells. A SCell can be stopped unless the SCell state associated with the SCell is set to "started" or "hibernated" when the SCell is configured.

[0220] A wireless device can start / stop SCell in response to receiving a SCell start / stop MAC CE. In one embodiment, the gNB may send one or more messages to the wireless device that include a SCell timer (e.g., sCellDeactivationTimer). In one embodiment, the wireless device may stop SCell in response to the expiration of the SCell timer.

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

[0222] When a wireless device receives a SCell Start / Stop MAC CE that stops an activated SCell, the wireless device may stop the activated SCell. In one embodiment, when a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires, the wireless device may stop the activated SCell. In response to the deactivation of an activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In one embodiment, in response to the deactivation of an activated SCell, the wireless device may clear one or more configured downlink assignments and / or one or more configured uplink permissions of configured uplink permission type 2 associated with the activated SCell. In one embodiment, in response to the deactivation of an activated SCell, the wireless device may suspend one or more configured uplink permissions of configured uplink permission type 1 associated with the activated SCell and / or flush the HARQ buffer associated with the activated SCell.

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

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

[0225] In Figure 21A and / or Figure 21B, if a SCell having SCell index i is configured, C i The field may indicate the start / stop status of the SCell having SCell index i. In one embodiment, C i When the field is set to 1, an SCell having SCell index i may be invoked. In one embodiment, C i When the field is set to zero, the SCell having SCell index i may be stopped. In one embodiment, if there is no SCell configured with SCell index i, the wireless device C i The field can be ignored. In Figures 21A and 21B, the R field may represent a reserved bit. The R field can be set to zero.

[0226] A base station (gNB) can configure a radio device (UE) using uplink (UL) bandwidth portions (BWPs) and downlink (DL) BWPs to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation is configured, the gNB can further configure the UE using at least a DL BWP to enable BA on an SCell (i.e., the UL may not have a UL BWP). For a PCell, the initial active BWP may be the first BWP used for initial access. For an SCell, the first active BWP may be the second BWP to which the UE is configured to operate on the SCell when the SCell is activated. For paired spectra (e.g., FDD), the gNB and / or UE can switch the DL BWP and UL BWP independently. For unpaired spectra (e.g., TDD), the gNB and / or UE can switch the DL BWP and UL BWP simultaneously.

[0227] In one embodiment, the gNB and / or UE can switch between configured BWPs by DCI or BWP inactive timer. If a 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, for an FDD system, if configured as a BA, one UL BWP and one DL BWP may be active simultaneously in an active serving cell for each uplink carrier. In one embodiment, for a TDD system, one DL / UL BWP pair may be active simultaneously in an active serving cell. Operating with one UL BWP and one DL BWP (or one DL / UL pair) may improve the UE's battery consumption. BWPs other than the one active UL BWP and one active DL BWP on which the UE can operate may be deactivated. In a stopped BWP, the UE does not need to monitor PDCCH and / or transmit on PUCCH, PRACH, and UL-SCH.

[0228] In one embodiment, a 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 an active BWP at once. 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. Upon addition of a SpCell or activation of an SCell, one BWP may first become active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP of a serving cell can be indicated by RRC and / or PDCCH. In one embodiment, for unpaired spectrum, a DL BWP can be paired with an UL BWP, and BWP switching may be common to both UL and DL.

[0229] FIG. 22 shows an example of BWP switching on a SCell. In one example, the UE may receive an RRC message including parameters of the SCell and one or more BWP configurations associated with the SCell. The RRC message may 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 may be configured as a first active BWP (e.g., BWP1), and one BWP may be configured as a default BWP (e.g., BWP0). The UE may receive a MAC CE and activate the SCell in the nth slot. The UE may 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 may start monitoring the PDCCH on BWP1.

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

[0231] In one embodiment, a MAC entity may apply normal operations to the active BWP of an activated serving cell configured with a BWP, including sending with UL-SCH, sending with RACH, monitoring PDCCH, sending PUCCH, receiving DL-SCH, and / or, if any, (re)initializing a suspended configured uplink authorization of authorization type 1 configured according to the stored configuration.

[0232] In one embodiment, on an inactive BWP of each activated serving cell configured in a BWP, the MAC entity may not transmit RACH, not monitor PDCCH, not transmit PUCCH, not transmit SRS, not receive DL-SCH, clear any configured downlink assignments and configured uplink authorizations of configured authorization type 2, and / or suspend any configured uplink authorizations of configured type 1.

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

[0234] In one embodiment, for a primary cell, the UE may be provided with a default DL BWP among the DL BWPs configured for the UE by the upper layer parameter Default-DL-BWP. In one embodiment, if the upper layer parameter Default-DL-BWP does not provide the UE with a default DL BWP, the default DL BWP may be the initial active DL BWP. In one embodiment, the UE may be provided with a timer value for the primary cell by the upper layer parameter bwp-InactivityTimer. If configured, the UE may increment the timer every 1 millisecond interval for frequency range 1 and every 0.5 milliseconds for frequency range 2 when running, if the UE is unable to detect DCI format 1_1 for paired spectral activity, or if the UE is unable to detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectral activity during the interval.

[0235] In one embodiment, if the UE is configured for a secondary cell using the upper layer parameter Default-DL-BWP, which indicates the default DL BWP among the configured DL BWPs, and the UE is configured using the upper layer parameter bwp-InactivityTimer, which indicates a timer value, then 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, if the UE is configured on a secondary cell or carrier by an upper layer parameter Active-BWP-DL-SCell which is a first active DL BWP and an upper layer parameter Active-BWP-UL-SCell which is a first active UL BWP, the UE can use the indicated DL BWP and indicated UL BWP on the secondary cell as the first active DL BWP and first active UL BWP on the secondary cell or on the carrier, respectively.

[0237] In one embodiment, the set of PDCCH candidates for the wireless device to be monitored is defined in terms 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 Type0-PDCCHCSS set configured by pdcch-ConfigSIB1 in the MIB, or by searchSpaceSIB1 in PDCCH-ConfigCommon, or by searchSpaceZero in PDCCH-ConfigCommon, for a DCI format having a CRC scrambled by SI-RNTI in the primary cell of MCG; a Type0A-PDCCHCSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon, for a DCI format having a CRC scrambled by SI-RNTI in the primary cell of MCG; a Type1-PDCCHCSS set configured by ra-SearchSpace in PDCCH-ConfigCommon, for a DCI format having a CRC scrambled by RA-RNTI or TC-RNTI in the primary cell of MCG; P-RNT A Type2-PDCCHCSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for DCI formats having CRCs scrambled by I, a Type3-PDCCHCSS set configured by SearchSpace in PDCCH-Config with searchSpaceType=common for DCI formats having CRCs scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, and only for primary cells, C-RNTI, MCS-C-RNTI, or CS-RNTI, and a USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific for DCI formats having CRCs 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

Number

Number

Number

Number

Number

Number

number

number

number

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

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

[0242] Figure 24 shows an embodiment of the configuration of a control resource set (CORESET). In one embodiment, a base station can transmit one or more configuration parameters of the CORESET to a radio device. The configuration parameters may include at least one of the following: a CORESET ID that identifies the CORESET, a frequency resource indicator, a duration parameter indicating the number of symbols in the CORESET, a CCE-REG mapping type indicator, multiple TCI states, an indicator indicating whether a TCI is present in a DCI, and similar. The frequency resource indicator, which includes a number of bits (e.g., 45 bits), indicates a frequency domain resource, where each bit of the indicator corresponds to a group of 6RBs, and the grouping begins with the first group of RBs in the BWP of a cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit corresponds to the first group of RBs in the BWP, and so on. A bit set to 1 indicates that the group of RBs corresponding to that bit belongs to the frequency domain resource of this CORESET. Bits corresponding to groups of RBs that are not fully included in the BWP in which the CORESET is configured are set to zero.

[0243] Figure 25A shows an embodiment of a data reception flowchart in a wireless device. In one embodiment, the wireless device receives one or more RRC messages containing cell configuration parameters, and the cell contains one or more BWPs. The configuration parameters indicate one or more CORESETs and / or one or more search spaces (SSs) configured on one or more BWPs. One or more CORESETs and / or one or more SSs may be implemented as in the embodiments of Figures 23 and / or 24.

[0244] As shown in Figure 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 a DCI indicating a downlink assignment to a PDCCH. Monitoring PDCCH candidates on an SS may include attempting to decode the DCI content of a PDCCH candidate having one or more PDCCH monitoring locations, one or more CCEs based on the aggregation level, multiple PDCCH candidates, and one or more DCI formats. One or more RRC messages may indicate the number of PDCCH candidates for each aggregation level on an SS. The wireless device may determine the number of CCEs for each aggregation level to detect a DCI. In one embodiment, the wireless device may determine one CCE to detect a 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 sixteen CCEs when the aggregation level is 16. Figure 25B shows an embodiment of CCEs and REGs on a BWP.

[0245] In one embodiment, the wireless device has a PDCCH monitoring opportunity,

number

number

number

number

number

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

[0247] In response to receiving a DCI, the radio device may receive a symbol for a transport block (TB) via a downlink assignment. The radio device may attempt to decode the TB based on the received symbol. The radio device may generate an acknowledgment (ACK) in response to successful decoding. The radio device may generate a negative acknowledgment (NACK) in response to unsuccessful decoding.

[0248] In one embodiment, a wireless device may send an ACK / NACK via a 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 one or more CCEs from which the wireless device receives the DCI, the cell index of the cell on which the wireless device monitors PDCCH candidates, and the RNTI value for receiving the DCI.

[0249] Figure 25B shows an example of PUCCH resource determination. In one embodiment, a radio device may receive one or more RRC messages containing configuration parameters for a BWP with bandwidth, including the cell's BWP, one or more radio resource units (e.g., RBs as shown in Figure 8). The configuration parameters may indicate resource allocation for one or more CORESETs. CORESETs are in the frequency domain.

number

number

number

[0250] In one embodiment, a wireless device may monitor PDCCH candidates for SS on one or more CCEs having RBGs of CORESET on an active BWP. A CCE may contain multiple (e.g., 6) resource element groups (REGs). A REG may contain one RB within a single OFDM symbol. REGs in a CORESET are numbered sequentially in a time-first manner, starting from 0, with respect to the first OFDM symbol and the smallest numbered resource block in the CORESET. In one embodiment, a CORESET consists of a single CCE-REG mapping indicator.

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

number

number

number

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

number

number

number

number

number

number

[0253] In one embodiment, the set of PDCCH candidates for the UE to monitor is defined with respect to a PDCCH search space set. The search space set may be a CSS set or a USS set. The UE monitors PDCCH candidates in one or more of the following search space sets: - A Type0-PDCCHPDCCH 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; - For DCI format with CRC scrambled by SI-RNTI on the primary cell of the MCG, the Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation within PDCCH-ConfigCommong; - For DCI formats with CRCs scrambled by RA-RNTI or TC-RNTI on the primary cell, a Type1-PDCCHPDCCH CSS set configured by ra-SearchSpace within PDCCH-ConfigCommon; - For DCI format with CRC scrambled by P-RNTI on the primary cell of the MCG, a Type2-PDCCHPDCCH CSS set configured by packingSearchSpace in PDCCH-ConfigCommon; - For DCI formats having CRCs scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, and only for primary cells by C-RNTI, MCS-C-RNTI, RNTI, or CS-RNTI, searchSpaceType=common, and a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config, and - For DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI, a USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific.

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

number

number

number

number

number

number

number

number

number

[0255] Figure 25B shows that the cell's BWP may include M RBGs indexed from RBG 0 to RBG M-1. A CORESET configured on the BWP may occupy multiple RBGs of M RBG 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, and so on. The number of RBG radio resources may be mapped to the number of CCEs indexed from CCE0 to CCE(N-1) based on multiple CCEs and CCE~REG mapping indicators (e.g., CCE~REG-MappingType). A radio device may monitor PDCCH candidates for SS on a subset of the number of CCEs, including, for example, CCE2, CCE4, CCE6, etc.

[0256] In one embodiment, a wireless device may receive a DCI on the SS, starting from CCE2, based on the equation above. The wireless 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 in Figure 25B).

[0257] In one embodiment, the wireless device may not have a dedicated PUCCH resource configuration. The wireless device may determine a PUCCH resource set based on a predefined PUCCH resource table in order to transmit HARQ-ACK information on the PUCCH. The PUCCH resource set contains 16 resources, each corresponding to the PUCCH format, start symbol, duration, PRB offset, and periodic shift index set for PUCCH transmission.

[0258] In one embodiment, the wireless device is index r PUCCH It is possible to determine the PUCCH resource that has [this].

number

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

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

number

[0261] In one embodiment, a wireless device may transmit one or more uplink control information (UCIs) to a base station via one or more PUCCH resources. One or more UCIs may include at least one of HARQ-ACK information, scheduling requests (SRs), and / or CSI reports. In one embodiment, a PUCCH resource may be identified by at least a frequency position (e.g., start PRB) and / or a PUCCH format. A PUCCH format may be constructed using an initial period shift value and a time-domain position parameter (e.g., start symbol index) of a base array. In one embodiment, a 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 one or two OFDM symbols and may be 2 bits or less. PUCCH format 1 occupies a number of OFDM symbols from 4 to 14 and may be 2 bits or less. PUCCH format 2 occupies one or two OFDM symbols and may be larger than 2 bits. PUCCH format 3 occupies 4 to 14 OFDM symbols and can be larger than 2 bits. PUCCH format 4 occupies 4 to 14 OFDM symbols and can be larger than 2 bits. PUCCH resources can be configured on a PCell or on a PUCCH secondary cell.

[0262] In one embodiment, when composed of multiple UL BWPs, a base station may transmit one or more RRC messages containing configuration parameters for one or more PUCCH resource sets (e.g., 1, 2, 3, 4, or greater than 4) to a radio device via the UL BWPs of the multiple UL BWPs. Each PUCCH resource set may consist of a PUCCH resource set index, a list of PUCCH resources, each PUCCH resource identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the maximum number of UCI information bits that a radio device may transmit using one of the lists of multiple PUCCH resources within the PUCCH resource set.

[0263] In one embodiment, when configured with 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 configuration 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 configuration value and less than or equal to a second configuration 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 configuration value and less than or equal to the third value (e.g., 1706), the wireless device may select a fourth PUCCH resource set in which the PUCCH resource set is equal to "3".

[0264] In one embodiment, a 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 and the number of UCI bits in a UCI transmission. In one embodiment, if the transmission has more than one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is 1 or 2, the wireless device may transmit the UCI in a PUCCH using PUCCH format 0. PUCCH format 0 may be based on DFT-spread OFDM, for example, to reduce the cubic meter. In one embodiment, if the transmission has more than four symbols and the number of HARQ-ACK / SR bits is 1 or 2, the wireless device may transmit the UCI in a PUCCH using PUCCH format 1. PUCCH format 1 may be based on DFT-spread OFDM, for example, to reduce the cubic meter. In one embodiment, if the transmission consists of more than one or two symbols and the number of UCI bits is greater than two, the wireless device may transmit the UCI in a PUCCH using PUCCH format 2. PUCCH format 2 may be based on OFDM. In one embodiment, if the transmission consists of more than four symbols and the number of UCI bits is greater than two, and the PUCCH resource does not contain orthogonal cover codes, the wireless device may transmit the UCI in a PUCCH using PUCCH format 3. PUCCH format 3 may be based on DFT-spread OFDM, for example, to reduce the cubic meter. In one embodiment, if the transmission consists of more than four symbols and the number of UCI bits is greater than two, and the PUCCH resource contains orthogonal cover codes, the wireless device may transmit the UCI in a PUCCH using PUCCH format 4. PUCCH format 4 may be based on DFT-spread OFDM, for example, to reduce the cubic meter.

[0265] In one embodiment, to transmit HARQ-ACK information on a PUCCH resource, the 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 a PUCCH resource based on the PUCCH resource indicator field in the DCI received in the PDCCH (e.g., having a DCI for DCI format 1_0 or 1_1). The 3-bit PUCCH resource indicator field in the DCI may indicate one of the eight PUCCH resources in 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 in the DCI.

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

[0267] In exemplary embodiments, Listen-before-talk (LBT) may be implemented for transmissions on cells consisting of unlicensed bands (for convenience, these may be referred to, for example, LAA cells and / or NR-U cells; LAA and NR-U cells may refer to any compatible cell operating on unlicensed bands. A cell may operate as a non-standalone with an anchor cell on a licensed band, or as a standalone without an anchor cell on a licensed band). LBT may include clear channel evaluation. For example, in an LBT procedure, an instrument may apply a clear channel evaluation (CCA) check before using a channel. For example, a CCA includes at least energy detection to determine the presence or absence of other signals on the channel (e.g., the channel is occupied) or (e.g., the channel is clear). Regulations in a particular country may influence LBT procedures. For example, European and Japanese regulations mandate the use of LBT on unlicensed bands, such as the 5 GHz unlicensed band. Apart from regulatory requirements, carrier sensing via LBT is one way to fairly share unlicensed spectrum.

[0268] In exemplary embodiments, discontinuous transmission on an unlicensed carrier with a limited maximum transmission duration may be enabled. Some of these functions may be supported by one or more signals transmitted from the start of discontinuous downlink transmission in the unlicensed band, and channel reservation may be enabled by the transmission of a signal by an NR-U node after gaining 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 certain threshold at which they can sense that the channel is occupied. Functions that need to be supported by one or more signals for operation in the unlicensed band with discontinuous downlink transmission may include one or more of the following: detection of downlink transmission in the unlicensed band (including cell identification) by a radio device, and synchronization of the radio device's time and frequency.

[0269] In exemplary embodiments, DL transmission and frame structure design for operation in unlicensed bandwidth may employ subframe, (mini)slot, and / or symbol boundary alignment according to carrier aggregate timing relationships across serving cells aggregated by the CA. This does not necessarily mean that base station transmissions begin at subframe, (mini)slot, and / or symbol boundaries. Unlicensed cell operation (e.g., LAA and / or NR-U) may support PDSCH transmission, for example, when not all OFDM symbols can be transmitted in subframes according to LBT. Distribution of control information required for PDSCH may also be supported.

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

[0271] Various LBT mechanisms can be implemented. In one embodiment, for some signals, in some implementation mode scenarios, in some situations, and / or at some frequencies, the LBT procedure may not be performed by the transmitting entity. In one embodiment, Category 1 (CAT1, e.g., no LBT) may be implemented in one or more instances. 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 radio 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) may be implemented. The period for determining that a channel is idle may be deterministic (e.g., by regulation). The base station may transmit an uplink permission to the radio device indicating one type of LBT (e.g., CAT2 LBT). CAT1 LBT and CAT2 LBT may be used for COT sharing. For example, the base station may transmit an uplink permission (lesprurious uplink control information) including the type of LBT. For example, CAT1 LBT and / or CAT2 LBT in uplink permission (or uplink control information) may indicate to receiving equipment (e.g., base stations and / or radio devices) 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 may have the following steps as one of its components: A transmitting entity can draw a random number N within a 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 as 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 resize the contention window when drawing the random number N. The random number N is used in the LBT procedure to determine the duration for which the channel is perceived as idle before the transmitting entity transmits on the channel.

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

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

[0274] In one embodiment, a DL transmit burst may be a series of transmissions (unicast, multicast, broadcast, and / or a combination thereof) by a base station (e.g., one or more radio devices) on a carrier component (CC). A UL transmit burst may be a series of transmissions from one or more radio devices to a base station on a CC. In one embodiment, DL transmit bursts and UL transmit bursts on a CC in an unlicensed spectrum may be scheduled in a TDM manner on the same unlicensed carrier. Switching between DL transmit bursts and UL transmit bursts may require LBTs (e.g., CAT1 LBT, CAT2 LBT, CAT3 LBT, and / or CAT4 LBT). For example, a given moment may be part of either a DL transmit burst or a UL transmit burst.

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

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

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

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

[0279] In one embodiment, a broadband carrier having multiple channels (subbands, SBs, RB sets, etc.) is supported in unlicensed bandwidth. In one embodiment, there may be one active BWP within the carrier. Channels (subbands, RB sets, etc.) may contain multiple RBs within the BWP for data / control signal transmission. Hereinafter, channels may also be referred to as subbands, SBs, RB sets, etc. In one embodiment, a BWP with one or more channels may be activated. In one embodiment, if the absence of Wi-Fi cannot be guaranteed (e.g., due to regulations), LBT can be performed in 20 MHz increments. In this case, multiple parallel LBT procedures may exist for this BWP. The actual transmit bandwidth may be affected by the success of the LBT, which can result in dynamic bandwidth transmission within this active broadband BWP.

[0280] In one embodiment, one or more active BWPs may be supported. To improve BWP utilization efficiency, the BWP bandwidth may be the same as the SB bandwidth of the LBT. For example, LBT may be performed on each BWP. The network can activate / deactivate BWPs based on the amount of data being transmitted. In one embodiment, one or more non-overlapping BWPs may be activated for a radio device in a wide component carrier, which may be similar to a carrier aggregate. To improve BWP utilization efficiency, the BWP bandwidth may be the same as the SB bandwidth of the LBT, i.e., LBT may be a carrier out on each BWP. Successful LBT on multiple SBs requires the radio device to have the ability to support one or more narrow RF or wide RF, which may include one or more activated BWPs.

[0281] In one embodiment, a single broadband wavepoint (BWP) may be activated for wireless devices within a component carrier. The bandwidth of the broadband BWP may be in units of the signal-to-bandwidth (SB) of the load-to-band (LBT). For example, if the LBT's SB is 20 MHz in the 5 GHz band, the broadband BWP bandwidth may include multiple 20 MHz units. The actual transmit bandwidth may be affected by the SB of the LBT, which can result from dynamic bandwidth transmission within this active broadband BWP.

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

[0283] Figure 27A shows an example of an SS / CORESET configuration in a BWP. In one embodiment, the frequency resource representation of the first SS or first CORESET configuration may show frequency resource distribution across multiple RB groups within the BWP. The multiple RB groups are not limited to, or are not limited to, the SB (e.g., 20 MHz) of the BWP. By distributing frequency resources within the BWP, the base station can flexibly allocate PDCCH resources to different UEs or different signaling purposes (e.g., common or UE-specific).

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

[0285] In one embodiment, the BWP may include multiple (e.g., 4) LBT SBs (SBs, or RB sets), each LBT SB occupying multiple RBs (or RB groups) of the BWP. The first LBT SB may overlap in frequency domains having a second LBT SB. The first LBT SB may not overlap in frequency domains having a second LBT SB.

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

[0287] In one embodiment, a base station may allocate a physical resource block (PRB) confined within one of the SBs of the BWP corresponding to the CORESET to a CORESET (for example, in the frequencyDomainResources high-level parameter of the CORESET in the RRC message, as shown in Figure 24) for a search space set configuration associated with multiple monitoring locations in a frequency domain. Within the search space set associated with the CORESET, each of the multiple monitoring locations in the frequency domain corresponds to (and / or is limited to) the SB of the SB. Each of the multiple monitoring locations may have a frequency domain resource allocation pattern replicated from the pattern configured in the CORESET. In the embodiment, CORESET parameters other than the frequency domain resource allocation pattern may be identical for each of the multiple monitoring locations in the frequency domain.

[0288] In one embodiment, before receiving a DCI, the radio device may not need to know which SB the base station can successfully perform the LBT procedure on (for example, if the LBT procedure indicates that the channel is clear on the SB) or which SB the base station can transmit a DCI on. If the BWP consists of multiple LBT SBs, the radio device may monitor PDCCHs on multiple SBs for receiving a DCI.

[0289] In one embodiment, a base station may transmit one or more RRC messages to a radio device, which include configuration parameters for a search space, indicating one or more SBs on which the radio device can monitor PDCCH candidates in the search space. Based on the configuration parameters, the radio device can monitor PDCCH candidates associated with the search space on one or more SBs.

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

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

[0292] In one exemplary embodiment, a wireless device may index the CCEs of a CORESET for each RB set of a BWP starting from the same initial value (e.g., 0). In one embodiment, the wireless device may index the CCEs of a CORESET in a first RB set of a BWP from 0 to N-1, where N is the total number of CCEs of a CORESET in the RB set. The wireless device may index the CCEs of a CORESET in a second RB set of a BWP from 0 to N-1. Based on indexing the CCEs of a CORESET from the same initial value for different RB sets of a BWP, the wireless device may determine a PUCCH resource based on the DCI, the PUCCH resource index indicated by the DCI, the total number of CCEs of a CORESET, and the CCE index of the starting CCE of one or more CCEs. 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 for. Exemplary embodiments enable base stations to reduce PUCCH resource allocation / reservation for wireless devices, and thus improve uplink resource utilization efficiency.

[0293] Figure 28 shows an exemplary embodiment of a PUCCH resource allocation / determination method for broadband NR-U cells.

[0294] In one embodiment, a base station can transmit one or more RRC messages to a radio device containing configuration parameters for a cell (e.g., PCell, or SCell). A cell may contain multiple BWPs. A cell may contain a single BWP. In one embodiment, a BWP may contain multiple (e.g., 4) LBT SBs (a set of SBs or RBs which may be equally referred to herein), each SB occupying multiple RBs (or groups of RBs) of the BWP. As shown in Figure 28, the SBs of the BWP include SB0, SB1, SB2, and so on. Configuration parameters may indicate multiple CORESETs configured on the BWP. Configuration parameters may indicate that the frequency resources of the multiple CORESETs are limited to the bandwidth of the SBs of the BWP. The frequency resource mapping pattern of the CORESETs on the first SB (e.g., defining which resource blocks of the first SB the CORESET includes, as shown by frequencyDomainResources in Figure 24) is replicated to the remaining SBs of the BWP. Configuration parameters may indicate that multiple SSs are configured on the CORESETs. For each of the multiple SSs, the configuration parameters may include monitoring frequency position parameters (e.g., a bitmap or monitoring position display as shown in Figure 28) that indicate which SB the monitoring frequency position of the SS is configured to. As shown in Figure 28, the SS (e.g., SS i The monitoring position indicator includes a bit string "110..." indicating the monitoring frequency position, which includes SB0 and SB1. In response to the monitoring frequency position including SB0 and SB1, the wireless device displays SS on SB0 and SB1. i You may also monitor the SS on the remaining SBs (e.g., SB2 and SB3). i There's no need to monitor it.

[0295] In one embodiment, SS on SB0 and SB1 i In response to monitoring, the wireless device will use SS on SB0. i DCI on CCE and / or SS on SB1 iA wireless device may attempt to detect DCIs (e.g., simultaneously or sequentially) on CCEs. The wireless device may index CCEs on different SBs of the BWP from the same initial value (e.g., 0) up to N-1 (e.g., N is the total number of CCEs in the SB). Based on the indexing of CCEs, the wireless device may attempt to detect the first DCIs on CCE2, CCE4, CCE6, ... on SB0, and the second DCIs on CCE2, CC4, CCE6, ... on SB1, where CC2, CC4, CC6, ... are SS, by implementing the example in Figure 25B. i This will be decided.

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

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

[0298] In one embodiment, a wireless device can determine a PUCCH resource for transmitting acknowledgment information based on the initiation CCE, the PR of the DCI, by implementing the exemplary embodiment described above with respect to Figure 25A and / or Figure 25B. As shown in Figure 28, the initiation CCE may have a CCE index equal to 2, regardless of the SB on which the wireless device receives the DCI. By implementing the exemplary embodiment, the wireless device may also determine a PUCCH resource based on the CCE index of the initiation CCE, where the CCEs in the SB are indexed from the same initial value for each SB of the BWP. The wireless device may determine a PUCCH resource based on the CCE index of the initiation CCE, regardless of the SB on which the wireless device receives the DCI (first DCI or second DCI). Otherwise, based on existing technology, a wireless device may determine different initiation CCE indices when receiving DCIs on different SBs. Thus, a wireless device may determine different PUCCH resources for transmitting UCIs based on different initiation CCE indices. Exemplary embodiments enable base stations to reduce PUCCH resource allocation / reservation for wireless devices, and thus improve uplink resource utilization efficiency.

[0299] In an NR-U cell (or a cell's BWP), a radio device may monitor a SS (or a PDCCH candidate for an SS) on one or more SBs of the BWP. The radio device may receive multiple DCIs on multiple SBs of one or more SBs, each DCI received via the CORESET search space on each of the SBs of one or more SBs. The radio device may receive multiple DCIs on multiple SBs if the base station successfully completes the LBT procedure for multiple SBs. Receiving multiple DCIs on multiple SBs can increase system throughput, for example, when each DCI schedules its respective TB. Based on existing techniques, the radio device may determine the same PUCCH resource for HARQ-ACK transmissions to different TBs scheduled by multiple DCIs. This can lead to collisions of HARQ-ACK transmissions to different TBs. Thus, existing techniques can result in collisions of UCI transmissions on PUCCH (within the same radio device or between different radio devices), reduced system throughput, increased uplink transmission delay, and / or increased power consumption. Therefore, in order to improve uplink resource utilization efficiency, system throughput, reduction of UCI transmission collisions, and reduction of power consumption, it is necessary to improve the PUCCH resource allocation method for broadband NR-U.

[0300] Figure 29 shows an embodiment of a PUCCH resource determination mechanism when multiple PDCCH monitoring frequency positions on multiple SBs of a BWP are supported. In one embodiment, a base station can send one or more RRC messages to a radio device that include configuration parameters for a cell (e.g., PCell, or SCell). A cell may include multiple BWPs. A cell may include a single BWP. In one embodiment, a BWP may include multiple (e.g., 4) SBs, each SB occupying multiple RBs (or RB groups) of the BWP. As shown in Figure 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 a CORESET are limited to the bandwidth of the BWP's SBs. The configuration parameters may indicate that multiple SSs are configured on the CORESET. For each of the multiple SSs, the configuration parameters may include monitoring frequency position parameters (e.g., a bitmap or monitoring position display shown in Figure 29) indicating which SB the monitoring frequency position of the SS is configured on. As shown in Figure 29, SS (for example, SS i The monitoring position indicator includes a bit string "110..." which indicates the monitoring frequency position including SB0 and SB1, and each bit in the bit string indicates whether the corresponding SB should be monitored by the SS's radio device. In response that the monitoring frequency position includes SB0 and SB1, the radio device monitors the SS on SB0 and SB1. i You may also monitor other SBs on BWP, i There's no need to monitor it.

[0301] In one embodiment, a wireless device may index the CCEs of each CCE in an SB based on at least one of the SB index and the total number of CCEs in the CORESET. In one embodiment, the CORESET on SB0 may contain the same total number of CCEs on SB1. In the example in Figure 29, the total number of CCEs in 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 CORESET on SBj as follows: N*(j-1) + i, starting from zero. The wireless device may index the i-th CCE of the CORESET on SBj as follows: N*(j-1) + i-1, starting from i. Having different CCE indices for different SBs can help wireless devices reduce PUCCH resource conflicts.

[0302] In one embodiment, a base station may transmit one or more RRC messages to a radio device that include configuration parameters for a BWP including a plurality of SBs. The configuration parameters indicate the CCE index offset (e.g., SB-specific) for each of the plurality of SBs relative to the 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 radio device can index the i-th CCE on the first SB as the first CCE_index_offset+i, index the i-th CCE on the second SB as the second CCE_index_offset+i, and so on. The CCE index offset for each SB may be a cell-specific parameter or a UE-specific parameter. In response that the CCE index offset is a cell-specific parameter, the base station may transmit the CCE index offset in system information. In response that the CCE index offset is a UE-specific parameter, the base station may transmit the CCE index offset in a UE-specific cell configuration message.

[0303] As shown in Figure 29, the wireless device may attempt to detect DCIs on CCEs on SB0 and SB1. In one embodiment, the wireless device may attempt to detect first DCIs on CCE2, CCE4, CCE6,... on SB0, where CC2, CC4, CC6,... are SS by implementing the embodiment shown in Figure 25B. i 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 Figure 29, the wireless device is on SB0 of BWP. i The first DCI on the CCE can be received. The wireless device is SS on SB1 of the BWP. iA second DCI may be received on the CCE. The first starting CCE on SB0 where the first DCI is received may have a first CCE index (e.g., 2 as shown in Figure 29). The second starting CCE on SB1 where the second DCI is received may have a second CCE index (e.g., N+2 as shown in Figure 29). The first and second starting CCEs located in the same place on SB0 and SB1 may have different CCE indices. In one embodiment, the first DCI may have the same PRI value as the second DCI.

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

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

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

[0308] In one embodiment, if the wireless device does not have a dedicated PUCCH resource configuration, the wireless device uses the first PUCCH resource, r, based on the first start CCE, first DCI, first PRI. PUCCH ,of

number

[0309] As shown in Figure 29, the wireless device uses a second PUCCH resource based on the second PRI of the second DCI, the second start CCE, and the second r PUCCH of,

number

[0310] In one embodiment, when the wireless device has a dedicated PUCCH resource configuration, the wireless device determines the first PUCCH resource, r, from a set of PUCCH resources (for example, the first set if composed of multiple sets of PUCCH resources) based on the first starting CCE and the first PRI of the first DCI PUCCH (for example, 0 ≦ r PUCCH ≦ R PUCCH -1) as

Number

[0311] In one embodiment, the wireless device determines the second PUCCH resource, r, based on the second starting CCE and the second PRI of the second DCI PUCCH (for example, 0 ≦ r PUCCH ≦ R PUCCH -1) as

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 embodiment, 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 for different SBs. In one embodiment, 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 embodiment, when the wireless device reuses the CCE index for different SBs, the wireless device may determine the PUCCH resource, r PUCCH as

Number

[0315] In one embodiment, when a wireless device reuses a CCE index on a different SB, the wireless device selects a PUCCH resource from a set of PUCCH resources (e.g., the first set when it consists of multiple sets of PUCCH resources) 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. PUCCH (For example, 0≦r PUCCH ≤R PUCCH -1) can be determined. In one embodiment, the wireless device is r PUCCH of

number

[0316] In the formula, N' CCE,p =K*N CCE,p , N CCE,p k is the total number of CCEs in CORESETp on the SB, k is the total number of SBs that the wireless device is configured to monitor, and 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 This is the value of the PRI field in DCI. In one embodiment, if the total number of SBs is greater than 2, SB_index is

number

[0317] Figure 30 shows a flowchart of an example of the PUCCH resource determination mechanism. In one embodiment, the base station may send one or more RRC messages containing cell configuration parameters to the radio device (not shown in Figure 30). The cell may contain multiple BWPs. One of the multiple BWPs may contain multiple SBs. In one embodiment, the base station may send a command (e.g., DCI) to the radio device indicating the activation of a BWP. In response to receiving the command, the radio device may activate the BWP. In response to the activation of the BWP, the radio device may monitor the SS of the CORESET on the first and second SBs and monitor the first and second SBs as indicated in the configuration parameters. The base station may perform LBT procedures sequentially or simultaneously on the first and second SBs.

[0318] In one embodiment, a base station may determine that an LBT procedure on a 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 via the first SB to a radio device, which may indicate a first downlink radio resource for downlink allocation for the transmission of a first TB and a first PUCCH resource for the ACK / NACK transmission of the first TB. In one embodiment, a base station may determine that an LBT procedure on a 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 via the second SB to a radio device, which may indicate a second downlink radio resource for downlink allocation for the transmission of a second TB (or, in repetition, the first TB) and a second PUCCH resource for the ACK / NACK transmission of the second TB.

[0319] In one embodiment, a wireless device may receive a first DCI while monitoring the SS of a CORESET on a first SB, and a second DCI while monitoring the SS of a CORESET on a second SB. Based on the reception of the first DCI, the wireless device may detect a first TB via a first downlink wireless resource on the first SB and determine a first acknowledgment 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 wireless resource on the second SB and determine a second acknowledgment for detecting the second TB.

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

[0321] Figure 31 shows an example of a PUCCH configuration when multiple SBs are supported in an NR-U system. In one embodiment, a base station can send one or more RRC messages to a radio device that include configuration parameters for a cell (e.g., PCell, or SCell). A cell may include multiple BWPs. A cell may include a single BWP. In one embodiment, a BWP may include multiple (e.g., 4) SBs, each SB occupying multiple RBs (or RB groups) of the BWP. As shown in Figure 31, the SBs of the BWP include SB0, SB1, SB2, etc. Configuration parameters may indicate multiple CORESETs configured on the BWP. Configuration parameters may indicate that the frequency resources of the CORESETs are limited to the bandwidth of the SBs of the BWP. Configuration parameters may indicate that multiple SSs are configured on the CORESETs. For each of the multiple SSs, the configuration parameters may include monitoring frequency position parameters (e.g., a bitmap or monitoring position display shown in Figure 31) indicating which SB the monitoring frequency position of the SS is configured on. As shown in Figure 31, SS (e.g., SS i The monitoring position indicator includes a bit string "110..." indicating the monitoring frequency position, which includes SB0 and SB1. In response to the monitoring frequency position including SB0 and SB1, the wireless device displays SS on SB0 and SB1. i You may also monitor other SBs on BWP, i There's no need to monitor it.

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

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

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

[0325] As shown in Figure 31, the wireless device may attempt to detect DCIs on CCEs on SB0 and SB1. In one embodiment, the wireless device may attempt to detect first DCIs on CCE2, CCE4, CCE6,... on SB0, where CC2, CC4, CC6,... are by implementing the embodiment shown in Figure 25B. i Based on the monitoring of CCE2, CCE4, CCE6, ..., the wireless device may attempt to detect a second DCI on CCE2, CCE4, CCE6, ... on SB1.

[0326] As shown in Figure 31, the wireless device is on SB0 of BWP. i The first DCI on the CCE can be received. The wireless device is SS on SB1 of the BWP. i A second DCI may be received on the CCE. The first starting CCE of the CCE on SB0 where the first DCI is received may have the same CCE index (e.g., 2 as shown in Figure 31) as the second starting CCE of the CCE on SB1 where the second DCI is received. The first starting CCE of the CCE on SB0 where the first DCI is received may have a different CCE index than the second starting CCE of the CCE on SB1 where the second DCI is received. In one embodiment, the first DCI may have the same PRI value as the second DCI.

[0327] In one embodiment, a wireless device may, based on the reception of a first DCI, detect a first TB via a first downlink wireless resource on a first SB and determine first acknowledgment information for detecting the first TB. The wireless device may, based on the reception of a second DCI, detect a second TB via a second downlink wireless resource on a second SB and determine second acknowledgment information for detecting the second TB.

[0328] In one embodiment, a wireless device may determine a first PUCCH resource from a first subset of PUCCH resources (e.g., PUCCH resources having PUCCH resource indices 0, 1, 2, ..., K-1, as shown in Figure 31) corresponding to a first SB in the PUCCH resource set, in order to transmit first acknowledgment information based on a first initiation 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 indices K, K+1, K+2, ..., 2*K-1, as shown in Figure 31) corresponding to a second SB in the PUCCH resource set, in order to transmit second acknowledgment information based on a second initiation CCE and a second PRI of a first DCI. The wireless device can determine a first PUCCH resource from a first subset of PUCCH resources by implementing the exemplary embodiment of Figure 25B. The wireless device can determine a second PUCCH resource from a second subset of PUCCH resources by implementing the exemplary embodiment shown in Figure 25B.

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

[0330] The exemplary embodiments in Figures 28, 29, and / or 31 can be implemented based on the configuration. In one embodiment, if the radio device and base station support at most one DCI for data scheduling on multiple RB sets of the BWP, the base station and radio device may implement a PUCCH resource determination method based on the embodiment in Figure 28. If the radio device and base station support multiple DCIs for data scheduling on multiple RB sets of the BWP and uplink channels, and the uplink channels are under heavy load, the base station and radio device may implement a PUCCH resource determination method based on the example in Figure 29. If the radio device and base station support multiple DCIs for data scheduling on multiple RB sets of the BWP and uplink channels, and the uplink channels are not under heavy load, the base station and radio device may implement a PUCCH resource determination method based on the example in Figure 31.

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

[0332] In one embodiment, a first wireless device may select a first UL SB from a plurality of UL SBs of a BWP for sending an ACK / NACK PUCCH 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 a plurality of UL SBs. In one embodiment, different UEs may be configured with different selection priorities. Setting different selection priorities may mitigate PUCCH collisions.

[0333] In one embodiment, a wireless device may monitor a PDCCH on a CCE of a SB with multiple SBs in the cell's BWP. The wireless device may receive a DCI including a wireless resource display and a PUCCH resource index via a PDCCH on one or more CCEs. The wireless device may receive a TB via the wireless resource indicated by the wireless resource display. The wireless device may determine the 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 information for receiving a TB via the PUCCH resource. The wireless device may further receive one or more RRC messages including configuration parameters for a cell containing multiple BWPs, each of which contains multiple SBs. Each of the multiple SBs may be identified by its respective SB index. The cell configuration parameters further include a first configuration parameter for a BWP with multiple BWPs, the first configuration parameter including one or more wireless resource configuration parameters for a CORESET. One or more wireless resource configuration parameters for a CORESET may indicate that the frequency resources of the CORESET are limited to the bandwidth of the SBs of the BWP. One or more radio resource configuration parameters may indicate that the search space associated with CORESET consists of one or more monitoring frequency position indicators. Each frequency position indicator corresponding to one or more of the SBs may indicate whether the radio device monitors the PDCCH for the search space on the SB. The frequency resources of CORESET on the SB may include multiple CCEs, each of which is identified by a CCE index. The CCE index of the first of the multiple CCEs may start from a first predetermined value (e.g., 0 or 1).

[0334] In one embodiment, a wireless device may monitor PDCCHs on the search space on multiple SBs in response to a monitoring frequency position indicator corresponding to an SB, which indicates PDCCH monitoring on the SB for the search space.

[0335] In one embodiment, one or more RRC messages may further indicate multiple PUCCH resource sets, each of which contains multiple PUCCH resources. Each of the multiple PUCCH resources may be identified by its own PUCCH resource index. A wireless device may determine a PUCCH resource from multiple PUCCH resources in one of the multiple PUCCH resource sets.

[0336] In one embodiment, the acknowledgment information may include an affirmative 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, a wireless device may monitor a second PDCCH on the CCE of a second SB of a plurality of SBs. The wireless device may receive a second DCI, including a second wireless resource indicator and a second PUCCH resource index, via the second PDCCH on one or more CCEs. The wireless device may receive a second TB via the second wireless resource indicated by the second wireless resource indicator. The wireless device may determine the second PUCCH resource based on at least one of the second PUCCH resource index, the second SB index of the second SB, and / or the second CCE index of the second starting CCE of one or more CCEs. The wireless device may transmit a second acknowledgment for the 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, a wireless device may monitor a PDCCH on a CCE of a certain SB among multiple SBs. The wireless device may receive a DCI including a wireless resource display and a PUCCH resource index via the PDCCH on one or more CCEs. The wireless device may receive a TB via the wireless resource indicated by the wireless resource display. The wireless device may determine a PUCCH resource based on at least one of the following: the PUCCH resource index, the PUCCH resource index offset associated with the SB, and / or the CCE index of the starting CCE of one or more CCEs. The wireless device may transmit acknowledgment information to receive a TB via the PUCCH resource.

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

[0341] Figure 32 shows a flowchart according to one embodiment of an exemplary embodiment of the present disclosure. 3210, the wireless device may receive configuration parameters of the BWP, including RB sets, where the CCEs of the BWP's CORESET are across the RB sets, and a subset of CCEs within each RB set of the RB sets are indexed from the same initial value. 3220, the wireless device may receive the DCI via one or more CCEs of a subset of CCEs within a given RB set of the RB sets. 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 an initial value within the RB set. 3240, the wireless device may transmit an uplink signal via an uplink resource determined based on the CCE index.

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

[0343] According to an exemplary embodiment, a wireless device may receive one or more RRC messages containing a second configuration parameter of a cell, and the cell includes a plurality of bandwidth portions, each including a bandwidth portion.

[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 may include a plurality of resource element groups, where each resource element group includes an RB in the symbol.

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

[0347] According to an exemplary embodiment, the configuration parameter may indicate that the bandwidth portion of the control resource set includes CCEs. The configuration parameter may also indicate that the frequency domain resource allocation pattern of the control resource set is replicated for each RB set of the bandwidth portion of the RB set, and the physical radio resources of the CCEs of the control resource set are mapped to each RB set. The radio device may further determine uplink resources based on the total number of a first subset of CCEs in a 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 a first RB set from a bandwidth portion of RB sets, for a search space associated with a control resource set. The search space may include one or more CCEs from a 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 indicators, each frequency position indicator corresponding to each RB set of the bandwidth portion of RB sets. The wireless device may monitor downlink control channels on the search space on the first RB set in response to a monitoring frequency position indicator corresponding to the first RB set indicating downlink control channel monitoring on the first RB set. The wireless device may receive control information while monitoring downlink control channels in 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 particular RB set. The wireless device can transmit a signal through the uplink resource associated with the first RB set. The control information may include a PUCCH resource display 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, a wireless device may determine an uplink resource based on a PUCCH resource index indicated by control information and a PUCCH resource index offset determined based on the CCE index.

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

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

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

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

Claims

1. A wireless device, said wireless device, The configuration parameters of the control resource set in the bandwidth portion (BWP) are received. The control resource set has a control channel element (CCE) spanning the first resource block (RB) set and the second RB set of the BWP, The first RB set has a first subset of the CCE, and the first index value of the first subset starts from a first initial value. The second RB set has a second subset of the CCE, and the second index value of the second subset starts from the same second initial value as the first initial value. The wireless device further, Control information is received via one or more CCEs of the first subset. A signal is transmitted via an uplink resource based on the index of one or more CCEs in the first subset, A wireless device in which the index is determined based on the first index value of the first subset, which starts from the same first initial value as the second initial value.

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

3. The wireless device according to claim 1, wherein the configuration parameter indicates that the 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 the physical wireless resources of the CCE of the control resource set are mapped to the first RB set and the second RB set.

4. The wireless device according to claim 1, wherein the configuration parameter indicates one or more RB sets, including the first RB set, to the search space associated with the control resource set.

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

6. The wireless device according to claim 4, wherein the search space associated with the control resource set comprises one or more monitoring frequency position indicators, each frequency position indicator corresponds to each RB set of the BWP's RB set, and the RB set includes the first RB set and the second RB set.

7. The aforementioned uplink resource, The physical uplink control channel (PUCCH) resource index indicated by the control information, and PUCCH resource index offset determined based on the aforementioned CCE index, A wireless device according to claim 1, determined based on the above.

8. The wireless device according to claim 1, wherein the CCE is a start CCE following the first CCE.

9. The aforementioned wireless device further, The second control information is received via one or more second CCEs from the second subset of CCEs in the second RB set. A second signal is transmitted via a second uplink resource based on the second index of one or more second CCEs in the second subset. The second index is determined based on the second index value of the second subset, which starts from the same second initial value as the first initial value. The wireless device according to claim 1.

Images