Method and system for inactivity management in a wireless cellular system

Abstract

A wireless device receives configuration parameters that indicate: a first dormant cell group includes a first cell; a second dormant cell group includes a second cell; and the second cell cross-carrier schedules the first cell. The wireless device receives a dormancy indication that indicates a non-dormant state of the first dormant cell group. In response to the dormancy indication indicating the non-dormant state, the wireless device maintains the first cell in a dormant state based on: the second cell cross-carrier scheduling the first cell, and the second cell being in the dormant state.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 953,849, filed Dec. 26, 2019, and U.S. Provisional Application No. 62 / 962,483, filed Jan. 17, 2020, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0004] Figure 1A And Figure 1B An exemplary mobile communication network in which embodiments of the present disclosure may be implemented is shown.

[0005] Figure 2A And Figure 2B Separate illustrations of a New Radio (NR) user plane and control plane protocol stack are shown.

[0006] Figure 3 Shows an example of a service provided between protocol layers of the NR user plane protocol stack in Figure 2A An example of a service provided between protocol layers of the NR user plane protocol stack is shown.

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

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

[0009] Figure 5A And Figure 5B Separate illustrations of the mapping between logical channels, transport channels, and physical channels for downlink and uplink are shown.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0024] Figure 17A 、 Figure 17B and Figure 17C Shows an example of the MAC sub-header.

[0025] Figure 18A Shows an example of the DL MAC PDU.

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

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

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

[0029] Figure 21A And Figure 21B Shows an example of SCell activation / deactivation MAC CE.

[0030] Figure 22 Shows an example of BWP management according to some embodiments.

[0031] Figure 23A And Figure 23B Shows an example of self-scheduling and cross-carrier scheduling according to some embodiments.

[0032] Figure 24 Shows an example of cell configuration parameters including cross-carrier scheduling configuration according to some embodiments.

[0033] Figure 25 Shows an example of search space configuration according to some embodiments.

[0034] Figure 26 Shows an example of control resource set configuration according to some embodiments.

[0035] Figure 27 Shows an example of transitioning between the quiescent state and non-quiescent state of a cell according to some embodiments.

[0036] Figure 28 Shows an example of cell quiescence management according to some embodiments.

[0037] Figure 29 Is a flowchart of an exemplary method for performing cell quiescence management according to some embodiments.

[0038] Figure 30 Is a flowchart of an exemplary method for performing cell quiescence management according to some embodiments.

[0039] Figure 31 Shows an exemplary flowchart of cell quiescence management according to some embodiments.

[0040] Figure 32 Shows an example of cell quiescence management according to some embodiments.

[0041] Figure 33 Shows an example of cell quiescence management according to some embodiments.

[0042] Figure 34 Shows an example of cell quiescence management according to some embodiments.

[0043] Figure 35Shows an example of cell dormancy management according to some embodiments.

[0044] Figure 36 Is a flowchart of an exemplary method for performing cell dormancy management according to some embodiments.

[0045] Figure 37 Shows an example of cell dormancy management according to some embodiments.

[0046] Figure 38 Shows an example of DRX configuration according to some embodiments.

[0047] Figure 39A And Figure 39B Shows an example of power saving operations based on wake-up indication and sleep indication according to some embodiments.

[0048] Figure 40 Shows an example of power saving operations based on layer 1 (DCI) according to some embodiments.

[0049] Figure 41 Shows an example of a wireless communication system with multiple TRPs / panels according to some embodiments.

[0050] Figure 42 Is a flowchart of an exemplary method for performing power saving operations using multiple TRPs / panels according to some embodiments.

[0051] Figure 43 Is a flowchart of an exemplary method for performing power saving operations using multiple TRPs / panels according to some embodiments.

[0052] Figure 44 Shows an exemplary power saving operation using multiple TRPs / panels according to some embodiments.

[0053] Figure 45 Shows an exemplary power saving operation using multiple TRPs / panels according to some embodiments.

[0054] Figure 46 Shows an exemplary DCI format including power saving information for multiple TRPs / panels according to some embodiments.

[0055] Figure 47 Shows an exemplary DCI format including power saving information for multiple TRPs / panels according to some embodiments.

[0056] Figure 48 Shows an exemplary DCI format including power saving information for multiple TRPs / panels according to some embodiments.

[0057] Figure 49 An exemplary DCI format including power saving information for multiple TRPs / panels according to some embodiments is shown.

[0058] Figure 50 An exemplary power saving operation using multiple TRPs / panels according to some embodiments is shown.

[0059] Figure 51 A flowchart of an exemplary method for performing a power saving operation using multiple TRPs / panels according to some embodiments. Detailed Description

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

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

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

[0063] In the present disclosure, "a", "an", and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase after the term "may" is an example of one of the various suitable possibilities that may or may not be used in one or more embodiments of the various embodiments. As used herein, the terms "comprising" and "consisting of" enumerate one or more components of the element being described. The term "comprising" is interchangeable with "including" and does not exclude components not listed from being included in the element being described. In contrast, "consisting of" provides a complete enumeration of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "at least partially based on" rather than, for example, "only based on". As used herein, the term "and / or" represents any possible combination of the listed elements. For example, "A, B, and / or C" can represent A; B; C; A and B; A and C; B and C; or A, B, and C.

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

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

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

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

[0068] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs a defined function and has a defined interface to other elements. The modules described in the present disclosure can be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware having biological elements), or a combination thereof, all of which can be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language that is configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement a module using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages such as assembly, C, C++. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC hardware description language (VHDL) or Verilog, which configure connections between less functional internal hardware modules on the programmable device. The techniques mentioned are often used in combination to achieve the result of a functional module.

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

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

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

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

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

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

[0075] In addition to the three-sector site, other implementations of the base station are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectorized site with more or fewer than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, a baseband processing unit coupled to a number of remote radio heads (RRHs), and / or a repeater or relay node for extending the coverage area of a donor node. The baseband processing unit coupled to the RRH may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be centralized in a pool of baseband processing units or virtualized. The repeater node may amplify and replay the radio signals received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signals received from the donor node to eliminate noise before amplifying and replaying the radio signals.

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

[0077] The 3rd Generation Partnership Project (3GPP) was established in 1998 to provide global specification standardization for mobile communication networks similar to the Figure 1A mobile communication network 100 herein. So far, 3GPP has developed specifications for three generations of mobile networks: the 3rd generation (3G) network known as the Universal Mobile Telecommunications System (UMTS), the 4th generation (4G) network known as Long Term Evolution (LTE), and the 5th generation (5G) network known as the 5G System (5GS). The embodiments of the present disclosure are described with reference to the RAN of the 3GPP 5G network referred to as the Next Generation RAN (NG-RAN). These embodiments may be applicable to the RANs of other mobile communication networks, such asFigure 1A RANs in [0000235], RANs of early 3G and 4G networks, and those of future networks not yet specified (e.g., 3GPP 6G networks). The NG-RAN implements the 5G radio access technology known as New Radio (NR) and can be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0078] Figure 1B Another exemplary mobile communication network 150 is shown in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. As Figure 1B shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UEs 156). These components may be implemented and operated in the same or similar manner as the corresponding components described with respect to Figure 1A

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

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

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

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

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

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

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

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

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

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

[0089] Figure 2A andFigure 2B Examples of the NR user plane and NR control plane protocol stacks for the Uu interface between the UE 210 and the gNB 220 are shown, respectively. Figure 2A and Figure 2B The protocol stacks shown in Figure 1B can be the same as or similar to those for the Uu interface between, for example, the UE156A and the gNB 160A shown in

[0090] Figure 2A An NR user plane protocol stack including five layers implemented in the UE 210 and the gNB 220 is shown. At the bottom of the protocol stack, the physical layers (PHY) 211 and 221 can provide transport services to the higher layers of the protocol stack and can correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include the medium access control layers (MAC) 212 and 222, the radio link control layers (RLC) 213 and 223, the packet data convergence protocol layers (PDCP) 214 and 224, and the service data application protocol layers (SDAP) 215 and 225. These four protocols can together constitute layer 2 or the data link layer of the OSI model.

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

[0092] PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from the intended source. PDCPs 214 and 224 can perform retransmission of undelivered packets, in-order delivery and reordering of packets, and removal of packets received repeatedly due to, for example, handover within the gNB. PDCPs 214 and 224 can perform packet duplication to increase the likelihood of a packet being received, and remove any duplicate packets at the receiver. Packet duplication can be applied to services that require high reliability.

[0093] Although Figure 3 not shown in, PDCPs 214 and 224 can 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 be connected to two cells or more generally to two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is a split bearer when a single radio bearer (such as one of the radio bearers provided by PDCPs 214 and 224 as a service to SDAPs 215 and 225) is handled by the cell groups in a dual-connectivity. PDCPs 214 and 224 can map / demap split radio bearers between RLC channels belonging to cell groups.

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

[0095] MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing can include: multiplexing data units belonging to the one or more logical channels into transport blocks (TBs) delivered to / from PHYs 211 and 221 and demultiplexing the data units from the transport blocks. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling can be performed at the gNB 220 (at MAC 222) for both downlink and uplink. MACs 212 and 222 can be configured to perform error correction by means of hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of UE210 by means of logical channel prioritization, and / or padding. MACs 212 and 222 can support one or more parameter sets and / or transmission timings. In one example, mapping restrictions in logical channel prioritization can control which parameter set and / or transmission timing a logical channel can use. As Figure 3 shown, MACs 212 and 222 can provide logical channels as services to RLCs 213 and 223.

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

[0097] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4A shown is the downlink data flow through the NR user plane protocol stack for three IP packets ( n , n+1 and m ) that result in the generation of two TBs at the gNB 220. The uplink data flow through the NR user plane protocol stack can be similar to the Figure 4A depicted downlink data flow.

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

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

[0100] Figure 4B shown. In LTE, the MAC sub-header can be fully located at the beginning of the MAC PDU. The NR MAC PDU structure can reduce the processing time and the associated latency because the MAC PDU sub-header can be calculated before the complete MAC PDU is assembled.

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

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

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

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

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

[0105] - Broadcast control channel (BCCH), which is used to carry system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), where the system information messages can be used by the UE to obtain information on how the cell is configured and how to operate within the cell;

[0106] - Common control channel (CCCH), which is used to carry control messages and random access;

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

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

[0109] Transport channels are used between the MAC layer and the PHY layer and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

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

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

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

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

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

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

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

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

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

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

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

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

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

[0123] Figure 2B illustrates an exemplary NR control plane protocol stack. As Figure 2B shown, the NR control plane protocol stack can use the same / similar first four protocol layers as the exemplary NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has Radio Resource Control (RRC) 216 and 226 and NAS protocol 217 and 237 at the top of this NR control plane protocol stack.

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

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

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

[0127] In the RRC connected 602, the UE has an established RRC context and can have at least one RRC connection with the base station. The base station can be similar to one of the following: Figure 1A the one or more base stations included in the RAN 104 depicted in Figure 1B or one of the gNB 160 or ng-eNB 162 depicted in Figure 2A and Figure 2BThe gNB 220 depicted therein; or any other base station described in the present disclosure. The base station connected to the UE 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. When in the RRC connected state 602, the mobility of the UE may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The serving base station of the UE 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 the RRC connected state 602 to the RRC idle state 604 via the connection release procedure 608, or to the RRC inactive state 606 via the connection deactivation procedure 610.

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

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

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

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

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

[0133] The base station storing the RRC context for the UE or the UE's last serving base station can be referred to as the anchor base station. The anchor base station can maintain the RRC context for the UE at least for the duration that the UE remains within the RAN notification area of the anchor base station and / or for the duration that the UE remains in RRC inactive 606.

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

[0135] In NR, physical signals and physical channels (as discussed regarding Figure 5A and Figure 5B ) can be mapped to orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal sub-carriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-orthogonal amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols), and divided into F parallel symbol streams. The F parallel symbol streams can be considered as if they are in the frequency domain and used as the input to an inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of the F sine basis functions corresponding to F orthogonal sub-carriers. The output of the IFFT block can be F time domain samples representing the sum of F orthogonal sub-carriers. The F time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be scrambled using an FFT block before being processed by the IFFT block. This operation produces a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse operation can be performed on the OFDM symbol at the receiver using an FFT block to recover the data mapped to the source symbols.

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

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

[0138] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Parameter sets with a higher subcarrier spacing have a shorter time slot duration and, correspondingly, more time slots per subframe. Figure 7 An exemplary transmission structure of time slot duration and time slots per subframe related to the parameter set is shown (for ease of illustration, Figure 7 the parameter set with a subcarrier spacing of 240 kHz is not shown). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the time slot duration and can start at any OFDM symbol and continue for as many symbols as required for transmission. These partial time slot transmissions can be referred to as micro time slot or sub time slot transmissions.

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

[0140] Figure 8 A single parameter set is shown as being used across the entire bandwidth of the NR carrier. In other exemplary configurations, multiple parameter sets can be supported on the same carrier.

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

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

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

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

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

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

[0147] The base station may semi-statically configure a default downlink BWP for the UE within the set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP to 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.

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

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

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

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

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

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

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

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

[0156] When using CA, one of the aggregated cells in the aggregated cells for the UE can be referred to as the primary cell (PCell). The PCell can be the serving cell to which the UE is initially connected at RRC connection establishment, re - establishment, and / or handover. The PCell can provide the UE with NAS mobility information and security inputs. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE can be referred to as secondary cells (SCells). In one example, the SCell can be configured after the PCell is configured for the UE. For example, the SCell can be configured through the RRC connection re - configuration procedure. In the downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DLSCC). In the uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

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

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

[0159] Figure 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. In Figure 10B the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs in this example: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as a primary SCell (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In one example, if Figure 10B the aggregated cells depicted in

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0213] The UE may determine the radio resources and / or uplink transmission power of the preamble 1341 and / or the transport block 1342 included in the 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 of the preamble 1341 and / or the transport block 1342. The time-frequency resources (e.g., PRACH) used for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel for monitoring and / or receiving the Msg B 1332.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0229] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 can be part of a mobile communication network, such as Figure 1A the mobile communication network 100 shown,Figure 1B The mobile communication network 150 or any other communication network shown. Figure 15 Only one wireless device 1502 and one base station 1504 are shown, but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same or similar configurations as those Figure 15 shown.

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

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

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

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

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

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

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

[0237] Processing system 1508 and / or processing system 1518 may be respectively connected to one or more peripheral devices 1516 and one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, Internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the one or more peripheral devices described above. The processing system 1518 in the wireless device 1502 may receive power from a power supply and / or may be configured to distribute power to other components in the wireless device 1502. The power supply may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. Processing system 1508 and / or processing system 1518 may be respectively connected to GPS chipset 1517 and GPS chipset 1527. GPS chipset 1517 and GPS chipset 1527 may be configured to provide the geographical location information of wireless device 1502 and base station 1504, respectively.

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

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

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

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

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

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

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

[0245] In one example, a MAC SDU can be a bit string whose length is byte-aligned (e.g., a multiple of eight bits). In one example, the MAC SDU can be included in the MAC PDU starting from the first bit. A MAC CE can be a bit string whose length is byte-aligned (e.g., a multiple of eight bits). A MAC sub-header can be a bit string whose length is byte-aligned (e.g., a multiple of eight bits). In one example, the MAC sub-header can be placed directly in front of the corresponding MAC SDU, MAC CE, or padding. The MAC entity can ignore the value of the reserved bits in the DL MAC PDU.

[0246] In one example, a MAC PDU can include one or more MAC subPDUs. The MAC subPDUs in the one or more MAC subPDUs can include: only the MAC sub-header (including padding); the MAC sub-header and the MAC SDU; the MAC sub-header and the MAC CE; and / or the MAC sub-header and the padding. The MAC SDU can have a variable size. The MAC sub-header can correspond to the MAC SDU, MAC CE, or padding.

[0247] In one example, when the MAC sub-header corresponds to a MAC SDU, a variable-size MAC CE, or padding, the MAC sub-header can include: an R field with a one-bit length; an F field with a one-bit length; an LCID field with a multi-bit length; and / or an L field with a multi-bit length.

[0248] Figure 17A An example of a MAC sub-header with an R field, an F field, an LCID field, and an L field is shown. In Figure 17A the exemplary MAC sub-header, the length of the LCID field can be six bits, and the length of the L field can be eight bits. Figure 17B An example of a MAC sub-header with an R field, an F field, an LCID field, and an L field is shown. In Figure 17B the exemplary MAC sub-header, the length of the LCID field can be six bits, and the length of the L field can be sixteen bits. When the MAC sub-header corresponds to a fixed-size MAC CE or padding, the MAC sub-header can include: an R field with a two-bit length and an LCID field with a multi-bit length. Figure 17C An example of a MAC sub-header with an R field and an LCID field is shown. In Figure 17C the exemplary MAC sub-header, the length of the LCID field can be six bits, and the length of the R field can be two bits.

