Method, apparatus, computer medium for downlink control channel switching

Abstract

A wireless device receives a configuration parameter indicating a duration value for skipping a physical downlink control channel (PDCCH) monitoring over a bandwidth portion (BWP). The duration value is from: a first value having a first subcarrier spacing (SCS) in response to the BWP; and in response to the BWP having a second value of a second SCS, wherein each of the second values is equal to a product of a respective one of the first values and the same granularity value. Downlink control information (DCI) indicating that PDCCH monitoring on the BWP is skipped over a duration based on a duration value of the duration values is received. And the wireless equipment skips to monitor the PDCCH on the BWP within the duration time based on the DCI.

Description

[0001] Divisional application

[0002] This application is a divisional application of the Chinese invention patent application with application number 2022800354193. The name of the invention of the application with application number 2022800354193 is "Method, device, and computer medium for downlink control channel skipping" and the application date is March 17, 2022.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application claims the benefit of U.S. Provisional Application No. 63 / 162,286, filed on March 17, 2021, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0006] Figure 1A and Figure 1B An example mobile communications network is shown in which embodiments of the present disclosure may be implemented.

[0007] Figure 2A and Figure 2B New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0008] Figure 3 Shown in Figure 2A Examples of services provided between the protocol layers of the NR user plane protocol stack.

[0009] Figure 4A Shows the flow Figure 2A Figure 2. Example downlink data flow of the NR user plane protocol stack.

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

[0011] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels for downlink and uplink are shown respectively.

[0012] Figure 6 is an example diagram showing RRC state transition of a UE.

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

[0014] Figure 8An example configuration of time slots in the time and frequency domain of an NR carrier is shown.

[0015] Fig. 9 An example of bandwidth adaptation using three configured BWPs for NR carriers is shown.

[0016] Fig. 10A Three carrier aggregation configurations with two component carriers are shown.

[0017] Fig. 10B An example of how aggregated cells may be configured into one or more PUCCH groups is shown.

[0018] Fig.11A An example of SS / PBCH block structure and location is shown.

[0019] Fig. 11B An example of CSI-RS mapped in the time and frequency domains is shown.

[0020] Fig. 12A and Fig. 12B Three examples of downlink and uplink beam management procedures are shown respectively.

[0021] Fig.13A , Fig. 13B and Fig. 13C A four-step contention-based random access procedure, a two-step contention-free random access procedure and another two-step random access procedure are shown respectively.

[0022] Fig.14A An example of a CORESET configuration for the bandwidth portion is shown.

[0023] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown.

[0024] Fig.15 An example of a wireless device in communication with a base station is shown.

[0025] Fig.16A , Fig. 16B , Fig. 16C and Fig.16D Exemplary structures for uplink and downlink transmissions are shown.

[0026] Fig.17A , Fig. 17B and Fig. 17C An example of a MAC subheader is shown.

[0027] Fig.18A An example of a DL MAC PDU is shown.

[0028] Fig.18B An example of a UL MAC PDU is shown.

[0029] Fig.19 An example of multiple LCIDs for the downlink is shown.

[0030] Fig. 20 An example of multiple LCIDs for the uplink is shown.

[0031] Fig.21A and Fig. 21B An example of the SCell activation / deactivation MAC CE format is shown.

[0032] Fig.22A and Fig. 22B An example of a DRX configuration is shown.

[0033] Fig.23 An example of BWP activation / deactivation on a cell according to some embodiments is shown.

[0034] Fig.24 Examples of various DCI formats are shown according to some embodiments.

[0035] Fig.25 An example of a dormant configuration of a cell according to some embodiments is shown.

[0036] Fig.26 An example of RRC configuration of control resource sets according to some embodiments is shown.

[0037] Fig. 27 An example of RRC configuration of a search space according to some embodiments is shown.

[0038] Fig.28A and Fig.28B An example of a search space group switching operation is shown in accordance with some embodiments.

[0039] Fig.29 An example of a PDCCH skipping operation according to some embodiments is shown.

[0040] Fig.30 An example of power saving based on PDCCH skipping according to some embodiments is shown.

[0041] Fig.31 An exemplary flow chart of a method for achieving power saving based on PDCCH skipping according to some embodiments is shown.

[0042] Fig.32 An example of PDCCH skipping based power saving for a BWP configured with subcarrier spacing is shown according to some embodiments.

[0043] Fig.33 An example of power saving based on PDCCH skipping over multiple cells is shown according to some embodiments.

[0044] Fig.34 A diagram is shown illustrating an example of PDCCH skipping across multiple cells according to some embodiments.

[0045] Fig.35 An example of power saving based on PDCCH skipping over multiple cell groups is shown according to some embodiments.

[0046] Fig.36 An example of power saving based on PDCCH skipping over multiple cell groups is shown according to some embodiments.

[0047] Fig.37 An example of power saving based on PDCCH skipping with DRX operation according to some embodiments is shown. DETAILED DESCRIPTION

[0048] 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 environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, 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 to any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Restrictions, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided only for illustrative purposes. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0049] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments may be applied. Therefore, exemplary embodiments that selectively implement the disclosed protocol may be implemented.

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

[0051] In the present disclosure, "a" and "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 a suitable possibility among multiple suitable possibilities that may or may not be used for one or more embodiments in various embodiments. As used herein, the terms "comprising" and "consisting of..." list one or more components of the element being described. The terms "comprising" and "including" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of..." provides a complete listing of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the listed elements. For example, “A, B and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0052] If A and B are sets, and every elementis 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") indicates that the phrase after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopt / use" (or equivalently "at least adopt / use") indicates that the phrase after the phrase "adopt / use" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

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

[0054] In the present disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may 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 a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

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

[0056] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented by hardware, software, firmware, wetware (for example, hardware with biological elements) in combination with hardware, or a combination thereof, all of which can be equivalent in behavior.For example, a module can be implemented as a software routine written in a computer language, which 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 LabVIEWMathScript).It is possible to implement a module using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware.Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between less functional internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

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

[0058] The CN 102 may 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 intra-carrier DN, for the wireless device 106. As part of the interface functionality, the CN 102 may set up an end-to-end connection between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

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

[0060] The term "wireless device" may be used throughout this disclosure to mean and encompass any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle roadside unit (RSU), a relay node, a car, 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.

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

[0062] The base stations included in the RAN 104 may include one or more sets of antennas for communicating with the wireless devices 106 over the 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 the cell may be determined by the range at 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 stations may together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0063] In addition to three-sector sites, 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 less 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 several 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 baseband processing unit pool or virtualized. The repeater node may amplify and rebroadcast the radio signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signal received from the donor node to eliminate noise before amplifying and rebroadcasting the radio signal.

[0064] The RAN 104 may be deployed as a homogeneous network of macrocell base stations with similar antenna types and similar high levels of transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, a small cell base station may be used to provide a small coverage area, such as a coverage area that overlaps with a relatively large coverage area provided by a macrocell base station. Small coverage areas may be provided in areas with high data traffic (or so-called "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

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

[0067] 5G-CN 152 provides an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an operator's internal DN, to UE 156. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CN of the 3GPP 4G network, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as network functions that provide services to other network functions via interfaces. The network functions of 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).

[0068] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. For ease of explanation, Figure 1BThey are shown as one component AMF / UPF 158 in FIG. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification to support routing of service flows to the one or more DNs, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement and uplink service verification), downlink packet buffering and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected with the one or more DNs, and / or a fulcrum for supporting multi-host PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

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

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

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

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

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

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

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

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

[0077] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE 210 and gNB 220 are shown, respectively. Figure 2A and Figure 2B The protocol stack shown in can be used with e.g. Figure 1B The protocol stacks of the Uu interface between UE156A and gNB 160A shown in are the same or similar.

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

[0079] Figure 3 An example of services provided between protocol layers of the NR user plane protocol stack is shown. Figure 2A and Figure 3 Starting from the top of , SDAP 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and DN. A 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 delay, data rate and / or error rate). 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 flows and the data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0080] The PDCP 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, may perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and may perform integrity protection to ensure that control messages originate from the intended source. The PDCP 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets due to, for example, intra-gNB handovers. The PDCP 214 and 224 may perform packet repetition to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet repetition may be applicable to services that require high reliability.

[0081] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technology that allows a UE to connect to two cells or more generally to two cell groups: a primary 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 PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapped split radio bearers between RLC channels belonging to a cell group.

[0082] RLC 213 and 223 can perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222, respectively. RLC 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the functions described. RLC configuration can be based on each logical channel, independent of parameter sets and / or transmission time interval (TTI) duration. As shown in FIG. Figure 3 As shown in FIG. 1 , RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0083] The MAC 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to the one or more logical channels into / from a transport block (TB) delivered to / from the PHY 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs with the aid of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction by 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 the UE 210 with the aid of logical channel prioritization, and / or padding. The MAC 212 and 222 may support one or more parameter sets and / or transmission timing. In an example, mapping restrictions in the logical channel prioritization may control which parameter sets and / or transmission timings may be used by the logical channels. Figure 3 As shown, MAC 212 and 222 may provide logical channels as services to RLC 213 and 223 .

[0084] PHY 211 and 221 can perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY 211 and 221 can perform multi-antenna mapping. Figure 3 As shown in , PHY 211 and 221 may provide one or more transport channels as a service to MAC 212 and 222 .

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

[0086] 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 a radio bearer. Figure 4A In the SDAP header (in Figure 4AThe data unit from / to a higher protocol layer is called a service data unit (SDU) of the lower protocol layer, and the data unit to / from a lower protocol layer is called a protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225 .

[0087] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., Figure 3 ), add the corresponding headers, and forward their corresponding outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A 222) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDU, as shown in FIG. Figure 4A In LTE, the MAC subheader can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU subheader can be calculated before assembling the complete MAC PDU.

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

[0089] Figure 4B Further shown is a MAC Control Element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B Two MAC CEs are shown inserted into the MAC PDU. Figure 4B) and inserting a MAC CE at the end of a MAC PDU for uplink transmission. MAC CE may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those used 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 subheader having a format similar to that described for a MAC SDU may be present before the MAC CE, and the MAC CE may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

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

[0091] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels is shown for downlink and uplink respectively. Information is passed through channels between RLC, MAC and PHY of the NR protocol stack. Logical channels can be used between RLC and 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. 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. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0092] - Paging Control Channel (PCCH), which is used to carry paging messages used to page UEs whose location is unknown to the network at the cell level;

[0093] - 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), which can be used by UEs to obtain information about how a cell is configured and how it operates within the cell;

[0094] - Common Control Channel (CCCH), which is used to carry control messages and random access;

[0095] - a dedicated control channel (DCCH) used to carry control messages to / from a specific UE to configure the UE; and

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

[0097] 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:

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

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

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

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

[0102] - Random Access Channel (RACH), which is used to allow a UE to contact the network without any previous scheduling.

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

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

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

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

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

[0108] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI) and scheduling request (SR); and

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

[0110] Similar to the physical control channel, the physical layer generates physical signals to support the lower-level operations of the physical layer. Figure 5A and Figure 5B As shown in , 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.

[0111] Figure 2B An example NR control plane protocol stack is shown. Figure 2B As shown in , the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack instead has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

[0113] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 or more generally between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transported between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 may provide control plane functions such as: broadcast of system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance and release of an RRC connection between UE 210 and 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 reporting; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS messaging. As part of establishing an RRC connection, the RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

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

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

[0116] In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with a base station. When in RRC idle 604, the UE may be in a sleep state for 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 known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0117] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows a quick transition to RRC Connected 602 with reduced signaling overhead compared to the transition from RRC Idle 604 to RRC Connected 602. While in RRC Inactive 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 RRC Inactive 606 to RRC Connected 602 through a Connection Resumption Procedure 614, or to RRC Idle 604 through a Connection Release Procedure 616, which may be the same or similar to the Connection Release Procedure 608.

[0118] The RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to notify the UE of an event via a paging message without broadcasting the paging message over the entire mobile communication network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE at a cell group level, so that the paging message may be broadcast over a cell in the cell group in which the UE currently resides instead of over the entire mobile communication network. The mobility management mechanism used for RRC idle 604 and RRC inactive 606 tracks the UE at a cell group level. These mobility management mechanisms may do so using groups of different granularities. For example, there may be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

[0119] Tracking areas may be used to track UEs at the CN level. A CN (e.g., CN 102 or 5G-CN 152) may provide a list of TAIs associated with UE registration areas to a UE. If a UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with a UE registration area, the UE may 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.

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

[0121] The base station storing the RRC context for the UE or the last serving base station of the UE may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or during the period of time that the UE remains in RRC inactivity 606.

[0122] gNBs, such as Figure 1BThe gNB 160 in the embodiment of the present invention 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 may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0123] In NR, physical signals and physical channels (about Figure 5A and Figure 5B Discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-quadrature 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 treated as if they are in the frequency domain and used as input to the 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 sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal subcarriers. 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 symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the 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 FFT block can be used to perform inverse processing on the OFDM symbol at the receiver to restore the data mapped to the source symbol.

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

[0125] The duration of a time slot may depend on a parameter set for the OFDM symbol used for the 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 mm-wave range). Parameter sets may be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines 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.

[0126] A slot may have a fixed number of OFDM symbols (eg, 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 The transmission structure of the time slot duration and each subframe time slot associated with the parameter set is shown (for ease of explanation, Figure 7 Parameter sets with subcarrier spacing of 240kHz are not shown in FIG. 1 ). Subframes in NR can be used as a time reference independent of parameter sets, while slots can be used as the unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the slot duration and start at any OFDM symbol and continue transmitting as many symbols as needed. These partial slot transmissions can be referred to as microslots or subslot transmissions.

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

[0128] Figure 8A single parameter set is shown used across the entire bandwidth of the NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

[0129] NR may 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). Moreover, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, the UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

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

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

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

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

[0134] One or more BWP indicator fields may be provided in downlink control information (DCI). The value of the BWP indicator field may indicate which BWP in a 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.

[0135] 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.

[0136] The base station may configure the BWP inactivity timer value for the PCell for the UE. 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 in the following circumstances: (a) when the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect the 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.

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

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

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

[0140] If the UE is configured for a secondary cell with a default downlink BWP and timer values ​​from the 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 the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values ​​for the primary cell.

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

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

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

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

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

[0146] The downlink control information of a cell (such as scheduling assignments and scheduling grants) 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 confirmation 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. The cell can be divided into multiple PUCCH groups.

[0147] Fig. 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 may include one or more downlink CCs, respectively. Fig. 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) may 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) may be transmitted in the uplink of PSCell 1061. In the example, if Fig. 10B If the aggregated cell depicted in FIG. 1 is not divided into PUCCH group 1010 and PUCCH group 1050 , a single uplink PCell transmits UCI associated with a downlink CC, and the PCell may become overloaded. Overload may be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061 .

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

[0149] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, the HARQ entity can operate on the serving cell. A transport block can be generated based on the assignment / grant of each serving cell. A transport block and potential HARQ retransmissions of the transport block can be mapped to a serving cell.

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

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

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

[0153] The UE may not know the location of the SS / PBCH blocks in the time and frequency domains (for example, when the UE is searching for cells). In order to find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain duration (for example, 20ms), the UE may 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 may determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block may be a cell definition SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, cell selection / search and / or reselection may be based on the CD-SSB.

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

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

[0156] The UE may 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 may not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices.

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

[0158] In an example, within a frequency range of a carrier, a base station may transmit multiple SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block of the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted in different frequency positions may be different or the same.

[0159] The CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more CSI-RSs of the same / similar CSI-RS. The UE may measure the one or more CSI-RSs. The UE may 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 may provide the CSI report to the base station. The base station may use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

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

[0161] 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 reporting, the UE can be configured with the timing and / or period of multiple CSI reports. For aperiodic CSI reporting, 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 value. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reporting. The base station can configure the UE with a CSI-RS resource set and CSI reporting using RRC signaling.

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

