Configuration of low power wake-up signal

Abstract

A method can include receiving, by a wireless device, one or more messages comprising a first parameter of a low-power wake-up signal (LP-WUS) that triggers physical downlink control channel (PDCCH) monitoring and further comprising a second parameter of an uplink signal. The method can further include monitoring the LP-WUS based on the first parameter. The wireless device can skip monitoring the PDCCH during a time period in which the wireless device is monitoring the LP-WUS. The method can further include transmitting the uplink signal based on the second parameter during the time period and, in response to the transmitting the uplink signal, monitoring the PDCCH for a response corresponding to the uplink signal.

Description

Cross-references to related applications

[0001] This application relates to and claims priority to U.S. Provisional Patent Application No. 63 / 553,418, filed February 14, 2025, the entire contents of which are incorporated herein by reference. Attached Figure Description

[0002] This document describes examples of several embodiments in various embodiments of the present disclosure with reference to the accompanying drawings.

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

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

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

[0006] Figure 4A It shows the way Figure 2A Example downlink data stream of the NR user plane protocol stack.

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

[0008] Figure 5 A and Figure 5 B illustrates the mapping between the logical channels, transport channels, and physical channels for both downlink and uplink.

[0009] Figure 6 This is an example diagram illustrating the RRC state transition of the UE.

[0010] Figure 7 An example configuration of NR frames in which OFDM symbols are grouped is shown.

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

[0012] Figure 9 An example of bandwidth adaptation using three configured BWPs for an NR carrier is shown.

[0013] Figure 10A Three carrier aggregation configurations with two component carriers are shown.

[0014] Figure 10BAn example of how to configure aggregated cells into one or more PUCCH groups is shown.

[0015] Figure 11A An example of the SS / PBCH block structure and location is shown.

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

[0017] Figure 12A and Figure 12B Examples of three downlink and uplink beam management procedures are shown respectively.

[0018] Figure 13A , Figure 13B and Figure 13C The four-step contention-based random access procedure, the two-step contention-free random access procedure, and another two-step random access procedure are shown respectively.

[0019] Figure 14A An example of the CORESET configuration for the bandwidth portion is shown.

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

[0021] Figure 15 An example of a wireless device communicating with a base station is shown.

[0022] Figure 16A , Figure 16B , Figure 16C and Figure 16D Example structures for uplink and downlink transmissions are shown.

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

[0024] Figure 18A An example of a DL MAC PDU is shown.

[0025] Figure 18B An example of a UL MAC PDU is shown.

[0026] Figure 19 An example of multiple LCIDs in the downlink is shown.

[0027] Figure 20 An example of multiple LCIDs in the upstream row is shown.

[0028] Figure 21A and Figure 21BAn example of SCell activation / deactivation of MAC CE format is shown.

[0029] Figure 22 An example of BWP activation / deactivation on a cell is shown.

[0030] Figure 23 Examples of various DCI formats are shown.

[0031] Figure 24A An example of a MIB message is shown.

[0032] Figure 24B An example configuration for CORESET 0 is shown.

[0033] Figure 24C An example of the configuration for search space 0 is shown.

[0034] Figure 25 An example of a SIB1 message is shown.

[0035] Figure 26 An example of a SIB1 message is shown.

[0036] Figure 27 An example of RRC configuration for BWP, PDCCH, and CORESET is shown.

[0037] Figure 28 An example of an RRC configuration for the search space is shown.

[0038] Figure 29 An example of an SSB configuration is shown.

[0039] Figure 30 An example of an SSB configuration is shown.

[0040] Figure 31 An example of an SSB configuration is shown.

[0041] Figure 32 An example of cell hibernation for power saving of wireless devices is shown.

[0042] Figure 33 An example of DRX configuration for a wireless device is shown.

[0043] Figure 34 An example of DRX operation for wireless devices is shown.

[0044] Figure 35A and Figure 35B Examples of wake-up and sleep signals for power saving in wireless devices are shown.

[0045] Figure 36A and Figure 36BAn example of search space set switching for power saving in wireless devices is shown.

[0046] Figure 37 An example of PDCCH skipping for power saving in wireless devices is shown.

[0047] Figure 38 An example of low-power wake-up signal (LP-WUS) reception is shown.

[0048] Figure 39 An example embodiment of LP-WUS configuration and reception is shown.

[0049] Figure 40 An example embodiment of LP-WUS configuration is shown.

[0050] Figure 41 An example embodiment of the LP-SS / LP-WUS configuration is shown.

[0051] Figure 42 An example embodiment of LP-WUS configuration / operation is shown. Detailed Implementation

[0052] In this disclosure, various embodiments are presented as examples of how the disclosed techniques and / or how the disclosed techniques can be practiced in various environments and scenarios. Those skilled in the art will appreciate that various changes in form and detail can be made therein without departing from its scope. In fact, after reading this specification, those skilled in the art will appreciate how alternative embodiments can be implemented. These embodiments should not be limited to any of the exemplary embodiments described. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments can be combined to create other embodiments within the scope of this disclosure. The drawings highlighting any features and advantages are presented for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, in some embodiments, any actions listed in the flowcharts can be reordered or used only optionally.

[0053] The embodiments can be configured to operate on demand. The disclosed mechanisms can be performed when certain criteria are met, such as in a wireless device, base station, radio environment, network, combination of the foregoing, and / or the like. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, combination of the foregoing, and / or the like. Various example embodiments can be applied when one or more of the stated criteria are met. Therefore, example embodiments that selectively implement the disclosed protocols can be implemented.

[0054] A base station can communicate with a mix of various wireless devices. Wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have specific capabilities depending on their category and / or capabilities. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may refer to a subset of all wireless devices in the coverage area. This disclosure may refer to, for example, multiple wireless devices having given capabilities and located in a given sector of a base station, and a given LTE or 5G version. The multiple wireless devices mentioned in this disclosure may refer to selected multiple wireless devices, and / or a subset of all wireless devices in the coverage area performing according to the disclosed method, and / or the like. Multiple base stations or multiple wireless devices may exist in the coverage area that may not comply with the disclosed method; for example, those wireless devices or base stations may perform based on older versions of LTE or 5G technology.

[0055] In this disclosure, “a” and “an”, and similar phrases, should be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” should be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” should be interpreted as “may, for example”. In other words, the term “may” indicates that the phrase immediately following the term “may” is an example of one of a variety of suitable possibilities that may or may not be employed in one or more of the various embodiments. As used herein, the terms “comprises” and “consistsof” enumerate one or more components of the described element. The term “comprises” is interchangeable with “includes” and does not exclude the inclusion of unlisted components in the described element. In contrast, “consistsof” provides a complete enumeration of one or more components of the described element. As used herein, the term “based on” should be interpreted as “at least partially based on”, rather than, for example, “based on only”. As used herein, the term “and / or” indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0056] If A and B are sets and every element of A is 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, 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 immediately following the term “based on” is an example of one of several suitable possibilities, which may or may not be employed in one or more of the various embodiments. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase immediately following the phrase “in response to” is an example of one of several suitable possibilities, which may or may not be employed in one or more of the various embodiments. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase immediately following the phrase “depends on” is an example of one of several suitable possibilities, which may or may not be employed in one or more of the various embodiments. The phrase “adopt / use” (or equivalently “at least adopt / use”) indicates that the phrase immediately following the phrase “adopt / use” is an example of one of a variety of suitable possibilities that may or may not be adopted in one or more of the various embodiments.

[0057] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, and / or the like can be "configured" within the device, whether the device is in an operational or non-operational state, to provide the device with specific characteristics. Terms such as "control message for inducing an action in the device" can mean that the control message has parameters that can be used to configure specific characteristics or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0058] In this disclosure, a parameter (or similarly 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 one example embodiment, when one or more messages include multiple parameters, this means that one of the multiple parameters is in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0059] Many of the features presented are described as optional by using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly list every permutation that can be obtained by selecting from the set of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be implemented in seven ways: having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

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

[0061] Figure 1A An example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented is shown. 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 a radio device 106.

[0062] CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs. As part of the interface functionality, CN 102 may establish an end-to-end connection between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide billing functions.

[0063] RAN 104 connects CN 102 to radio device 106 via radio communication over the air interface. As part of the radio communication, RAN 104 provides scheduling, radio resource management, and retransmission protocols. The communication direction from RAN 104 to radio device 106 over the air interface is referred to as the downlink, and the communication direction from radio device 106 to RAN 104 over the air interface is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of these duplex technologies.

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

[0065] RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass Node B (associated with UMTS and / or 3G standards), Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), Remote Radio Header (RRH), baseband processing unit coupled to one or more RRHs, repeater or relay node for extending the coverage area of ​​donor nodes, Next Generation Evolved Node B (ng-eNB), Generation Node B (gNB, associated with NR and / or 5G standards), Access Point (AP, such as associated with Wi-Fi 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).

[0066] The base stations included in RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over an air interface. For example, one or more of the base stations may include three sets of antennas to control three cells (or sectors) respectively. The size of the cells may be determined by the range in 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 device 106 over a wide geographical area to support wireless device mobility.

[0067] Besides three-sector sites, other implementations of the base station are also possible. For example, one or more of the base stations in RAN 104 can be implemented as sub-sector sites with more or fewer than three sectors. One or more of the base stations in RAN 104 can be implemented as access points, as baseband processing units coupled to several remote radio heads (RRHs), and / or as repeaters or relay nodes for extending the coverage area of ​​donor nodes. The baseband processing units coupled to RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing units can be centralized in a pool of baseband processing units or virtualized. Repeater nodes can amplify and rebroadcast radio signals received from donor nodes. Relay nodes can perform the same / similar functions as repeater nodes, but can decode radio signals received from donor nodes to remove noise before amplifying and rebroadcasting the radio signals.

[0068] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna patterns and similar high-level transmit power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas overlapping with the relatively large coverage areas provided by macrocell base stations. These small coverage areas can be provided in areas with high data traffic (or so-called "hot spots") or in areas with weak macrocell coverage. Examples of small cell base stations, in descending order of coverage area, include microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0069] The Third Generation Partnership Project (3GPP) was established in 1998 to provide solutions for similar projects. Figure 1AThe specifications for mobile communication networks 100 in this disclosure are globally standardized. To date, 3GPP has produced specifications for three generations of mobile networks: the third-generation (3G) network known as Universal Mobile Telecommunications System (UMTS), the fourth-generation (4G) network known as Long Term Evolution (LTE), and the fifth-generation (5G) network known as 5G System (5GS). Embodiments of this disclosure are described with reference to the RAN (referred to as Next Generation RAN (NG-RAN)) of the 3GPP 5G network. These embodiments may be applied to the RANs of other mobile communication networks, such as... Figure 1A RAN 104, the RAN of earlier 3G and 4G networks, and the RAN of future networks yet to be specified (such as 3GPP 6G networks). NG-RAN implements 5G radio access technology known as New Radio (NR) and can be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0070] 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, 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). These components can be used with... Figure 1A The corresponding components are implemented and operated in the same or similar ways as described.

[0071] 5G-CN 152 provides UE 156 with interfaces to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs. As part of its interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and the one or more DNs, authenticate UE 156, and provide billing functions. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0072] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, they are... Figure 1BThe UPF 158B is shown as a component AMF / UPF 158. The UPF 158B can be used as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification supporting traffic flow routing to the one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic authentication), downlink packet buffering, and downlink data notification triggering. The UPF 158B can be used as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session interconnection point to the one or more DNs, and / or a branch point supporting multi-homed PDU sessions. The UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

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

[0074] For clarity, 5G-CN 152 may include Figure 1B One or more additional network functions not shown in the diagram. 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 Open Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0075] NG-RAN 154 can connect 5G-CN 152 to UE 156 via radio communication over an air interface. 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)). gNB 160 and ng-eNB 162 may be more generally referred to as base stations. gNB 160 and ng-eNB 162 may include one or more sets of antennas for communicating with UE 156 over an air interface. For example, one or more of gNB 160 and / or one or more of ng-eNB 162 may include three sets of antennas to control three cells (or sectors) respectively. Together, the gNB 160 and ng-eNB 162 cells can provide radio coverage to UE 156 over a wide geographical area to support UE mobility.

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

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

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

[0079] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions such as initial access, mobility, and paging. Although Figure 1B Only one AMF / UPF 158 is shown, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0080] As discussed, Figure 1B The interfaces between network elements (such as Uu, Xn, and NG interfaces) can be associated with the protocol stack used by the network elements to exchange data and signaling messages. The protocol stack can include two planes: the user plane and the control plane. The user plane handles the data of interest to the user, while the control plane handles the signaling messages of interest to the network elements.

[0081] Figure 2A and Figure 2BExamples of NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220 are shown respectively. Figure 2A and Figure 2B The protocol stack shown can be used, for example, for... Figure 1B The Uu interfaces between UE 156A and gNB 160A shown in the figure are the same or similar.

[0082] Figure 2A The diagram illustrates the five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers and correspond to Layer 1 of the Open Systems Interconnection (OSI) model. Above PHY 211 and 221 are the Media Access Control (MAC) 212 and 222, Radio Link Control (RLC) 213 and 223, Packet Data Convergence Protocol (PDCP) 214 and 224, and Serving Data Application Protocol (SDAP) 215 and 225. These four protocols together constitute Layer 2 of the OSI model, or the data link layer.

[0083] Figure 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From Figure 2A and Figure 3 Starting at the top, SDAPs 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 the DN. The PDU session can have one or more QoS flows. The CN's UPF (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or bit error rate). SDAPs 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 QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can be informed of the mapping between QoS flows and data radio bearers through reflection mapping or control signaling received from gNB 220. For reflection mapping, the SDAP 225 at gNB 220 can mark downlink packets with a QoS Flow Indicator (QFI), which can be observed by the SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0084] PDCP 214 and 224 perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and perform integrity protection (ensuring that control messages originate from their intended source). PDCP 214 and 224 can perform retransmission of undelivered packets, packet delivery and reordering, and removal of packets received repeatedly, such as due to intra-gNB handover. PDCP 214 and 224 can perform packet duplication to increase the likelihood of packets being received and remove any duplicate packets at the receiver. Packet duplication can be useful for services requiring high reliability.

[0085] although Figure 3 Although not shown, PDCPs 214 and 224 can perform mapping / demapping 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). Split bearers refer to a single radio bearer (e.g., one of the radio bearers served to SDAPs 215 and 225 by PDCPs 214 and 224) being handled by the cell group in dual connectivity. PDCPs 214 and 224 can map / demapping the split radio bearers between RLC channels belonging to the cell group.

[0086] RLCs 213 and 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222. RLCs 213 and 223 support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode the RLC is operating in, the RLC can perform one or more of the specified functions. RLC configuration can be per-logic, independent of parameter sets and / or Transmission Time Interval (TTI) duration. Figure 3 As shown, RLCs 213 and 223 can provide RLC channels to PDCPs 214 and 224, respectively.

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

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

[0089] Figure 4A This illustrates an example downlink data flow through the NR user plane protocol stack. Figure 4A The diagram illustrates three IP packets (n, n+1, and m) passing through the NR user plane protocol stack to generate a two-terabyte downlink data stream at gNB 220. The uplink data stream passing through the NR user plane protocol stack can be similar to... Figure 4A The downlink data flow is depicted in the diagram.

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

[0091] Figure 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). Figure 3 It adds the corresponding header and forwards its output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., ... Figure 4A For IP packets (as shown in m), the output is forwarded to MAC 222. MAC 222 can multiplex multiple RLC PDUs and can append MAC sub-headers to RLC PDUs to form transport blocks. In NR, MAC sub-headers can be distributed throughout the entire MAC PDU, such as... Figure 4A As shown. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure reduces processing time and associated latency because the MAC PDU sub-header can be calculated before the complete MAC PDU is assembled.

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

[0093] Figure 4B Also 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 The diagram shows two MAC CEs inserted into the MAC PDU. For downlink transmissions, the MAC CE can be inserted at the beginning of the MAC PDU (e.g., ...). Figure 4B(As shown), for uplink transmissions, a MAC CE can be inserted at the end of the MAC PDU. MAC CEs can 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 for activating / deactivating PDCP copy detection, Channel State Information (CSI) reports, Sounding Reference Signal (SRS) transmissions, and previously configured components; MAC CEs related to Discontinuous Reception (DRX); Timing Advancement MAC CEs; and MAC CEs related to random access. A MAC subheader may precede the MAC CE, with a format similar to that described for the MAC SDU, and can be identified by a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0095] Figure 5 A and Figure 5 B illustrates the mapping between logical channels, transport channels, and physical channels for both downlink and uplink. Information is transmitted between the RLC, MAC, and PHY of the NR protocol stack via channels. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for 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: -- Paging Control Channel (PCCH), used to carry paging messages for paging UEs whose location is unknown to the network at the cell level; -- Broadcast Control Channel (BCCH) is used to carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIB), wherein the system information messages can be used by the UE to obtain information about how the cell is configured and how it operates within the cell; -- Common Control Channel (CCCH), used to carry control messages along with random access; -- Dedicated Control Channel (DCCH) for carrying control messages to / from a specific UE to configure the UE; and -- Dedicated Service Channel (DTCH) is used to carry user data to / from a specific UE.

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

[0097] The PHY can use physical channels to transfer information between PHY processing layers. A physical channel may have an associated set of time-frequency resources for carrying information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide this control information to lower PHY layers via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR includes, for example: -- Physical Broadcast Channel (PBCH), used to carry MIBs from the BCH; -- Physical Downlink Shared Channel (PDSCH), used to carry downlink data and signaling messages from DL-SCH, as well as paging messages from PCH; -- Physical downlink control channel (PDCCH), used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations and uplink power control commands; -- Physical Uplink Shared Channel (PUSCH), used to carry uplink data and signaling messages from UL-SCH, and in some cases uplink control information (UCI) as described below; -- Physical Uplink Control Channel (PUCCH), used to carry UCI, which may include HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and -- Physical Random Access Channel (PRACH), used for random access.

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

[0099] Figure 2B This shows an example NR control plane protocol stack. Figure 2B As shown, the NR control plane protocol stack can 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. Unlike the NR user plane protocol stack, which has SDAP 215 and 225 at the top, the NR control plane stack has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top.

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

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

[0102] Figure 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... Figure 1A The wireless device 106 depicted in the text Figure 2A and Figure 2B The UE 210 depicted in this disclosure is the same as or similar to any other wireless device described herein. Figure 6 As shown, the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

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

