Multiple physical downlink shared channel transmissions

Abstract

A wireless device receives configuration parameters indicating: a first downlink control information (DCI) format associated with scheduling of a physical downlink shared channel (PDSCH) in a time slot, and a second DCI format associated with scheduling of a plurality of PDSCHs in a plurality of time slots. A first DCI scheduling a first transport block (TB) is received via a first PDSCH resource in a first time slot based on monitoring a first physical downlink control channel (PDCCH) monitoring occasion for the first DCI format. A second DCI scheduling a second TB is received via a second PDSCH resource in a second time slot based on monitoring a second PDCCH monitoring occasion for the second DCI format.

Description

[0001] Divisional Application This application is a divisional application of the application filed on January 14, 2022, having application number 202280010071.2, and titled “Multiple Physical Downlink Shared Channel Transmissions.” Cross Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 137,648, filed January 14, 2021, the entire contents of which are hereby incorporated by reference. TECHNICAL FIELD

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

[0004] FIG. 1A and FIG. 1B An example mobile communication network in which implementations of the present disclosure can be implemented is shown.

[0005] FIG. 2A and FIG. 2B New Radio (NR) user plane and control plane protocol stacks are shown, respectively.

[0006] FIG. 3 Examples of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A are shown.

[0007] FIG. 4A An example downlink data flow through the NR user plane protocol stack of FIG. 2A is shown.

[0008] FIG. 4B An example format of a MAC subheader in a MAC PDU is shown.

[0009] FIG. 5A and FIG. 5B Mappings between logical channels, transport channels, and physical channels for downlink and uplink are shown, respectively.

[0010] FIG. 6 is an example diagram showing RRC state transitions of a UE.

[0011] FIG. 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown.

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

[0013] FIG. 9Examples of bandwidth adaptation using three configured BWPs for an NR carrier are shown.

[0014] FIG. 10A Examples of three carrier aggregation configurations with two component carriers are shown.

[0015] FIG. 10B Examples of how aggregated cells can be configured into one or more PUCCH groups are shown.

[0016] FIG. 11A Examples of SS / PBCH block structure and location are shown.

[0017] FIG. 11B Examples of CSI-RS mapped in time and frequency domain are shown.

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

[0019] FIG. 13A , FIG. 13B And FIG. 13C Four-step contention-based random access procedure, two-step contention-free random access procedure, and another two-step random access procedure are shown.

[0020] FIG. 14A Examples of CORESET configuration for a bandwidth part are shown.

[0021] FIG. 14B Examples of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing are shown.

[0022] FIG. 15 Examples of a wireless device in communication with a base station are shown.

[0023] FIG. 16A , FIG. 16B , FIG. 16C And FIG. 16D Example structures for uplink and downlink transmissions are shown.

[0024] FIG. 17A , FIG. 17B And FIG. 17C Examples of MAC subheaders in accordance with some embodiments are shown.

[0025] FIG. 18A Examples of DL MAC PDUs in accordance with some embodiments are shown.

[0026] FIG. 18B Examples of UL MAC PDUs in accordance with some embodiments are shown.

[0027] FIG. 19 An example of multiple LCIDs for downlink according to some embodiments is shown.

[0028] FIG. 20 An example of multiple LCIDs for uplink according to some embodiments is shown.

[0029] FIG. 21A and FIG. 21B An example of SCell Activation / Deactivation MAC CE format according to some embodiments is shown.

[0030] FIG. 22 An example of BWP Activation / Deactivation on SCell according to some embodiments is shown.

[0031] FIG. 23A , FIG. 23B and FIG. 23C An example of RRC message for configuration parameters of a cell according to some embodiments is shown.

[0032] FIG. 24 An example of RRC message for configuration parameters of a search space according to some embodiments is shown.

[0033] FIG. 25 An example of RRC message for configuration parameters of a control resource set (CORESET) according to some embodiments is shown.

[0034] FIG. 26 An example of search space configuration according to some embodiments is shown.

[0035] FIG. 27 An example of search space configuration according to some embodiments is shown.

[0036] FIG. 28 An example of PDCCH monitoring based on SS-based periodicity and duration according to some embodiments is shown.

[0037] FIG. 29 An example of DCI format according to some embodiments is shown.

[0038] FIG. 30A and FIG. 30B An example of single-PDSCH scheduling and multi-PDSCH scheduling according to some embodiments is shown.

[0039] FIG. 31 An example of PDCCH monitoring for different DCI formats on SS of a BWP according to some embodiments is shown.

[0040] FIG. 32Examples of PDCCH monitoring for different DCI formats on SS of a BWP are shown in accordance with some embodiments.

[0041] FIG. 33 Examples of PDCCH monitoring adaptation for multi-PDSCH scheduling are shown in accordance with some embodiments.

[0042] FIG. 34 Examples of single-PDSCH scheduling are shown in accordance with some embodiments.

[0043] FIG. 35 Examples of multi-PDSCH scheduling are shown in accordance with some embodiments.

[0044] FIG. 36 Examples of PDCCH monitoring skipping for multi-PDSCH scheduling are shown in accordance with some embodiments. DETAILED DESCRIPTION

[0045] In this disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those of ordinary skill in the relevant arts that various changes can be made thereto without departing from scope of the invention. Indeed, after understanding the specification, those of ordinary skill in the relevant arts will appreciate how to implement alternative embodiments. The present embodiments should not be limited by any described exemplary embodiments. Embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. The diagrams are only for purposes of illustrating example functional scenarios. The disclosed architecture is sufficiently flexible and configurable to allow for utilization in ways different than shown. For example, the actions listed in any flow diagram can be reordered or only optionally utilized in some embodiments.

[0046] Embodiments can be configured to operate as needed. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanisms can be performed when certain criteria are met. Exemplary criteria can be based at least in part on, for example, a wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, a combination of the above, etc. Various exemplary embodiments can be applied when one or more criteria are met. Thus, exemplary embodiments that selectively implement the disclosed protocols can be implemented.

[0047] A base station can communicate with a mix of wireless devices. The wireless devices and / or the base station can support multiple technologies and / or multiple versions of the same technology. The wireless devices can have certain specific capabilities depending on the wireless device class and / or capabilities. When the present disclosure refers to a base station communicating with a plurality of wireless devices, the present disclosure can mean a subset of the total wireless devices in a coverage area. For example, the present disclosure can mean a plurality of wireless devices having a given capability and in a given sector of the base station of a given LTE or 5G version. The plurality of wireless devices in the present disclosure can refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in a coverage area performing according to the disclosed methods, etc. There can be a plurality of base stations or a plurality of wireless devices in a coverage area that can not comply with the disclosed methods, for example, these wireless devices or base stations can perform based on an older version of LTE or 5G technology.

[0048] In the present disclosure, “a” and “an” and similar phrases will be interpreted to mean “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” will be interpreted to mean “at least one” and “one or more.” In the present disclosure, the term “may” is interpreted to mean “may, for example.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that can or can not be used in one or more embodiments. As used herein, the terms “comprises” and “consists of’ recite one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unlisted components being included in the element being described. In contrast, “consists of’ provides a complete listing of one or more components of the element being described. As used herein, the term “based on” shall mean “based at least in part on” and not “based solely on,” for example. As used herein, the term “and / or” means any possible combination of the enumerated elements. For example, “A, B, and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B, and C.

[0049] A is called a subset of B if every element of A is also an element of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celll, cell2} are: {celll}, {cell2}, and {celll, cell2}. The phrase "based on" (or, equivalently, "at least based on") indicates that the phrase after "based on" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "in response to" (or, equivalently, "at least in response to") indicates that the phrase after "in response to" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "in dependence of" (or, equivalently, "at least in dependence of") indicates that the phrase after "in dependence of" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "employing / using" (or, equivalently, "at least employing / using") indicates that the phrase after "employing / using" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments.

[0050] The term configured can relate to the capability of a device, whether the device is in an operational state or a non-operational state. Configured can also mean a particular setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. can be "configured" within a device to provide the device with specific characteristics, whether the device is in an operational state or a non-operational state. The term control message "causing" in a device can mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0051] In this disclosure, a parameter (or, equivalently, a field or an information element: IE) can include one or more information objects, and an information object can include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J. Then, for example, N includes K, and N includes J. In one example embodiment, when one or more messages include a plurality of parameters, it means that the parameter in the plurality of parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0052] Many of the features presented are described as optional by use of "may" or use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation of the optional features that can be obtained by selecting from among the described set of optional features. The present disclosure should be interpreted to explicitly disclose all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0053] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is herein defined as an element or component that performs a defined function and has a defined interface to other elements or components. Modules described in the present disclosure can be implemented in hardware, software, firmware, wetware (e.g., hardware with biological components such as neurons), or combinations thereof, all of which are behaviorally equivalent. For example, a module can be implemented as a software routine in a computer language such as C, C++, Fortran, Pascal, Java, Basic, Matlab, or others, or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It is possible to use physical hardware to implement a module, including discrete electronic components, programmable logic devices such as FPGAs and CPLDs, and application-specific integrated circuits (ASICs). Examples of programmable logic devices, as used herein, include programmable logic and other programmable circuits such as

[0054] FIG. 1A An example of a mobile communication network 100 in which embodiments of the present disclosure can be implemented is shown. The mobile communication network 100 can be, for example, a public land mobile network (PLMN) operated by a network operator. As FIG. 1A The mobile communication network 100 is shown to include a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0055] CN 102 can 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 the interface function, the CN 102 can setup end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functions.

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

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

[0058] The RAN 104 can include one or more base stations (not shown). The term “base station” can be used throughout this disclosure to refer to and encompass: a Node-B (associated with UMTS and / or 3G standards); an evolved Node-B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a repeater node or relay node used to extend the coverage area of a donor node; a next generation evolved Node-B (ng-eNB); a generation Node-B (gNB, associated with NR and / or 5G standards); an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station can include at least one gNB-central unit (gNB-CU) and at least one gNB-distributed unit (gNB-DU).

[0059] The base stations included in the RAN 104 can include one or more sets of antennas, which can be used to communicate with the wireless devices 106 through the use of the air interface. For example, one or more of the base stations can include three sets of antennas to control three cells (or sectors). The size of a cell can be determined by the range of the transmitters and receivers (e.g., base station receivers) that can successfully communicate with the transmitters (e.g., wireless device transmitters) operating in the cell. The cells of the base stations can together provide radio coverage to the wireless devices 106 over a wide geographic area to support the movement (e.g., roaming) of wireless devices.

[0060] In addition to three-sector sites, other implementations of the base stations are possible. For example, one or more of the base stations in the RAN 104 can be implemented as sectorized sites having more or less than three sectors. One or more of the base stations in the RAN 104 can be implemented as an access point, a baseband processing unit coupled to several remote radio heads (RRHs), and / or a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. A repeater node can amplify and rebroadcast a radio signal received from a donor node. A relay node can perform the same / similar functions as a repeater node but can decode a radio signal received from a donor node to cancel noise before amplifying and rebroadcasting the radio signal.

[0061] The RAN 104 can be deployed as a homogeneous network of macro cell base stations, each having similar antenna patterns and antenna gains, and / or as a heterogeneous network, including different types of base stations, e.g., macro cells, micro cells, femto cells, etc., which can have different antenna patterns, different antenna gains, and / or different coverage areas. The RAN 104 can be deployed, for example, in a metropolitan area.

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

[0063] FIG. 1B Another example mobile communication network 150 is shown in which embodiments of the disclosure can be implemented. The mobile communication network 150 can be, for example, a PLMN run by a network operator. As FIG. 1B shown in FIG. 1, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively, UEs 156). These components can be implemented and operate in a similar manner to that described above with regard to the corresponding components of the mobile communication network 100. FIG. 1A

[0064] The 5G-CN 152 provides UEs 156 with an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface function, the 5G-CN 152 can setup end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functions. In contrast to the CN of 3GPP 4G networks, the 5G-CN 152 can be based on a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of the 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0065] As FIG. 1B shown in FIG. 1, the 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, which are shown in FIG. 1B ​The AMF / UPF 158 can be implemented as one component for clarity. The UPF 158B can act as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B can perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering and downlink data notification triggering. The UPF 158B can act as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, a point of interconnect with the one or more DNs, and / or a branching point to support multi-homed PDU session. The UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and a DN.

[0066] The AMF 158A can perform functions such as non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3 GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including check of roaming rights, mobility management control (subscription and policies), network slice support, and / or session management function (SMF) selection. NAS can mean functionality operating between the CN and the UE, and AS can mean functionality operating between the UE and the RAN.

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

[0068] The NG-RAN 154 can connect the 5G-CN 152 to the UEs 156 through wireless communication over the air interface. The NG-RAN 154 can include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160), and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 can be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 can include one or more sets of antennas, which can be used to communicate with UEs 156 through the air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 can include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and ng-eNBs 162 can provide radio coverage to the UEs 156 across a wide geographic area to support UE mobility.

[0069] As shown in FIG. 1B , the gNBs 160 and / or ng-eNBs 162 can be connected by means of the NG interfaces to the 5G-CN 152, and by means of the Xn interface to other base stations. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or ng-eNBs 162 can be connected by means of the Uu interface to the UEs 156. For example, as shown in FIG. 1B , the gNB 160A can be connected by means of the Uu interface to the UE 156A. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces can be used by the network elements in FIG. 1B to exchange data and signaling messages, and can include two planes: the user plane and the control plane. The user plane can handle data of interest to users. The control plane can handle signaling messages of interest to the network elements.

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

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

[0072] The 5G-CN 152 is described as being configured to handle NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to connect to a 4G core network in a mode referred to as “non-standalone.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functionality (e.g., initial access, mobility, and paging). Although FIG. 1B Only one AMF / UPF 158 is shown in FIG. 1, but one gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0073] As discussed, FIG. 2A Interfaces between network elements in FIG. 1 (e.g., Uu, Xn, and NG interfaces) can be associated with a protocol stack that the network elements use to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. The user plane can handle data of interest to the user, while the control plane can handle signaling messages of interest to the network elements.

[0074] FIG. 2B andFIG. 2A Examples of NR user plane and NR control plane protocol stacks for the Uu interface between the UE 210 and the gNB 220 are shown. FIG. 2B and FIG. 1B The protocol stacks shown in FIGS. 1A-1C can be the same as or similar to those for the Uu interface between the UE 156A and the gNB 160A shown in FIG. 2A FIGS. 1A-1C.

[0075] FIG. 3 An NR user plane protocol stack is shown that includes five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, the physical layer (PHY) 211 and 221 can provide transport services to higher layers of the protocol stack and can correspond to layer 1 of the open systems interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include the medium 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. These four protocols can together make up layer 2 or the data link layer of the OSI model.

[0076] FIG. 2A Examples of services provided between the protocol layers of the NR user plane protocol stack are shown. From the top of FIG. 3 and FIG. 3 The SDAP 215 and 225 can perform QoS flow handling, starting from the top of FIG. 2A. The UE 210 can receive service through a PDU session, which can be a logical connection between the UE 210 and a DN. The PDU session can have one or more QoS flows. A UPF (e.g., UPF 158B) of a CN can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAP 215 and 225 can perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between QoS flows and data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between QoS flows and data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between QoS flows and data radio bearers.

[0077] The PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from an intended source. The PDCPs 214 and 224 can perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets that are received in repetition due to, for example, an intra-gNB handover. The PDCPs 214 and 224 can perform packet duplication to improve the likelihood that a packet will be received, and remove any duplicate packets at the receiver. Packet duplication can be applicable to services that require high reliability.

[0078] Although FIG. 3 Although not shown in FIG. 2, the PDCPs 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by the cell groups in dual connectivity. The PDCPs 214 and 224 can map / de-map the split radio bearers between RLC channels that belong to the cell groups.

[0079] The RLCs 213 and 223 can perform segmentation, retransmission by automatic repeat request (ARQ), and removal of duplicate data units received from the MACs 212 and 222, respectively. The RLCs 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode that the RLC is operating in, the RLC can perform one or more of the functions described. The RLC configuration can be on a per logical channel basis, independent of numerology and / or transmission time interval (TTI) duration. As shown in FIG. 2, the RLCs 213 and 223 can provide RLC channels as a service to the PDCPs 214 and 224, respectively. FIG. 3

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

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