[0163] 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 consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. The frontload 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., maximum number) of frontload DMRS symbols for 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 downlink and uplink, in which the DMRS position, DMRS pattern and / or scrambling sequence can be the same or different. The base station may use the same precoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE may use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

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

[0165] The PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. The higher layers may configure up to 3 DMRS for the PDSCH.

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

[0167] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS to consistently demodulate one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS mode. The front-loaded DMRS may be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of front-loaded DMRS symbols for the PUSCH and / or PUCCH, and the UE may use the front-loaded DMRS symbol to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS positions, DMRS patterns, and / or scrambling sequences of the DMRS may be the same or different.

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

[0169] Depending on the RRC configuration of the UE, an uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or type of the uplink PT-RS can be configured based on UE-specific configuration through a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least the MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use 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 limited to the scheduled time / frequency duration of the UE.

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

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

[0172] The antenna ports are defined so that the channel through which a symbol on the antenna port is communicated can be inferred from the channel through which another symbol on the same antenna port is communicated. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port. If one or more large-scale properties of the channel through which the first symbol on the first antenna port is communicated can be inferred from the channel through which the second symbol on the second antenna port is communicated, 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) parameters.

[0173] 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 beamforming reference signals. The UE may perform downlink beam measurements and generate beam measurement reports based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)). After setting up an RRC connection with a base station, the UE may perform a downlink beam measurement procedure.

[0174] Fig. 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Fig. 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters may be configured for the CSI-RS resource configuration through 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 periodicity 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-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid) and / or other radio resource parameters.

[0175] Fig. 11B The three beams shown may be configured for a UE in a UE-specific configuration. Fig. 11B Three beams (beam #1, beam #2, and beam #3) are illustrated in FIG. 1 , and more or fewer beams may be configured. CSI-RS 1101 may be allocated to beam #1, which may be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS 1102 may be allocated to beam #2, which may be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS 1103 may be allocated 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), a base station may use other subcarriers in the same RB (e.g., those subcarriers not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time domain multiplexing (TDM), a beam for a UE may be configured so that the beam for the UE uses symbols from beams of other UEs.

[0176] CSI-RS, such as Fig. 11BThose shown in (e.g., CSI-RS1101, 1102, 1103) can be transmitted by a base station and used by a UE for one or more measurement values. For example, the UE can measure the reference signal received power (RSRP) of the configured CSI-RS resource. The base station can configure the UE with a reporting configuration, and the UE can report the RSRP measurement value to the network (e.g., via one or more base stations) based on the reporting configuration. In the 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 the 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 the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, 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-corresponding capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate the uplink beam of the UE based on measurements of one or more SRS resources transmitted by the UE.

[0177] In the beam management procedure, the UE may assess (e.g., measure) the channel quality of one or more beam pair links, beam pair links including a transmit beam transmitted by a base station, and a receive beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, the one or more beam pair quality parameters including, 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).

[0178] Fig. 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurements of transmit (Tx) beams of a transmit reception point (TRP) (or multiple TRPs), for example to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals 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 ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of Tx beams of a TRP (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or the base station may perform procedure P2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0179] Fig. 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements on a UE's Tx beams, for example, to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals 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 ovals rotating in a clockwise direction indicated by dashed arrows 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 ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 can be used to enable a base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0180] 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., 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 above an error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0181] The UE may measure the quality of a beam-to-link using one or more reference signals (RS), 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 (DMRS). The quality of a beam-to-link may be based on one or more of the following: a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value and / or a CSI value measured on an RS resource. The base station may indicate that the RS resource is quasi-co-located (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, etc.). When the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from the transmission to the UE via the RS resource are similar or identical to the channel characteristics from the transmission to the UE via the channel, the RS resource and the one or more DMRS of the channel may be QCLed.

[0182] The network (e.g., gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in RRC_IDLE state and / or RRC_INACTIVE state may initiate a random access procedure to request a connection setup to the network. The UE may initiate a random access procedure from the RRC_CONNECTED state. The UE may initiate a random access procedure to request uplink resources (e.g., uplink transmission for SR when there are no available PUCCH resources) and / or to 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.

[0183] Fig.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. Fig.13AThe procedure 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).

[0184] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of 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.

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

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

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

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

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

[0190] 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 or in response to the transmission of Msg 1 1311. 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 is received by the base station. Msg 2 1312 may include a time alignment command that may 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 opportunity used by the UE to transmit 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 opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events that initiate a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. Examples of RA-RNTIs may be as follows:

[0191] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0192] Wherein s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≤s_id<14), t_id may be the index of the first time slot of the PRACH opportunity in the system frame (e.g., 0≤t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier and 1 for a SUL carrier).

[0193] The UE may transmit Msg3 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 example, Fig.13A Contention resolution in a contention-based random access procedure as shown in . In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UE. If the multiple UEs interpret 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 mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., if a C-RNTI is assigned, the TC-RNTI included in Msg2 1312 and / or any other suitable identifier).

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

[0195] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., a random access procedure) may be supported in an uplink carrier. For example, a base station may configure two separate RACH configurations for a UE: one for a SUL carrier and the other for a NUL carrier. For random access in a cell configured with a SUL carrier, the network may 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 may determine the SUL carrier. The uplink transmission (e.g., Msg 1 1311 and / or Msg 3 1313) of the random access procedure may remain on the selected carrier. In one or more cases, the UE may switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE may determine and / or switch an uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (eg, listen before talk).

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

[0197] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Fig. 13B For example, the base station may indicate or assign a preamble to be used for Msg 1 1321 to the UE. The UE may receive an indication of the preamble (eg, ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0198] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for 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 the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. Fig. 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 a RAR including a preamble identifier corresponding to a 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 a confirmation of the SI request.

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

[0200] 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. Transport block 1342 may include Fig.13A The transmission 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 the same content as the content of Msg 3 1313 shown in FIG. Fig.13A and Fig. 13B Msg 2 1312 (eg, RAR) and / or Fig.13A The content of Msg4 1314 shown is similar and / or identical.

[0201] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Fig. 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.

[0202] 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 the 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.

[0203] 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).

[0204] 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.

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

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

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

[0208] 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 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling of PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a UE group. DCI format 2_1 may be used to notify a UE group of physical resource blocks and / or OFDM symbols, where the UE may assume that no transmission to the UE is expected. DCI format 2_2 may be used to transmit a transmission power control (TPC) command for PUCCH or PUSCH. DCI formats 2_3 may be used to transmit a set of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

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

[0211] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown. The CCE to REG mapping can be an interlaced mapping (e.g., for the purpose of providing frequency diversity) or a non-interlaced mapping (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). The base station can perform different or the same CCE to REG mapping for different CORESETs. A CORESET can be associated with the CCE to REG mapping through RRC configuration. A 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) for PDCCH reception in the CORESET.

[0212] The base station may transmit an RRC message including configuration parameters of one or more CORESETs and one or more search space sets to the UE. The configuration parameters may indicate an association between a search space set and a 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 for each aggregation level; the PDCCH monitoring period and the PDCCH monitoring type; 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 UE's identity (e.g., C-RNTI).

[0213] like Fig. 14B As 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 of the CORESET based on the configuration parameters of the CORESET (e.g., interlaced or non-interlaced and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET based on the RRC message (e.g., up to 10). The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have 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. 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., scrambled bits of the CRC parity bits of the DCI matching the RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, time slot format indications, downlink preemption, etc.).

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

[0215] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. If the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE may use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may 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 may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. If the transmission exceeds one or two symbols and the number of UCI bits is two or more, the UE may use PUCCH format 2. PUCCH format 3 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not include orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources include orthogonal cover codes, the UE may use PUCCH format 4.

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

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

[0218] Fig.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 may be part of a mobile communication network, such as Figure 1A The mobile communication network 100 shown, Figure 1B The mobile communication network 150 shown or any other communication network. Fig.15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , 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 Fig.15 Configurations the same or similar to those shown.

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

[0220] In the downlink, data to be sent from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 via, for example, a core network. In the uplink, data to be sent from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement layer 3 and layer 2 OSI functions to process data for transmission. Layer 2 may include, for example, information about Figure 2A , Figure 2B , Figure 3 and Figure 4A Layer 3 may include the following: Figure 2B RRC layer.

[0221] After processing by processing system 1508, data to be transmitted to wireless device 1502 may be provided to transmission processing system 1510 of base station 1504. Similarly, after processing by processing system 1518, data to be transmitted to base station 1504 may be provided to transmission processing system 1520 of wireless device 1502. Transmission processing system 1510 and transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4A For transmission processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

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

[0223] like Fig.15 As shown, the wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may 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, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0224] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or codes that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Fig.15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that may be executed to perform one or more of their respective functions.

[0225] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or 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 device, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

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

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

[0228] Fig. 16B An example structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0229] Fig. 16C An example structure for downlink transmission is shown. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0230] Fig.16D Another example structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex valued OFDM baseband signal at an antenna port. Filtering may be employed prior to transmission.

[0231] The wireless device may receive one or more messages (e.g., RRC messages) including configuration parameters of multiple cells (e.g., primary cells, secondary cells) from a base station. The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the wireless device at 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, and the like. 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.

[0232] Once started, a timer can start running and continue running until it stops or until it expires. If the timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or can start from zero and expire once it reaches the value). The duration of the timer may not be updated until the timer stops or expires (e.g., due to BWP switching). A timer can be used for a time period / window of a measurement process. When the specification refers to an embodiment and a program 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 of implementing the timer can be used to measure the time period / window of the program. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In an example, instead of starting and expiring a random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the measurement process of the time window can be restarted. Other exemplary embodiments can be provided to restart the measurement of the time window.

[0233] The base station may transmit one or more MAC PDUs to the wireless device. In an example, the MAC PDU may be a bit string that is length byte aligned (e.g., aligned to a multiple of eight bits). In an example, the bit string may be represented by a table, wherein 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 order in which the lines are read. In an example, the bit order of the parameter fields within the MAC PDU is represented by the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

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

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

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

[0237] Fig.17A An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Fig.17A In an exemplary MAC subheader of , the LCID field may be six bits in length and the L field may be eight bits in length. Fig. 17B An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Fig. 17B In the exemplary MAC subheader shown in , the length of the LCID field may be six bits, and the length of the L field may be sixteen bits. When the MAC subheader corresponds to a fixed-size MAC CE or padding, the MAC subheader may include: an R field having a length of two bits and an LCID field having a length of multiple bits. Fig. 17C An example of a MAC subheader having an R field and an LCID field is shown. Fig. 17C In the exemplary MAC subheader shown in , the LCID field may be six bits in length and the R field may be two bits in length.

[0238] Fig.18AAn example of a DL MAC PDU is shown. Multiple MAC CEs (such as MAC CE 1 and 2) may be placed together. A MAC subPDU including a MAC CE may be placed before a MAC subPDU including a MAC SDU or a MAC subPDU including padding. Fig.18B An example of a UL MAC PDU is shown. Multiple MAC CEs (such as MAC CE 1 and 2) may be placed together. In an embodiment, a MAC subPDU including a MAC CE may be placed after all MAC subPDUs including a MAC SDU. Additionally, a MAC subPDU may be placed before a MAC subPDU including padding.

[0239] In an example, a MAC entity of a base station may transmit one or more MAC CEs to a MAC entity of a wireless device. Fig.19 An example of multiple LCIDs that may be associated with one or more MAC CEs is shown. The one or more MAC CEs may 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 status indication of UE-specific PDCCH MAC CE; TCI status indication of UE-specific PDSCH MAC CE; aperiodic CSI triggering status subselection MAC CE; SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE; UE contention resolution identity MAC CE; timing advance command MAC CE; DRX command MAC CE; long DRX command MAC CE; SCell activation / deactivation MAC CE (1 octet); SCell activation / deactivation MAC CE (4 octets); and / or duplicate activation / deactivation MAC CE. In an 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, may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in a MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

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

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

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

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

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

[0245] When the wireless device receives an SCell activation / deactivation MAC CE to deactivate the activated SCell, the wireless device may deactivate the activated SCell. In an example, when the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell 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 an 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 the configured uplink grant type 2 associated with the activated SCell. In an example, in response to deactivating the activated SCell, the wireless device may: suspend one or more configured uplink grants of the configured uplink grant type 1 associated with the activated SCell; and / or clear the HARQ buffer associated with the activated SCell.

[0246] When the SCell is deactivated, the wireless device may not perform operations including: 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 (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when at least one second PDCCH on a serving cell (e.g., a PCell or SCell configured with a PUCCH, i.e., a PUCCH SCell) that schedules the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an 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.

[0247] Fig.21A An example of an octet SCell activation / deactivation MAC CE is shown. Fig.19 The first MAC PDU subheader of the SCell activation / deactivation MAC CE (shown as '111010' in FIG. 1 ) may identify an octet SCell activation / deactivation MAC CE. The octet SCell activation / deactivation MAC CE may have a fixed size. The 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).

[0248] Fig. 21B An example of a four-octet SCell activation / deactivation MAC CE is shown. Fig.19The second MAC PDU subheader of the MAC PDU (e.g., '111001' shown in ) may identify a four-octet SCell activation / deactivation MAC CE. The four-octet SCell activation / deactivation MAC CE may have a fixed size. The 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).

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

[0250] Fig.22A An exemplary implementation of RRC configuration of parameters for power saving operation and / or DRX operation is shown. In the example, the base station may transmit one or more RRC messages to the wireless device, and the one or more RRC messages include configuration parameters for DRX operation. Based on the configuration parameters for DRX operation, the MAC entity of the wireless device may control the PDCCH monitoring activities of the C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and AI-RNTI of the MAC entity. When in RRC_CONNECTED, if DRX is configured, the MAC entity may use DRX operation to discontinuously monitor the PDCCH for all activated service cells. Otherwise, the MAC entity may monitor the PDCCH continuously.

[0251] In an example, the configuration parameters for the DRX operation may include: drx-onDurationTimer indicating the duration when the DRX cycle starts, drx-SlotOffset indicating the delay before starting the drx-onDurationTimer, drx-InactivityTimer indicating the duration after a PDCCH opportunity in which the PDCCH indicates a new UL or DL ​​transmission of the MAC entity, drx-RetransmissionTimerDL indicating the maximum duration until a DL retransmission is received (as per a DL HARQ process other than a broadcast process), drx-RetransmissionTimerUL indicating the maximum duration until a grant for a UL retransmission is received (as per a UL HARQ process other than a broadcast process), HARQ process), drx-LongCycleStartOffset indicating the long DRX cycle, and drx-StartOffset defining the subframes at which the long and short DRX cycles start, drx-ShortCycle of the short DRX cycle, drx-ShortCycleTimer indicating the duration that the wireless device can follow the short DRX cycle, drx-HARQ-RTT-TimerDL indicating the minimum duration before the MAC entity expects a DL assignment of HARQ retransmission (as per DL HARQ process other than the broadcast process), drx-HARQ-RTT-TimerUL indicating the minimum duration before the MAC entity expects a UL HARQ retransmission grant (as per UL HARQ process).

[0252] In an example, configuration parameters for power saving operations (e.g., associated with DRX operations) may include: ps-Wakeup indicating whether to start an associated drx-onDurationTimer if the wireless device monitors but does not detect a DCI with a CRC scrambled by a PS-RNTI (DCP), ps-TransmitOtherPeriodicCSI indicating whether to report periodic CSI that is not L1-RSRP on the PUCCH during the duration indicated by the drx-onDurationTimer if the DCP is configured but the associated drx-onDurationTimer is not started, and ps-TransmitPeriodicL1-RSRP indicating whether to transmit periodic CSI (i.e., L1-RSRP) on the PUCCH during the duration indicated by the drx-onDurationTimer if the DCP is configured but the associated drx-onDurationTimer is not started.