[0104] During RRC Idle 604, an RRC context may not be established for the UE. During RRC Idle 604, the UE may not have an RRC connection with the base station. When in RRC Idle 604, the UE may be in sleep mode for most of the time (e.g., to conserve battery power). The UE may periodically wake up (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The UE's mobility may be managed by the UE through a process known as cell reselection. The RRC state can be transitioned from RRC Idle 604 to RRC Connection 602 via Connection Establishment Procedure 612, which may involve a random access procedure discussed in more detail below.

[0105] In RRC inactivity 606, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connection 602. While in RRC inactivity 606, the UE can be in a sleep state, and the UE's mobility can be managed by the UE via cell reselection. The RRC state can be transitioned from RRC inactivity 606 to RRC connection 602 via connection recovery procedure 614, or to RRC idle 604 via connection release procedure 616, which may be the same as or similar to connection release procedure 608.

[0106] RRC status can be associated with mobility management mechanisms. In RRC Idle 604 and RRC Inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle 604 and RRC Inactive 606 is to enable the network to notify the UE of events via paging messages, without having to broadcast the paging message across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 allow the network to track the UE at the cell group level, so that paging messages can be broadcast on the individual cells of the cell group where the UE is currently camped, instead of being broadcast across the entire mobile network. The mobility management mechanisms in RRC Idle 604 and RRC Inactive 606 track the UE at the cell group level. They can do this using different grouping granularities. For example, there can be three levels of cell grouping granularity: individual cells; cells within a RAN area identified by a RAN Area Identifier (RAI); and a group of cells within a RAN area called the Tracking Area and identified by a Tracking Area Identifier (TAI).

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

[0108] RAN areas can be used to track UEs at the RAN level. For UEs in an RRC inactive 606 state, a RAN notification area can be assigned to the UE. A RAN notification area may include one or more cell identifiers, RAI lists, or TAI lists. In one example, a base station may belong to one or more RAN notification areas. In one example, a cell may belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in the RAN notification area assigned to the UE, the UE can perform a notification area update with the RAN to update the UE's RAN notification area.

[0109] The base station storing the RRC context for the UE or the UE's last serving base station may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least for a period of time while the UE is in the RAN notification area of ​​the anchor base station and / or for a period of time while the UE is in RRC inactivity 606.

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

[0111] In NR, physical signals and physical channels (about Figure 5 A and Figure 5 (Discussion B) can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data via F orthogonal subcarriers (or tones). Before transmission, the data can be mapped onto a series of complex symbols (e.g., M-ary Quadrature Amplitude Modulation (M-QAM) or M-ary Phase Shift Keying (M-PSK) symbols), called source symbols, and divided into F parallel symbol streams. These F parallel symbol streams can be considered to be in the frequency domain and used as input to an Inverse Fast Fourier Transform (IFFT) block, which transforms them to the time domain. The IFFT block can receive 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. These F time-domain samples can form a single OFDM symbol. After some processing (e.g., adding 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 an FFT block before being processed by the IFFT block. This operation produces OFDM symbols precoded by Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing of the OFDM symbols can be performed at the receiver using an FFT block to recover the data mapped to the source symbols.

[0112] Figure 7 This illustrates an example configuration in which OFDM symbols are grouped into NR frames. NR frames can be identified by a System Frame Number (SFN). An SFN can repeat over a period of 1024 frames. As shown, the duration of an NR frame can be 10 milliseconds (ms), and it can include 10 subframes with a duration of 1 ms. Subframes can be divided into time slots, and each time slot may contain, for example, 14 OFDM symbols.

[0113] The duration of a time slot can depend on the parameter set of the OFDM symbols used for that time slot. In NR, flexible parameter sets are supported to accommodate different cell deployments (e.g., from cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the millimeter-wave range). The parameter set can be defined based on the subcarrier spacing and the cyclic prefix duration. For parameter sets in NR, the subcarrier spacing can be increased by powers of 2 from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration can be decreased by powers of 2 from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following combinations of subcarrier spacing / cyclic prefix duration: 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.

[0114] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A parameter set with a higher subcarrier spacing has a shorter time slot duration and correspondingly more time slots per subframe. Figure 7 This illustrates a transmission structure that depends on the slot duration and the number of slots per subframe, based on a parameter set (for illustration purposes, the parameter set with a subcarrier spacing of 240 kHz is not shown). Figure 7 (As shown in the diagram). In NR, subframes can be used as a time reference independent of the parameter set, while time slots can be used as the unit on which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR can be decoupled from the time slot duration and can begin at any OFDM symbol, continuously transmitting any number of symbols as needed. These partial time slot transmissions can be referred to as mini-time slots or sub-time slot transmissions.

[0115] Figure 8 This illustrates an example configuration of a time slot for an NR carrier in both the time and frequency domains. The time slot comprises a Resource Element (RE) and a Resource Block (RB). An RE is the smallest physical resource in NR. (Example...) Figure 8 As shown, the RE spans one OFDM symbol in the time domain and one subcarrier in the frequency domain. Figure 8 As shown, the RB spans twelve consecutive REs in the frequency domain. The NR carrier can be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. This limitation (if used) can restrict the subcarrier spacing of the NR carrier to 50, 100, 200, and 400 MHz for 15, 30, 60, and 120 kHz respectively, where the 400 MHz bandwidth can be set based on a bandwidth limit of 400 MHz per carrier.

[0116] Figure 8 This example demonstrates the use of a single parameter set across the entire bandwidth of an NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

[0117] NR supports wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Furthermore, receiving the full carrier bandwidth may be impractical in terms of UE power consumption. In one example, to reduce power consumption and / or for other purposes, the UE may adapt its receive bandwidth based on the amount of traffic it is scheduled to receive. This is called bandwidth adaptation.

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

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

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

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

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

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

[0124] The base station can configure a BWP inactivity timer value for the UE for the PCell. The UE can start or restart the BWP inactivity timer at any appropriate time. For example, the UE can start or restart the BWP inactivity timer when it detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) when it detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI for a period of time (e.g., 1 ms or 0.5 ms), the UE can cause the BWP inactivity timer to run toward its expiration (e.g., incrementing from zero to the BWP inactivity timer value, or decrementing from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE can switch from the active downlink BWP to the default downlink BWP.

[0125] In one example, the base station can semi-statically configure one or more BWPs for the UE. The UE can 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 the timeout of the BWP inactivity timer (e.g., if the second BWP is the default BWP).

[0126] Downlink and uplink BWP handover (where BWP handover refers to switching from the currently active BWP to the currently inactive BWP) can be performed independently in paired spectrum. In unpaired spectrum, downlink and uplink BWP handover can be performed simultaneously. Configurable handover between BWPs can occur based on RRC signaling, DCI, timeout of the BWP inactivity timer, and / or the initiation of random access.

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

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

[0129] To provide higher data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit them simultaneously to / from the same UE. The carriers aggregated in a CA can be referred to as component carriers (CCs). When using CA, multiple serving cells exist for the UE, with one serving cell serving one CC. The CC can have three configurations in the frequency domain.

[0130] Figure 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 located directly adjacent to each other within the band. In the intra-band discontinuous configuration 1004, the two CCs are aggregated in the same frequency band (band A) and separated by a gap within the band. In the inter-band configuration 1006, the two CCs are located in frequency bands (band A and band B).

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

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

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

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

[0135] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10BIn the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. In this example, PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary SCells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) associated with the downlink CCs of PUCCH group 1010 (denoted as UCI 1031, UCI 1032, and UCI 1033) can be sent in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (denoted as UCI 1071, UCI 1072, and UCI 1073) can be sent in the uplink of PSCell 1061. In one example, if Figure 10B If the aggregated cells depicted are not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell is used to transmit the UCI associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

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

[0137] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In one example, the HARQ entity can operate on the serving cell. Transport blocks can be generated for each assignment / grant for each serving cell. Transport blocks, along with potential HARQ retransmissions of those transport blocks, can be mapped to the serving cell.

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

[0139] Figure 11A An example showing the structure and location of an SS / PBCH block is provided. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., such as...). Figure 11A The four SS / PBCH blocks shown are used. Bursts can be sent periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It will be understood that... Figure 11A This is one example, and these parameters (the number of SS / PBCH blocks per burst, the periodicity of the burst, and the position of the burst within a frame) can be configured, for example, based on: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the parameter set or subcarrier spacing of the cell; the network configuration (e.g., using RRC signaling); or any other suitable factor. In one example, the UE may assume the subcarrier spacing for the SS / PBCH blocks based on the monitored carrier frequency, unless the radio network configures the UE to assume a different subcarrier spacing.

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

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

[0142] The SS / PBCH block can be used by the UE to determine one or more parameters of the cell. For example, the UE can determine the physical cell identifier (PCI) of the cell based on the sequence of PSS and SSS, respectively. The UE can 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 can indicate that it has been transmitted according to a transmission mode in which the SS / PBCH block is at a known distance from the frame boundary.

[0143] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polar coding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH may include the current system frame number (SFN) of the cell and / or an indication of the SS / PBCH block timing index. These parameters facilitate time synchronization between the UE and the base station. The PBCH may include a Master Information Block (MIB) for providing one or more parameters to the UE. The MIB can be used by the UE to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI may include System Information Block Type 1 (SIB1). SIB1 may contain information required by the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH, which can be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 can be decoded using parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE can be directed to a frequency. The UE can search for SS / PBCH blocks at the frequency to which the UE is directed.

[0144] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCL) (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 blocks transmitted with different SS / PBCH block indices.

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

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

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

[0148] The base station can semi-statically configure one or more CSI-RS resource sets for the UE. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the UE that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0149] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, non-periodically, or semi-persistently. For periodic CSI reporting, the base station can configure the timing and / or periodicity of multiple CSI reports for the UE. For non-periodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate the periodic reports. The base station can use RRC signaling to configure CSI-RS resource sets and CSI reports for the UE.

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

[0151] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a pre-prefix DMRS mode. Pre-prefix DMRS can be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure a certain number (e.g., a maximum number) of pre-prefix DMRS symbols for the UE to use 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 four orthogonal downlink DMRS ports per UE. The radio network can support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, where DMRS locations, DMRS modes, and / or scrambling sequences can be the same or different. The base station can transmit downlink DMRS and the corresponding PDSCH using the same precoding matrix. The UE can use one or more downlink DMRS to perform coherent demodulation / channel estimation of the PDSCH.

[0152] In one example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of the transmission bandwidth. For instance, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices may differ based on the difference between the first and second bandwidths. The UE may assume that the same precoder matrix is ​​used across a set of PRBs. This set of PRBs may be represented as a Precoder Resource Block Group (PRG).

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

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

[0155] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS using PUSCH and / or PUCCH. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure one or more uplink DMRS configurations for the UE. At least one DMRS configuration can support a pre-signal DMRS mode. Pre-signal DMRS can be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure a certain number (e.g., a maximum number) of pre-signal DMRS symbols for PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS mode, and / or scrambling sequence can be the same or different.

[0156] A PUSCH may include one or more layers, and a UE may transmit at least one symbol of a DMRS existing on one or more of the layers of the PUSCH. In one example, a higher layer may configure up to three DMRSs for the PUSCH.

[0157] Uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may be present or absent depending on the UE's RRC configuration. The presence and / or mode of uplink PT-RS can be configured on a UE-specific basis via a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)), indicated by DCI. When configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters that include at least an 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 may assume the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS may be limited to the scheduled time / frequency duration for the UE.

[0158] SRS can be transmitted by the UE to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmissions from the UE. The base station can semi-statically configure one or more SRS resource sets for the UE. For each SRS resource set, the base station can configure one or more SRS resources for the UE. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources in the SRS resource sets of the one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodicity, aperiodicity, and / or similar behavior) can be transmitted instantaneously (e.g., simultaneously). The UE can transmit one or more SRS resources from the SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can 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 one example, at least one DCI format may be used by the UE to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In one example, when PUSCH and SRS are transmitted in the same time slot, the UE can be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0159] The base station may semi-statically configure one or more SRS configuration parameters for the UE that indicate at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); time slot, mini-time slot, and / or subframe-level periodicity; offset for periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; starting OFDM symbol of SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0160] An antenna port is defined such that the channel through which a symbol transmitted on the same antenna port is transmitted can be inferred from the channel through which another symbol transmitted on the same antenna port is transmitted. 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, and / or the like) used to transmit the second symbol on the same antenna port from the channel through which the first symbol transmitted on the antenna port is transmitted. If one or more large-scale characteristics can be inferred from the channel through which the second symbol transmitted on the second antenna port is transmitted, the first antenna port and the second antenna port can be referred to as quasi-co-located (QCL). The one or more large-scale characteristics may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0161] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on a downlink reference signal (e.g., Channel State Information Reference Signal (CSI-RS)). The UE can perform the downlink beam measurement procedure after establishing an RRC connection with the base station.

[0162] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11B The blocks shown can span resource blocks (RBs) within the cell bandwidth. The base station can 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 can be configured for CSI-RS resource configuration via higher-layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identifier, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), 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.

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

[0164] Such as Figure 11B The CSI-RS shown (e.g., CSI-RS 1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) of a configured CSI-RS resource. The base station can configure a reporting configuration for the UE, and the UE can report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In one example, the base station can determine one or more Transmission Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurement results. In one example, the base station can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can receive downlink transmissions using the receive (Rx) beam determined based on the one or more TCI states. In one 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 for the transmit (Tx) beam based on the spatial domain filter corresponding to the Rx beam. If the UE lacks beam correspondence capability, it can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE can perform the uplink beam selection procedure based on one or more Sounding Reference Signal (SRS) resources configured for it by the base station. The base station can select and indicate the uplink beam for the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0165] During beam management, the UE can evaluate (e.g., measure) the channel quality of one or more beampair links, which include transmit beams sent by the base station and receive beams received by the UE. Based on this evaluation, the UE can send a beam measurement report indicating the quality parameters of one or more beampairs, such as 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).

[0166] Figure 12A Examples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can implement the measurement of the transmit (Tx) beams of the UE at the Transport Receive Point (TRP) (or multiple TRPs), for example, to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP may include a Tx beam scan for a set of beams (shown as an ellipse rotating counterclockwise in the top row of P1 and P2 as indicated by the dashed arrow). Beamforming at the UE may include an Rx beam scan for a set of beams (shown as an ellipse rotating clockwise in the bottom row of P1 and P3 as indicated by the dashed arrow). Procedure P2 can be used to implement the measurement of the Tx beams of the UE at the TRP (shown as an ellipse rotating counterclockwise in the top row of P2 as indicated by the dashed arrow). The UE and / or base station can perform process P2 using a smaller beam set than that used in process P1, or using a narrower beam set than that used in process P1. This can be referred to as beam refinement. The UE can perform process P3 for Rx beam determination by using the same Tx beam at the base station and scanning the Rx beam at the UE.

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

[0168] The UE can initiate a beam failure recovery (BFR) procedure based on the detection of a beam failure. The UE can send a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect the beam failure based on the determination that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., an error rate higher than an error rate threshold, received signal power lower than a received signal power threshold, timer expiration, etc.).

[0169] The UE can use one or more reference signals (RS) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS) to measure the quality of the beamp-link. The quality of the beamp-link can be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station can indicate one or more DM-RS quasi-co-addressable (QCL) configurations of the RS resources and channels (e.g., control channels, shared data channels, and / or the like). The one or more DMRSs of the RS resources and channels can be QCL-configured when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) for transmissions to the UE via the RS resources are similar to or identical to the channel characteristics for transmissions to the UE via the channels.

[0170] The network (e.g., the network's gNB and / or ng-eNB) and / or the UE can initiate a random access procedure. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate the random access procedure to request connection establishment to the network. The UE can initiate the random access procedure from the RRC_CONNECTED state. The UE can initiate the random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is asynchronous). The UE can initiate the random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). The UE can initiate the random access procedure to perform a beam failure recovery request. The network can initiate a random access procedure to perform handover and / or establish time alignment for SCell addition.

[0171] Figure 13A A four-step contention-based random access procedure is illustrated. Before the procedure is initiated, the base station may send a configuration message 1310 to the UE. Figure 13A The process 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 a preamble (or random access preamble) and / or is referred to as a preamble (or random access preamble). Msg 2 1312 may include a random access response (RAR) and / or is referred to as a random access response (RAR).

[0172] Configuration message 1310 can be sent, for example, using one or more RRC messages. These one or more RRC messages can indicate one or more Random Access Channel (RACH) parameters to the UE. The one or more RACH parameters can 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 can broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages can be UE-specific (e.g., dedicated RRC messages sent to UEs in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE can determine the time-frequency resources and / or uplink transmit power for the transmission of 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 can determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0173] The one or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting Msg 11311. The one or more PRACH timings may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate the association between (a) one or more PRACH timings and (b) one or more reference signals. The one or more RACH parameters may indicate the 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 a PRACH timing and / or the number of preambles mapped to an SS / PBCH block.

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

[0175] 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). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude 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 with an RSRP higher than 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 the RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

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

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

[0178] The 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 has been received by the base station. Msg 2 1312 may include: a time alignment command, which can be used by the UE to adjust the UE's transmission timing; a scheduling grant for the transmission of Msg 3 1313; and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE can determine when to initiate the time window based on the PRACH timing used by the UE to transmit the preamble. For example, the UE can initiate the time window at one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing after the end of the preamble transmission). The one or more symbols can be determined based on a set of parameters. The PDCCH can be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE can identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI can be used depending on one or more events that initiate the random access procedure. The UE can use a Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE can determine the RA-RNTI based on: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 represents the NUL carrier, and 1 represents the SUL carrier).

[0179] The UE may transmit Msg 3 1313 in response to successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). Msg 3 1313 can be used for, for example... Figure 13A The diagram illustrates contention resolution in a contention-based random access procedure. In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide a RAR corresponding to one UE. A conflict may occur if the multiple UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier (e.g., a C-RNTI (if assigned), a TC-RNTI included in Msg 2 1312, and / or any other suitable identifier) ​​in Msg 3 1313.

[0180] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If Msg 3 1313 includes a C-RNTI, the base station will use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If Msg 3 1313 includes a TC-RNTI (e.g., if the UE is in RRC_IDLE state or 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 (e.g., is transmitted) the CCCH SDU sent in Msg 3 1313, the UE can determine that contention resolution was successful and / or the UE can determine that the random access procedure was successfully completed.

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

[0182] Figure 13B This illustrates a two-step contention-free random access process. Similar to... Figure 13A The four-step contention-based random access procedure shown in the diagram allows the base station to send configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar in some respects to configuration message 1310. Figure 13B The process shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... Figure 13A Msg 11311 and Msg 2 1312 are shown in the image. (As shown from...) Figure 13A and Figure 13B It will be understood that a contention-free random access procedure may not include messages such as Msg 3 1313 and / or Msg 4 1314.

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

[0184] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow) to monitor PDCCH for RAR. In the event of a beam failure recovery request, the base station can configure a separate time window and / or a separate PDCCH in the search space indicated by an RRC message (e.g., recoverySearchSpaceId) for the UE. The UE can monitor PDCCH transmissions addressed to the cell RNTI (C-RNTI) in said search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure has been successfully completed after transmitting Msg 1 1321 and receiving the corresponding Msg 2 1322, or in response to this. The UE can determine that the random access procedure has been successfully completed, for example, if the PDCCH transmission is addressed to the C-RNTI. The UE can determine that the random access procedure has been successfully completed, for example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU having said preamble identifier. The UE can determine this response as an indication of acknowledgment of the SI request.

[0185] Figure 13C Another two-step random access process is shown. Similar to... Figure 13A and Figure 13B In the random access procedure shown, the base station may send configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The process shown includes the transmission of two messages: Msg A1331 and Msg B1332.

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

[0187] UE can initiate [actions] against licensed spectrum and / or unlicensed spectrum. Figure 13C The two-step random access procedure is described in the text. The UE may determine whether to initiate the two-step random access procedure based on one or more factors. The one or more factors may be: the radio access technology in use (e.g., LTE, NR, etc.); whether the UE has a valid TA; cell size; the UE's RRC status; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

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

[0190] The UE and the base station can exchange control signaling. This 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 sent from the base station to the UE and / or uplink control signaling sent from the UE to the base station.

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

[0192] A base station may append one or more Cyclic Redundancy Check (CRC) parity bits to a DCI to facilitate the detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with the UE's identifier (or the identifiers of the group of UEs). Scrambling the CRC parity bits with the identifier may include a modulo-2 addition (or XOR 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).

[0193] DCIs can be used for various 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 notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or random access triggering PDCCH commands. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13AThe Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station to the UE may include Configuration Scheduling RNTI (CS-RNTI), Transmit Power Control - PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control - PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control - SRSRNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSIRNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

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

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

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

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

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

[0199] like Figure 14B As shown, the UE can determine the time-frequency resources for the CORESET based on RRC messages. The UE can determine the CCE-to-REG mapping (e.g., interleaved or non-interleaved and / or mapping parameters) for the CORESET based on the CORESET's configuration parameters. The UE can determine the number of search space sets configured on the CORESET (e.g., up to 10) based on RRC messages. The UE can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE can monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates from the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates using possible (or configured) PDCCH locations, 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. This decoding may be referred to as blind decoding. The UE can determine that the DCI is valid for the UE in response to a CRC check (e.g., the scrambled bits of the CRC parity check bit of the DCI match the RNTI value). The UE can process the information contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

[0200] The UE can send uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may send the HARQ acknowledgment 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 send the CSI to the base station. The base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The UE may send an SR indicating that uplink data is available for transmission to the base station. The UE may send UCI (e.g., HARQ acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to send the uplink control signaling via the PUCCH.

[0201] There are five PUCCH formats, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols and the number of UCI bits transmitted). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If the transmission is over 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 can use PUCCH format 0 to transmit UCI in the PUCCH resource. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can include two or fewer bits. If the transmission is over four or more symbols and the number of HARQ-ACK / SR bits is one or two, the UE can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. If the transmission is over one or two symbols and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can include more than two bits. If the transmission consists of four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can include more than two bits. If the transmission consists of four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal overlay code, the UE can use PUCCH format 4.

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

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

[0204] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 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. Figure 15 Only one wireless device 1502 and one base station 1504 are shown, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

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

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

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

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

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

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

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

[0212] Processing system 1508 and / or 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 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 may receive user input data from and / or provide user output data to the one or more peripheral devices 1516 and / or 1526. Processing system 1518 in wireless device 1502 may receive power from a power source and / or may be configured to distribute said power to other components in wireless device 1502. The power source may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. Processing system 1508 and / or processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for wireless device 1502 and base station 1504, respectively.

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

[0214] Figure 16B An example structure for modulating and up-converting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued SC-FDMA or CP-OFDM baseband signal for the antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

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

[0216] Figure 16D Another example configuration is shown for modulating and up-converting a baseband signal to a carrier frequency. The baseband signal can be a complex-valued OFDM baseband signal for the antenna port. Filtering can be applied before transmission.

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

[0218] A timer can begin running once started and continue running until it is stopped or until it expires. It can be started if it is not running, or restarted if it is running. A timer can be associated with a value (e.g., the timer can be started or restarted from a value, or it can be started from zero and expire when it reaches that value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer can be used to measure a time period / window of a process. When this specification refers to implementations and processes associated with one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways of implementing a timer can be used to measure a time period / window of the process. For example, a random access response window timer can be used to measure the time window for receiving a random access response. In one example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the process used to measure the time window can be restarted. Other example implementations for restarting the measurement of the time window can be provided.

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

[0220] In one example, the MAC SDU can be a bit string that is byte-aligned in length (e.g., aligned to a multiple of eight bits). In one example, the MAC SDU can be included in the MAC PDU starting from the first bit. The MAC CE can be a bit string that is byte-aligned in length (e.g., aligned to a multiple of eight bits). The MAC subheader can be a bit string that is byte-aligned in length (e.g., aligned to a multiple of eight bits). In one example, the MAC subheader can be placed immediately before the corresponding MAC SDU, MAC CE, or padding. The MAC entity can omit the values ​​of reserved bits in the DL MAC PDU.

[0221] In one example, a MAC PDU may include one or more MAC sub-PDUs. The MAC sub-PDUs may include: a MAC header only (including padding); a MAC header and a MAC SDU; a MAC header and a MAC CE; a MAC header and padding, or a combination thereof. The MAC SDU may be variable-sized. The MAC header may correspond to a MAC SDU, a MAC CE, or padding.

[0222] In one 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 with a one-bit length; an F field with a one-bit length; an LCID field with a multi-bit length; an L field with a multi-bit length, or a combination thereof.

[0223] Figure 17A An example of a MAC subheader with R, F, LCID, and L fields is shown. Figure 17A In the example MAC subheader, the LCID field can be six bits long, and the L field can be eight bits long. Figure 17B An example of a MAC subheader with R, F, LCID, and L fields is shown. Figure 17B In the example MAC subheader shown, the LCID field can be six bits long, and the L field can be sixteen bits long. When the MAC subheader corresponds to a fixed-size MACCE or padding, the MAC subheader may include: an R field with a length of two bits and an LCID field with a length of multiple bits. Figure 17C An example of a MAC subheader with an R field and an LCID field is shown. Figure 17C In the example MAC header shown, the LCID field can be six bits long, and the R field can be two bits long.

[0224] Figure 18AAn example of a DL MAC PDU is shown. Multiple MAC CEs, such as MAC CE 1 and 2, can be placed together. A MAC sub-PDU including a MAC CE can be placed before: a MAC sub-PDU including a MAC SDU, or a MAC sub-PDU including padding. Figure 18B An example of a UL MAC PDU is shown. Multiple MAC CEs, such as MAC CE 1 and 2, can be placed together. In one embodiment, the MAC sub-PDU including the MAC CE can be placed after all the MAC sub-PDUs including the MAC SDU. Furthermore, the MAC sub-PDU can be placed before the MAC sub-PDU including the filler.

[0225] In one example, the MAC entity of the base station can send one or more MACCEs to the MAC entity of the wireless device. Figure 19An example of multiple LCIDs that can be associated with the one or more MAC CEs is shown. The one or more MAC CEs include at least one of the following: SP ZP CSI-RS Resource Set Activation / Deactivation MAC CE, PUCCH spatial relation Activation / Deactivation MAC CE, SP SRS Activation / Deactivation MAC CE, SP CSI reporting on PUCCH Activation / Deactivation MAC CE, TCI State Indication for UE-specific PDCCH MAC CE, TCI State Indication for UE-specific PDSCH MAC CE, Aperiodic CSI Trigger StateSubselection MAC CE, SP CSI-RS / CSI-IM Resource Set Activation / Deactivation MAC CE, Radio Device Contention Resolution Identifier 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 Copy Activation / Deactivation MAC CE. In one example, a MAC CE, such as a MAC CE sent by a base station's MAC entity to a wireless device's MAC entity, may have an LCID in the 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, an LCID given by 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0226] In one example, the MAC entity of a wireless device can send one or more MACCEs to the MAC entity of a base station. Figure 20Examples of the one or more MAC CEs are shown. The one or more MAC CEs may include at least one of the following: Short Buffer Status Report (BSR) MAC CE, Beam Failure Recovery (BFR) MAC CE, Truncated BFR MAC CE, Truncated Enhanced BFR MAC CE, Long BSR MAC CE, C-RNTI MAC CE, Configured Authorization Acknowledgment MAC CE, Single-Entry PHR MAC CE, Multi-Entry PHR MAC CE, Short Truncated BSR and / or Long Truncated BSR, etc. In one example, the MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheaders corresponding to the MAC CEs. For example, the LCID given by 43 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a Truncated Enhanced BFR MAC CE.