[0249] Figure 18AAn example of a DL MAC PDU is shown. Multiple MAC CEs (such as MAC CE 1 and 2) can be placed together. A MAC subPDU including a MAC CE can be placed before any MAC subPDU containing a MAC SDU or a MAC subPDU containing padding. Figure 18B An example of a UL MAC PDU is shown. Multiple MAC CEs (such as MAC CE 1 and 2) can be placed together. A MAC subPDU including a MAC CE can be placed after all MAC subPDUs including a MAC SDU. Additionally, a MAC subPDU can be placed before a MAC subPDU containing padding.

[0250] In one example, a MAC entity of a base station can transmit one or more MAC CEs to a MAC entity of a wireless device. Figure 19 An example of multiple LCIDs that can be associated with one or more MAC CEs is shown. The one or more MAC CEs can include at least one of the following: SP ZP CSI-RS resource set activation / deactivation MAC CE; PUCCH spatial relation activation / deactivation MAC CE; SP SRS activation / deactivation MAC CE; SP CSI reporting on PUCCH activation / deactivation MAC CE; TCI state indication for UE-specific PDCCH MAC CE; TCI state indication for UE-specific PDSCH 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 duplication activation / deactivation MAC CE. In one example, a MAC CE, such as a MAC CE transmitted by a MAC entity of a base station to a MAC entity of a wireless device, can have an LCID in the MAC sub-header corresponding to the MAC CE. Different MAC CEs can have different LCIDs in the MAC sub-header corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC sub-header can indicate that the MAC CE associated with the MAC sub-header is a long DRX command MAC CE.

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

[0252] In carrier aggregation (CA), two or more component carriers (CC) can be aggregated. The wireless device can use the CA technology to receive or transmit simultaneously on one or more CC depending on the capabilities of the wireless device. In one example, the wireless device can support CA for contiguous CC and / or for non-contiguous CC. The CC can be organized into cells. For example, the CC can be organized into one primary cell (PCell) and one or more secondary cells (SCell). When configured with CA, the wireless device can have one RRC connection with the network. During RRC connection establishment / re-establishment handover, the cell providing the NAS mobility information can be the serving cell. During the RRC connection re-establishment / handover procedure, the cell providing the security input can be the serving cell. In one example, the serving cell can represent the PCell. In one example, the base station can transmit one or more messages including the configuration parameters of multiple one or more SCell to the wireless device depending on the capabilities of the wireless device.

[0253] When configured with CA, the base station and / or the wireless device can adopt the activation / deactivation mechanism of the SCell to improve the battery or power consumption of the wireless device. When the wireless device is configured with one or more SCell, the base station can activate or deactivate at least one of the one or more SCell. After the configuration of the SCell, the SCell can be deactivated immediately, unless the SCell state associated with the SCell is set to "activated" or "quiescent".

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

[0255] When a wireless device receives a SCell activation / deactivation MAC CE for activating a SCell, the wireless device may activate the SCell. In response to activating the SCell, the wireless device may perform operations including the following: SRS transmission on the SCell; CQI / PMI / RI / CRI reporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; and / or PUCCH transmission on the SCell. In response to activating the SCell, the wireless device may start or restart a first SCell timer associated with the SCell (e.g., sCellDeactivationTimer ). The wireless device may start or restart the first SCell timer in a time slot when it has received a SCell activation / deactivation MAC CE for activating the SCell. In one example, in response to activating the SCell, 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 example, in response to activating the SCell, the wireless device may trigger a PHR.

[0256] When a wireless device receives a SCell activation / deactivation MAC CE for deactivating an activated SCell, the wireless device may deactivate the activated SCell. In one example, when a first SCell timer associated with the activated SCell (e.g., sCellDeactivationTimer ) expires, the wireless device may deactivate the activated SCell. In response to deactivating the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In one example, in response to deactivating 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 example, in response to deactivating 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 empty the HARQ buffer associated with the activated SCell.

[0257] When the SCell is deactivated, the wireless device may not perform operations including the following: transmitting SRS on the SCell; reporting CQI / PMI / RI / CRI for the SCell; transmitting on the UL-SCH on the SCell; transmitting on the RACH on the SCell; monitoring at least one first PDCCH on the SCell; monitoring at least one second PDCCH for the SCell; and / or transmitting PUCCH on the SCell. When at least one first PDCCH on the activated SCell indicates an uplink grant or a downlink assignment, the wireless device may restart a first SCell timer associated with the activated SCell (e.g., sCellDeactivationTimer ). In one example, when at least one second PDCCH on the serving cell that schedules the activated SCell (e.g., the PCell or SCell configured with PUCCH, i.e., the PUCCH SCell) indicates an uplink grant or a downlink assignment for the activated SCell, the wireless device may restart a first SCell timer associated with the activated SCell (e.g., sCellDeactivationTimer ). In one example, when the 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.

[0258] Figure 21A An example of an octet SCell activation / deactivation MAC CE is shown. A first MAC PDU sub-header with a first LCID (e.g., '111010' as shown in Figure 19 ) may identify an octet SCell activation / deactivation MAC CE. An octet SCell activation / deactivation MAC CE may have a fixed size. An octet SCell activation / deactivation MAC CE may include a single octet. The single octet may include a first number of C fields (e.g., seven) and a second number of R fields (e.g., one). Figure 21B An example of a four-octet SCell activation / deactivation MAC CE is shown. A second MAC PDU sub-header with a second LCID (e.g., '111001' as shown in Figure 19 ) may identify a four-octet SCell activation / deactivation MAC CE. A four-octet SCell activation / deactivation MAC CE may have a fixed size. A four-octet SCell activation / deactivation MAC CE may include four octets. The four octets may include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., 1).

[0259] In Figure 21Aand / or Figure 21B In, if the SCell with SCell index i has been configured, then C i field may indicate the activation / deactivation status of the SCell with SCell index i. In one example, when the C i field is set to one, the SCell with SCell index i can be activated. In one example, when the C i field is set to zero, the SCell with SCell index i can be deactivated. In one example, if there is no SCell configured with SCell index i, then the wireless device may ignore the C i field. In Figure 21A and Figure 21B , the R field may indicate a reserved bit. The R field may be set to zero.