[0082] FIG. 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. FIG. 4A The diagram illustrates the flow through the NR user plane protocol stack to generate three IP packets of two TB at the gNB 220. n , n+1 and m The downlink data stream. The uplink data stream flowing through the NR user plane protocol stack can be... FIG. 4A The downlink data flow described in the text is similar.

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

[0084] FIG. 3 The remaining protocol layers can perform their associated functions (e.g., regarding...). FIG. 4A This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). FIG. 4A Regarding IP packets m (As shown) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed throughout MAC PDUs, such as... FIG. 4B As shown in the diagram. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

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

[0086] FIG. 4B The diagram further illustrates a MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, FIG. 4B This shows two MAC CEs inserted into the MAC PDU. These can be used at the beginning of downlink transmissions within the MAC PDU (e.g., ...). FIG. 5AMAC CEs can be used for in-band control signaling. Exemplary MAC CEs include: scheduling related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. There can be a MAC subheader with a similar format as described with respect to MAC SDUs before the MAC CE, and the MAC CE can be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0088] FIG. 5B And FIG. 5A The mapping between logical channels, transport channels, and physical channels is shown for downlink and uplink, respectively. Information is transferred through the channels between RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between RLC and MAC and can be classified into control channels, which carry control and configuration information in the NR control plane, or traffic channels, which carry data in the NR user plane. Logical channels can be classified as dedicated to a specific UE, or as common logical channels, which can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example: - a paging control channel (PCCH), which is used to carry paging messages for paging UEs whose location is not known by the network on a cell level; - a broadcast control channel (BCCH), which is used to carry system information messages in the form of a master information block (MIB) and a number of system information blocks (SIBs), where the system information messages can be used by UEs to obtain information about how the cell is configured and how to operate within the cell; - a common control channel (CCCH), which is used to carry control messages and random access; - a dedicated control channel (DCCH), which is used to carry control messages to / from specific UEs to configure the UEs; and - Dedicated Traffic Channel (DTCH), which is used for carrying user data to / from a specific UE.

[0089] Transport channels are used between the MAC layer and the PHY layer, and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example: - Paging Channel (PCH), which is used for carrying paging messages originating from PCCH; - Broadcast Channel (BCH), which is used for carrying the MIB from BCCH; - Downlink Shared Channel (DL-SCH), which is used for carrying downlink data and signaling messages, including SIBs from BCCH; - Uplink Shared Channel (UL-SCH), which is used for carrying uplink data and signaling messages; and - Random Access Channel (RACH), which is used to allow UEs to access the network without any prior scheduling.

[0090] The PHY can use physical channels to communicate information between processing stages of the PHY. A physical channel can have an associated set of time-frequency resources used to carry the information of one or more transport channels. The PHY can generate control information to support low-level operations of the PHY and provide the control information to lower levels of the PHY via physical control channels, referred to as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR includes, for example: - Physical Broadcast Channel (PBCH), which is used for carrying the MIB from BCH; - Physical Downlink Shared Channel (PDSCH), which is used for carrying downlink data and signaling messages from DL-SCH and paging messages from PCH; - Physical Downlink Control Channel (PDCCH), which is used for carrying downlink control information (DCI), which can include downlink scheduling commands, uplink scheduling grants, and uplink power control commands; - Physical Uplink Shared Channel (PUSCH), which is used for carrying uplink data and signaling messages from UL-SCH, and in some cases, uplink control information (UCI) as described below; - Physical Uplink Control Channel (PUCCH), which is used for carrying UCI, which can include HARQ acknowledgements, Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Scheduling Requests (SRs); and - Physical Random Access Channel (PRACH), which is used for random access.

[0091] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operations of the physical layer. As FIG. 5B and FIG. 2B The physical layer signals defined by NR include: primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS), and phase tracking reference signal (PT-RS), as shown in

[0092] FIG. 2B An example NR control plane protocol stack is shown. As shown in FIG. 6 The NR control plane protocol stack can use the same / similar first four protocol layers as the example NR user plane protocol stack. The four protocol layers include PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224. Rather than having SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

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

[0095] FIG. 1A is an example diagram illustrating RRC state transitions of a UE. The UE can be the same or similar to the wireless device 106, FIG. 2A the UE 210 depicted in FIG. 2B and FIG. 6 described in the present disclosure. As shown in FIG. 1A the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC CONNECTED), RRC idle 604 (e.g., RRC IDLE), and RRC inactive 606 (e.g., RRC INACTIVE).

[0096] In the RRC connected 602, the UE has an established RRC context and can have at least one RRC connection with a base station. The base station can be similar to one of: FIG. 1B the one or more base stations included in the RAN 104 depicted in FIG. 2A the gNB 160 or ng-eNB 162 depicted in FIG. 2B and FIG. 1Bthe gNB 220 depicted in the figures herein; or any other base station described in the present disclosure. A base station with which a UE is connected can have an RRC context for the UE. The RRC context, referred to as the UE context, can include parameters for communication between the UE and the base station. These parameters can include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in the RRC connected 602, mobility of the UE can be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE can measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station can request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608, or to RRC inactive 606 through a connection suspend procedure 610.

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

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

[0099] RRC states can be associated with mobility management mechanisms. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to inform the UE of events via a paging message without having to broadcast the paging message over the entire mobile communication network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 can allow the network to track the UE at a cell group level, such that a paging message can be broadcast on a cell in the cell group in which the UE is currently camped rather than over the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE at a cell group level. These mobility management mechanisms can use different granularities of grouping to do so. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN area identifier (RAI); and a group of RAN areas, referred to as tracking areas and identified by a tracking area identifier (TAI).

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

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

[0102] A last serving base station of a base station or UE storing an RRC context for the UE can be referred to as an anchor base station. The anchor base station can maintain the RRC context for the UE at least for a period of time that the UE remains in the RAN notification area of the anchor base station and / or for a period of time that the UE remains in RRC inactive 606.

[0103] A gNB, such as gNB 104, can be an anchor base station for a UE in RRC idle 604 or RRC inactive 606. The gNB can maintain an RRC context for the UE while the UE remains in the RAN notification area of the gNB and / or while the UE remains in RRC inactive 606. The gNB can be the last serving base station for the UE in RRC idle 604 or RRC inactive 606. FIG. 5AThe gNBs 160 in the 5G NR radio access network can be split into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DUs). The gNB-CU can be coupled to the one or more gNB-DUs using an FI interface. The gNB-CU can include the RRC, PDCP, and SDAP. The gNB-DUs can include the RLC, MAC, and PHY.

[0104] In NR, the physical signals and physical channels (about which FIG. 5B and FIG. 7 are discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data over a number of orthogonal subcarriers (or tones). Prior to transmission, data can be mapped to a number of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into a number of parallel symbol streams. The number of parallel symbol streams can be referred to as the number of tones, frequency bins, subcarriers, or spatial channels. F Each parallel symbol stream can be considered as if it is in the frequency domain and used as input to an inverse fast Fourier transform (IFFT) block. The IFFT block can take the source symbols (one from each parallel symbol stream) and use each source symbol to modulate a sinusoid with a different frequency. The output of the IFFT block can be a time domain signal that contains the sum of the sinusoids modulated by the source symbols. This time domain signal can be upconverted to a carrier frequency and transmitted over the air. F The number of parallel symbol streams can be mixed using an FFT block prior to being processed by the IFFT block. This operation results in DFT-precoded OFDM symbols and can be used by the UE in the uplink to reduce the peak to average power ratio (PAPR). The inverse processing can be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols. F F F F F F F F F

[0105] FIG. 7 ​​​​​​​​​An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame can be identified by a system frame number (SFN). The SFN can repeat with a period of 1024 frames. As shown, the duration of one NR frame can be 10 milliseconds (ms), and can include 10 subframes of 1 ms duration. A subframe can be divided into slots, which include, for example, 14 OFDM symbols per slot.

[0106] The duration of a slot can depend on the numerology of the OFDM symbols used for the slot. In NR, flexible numerologies are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mmWave range). A numerology can be defined in terms of subcarrier spacing and cyclic prefix duration. For numerologies in NR, the subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of two, and the cyclic prefix duration can be scaled down from a baseline cyclic prefix duration of 4.7 μβ by powers of two. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μβ; 30 kHz / 2.3 μβ; 60 kHz / 1.2 μβ; 120 kHz / 0.59 μβ; and 240 kHz / 0.29 μβ.

[0107] A slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations, and correspondingly more slots per subframe. FIG. 7 This slot duration and transmission structure per subframe in relation to numerology is shown for illustration, FIG. 8 (not shown in FIG. 3B) with a subcarrier spacing of 240 kHz). Subframes in NR can be used as a time reference independent of numerology, while slots can be used as a unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from slot duration, and start at any OFDM symbol, and continue for as many symbols as needed for the transmission. These partial-slot transmissions can be referred to as mini-slot or sub-slot transmissions.

[0108] FIG. 8 An exemplary configuration of a slot in the time and frequency domain of an NR carrier is shown. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one subcarrier in the frequency domain by one OFDM symbol in the time domain, as shown in FIG. 8 RB spans twelve consecutive REs in the frequency domain, as shown in FIG. 8The NR carrier can be limited to a width of 275 RBs or 275 x 12 = 3300 subcarriers. If such a limit is used, the NR carrier can be limited to 50 MHz, 100 MHz, 200 MHz, and 400 MHz for subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on a per-carrier bandwidth limit of 400 MHz.

[0109] FIG. 9 A single numerology is shown to be used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies can be supported on the same carrier.

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

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

[0112] For unpaired spectrum, a downlink BWP from the set of configured downlink BWPs can be linked with an uplink BWP from the 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 spectrum, a UE can expect the center frequency of a downlink BWP to be the same as the center frequency of an uplink BWP.

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

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

[0115] One or more BWP indicator fields can be provided in downlink control information (DCI). A value of a BWP indicator field can indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. A value of the one or more BWP indicator fields can indicate an active uplink BWP for one or more uplink transmissions.

[0116] A base station can semi-statically configure a default downlink BWP for a UE within a set of configured downlink BWPs associated with a PCell. If a base station does not provide a default downlink BWP for a UE, the default downlink BWP can be an initial active downlink BWP. A UE can determine which BWP is an initial active downlink BWP based on a CORESET configuration obtained using a PBCH.

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

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

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

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

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

[0122] To provide higher data rates, two or more carriers can be aggregated and transmitted to / from the same UE simultaneously using carrier aggregation (CA). The aggregated carriers in CA can be referred to as component carriers (CCs). When using CA, there are many serving cells for the UE, one for each CC. The CCs can have three configurations in the frequency domain.

[0123] FIG. 4B Three CA configurations with two CCs are shown. In an intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are positioned directly adjacent to each other within the band. In an intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated by a gap in the band. In an inter-band configuration 1006, the two CCs are in frequency bands (frequency band A and frequency band B).

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

[0125] When using CA, one of the aggregated cells for a UE can be referred to as a primary cell (PCell). The PCell can be the serving cell to which the UE initially connects at RRC connection setup, reestablishment, and / or handover. The PCell can provide NAS mobility information and security input to the UE. A UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as a downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as an uplink primary CC (UL PCC). Other aggregated cells for a UE can be referred to as secondary cells (SCells). In an example, SCells can be configured after the PCell is configured for a UE. For example, SCells can be configured through an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to an SCell can be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to an SCell can be referred to as an uplink secondary CC (UL SCC).

[0126] Configured SCells for a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Configured SCells can be activated and deactivated using a MAC CE for FIG. 10B For example, a MAC CE can indicate which SCells for a UE (e.g., in a subset of configured SCells) are activated or deactivated using a bitmap (e.g., one bit per SCell). Configured SCells can be deactivated in response to expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0128] FIG. 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. FIG. 10B In the example, 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 can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if FIG. 5A If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

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

[0130] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, a HARQ entity can operate on a serving cell. Transport blocks can be generated according to assignments / grants per serving cell. A transport block and potential HARQ retransmissions of the transport block can be mapped to a serving cell.

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

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

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

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

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

[0136] ​The PBCH can use QPSK modulation and can use forward error correction (FEC). The FEC can use polar coding. One or more symbols spanned by the PBCH can carry one or more DMRSs for demodulating the PBCH. The PBCH can include an indication of a current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters can help the UE with time synchronization with the base station. The PBCH can include a master information block (MIB) for providing one or more parameters to the UE. The MIB can be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI can include a system information block type 1 (SIB1). The SIB1 can contain information needed by the UE to access the cell. The UE can use one or more parameters of the MIB to monitor PDCCH that can be used to schedule PDSCH. The PDSCH can include the SIB1. The SIB1 can be decoded using parameters provided in the MIB. The PBCH can indicate that the SIB1 is not present. Based on the PBCH indicating that the SIB1 is not present, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency to which the UE points.

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

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

[0139] In an example, a base station can transmit a plurality of SS / PBCH blocks within a frequency range of a carrier. In an example, a first PCI of a first SS / PBCH block of the plurality of SS / PBCH blocks can be different than a second PCI of a second SS / PBCH block of the plurality of SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations can be different or the same.

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

[0141] A base station can semi-statically configure a UE with one or more CSI-RS resource sets. A CSI-RS resource can be associated with a location in time and frequency domain and periodicity. A base station can selectively activate and / or deactivate a CSI-RS resource. A base station can indicate to a UE that a CSI-RS resource in a CSI-RS resource set is activated and / or deactivated.

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

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

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

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

[0146] A PDSCH can include one or more layers. A UE can assume that at least one symbol with a DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer can configure up to 3 DMRSs for a PDSCH.

[0147] Downlink PT-RS can be transmitted by a base station and used by a UE for phase noise compensation. Whether or not a downlink PT-RS is present can depend on RRC configuration. The presence and / or pattern of a downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters that can be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of a downlink PT-RS can be associated with one or more DCI parameters including at least MCS. An NR network can support multiple PT-RS densities defined in time / frequency domain. When present, a frequency domain density can be associated with at least one configuration of a scheduled bandwidth. A UE can take a same precoding for a DMRS port and a PT-RS port. The number of PT-RS ports can be fewer than the number of DMRS ports in a scheduled resource. A downlink PT-RS can be confined in a scheduled time / frequency duration for a UE. A downlink PT-RS can be transmitted on a symbol to facilitate phase tracking at a receiver.

[0148] A UE can transmit an uplink DMRS to a base station for channel estimation. For example, a base station can use an uplink DMRS for consistent demodulation of one or more uplink physical channels. For example, a UE can transmit an uplink DMRS with a PUSCH and / or a PUCCH. An uplink DM-RS can span a similar frequency range as a frequency range associated with a corresponding physical channel. A base station can configure a UE with one or more uplink DMRS configurations. At least one DMRS configuration can support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs can be configured to be transmitted at one or more symbols of a PUSCH and / or a PUCCH. A base station can semi-statically configure a UE with a number (e.g., a maximum number) of front-loaded DMRS symbols of a PUSCH and / or a PUCCH that the UE can use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network can support a common DMRS structure (e.g., for cyclic prefix orthogonal frequency-division multiplexing (CP-OFDM)) for downlink and uplink, where a DMRS location, a DMRS pattern, and / or a scrambling sequence of a DMRS can be the same or different.

[0149] A PUSCH can include one or more layers, and a UE can transmit at least one symbol with a DMRS present on a layer of the one or more layers of the PUSCH. In an example, an upper layer can configure a PUSCH with up to three DMRSs.

[0150] Uplink PT-RS (which can be used by a base station for phase tracking and / or phase noise compensation) can or can 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 RRC signaling and / or one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI. When configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters including at least MCS. A radio network can support multiple uplink PT-RS densities defined in time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can take a same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be fewer than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS can be confined in the scheduled time / frequency duration for the UE.