[0227] In carrier aggregation (CA), two or more component carriers (CCs) can be aggregated. Depending on the capabilities of the radio device, the radio device can use CA technology to simultaneously receive or transmit on one or more CCs. In one embodiment, the radio device can support CA for consecutive CCs and / or for non-consecutive CCs. CCs can be organized into cells. For example, CCs can be organized into a primary cell (PCell) and one or more secondary cells (SCells). When CA is configured, the radio device can have an RRC connection with the network. During RRC connection establishment / re-establishment / handover, the cell providing NAS mobility information can be the serving cell. During the RRC connection re-establishment / handover process, the cell providing security input can be the serving cell. In one example, the serving cell can represent a PCell. In one example, depending on the capabilities of the radio device, the base station can send one or more messages to the radio device, the one or more messages including configuration parameters for one or more SCells.

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

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

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

[0231] When a wireless device receives a SCell activation / deactivation MAC CE to deactivate an activated SCell, the wireless device may deactivate the activated SCell. In one example, the wireless device may deactivate the activated SCell when the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires. In response to deactivating the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In one example, in response to deactivating the activated SCell, the wireless device may clear one or more configured downlink allocations and / or one or more configured uplink grants of Type 2 associated with the activated SCell. In one example, in response to deactivating the activated SCell, the wireless device may: suspend one or more configured uplink grants of Type 1 associated with the activated SCell; and / or flush the HARQ buffer associated with the activated SCell.

[0232] When an SCell is deactivated, the radio device may not perform the following operations: 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 an activated SCell indicates uplink grant or downlink allocation, the radio device may restart the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In one example, when at least one second PDCCH on the serving cell (e.g., PCell or SCell configured with PUCCH, i.e., PUCCH SCell) of the activated SCell indicates uplink grant or downlink allocation for the activated SCell, the radio device may restart the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In one example, when a SCell is deactivated, if an ongoing random access procedure exists on the SCell, the wireless device can abort the ongoing random access procedure on the SCell.

[0233] Figure 21AAn example of an 8-bit SCell activation / deactivation MAC CE is shown. It has a first LCID (e.g., as...). Figure 19 The first MAC PDU subheader (shown as '111010') can identify the one-eight-byte SCell activation / deactivation MAC CE. The one-eight-byte SCell activation / deactivation MAC CE can have a fixed size. The one-eight-byte SCell activation / deactivation MAC CE can include a single octet. The single octet can include a first number of C fields (e.g., seven) and a second number of R fields (e.g., one).

[0234] Figure 21B An example of a four-eight-bit SCell activation / deactivation MAC CE is shown. It has a second LCID (e.g., as...). Figure 19 The second MAC PDU subheader (shown as '111001') can identify the four octet SCell activation / deactivation MAC CE. The four octet SCell activation / deactivation MAC CE can have a fixed size. The four octet SCell activation / deactivation MAC CE can include four octets. The four octets can include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., 1).

[0235] exist Figure 21A and / or Figure 21B In this configuration, if an SCell with SCell index i is configured, the Ci field can indicate the activation / deactivation status of the SCell with SCell index i. In one example, when the Ci field is set to one, the SCell with SCell index i can be activated. In another example, when the Ci field is set to zero, the SCell with SCell index i can be deactivated. In yet another example, if no SCell with SCell index i is configured, the wireless device can ignore the Ci field. Figure 21A and Figure 21B In this context, the R field can indicate reserved bits. The R field can be set to zero.

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

[0237] In one example, the base station and / or radio device can switch BWPs between configured BWPs using a DCI or BWP inactivity timer. When a BWP inactivity timer is configured for a serving cell, the base station and / or radio device can 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 can be configured by the network. In one example, for an FDD system, when BA is configured, one UL BWP and one DL BWP can be active for each uplink carrier in an active serving cell at any given time. In one example, for a TDD system, one DL / UL BWP pair can be active in an active serving cell at any given time. Operating on the one ULBWP and the one DL BWP (or the one DL / UL pair) can improve the battery consumption of the radio device. BWPs other than the one active UL BWP and the one active DL BWP that the radio device can operate on can 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.

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

[0239] Figure 22 An example of BWP handover on a cell (e.g., PCell or SCell) is illustrated. In one example, a radio device may receive at least one RRC message from a base station, the at least one RRC message including cell parameters and one or more BWPs associated with the cell. The RRC message may include: an RRC connection reconfiguration message (e.g., RRCReconfiguration); an RRC connection re-establishment message (e.g., RRCReestablishment); and / or an RRC connection establishment message (e.g., RRCSetup). Of 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 radio device may receive a command to activate the cell (e.g., an RRC message, MAC CE, or DCI) in the nth time slot. If the cell is a PCell, the radio device may not receive a command to activate the cell; for example, the radio device may activate the PCell after receiving an RRC message including the configuration parameters of the PCell. The wireless device can begin monitoring the PDCCH on BWP 1 in response to activating the cell.

[0240] In one example, the wireless device may initiate (or restart) a BWP inactivity timer (e.g., bwp-InactivityTimer) in the m-th time slot in response to receiving a DCI indicating DL allocation on BWP 1. 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 s-th time slot. The wireless device may deactivate the cell and / or stop the BWP inactivity timer when the sCellDeactivationTimer expires (e.g., if the cell is an SCell). In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer on the PCell.

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

[0242] In one example, on an inactive BWP of each active serving cell configured with a BWP, the MAC entity may: not send on UL-SCH; not send on RACH; not monitor PDCCH; not send PUCCH; not send SRS and 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.

[0243] In one example, if the MAC entity does not receive a PDCCH for a BWP handover to the serving cell during a random access procedure associated with the serving cell, the radio device can perform a BWP handover to the BWP indicated by the PDCCH. In one example, if a bandwidth portion indicator field is configured in DCI format 1_1, the bandwidth portion indicator field value can indicate the active DL BWP for DL ​​reception from the configured DL BWP set. In one example, if a bandwidth portion indicator field is configured in DCI format 0_1, the bandwidth portion indicator field value can indicate the active UL BWP for UL transmission from the configured UL BWP set.

[0244] In one example, for the primary cell, the radio device may provide a default DL BWP from the configured DL BWPs via the higher-layer parameter Default-DL-BWP. If the radio device does not provide a default DL BWP via the higher-layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In one example, the radio device may provide a timer value for the primary cell via the higher-layer parameter bwp-InactivityTimer. If configured, during the interval, if the radio device may not detect DCI format 1_1 for paired spectrum operation, or if the radio device may not detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation, the radio device may increment the timer every 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 (if it is running).

[0245] In one example, if the radio device is configured with a higher-layer parameter Default-DL-BWP indicating the default DLBWP in the configured DL BWP for the secondary cell and the radio device is configured with a higher-layer parameter bwp-InactivityTimer indicating a timer value, then the radio device's procedure on the secondary cell can be the same as that on the primary cell, using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0246] In one example, if a radio device configures a first active DL BWP on a secondary cell or carrier by the higher-layer parameter Active-BWP-DL-SCell and a first active UL BWP by the higher-layer parameter Active-BWP-UL-SCell, then the radio device may use the DL BWP and the UL BWP indicated on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0247] In one example, the PDCCH candidate set for monitoring by the wireless device is defined based on the PDCCH search space set. The search space set includes either the CSS set or the USS set. The wireless device monitors PDCCH candidates in one or more of the following search space sets: Type 0-PDCCH CSS set configured by pdcch-ConfigSIB1 in the MIB, or searchSpaceSIB1 in PDCCH-ConfigCommon, or searchSpaceZero in PDCCH-ConfigCommon, for DCI format CRC scrambled by SI-RNTI on the primary cell of the MCG; Type 0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon, for DCI format CRC scrambled by SI-RNTI on the primary cell of the MCG; Type 1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon, for DCI format CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell; and Type 2-PDCCH configured by pagingSearchSpace in PDCCH-ConfigCommon. The CSS set is used for DCI format where CRC is scrambled by P-RNTI on the primary cell of the MCG; the Type3-PDCCH CSS set configured by SearchSpace with searchSpaceType = common in PDCCH-Config is used for DCI format where CRC is scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI or PS-RNTI and only for the primary cell by C-RNTI, MCS-C-RNTI or CS-RNTI; and the USS set configured by SearchSpace with searchSpaceType = ue-Specific in PDCCH-Config is used for DCI format where CRC is scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI or SL-L-CS-RNTI.

[0248] In one example, the wireless device is based on one or more PDCCH configuration parameters (e.g., based on those described later). Figure 27(Example Implementation) Determines the PDCCH monitoring timing on the active DL BWP, wherein one or more PDCCH configuration parameters include: PDCCH monitoring periodicity, PDCCH monitoring offset, and PDCCH monitoring mode within the time slot. For a search space set (SSs), the wireless device determines that the PDCCH monitoring timing exists in a space with a numbered... In the time slot, the time slot is located in the slot with the number In the frame, if . This refers to the number of time slots in a frame when the parameter set µ is configured. It is the slot offset indicated in the PDCCH configuration parameters (e.g., based on...). Figure 27 (Example embodiments). It is the PDCCH monitoring periodicity indicated in the PDCCH configuration parameters (e.g., based on...). Figure 27 (Example embodiment). The wireless device monitors PDCCH candidates for the search space set continuously. A series of consecutive time slots, from time slot And does not monitor the search space set The PDCCH candidates, in the next Within a consecutive time slot. In one example, at CCE aggregation level. The USS is defined by a set of PDCCH candidates that target the CCE aggregation level. . In one example, the wireless device targets a search space set. The associated CORESET Determine the aggregation level The CCE index, which corresponds to the PDCCH candidate The search space set in the time slot In the context of the active DL BWP for the serving cell, the serving cell corresponds to the carrier indication field value. , determined as ,in, For any CSS; For USS, , for , for , for ,as well as ; ; This refers to the number of CCEs, numbered from 0 to... In CORESET ; This is the carrier indication field value if the radio device is configured with a carrier indication field via CrossCarrierSchedulingConfig for the serving cell on which it monitors the PDCCH; otherwise, including for any CSS, ; ,in It is the number of PDCCH candidates that a wireless device is configured to monitor, for aggregation level. search space set For the serving cell, the serving cell corresponds to The service area; for any CSS, For USS, It is the maximum value of the following items: Retrieve all configured ones Value, for CCE aggregation level search space set ; and used for The RNTI value is C-RNTI.

[0249] In one example, a wireless device can monitor a set of PDCCH candidates based on configuration parameters of a search space set including multiple search spaces (SSs). The wireless device can monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. CORESETs can be based on [the parameters described later]. Figure 26 The example implementation is used for configuration. Monitoring may include decoding one or more PDCCH candidates in the group of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates using possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the public SS, and / or the number of PDCCH candidates in the UE-specific SS), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. Possible DCI formats may be based on Figure 23 Example implementation.

[0250] Figure 23Examples of DCI formats that can be used by a base station to send control information to a radio device or by a radio device for PDCCH monitoring are shown. Different DCI formats may include different DCI fields and / or different DCI payload sizes. Different DCI formats may have different signaling purposes. In one example, DCI format 0_0 can be used to schedule PUSCHs in a cell. DCI format 0_1 ​​can be used to schedule one or more PUSCHs in a cell, or to indicate CG-DFI (Configuration Grant-Downlink Feedback Information) for configuration-granted PUSCHs, etc. The DCI formats that a radio device can monitor in the SS can be configured.

[0251] Figure 24A Example of configuration parameters for the Primary Information Block (MIB) of a cell (e.g., PCell). In one example, the radio device may receive the MIB via the PBCH based on receiving the Primary Synchronization Signal (PSS) and / or the Secondary Synchronization Signal (SSS). The configuration parameters of the MIB may include six bits of the system frame number (SFN), subcarrier spacing indication (subCarrierSpacingCommon), frequency domain offset (ssb-SubcarrierOffset) between the SSB and the entire resource block grid in terms of the number of subcarriers, cellBarred indication indicating whether the cell is blocked, DMRS position indication (dmrs-TypeA-Position) indicating the DMRS position, PDCCH CORESET and SS parameters (pdcch-ConfigSIB1) (including common CORESET, common search space and necessary PDCCH parameters), etc.