[0260] A base station (gNB) may configure a wireless device (UE) with an uplink (UL) bandwidth part (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 at least a DL BWP for the wireless device (i.e., there may be no UL BWP in UL) to enable BA on the SCell. For the PCell, the initial active BWP may be the first BWP for initial access. For the SCell, the first active BWP may be the second BWP, which is configured for the wireless device to operate on the SCell when the SCell is activated. In paired spectrum (e.g., FDD), the base station and / or the wireless device may independently switch the DL BWP and the UL BWP. In unpaired spectrum (e.g., TDD), the base station and / or the wireless device may simultaneously switch the DL BWP and the UL BWP.

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

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

[0263] Figure 22 An example of BWP switching on an SCell is shown. In one example, the wireless device may receive at least one RRC message from the base station, the at least one RRC message including the parameters of the SCell and one or more BWP configurations associated with the SCell. The RRC message may include: an RRC connection reconfiguration message (e.g., RRCReconfiguration ); an RRC connection reestablishment message (e.g.,RRCRestablishment ); and / or an RRC connection setup message (e.g., RRCSetup . Among the one or more BWPs, at least one BWP can be configured as a first active BWP (e.g., BWP 1), and one BWP is configured as a default BWP (e.g., BWP 0). The wireless device can receive a MAC CE in the nth time slot to activate the SCell. The wireless device can start an SCell deactivation timer (e.g., sCellDeactivationTimer ), and start CSI-related actions for the SCell, and / or start CSI-related actions for the first active BWP of the SCell. The wireless device can start monitoring the PDCCH on BWP 1 in response to activating the SCell.

[0264] In one example, in response to receiving DCI indicating a DL assignment on BWP 1, the wireless device can start restarting the BWP inactivity timer (e.g., m ) in the bwp-InactivityTimer th time slot. When the BWP inactivity timer expires, the wireless device can switch back to the default BWP (e.g., BWP 0) as the active BWP in the s th time slot. When sCellDeactivationTimer expires, the wireless device can deactivate the SCell and / or stop the BWP inactivity timer.

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

[0266] In one example, on the inactive BWP of each activated serving cell configured with a BWP, the MAC entity can: not transmit on the UL-SCH; not transmit on the RACH; not monitor the PDCCH; not transmit the PUCCH; not transmit the SRS, not receive the DL-SCH; clear any configured downlink assignments and configured uplink grants of configured grant type 2; and / or suspend any configured uplink grants of configured type 1.

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

[0268] In one example, for a primary cell, the default DL BWP among the configured DL BWPs may be provided to the wireless device by a higher layer parameter Default-DL-BWP (Default - DL - BWP). If the default DL BWP is not provided to the wireless device by the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In one example, a timer value for the primary cell may be provided to the wireless device by a higher layer parameter bwp-InactivityTimer If configured, the wireless device may increment the timer at intervals of every 1 millisecond for frequency range 1 or every 0.5 millisecond for frequency range 2 (if running), provided that during the interval, if the wireless device fails to detect DCI format 1_1 for paired spectrum operation, or if the wireless device fails to detect DCI format 1_1 or DCI format 0_1 for unpaired spectrum operation.

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

[0270] In one example, if a wireless device is configured with a first active DL BWP on a secondary cell or carrier by means of the higher layer parameter Active-BWP-DL-SCell, and is configured with a first active UL BWP by means of the higher layer parameter Active-BWP-UL-SCell, the wireless device may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the corresponding first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0271] In one example, when the gNB and the wireless device support BWP operation, the gNB may transmit one or more DCIs on the first active BWP of the first serving cell, where the one or more DCIs indicate self-scheduling performed on the first active BWP, or the one or more DCIs indicate cross-carrier scheduling of the second active BWP of the second serving cell. Figure 23A and Figure 23B illustrates an example of self-scheduling and cross-carrier scheduling when multiple BWPs are configured in a cell.

[0272] Figure 23A illustrates an example of self-scheduling in the case where multiple BWPs are configured. In one example, a base station (e.g., gNB) may transmit one or more messages to a wireless device, the one or more messages including configuration parameters of multiple cells (e.g., CC1, CC2). The one or more messages (e.g., RRC messages) include a serving cell configuration IE (e.g., ServingCellConfig, as Figure 24 shown) for configuring (adding or modifying) the wireless device to have a serving cell (which may be the SpCell or SCell of the MCG or SCG), where the serving cell configuration IE further includes a PDCCH configuration IE (e.g., PDCCH- ServingCellConfig (PDCCH-serving cell configuration)) and / or a cross-carrier scheduling configuration (e.g., CrossCarrierSchedulingConfig ) IE. The cross-carrier scheduling configuration IE may include configuration parameters of the cross-carrier scheduling configuration. The configuration parameters may include scheduling cell information (e.g., s chedulingCellinfo ), and the scheduling cell information includes parameters indicating a first set of cell self-scheduling (e.g., cif-Presence (cif-existence)). In one example, the configuration parameters may further indicate that a cell may include multiple BWPs (e.g., BWP1, BWP2). In one example, in each cell, at most one of the multiple BWPs may be active. In Figure 23AIn an example, BWP1 in CC1 and BWP1 in CC2 are active, and BWP2 in CC1 and BWP2 in CC2 are inactive. In one example, when CC1 and CC2 are active, the wireless device can monitor the first PDCCH candidates on BWP1 of CC1 to detect one or more first DCIs for downlink assignments on BWP1 of CC1 or uplink grants for the uplink active BWP of CC1. The wireless device can monitor the second PDCCH candidates on BWP1 of CC2 to detect one or more second DCIs for downlink assignments on BWP1 of CC2 or uplink grants for the uplink active BWP of CC2. Monitoring multiple PDCCH candidates on the active BWPs of different cells separately or independently can enable flexible cell management. In one example, monitoring multiple PDCCH candidates on the active BWPs of different cells may not be efficient for control channel resource utilization and / or UE battery usage.

[0273] In one example, in the case of being configured with cross-carrier scheduling and multiple BWPs, a base station (e.g., gNB) can transmit a DCI for the second active BWP of the second cell on the first active BWP of the first cell, and the DCI indicates a downlink assignment or an uplink grant on the second active BWP of the second cell. Monitoring the second cell on the first cell can reduce the control channel resources on the second cell, and / or can reduce UE battery usage.

[0274] Figure 23B An example of cross-carrier scheduling configured with multiple BWPs is shown. In one example, the base station can transmit one or more messages to the wireless device, and the one or more messages include configuration parameters indicating that CC2 and / or CC3 are cross-carrier scheduled by CC1. The configuration parameters can include scheduling cell information (e.g., schedulingCellinfo ), and the scheduling cell information includes a second set of parameters (e.g., schedulingcellid and / or cif-InSchedulingCell (in the cif-scheduled cell)), and the second set of parameters indicates that the cell (identified by cif-InSchedulingCell ) is cross-carrier scheduled by another cell identified by schedulingcellid . In one example, the configuration parameters can indicate that a first cif value (indicated by cif- InSchedulingCell ) is associated with CC2 and / or a second cif value is associated with CC3 for cross-carrier scheduling. In one example, the configuration parameters can also indicate that the cell includes multiple BWPs (e.g., BWP1, BWP2). In one example, in a cell, at most one of the multiple BWPs can be active. In Figure 23BIn the example, BWP1 in CC1, BWP1 in CC2, and BWP1 in CC3 are active, and BWP2 in CC1, BWP2 in CC2, and BWP2 in CC3 are inactive. In one example, the wireless device may activate CC1, CC2, and CC3 in response to receiving an SCell activation / deactivation MAC CE indicating the activation of CC1, CC2, and CC3 (e.g., Figure 21A and / or Figure 21B ). In one example, when CC1, CC2, and CC3 are active, the wireless device may monitor the first PDCCH candidate on BWP1 of CC1 for self-scheduling. In one example, the first PDCCH candidate may be in the first common search space (CSS) and / or one or more UE-specific search spaces (USS). In one example, the wireless device may monitor a second PDCCH candidate for CC2 on BWP1 of CC1 (e.g., cross-carrier scheduling). In one example, the second PDCCH candidate may be identified by a first cif value associated with CC2 in the one or more USS. In one example, the wireless device may monitor a third PDCCH candidate for CC3 on BWP1 of CC1. In one example, the third PDCCH candidate may be identified by a second cif value associated with CC3 in the one or more USS. Through cross-carrier scheduling, the gNB may transmit DCI for cross-carrier scheduling of CC2 and CC3 on the active BWP of CC1, e.g., to reduce the control channel resource utilization of the wireless device on CC2 and CC3. The wireless device may reduce blind decoding attempts on CC2 and CC3, and / or may save battery power.

[0275] Figure 24 shows an example of an RRC message for a serving cell configuration (e.g., ServingCellConfig IE). The RRC message for the serving cell configuration may include at least one of the following: TDD configuration parameters, initial BWP ID, multiple DL BWPs, multiple UL BWPs, first active BWP, BWP inactivity timer, SCell deactivation timer, and / or cross-carrier scheduling configuration information (e.g., CrossCarrierSchedulingConfig ). The cross-carrier scheduling configuration information may include one or more cross-carrier scheduling configuration parameters, and the one or more cross-carrier scheduling configuration parameters include scheduling cell information (e.g., schedulingCellinfo ). The scheduling cell information of the second cell including two parameters (e.g., schedulingcellid and cif- InSchedulingCell ) may indicate that the first cell (identified by cif-InSchedulingCell ) is cross-carrier scheduled by the second cell identified by schedulingcellid .

[0276] In one example, the configuration parameters may include one or more PDCCH configuration parameters of a first cell and one or more PDCCH configuration parameters of a second cell. The one or more PDCCH configuration parameters may include: one or more control resource sets; one or more search spaces (configured in SearchSpace IE as shown in Figure 25 ); downlink preemption indication; one or more PUSCH power control parameters; one or more PUCCH power control parameters; and / or one or more SRS power control parameters.

[0277] Figure 25 An example of the configuration of the search space (e.g., SearchSpace IE) is shown. In one example, one or more search space configuration parameters of the search space may include at least one of the following: search space ID ( searchSpaceId ), control resource set ID ( controlResourceSetId ), monitoring time slot period and offset parameters ( mo nitoringSlotPeriodicityAndOffset ), search space duration value ( Duration ), monitoring symbol indication ( monitoringSymbolsWithinSlot ), number of candidates for aggregation level ( nrofCandidates ), and / or SS type indicating common SS type or UE-specific SS type ( searchSpaceType ). The monitoring time slot period and offset parameters may indicate the time slot (e.g., in a radio frame) for PDCCH monitoring and the time slot offset (e.g., related to the start of the radio frame). The monitoring symbol indication may indicate on which symbol(s) of the time slot the wireless device may monitor the PDCCH on the SS. The control resource set ID may identify the control resource set on which the SS may be located.

[0278] In one example, in response to the second cell being cross-carrier scheduled by the first cell, the search space of the second cell is linked to the search space of the first cell having the same search space ID.

[0279] In one example, in response to the second cell being cross-carrier scheduled by the first cell, except for the parameters of the one or more search spaces, there are no one or more PDCCH configuration parameters of the second cell in the configuration parameters of the second cell. In one example, in response to the second cell being cross-carrier scheduled by the first cell, except for the search space ID of the search space and the number of candidates for PDCCH monitoring, there are no one or more search space configuration parameters of the search space of the second cell in the configuration parameters of the search space of the second cell.

[0280] Figure 26Shows an example of the configuration of a Control Resource Set (CORESET). In one example, a base station may transmit one or more configuration parameters of a CORESET to a wireless device. The configuration parameters may include at least one of the following: a CORESET ID that identifies the CORESET, a frequency resource indication, a duration parameter indicating the number of symbols of the CORESET, a CCE-REG mapping type indicator ( Figure 26 (not shown in the figure), a plurality of TCI states, an indicator indicating whether there is a TCI in DCI, etc. The frequency resource indication, which includes several bits (e.g., 45 bits), indicates the frequency domain resources, and each bit of the indication corresponds to a group of 6 RBs, where 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 in the BWP, and so on. A bit set to 1 indicates that the RB group corresponding to that bit belongs to the frequency domain resources of the CORESET. Bits corresponding to a group of RBs that are not fully contained within the BWP in which the CORESET is configured are set to zero.

[0281] In one example, a set of PDCCH candidates to be monitored by a wireless device may be defined in terms of a PDCCH search space set. The search space set includes a CSS set or a USS set. The wireless device monitors PDCCH candidates in one or more of the following search space sets: the MIB in pdcch-ConfigSIB1 or the PDCCH-ConfigCommon in searchSpaceSIB1 or the PDCCH-ConfigCommon in searchSpaceZero Type0-PDCCH CSS set configured for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG; the PDCCH-ConfigCommon in searchSpaceOtherSystemInformation Type0A-PDCCH CSS set configured for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG; the PDCCH-ConfigCommon in ra-SearchSpace Type1-PDCCH CSS set configured for DCI formats with CRC scrambled by RA-RNTI or TC-RNTI on the primary cell; the PDCCH-ConfigCommon in pagingSearchSpace Type2-PDCCH CSS set configured for DCI formats with CRC scrambled by P-RNTI on the primary cell of the MCG; the PDCCH-Config (PDCCH-Configuration) with searchSpaceType = common of SearchSpaceFor DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, and a Type3-PDCCH CSS set configured only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI; and by PDCCH-Config in searchSpaceType = ue-Specific of SearchSpace A USS set configured for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI.

[0282] In one example, a wireless device determines PDCCH monitoring occasions on an active DL BWP based on one or more PDCCH configuration parameters, the one or more PDCCH configuration parameters including: PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring pattern within a slot. For a search space set (SS s ), if , then the wireless device determines that PDCCH monitoring occasions exist in a number of frames and a number of slots. is the number of slots in a frame when the configuration parameter set μ is configured. is the slot offset indicated in the PDCCH configuration parameters. is the PDCCH monitoring period indicated in the PDCCH configuration parameters. The wireless device monitors PDCCH candidates for the search space set starting from slot for consecutive slots and does not monitor PDCCH candidates for the search space set during the next consecutive slots. In one example, the USS at CCE aggregation level is defined by a set of PDCCH candidates for CCE aggregation level . If the wireless device is configured with CrossCarrierSchedulingConfig for the serving cell, then the carrier indicator field value corresponds to the value indicated by CrossCarrierSchedulingConfig .

[0283] In one example, the wireless device decides for a search space set associated with a CORESET that for the active DL BWP of the serving cell corresponding to the carrier indicator field value , in the slot , the PDCCH candidates of the search space set The aggregation level corresponding to The CCE index of is , where, for any CSS ; for USS , , for , for , for , and ; ; in CORESET Among them, Is the number of CCEs, numbered from 0 to ; if the wireless device is configured with a carrier indicator field for the serving cell on which it monitors the PDCCH CrossCarrierSchedulingConfig , then Is the carrier indicator field value; otherwise, including for any CSS, ; , where Is the number of PDCCH candidates that the wireless device is configured to monitor for the search space set Corresponding to the serving cell; for any CSS, The aggregation level of Monitoring; for any CSS, ; for USS, Is all configurations for the CCE aggregation level Of the search space set The maximum value of Value ; and for The RNTI value is C-RNTI.

[0284] 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 for detecting one or more DCIs. The monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. The monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding.

[0285] In one example, a base station and / or a wireless device may activate a secondary cell (SCell) in response to an SCell activation / deactivation MAC CE transmitted by the base station and / or received by the wireless device indicating activation of the SCell (e.g., Figure 21A and / or Figure 21B ). The base station and / or the wireless device may perform one or more actions on the activated SCell, the one or more actions 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. When the SCell is activated, in response to downlink control information transmitted by the base station and / or received by the wireless device indicating a dormant state of the SCell, the base station and / or the wireless device may transition the SCell from an active state (or a non-dormant state as referred to in this specification) to a dormant state. In one example, in response to transitioning the SCell from a dormant state to a non-dormant state, the wireless device may switch from the active BWP of the SCell to the dormant BWP of the SCell (e.g., configured by the base station). In one example, when the SCell is in a dormant state, the wireless device may perform at least one of the following: suppressing monitoring of the PDCCH on the SCell (or suppressing monitoring of the SCell if the SCell is cross-carrier scheduled by another cell); suppressing reception of the PDSCH on the SCell; suppressing transmission of the PUSCH on the SCell; suppressing transmission of the SRS on the SCell; and / or transmitting a CSI report for the SCell (e.g., periodic, aperiodic, and / or semi-persistent). In one example, when a dormant BWP is configured on the SCell and the SCell is transitioned to a dormant state, the wireless device may switch the active BWP of the SCell to the dormant BWP of the SCell and perform at least one of the following: suppressing monitoring of the PDCCH on the dormant BWP of the SCell (or suppressing monitoring of the SCell if the SCell is cross-carrier scheduled by another cell); suppressing reception of the PDSCH on the dormant BWP of the SCell; suppressing transmission of the PUSCH on the dormant BWP of the SCell; suppressing transmission of the SRS on the dormant BWP of the SCell; and / or transmitting a CSI report for the dormant BWP of the SCell (e.g., periodic, aperiodic, and / or semi-persistent). Transitioning the SCell to a dormant state may reduce the power consumption of the wireless device and / or reduce the SCell activation / deactivation state transition delay by using L1 signaling (e.g., DCI).

[0286] In one example, in response to downlink control information (DCI) indicating a non - dormant state of a secondary cell (SCell) transmitted by a base station and / or received by a wireless device, the base station and / or the wireless device may transition the SCell from a dormant state to a non - dormant state. In one example, when there is more available data for transmission / reception, the base station and / or the wireless device may transition the SCell from a dormant state to a non - dormant state by using layer 1 (e.g., DCI) signaling. In one example, when there is less available data for transmission / reception, the base station and / or the wireless device may transition the SCell from a non - dormant state to a dormant state by using layer 1 (e.g., DCI) signaling. Using layer 1 signaling to control the transition between the dormant state and the non - dormant state can improve the signaling transmission latency and the SCell state transition latency.

[0287] Figure 27 An exemplary implementation showing the transition between the dormant state and the non - dormant state on an SCell is presented. In one example, the base station may transmit one or more radio resource control (RRC) messages including configuration parameters of the SCell to the wireless device, where the SCell includes multiple bandwidth parts (BWPs). Among the multiple BWPs, a first BWP (e.g., Figure 27 BWP 3 in Figure 27 ) may be configured as a non - dormant BWP, and / or a second BWP (e.g., Figure 27 BWP 1 in

[0288] ) may be configured as a dormant BWP. In one example, a default BWP (e.g., Figure 27 BWP 0 in ) may be configured among the multiple BWPs. In one example, the non - dormant BWP may be the BWP that the wireless device can activate in response to transitioning the SCell from a dormant state to a non - dormant state. In one example, the dormant BWP may be the BWP that the wireless device can switch to in response to transitioning the SCell from a non - dormant state to a dormant state. In one example, the configuration parameters may indicate one or more search spaces and / or control resource sets (CORESETs) configured on the non - dormant BWP. The configuration parameters may indicate that no search space or no CORESET is configured on the dormant BWP. The configuration parameters may indicate the CSI reporting configuration parameters for the dormant BWP.In one example, the default BWP may be different from the inactive BWP. Configuration parameters may indicate one or more search spaces or one or more CORESETs configured on the default BWP. When the BWP inactivity timer expires or a DCI indicating a switch to the default BWP is received, the wireless device may switch to the default BWP as the active BWP. When the default BWP is active, the wireless device may perform at least one of the following: monitor the PDCCH on the default BWP of the SCell; receive the PDSCH on the default BWP of the SCell; transmit the PUSCH on the default BWP of the SCell; transmit the SRS on the default BWP of the SCell; and / or transmit a CSI report (e.g., periodic, aperiodic, and / or semi-persistent) for the default BWP of the SCell. In one example, when a resume / inactive indication indicating the inactive state of the SCell is received, the wireless device may switch to the inactive BWP as the active BWP of the SCell. In response to switching to the inactive BWP, the wireless device may perform at least one of the following: suppress monitoring of the PDCCH on the inactive BWP of the SCell (or suppress monitoring of the SCell if the SCell is cross-carrier scheduled by another cell); suppress receiving the PDSCH on the inactive BWP of the SCell; suppress transmitting the PUSCH on the inactive BWP of the SCell; suppress transmitting the SRS on the inactive BWP of the SCell; and / or transmit a CSI report (e.g., periodic, aperiodic, and / or semi-persistent) for the inactive BWP of the SCell.

[0289] As Figure 27 shown, the base station may transmit downlink control information (DCI) to the wireless device via a PDCCH resource, and the DCI includes a resume / inactive indication indicating the inactive state or the non-inactive state of the SCell. In response to the resume / inactive indication indicating the inactive state of the SCell, the wireless device may perform the following operations: if the SCell is in the non-inactive state before receiving the DCI, transition the SCell to the inactive state; or if the SCell is in the inactive state before receiving the DCI, maintain the SCell in the inactive state. Transitioning the SCell to the inactive state may include: switching to the inactive BWP of the SCell (e.g., configured by the base station). In response to the resume / inactive indication indicating the non-inactive state of the SCell, the wireless device may perform the following operations: if the SCell is in the inactive state before receiving the DCI, transition the SCell to the non-inactive state; or if the SCell is in the non-inactive state before receiving the DCI, maintain the SCell in the non-inactive state. Transitioning the SCell to the non-inactive state may include: transitioning to the non-inactive BWP of the SCell (e.g., configured by the base station).

[0290] AsFigure 27 As shown, in response to transitioning a SCell from a dormant state to a non-dormant state, a wireless device may switch to a non-dormant BWP configured by a base station (e.g., BWP 3 as shown in Figure 27 ), as the active BWP of the SCell. Based on the switch to the non-dormant BWP as the active BWP of the SCell, the wireless device may perform at least one of the following: monitor the PDCCH on the active BWP of the SCell (or monitor the PDCCH for the SCell when the SCell is configured to be cross-carrier scheduled by another cell); receive the PDSCH on the active BWP of the SCell; and / or transmit the PUCCH / PUSCH / RACH / SRS on the active BWP (e.g., if the active BWP is an uplink BWP).

[0291] As Figure 27 shown, in response to transitioning a SCell from a non-dormant state to a dormant state, a wireless device may switch to a dormant BWP configured by a base station (e.g., BWP 1 of the SCell as shown in Figure 27 ). Based on the switch to the dormant BWP of the SCell, the wireless device may perform at least one of the following: inhibit monitoring the PDCCH on the dormant BWP of the SCell (or inhibit monitoring the PDCCH for the SCell when the SCell is configured to be cross-carrier scheduled by another cell); inhibit receiving the PDSCH on the dormant BWP of the SCell; inhibit transmitting the PUCCH / PUSCH / RACH / SRS on the dormant BWP (e.g., if the dormant BWP is an uplink BWP); and / or transmit a CSI report for the dormant BWP of the SCell based on the CSI report configuration parameters configured on the dormant BWP of the SCell.

[0292] Figure 28 shows an example of cell-group-based dormant indication according to some embodiments. In one example, a base station may transmit one or more RRC messages to a wireless device, the one or more RRC messages including configuration parameters of a plurality of SCells, the plurality of SCells being grouped into a plurality of SCell groups for dormant indication (e.g., Figure 28 SCell group 1, SCell group 2 in Figure 28As shown, SCell group 1 includes cell 1, cell 2, etc. SCell group 2 includes cell 3, cell 4, etc. In one example, the SCell in the plurality of SCell may include a plurality of BWPs, and the plurality of BWPs includes at least one of the following: a first BWP as a non-dormant BWP and / or a second BWP as a dormant BWP.

[0293] In one example, the wireless device may apply a dormant indication for all the SCells of the SCell group, including: in response to receiving a dormant indication indicating the dormant state of the SCell group, transitioning to the corresponding dormant BWP of each SCell of the SCell group for each SCell of the SCell group. In one example, the wireless device may apply a non-dormant indication for all the SCells of the SCell group, including: in response to receiving a dormant indication indicating the non-dormant state of the SCell group, transitioning to the corresponding non-dormant BWP of each SCell of the SCell group for each SCell of the SCell group.

[0294] As Figure 28 shown, the wireless device may receive a dormant indication bitmap including a plurality of dormant indication bits, where each bit corresponding to a respective SCell group in the plurality of SCell groups indicates the dormant / non-dormant state of the respective SCell group. In one example, the dormant indication bitmap may be included in the downlink control information. In one example, the first bit (e.g., Figure 28 the 1st bit in Figure 28 ) of the dormant indication bitmap set to "0" may indicate the dormant state of SCell group 1. The second bit (e.g.,

[0295] the 2nd bit in Figure 27 and / or Figure 28 ) of the dormant indication bitmap set to "1" may indicate the non-dormant state of SCell group 2, and so on.

[0296] In one example, in response to the second bit of the DRX indication bitmap indicating the non-DRX state of SCell group 2, the wireless device may transition one or more SCells of SCell group 2 to the non-DRX state, including: switching to the non-DRX BWP of cell 3 as the active BWP of cell 3, switching to the non-DRX BWP of cell 4 as the active BWP of cell 4, and so on. In one example, in response to the second bit of the DRX indication bitmap indicating the non-DRX state of SCell group 2, if the SCell was in the non-DRX state before receiving the DRX indication bitmap, the wireless device may maintain the non-DRX state of the SCells of SCell group 2. The wireless device may perform actions on the corresponding non-DRX BWPs on cell 3, cell 4, etc. based on Figure 27 one or more embodiments thereof. Transitions of SCell states between DRX and non-DRX based on cell grouping may improve signaling overhead, transmission latency, and / or reduce the power consumption of the wireless device.

[0297] In one example, when receiving a DRX indication for a first cell, the wireless device may apply the DRX indication of the first cell to a second cell in response to the second cell being carrier aggregated by the first cell. In response to the DRX indication indicating the non-DRX state of the first cell, the wireless device may transition the first cell to the non-DRX state by applying the DRX indication, and transition the second cell to the non-DRX state based on the second cell being carrier aggregated by the first cell. In response to the DRX indication indicating the DRX state of the first cell, the wireless device may transition the first cell to the DRX state by applying the DRX indication, and transition the second cell to the DRX state based on the second cell being carrier aggregated by the first cell. Applying the DRX indication for the scheduled cell (e.g., which is configured to carrier aggregate the scheduled cell) to the scheduled cell regardless of whether the DRX indication indicates the DRX state or the non-DRX state may increase the power consumption of the wireless device and the interference of uplink transmissions to other wireless devices. In the case where the scheduling cell is configured to carrier aggregate the scheduled cell, when receiving a DRX indication for the scheduling cell, exemplary embodiments may reduce the power consumption of the wireless device and reduce the SCell DRX / non-DRX transition latency.

[0298] In one example, when the scheduled cell and the scheduling cell are grouped into different cell groups for inactivity indication, the wireless device may receive: a first inactivity indication for a first cell group including the scheduled cell, and a second inactivity indication for a second cell group including the scheduling cell. The first inactivity indication may be different from the second inactivity indication. In one example, the first inactivity indication and the second inactivity indication being different may be referred to as conflicting inactivity indications for the scheduling cell and the scheduled cell. In response to receiving the conflicting inactivity indications for the scheduling cell and the scheduled cell, it may be difficult for the wireless device to resolve the conflicting information in determining the appropriate actions for the scheduling cell and / or the scheduled cell by implementing the prior art. The wireless device may determine the actions for the scheduling cell and / or the scheduled cell based on the implementation of the wireless device. Determining the actions for the scheduling cell and / or the scheduled cell based on the implementation of the wireless device may result in a misalignment between the base station and the wireless device regarding the status of the scheduling cell and / or the scheduled cell. It is necessary to solve the problem of conflicting inactivity indications for cross-carrier scheduling to align between the base station and the wireless device. When receiving the conflicting inactivity indications for the scheduling cell and the scheduled cell, the exemplary embodiment may reduce the power consumption of the wireless device and reduce the SCell inactivity / activation transition waiting time.

[0299] Figure 29 is a flowchart of an exemplary method for performing inactivity management of multiple SCell according to some embodiments. In one example, the base station may determine that a first cell is cross-carrier scheduled by a second cell for the wireless device. When the first cell is not configured with downlink control channel resources for the wireless device, the base station may determine that the first cell is cross-carrier scheduled by the second cell. When the first cell has a smaller bandwidth than the second cell, the base station may determine that the first cell is cross-carrier scheduled by the second cell. The base station may transmit one or more RRC messages (e.g., ServingCellConfig IE, PDCCH-ServingCellConfig IE, CellGroupConfig IE, etc.) including configuration parameters of multiple cells (e.g., PCell and / or SCell) to the wireless device, where the multiple cells are grouped into multiple cell groups for inactivity indication. The multiple cells may include the first cell and the second cell. In response to the first cell being cross-carrier scheduled by the second cell, the configuration parameters may indicate that the first cell and the second cell belong to the same cell group for inactivity indication among the multiple cell groups. In one example, when a third cell among the multiple cells is not cross-carrier scheduled by a fourth cell among the multiple cells (e.g., the third cell is self-scheduled), the configuration parameters may indicate that the third cell and the fourth cell belong to two different cell groups for inactivity indication among the multiple cell groups.

[0300] As Figure 29As shown, based on the first cell and the second cell belonging to the same cell group for inactivity indication, the base station may transmit downlink control information including an inactivity indication bitmap to the wireless device. The inactivity indication bitmap may include a plurality of inactivity indication bits, where each bit corresponding to a respective cell group in the plurality of cell groups may indicate an inactivity state or a non-inactivity state for the respective cell group based on the bit value of the bit. In one example, a bit value set to a first value (e.g., 0) may indicate the inactivity state of the cell group. A bit value set to a second value (e.g., 1) may indicate the non-inactivity state of the cell group.

[0301] As Figure 29 shown, the base station may transmit an inactivity indication bit indicating an inactivity state corresponding to a cell group including the first cell and the second cell to the wireless device. Based on the inactivity indication, the base station may transition the first cell and the second cell to the inactivity state, where the transition may include: switching to the inactivity BWP of the first cell and switching to the inactivity BWP of the second cell. If the first cell and / or the second cell is in the inactivity state before the base station transmits the inactivity indication bit indicating the inactivity state, the base station may maintain the inactivity state of the first cell and / or the second cell. Maintaining the inactivity state may include: maintaining the state of the inactivity BWP of the first cell and / or the second cell (e.g., not switching the BWP). In one example, configuration parameters may indicate a first BWP of the first cell as the inactivity BWP of the first cell, and / or indicate a second BWP of the second cell as the inactivity BWP of the second cell.

[0302] In one example, the base station may transmit an inactivity indication bit indicating a non-inactivity state corresponding to a cell group including the first cell and the second cell to the wireless device. Based on the inactivity indication, the base station may transition the first cell and the second cell to the non-inactivity state, where the transition may include: switching to the non-inactivity BWP of the first cell and switching to the non-inactivity BWP of the second cell. If the first cell and / or the second cell is in the non-inactivity state before the base station transmits the inactivity indication bit indicating the non-inactivity state, the base station may maintain the non-inactivity state of the first cell and / or the second cell. Maintaining the non-inactivity state may include: maintaining the state of the non-inactivity (e.g., active) BWP of the first cell and / or the second cell (e.g., not switching the BWP). In one example, configuration parameters may indicate a third BWP of the first cell as the non-inactivity BWP of the first cell, and / or indicate a fourth BWP of the second cell as the non-inactivity BWP of the second cell.

[0303] In one example, in response to receiving a discontinuous reception (DRX) indication bit indicating a discontinuous reception state corresponding to a cell group including a first cell and a second cell, a wireless device may transition the first cell and the second cell to the discontinuous reception state, where the transition may include: switching to a DRX bandwidth part (BWP) of the first cell and switching to a DRX BWP of the second cell. If the first cell and / or the second cell is in the discontinuous reception state before the wireless device receives the DRX indication bit indicating the discontinuous reception state, the wireless device may maintain the discontinuous reception state of the first cell and / or the second cell. In one example, in response to receiving a DRX indication bit indicating a non-discontinuous reception state corresponding to a cell group including a first cell and a second cell, the wireless device may transition the first cell and the second cell to the non-discontinuous reception state, where the transition may include: switching to a non-DRX BWP of the first cell and switching to a non-DRX BWP of the second cell. If the first cell and / or the second cell is in the non-discontinuous reception state before the wireless device receives the DRX indication bit indicating the non-discontinuous reception state, the wireless device may maintain the non-discontinuous reception state of the first cell and / or the second cell.

[0304] Through an exemplary embodiment, based on the first cell being cross-carrier scheduled by the second cell, a base station may group the first cell and the second cell into the same cell group for DRX indication. Grouping the scheduling cell and the scheduled cell into the same cell group for DRX indication may reduce conflicting DRX indications for the scheduling cell and the scheduled cell. By implementing the exemplary embodiment, the base station and the wireless device may reduce the power consumption of the wireless device and / or reduce the uplink interference to other uplink transmissions.

[0305] Figure 30 is a flowchart of an exemplary method for performing DRX management of multiple secondary cell groups (SCells) according to some embodiments. In one example, a wireless device may receive one or more radio resource control (RRC) messages (e.g., ServingCellConfig IEs, PDCCH-ServingCellConfig IEs, CellGroupConfig IEs, etc.) from a base station, including configuration parameters of multiple cells (e.g., a primary cell (PCell) and / or SCells). The configuration parameters may indicate that a first cell among the multiple cells is cross-carrier scheduled by a second cell among the multiple cells. The configuration parameters may indicate that the multiple cells are grouped into multiple cell groups for DRX indication, where the second cell belongs to a first cell group among the multiple cell groups, and the first cell does not belong to the first cell group.

[0306] As Figure 30As shown, a wireless device may receive downlink control information including a quiescence indication bitmap. The quiescence indication bitmap may include a plurality of quiescence indication bits, where each bit corresponding to a respective cell group among the plurality of cell groups may indicate a quiescence state or a non - quiescence state for the respective cell group based on the bit value of the bit. In one example, a bit value set to a first value (e.g., 0) may indicate the quiescence state of a cell group. A bit value set to a second value (e.g., 1) may indicate the non - quiescence state of a cell group.

[0307] As Figure 30 shown, the wireless device may perform one or more actions on the first cell and / or the second cell based on whether the quiescence indication bit corresponding to a first cell group that includes the second cell and does not include the first cell in the quiescence indication bitmap indicates a quiescence state or a non - quiescence state.

[0308] In one example, in response to the quiescence indication bit indicating the quiescence state of the second cell, the wireless device may transition the first cell and the second cell to the quiescence state based on the second cell cross - carrier scheduling the first cell, where the transition may include: switching to the quiescent BWP of the first cell and switching to the quiescent BWP of the second cell. If the first cell and / or the second cell is in the quiescence state before the base station transmits the quiescence indication indicating the quiescence state, the wireless device may maintain the quiescence state of the first cell and / or the second cell.

[0309] In one example, in response to the quiescence indication bit indicating the non - quiescence state of the second cell, the wireless device may transition the second cell to the non - quiescence state, where the transition may include: switching to the non - quiescent BWP of the second cell. If the second cell is in the non - quiescence state before the wireless device receives the quiescence indication indicating the non - quiescence state of the second cell, the wireless device may maintain (e.g., not switch the BWP) the non - quiescence state of the second cell.

[0310] In one example, in response to the quiescence indication bit indicating the non - quiescence state of the second cell, the wireless device may maintain the original state of the first cell by not applying the quiescence indication bit of the second cell to the first cell. Maintaining the original state of the first cell may include: if the first cell is in the quiescence state before receiving the quiescence indication for the second cell, maintaining the quiescence state of the first cell (not switching the BWP). Maintaining the original state of the first cell may include: if the first cell is in the non - quiescence state before receiving the quiescence indication for the second cell, maintaining the non - quiescence state of the first cell (not switching the BWP).

[0311] Through embodiments, a wireless device and / or a base station can determine whether to apply a dormancy indication of a scheduled cell to a scheduled cell, e.g., based on whether the dormancy indication indicates a dormant state or a non-dormant state of the scheduled cell. In one example, when a first dormancy indication indicates a dormant state of a scheduled cell, the wireless device can apply the first dormancy indication of the scheduled cell to the scheduled cell. In one example, when a second dormancy indication indicates a non-dormant state of a scheduled cell, the wireless device can maintain the original state of the scheduled cell by not applying the second dormancy indication of the scheduled cell to the scheduled cell. Exemplary embodiments can improve the power consumption of the wireless device.

[0312] Figure 31 is a flowchart of an exemplary method for performing dormancy management of multiple SCell according to some embodiments. In one example, a wireless device can receive one or more RRC messages (e.g., ServingCellConfig IE, PDCCH-ServingCellConfig IE, CellGroupConfig IE, etc.) including configuration parameters of multiple cells (e.g., PCell and / or SCell) from a base station. The configuration parameters can indicate that a first cell among the multiple cells is cross-carrier scheduled by a second cell among the multiple cells. The configuration parameters can indicate that the multiple cells are grouped into multiple cell groups for dormancy indication, where the second cell belongs to a first cell group among the multiple cell groups, and the first cell does not belong to the first cell group. The configuration parameters can indicate whether the dormancy indication of the second cell applies to the first cell. The dormancy indication can include at least one of the following: a dormancy state indication or a non-dormancy state indication.

[0313] As Figure 31 shown, the wireless device can receive downlink control information (DCI) including a dormancy indication bitmap. The dormancy indication bitmap can include multiple dormancy indication bits, e.g., by implementing Figure 29 and / or Figure 30 examples.

[0314] As Figure 31As shown, in response to the inactive indication bit indicating the inactive state of the second cell, the wireless device may transition the second cell to the inactive state, where the transition may include: switching to the inactive BWP of the second cell. If the second cell is in the inactive state before the wireless device receives the inactive indication indicating the inactive state, the wireless device may maintain the inactive state of the second cell. In one example, in response to the inactive indication bit indicating the non-inactive state of the second cell, the wireless device may transition the second cell to the non-inactive state, where the transition may include: switching to the non-inactive BWP of the second cell. If the second cell is in the non-inactive state before the wireless device receives the inactive indication indicating the non-inactive state of the second cell, the wireless device may maintain (e.g., not switch the BWP) the non-inactive state of the second cell.

[0315] As Figure 31 shown, the wireless device may determine the state of the first cell based on a configuration parameter indicating whether the inactive indication of the second cell applies to the first cell.

[0316] In one example, in response to the configuration parameter indicating that the inactive indication of the second cell applies to the first cell, the wireless device may apply the inactive indication of the second cell to the first cell. In one example, by applying the inactive indication of the second cell to the first cell, the wireless device may transition the first cell to the inactive state, where the transition may include: switching to the inactive BWP of the first cell in response to the inactive indication of the second cell indicating the inactive state. In one example, by applying the inactive indication of the second cell to the first cell, the wireless device may transition the first cell to the non-inactive state, where the transition may include: switching to the non-inactive BWP of the first cell in response to the inactive indication of the second cell indicating the non-inactive state.

[0317] In one example, in response to the configuration parameter indicating that the inactive indication of the second cell does not apply to the first cell, the wireless device may suppress applying (ignore or not apply) the inactive indication of the second cell to the first cell. In one example, by not applying the inactive indication of the second cell to the first cell, the wireless device may maintain the original state of the first cell. Maintaining the original state of the first cell may include: if the first cell is in the inactive state before receiving the inactive indication for the second cell, maintaining the inactive state of the first cell (not switching the BWP). Maintaining the original state of the first cell may include: if the first cell is in the non-inactive state before receiving the inactive indication for the second cell, maintaining the non-inactive state of the first cell (not switching the BWP).

[0318] Through an implementation, a wireless device and / or a base station can determine whether to apply a rest indication of a scheduled cell to a scheduled cell, e.g., based on whether the rest indication of the scheduled cell is applicable to a first cell (e.g., via RRC configuration, based on an indication of a UE that transmits auxiliary information and / or capability parameters of the UE, and / or as a predefined rule). Exemplary implementations can improve the power consumption of a wireless device.

[0319] Figure 32 An example of rest management for multiple SCell is shown according to some implementations. In one example, a wireless device can receive one or more RRC messages (e.g., ServingCellConfig IE, PDCCH-ServingCellConfig IE, CellGroupConfig IE, etc.) from a base station that include configuration parameters for multiple cells (e.g., a PCell and / or SCell). The configuration parameters can include a first configuration parameter that indicates that the multiple cells are grouped into multiple cell groups for rest indication (e.g., Figure 32 cell group 1, cell group 2, etc. in Figure 32 . Each cell group of the multiple cell groups can include one or more cells. In the example of Figure 32 , cell group 1 includes cell 1, cell 2, etc. Cell group 2 includes cell 3, cell 4, etc. The configuration parameters can include a second configuration parameter that indicates that a first cell among the multiple cells is cross-carrier scheduled by a second cell among the multiple cells. In the example of

[0320] As Figure 32 shown, a wireless device can receive downlink control information that includes a rest indication bitmap. The rest indication bitmap can include multiple rest indication bits, where each bit corresponding to a respective cell group among the multiple cell groups can indicate a rest state or a non-rest state for the respective cell group based on the bit value of the bit. In one example, a bit value set to a first value (e.g., 0) can indicate the rest state of the cell group. A bit value set to a second value (e.g., 1) can indicate the non-rest state of the cell group. In Figure 32In an example, the first bit corresponding to cell group 1 including at least cell 1 in the bitmap is set to a first value (e.g., 0) indicating the dormant state of cell group 1, and the second bit corresponding to cell group 2 including at least cell 3 in the bitmap is set to a second value (e.g., 1) indicating the non-dormant state of cell group 2. In one example, the first bit and the second bit can be set to different bit values indicating conflict dormant indications for the first cell (cell 1) and the second cell (cell 3), where the second cell is cross-carrier scheduled by the first cell. In response to the second cell (cell 3) being cross-carrier scheduled by the first cell (cell 1) and the first cell and the second cell belonging to different cell groups for dormant indication, the wireless device can determine the first state of the first cell and / or the second state of the second cell based on at least one of the following: the first dormant indication value of the first bit ( Figure 32 the first bit in); the second dormant indication value of the second bit ( Figure 32 the second bit in) associated with the second cell; the original state of the first cell before receiving the dormant indication; the original state of the second cell before receiving the dormant indication. The wireless device can determine the first state of the first cell and / or the second state of the second cell by implementing Figure 33 、 Figure 34 、 Figure 35 and / or Figure 37 exemplary embodiments. The exemplary embodiments can improve the power consumption of the wireless device by determining the states of the scheduling cell and the scheduled cell based on at least one of the following: the first dormant indication associated with the scheduling cell; the second dormant indication associated with the scheduled cell; the original state of the scheduling cell; the original state of the scheduled cell; and / or the carrier scheduling parameter.

[0321] Figure 33 shows an example of the dormant management of multiple SCell according to some embodiments. In one example, the wireless device can receive one or more RRC messages (e.g., Figure 32 ) including configuration parameters of multiple cells (e.g., PCell and / or SCell) from the base station by implementing the exemplary embodiments of ServingCellConfig IE, PDCCH- ServingCellConfig IE, CellGroupConfig IE, etc.). The configuration parameters can include a first configuration parameter indicating that the multiple cells are grouped into multiple cell groups for dormant indication (e.g., Figure 33 cell group 1, cell group 2, etc. in). Each cell group in the multiple cell groups can include one or more cells. In Figure 33In an example, cell group 1 includes cell 1, cell 2, etc. Cell group 2 includes cell 3, cell 4, etc. The configuration parameter may include a second configuration parameter that indicates that a first cell among the plurality of cells is cross-carrier scheduled by a second cell among the plurality of cells. In Figure 33 the example, cell 3 of cell group 2 is cross-carrier scheduled by cell 1 of cell group 1.

[0322] As Figure 33 shown, the wireless device may receive downlink control information including a quiescence indication bitmap by implementing Figure 32 an exemplary implementation of. The quiescence indication bitmap may include a plurality of quiescence indication bits, where each bit corresponding to a respective cell group among the plurality of cell groups may indicate a quiescence state or a non-quiescence state for the respective cell group based on the bit value of the bit. In Figure 33 the example, the first bit of the bitmap corresponding to cell group 1 including at least cell 1 is set to a first value (e.g., 0) indicating the quiescence state of cell group 1, and the second bit of the bitmap corresponding to cell group 2 including at least cell 3 is set to a second value (e.g., 1) indicating the non-quiescence state of cell group 2.

[0323] In one example, in response to a second cell being cross-carrier scheduled by a first cell and the first cell and the second cell belonging to different cell groups for quiescence indication, the wireless device may determine the state of the second cell based on the quiescence indication for the first cell by applying the first quiescence indication of the first cell to the second cell and / or ignoring or not applying the second quiescence indication for the second cell. In one example, the wireless device may transition the second cell to a quiescence state, where the transition may include switching to a quiescent BWP of the second cell in response to: the first quiescence indication indicating the quiescence state of the first cell group including the first cell; the second quiescence indication indicating the non-quiescence state of the second cell group including the second cell; and the second cell being cross-carrier scheduled by the first cell. In Figure 33In an example, in response to the first bit indicating the inactivity state of cell group 1 and the second bit indicating the non-inactivity state of cell group 2, the wireless device may transition the first cell (cell 1) of cell group 1 to the inactivity state (e.g., switch to the inactivity BWP of the first cell), and transition the second cell (cell 3) of the second cell group 2 to the inactivity state (e.g., switch to the inactivity BWP of the second cell) by ignoring the inactivity indication for the second cell of cell group 2. In one example, in response to the first bit indicating the inactivity state of cell group 1 and the second bit indicating the non-inactivity state of cell group 2, if the second cell (cell 3) of cell group 2 is in the inactivity state before receiving the inactivity indication bitmap, the wireless device may maintain the inactivity state of the second cell (e.g., do not switch the BWP of the second cell) by ignoring the inactivity indication for the second cell of cell group 2.

[0324] Figure 34 shows an example of inactivity management for multiple SCell according to some embodiments. In one example, the wireless device may receive one or more RRC messages (e.g., Figure 32 and / or Figure 33 IE, ServingCellConfig IE, PDCCH- ServingCellConfig IE, CellGroupConfig IE, etc.) including configuration parameters of multiple cells (e.g., PCell and / or SCell) from the base station by implementing the exemplary embodiments of Figure 32 and / or Figure 33 . In one example, the wireless device may receive downlink control information including an inactivity indication bitmap by implementing the exemplary embodiments of Figure 34 . In the example of Figure 34 , the first bit corresponding to cell group 1 including at least cell 1 in the inactivity indication bitmap is set to a first value (e.g., 0) indicating the inactivity state of cell group 1, and the second bit corresponding to cell group 2 including at least cell 3 in the inactivity indication bitmap is set to a second value (e.g., 1) indicating the non-inactivity state of cell group 2.

[0325] In one example, in response to the second cell being cross-carrier scheduled by the first cell and the first cell and the second cell belonging to different cell groups for the inactivity indication, the wireless device may determine the state of the second cell based on the first inactivity indication of the first cell and / or the second inactivity indication for the second cell. In one example, the wireless device may maintain the original state of the second cell (e.g., do not switch the BWP) in response to: the first inactivity indication indicating the inactivity state of the first cell group including the first cell; the second inactivity indication indicating the non-inactivity state of the second cell group including the second cell; and the second cell being cross-carrier scheduled by the first cell. In Figure 34In an example, in response to the first bit for cell group 1 indicating a dormant state and the second bit for cell group 2 indicating a non-dormant state, the wireless device may transition the first cell (cell 1) of cell group 1 to a dormant state (e.g., switch to the dormant BWP of the first cell), and maintain the original state of the second cell (cell 3) of cell group 2. Maintaining the original state of the second cell may include: if the second cell was in a dormant state before receiving the dormant indication bitmap, maintaining the dormant state of the second cell. Maintaining the original state of the second cell may include: if the second cell was in a non-dormant state before receiving the dormant indication bitmap, maintaining the non-dormant state of the second cell.

[0326] Figure 35 FIG. shows an example of the dormant management of multiple SCell according to some embodiments. In one example, the wireless device may receive one or more RRC messages (e.g., Figure 32 , Figure 33 and / or Figure 34 IEs) including configuration parameters of multiple cells (e.g., PCell and / or SCell) from the base station by implementing the exemplary embodiments of ServingCellConfig IE, PDCCH-ServingCellConfig IE, CellGroupConfig IE, etc.). In one example, the wireless device may receive the downlink control information including the dormant indication bitmap by implementing the exemplary embodiments of Figure 32 , Figure 33 and / or Figure 34 . In the example of Figure 35 , the first bit corresponding to cell group 1 including at least cell 1 in the dormant indication bitmap is set to a first value (e.g., 0) indicating the dormant state of cell group 1. The second bit corresponding to cell group 2 including at least cell 3 in the dormant indication bitmap is set to a second value (e.g., 1) indicating the non-dormant state of cell group 2.

[0327] In one example, in response to a second cell being cross-carrier scheduled by a first cell and the first cell and the second cell belonging to different cell groups for inactivity indication, a wireless device may determine the state of the first cell and the state of the second cell based on a first inactivity indication of the first cell and / or a second inactivity indication for the second cell. In one example, in response to the first inactivity indication indicating an inactive state of the first cell and the second inactivity indication indicating a non-inactive state of the second cell and the second cell being cross-carrier scheduled by the first cell, the wireless device may transition the first cell to a non-inactive state by ignoring or not applying the first inactivity indication for the first cell. In one example, the wireless device may transition the first cell to a non-inactive state in response to: the first inactivity indication indicating an inactive state of a first cell group including the first cell; the second inactivity indication indicating a non-inactive state of a second cell group including the second cell; and the second cell being cross-carrier scheduled by the first cell. In Figure 35 an example, in response to the first bit for cell group 1 indicating an inactive state, the second bit for cell group 2 indicating a non-inactive state, and cell 3 of cell group 2 being cross-carrier scheduled by cell 1 of cell group 1, the wireless device may transition cell 1 to a non-inactive state (e.g., switch to a non-inactive BWP of cell 1) by ignoring or not applying the first bit to cell 1. The wireless device may transition the second cell to a non-inactive state (e.g., switch to a non-inactive BWP of cell 3).

[0328] Figure 36 is a flowchart of an exemplary method for performing SCell inactivity management according to some embodiments. In one example, a wireless device may receive one or more RRC messages including configuration parameters that indicate: a first cell is cross-carrier scheduled by a second cell; the first cell belongs to a first cell group for inactivity indication; and / or the second cell belongs to a second cell group for inactivity indication. The wireless device may receive a DCI including an inactivity indication bitmap that includes a first bit corresponding to the first cell group and a second bit corresponding to the second cell group. The first bit may be set to a first value indicating a non-inactive state of the first cell group. The second bit may be set to a second value indicating an inactive state of the second cell group.

[0329] In one example, in response to a second bit indicating an inactive state of a second cell group, where the second cell group includes a second cell, the wireless device may transition the second cell to the inactive state, e.g., switch to an inactive BWP of the second cell. In response to receiving a first bit indicating a non-inactive state of a first cell group and / or a second bit indicating an inactive state of the second cell group, the wireless device may determine the state of the first cell based on whether an inactive BWP is configured on the first cell. In one example, in response to an inactive BWP being configured on the first cell, the wireless device may apply the second bit of the second cell group to the first cell and / or may ignore or not apply the first bit of the first cell group to the first cell, where applying the second bit to the first cell may include: transitioning the first cell to the inactive state when the second bit indicates an inactive state, e.g., switching to an inactive BWP of the first cell. In one example, in response to an inactive BWP not being configured on the first cell and / or the second bit indicating an inactive state, the wireless device may maintain the first cell in its original state by ignoring or not applying the first bit and / or the second bit, e.g., maintaining the state of the BWP of the first cell (e.g., non-inactive) without switching to an inactive BWP of the first cell.

[0330] Figure 37 An example of inactive management of multiple SCell is shown according to some embodiments. In one example, the wireless device may receive one or more RRC messages (e.g., Figure 32 , Figure 33 , Figure 34 and / or Figure 35 ) including configuration parameters of multiple cells (e.g., PCell and / or SCell) from the base station by implementing the exemplary embodiments of ServingCellConfig IE, PDCCH-ServingCellConfig IE, CellGroupConfig IE, etc.). In one example, the wireless device may receive downlink control information including an inactive indication bitmap by implementing the exemplary embodiments of Figure 32 , Figure 33 , Figure 34 and / or Figure 35 . In the example of Figure 37 , the first bit corresponding to cell group 1 including at least cell 1 of the inactive indication bitmap is set to a first value (e.g., 1) indicating a non-inactive state of cell group 1, and the second bit corresponding to cell group 2 including at least cell 3 of the inactive indication bitmap is set to a second value (e.g., 0) indicating an inactive state of cell group 2.

[0331] In one example, in response to a second cell being cross-carrier scheduled by a first cell and the first cell and the second cell belonging to different cell groups for inactivity indication, a wireless device may determine the state of the first cell based on a first inactivity indication of the first cell and determine the state of the second cell based on a second inactivity indication for the second cell. The wireless device may determine the state of the first cell and the state of the second cell independently and / or separately. In one example, in response to a first inactivity indication for a first cell group including the first cell indicating a non-inactive state, the wireless device may transition the first cell to the non-inactive state. In response to a second inactivity indication for a second cell group including the second cell indicating an inactive state, the wireless device may transition the second cell to the inactive state. In Figure 37 an example, in response to a first bit for cell group 1 indicating a non-inactive state and a second cell (e.g., cell 3) of cell group 2 being cross-carrier scheduled by a first cell (e.g., cell 1) of cell group 1, the wireless device may transition cell 1 to the non-inactive state (e.g., switch to a non-inactive BWP of cell 1). In Figure 37 an example, in response to a second bit for cell group 2 indicating an inactive state and a second cell (e.g., cell 3) of cell group 2 being cross-carrier scheduled by a first cell (e.g., cell 1) of cell group 1, the wireless device may transition cell 3 to the inactive state (e.g., switch to an inactive BWP of cell 3). The wireless device may apply the inactivity indication to the scheduled cell and the scheduling cell independently and / or separately.

[0332] In one example, a wireless device may receive one or more radio resource control (RRC) messages including configuration parameters that indicate that a first cell belongs to a first dormant cell group and a second cell belongs to a second dormant cell group. The wireless device may receive a dormant / non-dormant indication (e.g., included in downlink control information) indicating a non-dormant state of the first cell group. In response to receiving the indication, based on the first cell being cross-carrier scheduled by the second cell and the second cell group being in a dormant state, the wireless device may maintain the first cell in a dormant state by ignoring the dormant / non-dormant indication for the first cell. In one example, the second cell group is in a dormant state before the wireless device receives the dormant indication. In response to receiving a second dormant indication indicating the dormant state of the second cell group, the wireless device may transition the second cell group to a dormant state. The wireless device may receive DCI including the dormant indication via a PDCCH resource. In one example, the one or more configuration parameters may indicate that the first cell is cross-carrier scheduled by the second cell. Maintaining the first cell in a dormant state may include: maintaining the state of the dormant BWP of the first cell without switching the BWP of the first cell. The first cell is in a dormant state before the wireless device receives the dormant indication. In one example, in response to the first cell being in a non-dormant state and the second cell group being in a dormant state before receiving the dormant indication, the wireless device may transition the first cell to a dormant state. The one or more configuration parameters may indicate that the first cell includes a first plurality of BWPs and the second cell includes a second plurality of BWPs. The one or more configuration parameters may indicate a first BWP among the first plurality of BWPs of the first cell as the dormant BWP of the first cell, and indicate a second BWP among the first plurality of BWPs as the non-dormant BWP of the first cell. The one or more configuration parameters may indicate a first BWP among the second plurality of BWPs of the second cell as the dormant BWP of the second cell, and indicate a second BWP among the second plurality of BWPs as the non-dormant BWP of the second cell. In response to the first BWP of the first cell being configured as the dormant BWP of the first cell and transitioning the first cell to a dormant state, the wireless device may switch to the first BWP of the first cell. In response to the second BWP of the first cell being configured as the non-dormant BWP of the first cell and transitioning the first cell to a non-dormant state, the wireless device may switch to the second BWP of the first cell. In response to the first BWP of the second cell being configured as the dormant BWP of the second cell and transitioning the second cell to a dormant state, the wireless device may switch to the first BWP of the second cell. In response to the second BWP of the second cell being configured as the non-dormant BWP of the second cell and transitioning the second cell to a non-dormant state, the wireless device may switch to the second BWP of the second cell.

[0333] In one example, a wireless device may receive one or more RRC messages including configuration parameters that indicate that a first cell belongs to a first cell group for inactivity indication and that a second cell belongs to a second cell group for inactivity indication. The wireless device may receive an inactivity indication for the first cell group. The wireless device may ignore the inactivity indication based on the first cell being cross-carrier scheduled by the second cell, where the second cell is in an inactive state. Based on the first cell being cross-carrier scheduled by the second cell and the second cell being in a non-inactive state, the wireless device may transition the first cell to a non-inactive state.

[0334] In one example, a wireless device may receive one or more RRC messages including configuration parameters that indicate that a first cell belongs to a first cell group for inactivity indication and that a second cell belongs to a second cell group for inactivity indication. The wireless device may receive a first inactivity indication and a second inactivity indication, where the first inactivity indication indicates a non-inactive state of the first cell group and the second inactivity indication indicates an inactive state of the second cell group. The wireless device may ignore the first inactivity indication for the first cell based on the first cell being cross-carrier scheduled by the second cell. The wireless device may transition the first cell to an inactive state based on ignoring the first inactivity indication and applying the second inactivity indication.

[0335] In one example, a wireless device may receive one or more RRC messages including configuration parameters that indicate that a first cell belongs to a first cell group for inactivity indication and that a second cell belongs to a second cell group for inactivity indication. The wireless device may receive a first inactivity indication and a second inactivity indication, where the first inactivity indication indicates a non-inactive state of the first cell group and the second inactivity indication indicates an inactive state of the second cell group. The wireless device may ignore the second inactivity indication for the second cell based on the first cell being cross-carrier scheduled by the second cell. The wireless device may transition the second cell to a non-inactive state based on ignoring the second inactivity indication.

[0336] In one example, a base station may transmit one or more RRC messages including configuration parameters to a wireless device, where the configuration parameters indicate that a first cell and a second cell belong to a cell group for inactivity indication based on the first cell being cross-carrier scheduled by the second cell. The base station may transmit an inactivity indication indicating an inactivity transition of the cell group. Based on the inactivity indication, the base station may transition the first cell to an inactive state for the wireless device and transition the second cell to an inactive state for the wireless device.

[0337] In one example, a wireless device may receive one or more configuration parameters that indicate that a first cell is cross-carrier scheduled by a second cell. The wireless device may receive a first inactivity indication and a second inactivity indication, where the first inactivity indication indicates a non-inactive state of the first cell and the second inactivity indication indicates an inactive state of the second cell. Based on the first inactivity indication and the second inactivity indication, the wireless device may transition the first cell to an inactive state in response to an inactive BWP being configured on the first cell, and maintain the first cell in its original state in response to an inactive BWP not being configured on the first cell.

[0338] In one example, a wireless device may reduce power consumption based on implementing inactivity management (e.g., by using Figure 27 and / or Figure 28 exemplary implementations). In one example, a wireless device may reduce power consumption based on skipping PDCCH monitoring during DRX active time (e.g., when DRX operation is configured for the wireless device). The power saving operations may include at least one of the following: inactivity transition based on DCI (e.g., Figure 27 and / or Figure 28 examples); skipping PDCCH monitoring during DRX active time (e.g., Figure 39A and / or Figure 39B examples); dynamically reducing PDCCH monitoring (e.g., Figure 40 examples); and so on.

[0339] In one example, DRX operation may be used by a wireless device to extend the battery life of the wireless device. When DRX is configured, the wireless device may discontinuously monitor the downlink control channel, e.g., PDCCH or EPDCCH. The base station may configure DRX operation with a set of DRX parameters (e.g., using RRC configuration). The DRX parameter set may be selected based on the application type such that the wireless device may reduce power and resource consumption. In response to DRX being configured / activated, the wireless device may receive packets with extended latency as the wireless device may be in the DRX sleep / off state when the data arrives at the wireless device, and the base station may wait until the wireless device transitions to the DRX on state.

[0340] In one example, during the DRX mode, when there are no packets to receive, the wireless device may turn off most of its circuitry. The wireless device may discontinuously monitor the PDCCH in the DRX mode. When DRX operation is not configured, the wireless device may continuously monitor the PDCCH. During this period, the wireless device listens for the downlink (DL) (or monitors the PDCCH) which is referred to as the DRX active state. In the DRX mode, the time when the wireless device does not listen / monitor the PDCCH is referred to as the DRX sleep state.

[0341] Figure 38 An example of a DRX configuration according to some embodiments is shown. The base station may transmit an RRC message including one or more DRX parameters including a DRX cycle. The one or more parameters may include a first parameter and / or a second parameter. The first parameter may indicate a first time value of a DRX active state of the DRX cycle (e.g., DRX on duration). The second parameter may indicate a second time of a DRX sleep state of the DRX cycle (e.g., DRX off duration). The one or more parameters may additionally include a duration of the DRX cycle. During the DRX active state, the wireless device may monitor the PDCCH to detect one or more DCIs on the serving cell. During the DRX sleep state, the wireless device may stop monitoring the PDCCH on the serving cell. When multiple cells are active, the wireless device may monitor all PDCCHs on (or for) the multiple cells during the DRX active state. During the DRX off duration, the wireless device may stop monitoring all PDCCHs on (or for) the multiple cells. The wireless device may repeat the DRX operation according to the one or more DRX parameters.

[0342] In one example, DRX may be beneficial to the base station. In one example, if DRX is not configured, the wireless device may transmit periodic CSI and / or SRS frequently (e.g., based on configuration). With DRX, during the DRX off period, the wireless device may not transmit periodic CSI and / or SRS. The base station may assign these resources to other UEs to improve resource utilization efficiency.

[0343] In one example, the MAC entity may be configured by an RRC with DRX functionality that controls the activity of the wireless device's downlink control channel (e.g., PDCCH) monitoring for multiple RNTIs of the MAC entity. The multiple RNTIs may include at least one of the following: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. In one example, in response to being in RRC_CONNECTED, if DRX is configured, the MAC entity may use DRX operation to discontinuously monitor the PDCCH; otherwise, the MAC entity may continuously monitor the PDCCH.

[0344] In one example, the RRC can control DRX operations by configuring multiple timers. The multiple timers can include: a DRX on-duration timer (e.g., drx-onDurationTimer (drx-on-duration timer)); a DRX inactivity timer (e.g., drx-InactivityTimer (drx-inactivity timer)); a downlink DRX HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL (drx-HARQ-RTT-timer DL)); an uplink DRX HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL (drx-HARQ-RTT-timer UL)); a downlink retransmission timer (e.g., drx-RetransmissionTimerDL (drx-retransmission timer DL)); an uplink retransmission timer (e.g., drx-RetransmissionTimerUL (drx-retransmission timer UL)); one or more parameters of a short DRX configuration (e.g., drx-ShortCycle (drx-short cycle) and / or drx-ShortCycleTimer (drx-short cycle timer)) and one or more parameters of a long DRX configuration (e.g., drx-LongCycle (drx-long cycle)). In one example, the time granularity of the DRX timer can be in PDCCH subframes (e.g., indicated as psf in the DRX configuration) or in milliseconds.