[0151] A UE can transmit SRS to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. SRS transmitted by a UE can allow a base station to estimate the uplink channel state at one or more frequencies. A scheduler at the base station can employ the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmissions from the UE. A base station can semi-statically configure a UE with one or more SRS resource sets. For an SRS resource set, the base station can configure the UE with one or more SRS resources. SRS resource set applicability can be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, SRS resources in an SRS resource set of the one or more SRS resource sets (e.g., with same / similar time domain behavior, periodic, aperiodic, etc.) can be transmitted at a time (e.g., simultaneously). A UE can transmit one or more SRS resources in an SRS resource set. An NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. A UE can transmit SRS resources based on one or more trigger types, where the one or more trigger types can include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format can be employed for a UE to select at least one configured SRS resource set of one or more configured SRS resource sets. SRS trigger type 0 can refer to SRS triggered based on higher layer signaling. SRS trigger type 1 can refer to SRS triggered based on one or more DCI formats. In an example, a UE can be configured to transmit SRS after the transmission of PUSCH and corresponding uplink DMRS when PUSCH and SRS are transmitted in a same slot.

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

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

[0154] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamformed reference signals. A UE can perform downlink beam measurements based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)) and generate a beam measurement report. A UE can perform a downlink beam measurement procedure after setting up an RRC connection with a base station.

[0155] FIG. 11B An example of a channel state information reference signal (CSI-RS) mapped in time and frequency domain is shown. FIG. 11BThe squares shown in the middle can represent resource blocks (RBs) within a bandwidth of a cell. A base station can transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters can be configured for a CSI-RS resource configuration by higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), CSI-RS power parameter, CSI-RS sequence parameter, code division multiplexing (CDM) type parameter, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL- scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

[0157] CSI-RS, such as FIG. 12AThose illustrated in FIG. 11 (e.g., CSI-RSs 1101, 1102, 1103) can be transmitted by a base station and used by a UE for one or more measurements. For example, a UE can measure a reference signal received power (RSRP) of a configured CSI-RS resource. A base station can configure a UE with a reporting configuration, and the UE can report the RSRP measurement to the network (e.g., via one or more base stations) based on the reporting configuration. In an example, a base station can determine one or more transmission configuration indication (TCI) states including a plurality of reference signals based on the reported measurements. In an example, a base station can indicate the one or more TCI states to a UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). A UE can receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, a UE can or can not have a beam correspondence capability. If a UE has a beam correspondence capability, the UE can determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of a corresponding Rx beam. If a UE does not have a beam correspondence capability, the UE can perform an uplink beam selection procedure to determine a spatial domain filter of a Tx beam. The UE can perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by a base station. The base station can select and indicate an uplink beam of the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0158] In a beam management procedure, a UE can assess (e.g., measure) a channel quality of one or more beam pair links, including a transmission beam transmitted by a base station and a receive beam received by the UE. Based on the assessment, the UE can transmit a beam measurement report indicating one or more beam pair quality parameters including, for example, one or more beam identifications (e.g., beam indices, reference signal indices, etc.), an RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (RI).

[0159] FIG. 12BExamples of three downlink beam management procedures are shown: PI, P2, and P3. Procedure PI can enable UE measurements of transmission (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of PI, respectively). Beamforming at the TRP can include a Tx beam sweep for a set of beams (shown as ellipses rotating in a counterclockwise direction indicated by dashed arrows in the top rows of PI and P2). Beamforming at the UE can include an Rx beam sweep for a set of beams (shown as ellipses rotating in a clockwise direction indicated by dashed arrows in the bottom rows of PI and P3). Procedure P2 can be used to enable UE measurements of Tx beams of a TRP (shown as ellipses rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or base station can perform procedure P2 using a smaller set of beams than used in procedure PI, or using narrower beams than used in procedure PI. This can be referred to as beam refinement. The UE can perform procedure P3 for Rx beam determination by using the same Tx beams at the base station and sweeping Rx beams at the UE.

[0160] FIG. 13A Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements of Tx beams of a UE, e.g., to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, e.g., an Rx beam sweep from a set of beams (shown as ellipses rotating in a clockwise direction indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station can include, e.g., an Rx beam sweep from a set of beams (shown as ellipses rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 can be used to enable a base station to adjust its Rx beams when the UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 using a smaller set of beams than used in procedure PI, or using narrower beams than used in procedure PI. This can be referred to as beam refinement. The UE can perform procedure U3 to adjust its Tx beams when the base station uses a fixed Rx beam.

[0161] A UE can initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE can transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, etc.) based on initiation of the BFR procedure. The UE can detect a beam failure based on a determination that a quality of a beam pair link of an associated control channel is not satisfactory (e.g., has an error rate above an error rate threshold, has a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0162] A UE can measure a quality of a beam pair link using one or more reference signals (RSs) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam pair link can be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resource. A base station can indicate that a RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, etc.). The one or more DMRSs of the RS resource and the channel can be QCLed when channel properties (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from transmissions to the UE via the RS resource are similar or the same as channel properties from transmissions to the UE via the channel.

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

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

[0165] The configuration message 1310 can be transmitted, for example, using one or more RRC messages. The one or more RRC messages can indicate, to a UE, one or more random access channel (RACH) parameters. The one or more RACH parameters can include at least one of: 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 one or more RRC messages can be broadcast or multicast by a base station to one or more UEs. The one or more RRC messages can be UE-specific (e.g., a dedicated RRC message transmitted to a UE in an RRC CONNECTED state and / or an RRC INACTIVE state). The UE can determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313. Based on the one or more RACH parameters, the UE can determine a reception timing and a downlink channel for receiving Msg 2 1312 and Msg 4 1314.

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

[0167] The one or more RACH parameters provided in the configuration message 1310 can be used to determine an uplink transmission power for Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., a received target power and / or an initial power for preamble transmission). There can be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters can indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmission of Msg 1 1311 and Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters can indicate one or more thresholds based on which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

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

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

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

[0171] Msg 2 1312 received by the UE can include a RAR. In some scenarios, Msg 2 1312 can include multiple RARs corresponding to multiple UEs. Msg 2 1312 can be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 can be scheduled on a DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 can indicate that Msg 1 1311 was received by the base station. Msg 2 1312 can include a time alignment command that can be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmission of Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting a preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE can determine when to start the time window based on the PRACH occasion used by the UE to transmit the preamble. For example, the UE can start the time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH occasion starting from the end of the preamble transmission). The one or more symbols can be determined based on a numerology. The PDCCH can be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE can identify the RAR based on a radio network temporary identifier (RNTI). The RNTI can be used depending on one or more events that initiated the random access procedure. The UE can use a random access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH occasion in which the UE transmitted the preamble. For example, the UE can determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or an UL carrier indicator of the PRACH occasion. An example of the RA-RNTI can be as follows: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id where s_id can be an index of the first OFDM symbol of the PRACH occasion (e.g., 0 ≤ s_id < 14), t_id can be an index of the first slot of the PRACH occasion in a system frame (e.g., 0 ≤ t_id < 80), f_id can be an index of the PRACH occasion in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for the preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

[0172] The UE can transmit Msg 3 1313 in response to successfully receiving Msg 2 1312 (e.g., using the resources identified in Msg 2 1312). Msg 3 1313 can be used, for example, to FIG. 13B contention resolution in the contention-based random access procedure shown in FIG. 13. In some scenarios, multiple UEs can transmit the same preamble to the base station, and the base station can provide a RAR corresponding to the UEs. If the multiple UEs interpret the RAR as corresponding to themselves, a collision can occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE does not use the identity of another UE by mistake. To perform contention resolution, the UE can include a device identifier in Msg 3 1313 (e.g., a TC-RNTI included in Msg 2 1312 and / or any other suitable identifier if a C-RNTI is assigned).

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

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

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

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

[0177] After transmitting the preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for a RAR. In the case of a beam failure recovery request, the base station can configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In FIG. 13C In the contention-free random access procedure shown, the UE can determine that the random access procedure successfully completes after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, the UE can determine that the random access procedure successfully completes if the PDCCH transmission is addressed to a C-RNTI. For example, the UE can determine that the random access procedure successfully completes if the UE receives a RAR that includes a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC subPDU with the preamble identifier. The UE can determine that the response is an indication of an acknowledgement of the SI request.

[0178] FIG. 13A Another two-step random access procedure is shown. Similar to the random access procedure shown in FIG. 13B and FIG. 13C Similar to the random access procedure shown in FIG. 13A The procedure shown includes the transmission of two messages: Msg A 1331 and Msg B 1332.

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

[0180] The UE can initiate the random access procedure for a licensed spectrum and / or an unlicensed spectrum​FIG. 13A The UE can determine whether to initiate the two-step random access procedure based on one or more factors. The one or more factors can be: a radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; a cell size; an RRC state of the UE; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factor.

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

[0182] The transport block 1342 can include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an international mobile subscriber identity (IMSI)). The base station can transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 can include at least one of: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE can determine that the two-step random access procedure is successfully completed if: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., the transport block 1342).

[0183] The UE and the base station can exchange control signaling. The control signaling can be referred to as L1 / L2 control signaling and can originate from a PHY layer (e.g., layer 1) and / or a MAC layer (e.g., layer 2). The control signaling can 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.

[0184] Downlink control signaling can include: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; time slot format information; pre-emption indication; power control command; and / or any other suitable signaling. A UE can receive downlink control signaling in a payload transmitted by a base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH can be referred to as downlink control information (DCI). In some scenarios, the PDCCH can be a group common PDCCH (GC-PDCCH) common to a group of UEs.

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

[0186] DCIs can be used for different purposes. The purpose can be indicated by a 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) can indicate paging information and / or a system information change notification. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or a trigger of PDCCH-ordered random access. A DCI with CRC parity check bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate a contention resolution (e.g., similar to a PDCCH order release). FIG. 14AMsg 3 1313 (e.g., Msg 3 of Msg 3 1313). Other RNTIs configured to the UE by the base station can include: configured scheduling RNTI (CS-RNTI), transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), and / or the like.

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

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

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

[0190] FIG. 1A An example of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing is shown. The CCE-to-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 coordination and / or frequency-selective transmission of control channels). The base station can perform different or the same CCE-to-REG mapping for different CORESETs. A CORESET can be associated with a CCE-to-REG mapping by RRC configuration. A CORESET can be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter can indicate QCL information for a demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

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

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

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

[0194] There can be five PUCCH formats, and the UE can determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of the UCI transmission and a number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. The UE can use PUCCH format 0 to transmit UCI in a PUCCH resource if more than one or two symbols are transmitted and a number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two. PUCCH format 1 can occupy a number between four and fourteen OFDM symbols and can include two or fewer bits. The UE can use PUCCH format 1 if four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. The UE can use PUCCH format 2 if more than one or two symbols are transmitted and the number of UCI bits is two or more. PUCCH format 3 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. The UE can use PUCCH format 3 if four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code. PUCCH format 4 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. The UE can use PUCCH format 4 if four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code.

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

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

[0197] FIG. 15 An example of a wireless device 1502 in communication with a base station 1504 is shown in accordance with embodiments of the present disclosure. The wireless device 1502 and the base station 1504 can be part of a mobile communication network, such as the mobile communication network 100 shown in FIG. 1. FIG. 15 The mobile communication network 100,FIG. 2A The mobile communication network 150 shown or any other communication network. FIG. 2B The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... FIG. 3 The same or similar configurations shown.

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

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

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

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

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

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

[0204] The processing system 1508 and / or the processing system 1518 can include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors can include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, on-board components, or any combination thereof. The processing system 1508 and / or the processing system 1518 can perform at least one of the following: signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that can enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0205] The processing system 1508 and / or the processing system 1518 can be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 can include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touchpad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 can receive user input data from and / or provide user output data to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power supply and / or can be configured to distribute the power to the other components in the wireless device 1502. The power supply can 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 can be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

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

[0207] FIG. 17A Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

[0208] FIG. 17A An exemplary structure for downlink transmission is shown. A baseband signal representing a physical downlink channel can perform one or more functions. The one or more functions can include: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulating scrambled bits to generate complex-valued modulation symbols; mapping complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on an antenna port; mapping of complex-valued modulation symbols for an antenna port to resource elements; generating a complex-valued time-domain OFDM signal for an antenna port; and so on. These functions are shown as examples, and other mechanisms can be implemented in various embodiments.

[0209] FIG. 17B Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

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

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

[0212] A base station can transmit one or more MAC PDUs to a wireless device. In an example, a MAC PDU can be a bit string that is length byte-aligned (e.g., aligned to a multiple of eight bits). In an example, a bit string can be represented by a table, where the most significant bit is the leftmost bit of the first row of the table and the least significant bit is the rightmost bit of the last row of the table. More generally, a bit string can be read from left to right and then in the reading order of the lines. In an example, the bit order of a parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0213] In an example, a MAC SDU can be a bit string that is length byte aligned (e.g., aligned to a multiple of eight bits). In an example, a MAC SDU can be included in a MAC PDU starting from the first bit. A MAC CE can be a bit string that is length byte aligned (e.g., aligned to a multiple of eight bits). A MAC subheader can be a bit string that is length byte aligned (e.g., aligned to a multiple of eight bits). In an example, a MAC subheader can be placed directly in front of a corresponding MAC SDU, MAC CE, or padding. A MAC entity can ignore the value of reserved bits in a DL MAC PDU.

[0214] In an example, a MAC PDU can include one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs can include: only a MAC subheader (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. A MAC SDU can have a variable size. A MAC subheader can correspond to a MAC SDU, a MAC CE, or padding.

[0215] In an example, when a MAC subheader corresponds to a MAC SDU, a variable size MAC CE, or padding, the MAC subheader can include: an R field having a one bit length; an F field having a one bit length; an LCID field having a multiple bit length; an L field having a multiple bit length, or a combination thereof.

[0216] FIG. 17B An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. In FIG. 17C In an example MAC subheader shown in FIG. 17C An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. In FIG. 18A In an example MAC subheader shown in FIG. 18B An example of a MAC subheader having an R field and an LCID field is shown. In FIG. 19 In an example MAC subheader shown in

[0217] FIG. 20An example of a DL MAC PDU is shown. Multiple MAC CEs, such as MAC CEs 1 and 2, can be placed together. A MAC subPDU including a MAC CE can be placed before a MAC subPDU including a MAC SDU or a MAC subPDU including padding. sCellDeactivationTimer An example of a UL MAC PDU is shown. Multiple MAC CEs, such as MAC CEs 1 and 2, can be placed together. In an embodiment, a MAC subPDU including a MAC CE can be placed after all MAC subPDUs including MAC SDUs. Additionally, a MAC subPDU can be placed before a MAC subPDU including padding.

[0218] In an example, a MAC entity of a base station can transmit one or more MAC CEs to a MAC entity of a wireless device. sCellDeactivationTimer An example of multiple LCIDs that can be associated with one or more MAC CEs is shown. The one or more MAC CEs can include at least one of: a SP ZP CSI-RS resource set activation / deactivation MAC CE; a PUCCH spatial relation activation / deactivation MAC CE; a SP SRS activation / deactivation MAC CE; a SP CSI reporting on PUCCH activation / deactivation MAC CE; a TCI state indication for UE-specific PDCCH MAC CE; a TCI state indication for UE-specific PDSCH MAC CE; a aperiodic CSI trigger state sub-selection MAC CE; a SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE; a UE contention resolution identity MAC CE; a timing advance command MAC CE; a DRX command MAC CE; a long DRX command MAC CE; a SCell activation / deactivation MAC CE (1 octet); a SCell activation / deactivation MAC CE (4 octets); and / or a duplication activation / deactivation MAC CE. In an example, a MAC CE, as transmitted by a MAC entity of a base station to a MAC entity of a wireless device, can have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs can have different LCIDs in MAC subheaders corresponding to the MAC CEs. For example, an LCID given by 111011 in a MAC subheader can indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0219] In an example, a MAC entity of a wireless device can transmit one or more MAC CEs to a MAC entity of a base station. sCellDeactivationTimerExamples of one or more MAC CEs are shown. The one or more MAC CEs can include at least one of: a short buffer status report (BSR) MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grant confirmation MAC CE; a single entry PHR MAC CE; a multiple entry PHR MAC CE; a short truncated BSR; and / or a long truncated BSR. In an example, a MAC CE can have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs can have different LCIDs in a MAC subheader corresponding to the MAC CEs. For example, an LCID given by 111011 in a MAC subheader can indicate that the MAC CE associated with the MAC subheader is a short truncated command MAC CE.