[0252] In one example, pdcch-ConfigSIB1 may include a first parameter (e.g., controlResourceSetZero) that indicates the public ControlResourceSet (CORESET) (e.g., CORESET#0) with ID#0 for the initial BWP of the cell. controlResourceSetZero can be an integer between 0 and 15. Each integer between 0 and 15 can identify a configuration for CORESET#0.

[0253] Figure 24B This shows an example of the configuration for CORESET#0. For example... Figure 24BAs shown, based on the integer value of controlResourceSetZero, the wireless device can determine the SSB and CORESET#0 multiplexing mode, the number of RBs for CORESET#0, the number of symbols for CORESET#0, and the RB offset for CORESET#0.

[0254] In one example, pdcch-ConfigSIB1 may include a second parameter (e.g., searchSpaceZero) that indicates the public search space (e.g., SS#0) with ID#0 for the cell's initial BWP. searchSpaceZero can be an integer between 0 and 15. Each integer between 0 and 15 can identify a configuration for SS#0.

[0255] Figure 24C This shows an example of the configuration for SS#0. For example... Figure 24C As shown, based on the integer value of searchSpaceZero, the wireless device can determine one or more parameters (e.g., O, M) for slot determination for PDCCH monitoring, the first symbol index for PDCCH monitoring, and / or the number of search spaces per slot.

[0256] In one example, based on the received MIB, the wireless device can monitor the PDCCH via SS#0 of CORESET#0 to receive the DCI of Scheduling System Information Block 1 (SIB1). The SIB1 message can be based on... Figure 25 This is implemented using an example embodiment. The wireless device can receive a DCI scrambled with a CRC using a dedicated System Information Radio Network Temporary Identifier (SI-RNTI) for receiving the SIB1.

[0257] Figure 25 and Figure 26 An example of RRC configuration parameters for a System Information Block (SIB) is shown. An SIB (e.g., SIB1) can be broadcast to all radio devices. The SIB may contain scheduling configurations related to assessing whether a radio device is allowed to access the cell, paging configuration information, and / or other system information. The SIB may contain radio resource configuration information common to all radio devices and prohibition information applied to unified access control. In one example, the base station may send one or more SIB messages to radio devices (or multiple radio devices).

[0258] like Figure 25As shown, the parameters of the one or more SIB information may include: one or more parameters for cell selection related to the serving cell (e.g., cellSelectionInfo), one or more configuration parameters of the serving cell (e.g., in the ServingCellConfigCommonSIB IE), and one or more other parameters. The ServingCellConfigCommonSIB IE may include at least one of the following: common downlink parameters of the serving cell (e.g., in the DownlinkConfigCommonSIB IE), common uplink parameters of the serving cell (e.g., in the UplinkConfigCommonSIB IE), and other parameters.

[0259] like Figure 26 As shown, the SIB1 message may include scheduling information for other SIBs (e.g., SIB2, SIB3, SIB4, ...), for example, via an SI-SchedulingInfo IE. The SI-SchedulingInfo IE may include an SI-RequestConfig IE for the normal uplink carrier (NUL) of the cell and an SI-RequestConfigSUL IE for the supplementary uplink carrier of the cell. The SI-RequestConfig IE or SI-RequestConfigSUL IE may indicate the RACH configuration (e.g., a rach-OccasionsSI IE) for the corresponding SI request.

[0260] In one example, the DownlinkConfigCommonSIB IE may include parameters of the initial downlink BWP (initialDownlinkBWP IE) for the serving cell (e.g., SpCell). The parameters of the initial downlink BWP may be included in the BWP-DownlinkCommon IE (e.g., ...). Figure 27 (As shown). The BWP-DownlinkCommon IE can be used to configure common parameters of the serving cell's downlink BWP. The base station can configure locationAndBandwidth such that the initial downlink BWP includes the entire CORESET#0 of the serving cell in the frequency domain. The radio device can apply locationAndBandwidth upon receiving this field (e.g., to determine the frequency location of the signal described in relation to this locationAndBandwidth), but it retains CORESET#0 until after receiving RRCSetup / RRCResume / RRCReestablishment.

[0261] In one example, the DownlinkConfigCommonSIB IE may include parameters for paging channel configuration. These parameters may include a paging cycle value (T, via the defaultPagingCycle IE), a parameter indicating the total number (N) of paging frames (PF) in the paging DRX cycle and the paging frame offset (PF_offset) (nAndPagingFrameOffset IE), the total number of paging opportunities (PO) per PF (Ns), and a first PDCCH monitoring opportunity indication parameter (firstPDCCH-MonitoringOccasionofPO IE) indicating the first PDCCH monitoring opportunity for each PO of the PF. The radio device can monitor the PDCCH to receive paging messages based on the parameters configured in the PCCH configuration.

[0262] In one example, the parameter first-PDCCH-MonitoringOccasionOfPO can be signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO can be signaled in the corresponding BWP configuration.

[0263] Figure 27 This illustrates an example of RRC configuration parameters (e.g., BWP-DownlinkCommon IE) in the downlink BWP of the serving cell. The base station may send one or more configuration parameters of the serving cell's downlink BWP (e.g., initial downlink BWP) to radio devices (or multiple radio devices). Figure 27As shown, the one or more configuration parameters of the downlink BWP may include: one or more general BWP parameters for the downlink BWP, one or more cell-specific parameters for the PDCCH of the downlink BWP (e.g., in pdcch-ConfigCommon IE), one or more cell-specific parameters for the PDSCH of the BWP (e.g., in pdsch-ConfigCommon IE), and one or more other parameters. pdcch-ConfigCommon IE may include parameters for COESET #0 (e.g., controlResourceSetZero), which can be used in any public or UE-specific search space. The value of controlResourceSetZero can be interpreted as the corresponding bit in MIB pdcch-ConfigSIB1. pdcch-ConfigCommon IE may include parameters for an additional common control resource set (e.g., in commonControlResourceSet), which can be configured and used in any public or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for that ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is included in the bandwidth of CORESET#0. The pdcch-ConfigCommon IE can include parameters for a list of additional common search spaces (e.g., in commonSearchSpaceList). The search space parameters can be based on what will be described later. Figure 28 This can be implemented using an example. The pdcch-ConfigCommon IE can indicate the search space for paging (e.g., pagingSearchSpace), the search space for random access procedures (e.g., ra-SearchSpace), the search space for SIB1 messages (e.g., searchSpaceSIB1), the common search space #0 (e.g., searchSpaceZero), and one or more other search spaces from the list of search spaces.

[0264] like Figure 27 As shown, a control resource set (CORESET) can be associated with a CORESET index (e.g., ControlResourceSetId). A CORESET can be based on the above information regarding... Figure 14A and / or Figure 14BThe example implementation described is used. A CORESET index with a value of 0 can identify a common CORESET (controlResourceSetZero) configured in the MIB and in ServingCellConfigCommon, and may not be used in the ControlResourceSet IE. A CORESET index with other values ​​can identify a CORESET configured by dedicated signaling or in SIB1. The controlResourceSetId is unique among the BWPs of the serving cell. A CORESET can be associated with a coresetPoolIndex, which indicates the index of the CORESET pool used for the CORESET. A CORESET can be associated with a time duration parameter (e.g., duration), which indicates the continuous time duration of the CORESET in terms of the number of symbols. In one example, as Figure 27 As shown, the configuration parameters of CORESET may include at least one of the following: frequency resource indicators (e.g., frequencyDomainResources), CCE-REG mapping type indicators (e.g., cce-REG-MappingType), multiple TCI states, indicators indicating whether a TCI exists in the DCI, etc.

[0265] Figure 28 An example of a search space (e.g., SearchSpace IE) configuration is shown. In one example, one or more search space configuration parameters may include at least one of the following: searchspace ID, control resource set ID, monitoring slot periodicity and offset parameters, search space duration, monitoring symbols within slot, number of candidates for aggregation level (nrofCandidates), and / or SS type indicating a public SS type or a UE-specific SS type (searchSpaceType). The monitoring slot periodicity and offset parameters may indicate the slot (e.g., within a radio frame) and slot offset (e.g., relative to the start of a radio frame) used for PDCCH monitoring. The monitoring symbols indication may indicate on which symbols(s) of the slot(s) the radio device can monitor the PDCCH on the SS. The control resource set ID may identify the control resource set on which the SS can reside.

[0266] In one example, a radio device in RRC_IDLE or RRC_INACTIVE state can periodically monitor paging opportunities (POs) to receive paging messages for the radio device. Before monitoring a PO, the radio device in RRC_IDLE or RRC_INACTIVE state can wake up before each PO to prepare and / or activate all components in preparation for data reception (warm-up). The interval between the wake-up and the PO can be long enough to accommodate all processing requirements. After the warm-up, the radio device can perform timing acquisition and coarse synchronization from the SSB, frequency and time tracking, time and frequency offset compensation, and / or local oscillator calibration. Thereafter, the radio device can monitor the PDCCH for paging DCI at one or more PDCCH monitoring opportunities based on the configuration parameters of the PCCH configuration configured in SIB1. The configuration parameters of the PCCH configuration can be based on the above regarding... Figure 25 The example embodiments described are used to implement this.

[0267] In one example, a base station can periodically send one or more SSBs to a wireless device or multiple wireless devices. The wireless device (in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state) can use the one or more SSBs to synchronize time and frequency with the base station's cell. SSBs include the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Physical Broadcast Channel (PBCH), and PBCH DM-RS, and can be based on the above regarding... Figure 11A The example embodiments described are sent. For example... Figure 11A As shown, an SSB can occupy a number (e.g., 4) of OFDM symbols. A base station can transmit one or more SSBs in an SSB burst, for example, to achieve beam scanning for the PSS / SSS and PBCH. An SSB burst comprises a group of SSBs, each of which may be transmitted on a different beam. The SSBs in an SSB burst can be transmitted in a time-division multiplexing manner. In one example, an SSB burst can always be confined to a 5ms window and located in the first or second half of a 10ms radio frame. In this specification, an SSB burst can be equivalently referred to as the transmission window (e.g., 5ms) for transmitting said group of SSBs.

[0268] In an example, the base station may indicate the transmission period of SSB via an RRC message (for example, ssb-PeriodicityServingCell in ServingCellConfigCommonSIB of a SIB1 message, or ServingCellConfigCommon of the serving cell). The candidate values of the transmission period may be in the range of {5ms, 10ms, 20ms, 40ms, 80ms, 160ms}. The maximum number (Lmax) of candidate SSBs within an SSB burst depends on the carrier frequency / frequency band of the cell. In an example, if fc<=3GHz, then Lmax=4, where fc is the carrier frequency of the cell. If 3GHz<fc<=6GHz, then Lmax=8. If fc>=6GHz, then Lmax=64, and so on.

[0269] In an example, the starting OFDM symbol index of a candidate SSB (occupying 4 OFDM symbols) within an SSB burst (5ms) may depend on the subcarrier spacing (SCS) and the carrier frequency band of the cell.

[0270] Figure 29 shows an example of determining the starting OFDM symbol index.

[0271] As shown in Figure 29 , for a cell configured with 15 kHz and a carrier frequency fc<3GHz (Lmax=4), the starting OFDM symbol indices of SSBs in the SSB burst are 2, 8, 16 and 22. The OFDM symbols in a half-frame are indexed, where the first symbol of the first slot is indexed as 0. For a cell configured with 15 kHz and a carrier frequency 3GHz<fc<6GHz (Lmax=8), the starting OFDM symbol indices of SSBs in the SSB burst are 2, 8, 16, 22, 30, 36, 44 and 50, and so on. In an example, when the base station transmits SSBs without using beamforming, the base station may transmit only one SSB by using the first SSB starting position.

[0272] Figure 30 shows an example of SSB transmission performed by the base station for a cell. In the Figure 30 example, the SCS of the cell is 15 kHz, and the cell is configured with 3GHz<fc<=6GHz. Based on the Figure 30 exemplary embodiment, the maximum number of candidate SSBs in the SSB burst is 8 (Lmax=8). As shown in Figure 30As shown, SSB#1 begins with symbol #2 of the 70th symbol in 5 ms; SSB#2 begins with symbol #8; SSB#3 begins with symbol #16; SSB#4 begins with symbol #22; SSB#5 begins with symbol #30; SSB#6 begins with symbol #36; SSB#7 begins with symbol #44; and SSB#8 begins with symbol #50. The SSB burst occurs in the first half of a 10 ms radio frame (rather than...). Figure 30 (The latter half shown) is sent.

[0273] In one example, an SSB burst (also for each SSB within the SSB burst) can be sent at a certain period. Figure 30 In the example, the default period for an SSB burst is 20 ms, for example, before the radio device receives the SIB1 message for initial cell access. A base station with a 20 ms SSB (or SSB burst) transmission period may transmit an SSB burst in the first 5 ms of each 20 ms period. The base station does not transmit an SSB burst in the remaining 15 ms of each 20 ms period.

[0274] In one example, the base station may send an RRC message (e.g., SIB1 and / or ServingCellConfigCommon IE) indicating cell-specific configuration parameters for SSB transmission in the serving cell (e.g., PCell or SCell). The cell-specific configuration parameters may include the value of the SSB burst's transmission period (ssb-PeriodicityServingCell) and the position of a certain number of SSBs (e.g., active SSBs) among multiple candidate SSBs included in the SSB burst. The multiple candidate SSBs may be based on the above information. Figure 29 The example embodiments described are implemented as follows. The cell-specific configuration parameters may include SSB location indicators in an SSB burst (e.g., ssb-PositionsInBurst). The location indicators may include a first bitmap (e.g., groupPresence) and a second bitmap (e.g., inOneGroup) indicating the locations of a certain number of SSBs included in the SSB burst.

[0275] In one example, the base station may transmit a Master Information Block (MIB) on the PBCH to indicate configuration parameters (for CORESET#0) for the radio device to monitor the PDCCH to receive SIB1 messages. The base station may transmit the MIB message with a transmission period of 80 milliseconds (ms). The same MIB message may be repeated within these 80 ms (depending on the SSB period). The content of the MIB message is identical within the 80 ms period. The same MIB is transmitted on all SSBs within the SS burst. In one example, the PBCH may indicate that no associated SIB1 exists. In this case, the radio device may be directed to another frequency from which to search for an SSB associated with SIB1, and the radio device may assume that there is no frequency range from which an SSB associated with SIB1 exists. The indicated frequency range may be limited to consecutive spectrum allocations of the same operator in which the SSB is detected.

[0276] In one example, the base station can send SIB1 messages at a period of 160 ms. The base station can send the same SIB1 message within 160 ms with a variable transmission repetition period. The default transmission repetition period for SIB1 is 20 ms. The base station can determine the actual transmission repetition period based on the network implementation. In one example, for SSB and CORESET multiplexing mode 1, the SIB1 repetition transmission period is 20 ms. For SSB and CORESET multiplexing modes 2 / 3, the SIB1 transmission repetition period is the same as the SSB period. SIB1 may include information about the availability and scheduling of other SIBs (e.g., SIB-to-SI message mapping, period, SI window size), an indication of whether one or more SIBs are provided only on demand, and configuration parameters required for the radio device to perform an SI request in this case.

[0277] In one example, a base station may transmit SSBs on each of a plurality of serving cells (e.g., PCell or SCell) configured for a radio device. The base station may transmit SSBs on some of these serving cells and may not transmit SSBs on the others. A serving cell without an SSB can be called an SSB-free serving cell. A serving cell in which the base station always transmits SSBs can be called an SSB-always-on serving cell. Besides always-on and SSB-free, a base station may transmit SSBs on a serving cell based on an instruction from the radio device or another base station, and / or triggered by the base station itself (e.g., by transmitting SCell activation / deactivation of MAC CE). When there is no instruction from the radio device or another base station, or no trigger from the base station, the base station may stop transmitting SSBs. SSBs transmitted / stopped upon request can be called on-demand SSBs.

[0278] Figure 31 Examples of various SSB transmissions are shown.

[0279] In one example, the base station can be a serving cell (e.g., PCell or SCell). Figure 31 In Cell 1), the SSB configuration is always enabled. In this case, the base station continuously sends SSBs periodically (e.g., ssb-PeriodicityServingCell) based on the SSB configuration parameters. SSBs can be sent as follows: a certain number of SSBs (e.g., indicated by ssb-PositionsInBurst) are included in an SSB burst, and the SSB burst is sent periodically according to the stated period, for example, according to... Figure 30 Examples. In one example, always-on SSB can be forcibly configured on the PCell and optionally configured on the SCell. Radio devices can achieve time and / or frequency synchronization (and / or beam alignment) with the serving cell based on periodically transmitted SSBs. Always transmitting SSBs may increase the power consumption of the base station.

[0280] like Figure 31 As shown, the base station can be configured to serve a cell (e.g., SCell) that does not perform SSB transmission. Figure 31 In the case of Cell2, for example, to reduce the power consumption of the serving cell. The wireless device may reference another serving cell (e.g., PCell or PSCell, or SCell). Figure 31 Cell 1) is used to obtain time and / or frequency synchronization with the serving cell. The PCell / PSCell / SCell used as a reference for the SSB of the serving cell (e.g., an SSB reference cell) can be configured by the serving cell's RRC message. The SSB reference cell can be deployed in-band (within the same frequency band) with the serving cell, or it can be deployed inter-band (in different frequency bands) with the serving cell. The SSB-free configuration of the serving cell can be limited to the following: the SSB reference cell is always present in carrier aggregation (CA) or dual connectivity (DC) deployments, and / or the time / frequency synchronization error between the SSB reference cell and the serving cell is within a threshold, and / or they are deployed in the same frequency range (FR). Allowing the serving cell to not perform SSB transmissions may reduce the power consumption of the base station.

[0281] like Figure 31 As shown, a base station can configure on-demand SSB transmission for a serving cell (e.g., SCell, such as Cell 3), for example, to provide SSBs for time / frequency synchronization and / or, in parallel, reduce the power consumption of the serving cell, especially when the serving cell does not have an SSB reference cell (e.g., due to single-cell deployment, or because the time / frequency synchronization error between the SSB reference cell and the serving cell is greater than a threshold). There are several ways to provide on-demand SSBs for the serving cell.

[0282] As the first way to provide on-demand SSBs to the service community (such as...) Figure 31 As shown, a base station can trigger the transmission of an on-demand SSB based on receiving an uplink wake-up signal (WUS) from a radio device. The WUS can be based on existing technologies (e.g., preambles, SRS, and / or SR, etc.) or a new signal specifically designed for on-demand SSB requests. The radio device can trigger the transmission of the WUS based on its traffic load and / or power level. In one example, the radio device can trigger the transmission of the WUS based on channel measurements of the serving cell's discovery reference signal (DRS) (if configured). The DRS can be a simplified SSB with only a PSS but no SSS and PBCH, a simplified SSB with only an SSS but no PSS and PBCH, a CSI-RS, a location RS, or a newly defined RS specifically for on-demand SSB requests. Before triggering an on-demand SSB for the serving cell, the base station can (optionally) transmit a DRS to allow the radio device to perform channel measurements (which can be used by the radio device to determine whether to trigger the transmission of the WUS). Upon receiving a WUS (e.g., a wake-up indication), the base station can begin transmitting the on-demand SSB. When a WUS (e.g., an indication to enter sleep mode) is received, or when no WUS indicating wake-up is received at the WUS time, the base station can stop (or skip) transmitting on-demand SSBs. Allowing radio devices to request on-demand SSB transmissions (or request to stop on-demand transmissions) enables the base station to stop SSB transmissions for power saving / energy conservation when there are no active radio devices in the serving cell.

[0283] As a second way to provide on-demand SSBs to the service community (such as...) Figure 31 As shown), the base station can trigger the transmission of on-demand SSBs by activating the SCell. The base station can activate / deactivate the MAC CE (e.g., based on...) by sending the SCell. Figure 21A and / or Figure 21B (Example) Activating the SCell for a radio device. Before the SCell is activated, the base station may skip (or may stop / avoid) transmitting on-demand SSBs. After the SCell is activated, the base station may begin transmitting on-demand SSBs. The base station may determine when / whether to activate the SCell (along with on-demand SSB transmission) based on the radio device's traffic load / requests and / or requests from another base station via the backhaul link. In one example, the aforementioned DRS may be optionally transmitted by the base station. The radio device may transmit channel measurements of the serving cell based on the DRS to help the base station determine when / whether to activate the serving cell.

[0284] Figure 32This illustrates an example of transitioning between sleep and non-sleep states on an SCell. In one example, the base station may send one or more RRC messages to the radio device, including configuration parameters for the SCell, where the SCell comprises multiple BWPs. Among the multiple BWPs, the first BWP (e.g., Figure 32 BWP 3 in the configuration can be configured as a non-sleeping BWP, and / or a second BWP (e.g., Figure 32 BWP 1) in the configuration can be configured to hibernate. In one example, the default BWP (e.g.) Figure 32 The BWP (Best-Package 0) can be configured among the plurality of BWPs. In one example, a non-sleep BWP can be a BWP that the wireless device can activate in response to transitioning a SCell from a sleep state to a non-sleep state. In one example, a sleep BWP can be a BWP that the wireless device can switch to in response to transitioning a SCell from a non-sleep state to a sleep state. In one example, the configuration parameters can indicate one or more search spaces and / or CORESETs configured on a non-sleep BWP. The configuration parameters can indicate that no search space or CORESET is configured on a sleep BWP. The configuration parameters can indicate CSI reporting configuration parameters for a sleep BWP.

[0285] In one example, the default BWP may be different from the sleeping BWP. The configuration parameters may indicate one or more search spaces or one or more CORESETs configured on the default BWP. When a BWP inactivity timer expires or a DCI indicating a switch to the default BWP is received, the wireless device may switch to the default BWP as the active BWP. When the default BWP is active, the wireless device may perform at least one of the following: monitor the PDCCH on the default BWP of the SCell, receive the PDSCH on the default BWP of the SCell, transmit the PUSCH on the default BWP of the SCell, transmit the SRS on the default BWP of the SCell, and / or transmit a CSI report (e.g., periodic, aperiodic, and / or semi-persistent) for the default BWP of the SCell. In one example, when a sleep / non-sleep indication indicating the sleep state of the SCell is received, the wireless device may switch to the sleeping BWP as the active BWP of the SCell. In response to switching to a dormant BWP, the radio device may perform at least one of the following: avoid monitoring PDCCH on the dormant BWP of the SCell (or for the SCell if the SCell is scheduled across carriers by another cell), avoid receiving PDSCH on the dormant BWP of the SCell, avoid transmitting PUSCH on the dormant BWP of the SCell, avoid transmitting SRS on the dormant BWP of the SCell, and / or transmit CSI reports (e.g., periodic, aperiodic, and / or semi-persistent) for the dormant BWP of the SCell.

[0286] like Figure 32 As shown, a base station can send a DCI to a radio device via PDCCH resources. The DCI includes a sleep / non-sleep indication indicating whether the SCell is in a sleep or non-sleep state. In response to the sleep / non-sleep indication indicating a sleep state for the SCell, the radio device can: transition the SCell to a sleep state if the SCell was in a non-sleep state before receiving the DCI, or maintain the SCell in a sleep state if it was in a sleep state before receiving the DCI. Transitioning the SCell to a sleep state may include switching to a sleep BWP for the SCell (e.g., configured by the base station). In response to the sleep / non-sleep indication indicating a non-sleep state for the SCell, the radio device can: transition the SCell to a non-sleep state if the SCell was in a sleep state before receiving the DCI, or maintain the SCell in a non-sleep state if it was in a sleep state before receiving the DCI. Transitioning the SCell to a non-sleep state may include switching to a non-sleep BWP for the SCell (e.g., configured by the base station).

[0287] like Figure 32 As shown, in response to transitioning the SCell from a sleep state to a non-sleep state, the wireless device can switch to a non-sleep BWP configured by the base station (e.g., ...). Figure 32 The BWP shown (3) serves as the active BWP for the SCell. Based on switching to a non-sleep BWP as the active BWP for the SCell, the radio device may perform at least one of the following: monitor the PDCCH on the active BWP of the SCell (or monitor the PDCCH for the SCell when the SCell is configured to be scheduled across carriers by another cell), receive the PDSCH on the active BWP of the SCell, and / or transmit PUCCH / PUSCH / RACH / SRS on the active BWP (e.g., if the active BWP is an uplink BWP).

[0288] like Figure 32 As shown, in response to transitioning the SCell from a non-sleep state to a sleep state, the wireless device can switch to a sleep BWP configured by the base station (e.g., ...). Figure 32The SCell BWP shown is 1). Based on the switch to the SCell's dormant BWP, the radio device may perform at least one of the following: avoid monitoring PDCCH on the SCell's dormant BWP (or avoid monitoring PDCCH for the SCell when the SCell is configured to be scheduled across carriers by another cell), avoid receiving PDSCH on the SCell's dormant BWP, avoid transmitting PUCCH / PUSCH / RACH / SRS on the dormant BWP (e.g., if the dormant BWP is an uplink BWP), and / or transmit a CSI report for the SCell's dormant BWP based on the CSI report configuration parameters configured on the SCell's dormant BWP.

[0289] In one example embodiment, DRX operation can be used by a wireless device to improve its battery life. With DRX configured, the wireless device can discontinuously monitor downlink control channels, such as PDCCH or EPDCCH. The base station can, for example, use RRC configuration to configure DRX operation with a set of DRX parameters. These parameters can be selected based on application type, allowing the wireless device to reduce power and resource consumption. In response to DRX being configured / activated, the wireless device can receive data packets with extended delays because the wireless device may be in a DRX sleep / off state when data arrives, and the base station may wait until the wireless device transitions to a DRX-enabled state.

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

[0291] Figure 33An example of DRX operation is shown. A base station can send an RRC message including one or more DRX parameters for a DRX period. The one or more parameters may include a first parameter and / or a second parameter. The first parameter may indicate a first time / window value for the DRX active state of the DRX period (e.g., DRX on duration). The second parameter may indicate a second time for the DRX sleep state of the DRX period (e.g., DRX off duration). The one or more parameters may also include the duration of the DRX period. During the DRX active state, the radio device can monitor the PDCCH to detect one or more DCIs on the serving cell. During the DRX sleep state, the radio device can stop monitoring the PDCCH on the serving cell. When multiple cells are active, the radio device can monitor all PDCCHs on (or for) all cells during the DRX active state. During the DRX off duration, the radio device can stop monitoring all PDCCHs on (or for) all cells. The radio device can repeat the DRX operation based on one or more DRX parameters.

[0292] In one example embodiment, DRX can be beneficial to the base station. In one example, without DRX configured, the radio device may frequently (e.g., based on configuration) transmit periodic CSI and / or SRS. With DRX, the radio device may not transmit periodic CSI and / or SRS during DRX off periods. The base station can then allocate these resources to other UEs to improve resource utilization efficiency.

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

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

[0295] In one example embodiment, in response to a configured DRX period, the activation time of the DRX operation may include the time during which at least one timer is running. The at least one timer may include drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or mac-ContentionResolutionTimer. During the activation time of the DRX operation, the wireless device may monitor the PDCCH using an RNTI affected by the DRX operation. The RNTI may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and / or AI-RNTI.

[0296] In one example embodiment, `drx-Inactivity-Timer` can specify the duration for which the wireless device can remain active after successfully decoding a PDCCH indicating a new transmission (UL, DL, or SL). This timer can be restarted upon receiving a PDCCH for a new transmission (UL, DL, or SL). The wireless device can transition to DRX mode (e.g., using a short or long DRX cycle) in response to the expiration of this timer. In one example, `drx-ShortCycle` can be the first type of DRX cycle that the wireless device must follow when entering DRX mode (e.g., if configured). In one example, `DRX-Config IE` indicates the length of the short cycle. `drx-ShortCycleTimer` can be represented as a multiple of `shortDRX-Cycle`. This timer can indicate the initial number of short DRX cycles followed before entering a long DRX cycle. `drx-onDurationTimer` can specify the duration for which a DRX cycle begins (e.g., DRX on). `drx-onDurationTimer` can indicate the duration for which the device must remain active before entering sleep mode (DRX off). The drx-HARQ-RTT-TimerDL can specify the minimum duration from the receipt of a new transmission until the wireless device can anticipate a retransmission of the same packet. This timer can be fixed and may not be configurable by RRC. The drx-RetransmissionTimerDL can indicate the maximum duration for which the wireless device can monitor the PDCCH when it anticipates a retransmission from the base station.

[0297] In response to a configured DRX period, the activation time can include the time during which a scheduling request is sent on the PUCCH and is in a suspended state. In one example, in response to a configured DRX period, the activation time can include the time during which an uplink grant for a suspended HARQ retransmission may occur and data exists in the corresponding HARQ buffer for a synchronized HARQ procedure. In response to a configured DRX period, the activation time can include the time during which a PDCCH indicating a new transmission addressing a MAC entity's C-RNTI has not been received after successfully receiving a random access response for a preamble not selected for the MAC entity.

[0298] In one example embodiment, the DL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) may expire in a subframe, and the data for the corresponding HARQ procedure may not be successfully decoded. The MAC entity can start drx-RetransmissionTimerDL for the corresponding HARQ procedure. The UL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL) may expire in a subframe. The MAC entity can start drx-RetransmissionTimerUL for the corresponding HARQ procedure.

