Low power operation in carrier aggregation

Abstract

The wireless device receives a first radio resource control (RRC) message from the base station indicating a request for radio access capability of the wireless device. A second RRC message is transmitted to the base station and includes information of the radio access capability for power saving operation. The information includes a first parameter indicating whether the wireless device supports skipping of physical downlink control channel (PDCCH) monitoring on the active bandwidth portion and a second parameter indicating whether the wireless device supports switching of PDCCH monitoring between search space groups of the active bandwidth portion. The wireless device receives a third RRC message from the base station including configuration parameters based on the first parameter and the second parameter for power saving operation.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 167,305, filed March 29, 2021, which is incorporated herein by reference in its entirety. Summary of the Invention [Means for solving the problem]

[0002] In this disclosure, various embodiments are presented as examples of how the disclosed technology may be implemented and / or how the disclosed technology may be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and details may be made without departing from the scope. Indeed, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the exemplary embodiments. The embodiments of the present disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create further embodiments within the scope of the present disclosure. The figures that highlight features and advantages are shown by way of example only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, the actions listed in any flowchart may be rearranged in some embodiments or used only optionally. [Brief description of the drawings]

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

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

[0005] [Diagram 2] 2A and 2B show the New Radio (NR) user plane and control plane protocol stacks, respectively.

[0006] [Diagram 3] FIG. 3 illustrates one embodiment of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

[0007] [Figure 4A] FIG. 4A shows an example downlink data flow through the NR user plane protocol stack of FIG. 2A.

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

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

[0010] [Figure 6] FIG. 6 is an exemplary diagram illustrating RRC state transitions of a UE.

[0011] [Figure 7] FIG. 7 shows an example structure of an NR frame in which OFDM symbols are grouped.

[0012] [Figure 8] FIG. 8 shows an example configuration of slots in the time and frequency domain of an NR carrier.

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

[0014] [Figure 10A] FIG. 10A shows three carrier aggregation configurations with two component carriers.

[0015] [Figure 10B] FIG. 10B illustrates one example of how aggregation cells can be organized into one or more PUCCH groups.

[0016] [Figure 11A] FIG. 11A illustrates one embodiment of an SS / PBCH block structure and location.

[0017] [Figure 11B] FIG. 11B illustrates an example of a CSI-RS mapped to the time and frequency domain.

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

[0019] [Figure 13] 13A, 13B, and 13C show a four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure, respectively.

[0020] [Figure 14A] FIG. 14A shows an embodiment of a CORESET configuration for bandwidth portions.

[0021] [Figure 14B] FIG. 14B illustrates one embodiment of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing.

[0022] [Figure 15] FIG. 15 illustrates an embodiment of a wireless device communicating with a base station.

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

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

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

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

[0027] [Figure 19] FIG. 19 shows an example of multiple LCIDs for the downlink.

[0028] [Figure 20] FIG. 20 shows an example of multiple LCIDs for the uplink.

[0029] [Figure 21] 21A and 21B show an example of a SCell Activation / Deactivation MAC CE format.

[0030] [Figure 22] 22A and 22B show examples of DRX configurations.

[0031] [Diagram 23] FIG. 23 illustrates an example of BWP activation / deactivation on a SCell, according to some embodiments.

[0032] [Figure 24] FIG. 24 shows examples of various DCI formats.

[0033] [Diagram 25]FIG. 25 shows an example of a cell dormant configuration.

[0034] [Figure 26] FIG. 26 illustrates an example of cell / cell group dormancy transition according to some embodiments.

[0035] [Figure 27] FIG. 27 illustrates an example of an RRC configuration of a control resource set.

[0036] [Figure 28] FIG. 28 shows an example of an RRC configuration of the search space.

[0037] [Figure 29] FIG. 29 shows an example of a DCI format for a search space group switching operation, according to some embodiments.

[0038] [Diagram 30] 30A and 30B show an example of a search space group switching operation according to some embodiments.

[0039] [Diagram 31] FIG. 31 illustrates an example of power saving based on PDCCH skipping, according to some embodiments.

[0040] [Diagram 32] FIG. 32 shows an example of a power saving operation indication, according to some embodiments.

[0041] [Diagram 33] FIG. 33 illustrates an example of cell grouping for power saving operation, according to some embodiments.

[0042] [Diagram 34] FIG. 34 illustrates an example of a cell group based power saving indication, according to some embodiments.

[0043] [Diagram 35] FIG. 35 illustrates an example of a power saving indication for multiple cell groups, according to some embodiments.

[0044] [Diagram 36] FIG. 36 illustrates an example of cell grouping for power saving operation, according to some embodiments.

[0045] [Figure 37] FIG. 37 illustrates an example of a power saving indication for multiple cell groups, according to some embodiments.

[0046] [Figure 38] FIG. 38 illustrates an example of power saving operation of a cell, according to some embodiments.

[0047] [Figure 39] FIG. 39 illustrates an example of power saving operation of a cell, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0049] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Wireless devices may have some specific capabilities depending on the category and / or capabilities of the wireless devices. When the disclosure refers to a base station communicating with multiple wireless devices, the disclosure may refer to a subset of all wireless devices in the coverage area. The disclosure may refer to multiple wireless devices of a given LTE or 5G release, for example, that include a given capability and are in a given sector of the base station. Multiple wireless devices in the disclosure may refer to selected multiple wireless devices and / or a subset of all wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in a coverage area that may not comply with the disclosed methods. For example, those wireless devices or base stations perform based on older releases of LTE or 5G technology.

[0050] As used herein, "a" and "an" and similar phrases are to be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" should be interpreted as "at least one" and "one or more". As used herein, the term "may" should be interpreted as "may be, for example". In other words, the term "may" indicates that the phrase following the term "may" is an example of multiple preferred possibilities and may or may not be used with one or more of the various embodiments. As used herein, the terms "comprises" and "consists of" recite one or more components of a described element. The term "comprises" is interchangeable with "includes" and does not exclude unrecited components included in the described element. In contrast, "consists of" provides a complete recitation of one or more components of a described element. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" refers to any possible combination of the listed elements. For example, "A, B, and / or C" can refer to A, B, C, A and B, A and C, B and C, or A, B, and C.

[0051] If A and B are sets and every element of A is also an element of B, then A is said to be a subset of B. Only non-empty sets and subsets are considered herein. For example, possible subsets of B={cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "based at least on") indicates that the phrase following the term "based on" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "adopted / used" (or, equivalently, "adopted / used at least") indicates that the phrase following the phrase "adopted / used" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments.

[0052] The term configured may relate to the capacity of a device, whether the device is in an operational or non-operational state. Configured may refer to a particular setting of a device that affects the operational characteristics of the device, whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device, whether the device is in an operational or non-operational state, to provide the device with a particular characteristic. A term such as "a control message originating in a device" may mean that the control message has parameters that can be used to configure a particular characteristic in the device or to implement a particular action in the device, whether the device is in an operational or non-operational state.

[0053] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, which may contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, which contains parameter (IE)K, which contains parameter (IE)J, then, e.g., N contains K and N contains J. In an example embodiment, when one or more messages contain multiple parameters, it means that a parameter of the multiple parameters is included in at least one of the one or more messages, but need not be included in each of the one or more messages.

[0054] Many of the presented features are described as being optional through the use of "may" or through the use of parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe each and every variation that may be obtained by selecting from a set of optional features. This disclosure should be construed as explicitly disclosing all such variations. For example, a system described as having three optional features may be embodied in seven ways, i.e., with only one of the three possible features, any two of the three features, or three of the three features.

[0055] Many of the elements described in the disclosed embodiments may be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, which may be behaviorally equivalent. For example, a module may be implemented in software routines written in a computer language configured to run on a hardware machine (C, C++, Fortran, Java, Basic, Matlab, etc.) or Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It may also be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using Hardware Description Languages ​​(HDLs) such as Verilog or VHSIC Hardware Description Language (VHDL), which configure the connections between the internal hardware modules with fewer functions of the programmable device. To achieve a functional modular result, the above techniques are often used in combination.

[0056] 1A illustrates an example of a mobile communication network 100 in which an embodiment of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

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

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

[0059] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile or fixed (non-portable) device for which wireless communication is required or available. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicular roadside 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 / receive unit (WTRU), and / or wireless communication device.

[0060] The RAN 104 may include one or more base stations (not shown). The term base station may 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 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, e.g., associated with WiFi or other suitable wireless communication standard), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

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

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

[0063] The RAN 104 may be deployed as a homogeneous network of macrocell base stations with similar antenna patterns and similar high-level transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations may be used to provide small coverage areas, e.g., coverage areas that overlap with the relatively large coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas of high data traffic (or so-called hot spots) or areas where macrocell coverage is weak. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

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

[0065] FIG. 1B illustrates another example mobile communication network 150 in which an embodiment of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1B, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and a UE 156A and a UE 156B (collectively, UE 156). These components may be implemented and operate in the same or similar manner as the corresponding components described with respect to FIG. 1A.

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

[0067] As shown in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, shown as one component AMF / UPF 158 in FIG. 1B for ease of explanation. The UPF 158B may act as a gateway between the NG-RAN 154 and one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic usage reporting, uplink classification to support routing of traffic flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggers. The UPF 158B may act as an anchor point for intra / inter radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branching point to support multi-homed PDU sessions. The UE 156 may be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

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

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

[0070] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via wireless communication over the air interface. The NG-RAN 154 may include one or more gNBs (collectively gNB 160), illustrated as gNB 160A and gNB 160B, and / or one or more ng-eNBs (collectively ng-eNB 162), illustrated as ng-eNB 162A and ng-eNB 162B. The gNBs 160 and ng-eNB 162 may be more generally referred to as base stations. The gNBs 160 and ng-eNB 162 may include one or more sets of antennas for communicating with the UE 156 over the air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas for controlling three cells (or sectors), respectively. Together, the gNB160 and ng-eNB162 cells may provide radio coverage to the UE156 over a wide geographic area to support UE mobility.

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

[0072] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by an NG-User Plane (NG-U) interface. The NG-U interface may provide for the provision of user plane PDUs between the gNB 160A and the UPF 158B (e.g., non-guaranteed delivery). The gNB 160A may be connected to the AMF 158A using an NG Control Plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or alert message transmission.

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

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

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

[0076] Figures 2A and 2B show examples of NR user plane and NR control plane protocol stacks, respectively, for the Uu interface between a UE 210 and a gNB 220. The protocol stacks shown in Figures 2A and 2B may be the same or similar to those used for the Uu interface between a UE 156A and a gNB 160A shown in Figure 1B, for example.

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

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

[0079] The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). The PDCPs 214 and 224 may perform, for example, retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets for intra-gNB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of a packet being received and remove any duplicate packets at the receiver. Packet duplication may be useful for services that require high reliability.

[0080] Although not shown in FIG. 3, the PDCPs 214 and 224 may perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells, or more generally, 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 a cell group in dual connectivity. The PDCPs 214 and 224 may map / demap the split radio bearer between the RLC channels belonging to the cell group.

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

[0082] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from the PHYs 211 and 221. The MACs 222 may be configured to perform scheduling, scheduling information reporting, and prioritization between UEs by dynamic scheduling. Scheduling may be performed at the gNB 220 (at the MACs 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction, prioritization between logical channels of the UE 210 by logical channel prioritization, and / or padding through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in case of carrier aggregation (CA)). The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In one embodiment, mapping restrictions on logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, MACs 212 and 222 may provide logical channels to RLCs 213 and 223 as services.

[0083] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions to transmit and receive information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels to the MACs 212 and 222 as a service.

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

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

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

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

[0088] FIG. 4B further illustrates a MAC Control Element (CE) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. The MAC CEs may be inserted at the beginning of the MAC PDU for downlink transmission (as shown in FIG. 4B) and at the end of the MAC PDU for uplink transmission. The MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs, such as buffer status reports and power headroom reports, enable / disable MAC CEs, such as for PDCP duplicate detection enable / disable, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components, discontinuous reception (DRX)-related MAC CEs, timing advancement MAC CEs, and random access-related MAC CEs. The MAC CEs may be preceded by a MAC subheader of a format similar to that described for the MAC SDU and may be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0090] 5A and 5B show the mapping between logical, transport, and physical channels for the downlink and uplink, respectively. Information is passed through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels may be used between the RLC and MAC and may be classified as control channels, which carry control and configuration information in the NR control plane, or as traffic channels, which carry data in the NR user plane. Logical channels may be classified as dedicated logical channels, which are dedicated to a particular UE, or as common logical channels, which may be used by two or more UEs. Logical channels may also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, - a Paging Control Channel (PCCH) for carrying paging messages used to page UEs whose location is unknown to the network at the cell level; - a Broadcast Control Channel (BCCH) for carrying system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which may 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) for carrying control messages with random access; - a Dedicated Control Channel (DCCH) for carrying control messages to and from a specific UE for configuring the UE; - A Dedicated Traffic Channel (DTCH) for carrying user data to and from a specific UE.

[0091] Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example: - a paging channel (PCH) for carrying paging messages originating from the PCCH; - a Broadcast Channel (BCH) for carrying the MIB from the BCCH; - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from the BCCH; - an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; - A Random Access Channel (RACH) that allows a UE to contact the network without prior scheduling.

[0092] The PHY may pass information between processing levels of the PHY using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY may generate control information to support the lower level operation of the PHY and provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR may include, for example: - a Physical Broadcast Channel (PBCH) to carry the MIB from the BCH; - a Physical Downlink Shared Channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH; - a Physical Downlink Control Channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands; - a Physical Uplink Shared Channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and, in some examples, Uplink Control Information (UCI), as described below; - a physical uplink control channel (PUCCH) for carrying UCI, which may include a HARQ acknowledgement, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a scheduling request (SR); - A Physical Random Access Channel (PRACH) for random access.

[0093] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by NR include the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), the Channel State Information Reference Signal (CSI-RS), the Demodulation Reference Signal (DMRS), the Sounding Reference Signal (SRS), and the Phase Tracking Reference Signal (PT-RS). These physical layer signals are described in more detail below.

[0094] 2B shows an example of an NR control plane protocol stack. In FIG. 2B, the NR control plane protocol stack may use the first four protocol layers that are the same / similar to the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane 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.

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

[0096] The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220, or more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may 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 may multiplex the control plane and user plane data within the same transport block (TB). The RRCs 216 and 226 may provide control plane functions such as broadcasting system information related to the AS and the NAS, paging initiated by the CN or the RAN, establishment, maintenance, and release of an RRC connection between the UE 210 and the RAN, security functions including key management, establishment, configuration, maintenance, and release of signaling and data radio bearers, mobility functions, QoS management functions, control of UE measurement reporting and reporting, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing an RRC connection, the RRCs 216 and 226 may establish an RRC context, which may involve setting parameters for communications between the UE 210 and the RAN.

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

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

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

[0100] In RRC Inactive 606, previously established RRC context is maintained in the UE and base station. This allows for faster transition to RRC Connection 602 with reduced signaling overhead compared to transition from RRC Idle 604 to RRC Connection 602. In RRC Inactive 606, the UE is in a sleep state and UE mobility may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connection 602 by a Connection Resume procedure 614 or to RRC Idle 604 via a Connection Release procedure 616 that is the same as or similar to the Connection Release procedure 608.

[0101] The RRC states may 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 inform the UE of events via paging messages without broadcasting the paging messages throughout the entire mobile communication network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 may allow the network to track the UE on a cell group level, so that paging messages may be broadcast on cells of the cell group in which the UE is currently located instead of the entire mobile communication network. The mobility management mechanisms in RRC Idle 604 and RRC Inactive 606 track the UE on a cell group level. They may do so using different granularity of grouping. For example, there may be three levels of granularity of cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas referred to as a tracking area and identified by a Tracking Area Identifier (TAI).

[0102] The tracking area may be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) may provide the UE with a list of TAIs associated with the 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 may perform a registration update with the CN to enable the CN to update the UE's location and provide the UE with a new UE registration area.

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

[0104] A base station that stores an RRC context for a UE or a last serving base station for the UE may be referred to as an anchor base station. The anchor base station may 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.

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