[0220] In carrier aggregation (CA), two or more component carriers (CCs) can be aggregated. A wireless device can simultaneously receive or transmit on one or more CCs using techniques of CA depending on the capabilities of the wireless device. In embodiments, a wireless device can support CA for contiguous CCs and / or for non-contiguous CCs. CCs can be organized into cells. For example, CCs can be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, a wireless device can have one RRC connection with a network. A cell that provides NAS mobility information can be a serving cell during an RRC connection setup / reestablishment handover. A cell that provides security input can be a serving cell during an RRC connection reestablishment / handover procedure. In an example, a serving cell can represent a PCell. In an example, a base station can transmit one or more messages including configuration parameters of a plurality of one or more SCells to a wireless device depending on the capabilities of the wireless device.

[0221] When configured with CA, a base station and / or a wireless device can employ an activation / deactivation mechanism of SCells to improve battery or power consumption of the wireless device. When a wireless device is configured with one or more SCells, a base station can activate or deactivate at least one of the one or more SCells. An SCell can be deactivated upon configuration of the SCell unless an SCell state associated with the SCell is set to “activated” or “dormant.”

[0222] A wireless device can activate / deactivate an SCell in response to receiving an SCell activation / deactivation MAC CE. In an example, a base station can transmit one or more messages including an SCell timer (e.g., sCellDeactivationTimer ) to a wireless device. In an example, a wireless device can deactivate an SCell in response to an expiration of the SCell timer.

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

[0224] When the wireless device receives a SCell activation / deactivation MAC CE deactivating an activated SCell, the wireless device can deactivate the activated SCell. In an example, when a first SCell timer associated with the activated SCell (e.g., FIG. 21A ) expires, the wireless device can deactivate the activated SCell. In response to deactivating the activated SCell, the wireless device can stop the first SCell timer associated with the activated SCell. In an example, in response to deactivating the activated SCell, the wireless device can clear one or more configured downlink assignments and / or one or more configured uplink grants of configured uplink grant type 2 associated with the activated SCell. In an example, in response to deactivating the activated SCell, the wireless device can: suspend one or more configured uplink grants of configured uplink grant type 1 associated with the activated SCell; and / or empty a HARQ buffer associated with the activated SCell.

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

[0226] FIG. 19 An example of a one-octet SCell activation / deactivation MAC CE is shown. A first MAC PDU subheader with a first LCID (e.g., ‘111010’ as shown in FIG. 21A ) can identify a one-octet SCell activation / deactivation MAC CE. The one-octet SCell activation / deactivation MAC CE can have a fixed size. The one-octet SCell activation / deactivation MAC CE can include a single octet. The single octet can include a first number of C fields (e.g., seven) and a second number of R fields (e.g., one). FIG. 21B An example of a four-octet SCell activation / deactivation MAC CE is shown. A second MAC PDU subheader with a second LCID (e.g., ‘111001’ as shown in FIG. 21A ) can identify a four-octet SCell activation / deactivation MAC CE. The four-octet SCell activation / deactivation MAC CE can have a fixed size. The four-octet SCell activation / deactivation MAC CE can include four octets. The four octets can include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., one).

[0227] In FIG. 21B and / orBWP- In an example, if a SCell with SCell index i is configured, then C i The field can indicate an activation / deactivation status of a SCell with SCell index i. In an example, when C i The SCell with SCell index i can be activated when the C i The SCell with SCell index i can be deactivated when the C i The field can be ignored by the wireless device if there is no SCell configured with SCell index i. In InactivityTimer In an example, the R field can indicate a reserved bit. The R field can be set to zero. FIG. 22 In an example, the R field can indicate a reserved bit. The R field can be set to zero.