[0299] In one example, the wireless device can receive either the DRX command MAC CE or the long DRX command MAC CE (e.g., based on the above regarding...). Figure 19 (Example embodiments described). The MAC entity of the wireless device can stop the drx-onDurationTimer and / or stop the drx-InactivityTimer in response to receiving a DRX command MAC CE and / or a long DRX command MAC CE. In one example, if the drx-InactivityTimer expires and if a short DRX cycle is configured, the MAC entity can start or restart the drx-ShortCycleTimer and use the short DRX cycle. Otherwise, the MAC entity can use the long DRX cycle.

[0300] In one example, the drx-ShortCycleTimer can expire within a subframe. The MAC entity can use a long DRX period. In one example, a MAC control element can receive long DRX commands. The MAC entity can stop the drx-ShortCycleTimer and can use a long DRX period.

[0301] In one example embodiment, if a short DRX period is used and [(SFN 10) + Subframe Number] Modulo (drx-ShortCycle) = (drxStartOffset) Modulo (drx-ShortCycle) allows the wireless device to start drx-onDurationTimer after drx-SlotOffset from the start of the subframe, where drx-SlotOffset can be a value indicating the delay before starting drx-onDurationTimer (configured in the DRX configuration parameters). In one example, if a long DRX period is used and [(SFN 10) + Subframe Number] Modulo (drx-longCycle) = drxStartOffset. The wireless device can start drx-onDurationTimer after drx-SlotOffset from the start of the subframe, where drx-SlotOffset can be a value indicating the delay before starting drx-onDurationTimer (configured in DRX configuration parameters).

[0302] Figure 34 An example of DRX operation is shown. The base station can send an RRC message that includes configuration parameters for DRX operation. The configuration parameters may include a first timer value for a DRX inactivity timer (e.g., drx-InactivityTimer), a second timer value for a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL), and a third timer value for a HARQ retransmission timer (e.g., drx-RetransmissionTimerDL or drx-RetransmissionTimerUL).

[0303] like Figure 34 As shown, the base station can send a DCI (e.g., the first DCI) including downlink allocation for the TB to the radio device via the PDCCH. In response to receiving the DCI, the radio device can start a drx-InactivityTimer. While the drx-InactivityTimer is running, the radio device can monitor the PDCCH. The radio device can receive the TB based on the received DCI. The radio device can send a NACK to the base station if the TB is not successfully decoded. In the first symbol after the NACK is sent, the radio device can start a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL). The radio device can stop the drx-RetransmissionTimerDL for the HARQ procedure corresponding to the TB. Figure 34 (Not shown in the image). While the HARQ RTT timer is running, the wireless device can stop monitoring the PDCCH for one or more RNTIs affected by DRX operation. The one or more RNTIs may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and / or AI-RNTI.

[0304] like Figure 34As shown, when the HARQ RTT timer expires, the wireless device can monitor the PDCCH and start the HARQ retransmission timer (e.g., drx-RetransmissionTimerDL). While the HARQ retransmission timer is running, the wireless device can receive a second DCI (e.g., scheduled TB retransmission) during PDCCH monitoring. Figure 34 (The second DCI in the PDCCH). If the second DCI is not received before the HARQ retransmission timer expires, the wireless device may stop monitoring the PDCCH.

[0305] Figure 35A An example of a power-saving mechanism based on wake-up indication is shown. The base station can send one or more messages to the wireless device including parameters such as the wake-up duration (e.g., power-saving duration, or power-saving channel (PSCH) timing). The wake-up duration can be located a certain number of time slots (or symbols) prior to the DRX on-time of the DRX cycle. The DRX cycle can be based on the above regarding... Figure 33The example embodiments described are implemented. The number of time slots (or symbols), or the interval between the wake-up duration and the DRX enable duration, can be configured or predefined as a fixed value in the one or more RRC messages. The interval can be used for at least one of the following: synchronization with the base station; measurement of reference signals; and / or retuning RF parameters. The interval can be determined based on the capabilities of the wireless device and / or the base station. In one example, the parameters of the wake-up duration can be predefined without RRC configuration. In one example, the wake-up mechanism can be based on a wake-up indication via the PSCH. The parameters of the wake-up duration can include at least one of the following: the PSCH channel format (e.g., parameter set, DCI format, PDCCH format); the period of the PSCH; the control resource set and / or search space of the PSCH. When the parameters of the wake-up duration are configured, the wireless device can monitor the wake-up signal or PSCH during the wake-up duration. When the parameters of the PSCH timing are configured, the wireless device can monitor the PSCH during the PSCH timing to detect a wake-up indication. In response to receiving a wake-up signal / channel (or a wake-up indication via PSCH), the wireless device can wake up to monitor the PDCCH during the DRX active time of the next DRX cycle, according to the DRX configuration. In one example, in response to receiving a wake-up indication via PSCH, the wireless device can monitor the PDCCH during the DRX active time (e.g., when the drx-onDurationTimer is running). If no PDCCH is received during the DRX active time, the wireless device can return to sleep. The wireless device can remain asleep during the DRX off duration of the DRX cycle. In one example, if the wireless device does not receive a wake-up signal / channel (or a wake-up indication via PSCH) during the wake-up duration (or PSCH timing), the wireless device can skip monitoring the PDCCH during the DRX active time. In one example, if the wireless device receives an indication to skip PDCCH monitoring during the wake-up duration (or PSCH timing), the wireless device can skip monitoring the PDCCH during the DRX active time.

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

[0307] In one example Figure 33 , Figure 35A and / or Figure 35B One or more embodiments can be extended or combined to further improve the power consumption of the wireless device and / or the signaling overhead of the base station. The base station can send a power-saving indication in the DCI via the PSCH, indicating whether the wireless device should wake up for the next DRX on-duration or skip the next DRX on-duration. The wireless device can receive the DCI via the PSCH. In response to the power-saving indication instructing the wireless device to wake up for the next DRX on-duration, the wireless device can wake up for the next DRX on-duration. The wireless device monitors the PDCCH during the next DRX on-duration in response to the wake-up. In response to the power-saving indication instructing the wireless device to skip (or enter sleep) for the next DRX on-duration, the wireless device enters sleep or skips for the next DRX on-duration. In response to the power-saving indication instructing the wireless device to enter sleep for the next DRX on-duration, the wireless device skips monitoring the PDCCH during the next DRX on-duration.

[0308] In one example, the wireless device can perform power-saving operations based on search space switching.

[0309] Figure 36AAn example of DCI format 2_0 is shown, including one or more Search Space Set Group (or SSSG) handover indications (or Search Space Set Group handover flags). In one example, DCI format 2_0 may include one or more slot format indicators (e.g., slot format indicator 1, slot format indicator 2, ..., slot format indicator N), one or more available RB set indicators, one or more COT duration indicators, and one or more SSS group handover flags. In one example, each of the one or more SSS group handover flags may correspond to a corresponding cell group in a plurality of cell groups. Each of the plurality of cell groups may include one or more cells. The SSS group handover flag corresponding to a cell group among the one or more SSS group handover flags, when set to a first value, may indicate a handover from a first SSS group to a second SSS group for each cell in the cell group. The SSS group handover flag, when set to a second value, may indicate a handover from a second SSS group to a first SSS group for each cell in the cell group. The radio device may be based on Figure 36B The example implementation performs an SSS group switch.

[0310] Figure 36B This shows a DCI-based (e.g., DCI format 2_0, or) Figure 23 Examples of SSS group switching (other DCI formats described in the text). In one example, a wireless device can be switched by searchSpaceGroupIdList (e.g., based on...). Figure 28 (Example implementation) provides a group index for search space sets (e.g., Type3-PDCCH CSS sets and / or USS sets) for use in PDCCH monitoring on the serving cell.

[0311] In one example, the wireless device may not be provided with a searchSpaceGroupIdList for the search space set. If the search space set is not configured with a searchSpaceGroupIdList, Figure 36B The implementation may not be applicable to PDCCH monitoring in this search space. Based on not applying... Figure 36B In one embodiment, the wireless device can monitor the search space set on the BWP without switching out of the search space set to perform PDCCH monitoring.

[0312] In one example, if the wireless device is provided with a cellGroupsForSwitchList indicating one or more serving cell groups (e.g., based on...), Figure 27 (Example embodiments shown in the figure) Figure 36B This implementation can be applied to all serving cells within each group. If the radio device is not provided with cellGroupsForSwitchList, Figure 36B Implementations may be applicable only to serving cells that provide searchSpaceGroupIdList to wireless devices.

[0313] In one example, if the wireless device is provided with searchSpaceGroupIdList, the wireless device can reset PDCCH monitoring based on the search space set with group index 0 (if provided by searchSpaceGroupIdList).

[0314] In one example, the wireless device could be powered by searchSpaceSwitchDelay (e.g., ...). Figure 27 (As shown) provides a certain number of symbols Based on the wireless device's processing capabilities (e.g., wireless device processing capability 1, wireless device processing capability 2, etc.) and SCS configuration Wireless device processing capacity for SCS configuration 1 This may apply unless the wireless device indicates support for wireless device processing capability 2. In one example, = 25 for wireless device capability 1 and =0, =25 for wireless device capability 1 and =1, =25 for wireless device capability 1 and =2, =10 is used for wireless device capability 2 and =0, =12 is used for wireless device capability 2 and =1, and =22 is used for wireless device capability 2 and =2, etc.

[0315] In one example, you can use `searchSpaceSwitchTimer` (in time slots, for example, ...) Figure 27 (As shown) The wireless device is provided with a timer value for the serving cell provided by the searchSpaceGroupIdList, or, if provided, a timer value for a set of serving cells provided by cellGroupsForSwitchList. The wireless device may decrement the timer value by one after each slot based on a reference SCS configuration that serves as a minimum SCS configuration. In the serving cell or among all configured DL BWPs in the group of serving cells. The radio device may maintain the reference SCS configuration during the timer decrement process.

[0316] In one example, `searchSpaceSwitchTimer` can be defined as a time-slot-based value used to monitor the PDCCH in the active DL BWP of the serving cell before moving to the default search space group (e.g., search space group 0). For a 15 kHz SCS, the effective timer value can be one of {1, ..., 20}. For a 30 kHz SCS, the effective timer value can be one of {1, ..., 40}. For a 60 kHz SCS, the effective timer value can be one of {1, ..., 80}. In one example, the base station can configure the same timer value for all serving cells in the same `CellGroupForSwitch`.

[0317] like Figure 36B As shown, the wireless device can 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 cell's BWP. The location of the search space set group handover flag field for the serving cell in DCI format 2_0 can be provided to the wireless device via the SearchSpaceSwitchTrigger. The SearchSpaceSwitchTrigger can be based on... Figure 28 The example embodiment is used for configuration. The wireless device can receive DCI (e.g., Figure 36B The first DCI in DCI format 2_0 is included. The DCI can indicate an SSS group handover for the cell, for example, when the value of the SSS group handover flag field in DCI format 2_0 is 1. In response to receiving the DCI, the radio device can begin monitoring PDCCH according to the second SSS group (e.g., the second SSS group or the SSS with group index 1) and stop monitoring PDCCH on the first SSS group (or the SSS with group index 0 for the serving cell). The radio device can begin monitoring PDCCH on the second SSS group (e.g., the second SSS group or the SSS with group index 1) and stop monitoring PDCCH on the first SSS group in a first time slot, the first time slot being at least... Following the symbol, which is after the last symbol of the PDCCH having the DCI format 2_0. Based on the received DCI, the wireless device can set the timer value of the search space switching timer to the value provided by searchSpaceSwitchTimer.

[0318] In one example, the radio device can monitor the PDCCH on a second SSS group (e.g., the second SSS group or the SSS with group index 1) based on the configuration of the SSS group of the cell's BWP. The location of the search space set group handover flag field for the serving cell in DCI format 2_0 can be provided to the radio device via the SearchSpaceSwitchTrigger. The radio device can receive the DCI. The DCI can indicate an SSS group handover for the cell; for example, when the value of the search space set group handover flag field in DCI format 2_0 is 0, the radio device can 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 index 1 for the serving cell. The radio device can 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 index 1 in a first time slot, at least in... The symbol follows the last symbol of the PDCCH having the DCI format 2_0.

[0319] In one example, if the radio device monitors the PDCCH for the serving cell according to a first SSS group (e.g., a search space set with group index 1), the radio device may begin monitoring the PDCCH for the serving cell according to a second SSS group (e.g., a search space set with group index 0), and stop monitoring the PDCCH for the serving cell according to the first SSS group at the beginning of a first time slot, the first time slot being at least... The symbol follows either the time slot after which the timer expires, or the last symbol after the remaining channel occupancy duration for the serving cell as indicated by DCI format 2_0.

[0320] In one example, the radio 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, which is configured to monitor the Group-Common-PDCCH for the Slot Format Indicator (SFI). In response to the absence of the SearchSpaceSwitchTrigger, the DCI format 2_0 may not include the SSS group handover flag field. When the SearchSpaceSwitchTrigger is not provided, if the radio device detects the DCI format by monitoring the PDCCH according to a first SSS group (e.g., a search space set with group index 0), the radio device may begin monitoring the PDCCH for the serving cell according to a second SSS group (e.g., a search space set with group index 1) and stop monitoring the PDCCH according to the first SSS group. The radio device may begin monitoring the PDCCH according to the second SSS group and stop monitoring the PDCCH according to the first SSS group in a first time slot, at least in... The symbol follows the last symbol of the PDCCH with the DCI format. If the wireless device detects the DCI format by monitoring the PDCCH in any search space set, the wireless device can set (or restart) the timer value to the value provided by searchSpaceSwitchTimer.

[0321] In one 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 for the serving cell according to a first SSS group (e.g., a search space set with group index 1), the wireless device may begin monitoring the PDCCH for the serving cell according to a second SSS group (e.g., a search space set with group index 0), and stop monitoring the PDCCH for the serving cell according to the first SSS group at the beginning of a first time slot, the first time slot being at least... After a symbol, which is after the time slot where the timer expires, or, if the radio 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 for the serving cell indicated by DCI format 2_0.

[0322] In one example, the wireless device can determine the time slot and the symbols within the time slot based on a minimum SCS configuration for a serving cell provided with a searchSpaceGroupIdList, or, if provided with a cellGroupsForSwitchList, for a set of serving cells, start or stop monitoring the PDCCH according to the search space set, wherein the minimum SCS configuration is In the serving cell or in all configured DL BWPs in the group of serving cells, and, if any, in the serving cell in which the radio device receives the PDCCH and detects the corresponding DCI format 2_0 that triggers the start or stop of PDCCH monitoring according to the search space set.

[0323] In one example, the wireless device can implement a PDCCH skipping mechanism for power-saving operation.

[0324] Figure 37 An example of power-saving operation based on PDCCH skipping is shown.

[0325] In one example, the base station may send one or more RRC messages to the radio device, the RRC messages including configuration parameters of the PDCCH for the cell's BWP (e.g., based on the above regarding...). Figure 27 and / or Figure 28 (Example embodiment described). Based on the configuration parameters of the PDCCH, the wireless device can monitor the PDCCH on the BWP. The BWP can be an active downlink BWP. The wireless device can, based on the above description... Figure 22 The example embodiments described are used to activate the BWP.

[0326] like Figure 37 As shown, the wireless device can receive a first DCI (e.g., the first DCI) indicating that the PDCCH should be skipped within a time window. The time value of the time window can be indicated by the first DCI and / or configured by the one or more RRC messages. In response to receiving the first DCI, the wireless device can stop monitoring the PDCCH on the BWP. Stopping monitoring the PDCCH on the BWP can include stopping monitoring the PDCCH on one or more SSS groups configured on the BWP (e.g., including a Type 3 CSS set and / or a USS set). The wireless device maintains the active state of the BWP. The first DCI may not indicate a switchover of the active BWP. In one example, the base station may not send the PDCCH to the wireless device during the time window (or when a timer associated with the time window is running).

[0327] like Figure 37As shown, when the time window expires / ends, the wireless device can resume monitoring the PDCCH on the BWP. Based on the resumption of PDCCH monitoring, the wireless device can receive a second DCI (e.g., a second DCI) scheduled via the PDSCH for the TB. The wireless device can receive the TB via the PDSCH scheduled by the second DCI. In one example, in response to the expiration of the time window, the base station can send the second DCI to the wireless device.

[0328] In one example Figure 32 , Figure 33 , Figure 34 , Figure 35A , Figure 35B , Figure 36A , Figure 36B and / or Figure 37 One or more embodiments may be extended or combined to further improve the power consumption of the wireless device and / or the signaling overhead of the base station.

[0329] During the 3GPP Rel. 15 / 16 / 17 standardization work, various power-saving technologies for wireless devices were specified, such as those based on... Figure 32 SCell hibernation, based on Figure 33 and / or Figure 34 DRX, such as Figure 35A and / or Figure 35B The DRX based on the wake-up signal (where the wake-up signal is transmitted as a DCI with a CRC scrambled by PS-RNTI, such as DCP) is shown. Figure 36A and / or Figure 36B Power saving based on SSSG switching, and PDCCH skipping based on DCI (e.g., Figure 37 ), paging monitoring based on advance paging indication (PEI), etc.

[0330] Low-power receiver technology has recently been developed to further reduce the power consumption of wireless devices communicating with base stations on one or more cells. In one example, in addition to the various power-saving techniques specified in the 3GPP Rel. 15 / 16 / 17 standard, the wireless device may be equipped with a low-power receiver (LR) and a main receiver (MR).

[0331] The MR of the wireless device can be used to receive NR SSB / PDCCH / PDSCH, RRM, RLM, BFR, CSI measurements, etc., as does a wireless device implemented according to the 3GPP Rel.15 / 16 / 17 standard, while the LR can be used by the wireless device to monitor / receive low-power wake-up signals (LP-WUS) and / or low-power synchronization signals (LP-SS). The LP-WUS / LP-SS can be simpler than existing NR downlink signals (e.g., SSB, CSI_RS, PDCCH / PDSCH / DRMR, etc.). The LP-WUS / LP-SS can be transmitted using On-Off Keying (OOK), Amplitude Shift Keying (ASK), and / or Frequency Shift Keying (FSK) modulation. The LR can consume less power than the MR, for example, when the LR uses incoherent envelope-based signal detection to receive LP-WUS and / or LP-SS, while the MR uses coherent detection to receive BPSK / QPSK / QAM modulated NR channels / signals. The receiver used by the LR and based on the incoherent envelope detection of the LP-WUS can be referred to as a low-power wake-up receiver (LP-WUR).

[0332] The wireless device may not power on the MR for time / frequency synchronization, system information reception and / or paging message reception before receiving the LP-WUS by using the LR, for example, in the RRC_IDLE state.

[0333] The wireless device may perform PDCCH monitoring without using the MR before receiving the LP-WUS using the LR (unless the wireless device is periodically woken up to perform RRM / RLM / BFD / CSI measurements / reports), for example, in the RRC_CONNECTED state.

[0334] When the paging rate for the wireless device equipped with LR and MR is low, the wireless device can power on the LR and turn off the MR most of the time, thereby saving the power consumption of the wireless device in the RRC_IDLE state.

[0335] Similarly, when data for the wireless device equipped with LR and MR becomes sparse, the wireless device can use the LR to monitor LP-WUS most of the time and skip the PDCCH monitoring performed by the MR, thereby saving power consumption of the wireless device in the RRC_CONNECTED state.

[0336] Figure 38 An example of power-saving techniques using LR and MR wireless devices is shown. Figure 38In the example, the wireless device may be equipped with an LR and a MR. The LR and the MR may be two physically different receivers, for example, having separate RF modules and / or baseband processors. The LR and the MR may also be two virtually different receivers, for example, sharing some RF modules and / or baseband processors.

[0337] exist Figure 38 In the example, the radio device may be configured (e.g., via broadcast messages (SIB1 / SIB2 / ...) or unicast messages (e.g., UE-specific RRC messages)) with one or more configuration parameters for LP-WUS (and / or LP-SS). The one or more configuration parameters may include the transmission period of the LP-WUS (e.g., LP-WUS periodicity), the value of the period duration (during which the radio device monitors the LP-WUS), frequency resource indication (e.g., the number of RBs), and / or the number of symbols for the WUS.

[0338] exist Figure 38 In the example, the wireless device can periodically monitor the LP-WUS using the LR (e.g., attempt to detect the presence of the LP-WUS based on one or more configuration parameters). The base station may not transmit the LP-WUS, for example, when there is no paging / data transmission for the wireless device. Before receiving the LP-WUS via the LR, the wireless device may not power on the MR, or keep the MR in a sleep mode (e.g., hypersleep, deep sleep, light sleep, microsleep, etc.), or may not monitor the PDCCH of one or more cells using the MR (e.g., except for using the MR to perform RRM / RLM / BFR / CSI measurements on SSB / CSI-RS).

[0339] exist Figure 38In the example, in response to receiving the LP-WUS using the LR, the wireless device can transition the MR from a sleep state to an active state (e.g., for time / frequency synchronization, paging / PEI / DCP / PDCCH monitoring, etc.). The wireless device may spend some time (e.g., transition gap, rise time, etc.) for the MR to transition from a sleep state to an active state. The length of the transition gap may depend on the wireless device's ability to wake the MR, and / or may depend on which sleep state the MR was in before receiving the LP-WUS. A typical rise time for the MR to transition from a deep sleep state to an active state may be 400 milliseconds or 800 milliseconds. A typical rise time for the MR to transition from a deep sleep state to an active state may be tens of milliseconds. A typical rise time for the MR to transition from a light sleep / microsleep state to an active state may be several milliseconds, and so on.

[0340] In one example, after the transition interval, the MR can begin performing time / frequency synchronization based on SSB / TRS / CSI-RS, for example, if the radio device is in RRC_IDLE or RRC_INACTIVE state. After performing the time / frequency synchronization, if the PEI is configured by the base station, the radio device can monitor the PEI to determine whether to monitor the PO to receive paging messages; or, if the PEI is not configured by the base station, the radio device can monitor the PO to receive paging messages.