[0345] In one example, in response to a DRX cycle being configured, the active time can include the time when at least one timer is running. The at least one timer can include drx-onDurationTimer 、 drx-InactivityTimer 、 drx-RetransmissionTimerDL 、 drx-RetransmissionTimerUL or mac- ContentionResolutionTimer .

[0346] In one example, drx-Inactivity-Timer (drx-inactivity-timer) can specify the duration for which the wireless device can be active after successfully decoding a PDCCH indicating a new transmission (UL or DL or SL). This timer can be restarted when a PDCCH for a new transmission (UL or DL or SL) is received. The wireless device can transition to the DRX mode (e.g., using a short DRX cycle or a long DRX cycle) in response to the expiration of this timer. In one example, drx-ShortCycle can be the first type of DRX cycle that the wireless device needs to follow when entering the DRX mode (e.g., if configured). In one example, the DRX-Config IE indicates the length of the short cycle. drx-ShortCycleTimerIt can be expressed as multiple short DRX-Cycles. The timer can indicate the number of initial DRX cycles following the short DRX cycle before entering the long DRX cycle. drx-onDurationTimer The duration at the start of a DRX cycle (e.g., DRX on) can be specified. drx- onDurationTimer The duration before entering the sleep mode (DRX off) can be indicated. drx-HARQ-RTT- TimerDL The minimum duration from when a new transmission is received and before the wireless device may expect a retransmission of the same packet can be specified. This timer can be fixed and not configurable by RRC. drx-RetransmissionTimerDL The maximum duration during which the wireless device can monitor the PDCCH when it expects a retransmission from the base station can be indicated.