[0228] A base station can configure a wireless device with uplink (UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation is configured, the base station can further configure the wireless device with at least a DL BWP (i.e., there can be no UL BWP in UL) to enable BA on a SCell. For a PCell, an initial active BWP can be a first BWP used for initial access. For a SCell, a first active BWP can be a second BWP configured for the wireless device to operate on the SCell when the SCell is activated. In paired spectrum (e.g., FDD), the base station and / or the wireless device can independently switch the DL BWP and the UL BWP. In unpaired spectrum (e.g., TDD), the base station and / or the wireless device can simultaneously switch the DL BWP and the UL BWP.

[0229] In an example, a base station and / or a wireless device can switch BWP among configured BWPs by DCI or BWP inactivity timer. When a BWP inactivity timer is configured for a serving cell, the base station and / or the wireless device can switch an active BWP to a default BWP in response to an expiration of the BWP inactivity timer associated with the serving cell. The default BWP can be configured by the network. In an example, for an FDD system, one UL BWP and one DL BWP per uplink carrier in an active serving cell can be in active state at a time when configured with BA. In an example, for a TDD system, one DL / UL BWP pair can be in active state in an active serving cell at a time. Operating on the one UL BWP and the one DL BWP (or the one DL / UL pair) can improve wireless device battery consumption. BWPs other than the one active UL BWP and the one active DL BWP on which the wireless device can work can be deactivated. On the deactivated BWPs, the wireless device can: not monitor PDCCH; and / or not transmit on PUCCH, PRACH, and UL-SCH.

[0230] In an example, a serving cell can be configured with up to a first number (e.g., four) of BWPs. In an example, for an activated serving cell, there can be one active BWP at any point in time. In an example, BWP switching for a serving cell can be used to simultaneously activate an inactive BWP and deactivate an active BWP. In an example, BWP switching can be controlled by PDCCH indicating downlink assignment or uplink grant. In an example, BWP switching can be controlled by a BWP inactivity timer (e.g., RRCReconfiguration RRCRestablishment In an example, BWP switching can be controlled by a MAC entity in response to initiating a random access procedure. Upon adding a SpCell or activating an SCell, one BWP can initially be active without receiving PDCCH indicating downlink assignment or uplink grant. An active BWP for a serving cell can be indicated by RRC and / or PDCCH. In an example, for unpaired spectrum, a DL BWP can be paired with a UL BWP and BWP switching can be common for both UL and DL.

[0231] RRCSetup An example of BWP switching on a cell (e.g., PCell or SCell) is shown. In an example, a wireless device can receive at least one RRC message from a base station, the at least one RRC message including parameters of a cell and one or more BWPs associated with the cell. The RRC message can include: an RRC connection reconfiguration message (e.g., sCellDeactivationTimer ); an RRC connection reestablishment message (e.g., BWP-InactivityTimer); and / or RRC connection setup messages (e.g., First Of the one or more BWPs, at least one BWP can be configured as the first active BWP (e.g., BWP 1), and one BWP is configured as the default BWP (e.g., BWP 0). The radio device can receive a command to activate the cell (e.g., RRC message, MAC CE, or DCI) in the nth time slot. The radio device can start a cell deactivation timer (e.g., ...). sCellDeactivationTimer The wireless device may initiate CSI-related actions for the cell and / or initiate CSI-related actions for the first active BWP of the cell. In response to cell activation, the wireless device may begin monitoring the PDCCH on BWP 1.

[0232] In the example, in response to receiving the DCI indicating DL assignment on BWP 1, the wireless device can... m 个 The time slot begins to restart the BWP inactive timer (e.g., bwp-InactivityTimer When the BWP inactivity timer expires, the wireless device can... bwp-InactivityTimer s The time slot switches back to the default BWP (e.g., BWP 0) as the active BWP. When MIB When the time expires, the wireless device can disable the cell and / or stop the BWP inactive timer.

[0233] In the example, the MAC entity can apply normal operation to the active BWP of the active serving cell configured with BWP, including: transmitting on UL-SCH; transmitting on RACH; monitoring PDCCH; transmitting PUCCH; receiving DL-SCH; and / or (re)initializing any suspended configured uplink license of configured license type 1 according to the stored configuration (if any).

[0234] In the example, on an inactive BWP of each active serving cell configured with a BWP, the MAC entity may: not transmit on UL-SCH; not transmit on RACH; not monitor PDCCH; not transmit PUCCH; not transmit SRS and not receive DL-SCH; clear any configured downlink assignments and configured uplink licenses of configured license type 2; and / or suspend any configured uplink licenses of configured type 1.

[0235] In an example, if a MAC entity receives a PDCCH for a BWP switch of a serving cell while a random access procedure associated with this serving cell is not ongoing, the wireless device can perform a BWP switch to the BWP indicated by the PDCCH. In an example, if the bandwidth part indicator field is configured with DCI format 1 1, the bandwidth part indicator field value can indicate the active DL BWP for DL reception from the set of configured DL BWPs. In an example, if the bandwidth part indicator field is configured with DCI format 0 1, the bandwidth part indicator field value can indicate the active UL BWP for UL transmission from the set of configured UL BWPs.

[0236] In an example, for a primary cell, a default DL BWP among the configured DL BWPs can be provided to the wireless device by a higher layer parameter Default-DL-BWP. If the default DL BWP is not provided to the wireless device by the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In an example, a timer value for the primary cell can be provided to the wireless device by a higher layer parameter pdcch-ConfigSIB1 Timer-SCell. If configured, the wireless device can increment the timer (if running) at per 1 millisecond intervals for frequency range 1 or per 0.5 millisecond intervals for frequency range 2, with the condition that during said intervals, if the wireless device fails to detect a DCI format 1 1 for paired spectrum operation, or if the wireless device fails to detect a DCI format 1 1 or a DCI format 0 1 for unpaired spectrum operation.

[0237] In an example, if a wireless device is configured for a secondary cell with a higher layer parameter Default-DL-BWP indicating a default DL BWP among the configured DL BWPs, and the wireless device is configured with a higher layer parameter Timer-SCell indicating a timer value ​ , the wireless device procedure on the secondary cell can be the same as the wireless device procedure on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0238] In an example, if a wireless device is configured with a first active DL BWP on a secondary cell or carrier by a higher layer parameter Active-BWP-DL-SCell and a first active UL BWP by a higher layer parameter Active-BWP-UL-SCell, the wireless device can use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0239] In an example, the set of PDCCH candidates to be monitored by the wireless device can be defined in terms of PDCCH search space sets. A 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: ​ configured by ​ or by PDCCH-ConfigCommon configured by searchSpaceSIB1 or by PDCCH-ConfigCommon configured by searchSpaceZero Type0-PDCCH CSS set configured for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG; by PDCCH-ConfigCommon configured by searchSpaceOtherSystemInformation Type0A-PDCCH CSS set configured for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG; by PDCCH-ConfigCommon configured by ra-SearchSpace Type1-PDCCH CSS set configured for DCI formats with CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell; by PDCCH-ConfigCommon configured by pagingSearchSpace Type2-PDCCH CSS set configured for DCI formats with CRC scrambled by P-RNTI on the primary cell of the MCG; by PDCCH-Config Type3-PDCCH CSS set configured for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI in (PDCCH-Config) with searchSpaceType = common Type3-PDCCH CSS set configured for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI in (PDCCH-Config) with SearchSpace = PDCCH-Config Type3-PDCCH CSS set configured for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI in (PDCCH-Config) with searchSpaceType = ue-Specific Type3-PDCCH CSS set configured for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI in (PDCCH-Config) with SearchSpace =

[0240] In an example, a wireless device determines a PDCCH monitoring occasion on an active DL BWP based on one or more PDCCH configuration parameters including: a PDCCH monitoring periodicity, a PDCCH monitoring offset, and a PDCCH monitoring pattern within a slot. For a search space set (SS s ), if , then the wireless device determines that the PDCCH monitoring occasion exists in a number of slots in a number of frames equal to . is the number of slots in a frame when the set of configuration parameters . μ is the slot offset indicated in the PDCCH configuration parameters. is the PDCCH monitoring periodicity indicated in the PDCCH configuration parameters. The wireless device monitors PDCCH candidates for the search space set starting from slot for consecutive slots and does not monitor PDCCH candidates for the search space set during the next consecutive slots. In an example, a USS at a CCE aggregation level is defined by a set of PDCCH candidates for a CCE aggregation level . In an example, a wireless device decides, for a search space set associated with a CORESET

[0241] , that in a slot , for an active DL BWP of a serving cell corresponding to a carrier indicator field value , the CCE indices of an aggregation level corresponding to PDCCH candidates of the search space set are , where for any CSS ; for a USS , , for , for , for , for , and ; ; in a CORESET , is the number of CCEs numbered from 0 to ; if the wireless device is configured with a carrier indicator field for a serving cell on which PDCCH is monitored CrossCarrierSchedulingConfig , then It is the carrier indicator field value; otherwise, including for any CSS, ; ,in The wireless device is configured to be compatible with... For the corresponding service cell, this is for the search space set aggregation level The number of PDCCH candidates monitored; for any CSS, For USS, It is pervasive for the search space set CCE aggregation level All configurations value The maximum value; and used for The RNTI value is C-RNTI.

[0242] In the example, the wireless device can monitor a set of PDCCH candidates based on configuration parameters of a search space set including multiple search spaces (SSs). The wireless device can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates 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 referred to as blind decoding.

[0243] Figure 23A This example illustrates the configuration parameters of the Master Information Block (MIB) for a cell (e.g., PCell). In this example, the radio device can receive the MIB via the PBCH based on the received Primary Synchronization Signal (PSS) and / or Secondary Synchronization Signal (SSS). The MIB configuration parameters may include six bits of the System Frame Number (SFN). systemFrameNumber Subcarrier spacing indication ( subCarrierSpacingCommon The frequency domain offset between the SSB and the entire resource block grid in terms of the number of subcarriers. ssb-SubcarrierOffset Indicators indicating whether a residential area is prohibited ( ) cellBarred ), DMRS location indication (indicating the location of DMRS) dmrs-TypeA-Position ), including the parameters of the PDCCH CORESET and SS of the public CORESET ( pdcch-ConfigSIB1) Public search space and necessary PDCCH parameters.

[0244] In an example, pdcch-ConfigSIB1 may include a first parameter (e.g., controlResourceSetZero ) indicating a common ControlResourceSet (CORESET) with ID #0 (e.g., CORESET #0) of an initial BWP of a cell. controlResourceSetZero may be an integer between 0 and 15. Each integer between 0 and 15 can identify a configuration of CORESET #0. Figure 23B An example of a configuration of CORESET #0 is shown. As Figure 23B indicated, based on a value of the integer of controlResourceSetZero , a wireless device can determine a SSB and CORESET #0 multiplexing pattern, a number of RBs of CORESET #0, a number of symbols of CORESET #0, a RB offset of CORESET #0.

[0245] In an example, pdcch-ConfigSIB1 may include a second parameter (e.g., searchSpaceZero ) indicating a common search space with ID #0 (e.g., SS #0) of an initial BWP of a cell. searchSpaceZero may be an integer between 0 and 15. Each integer between 0 and 15 can identify a configuration of SS #0. Figure 23C An example of a configuration of SS #0 is shown. As Figure 23C indicated, based on a value of the integer of searchSpaceZero , a wireless device can determine one or more parameters (e.g., O , M ) for slot determination for PDCCH monitoring, a first symbol index for PDCCH monitoring, and / or a number of search spaces per slot.

[0246] In an example, based on receiving a MIB, a wireless device can monitor a PDCCH via a SS #0 of a CORESET #0 for receiving a DCI scheduling a system information block 1 (SIB1). The wireless device can receive the DCI with a CRC scrambled with a system information radio network temporary identifier (SI-RNTI) that is specific to receiving the SIB1.

[0247] Figure 24 An example of RRC configuration parameters of a system information block (SIB) is shown. A SIB (e.g., SIB1 ) can contain information relevant when evaluating whether to allow a wireless device to access a cell, and can define the scheduling of other system information. A SIB can contain radio resource configuration information common to all wireless devices and barring information applied for unified access control. In an example, a base station can transmit one or more SIBs of information to a wireless device (or multiple wireless devices). As Figure 24As shown, the one or more SIB information parameters can include one or more parameters for cell selection related to the serving cell (e.g., cellSelectionInfo ), one or more configuration parameters of the serving cell (e.g., indicated in ServingCellConfigCommonSIB IE ), and one or more other parameters. ServingCellConfigCommonSIB IE The one or more SIB information parameters can include at least one of: common downlink parameters of the serving cell (e.g., indicated in DownlinkConfigCommonSIB IE), common uplink parameters of the serving cell (e.g., indicated in UplinkConfigCommonSIB IE), and other parameters.

[0248] In an example, DownlinkConfigCommonSIB IE can include parameters of an initial downlink BWP of a serving (e.g., SpCell) cell. The parameters of the initial downlink BWP can be included in BWP-DownlinkCommon IE (as shown in Figure 25 ). BWP-DownlinkCommon IE can be used to configure common parameters of downlink BWPs of a serving cell. The base station can configure locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of the serving cell in the frequency domain. The wireless device can apply locationAndBandwidth (e.g., determine the frequency location of the signal described with respect to this locationAndBandwidth ) upon receiving this field, but it keeps CORESET#0 until receiving RRCSetup / RRCResume / RRCReestablishment afterwards.

[0249] In an example, UplinkConfigCommonSIB IE can include parameters of an initial uplink BWP of a serving cell (e.g., SpCell). The parameters of the initial uplink BWP can be included in BWP-UplinkCommon IE. BWP- UplinkCommon IE can be used to configure common parameters of uplink BWPs. The common parameters of uplink BWPs are “cell-specific”. The base station can ensure the necessary alignment with corresponding parameters of other wireless devices. The common parameters of the initial bandwidth part of the PCell can be provided via system information. For all other serving cells, the base station can provide the common parameters via dedicated signaling.

[0250] Figure 25 An example is shown of RRC configuration parameters (e.g., BWP- DownlinkCommon IE) in a downlink BWP of a serving cell. The base station can transmit one or more configuration parameters of a downlink BWP (e.g., an initial downlink BWP) of a serving cell to a wireless device (or multiple wireless devices). As Figure 25As shown, one or more configuration parameters of a downlink BWP can include one or more general BWP parameters of the downlink BWP, one or more cell-specific parameters of PDCCH of the downlink BWP (e.g., in pdcch-ConfigCommon IE), one or more cell-specific parameters of PDSCH of the BWP (e.g., in pdsch-ConfigCommon IE), and one or more other parameters. pdcch-ConfigCommon The IE can include parameters of a common control resource set #0 (e.g., in controlResourceSetZero ), which can be used in any common or UE-specific search space. controlResourceSetZero The value of MIB pdcch-ConfigSIB1 can be interpreted like the corresponding bit in pdcch-ConfigCommon . The IE can include parameters of an additional common control resource set (e.g., in commonControlResourceSet ), which can be configured and used for any common or UE-specific search space. If the network configures this field, for this ControlResourceSet , it uses ControlResourceSetId other than 0. The parameters of the control resource set can be implemented as shown in Figure 25 . The network configures SIB1 in commonControlResourceSet so that it is contained in the bandwidth of CORESET #0. pdcch-ConfigCommon The IE can include parameters of a list of additional common search spaces (e.g., in commonSearchSpaceList ). The parameters of the search spaces can be implemented based on the example of Figure 26 . pdcch- ConfigCommon The IE can indicate from the list of search spaces a search space for paging (e.g., pagingSearchSpace ), a search space for random access procedure (e.g., ra-SearchSpace ), a search space for SIB1 message (e.g., searchSpaceSIB1 ), common search space #0 (e.g., searchSpaceZero ), and one or more other search spaces.

[0251] As shown in Figure 25 , a control resource set (CORESET) can be associated with a CORESET index (e.g., ControlResourceSetId ). A CORESET index with a value of 0 can identify a common CORESET configured in MIB and in ServingCellConfigCommon ( controlResourceSetZero ), and cannot be used in ControlResourceSet IE. A CORESET index with other values can identify a CORESET configured by dedicated signaling or in SIB1 .controlResourceSetId It is unique within the BWP of the serving cell. CORESET can be associated with an index of the CORESET pool that indicates the CORESET. coresetPoolIndex Associated with CORESET. CORESET can be associated with duration parameters (e.g., duration Associated with this, the duration parameter indicates the continuous duration of CORESET in terms of the number of signs. In the example, such as... Figure 25 As shown, CORESET configuration parameters may include at least one of the following: frequency resource indication (e.g., frequencyDomainResources ), CCE-REG mapping type indicator (e.g., cce-REG-MappingType This includes multiple TCI states, indicators indicating the presence of TCIs in the DCI, etc. A frequency resource indicator containing several bits (e.g., 45 bits) indicates frequency domain resources, each bit corresponding to a group of 6 RBs, where the grouping starts from the first RB group in the BWP of the cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit corresponds to the first RB group in the BWP, and so on. A bit set to 1 indicates that the RB group corresponding to that bit belongs to the frequency domain resources of the CORESET. Bits corresponding to a group of RBs not fully included in the BWP configured within the CORESET are set to zero.

[0252] Figure 26 The configuration of the search space is shown (e.g., SearchSpace Example (IE). In the example, one or more search space configuration parameters may include at least one of the following: search space ID ( searchSpaceId Control Resource Set ID ( controlResourceSetId ), monitoring time slot period and offset parameters ( mo nitoringSlotPeriodicityAndOffset Search space duration value ( duration ), monitoring symbol indication ( monitoringSymbolsWithinSlot ), the number of candidates for the aggregation level ( nrofCandidates ) and / or SS type indicator indicating common SS type or UE-specific SS type ( searchSpaceType The monitoring slot period and offset parameters can indicate the slots used for periodic PDCCH monitoring (e.g., within a radio frame) and the slot offset (e.g., related to the start of a radio frame). The monitoring symbol indicator can indicate on which (which) symbols of a slot the wireless device can monitor the PDCCH on the SS. The control resource set ID can identify the set of control resources on which the SS can reside. The search space duration value can indicate the duration of the SS in each time slot (e.g., during...). monitoringSlotPeriodicityAndOffsetThe number of consecutive slots that the search space duration value indicates (e.g., as given in the search space duration field in the search space configuration). If the search space duration value is not present, the wireless device can apply a value of 1 slot, except for DCI format 2 0. For DCI format 2 0, the wireless device can ignore this field. The maximum valid duration can be periodicity-1 (e.g., as given in the periodicity field in the search space configuration). In an example, the SS type indicator can indicate whether the SS is a common search space (e.g., currently) or a UE-specific search space and the DCI format to monitor. The DCI format configured by the search space configuration can include at least one of DCI format 0 0, DCI format 0 1, DCI format 1 0, DCI format 1 1, DCI format 2 0, DCI format 2 1, DCI format 2 2, DCI format 2 3, DCI format 1 2, DCI format 0 2, DCI format 3 0, DCI format 3 1, and / or the like. Based on the DCI format, the wireless device can monitor the SS. monitoringSlotPeriodicityAndOffset In an example, the search space duration field can be configured by the search space configuration. The search space duration field can indicate the number of consecutive slots that the search space duration value indicates (e.g., as given in the search space duration field in the search space configuration). If the search space duration value is not present, the wireless device can apply a value of 1 slot, except for DCI format 2 0. For DCI format 2 0, the wireless device can ignore this field. The maximum valid duration can be periodicity-1 (e.g., as given in the periodicity field in the search space configuration). In an example, the SS type indicator can indicate whether the SS is a common search space (e.g., currently) or a UE-specific search space and the DCI format to monitor. The DCI format configured by the search space configuration can include at least one of DCI format 0 0, DCI format 0 1, DCI format 1 0, DCI format 1 1, DCI format 2 0, DCI format 2 1, DCI format 2 2, DCI format 2 3, DCI format 1 2, DCI format 0 2, DCI format 3 0, DCI format 3 1, and / or the like. Based on the DCI format, the wireless device can monitor the SS. SearchSpace searchSpaceType The DCI format configured by the search space configuration can include at least one of DCI format 0 0, DCI format 0 1, DCI format 1 0, DCI format 1 1, DCI format 2 0, DCI format 2 1, DCI format 2 2, DCI format 2 3, DCI format 1 2, DCI format 0 2, DCI format 3 0, DCI format 3 1, and / or the like. Based on the DCI format, the wireless device can monitor the SS. Figure 29 In an example, the search space duration field can be configured by the search space configuration. The search space duration field can indicate the number of consecutive slots that the search space duration value indicates (e.g., as given in the search space duration field in the search space configuration). If the search space duration value is not present, the wireless device can apply a value of 1 slot, except for DCI format 2 0. For DCI format 2 0, the wireless device can ignore this field. The maximum valid duration can be periodicity-1 (e.g., as given in the periodicity field in the search space configuration). In an example, the SS type indicator can indicate whether the SS is a common search space (e.g., currently) or a UE-specific search space and the DCI format to monitor. The DCI format configured by the search space configuration can include at least one of DCI format 0 0, DCI format 0 1, DCI format 1 0, DCI format 1 1, DCI format 2 0, DCI format 2 1, DCI format 2 2, DCI format 2 3, DCI format 1 2, DCI format 0 2, DCI format 3 0, DCI format 3 1, and / or the like. Based on the DCI format, the wireless device can monitor the SS.

[0253] Figure 27 An example of a configuration of a search space (e.g., a common search space) is shown. In an example, in addition to the first parameter configured by the search space configuration as shown above, a second parameter configured by the search space configuration can be used for the SS. The second parameter configured by the search space configuration can include a CORESET ID that identifies a corresponding CORESET for the SS. When the CORESET ID is present in the search space configuration, the wireless device can ignore the search space duration field in the search space configuration of the SS. In an example, the SS type indicator can indicate whether the SS is a common search space (e.g., currently) or a UE-specific search space and the DCI format to monitor. The DCI format configured by the search space configuration can include DCI format 2 4, DCI format 2 5, DCI format 2 6, and / or the like. Based on the DCI format, the wireless device can monitor the SS. SearchSpaceExt-r16 Figure 26 SearchSpace SearchSpaceExt-r16 SearchSpaceExt-r16 SearchSpaceExt-r16 SearchSpace controlResourceSetId SearchSpaceExt-r16 searchSpaceType- r16 searchSpaceType-r16 Figure 29 In an example, the search space duration field can be configured by the search space configuration. The search space duration field can indicate the number of consecutive slots that the search space duration value indicates (e.g., as given in the search space duration field in the search space configuration). If the search space duration value is not present, the wireless device can apply a value of 1 slot, except for DCI format 2 0. For DCI format 2 0, the wireless device can ignore this field. The maximum valid duration can be periodicity-1 (e.g., as given in the periodicity field in the search space configuration). In an example, the SS type indicator can indicate whether the SS is a common search space (e.g., currently) or a UE-specific search space and the DCI format to monitor. The DCI format configured by the search space configuration can include at least one of DCI format 0 0, DCI format 0 1, DCI format 1 0, DCI format 1 1, DCI format 2 0, DCI format 2 1, DCI format 2 2, DCI format 2 3, DCI format 1 2, DCI format 0 2, DCI format 3 0, DCI format 3 1, and / or the like. Based on the DCI format, the wireless device can monitor the SS.

[0254] In an example, the search space duration field can be configured by the search space configuration. The search space duration field can indicate the number of consecutive slots that the search space duration value indicates (e.g., as given in the search space duration field in the search space configuration). If the search space duration value is not present, the wireless device can apply a value of 1 slot, except for DCI format 2 0. For DCI format 2 0, the wireless device can ignore this field. The maximum valid duration can be periodicity-1 (e.g., as given in the periodicity field in the search space configuration). In an example, the SS type indicator can indicate whether the SS is a common search space (e.g., currently) or a UE-specific search space and the DCI format to monitor. The DCI format configured by the search space configuration can include at least one of DCI format 0 0, DCI format 0 1, DCI format 1 0, DCI format 1 1, DCI format 2 0, DCI format 2 1, DCI format 2 2, DCI format 2 3, DCI format 1 2, DCI format 0 2, DCI format 3 0, DCI format 3 1, and / or the like. Based on the DCI format, the wireless device can monitor the SS. SearchSpaceExt-r16 searchSpaceGroupIdList SearchSpaceExt-r16 ​​​​​​​​​​​​​​Configuration parameters of a configured SS can include a frequency monitoring location indication bitmap (e.g., freqMonitorLocations ). A value of 1 of a bit of the bitmap can indicate that a frequency domain resource allocation configured from a pattern of an associated CORESET is mapped to a corresponding resource block (RB) set. LSBs of the bitmap can correspond to the lowest RB sets in the BWP. For an RB set indicated in the bitmap, a first PRB of a frequency domain monitoring location confined within the RB set is aligned with a first PRB of the RB set provided by the associated CORESET. rb-Offset}).

[0255] Figure 28 Examples of PDCCH monitoring of a SS based on a configuration of the SS are shown. In an example, based on the example embodiments described above with respect to Figure 26 and / or Figure 27 , a wireless device can be configured with a SS. The wireless device can determine a PDCCH monitoring occasion within a slot on an active DL BWP based on one or more configuration parameters of the SS s , including a PDCCH monitoring periodicity , a PDCCH monitoring duration , a PDCCH monitoring offset , and a PDCCH monitoring pattern monitoringSymbolsWithinSlot . For a SS , if . + - , the wireless device can determine that there is a PDCCH monitoring occasion in a slot in a frame . may be multiple slots in a frame. The frame structure can be implemented based on the example embodiments described above with respect to FIG. 7 . The wireless device can monitor PDCCH candidates of the SS in consecutive slots starting from a slot , and not monitor search spaces of PDCCH candidates in the next consecutive slots. As shown in FIG. 28 , . Based on and ​​The wireless device can monitor the PDCCH in slot 0, slot 1, and slot 2. The wireless device can skip monitoring the PDCCH in slot 3, slot 4, and slot 5. The wireless device can monitor the PDCCH candidates based on the example embodiments described in the preceding paragraphs of this specification.

[0256] FIG. 29 Examples of DCI formats that can be used when a first wireless device (e.g., a base station) transmits control information to a second wireless device (e.g., a terminal) are shown. Different DCI formats can include different DCI fields and / or have different DCI payload sizes. Different DCI formats can have different signaling purposes. In an example, DCI format 0 0 can be used to schedule a PUSCH in one cell. DCI format 0 1 can be used to schedule one or more PUSCHs in one cell, or to indicate a CG-DFI (configured grant-Downlink feedback information) for a configured grant PUSCH, etc. The DCI formats that the wireless device can monitor in the SSs can be configured based on the example embodiments described above in relation to FIG. 26 and / or FIG. 27 .

[0257] FIG. 30A Examples of DCI-based PDSCH scheduling are shown. In an example, a wireless device can monitor a PDCCH via one or more SSs on a BWP of a cell. The one or more SSs can be configured based on the example embodiments described above in relation to FIG. 26 and / or FIG. 27 . The wireless device can monitor the PDCCH in one or more slots based on a PDCCH monitoring periodicity and a PDCCH monitoring duration configured for the one or more SSs. In an example, the wireless device can receive a DCI during the PDCCH monitoring in a slot. The DCI can include a downlink assignment (or an uplink grant) indicating PDSCH resources (or PUSCH resources) for transmitting a TB. Each DCI can schedule a TB corresponding to a HARQ process. The TB can include a single codeword (e.g., in response to the wireless device not supporting spatial multiplexing). The TB can include two codewords (e.g., in response to the wireless device supporting spatial multiplexing), each codeword being associated with a corresponding MCS indication, NDI indication, and / or RV indication. The downlink assignment for the TB can include one or more symbols of a slot.

[0258] As FIG. 30AAs shown, different DCIs can indicate downlink assignments corresponding to different PDSCHs (for different TBs). DCI1 in the first slot can indicate a downlink assignment for PDSCH1. DCI2 in the second slot can indicate a downlink assignment for PDSCH2. DCI3 in the second slot can indicate a downlink assignment for PDSCH3, and so on. Each PDSCH (e.g., PDSCH1, PDSCH2, PDSCH3) can be used to transmit a TB corresponding to a HARQ process. In an example, a slot can include resources for PDCCH and / or PDSCH. The resources for PDCCH / PDSCH can be configured based on the example embodiments described above in relation to FIG. 7 slots. The resources for PDCCH / PDSCH can be configured based on the example embodiments described above in relation to FIG. 14A 、 FIG. 14B 、 FIG. 25 、 FIG. 26 and / or FIG. 27 .

[0259] As shown in FIG. 30A , a DCI can indicate PDSCH resources for a TB corresponding to a HARQ process. Scheduling a TB based on a DCI can be referred to as a single-PDSCH scheduling scheme. In comparison to a single-PDSCH scheduling scheme, a DCI scheduling multiple PDSCHs can be referred to as a multiple-PDSCH (or multi-PDSCH) scheduling scheme. Scheduling multiple PDSCHs (e.g., each PDSCH associated with a corresponding TB) based on a single DCI can reduce signaling overhead and / or reduce power consumption for PDCCH monitoring. The multiple-PDSCH scheduling scheme can be beneficial for wireless systems deployed at high frequencies (e.g., above 50 GHz), where a slot length can be 15.6 us for a 960 KHz subcarrier spacing in comparison to 1 ms for a 15 KHz subcarrier spacing at low frequencies (e.g., 2 GHz). FIG. 30B An example of a multiple-PDSCH scheduling scheme is shown.

[0260] As shown in FIG. 30B , a wireless device can receive a DCI during PDCCH monitoring in a slot. The DCI can include a set of downlink assignments (or uplink grants) indicating multiple PDSCH resources (or PUSCH resources) for transmitting multiple TBs. The DCI can schedule multiple TBs, each TB associated with a corresponding HARQ process. Each TB of the multiple TBs can be transmitted in a corresponding slot indicated by one of the PDSCH resources associated with the TB.

[0261] As shown in FIG. 30BAs shown, DCI 1 in the first slot (e.g., slot y) can indicate downlink assignments for PDSCH1, PDSCH2, PDSCH3, and PDSCH4. PDSCH1 can be in slot x and used to transmit TB 1. PDSCH2 can be in slot x+1 and used to transmit TB 2. PDSCH3 can be in slot x+2 and can be used to transmit TB 3. PDSCH4 can be in slot x+3 and can be used to transmit TB 4. Scheduling multiple PDSCHs in a DCI can reduce signaling overhead and / or reduce power consumption of a wireless device.

[0262] In an example, when a wireless system is deployed at high frequencies (e.g., above 50 GHz), a scheduling unit (e.g., a slot) can be much shorter than at low frequencies (e.g., 2 GHz). A wireless device can monitor PDCCH more frequently at high frequencies than in low frequencies. For example, when using 960 KHz SCS at high frequencies, the length of a slot can be about 1 / 64 of the length of a slot when using 15 KHz SCS at low frequencies. If a wireless device is configured to monitor PDCCH at the granularity of a slot, the wireless device can monitor PDCCH in a system configured with 960 KHz SCS with 64 times the complexity of PDCCH monitoring in a system configured with 15 KHz SCS. This can increase power consumption of the wireless device. In an example, if the SCS is 15 KHz, the maximum number of PDCCH candidates per slot on a BWP can be 44, if the SCS of the BWP is 30 KHz, the maximum number is 36, if the SCS of the BWP is 60 KHz, the maximum number is 22, or if the SCS of the BWP is 120 KHz, the maximum number is 20. The maximum number of PDCCH candidates per slot can decrease as the SCS increases. Decreased PDCCH candidates can decrease throughput of signaling transmissions.

[0263] In an example, to improve power consumption of a wireless device operating at high frequencies and / or to increase signaling throughput, a base station can transmit a DCI scheduling multiple PDSCHs based on the example embodiments described above with respect to FIG. 30B In an example, a base station can transmit, to a wireless device at high frequencies, configuration parameters of a first SS of a first BWP indicating a first PDCCH monitoring periodicity and a first PDCCH monitoring duration (e.g., a first PDCCH monitoring occasion) based on the example embodiments described above with respect to T s= 1 slot), where for the second BWP, the first PDCCH monitoring periodicity can be longer than the second PDCCH monitoring periodicity of the second SS, and / or for the second BWP, the first PDCCH monitoring duration can be shorter than the second PDCCH monitoring duration. Based on the prior art, the wireless device can monitor PDCCHs configured on the first SS with different DCI formats with the first PDCCH monitoring periodicity and the first PDCCH monitoring duration. In an example, some DCI formats (e.g., DCI format 0_0 / 1_0, DCI format 2_x, etc.) can not be suitable for transmission based on the first PDCCH monitoring periodicity and the first PDCCH monitoring duration. DCI format 1_0 (or 0_0) can be used only to schedule a single PDSCH (or a single PUSCH). Based on backward compatibility / device cost considerations, DCI format 1_0 (or 0_0) can not be used to schedule multiple PDSCHs (or multiple PUSCHs). DCI format 2_x (e.g., 2_0 / 2_1 / 2_2 / 2_3 / 2_4 / 2_5 / 2_6) can not be used to schedule PDSCHs / PUSCHs. Monitoring DCI format 0_0 / 1_0 and / or DCI format 2_x according to the longer PDCCH monitoring periodicity and the shorter PDCCH monitoring duration configured for multi-PDSCH scheduling can increase latency for system information delivery (e.g., when system information is scheduled by DCI format 1_0), or increase latency for group common control information delivery (e.g., when group common control information is scheduled by DCI format 2_x). The prior art can increase latency for system information or group common control information delivery when PDCCH monitoring periodicity and / or PDCCH monitoring duration are configured for multi-PDSCH scheduling. When multi-PDSCH scheduling is supported, for example, at high frequencies, there is a need to reduce latency for system information or group common control information delivery.

[0264] In an example embodiment, a base station can transmit a configuration parameter to a wireless device, the configuration parameter including a DCI format specific PDCCH monitoring periodicity / duration on a SS of a BWP. The wireless device can determine PDCCH monitoring occasions for different DCI formats according to different DCI format specific PDCCH monitoring periodicity and / or different DCI format specific PDCCH monitoring duration. The example embodiment can reduce latency for system information or group common control information delivery when multi-PDSCH scheduling is supported. The example embodiment can reduce power consumption for PDCCH monitoring for UE specific TB scheduling when multi-PDSCH scheduling is supported.

[0265] In an exemplary implementation, when a DCI scheduling multiple PDSCHs is received, the wireless device may ignore the PDCCH monitoring period / duration of the SS configured by the RRC message. Ignoring the PDCCH monitoring period / duration may include skipping monitoring of a certain number of PDCCHs in a time slot after receiving the DCI, wherein this number may be determined based on the total number of PDSCHs scheduled by the DCI.

[0266] In an exemplary implementation, the base station can keep the SS configuration parameters unchanged. The wireless device can adapt PDCCH monitoring based on whether DCI schedules a single PDSCH or multiple PDSCHs in multiple time slots. This exemplary implementation can reduce the power consumption of the wireless device and / or the latency for delivering system information.

[0267] In an exemplary implementation, the wireless device can be used for a first DCI format (e.g., such as...). FIG. 29 The PDCCH is monitored during the first PDCCH monitoring time for single PDSCH / PUSCH scheduling in the DCI format 1_0 / 0_0 shown, or other common DCI formats 2-0 / 2-1 / 2-2 / 2-3 / 2-4 / 2-5 / 2-6. The wireless device can monitor the PDCCH during the second PDCCH monitoring time for the second DCI format (e.g., DCI format 1_1 / 0_1 or DCI format 1_2 / 0_2) for multi-PDSCH / PUSCH scheduling. The first PDCCH monitoring time may have a shorter period than the second PDCCH monitoring time. The first PDCCH monitoring time may have a longer duration (in time slots) than the second PDCCH monitoring time. The first and second PDCCH monitoring times can be associated with a single SS (e.g., CSS or USS) or different SSs. Based on monitoring the first PDCCH monitoring time, the wireless device can perform PDSCH / PUSCH (or indices such as...) via PDSCH / PUSCH. FIG. 29A wireless device can receive a first DCI with a first DCI format scheduling a TB. The TB can be a system information message or a broadcast message. The wireless device can receive the TB via a PDSCH or transmit the TB via a PUSCH. In an example, based on monitoring a second PDCCH monitoring occasion, the wireless device can receive a second DCI with a second DCI format scheduling multiple TBs via multiple PDSCHs / PUSCHs in multiple slots. The multiple slots can be consecutive or non-consecutive. Each of the multiple TBs can be associated with (or belong to) a different HARQ process. The wireless device can receive the multiple TBs via multiple PDSCHs in the multiple slots (if the DCI includes a downlink assignment indication) or transmit the multiple TBs via multiple PUSCHs in the multiple slots (if the DCI includes an uplink grant indication). Exemplary embodiments can reduce latency of system information or group common control information delivery when multiple PDSCH scheduling is supported. Exemplary embodiments can reduce power consumption of PDCCH monitoring for UE-specific TB scheduling when multiple PDSCH scheduling is supported.

[0268] FIG. 31 Exemplary embodiments of PDCCH monitoring configuration for multiple PDSCH scheduling in a BWP are shown. In an example, a wireless device can receive parameters of a search space (SS) on a BWP of a cell from a base station. The parameters can be transmitted in one or more RRC messages. The parameters can include a first plurality of PDCCH monitoring periodicities and a second plurality of PDCCH monitoring durations. The parameters can indicate whether the SS belongs to a common SS or a UE-specific SS. The parameters can indicate a third number of DCI formats. Each PDCCH monitoring periodicity of the first plurality of PDCCH monitoring periodicities can be associated with a corresponding DCI format of the third number of DCI formats. Each PDCCH monitoring duration of the second plurality of PDCCH monitoring durations can be associated with a corresponding DCI format of the third number of DCI formats. In an example, a DCI format of the third number of DCI formats can be associated with a corresponding PDCCH monitoring periodicity of the first plurality of PDCCH monitoring periodicities. A DCI format of the third number of DCI formats can be associated with a corresponding PDCCH monitoring duration of the second plurality of PDCCH monitoring durations.

[0269] In an example, the third number of DCI formats can include FIG. 29one or more first DCI formats. The one or more first DCI formats can include at least one of the following: DCI format 0 0, DCI format 0 1, DCI format 0 2, DCI format 1 0, DCI format 1 1, DCI format 1 2, DCI format 2 0, DCI format 2 1, DCI format 2 2, DCI format 2 3, DCI format 2 4, DCI format 2 5, DCI format 2 6, DCI format 3 0, and / or DCI format 3 1. The third number of DCI formats can include different than FIG. 29 one or more second DCI formats of the one or more first DCI formats. A second DCI format of the one or more second DCI formats can be designed for signaling delivery in a short slot length. A second DCI format of the one or more second DCI formats (e.g., DCI format 1 3) can be designed for scheduling multiple PDSCHs by a DCI. A second DCI format of the one or more second DCI formats (e.g., DCI format 0 3) can be designed for scheduling multiple PUSCHs by a DCI. A second DCI format of the one or more second DCI formats can be designed for scheduling a PDSCH and a PUSCH by a DCI.

[0270] In an example, a DCI format 1 0 (or DCI format 0 0) configured on the SS can be associated with a first PDCCH monitoring periodicity and / or a first PDCCH monitoring duration. A DCI format 1 1 (or DCI format 0 1) configured on the SS can be associated with a second PDCCH monitoring periodicity and / or a second PDCCH monitoring duration. A DCI format 1 2 (or DCI format 0 2) configured on the SS can be associated with a third PDCCH monitoring periodicity and / or a third PDCCH monitoring duration. A DCI format 2 0 (or DCI format 2 1, DCI format 2 2, etc.) can be associated with a fourth PDCCH monitoring periodicity and / or a fourth PDCCH monitoring duration. A DCI format 1 3 (or DCI format 1 3, or a new DCI format designed for multiple PDSCH / PUSCH scheduling) can be associated with a fifth PDCCH monitoring periodicity and / or a fifth PDCCH monitoring duration.

[0271] In an example, a first PDCCH monitoring periodicity for DCI format 1 0 (or DCI format 0 0) can be shorter than other PDCCH monitoring periodicities for other DCI formats. A first PDCCH monitoring duration for DCI format 1 0 (or DCI format 0 0) can be longer than other PDCCH monitoring durations for other DCI formats. Configuring a shorter monitoring periodicity and / or a longer monitoring duration for DCI format 1 0 / 0 0 can reduce latency for system information (or paging, PDCCH order, RAR message, etc.) delivery scheduled by compact DCI (e.g., DCI format 1 0 / 0 0).

[0272] In an example, a second PDCCH monitoring periodicity for DCI format 1 1 (or DCI format 0 1) can be longer than other PDCCH monitoring periodicities for other DCI formats. A second PDCCH monitoring duration for DCI format 1 1 (or DCI format 0 1) can be shorter than other PDCCH monitoring durations. If DCI format 1 1 / 0 1 is used to schedule multiple PDSCHs (or PUSCHs), configuring a longer monitoring periodicity and / or a shorter monitoring duration for DCI format 1 1 / 0 1 can reduce power consumption for PDCCH scheduling multiple PDSCHs / PUSCHs, for example, when the wireless device is being configured to operate at high frequencies with a larger SCS (e.g., 480 KHz, 960 KHz, etc.).

[0273] In an example, a base station can transmit a new DCI format (e.g., DCI format 1 3, different from DCI format 1 0, DCI format 1 1, and / or DCI format 1 2) for multi-PDSCH scheduling. For the new DCI format, the base station can configure a PDCCH monitoring periodicity that is longer than other PDCCH monitoring periodicities for other DCI formats. For the new DCI format, the base station can configure a PDCCH monitoring duration that is shorter than other PDCCH monitoring durations for other DCI formats.

[0274] In an example, based on parameters of an SS on a BWP of a cell, a wireless device can monitor PDCCHs for different DCI formats with different monitoring periodicities and / or different monitoring durations. As shown in FIG. 31 a wireless device can monitor a PDCCH for a first DCI format on a BWP with a first monitoring periodicity and / or a first monitoring duration. During monitoring the PDCCH, the wireless device can receive a first DCI with the first DCI format and a second DCI with the first DCI format. The wireless device can determine a PDCCH monitoring occasion according to the monitoring periodicity and / or the monitoring duration based on the example embodiments described above with respect to FIG. 28 FIG. 32 ​In an example embodiment, the wireless device can determine a PDCCH monitoring occasion according to a per-DCI format monitoring periodicity and / or a per-DCI format monitoring duration. In an example, a first DCI can schedule a TB via a PDSCH / PUSCH, where the TB can be a system information message, a paging message, a PDCCH order, a short message delivered by the first DCI, and / or the like. In response to receiving the first DCI, the wireless device can receive / transmit the TB based on the first DCI.

[0275] As shown in FIG. 31 , the wireless device can monitor for a PDCCH of a second DCI format on the BWP with a second monitoring periodicity and / or a second monitoring duration. During monitoring for the PDCCH, the wireless device can receive a third DCI with the second DCI format and a fourth DCI with the second DCI format. The wireless device can determine a PDCCH monitoring occasion according to the monitoring periodicity and / or the monitoring duration based on the example embodiments described above with respect to FIG. 28 , in an example, the third DCI can schedule multiple TBs via multiple PDSCHs, where each of the multiple TBs is associated with a corresponding HARQ process. The multiple PDSCHs can be in consecutive slots. Each of the multiple PDSCHs can be associated with one or more symbols in a corresponding slot associated with the PDSCH. In response to receiving the third DCI, the wireless device can receive the multiple TBs in the consecutive slots based on the third DCI.

[0276] In an example, the fourth DCI can schedule multiple TBs via multiple PUSCHs. Each of the multiple TBs can be associated with a corresponding HARQ process. The multiple PUSCHs can be in consecutive slots. Each of the multiple PUSCHs can be associated with one or more symbols in a corresponding slot associated with the PUSCH. In response to receiving the fourth DCI, the wireless device can transmit the multiple TBs in the consecutive slots based on the fourth DCI.

[0277] Based on FIG. 31In example embodiments, a base station configures a DCI format specific PDCCH monitoring periodicity and / or PDCCH monitoring duration for one or more DCI formats associated with a SS on a BWP. In an example, different DCI formats configured on a SS can be associated with different or separate PDCCH monitoring periodicities and / or PDCCH monitoring durations. Based on the configuration, a wireless device can adapt PDCCH monitoring for different DCI formats according to different or separate PDCCH monitoring periodicities and / or different PDCCH monitoring durations. Example embodiments can reduce latency of system information or group common control information delivery when multi-PDSCH scheduling is supported. Example embodiments can reduce power consumption of PDCCH monitoring for UE specific TB scheduling when multi-PDSCH scheduling is supported.

[0278] FIG. 32 Example embodiments are shown that configure a PDCCH monitoring periodicity / duration per DCI format. As shown in FIG. 32 , a wireless device can be configured with a first periodicity and a first duration for monitoring PDCCH according to a first DCI format on a SS of a BWP of a cell. The wireless device can be configured with a second periodicity and a second duration for monitoring PDCCH according to a second DCI format on the SS. The wireless device can be configured with a third periodicity and a third duration for monitoring PDCCH according to a third DCI format on the SS. The configuration of multiple periodicities and / or multiple durations can be implemented based on example embodiments described above with respect to FIG. 31 .

[0279] As shown in FIG. 32 , based on the first periodicity and the first duration, the wireless device can monitor PDCCH for the first DCI format on a first number (e.g., 3 out of FIG. 32 ) of slots determined by the first duration in a second number (e.g., 5 out of FIG. 32 ) of slots determined by the first periodicity. After the first number of slots, the wireless device can skip PDCCH monitoring for the first DCI format in the remaining slots of the second number of slots.

[0280] As shown in FIG. 32 , based on the second periodicity and the second duration, the wireless device can monitor PDCCH for the second DCI format on a first number (e.g., 2 out of FIG. 32 ) of slots determined by the second duration in a second number (e.g., 4 out of FIG. 32 ) of slots determined by the second periodicity. After the first number of slots, the wireless device can skip PDCCH monitoring for the second DCI format in the remaining slots of the second number of slots.

[0281] As shown in FIG. 31 , based on the third periodicity and the third duration, the wireless device can monitor the PDCCH for the third DCI format in a first number (e.g., 1 out of 3) of slots determined by the third duration, after the first number of slots, the wireless device can skip monitoring the PDCCH for the third DCI format in the remaining slots in the second number of slots. FIG. 32 FIG. 31 Based on the example embodiments of FIG. 32 and / or FIG. 31 , the wireless device can determine the PDCCH monitoring occasions for different DCI formats according to different / separate DCI format specific PDCCH monitoring periodicity and / or different / separate DCI format specific PDCCH monitoring duration. The example embodiments can reduce latency of system information or group common control information delivery when multiple PDSCH scheduling is supported. The example embodiments can reduce power consumption of PDCCH monitoring for UE specific TB scheduling when multiple PDSCH scheduling is supported.

[0282] FIG. 32 and / or FIG. 31 may be extended for improving the signaling overhead of PDCCH configuration in RRC messages. In an example, different DCI formats configured on an SS can be associated with the same PDCCH monitoring periodicity and different / separate PDCCH monitoring duration. According to FIG. 32 and / or FIG. 33 , the wireless device can monitor the PDCCH for different DCI formats based on the same PDCCH periodicity and different / separate PDCCH monitoring duration. In an example, different DCI formats configured for an SS can be associated with the same PDCCH monitoring duration and different / separate PDCCH monitoring periodicity. According to FIG. 26 and / or FIG. 27 , the wireless device can monitor the PDCCH for different DCI formats based on the same PDCCH duration and different / separate PDCCH monitoring periodicity.

[0283] In an example, the PDCCH monitoring periodicity and / or duration configured per DCI format can increase the signaling overhead of RRC messages. To obtain backward compatibility, it can be beneficial to keep the PDCCH configuration parameters unchanged (e.g., in some cases). The example embodiments can include adjusting / adapting the PDCCH monitoring based on PDSCH scheduling configuration (e.g., single PDSCH scheduling or multiple PDSCH scheduling, etc.).

[0284] ​​FIG. 34 Exemplary embodiments of PDCCH monitoring for multiple PDSCH scheduling are shown. In an example, a wireless device can receive configuration parameters of a BWP of a cell from a base station. The configuration parameters can include first parameters of a search space (SS) set on the BWP of the cell. The first parameters can be transmitted in one or more RRC messages. The first parameters can include a PDCCH monitoring periodicity and a PDCCH monitoring duration. The first parameters can indicate multiple DCI formats configured on the SS (DCI format 1_0 / 1_1 / 1_2 for multiple PDSCH scheduling, DCI format 1_3, etc.). The configuration parameters can be implemented based on the exemplary embodiments described above with respect to startSymbolAndLength and / or startSymbolAndLength the exemplary embodiments described above.

[0285] In an example, the configuration parameters can include second parameters of PDSCHs on the BWP. The second parameters can include at least one of the following: a data scrambling identity of the PDSCHs, one or more DMRS mapping parameters, one or more TCI states, a resource allocation type indication, one or more PDSCH time domain allocation lists, a PDSCH aggregation factor, one or more rate matching patterns, an MCS table indicator, a maximum number of code words scheduled by the DCI, a PRB bundling parameter, an RS configuration parameter, etc.

[0286] In an example, the one or more PDSCH time domain allocation lists can include a first PDSCH time domain allocation list associated with single PDSCH scheduling (e.g., including a first number of K0, S, and L combinations). The first number can be 4, 8, 16, 32, or 64. The first PDSCH time domain allocation list associated with single PDSCH scheduling can be implemented based on the exemplary embodiments shown as startSymbolAndLength The first PDSCH time domain allocation list can be associated with a first number of DCI formats (e.g., DCI format 1_0, DCI format 1_2).

[0287] In an example, the one or more PDSCH time domain allocation lists can include a second PDSCH time domain allocation list associated with multiple PDSCH scheduling. The second PDSCH time domain allocation list can have a plurality (e.g., 4, 8, 16, 32, or 64) of entries. Each entry can include a K0 value and a plurality of FIG. 33 (S and L) indications. The plurality of FIG. 35 indications can correspond to a particular PDSCH. The total number of the plurality of FIG. 28 indications (e.g., as FIG. 33The indicated N) can indicate how many PDSCHs the DCI can schedule for multiple (consecutive) slots. In an example, the total number can be 2, 4, 8, 16, or any number configured by the base station. The second PDSCH time domain allocation list associated with the multi-PDSCH scheduling can be based on the example implementation as FIG. 33 illustrated. The second PDSCH time domain allocation list can be associated with a second number of DCI formats (e.g., DCI format 1_1, DCI format 1_3 for multi-PDSCH scheduling). The different DCI formats associated with different PDSCH time domain allocation lists can allow the base station to schedule system information or group common control information with single PDSCH scheduling through compact DCI formats (e.g., DCI format 1_0 / 0_0). The different DCI formats associated with different PDSCH time domain allocation lists can allow the base station to schedule UE-specific data with multi-PDSCH scheduling through full size DCI formats (e.g., DCI format 1_1 / 1_2 / 1_3, etc.). The example implementation can improve latency of system information delivery and / or reduce power consumption of PDCCH monitoring.

[0288] In an example, based on the SS-based PDCCH monitoring periodicity and PDCCH monitoring duration, the wireless device can monitor the PDCCH on the SS for receiving the DCI, for example, by implementing the example implementation described above with respect to startSymbolAndLength

[0289] As FIG. 35 illustrated, the wireless device can receive a first DCI during monitoring the PDCCH on the SS of the BWP. In response to receiving the first DCI with the first DCI format including a TDRA field indicating an entry of a first PDSCH time domain allocation list, the wireless device can receive a first TB via a PDSCH indicated by the first DCI. The TDRA field of the first DCI indicates the entry of the first PDSCH time domain allocation list based on the first DCI with the first DCI format. The wireless device can determine time domain resources of the PDSCH based on the TDRA field of the DCI. The wireless device can maintain monitoring the PDCCH according to the PDCCH monitoring periodicity and PDCCH monitoring duration of the SS.

[0290] As FIG. 33 ​As shown, a wireless device can receive a second DCI during monitoring of a PDCCH on a BWP's SS. In response to receiving a second DCI with a second DCI format including a TDRA field indicating entries in a second PDSCH time-domain allocation list, the wireless device can determine that the second DCI schedules multiple PDSCHs. The TDRA field of the second DCI indicates entries in a second PDSCH time-domain allocation list based on the second DCI with the second DCI format. Based on the TDRA field of the second DCI, the wireless device can determine the time-domain resources of multiple PDSCHs in different time slots for multiple TBs. The wireless device can receive multiple TBs based on the second DCI. In the example, in response to receiving a second DCI scheduling multiple PDSCHs, the wireless device can skip monitoring PDCCHs with the second DCI format in multiple time slots by ignoring the period and duration of the SS. The wireless device can determine the multiple time slots in which it can skip monitoring PDCCHs with the second DCI format as N-1 time slots, where N is the total number of PDSCHs scheduled by the second DCI, or the number of entries in the second PDSCH time-domain allocation list. FIG. 33 The total number indicated (e.g., such as) FIG. 33 (As shown).

[0291] based on FIG. 34 In an exemplary implementation, in response to a wireless device receiving a DCI scheduling multiple PDSCHs in consecutive time slots, the wireless device can skip PDCCH monitoring within multiple time slots by ignoring the PDCCH monitoring period and the PDCCH monitoring duration. If the prior art is implemented, the wireless device can maintain monitoring of PDCCHs in multiple consecutive time slots based on the PDCCH monitoring duration (e.g., if the PDCCH monitoring duration is configured for two or more time slots), even if the wireless device receives a DCI scheduling multiple PDSCHs. Based on the exemplary implementation, when receiving a DCI scheduling multiple PDSCHs, the wireless device can ignore the PDCCH monitoring period and / or the PDCCH monitoring duration by skipping monitoring of PDCCHs in a certain number of time slots after receiving the DCI, where this number can be determined based on the total number of PDSCHs scheduled by the DCI.

[0292] based on FIG. 34In an exemplary implementation, without changing the configuration parameters of the SS (e.g., PDCCH monitoring period and / or PDCCH monitoring duration), the wireless device can adapt PDCCH monitoring to be based on whether a single PDSCH or multiple PDSCHs are scheduled according to the DCI. In the example, the wireless device can monitor a PDCCH with a first DCI (e.g., having a first DCI format) that schedules a single PDSCH, based on the configured PDCCH monitoring period and / or the configured PDCCH monitoring duration. In the example, based on receiving a second DCI that schedules multiple PDSCHs (e.g., having a second DCI format), the wireless device can ignore the configured PDCCH monitoring period and / or the configured PDCCH monitoring duration for multiple time slots. Ignoring the configured PDCCH monitoring period and / or the configured PDCCH monitoring duration for multiple time slots can include skipping monitoring of PDCCHs with the second DCI format for multiple time slots, even if the SS's PDCCH monitoring period and / or PDCCH monitoring duration indicates that the wireless device is monitoring PDCCHs on the SS. The exemplary implementation maintains backward compatibility by keeping the SS's configuration parameters unchanged. By keeping the SS configuration parameters unchanged, the exemplary implementation allows the wireless device to adapt PDCCH monitoring based on whether DCI schedules a single PDSCH or multiple PDSCHs in multiple time slots. The exemplary implementation can reduce the power consumption of the wireless device and / or the delivery latency of system information / paging / group common control information / PDCCH commands, etc.

[0293] In the example, FIG. 35 This can be extended to further reduce the power consumption of PDCCH monitoring. The wireless device can determine the (actual) PDCCH monitoring period and / or duration for receiving PDCCH monitoring of a DCI that schedules multiple PDSCHs, based on a configured PDCCH monitoring period / duration and the total number of PDSCHs that the DCI can schedule. Unlike prior art that determines PDCCH monitoring timing based on the SS-based PDCCH monitoring period / duration, exemplary embodiments include determining PDCCH monitoring timing not only based on the SS-based PDCCH monitoring period / duration but also based on the total number of PDSCHs that the DCI can schedule. Exemplary embodiments can reduce the power consumption of the wireless device, for example, without increasing the latency for control signaling delivery.

[0294] In an example, if a configured PDCCH monitoring periodicity of an SS is x slots and a total number of PDSCHs that can be scheduled by a DCI is y. The wireless device can determine an actual PDCCH monitoring periodicity for receiving the DCI as a least common multiple of x and y (e.g., 12 if x = 3 and y = 4). The wireless device can determine the actual PDCCH monitoring periodicity as a maximum of x and y (e.g., 4 if x = 3 and y = 4). The wireless device can determine the actual PDCCH monitoring periodicity as a minimum of x and y (e.g., 3 if x = 3 and y = 4).

[0295] In an example, if a configured PDCCH monitoring duration of an SS is m slots and a total number of PDSCHs that can be scheduled by a DCI is y. The wireless device can determine an actual PDCCH monitoring duration for receiving the DCI as a number equal to floor(m / y) (e.g., 1 if m = 3 and y = 4, or 2 if m = 8 and y = 4, and so on).

[0296] FIG. 31 An example embodiment of a single PDSCH scheduling scheme is shown. In an example, a base station can transmit, to a wireless device, an RRC message including configuration parameters of a PDSCH on a BWP of a cell. The configuration parameters can include a list of PDSCH resource allocation configurations for single PDSCH scheduling on the BWP. The list can include a plurality of entries indicating PDSCH time domain resource allocation in a slot. Each entry of the list can include a K0 value indicating a slot offset of a second slot in which the PDSCH is transmitted relative to a first slot in which a DCI corresponding to the PDSCH is transmitted. Each entry of the list can further include one or more starting symbol and length indications indicating a starting symbol (S) of a slot of the PDSCH and a length (L) of a plurality of symbols of the PDSCH in the slot. A total number of entries in the list can be 4, 8, 16, 32, 64, and so on. In an example, a TDRA field of the DCI can indicate an entry of the list of PDSCH time domain resource indications. If the total number of entries is 4, the TDRA field can have 2 bits, if the total number is 8, 3 bits, if the total number is 16, 4 bits, and so on. As FIG. 32As shown, DCI1 can include a TDRA field indicating a second entry of the list. The second entry of the list can indicate K0=2, S=2, and L=9. In response to receiving DCI1 with the TDRA field in slot x, the wireless device can determine that the PDSCH scheduled by DCI1 is in slot x+2 (e.g., K0=2), the second symbol of the slot as the starting symbol of the PDSCH (e.g., S=2), and the total number of symbols of the PDSCH is 9 (e.g., L=9). Based on the determined PDSCH resources in slot x+2, the wireless device can receive the TB via the PDSCH resources.

[0297] FIG. 33 An example of a multi-PDSCH scheduling scheme is shown. In the example, a base station can transmit, to a wireless device, an RRC message including configuration parameters of a PDSCH on a BWP of a cell. The configuration parameters can include a list of PDSCH resource allocation configurations for multi-PDSCH scheduling on the BWP. The list can include a first number of entries indicating PDSCH time domain resource allocation in a second number of (consecutive) slots. The total number of entries in the list (the first number) can be 4, 8, 16, 32, 64, etc. Each entry of the list can include a K0 value indicating a slot offset of a starting slot of a starting PDSCH of the multiple PDSCHs relative to a first slot of a DCI scheduling the multiple PDSCHs. The wireless device can receive the DCI based on PDCCH monitoring by implementing the example embodiments described above with respect to FIG. 35 、 FIG. 35 and / or FIG. 35 Each entry of the list can further include a second number of starting symbol and length indications, each associated with a corresponding PDSCH of the multiple PDSCHs. The second number can indicate how many PDSCHs the DCI can schedule. The second number can be configured in the RRC message (or predefined as a fixed value) for the PDSCH configuration. Each starting symbol and length indication can indicate a starting symbol (S) of a slot of the corresponding PDSCH and a length (L) of a number of symbols of the PDSCH in the slot. As FIG. 36 shown, the first starting symbol and length indication of entry 1 can indicate S=1 and L=9 for PDSCH 1 in the starting slot. The second starting symbol and length indication of entry 1 can indicate S=1 and L=10 for PDSCH 2 in the next slot after the starting slot. The third starting symbol and length indication of entry 1 can indicate S=1 and L=9 for PDSCH 3 in the slot after the next slot, and so on.

[0298] In an example, the DCI scheduling the multiple PDSCHs (e.g., FIG. 33The TDRA field of the DCI 1) can indicate an entry of a PDSCH time domain resource indication list. If the total number of entries is 4, the TDRA field can have 2 bits, if the total number is 8, 3 bits, if the total number is 16, 4 bits, and so on. As shown in FIG. 36 FIG. 6, the DCI 1 can include a TDRA field indicating a second entry of the list. The second entry of the list can indicate K0=1, S=2, and L=9 for PDSCH 1, S=2 and L=10 for PDSCH 2, S=2 and L=9 for PDSCH 3, and so on. In response to receiving the DCI 1 (e.g., in slot x) with the TDRA field, the wireless device can determine that the slot with the plurality of PDSCHs scheduled by the DCI 1 includes slot x+1, x+2, x+3, and so on (e.g., K0=1). In an example, based on K0=1, a first PDSCH of the plurality of PDSCHs can be in slot x+1. The first PDSCH can have a second symbol (e.g., S=2) of slot x+1 as a starting symbol of the first PDSCH, and a total number of symbols of the first PDSCH is 9 (e.g., L=9). A second PDSCH of the plurality of PDSCHs can be in slot x+2, a second symbol (e.g., S=2) of slot x+2 as a starting symbol of the second PDSCH, and a total number of symbols of the second PDSCH is 10 (e.g., L=10). A third PDSCH of the plurality of PDSCHs can be in slot x+3, a second symbol (e.g., S=2) of slot x+3 as a starting symbol of the third PDSCH, and a total number of symbols of the third PDSCH is 9 (e.g., L=9).

[0299] Based on the determined plurality of PDSCHs, the wireless device can receive a plurality of TBs via the plurality of PDSCHs, each TB received in a corresponding PDSCH of the plurality of PDSCHs. In an example, the wireless device can receive a first TB in PDSCH 1 in slot x+1, a second TB in PDSCH 2 in slot x+2, a third TB in PDSCH 3 in slot x+3, and so on.

[0300] FIG. 28 An example embodiment of PDCCH monitoring for multi-PDSCH scheduling is shown. In an example, a wireless device can receive, from a base station, an RRC message including configuration parameters of a search space (SS) in a BWP of a cell. The configuration parameters can be implemented based on the example embodiments described above with respect to FIG. 36 FIG. 6.

[0301] As shown in FIG. 36 FIG. 6, the wireless device can monitor a PDCCH based on a PDCCH monitoring periodicity / duration associated with the SS. The wireless device can monitor the PDCCH according to the PDCCH monitoring periodicity / duration based on the example embodiments described above with respect to FIG. 36The described exemplary implementation uses a period / duration to monitor the PDCCH. The wireless device can receive multiple scheduled PDSCHs in time slot 0 (e.g., PDSCH1 in time slot 1, PDSCH2 in time slot 2, PDSCH3 in time slot 3, and PDSCH4 in time slot 4, etc.). ​ The first DCI (e.g., DCI1) is shown. In response to receiving the first DCI, the wireless device can receive multiple TBs via several PDSCHs (e.g., the first TB in PDSCH1, the second TB in PDSCH2, the third TB in PDSCH3, and the fourth TB in PDSCH4). In response to receiving the first DCI, the wireless device can skip multiple TBs after slot 0 (e.g., DCI1, DCI2, DCI3, and DCI4) by ignoring the PDCCH monitoring period and PDCCH monitoring duration of the SS and based on the first DCI that schedules multiple PDSCHs. ​ The number of time slots that a wireless device can skip for PDCCH monitoring can be determined based on the total number of PDSCHs. In the example, if the total number of PDSCHs scheduled by the first DCI is 4, the wireless device can skip PDCCH monitoring for 1, 2, or 3 time slots (e.g., time slot 1, time slot 2, and / or time slot 3) after time slot 0, even if the PDCCH monitoring period and / or PDCCH monitoring duration of the SS instructs the wireless device to monitor time slots 1, 2, and / or time slot 3 (e.g., if the PDCCH monitoring duration is configured for 3 or more time slots). By ignoring PDCCH configuration parameters (e.g., PDCCH monitoring period / duration) to skip PDCCH monitoring within multiple time slots after receiving a DCI that schedules multiple PDSCHs, the power consumption of the wireless device can be improved.

[0302] Similarly, such as ​As shown, after skipping 3 slots for PDCCH monitoring, the wireless device can resume (or start) monitoring PDCCH in slot 4. The wireless device can resume (or start) monitoring PDCCH in slot 4 based on receiving a first DCI that schedules 4 PDSCHs in 4 consecutive slots. During monitoring PDCCH in slot 4, the wireless device can receive a second DCI that schedules multiple PDSCHs (e.g., PDSCH 5 in slot 5, PDSCH 6 in slot 6, PDSCH 7 in slot 7, and PDSCH 8 in slot 8). The wireless device can receive multiple TBs via the multiple PDSCHs (e.g., receive TB 5 via PDSCH 5, receive TB 6 via PDSCH 6, receive TB 7 via PDSCH 7, and receive TB 8 via PDSCH 8, etc.). In response to receiving the second DCI in slot 4, the wireless device skips PDCCH monitoring in the next 3 slots (e.g., slot 5, slot 6, and slot 7) after slot 4, even if the PDCCH monitoring periodicity and / or PDCCH monitoring duration of the SS indicates that the wireless device monitors slot 5, slot 6, and / or slot 7 (e.g., if the PDCCH monitoring duration is configured to be 3 or more slots).

[0303] In an example, if multiple PDSCH scheduling is configured, it can be difficult for the wireless device to determine whether it can skip PDCCH monitoring. If the received DCI schedules multiple PDSCHs in consecutive slots, the wireless device can skip PDCCH monitoring in some slots. However, according to the PDCCH monitoring duration of the PDCCH, if the PDCCH monitoring duration of the PDCCH is configured to be more than 1 slot, the wireless device can need to monitor the PDCCH in multiple slots. The existing techniques can increase the power consumption of the wireless device. The existing techniques can misalign the PDCCH monitoring behavior between the base station and the wireless device. The example embodiments can improve the power consumption of the wireless device by ignoring the PDCCH monitoring periodicity / duration configured by the RRC message, the wireless device can skip PDCCH monitoring in multiple slots when the wireless device receives a DCI via the PDCCH that schedules multiple PDSCHs.

[0304] In an example embodiment, the wireless device monitors, based on a first periodicity and a first duration, a first PDCCH of a first DCI format on a search space of a BWP. During monitoring of the first PDCCH, the wireless device receives, via a PDSCH in a slot, a first DCI of the first DCI format indicating a first TB. The wireless device monitors, based on a second periodicity and a second duration, a second PDCCH of a second DCI format on the search space of the BWP. The wireless device receives, during monitoring of the second PDCCH, via a plurality of PDSCHs in a plurality of slots, a second DCI of the second DCI format indicating a plurality of TBs, each TB being associated with a corresponding PDSCH in a corresponding slot.

[0305] In an example embodiment, the wireless device receives, via a RRC message, a parameter of a search space on a bandwidth part, where the parameter indicates that a first DCI format is associated with a first periodicity and a first duration, and a second DCI format is associated with a second periodicity and a second duration.

[0306] In an example embodiment, the first DCI format comprises a DCI format 1 0. The second DCI format comprises a DCI format 1 1.

[0307] In an example embodiment, the cell comprises a plurality of BWPs, including the BWP.

[0308] In an example embodiment, monitoring the first PDCCH of the first DCI format comprises attempting to decode the first DCI of the first DCI format via resource elements associated with the search space on a first number of slots of a second number of slots, where the first number is determined based on the first duration and / or the second number is determined based on the first periodicity. The wireless device skips monitoring the first PDCCH of the first DCI format in one or more remaining slots of the second number of slots other than the first number of slots.

[0309] In an example embodiment, monitoring the second PDCCH of the second DCI format comprises attempting to decode the second DCI of the second DCI format via resource elements associated with the search space on a first number of slots of a second number of slots, where the first number is determined based on the second duration and / or the second number is determined based on the second periodicity. The wireless device skips monitoring the second PDCCH of the second DCI format in one or more remaining slots of the second number of slots other than the first number of slots.

[0310] In an example embodiment, the wireless device receives one or more PDSCH configuration parameters of a BWP, where the one or more PDSCH configuration parameters indicate a first PDSCH resource allocation configuration list associated with a first DCI format and a second PDSCH resource allocation configuration list associated with a second DCI format.

[0311] In an example embodiment, each entry of the first PDSCH resource allocation configuration list includes at least one of a slot offset of a second slot of a first PDSCH relative to a first slot on which the wireless device receives a first DCI, a starting symbol of the first PDSCH in the second slot, and a number of symbols of the first PDSCH in the second slot and counting from the starting symbol. The first DCI format includes a time domain resource allocation (TDRA) field indicating an entry of the first PDSCH resource allocation configuration list indicating the slot offset of the second slot of the first PDSCH relative to the first slot on which the wireless device receives the first DCI, the starting symbol of the first PDSCH in the second slot, and the number of symbols of the first PDSCH in the second slot and counting from the starting symbol. The wireless device receives a first TB via the PDSCH based on the slot offset, the starting symbol, and the number of symbols.

[0312] In an example embodiment, each entry of the second PDSCH resource allocation configuration list includes at least one of a slot offset of a second slot of a starting PDSCH of a plurality of PDSCHs relative to a first slot on which the wireless device receives a second DCI, a plurality of starting symbol and length indications, where each starting symbol and length indication of the plurality of starting symbol and length indications associated with a corresponding PDSCH of the plurality of PDSCHs indicates a starting symbol of the corresponding PDSCH in a slot associated with the corresponding PDSCH and a number of symbols of the corresponding PDSCH in the slot and counting from the starting symbol. The second DCI format includes a time domain resource allocation (TDRA) field indicating an entry of the second PDSCH resource allocation configuration list indicating the slot offset of the second slot of the starting PDSCH relative to the first slot on which the wireless device receives the second DCI and the plurality of starting symbol and length indications of the plurality of PDSCHs. The wireless device receives a plurality of TBs via the plurality of PDSCHs based on the slot offset and the plurality of starting symbol and length indications of the plurality of PDSCHs.

[0313] In an example embodiment, the search space is a wireless device specific search space type. The search space is a cell common search space type.

[0314] In an example embodiment, the first periodicity is shorter than the second periodicity. The first duration is greater than the second duration.

[0315] In an example embodiment, a wireless device receives one or more RRC messages including parameters of a search space on a BWP, where the parameters include: a periodicity of PDCCH monitoring on the search space, a duration of PDCCH monitoring on the search space, and a plurality of DCI formats. The wireless device monitors PDCCH of the plurality of DCI formats based on the periodicity and the duration. The wireless device receives, via a PDSCH, a first DCI having a first DCI format of the plurality of DCI formats indicating a first TB. The wireless device keeps monitoring PDCCH of the first DCI format according to the periodicity and the duration. The wireless device receives, via a plurality of PDSCHs, a second DCI having a second DCI format of the plurality of DCI formats indicating a plurality of TBs, each TB associated with a corresponding PDSCH. The wireless device skips monitoring PDCCH of the second DCI format for a number of slots by ignoring the periodicity and the duration, where the number is determined based on a total number of the plurality of PDSCHs.

[0316] In an example embodiment, a wireless device receives one or more RRC messages including parameters of a search space on a BWP, where the parameters include: a periodicity of PDCCH monitoring on the search space, a duration of PDCCH monitoring on the search space, and a plurality of DCI formats. The wireless device monitors PDCCH of the plurality of DCI formats based on the periodicity and the duration. The wireless device receives, via a plurality of PDSCHs in a plurality of slots, DCI having a first DCI format of the plurality of DCI formats indicating a plurality of TBs, each TB associated with a corresponding PDSCH. The wireless device skips monitoring PDCCH of the first DCI format for a number of slots by ignoring the periodicity and the duration, where the number is determined based on a total number of the plurality of PDSCHs.

Claims

1. A method comprising: receiving, by a wireless device, a plurality of radio resource control (RRC) messages comprising a plurality of configuration parameters, the plurality of configuration parameters comprising: a first physical downlink shared channel (PDSCH) time domain allocation list associated with a first downlink control information (DCI) format for scheduling PDSCH in a slot; and a second PDSCH time domain allocation list associated with a second DCI format for scheduling a plurality of PDSCHs in a plurality of slots; receiving a first DCI having the second DCI format, the second DCI format indicating a first entry of the second PDSCH time domain allocation list; receiving a plurality of transport blocks (TBs) in a plurality of first slots via a plurality of PDSCH resources determined based on the first entry.

2. The method of claim 1, wherein the second DCI format is DCI format 1 1.

3. The method of any one of claims 1-2, wherein each of the plurality of TBs is associated with a respective hybrid automatic repeat request process number, the hybrid automatic repeat request process number indicating one of a plurality of hybrid automatic repeat request processes.

4. The method of any one of claims 1 to 3, further comprising: monitoring a first search space for receiving the first DCI having the second DCI format, wherein a first monitoring periodicity of the first search space is greater than a second monitoring periodicity of a second search space, the second search space for receiving a second DCI having the first DCI format.

5. The method of claim 4, further comprising: based on monitoring of the second search space, receiving the second DCI having the first DCI format, the first DCI format indicating a second entry of the first PDSCH time domain allocation list; and receiving a second TB in a second slot via a second PDSCH resource determined based on the second entry, wherein the second TB is associated with a second hybrid automatic repeat request process.

6. The method of any one of claims 1-5, wherein receiving the plurality of TBs in the first slots comprises receiving each of the plurality of TBs in a respective one of the first slots.

7. The method of any one of claims 1-6, wherein the first entry of the second PDSCH time domain allocation list indicates a plurality of PDSCH resources in the first slots, and wherein each of the plurality of PDSCH resources in a respective one of the first slots is associated with: a slot offset indication; and a start symbol and length indication.

8. A method comprising: sending, by a base station to a wireless device, a plurality of radio resource control (RRC) messages comprising a plurality of configuration parameters, the plurality of configuration parameters comprising: a first physical downlink shared channel (PDSCH) time domain allocation list associated with a first downlink control information (DCI) format for scheduling PDSCH in a slot; and a second PDSCH time domain allocation list associated with a second DCI format for scheduling a plurality of PDSCHs in a plurality of slots; a first physical downlink shared channel (PDSCH) time domain allocation list associated with a first downlink control information (DCI) format used to schedule a PDSCH in a slot; and a second PDSCH time domain allocation list associated with a second DCI format used to schedule multiple PDSCHs in multiple slots; transmit a first DCI having the second DCI format, the second DCI format indicating a first entry of the second PDSCH time domain allocation list; transmit multiple transport blocks (TBs) via multiple PDSCH resources determined based on the first entry in multiple first slots.

9. The method of claim 8, wherein the second DCI format is DCI format 1 1.

10. The method of any one of claims 8-9, wherein each of the multiple TBs is associated with a respective hybrid automatic repeat request process number, the hybrid automatic repeat request process number indicating one of multiple hybrid automatic repeat request processes.

11. The method of any one of claims 8-10, wherein the multiple configuration parameters cause the wireless device to monitoring a first search space for receiving the first DCI having the second DCI format, wherein, a first monitoring periodicity of the first search space is greater than a second monitoring periodicity of a second search space, the second search space used to receive a second DCI having the first DCI format.

12. The method of claim 11, the method further comprising: transmit the second DCI having the first DCI format, the first DCI format indicating a second entry of the first PDSCH time domain allocation list; and receive a second TB via a second PDSCH resource determined based on the second entry in a second slot, wherein the second TB is associated with a second hybrid automatic repeat request process.

13. The method of any one of claims 8-12, wherein receiving the multiple TBs in the first slots comprises receiving each of the multiple TBs in a respective one of the first slots.

14. A wireless device, the wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method of any one of claims 1-13.

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

Images