[0341] In one example, after the transition interval, the MR can begin monitoring the cell's PDCCH, for example, if the DCP is not configured by the base station. If the DCP is configured by the base station, the MR of the radio device can monitor the DCP and determine whether to monitor the PDCCH based on whether the DCP indicates wake-up or sleep (or whether the DCP indicates the start of the DRX duration timer configured by the radio device, for example, according to...). Figure 35A and / or Figure 35B Examples.

[0342] based on Figure 38 For example, compared to wireless devices implementing 3GPP Rel.15 / 16 / 17 power-saving technologies, wireless devices equipped with LP-WUR can use LR (for detecting LP-WUS) to determine whether to wake up MR for normal NR signal / channel reception / monitoring, thereby reducing power consumption for PDCCH monitoring and / or paging monitoring.

[0343] In one example, the LP-WUS monitoring can be combined with DCP-based power-saving operation to further reduce the power consumption of the wireless device.

[0344] Figure 39 An example of a combination of LP-WUS and DCP for power saving in wireless devices is shown. Figure 39 In the example, the wireless device can be configured with LP-WUS configuration parameters (e.g., based on...). Figure 38 Examples), DCP and DRX configurations (e.g., based on) Figure 35A and / or Figure 35B (For example, where the wake-up indication is carried by the DCP).

[0345] exist Figure 39 In the example, the wireless device can be based on Figure 38 The example uses the LR to monitor the LP-WUS. Before receiving the LP-WUS, the wireless device does not monitor the PDCCH and the DCP, and keeps the MR in a (deep or light) sleep state.

[0346] exist Figure 39 In the example, at T1, the wireless device receives the LP-WUS. The wireless device may raise the MR to monitor the DCP. In response to receiving a wake-up indication in the DCP, the wireless device may start a DRX duration timer for the first DRX cycle at T2 according to the DRX configuration. The time gap between T1 and T2 may be long enough for the MR to be raised to monitor the DCP and for the DRX duration timer to be started. The wireless device may monitor the PDCCH while the DRX duration timer is running, for example, based on... Figure 35A and / or Figure 35B Examples.

[0347] exist Figure 39 In the example, at T3, when the DRX duration timer expires, the wireless device can stop monitoring the PDCCH.

[0348] exist Figure 39 In the example, at T4, the wireless device does not receive the LP-WUS while monitoring the LP-WUS according to the configuration parameters of the LP-WUS. In response to not receiving the LP-WUS, the wireless device may skip monitoring the DCP and may not start the DRX duration timer for the second DRX cycle. The wireless device may skip monitoring the PDCCH during the second DRX cycle.

[0349] In one example, when the wireless device stops / skips monitoring the PDCCH due to the lack of detection of LP-WUS, the wireless device still performs one or more RRM / RLM / BFD / CSI measurements / reports on one or more RSs configured for the one or more measurements / reports.

[0350] In existing technologies, LP-SS / LP-WUS can be configured for each BWP of a cell, or for the initial / default BWP of the cell. In this case, the radio device can apply power-saving operations to the BWP or cell based on the LP-SS / LP-WUS configured per BWP or per cell. In other existing technologies, LP-SS / LP-WUS can be configured for a cell group. In this case, the radio device can apply power-saving operations to all cells in the cell group based on receiving the LP-SS / LP-WUS. The power-saving operation based on LP-SS / LP-WUS can be based on... Figure 38 and / or Figure 39 This can be implemented using an example.

[0351] However, the radio device may not support all different types of LP-SS / LP-WUS configurations (e.g., LP-SS / LP-WUS configuration per BWP, LP-SS / LP-WUS configuration per cell, LP-SS / LP-WUS configuration per cell group, etc.). For example, to support LP-SS / LP-WUS configuration per BWP, the radio device may be required to install multiple LP-WURs, each LP-WUR for processing / detecting LP-SS / LP-WUS for a specific BWP. Similarly, to support LP-SS / LP-WUS configuration per cell, the radio device may be required to install multiple LP-WURs, each LP-WUR for processing / detecting LP-SS / LP-WUS for a specific cell. Different types of LP-SS / LP-WUS configurations may require the radio device to have different levels of implementation complexity.

[0352] In the prior art, the base station may not be aware of which LP-SS / LP-WUS configuration(s) the wireless device is supporting. This prior art may lead to incorrect LP-SS / LP-WUS configurations for the wireless device. For example, if the wireless device only supports LP-SS / LP-WUS configurations configured by MAC entity, the base station, unaware of this information, may incorrectly configure LP-SS / LP-WUS configurations configured by BWP that the wireless device may not be able to process / detect. The prior art may increase the power consumption of the wireless device and / or reduce system throughput.

[0353] In existing technologies, the frequency location of LP-SS / LP-WUS can be configured by reusing the SSB configuration method. However, LP-SS / LP-WUS differs from the SSB configuration of the serving cell, where the SSB is deployed (to facilitate time / frequency synchronization by the radio device) to follow the Global Synchronization Channel Number (GSCN) grid (1 MHz granularity) for Standalone (SA) mode, or to the frequency location indicated by NR-ARFCN values ​​(5 / 15 / 60 kHz granularity) for Non-Standalone (NSA) mode. Configuring LP-SS / LP-WUS in the same way as the SSB configuration may increase the power consumption of the radio device for detecting LP-SS / LP-WUS. In one example, the radio device can blindly detect the presence of an SSB within the cell's frequency bandwidth with a 1 MHz granularity (based on the GSCN grid). However, it may not be necessary for the radio device to blindly detect the presence of LP-SS / LP-WUS with a 1 MHz granularity within the cell's frequency bandwidth. Existing technologies may increase the power consumption of the radio device for processing / detecting LP-SS / LP-WUS.

[0354] In existing technologies, when a radio device is configured (or activated) with LP-WUS monitoring, it can stop monitoring the PDCCH. While monitoring LP-WUS, the radio device can skip PDCCH monitoring on one or more serving cells. The radio device can resume PDCCH monitoring when it detects LP-WUS. In some existing technologies, the radio device can resume PDCCH monitoring when it has (urgent) uplink data available for PUSCH transmission. However, for the radio device, how to handle on-demand SSB / SIB1 requests (e.g., whether to allow the radio device to send uplink WUS requesting on-demand SSB / SIB1, or whether to allow the radio device to monitor PDCCH after uplink WUS transmission) when it is not monitoring PDCCH and is monitoring LP-WUS may be unclear. It could be triggered by another cell or by the serving cell itself on which the radio device is not monitoring PDCCH (e.g., based on...). Figure 31 Example: On-demand SSB / SIB1 request (which can be uplink WUS). Uplink WUS can be different from PUSCH / PUCCH transmission. Existing technology may increase the latency of on-demand SSB / SIB1 transmission when configuring / activating LP-WUS for a wireless device.

[0355] One or more example embodiments include a first message from a base station requesting radio access capabilities of the wireless device. The wireless device sends a second message to the base station regarding radio access capabilities for power-saving operation, wherein the second message indicates that the wireless device supports at least one of the following: an LP-WUS configuration applicable to a BWP (referred to herein as per-BWP LP-WUS configuration), an LP-WUS configuration applicable to a cell (referred to herein as per-cell LP-WUS configuration), an LP-WUS configuration applicable to a DRX cell group (referred to herein as per-cell group LP-WUS configuration), and / or an LP-WUS configuration applicable to a MAC entity (referred to herein as per-MAC entity LP-WUS configuration). Example embodiments may align the base station and the wireless device in terms of the LP-SS / LP-WUS configurations supported by the wireless device, and accordingly allow the base station to configure appropriate LP-SS / LP-WUS configurations to reduce the power consumption of the wireless device.

[0356] One or more example embodiments include a wireless device receiving one or more RRC messages including configuration parameters of a cell's BWP configuration, wherein the configuration parameters of the BWP configuration include the frequency domain location and bandwidth of the LP-SS / LP-WUS refined within the BWP. The frequency domain location and bandwidth of the LP-SS / LP-WUS differ from the frequency domain location and bandwidth of the BWP.

[0357] One or more example embodiments include a wireless device receiving one or more RRC messages containing configuration parameters of a serving cell configuration (ServingCellConfig, ServingCellConfigCommon, ServingCellConfigSIB, etc.), wherein the configuration parameters of the serving cell configuration include refined frequency domain positions of the LP-SS / LP-WUS within the serving cell (LP-SS / WUS-offsetToPointA, LP-SS / WUS-offsetToCarrier, etc.). The frequency domain position of the LP-SS / LP-WUS differs from the frequency domain position of the cell (indicated by offsetToPointA or offsetToCarrier).

[0358] One or more example embodiments include a wireless device receiving one or more RRC messages containing configuration parameters of a physical cell group configuration (PhysicalCellGroupConfig, etc.) for a serving cell group (e.g., a group of SCells in the case of CA), wherein the configuration parameters of the physical cell group configuration include the frequency domain location (AFRCN, etc.) of the LP-SS / LP-WUS for the serving cell group. The frequency domain location of the LP-SS / LP-WUS differs from the frequency domain location of any cell in the serving cell group.

[0359] One or more example embodiments include a wireless device receiving one or more RRC messages that include configuration parameters of a MAC cell group configuration (CellGroupConfig, etc.) for a serving cell group (e.g., MCG or SCG), wherein the configuration parameters of the MAC cell group configuration include the frequency domain location (AFRCN, etc.) of the LP-SS / LP-WUS for the serving cell group. The frequency domain location of the LP-SS / LP-WUS differs from the frequency domain location of any cell in the serving cell group.

[0360] One or more example embodiments include a wireless device receiving from a base station one or more parameters indicating an MCG including a PCell and a first plurality of SCells, wherein the MCG is associated with a first LP-WUS, and one or more parameters indicating an SCG including a PSCell and a second plurality of SCells, wherein the SCG is associated with a second LP-WUS. Configuration parameters of the first LP-WUS differ from configuration parameters of the second LP-WUS. During monitoring a first PDCCH of the MCG, the wireless device receives a first command indicating activation of monitoring of the first LP-WUS. The wireless device stops monitoring the first PDCCH of the MCG based on monitoring the first LP-WUS. During monitoring a second PDCCH of the SCG, the wireless device receives a second command indicating activation of monitoring of the second LP-WUS. The wireless device stops monitoring the second PDCCH of the SCG based on monitoring the second LP-WUS. Monitoring of the first LP-WUS is independent of monitoring of the second LP-WUS. Monitoring of the first PDCCH is independent of monitoring of the second PDCCH.

[0361] One or more example embodiments include a wireless device receiving one or more parameters of LP-WUS from a base station, wherein the one or more parameters include a parameter indicating the frequency location (or starting point) of LP-WUS. This parameter includes at least one of the following: an absolute radio frequency channel number (ARFCN) value, a frequency offset value associated with Point A of the cell, a frequency offset value associated with the start / end point of the cell's SSB, a frequency offset value associated with the lowest common resource block of the cell's carrier bandwidth, etc. Based on this parameter and in response to activating LP-WUS, the wireless device monitors LP-WUS at that frequency location and stops monitoring the PDCCH of one or more cells.

[0362] One or more example embodiments include a wireless device receiving one or more RRC messages from a base station, the one or more RRC messages including a first parameter for triggering LP-WUS monitoring on a first cell and a second parameter for triggering on-demand SSB / SIB1 transmission for a second cell. The wireless device receives an indication (or command) to activate LP-WUS monitoring. In response to LP-WUS monitoring, the wireless device stops monitoring the PDCCH on the first cell. The wireless device deactivates LP-WUS monitoring in response to transmitting an uplink signal via the first cell to trigger on-demand SSB / SIB1 transmission for the second cell. Based on this deactivation, the wireless device monitors the PDCCH to obtain a response corresponding to the uplink signal.

[0363] One or more example embodiments include a timer associated with LP-WUS monitoring being stopped by a wireless device in response to at least one of the following: triggering an on-demand SSB; and sending an uplink signal requesting on-demand SSB transmission.

[0364] Figure 40 An example embodiment of the LP-WUS configuration is shown.

[0365] exist Figure 40 In the example, the wireless device receives from the base station (e.g., at T0) a first message (e.g., a UE capability information request included in an RRC message) that includes a request for the wireless device's radio access capabilities.

[0366] exist Figure 40 In the example, the wireless device sends a second message (e.g., an RRC message) to the base station (e.g., at T1) regarding the wireless device radio access capability for power-saving operation, wherein the second message indicates that the wireless device supports LP-WUS configuration applicable to MAC entities (referred to in this specification as per-MAC entity LP-WUS configuration).

[0367] exist Figure 40In the example, the base station sends a third message (e.g., an RRC message) to the radio device (e.g., at T2) that includes configuration parameters of the LP-WUS configuration. This LP-WUS configuration is configured per MAC entity. The configuration parameters of the LP-WUS configuration can be based on... Figure 38 and / or Figure 39 This can be implemented using an example.

[0368] In one example, the LP-WUS configuration for each MAC entity can instruct the LP-WUS to control PDCCH monitoring for all cells (e.g., SpCell, SCell) in the cell group corresponding to the MAC entity. If the MAC entity is used for (or associated with) an MCG, the first LP-WUS configured for the MCG is used to control PDCCH monitoring for all cells (e.g., PCell and / or SCell) included in the MCG. If the MAC entity is used for an SCG, the second LP-WUS configured for the SCG is used to control PDCCH monitoring for all cells (e.g., PSCell and / or SCell) included in the SCG. When dual connectivity (DC) is configured, the MCG and SCG are, for example, based on... Figure 3 The examples are associated with different MAC entities.

[0369] In one example embodiment, the configuration parameters of the cell group configuration (CellGroupConfig, etc.) for a serving cell group (e.g., MCG or SCG) include frequency domain location indications (AFRCN, GSCN, etc.) for the LP-SS / LP-WUS of that serving cell group. The frequency domain location of the LP-SS / LP-WUS differs from the frequency domain location of any serving cell in that serving cell group. Explicitly indicating the frequency domain location of the LP-SS / LP-WUS can reduce the power consumption of the radio device for detecting the LP-SS / LP-WUS. Configuring the frequency parameters of the LP-SS / LP-WUS separately from the cell configuration of the serving cell within the MAC cell group configuration parameters allows the base station to configure LP-SS / LP-WUS common to the cell group, thus reducing the resource consumption of the LP-SS / LP-WUS.

[0370] In one example, the frequency location of LP-SS / LP-WUS can be based on what will be described later. Figure 41 This can be implemented using an example.

[0371] In one example embodiment, the first LP-WUS associated with the MCG and the second LP-WUS associated with the SCG are configured separately and / or independently.

[0372] In one example embodiment, the wireless device receives from a base station (e.g., at T2) one or more parameters indicating an MCG comprising a PCell and a first plurality of SCells, wherein the MCG is associated with a first LP-WUS, and one or more parameters indicating an SCG comprising a PSCell and a second plurality of SCells, wherein the SCG is associated with a second LP-WUS. The configuration parameters of the first LP-WUS are different from the configuration parameters of the second LP-WUS.

[0373] exist Figure 40 In the example, the base station may send a command instructing the activation of LP-WUS (e.g., first LP-WUS and / or second LP-WUS). This command may be a DCI (e.g., unicast DCI or group public DCI) or a MAC CE.

[0374] In one example embodiment, the wireless device receives a first command instructing the activation of monitoring of the first LP-WUS during the monitoring of the first PDCCH of the MCG. The wireless device stops monitoring the first PDCCH of the MCG based on monitoring the first LP-WUS. The wireless device can resume monitoring the first PDCCH of the MCG in response to receiving the first LP-WUS.

[0375] In one example embodiment, the wireless device receives a second command indicating activation of monitoring of the second LP-WUS during monitoring of the second PDCCH of the SCG. The wireless device stops monitoring the second PDCCH of the SCG based on monitoring the second LP-WUS. The wireless device can resume monitoring the second PDCCH of the SCG in response to receiving the second LP-WUS.

[0376] In one example embodiment, monitoring of the first LP-WUS is independent of monitoring of the second LP-WUS. Monitoring of the first PDCCH is independent of monitoring of the second PDCCH. Configuration parameters of the first LP-WUS (e.g., periodicity, duty cycle, frequency / time resource indication, etc.) are configured separately and / or independently from configuration parameters of the second LP-WUS.

[0377] In one example embodiment, when the first LP-WUS is not configured for the MCG and the second LP-WUS is configured for the SCG, the wireless device does not apply the second LP-WUS to the MCG. In this case, the wireless device is based on the above regarding... Figure 32 , Figure 33 , Figure 34 , Figure 35A , Figure 35B , Figure 36A , Figure 36B and / or Figure 37The existing Rel.15 / 16 / 17 / 18 power-saving operation described herein monitors the PDCCH on the MCG. Similarly, if the second LP-WUS is not configured for the SCG and the first LP-WUS is configured for the MCG, the wireless device does not apply the first LP-WUS to the SCG. In this case, the wireless device monitors the PDCCH on the SCG based on the existing Rel.15 / 16 / 17 / 18 power-saving operation.

[0378] based on Figure 40 In this example embodiment, the base station and the wireless device are aligned in terms of the LP-SS / LP-WUS configurations supported by the wireless device. The base station can be configured with appropriate LP-SS / LP-WUS configurations to reduce the power consumption of the wireless device and / or reduce the resource consumption of the LP-SS / LP-WUS configuration.

[0379] Sharing the same LP-SS / LP-WUS configuration across multiple cells (PCell and / or SCell) of a MAC entity (e.g., MCG or SCG) can reduce the resource consumption of the LP-SS / LP-WUS configuration. This example embodiment may increase the power consumption of the radio device, for example, when the radio device wakes up upon receiving LP-SS / LP-WUS to monitor the PDCCH on all cells of the MAC entity. Figure 40 The example implementation can be modified to configure LP-SS / LP-WUS from the MAC entity level to the DRX cell group level.

[0380] In one example, within a MAC entity, a first LP-SS / LP-WUS can be configured to be associated with a first DRX cell group, and a second LP-SS / LP-WUS can be configured to be associated with a second DRX cell group. The first and second DRX cell groups can be deployed in different frequency bands / ranges. Each cell in a DRX cell group can share the same LP-SS / LP-WUS configuration, in which case the radio device wakes up upon receiving an LP-SS / LP-WUS associated with the DRX cell group to monitor the PDCCH on each cell of the DRX cell group. To implement this embodiment, the radio device sends (e.g., in...) Figure 40 The second message (at T1) indicates that the radio device supports the LP-WUS configuration applicable to DRX cell groups (referred to in this specification as the per-DRX cell group LP-WUS configuration).

[0381] In one example embodiment, configuration parameters for LP-SS / LP-WUS (e.g., frequency location indication) may be included in a CellGroupConfig IE, where two LP-SS / LP-WUS configurations can be configured, each associated with (or linked to) one of DRX-config or DRX-ConfigSecondaryGroup. DRX-config is associated with a first number of serving cells. DRX-ConfigSecondaryGroup is associated with a second number of serving cells. The first and second number of serving cells are multiple serving cells configured by the CellGroupConfig IE (e.g., sCellToAddModList). Each of the multiple serving cells belongs to either a first DRX cell group (associated with DRX-Config) or a second DRX cell group (associated with DRX-ConfigSecondaryGroup). Configuration parameters for DRX-Config and / or DRX-ConfigSecondaryGroup can be based on... Figure 33 and / or Figure 34 This can be implemented using an example.

[0382] Using different LP-SS / LP-WUS configurations between two different DRX cell groups within a MAC entity may increase the resource consumption of the LP-SS / LP-WUS configuration and reduce the power consumption of the radio device for waking up PDCCH monitoring. Detection of LP-SS / LP-WUS associated with a DRX cell group may only require the radio device to wake up to perform PDCCH monitoring on that DRX cell group, and / or may have no impact on power-saving operations on the second DRX cell group. Example embodiments can improve the power consumption of the radio device.

[0383] Figure 41 Showing based on Figure 40 Example implementation of LP-WUS configuration.

[0384] In one example embodiment, the wireless device can receive one or more RRC messages from a base station, including configuration parameters for LP-SS / LP-WUS, for example, based on... Figure 38 , Figure 39 and / or Figure 40 Example. This configuration parameter can indicate the frequency location (e.g., starting point and / or bandwidth) of LP-SS / LP-WUS.

[0385] In one example embodiment, configuration parameters may include an NR-ARFCN value for LP-SS / LP-WUS, indicating the start / start point of LP-SS / LP-WUS in the frequency domain. Using an NR-ARFCN value to indicate the frequency location of LP-SS / LP-WUS allows wireless devices to quickly identify and detect the frequency location of LP-SS / LP-WUS, for example, without referencing the frequency location of any serving cell. This example embodiment can reduce the power consumption of the wireless device used to detect LP-SS / LP-WUS.

[0386] In one example embodiment, configuration parameters may include a GSCN (Global Synchronization Channel Number) value for LP-SS / LP-WUS, indicating the start / start point of the LP-SS / LP-WUS in the frequency domain. Using the GSCN value to indicate the frequency location of the LP-SS / LP-WUS allows the wireless device to quickly identify and detect the LP-SS / LP-WUS, for example, without referencing the frequency location of any serving cell. This example embodiment can reduce the power consumption of the wireless device used for LP-SS / LP-WUS detection. Compared to NR-ARFCN, using GSCN allows for LP-SS / LP-WUS placement at a granularity of up to 1MHz, thus accelerating LP-SS / LP-WUS detection.

[0387] In one example embodiment, the configuration parameters may include a value for the frequency offset to Point A of the serving cell for the LP-SS / LP-WUS, indicating the start / start point of the LP-SS / LP-WUS in the frequency domain. Indicating the frequency location of the LP-SS / LP-WUS relative to Point A allows the radio device to quickly identify and detect the LP-SS / LP-WUS within the cell, for example, when the radio device obtains the location of Point A of the cell. This example embodiment can reduce the power consumption of the radio device used to detect the LP-SS / LP-WUS. Compared to NR-ARFCN and GSCN, using Point A as a reference for the frequency location of the LP-SS / LP-WUS allows the radio device to quickly identify the LP-SS / LP-WUS in the frequency domain when the radio device already has knowledge of Point A.