[0347] In response to a DRX cycle being configured, the active time can include the time when a scheduling request is sent on the PUCCH and is pending. In one example, in response to a DRX cycle being configured, the active time can include the time when an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ buffer for synchronizing the HARQ process. In response to a DRX cycle being configured, the active time can include the time after a random access response for a preamble not selected by the MAC entity is successfully received and before a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity is received.

[0348] The DL HARQ RTT timer may expire in a subframe and the data of the corresponding HARQ process may not be successfully decoded. The MAC entity can start drx-RetransmissionTimerDL for the corresponding HARQ process. The UL HARQ RTT timer can expire in a subframe. The MAC entity can start drx-RetransmissionTimerUL for the corresponding HARQ process. A DRX command MAC control element or a long DRX command MAC control element can be received. The MAC entity can stop drx- onDurationTimer and stop drx-InactivityTimer In one example, drx-InactivityTimer can expire, or a DRX command MAC control element can be received in a subframe. In one example, in response to a short DRX cycle being configured, the MAC entity can start or restart drx-ShortCycleTimer and can use the short DRX cycle. Otherwise, the MAC entity can use the long DRX cycle.

[0349] In one example, drx-ShortCycleTimer can expire in a subframe. The MAC entity can use the long DRX cycle. In one example, a long DRX command MAC control element can be received. The MAC entity can stopdrx- ShortCycleTimer And a long DRX cycle can be used.