[0253] In an example, the configuration parameters for power saving operation may include: indicating a ps-RNTI for DCI format 2_6 (eg, based on Fig.24 The configuration parameters may include a ps-RNTI indicating the number of search space sets for monitoring PDCCH on the active DL BWP of the PCell or SpCell according to the common search space to detect DCI format 2_6, and a size-DCI-2-6 indicating the payload size of the DCI format 2_6. The configuration parameters may include a ps-PositionDCI-2-6 indicating the position of the wake-up indication bit in the DCI format 2_6, wherein when reporting to a higher layer, a wake-up indication bit set to 0 indicates that the drx-onDurationTimer of the next long DRX cycle is not started, or when reporting to a higher layer, a wake-up indication bit set to 1 indicates that the drx-onDurationTimer of the next long DRX cycle is started.

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

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

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

[0257] In an example, when a DRX cycle is configured, the wireless device can determine that the active time of the service cells in the DRX group includes the following times: the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running, or the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running in any service cell in the DRX group, or the ra-ContentionResolutionTimer (or msgB-ResponseWindow) is running, or the SR is sent on the PUCCH and is pending; a PDCCH indicating a new transmission of the C-RNTI addressed to the MAC entity has not been received after successfully receiving a RAR of a random access preamble that is not selected by the MAC entity in a contention-based random access preamble.

[0258] In an example, when DRX operation is configured, if a MAC PDU is received in a configured downlink assignment, the MAC entity of the wireless device may start a drx-HARQ-RTT-TimerDL of the corresponding HARQ process and / or stop a drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.

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

[0260] In an example, when DRX operation is configured, if the drx-HARQ-RTT-TimerDL expires and if the data of the corresponding HARQ process is not successfully decoded, the MAC entity of the wireless device can start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the expiration of the drx-HARQ-RTT-TimerDL.

[0261] In an example, when DRX operation is configured, if the drx-HARQ-RTT-TimerUL expires, the MAC entity of the wireless device may start the drx-RetransmissionTimerUL of the corresponding HARQ process in the first symbol after the expiration of the drx-HARQ-RTT-TimerUL.

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

[0263] In an example, when DRX operation is configured, if the drx-InactivityTimer of a DRX group expires, if a short DRX cycle is configured, the MAC entity of the wireless device may start or restart the drx-ShortCycleTimer of the DRX group and / or use the short DRX cycle of the DRX group in the first symbol after the expiration of the drx-InactivityTimer. If the drx-InactivityTimer of the DRX group expires, if a short DRX cycle is not configured, the MAC entity of the wireless device may use the long DRX cycle of the DRX group.

[0264] In an example, when DRX operation is configured, if a DRX command MAC CE is received, if a short DRX cycle is configured, the MAC entity of the wireless device can start or restart the drx-ShortCycleTimer of each DRX group and / or use the short DRX cycle of each DRX group in the first symbol after the end of reception of the DRX command MAC CE. If a DRX command MAC CE is received, if the short DRX cycle is not configured, the MAC entity of the wireless device can use the long DRX cycle of the DRX group.

[0265] In an example, when DRX operation is configured, if the drx-ShortCycleTimer of a DRX group expires, the MAC entity of the wireless device may use a long DRX cycle for the DRX group. If a long DRX command MAC CE is received, the MAC entity of the wireless device may stop the drx-ShortCycleTimer for each DRX group and / or use a long DRX cycle for each DRX group.

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

[0267] Fig. 22B An exemplary implementation of power saving operation based on DCP reception is shown. In the example, when the wireless device receives a DCP including a wake-up indication set to a first value, the wireless device may start a drx-onDurationTimer associated with DRX operation and / or monitor the PDCCH while the drx-onDurationTimer is running. When the drx-onDurationTimer expires (or DRX switches to the DRX off duration), the wireless device may stop monitoring the PDCCH. In the example, when the wireless device receives a DCP including a wake-up indication set to a second value, the wireless device may not start the drx-onDurationTimer associated with DRX operation and / or skip monitoring the PDCCH during the DRX on duration.

[0268] In an exemplary embodiment, when DRX operation is configured, if a long DRX cycle is used for a DRX group, and [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset, and if DCP monitoring is configured for an active DL BWP, the MAC entity of the wireless device may start a drx-onDurationTimer after drx-SlotOffset from the start of the subframe, if an indication of a DCP associated with the current DRX cycle received from a lower layer indicates the start of the drx-onDurationTimer, or if all DCP opportunities associated with the current DRX cycle in the time domain occur in active time, taking into account grants / assignments / DRX Commands MAC CE / long DRX Commands MAC CE. A CE is received and a scheduling request is sent until 4 ms before the start of the last DCP opportunity, or during a measurement gap, or when the MAC entity monitors PDCCH transmissions on the search space indicated by recoverySearchSpaceId of the SpCell identified by C-RNTI while ra-ResponseWindow is running, or if ps-Wakeup is configured with the value true and a DCP indication associated with the current DRX cycle has not been received from lower layers.

[0269] In an example, when DRX operation is configured, if a long DRX cycle is used for a DRX group, and [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset, and if DCP monitoring is not configured for an active DLBWP configuration, the MAC entity of the wireless device may start the drx-onDurationTimer for the DRX group after drx-SlotOffset from the start of the subframe.

[0270] In an example, when DRX operation is configured, if the DRX group is in active time, the MAC entity of the wireless device may monitor the PDCCH on the serving cell in the DRX group. If the PDCCH indicates DL transmission, the MAC entity of the wireless device may start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process and / or stop the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends. If the PDSCH-to-HARQ_feedback timing indicates a non-numeric k1 value, the MAC entity may start the drx-RetransmissionTimerDL in the first symbol after the PDSCH transmission of the corresponding HARQ process. When the HARQ feedback is delayed by the PDSCH-to-HARQ_feedback timing indicating a non-numeric k1 value, the corresponding transmission timing for sending DL HARQ feedback is indicated in a later PDCCH requesting HARQ-ACK feedback.

[0271] In an example, when DRX operation is configured, if the DRX group is in active time, the MAC entity of the wireless device can monitor the PDCCH on the serving cell in the DRX group. If the PDCCH indicates UL transmission, the MAC entity can start the drx-HARQ-RTT-TimerUL of the corresponding HARQ process and / or stop the drx-RetransmissionTimerUL of the corresponding HARQ process in the first symbol after the first transmission (within the bundle) of the corresponding PUSCH transmission ends.

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

[0273] In an example, when DRX operation is configured, if DCP monitoring is configured for active DL BWP, and if the current symbol n occurs within the drx-onDurationTimer duration, and if the drx-onDurationTimer associated with the current DRX cycle is not started, if when evaluating all DRX active time conditions, the grant / assignment / DRX Command MAC CE / Long DRX Command MAC CE received before 4ms before symbol n and the SR sent are taken into account, the MAC entity shall not be in active time: the MAC entity shall not transmit periodic SRS and semi-persistent SRS, shall not report semi-persistent CSI configured on PUSCH, shall not report periodic CSI that is L1-RSRP on PUCCH if ps-TransmitPeriodicL1-RSRP is not configured with the value true, and shall not report periodic CSI that is not L1-RSRP on PUCCH if ps-TransmitOtherPeriodicCSI is not configured with the value true.

[0274] In an example, when DRX operation is configured, if DCP monitoring is configured for active DL BWP configuration, and / or if the current symbol n does not occur within the drx-onDurationTimer duration, and / or if the drx-onDurationTimer associated with the current DRX cycle is started, in the current symbol n, if the grant / assignment scheduled on the serving cell in the DRX group and the DRX Command MAC CE / Long DRX Command MAC received before 4 ms before symbol n are taken into account when evaluating all DRX active time conditions. CE and the segment request sent, the DRX group will not be in active time: the MAC entity should not transmit periodic SRS and semi-persistent SRS in this DRX group, the CSI on PUCCH and the semi-persistent CSI configured on PUSCH are not reported in this DRX group, if the CSI mask (csi-Mask) is set by the upper layer and in the current symbol n, the CSI on PUCCH is not reported in this DRX group, if when evaluating all DRX active time conditions, the grant / assignment scheduled on the serving cell in the DRX group and the DRX command MAC CE / long DRX command MAC CE received before 4ms before symbol n are taken into account, the drx-onDurationTimer of this DRX group will not run.

[0275] In the example, regardless of whether the MAC entity monitors PDCCH on serving cells in the DRX group, when so desired, the MAC entity can transmit HARQ feedback, non-periodic CSI on PUSCH, and non-periodic SRS on serving cells in the DRX group. If it is not a full PDCCH opportunity (e.g., the active time starts or ends in the middle of the PDCCH opportunity), the MAC entity does not need to monitor the PDCCH.

[0276] In some embodiments, the base station may configure the wireless device 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 the wireless device with at least a DL BWP (i.e., there may be no UL BWP in the 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 that is configured for the wireless device to operate on the SCell when the SCell is activated. In a paired spectrum (e.g., FDD), the base station and / or the wireless device may switch the DL BWP and the UL BWP independently. In an unpaired spectrum (e.g., TDD), the base station and / or the wireless device may switch the DL BWP and the UL BWP simultaneously.

[0277] In an example, the base station and / or the wireless device may switch the BWP between configured BWPs using DCI or a BWP inactivity timer. When the BWP inactivity timer is configured for a serving cell, the base station and / or the wireless device may switch the active BWP to a 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 an example, for an FDD system, when configured with a BA, one UL BWP and one DL BWP for each uplink carrier may be active at a certain time in an active serving cell. In an example, for a TDD system, one DL / UL BWP pair may be active at a certain time in an active serving cell. Operating on the one UL BWP and the one DL BWP (or the one DL / UL pair) may improve wireless device battery consumption. BWPs other than the one active UL BWP and the one active DL BWP on which the wireless device may operate may be deactivated. On a deactivated BWP, the wireless device may: not monitor the PDCCH; and / or not transmit on the PUCCH, PRACH, and UL-SCH.

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

[0279] Fig.23 An example of BWP switching on a cell (e.g., a PCell or SCell) according to some embodiments is shown. In the example, a wireless device may receive at least one RRC message from a base station, the at least one RRC message including parameters of the cell and one or more BWPs associated with the cell. The RRC message may include: an RRC connection reconfiguration message (e.g., RRCReconfiguration); an RRC connection 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 may be configured as a first active BWP (e.g., BWP 1) and one BWP may be configured as a default BWP (e.g., BWP 0). The wireless device may receive a command to activate the cell (e.g., an RRC message, a MAC CE, or a DCI) in the nth time slot. In the case where the cell is a PCell, the wireless device may not receive a command to activate the cell, for example, once the wireless device receives an RRC message including configuration parameters of the PCell, the wireless device may activate the PCell. The wireless device may start monitoring the PDCCH on BWP 1 in response to activating the cell.

[0280] In an example, in response to receiving a DCI indicating a DL assignment on BWP 1, the wireless device may 个The wireless device may start (or restart) a BWP inactivity timer (e.g., bwp-InactivityTimer) in the sth time slot. When the BWP inactivity timer expires, the wireless device may switch back to the default BWP (e.g., BWP 0) as the active BWP in the sth time slot. When the sCellDeactivationTimer expires (e.g., if the cell is an SCell), the wireless device may deactivate the cell and / or stop the BWP inactivity timer. In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer to the PCell.

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

[0282] In an example, on an inactive BWP for each activated service cell configured with a BWP, the MAC entity may: not transmit on UL-SCH; not transmit on RACH; not monitor PDCCH; not transmit PUCCH; not transmit SRS, not receive 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.

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

[0284] In an example, for the primary cell, a default DL BWP among the configured DL BWPs may be provided to the wireless device via a higher layer parameter Default-DL-BWP. If a default DL BWP is not provided to the wireless device via the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In an example, a timer value for the primary cell may be provided to the wireless device via a higher layer parameter bwp-InactivityTimer. If configured, the wireless device may increment the timer (if running) at intervals of every 1 millisecond for frequency range 1 or every 0.5 millisecond for frequency range 2, if during the interval, 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.

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

[0286] In an example, if the wireless device is configured with a first active DL BWP on a secondary cell or carrier via a higher layer parameter Active-BWP-DL-SCell and a first active UL BWP via a 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 ULBWP on the secondary cell or carrier.

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

[0288] In an example, the wireless device determines the PDCCH monitoring occasion on the active DL BWP based on one or more PDCCH configuration parameters, including: PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring pattern within a time slot. For a search space set (SS s), if Then the wireless device determines that the PDCCH monitoring opportunities exist in the number n f The number of frames is in the time slot. is the number of time slots in a frame when the parameter set μ is configured. o s k is the slot offset indicated in the PDCCH configuration parameter. s The PDCCH monitoring period is indicated in the PDCCH configuration parameter. Start monitoring PDCCH candidates for the search space set for T s consecutive time slots, and in the next k s -T s No PDCCH candidates are monitored for the search space set s during consecutive time slots. In an example, the USSs at the CCE aggregation level L∈{1,2,4,8,16} are defined by the set of PDCCH candidates for the CCE aggregation level L.

[0289] In an example, the wireless device decides, for a search space set s associated with CORESETp, that for a carrier indicator field value n CI For the active DL BWP of the corresponding serving cell, in the time slot In the search space set, the PDCCH candidates The corresponding CCE index of aggregation level L is For any CSS For USS Y p,>1 =n RNTI ≠0, for p mod3 = 0A p =39827, for p mod3 = 1A p =39829, for p mod3 = 2A p =39839, and D = 65537; i = 0, ..., L-1; in CORESETp, N CCE,p is the number of CCEs, numbered from 0 to N CCE,p -1; if the wireless device is configured with a carrier indicator field CrossCarrierSchedulingConfig for the serving cell on which to monitor the PDCCH, then n CIis the Carrier Indicator field value; otherwise, including for any CSS, n CI =0; in The wireless device is configured to communicate with n CI The number of PDCCH candidates monitored for the aggregation level L of the search space set s for the corresponding serving cell; for any CSS, For USS, is the number of n over all configurations of CCE aggregation level L for search space set s CI value The maximum value of RNTI The RNTI value is C-RNTI.

[0290] In an example, a wireless device may monitor a set of PDCCH candidates based on configuration parameters of a search space set including multiple search spaces (SSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates based on the monitored DCI format. Monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. Possible DCI formats may be based on Fig.24 An exemplary embodiment of .

[0291] Fig.24 An example of a DCI format is shown, which can be used by a base station to transmit control information to a wireless device, or by a wireless device for PDCCH monitoring. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In the example, DCI format 0_0 can be used to schedule PUSCH in a cell. DCI format 0_1 ​​can be used to schedule one or more PUSCHs in a cell, or to indicate CG-DFI (configured grant-Downlink feedback information) of a configured granted PUSCH, etc. The DCI format that a wireless device can monitor in an SS can be based on information about Fig. 27 The exemplary embodiment is configured as will be explained later.

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

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

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

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

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

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

[0298] Fig.26 An example of RRC configuration parameters (e.g., BWP-DownlinkDedicated IE) for a downlink BWP of a serving cell according to some embodiments is shown. The base station may transmit one or more configuration parameters of a downlink BWP (e.g., an initial downlink BWP) of a serving cell to a wireless device (or multiple wireless devices). Fig.26 As shown, one or more configuration parameters of the downlink BWP may include: one or more parameters of the PDCCH of the downlink BWP (e.g., in the pdcch-Config IE), and one or more other parameters. The pdcch-Config IE may include parameters of one or more control resource sets (CORESETs), which may be used for bandwidth parts in any common or UE-specific search space. The one or more parameters of the PDCCH may indicate multiple search spaces of the bandwidth part, each search space being associated with a search space ID. The one or more parameters of the PDCCH may include a search space switching configuration parameter (e.g., searchSpaceSwitchConfig-r16IE) indicating one or more cell groups for search space switching. When a bit of the search space switching indication bitmap of the DCI (e.g., DCI format 2_0) indicates a first value, the wireless device may switch to the first search space group for all cells in the cell group corresponding to the bit. When a bit of the search space switching indication bitmap of the DCI (e.g., DCI format 2_0) indicates a second value, the wireless device may switch to the second search space group for all cells in the cell group corresponding to the bit.

[0299] like Fig.26As shown, a CORESET can be associated with a CORESET index (e.g., ControlResourceSetId). A CORESET index with a value of 0 can identify a common CORESET configured in the MIB and in ServingCellConfigCommon (controlResourceSetZero) and cannot be used in the ControlResourceSet IE. CORESET indexes with other values ​​can identify a CORESET configured by dedicated signaling or in SIB1. controlResourceSetId is unique among the BWPs of the serving cell. A CORESET can be associated with a coresetPoolIndex indicating an index of a CORESET pool of the CORESET. A CORESET can be associated with a duration parameter (e.g., duration) that indicates the continuous duration of the CORESET in a number of symbols. In the example, Fig.26 As shown, the configuration parameters of the CORESET may include at least one of the following: a frequency resource indication (e.g., frequencyDomainResources), a CCE-REG mapping type indicator (e.g., cce-REG-MappingType), multiple TCI states, an indicator indicating whether TCI is present in the DCI, etc. The frequency resource indication comprising several bits (e.g., 45 bits) indicates frequency domain resources, 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 the cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit corresponds to the first RB group in the BWP, and so on. A bit set to 1 indicates that the RB group corresponding to the bit belongs to the frequency domain resources of the CORESET. The bits corresponding to a group of RBs that are not fully contained in the BWP in which the CORESET is configured are set to zero.

[0300] In an example, the base station may transmit one or more RRC messages to the wireless device, the RRC messages including PDCCH configuration parameters applicable to all downlink BWPs of the cell (e.g., Fig.26 In an example, the PDCCH configuration parameter may include a timer value (e.g., in symbols / slots or integers in ms) for a search space switch timer (e.g., searchSpaceSwitchTimer IE). The search space switch timer and time value may be used to set the search space switch timer to the same as the PDCCH-ServingCellConfig IE. Fig.28B The search space switching operation described in .

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

[0302] like Fig. 27 As shown, one or more search space configuration parameters of a search space may include a search space group list (e.g., searchSpaceGroupIdList) that indicates one or more search space groups to which the search space may belong for a search space switching operation. The search space switching operation may be based on Fig.28A and / or Fig.28B An exemplary embodiment of .

[0303] Fig.28A An example of a DCI format 2_0 including one or more search space cluster group (or SSSG) switching indications (or search space cluster group switching flags) according to some embodiments is shown. In the example, DCI format 2_0 may include one or more time slot format indicators (e.g., time slot format indicator 1, time slot format indicator 2, ... time slot format indicator N), one or more available RB set indicators, one or more COT duration indications, and one or more SSS group switching flags. In the example, each of the one or more SSS group switching flags may correspond to a corresponding cell group in a plurality of cell groups. The plurality of cell groups may be based on the above description of Fig.26The exemplary embodiment described is implemented. Each of the multiple cell groups may include one or more cells. When set to a first value, an SSS group switching flag in one or more SSS group switching flags corresponding to a cell group may indicate that each cell in the cell group is switched from a first SSS group to a second SSS group. When set to a second value, the SSS group switching flag may indicate that each cell in the cell group is switched from a second SSS group to a first SSS group. In the example, the multiple SSS groups including the first SSS group and the second SSS group may be based on the above description of Fig. 27 The wireless device may be configured based on the exemplary embodiment described. Fig.28B An exemplary embodiment of the present invention is used to perform SSS group switching.

[0304] Fig.28B shows a DCI format (e.g., DCI format 2_0 or Fig.24 In the example, the searchSpaceGroupIdList (e.g., based on the searchSpaceGroupIdList) can be used to switch the SSS group. Fig. 27 An exemplary embodiment of the present invention provides a group index of a search space set (e.g., a Type3-PDCCH CSS set, a USS set, or any other type of search space set) to a wireless device for PDCCH monitoring on a serving cell.

[0305] In an example, the searchSpaceGroupIdList of the search space set may not be provided to the wireless device. If the search space set is not configured with a searchSpaceGroupIdList, then Fig.28B The implementation scheme may not be applicable to PDCCH monitoring of the search space. Fig.28B In an embodiment, the wireless device may monitor the search space set on the BWP without switching out of the search space set monitored by the PDCCH.

[0306] In an example, if a cellGroupsForSwitchList indicating one or more serving cell groups is provided to a wireless device (e.g., based on Fig.26 ), then Fig.28B The implementation of can be applied to all serving cells in each group. If the wireless device is not provided with cellGroupsForSwitchList, then Fig.28B The implementation scheme may only be applied to serving cells for which the wireless device is provided with searchSpaceGroupIdList.

[0307] In an example, if the wireless device is provided with searchSpaceGroupIdList, the wireless device may reset PDCCH monitoring according to the search space set with group index 0 if provided by searchSpaceGroupIdList.

[0308] In the example, the SpaceSwitchDelay can be searched (e.g., Fig.26 ) provides a plurality of symbols P to the wireless device based on the UE processing capability (e.g., UE processing capability 1, UE processing capability 2, etc.) and the SCS configuration μ sMNOPQ . The SCS configured UE processing capability 1μ may apply unless the wireless device indicates support for UE processing capability 2. In the example, for UE capability 1 and μ=0, P sMNOPQ =25; for UE capability 1 and μ=1, P sMNOPQ =25; for UE capability 1 and μ=2, P sMNOPQ =25; for UE capability 2 and μ=0, P sMNOPQ =10; for UE capability 2 and μ=1, P sMNOPQ =12; and for UE capability 2 and μ=2, P sMNOPQ =22; and so on.

[0309] In an example, the searchSpaceSwitchTimer (e.g., Fig.26 The wireless device may provide a timer value in time slots for the serving cells for which the wireless device is provided with searchSpaceGroupIdList, or, if provided, for the set of serving cells provided by cellGroupsForSwitchList. The wireless device may decrement the timer value by one after each time slot based on a reference SCS configuration, which is the smallest SCS configuration μ among all configured DL BWPs in the serving cell or in the set of serving cells. The wireless device may maintain the reference SCS configuration during the timer decrement procedure.

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

[0311] like Fig.28B As shown, the wireless device may monitor the PDCCH on the first SSS group (e.g., the first SSS group or the SSS with group index 0) based on the configuration of the SSS group of the BWP of the cell. The location of the search space cluster group switch flag field of the serving cell may be provided to the wireless device by the SearchSpaceSwitchTrigger in DCI format 2_0. The SearchSpaceSwitchTrigger may be based on Fig. 27 The wireless device may receive a DCI (e.g., Fig.28B For example, when the value of the SSS group switching flag field in DCI format 2_0 is 1, the DCI may indicate an SSS group switching of the cell. In response to receiving the DCI, the wireless device may start monitoring the PDCCH according to the second SSS group (e.g., the second SSS group or the SSS with a group index of 1) and stop monitoring the PDCCH on the first SSS group (or the SSS with a group index of 0 for the serving cell). The wireless device may start monitoring the PDCCH on the second SSS group (e.g., the second SSS group or the SSS with a group index of 1) and stop monitoring the PDCCH on the first SSS group (or the SSS with a group index of 0 for the serving cell). The wireless device may start monitoring the PDCCH on the second SSS group (e.g., the second SSS group or the SSS with a group index of 1) and stop monitoring the PDCCH on the first SSS group (or the SSS with a group index of 0 for the serving cell) at least P after the last symbol of the PDCCH with DCI format 2_0. sMNOPQ The wireless device may stop monitoring the PDCCH on the first SSS group at the first time slot of a symbol. Based on receiving the DCI, the wireless device may set the timer value of the search space switch timer to the value provided by searchSpaceSwitchTimer.

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

[0313] In an example, if the wireless device monitors the PDCCH of the serving cell according to a first SSS group (e.g., a search space set with a group index of 1), the wireless device may start monitoring the PDCCH of the serving cell according to a second SSS group (e.g., a search space set with a group index of 0) and stop monitoring the PDCCH according to the first SSS group for the serving cell at the beginning of a first time slot that is at least P after the time slot at which the timer expires. sMNOPQ symbols, or after the last symbol of the remaining channel occupancy duration of the serving cell indicated by DCI format 2_0.

[0314] In an example, the wireless device may not be provided with a SearchSpaceSwitchTrigger for the serving cell, for example, the SearchSpaceSwitchTrigger is not present in the configuration parameters of the SlotFormatIndicator, where the SlotFormatIndicator is configured to monitor the group common PDCCH for a slot format indicator (SFI). In response to not providing the SearchSpaceSwitchTrigger, the DCI format 2_0 may not include an SSS group switch flag field. When the SearchSpaceSwitchTrigger is not provided, if the wireless device detects the DCI format by monitoring the PDCCH according to a first SSS group (e.g., a search space set with a group index of 0), the wireless device may start monitoring the PDCCH according to a second SSS group (e.g., a search space set with a group index of 1) and stop monitoring the PDCCH according to the first SSS group for the serving cell. The wireless device may monitor the PDCCH at least P after the last symbol of the PDCCH with the DCI format. sMNOPQ The wireless device may start monitoring the PDCCH according to the second SSS group at the first time slot of a symbol and stop monitoring the PDCCH according to the first SSS group. If the wireless device detects a DCI format by monitoring the PDCCH in any search space set, the wireless device may set (or restart) the timer value to the value provided by searchSpaceSwitchTimer.

[0315] In an example, the wireless device may not be provided with a SearchSpaceSwitchTrigger for the serving cell. When the SearchSpaceSwitchTrigger is not provided, if the wireless device monitors the PDCCH of the serving cell according to a first SSS group (e.g., a search space set with a group index of 1), the wireless device may start monitoring the PDCCH of the serving cell according to a second SSS group (e.g., a search space set with a group index of 0) and stop monitoring the PDCCH according to the first SSS group for the serving cell at the beginning of a first time slot that is at least P after the time slot where the timer expires. sMNOPQ symbols, or if the wireless device is provided with a search space set to monitor the PDCCH to detect DCI format 2_0, after the last symbol of the remaining channel occupancy duration of the serving cell indicated by DCI format 2_0.

[0316] In an example, the wireless device may determine the time slots and symbols in the time slots to start or stop PDCCH monitoring based on the search space set of the service cell for which searchSpaceGroupIdList is provided to the wireless device, or if cellGroupsForSwitchList is provided, determine the time slots and symbols in the time slots to start or stop PDCCH monitoring for the service cell set based on the minimum SCS configuration μ in all configured DL BWPs in the service cell or in the service cell set, and if any, in the service cell of the corresponding DCI format 2_0 that triggers the start or stop of PDCCH monitoring in which the wireless device receives PDCCH and detects the triggering of PDCCH monitoring based on the search space set.

[0317] In an example, a wireless device may perform a PDCCH skipping mechanism for power saving operation. Fig.29 An example of power saving operation based on PDCCH skipping according to some embodiments is shown.

[0318] In an example, the base station may transmit one or more RRC messages to the wireless device, the RRC message including configuration parameters of the PDCCH of the BWP of the cell (eg, based on the above description of Fig.26 and / or Fig. 27 Based on the configuration parameters of the PDCCH, the wireless device may monitor the PDCCH on the BWP. The BWP may be an active downlink BWP. The wireless device may monitor the PDCCH on the BWP based on the configuration parameters of the PDCCH. Fig.23 An exemplary embodiment is described to activate the BWP.

[0319] like Fig.29 As shown, the wireless device may receive a first DCI (e.g., a first DCI) indicating that a PDCCH is skipped within a time window. The time value of the time window may be indicated by the first DCI, or configured by one or more RRC messages. In response to receiving the first DCI, the wireless device may stop monitoring the PDCCH on the BWP. Stopping monitoring the PDCCH on the BWP may include stopping monitoring the PDCCH on one or more SSS groups configured on the BWP. The wireless device may maintain an active state of the BWP. The first DCI may not indicate an active BWP switch. In an example, during the time window (or when a timer associated with the time window is running), the base station may not transmit a PDCCH to the wireless device.

[0320] like Fig.29As shown, when the time window expires, the wireless device can resume PDCCH monitoring on the BWP. Based on resuming PDCCH monitoring, the wireless device can receive a second DCI (e.g., a second DCI) that schedules a TB via the PDSCH. The wireless device can receive a TB via the PDSCH scheduled by the second DCI. In the example, in response to the time window expiring, the base station can transmit the second DCI to the wireless device.

[0321] In an example, the power saving operation based on PDCCH skipping on the active BWP may provide a better performance than that based on BWP switching (e.g., Fig.23 )'s power saving operation better power saving gain. Power saving based on BWP switching may include active BWP switching, which may take several milliseconds and / or require wireless service to re-tune the RF chain and / or beam direction. Power saving based on PDCCH skipping may not include active BWP switching. Therefore, no RF chain and / or beam direction re-tuning is required. Power saving based on PDCCH skipping may include skipping PDCCH monitoring on an active BWP for a period of time, and the wireless device may maintain the active state of the BWP for the duration of skipping PDCCH monitoring.

[0322] In an example, the wireless system may be deployed at a high frequency (e.g., above 50 GHz). The base station may apply a short time slot length (e.g., 15.6 us for an SCS with 960 KHz, 31.2 us for an SCS with 480 KHz, etc.) to accommodate frequency selective channel conditions and phase noise compensation for high frequency deployments. A time slot with a 15 KHz SCS may be 1 ms, which may include 2 time slots with a 30 KHz SCS, 4 time slots with a 60 KHz SCS, 8 time slots with a 120 KHz SCS, 16 time slots with a 240 KHz SCS, 32 time slots with a 480 KHz SCS, or 64 time slots with a 960 KHz SCS, etc. The time slot structure with an SCS (e.g., associated with a parameter set) may be based on the above description of the SCS. Figure 7 The exemplary embodiments described are implemented.

[0323] In the prior art, a base station may transmit a DCI including a PDCCH skip indication field indicating the number of time slots for skipping PDCCH monitoring. The PDCCH skip indication field may include multiple bits. The code point of the PDCCH skip indication field may indicate the number of time slots. The number of time slots that a wireless device may skip monitoring for PDCCH may be within a wide range, especially in the case of high SCS. In an example, the number of durations (in time slots) indicating the PDCCH skip on a BWP may be (at most) X (e.g., X=64) for a BWP configured with a 15KHz SCS, 2*X for a BWP configured with a 30KHz SCS, ..., or 64*X for a BWP configured with a 960KHz SCS. When X=64, for a 960KHz SCS, the number may be at most 64*64=4096, which may require 12 bits to indicate the number. This may increase the bit size of the DCI to indicate the duration value of the PDCCH skip indication on a BWP that may be configured with a 960 KHz SCS. Different parameter sets or SCSs may require different number of bits for the PDCCH skip duration indication.

[0324] Similarly, the base station can configure multiple PDCCH skip durations through an RRC message and transmit a DCI indicating one of the multiple PDCCH skip durations. Based on the prior art, the base station can configure multiple PDCCH skip durations according to the BWP (a BWP configured with a parameter set including the configuration of the SCS and CP duration) (through an RRC message or DCI). When a 15KHz SCS is configured for the BWP, the multiple PDCCH skip durations in the RRC message may have (up to) X (e.g., X=64) values, which may require 6 bits for indication. When a 960KHz SCS is configured for the BWP, the multiple PDCCH skip durations in the RRC message may have (up to) 64*X (e.g., 4096) values, which may require 12 bits for indication. Different parameter sets or SCSs may require different numbers of bits for PDCCH skip duration indication.

[0325] Due to power saving requirements in high frequency deployments, the prior art may require different bit widths to indicate the duration (or number of time slots) of PDCCH skipping for different parameter sets or SCSs. Based on the prior art, for a higher parameter set or SCS, the base station may use a larger bit width than a lower parameter set or SCS to indicate the duration of PDCCH skipping. Therefore, the prior art may cause inefficiencies in wireless communications, such as more signaling bits, and result in increased power consumption of wireless devices.

[0326] An exemplary embodiment includes transmitting by a base station and / or receiving by a wireless device an RRC message indicating one or more duration values ​​for PDCCH monitoring on a BWP for skipping a cell. The one or more duration values ​​may be a first value (or from a first set of values) in response to the BWP being configured with a first SCS, or a second value (or from a second set of values) in response to the BWP being configured with a second SCS. Each value in the second set of values ​​is equal to the product of a corresponding value in the first set of values ​​and the same granularity value. In the example, if the first value (or the first value in the first set of values) for the first SCS (e.g., 120KHz) is set to X, the corresponding value of the second value (or the second value in the second set of values) for the second SCS (e.g., 480KHz) is equal to 4*X, where 4 is obtained by 480KHz / 120KHz. Similarly, if a first value (or a first value in a first set of values) for a first SCS (e.g., 120 KHz) is set to X, a corresponding value for a second value (or a second value in a second set of values) for a second SCS (e.g., 960 KHz) is equal to 8*X, where 8 is obtained by 960 KHz / 120 KHz. The wireless device may receive a DCI indicating a duration value from among a plurality of duration values ​​for skipping PDCCH monitoring on the BWP. Based on receiving the DCI, the wireless device may skip PDCCH monitoring on the BWP for the duration indicated by the duration value.

[0327] Based on the exemplary embodiment, the duration value for skipping PDCCH monitoring on a BWP with a higher SCS is equal to the product of the duration value for skipping PDCCH monitoring on a BWP with a lower SCS and a predefined granularity value. The predefined granularity value is the ratio of the higher SCS to the lower SCS. By implementing the exemplary embodiment, the base station can indicate multiple duration values ​​with the same number of bits for different parameter sets. The wireless device can receive indications of multiple duration values ​​with the same number of bits for different parameter sets. The exemplary embodiment can allow the base station to configure different granularity values ​​corresponding to different parameter sets for the duration indication of PDCCH skipping. The exemplary embodiment can reduce the signaling overhead of the PDCCH skip duration indication for different parameter sets (or SCS). The exemplary embodiment can reduce the power consumption of the wireless device receiving the PDCCH skip duration indication for different parameter sets (or SCS).

[0328] In an example, a wireless device may receive a PDCCH skip indication via a first cell, the PDCCH skip indication indicating skipping of PDCCH monitoring on a second cell, wherein the first cell and the second cell may have different parameter sets (or the active BWPs of the first cell and the second cell have different parameter sets). In response to the first cell and the second cell having different parameter sets and receiving the PDCCH skip indication on the first cell, by implementing the prior art, it may be difficult for the wireless device to determine how long the wireless device can skip PDCCH monitoring on the second cell. With respect to how long the wireless device can skip PDCCH monitoring on the second cell, the prior art may cause the base station to be misaligned with the wireless device. Therefore, reliance on the prior art may increase power consumption of the wireless device and / or increase data transmission latency of the base station. When the wireless device performs a power saving operation based on PDCCH skipping, it is necessary to reduce power consumption of the wireless device, reduce signaling overhead, and reduce signaling / data transmission latency.

[0329] In an exemplary embodiment, the wireless device may determine the number of time slots skipped for the PDCCH on the first BWP based on the number and granularity value included in the DCI indicating the PDCCH skipping. The wireless device may determine the time slot length (e.g., in milliseconds) skipped for the PDCCH on the first BWP based on a first parameter set associated with the first BWP. The wireless device may determine the time slot length skipped for the PDCCH on the first BWP based on a second parameter set associated with the second BWP. The second BWP may be on the first cell or on the second cell. The wireless device may receive the DCI via the second BWP. By implementing the exemplary embodiment, the base station may adapt the granularity of the time window size skipped by the PDCCH. The base station may reduce the signaling overhead for indicating the time window in the DCI, and / or maintain the same DCI size for transmitting the DCI in different frequency bands associated with different parameter sets. The exemplary embodiment may reduce the power consumption of the wireless device.

[0330] In an exemplary embodiment, the wireless device may determine the number of slots to skip for the PDCCH based on at least one of: a first number indicated by the DCI, a second number determined based on a parameter set of the BWP, a third number of multiple PDSCHs scheduled by a single DCI, a fourth number of minimum applicable scheduling offsets applicable to receiving the PDSCH, etc. The exemplary embodiment may reduce the signaling overhead for indicating the duration of the PDCCH skipping, and thus also reduce the power consumption of the wireless device.

[0331] Fig.30An exemplary embodiment of power saving operation with PDCCH skipping is shown. In an exemplary embodiment, the base station may transmit one or more RRC messages to the wireless device, the one or more RRC messages including configuration parameters of the cell. The cell may include multiple BWPs. The wireless device may, for example, Fig.23 The exemplary embodiment described above can be used to activate a BWP in a plurality of BWPs of a cell. The wireless device can monitor the PDCCH on the BWP based on one or more configuration parameters of the PDCCH on the BWP. The one or more configuration parameters of the PDCCH can be based on the above description of Fig.26 and / or Fig. 27 The exemplary embodiments described are implemented.

[0332] like Fig.30 As shown, the wireless device may receive a first DCI indicating a number (X) and a granularity value (Y) of PDCCH skips on the BWP. The number may be indicated from a plurality of duration values ​​configured by an RRC message (transmitted by the base station to the wireless device before receiving the first DCI). The wireless device may receive the first DCI during monitoring of the PDCCH on the BWP. Based on the above description of Fig.24 In the described exemplary embodiment, the first DCI may be one of the DCI formats. The first DCI may include a first DCI field indicating X and a second DCI field indicating Y.

[0333] like Fig.30 As shown, based on the number and granularity value received in the first DCI, the wireless device may determine the PDCCH skip duration. The wireless device may determine the PDCCH skip duration as a number of time slots, where the number may be equal to X*Y. The wireless device may skip (or stop) monitoring the PDCCH on the BWP during the number of time slots, for example, after receiving the first DCI. After receiving the first DCI, the wireless device may start a timer associated with the PDCCH skip duration. The wireless device may decrement the timer by a first value (e.g., 1) after each time slot.

[0334] In an exemplary embodiment, X may be an integer. Y may be a value greater than 0. Y having an integer greater than 1 may indicate that the granularity of X may be in units of multiple slots. A value of Y greater than 0 and less than 1 may indicate that the granularity of X may be in units of fractions of slots. A value of Y equal to 1 may indicate that the granularity of X may be in units of slots. In an example, a combination of [X, Y] = [4, 1] may indicate that the PDCCH skip duration has a length of 4*1 = 4 slots. A combination of [X, Y] = [2, 1 / 4] may indicate that the PDCCH skip duration has a length of 2*1 / 4 = 1 / 2 slots. A combination of [X, Y] = [8, 8] may indicate that the PDCCH skip duration has a length of 8*8 = 64 slots.

[0335] In an exemplary embodiment, the wireless device may determine a first DCI indicating a PDCCH skip based on at least one of one or more DCI fields and / or RNTIs of the DCI. The DCI may schedule a PDSCH transmission or schedule a PUSCH transmission. Based on one or more DCI fields being set to a predefined value, the wireless device may determine that the first DCI indicates a PDCCH skip on the BWP. The one or more DCI fields may include one of the following: a HARQ process ID, a TDRA field, a FDRA field, a PDSCH-to-HARQ feedback timing indicator, etc. Based on the RNTI associated with the first DCI being a dedicated RNTI associated with the PDCCH skip (e.g., different from a C-RNTI or other existing RNTI), the wireless device may determine the first DCI as a PDCCH skip indication (e.g., not scheduling PDSCH or PUSCH).

[0336] In an exemplary embodiment, the first field indicating X in the first DCI may be a new DCI field, or a reuse of the first existing DC field of the first DCI.

[0337] In an exemplary embodiment, the second field indicating Y in the first DCI may be a DCI field of the first DCI (eg, a new DCI field or an existing DCI field).

[0338] In an exemplary embodiment, the DCI field used to indicate Y may be a minimum applicable scheduling offset indicator of the first DCI (e.g., a first DCI having DCI format 1_1, DCI format 0_1, etc.). In response to the minimum applicable scheduling offset indicator indicating k (e.g., 1, 2, 3, etc.) as a minimum value K0 (or a minimum value K2), the wireless device may determine that Y=k.

[0339] In an exemplary embodiment, the DCI field used to indicate Y may be a multi-PDSCH scheduling indicator (multi-PUSCH scheduling indicator) in the first DCI. The multi-PDSCH scheduling indicator may be a TDRA field of the first DCI, wherein the TRDRA field indicates a time domain resource allocation parameter for the number of multiple PDSCHs scheduled by a single DCI. The multi-PDSCH scheduling indicator may be an NDI (or RV, etc.) field of the first DCI, wherein the NDI field indicates an NDI value for the number of multiple PDSCHs scheduled by a single DCI. The multi-PDSCH scheduling indicator may indicate the number of multiple PDSCHs scheduled by a single DCI, wherein the number of PDSCHs may be transmitted in multiple (continuous or discontinuous) time slots. In response to the multi-PDSCH scheduling indicator of the first DCI indicating m (e.g., 2, 4, 6, etc.) as the number of multiple PDSCHs scheduled by a single DCI, the wireless device may determine that Y=m.

[0340] In an exemplary embodiment, the wireless device may determine the slot length based on the SCS configuration associated with the BWP of the cell, for example, 15KHz SCS is 1ms, 30KHz SCS is 0.5ms, ..., 960KHz SCS is 1 / 64ms, etc.

[0341] In an exemplary embodiment, the wireless device may determine the timeslot length based on an SCS configuration associated with a second BWP of another cell (e.g., a second cell different from the cell), wherein the wireless device receives a first DCI via a second BWP of the second cell and indicates a PDCCH skip on the BWP of the cell.

[0342] In an exemplary embodiment, the wireless device may determine the slot length based on a reference SCS configuration, which is the minimum SCS configuration among all configured DL BWPs in the cell, e.g., if SCS configurations 0, 1, and 2 are configured on the cell (BWP 0 has SCS 0, BWP 1 has SCS1, or BWP 2 has SCS2), the reference SCS configuration may be 0 (corresponding to a 1 ms slot length). SCS configuration 0 may correspond to a 15 KHz SCS, SCS configuration 1 may correspond to a 30 KHz SCS, etc. The UE wireless device may maintain the reference SCS configuration during the timer decrement procedure.

[0343] In an exemplary embodiment, when the PDCCH skip duration expires, or a timer associated with the PDCCH skip duration expires, the wireless device may resume (start or restart) monitoring of the PDCCH on the BWP. Based on resuming PDCCH monitoring, the wireless device may receive a second DCI scheduling PDSCH or PUSCH. The wireless device may receive PDSCH based on the second DCI, or transmit PUSCH based on the second DCI.

[0344] based on Fig.30 In an exemplary embodiment, the wireless device may determine the number of time slots skipped for the PDCCH on the first BWP based on the number and granularity value included in the DCI indicating the PDCCH skip. The wireless device may determine the length of the time slots skipped for the PDCCH on the first BWP of the first cell (e.g., in milliseconds) based on a first parameter set associated with the first BWP or a second parameter set associated with the second BWP. The second BWP may be on the first cell or on the second cell. The wireless device may receive the DCI via the second BWP. By implementing the exemplary embodiment, the base station may adapt the granularity of the time window size skipped by the PDCCH. The base station may reduce the signaling overhead for indicating the time window in the DCI and / or maintain the same DCI size for transmitting the DCI in different frequency bands associated with different parameter sets. The exemplary embodiment may reduce the power consumption of the wireless device.

[0345] In an exemplary embodiment, granular indication for PDCCH skipping in DCI via PDCCH may increase the DCI payload size, which may not be efficient in certain situations, for example, when downlink control channel resources are limited.

[0346] Fig.31 Based on the above Fig.30 A flow chart of an exemplary method for improving signaling overhead for PDCCH skip indication according to one or more exemplary embodiments is described.

[0347] In an exemplary embodiment, Fig.31 As shown, the wireless device may receive an RRC message including configuration parameters for the PDCCH on the BWP of the cell. The configuration parameters may be based on the above description of Fig.23 In an example, the configuration parameters may include a plurality of duration values ​​(eg, in units of time slots) for skipping PDCCH monitoring on a BWP.

[0348] In an exemplary embodiment, the wireless device may monitor the PDCCH on the BWP based on the configuration parameters. The wireless device may receive a DCI indicating a PDCCH skip. The DCI may include a first number (e.g., n) of PDCCH skips. The DCI may be based on the above description of Fig.30 The first number may be indicated from a plurality of duration values ​​configured by an RRC message, which may be received before receiving the DCI.

[0349] In an exemplary embodiment, the base station may indicate a first number of granularities (e.g., time slots, mini-slots, or multi-slots) in one or more RRC messages (e.g., included in the configuration parameters of the PDCCH on the BWP). The one or more RRC messages may include a granularity value for the first number. Based on the granularity indicated via the one or more RRC messages, the wireless device may determine a length of a time window to skip for the PDCCH, where the length is the first number multiplied by the granularity in time slots. The wireless device may skip (or stop) monitoring the PDCCH on the BWP during the time window. After the time window (or when a timer associated with the time window expires), the wireless device may resume (restart) monitoring the PDCCH on the BWP.

[0350] In an example, the granularity of the first number may not be explicitly indicated in one or more RRC messages. The wireless device may determine the granularity (value) of the first number based on a parameter set for the BWP. Different parameter sets may be determined with different granularities (values). Thus, the wireless device may determine the time window size for PDCCH skipping based on the first number and the granularity explicitly indicated in one or more RRC messages.

[0351] like Fig.31 As shown, based on the first number (n) and the parameter set of the BWP, the wireless device (and / or base station) can determine a second number (e.g., m) of time slots to skip for the PDCCH on the BWP. The wireless device can stop monitoring the PDCCH on the BWP during the second number (m) of time slots after receiving the DCI. Fig.30 The described exemplary embodiment determines the time slot length in milliseconds.

[0352] In an exemplary embodiment, the wireless device (and / or base station) may determine that the second number (m) for skipping PDCCH monitoring on the BWP is equal to the first number (n) multiplied by a third number (e.g., l) (e.g., a granularity value). The first number is one of the multiple duration values ​​configured in the RRC message. The third number (l) may be determined (or predefined) based on the parameter set of the BWP. The parameter set index (u) of the parameter set responsive to the BWP is a first value (e.g., 0, 1, 2), and the third number (l) may be 1. In this case, the first number (n) is used for the BWP configured with the parameter set index having the first value. The parameter set index (u) of the parameter set responsive to the BWP is a second value (e.g., 3, 4), and the third number (l) may be 2. In this case, the second number (2*n) is used for the BWP configured with the parameter set index having the second value. The parameter set index (u) of the parameter set responsive to the BWP is a third value (e.g., 5, 6), and the third number (l) may be 4. In this case, the second number (4*n) is used for BWPs configured with parameter set indices having a third value, etc. The association between l and u may be configured by the base station (e.g., in an RRC message, MAC CE, and / or DCI) or predefined to be known to the base station and the wireless device. The parameter set of the BWP associated with the SCS and CP duration may be based on the above description of Figure 7 The exemplary embodiments described are implemented. The configuration of different granularity values ​​(1) for different parameter sets can reduce the signaling overhead for the PDCCH skip duration indication, and / or when the BWP can be configured with parameter sets (or SCSs) in multiple parameter sets (or SCSs), the same bit size of the PDCCH skip duration indication can be maintained.

[0353] Based on the above Fig.30 and / or Fig.31 In the exemplary embodiment described, the length (number of time slots) of the duration for skipping PDCCH monitoring on a BWP configured with a larger SCS (or a higher parameter set index) may be equal to the product of the corresponding length (e.g., n as shown above) of the duration for skipping PDCCH monitoring on a BWP configured with a lower SCS (or a lower parameter set index) and the granularity value (e.g., l as shown above). The granularity value may be a predefined value, such as a ratio of a larger SCS to a lower SCS.

[0354] In an exemplary embodiment, the wireless device may further determine the second number of time slots (m) to skip based on at least one of the following: the number of PDSCHs scheduled by a single DCI (the first DCI or the second DCI) on the BWP (x), the minimum applicable scheduling offset indicator (y) of the first DCI. In an exemplary embodiment, the wireless device may determine m=n*x. In an exemplary embodiment, the wireless device may determine m=n*y. In general, the wireless device may determine the second number (time slots) to skip for the PDCCH based on at least one of the following: the first number indicated by the DCI, the second number determined based on the parameter set of the BWP, the third number of multiple PDSCHs scheduled by a single DCI, the fourth number of the minimum applicable scheduling offset applicable to receiving the PDSCH, etc.

[0355] like Fig.31 As shown, based on the determined second number, the wireless device may stop (or skip) monitoring the PDCCH on the BWP during a time window having a second number (m) of time slots in length, e.g., after the wireless device receives the DCI. The time window may start at the first time slot (e.g., with or without a time slot offset) after the last symbol of the second time slot in which the wireless device receives the DCI.

[0356] like Fig.31 As shown, after the time window expires, the wireless device may resume (start or restart) monitoring of the PDCCH on the BWP. The wireless device may resume monitoring of the PDCCH on the BWP after this number of time slots since receiving the DCI.

[0357] based on Fig.31 In an exemplary embodiment, a granularity indication for PDCCH skipping may be determined based on configuration parameters of BWP (e.g., parameter set, multiple PDSCHs scheduled by DCI, cross-slot scheduling restrictions, etc.). Based on the exemplary embodiment, the base station and / or wireless device may adjust / adapt / determine the granularity of the time window size for PDCCH skipping based on RRC configuration and / or parameter set of BWP. The exemplary embodiment may reduce the signaling overhead for PDCCH skipping indication.

[0358] Fig.32 Based on the above Fig.30 and / or Fig.31 An exemplary embodiment of the PDCCH skip duration indication of one or more exemplary embodiments described. In the example, by implementing the above Figure 7In the exemplary embodiment described, the BWP may be configured with one of the first SCS, the second SCS, the third SCS, the fourth SCS, etc. based on the RRC configuration. In response to the BWP being configured with the first SCS (e.g., 15 KHz), the duration value of the PDCCH skipping may be configured as X, which may be based on the above description of Fig.30 and / or Fig.31 The described exemplary embodiments configure one or more duration values ​​of multiple duration values ​​in the RRC message. In response to the BWP being configured with a second SCS (e.g., 30 KHz), the duration value of the PDCCH skip indication for the BWP can be configured as 2*X. In response to the BWP being configured with a third SCS (e.g., 60 KHz), the duration value of the PDCCH skip indication for the BWP can be configured as 4*X. In response to the BWP being configured with a fourth SCS (e.g., 120 KHz), the duration value of the PDCCH skip indication for the BWP can be configured as 8*X, etc.

[0359] Based on the above Fig.30 , Fig.31 and / or Fig.32 In the exemplary embodiment described, the length (number of time slots) of the duration for skipping PDCCH monitoring on a BWP configured with a larger SCS (or a higher parameter set index) may be equal to the product of the corresponding length of the duration for skipping PDCCH monitoring on a BWP configured with a smaller SCS and the granularity value. The granularity value may be a predefined value, for example, a ratio of a larger SCS to a smaller SCS. Based on the ratio of a larger SCS to a smaller SCS, the granularity value may be one of 2, 4, 8, 16, etc. The smaller SCS may be an SCS of 15KHz, 30KHz, 60KHz, or 120KHz. The smaller SCS may be referred to as a reference SCS. The larger SCS may be an SCS of 240KHz, 480KHz, 960KHz, etc. Based on a fixed relationship (determined based on the granularity value) between the time value of the smaller SCS and the corresponding time value of the larger SCS, the base station may configure a first set of time values ​​for the smaller SCS and a second set of time values ​​for the larger SCS, wherein the first group and the second group have the same size. The first group and the second group having the same size may allow the base station to use the same size of bits to indicate the time value of the PDCCH skip indication for different parameter sets or SCSs.

[0360] By achieving Fig.30 , Fig.31 and / or Fig.32In an exemplary embodiment, the base station can adapt the granularity of the time window size of the PDCCH skipping for different parameter sets, for example, so that the base station can use the same number of bits in the RRC message and / or DCI format to indicate the duration value of the PDCCH skipping for different parameter sets. The base station can reduce the signaling overhead for indicating the time window in the DCI and / or maintain the same DCI size for transmitting the DCI in different frequency bands associated with different parameter sets. The exemplary embodiment can reduce the power consumption of the wireless device.

[0361] In an exemplary embodiment, the base station and / or the wireless device may determine that the first number is in milliseconds (e.g., in absolute time units, rather than in time slots associated with a parameter set). The wireless device may determine the second number of time slots based on the first number and the parameter set of the BWP. In an example, the first number may be indicated as 5 milliseconds. When the parameter set of the BWP has a 15KHz SCS, the wireless device may determine the skip window as 4 time slots (e.g., the second number is equal to 4). When the parameter set of the BWP has a 30KHz SCS, the wireless device may determine the window as 8 time slots. When the parameter set of the BWP has a 60KHz SCS, the wireless device may determine the window as 16 time slots, etc. By way of an exemplary embodiment, by indicating the PDCCH skip window length in milliseconds, the base station may reduce the signaling overhead of the DCI for power saving indication (e.g., when the cell is deployed in a high frequency with a short time slot length) and / or reduce the power consumption of the wireless device.

[0362] In an example, a base station may transmit a PDCCH skip indication for a group of cells (or multiple cell groups). The PDCCH skip indication may include a number in units of time slots. The group of cells may include multiple cells. Each cell (or each BWP of a cell) may be configured with a separate and / or independent parameter set. In the case of different parameter sets, for example, based on the above description of Figure 7In the exemplary embodiment described, the time slot length may be different. Based on the prior art, assuming that different cells (or different BWPs of cells) in a cell group may have different parameter sets, the wireless device may not be able to determine or inefficiently determine how long the wireless device can skip PDCCH monitoring on each cell (or each BWP of the cell) in the cell group. For example, the wireless device may (e.g., mistakenly) stop monitoring the PDCCH on the cell for a longer time than the base station expects, in which case the wireless device may miss downlink signaling reception on the cell. In another example, the wireless device may (e.g., mistakenly) stop monitoring the PDCCH on the cell (or BWP) for a shorter time than the base station expects, in which case the wireless device may wake up too early on the cell (or BWP) and thus increase unnecessary power consumption. Therefore, when the wireless device is instructed to skip PDCCH monitoring on multiple cells (or multiple BWPs of cells), it is necessary to align the base station with the wireless device on the length of the PDCCH skip period.

[0363] In an exemplary embodiment, when different cells in a plurality of cells are configured with different parameter sets, the wireless device may skip monitoring PDCCHs on a plurality of cells (e.g., belonging to a cell group) for the same duration (e.g., several milliseconds), and resume monitoring PDCCHs on the plurality of cells after the same duration. The duration may be determined based on at least one of the following: a number associated with a PDCCH skip indication, and a reference SCS of the plurality of cells. When PDCCH skipping operations are configured on a plurality of cells, the exemplary embodiment may simplify PDCCH monitoring complexity.

[0364] In an exemplary embodiment, the base station may transmit different PDCCH skip durations for different cell groups to the wireless device in a DCI. The exemplary embodiment may reduce the signaling overhead of PDCCH skip duration indication for multiple cell groups and thus also improve (and reduce) power consumption of the wireless device.

[0365] Fig.33 Based on the above Fig.30 , Fig.31 and / or Fig.32 An exemplary embodiment of power saving operation with PDCCH skipping on a cell group of the described exemplary embodiments. In an exemplary embodiment, a wireless device may receive one or more RRC messages from a base station, the one or more RRC messages including configuration parameters for a cell group.

[0366] In an example, a cell group may include one or more cells. Different cell groups may include different cells. A cell may uniquely belong to a cell group in a cell group. A cell group may be identified by a cell group index.

[0367] In an example, a cell may include multiple BWPs, each BWP being associated with a BWP index. The configuration and operation of the BWP may be based on the above description of Fig.23 The exemplary embodiments described are implemented.

[0368] In an example, each BWP of a cell may be associated with a set of parameters (e.g., based on the above description of Figure 7 When a cell is not configured with a BWP, the cell may be associated with a parameter set. In this specification, a BWP / cell may be referred to as a BWP of a cell (e.g., an active BWP) when the cell includes multiple BWPs, or may be referred to as a cell when the cell does not include multiple BWPs.

[0369] like Fig.33 As shown, the wireless device may monitor the PDCCH on the first cell group in the cell group. The wireless device may monitor the PDCCH on the cell (or the active BWP of the cell) based on the configuration parameters of the PDCCH on the cell / BWP. The configuration parameters may be based on the above description of Fig.26 and / or Fig. 27 The exemplary embodiments described are implemented.

[0370] like Fig.33 As shown, a wireless device may receive a first DCI (e.g., a first DCI) indicating skipping of PDCCH monitoring on a first cell group. The first DCI may include a first number (e.g., in units of time slots). Based on the first number and a reference subcarrier spacing (SCS), the wireless device may determine a duration of the PDCCH skipping on the first cell group.

[0371] In an exemplary embodiment, the first number may be indicated as X. In response to the reference SCS being associated with a first parameter set index (e.g., corresponding to a 15KHz SCS), the wireless device may determine the duration to be X milliseconds. After receiving the first DCI, the wireless device may skip monitoring the PDCCH on the first cell group within X milliseconds. If the first cell (or the active BWP of the first cell) is configured with a 15KHz SCS, the wireless device may skip monitoring the PDCCH on the first cell (or the active BWP of the first cell) in the first cell group within X time slots. If the second cell (or the active BWP of the second cell) is configured with a 30KHz SCS, the wireless device may skip monitoring the PDCCH on the second cell in the first cell group within 2*X time slots. If the third cell (or the active BWP of the third cell) is configured with a 60KHz SCS, the wireless device may skip monitoring the PDCCH on the third cell in the first cell group within 4*X time slots, etc.

[0372] In an exemplary embodiment, the first number may be indicated as X. In response to the reference SCS being associated with a second parameter set index (e.g., corresponding to a 30KHz SCS), the wireless device may determine the duration to be X / 2 milliseconds. After receiving the first DCI, the wireless device may skip monitoring the PDCCH on the first cell group within X / 2 milliseconds. If the first cell is configured with a 15KHz SCS, the wireless device may skip monitoring the PDCCH on the first cell in the first cell group within X / 2 time slots. If the second cell (or the active BWP of the second cell) is configured with a 30KHz SCS, the wireless device may skip monitoring the PDCCH on the second cell (or the active BWP of the second cell) in the first cell group within X time slots. If the third cell (or the active BWP of the third cell) is configured with a 60KHz SCS, the wireless device may skip monitoring the PDCCH on the third cell in the first cell group within 2*X time slots, etc.

[0373] In an exemplary embodiment, the wireless device may determine the reference SCS as the SCS associated with the lowest (or highest) parameter set (or SCS) index in the BWP of one or more cells in the first cell group.

[0374] In an exemplary embodiment, the wireless device may determine the reference SCS as the SCS associated with a set of parameters of a (downlink) active BWP of a BWP of one or more cells in the first cell group, on which the wireless device receives the first DCI.

[0375] In an exemplary embodiment, the wireless device may determine the reference SCS as the SCS associated with the parameter set of the (downlink) BWP of the BWP of the PCell of one or more cells in the first cell group. The BWP may be the initial BWP of the PCell or the active BWP of the PCell. Fig. 10A and / or Fig. 10B The exemplary embodiments described are used to configure a PCell.

[0376] In an exemplary embodiment, based on the first number and the reference SCS, the wireless device may determine the length of the time window as a first number of time slots, wherein the time slot length is based on the reference SCS.

[0377] In an exemplary embodiment, the wireless device may determine that the duration is applied to all cells in the first cell group. Based on the determination, the wireless device may stop monitoring the PDCCH on the first cell group for the duration. The duration may start from the first time slot after the last symbol of the second time slot in which the wireless device receives the first DCI. Based on the time slot described later, Fig.34 In an exemplary embodiment, when different cells in the first cell group are configured with different parameter sets, the wireless device may skip PDCCH monitoring on different cells with different numbers of time slots.

[0378] based on Fig.33 In an exemplary embodiment, when different cells in a plurality of cells are configured with different parameter sets, a wireless device may skip monitoring PDCCHs on a plurality of cells (e.g., belonging to the same cell group) for the same duration (e.g., several milliseconds), and resume monitoring PDCCHs on the plurality of cells after the same duration. The duration may be determined based on at least one of: a number associated with a PDCCH skip indication, and a reference SCS of the plurality of cells. When a PDCCH skip operation is configured on a plurality of cells, the exemplary embodiment may simplify PDCCH monitoring complexity.

[0379] Fig.34 An exemplary embodiment of power saving operation with PDCCH skipping on multiple cells (or multiple BWPs of cells) is shown. In the example, the wireless device can be configured with a certain number of cells, each cell including a corresponding active BWP (e.g., BWP1 of cell 1, BWP2 of cell 2, BWP3 of cell 3, BWP4 of cell 4, etc.). BWP1, BWP2, BWP3, and BWP4 can be configured in the same cell. Based on the above description of Fig.23The exemplary embodiment described herein can be used to activate the number of cells. BWP1 of cell 1 can be configured with 15KHz SCS, BWP2 can be configured with 30KHz SCS, BWP3 can be configured with 60KHz SCS, BWP4 can be configured with 120KHz SCS, etc. In the example, a 15KHz-SCS time slot (e.g., 1 millisecond) can have the same length as 2 30KHz-SCS time slots, 4 60KHz-SCS time slots, 8 120KHz-SCS time slots, etc.

[0380] In an example, a wireless device may receive a DCI including a number (X) of PDCCH skips on multiple cells. The DCI may be based on the above description of Fig.33 The exemplary embodiments described are implemented (e.g., Fig.33 The first DCI in the DCI).

[0381] In an example, the wireless device may determine the PDCCH skip duration based on X and the reference SCS. The reference SCS may be based on the above description of Fig.33 The exemplary embodiment described is implemented. In the exemplary embodiment, the wireless device may determine the reference SCS to be 15KHz. Based on determining the reference SCS to be 15KHz, the wireless device may determine the PDCCH skip duration to be X milliseconds. Based on determining the PDCCH skip duration to be X milliseconds, the wireless device may skip monitoring the PDCCH on BWP1 with X time slots (e.g., 15KHz-SCS time slot is 1 millisecond), skip monitoring the PDCCH on BWP2 with 2*X time slots (e.g., 30KHz-SCS time slot is 0.5 milliseconds), skip monitoring the PDCCH on BWP3 with 4*X time slots (e.g., 60KHz-SCS time slot is 0.25 milliseconds), skip monitoring the PDCCH on BWP4 with 8*X time slots (e.g., 120KHz-SCS time slot is 0.125 milliseconds), etc. Based on the exemplary embodiment, although the wireless device skips PDCCH monitoring on different cells (or different BWPs) with different numbers of time slots, the wireless device can skip PDCCH monitoring on multiple cells (or multiple BWPs of a cell) with the same duration (e.g., X milliseconds). When PDCCH skipping operation is configured on multiple cells (or multiple BWPs of a cell), the exemplary embodiment can simplify the PDCCH monitoring complexity. The exemplary embodiment can reduce the power consumption of the wireless device for performing PDCCH monitoring on multiple cells (or multiple BWPs of a cell).

[0382] In an exemplary embodiment, the wireless device may determine a corresponding PDCCH skip duration for each of the plurality of cells based on X and a corresponding SCS associated with each of the plurality of cells. Fig.34 15KHz SCS is configured on BWP1 of cell 1 in the wireless device, the wireless device may determine the first PDCCH skip duration of the first cell / BWP to be X milliseconds including X time slots (e.g., a 15KHz-SCS time slot is 1 millisecond). Fig.34 2 in the second cell / BWP (e.g., BWP2 of cell 2 in the wireless device), the wireless device may determine the second PDCCH skip duration of the second cell / BWP to be X / 2 milliseconds including X time slots (e.g., a 30 KHz-SCS time slot is 1 / 2 millisecond). Fig.34 Based on configuring 60KHz SCS on BWP3 of cell 3 in the wireless device, the wireless device may determine the third PDCCH skip duration of the third cell / BWP to be X / 4 milliseconds including X time slots (e.g., a 60KHz-SCS time slot is 1 / 4 millisecond). Fig.34 For example, if a 120KHz SCS is configured on BWP4 of cell 4 in the wireless device, the wireless device may determine a fourth PDCCH skip duration of a fourth cell / BWP as X / 8 milliseconds including X time slots (e.g., a 120KHz-SCS time slot is 1 / 8 millisecond), etc. The wireless device may skip monitoring the PDCCH on the first cell / BWP during the first PDCCH skip duration, skip monitoring the PDCCH on the second cell / BWP during the second PDCCH skip duration, etc. An exemplary embodiment may enable the wireless device to skip PDCCH monitoring on different cells with different durations. An exemplary embodiment may reduce downlink signaling transmission latency, however, may increase power consumption of the wireless device.

[0383] Fig.35 An exemplary embodiment of power saving operation with PDCCH skipping on multiple cell groups is shown. In the example, the wireless device can receive one or more RRC messages from a base station, the one or more RRC messages including configuration parameters of the cell groups. The cell groups can be based on the above description of Fig.34 The exemplary embodiments described are implemented.

[0384] In an example, the wireless device may monitor the PDCCH on the cell group. The wireless device may receive a DCI indicating to skip the PDCCH monitoring on one or more cell groups in the cell group. The DCI may include a plurality of numbers, each number corresponding to a cell group in the cell group. The association between the number in the plurality of numbers and the corresponding cell group in the cell group may be based on the information described later. Fig.37 The wireless device may apply a quantity for skipping PDCCH monitoring to a corresponding cell group. Different quantities may correspond to different cell groups. A quantity with a value of 0 may indicate that the wireless device continues (does not stop / does not skip) PDCCH monitoring on the cell group associated with the quantity.

[0385] In an example, based on a first number of the numbers indicated in the DCI (e.g., and a parameter set, etc.), the wireless device may determine a first duration (e.g., a first duration) corresponding to a PDCCH skip on a first number of cell groups. The wireless device may determine a first duration (e.g., a first duration) corresponding to a PDCCH skip on a first number of cell groups based on the first number of the numbers indicated in the DCI. Fig.30 , Fig.31 , Fig.32 , Fig.33 and / or Fig.34 The described exemplary embodiment determines a first duration.

[0386] Similarly, based on a second number of the numbers indicated in the DCI (e.g., and a parameter set, etc.), the wireless device may determine a second duration (e.g., a second duration) corresponding to the PDCCH skipping on the second number of cell groups. The wireless device may determine a second duration (e.g., a second duration) corresponding to the PDCCH skipping on the second number of cell groups based on the second number of the numbers indicated in the DCI (e.g., and a parameter set, etc.). Fig.30 , Fig.31 , Fig.32 , Fig.33 and / or Fig.34 The described exemplary embodiment determines a second duration.

[0387] In an exemplary embodiment, the wireless device may skip PDCCH monitoring on the first cell group for a first duration. The wireless device may skip PDCCH monitoring on the second cell group for a second duration. The first duration and the second duration may start from a first time slot after the last symbol of a second time slot in which the wireless device receives DCI.

[0388] In an exemplary embodiment, when the first duration expires, the wireless device may resume PDCCH monitoring on the first group of cells. When the second duration expires, the wireless device may resume PDCCH monitoring on the second group of cells, and so on.

[0389] Fig.36An exemplary implementation of power saving operation with PDCCH skipping on multiple cell groups is shown. In the example, a base station may transmit one or more RRC messages to a wireless device, the one or more RRC messages including configuration parameters for power saving operation based on PDCCH skipping on multiple cell groups. The configuration parameter may indicate an association between a cell group in a cell group and a number of multiple quantities indicated in a DCI indicating PDCCH skipping (or a PDCCH skipping indicating DCI). The configuration parameter may include a corresponding position parameter for each cell group (e.g., identified by a cell group index). The position parameter may indicate which number of multiple quantities included in the DCI applies to the cell group. A number of the multiple quantities in the DCI determined based on the position parameter associated with the cell group may indicate a duration during which the wireless device may skip monitoring the PDCCH on the cell group. As Fig.36 As shown, the first number among the numbers indicated in the DCI may correspond to a first cell group including cell 1, cell 2, etc., and may indicate a first duration for skipping monitoring of the PDCCH on the first cell group. The second number may correspond to a second cell group including cell m, cell m+1, etc., and may indicate a second duration for skipping monitoring of the PDCCH on the second cell group, etc.

[0390] based on Fig.35 and / or Fig.36 Exemplary embodiments (e.g., in combination with Fig.30 , Fig.31 , Fig.32 , Fig.33 and / or Fig.34 In one or more of the above), the base station may transmit different PDCCH skip durations for different cell groups to the wireless device in the DCI. The exemplary implementation may improve the power consumption of the wireless device and / or reduce the signaling overhead of the PDCCH skip duration indication for multiple cell groups.

[0391] In an example, the wireless device may be configured with DRX operation. The DRX operation may be based on the above description of Fig.22A and / or Fig. 22BThe exemplary embodiments described are implemented. The wireless device may be configured with multiple cell groups. Each cell group may include one or more cells. The wireless device may perform DRX operations for each cell group individually and / or independently. In the example, each cell group (or may be referred to as each DRX group in this specification) may be configured with separate DRX parameters. When multiple DRX groups are configured, each cell may be uniquely assigned to one of the multiple groups. The DRX parameters that may be configured separately for each DRX group may include at least one of drx-onDurationTimer and drx-InactivityTimer. The DRX parameters that may be shared by multiple groups may include at least one of the following: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL. The wireless device may perform a first DRX operation for the first cell group based on the DRX parameters associated with the first cell group, independently of one or more DRX operations for other cell groups.

[0392] In the prior art, when DRX operation is configured, a base station may transmit a PDCCH skip indication to a wireless device, the PDCCH skip indication indicating that PDCCH monitoring is skipped during a DRX on-duration (e.g., when drx-onDurationTimer is running). By implementing the prior art, when multiple DRX groups (or cell groups) are configured, the wireless device may not be able to determine or inefficiently determine on which cell group(s) of the multiple DRX groups the wireless device may skip PDCCH monitoring in response to receiving a PDCCH skip indication indicating that PDCCH monitoring is skipped during a DRX on-duration period. For example, different DRX groups may have DRX on-duration periods of different lengths. Therefore, the base station and the wireless device may not be aligned in terms of whether the wireless device may skip PDCCH monitoring on one or more DRX groups in response to a PDCCH skip indication indicating that PDCCH monitoring is skipped during a DRX on-duration period. The use of the prior art may increase signaling / data transmission latency and result in increased power consumption of the wireless device. It is necessary to reduce power consumption of the wireless device and / or reduce signaling / data transmission latency.

[0393] In an exemplary embodiment, the wireless device can determine on which cell group(s) the wireless device can skip PDCCH monitoring during the DRX on duration based on at least one of the following: a PDCCH monitoring skip indication and / or a BWP / cell on which the wireless device receives the PDCCH monitoring skip indication.

[0394] In an exemplary embodiment, the PDCCH skip indication may be indicated per DRX group. Based on receiving a PDCCH skip indication on a cell belonging to a DRX group, the PDCCH skip indication may be indicated for the DRX group. In response to receiving a PDCCH skip indication in a first cell belonging to a first DRX group, the wireless device may apply the PDCCH skip indication to the first DRX group. An exemplary embodiment may flexibly indicate PDCCH skipping for different DRX groups by transmitting the PDCCH skip indication via different DRX groups. An exemplary embodiment may reduce signaling / data transmission latency.

[0395] In an exemplary embodiment, a PDCCH skip indication may be indicated for all DRX groups. The wireless device may determine that the PDCCH skip indication is applied to all DRX groups regardless of which cell in the DRX group the wireless device receives the PDCCH skip indication on. The wireless device may skip PDCCH monitoring on all cells in the DRX group within all DRX on-durations, the DRX on-durations including: a first DRX on-duration corresponding to a first DRX group, and a second DRX on-duration corresponding to a second DRX group, etc. The exemplary embodiment may reduce the signaling overhead of the PDCCH skip indication for multiple DRX groups. When the wireless device is configured with multiple DRX groups, the exemplary embodiment may reduce the power consumption of the wireless device.

[0396] In an exemplary embodiment, the PDCCH skip indication may be indicated per DRX group. The DCI may include multiple PDCCH skip indications, each indication corresponding to a corresponding DRX group in multiple DRX groups. The wireless device may apply a first PDCCH skip indication to a first DRX group based on a first PDCCH skip indication corresponding to a first DRX group among multiple PDCCH skip indications in the DCI, thereby indicating that PDCCH monitoring is skipped during the DRX on duration. The wireless device may apply a second PDCCH skip indication to a second DRX group based on a second PDCCH skip indication corresponding to a second DRX group among multiple PDCCH skip indications in the DCI, thereby indicating that PDCCH monitoring is skipped during the DRX on duration. The exemplary embodiment may flexibly indicate PDCCH skipping for different DRX groups. Therefore, the exemplary embodiments of the present disclosure may reduce signaling / data transmission waiting time.

[0397] Fig.37 An exemplary embodiment of power saving operation with PDCCH skipping combined with DRX operation is shown. In the example, the base station can transmit and / or the wireless device can receive one or more RRC messages including multiple cell groups (e.g., a first cell group, a second cell group, etc.). The multiple cell groups can be based on the above description of Fig.33 The exemplary embodiments described are implemented. When a first cell group is configured with a first DRX operation, the first cell group may be referred to as a first DRX group (e.g., which may be deployed in a first frequency band). When a second cell group is configured with a second DRX operation, the second cell group may be referred to as a second DRX group (e.g., which may be deployed in a second frequency band), etc. Different DRX groups may be associated with different DRX parameters.

[0398] In an exemplary embodiment, different DRX groups may be configured with the same DRX parameters, which include at least one of the following: DRX parameters that may be common to multiple groups may include at least one of the following: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL.

[0399] In an exemplary embodiment, different DRX groups may be configured with separate and / or independent parameters including at least one of drx-onDurationTimer and / or drx-InactivityTimer.

[0400] like Fig.37 As shown, the first cell group may be configured with a first DRX on duration (or a first drx-onDurationTimer). The second cell group may be configured with a second DRX on duration (or a second drx-onDurationTimer). The first drx-onDurationTimer may be different from the second drx-onDurationTimer (e.g., having a different length). The lengths of the DRX cycles (e.g., indicated by drx-ShortCycle or drx-LongCycleStartOffset) of different DRX groups may be the same.

[0401] In an exemplary embodiment, the wireless device can determine on which cell group(s) the wireless device can skip PDCCH monitoring during the DRX on duration based on at least one of the following: a PDCCH monitoring skip indication and / or a BWP / cell on which the wireless device receives the PDCCH monitoring skip indication.

[0402] In an exemplary embodiment, in response to receiving a first DCI indicating skipping of PDCCH monitoring during a DRX On Duration via a BWP / cell of a first DRX group, the wireless device may determine that the wireless device may skip PDCCH monitoring on the first DRX group during a first DRX On Duration associated with (or configured on) the first DRX group. The wireless device may receive the first DCI during the first DRX On Duration (or while a first drx-OnDurationTimer is running). The first drx-OnDurationTimer may be started before the wireless device receives the first DCI (e.g., at the start of a DRX cycle). The first DCI may include a first number (e.g., a first skip indicator) for PDCCH skip indications. The first number set to a first value (e.g., a predefined value, a non-numeric value) may indicate that PDCCH monitoring is skipped during (a remaining period of) the DRX On Duration. The remaining period of the DRX On Duration may start from a time slot after receiving the first DCI and end in response to the expiration of the first drx-OnDurationTimer. Depending on the DRX operation and / or when the wireless device receives the first DCI, the remaining period of the DRX On Duration may have a variable length. When indicated as a second value different from the first value (e.g., an integer equal to or greater than 0), the first number may indicate a first number of slots to skip for PDCCH (or a first number of milliseconds to skip for PDCCH). Skipping PDCCH monitoring on the first DRX group may not affect PDCCH monitoring on the second DRX group by the wireless device. Fig.36 As shown, although the wireless device stops monitoring the PDCCH on the first DRX group based on receiving the first DCI, the wireless device may continue to monitor the PDCCH on the second DRX group.

[0403] In an exemplary embodiment, the wireless device may receive a second skip indicator (e.g., in a second DCI) via a second cell of a second DRX group. Based on receiving the second skip indicator via the second cell of the second DRX group, the wireless device may stop (or skip) PDCCH monitoring on the second DRX group. The wireless device may receive the second DCI during the second DRX on duration (or when the second drx-OnDurationTimer is running). The second drx-OnDurationTimer may be started before the wireless device receives the second DCI (e.g., at the start of the DRX cycle). The second DCI may include a second number (e.g., a second skip indicator) for PDCCH skip indications. The second number set to a first value (e.g., a predefined value, a non-numeric value) may indicate that PDCCH monitoring is skipped within (the remaining period of) the DRX on duration. The remaining period of the DRX on duration may start from a time slot after the second DCI is received and may end in response to the expiration of the second drx-OnDurationTimer. The remaining period of the DRX on duration may have a variable length depending on the DRX operation and / or when the wireless device receives the second DCI. When indicated as a second value different from the first value (e.g., an integer equal to or greater than 0), the second number may indicate a second number of slots skipped for the PDCCH (or a second number of milliseconds skipped for the PDCCH). Skipping PDCCH monitoring on the second DRX group may not affect PDCCH monitoring of the wireless device on the first DRX group.

[0404] based on Fig.37 In an exemplary embodiment, the wireless device may perform a PDCCH skipping operation per DRX group based on receiving a PDCCH skipping indication on a cell in a plurality of cell groups. When a PDCCH skipping indication is received via a cell belonging to a DRX group, the wireless device may apply the PDCCH skipping indication to the DRX group. A PDCCH skipping indication received in a cell belonging to a first DRX group may not be applied to any cell of a second DRX group that is different from the first DRX group. An exemplary embodiment may enable the wireless device to perform power saving operations per cell group based on a PDCCH skipping operation in combination with a DRX operation. An exemplary embodiment may reduce signaling / data transmission waiting time while maintaining low power consumption.

[0405] In an example, transmitting multiple DCIs (each DCI including a PDCCH skip indicator per DRX group) may increase signaling overhead, which may not be efficient when downlink control channel resources are limited. In an exemplary embodiment, the base station may transmit a single DCI including multiple PDCCH skip indicators, each PDCCH skip indicator corresponding to a DRX group in a plurality of DRX groups, and indicating that PDCCH monitoring is skipped during a DRX on duration associated with the corresponding DRX group. The exemplary embodiment may be implemented by Fig.35 , Fig.36 and / or Fig. 22B It is achieved by combining the DRX operations.

[0406] In an exemplary embodiment, the base station may transmit a DCI including multiple quantities (e.g., Fig.36 In the example, corresponding to the first cell group (eg, Fig.36 A first number corresponding to the second cell group may be set to a first value (e.g., a predefined value, a non-numeric value), which may indicate that PDCCH monitoring is skipped during (the remaining period of) a first DRX on-duration associated with the first cell group. A second number corresponding to the second cell group may be set to a first value (e.g., a predefined value, a non-numeric value), which may indicate that PDCCH monitoring is skipped during (the remaining period of) a second DRX on-duration associated with the second cell group, etc. Based on Fig.35 and / or Fig.36 In an exemplary embodiment, when set to a second value different from the first value, the number in the plurality of numbers may indicate a duration for skipping PDCCH monitoring. The association between the plurality of numbers and the plurality of DRX groups may be based on the above description of Fig.36 The exemplary embodiments described are implemented.

[0407] In an example, in response to a first number (e.g., set to a first value) associated with a first DRX group indicating that PDCCH monitoring is skipped during a DRX on duration, the wireless device may skip PDCCH monitoring on the first DRX group during the first DRX on duration. In response to a second number (e.g., set to a first value) associated with a second DRX group indicating that PDCCH monitoring is skipped during a DRX on duration, the wireless device may skip PDCCH monitoring on the second DRX group during a second DRX on duration, and so on. Based on an exemplary embodiment, a base station may transmit and / or a wireless device may receive a single DCI including multiple PDCCH skip indications, each PDCCH skip indication corresponding to a DRX group among multiple DRX groups, and indicating that PDCCH monitoring is skipped during a DRX on duration associated with the corresponding DRX group. An exemplary embodiment may reduce signaling overhead for PDCCH skip indications for multiple DRX groups.

[0408] Based on the above Fig.30 , Fig.31 , Fig.32 , Fig.33 , Fig.34 , Fig.35 , Fig.36 and / or Fig.37 In the described exemplary embodiment, the wireless device may monitor the PDCCH on the BWP of the cell. The wireless device may receive a DCI indicating to stop monitoring the PDCCH on the BWP during the monitoring of the PDCCH, wherein the DCI includes a first field indicating a first time value and / or a second field indicating a granularity value of the first time value. The wireless device may determine a first number of time slots for skipping monitoring of the PDCCH based on the first time value and the granularity value. The wireless device may stop monitoring the PDCCH on the BWP for a duration, wherein the duration starts from the first time slot after receiving the DCI and has a length of the first number of time slots. The wireless device may resume monitoring the PDCCH on the BWP after the duration.

[0409] According to an exemplary embodiment, when the wireless device stops monitoring the PDCCH on the BWP, the wireless device may keep the BWP in an active state. The DCI does not indicate an active BWP switch.

[0410] According to an exemplary embodiment, the first time slot may be the next time slot after the last symbol of the current time slot in which the wireless device receives the DCI. The DCI includes at least one of the following: a group common DCI addressed to a plurality of wireless devices including the wireless device and / or a wireless device-specific DCI addressed to the wireless device.

[0411] According to an exemplary embodiment, the first time slot may be a second time slot that occurs at a second number of time slots after the last symbol of the current time slot. The wireless device receives the DCI in the current time slot. The second number may be determined based on at least one of a wireless device processing capability and a PDCCH skip delay parameter included in one or more RRC messages. The PDCCH skip delay parameter may indicate a second number of time slots after which the wireless device may apply a PDCCH skip operation since receiving the DCI. Within the second number of time slots after receiving the DCI, the wireless device may not apply the PDCCH skip operation.

[0412] According to an exemplary embodiment, the granularity value set to the first value may indicate that the first time value is in units of time slots, wherein the time slot length is based on a parameter set of the BWP. Based on the first time value being in units of time slots, the first number may be determined as the first time value.

[0413] According to an exemplary embodiment, the granularity value set to the second value may indicate that the first time value is in units of mini-slots, wherein a mini-slot includes one or more symbols of a time slot. The first quantity is determined as the first time value multiplied by a second value, wherein the second value is 1 / x, and x is the total number of mini-slots included in the time slot.

[0414] According to an exemplary embodiment, the granularity value set to the third value may indicate that the first time value is in units of multislots, wherein the multislots include a second number of slots, the second number being greater than 1. The first number is determined as the first time value multiplied by the second number.

[0415] According to an exemplary embodiment, a wireless device may receive one or more RRC messages including configuration parameters of a cell. The cell may include multiple BWPs including a BWP. Each BWP of the cell may be configured with a parameter set associated with one or more parameter set parameters, the one or more parameter set parameters including at least one of a parameter set index, a subcarrier spacing value, and a cyclic prefix value. The wireless device may activate the BWP based on receiving an activation command indicating activation of the BWP. The activation command may include at least one of the following: a second DCI indicating a switch from a second BWP of the cell to an active BWP of the BWP, a MAC CE indicating activation of the cell, and / or an RRC message including a cell status indication indicating an activity status of the cell.

[0416] According to an exemplary embodiment, the wireless device may receive one or more RRC messages from a base station including a configuration parameter indicating multiple time values, wherein a first field of the DCI indicates a time value in the multiple time values. The multiple time values ​​may include one or more integers greater than zero.

[0417] In an example, the plurality of time values ​​may include the number zero. When the first time value indicates the number zero, the wireless device may continue to monitor the PDCCH on the BWP.

[0418] According to an exemplary embodiment, the plurality of time values ​​may include a predefined value. The predefined value may include a non-numeric value. When the first time value indicates the predefined value, the wireless device may stop monitoring the PDCCH on the bandwidth portion during the DRX On Duration of the DRX operation.

[0419] According to an exemplary embodiment, the plurality of time values ​​may include predefined values. The predefined values ​​may include non-numeric values. When the first time value indicates the predefined value, the wireless device may stop monitoring the PDCCH on the BWP within a time window associated with the first SSG on the BWP. The time value of the time window may be indicated in a configuration parameter.

[0420] According to an exemplary embodiment, in response to expiration of the time window, the wireless device may switch from the first SSG to the second SSG on the BWP.

[0421] According to an exemplary embodiment, the wireless device may receive one or more RRC messages including configuration parameters of multiple SSGs on a BWP of a cell, wherein the multiple SSGs include a first SSG and a second SSG. Each SSG in the multiple SSGs may include one or more search spaces having the same SSG group index. The DCI may not indicate that the SSG is switched from the first SSG to the second SSG.

[0422] According to an exemplary embodiment, the configuration parameters may include a first configuration parameter for a search space, wherein the first configuration parameter includes: a search space indicator identifying the search space, a control resource set indicator indicating a control resource set associated with the search space, a monitoring slot period and offset parameter for PDCCH monitoring on the search space, a duration, a monitoring symbol within the slot indicator, a number of candidates, a search space type, and / or one or more SSG group indices associated with the search space. The control resource set may be configured with a second configuration parameter, the second configuration parameter including: a frequency domain resource configuration parameter, a duration value, a control channel element to resource element group mapping type indication, and / or a control resource set pool index.

[0423] In an exemplary embodiment, the wireless device may receive a DCI indicating skipping of PDCCH monitoring on the BWP, wherein the DCI indicates a time value and / or a granularity value. The wireless device may determine a number of time slots for skipping PDCCH monitoring based on the time value and the granularity value. The wireless device may stop monitoring PDCCH on the bandwidth portion during the number of time slots. The wireless device may resume monitoring PDCCH on the BWP after the number of time slots.

[0424] In an exemplary embodiment, the wireless device may receive a DCI indicating to stop monitoring the PDCCH on the BWP, wherein the DCI includes a field indicating a time value among a plurality of time values. The wireless device may determine the granularity of the time value based on a parameter set of the BWP. The wireless device may stop monitoring the PDCCH on the BWP for a duration of a number of time slots. The number may be determined based on the time value and the granularity. The wireless device may resume monitoring the PDCCH on the BWP after the duration.

[0425] According to an example embodiment, the wireless device may monitor the PDCCH on the BWP before receiving the DCI.

[0426] According to an exemplary embodiment, in response to the parameter set being a first value, the granularity may be in units of time slots.

[0427] According to an exemplary embodiment, in response to the parameter set being a second value, the granularity may be in units of a fraction of a time slot, wherein the fraction is determined based on the second value.

[0428] According to an exemplary embodiment, in response to the parameter set being a third value, the granularity may be in units of a number of time slots, wherein the number is determined based on the third value.

[0429] According to an exemplary embodiment, the granularity can be further determined based on at least one of: a first number of PDSCHs scheduled by the DCI, wherein the first number of PDSCHs are transmitted in multiple time slots, and a second number of time slots for the gap between the first time slot of the DCI and the second time slot of the PDSCH scheduled by the DCI.

[0430] In an exemplary embodiment, a wireless device may receive configuration parameters for a cell group, each cell group including one or more cells. The wireless device may monitor a PDCCH on the cell group. The wireless device may receive a DCI during monitoring of the PDCCH, the DCI including a number for skipping PDCCH monitoring on a first cell group in the cell group. The wireless device may determine a first parameter set for the first cell group based on the configuration parameters. The wireless device may determine a duration for skipping PDCCH monitoring based on the number and the first parameter set. The wireless device may skip monitoring one or more PDCCHs on the first cell group during the duration. The wireless device may resume (or restart) monitoring one or more PDCCHs on the first cell group in response to expiration of the duration.

[0431] According to an exemplary embodiment, a cell may include multiple BWPs, each BWP being associated with a (BWP-specific) parameter set identified by a parameter set index, a subcarrier spacing value and / or a cyclic prefix value.

[0432] According to an exemplary embodiment, a cell may be associated with a (cell-specific) parameter set identified by a parameter set index, a subcarrier spacing value and / or a cyclic prefix value.

[0433] According to an exemplary embodiment, the first parameter set may be a reference parameter set associated with a minimum subcarrier spacing between BWPs of one or more cells in the first cell group.

[0434] According to an exemplary embodiment, the first parameter set may be a reference parameter set associated with a minimum subcarrier spacing between one or more cells in the first cell group.

[0435] According to an exemplary embodiment, the first parameter set may be a reference parameter set associated with a maximum subcarrier spacing between one or more cells in the first cell group.

[0436] According to an exemplary embodiment, the first set of parameters may be a set of reference parameters associated with a downlink BWP on which the wireless device receives the DCI.

[0437] According to an exemplary embodiment, the duration may have a length of a number of time slots, wherein the length of the time slot is determined based on the first set of parameters.

[0438] In an exemplary embodiment, a wireless device may receive configuration parameters for a cell group, each cell group including one or more cells. The wireless device may monitor a PDCCH on a cell group. The wireless device may receive a DCI including a number for skipping monitoring of a PDCCH on a cell group, wherein each number in the number corresponds to a corresponding cell group in the cell group. The wireless device may determine a first duration for skipping monitoring of a first PDCCH on a first cell group based on a first number corresponding to a first cell group. The wireless device may skip monitoring of a first PDCCH on a first cell group within a first duration. The wireless device may resume (start or restart) monitoring of a first PDCCH on a first cell group after the first duration.

[0439] According to an exemplary embodiment, the first duration may have a first number of time slots, wherein the length of the time slot is determined based on a reference parameter set of one or more cells in the first cell group. The reference parameter set may be a minimum parameter set among the parameter sets of the one or more cells. The reference parameter set may be a parameter set of a BWP on which the wireless device receives the DCI.

[0440] According to an exemplary embodiment, the first number may be in milliseconds, and the first duration may have a length of the first number of milliseconds.

[0441] According to an exemplary embodiment, the first number set to the first value may indicate that the first duration is a time period that starts after receiving the DCI and is within the duration that a first DRX on-duration timer associated with the first cell group is running.

[0442] According to an exemplary embodiment, a wireless device may receive one or more RRC messages including a first configuration parameter for a first DRX operation associated with a first cell group and a second configuration parameter for a second DRX operation associated with a second cell group in the cell group. The first configuration parameter may include a first timer value for a first DRX on duration timer. The second configuration parameter may include a second timer value for a second DRX on duration timer.

[0443] According to an exemplary embodiment, the wireless device may determine a second duration for skipping monitoring of a second PDCCH on the second cell group based on a second quantity in the quantity and corresponding to the second cell group. The wireless device may skip monitoring of the second PDCCH on the second cell group during the second duration. The wireless device may resume monitoring of the second PDCCH on the second cell group after the second duration. The second quantity set to the first value may indicate that the second time is a time period after receiving the DCI and during which a second DRX on-duration timer associated with the second cell group is running.

[0444] In an exemplary embodiment, the wireless device may receive configuration parameters for cell groups, each cell group including one or more cells. The wireless device may monitor the PDCCH on the cell group. The wireless device may receive a first DCI including a PDCCH skip indicator via a first cell in a first cell group in the cell group and while a first DRX on duration timer is running. Based on receiving the DCI via the first cell in the first cell group, the wireless device may determine that the PDCCH skip indicator is applied to the first cell group. When the first DRX on duration timer is running, the wireless device may skip monitoring the first PDCCH on the first cell group after receiving the first DCI.

[0445] According to an exemplary embodiment, while the second DRX On Duration timer is running, the wireless device may continue to monitor the second PDCCH on the second cell group regardless of whether the first DCI is received.

[0446] According to an exemplary embodiment, the wireless device may receive a second DCI including a PDCCH skip indicator via a second cell in a second cell group in the cell group and while a second DRX on duration timer is running. When the second DRX on duration timer is running, the wireless device may skip monitoring a second PDCCH on the second cell group after receiving the second DCI.

[0447] According to an exemplary embodiment, the wireless device may start a first DRX on-duration timer with a first initial timer value at the beginning of a first DRX cycle associated with the first cell group. The PDCCH skip indicator included in the DCI may be received while the first DRX on-duration timer is running.

[0448] According to an exemplary embodiment, the PDCCH skip indicator set to a first value may indicate that the wireless device skips PDCCH monitoring on the first cell group during a time period when the first DRX on-duration timer is running. The first value may be a predefined value. The first value may be a non-numeric value.

Claims

1. A method comprising: receiving, by a wireless device, a configuration parameter indicating a plurality of values ​​for skipping physical downlink control channel (PDCCH) monitoring on a bandwidth part (BWP) having a first set of parameters; Receive downlink control information DCI, the DCI indicating: a first value of the plurality of values; as well as Skipping PDCCH monitoring on the BWP; Determining, based on the first value of the BWP and a first set of parameters, a number of time slots for skipping PDCCH monitoring; as well as Monitoring of the PDCCH on the BWP is skipped for the number of time slots.

2. The method of claim 1, wherein the configuration parameters are received in a radio resource RRC message.

3. The method of any one of claims 1 to 2, wherein the plurality of values ​​are in units of time slots.

4. The method according to any one of claims 2 to 3, wherein: A first parameter set of a BWP of a cell is indicated through the RRC message, wherein the cell includes one or more BWPs having the BWP.

5. The method of any one of claims 1 to 4, further comprising resuming monitoring of the PDCCH on the BWP after the number of time slots. 6 . The method according to claim 1 , wherein the DCI is received in a DRX active time of a discontinuous reception (DRX) configuration.

7. The method of any one of claims 1 to 6, wherein the number is determined as the product of the first value and a fixed numerical value associated with the first set of parameters.

8. A method comprising: Transmitting, by a base station, a configuration parameter to a wireless device, the configuration parameter indicating a plurality of values ​​for skipping physical downlink control channel (PDCCH) monitoring on a bandwidth part (BWP) having a first parameter set; Transmitting downlink control information DCI, the DCI indicating: a first value of the plurality of values; and PDCCH monitoring on the BWP is skipped.

9. The method of claim 8, wherein the configuration parameters are transmitted in a radio resource RRC message.

10. The method of any one of claims 8 to 9, wherein the plurality of values ​​are in units of time slots.

11. The method according to any one of claims 9 to 10, wherein: A first parameter set of a BWP of a cell is indicated through the RRC message, wherein the cell includes one or more BWPs having the BWP.

12. The method according to any one of claims 8 to 11, wherein the DCI is transmitted in a DRX active time of a discontinuous reception (DRX) configuration.

13. The method of any one of claims 8 to 12, wherein the number of time slots for skipping PDCCH monitoring is the product of the first value and a fixed value associated with the first set of parameters.

14. An apparatus comprising one or more processors and a memory storing instructions, which, when executed by the one or more processors, causes the apparatus to perform the method of any one of claims 1 to 13.

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

Images