[0388] exist Figure 41 In the example, Point A is a common reference point for the cell's carrier bandwidth, SSB location, etc. Point A can be indicated by KSSB (or offsetToPointA) in the SIB1 message.

[0389] exist Figure 41In the example, the SSB can be configured within the initial downlink BWP (e.g., BWP0) with a bandwidth of 20 PRBs. Unlike the SSB, the LP-SS / LP-WUS can be configured with a bandwidth of 10 PRBs (or 15 PRBs). The frequency location of the LP-SS / LP-WUS can be configured differently and independently from that of the SSB.

[0390] exist Figure 41 In the example, a BWP (e.g., BWP0, ..., BWPi) can be configured with location and bandwidth parameters (e.g., locationAndBandwidth, Nstart, BWPi) that indicate the start of the BWP relative to a common RB x, which is indicated by OffsetToCarrier (in SIB1) relative to Point A (which is included in common RB 0).

[0391] exist Figure 41 In the example, LP-SS / LP-WUS can be multiplexed with the SSB frequency domain and / or with the SSB time domain in the cell.

[0392] In one example embodiment, the configuration parameters may include a value for the frequency offset to common RB x for the LP-SS / LP-WUS, indicating the start / start point of the LP-SS / LP-WUS in the frequency domain. Indicating the frequency location of the LP-SS / LP-WUS relative to common RB x allows the radio device to quickly identify and detect the LP-SS / LP-WUS within the cell, for example, when the radio device obtains the location of common RB x of the cell. This example embodiment can reduce the power consumption of the radio device used to detect the LP-SS / LP-WUS. Using common RB x as a reference for the frequency location of the LP-SS / LP-WUS allows the radio device to quickly identify the LP-SS / LP-WUS in the frequency domain when the radio device already has knowledge of the cell's common RB x.

[0393] In one example embodiment, configuration parameters may include values ​​for the frequency offset of the start / end PRB to the SSB for the LP-SS / LP-WUS, indicating the start / start point of the LP-SS / LP-WUS in the frequency domain. Indicating the frequency location of the LP-SS / LP-WUS relative to the SSB allows the radio device to quickly identify and detect the LP-SS / LP-WUS within the cell, for example, when the radio device obtains the location of the cell's SSB. This example embodiment can reduce the power consumption of the radio device used to detect the LP-SS / LP-WUS. Using the SSB as a reference for the frequency location of the LP-SS / LP-WUS allows the radio device to quickly identify the LP-SS / LP-WUS in the frequency domain even when the radio device already has knowledge of the cell's SSB.

[0394] Figure 42 An example implementation of LP-WUS monitoring is shown.

[0395] In one example, the wireless device receives data from the base station (e.g., in...). Figure 42 The RRC message (at T0 in the context of the first cell) includes a first parameter for triggering LP-WUS monitoring for PDCCH on the first cell and a second parameter for triggering uplink signals for on-demand SSB / SIB1 transmission on the second cell. In one example, the first parameter may be based on... Figure 38 , Figure 39 , Figure 40 and / or Figure 41 This can be implemented using an example.

[0396] In one example, the second parameter can be based on Figure 31 This can be implemented using an example. The second parameter can include the frequency / time resource indication of the uplink signal.

[0397] In one example, the frequency / time resource indication may include a RACH resource indication, for example, when the uplink signal is a PRACH preamble.

[0398] In one example, the frequency / time resource indication may include a PUCCH resource indication, for example, when the uplink signal is an SR via the PUCCH.

[0399] In one example, the frequency / time resources of the uplink signal on the first cell can be used to trigger on-demand SSB / SIB1 messages for the second cell.

[0400] In one example, the first cell can be a PCell or an active SCell.

[0401] In one example, the second cell can be a deactivated SCell or an activated SCell.