[0350] In one example, if a short DRX cycle is used and [(SFN * 10) + subframe number] modulo ( drx-ShortCycle ) = ( drxStartOffset ) modulo ( drx-ShortCycle ), the wireless device can start drx-onDurationTimer . In one example, if a long DRX cycle is used and [(SFN * 10) + subframe number] modulo ( drx-longCycle ) = drxStartOffset , the wireless device can start drx-onDurationTimer .

[0351] Figure 39A FIG. shows an example of a wake-up indication-based power saving mechanism according to some embodiments. The base station may transmit one or more messages to the wireless device that include parameters of a wake-up duration (e.g., a power saving duration or a physical-sidelink control channel (PSCH) occasion). The wake-up duration may be located in a plurality of time slots (or symbols) before the DRX-on duration of the DRX cycle. The plurality of time slots (or symbols), or the gap between the wake-up duration and the DRX-on duration, may be configured in the one or more RRC messages or predefined as a fixed value. The gap may be used for at least one of the following: synchronizing with the base station; measuring a reference signal; and / or retuning RF parameters. The gap may be determined based on the capabilities of the wireless device and / or the base station. In one example, the parameters of the wake-up duration may be predefined without RRC configuration. In one example, the wake-up mechanism may be based on a wake-up indication via the PSCH. The parameters of the wake-up duration may include at least one of the following: PSCH channel format (e.g., parameter set, DCI format, PDCCH format); period of the PSCH; control resource set and / or search space of the PSCH. When configured with the parameters of the wake-up duration, the wireless device may monitor a wake-up signal or the PSCH during the wake-up duration. When configured with the parameters of the PSCH occasion, the wireless device may monitor the PSCH during the PSCH occasion to detect a wake-up indication. In response to receiving a wake-up signal / channel (or a wake-up indication received via the PSCH), the wireless device may wake up during the DRX active time of the next DRX cycle according to the DRX configuration to monitor the PDCCH. In one example, in response to receiving a wake-up indication via the PSCH, the wireless device may be in the DRX active time (e.g., when drx-onDurationTimerMonitor the PDCCH during runtime. If no PDCCH is received during the DRX active time, the wireless device can continue to sleep. The wireless device can remain asleep during the DRX off duration of the DRX cycle. In one example, if the wireless device does not receive a wake-up signal / channel (or a wake-up indication received via the PSCH) during the wake-up duration (or the PSCH occasion), the wireless device can skip monitoring the PDCCH during the DRX active time. In one example, if the wireless device receives an indication to skip PDCCH monitoring during the wake-up duration (or the PSCH occasion), the wireless device can skip monitoring the PDCCH during the DRX active time.

[0352] In one example, the power saving mechanism can be based on a sleep indication via the PSCH. Figure 39B An example of power saving based on a sleep indication according to some embodiments is shown. In response to receiving a sleep indication via the PSCH, the wireless device can continue to sleep during the DRX active time (e.g., the next DRX on duration of the DRX cycle) and skip monitoring the PDCCH. In one example, if the wireless device does not receive a sleep indication via the PSCH during the wake-up duration, the wireless device monitors the PDCCH during the DRX active time according to the configuration parameters of the DRX operation. This mechanism can reduce the power consumption of PDCCH monitoring during the DRX active time.

[0353] In one example, power saving can be achieved by combining Figure 39A and Figure 39B The base station can transmit a power saving indication in the DCI via the PSCH, thereby indicating to the wireless device to wake up or skip the next DRX on duration for the next DRX on duration. The wireless device can receive the DCI via the PSCH. In response to the power saving indication indicating that the wireless device should wake up for the next DRX on duration, the wireless device can wake up for the next DRX on duration. The wireless device monitors the PDCCH during the next DRX on duration in response to waking up. In response to the power saving indication indicating that the wireless device should skip (or sleep) for the next DRX on duration, the wireless device sleeps or skips for the next DRX on duration. In response to the power saving indication indicating that the wireless device should sleep for the next DRX on duration, the wireless device skips detecting the PDCCH during the next DRX on duration.

[0354] In one example, one or more embodiments of Figure 28 、 Figure 39A and / or Figure 39B can be extended to further improve the power consumption of the wireless device and / or the signaling overhead of the base station.

[0355] Figure 40 illustrates an example of a power saving mechanism according to some embodiments. The base station may transmit one or more RRC messages to the wireless device, including first configuration parameters of a power saving channel (PSCH) and second configuration parameters of a power saving (PS) operation.

[0356] In one example, the first configuration parameters of the PSCH may include at least one of the following: a first number of search spaces (SSs) on which the wireless device monitors the PSCH and / or a second number of control resource sets (CORESETs); one or more first DCI formats utilized by the wireless device to monitor the PSCH; a radio network temporary identifier (RNTI) dedicated to monitoring the PSCH (e.g., PS-RNTI).

[0357] In one example, the second configuration parameters of the PS operation may include at least one of the following: a third number of SSs on which the wireless device monitors the PDCCH and / or a fourth number of CORESETs in the PS operation; one or more second DCI formats utilized by the wireless device to monitor the PDCCH in the PS operation; one or more first MIMO parameters indicating a first maximum number of antennas (layers, ports, TRPs, panels, etc.) based on which the wireless device performs MIMO processing (transmission or reception) in the PS operation; one or more first cross-slot scheduling indicators indicating whether cross-slot scheduling is configured when the wireless device is in the PS operation; a BWP index indication based on which the wireless device transmits or receives data packets in the PS operation; and / or a cell index indication based on which the wireless device transmits or receives data packets in the PS operation.

[0358] In one example, the third number may be zero or a number greater than zero. In one example, the fourth number may be zero or a number greater than zero. In response to the third number being zero, the wireless device may skip monitoring the PDCCH in the PS operation. In response to the fourth number being zero, the wireless device may skip monitoring the PDCCH in the PS operation.

[0359] In one example, the one or more RRC messages may further include third configuration parameters for normal functional operation (e.g., full functionality, non-PS, non-inactive state, etc.). The third configuration parameters may include at least one of the following: a fifth number of SSs and / or a sixth number of CORESETs on which the wireless device monitors PDCCH in non-PS operation; one or more third DCI formats utilized by the wireless device to monitor PDCCH in PS operation; one or more second MIMO parameters indicating a second maximum number of antennas (layers, ports, TRPs, panels, etc.) based on which the wireless device performs MIMO processing (transmission or reception) in non-PS operation; one or more second cross-slot scheduling indicators indicating whether cross-slot scheduling is configured when the wireless device is in non-PS operation; and so on. For power saving purposes, after receiving a DCI indicating cross-slot scheduling and before receiving a data packet based on the DCI, the wireless device may turn off some receiver modules (e.g., data buffering, RF chain, channel tracking, etc.) based on the configured cross-slot scheduling. In one example, the third number of SSs and / or the fourth number of CORESETs may occupy less radio resources than the fifth number of SSs and / or the sixth number of CORESETs, e.g., for power saving purposes. The first maximum number may be less than the second maximum number, e.g., for power saving purposes.

[0360] As Figure 40 shown, when configured with the parameters of PSCH and PS operation, the wireless device may monitor PSCH during the PSCH monitoring occasion (e.g., on the first number of SSs and / or the second number of CORESETs) to detect DCI with a CRC scrambled by PS-RNTI. Based on the PSCH monitoring, the wireless device may detect the PS indication included in the DCI received via PSCH. The DCI may also indicate an active BWP switch. In response to receiving the PS indication via PSCH, the wireless device may start performing PS operation based on the one or more second configuration parameters of PS operation.

[0361] In one example, performing PS operation based on the one or more second configuration parameters may include at least one of the following: monitoring PDCCH on the third number of SSs and / or on the fourth number of CORESETs; suppressing monitoring of PSCH on the first number of SSs and / or the second number of CORESETs; suppressing monitoring of PDCCH on the fifth number of SSs and / or the sixth number of CORESETs; transmitting or receiving data packets using the first maximum number of antennas (layers, ports, TRPs, panels, etc.); and / or transmitting or receiving data packets using cross-slot scheduling based on the one or more first cross-slot scheduling indicators.

[0362] In one example, performing the PS operation may further include: switching the active BWP of one or more cells (e.g., PCell / SCell or cell group) to the inactivated BWP of the one or more cells. When DRX operation is not configured, the wireless device may continuously monitor the PDCCH on a third number of SSs and / or on a fourth number of CORESETs. When DRX operation is configured, the wireless device may discontinuously monitor the PDCCH on a third number of SSs and / or on a fourth number of CORESETs during the DRX active time (e.g., the next DRX on duration). In response to receiving DCI indicating an uplink grant or a downlink assignment, the wireless device may transmit or receive a data packet or TB based on monitoring the PDCCH.

[0363] In one example, in response to receiving a PS indication via the PSCH, based on the PS indication indicating a state transition of the SCell, the wireless device may transition the SCell from an active state to an inactivated state. The inactivated state of the SCell may be a period duration during which the wireless device may perform the following operations: stop monitoring the PDCCH on / for the SCell, stop receiving the PDSCH on the SCell, stop transmitting uplink signals (PUSCH, PUCCH, PRACH, DMRS, and / or PRACH) on the SCell, and / or transmit a CSI report for the SCell. The wireless device may maintain the inactivated state of the SCell until receiving a second indicator indicating a transition of the SCell from the inactivated state to the active state.

[0364] As Figure 40 shown, when the parameters of the PSCH and the PS operation are configured, the wireless device may monitor the PSCH during the PSCH monitoring occasion (e.g., on a first number of SSs and / or on a second number of CORESETs). For example, when the base station determines that the wireless device should remain in the full-function mode or the non-PS mode, the wireless device cannot detect the PS indication via the PSCH. In response to not receiving the PS indication via the PSCH, the wireless device may start operating in the full-function mode (e.g., non-inactivated state, wake-up state, full-power state, etc.) based on the one or more third configuration parameters.

[0365] In one example, the base station may transmit a PS indication indicating whether the wireless device should remain in the full-function mode. The wireless device may receive the PS indication via the PSCH. In response to the PS indication indicating that the wireless device should remain in the full-function mode, the wireless device may start operating in the full-function mode based on the one or more third configuration parameters.

[0366] In one example, performing operations in the full functionality mode based on the one or more third configuration parameters may include at least one of the following: monitoring PDCCH on a fifth quantity of SSs and / or a sixth quantity of CORESETs; suppressing monitoring of PSCH on a first quantity of SSs and / or a second quantity of CORESETs; suppressing monitoring of PDCCH on a third quantity of SSs and / or a fourth quantity of CORESETs; transmitting or receiving data packets using a second maximum quantity of antennas (layers, ports, TRPs, panels, etc.); transmitting or receiving data packets using the same slot scheduling based on the one or more second cross-slot scheduling indicators indicating the same slot scheduling. When DRX operation is not configured, the wireless device may continuously monitor PDCCH. When DRX operation is configured, the wireless device may discontinuously monitor PDCCH during the DRX active time. In response to receiving DCI indicating an uplink grant or a downlink assignment, the wireless device may transmit or receive data packets or TBs based on monitoring PDCCH.

[0367] Figure 41 An example of transmission and reception using multiple transmission reception points (TRPs) and / or multiple panels is shown in accordance with some embodiments. In one example, a base station may be equipped with more than one TRP (e.g., TRP 1 and TRP 2). A wireless device may be equipped with more than one panel (e.g., panel 1 and panel 2). Transmission and reception using multiple TRPs and / or multiple panels may improve system throughput and / or transmission robustness for wireless communication at high frequencies (e.g., above 6 GHz).

[0368] In one example, a TRP among the multiple TRPs of a base station may be identified by at least one of the following: a TRP identifier (ID), a cell index, or a reference signal index. In one example, the TRP ID of a TRP may include the control resource cluster group (or pool) index of the control resource cluster group from which the base station transmits DCI on a control resource set (e.g., CORESETPoolIndex ). In one example, the TRP ID of a TRP may include the TRP index indicated in the DCI. In one example, the TRP ID of a TRP may include the TCI state group index of a TCI state group. The TCI state group may include at least one TCI state in which the wireless device receives a downlink TB, or the base station transmits a downlink TB in the at least one TCI state.

[0369] In one example, when configured with multiple panels, a wireless device may determine to activate (or select) one of the multiple panels to receive a downlink signal / channel transmitted by one of multiple TRPs of a base station. The activation / selection of one of the multiple panels may be based on receiving downlink signaling indicating the activation / selection, or based on: measuring the downlink channel quality based on one or more reference signals transmitted from the base station. The wireless device may apply a spatial domain filter for transmission from one of the multiple panels to one of the multiple TRPs of the base station, and the spatial domain filter is determined based on at least one of the following: UL TCI indication of DCI, SRI indication of DCI, etc. In one example, when receiving DCI, the wireless device may determine a panel and a transmission beam (or spatial domain transmission filter) on the panel based on the SRS resource indicator (or uplink TCI) in the DCI. A panel may be identified by a panel ID. The panel ID may be indicated by an SRS ID (or SRS group / pool index), one or more fields of DCI, and / or a control resource set (CORESET) ID.

[0370] In one example, a base station may be equipped with multiple TRPs. The base station may transmit one or more RRC messages to the wireless device, and the one or more RRC messages include configuration parameters of multiple CORESETs on a cell (or a BWP of the cell). Each of the multiple CORESETs may be identified by a CORESET index and may be associated with (or configured with) a CORESET pool (or group) index. One or more CORESETs having the same CORESET pool index among the multiple CORESETs may indicate that the DCI received on the one or more CORESETs is transmitted from the same TRP among the multiple TRPs of the base station. The wireless device may determine a receive beam (or spatial domain filter) for PDCCH / PDSCH based on the TCI indication (e.g., DCI) and the CORESET pool index associated with the CORESET for the DCI.

[0371] In one example, when the wireless device receives one or more RRC messages including ControlResourceSet a first CORESET pool index in the IE (e.g., CORESETPoolIndex ) value and a second COESET pool index (e.g., PDCCH-Config IE (PDCCH-Configuration IE)), the wireless device may receive multiple PDCCHs scheduling PDSCHs that are fully overlapped / partially overlapped / non-overlapped in the time and frequency domains. When the PDCCHs scheduling two PDSCHs are associated with different CORESETPoolIndex having different values ControlResourceSetWhen, the wireless device can determine to receive only PDSCHs that completely / partially overlap in the time domain.

[0372] In one example, the wireless device can assume (or determine) that for CORESETPoolIndex without ControlResourceSet for ControlResourceSet is assigned a value of 0 CORESETPoolIndex . When scheduling the wireless device with PDSCHs that completely / partially / do not overlap in the time and frequency domains, the scheduling information for receiving the PDSCH is indicated and executed only by the corresponding PDCCH. It is expected to schedule the wireless device using the same active BWP and the same SCS. In one example, when scheduling the wireless device with PDSCHs that completely / partially / do not overlap in the time and frequency domains, the wireless device can be scheduled using at most two codewords simultaneously.

[0373] In one example, when the PDCCHs scheduling two PDSCHs are associated with different CORESETPoolIndex with different values of ControlResourceSet , the wireless device is allowed to perform the following operations: For any two HARQ process IDs in a given scheduled cell, if the wireless device is scheduled to start receiving a first PDSCH starting from symbol CORESETpoolIndex associated with the value of i and ending at symbol j via a PDCCH, then the wireless device can be scheduled to receive a PDSCH starting earlier than the end point of the first PDSCH using a PDCCH that ends later than symbol CORESETpoolIndex associated with a different value of i ; in a given scheduled cell, the wireless device can receive the first PDSCH and the second PDSCH in a time slot i , the first PDSCH has a corresponding HARQ-ACK assigned to be transmitted in time slot j , the second PDSCH is associated with CORESETpoolIndex a value different from that of the first PDSCH, the second PDSCH starts later than the first PDSCH, and has a corresponding HARQ-ACK assigned to be transmitted in a time slot before j .

[0374] In one example, if the wireless device is configured by a higher layer parameter ControlResourceSet containing two different values of CORESETPoolIndex in PDCCH-Config , then for both cases ， when tci-PresentInDCI (tci-present in DCI) is set to "enabled" and tci-PresentInDCIWhen not configured in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than a threshold timeDurationForQCL, then the wireless device can assume that in the latest time slot (where one or more CORESETs with the same value as the PDCCH that schedules the PDSCH within the active BWP of the serving cell are monitored by the wireless device), the DM-RS ports of the PDSCH associated with the value of the serving cell CORESETPoolIndex are QCL with the RS in terms of QCL parameters for the CORESET (which is configured with CORESETPoolIndex the same value as the PDCCH that schedules the PDSCH) among the CORESETs associated with the monitored search space with the lowest CORESETPoolIndex PDCCH quasi-co-location indication. If the offset between the reception of the DL DCI and the corresponding PDSCH is less than a threshold CORESET-ID and there is a configured TCI state of the serving cell of the scheduled PDSCH timeDurationForQCL "QCL-TypeD (QCL type D)", and at least one TCI code point indicates two TCI states, then the wireless device can assume that the DM-RS ports of the PDSCH of the serving cell are QCL with the RS in terms of QCL parameters associated with the TCI state corresponding to the lowest code point among the TCI code points that include two different TCI states. at least A configured TCI state include "QCL-TypeD (QCL type D)", and at least one TCI code point indicates two TCI states, then the wireless device can assume that the DM-RS ports of the PDSCH of the serving cell are QCL with the RS in terms of QCL parameters associated with the TCI state corresponding to the lowest code point among the TCI code points that include two different TCI states.

[0375] In one example, the wireless device can receive a first DCI including a first deactivation indication from a first TRP (e.g., identified by a first CORESET pool index) and a second DCI including a second deactivation indication from a second TRP (e.g., identified by a second CORESET pool index). The wireless device can receive two deactivation indications from two TRPs, e.g., when the base station does not coordinate the transmission of the two different deactivation indications from the two TRPs due to non-ideal backhaul. In one example, the first deactivation indication indicates a transition to a deactivated BWP of the cell. The second deactivation indication indicates a transition to a non-deactivated BWP of the cell. In the prior art, the wireless device can apply each of the first deactivation indication and the second deactivation indication to the cell individually. For example, if the wireless device receives the first deactivation indication earlier than the second deactivation indication, the wireless device can switch to the deactivated BWP of the cell and then switch to the non-deactivated BWP of the cell. Based on receiving different deactivation indications from multiple TRPs of the cell, switching back and forth between the non-deactivated BWP and the deactivated BWP of the cell can result in increased BWP switching latency, reduced system throughput, and / or increased power consumption of the wireless device.

[0376] When a wireless device (e.g., equipped with multiple panels) communicates with a base station equipped with multiple TRPs, exemplary embodiments can improve BWP switching latency, system throughput, and / or power consumption of the wireless device. Exemplary embodiments can include: transitioning the cell to an inactive BWP on a first TRP and / or maintaining the state of the active BWP of the cell on a second TRP based on a first inactivity indication received via the first TRP and / or a second inactivity indication received via the second TRP. Exemplary embodiments can include: monitoring the PDCCH on a first CORESET associated with the first TRP and skipping monitoring the PDCCH on a second CORESET associated with the second TRP based on receiving DCI including a first inactivity indication associated with the first TRP and a second inactivity indication associated with the second TRP. Exemplary embodiments can include: skipping monitoring the PDCCH on a first CORESET associated with the first TRP and skipping monitoring the PDCCH on a second CORESET associated with the second TRP based on receiving DCI including an inactivity indication.

[0377] In one example, the wireless device can receive a first DCI including a downlink assignment or an uplink grant on the active BWP of the cell from a first TRP (e.g., identified by a first CORESET pool index), and receive a second DCI including an inactivity indication from a second TRP (e.g., identified by a second CORESET pool index). The wireless device can receive two DCIs from the two TRPs, e.g., when the base station does not coordinate the transmission of the two DCIs from the two TRPs due to non-ideal backhaul. In one example, the first DCI indicates the scheduling of a data packet on the active BWP of the cell. The second inactivity indication indicates a transition to the inactive BWP of the cell. In the prior art, the wireless device can apply each of the two DCIs to the cell individually. For example, the wireless device can start receiving or transmitting a data packet based on the first DCI, and then during the process of receiving or transmitting the data packet, if the wireless device receives the first DCI earlier than the second DCI, switch to the inactive BWP of the cell based on the second DCI. For example, the wireless device can switch to the inactive BWP of the cell based on the second DCI, and if the wireless device receives the second DCI earlier than the first DCI, cannot transmit or receive a data packet based on the first DCI. By implementing the prior art, the wireless device can interrupt the ongoing data packet transmission or reception on the first TRP while performing an inactivity state transition based on the inactivity indication received from the second TRP. The prior art may reduce system throughput, increase data transmission latency, and / or signaling overhead.

[0378] When a wireless device (e.g., equipped with multiple panels) communicates with a base station equipped with multiple TRPs, exemplary embodiments can improve system throughput and / or power consumption of the wireless device. Exemplary embodiments can include maintaining the state of the active BWP of a cell on a first TRP and / or ignoring a dormancy indication received on a second TRP based on: the wireless device being in the process of data reception or transmission on the first TRP, and / or receiving a dormancy indication from the second TRP.

[0379] Figure 42 is a flowchart of an exemplary method for performing power saving operations using multiple TRPs / panels according to some embodiments. In one example, a wireless device may receive one or more RRC messages from a base station that include configuration parameters of a cell (e.g., a PCell or an SCell). The configuration parameters may include first parameters of multiple CORESETs grouped into multiple CORESET groups (or pools). Each CORESET of the multiple CORESETs may be identified by a CORESET ID (e.g., as Figure 26 shown controlResourceSetId ). Each CORESET of the multiple CORESETs may be associated with a CORESET pool index ( e.g., CORESETPoolIndex ). Each CORESET group (or pool) of the multiple CORESET groups (or pools) may include one or more CORESETs having the same CORESET group index (or pool index). In one example, when the wireless device is configured with more than one CORESET pool (e.g., more than one CORESET pool index), the wireless device may receive multiple DCIs scheduling PDSCHs that are completely / partially / non-overlapping in the time and frequency domains. When the DCIs scheduling two PDSCHs are associated with different CORESETPoolIndex with different values of ControlResourceSet , the wireless device may expect to receive PDSCHs that are completely / partially overlapping in the time domain.

[0380] In one example, a configuration parameter may indicate a first BWP among a plurality of BWPs of a cell as a dormant BWP of the cell. The wireless device may switch to the dormant BWP in response to receiving a dormant indication indicating a dormant transition for the cell. In one example, the configuration parameter may indicate that no SS or CORESET is configured on the dormant BWP. In response to switching to the dormant BWP of the cell, the wireless device may stop monitoring the PDCCH on the cell. In one example, the configuration parameter may indicate one or more CSI reports configured on the dormant BWP. In response to switching to the dormant BWP of the cell, the wireless device may transmit the one or more CSI reports for the dormant BWP of the cell (e.g., via the PCell or PUCCH SCell).

[0381] In one example, a configuration parameter may indicate a second BWP among the plurality of BWPs of the cell as a non-dormant BWP of the cell. The wireless device may switch to the non-dormant BWP in response to receiving a dormant indication indicating a non-dormant transition for the cell, e.g., when the wireless device stays on the dormant BWP of the cell before receiving the dormant indication.

[0382] In one example, when the cell is in an active state or a non-dormant state, the wireless device may monitor the PDCCH on one or more SSs of the plurality of CORESET pools of the active BWP of the cell for detecting DCI. The wireless device may receive two DCIs via different CORESET pools among the plurality of CORESET pools. In one example, the wireless device may receive a first DCI including a first dormant indication for the cell via a first SS of a first CORESET of a first CORESET pool among the plurality of CORESET pools. The wireless device may receive a second DCI including a second dormant indication for the cell via a second SS of a second CORESET of a second CORESET pool among the plurality of CORESET pools. The wireless device may receive the first DCI and the second DCI in the same time slot or different time slots. The first DCI and the second DCI may be UE-specific DCI formats (e.g., DCI format 0-0 / 0-1 / 1-0 / 1-1) or group-common DCI formats (e.g., DCI format 2-6).

[0383] In one example, in response to receiving the two dormant indications via two different CORESET pools, the wireless device may determine an action for the cell based on a first value of the first dormant indication and a second value of the second dormant indication.

[0384] In one example, in response to a first inactivity indication (e.g., set to a first value) indicating a non-inactivity transition including switching to a non-inactive BWP of a cell and a second inactivity indication (e.g., set to a second value) indicating an inactivity transition including switching to an inactive BWP of the cell, a wireless device may monitor a first CORESET pool on the active BWP of the cell based on the first inactivity indication and transmit one or more CSI reports for the inactive BWP of the cell based on the second inactivity indication. The active BWP may be the BWP (or non-inactive BWP) among the plurality of BWPs of the cell that was active on the cell before the wireless device received the first DCI. Monitoring the first CORESET pool may include: monitoring PDCCH candidates on one or more SSs configured on one or more CORESETs having a first CORESET pool index. The wireless device may measure one or more reference signals (e.g., PSS / SSS / PBCH and / or CSI-RS, DMRS) configured in the configuration parameters for the inactive BWP of the cell for the one or more CSI reports. In one example, the first CORESET pool may include one or more first CORESETs that are associated with one or more sets of SSs having a search space type parameter set to "common SS" (e.g., searchSpaceType )). In one example, the second CORESET pool may include one or more second CORESETs that are associated with one or more sets of SSs having a search space type parameter set to "UE-specific SS" (e.g., searchSpaceType ). In one example, the first CORESET pool may be the CORESET pool among the plurality of CORESET pools on the cell that has a CORESET pool index set to a first value (e.g., 0), or the lowest CORESET pool index among the plurality of CORESET pool indexes of the plurality of CORESET pools. In one example, the second CORESET pool may be the CORESET pool among the plurality of CORESET pools on the cell that has a CORESET pool index set to a second value different from the first value.