[0106] In NR, physical signals and physical channels (FIGS. 5A and 5B) may be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data on F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, which are split into F parallel symbol streams. The F parallel symbol streams may be treated as if they were in the frequency domain and used as input to an inverse fast Fourier transform (IFFT) block that transforms them to the time domain. The IFFT block may take F source symbols, one at a time, from each of the F parallel symbol streams and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time domain samples that represent a sum of the F orthogonal subcarriers. The F time domain samples may form a single OFDM symbol. After some processing (e.g., adding a cyclic prefix) and upconversion, the OFDM symbols provided by the IFFT block may be transmitted over the air interface at a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This processing produces a Discrete Fourier Transform (DFT) precoded OFDM symbol, which can be used by UEs in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0107] FIG. 7 illustrates an example configuration of an NR frame in which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat at a period of 1024 frames. As illustrated, an NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each of which is 1 ms in duration. The subframes may be divided into slots, each of which includes, for example, 14 OFDM symbols per slot.

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

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

[0110] FIG. 8 shows an example configuration of slots in the time and frequency domains of an NR carrier. A slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers. Such limitations, if used, may limit an NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, and the 400 MHz bandwidth may be set based on the 400 MHz per carrier bandwidth limit.

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

[0112] NR may support a wide range of carrier bandwidths (e.g., up to 400 MHz with 120 kHz subcarrier spacing). Not all UEs may be able to receive the full carrier bandwidth (e.g., hardware limitations, etc.). Also, receiving the full carrier bandwidth may be prohibitive from a UE power consumption perspective. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its reception bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

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

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

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

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

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

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

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

[0120] In one embodiment, a base station may semi-statically configure a UE with one or more BWPs, and the UE may 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., if the second BWP is a default BWP).

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

[0122] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with three BWPs may be switched from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, 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 may be the initial active BWP, and BWP 904 may be the default BWP. The UE may switch between BWPs at a switching point. In the example of FIG. 9, the UE may switch from BWP 902 to BWP 904 at switching point 908. Switching at switching point 908 may occur for any suitable reason, for example, in response to expiration of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 906 at switching point 910 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch from the active BWP 906 to BWP 904 at switching point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 902 at switching point 914 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0123] If the UE is configured for a secondary cell with a default downlink BWP in the set of configured downlink BWPs and timer values, the UE procedures for switching the BWP on the secondary cell may be the same / similar to those on the primary cell, e.g., the UE may use timer values ​​and default downlink BWPs for the secondary cell in the same / similar manner that the UE uses these values ​​for the primary cell.

[0124] To provide a larger data rate, two or more carriers can be aggregated and transmitted simultaneously to and from the same UE using carrier aggregation (CA). The aggregated carriers in CA can be referred to as component carriers (CC). When CA is used, there are many serving cells for the UE and one for the CC. The CC can have three configurations in the frequency domain.

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

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

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

[0128] A configured SCell for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of a SCell may mean that PDCCH and PDSCH reception on the SCell is deactivated and PUSCH, SRS, and CQI transmission on the SCell is deactivated. A configured SCell may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCell (e.g., among a subset of configured SCells) for a UE is activated or deactivated. A configured SCell may be deactivated in response to expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0130] FIG. 10B illustrates an example of how aggregation cells may be configured into one or more PUCCH groups. The PUCCH group 1010 and the PUCCH group 1050 may each include one or more downlink CCs. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. The PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as Primary SCell (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted on the uplink of PSCell 1061. In one embodiment, if the aggregation cells depicted in FIG. 10B are not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell and PCell for transmitting UCI associated with downlink CCs may be overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, the overload may be prevented.

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

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

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

[0134] FIG. 11A illustrates an example of a structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). A burst may be transmitted periodically (e.g., every two frames or every 20 ms). A burst may be limited to a half frame (e.g., the first half frame having a duration of 5 ms). It will be appreciated that FIG. 11A is an example, and these parameters (number of SS / PBCH blocks per burst, periodicity of the burst, location of the burst within a frame) may be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH block is transmitted, the numerology or subcarrier spacing of the cell, configuration by the network (e.g., using RRC signaling), or any other suitable factor. In one example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the wireless network configures the UE to assume a different subcarrier spacing.

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

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

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

[0138] The PBCH may use QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of the cell's current system frame number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a Master Information Block (MIB) used to provide one or more parameters to the UE. The MIB is used to identify the remaining minimum system information (RMSI) with which the UE is associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. The SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. The UE may be pointed to a frequency based on the PBCH indicating that SIB1 is not present, and the UE may search for an SS / PBCH block on the frequency to which the UE is pointed.

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

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

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

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

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

[0144] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with the timing and / or periodicity of the CSI reports. For aperiodic CSI reporting, the base station may request the CSI reports. For example, the base station may instruct the UE to measure configured CSI-RS resources and provide a CSI report on the measurements. For semi-persistent CSI reporting, the base station may configure the UE to periodically transmit and selectively start or stop periodic reports. The base station may configure the UE with the CSI-RS resource set and CSI reports using RRC signaling.

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

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

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

[0148] The PDSCH may include one or more layers. The UE may assume that at least one symbol with a DMRS is present on one or more layers of the PDSCH. Higher layers may configure up to three DMRS for the PDSCH.

[0149] The downlink PT-RS may be transmitted by the base station and may be used by the UE for phase noise compensation. Whether the downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by DCI. When configured, the dynamic presence of the downlink PT-RS may be associated with one or more DCI parameters including at least the MCS. The NR network may support multiple PT-RS densities defined in the time and / or frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS may be restricted to the scheduled time / frequency period of the UE. The downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

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

[0151] The PUSCH may include one or more layers, and the UE may transmit at least one symbol having a DMRS present on one or more layers of the PUSCH. In one embodiment, higher layers may configure up to three DMRSs for the PUSCH.

[0152] An uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not be present depending on the RRC configuration of the UE. The presence and / or pattern of the uplink PT-RS may be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by RRC signaling and / or DCI. When configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters including at least the MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS may be limited to the scheduled time / frequency duration of the UE.

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

[0154] The base station may quasi-statistically configure the 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 the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot, minislot, and / or subframe level periodicity, an offset for periodic and / or aperiodic SRS resources, a number of OFDM symbols in the SRS resource, a starting OFDM symbol of the SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a periodic shift, and / or an SRS sequence ID.

[0155] The antenna ports are defined such that a channel on which a symbol on an antenna port is carried can be inferred from a channel on which another symbol on the same antenna port is carried. When a first symbol and a second symbol are transmitted on the same antenna port, a receiver may infer a channel (e.g., fade gain, multipath delay, and / or the like) on which a second symbol on an antenna port is carried from a channel on which a first symbol on the antenna port is carried. A first antenna port and a second antenna port may be referred to as quasi-colocated (QCLed) if one or more large-scale characteristics of a channel on which a first symbol on the first antenna port is carried can be inferred from a channel on which a second symbol of the second antenna port is carried. The one or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (Rx) parameters.

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

[0157] FIG. 11B illustrates an example of a channel state information reference signal (CSI-RS) mapped to the time and frequency domain. The squares illustrated in FIG. 11B may span resource blocks (RBs) within the bandwidth of a cell. The base station may transmit one or more RRC messages including a CSI-RS resource configuration parameter indicating one or more CSI-RS. One or more of the following parameters may be set by higher layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) location within a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and radio frame periodicity), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, quasi-collocation (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

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

[0161] FIG. 12A shows examples of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements at a transmit (Tx) beam of a transmit receive point (TRP) (or multiple TRPs) to support selection of, for example, one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at a TRP may include a Tx beam sweep for a set of beams (shown as an ellipse rotating in a counterclockwise direction as indicated by the dashed arrow in the top rows of P1 and P2). Beamforming at a UE may include a Rx beam sweep for a set of beams (shown as an ellipse rotating in a clockwise direction as indicated by the dashed arrow in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements at a Tx beam of a TRP (shown as an ellipse rotating in a counterclockwise direction as indicated by the dashed arrow in the top row of P2). The UE and / or base station may perform procedure P2 using a smaller set of beams than used in procedure P1 or using narrower beams than used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beams at the UE.

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

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

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

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

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

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

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

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

[0170] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., Group A and / or Group B). The preamble group may include one or more preambles. The UE may determine the preamble group based on a path loss measurement and / or a size of Msg3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and / or the 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.

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

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

[0173] Msg2 1312 received by the UE may include an RAR. In some scenarios, Msg2 1312 may include multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 was received by the base station. Msg2 1312 may include a time alignment command that the UE may use to adjust the UE's transmission timing, a scheduling grant for the transmission of Msg3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After the UE transmits the preamble, the UE may start a time window (e.g., ra-ResponseWindow) in which it monitors the PDCCH for Msg2 1312. The UE may determine when to start the time window based on the PRACH opportunity the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on numerology. The PDCCH may be within a common search space (e.g., Type1-PDCCH common search space) configured by the RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used in response to one or more events that initiate the random access procedure. The UE may use a Random Access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity on which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on an OFDM symbol index, a slot index, a frequency domain index, and / or a UL carrier indicator of the PRACH opportunity. Examples of the RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≦s_id<14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

[0174] The UE may transmit Msg3 1313 in response to successful reception of Msg2 1312 (e.g., using resources identified in Msg2 1312). Msg3 1313 may be used for contention resolution, for example, in the contention-based random access procedure shown in FIG. 13A. In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide the UE with a corresponding RAR. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Contention resolution (e.g., use of Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other suitable identifier) ​​in Msg3 1313.

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

[0176] The UE may be configured with a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedure) may be supported on the uplink carrier. For example, the base station may configure the UE with two separate RACH configurations, one for the SUL carrier and one for the NUL carrier. For random access in a cell configured with the SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The UE may determine the SUL carrier, for example, if the measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. The UE may switch uplink carriers during the random access procedure (e.g., between Msg1 1311 and Msg3 1313) in one or more cases. For example, the UE may determine and / or switch the uplink carrier for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (e.g., listen-before-talk).

[0177] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, the base station may transmit a configuration message 1320 to the UE before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. FIG. 13B includes the transmission of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312, respectively, illustrated in FIG. 13A. As can be seen from FIG. 13A and FIG. 13B, the contention-free random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

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

[0179] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor for PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure shown in FIG. 13B, the UE may determine that the random access procedure is successfully completed after or in response to transmitting Msg1 1321 and receiving the corresponding Msg2 1322. The UE may determine that the random access procedure is successfully completed, for example, if the PDCCH transmission is addressed to the C-RNTI. The UE may determine that the random access procedure is successfully completed, for example, if the UE receives an RAR including a preamble identifier corresponding to a preamble transmitted by the UE and / or if the RAR includes a MAC sub-PDU including a preamble identifier. The UE may determine the response as an indication of a response acknowledgment to the SI request.

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

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

[0182] The UE may initiate the two-step random access procedure of FIG. 13C for licensed and / or unlicensed spectrum. The UE may determine whether to initiate the two-step random access procedure based on one or more factors. The one or more factors may be the radio access technology in use (e.g., LTE, NR, and / or similar), whether the UE has a valid TA, the cell size, the RRC state of the UE, the type of spectrum (e.g., licensed vs. unlicensed), and / or any other suitable factor.

[0183] The UE may determine radio resources and / or uplink transmit 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 may indicate a modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or the transport block 1342. The time-frequency resources for transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmission of the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0184] The transport block 1342 may include data (e.g., delay sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation and / or MCS), a UE identifier for contention resolution, and / or an RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE and / or the UE identifier in Msg B 1332 matches the UE identifier (e.g., transport block 1342) in Msg A 1331.

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

[0186] The downlink control signaling may include downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or any other suitable signaling. A UE may receive the downlink control signaling in a payload transmitted by a base station on a Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a Group Common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0187] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with an identifier may include a modulo-2 addition (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a Radio Network Temporary Identifier (RNTI), which is a 16-bit value.

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

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

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

[0191] FIG. 14A illustrates an example of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources on which a UE attempts to decode DCI using one or more search spaces. A base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, 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 a slot. A fourth CORESET 1404 occurs at a seventh symbol of the slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0192] FIG. 14B illustrates an example of CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be interleaved (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate interference coordination and / or frequency selective transmission of control channels). A base station may perform different or the same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by an RRC configuration. A CORESET may be configured with an antenna port quasi-co-location (QCL) parameter. The QCL parameter of an antenna port may indicate the QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

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

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

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

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

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

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

[0199] FIG. 15 illustrates an example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in FIG. 1A, the mobile communication network 150 shown in FIG. 1B, or other communication network. Although only one wireless device 1502 and one base station 1504 are shown in FIG. 15, it will be understood that a mobile communication network may include more than one UE and / or more than one base station having the same or similar configuration as shown in FIG. 15.

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

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

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

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

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

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

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

[0207] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a 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, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data and / or provide user output data from 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 source and / or can be configured to distribute power to other components in the wireless device 1502. The power source 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.

[0208] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of scrambling, modulation of scramble bits to generate complex-valued symbols, mapping of complex-valued modulation symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding of the complex-valued symbols, mapping of the precoded complex-valued symbols onto resource elements, generating complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or the like. In one embodiment, if transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one embodiment, if transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated according to FIG. 16A. These functions are illustrated as examples, and it is anticipated that other mechanisms may be implemented in various embodiments.

[0209] 16B shows an example structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal for an antenna port. Filtering may be used before transmission.

[0210] 16C illustrates an exemplary structure of a downlink transmission. A baseband signal representing a physical downlink channel can perform one or more functions. The one or more functions may include scrambling of coded bits in a codeword to be transmitted on the physical channel, modulation of the scrambled bits to generate complex-valued modulation symbols, mapping of the complex-valued modulation symbols onto one or several transmission layers, precoding of the complex-valued modulation symbols on the layers for transmission on the antenna ports, mapping of the complex-valued modulation symbols of the antenna ports to resource elements, generation of a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are illustrated as examples, and it is anticipated that other mechanisms may be implemented in various embodiments.

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

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

[0213] A timer may begin execution when started and continue to execute until stopped or expires. A timer may be started if not running or restarted if running. A timer may be associated with a value (e.g., a timer may be started or restarted from a value, or may be started from zero and expire when the value is reached). A timer's duration may not be updated until the timer is stopped or expires (e.g., due to a BWP switch). A timer may be used to measure a time period / window of a process. When this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways to implement one or more timers. For example, it will be understood that one or more of multiple ways to implement a timer may be used to measure a time period / window for a procedure. For example, a random access response window timer may be used to measure a window time for receiving a random access response. In one embodiment, the time difference between two timestamps may be used instead of the start and expiration of the random access response window timer. When the timer is restarted, the process for measuring the time window may be restarted. Other example implementations may be provided for restarting the measurement of the time window.

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

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

[0216] In one embodiment, a MAC PDU may include one or more MAC sub-PDUs, where a MAC sub-PDU includes 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. The MAC SDU may be of variable size. The MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0217] In one embodiment, if the MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may include a 1-bit long R field, a 1-bit long F field, a multi-bit long LCID field, a multi-bit long L field, or a combination thereof.

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

[0219] FIG. 18A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. The MAC sub-PDU containing the MAC CE may be placed before the MAC sub-PDU containing the MAC SDU or the MAC sub-PDU containing padding. FIG. 18B shows an example of a UL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. In one embodiment, the MAC sub-PDU containing the MAC CE may be placed after all MAC sub-PDUs containing the MAC SDU. Additionally, the MAC sub-PDU may be placed before the MAC sub-PDU containing padding.

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

[0221] In one embodiment, the MAC entity of the wireless device may transmit one or more MAC CEs to the MAC entity of the base station. FIG. 20 illustrates an example of one or more MAC CEs. The one or more MAC CEs may 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 barring BSR, and / or a long barring BSR. In one embodiment, the MAC CE may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in a MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short barring command MAC CE.

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

[0223] When configured with CA, the base station and / or wireless device may use an SCell activation / deactivation mechanism to improve battery or power consumption of the wireless device. When a wireless device is configured with one or more SCells, the base station may activate or deactivate at least one of the one or more SCells. A SCell may be deactivated unless the SCell state associated with the SCell is set to "activated" or "deactivated" upon configuration of the SCell.

[0224] The wireless device may activate / deactivate the SCell in response to receiving the SCell Activation / Deactivation MAC CE. In one embodiment, the base station may send one or more messages including a SCell timer (e.g., sCellDeactivationTimer) to the wireless device. In one embodiment, the wireless device may deactivate the SCell in response to expiration of the SCell timer.

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