[0402] exist Figure 42 In the example, based on receiving a message at T0, the radio device monitors the PDCCH on one or more serving cells (e.g., by using the radio device's MR).

[0403] exist Figure 42 In the example, the wireless device can monitor the PDCCH during the process. Figure 42 At T1, a command is received instructing the activation of LP-WUS monitoring, for example, based on... Figure 40 Examples.

[0404] exist Figure 42 In the example, the radio device begins monitoring LP-WUS based on a received command (e.g., from T1) (e.g., by using the radio device's LR). In response to LP-WUS monitoring, the radio device stops monitoring the PDCCH on one or more serving cells (by using the radio device's MR). LP-WUS monitoring can be based on... Figure 38 and / or Figure 39 Examples.

[0405] exist Figure 42 In the example, the radio device may not receive LP-WUS during LP-WUS monitoring. In response to not receiving LP-WUS during the LP-WUS reception period, the radio device may continue to skip PDCCH monitoring on the one or more serving cells. The radio device may continue monitoring LP-WUS based on the first parameter of LP-WUS, for example, based on... Figure 38 and / or Figure 39 Examples.

[0406] exist Figure 42 In the example, the wireless device can initiate a procedure to trigger on-demand SSB / SIB1 messages while monitoring LP-WUS and stopping monitoring PDCCH.

[0407] In one example, the wireless device may initiate the process for a second cell, for instance, when the second cell is configured with on-demand SSB / SIB1 messages and the wireless device determines that the SSB / SIB1 messages have not yet been transmitted by the base station on the second cell.

[0408] In one example, the wireless device may initiate the procedure for the second cell when the wireless device determines that it is synchronized with the second cell and / or obtains the SIB1 message of the second cell.

[0409] exist Figure 42 In the example, the wireless device, based on initiating the process, can monitor LP-WUS and skip monitoring PDCCH on the first cell, for example, during... Figure 42At point T2, an uplink signal is sent via the first cell.

[0410] exist Figure 42 In the example, the wireless device can respond to transmitting an uplink signal via the first cell that triggers an on-demand SSB / SIB1 for the second cell, for example in Figure 42 At T2, LP-WUS monitoring is deactivated. Deactivating LP-WUS monitoring may include stopping the use of LR to detect LP-WUS. The wireless device may, based on the deactivation of LP-WUS monitoring, resume monitoring the PDCCH of the first cell to obtain a response corresponding to the uplink signal.

[0411] exist Figure 42 In the example, in response to an uplink signal triggering an on-demand SSB / SIB1 message, the radio device (automatically) resumes PDCCH monitoring on the first cell, even if the radio device has not yet received LP-WUS. Based on the resumption of PDCCH monitoring, the radio device can receive a response to the uplink signal, for example in... Figure 42 At T3. The response can be a RAR corresponding to a preamble, for example, when the uplink signal is a preamble. The response can be a DCI, for example, when the uplink signal is an SR via PUCCH.

[0412] Figure 42 The example implementation can be extended to cases where a timer associated with LP-WUS monitoring is configured. In one example, the radio device may, in response to receiving a command instructing the activation of LP-WUS monitoring, such as at T1, start a timer / window associated with LP-WUS monitoring (e.g., configured by the base station in an RRC message at T0). While the timer is running, the radio device monitors LP-WUS and stops monitoring the PDCCH on the one or more serving cells. When the timer expires, the radio device resumes PDCCH monitoring and deactivates LP-WUS monitoring. Figure 42 In the example, in response to triggering on-demand SSB / SIB1 at T2, the wireless device can stop the timer, deactivate LP-WUS monitoring, and resume PDCCH monitoring. Stopping the timer allows the wireless device to resume PDCCH monitoring.

[0413] based on Figure 42For example, the wireless device deactivates LP-WUS monitoring in response to sending an uplink signal triggering On-Demand SSB / SIB1. Based on this deactivation, the wireless device monitors the PDCCH to obtain a response corresponding to the uplink signal. In response to triggering On-Demand SSB / SIB1 and / or sending an uplink signal requesting On-Demand SSB / SIB1 transmission, the wireless device stops the timer associated with LP-WUS monitoring. This example embodiment can reduce the latency of On-Demand SSB / SIB1 requests when the wireless device is configured / activated for power-saving LP-WUS monitoring.

[0414] based on Figure 40 , Figure 41 and / or Figure 42 In an example embodiment, a wireless device receives one or more RRC messages from a base station. These RRC messages include a first parameter triggering LP-WUS monitoring on a first cell and a second parameter triggering an uplink signal for on-demand SSB / SIB1 transmission to a second cell. The wireless device receives an indication (or command) indicating activation of LP-WUS monitoring. In response to LP-WUS monitoring, the wireless device stops monitoring the PDCCH on the first cell. The wireless device deactivates LP-WUS monitoring in response to transmitting an uplink signal via the first cell triggering on-demand SSB / SIB1 transmission to the second cell. Based on this deactivation, the wireless device monitors the PDCCH to obtain a response corresponding to the uplink signal.

[0415] In one example embodiment, the wireless device receives one or more parameters from a base station, including a first parameter triggering LP-WUS monitoring on a first cell and a second parameter triggering an uplink signal for on-demand SSB / SIB1 transmission to a second cell. The wireless device receives an indication (or command) indicating activation of LP-WUS monitoring. In response to LP-WUS monitoring, the wireless device stops monitoring the PDCCH on the first cell. The wireless device deactivates LP-WUS monitoring in response to transmitting an uplink signal via the first cell triggering on-demand SSB / SIB1 transmission to the second cell. Based on the deactivation, the wireless device monitors the PDCCH to obtain a response corresponding to the uplink signal.

[0416] In one example embodiment, the wireless device receives one or more parameters from a base station, including a first parameter triggering LP-WUS monitoring of the PDCCH and a second parameter triggering an uplink signal for on-demand SSB / SIB1 transmission. The wireless device receives an indication (or command) indicating activation of LP-WUS monitoring. In response to LP-WUS monitoring, the wireless device stops monitoring the PDCCH. The wireless device deactivates LP-WUS monitoring in response to sending an uplink signal triggering on-demand SSB / SIB1. Based on this deactivation, the wireless device monitors the PDCCH to obtain a response corresponding to the uplink signal.

[0417] According to an example embodiment, the wireless device receives the instruction indicating the activation of LP-WUS monitoring during the monitoring of the PDCCH of a first cell.

[0418] According to one example embodiment, the wireless device monitors LP-WUS while maintaining the activation state of the first BWP of the first cell.

[0419] According to an example embodiment, the wireless device stops monitoring the PDCCH of the first BWP while maintaining the activation state of the first BWP of the first cell.

[0420] According to one example embodiment, a radio device activates a first BWP in a first cell. Based on the fact that the first BWP is the active BWP of the first cell, the radio device monitors the PDCCH on the first BWP.

[0421] According to one example embodiment, the one or more parameters include a timer value associated with monitoring LP-WUS. The wireless device starts the timer in response to receiving the instruction. The wireless device stops the timer in response to at least one of: triggering an on-demand SSB; and transmitting the uplink signal.

[0422] According to one example embodiment, the wireless device stops the timer in response to receiving an LP-WUS indicating that it is monitoring one or more cells including a first cell and / or a second cell.

[0423] According to one example embodiment, the indication / command does not include an active BWP switching indication.

[0424] According to an example embodiment, the LP-WUS is based on On / Off Keying (OOK) transmission, wherein, based on the OOK: the LP-WUS is awakened by a transmission indication to monitor the PDCCH of a first cell and / or a second cell; and the LP-WUS is not awakened by a transmission indication to monitor the PDCCH.

[0425] According to one example embodiment, the wireless device receives WUS based on envelope detection of the LP-WUS based on the OOK. The wireless device does not wake up to monitor the PDCCH in response to not receiving the LP-WUS.

[0426] According to one example embodiment, in response to receiving the LP-WUS, the wireless device uses the wireless device's main receiver (MR) to monitor the PDCCH of one or more cells, including at least one of a first cell and a second cell.

[0427] According to one example embodiment, the wireless device receives a DCI during PDCCH monitoring, the DCI indicating uplink granting for the Physical Uplink Shared Channel (PUSCH) and / or downlink scheduling for the Physical Downlink Shared Channel (PDSCH).

[0428] According to one example embodiment, the wireless device monitors LP-WUS by using the low-power receiver (LR) of the wireless device.

[0429] According to one example embodiment, the first parameter includes at least one of the following: the transmission periodicity of the LP-WUS, the value of the periodic duration (during which the wireless device monitors the LP-WUS), the number of resource blocks (RBs), and / or the number of symbols of the WUS.

[0430] According to one example embodiment, the number is less than the total number of symbols in the time slot.

[0431] According to one example embodiment, the number is equal to or greater than the total number of symbols in the time slot.

[0432] According to an example embodiment, the first parameter includes at least one of the following: a time offset of the periodic duration associated with a time reference point (system radio frame or subframe), a time offset of the start symbol of the LP-WUS associated with the start point of the periodic duration, and / or a time offset of the end symbol of the LP-WUS associated with the end point of the periodic duration.

[0433] According to one example embodiment, the indication / command includes at least one of the following: RRC message, MAC CE, and / or DCI.

[0434] According to one example embodiment, the DCI is a group common DCI.

[0435] According to one example embodiment, the group common DCI is DCI format 2_6.

[0436] According to one example embodiment, the group common DCI is CRC scrambled by at least one of the following: PS-RNTI and / or RNTI associated with activation / deactivation monitoring LP-WUS.

[0437] According to one example embodiment, the group common DCI is a DCI format different from DCI format 2_6.

[0438] According to one example embodiment, the group public DCI includes a bit corresponding to the wireless device, the bit indicating whether LP-WUS monitoring is enabled for the wireless device.

[0439] According to one example embodiment, the position of the bit corresponding to the wireless device is indicated by higher-level parameters in one or more RRC messages.

[0440] According to one example embodiment, the DCI is a unicast DCI whose CRC is scrambled by at least one of the following: C-RNTI and / or CS-RNTI.

[0441] According to one example embodiment, the DCI includes a DCI field indicating whether LP-WUS monitoring is activated.

[0442] According to one example embodiment, the DCI field is a PDCCH monitoring adaptation field. The size of the DCI field is indicated by higher-level / RRC parameters in the one or more RRC messages.

[0443] According to one example embodiment, the uplink signal includes at least one of the following: a preamble, a sounding reference signal (SRS), a scheduling request (SR) via the physical uplink control channel (PUCCH), and / or a media access control element (MACECE).

[0444] According to an example embodiment, the wireless device triggers an on-demand SSB request process for a second cell based on the following: no SSB is detected on the second cell, and / or the second parameter indicates that the SSB is transmitted on demand via the second cell.

[0445] According to one example embodiment, the first cell is different from the second cell. The first cell is a PCell or an active SCell. The second cell is a deactivated SCell.

[0446] According to one example embodiment, the first cell is the same as the second cell. The first cell is a PCell or an active SCell.

[0447] According to one example embodiment, the wireless device transmits the uplink signal based on at least one of the following: the first cell is a PCell and / or the first cell is an active SCell.

[0448] According to one example embodiment, activating LP-WUS monitoring includes starting to monitor the LP-WUS based on the first parameter. Deactivating LP-WUS monitoring includes stopping monitoring the LP-WUS.

[0449] According to one example embodiment, the response includes at least one of the following: a DCI with CRC scrambled by C-RNTI and NDI inverted, and / or includes a RAR corresponding to the preamble index of the uplink signal, wherein the uplink signal is a preamble.

[0450] In one example embodiment, the wireless device receives a first message from a base station, the first message including a request for wireless access capabilities of the wireless device. The wireless device sends a second message to the base station regarding wireless access capabilities for power-saving operation, wherein the second message indicates that the wireless device supports at least one of the following: LP-WUS configuration per BWP, LP-WUS configuration per cell, LP-WUS configuration per DRX cell group, and / or LP-WUS configuration per MAC entity.

[0451] In one example embodiment, the wireless device receives a first message from a base station, the first message including a request for wireless access capabilities of the wireless device. The wireless device sends a second message to the base station regarding wireless access capabilities for power-saving operation, wherein the second message indicates that the wireless device supports at least one of the following: LP-WUS configuration for BWP, LP-WUS configuration for a cell, LP-WUS configuration for DRX cell groups, and / or LP-WUS configuration for MAC entities.

[0452] According to one example embodiment, the second message is indicated by frequency band / frequency range.

[0453] In one example embodiment, a wireless device receives one or more parameters from a base station indicating an MCG comprising a PCell and a first plurality of SCells, wherein the MCG is associated with a first LP-WUS, and an SCG comprising a PSCell and a second plurality of SCells, wherein the SCG is associated with a second LP-WUS. The configuration parameters of the first LP-WUS are different from the configuration parameters of the second LP-WUS. During the monitoring of a first PDCCH of the MCG, the wireless device receives a first command indicating the activation of monitoring the first LP-WUS. Based on the monitoring of the first LP-WUS, the wireless device stops monitoring the first PDCCH of the MCG. During the monitoring of a second PDCCH of the SCG, the wireless device receives a second command indicating the activation of monitoring the second LP-WUS. Based on the monitoring of the second LP-WUS, the wireless device stops monitoring the second PDCCH of the SCG. Monitoring of the first LP-WUS is independent of monitoring of the second LP-WUS. Monitoring of the first PDCCH is independent of monitoring of the second PDCCH.

[0454] In one example embodiment, a wireless device receives one or more parameters of LP-WUS from a base station, wherein the one or more parameters include parameters indicating the frequency location (or start point) of the LP-WUS. The parameters include at least one of the following: an absolute radio frequency channel number (ARFCN) value, a frequency offset value associated with Point A of the cell, a frequency offset value associated with the start / end point of the SSB of the cell, a frequency offset value associated with the lowest common resource block of the carrier bandwidth of the cell, etc. Based on the parameters and in response to activating the LP-WUS, the wireless device monitors the LP-WUS at the frequency location and stops monitoring the PDCCH of one or more cells.

[0455] Clause 1. A method comprising: receiving one or more messages by a wireless device, the one or more messages including: a first parameter triggering a low-power wake-up signal (LP-WUS) for physical downlink control channel (PDCCH) monitoring on a cell; and a second parameter requesting an uplink signal for on-demand System Information Block 1 (SIB1) of the cell; monitoring the LP-WUS based on the first parameter, wherein the wireless device skips monitoring the PDCCH of the cell during a time period in which the wireless device is monitoring the LP-WUS; during the time period, transmitting the uplink signal requesting the on-demand SIB1 of the cell based on the second parameter; deactivating monitoring of the LP-WUS based on transmitting the uplink signal; and monitoring the PDCCH based on the deactivation to obtain a response corresponding to the uplink signal.

[0456] Clause 2. A method comprising: receiving one or more messages by a wireless device, the one or more messages including: a first parameter triggering a low-power wake-up signal (LP-WUS) for physical downlink control channel (PDCCH) monitoring; and a second parameter for an uplink signal; monitoring the LP-WUS based on the first parameter, wherein the wireless device skips monitoring the PDCCH during a time period in which the wireless device is monitoring the LP-WUS; transmitting the uplink signal based on the second parameter during the time period; and monitoring the PDCCH in response to transmitting the uplink signal to obtain a response corresponding to the uplink signal.

[0457] Clause 3. The method according to any one of Clauses 1 to 2, wherein the wireless device monitors the PDCCH based on deactivating the monitoring of the LP-WUS during the said time period.

[0458] Clause 4. The method according to any one of Clauses 1 to 3, wherein the wireless device monitors the PDCCH based on ignoring the first parameter of the LP-WUS during the said time period.

[0459] Clause 5. The method according to any one of Clauses 1 to 4, wherein the wireless device deactivates monitoring of the LP-WUS in response to / afterwards / based on transmitting the uplink signal.

[0460] Clause 6. The method according to any one of Clauses 1 to 5, wherein the one or more messages include at least one of: a System Information Block (SIB); and a Radio Resource Control (RRC) Information Element (IE).

[0461] Clause 7. The method according to any one of Clauses 1 to 6, wherein the wireless device is in an RRC idle state or an RRC inactive state.

[0462] Clause 8. The method according to any one of Clauses 1 to 7, wherein the wireless device receives an instruction to activate monitoring of the LP-WUS.

[0463] Clause 9. The method according to any one of Clauses 1 to 8, wherein the instruction is included in the first parameter of the LP-WUS.

[0464] Clause 10. The method according to any one of Clauses 1 to 9, wherein the wireless device monitors the LP-WUS of a first cell in one or more cells.

[0465] Clause 11. The method according to any one of Clauses 1 to 10, wherein the wireless device transmits the uplink signal via a second cell of one or more cells.

[0466] Clause 12. The method according to any one of Clauses 1 to 11, wherein the first cell is the same as the second cell.

[0467] Clause 13. The method according to any one of Clauses 1 to 12, wherein the first cell is different from the second cell.

[0468] Clause 14. The method according to any one of Clauses 1 to 13, wherein the wireless device is in an RRC connection state.

[0469] Clause 15. The method according to any one of Clauses 1 to 14, wherein the radio device monitors the LP-WUS while maintaining the activation state of the first BWP of the cell.

[0470] Clause 16. The method according to any one of Clauses 1 to 15, wherein the radio device stops monitoring the PDCCH of the first BWP while maintaining the active state of the first BWP of the cell.

[0471] Clause 17. The method according to any one of Clauses 1 to 16 further includes activating the first BWP of the cell.

[0472] Clause 18. The method according to any one of Clauses 1 to 17, wherein the wireless device monitors the PDCCH on the first BWP based on the fact that the first BWP is the active BWP of the cell.

[0473] Clause 19. The method according to any one of Clauses 1 to 18, wherein the first parameter includes a timer value associated with monitoring the LP-WUS.

[0474] Clause 20. The method according to any one of Clauses 1 to 19 further includes starting the timer in response to at least one of: receiving the first parameter of the LP-WUS; and the first parameter including an indication to activate monitoring of the LP-WUS.

[0475] Clause 21. The method according to any one of Clauses 1 to 20 further includes suspending / stopping the timer in response to at least one of: triggering the on-demand SIB1; and sending the uplink signal.

[0476] Clause 22. The method according to any one of Clauses 1 to 21 further includes suspending / stopping the timer in response to receiving an instruction from the LP-WUS to monitor the PDCCH of one or more cells including the cell.

[0477] Clause 23. The method according to any one of Clauses 1 to 22, wherein the indication does not include an active BWP switching indication.

[0478] Clause 24. The method according to any one of Clauses 1 to 23, wherein the LP-WUS is transmitted based on on-off keying (OOK) modulation, wherein, based on the OOK: the LP-WUS is transmitted to indicate wake-up to monitor the PDCCH of the cell; and the LP-WUS is not transmitted to indicate no wake-up to monitor the PDCCH.

[0479] Clause 25. The method according to any one of Clauses 1 to 24, wherein the wireless device receives the LP-WUS based on envelope detection of the LP-WUS based on the OOK modulation.

[0480] Clause 26. The method according to any one of Clauses 1 to 25, wherein the wireless device does not wake up to monitor the PDCCH in response to not receiving the LP-WUS.

[0481] Clause 27. The method according to any one of Clauses 1 to 26, wherein the LP-WUS is a downlink signal of one or more DCIs that are different from at least one of the following: DCI format 2_6; and DCI format 2_7.

[0482] Clause 28. The method according to any one of Clauses 1 to 27, wherein the LP-WUS is a downlink signal received without using a Radio Network Temporary Identifier (RNTI), wherein the RNTI is at least one of: a first RNTI for receiving DCI format 2_6; and a second RNTI for receiving DCI format 2_7.

[0483] Clause 29. The method according to any one of Clauses 1 to 28 further includes monitoring the PDCCH of one or more cells including the cell using the main receiver (MR) of the radio device in response to receiving the LP-WUS.

[0484] Clause 30. The method according to any one of Clauses 1 to 29 includes receiving a DCI indicating uplink grants for the Physical Uplink Shared Channel (PUSCH) and / or downlink scheduling for the Physical Downlink Shared Channel (PDSCH) during monitoring of the PDCCH.

[0485] Clause 31. The method according to any one of Clauses 1 to 30 includes receiving a DCI indicating a paging message for the wireless device during monitoring of the PDCCH.

[0486] Clause 32. The method according to any one of Clauses 1 to 31, wherein the wireless device monitors the LP-WUS using the low-power receiver (LR) of the wireless device.

[0487] Clause 33. The method according to any one of Clauses 1 to 32, wherein the first parameter includes at least one of the following: the transmission periodicity of the LP-WUS; the value of the periodic duration during which the wireless device monitors the LP-WUS; the number of resource blocks (RBs); and the number of symbols of the LP-WUS.

[0488] Clause 34. The method according to any one of Clauses 1 to 33, wherein the number is less than the total number of symbols in the time slot.

[0489] Clause 35. The method according to any one of Clauses 1 to 34, wherein the number is equal to or greater than the total number of symbols in the time slot.

[0490] Clause 36. The method according to any one of Clauses 1 to 35, wherein the first parameter includes at least one of the following: a time offset of the periodic duration associated with a time reference point; a time offset of the start symbol of the LP-WUS associated with the start point of the periodic duration; and a time offset of the end symbol of the LP-WUS associated with the end point of the periodic duration.

[0491] Clause 37. The method according to any one of Clauses 1 to 36, wherein the time reference point is a system radio frame or subframe of the reference cell.

[0492] Clause 38. The method according to any one of Clauses 1 to 37, wherein the reference cell is the primary cell.

[0493] Clause 39. The method according to any one of Clauses 1 to 38, wherein the reference cell is a secondary cell.

[0494] Clause 40. The method according to any one of Clauses 1 to 39, wherein the reference cell is the cell in which the LP-WUS is configured with the first parameter.

[0495] Clause 41. The method according to any one of Clauses 1 to 40, wherein the instruction includes at least one of: RRC message; MAC CE; and DCI.

[0496] Clause 42. The method according to any one of Clauses 1 to 41, wherein the DCI is a group public DCI.

[0497] Clause 43. The method according to any one of Clauses 1 to 42, wherein the group common DCI is DCI format2_6.

[0498] Clause 44. The method according to any one of Clauses 1 to 43, wherein the group public DCI is CRC scrambled by at least one of: PS-RNTI; and RNTI associated with the LP-WUS.

[0499] Clause 45. The method according to any one of Clauses 1 to 44, wherein the group public DCI is a DCI format different from at least one of the following: DCI format 2_6; and DCI format 2_7.

[0500] Clause 46. The method according to any one of Clauses 1 to 45, wherein the group public DCI includes a bit corresponding to the wireless device that indicates whether the LP-WUS monitoring is enabled for the wireless device.

[0501] Clause 47. The method according to any one of Clauses 1 to 46, wherein the position of the bit corresponding to the wireless device is indicated by a higher-layer parameter in one or more messages.

[0502] Clause 48. The method according to any one of Clauses 1 to 47, wherein the DCI is a unicast DCI in which the CRC is scrambled by at least one of the following: C-RNTI; and CS-RNTI.

[0503] Clause 49. The method according to any one of Clauses 1 to 48, wherein the DCI includes a DCI field indicating whether the LP_WUS monitoring is activated.

[0504] Clause 50. The method according to any one of Clauses 1 to 49, wherein the DCI field is a PDCCH monitoring adaptation field.

[0505] Clause 51. The method according to any one of Clauses 1 to 50, wherein the size of the DCI field is indicated by a high-level / RRC parameter in the one or more messages.

[0506] Clause 52. The method according to any one of Clauses 1 to 51, wherein the uplink signal includes at least one of the following: a preamble; a sounding reference signal (SRS); a scheduling request (SR) via the physical uplink control channel (PUCCH); and a MACE CE.

[0507] Clause 53. The method according to any one of Clauses 1 to 52, wherein the second parameter of the uplink signal indicates the preamble for a random access (RA) procedure, wherein the radio device transmits the preamble based on initiating the RA procedure.

[0508] Clause 54. The method according to any one of Clauses 1 to 53, wherein the wireless device triggers the on-demand SIB1 request process based on at least one of the following: SIB1 is not detected; and the second parameter indicates that the SIB1 is requested on demand.

[0509] Clause 55. The method according to any one of Clauses 1 to 54, wherein: the activation monitoring of the LP-WUS comprises starting monitoring of the LP-WUS according to the first parameter; and the deactivation monitoring of the LP-WUS comprises stopping monitoring of the LP-WUS.

[0510] Clause 56. The method according to any one of Clauses 1 to 55, wherein the response comprises at least one of: a first DCI whose CRC is scrambled by C-RNTI and whose NDI is inverted; and a second DCI whose CRC is scrambled by SI-RNTI; and a random access response (RAR) comprising a preamble index corresponding to the uplink signal, wherein the uplink signal is a preamble.

[0511] Clause 57. The method according to any one of Clauses 1 to 56, wherein the wireless device receives the one or more messages including the first parameter of the LP-WUS, based on both the LR and the MR being equipped on the wireless device.

[0512] Clause 58. The method according to any one of Clauses 1 to 57 further comprises: the wireless device receiving from a base station a first message including a request for wireless device radio access capability; and sending to the base station a second message for wireless device radio access capability for power-saving operation.

[0513] Clause 59. The method according to any one of Clauses 1 to 58, wherein the second message indicates that the wireless device supports at least one of the following: per-bandwidth portion (BWP) LP-WUS configuration; per-cell LP-WUS configuration; per-discontinuous reception (DRX) cell group LP-WUS configuration; and per-media access control (MAC) entity LP-WUS configuration.

[0514] Clause 60. The method according to any one of Clauses 1 to 59, wherein the second message indicates that the wireless device supports at least one of: the LP-WUS configuration applicable to BWP; the LP-WUS configuration applicable to a cell; the LP-WUS configuration applicable to a DRX cell group; and the LP-WUS configuration applicable to a MAC entity.

[0515] Clause 61. The method according to any one of Clauses 1 to 60, wherein the second message is indicated by frequency band or by frequency range (FR).

[0516] Clause 62. A method comprising: receiving parameters by a radio device, the parameters indicating: a primary cell group (MCG) including a primary cell (PCell) and a first plurality of secondary cells (SCells), wherein the MCG is associated with a first low-power wake-up signal (LP-WUS); and a secondary cell group (SCG) including a primary SCG cell (PSCell) and a second plurality of SCells, wherein the SCG is associated with a second LP-WUS; receiving a first command indicating activation of monitoring the first LP-WUS during monitoring of a first physical downlink control channel (PDCCH) of the MCG; stopping monitoring of the first PDCCH of the MCG based on monitoring of the first LP-WUS; and receiving a second command indicating activation of monitoring of the second LP-WUS during monitoring of a second PDCCH of the SCG; stopping monitoring of the second PDCCH of the SCG based on monitoring of the second LP-WUS.

[0517] Clause 63. A method comprising: receiving parameters by a wireless device, the parameters indicating: a primary cell group (MCG) including a primary cell (PCell) and a first plurality of secondary cells (SCells), wherein the MCG is associated with a first low-power wake-up signal (LP-WUS); and a secondary cell group (SCG) including a primary SCG cell (PSCell) and a second plurality of SCells, wherein the SCG is associated with a second LP-WUS; stopping monitoring of a first PDCCH of the MCG during a first time period of monitoring the first LP-WUS; and stopping monitoring of a second PDCCH of the SCG during a second time period of monitoring the second LP-WUS.

[0518] Clause 64. The method according to any one of Clauses 62 and 63, wherein the monitoring of the first LP-WUS is independent of the monitoring of the second LP-WUS.

[0519] Clause 65. The method according to any one of Clauses 62 and 63, wherein the first PDCCH of the MCG is stopped from monitoring independently of the second PDCCH of the SCG.

[0520] Clause 66. The method according to any one of Clauses 62 and 63, wherein the first time period is independent of the second time period.

[0521] Clause 67. The method according to any one of Clauses 62 and 63, wherein the first time period is determined based on a first configuration parameter of the first LP-WUS associated with the MCG.

[0522] Clause 68. The method according to any one of Clauses 62 and 63, wherein the second time period is determined based on a second configuration parameter of the second LP-WUS associated with the SCG.

[0523] Clause 69. The method according to any one of Clauses 62 and 63, wherein: the MCG is associated with a first MAC entity of the wireless device; and the SCG is associated with a second MAC entity of the wireless device.

[0524] Clause 70. The method according to any one of Clauses 62 and 63 further comprises: receiving from a base station a first message by the wireless device a request for wireless device radio access capability; and sending to the base station a second message for wireless device radio access capability for power-saving operation, wherein the second message indicates that the wireless device supports LP-WUS configured per MAC entity.

[0525] Clause 71. An apparatus comprising: one or more processors; and a memory storing instructions, which, when executed by said one or more processors, cause the apparatus to perform the method according to any one of Clauses 1 to 70.

[0526] Clause 72. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a device, cause the device to perform the method according to any one of Clauses 1 to 70.

[0527] The foregoing provisions illustrate various embodiments. These embodiments can be combined with each other. Similarly, for each reference to a wireless device taking an action such as receiving, some embodiments similarly involve a base station taking an opposite action such as transmitting.

Claims

1. A method comprising: One or more messages are received by a wireless device, the one or more messages including: The first parameter of the low-power wake-up signal LP-WUS that triggers the monitoring of the physical downlink control channel (PDCCH) on the cell; and Request the second parameter of the uplink signal of the on-demand system information block SIB1 of the cell; Based on the first parameter, the LP-WUS is monitored, wherein the wireless device skips monitoring of the PDCCH of the cell during the time period in which the wireless device is monitoring the LP-WUS; During the time period, the uplink signal requesting the on-demand SIB1 of the cell is sent based on the second parameter; Based on the transmission of the uplink signal, the monitoring of the LP-WUS is deactivated; and Based on the deactivation, the PDCCH is monitored in response to the uplink signal.

2. A method comprising: One or more messages are received by a wireless device, the one or more messages including: The first parameter of the low-power wake-up signal LP-WUS that triggers physical downlink control channel (PDCCH) monitoring; and The second parameter of the uplink signal; The LP-WUS is monitored based on the first parameter, wherein the wireless device skips monitoring of the PDCCH during the time period in which the wireless device is monitoring the LP-WUS; During the said time period, the uplink signal is transmitted based on the second parameter; and In response to the transmission of the uplink signal, the PDCCH is monitored for the response corresponding to the uplink signal.

3. The method according to any one of claims 1 to 2, wherein the wireless device monitors the PDCCH based on deactivating the monitoring of the LP-WUS during the time period.

4. The method according to any one of claims 1 to 3, wherein the wireless device monitors the PDCCH during the time period based on the first parameter ignoring the LP-WUS.

5. The method according to any one of claims 1 to 4, wherein the wireless device deactivates the monitoring of the LP-WUS in response to the transmission of the uplink signal / after the transmission of the uplink signal / based on the transmission of the uplink signal.

6. The method according to any one of claims 1 to 5, wherein the one or more messages comprise at least one of the following: System Information Block (SIB); and Radio Resource Control (RRC) information element IE.

7. The method according to any one of claims 1 to 6, wherein the wireless device is in an RRC idle state or an RRC inactive state.

8. The method according to any one of claims 1 to 7, wherein the wireless device receives an indication indicating activation of monitoring of the LP-WUS.

9. The method of claim 8, wherein the indication is included in the first parameter of the LP-WUS.

10. The method according to any one of claims 1 to 9, wherein the wireless device monitors the LP-WUS of a first cell in one or more cells.

11. The method according to any one of claims 1 to 10, wherein the wireless device transmits the uplink signal via a second cell of one or more cells.

12. The method according to any one of claims 1 to 11, wherein the first cell is the same as the second cell.

13. The method according to any one of claims 1 to 12, wherein the first cell is different from the second cell.

14. The method according to any one of claims 1 to 13, wherein the wireless device is in an RRC connection state.

15. The method according to any one of claims 1 to 14, wherein the wireless device monitors the LP-WUS while the wireless device maintains the active state of the first BWP of the cell.

16. The method of claim 15, wherein the wireless device stops monitoring the PDCCH of the first BWP while the wireless device maintains the active state of the first BWP of the cell.

17. The method according to any one of claims 15 to 16, further comprising activating the first BWP of the cell.

18. The method according to any one of claims 15 to 17, wherein the wireless device monitors the PDCCH on the first BWP based on the fact that the first BWP is the active BWP of the cell.

19. The method of any one of claims 15 to 18, wherein the first parameter includes a timer value associated with monitoring the LP-WUS.

20. The method of claim 19, further comprising starting the timer in response to at least one of the following: Receive the first parameter of the LP-WUS; and The first parameter includes an indication of activation of the monitoring of the LP-WUS.

21. The method according to any one of claims 19 to 20, further comprising suspending / stopping the timer in response to at least one of the following: Trigger the on-demand SIB1; and Send the uplink signal.

22. The method according to any one of claims 19 to 21, further comprising suspending / stopping the timer in response to receiving the LP-WUS indicating that monitoring of the PDCCH of one or more cells including the cell is required.

23. The method according to any one of claims 8 to 19 or 20 to 22, wherein the indication does not include an active BWP switching indication.

24. The method according to any one of claims 1 to 23, wherein the LP-WUS is transmitted based on on-off keyed OOK modulation, wherein, Based on the aforementioned OOK: The LP-WUS is sent an instruction to wake up in order to monitor the PDCCH of the cell; and The LP-WUS was not sent an instruction not to wake up to monitor the PDCCH.

25. The method of claim 24, wherein the wireless device receives the LP-WUS based on envelope detection of the LP-WUS, the envelope detection being based on the OOK modulation.

26. The method according to any one of claims 1 to 25, wherein the wireless device does not wake up to monitor the PDCCH in response to not receiving the LP-WUS.

27. The method according to any one of claims 1 to 26, wherein the LP-WUS is a downlink signal different from one or more DCIs, the one or more DCIs including at least one of the following: DCI format 2_6; and DCI format 2_7.

28. The method according to any one of claims 1 to 27, wherein the LP-WUS is a downlink signal received without using a Radio Network Temporary Identifier (RNTI), wherein the RNTI is at least one of the following: Used to receive the first RNTI in DCI format 2_6; and Used to receive the second RNTI in DCI format 2_7.

29. The method according to any one of claims 1 to 28, further comprising: In response to receiving the LP-WUS, the main receiver (MR) of the radio device is used to monitor the PDCCH of one or more cells including the cell.

30. The method according to any one of claims 1 to 29, comprising: During monitoring of the PDCCH, a DCI is received, which indicates uplink granting for the Physical Uplink Shared Channel (PUSCH) and / or downlink scheduling for the Physical Downlink Shared Channel (PDSCH).

31. The method according to any one of claims 1 to 30, comprising: During monitoring of the PDCCH, a DCI is received, which indicates a paging message for the wireless device.

32. The method according to any one of claims 1 to 31, wherein the wireless device uses the low-power receiver LR of the wireless device to monitor the LP-WUS.

33. The method according to any one of claims 1 to 32, wherein the first parameter includes at least one of the following: The transmission periodicity of the LP-WUS; The value of the periodic time duration during which the wireless device monitors the LP-WUS; The number of resource blocks (RBs); and The number of symbols in the LP-WUS.

34. The method of claim 33, wherein the number of symbols is less than the total number of symbols in a time slot.

35. The method of claim 33, wherein the number of symbols is equal to or greater than the total number of symbols in the time slot.

36. The method according to any one of claims 33 to 35, wherein the first parameter comprises at least one of the following: The time offset of the periodic time duration relative to the time reference point; The time offset of the starting symbol of the LP-WUS associated with the starting point of the periodic time duration; and The time offset of the end symbol of the LP-WUS associated with the end point of the periodic time duration.

37. The method of claim 36, wherein the time reference point is a system radio frame or subframe of the reference cell.

38. The method of claim 37, wherein the reference cell is the primary cell.

39. The method of claim 37, wherein the reference cell is a secondary cell.

40. The method according to any one of claims 37 to 39, wherein the reference cell is the cell on which the LP-WUS is configured using the first parameter.

41. The method according to any one of claims 8 to 19 or 20 to 40, wherein the indication includes at least one of the following: RRC message; MAC CE; and DCI.

42. The method of claim 41, wherein the DCI is a group common DCI.

43. The method of claim 42, wherein the group common DCI is DCI format 2_6.

44. The method according to any one of claims 42 to 43, wherein the group common DCI is CRC scrambled by at least one of the following: PS-RNTI; and The RNTI associated with the LP-WUS.

45. The method of claim 42 or 44, wherein the group common DCI is a DCI format different from at least one of the following: DCI format 2_6; and DCI format 2_7.

46. ​​The method of any one of claims 42 to 45, wherein the group common DCI includes a bit corresponding to the wireless device, the bit indicating whether the LP-WUS monitoring is enabled for the wireless device.

47. The method of claim 46, wherein the position of the bit corresponding to the wireless device is indicated by higher-level parameters in one or more messages.

48. The method of claim 41, wherein the DCI is a unicast DCI scrambled by at least one of the following: C-RNTI; and CS-RNTI.

49. The method according to any one of claims 41 to 48, wherein the DCI includes a DCI field indicating whether the LP-WUS monitoring is activated.

50. The method of claim 49, wherein the DCI field is a PDCCH monitoring adaptive field.

51. The method according to any one of claims 49 to 50, wherein the size of the DCI field is indicated by a high-level or RRC parameter in the one or more messages.

52. The method according to any one of claims 1 to 51, wherein the uplink signal comprises at least one of the following: Preamble; Detection Reference Signal (SRS); Scheduling request SR via the Physical Uplink Control Channel (PUCCH); and MACE CE.

53. The method of claim 52, wherein the second parameter of the uplink signal indicates that the preamble is used for a random access (RA) procedure, wherein the wireless device transmits the preamble based on initiating the RA procedure.

54. The method according to any one of claims 1 to 53, wherein the wireless device triggers the on-demand SIB1 request process based on at least one of the following: SIB1 was not detected; and The second parameter indicates that SIB1 is requested on demand.

55. The method according to any one of claims 1 to 54, wherein: Activating monitoring of the LP-WUS includes starting monitoring of the LP-WUS according to the first parameter; and Deactivating monitoring of the LP-WUS includes stopping monitoring of the LP-WUS.

56. The method according to any one of claims 1 to 55, wherein the response comprises at least one of the following: CRC is the first DCI scrambled by C-RNTI and with NDI inverted; and CRC is a second DCI scrambled by SI-RNTI; A random access response (RAR), the random access response including a preamble index corresponding to the uplink signal, wherein the uplink signal is a preamble.

57. The method according to any one of claims 1 to 56, wherein the wireless device receives one or more messages including the first parameter of the LP-WUS based on both a low-power wake-up radio (LR) and a master radio (MR) equipped on the wireless device.

58. The method according to any one of claims 1 to 57, further comprising: The wireless device receives a first message from the base station, the first message including a request for wireless access capability from the wireless device; as well as Send a second message to the base station regarding the wireless access capability of the wireless device for power-saving operation.

59. The method according to any one of claims 1 to 58, wherein the second message indicates that the wireless device supports at least one of the following: BWPLP-WUS configuration per bandwidth segment; LP-WUS configuration per community; LP-WUS configuration for each discontinuous reception DRX cell group; and Configure the LP-WUS entity for each media access control MAC entity.

60. The method according to any one of claims 1 to 59, wherein the second message indicates that the wireless device supports at least one of the following: LP-WUS configuration for BWP; LP-WUS configuration applicable to the cell; LP-WUS configuration for DRX cell groups; and LP-WUS configuration for MAC entities.

61. The method according to any one of claims 1 to 60, wherein the second message is indicated by frequency band or by frequency range FR.

62. An apparatus comprising: One or more processors; as well as A memory that stores instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to any one of claims 1 to 61.

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

Images