[0385] In one example, in response to the first inactivity indication indicating a non-inactivity transition, the second inactivity indication indicating an inactivity transition, the first inactivity indication being received via the first CORESET pool, and the second inactivity indication being received via the second CORESET pool, the wireless device may stop monitoring the second CORESET pool on the active BWP of the cell. Stopping monitoring the second CORESET pool may include: stopping monitoring PDCCH candidates on one or more SSs configured on one or more CORESETs having a second CORESET pool index.

[0386] In one example, in response to the second inactive indication indicating an inactive transition and the second inactive indication indicating a non-inactive transition, the wireless device may: monitor a second CORESET pool on the active BWP of the cell, transmit one or more CSI reports for the inactive BWP of the cell, and / or stop monitoring a first CORESET pool on the active BWP of the cell.

[0387] In one example, in response to both the first inactive indication and the second inactive indication indicating an inactive transition, the wireless device may: stop monitoring the PDCCH on the first CORESET pool and the second CORESET pool, and / or switch to the inactive BWP, including transmitting a CSI report for the inactive BWP of the cell.

[0388] In one example, in response to both the first inactive indication and the second inactive indication indicating a non-inactive transition, the wireless device may maintain the state of the active BWP, including: monitoring the PDCCH on the first CORESET pool and the second CORESET pool of the active BWP of the cell.