[0226] When the wireless device receives a SCell Activation / Deactivation MAC CE to deactivate the activated SCell, the wireless device may deactivate the activated SCell. In one embodiment, when a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires, the wireless device may deactivate the activated SCell. In response to deactivation of the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In one embodiment, in response to deactivation of the activated SCell, the wireless device may 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 one embodiment, in response to deactivation of the activated SCell, the wireless device may suspend one or more configured uplink grants of configured uplink grant type 1 associated with the activated SCell and / or flush HARQ buffers associated with the activated SCell.

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

[0228] FIG. 21A shows an example of a one-octet SCell Activation / Deactivation MAC CE. A first MAC PDU subheader with a first LCID (e.g., “111010” as shown in FIG. 19) may identify a one-octet SCell Activation / Deactivation MAC CE. The size of the one-octet SCell Activation / Deactivation MAC CE may be constant. The one-octet SCell Activation / Deactivation MAC CE may include a single octet. The single octet may include a first number C field (e.g., 7) and a second number R field (e.g., 1).

[0229] Figure 21B shows an example of a 4-octet SCell Activation / Deactivation MAC CE. A second MAC PDU subheader with a second LCID (e.g., "111001" as shown in Figure 19) may identify the 4-octet SCell Activation / Deactivation MAC CE. The size of the 4-octet SCell Activation / Deactivation MAC CE may be constant. The 4-octet SCell Activation / Deactivation MAC CE may include 4 octets. The four octets may include a third number C field (e.g., 31) and a fourth number R field (e.g., 1).

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

[0231] FIG. 22A illustrates an example embodiment of RRC configuration of parameters for power saving operation and / or DRX operation. In one embodiment, the base station may transmit one or more RRC messages including configuration parameters for DRX operation to the wireless device. The MAC entity of the wireless device may control the PDCCH monitoring activity of the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and AI-RNTI based on the configuration parameters for DRX operation. When RRC_CONNECTED, if DRX is configured, for all activated serving cells, the MAC entity may discontinuously monitor the PDCCH using DRX operation. Otherwise, the MAC entity may continuously monitor the PDCCH.

[0232] In one embodiment, the configuration parameters for the DRX operation include drx-onDurationTimer indicating a period at the start of a DRX cycle, drx-SlotOffset indicating a delay before starting the drx-onDurationTimer, drx-InactivityTimer indicating a period after a PDCCH opportunity when the PDCCH indicates a new UL or DL ​​transmission to the MAC entity, drx-RetransmissionTimerDL indicating a maximum period before a DL retransmission is received (per DL HARQ process excluding the broadcast process), drx-RetransmissionTimerUL indicating a maximum period before a grant for a UL retransmission is received (per UL HARQ process), drx-LongCycleStartOffset indicating a Long DRX cycle, drx-StartOffset defining the subframe at which the Long and Short DRX cycles start, drx-ShortCycle for the Short DRX cycle, and drx-InactivityTimer indicating a period after a PDCCH opportunity when the PDCCH indicates a new UL or DL ​​transmission to the MAC entity, drx-RetransmissionTimerUL indicating a maximum period before a grant for a UL retransmission is received (per UL HARQ process), drx-LongCycleStartOffset indicating a Long DRX cycle, drx-StartOffset defining the subframe at which the Long and Short DRX cycles start, drx-ShortCycle for the Short DRX cycle, and drx-InactivityTimer indicating a period after a PDCCH opportunity when the wireless device is in the The time periods may include: drx-ShortCycleTimer indicating the period that the DRX cycle may be followed; drx-HARQ-RTT-TimerDL (per DL HARQ process excluding broadcast process) indicating the minimum period before a DL allocation for a HARQ retransmission is expected by the MAC entity; and drx-HARQ-RTT-TimerUL (per UL HARQ process) indicating the minimum period before a UL HARQ retransmission grant is expected by the MAC entity.

[0233] In one embodiment, configuration parameters for power saving operation (e.g., related to DRX operation) may include: ps-Wakeup, which indicates whether to start an associated drx-onDurationTimer when a DCI including a CRC scrambled by a PS-RNTI (DCP) is monitored but not detected by the wireless device; ps-TransmitOtherPeriodicCSI, which indicates whether to report periodic CSI that is not L1-RSRP on the PUCCH for the duration indicated by the drx-onDurationTimer when a DCP is configured but the associated drx-onDurationTimer has not been started; and ps-TransmitPeriodicL1-RSRP, which indicates whether to transmit periodic CSI that is L1-RSRP on the PUCCH for the duration indicated by the drx-onDurationTimer when a DCP is configured but the associated drx-onDurationTimer has not been started.

[0234] In one example, the configuration parameters for power saving operation may include ps-RNTI (e.g., based on the example embodiment of FIG. 24) indicating a PS-RNTI for DCI format 2_6, dci-Format2-6 indicating the number of search space sets for PDCCH monitoring for detection of DCI format 2_6 on active DL BWP of PCell or SpCell according to the common search space, and size-DCI-2-6 indicating the payload size for DCI format 2_6. The configuration parameters may include ps-PositionDCI-2-6 indicating the position in DCI format 2_6 of the wakeup indication bit, where when reported to upper layers, a wakeup indication bit set to 0 indicates not to start the drx-onDurationTimer for the next long DRX cycle, or when reported to upper layers, a wakeup indication bit set to 1 indicates to start the drx-onDurationTimer for the next long DRX cycle.

[0235] In one embodiment, a search space set is provided to the wireless device to monitor the PDCCH for detection of DCI format 2_6 in the active DL BWP of the PCell or SpCell, and if the UE detects DCI format 2_6, the physical layer of the wireless device reports the value of the wake-up indication bit for the wireless device to a higher layer (e.g., a MAC entity / layer of the wireless device) for the next long DRX cycle. If the wireless device does not detect DCI format 2_6, the physical layer of the wireless device does not report the value of the wake-up indication bit to a higher layer for the next long DRX cycle.

[0236] In one embodiment, the wireless device is provided with a search space set for monitoring the PDCCH for detection of DCI format 2_6 in an active DL BWP of a PCell or SpCell, and if the wireless device is not required to monitor the PDCCH for detection of DCI format 2_6 for all corresponding PDCCH monitoring opportunities outside the active time before the next long DRX cycle or does not have a PDCCH monitoring opportunity for detection of DCI format 2_6 outside the active time of the next long DRX cycle, the physical layer of the wireless device reports a value of 1 for the wake-up indication bit to upper layers during the next long DRX cycle.