[0389] In Figure 42 the example of, in response to receiving two different inactive indications, the wireless device may maintain the state of the active BWP of the cell and transmit a CSI for the inactive BWP of the cell (e.g., for the same duration). Maintaining the state of the active BWP may include: monitoring the PDCCH on the first CORESET pool (e.g., associated with the first TRP of the cell) of the plurality of CORESET pools and not monitoring the PDCCH on at least a second CORESET pool (e.g., associated with the second TRP of the cell) of the plurality of CORESET pools. The first CORESET pool includes a first CORESET on which the wireless device receives a first inactive indication indicating a non-inactive transition. The second CORESET pool includes a second CORESET on which the wireless device receives a second inactive indication indicating an inactive transition. This implementation may improve data transmission latency (e.g., by maintaining PDCCH monitoring on the first CORESET pool of the cell) and reduce the power consumption of the wireless device (e.g., by stopping monitoring the PDCCH on the second CORESET pool of the cell). This implementation may enable the base station to obtain an up-to-date CSI report for the inactive BWP (for later data scheduling via the second TRP) (e.g., by transmitting a CSI report for the inactive BWP from the wireless device). This implementation may improve system throughput.

[0390] Figure 43is a flowchart of an exemplary method for performing power saving operations using multiple TRPs / panels according to some embodiments. In one example, a wireless device may receive one or more RRC messages from a base station that include configuration parameters of a cell (e.g., a PCell or an SCell). The configuration parameters may be similar to those discussed above with respect to Figure 42 those discussed.

[0391] In one example, when the cell is in an active state or a non-idle state, the wireless device may monitor the PDCCH on one or more SSs of multiple CORESET pools of the active BWP of the cell for detecting DCI. The wireless device may receive two DCIs via different CORESET pools among the multiple CORESET pools. In one example, the wireless device may receive a first DCI via a first SS of a first CORESET of a first CORESET pool of the multiple CORESET pools, the first DCI including a first idle indication for the cell. The wireless device may receive a second DCI via a second SS of a second CORESET of a second CORESET pool of the multiple CORESET pools, the second DCI including a second idle indication for the cell. The wireless device may receive the first DCI and the second DCI in the same time slot or different time slots.

[0392] In one example, in response to receiving the first idle indication via the first CORESET pool and the second idle indication via the second CORESET pool, the wireless device may determine to apply one of the two idle indications to the cell and / or ignore the other of the two idle indications based on a comparison of a first CORESET pool index of the first CORESET pool and a second CORESET pool index of the second COESET pool.

[0393] In one example, in response to the first CORESET pool index being lower than the second CORESET pool index, the wireless device may apply the first idle indication to the cell and / or ignore the second idle indication. Applying the first idle indication to the cell may include: switching to the idle BWP of the cell in response to the first idle indication indicating an idle state of the cell, regardless of the second idle indication. Applying the first idle indication to the cell may include: maintaining the state of the active BWP of the cell in response to the first idle indication indicating a non-idle state of the cell, regardless of the second idle indication.

[0394] In one example, in response to a second CORESET pool index being lower than a first CORESET pool index, a wireless device may apply a second inactivity indication to a cell and / or ignore a first inactivity indication. Applying the second inactivity indication to the cell may include: switching to an inactive BWP of the cell in response to the second inactivity indication indicating an inactive state of the cell, regardless of the first inactivity indication. Applying the second inactivity indication to the cell may include: maintaining a state of an active BWP of the cell in response to the second inactivity indication indicating a non-inactive state of the cell, regardless of the first inactivity indication.

[0395] In Figure 43 an example, the wireless device may determine to apply one of the inactivity indications received on the plurality of CORESET pools (and / or ignore the remaining inactivity indications). The wireless device may apply a first inactivity indication among the plurality of inactivity indications received on a CORESET pool having a lowest CORESET pool index among the plurality of CORESET pool indexes having the plurality of CORESET pools. Applying the first inactivity indication may include: maintaining a state of an active BWP of the cell in response to the first inactivity indication indicating a non-inactive state of the cell; or switching to an inactive BWP of the cell in response to the first inactivity indication indicating an inactive state of the cell. This embodiment may improve power consumption of the wireless device. This embodiment may improve alignment between the base station and the wireless device regarding a cell state when the base station transmits and the wireless device receives the plurality of inactivity indications on the plurality of TRPs. This embodiment may improve system throughput and / or data transmission latency.

[0396] In one example, the base station may transmit an inactivity indication via one of the plurality of CORESET pools. The base station may not transmit the plurality of inactivity indications via the plurality of CORESET pools. One of the plurality of CORESET pools on which the base station transmits the inactivity indication may be configured in configuration parameters of the cell. In one example, one of the plurality of CORESET pools for the inactivity indication may be predefined (e.g., a first CORESET pool having the lowest CORESET pool index). Transmitting the inactivity indication via one CORESET pool instead of via the plurality of CORESET pools may improve power consumption of the wireless device, reduce signaling overhead of the base station, and / or reduce inactivity indication processing complexity of the wireless device.

[0397] Figure 44 illustrates an exemplary power saving operation using multiple TRPs / panels according to some embodiments. In one example, the wireless device may receive one or more RRC messages from the base station including configuration parameters of a cell (e.g., a PCell or an SCell). The configuration parameters may be similar to those described above with respect to Figure 42Those configuration parameters discussed

[0398] In one example, the configuration parameter may indicate whether the wireless device applies the quiescence indication included in the DCI to a single CORESET pool or multiple CORESET pools. In response to the configuration parameter indicating that the wireless device applies the quiescence indication to a single CORESET pool, the wireless device may apply the quiescence indication to the single CORESET pool and not apply the quiescence indication to other CORESET pools. Applying the quiescence indication to a CORESET pool may include: monitoring the PDCCH on the SS of one or more CORESETs in the CORESET pool in response to the quiescence indication indicating a non-quiescent state of the cell. Applying the quiescence indication to a CORESET pool may include: stopping monitoring the PDCCH on the SS of one or more CORESETs in the CORESET pool in response to the quiescence indication indicating a quiescent state of the cell. In response to the configuration parameter indicating that the wireless device applies the quiescence indication to all CORESET pools, the wireless device may apply the quiescence indication to all CORESET pools, regardless of which CORESET pool the wireless device receives the quiescence indication on.

[0399] In one example, when the cell is in a quiescent state, the wireless device may skip monitoring the PDCCH and / or transmitting a CSI report regarding the quiescent BWP of the cell. The wireless device may receive a DCI including a quiescence indication indicating a switch to the non-quiescent BWP of the cell. The wireless device may receive the DCI via an active (or non-quiescent) PCell, PSCell, or second SCell.

[0400] In one example, in response to receiving a quiescence indication indicating a switch to the non-quiescent BWP of the cell, the wireless device may switch from the quiescent BWP of the cell to the non-quiescent BWP of the cell. In response to receiving a quiescence indication indicating a switch to the non-quiescent BWP of the cell, the wireless device may monitor the PDCCH on the first CORESET pool on the non-quiescent BWP of the cell and / or skip monitoring the PDCCH on the remaining CORESET pools. The first CORESET pool may be the CORESET pool having the lowest CORESET pool index among the multiple CORESET pool indices of the multiple CORESET pools. The first CORESET pool may be the CORESET pool configured with an SS having a first SS type (e.g., a common SS).

[0401] In Figure 44In an example, in response to receiving a quiescence indication indicating a non-quiescent transition, a wireless device may start monitoring a first CORESET pool (e.g., associated with a first TRP or a primary TRP) among multiple pools (e.g., associated with multiple TRPs). Monitoring a single TRP (or the primary TRP) immediately upon receiving a non-quiescent transition instead of the PDCCH on multiple TRPs may improve the power consumption of the wireless device. Stopping monitoring the multiple TRPs immediately upon receiving a quiescent transition may improve the power consumption of the wireless device.

[0402] In one example, a base station may transmit DCI including multiple quiescence indications (or power saving indications as shown in Figure 39A , Figure 39B and / or Figure 40 ), each quiescence indication corresponding to a TRP (or a CORESET pool) among multiple TRPs (or multiple CORESET pools). Transmitting multiple quiescence indications for multiple TRPs in a single DCI may improve the downlink signaling overhead and / or reduce the signaling processing complexity of the wireless device.

[0403] Figure 45 illustrates an exemplary power saving operation using multiple TRPs / panels according to some embodiments. In one example, a wireless device may receive one or more RRC messages from a base station including configuration parameters of a cell (e.g., a PCell or an SCell). The configuration parameters may be similar to those described above with respect to Figure 42 .

[0404] In one example, when a cell is in a quiescent state, the wireless device may skip monitoring the PDCCH and / or transmitting a CSI report on the quiescent BWP of the cell. The wireless device may receive DCI including multiple quiescence indications, each quiescence indication corresponding to a CORESET pool among multiple CORESET pools. The wireless device may receive the DCI via an active (or non-quiescent) PCell, PSCell, or a second SCell.

[0405] In one example, in response to a first inactive indication corresponding to a first CORESET pool among the plurality of CORESET pools indicating a non-inactive state of a cell, a wireless device may monitor PDCCH on one or more SSs on the first CORESET pool of the non-inactive BWP of the cell. In response to a second inactive indication corresponding to a second CORESET pool among the plurality of CORESET pools indicating an inactive state of the cell, the wireless device may skip monitoring PDCCH on one or more SSs on the second CORESET pool of the non-inactive BWP of the cell. By implementing the exemplary embodiment, the wireless device may apply the inactive indication received in DCI among the plurality of inactive indications to a corresponding TRP among the plurality of TRPs. This embodiment may enable a base station to flexibly manage the inactive / non-inactive states of a plurality of TRPs (or CORESET pools). This embodiment may improve the downlink signaling overhead and / or signaling processing complexity of the wireless device.

[0406] Figure 45 It can be extended to other power saving operations, including: wake-up / sleep operations with DRX operations (e.g., based on Figure 39A and / or Figure 39B ); PDCCH monitoring adaptation on the active BWP of a cell (e.g., based on Figure 40 , with or without switching to the inactive BWP of the cell); maximum MIMO layer adaptation; and / or cross-slot scheduling indication. In one example, a wireless device may receive DCI including a plurality of power saving indications, each power saving indication corresponding to a CORESET pool among the plurality of CORESET pools. The wireless device may receive DCI via a PCell, a PSCell, or a second SCell in an active state (or non-inactive state). The power saving indication may include at least one of the following: a wake-up / sleep indication; an SCell inactive indication; or a PDCCH monitoring configuration index identifying one or more PDCCH monitoring parameters (e.g., PDCCH monitoring period, number of PDCCH candidates, number of SSs, etc.).

[0407] In one example, in response to a first power saving indication corresponding to a first CORESET pool among the plurality of CORESET pools in the plurality of power saving indications indicating a first power saving operation of a cell, a wireless device may apply the first power saving operation to one or more SSs on the first CORESET pool of the cell. The first power saving operation may include at least one of the following: skipping PDCCH monitoring during the DRX active time and / or switching to the inactivity BWP of the cell. The first power saving operation may include: monitoring the PDCCH on the active BWP of the cell with a reduced monitoring period based on the first power saving indication. The first power saving operation may include: monitoring the PDCCH on a reduced number of search spaces (or CORESETs) based on the first power saving indication. The first power saving operation may include: reducing the maximum MIMO layer based on the first power saving indication. The first power saving operation may include: implementing cross-slot scheduling based on the first power saving indication. In response to a second power saving indication corresponding to a second CORESET pool among the plurality of CORESET pools in the plurality of power saving indications indicating a second power saving operation of the cell, the wireless device may apply the second power saving operation to one or more SSs on the second CORESET pool of the cell. The second power saving operation may include at least one of the following: skipping PDCCH monitoring during the DRX active time and / or switching to the inactivity BWP of the cell. The second power saving operation may include: monitoring the PDCCH on the active BWP of the cell with a reduced monitoring period based on the second power saving indication. The second power saving operation may include: monitoring the PDCCH on a reduced number of search spaces (or CORESETs) based on the second power saving indication. The second power saving operation may include: reducing the maximum MIMO layer based on the second power saving indication. The second power saving operation may include: implementing cross-slot scheduling based on the second power saving indication. By implementing the exemplary embodiment, the wireless device may apply the power saving indication received in the DCI among the plurality of power saving indications to the corresponding TRP among the plurality of TRPs. This embodiment may enable the base station to flexibly manage the power states of the plurality of TRPs (or CORESET pools). This embodiment may improve the downlink signaling overhead and / or signaling processing complexity of the wireless device.

[0408] Figure 46 An exemplary DCI format for power saving indications for a plurality of TRPs (or CORESET pools) according to some embodiments is shown. In one example, a wireless device may receive one or more RRC messages from a base station that include configuration parameters of a cell (e.g., a PCell or an SCell). The configuration parameters may be similar to those described above with respect to Figure 42 those described. [04...

Claims

1. A communication method, comprising: Receiving, by a wireless device, configuration parameters of a cell, the configuration parameters indicating: A first control resource set (CORESET) associated with a first CORESET pool index; and A second CORESET associated with a second CORESET pool index; Receiving downlink control information, the downlink control information indicating: A CORESET pool index; And A power saving indication, the power saving indication indicating a power saving operation for the cell; And Applying the power saving operation to the first CORESET of the cell based on the CORESET pool index in the downlink control information being the first CORESET pool index.

2. The method according to claim 1, further comprising: Monitoring a physical downlink control channel of the first CORESET; And Monitoring a physical downlink control channel of the second CORESET.

3. The method according to claim 2, wherein applying the power saving operation to the first coreset includes: During a discontinuous reception (DRX) active time, skipping monitoring of the physical downlink control channel of the first CORESET associated with the first CORESET pool index.

4. The method according to any one of claims 1 to 3, further comprising not applying the power saving operation to the second CORESET based on the CORESET pool index being a first CORESET pool index different from the second CORESET pool index.

5. The method according to claim 1, further comprising: Receiving second downlink control information including a second power saving indication and not including the CORESET pool index, the second power saving indication indicating the power saving operation for the cell; and In response to the absence of the CORESET pool index in the second downlink control information, applying the power saving operation to the first CORESET and the second CORESET of the cell.

6. A wireless device, comprising one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, cause the wireless device to perform the method according to any one of claims 1 to 5.

7. A non-transitory computer-readable medium including instructions, the instructions, when executed by one or more processors of a wireless device, cause the wireless device to perform the method according to any one of claims 1 to 5.

8. A communication method, comprising: Transmitting, by a base station, configuration parameters of a cell to a wireless device, the configuration parameters indicating: A first control resource set (CORESET) associated with a first CORESET pool index; and A second CORESET associated with a second CORESET pool index; And Transmitting downlink control information to the wireless device, the downlink control information indicating: A CORESET pool index; And A power saving indication, the power saving indication indicating a power saving operation for the cell, Wherein, based on the coreset pool index in the downlink control information being the first coreset pool index, the wireless device applies the power saving operation to the first coreset of the cell.

9. The method according to claim 8, further comprising: Transmitting a physical downlink control channel of the first coreset; And Transmitting a physical downlink control channel of the second coreset.

10. The method according to claim 9, wherein applying the power saving operation to the first coreset by the wireless device comprises: During a discontinuous reception (DRX) active time, the wireless device skips monitoring the physical downlink control channel of the first coreset associated with the first coreset pool index.

11. According to the method according to any one of claims 8-10, wherein, Based on the coreset pool index being a first coreset pool index different from the second coreset pool index, the wireless device does not apply the power saving operation to the second coreset.

12. The method according to claim 8, further comprising: Transmitting second downlink control information including a second power saving indication and not including the coreset pool index, the second power saving indication indicating the power saving operation for the cell, Wherein, in response to the absence of the coreset pool index in the second downlink control information, the wireless device applies the power saving operation to the first coreset and the second coreset of the cell.

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

14. A non - volatile computer - readable medium comprising instructions that, when executed by one or more processors of a base station, cause the base station to perform the method according to any one of claims 8 to 12.

15. A communication system comprising: A base station comprising one or more first processors and a first memory storing first instructions that, when executed by the one or more first processors, cause the base station to: Transmit configuration parameters of a cell, the configuration parameters indicating: A first control resource set (coreset) associated with a first coreset pool index; and A second coreset associated with a second coreset pool index; and Transmit downlink control information, the downlink control information indicating: A coreset pool index; And A power saving indication, the power saving indication indicating the power saving operation for the cell; And A wireless device comprising one or more second processors and a second memory storing second instructions that, when executed by the one or more second processors, cause the wireless device to: Receive the configuration parameters of the cell; Receive the downlink control information; and Based on the coreset pool index in the downlink control information being the first coreset pool index, apply the power saving operation to the first coreset of the cell.

Images