[0237] In one embodiment, the serving cell of the MAC entity may be configured by RRC in two DRX groups with distinct DRX parameters. When RRC does not configure a secondary DRX group, there may be only one DRX group and all serving cells belong to that one DRX group. When configuring two DRX groups, each serving cell is uniquely assigned to one of the two groups. The DRX parameters configured separately for each DRX group are drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX groups are drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle(optional), drx-ShortCycleTimer(optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.

[0238] In one embodiment, when a DRX cycle is configured, the wireless device may determine that the active time for a serving cell in the DRX group includes the time during which the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is operating, or the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is operating in any serving cell in the DRX group, or the ra-ContentionResolutionTimer (or msgB-ResponseWindow) is operating, or an SR is transmitted on the PUCCH and is pending, and a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of an RAR for a random access preamble not selected by the MAC entity among the contention-based random access preambles.

[0239] In one embodiment, when DRX operation is configured, if a MAC PDU is received with a configured downlink allocation, the MAC entity of the wireless device may start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying the corresponding DL HARQ feedback and / or may stop the drx-RetransmissionTimerDL for the corresponding HARQ process.

[0240] In one embodiment, when DRX operation is configured, if a MAC PDU is transmitted in a configured uplink grant and no LBT failure indication is received from a lower layer, the MAC entity of the wireless device may start a drx-HARQ-RTT-TimerUL for the corresponding HARQ process at the first symbol after the end of the first transmission of the corresponding PUSCH transmission (e.g., in a bundle) and / or may stop a drx-RetransmissionTimerUL for the corresponding HARQ process at the first transmission of the corresponding PUSCH transmission (in a bundle).

[0241] In one embodiment, when DRX operation is configured, if the drx-HARQ-RTT-TimerDL expires and if the data of the corresponding HARQ process has not been successfully decoded, the MAC entity of the wireless device may start the drx-RetransmissionTimerDL for the corresponding HARQ process at the first symbol after expiration of the drx-HARQ-RTT-TimerDL.

[0242] In one embodiment, when DRX operation is configured, if the drx-HARQ-RTT-TimerUL expires, the MAC entity of the wireless device may start the drx-RetransmissionTimerUL for the corresponding HARQ process at the first symbol after expiration of the drx-HARQ-RTT-TimerUL.

[0243] In one embodiment, when DRX operation is configured, when a DRX Command MAC CE or a Long DRX Command MAC CE is received, the MAC entity of the wireless device may stop the drx-onDurationTimer for each DRX group and / or may stop the drx-InactivityTimer for each DRX group.

[0244] In one embodiment, when DRX operation is configured, if the drx-InactivityTimer for a DRX group expires, the MAC entity of the wireless device may start or restart the drx-ShortCycleTimer for this DRX group at the first symbol after expiration of the drx-InactivityTimer and / or may use a Short DRX cycle for this DRX group if a Short DRX cycle is configured. If the drx-InactivityTimer for a DRX group expires, the MAC entity of the wireless device may use a Long DRX cycle for this DRX group if a Short DRX cycle is not configured.

[0245] In one embodiment, when DRX operation is configured, if a DRX Command MAC CE is received, the MAC entity of the wireless device may start or restart the drx-ShortCycleTimer for each DRX group in the first symbol after the end of DRX Command MAC CE reception and / or may use a Short DRX cycle for each DRX group if a Short DRX cycle is configured. If a Short DRX cycle is not configured, if a DRX Command MAC CE is received, the MAC entity of the wireless device may use a Long DRX cycle for this DRX group.

[0246] In one embodiment, when DRX operation is configured, if the drx-ShortCycleTimer for a DRX group expires, the MAC entity of the wireless device may use a Long DRX cycle for this DRX group. If a Long DRX Command MAC CE is received, the MAC entity of the wireless device may stop the drx-ShortCycleTimer for each DRX group and / or use a Long DRX cycle for each DRX group.

[0247] In one embodiment, when DRX operation is configured, if a Short DRX cycle is used for a DRX group, and if [(SFN × 10) + subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle), the MAC entity of the wireless device may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.

[0248] FIG. 22B illustrates an example embodiment of power saving operation based on DCP reception. In one example, when a wireless device receives a DCP including a wake-up indication set to a first value, the wireless device may start a drx-onDurationTimer associated with DRX operation and / or monitor a PDCCH while the drx-onDurationTimer is activated. Upon expiration of the drx-onDurationTimer (or DRX switch to DRX off duration), the wireless device may stop monitoring a PDCCH. In one example, when a wireless device receives a DCP including a wake-up indication set to a second value, the wireless device may not start a drx-onDurationTimer associated with DRX operation and / or skip monitoring a PDCCH for the DRX on duration.

[0249] In an exemplary embodiment, when DRX operation is configured, if a Long DRX cycle is used for the DRX group and [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset, and if DCP monitoring is configured for an active DL BWP, the MAC entity of the wireless device shall start the drx-onDurationTimer when a DCP indication associated with the current DRX cycle received from lower layers indicates to start the drx-onDurationTimer or when all DCP opportunities in the time domain associated with the current DRX cycle have been received grant / allocation / DRX Command MAC CE / Long DRX Command MAC The CE may start the drx-onDurationTimer up to 4 ms before the start of the last DCP opportunity or during a measurement gap or when the MAC entity monitors PDCCH transmissions on the search space indicated by recoverySearchSpaceId for the SpCell identified by the C-RNTI while the ra-ResponseWindow is active, taking into account transmitted scheduling requests, or if ps-Wakeup is configured with the value true and no DCP indication associated with the current DRX cycle has been received from lower layers, during active time or after drx-SlotOffset from the beginning of the subframe.

[0250] In one embodiment, when DRX operation is configured, if a Long DRX cycle is used for a DRX group, and if [(SFN x 10) + subframe number] modulo (drx-LongCycle) = drx-StartOffset, and DCP monitoring is not configured for an active DL BWP, the MAC entity of the wireless device may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.

[0251] In one embodiment, when DRX operation is configured, if a DRX group is in active time, the MAC entity of the wireless device may monitor the PDCCH on the serving cell in this DRX group. If the PDCCH indicates DL transmission, the MAC entity of the wireless device may start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission performing DL HARQ feedback and / or may stop the drx-RetransmissionTimerDL for the corresponding HARQ process. The MAC entity may start the drx-RetransmissionTimerDL in the first symbol after the PDSCH transmission for the corresponding HARQ process if the PDSCH-to-HARQ_feedback timing indicates a non-numeric k1 value. If the HARQ feedback is postponed by the PDSCH-to-HARQ_feedback timing indicating a non-numeric k1 value, the corresponding transmission opportunity to transmit DL HARQ feedback is indicated in a later PDCCH requesting HARQ-ACK feedback.

[0252] In one embodiment, when DRX operation is configured, if a DRX group is in active time, the MAC entity of the wireless device may monitor the PDCCH on the serving cell in this DRX group. For example, if the PDCCH indicates an UL transmission, the MAC entity may start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process at the first symbol (within a bundle) after the end of the first transmission of the corresponding PUSCH transmission and / or may stop the drx-RetransmissionTimerUL for the corresponding HARQ process.

[0253] In one embodiment, when DRX operation is configured, if a DRX group is in active time, the MAC entity of the wireless device may monitor the PDCCH on a serving cell in this DRX group. If the PDCCH indicates a new transmission (DL or UL) on a serving cell in this DRX group, the MAC entity may start or restart the drx-InactivityTimer for this DRX group at the first symbol after the end of PDCCH reception. If a HARQ process receives downlink feedback information and an acknowledgement is indicated, the MAC entity may stop the drx-RetransmissionTimerUL for the corresponding HARQ process.

[0254] In one embodiment, when DRX operation is configured, if DCP monitoring is configured for an active DL BWP, if the current symbol n occurs within the drx-onDurationTimer period, if the drx-onDurationTimer associated with the current DRX cycle is not started, when the MAC entity evaluates all DRX active time conditions, taking into account received grants / allocations / DRX Command MAC CE / Long DRX Command MAC CE and SRs transmitted up to 4 ms prior to symbol n, if it is not in the active time, the MAC entity shall not transmit periodic SRS and semi-persistent SRS, shall not report semi-persistent CSI configured on PUSCH, shall not report periodic CSI that is L1-RSRP on PUCCH if ps-TransmitPeriodicL1-RSRP is not configured with the value true, and shall not report periodic CSI that is not L1-RSRP on PUCCH if ps-TransmitOtherPeriodicCSI is not configured with the value true.

[0255] In one embodiment, when DRX operation is configured, if DCP monitoring is not configured for an active DL BWP and / or the current symbol n does not occur within the drx-onDurationTimer period and / or the drx-onDurationTimer associated with the current DRX cycle is started, the MAC entity shall consider the serving cell of this DRX group and the DRX Command MAC CE / Long DRX Command MAC CE received, the grants / assignments scheduled on, and the scheduling requests sent up to 4 ms prior to symbol n when evaluating all DRX active time conditions, if CSI masking (csi-Mask) is configured by upper layers and at the current symbol n ... Taking into account the scheduled grants / allocations on the CE's serving cell, if not operational, do not transmit periodic SRS and semi-persistent SRS in this DRX group; do not report CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group; do not report CSI on PUCCH in this DRX group.

[0256] In one embodiment, regardless of whether the MAC entity is monitoring the PDCCH on the serving cell in the DRX group, the MAC entity may transmit HARQ feedback, aperiodic CSI on the PUSCH, and, if such is expected, aperiodic SRS on the serving cell in the DRX group. The MAC entity does not need to monitor the PDCCH for non-full PDCCH opportunities (e.g., if the active time starts or ends in the middle of a PDCCH opportunity).

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

[0258] In one embodiment, the base station and / or wireless device can switch the BWP between configured BWPs by DCI or BWP inactivity timer. If a BWP inactivity timer is configured for a serving cell, the base station and / or wireless device can switch the active BWP to a default BWP in response to expiration of a BWP inactivity timer associated with the serving cell. The default BWP can be configured by the network. In one embodiment, for an FDD system, one UL BWP and one DL BWP for each uplink carrier can be active simultaneously in an active serving cell when configured with a BA. In one embodiment, for a TDD system, one DL / UL BWP pair can be active simultaneously in an active serving cell. Operating with one UL BWP and one DL BWP (or one DL / UL pair) can improve battery consumption of the wireless device. BWPs other than one active UL BWP and one active DL BWP in which the wireless device can operate can be deactivated. In a deactivated BWP, the wireless device may not monitor the PDCCH and / or may not transmit on the PUCCH, PRACH, and UL-SCH.

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

[0260] FIG. 23 illustrates an example of a BWP switching on a cell (e.g., a PCell or SCell). In one example, a wireless device may receive from a base station at least one RRC message including parameters of the cell and one or more BWPs associated with the cell. The RRC message may include an RRC connection reconfiguration message (e.g., RRCReconfiguration), an RRC connection re-establishment message (e.g., RRCRestablishment), and / or an RRC connection setup message (e.g., RRCSetup). Of the one or more BWPs, at least one BWP may be configured as a first active BWP (e.g., BWP1) and one BWP may be configured as a default BWP (e.g., BWP0). The wireless device may receive a command (e.g., an RRC message, MAC CE, or DCI) to activate the cell in the nth slot. If the cell is a PCell, the wireless device may not receive a command to activate the cell, e.g., the wireless device may activate the PCell when the wireless device receives an RRC message including configuration parameters of the PCell. The wireless device may begin monitoring the PDCCH on BWP1 in response to activating the cell.

[0261] In one example, in response to receiving a DCI indicating a DL allocation on BWP1, the wireless device may start (or re-start) a BWP inactivity timer (e.g., bwp-InactivityTimer) at the mth slot. The wireless device may switch back to a default BWP (e.g., BWP0) as the active BWP at the sth slot if the BWP inactivity timer expires. The wireless device may deactivate the cell and / or stop the BWP inactivity timer if the sCellDeactivationTimer expires (e.g., if the cell is a SCell). In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer on the PCell.

[0262] In one embodiment, the MAC entity may apply normal operation to active BWPs of activated serving cells configured with BWPs, including transmitting on UL-SCH, transmitting on RACH, monitoring PDCCH, transmitting PUCCH, receiving DL-SCH, and / or (re)initializing suspended configured uplink grants of configured grant type 1 according to the stored configuration, if any.

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

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

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

[0266] In one embodiment, if a wireless device is configured for a secondary cell with an upper layer parameter Default-DL-BWP indicating a default DL BWP among the configured DL BWPs, and the wireless device is configured with an upper layer parameter bwp-InactivityTimer indicating a timer value, the wireless device procedure on the secondary cell may be the same as that on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0267] In one example, if a wireless device is configured with higher layer parameters Active-BWP-DL-SCell being the first active DL BWP on a secondary cell or carrier, and with higher layer parameters Active-BWP-UL-SCell being the first active UL BWP, the wireless device may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the first active DL BWP and the first active UL BWP on the secondary cell or carrier, respectively.

[0268] In one embodiment, the set of PDCCH candidates for a wireless device to monitor is defined in terms of a PDCCH search space set, which includes a CSS set or a USS set. The wireless device is to monitor PDCCH candidates in one or more of the following search space sets: a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB, or by searchSpaceSIB1 in PDCCH-ConfigCommon, or by searchSpaceZero in PDCCH-ConfigCommon, for a DCI format having a CRC scrambled by SI-RNTI in a primary cell of the MCG; a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon, for a DCI format having a CRC scrambled by SI-RNTI in a primary cell of the MCG; a Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon, for a DCI format having a CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI in a primary cell; Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by P-RNTI in the primary cell of the MCG Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType=common 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, for the primary cell only, C-RNTI, MCS-C-RNTI, or CS-RNTIA CSS set and a USS set configured by the SearchSpace in the PDCCH-Config with searchSpaceType=ue-Specific for a DCI format having a CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

[0269] In one embodiment, the wireless device determines a PDCCH monitoring opportunity on an active DL BWP based on one or more PDCCH configuration parameters including a PDCCH monitoring periodicity in a slot, a PDCCH monitoring offset, and a PDCCH monitoring pattern. For a search space set (SS s), the wireless device determines whether a PDCCH monitoring opportunity occurs in slot number

number

number

number

number

number

[0270] In an embodiment, the wireless device may perform the following for a search space set s associated with CORESETp:

number

number

number

number

number

number

number

number

number

[0271] In one example, a wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set including multiple search spaces (SS). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to a monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in a common SS, and / or number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The possible DCI formats may be based on the example embodiment of FIG. 24.

[0272] FIG. 24 shows examples of DCI formats that may be used by a base station to transmit control information to a wireless device or may be used by a wireless device for PDCCH monitoring. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In one example, DCI format 0_0 may be used to schedule a PUSCH in one cell. DCI format 0_1 ​​may be used to schedule one or more PUSCHs in one cell or indicate CG-DFI (configured grant-downlink feedback information) for a configured grant PUSCH, etc. DCI formats that a wireless device may monitor in an SS may be configured based on an example embodiment for FIG. 28 described later.

[0273] FIG. 25 illustrates an example of an RRC configuration for a serving cell having a dormancy configuration. In one embodiment, the base station may transmit to the wireless device one or more configuration parameters for the dormancy operation of the cell. In one embodiment, the configuration parameters may include a dormancyGroupOutsideActiveTime that includes a bitmap for multiple groups of configured SCells. The bitmap position may be immediately after the wake-up indication bit position (e.g., configured in DCI format 2_6). The bitmap size may be equal to the number of groups of configured SCells, and each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured SCells. A "0" value for a bit of the bitmap indicates an active DL BWP, provided by dormantBWP-Id (e.g., as shown in FIG. 25), for the wireless device for each woken SCell in the corresponding group of configured SCells. A "1" value for a bit in the bitmap may indicate the active DL BWP provided by firstOutsideActiveTimeBWP-Id for the wireless device for each activated SCell in the corresponding group of configured SCells if the current active DL BWP is a dormant DL BWP, or may indicate the current active DL BWP for the wireless device for each activated SCell in the corresponding group of configured SCells if the current active DL BWP is not a dormant DL BWP. The wireless device may set the active DL BWP to the indicated active DL BWP.

[0274] In one embodiment, the wireless device may be provided with a search space set (e.g., based on FIG. 22A and / or FIG. 28) and may monitor the PDCCH to detect DCI format 2_6 in an active DL BWP of a PCell or SpCell. The wireless device may detect DCI format 2_6. In one embodiment, the DCI format 2_6 may include an SCell dormancy indication field, which is a bitmap of a size equal to the number of configured SCell groups provided by dormancyGroupWithinActiveTime (e.g., as shown in FIG. 25), where each bit of the bitmap corresponds to a group of SCells configured from the number of configured SCell groups.

[0275] In one embodiment, a wireless device may be configured with a search space (or search space set) to monitor the PDCCH for detection of DCI format 0_1 ​​and DCI format 1_1, one or both of which include a SCell dormancy indication field. If the wireless device detects DCI format 0_1 ​​or DCI format 1_1 that does not include a carrier indicator field or detects DCI format 0_1 ​​or DCI format 1_1 that includes a carrier indicator field with a value equal to 0, the wireless device may set the active DL BWP to the indicated active DL BWP. In one embodiment, the indicated active DL BWP may be the active DL BWP provided by the dormantBWP-Id for each activated SCell in a group of configured SCells if a bit corresponding to the group in the SCell dormancy indication bitmap is set to a “0” value. In one embodiment, if the bit is set to a “1” value, then for the wireless device for each activated SCell in the corresponding group of configured SCells if the current active DL BWP is a dormant DL BWP, or if the current active DL BWP is not a dormant DL BWP, then the indicated active DL BWP may be the active DL BWP provided by firstWithinActiveTimeBWP-Id for each activated SCell in the corresponding group of configured SCells.

[0276] In an example embodiment, the wireless device may determine a DCI (e.g., DCI format 1_1) as indicating a SCell dormant state (e.g., not scheduling PDSCH reception or indicating an SPS PDSCH release) based on at least one of the following conditions: the wireless device is provided with a search space set to monitor the PDCCH for detection of DCI; the CRC of the DCI is scrambled by the C-RNTI or MCS-C-RNTI; the one-shot HARQ-ACK request field is not present or has a “0” value; the DCI detected on the PCell does not include a carrier indicator field or includes a carrier indicator field having a value equal to 0; resourceAllocation=resourceAllocationType0 and all bits of the frequency domain resource allocation field in the DCI are equal to 0; resourceAllocation=resourceAllocationType1 and all bits of the frequency domain resource allocation field in the DCI are equal to 1; and / or resourceAllocation=dynamicSwitch and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0 or 1. In one example, in response to determining the DCI as indicating SCell dormancy, the wireless device may consider the following fields for transport block 1: MCS, NDI, RV and HARQ process number, antenna port, DMRS sequence initialization as providing a bitmap for each configured SCell, in ascending order of SCell index. A "0" value for a bit in the bitmap may indicate an active DL BWP, as provided by the dormantBWP-Id, to the wireless device for the corresponding activated SCell.A “1” value for a bit in the bitmap may indicate to the wireless device for the corresponding activated SCell an active DL BWP, provided by firstWithinActiveTimeBWP-Id, if the current active DL BWP is a dormant DL BWP or a current active DL BWP, if the current active DL BWP is not a dormant DL BWP. The wireless device may set the active DL BWP to the indicated active DL BWP.

[0277] In one embodiment, if the active DL BWP provided by the dormantBWP-Id for the wireless device on the activated SCell is not the default DL BWP for the wireless device on the activated SCell, the BWP inactivity timer is not used for the transition from the active DL BWP provided by the dormantBWP-Id to the default DL BWP on the activated SCell.

[0278] In one example, the wireless device may provide HARQ-ACK information in response to detecting DCI format 1_1 indicating SCell dormancy N symbols after the last symbol of a PDCCH providing DCI format 1_1. If processingType2Enabled in PDSCH-ServingCellConfig is set to enabled for a serving cell having a PDCCH providing DCI format 1_1, N=7 for μ=0, N=7.5 for μ=1, and N=15 for μ=2, otherwise, N=14 for μ=0, N=16 for μ=1, N=27 for μ=2, and N=31 for μ=3, where μ is the minimum SCS configuration between the SCS configuration of the PDCCH providing DCI format 1_1 and the SCS configuration of the PUCCH having HARQ-ACK information in response to detecting DCI format 1_1.

[0279] FIG. 26 illustrates an example embodiment of a dormancy indication based on cell grouping. In one embodiment, a base station may transmit one or more RRC messages including configuration parameters of a plurality of SCells to a wireless device, where the plurality of SCells are grouped into a plurality of SCell groups (e.g., SCell group 1, SCell group 2 in FIG. 26) for dormancy indication. Each SCell group of the plurality of SCell groups may include one or more SCells of the plurality of SCells. As shown in FIG. 26, SCell group 1 includes cell 1, cell 2, etc. SCell group 2 includes cell 3, cell 4, etc. In one embodiment, a SCell of the plurality of SCells may include a plurality of BWPs including at least one of a first BWP as a non-dormant BWP and / or a second BWP as a dormant BWP.

[0280] In one embodiment, the wireless device may apply a dormancy indication to all (active) SCells of the SCell group, including transitioning, for each of the SCells of the SCell group, to a corresponding dormant BWP of each of the SCells of the SCell group, in response to receiving a dormancy indication indicating a dormant state of the SCell group. In one embodiment, the wireless device may apply a non-dormant indication to all SCells of the SCell group, including transitioning, for each of the SCells of the SCell group, to a corresponding non-dormant BWP of each of the SCells of the SCell group, in response to receiving a dormant indication indicating a non-dormant state of the SCell group.

[0281] As shown in FIG. 26, the wireless device may receive a dormancy indication bitmap including a plurality of dormancy indication bits, where each bit of the plurality of dormancy indication bits corresponding to a respective SCell group of the plurality of SCell groups indicates a dormant / non-dormant state for the respective SCell group. In one embodiment, the dormancy indication bitmap may be included in the DCI. In one embodiment, a first bit of the dormancy indication bitmap (e.g., the first bit in FIG. 26) set to "0" may indicate a dormant state of SCell group 1. A second bit of the dormancy indication bitmap (e.g., the second bit in FIG. 26) set to "1" may indicate a non-dormant state of SCell group 2.

[0282] In one example, in response to a first bit in the dormancy indication bitmap indicating a dormant state of SCell group 1, the wireless device may transition one or more SCells of SCell group 1 to a dormant state, including switching from an active BWP of cell 1 to a dormant BWP of cell 1, switching from an active BWP of cell 2 to a dormant BWP of cell 2, etc. In one example, in response to a first bit in the dormancy indication bitmap indicating a dormant state of SCell group 1, the wireless device may maintain the dormant state of the SCells of SCell group 1 if the SCells were in a dormant state prior to receiving the dormant indication. The wireless device may perform an action for each dormant BWP of cell 1, cell 2, etc. based on one or more embodiments of FIG. 26.

[0283] In one example, in response to a second bit in the dormancy indication bitmap indicating a non-dormant state of SCell group 2, the wireless device may transition one or more SCells of SCell group 2 to a non-dormant state, including switching to a non-dormant BWP of cell 3 as the active BWP of cell 3, switching to a non-dormant BWP of cell 4 as the active BWP of cell 4, etc. In one example, in response to a second bit in the dormancy indication bitmap indicating a non-dormant state of SCell group 2, the wireless device may maintain the non-dormant state of the SCells of SCell group 2 if the SCells were in a non-dormant state prior to receiving the dormant indication bitmap. The wireless device may perform actions for each non-dormant BWP of cell 3, cell 4, etc. based on one or more embodiments of FIG. 23. Transitioning the SCell state between dormant and non-dormant states based on cell grouping may improve signaling overhead, transmission delay, and / or reduce power consumption of the wireless device.

[0284] FIG. 27 illustrates an example of an RRC configuration parameter (e.g., BWP-DownlinkDedicated IE) of a downlink BWP of a serving cell. A base station may transmit one or more configuration parameters of a downlink BWP (e.g., initial downlink BWP) of a serving cell to a wireless device (or multiple wireless devices). As illustrated in FIG. 27, the one or more configuration parameters of the downlink BWP may include one or more parameters for a PDCCH of the downlink BWP (e.g., in a pdcch-Config IE) and one or more other parameters. The pdcch-Config IE may include one or more control resource set (CORESET) parameters that can be used in any common or UE-specific search space for the bandwidth portion. The one or more parameters of the PDCCH may indicate multiple search spaces for the bandwidth portion, each search space being associated with a search space ID. The one or more parameters of the PDCCH may include a search space switch configuration parameter (e.g., searchSpaceSwitchConfig-r16 IE) indicating one or more cell groups for search space switching. When a bit of a search space switching indication bitmap of a DCI (e.g., DCI format 2_0) indicates a first value, the wireless device may switch to a first search space group for all cells in a cell group corresponding to that bit. When a bit of a search space switching indication bitmap of a DCI (e.g., DCI format 2_0) indicates a second value, the wireless device may switch to a second search space group for all cells in a cell group corresponding to that bit.

[0285] As shown in FIG. 27, a CORESET may be associated with a CORESET index (e.g., ControlResourceSetId). A CORESET index of value 0 may identify a common CORESET configured in the MIB and ServingCellConfigCommon(controlResourceSetZero) and may not be used in the ControlResourceSet IE. A CORESET index with other values ​​may identify a CORESET configured by dedicated signaling or in SIB1. The controlResourceSetId is unique among the BWPs of the serving cell. A CORESET may be associated with a coresetPoolIndex indicating the index of the CORESET pool of the CORESET. A CORESET may be associated with a duration parameter (e.g., duration) indicating the continuous time duration of the CORESET in number of symbols. In an embodiment, as shown in FIG. 27, the configuration parameters of the CORESET may include at least one of a frequency resource indication (e.g., frequencyDomainResources), a CCE-REG mapping type indicator (e.g., cce-REG-MappingType), a number of TCI states, an indicator indicating whether a TCI is present in the DCI, and the like. The frequency resource indication, which includes a number of bits (e.g., 45 bits), indicates frequency domain resources, where each bit of the indication corresponds to a group of 6 RBs, and the grouping starts from the first RB group in the BWP of a cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit corresponds to the first RB group of the BWP, and so on. A bit set to 1 indicates that the RB group corresponding to that bit belongs to the frequency domain resources of this CORESET. Bits corresponding to groups of RBs that are not completely included in the BWP for which the CORESET is configured are set to zero.

[0286] In one embodiment, the base station may send one or more RRC messages to the wireless device including PDCCH configuration parameters (e.g., the PDCCH-ServingCellConfig IE shown in FIG. 27) valid for all downlink BWPs of the cell. In an embodiment, the PDCCH configuration parameters may include a timer value (e.g., an integer in units of symbols / slots or an integer in units of milliseconds) for a search space switch timer (e.g., a searchSpaceSwitchTimer IE). The search space switch timer and time value may be used for the search space switch operation described in FIG. 30A.

[0287] FIG. 28 illustrates an example of a configuration of a search space (e.g., SearchSpace IE) of a BWP. In one example, one or more search space configuration parameters of the search space may include at least one of a search space ID (searchSpaceId), a control resource set ID (controlResourceSetId), a monitoring slot periodicity and offset parameter (monitoringSlotPeriodicityAndOffset), a search space duration value (duration), a monitoring symbol indication (monitoringSymbolsWithinSlot), a number of candidates for an aggregation level (nrofCandidates), and / or an SS type (searchSpaceType) indicating a common SS type or a UE-specific SS type. The monitoring slot periodicity and offset parameters may indicate a slot (e.g., within a radio frame) and a slot offset (e.g., relative to the start of a radio frame) for PDCCH monitoring. The monitoring symbol indication may indicate which symbols of a slot the wireless device may monitor the PDCCH on the SS. The control resource set ID may identify a control resource set in which the SS may be located.

[0288] As shown in Figure 28, one or more search space configuration parameters of a search space may include a search space group list (e.g., searchSpaceGroupIdList) that indicates one or more search space groups to which the search space may belong for a search space switching operation. The search space switching operation may be based on the example embodiments of Figures 29, 30A and / or 30B.

[0289] FIG. 29 illustrates an example of DCI format 2_0 including one or more search space set group (or SSSG) switching indications (or search space set group switching flags). In this specification, a search space set group (SSSG) may be equivalent to a search space group (SSG). In one example, DCI format 2_0 may include one or more slot format indicators (e.g., slot format indicator 1, slot format indicator 2, ..., slot format indicator N), one or more available RB set indicators, one or more COT duration indications, and one or more SSS group switching flags. In one example, each of the one or more SSS group switching flags may correspond to a respective cell group of a plurality of cell groups. The plurality of cell groups may be implemented according to the example embodiment described above with respect to FIG. 27. Each cell group of the plurality of cell groups may include one or more cells. The SSS group switching flag of the one or more SSS group switching flags corresponding to the cell group may switch from a first SSS group to a second SSS group for each cell of the cell group when set to a first value. The SSS group switch flag, when set to the second value, may indicate a switch from the second SSS group to the first SSS group for each cell of the cell group. In one example, the multiple SSS groups including the first SSS group and the second SSS group may be configured based on the example embodiment described above with respect to Figure 28. The wireless device may perform SSS group switching based on the example embodiment of Figures 30A and 30B.

[0290] FIG. 30A illustrates an example of SSS group switching based on DCI (e.g., DCI format 2_0 described in FIG. 24, or other DCI format). In one example, a wireless device may be provided with a group index for a search space set (e.g., a Type3-PDCCH CSS set, a USS set, or any other type of search space set) according to searchSpaceGroupIdList (e.g., based on the example embodiment of FIG. 28) for PDCCH monitoring on a serving cell. The wireless device may be provided with multiple SSS groups (e.g., or SSG). The wireless device may monitor the PDCCH based on configuration parameters of the PDCCH, for example, based on the example embodiment described above with respect to FIG. 28.

[0291] In one embodiment, the wireless device may not be provided with a searchSpaceGroupIdList for the search space set. The embodiment of Figure 30A may not be applicable to PDCCH monitoring on a search space set if the search space set is not configured with a searchSpaceGroupIdList. Based on not applying the embodiment of Figure 30A, the wireless device may, for example, monitor the search space set on the BWP without switching from the search space set for PDCCH monitoring.

[0292] In one example, if the wireless device is provisioned with a cellGroupsForSwitchList (e.g., based on the example embodiment shown in FIG. 27) indicating one or more groups of serving cells, the embodiment of FIG. 30A may apply to all (actuator) serving cells in each group. If the wireless device is not provisioned with a cellGroupsForSwitchList, the embodiment of FIG. 30A may apply only to serving cells for which the wireless device is provided with a searchSpaceGroupIdList.

[0293] In one embodiment, if the wireless device is provided with a searchSpaceGroupIdList, the wireless device may reset PDCCH monitoring according to the search space set having group index 0, if provided by the searchSpaceGroupIdList.

[0294] In one embodiment, the wireless device receives some symbols P switch In one embodiment, the delay time may be provided by a searchSpaceSwitchDelay (e.g., as shown in FIG. 27) having P switch The minimum value of may be determined based on UE processing capabilities and numerology. switch The value indicated for searchSpaceSwitchDelay may be equal to or greater than the minimum value corresponding to the numerology of the BWP and the UE processing capability of the wireless device.

[0295] In one embodiment, the wireless device may be provided with a timer value by searchSpaceSwitchTimer (e.g., in units of slots, as shown in FIG. 27) for the serving cell for which the wireless device is provided with searchSpaceGroupIdList, or for the set of serving cells provided by cellGroupsForSwitchList, if provided. The wireless device may decrement the timer value by one after each slot based on a reference SCS configuration μ, which is the smallest SCS configuration μ among all configured DL BWPs in the serving cell, or in the set of serving cells. The wireless device may maintain the reference SCS configuration during the timer decrement procedure.

[0296] In an embodiment, searchSpaceSwitchTimer may be defined as a value in slots for monitoring PDCCH in the active DL BWP of the serving cell before moving to a default search space group (e.g., search space group 0). For a 15 kHz SCS, a valid timer value may be one of {1, ..., 20}. For a 30 kHz SCS, a valid timer value may be one of {1, ..., 40}. For a 60 kHz SCS, a valid timer value may be one of {1, ..., 80}. In one embodiment, the base station may configure the same timer value for all serving cells in the same CellGroupForSwitch.

[0297] As shown in Figure 30A, the wireless device may monitor the PDCCH on the first SSS group (e.g., the first SSS group, or the SSS with group index 0, or the first SSG) based on the configuration of the SSS group of the BWP of the cell. The wireless device may be provided with a SearchSpaceSwitchTrigger with the position of the search space set group switch flag field for the serving cell in DCI format 2_0. The SearchSpaceSwitchTrigger may be configured based on the example embodiment of Figure 28.

[0298] In one embodiment, the wireless device may receive a DCI (e.g., the first DCI of FIG. 30A having DCI format 2_0) in a first slot (e.g., T1). The DCI may indicate an SSS group switch for the cell, for example, when a value of an SSS group switch flag field in DCI format 2_0 is 1. In response to receiving the DCI, the wireless device may start monitoring a PDCCH according to a second SSS group (e.g., the second SSS group, or the SSS with group index 1, or the second SSG) and stop monitoring a PDCCH on the first SSS group (or the SSS with group index 0 of the serving cell). The wireless device may start monitoring a PDCCH on the second SSS group (e.g., the second SSS group, or the SSS with group index 1, or the second SSG) and stop monitoring a PDCCH on the first SSS group in a second slot (e.g., T2). The wireless device may start monitoring a PDCCH on the second SSS group (e.g., the second SSS group, or the SSS with group index 1, or the second SSG) and stop monitoring a PDCCH on the first SSS group in a second slot (e.g., T2). switch The second slot may determine the SSS group switching gap based on at least P after the last symbol of the PDCCH having DCI format 2_0 (e.g., the first slot). switch Based on receipt of the DCI, the wireless device may set (or reset) the timer value of the search space switch timer at the second slot (e.g., T2) to the value provided by searchSpaceSwitchTimer.

[0299] In one embodiment, the wireless device may monitor a PDCCH on a second SSS group (e.g., a second SSS group, or an SSS with group index 1, or a second SSG) based on the configuration of the SSS group of the BWP of the cell. The wireless device may be provided with a location of a search space set group switch flag field for the serving cell in DCI format 2_0 by SearchSpaceSwitchTrigger. The wireless device may receive a DCI. If the DCI may indicate an SSS group switch for the cell, e.g., a value of the search space set group switch flag field in DCI format 2_0 is 0, the wireless device may monitor a PDCCH according to a search space set with group index 0 and may stop monitoring a PDCCH according to a search space set with group index 1 for the serving cell. The wireless device may start monitoring a PDCCH according to a search space set with group index 0 and may start monitoring a PDCCH according to a search space set with group index 1 for the serving cell after at least the P symbol after the last symbol of the PDCCH with DCI format 2_0. switch At the first slot, which is a symbol, monitoring of the PDCCH may be stopped according to a search space set with group 1.

[0300] As shown in FIG. 30A, while monitoring the PDCCH on the second SSG and when the searchSpaceSwitchTimer executes, the wireless device may receive a DCI indicating a downlink assignment, or an uplink grant, or common control information. The wireless device may process the DCI accordingly (e.g., receive a PDSCH, transmit a PUSCH, or receive common control information, etc.). The timer may expire at a third slot (e.g., T3). In response to expiration of the timer, the wireless device may start monitoring the PDCCH of the serving cell according to the first SSG (e.g., a search space set with group index 0) and stop monitoring the PDCCH according to the second SSG of the serving cell at the start of a fourth slot (e.g., T4). The fourth slot may be at least P1 slot after the third slot at which the searchSpaceSwitchTimer expires. switch It can be a symbol.

[0301] In one embodiment, the wireless device is configured to monitor the Group-Common-PDCCH for the Slot-Format-Indicator (SFI) if a SearchSpaceSwitchTrigger for the serving cell, e.g., SearchSpaceSwitchTrigger, is not provided and the SlotFormatIndicator is not present in the configuration parameters of the SlotFormatIndicator. In response to the SearchSpaceSwitchTrigger not being provided, the DCI format 2_0 may not include an SSS group switch flag field. When the SearchSpaceSwitchTrigger is not provided and the wireless device detects a DCI format by monitoring a PDCCH according to a first SSS group (e.g., a search space set with group index 0), the wireless device may start monitoring a PDCCH according to a second SSS group (e.g., a search space set with group index 1) and may stop monitoring a PDCCH for the serving cell according to the first SSS group. The wireless device may start monitoring a PDCCH according to the second SSS group and may monitor the PDCCH for at least the PSS group after the last symbol of the PDCCH having the DCI format. switch The wireless device may stop monitoring the PDCCH according to the first SSS group at the first slot that is a symbol. The wireless device may set (or restart) a timer value to a value provided by searchSpaceSwitchTimer if the wireless device detects a DCI format by monitoring the PDCCH in any search space set.

[0302] In one embodiment, the wireless device may not provide a SearchSpaceSwitchTrigger for the serving cell. When a SearchSpaceSwitchTrigger is not provided, if the wireless device monitors the PDCCH for the serving cell according to the first SSS group (e.g., a search space set with group index 1), the wireless device starts monitoring the PDCCH for the serving cell according to the second SSS group (e.g., a search space set with group index 0) and starts monitoring the PDCCH for the serving cell according to the second SSS group (e.g., a search space set with group index 0) for at least one PDCCH for the serving cell according to the first SSS group (e.g., a search space set with group index 1) after the slot in which the timer expires or, if a search space set is provided for the wireless device to monitor the PDCCH to detect DCI format 2_0, after the last symbol of the remaining channel occupancy period for the serving cell indicated by DCI format 2_0. switch The PDCCH may stop monitoring the PDCCH according to the first SSS group for the serving cell at the beginning of the first slot, which is a symbol.

[0303] In one example, the wireless device may determine the slot and symbol in the slot at which to start or stop PDCCH monitoring according to a search space set for a serving cell for which searchSpaceGroupIdList is provided, or for a set of serving cells if cellGroupsForSwitchList is provided, based on the smallest SCS configuration μ, if any, among all configured DL BWPs in the serving cell or set of serving cells and in the serving cell for which the wireless device receives a PDCCH and detects a corresponding DCI format 2_0, triggering the start or stop of PDCCH monitoring according to the search space set.

[0304] In one embodiment, the wireless device may perform a PDCCH skipping based power saving operation. Figure 31 illustrates an example of a PDCCH skipping based power saving operation.

[0305] In one example, the base station may send one or more RRC messages including configuration parameters of a PDCCH for the BWP of the cell to the wireless device (e.g., based on the example embodiments described above with respect to FIG. 27 and / or FIG. 28). Based on the configuration parameters of the PDCCH, the wireless device may monitor the PDCCH on the BWP. The BWP may be a downlink BWP in an active state. The wireless device may activate the BWP based on the example embodiments described above with respect to FIG. 23.

[0306] As shown in FIG. 31, the wireless device may receive a first DCI (e.g., a first DCI) at a first slot (T1) indicating to skip (or stop) monitoring the PDCCH within a time window. The time value of the time window may be indicated by the first DCI and / or may be configured by one or more RRC messages. In response to receiving the first DCI, the wireless device may stop monitoring the PDCCH on the BWP. Stopping monitoring the PDCCH on the BWP may include stopping monitoring the PDCCH on one or more SSS groups configured on the BWP. The wireless device may maintain an active state of the BWP. The first DCI may not indicate an active BWP switch. In one embodiment, during the time window (or when a timer associated with the time window is running), the base station may not transmit the PDCCH to the wireless device.

[0307] As shown in Figure 31, when the time window expires (e.g., at the second slot T2), the wireless device may resume PDCCH monitoring on the BWP. Based on the resumption of PDCCH monitoring, the wireless device may receive a second DCI (e.g., a second DCI) scheduling TB via the PDSCH. The wireless device may receive a TB via the PDSCH scheduled by the second DCI. In one embodiment, in response to the expiration of the time window, the base station may transmit the second DCI to the wireless device.

[0308] In one example, a wireless device may perform multiple power saving operations. The multiple power saving operations may include a PDCCH skipping based power saving operation (e.g., based on the example embodiment described above with respect to FIG. 31), a BWP switching based power saving operation (e.g., based on the example embodiment described above with respect to FIG. 23 and / or FIG. 26), and an SSG switching based power saving operation (e.g., FIG. 30A and / or FIG. 30B). Different power saving operations may provide different power saving gains.

[0309] In one embodiment, the PDCCH skipping based power saving operation may not include active BWP switching. The wireless device may skip PDCCH monitoring for a certain duration while maintaining the active state of the BWP on the cell. Thus, no realignment of the RF chain and / or beam direction is required. In one embodiment, the power saving operation based on PDCCH skipping on the active BWP (e.g., FIG. 31) may provide better power saving gain than the power saving operation based on active BWP switching (e.g., FIG. 23) or dormant BWP switching (e.g., FIG. 26). The BWP switching based power saving may include active BWP switching, which may take several milliseconds and / or may require the wireless service to realign the RF chain and / or beam direction. In the case of the PDCCH skipping based power saving operation, the wireless device may take several symbols, or a slot (or several slots) to stop monitoring the PDCCH, which may result in a higher power saving gain than the BWP switching based power saving operation.

[0310] In one embodiment, the wireless device may take several slots to switch the active BWP on a cell depending on the numerology and the type of wireless device capability. In one embodiment, when the numerology index of the BWP (e.g., source BWP or target BWP) is 0 (e.g., u=0), the wireless device may take 1 slot to switch the active BWP on a cell if the wireless device indicates wireless device capability type 1, or 3 slots if the wireless device indicates wireless device capability type 2. In one embodiment, when the numerology index is 1 (e.g., u=1), the wireless device may take 2 slots to switch the active BWP on a cell if the wireless device indicates wireless device capability type 1, or 5 slots if the wireless device indicates wireless device capability type 2. In one embodiment, when the numerology index is 2 (e.g., u=2), the wireless device may take 3 slots to switch the active BWP on a cell if the wireless device indicates wireless device capability type 1, or 9 slots if the wireless device indicates wireless device capability type 2. In one embodiment, when the numerology index is 3 (e.g., u=3), the wireless device may take 6 slots to switch the active BWP on the cell if the wireless device indicates wireless device capability type 1, or 18 slots if the wireless device indicates wireless device capability type 2.

[0311] In an example embodiment, the wireless device may perform an SSG switching based power saving operation. The wireless device may determine an SSG switching delay (P switch). The wireless device may apply an SSG switching delay to the SSG switching indication. The application delay of the SSG switching indication is used for blind decoding switching from the first SSG to the second SSG, channel estimation, etc., to accommodate blind decoding of DCI. The SSG switching delay ranges from 10 to 52 symbols depending on the base station configuration (e.g., based on the exemplary embodiment described above with reference to FIG. 30A and / or FIG. 30B). Compared to the SSG switching based power saving operation, the PDCCH skipping based power saving operation may require less application delay to apply the PDCCH skipping indication. The application delay of the PDCCH skipping indication may be used to accommodate blind decoding PDCCH. The application delay may be several symbols, or several slots (e.g., one slot in some cases). Thus, in some cases, the PDCCH skipping based power saving operation may provide a higher power saving gain than the SSG switching based power saving operation.

[0312] In one embodiment, a wireless device may perform different power saving operations for different cells when configured with multiple cells (or carrier aggregation, CA). In one embodiment, a wireless device may perform a BWP switching (or active / dormant BWP switching) based power saving operation on a first cell when the wireless device has no data transmission on the first cell. The wireless device may perform an SSG switching based power saving operation on a second cell when the wireless device has few data transmissions on the second cell. The wireless device may perform a PDCCH skipping based power saving operation on a third cell when the wireless device has no data transmission on a third cell, and the wireless device may have data transmissions on the third cell soon. Different power saving operations may provide different power saving gains, e.g., for different data transmission needs / requirements, in different cases.

[0313] In existing technologies, a base station may transmit an SCell dormancy indication and / or an SSG switching indication to wireless devices of different cells (or cell groups) via different DCIs. The base station may transmit a first DCI (e.g., DCI format 2_0) indicating SSG switching based power saving for a first cell group. The base station may transmit a second DCI (e.g., DCI format 2_6, or DCI format 1_1 / 0_1) indicating dormant BWP switching based power saving for a second cell group. The base station may transmit a third DCI (e.g., DCI format 1_1 / 0_1) indicating a PDCCH skipping based power saving operation for a third cell group. Using multiple DCIs to transmit different power saving indications for different cell groups may increase the signaling overhead of the base station. By implementing existing technologies, a wireless device may require additional time and processing resources to monitor the PDCCH to receive multiple DCIs indicating different power saving operations for different cell groups. This increases power consumption by the wireless device for monitoring and receiving multiple DCIs. Thus, there is a need to reduce the signaling overhead of a base station for transmitting power save indications for multiple cells and / or reduce the power consumption of a wireless device for receiving the power save indications. In an exemplary embodiment, a base station may transmit an RRC message to a wireless device including configuration parameters of multiple cell groups and multiple PS operations. The base station may transmit a DCI including multiple cell group specific PS indications, each PS indication indicating one of multiple power save operations configured by the base station. Based on receiving the DCI, the wireless device may perform cell group specific power save operations for the multiple cell groups. Each of the cell group specific power save operations may be performed with a separate and / or independent application delay. The exemplary embodiment may reduce the signaling overhead for the PS indications for multiple cells because multiple DCIs may not be required to configure power save operations for multiple cell groups. The exemplary embodiment may also reduce the power consumption of a wireless device for receiving the PS indications for multiple cells.

[0314] 32 illustrates an example of a configuration of multiple power saving operations. In one example, a base station may transmit one or more RRC messages to a wireless device including configuration parameters for multiple (or lists) power saving operations on multiple cells. The multiple power saving operations may include one or more first power saving operations associated with a dormant BWP switch, one or more second power saving operations associated with an SSG switch, one or more third power saving operations associated with PDCCH skipping, etc.

[0315] In an example embodiment, as shown in FIG. 32, a first power saving operation of the plurality of power saving operations (e.g., a first entry of the list) may indicate a switch from a non-dormant BWP on the cell to a dormant BWP. A second power saving operation of the plurality of power saving operations (e.g., a second entry of the list) may indicate a switch from a dormant BWP on the cell to a non-dormant BWP. A third power saving operation of the plurality of power saving operations (e.g., a third entry of the list) may indicate a switch from a first (non-dormant) SSG to a second (non-dormant) SSG on the active BWP of the cell. A fourth power saving operation of the plurality of power saving operations (e.g., a fourth entry of the list) may indicate a switch from a dormant SSG to a non-dormant SSG on the active BWP of the cell. A fifth power saving operation of the plurality of power saving operations (e.g., a fifth entry of the list) may indicate a switch from a non-dormant SSG to a dormant SSG on the active BWP of the cell. A sixth power saving operation of the plurality of power saving operations (e.g., a sixth entry of the list) may indicate stopping (or skipping) monitoring the PDCCH for a first number of slots on the active BWP of the cell. A seventh power saving operation of the plurality of power saving operations (e.g., a seventh entry of the list) may indicate stopping (or skipping) monitoring the PDCCH for a second number of slots on the active BWP of the cell. An eighth power saving operation of the plurality of power saving operations (e.g., an eighth entry of the list) may indicate stopping (or skipping) monitoring the PDCCH for a third number of slots on the active BWP of the cell.

[0316] Based on the exemplary embodiment, the base station may flexibly determine multiple power saving operations for the wireless device. In one embodiment, if the wireless device does not support PDCCH skipping-based power saving operation, the base station may not configure the sixth, seventh, and / or eighth entries, etc. in FIG. 32. In one embodiment, if the wireless device does not support SSG switching-based power saving operation, the base station may not configure the third, fourth, and / or fifth entries in FIG. 32. In one embodiment, if the wireless device does not support a pause BWP switching-based power saving operation, the base station may not configure the first and second entries in FIG. 32. The configuration of a wireless device-specific power saving operation list may enable the base station to transmit a DCI indicating a power saving operation from the wireless device's power saving operation list. The exemplary embodiment may reduce signaling overhead for power saving operation indication.

[0317] FIG. 33 illustrates an example of cell grouping for multiple power saving operations. In one example, a base station may transmit one or more RRC messages including configuration parameters of multiple (or list) power saving operations on multiple cells to a wireless device. The list or multiple power saving operations may be implemented based on the example embodiment of FIG. 32. A plurality of cells may be grouped into several cell groups for power saving operation indication. As shown in FIG. 33, the multiple cells may include cell 1, cell 2, cell 3, cell 4, cell 5, cell 6, etc. The base station may group the multiple cells into several cell groups including a first cell group (first cell group) including cell 1 and cell 2, etc., a second cell group (second cell group) including cell 3 and cell 4, etc., and a third cell group (third cell group) including cell 4 and cell 5, etc. A cell of the multiple cells may uniquely belong to one of several cell groups. A cell group may include one or more cells.

[0318] In an example embodiment, the one or more RRC messages may include a location parameter indicating that a PS indication of the plurality of PS indications in the DCI corresponds to a respective cell group of a number of cell groups. Each one of the plurality of PS indications may correspond to a respective cell group of a number of cell groups. The PS indication of the plurality of PS indications in the DCI may indicate one of a list (or plurality) of power saving operations (e.g., based on an example embodiment described above with respect to FIG. 32). The DCI may be transmitted over PDCCH resources. The DCI may be based on an example embodiment described above with respect to FIG. 24.

[0319] FIG. 34 illustrates an example embodiment of cell grouping by DCI and PS indication based on cell group based on the example embodiment described above with respect to FIG. 32 and / or FIG. 33. In one example, a base station may transmit a DCI including a plurality of PS indications for a number of cell groups to a wireless device. A first PS indication (first PS indication) of the plurality of PS indications may correspond to a first cell group of the number of cell groups based on a first location parameter associated with the first cell group indicating that the first PS indication is associated with the first cell group. A second PS indication (second PS indication) of the plurality of PS indications may correspond to a second cell group of the number of cell groups based on a second location parameter associated with the second cell group indicating that the second PS indication is associated with the second cell group. A third PS indication (third PS indication) of the plurality of PS indications may correspond to a third cell group of the number of cell groups based on a third location parameter associated with the third cell group indicating that the third PS indication is associated with the third cell group, etc.

[0320] In an exemplary embodiment, the wireless device may receive a DCI including a plurality of PS indications, as shown in FIG. 34. In one example, the wireless device may determine a first PS indication for a first cell group based on a first location parameter. In response to the first PS indication indicating the first entry (first entry) of FIG. 32, the wireless device may switch to a respective dormant BWP for each (activated) cell of the first cell group (e.g., cell 1, cell 2 based on the exemplary embodiment described above with respect to FIG. 33). The wireless device may switch to a dormant BWP based on the exemplary embodiment described above with respect to FIG. 26. In one example, the wireless device may determine a second PS indication for a second cell group based on a second location parameter. In response to the second PS indication indicating the third entry (third entry) of FIG. 32, the wireless device may switch to a respective second SSG on an active BWP for each (activated) cell of the second cell group (cell 3 and / or cell 4 based on FIG. 33). The wireless device may switch from the first SSG to the second SSG based on the exemplary embodiment described above with respect to FIG. 30A and / or FIG. 30B. In one example, the wireless device may determine an Nth PS indication for the Nth cell group based on the Nth location parameter. In response to the Nth PS indication indicating the sixth entry (6th entry) of FIG. 32, the wireless device may skip (or stop) PDCCH monitoring on the active BWP of each (activated) cell of the Nth cell group. The wireless device may skip (or stop) PDCCH monitoring for the first number of slots based on the exemplary embodiment described above with respect to FIG. 31.

[0321] In one embodiment, the PS indication of the DCI may include a bit number indicating one of multiple PS actions configured by the base station. In one embodiment, the PS indication may be a 3-bit DCI field if there are eight entries in the list as shown in Figure 32. In one embodiment, the PS indication may be a 2-bit DCI field if there are four entries in the list as shown in Figure 32, etc.

[0322] FIG. 35 illustrates an example embodiment of power saving operations for a plurality of cells based on the example embodiments described above with respect to FIG. 32, FIG. 33, and / or FIG. 34. In one example, a wireless device may receive one or more RRC messages from a base station including configuration parameters for a plurality of PS operations on a plurality of cells. The plurality of PS operations may be implemented based on the example embodiment described above with respect to FIG. 32. The plurality of cells may be grouped into a number of cell groups based on the example embodiment described above with respect to FIG. 33. The configuration parameters may include, for each cell group of the number of cell groups, a respective location parameter indicating a power saving indication (PSI) of a plurality of PSIs in a DCI corresponding to the cell group.

[0323] In an example embodiment, as shown in Figure 35, a wireless device may receive a DCI in a first slot T1 that includes a plurality of PSIs, each of which may indicate one of a plurality of PS actions comprised of one or more RRC messages.

[0324] In an example embodiment, based on receiving the DCI, the wireless device may determine, for a first cell group (first cell group), a first PSI (first PSI) from the multiple PSIs based on a first location parameter associated with the first cell group. In one example, the first PSI may indicate PDCCH skipping (for the first number of slots), for example, if the first PSI indicates the sixth entry of the PS action list of FIG. 32. Based on the first PSI indicating PDCCH skipping, the wireless device may stop monitoring the PDCCH on the active BWP of each (active) cell of the first cell group at the second slot T2 (for the first number of slots). The application delay (e.g., the gap between T2 and T1) may be configured in one or more RRC messages and / or may be indicated by the DCI. The application delay may be predefined as a fixed value.

[0325] In an example embodiment, based on receiving the DCI, the wireless device may determine, for a second cell group (second cell group), a second PSI (second PSI) from the plurality of PSIs based on a second location parameter associated with the second cell group. In one example, the second PSI may indicate a switch from the first SSG to the second SSG, for example, when the second PSI indicates the third entry of the list of PS operations of FIG. 32. Based on the second PSI indicating the SSG switch, the wireless device may stop monitoring the PDCCH via the first SSG at the third slot T3 and start monitoring the PDCCH via the second SSG on the active BWP of each (active) cell of the second cell group. The application delay (e.g., the gap between T3 and T1) may be configured in one or more RRC messages and / or may be indicated by the DCI. The application delay may be predefined as a fixed value.

[0326] In an example embodiment, based on receiving the DCI, the wireless device may determine a third PSI (third PSI) for a third cell group (third cell group) from the plurality of PSIs based on a third location parameter associated with the third cell group. In one example, the third PSI may indicate a dormant transition, for example, when the third PSI indicates a first entry of the PS action list of FIG. 32. Based on the third PSI indicating a dormant transition, the wireless device may switch from an active BWP to a dormant BWP for each (active) cell of the third cell group at the fourth slot T4. The application delay (e.g., a gap between T4 and T1) may be configured in one or more RRC messages and / or may be indicated by the DCI. The application delay may be predefined as a fixed value.

[0327] Based on the example embodiments of Figures 32, 33, 34, and / or 35, a base station may transmit a DCI including multiple cell group specific PS indications to a wireless device, where each PS indication indicates one of multiple power saving operations configured by the base station. Based on receiving the DCI, the wireless device may perform cell group specific power saving operations for the multiple cell groups. Each of the cell group specific power saving operations may be performed with a separate and / or independent application delay. The example embodiments may reduce signaling overhead for PS indications for multiple cells. The example embodiments may reduce power consumption of the wireless device for receiving PS indications for multiple cells.

[0328] In the exemplary embodiment, the wireless device may not be able to perform different PS operations on different cells (or cell groups) simultaneously. The wireless device may not be able to process multiple PS indications (for different cells / cell groups) received in a single DCI. The exemplary embodiment may reduce the complexity of processing PS indications for different cell groups by receiving different PS indications in different DCIs.

[0329] In the existing technology, the first cell group grouped for the SSG switching indication and the second cell group grouped for the dormant BWP switching indication are configured separately and / or independently by an RRC message. When indicating PDCCH skipping for multiple cells, by reusing the existing technology, it may be difficult for the wireless device to determine whether to apply PDCCH skipping to the cell group belonging to the first cell group or the cell group belonging to the second cell group. In one embodiment, the cell grouping for the PDCCH skipping indication may have different considerations (e.g., PDCCH monitoring periodicity, time offset, etc.) than the cell grouping for the SSG switching indication or the dormant BWP switching indication. Reusing the cell group configured for the SSG switching indication or the dormant BWP switching indication for the PDCCH skipping indication may increase the power consumption of the wireless device and / or increase the data transmission delay (e.g., on some cells if the cells are in the cell group indicated for PDCCH skipping). When the PDCCH skipping indication is applied to multiple cells, the power consumption and / or the data transmission delay need to be improved.

[0330] FIG. 36 illustrates an example embodiment of cell grouping for different PS operations based on one or more of the example embodiments described above with respect to FIG. 32, FIG. 33, FIG. 34, and / or FIG. 35. In one example, a base station may send one or more RRC messages to a wireless device including configuration parameters of a plurality (or list) of PS operations on a plurality of cells (e.g., cell 1, cell 2, ...). The list or plurality of PS operations may be implemented based on the example embodiment of FIG. 32. The plurality of cells may be grouped into a PS operation specific number of cell groups for each of the plurality of PS operations.

[0331] In an example embodiment, for a first PS operation (e.g., PDCCH skipping based PS operation), the multiple cells may be grouped into a first number of cell groups including a first group including cell 1, cell 2, etc., a second group including cell 3, cell 4, etc., and a third group including cell 5, cell 6, etc.

[0332] In an example embodiment, for a second PS operation (e.g., SSG switching based PS operation), the multiple cells may be grouped into a first number of cell groups including a first group including cell 1, cell 3, etc., a second group including cell 2, cell 5, etc., and a third group including cell 4, cell 6, etc.

[0333] In an example embodiment, for a third PS operation (e.g., dormancy transition based PS operation), the multiple cells may be grouped into a first number of cell groups including a first group including cell 1, cell 5, etc., a second group including cell 2, cell 4, etc., and a third group including cell 3, cell 6, etc.

[0334] In an exemplary embodiment, a cell may belong to different cell groups, for example, cell 1 may belong to a first cell group of a first number of cell groups, a first cell group of a second number of cell groups, and a first cell group of a third cell group. The first cell group, the second cell group, and the third cell group are configured separately and / or independently. Separately and / or independently grouping cells for different PS operations may flexibly allow the base station to indicate PS operations for different cells.

[0335] As shown in FIG. 36, cell 1 and cell 2 may be grouped into the same cell group (e.g., the first group of the first cell group) for a first PS operation indication. Cell 1 and cell 3 may be grouped into the same cell group for a second PS operation indication. Cell 1 and cell 5 may be grouped into the same cell group for a third PS operation indication. Cells grouped into different cell groups for different PS operations may allow a base station to flexibly indicate different PS operations for cells with reduced signaling overhead.

[0336] In an example embodiment, the one or more RRC messages may include a location parameter indicating that a PS indication of the plurality of PS indications in the DCI corresponds to a respective cell group of a number of cell groups. The certain cell groups may be a first cell group. The certain cell groups may be a second cell group. The certain cell groups may be a third cell group, etc. The wireless device may determine whether the certain cell groups are a first cell group, a second cell group, or a third cell group based on whether the PS indication indicates a first PS operation, a second PS operation, or a third PS operation. In an example embodiment, each of the plurality of PS indications may correspond to a respective cell group of a number of cell groups. The PS indication of the plurality of PS indications in the DCI may indicate one of a PDCCH skipping-based PS operation, an SSG switching-based PS operation, a dormancy transition-based PS operation, etc. The DCI may be transmitted over a PDCCH resource. The DCI may be based on the example embodiment described above with respect to FIG. 24.

[0337] FIG. 37 illustrates an example embodiment of PS operations for multiple cells based on the example embodiment described above with respect to FIG. 36. In one example, a base station may transmit one or more RRC messages to a wireless device including configuration parameters for multiple PS operations on multiple cells. The multiple PS operations may be implemented based on the example embodiment described above with respect to FIG. 32. The multiple cells may be grouped into cell groups based on the example embodiment described above with respect to FIG. 36. The configuration parameters may include, for each cell group, a respective location parameter indicating a power saving indication (PSI) of multiple PSIs in a DCI corresponding to the cell group.

[0338] In an example embodiment, the plurality of cells may be grouped into a first cell group associated with a first PS operation of the plurality of PS operations, the plurality of cells may be grouped into a second cell group associated with a second PS operation of the plurality of PS operations, and the plurality of cells may be grouped into a third cell group associated with a third PS operation of the plurality of PS operations.

[0339] In an example embodiment, as shown in FIG. 37, the wireless device may receive, at a first slot T1, a first DCI including a first PS indication for a cell group. The first PS indication may indicate a first PS operation (e.g., a PDCCH skipping-based PS operation). The wireless device may determine, based on the first PS indication indicating the first PS operation, that the cell group is associated with (or from) a first cell group associated with the first PS operation. In response to the first PS operation being a PDCCH skipping-based PS operation, the wireless device may skip (or stop) monitoring a PDCCH on the first cell based on the first cell belonging to the cell group of the first cell group. In response to the first PS operation being a PDCCH skipping-based PS operation, the wireless device may skip (or stop) monitoring a PDCCH on each active cell of the cell group of the first cell group.

[0340] In an example embodiment, as shown in FIG. 37, the wireless device may receive, in a second slot T2, a second DCI including a second PS indication for the cell group. The second PS indication may indicate a second PS operation (e.g., an SSG switching based PS operation). The wireless device may determine, based on the second PS indication indicating the second PS operation, that the cell group is based on a second cell group associated with the second PS operation. In response to the second PS operation being an SSG switching based PS operation, the wireless device may switch PDCCH monitoring from a first SSG on the first cell to a second SSG based on a first cell belonging to the cell group of the second cell group. In response to the second PS operation being an SSG switching based PS operation, the wireless device may switch PDCCH monitoring from a first SSG on the first cell to a second SSG of each active cell of the cell group of the second cell group.

[0341] In an example embodiment, as shown in FIG. 37, the wireless device may receive a third DCI including a third PS indication for the cell group in a third slot T3. The third PS indication may indicate a third PS operation (e.g., a dormancy transition-based PS operation). The wireless device may determine, based on the third PS indication indicating the third PS operation, that the cell group is based on a third cell group associated with the third PS operation. In response to the third PS operation being a dormancy transition-based PS operation, the wireless device may transition to a dormant state on the first cell based on the first cell belonging to the cell group of the third cell group. In response to the third PS operation being a dormancy transition-based PS operation, the wireless device may transition to a dormant state for each awake cell of the cell group of the third cell group.

[0342] Based on the example embodiment of FIG. 37, a wireless device may be PS operation specific cell group of multiple configured cells. The wireless device may apply PS operation to the cell group associated with the PS operation. The cells may belong to different cell groups associated with different PS operations, for example, when the wireless device supports different PS operations on the cells. The example embodiment may reduce signaling overhead of PS indication for multiple cells when the wireless device supports different PS operations on the cells.

[0343] FIG. 38 illustrates an example embodiment of PS operation for multiple cells based on the example embodiment described above with respect to FIG. 36. In one example, a base station may send one or more RRC messages to a wireless device including configuration parameters for multiple PS operations on multiple cells. The multiple PS operations may be implemented based on the example embodiment described above with respect to FIG. 32. The multiple cells may be grouped into cell groups based on the example embodiment described above with respect to FIG. 36.

[0344] In an example embodiment, the plurality of cells may be grouped into a first cell group associated with a first PS operation of the plurality of PS operations. The plurality of cells may be grouped into a second cell group associated with a second PS operation of the plurality of PS operations. The plurality of cells may be grouped into a third cell group associated with a third PS operation of the plurality of PS operations. The plurality of cells may be grouped based on the example embodiment described above with respect to FIG.

[0345] In an example embodiment, as shown in FIG. 38, a wireless device may receive a DCI including a PS indication indicating one of a plurality of PS operations. The wireless device may determine whether the PS indication indicates a first PS operation of the plurality of PS operations. In response to the PS indication indicating the first PS operation, the wireless device may determine a first cell group associated with the first PS operation from a plurality of cell groups (e.g., including a first cell group, a second cell group, and / or a third cell group). In response to the cell belonging to the first cell group, the wireless device may apply the first PS operation to the cell. Applying the first PS operation on the cell may include skipping (or stopping) PDCCH monitoring on the cell for some slots based on the example embodiment described above with respect to FIG. 31.

[0346] In one example, a wireless device may receive a DCI including a PS indication indicating one of a plurality of PS operations. The wireless device may determine whether the PS indication indicates a second PS operation of the plurality of PS operations. In response to the PS indication indicating the second PS operation, the wireless device may determine a second cell group associated with the second PS operation from a plurality of cell groups (e.g., including a first cell group, a second cell group, and / or a third cell group). In response to the cell belonging to the second cell group, the wireless device may apply the second PS operation to the cell. Applying the second PS operation on the cell may include switching PDCCH monitoring on the cell from a first SSG to a second SSG based on the example embodiments described above with respect to FIG. 30A and / or FIG. 30B.

[0347] In one example, a wireless device may receive a DCI including a PS indication indicating one of a plurality of PS operations. The wireless device may determine whether the PS indication indicates a third PS operation of the plurality of PS operations. In response to the PS indication indicating the third PS operation, the wireless device may determine a third cell group associated with the third PS operation from a plurality of cell groups (e.g., including the first cell group, the second cell group, and / or the third cell group). In response to a cell belonging to the third cell group, the wireless device may apply the third PS operation on the cell. Applying the third PS operation to the cell may include transitioning to a dormant state of the cell according to the example embodiment described above with reference to FIG. 26.

[0348] In one embodiment, a wireless device may perform different power saving operations for different cells when configured with multiple cells (or carrier aggregation, CA). In one embodiment, a wireless device may perform a BWP switching (or active / dormant BWP switching) based power saving operation on a first cell when the wireless device has no data transmission on the first cell. The wireless device may perform an SSG switching based power saving operation on a second cell when the wireless device has few data transmissions on the second cell. The wireless device may perform a PDCCH skipping based power saving operation on a third cell when the wireless device has no data transmission on a third cell, and the wireless device may have data transmissions on the third cell soon. Different power saving operations may provide different power saving gains, e.g., for different data transmission needs / requirements, in different cases.

[0349] In an existing technique, a wireless device may receive a PS indication (e.g., in a DCI having a DCI format) indicating one of a plurality of PS operations on a cell. In one embodiment, based on an existing technique, a base station may use a first number of bits to indicate one of a second number of PS operations. The first number may be a fixed value based on the second number. For example, a fixed 3-bit value may be used to represent eight different numbers corresponding to eight different PS operations. However, a wireless device may not support (or prefer) some of the plurality of PS operations on some cells. In one embodiment, if a cell is configured with a higher numerology (e.g., u=5 or 6), the wireless device may not support SSG switching based PS operation on the cell. In one embodiment, the wireless device may not support PDCCH skipping based power saving on the cell due to hardware limitations of PDCCH decoding. In one embodiment, if a cell is configured with a single BWP, the wireless device may not support dormancy transition based PS operation on a cell configured with a single BWP. Using a fixed number of bits to indicate multiple PS operations on a cell in a DCI having a DCI format may unnecessarily increase signaling overhead and / or increase power consumption of wireless devices that may support a limited number of multiple PS operations. There is a need to reduce signaling overhead and / or reduce power consumption of wireless devices.

[0350] In an example embodiment, the wireless device may indicate to the base station a first plurality of PS operations (e.g., a list of PS operations) that are supported / preferred (or not supported or not preferred) by the wireless device from a second plurality of PS operations, e.g., in a first RRC message including an indication of information of the wireless device's radio access capabilities. The second plurality of PS operations may include PDCCH monitoring skipping, SSG switching, SCell dormancy transition, etc. For example, the indication may include one or more parameter indications of whether one or more respective PS operations of the first plurality of PS operations are supported. The base station may appropriately transmit configuration parameters of the plurality of PS operations (e.g., list) based on the indication, e.g., in a second RRC message. The base station may transmit to the wireless device DCI indicating a PS operation from the plurality of PS operations based on the configuration parameters. A DCI configured in a DCI format (e.g., based on the exemplary embodiment described above with respect to FIG. 24) may include a DCI field indicating a PS operation (supported by the wireless device) (e.g., skipping PDCCH monitoring for a certain duration, switching PDCCH monitoring from a first SSG to a second SSG, transitioning to a dormant state of an SCell, etc.) and having a bit size based on an indication of a radio access capability of the wireless device for a power saving operation. For example, the bit size of the DCI field may be flexibly configured by the base station (and correspondingly determined by the wireless device) based on the radio access capability of the wireless device for a power saving operation and / or a configuration parameter configured by the base station. The exemplary embodiment may reduce signaling overhead for the PS indication of the wireless device and / or reduce power consumption of the wireless device for receiving the PS indication.

[0351] FIG. 39 illustrates an exemplary embodiment of a PS operation. In one embodiment, the wireless device can transmit information indicating one or more configuration parameters of the PS operation to the base station UE. The UE information can be transmitted from the wireless device to the base station, for example, via a UE Capability Information RRC message (e.g., a UECapabilityInformation IE). The UE Capability Information RRC message can be a response to a capability request RRC message received from the base station (e.g., a UECapabilityEnquiry IE in the first RRC message, as shown in FIG. 39).

[0352] In an example embodiment, the UE information may be a UE assistance information RRC message (e.g., a UEAssistanceInformation IE). The UE assistance information RRC message may be a response to an RRC reconfiguration IE received from the base station. The wireless device may transmit UE assistance information indicating its preference for one or more of the multiple PS operations in RRC_CONNECTED. The wireless device may be configured to transmit UE assistance information including, for example, having a PS operation preference for the multiple PS operations and a change in the PS operation preference, if configured to do so. The PS operation preference may include a preference for PDCCH skipping based PS operation from the multiple PS operations on the cell / cell group. The PS operation preference may include a preference for SSG switching based PS operation from the multiple PS operations on the cell / cell group. The PS operation preference may include a preference for dormancy transition based PS operation from the multiple PS operations on the cell / cell group.

[0353] In an exemplary embodiment, a configuration parameter (e.g., in a UE Capability Information RRC message) may indicate whether the wireless device supports PDCCH skip based PS operation (e.g., per BWP, per cell, or per cell group, or per band / band combination). The PDCCH skip based PS operation may be implemented based on the exemplary embodiments described above with respect to FIG. 31 and / or FIG. 32. A parameter of the configuration parameter set to a first value may indicate that the wireless device supports PDCCH skip based PS operation (or that the wireless device supports PDCCH skip on an active BWP). A parameter of the configuration parameter set to a second value may indicate that the wireless device does not support PDCCH skip based PS operation (or that the wireless device does not support PDCCH skip on an active BWP). As an example, the band may be a frequency band based on the exemplary embodiment described above with respect to FIG. 10A. A plurality of cells may be configured within the frequency band. The per-band indication of whether the wireless device supports PDCCH skip based PS operation may include a first parameter corresponding to a first frequency band and a second parameter corresponding to a second frequency band. The first parameter may indicate whether the wireless device supports PDCCH skip based PS operation on a cell of a first plurality of cells deployed (or configured) in a first frequency band. The second parameter may indicate whether the wireless device supports PDCCH skip based PS operation on a cell of a second plurality of cells deployed (or configured) in a second frequency band. By implementing the example embodiment, a per-band (or per-frequency band) indication of whether the wireless device supports PDCCH skip based PS operation may reduce signaling overhead of capability indication in terms of power saving operation.

[0354] In an example embodiment, the configuration parameters may indicate whether the wireless device supports SSG switching based PS operation (e.g., per BWP, per cell, per cell group, or per band / band combination). The SSG switching based PS operation may be implemented based on the example embodiments described above with respect to FIG. 30A and / or FIG. 32. The parameter of the configuration parameters set to a first value may indicate that the wireless device supports SSG switching based PS operation (or that the wireless device supports SSG switching on an active BWP). The parameter of the configuration parameters set to a second value may indicate that the wireless device does not support SSG switching based PS operation (or that the wireless device does not support SSG switching on an active BWP). As an example, the band may be a frequency band based on the example embodiments described above with respect to FIG. 10A. A plurality of cells may be configured within the frequency band. The per-band indication of whether the wireless device supports SSG switching based PS operation may include a first parameter corresponding to a first frequency band and a second parameter corresponding to a second frequency band. The first parameter may indicate whether the wireless device supports SSG switching based PS operation on a cell of a first plurality of cells deployed (or configured) in a first frequency band. The second parameter may indicate whether the wireless device supports SSG switching based PS operation on a cell of a second plurality of cells deployed (or configured) in a second frequency band. By implementing an example embodiment, a per-band (or per-frequency band) indication of whether the wireless device supports SSG switching based PS operation may reduce signaling overhead of capability indications in terms of power saving operation.

[0355] In an exemplary embodiment, the configuration parameters may indicate whether the wireless device supports dormancy transition-based PS operation (e.g., per BWP, per cell, per cell group, or per band / band combination). The dormancy-based PS operation may be implemented based on the exemplary embodiments described above with respect to FIG. 26A and / or FIG. 32. The parameter of the configuration parameters set to a first value may indicate that the wireless device supports dormancy-based PS operation. The parameter of the configuration parameters set to a second value may indicate that the wireless device does not support dormancy-based PS operation. As an example, the band may be a frequency band based on the exemplary embodiment described above with respect to FIG. 10A. A plurality of cells may be configured within the frequency band. The band-by-band indication of whether the wireless device supports dormancy-based PS operation may include a first parameter for the first frequency band and a second parameter for the second frequency band. The first parameter may indicate whether the wireless device supports dormancy-based PS operation on a cell of a first plurality of cells deployed (or configured) in the first frequency band. The second parameter may indicate whether the wireless device supports dormancy-based PS operation on cells of a second plurality of cells deployed (or configured) in the second frequency band. By implementing an example embodiment, a per-band (or per-frequency band) indication of whether the wireless device supports dormancy-based PS operation may reduce signaling overhead of capability indications in terms of power saving operation.

[0356] In one example, a parameter for indicating capability of PDCCH skipping based power saving, a parameter for indicating capability of SSG switching based power saving, and / or a parameter for indicating capability of dormancy based power saving may be indicated separately and / or independently in the configuration parameters of the UE Capability Information RRC message. Exemplary embodiments may enable a wireless device to separately indicate its radio access capabilities with respect to different power saving operations and / or enable a base station to flexibly configure power saving parameters for a wireless device.

[0357] In accordance with an example embodiment, a wireless device may indicate to a base station configuration parameters (e.g., via UE capability information and / or UE assistance information) of multiple PS operations supported (reported or preferred) by the wireless device. Example embodiments may enable a base station to know which PS operations the wireless device supports or prefers on a cell / cell group / frequency band.

[0358] In an example embodiment, based on the configuration parameters of the PS operations reported by the wireless device in the UE Capability Information RRC message, as shown in Figure 39, the base station may send second configuration parameters of the PS operations (e.g., the configuration of the PSI shown in Figure 39) to the wireless device. The second configuration parameters may be implemented based on the example embodiment described above with respect to Figure 32.

[0359] In an example embodiment, a configuration parameter (e.g., reported in a UE Capability Information RRC message) may indicate that the wireless device supports (or prefers) PDCCH skip based PS operation. Thus, the base station may configure multiple PS operations including PDCCH skip based PS operation in an RRC message including the configuration parameter for PDCCH skip based PS operation, e.g., based on the example embodiment described above with respect to FIG. 31. In one example, the configuration parameter may indicate that the wireless device does not support (or prefers) PDCCH skip based PS operation. Thus, the base station may configure multiple PS operations without PDCCH skip based PS operation.

[0360] In an example embodiment, a configuration parameter (e.g., reported in a UE Capability Information RRC message) may indicate that the wireless device supports (or prefers) SSG switching based PS operation. Thus, the base station may configure multiple PS operations including SSG switching based PS operation, e.g., in an RRC message including the configuration parameter for SSG switching based PS operation according to the example embodiment described above with respect to FIG. 30A. In one example, the configuration parameter may indicate that the wireless device does not support (or prefers) SSG switching based PS operation. Thus, the base station may configure multiple PS operations without SSG switching based PS operation.

[0361] In an example embodiment, a configuration parameter (e.g., reported in a UE Capability Information RRC message) may indicate that the wireless device supports (or prefers) dormant transition based PS operation. Thus, the base station may configure multiple PS operations including dormant transition based PS operation in an RRC message including the configuration parameter dormant transition based PS operation, e.g., based on the example embodiment described above with respect to FIG. 26. In one example, the configuration parameter may indicate that the wireless device does not support (or prefers) dormant transition based PS operation. Thus, the base station may configure multiple PS operations without dormant transition based PS operation.

[0362] In an example embodiment, as shown in FIG. 39, the wireless device may receive a DCI having a DCI format (e.g., based on the example embodiment described above with respect to FIG. 24) including a PS indication field. The PS indication field of the DCI may be referred to as a PDCCH monitoring adaptation indication field, a PDCCH skipping / SSG switching / dormancy indication field, etc. The PS indication field may have a bit size configured based on the wireless device's radio access capability for power saving operation (e.g., based on the UE information indicating one or more PS operations of FIG. 39). Based on the PS indication, the wireless device may determine a first PS action from a plurality of PS actions configured by the base station. The wireless device may apply the first PS action to one or more cells based on the PS indication indicating the first PS action. The first PS action may include at least one of a plurality of PS actions including skipping (or stopping) PDCCH monitoring on one or more cells, switching from a first SSG to a second SSG for PDCCH monitoring on one or more cells, or going into a dormant state on one or more cells.

[0363] In one example, based on the UE Capability Information RRC message indicating that the wireless device supports PDCCH skipping on the active BWP of the cell, the base station (or wireless device) may determine that the PS indication field of the DCI has a first number of bits (e.g., 1). The PS indication field may indicate whether the wireless device skips PDCCH monitoring (for a duration) on the active BWP of the cell. The wireless device may skip PDCCH monitoring of the active BWP (for a duration indicated by the DCI out of a plurality of time durations set by the RRC message) based on the exemplary embodiment described above with respect to FIG. 31. Based on the exemplary embodiment of FIG. 31, the wireless device may resume PDCCH monitoring on the active BWP after the duration.

[0364] In one example, in response to the UE Capability Information RRC message indicating that the wireless device supports SSG switching on the active BWP of the cell, the base station (or wireless device) may determine that the PS indication field of the DCI has a second number of bits (e.g., 1 or 2). The PS indication field may indicate whether the wireless device switches PDCCH monitoring from a first SSG of the SSGs on the active BWP of the cell to a second SSG of the SSGs. The wireless device may switch PDCCH monitoring between SSGs on the active BWP of the cell based on the exemplary embodiment described above with respect to FIG. 30A. Based on the exemplary embodiment of FIG. 30A, the wireless device may switch PDCCH monitoring to a default SSG of the active BWP (e.g., having an SSG index zero) in response to expiration of an SSG switching timer on a non-default SSG of the active BWP (e.g., having an SSG index not equal to zero).

[0365] In one example, in response to the UE Capability Information RRC message indicating that the wireless device supports a dormant indication on the active BWP of the cell, the base station (or wireless device) may determine that the PS indication field of the DCI has a third number of bits (e.g., 3 or 4). The PS indication field may indicate whether the wireless device transitions the cell to a dormant state. The wireless device may transition the cell to a dormant state based on the exemplary embodiment described above with respect to FIG. 26. Based on the exemplary embodiment of FIG. 26, the wireless device may switch the active BWP of the cell to the dormant BWP of the cell in response to transitioning the cell to a dormant state.

[0366] Based on an example embodiment, the wireless device may indicate to the base station a list of PS operations supported / preferred (or not supported or not preferred) by the wireless device, e.g., via an RRC message indicating the wireless device's radio access capability for power saving operations. For example, to indicate the wireless device's radio access capability, the RRC message may include one or more parameters indicating whether one or more respective PS operations of the list of PS operations are supported / preferred by the wireless device. The base station may transmit (e.g., in an RRC message) a configuration parameter of the list of PS operations based on the indication accordingly. The base station may transmit a DCI indicating the PS operations to the wireless device DCI based on the configuration parameter, the DCI having a DCI format including a power saving indication field having a bit size configured based on an indication from the wireless device of one or more supported PS operations. The bit size of the power saving indication field of the DCI may be flexibly configured / determined based on the supported power saving operations reported by the wireless device and / or the configured power saving operations indicated by the base station. The example embodiment may reduce signaling overhead for the PS indication of the wireless device and reduce power consumption of the wireless device for receiving the PS indication.

[0367] In an example embodiment, a wireless device may receive configuration parameters for PS operations for cells. The cells may be grouped into cell groups including a first cell group. The PS operations may include a first PS operation. The first PS operation may include skipping monitoring a PDCCH on the cells. The configuration parameters include a location parameter indicating that a PS indication of a PS indication in a DCI corresponds to the first cell group. The wireless device may receive a DCI including a PS indication. The wireless device may skip monitoring a first PDCCH on the first cell of the cells in response to a first PS indication of a first cell belonging to the first cell group and a first PS operation of the PS operation of the first PS indication in the DCI corresponding to the first cell group.

[0368] According to an example embodiment, the wireless device may skip monitoring the first PDCCH on the first cell using a time window. The wireless device may resume monitoring the first PDCCH on the first cell in response to expiration of the time window. The length of the time window may be indicated by a first configuration parameter of the first PS operation. The first configuration parameter may be included in the configuration parameters.

[0369] According to an example embodiment, the wireless device may maintain an active state of a BWP on the first cell while the wireless device skips monitoring the first PDCCH on the first cell. Maintaining an active state of the BWP may include receiving a transport block via a downlink shared channel of the BWP.

[0370] According to an example embodiment, the PS operation may further include a second PS operation including switching monitoring of the PDCCH from the first SSG to the second SSG. In response to a second PS indication of a second cell belonging to the second cell group and a PS indication in a DCI corresponding to the second cell group, the wireless device may switch monitoring of the PDCCH from the first SSG to the second SSG on the second cell indicating the second PS operation of the PS operation. Switching monitoring of the PDCCH from the first SSG to the second SSG on the second cell may include stopping monitoring of the PDCCH on the first SSG on the active BWP of the second cell and starting monitoring of the PDCCH on the second SSG on the active BWP of the second cell.

[0371] According to an example embodiment, the PS operation may further include a third PS operation including transitioning to a dormant state. The wireless device may transition to a dormant state on the third cell in response to a third PS indication of a third cell belonging to the third cell group and a PS indication in a DCI corresponding to the third cell group indicating the third PS operation of the PS operation. The transition to a dormant state on the third cell may include switching an active BWP of the third cell to a dormant BWP of the third cell including a plurality of BWPs. The plurality of BWPs may include the dormant BWP. The switching to the dormant BWP may include stopping monitoring a PDCCH on the dormant BWP of the third cell, stopping receiving transport blocks via the dormant BWP of the third cell, and transmitting channel state information for the dormant BWP of the third cell.

[0372] According to an example embodiment, a wireless device may activate a first BWP of the multiple BWPs of a first cell based on receiving an activation command indicating activation of the first BWP. The activation command may include at least one of a second DCI indicating a switch from the second BWP of the first cell to the first BWP as an active BWP, a MAC CE indicating activation of the first cell, and / or an RRC message including a cell status indication for the first cell indicating an active state. In response to the activation of the first BWP, the wireless device may monitor a PDCCH on the first BWP of the first cell. Monitoring the PDCCH on the first BWP may include at least one of monitoring the PDCCH via a first SSG of the multiple SSGs on the first BWP and monitoring the PDCCH via a second SSG of the multiple SSGs on the first BWP. Skipping monitoring the first PDCCH on the first cell may include at least one of skipping monitoring the first PDCCH via a first SSG on the first BWP and skipping monitoring the first PDCCH via a second SSG on the first BWP. The multiple SSGs may include a dormant SSG. The dormant SSG may not include a search space. The first SSG may include one or more first search spaces. The second SSG may include one or more second search spaces.

[0373] According to an example embodiment, the configuration parameters may include a first configuration parameter for each search space of the one or more first search spaces, which may include a search space indicator identifying the search space, a control resource set indicator indicating a control resource set associated with the search space, monitoring slot periodicity and offset parameters for PDCCH monitoring over the search space, a duration, a monitoring symbol in slot indicator, a number of candidates, a search space type, and one or more SSG group indices associated with the search space.

[0374] According to an example embodiment, the control resource set may be configured with second configuration parameters including a frequency domain resource configuration parameter, a duration value, a control channel element to resource element group mapping type indication, and a control resource set pool index.

[0375] In an example embodiment, a wireless device may receive configuration parameters for PS operations on cells, where the cells are grouped into cell groups including a first cell group associated with a first PS operation of the PS operations and a second cell group associated with a second PS operation of the PS operations. The wireless device may receive a DCI indicating the PS operation of the PS operations. The wireless device may select a first cell group from the cell groups including the first cell group and the second cell group based on the PS operation being a first PS operation. The wireless device may apply a first PS operation on the first cell based on the first cell belonging to the selected first cell group, including skipping monitoring a downlink control channel on the first cell.

[0376] According to an example embodiment, the first PS action may include skipping monitoring a downlink control channel on the cell.

[0377] According to an example embodiment, the second PS operation includes switching downlink control channel monitoring from a first SSG on the cell to a second SSG. The wireless device can receive a second DCI indicating the second PS operation. The wireless device can determine a second cell group from the cell groups based on the second DCI indicating the second PS operation. The wireless device can apply the second PS operation on the first cell in response to the first cell belonging to the second cell group, the second PS operation including switching downlink control channel monitoring from the first SSG on the first cell to the second SSG on the first cell.

[0378] According to an example embodiment, the PS operation may further include a third PS operation including transitioning the cell to a dormant state. The cell group may further include a third cell group associated with the third PS operation. The wireless device may receive a third DCI indicating the third PS operation. The wireless device may determine a third cell group from the cell groups based on the third DCI indicating the third PS operation. The wireless device may apply the third PS operation on the first cell, including transitioning the first cell to a dormant state, in response to the first cell belonging to the third cell group.

[0379] In an example embodiment, the wireless device may transmit information including a first configuration parameter indicating that the wireless device supports multiple PS operations on a cell, the multiple PS operations including a first PS operation associated with skipping monitoring a PDCCH and a second PS operation associated with switching a PDCCH from a first SSG to a second SSG. The wireless device may receive one or more RRC messages including a second configuration parameter of the multiple PS operations. The wireless device may receive a DCI indicating a first PS operation associated with the first cell and a second PS operation associated with the second cell. The wireless device may apply the first PS operation including skipping monitoring a downlink control channel on the first cell and may apply the second PS operation including monitoring a downlink control channel from the first SST to the second SSG on the second cell. The information may be included in a wireless device capability message. The information may be included in a wireless device assistant message.

Claims

1. 1. A method comprising: A wireless device transmits, to a base station, a radio resource control (RRC) message including information of the wireless device's radio access capabilities. Including, The information includes, for each frequency band, A first parameter indicating whether the wireless device supports skipping of a physical downlink control channel (PDCCH) monitoring for power saving operation; a second parameter indicating whether the wireless device supports switching of PDCCH monitoring between search space groups (SSGs) for the power saving operation; A method comprising:

2. 2. The method of claim 1, further comprising receiving a downlink control information (DCI) having a DCI format including a PDCCH monitoring adaptation field having a bit size based on the first parameter and the second parameter.

3. The method of claim 2 , wherein the PDCCH monitoring adaptation field includes a value indicative of one or more of the power saving operations based on the first parameter and the second parameter.

4. The method of any one of claims 1 to 3, further comprising receiving a first RRC message from the base station indicating a request for the radio access capability of the wireless device, the RRC message being a second RRC message transmitted in response to the request.

5. The method of any one of claims 1 to 3, further comprising receiving, from the base station, a third RRC message including configuration parameters for the power saving operation of the wireless device based on the first parameter and the second parameter.

6. 6. The method of claim 5, wherein the configuration parameters include a plurality of duration values ​​for skipping the PDCCH monitoring based on the first parameter being set to a value indicating that the wireless device supports skipping the PDCCH monitoring.

7. The configuration parameter is based on the second parameter being set to a value indicating that the wireless device supports inter-SSG PDCCH monitoring switching, A plurality of search spaces grouped into SSGs identified by respective SSG indices; A timer value of a timer for switching PDCCH monitoring between the SSGs; The method according to any one of claims 5 to 6, wherein

8. 1. A method comprising: receiving, by a base station, a radio resource control (RRC) message from a wireless device, the radio resource control message including information of a radio access capability of the wireless device; Including, The information includes, for each frequency band, A first parameter indicating whether the wireless device supports skipping of a physical downlink control channel (PDCCH) monitoring for power saving operation; a second parameter indicating whether the wireless device supports switching of PDCCH monitoring between search space groups (SSGs) for the power saving operation; A method comprising:

9. The method of claim 8, further comprising transmitting a downlink control information (DCI) having a DCI format including a PDCCH monitoring adaptation field having a bit size based on the first parameter and the second parameter.

10. The method of claim 9, wherein the PDCCH monitoring adaptation field includes a value indicating one or more of the power saving operations based on the first parameter and the second parameter.

11. A method according to any one of claims 8 to 10, further comprising transmitting to the wireless device a first RRC message indicating a request for the wireless access capability of the wireless device.

12. A method according to any one of claims 8 to 11, further comprising transmitting to the wireless device an indication of multiple duration values ​​for skipping the PDCCH monitoring on a downlink bandwidth portion (BWP) of a cell, based on the first parameter being set to a value indicating that the wireless device supports skipping the PDCCH monitoring.

13. The method of claim 12, further comprising: transmitting to the wireless device a command for transmitting a PDCCH monitoring switch between SSGs based on the second parameter being set to a value indicating that the wireless device supports PDCCH monitoring switch between SSGs. A plurality of search spaces grouped into SSGs identified by respective SSG indices; A timer value of a timer for switching PDCCH monitoring between the SSGs on the downlink BWP of the cell; The method of any one of claims 8 to 12, further comprising transmitting an indication of.

14. An apparatus comprising: one or more processors; A memory storing instructions which, when executed by the one or more processors, cause the apparatus to perform a method according to any one of claims 1 to 13; An apparatus comprising:

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

Images