Low power wake-up signal reception

Abstract

A method can include receiving, by a wireless device, one or more radio resource control (RRC) messages. The messages can include first parameters of reference signals (RSs) of a cell including one or more downlink bandwidth parts (BWPs). A first downlink BWP, of the one or more downlink BWPs, can include first frequency resources. The messages can also include second parameters of a low power wake-up signal (LP-WUS) configured with second frequency resources. The method can also include monitoring, via the second frequency resources and for receiving the LP-WUS, the LP-WUS, using at least one of the RSs of the cell, based on: the LP-WUS being quasi-co-located (QCLed) with the at least one of the RSs of the cell and the second frequency resources being within the first frequency resources of the first downlink BWP. The first downlink BWP can be an active downlink BWP of the cell.

Description

TITLELow Power Wake-up Signal ReceptionCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 572,776, filed April 1 , 2024, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0003] FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

[0004] FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.

[0005] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

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

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

[0008] FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.

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

[0010] FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.

[0011] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.

[0012] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0013] FIG. 10A illustrates three carrier aggregation configurations with two component carriers.

[0014] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.

[0015] FIG. 11A illustrates an example of an SS / PBCH block structure and location.

[0016] FIG. 11 B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.

[0017] FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.

[0018] FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.

[0019] FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.

[0020] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.

[0021] FIG. 15 illustrates an example of a wireless device in communication with a base station

[0022] FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.

[0023] FIG. 17A, FIG. 17B, and FIG. 17C illustrate an aspect of an example embodiment according to the present disclosure.

[0024] FIG. 18A and FIG. 18B illustrate an aspect of an example embodiment according to the present disclosure.

[0025] FIG. 19 illustrates an aspect of an example embodiment according to the present disclosure.

[0026] FIG. 20 illustrates an aspect of an example embodiment according to the present disclosure.

[0027] FIG. 21A and FIG. 21B illustrate an aspect of an example embodiment according to the present disclosure.

[0028] FIG. 22 illustrates an aspect of an example embodiment according to the present disclosure.

[0029] FIG. 23 illustrates an aspect of an example embodiment according to the present disclosure.

[0030] FIG. 24A, FIG. 24B, and FIG. 24C illustrate an aspect of an example embodiment according to the present disclosure.

[0031] FIG. 25 illustrates an aspect of an example embodiment according to the present disclosure.

[0032] FIG. 26 illustrates an aspect of an example embodiment according to the present disclosure.

[0033] FIG. 27 illustrates an aspect of an example embodiment according to the present disclosure.

[0034] FIG. 28 illustrates an aspect of an example embodiment according to the present disclosure.

[0035] FIG. 29 illustrates an aspect of an example embodiment according to the present disclosure.

[0036] FIG. 30 illustrates an aspect of an example embodiment according to the present disclosure.

[0037] FIG. 31 illustrates an aspect of an example embodiment according to the present disclosure.

[0038] FIG. 32 illustrates an aspect of an example embodiment according to the present disclosure.

[0039] FIG. 33 illustrates an aspect of an example embodiment according to the present disclosure.

[0040] FIG. 34A, FIG. 34B, and FIG. 34C illustrate an aspect of an example embodiment according to the present disclosure.

[0041] FIG. 35 illustrates an aspect of an example embodiment according to the present disclosure.

[0042] FIG. 36 illustrates an aspect of an example embodiment according to the present disclosure.

[0043] FIG. 37 illustrates an aspect of an example embodiment according to the present disclosure.

[0044] FIG. 38 illustrates an aspect of an example embodiment according to the present disclosure.

[0045] FIG. 39 illustrates an aspect of an example embodiment according to the present disclosure.DETAILED DESCRIPTION

[0046] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the describedexemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0047] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0048] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and / or capabil ity(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations ora plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0049] In this disclosure, "a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of”, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0050] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celH , cell2} are: {celH }, {cell2}, and {celH, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least’) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0051] The term configured may relate to the capacity of a device whether the device is in an operational or non- operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0052] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

[0053] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

[0054] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element), or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVI E WMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, applicationspecific 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++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

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

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

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

[0058] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device maybe a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wirelessdevice encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0059] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

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

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

[0062] The RAN 104 maybe deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

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

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

[0066] As illustrated in FIG. 1 B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG. 1B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / i nter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.

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

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

[0069] The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more g NBs, illustrated as g NB 160A and g NB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

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

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

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

[0073] The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. 1 B, one g N B or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.

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

[0075] FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B maybe the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1B.

[0076] FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

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

[0078] The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-g NB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

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

[0080] The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and / or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

[0081] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through HybridAutomatic Repeat Request (HARQ) (e.g. , one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

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

[0083] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the g N B 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

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

[0085] The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g., with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.

[0086] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0087] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs maybe 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 activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0088] Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

[0089] FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:

[0090] -- a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;

[0091] - a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;

[0092] - a common control channel (CCCH) for carrying control messages together with random access;

[0093] - a dedicated control channel (DCCH) for carrying control messages to / from a specific the UE to configure the UE; and

[0094] - a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE.

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

[0096] - a paging channel (PCH) for carrying paging messages that originated from the PCCH;

[0097] - a broadcast channel (BCH) for carrying the MIB from the BCCH;

[0098] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;

[0099] -- an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and

[0100] -- a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.

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

[0102] - a physical broadcast channel (PBCH) for carrying the MIB from the BCH;

[0103] -- a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;

[0104] -- a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0105] - a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL- SCH and in some instances uplink control information (UCI) as described below;

[0106] -- a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and

[0107] -- a physical random access channel (PRACH) for random access.

[0108] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

[0109] FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

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

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

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

[0113] In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2Aand FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise 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., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station may request a handover to a cell of one of the neighboring base stationsbased on the reported measurements The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

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

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

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

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

[0118] RAN areas may be used to track the UE at the RAN level. Fora UE in RRC inactive 606 state, the UE maybe assigned a RAN notification area A RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell maybelong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE’s RAN notification area.

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

[0120] AgNB, such as gNBs 160 in FIG. 1B, maybe split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SOAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0121] In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (I EFT) block that transforms them into the time domain. The I EFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PARR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

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

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

[0124] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

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

[0126] FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

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

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

[0129] For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

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

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

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

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

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

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

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

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

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

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

[0140] FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

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

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

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

[0144] Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self-scheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or Rl) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.

[0145] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC1 1031, UC1 1032, and UC1 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC1 1071, UC1 1072, and UC1 1073, maybe transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell maybecome overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

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

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

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

[0149] FIG. 11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11 A). Bursts may be transmitted periodically (e g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 11 A is an example, and that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g , using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.

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

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

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

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

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

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

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

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

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

[0159] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE maybe configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

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

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

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

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

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

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

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

[0167] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT- RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.

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

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

[0170] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi colocated (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or spatial Receiving (Rx) parameters.

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

[0172] FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11 B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a 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.

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

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

[0175] In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g , a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (Rl).

[0176] FIG. 12A illustrates examples of three downlink beam management procedures: P1 , P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1 ). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). The UE and / or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

[0177] FIG. 12B illustrates examples of three uplink beam management procedures: U 1 , U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

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

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

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

[0181] FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 31313, and a Msg 4 1314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0182] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcastor multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRCJNACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 1 1311 and / or the Msg 31313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 21312 and the Msg 4 1314

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

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

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

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

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

[0188] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 31313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel -PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

[0189] RA-RNTI= 1 + sjd + 14 x tjd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id, where sjd maybe an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 < tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 0 < fjd < 8), and ul_carrierjd may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

[0190] The UE may transmit the Msg 31313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 21312). The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 31313 and the Msg 41314) may be used to increase the likelihood that the UE does not incorrectly use anidentity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

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

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

[0193] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322. The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention- free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 4 1314.

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

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

[0196] FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

[0197] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ AC K / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS 13A and 13B and / or the Msg 4 1314 illustrated in FIG. 13A.

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

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

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

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

[0202] The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; a slot format information; a preemption indication; a 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 a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

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

[0204] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), aSlot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0205] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g. , with compact DCI payloads). DCI format 0_1 may be used for scheduling PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 maybe used for scheduling PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1 J may be used for scheduling PDSCH in a cell (e.g., with more DCI payloads than DCI format 1 _0) . DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2 J may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

[0207] FIG. 1 A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a timefrequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs ata third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

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

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

[0210] As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

[0211] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL- SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or aphysical uplink shared channel (PUSCH) . The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

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

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

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

[0215] FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

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

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

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

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

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

[0221] The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and / or the reception processing system 1522 may be coupled to a memory (eg., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.

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

[0223] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the powerto the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0224] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP- OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments

[0225] FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

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

[0227] FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

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

[0229] A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g., the timer may be started or restarted from a value or may be started from zero and expire once it reaches the 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 may be used to measure a time period / window for a process. When the specification refers to an implementation and procedure related to 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 to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

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

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

[0232] In an example, a MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs may comprise: a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. The MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0233] In an example, when a MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may comprise: 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.

[0234] FIG. 17A shows an example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader of FIG. 17A, the LCID field may be six bits in length, and the L field may be eight bits in length. FIG. 17B shows example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader shown in FIG. 17B, the LCID field may be six bits in length, and the L field may be sixteen bits in length. When a MAC subheader corresponds to a fixed sized MAC CE or padding, the MAC subheader may comprise: a R field with a two-bit length and an LCID field with a multi-bit length. FIG. 17C shows an example of a MAC subheader with an R field and an LCID field. In the example MAC subheader shown in FIG. 17C, the LCID field maybe six bits in length, and the R field may be two bits in length.

[0235] FIG. 18A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. A MAC subPDU, comprising a MAC CE, may be placed before: a MAC subPDU comprising a MAC SDU, or a MAC subPDU comprising padding. FIG. 18B shows an example of a UL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. In an embodiment, a MAC subPDU comprising a MAC CE may be placed after all MAC subPDUs comprising a MAC SDU. In addition, the MAC subPDU may be placed before a MAC subPDU comprising padding.

[0236] In an example, a MAC entity of a base station may transmit one or more MAC CEs to a MAC entity of a wireless device. FIG. 19 shows an example of multiple LCIDs that may be associated with the one or more MAC CEs. The one or more MAC CEs comprise at least one of: a SP ZP CSI-RS Resource Set Acti vation / Deactivation MAC CE, a PUCCH spatial relation Activation / Deactivation MAC CE, a SP SRS Activation / Deactivation MAC CE, a SP CSI reporting on PUCCH Activation / Deactivation MAC CE, a TCI State Indication for UE-specific PDCCH MAC CE, a TCI State Indication for UE-specific PDSCH MAC CE, an Aperiodic CSI Trigger State Subselection MAC CE, a SP CSI- RS / CSI-IM Resource Set Activation / Deactivation MAC CE, a wireless device contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a Long DRX command MAC CE, an SCell activation / deactivation MAC CE (1 Octet), an SCell acti vation / deacti vation MAC CE (4 Octet), and / or a duplication activation / deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by a MAC entity of a base station to a MAC entity of a wireless device, may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0237] In an example, the MAC entity of the wireless device may transmit to the MAC entity of the base station one or more MAC CEs. FIG. 20 shows an example of the one or more MAC CEs. The one or more MAC CEs may comprise at least one of: a short buffer status report (BSR) MAC CE, a beam failure recovery (BFR) MAC CE, a truncated BFRMAC CE, a truncated enhanced BFR MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single entry PHR MAC CE, a multiple entry PHR MAC CE, a short truncated BSR, and / or a long truncated BSR etc. In an example, a MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 43 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a truncated enhanced BFR MAC CE.

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

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

[0240] A wireless device may activate / deactivate an SCell in response to receiving an SCell Activation / Deactivation MAC CE. In an example, a base station may transmit, to a wireless device, one or more messages comprising an SCell timer (e.g., sCellDeactivationTimer). In an example, a wireless device may deactivate an SCell in response to an expiry of the SCell timer.

[0241] When a wireless device receives an SCell Act! vation / Deactivation MAC CE activating an SCell, the wireless device may activate the SCell. In response to the activating the SCell, the wireless device may perform operations comprising SRS transmissions on the SCell; CQI / PMI / RI / CRI reporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; and / or PUCCH transmissions on the SCell. In response to the activating the SCell, the wireless device may start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in the slot when the SCell Activation / Deactivation MAC CE activating the SCell has been received. In an example, in response to the activating the SCell, the wireless device may (re-)initialize one or more suspended configured uplink grants of a configured grant Type 1 associated with the SCellaccording to a stored configuration. In an example, in response to activating the SCell, the wireless device may trigger PHR.

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

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

[0244] FIG. 21A shows an example of an SCell Activation / Deactivation MAC CE of one octet. A first MAC PDU subheader with a first LCID (e.g., '111010’ as shown in FIG. 19) may identify the SCell Activation / Deactivation MAC CE of one octet. The SCell Activation / Deactivation MAC CE of one octet may have a fixed size. The SCell Activation / Deactivation MAC CE of one octet may comprise a single octet. The single octet may comprise a first number of C-fields (e.g., seven) and a second number of R-fields (e.g., one).

[0245] FIG. 21 B shows an example of an SCell Activation / Deactivation MAC CE of four octets. A second MAC PDU subheader with a second LCID (e.g., '111001’ as shown in FIG. 19) may identify the SCell Activation / Deactivation MAC CE of four octets. The SCell Activation / Deactivation MAC CE of four octets may have a fixed size. The SCell Activation / Deactivation MAC CE of four octets may comprise four octets. The four octets may comprise a third number of C-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).

[0246] In FIG. 21A and / or FIG. 21B, a Ci field may indicate an activation / deactivation status of an SCell with an SCell index i if an SCell with SCell index i is configured. In an example, when the G field is set to one, an SCell with an SCell index i may be activated. In an example, when the Ci field is set to zero, an SCell with an SCell index i may bedeactivated In an example, if there is no SCell configured with SCell index i, the wireless device may ignore the C, field. In FIG. 21 A and FIG. 21 B, an R field may indicate a reserved bit. The R field may be set to zero.

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

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

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

[0250] FIG. 22 shows an example of BWP switching on a cell (e.g., PCell or SCell). In an example, a wireless device may receive, from a base station, at least one RRC message comprising parameters of a cell and one or more BWPs associated with the cell. The RRC message may comprise: RRC connection reconfiguration message (e.g., RRCReconfigu ration) RRC connection reestablishment message (e.g., RRCReestablishmenf); and / or RRC connectionsetup message (e.g . , RRCSetup). Among the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), one BWP as the default BWP (e.g., BWP 0). The wireless device may receive a command (e.g., RRC message, MAC CE or DCI) to activate the cell at an nth slot. In case the cell is a PCell, the wireless device may not receive the command activating the cell, for example, the wireless device may activate the PCell once the wireless device receives RRC message comprising configuration parameters of the PCell. The wireless device may start monitoring a PDCCH on BWP 1 in response to activating the cell.

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

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

[0253] In an example, on an inactive BWP for each activated serving cell configured with a BWP, a MAC entity may: not transmit on UL-SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignment and configured uplink grant of configured grant Type 2; and / or suspend any configured uplink grant of configured Type 1.

[0254] In an example, if a MAC entity receives a PDCCH for a BWP switching of a serving cell while a Random Access procedure associated with this serving cell is not ongoing, a wireless device may perform the BWP switching to a BWP indicated by the PDCCH. In an example, if a bandwidth part indicator field is configured in DCI format 1 J , the bandwidth part indicator field value may indicate the active DL BWP, from the configured DL BWP set, for DL receptions. In an example, if a bandwidth part indicator field is configured in DCI format 0_1 , the bandwidth part indicator field value may indicate the active UL BWP, from the configured UL BWP set, for UL transmissions.

[0255] In an example, for a primary cell, a wireless device may be provided by a higher layer parameter Defau It-DL- BWP a default DL BWP among the configured DL BWPs If a wireless device is not provided a default DL BWP by the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In an example, a wireless device may be provided by higher layer parameter bwp-lnactivityTimer, a timer value for the primary cell. If configured, the wireless device may increment the timer, if running, every interval of 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 if the wireless device may not detect a DCI format 1_1 for paired spectrum operation or if the wireless device may not detect a DCI format 1_1 or DCI format 0_1 for unpaired spectrum operation during the interval.

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

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

[0258] In an example, a set of PDCCH candidates for a wireless device to monitor is defined in terms of PDCCH search space sets. A search space set comprises a CSS set or a USS set. A wireless device monitors PDCCH candidates in one or more of the following search spaces sets: a TypeO-PDCCH CSS set configured by pdcch- ConfigSIBI in MIB or by searchSpaceSIBI in PDCCH-ConfigCommon or by search SpaceZero in PDCCH- ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a TypeOA-PDCCH CSS set configured by searchSpaceOtherSystemlnformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a Typel -PDCCH CSS set configured by ra-Se arch Space in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI, a MsgB-RNTI, or a TC-RNTI on the primary cell, a Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG, a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s), and a USS set configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS- RNTI(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

[0259] In an example, a wireless device determines a PDCCH monitoring occasion on an active DL BWP based on one or more PDCCH configuration parameters (e.g., based on example embodiment of FIG. 27 which will be described later) comprising: a PDCCH monitoring periodicity, a PDCCH monitoring offset, and a PDCCH monitoring pattern within a slot. For a search space set (SS s), the wireless device determines that a PDCCH monitoring occasion(s) exists in a slot with number n^fin a frame with number nfif (nf•is a numberof slots in a frame when numerology is configured. osis a slot offset indicated in the PDCCH configuration parameters (e.g., based on example embodiment of FIG. 27). ksis a PDCCH monitoring periodicity indicated in the PDCCH configuration parameters (e.g., based on example embodiment of FIG. 27). The wireless device monitors PDCCH candidates for the search space set for Tsconsecutive slots, starting from slot n^, and does not monitor PDCCHcandidates for search space set s for the next ks- Tsconsecutive slots. In an example, a USS at CCE aggregation level L G {1, 2, 4, 8, 16} is defined by a set of PDCCH candidates for CCE aggregation level L.

[0260] In an example, a wireless device decides, for a search space set s associa indexes for aggregation level L corresponding to PDCCH candidate ms naof the se active DL BWP of a serving cell corresponding to carrier indicator field value nclasnRNT| 0, Ap= 39827 for p mod 3 = 0, Ap= 39829 for p mod 3 = 1, Ap= 39839 for p mod 3 = 2, and D = 65537,' i = 0, ■■■ ,L - 1; A / CCEpis the number of CCEs, numbered from 0 to NCCE p- 1, in CORESET p; nCIis the carrier indicator field value if the wireless device is configured with a carrier indicator field byCrossCarrierSchedulingConfig for the serving cell on which PDCCH is monitored; otherwise, including for any CSS, nrr- 0; m,.n„, = 0,is the number of PDCCH candidates the wireless device is configured to monitor for aggregation level L of a search space set s for a serving cell corresponding to nc;; for anyover all configured nC]values for a CCE aggregation level L of search space set s; and the RNTI value used for nRNT, is the C-RNTI.

[0261] In an example, a wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set comprising a plurality of search spaces (SSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. A CORESET may be configured based on the example embodiment of FIG. 26 which will be described later. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common SSs, and / or number of PDCCH candidates in the UE-specific SSs) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The possible DCI formats may be based on example embodiments of FIG. 23.

[0262] FIG. 23 shows examples of DCI formats which may be used by a base station for transmitting control information to a wireless device or used by the wireless device for PDCCH monitoring. Different DCI formats may comprise different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In an example, DCI format 0_0 may be used to schedule PUSCH in one cell. DCI format 0_1 may be used to schedule one or multiple PUSCH in one cell or indicate CG-DFI (configured grant-Downlink Feedback Information) for configured grant PUSCH, etc. The DCI format(s) which the wireless device may monitor in a SS may be configured.

[0263] FIG. 24A shows an example of configuration parameters of a master information block (MIB) of a cell (e.g., PCell). In an example, a wireless device, based on receiving primary synchronization signal (PSS) and / or secondary synchronization signal (SSS), may receive a MIB via a PBCH. The configuration parameters of a MIB may comprise six bits (systemFrameNumbef) of system frame number (SFN), subcarrier spacing indication (subCarrierSpacingCommon), a frequency domain offset (ssb-SubcarrierOffset) between SSB and overall resource block grid in number of subcarriers, an indication (cellBarred) indicating whether the cell is bared, a DMRS position indication dmrs-TypeA- Position) indicating position of DMRS, parameters of CORESET and SS of a PDCCH (pdcch-ConfigSIB1) comprising a common CORESET, a common search space and necessary PDCCH parameters, etc.

[0264] In an example, a pdcch-ConfigSIB1 may comprise a first parameter (e.g., controlResourceSetZero) indicating a common ControlResourceSet (CORESET) with ID #0 (e.g., CORESET#0) of an initial BWP of the cell. controlResourceSetZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify a configuration of CORESET#0.

[0265] FIG. 24B shows an example of a configuration of CORESET O. As shown in FIG. 24B, based on a value of the integer of controlResourceSetZero, a wireless device may determine a SSB and CORESET#0 multiplexing pattern, a number of RBs for CORESETflO, a number of symbols for CORESET#0, an RB offset for CORESET#0.

[0266] In an example, a pdcch-ConfigSIB1 may comprise a second parameter (e.g., searchSpaceZero) indicating a common search space with ID #0 (e.g., SS#0) of the initial BWP of the cell. searchSpaceZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify a configuration of SS#0.

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

[0268] In an example, based on receiving a MIB, a wireless device may monitor PDCCH via SS#0 of CORESETflO for receiving a DCI scheduling a system information block 1 (SIB1 ). A SIB1 message may be implemented based on the example embodiment of FIG. 25. The wireless device may receive the DCI with CRC scrambled with a system information radio network temporary identifier (SI-RNTI) dedicated for receiving the SIB1.

[0269] FIG. 25 and FIG. 26 show examples of RRC configuration parameters of system information block (SIB). A SIB (e.g., SIB1) may be transmitted to all wireless devices in a broadcast way. The SIB may contain information relevant when evaluating if a wireless device is allowed to access a cell, information of paging configuration and / or scheduling configuration of other system information. A SIB may contain radio resource configuration information that is common for all wireless devices and barring information applied to a unified access control. In an example, a base station may transmit to a wireless device (or a plurality of wireless devices) one or more SIB information.

[0270] As shown in FIG 25, parameters of the one or more SIB information may comprise: one or more parameters (e.g., cel / Selectionlnfo) for cell selection related to a serving cell, one or more configuration parameters of a serving cell(e g., in Sen / ingCellConfigCommonSIB IE), and one or more other parameters. The Sen / ingCellConfigCommonSIB IE may comprise at least one of: common downlink parameters (e.g., in DownlinkConfigCommonSIB IE) of the serving cell, common uplink parameters (e.g., in UplinkConfigCommonSIB IE) of the serving cell, and other parameters.

[0271] As shown in FIG. 26, a SIB1 message may comprise scheduling information for other SIBs (e.g., SIB2, SIB3, SIB4, ...), e.g., by Sl-Schedulinglnfo IE. A Sl-Schedulinglnfo IE may comprise a Sl-RequestConfig IE fora normal uplink carrier (NUL) of a cell and a SI-RequestConfigSUL IE for a supplementary uplink carrier of the cell. A Sl- RequestConfig IE or a SI-RequestConfigSUL IE may indicate a RACH configuration (e.g., rach-OccasionsSI IE) for a corresponding SI request.

[0272] In an example, a DownlinkConfigCommonSIB IE may comprise parameters of an initial downlink BWP (initialDownlinkBWP IE) of the serving cell (e.g., SpCell). The parameters of the initial downlink BWP may be comprised in a BWP-DownlinkCommon IE (as shown in FIG. 27). The BWP-DownlinkCommon IE may be used to configure common parameters of a downlink BWP of the serving cell. The base station may configure the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET O of this serving cell in the frequency domain. The wireless device may apply the locationAndBandwidth upon reception of this field (e.g., to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET#0 until after reception of RRCSetup / RRCResume / RRCReestablishment.

[0273] In an example, the DownlinkConfigCommonSIB IE may comprise parameters of a paging channel configuration. The parameters may comprise a paging cycle value (T, by defaultPagingCycle IE), a parameter (nAndPagingFrameOffset IE) indicating total number N) of paging frames (PFs) and paging frame offset (PF_offset) in a paging DRX cycle, a number (Ns) for total paging occasions (POs) per PF, a first PDCCH monitoring occasion indication parameter (firstPDCCH-MonitoringOccasionofPO IE) indicating a first PDCCH monitoring occasion for paging of each PO of a PF. The wireless device, based on parameters of a PCCH configuration, may monitor PDCCH for receiving paging message.

[0274] In an example, the parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in SIB1 for paging in initial DL BWP. For paging in a DL BWP other than the initial DL BWP, the parameter first-PDCCH- MonitoringOccasionOfPO may be signaled in the corresponding BWP configuration.

[0275] FIG. 27 shows an example of RRC configuration parameters (e.g., BWP-DownlinkCommon IE) in a downlink BWP of a serving cell. A base station may transmit to a wireless device (or a plurality of wireless devices) one or more configuration parameters of a downlink BWP (e.g., initial downlink BWP) of a serving cell. As shown in FIG. 27, the one or more configuration parameters of the downlink BWP may comprise: one or more generic BWP parameters of the downlink BWP, one or more cell specific parameters for PDCCH of the downlink BWP (e.g., in pdcch-ConfigCommon IE), one or more cell specific parameters for the PDSCH of this BWP (e.g., in pdsch-ConfigCommon IE), and one or mor other parameters. A pdcch-ConfigCommon IE may comprise parameters of COESET #0 (e.g., contro / ResourceSetZero) which may be used in any common or UE-specific search spaces. A value of thecontrolResourceSetZero may be interpreted like the corresponding bits in MIB pdcch-ConfigSIB1. A pdcch- ConfigCommon IE may comprise parameters (e.g., in commonControlResourceSet) of an additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetld other than 0 for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESET#0. A pdcch-ConfigCommon IE may comprise parameters (e.g., in commonSearchSpaceLisf) of a list of additional common search spaces. Parameters of a search space may be implemented based on the example of FIG. 29 which will be described later. A pdcch-ConfigCommon IE may indicate, from a list of search spaces, a search space for paging (e.g., pagingSearchSpace), a search space for random access procedure (e.g., ra-SearchSpace), a search space for SIB1 message (e.g., searchSpaceSIBI), a common search spaceflO (e.g., searchSpaceZero), and one or more other search spaces.

[0276] As shown in FIG. 27, a control resource set (CORESET) may be associated with a CORESET index (e.g., ControlResourceSetld . A CORESET may be implemented based on example embodiments described above with respect to FIG. 14A and / or FIG. 14B. The CORESET index with a value of 0 may identify a common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and may not be used in the ControlResourceSet IE. The CORESET index with other values may identify CORESETs configured by dedicated signaling or in SIB1. The ControlResourceSetld is unique among the BWPs of a serving cell. A CORESET may be associated with coresetPoollndex indicating an index of a CORESET pool for the CORESET. A CORESET may be associated with a time duration parameter (e.g., duration) indicating contiguous time duration of the CORESET in number of symbols. In an example, as shown in FIG. 27, configuration parameters of a CORESET may comprise at least one of: frequency resource indication (e.g., frequencyDomainResources), a CCE-REG mapping type indicator (e.g., cce-REG-MappingType), a plurality of TCI states (e.g., tci-StatesPDCCH-ToAddList), an indicator (e.g., tci- PresentDCI-1-2-r16) indicating whether a TCI is present in a DCI, a CORESET pool index (e.g., coresetPoollndex), an indication (e.g., followllnifiedTCI-state) indicating whether to follow unified TCI state for the CORESET, an indication (e.g., applylndicatedTCI-State) indicating whether to apply the first indicated TCI state, the second indicated TCI state, or both TCI states, and the like. A TCI state may be implemented based on examples of FIG. 28 which will be described below in this specification.

[0277] FIG. 28 shows an example of RRC configuration of TCI states and PDSCH parameters.

[0278] In the example of FIG. 28, a wireless device may be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode PDSCH according to a detected PDCCH with DCI intended for the wireless device and the given serving cell, where M depends on the wireless device capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring a quasi co-location, which can also be referred to as quasi-colocation, relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS port of PDCCH or the CSI-RS port(s) of a CSI-RS resource. The quasi co-locationrelationship is configured by the higher layer parameter qcl-Type1 for the first DL RS, and qcl-Type2 for the second DL RS (if configured). For the case of two DL RSs, the QCL types shall not be the same, regardless of whether the references are to the same DL RS or different DL RSs.

[0279] In an example, the quasi co-location types corresponding to each DL RS are given by the higher layer parameter qcl-Type in QCL-Info and may take one of the following values:'typeA': {Doppler shift, Doppler spread, average delay, delay spread}'typeB': {Doppler shift, Doppler spread}'typeC: {Doppler shift, average delay}'typeD': {Spatial Rx parameter}

[0280] In an example, a wireless device may be configured with a list of up to 128 TCI-State configurations, within the higher layer parameter dl-OrJointTCI-StateList in PDSCH-Config for providing a reference signal for the quasi colocation for DM-RS of PDSCH and DM-RS of PDCCH in a BWP / CC, for CSI-RS, and to provide a reference, if applicable, for determining UL TX spatial filter for dynamic-grant and configured-grant based PUSCH and PUCCH resource in a BWP / CC, and SRS.

[0281] In an example, if the TCI-State or TCI-UL-State configurations are absent in a BWP of the CC, the wireless device may apply the TCI-State or TCI-UL-State configurations from a reference BWP of a reference CC configured by unifiedTCI-StateRef. The wireless device is not expected to be configured with td-StatesToAddModList, SpatialRelationlnfo or PUCCH-SpatialRelationlnfo, except SpatialRelationlnfoPos in a CC in a band, if the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList in any CC in the same band. The wireless device may assume that when the wireless device is configured with tci-StatesToAddModList in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16, or simultaneousSpatial-UpdatedList2-r16!the wireless device is not configured with dl-OrJointTCI-StateList or ul-TCI- StateList in any CC within the same band in the CC list.

[0282] In an example, a wireless device receives an activation command (e.g., a MAC CE), used to map up to 8 TCI states and / or pairs of TCI states, with one TCI state for DL channels / signals and / or one TCI state for UL channels / signals to the codepoints of the DCI field 'Transmission Configuration Indication' for one or for a set of CCs / DL BWPs, and / or up to 8 sets of TCI states, where each set is comprised of up to two TCI state(s) for DL and UL signals / channels, or up to two TCI state(s) for DL channels / signals and up to two TCI state(s) for UL channels / signals to the codepoints of the DCI field 'Transmission Configuration Indication' for one or for a set of CCs / DL BWPs, and if applicable, for one or for a set of CCs / UL BWPs. When a set of TCI state IDs are activated for a set of CCs / DL BWPs and if applicable, for a set of CCs / UL BWPs, where the applicable list of CCs is determined by the indicated CC in the activation command, the same set of TCI state IDs are applied for all DL and / or UL BWPs in the indicated CCs. If the activation command maps TCI-State(s) and / or TCI-UL-State(s) to only one TCI codepoint, the UE shall apply theindicated TCI-State(s) and / or TCI-UL-State(s) to one or to a set of CCs / DL BWPs, and if applicable, to one or to a set of CCs / UL BWPs once the indicated mapping for the one single TCI codepoint is applied.

[0283] In the example of FIG. 28, the field cell of a QCL-Info associated with a TCI state indicates the wireless device’s serving cell in which the referenceSignai is configured. If the field is absent, the referenceSignai is configured in the serving cell in which the TCI-State is applied by the wireless device. The RS may be located on a serving cell other than the serving cell for which the TCI-State is applied by the wireless device only if the qcl-Type is configured as typeC or typeD. If the referenceSignai is set to csi-rs and unifiedTCI-StateType is configured, either both cell and bwp- Id are present or both cell and bwp-ld are absent.

[0284] In the example of FIG. 28, the field bwp-ld of a QCL-Info associated with a TCI state indicates the DL BWP which the RS is located in If the field is absent, the RS is located in the DL BWP in which the TCI-State is applied by the wireless device.

[0285] In the example of FIG. 28, the field referenceSignai of a QCL-Info associated with a TCI state indicates a reference signal with which quasi-collocation information is provided.

[0286] In an example, when the bwp-ld or cell for QCL-TypeA / D source RS in a QCL-Info of the TCI state is not configured, the wireless device assumes that QCL-TypeA / D source RS is configured in the CC / DL BWP where TCI state applies.

[0287] In an example, when tci-PresentlnDCI is set as 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET, a wireless device configured with dl-OrJo / ntTCI-StateL / st with activated TCI-State or ul-TCI-StateList with activated TCI-UL-State receives DCI format 1_1 / 1_2 / 1_3 providing indicated TCI-State(s) and / or TCI-LIL-State(s) fora CC or all CCs in the same CC list configured by simultaneousU-TCI-UpdateList1-r17, simultaneousU-TCI-UpdateList2- r17, simultaneousU-TCI-UpdateList3-r17, simultaneousU-TCI-UpdateUst4-r17. The DCI format 1_1 / 1_2 can be with or without, if applicable, DL assignment. If the DCI format 1_1 / 1_2 / is without DL assignment, the UE can assume the following:CS-RNTI is used to scramble the CRC for the DCIThe values of the following DCI fields are set as follows:RV = all TsMCS = all '1'sNDI = 0Set to all '0's for FDRA Type 0, or all '1 's for FDRA Type 1 , or all '0's for dynamicSwitch (same as in Table 10.2-4 of [6, TS 38.213]).

[0288] In an example, after a wireless device receives an initial higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State and before application of an indicated TCI state from the configured TCI states, the wireless device assumes that DM-RS of PDSCH and DM-RS of PDCCH and the CSI-RS applying the indicated TCI state are quasi co-located with the SS / PBCH block the UE identified during the initial access procedure.

[0289] In an example, after a wireless device receives an initial higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State or ul-TCI-StateUst with more than one TCI-UL-State and before application of an indicated TCI state from the configured TCI states, the UE assumes that the UL TX spatial filter, if applicable, for dynamic-grant and configured-grant based PUSCH and PUCCH, and for SRS applying the indicated TCI state, is the same as that for a PUSCH transmission scheduled by a RAR UL grant or a MsgA PUSCH transmission during the initial access procedure.

[0290] In an example, after a wireless device receives a higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State as part of a Reconfiguration with sync procedure and before applying an indicated TCI state from the configured TCI states, the wireless device assumes that DM-RS of PDSCH and DM-RS of PDCCH, and the CSI-RS applying the indicated TCI state are quasi co-located with the SS / PBCH block or the CSI-RS resource the UE identified during the random access procedure initiated by the Reconfiguration with sync procedure.

[0291] In an example, after a wireless device receives a higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State or more than one TCI-UL-State as part of a Reconfiguration with sync procedure and before applying an indicated TCI state from the configured TCI states, the wireless device assumes that the UL TX spatial filter, if applicable, for dynamic-grant and configured-grant based PUSCH and PUCCH, and for SRS applying the indicated TCI state, is the same as that for a PUSCH transmission scheduled by a RAR UL grant or a MsgA PUSCH transmission during random access procedure initiated by the Reconfiguration with sync procedure.

[0292] In an example, if a wireless device receives a higher layer configuration of dl-OrJointTCI-StateList with a single TCI-State, which can be used as an indicated TCI state, the wireless device obtains the QCL assumptions from the configured TCI state for DM-RS of PDSCH and DM-RS of PDCCH, and the CSI -RS applying the indicated TCI state.

[0293] In an example, if a wireless device receives a higher layer configuration of dl-OrJointTCI-StateList with a single TCI-State or ul-TCI-StateListwith a single TCI-UL-State, that can be used as an indicated TCI state, the wireless device determines an UL TX spatial filter, if applicable, from the configured TCI state for dynamic-grant and configured- grant based PUSCH and PUCCH, and SRS applying the indicated TCI state.

[0294] In an example, when a wireless device configured with dl-OrJointTCI-StateUst would transmit a PUCCH with positive HARQ-ACK or a PUSCH with positive HARQ-ACK corresponding to the DCI carrying the TCI State indication and without DL assignment, or corresponding to the PDSCH scheduled by the DCI carrying the TCI State indication, and if the indicated T Cl State(s) is / are different from the previously indicated onefs), the indicated TCI-State(s) and / or TCI-UL-State(s) should be applied starting from the first slot that is at least beamAppTime symbols after the last symbol of the PUCCH or the PUSCH, and if the wireless device receives more than one indicated TCI state for a CC / BWP to be applied starting from the first slot that is at least beamAppTime symbols after the last symbol of the PUCCH or the PUSCH, the indicated TCI state carried in the latest DCI in time corresponding to positive HARQ-ACK value is applied. The first slot and the beamAppTime symbols are both determined on the active BWP with thesmallest SCS among the BWP(s) from the CCs applying the indicated TCI-State(s) or TCI-UL-State(s) that are active at the end of the PUCCH or the PUSCH carrying the positive HARQ-ACK.

[0295] In an example, when a wireless device would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, the indicated mapping between TCI states and codepoints of the DCI field 'Transmission Configuration indication' should be applied starting from the first slot that is after slot n + 3Nobtframe,IJ• kmcwhere [ is the SCS configuration for the PUCCH and piKmncis thesubcarrier spacing configuration for kmacwith a value of 0 for frequency range 1 , and / cmacis provided by K-Mac or / rniac= 0 if K-Mac is not provided. If tci-PresentlnDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET scheduling the PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL if applicable, after a wireless device receives an initial higher layer configuration of T Cl states and before reception of the activation command, the wireless device may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the SS / PBCH block determined in the initial access procedure with respect to qcl-Type set to 'typeA', and when applicable, also with respect to qcl-Type set to 'typeD'.

[0296] In an example, if a wireless device is configured with the higher layer parameter tci-PresentlnDCI that is set as 'enabled' for the CORESET scheduling a PDSCH, the wireless device assumes that the TCI field is present in the DCI format 1_1 or format 1_3 of the PDCCH transmitted on the CORESET. If a wireless device is configured with the higher layer parameter tci-PresentDCI-1-2 for the CORESET scheduling the PDSCH, the wireless device assumes that the TCI field with a DCI field size indicated by tci-PresentDCI-1-2 is present in the DCI format 1_2 of the PDCCH transmitted on the CORESET. If a wireless device is configured with the higher layer parameter tci-PresentlnDCI that is set as 'enabled' for the CORESET scheduling the multicast PDSCH, the UE assumes that the TCI field is present in the DCI format 4_2 of the PDCCH transmitted on the CORESET. If the PDSCH is scheduled by a DCI format not having the TCI field present, and the time offset between the reception of the DL DCI and the corresponding PDSCH of a serving cell is equal to or greater than a threshold timeDurationForQCL if applicable, where the threshold is based on reported wireless device capability, for determining PDSCH antenna port quasi co-location, the wireless device assumes that the TCI state or the QCL assumption for the PDSCH is identical to the TCI state or QCL assumption whichever is applied for the CORESET used for the PDCCH transmission within the active BWP of the serving cell.

[0297] FIG. 29 shows an example of configuration of a search space (e g., SearchSpace IE). In an example, one or more search space configuration parameters of a search space may comprise at least one of: a search space ID (searchSpaceld), a control resource set ID (controlResourceSetld), a monitoring slot periodicity and offset parameter (monitoringSlotPeriodicityAndOffset), a search space time duration value (duration), a monitoring symbol indication (monitoringSymbolsWithinSlot), a number of candidates for an aggregation level (nrofCandidates), and / or a SS type indicating a common SS type ora UE-specific SS type (searchSpace Type). The monitoring slot periodicity and offset parameter may indicate slots (e.g., in a radio frame) and slot offset (e.g., relative to a starting of a radio frame) forPDCCH monitoring. The monitoring symbol indication may indicate on which symbol(s) of a slot a wireless device may monitor PDCCH on the SS. The control resource set ID may identify a control resource set on which a SS may be located.

[0298] In an example, a wireless device, in RRCJDLE or RRC_I NACTIVE state, may periodically monitor paging occasions (POs) for receiving paging message for the wireless device. Before monitoring the PCs, the wireless device, in RRC_I DLE or RRC_I NACTIVE state, may wake up at a time before each PO for preparation and / or turn all components in preparation of data reception (warm up). The gap between the waking-up and the PO may be long enough to accommodate all the processing requirements. The wireless device may perform, after the warming up, timing acquisition from SSB and coarse synchronization, frequency and time tracking, time and frequency offset compensation, and / or calibration of local oscillator. After that, the wireless device may monitor a PDCCH for a paging DCI in one or more PDCCH monitoring occasions based on configuration parameters of the PCCH configuration configured in SIB1. The configuration parameters of the PCCH configuration may be implemented based on example embodiments described above with respect to FIG. 25.

[0299] / / background on SSBs

[0300] In an example, a base station may transmit one or more SSBs periodically to a wireless device, or a plurality of wireless devices. The wireless device (in RRC_I DLE state, RRC_I NACTIVE state, or RRC_CONNECTED state) may use the one or more SSBs for time and frequency synchronization with a cell of the base station. An SSB, comprising a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH), and a PBCH DM-RS, maybe transmitted based on example embodiments described above with respect to FIG. 11 A. An SSB may occupy a number (e.g ., 4) of OFDM symbols as shown in FIG. 11 A. The base station may transmit one or more SSBs in a SSB burst, e.g., to enable beam-sweeping for PSS / SSS and PBCH. An SSB burst comprises a set of SSBs, each SSB potentially transmitted on a different beam. SSBs in the SSB burst may be transmitted in time-division multiplexing fashion. In an example, an SSB burst may always be confined to a 5ms window and is either located in first-half or in the second half of a 10ms radio frame. In this specification, an SSB burst may be equivalently referred to as a transmission window (e.g., 5ms) in which the set of SSBs are transmitted.

[0301] In an example, the base station may indicate a transmission periodicity of SSB via RRC message (e.g., ssb- PeriodicitySen / ingCell in ServingCellConfigCommonSIB of SIB1 message, or ServingCellConfigCommon of a serving cell). A candidate value of the transmission periodicity may be in a range of {5ms, 10ms, 20ms, 40ms, 80ms, 160ms). The maximum number of candidate SSBs (Lmax) within an SSB burst depends upon the carrier frequency / band of the cell. In an example, Lma=4 if fc<=3GHz, wherein fcis the carrier frequency of the cell. Lmax=8 if 3GHz<fc<=6GHz. Lmax =64 if fc>=6GHz, etc.

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

[0303] FIG. 30 shows an example of starting OFDM symbol index determination.

[0304] As shown in FIG 30, starting OFDM symbol indexes of SSBs in a SSB burst, for a cell configured with 15 kHz and carrier frequency fc<3G Hz (Lmax=4), are 2, 8, 16, and 22. OFDM symbols in a half-frame are indexed with the first symbol of the first slot being indexed as 0. Starting OFDM symbol indexes of SSBs in a SSB burst, for a cell configured with 15 kHz and carrier frequency 3GHz<fc<6GHz (Lmax=8), are 2, 8, 16, 22, 30, 36, 44 and 50, etc. In an example, when the base station is not transmitting the SSBs with beam forming, the base station may transmit only one SSB by using the first SSB starting position.

[0305] FIG. 31 shows an example of SSB transmission of a cell by a base station. In the example of FIG. 31 , a SOS of the cell is 15 kHz, and the cell is configured with 3GHz<fc<=6GHz. Based on the example embodiment of FIG. 31, maximum number of candidate SSBs in a SSB burst is 8 (Lmax=8). As shown in FIG. 31 , SSB#1 starts at symbol#2 of 70 symbols in 5ms, SSB#2 starts at symbol#8, SSB#3 starts at symbol#16, SSB#4 starts at symbol#22, SSB#5 starts at symbol#30, SSB#6 starts at symbol#36, SSB#7 starts at symbol#44, and SSB#8 starts at symbol 50. The SSB burst is transmitted in the first half (not the second half as shown in FIG. 31) of a radio frame with 10 ms.

[0306] In an example, the SSB bust (also for each SSB of the SSB burst) may be transmitted in a periodicity. In the example of FIG. 31, a default periodicity of a SSB burst is 20 ms, e.g. , before a wireless device receives an SIB1 message for initial access of the cell. The base station, with 20 ms transmission periodicity of SSB (or SSB burst), may transmit the SSB burst in the first 5 ms of each 20 ms. The base station does not transmit the SSB burst in the rest 15 ms of the each 20 ms.

[0307] In an example, a base station may transmit RRC messages (e.g., SIB1 and / or ServingC llConfigCommon IE) indicating cell specific configuration parameters of SSB transmission of a serving cell (e.g., a PCell ora SCell). The cell specific configuration parameters may comprise a value for a transmission periodicity (ssb-PeriodicityServingCelfj of a SSB burst, locations of a number of SSBs (e.g., active SSBs), of a plurality of candidate SSBs, comprised in the SSB burst. The plurality of candidate SSBs may be implemented based on example embodiments described above with respect to FIG. 30. The cell specific configuration parameters may comprise position indication of a SSB in a SSB burst (e g., ssb-PositionsInBurst). The position indication may comprise a first bitmap (e.g., groupPresence) and a second bitmap (e.g., inOneGroup) indicating locations of a number of SSBs comprised in a SSB burst.

[0308] In an example, a base station may transmit a Master Information Block (MIB) on PBCH, to indicate configuration parameters (for CORESET#0) fora wireless device monitoring PDCCH for receiving a SIB1 message. The base station may transmit a MIB message with a transmission periodicity of 80 millisecond (ms). The same MIB message may be repeated (according to SSB periodicity) within the 80 ms. Contents of a MIB message are same over 80 ms period. The same MIB is transmitted over all SSBs within a SS burst. In an example, PBCH may indicate that there is no associated SIB1 , in which case a wireless device may be pointed to another frequency from where to search for an SSB that is associated with a SIB1 as well as a frequency range where the wireless device may assume no SSB associated with SIB1 is present. The indicated frequency range may be confined within a contiguous spectrum allocation of the same operator in which SSB is detected.

[0309] In an example, a base station may transmit a SIB1 message with a periodicity of 160 ms. The base station may transmit the same SIB1 message with variable transmission repetition periodicity within 160 ms. The default transmission repetition periodicity of SIB1 is 20 ms. The base station may determine an actual transmission repetition periodicity based on network implementation. In an example, forSSB and CORESET multiplexing pattern 1, SIB1 repetition transmission period is 20 ms. For SSB and CORESET multiplexing pattern 2 / 3, SIB1 transmission repetition period is the same as the SSB period. SIB1 may comprise information regarding the availability and scheduling (e.g., mapping of SIBs to SI message, periodicity, Si-window size) of other SIBs, an indication whether one or more SIBs are only provided on-demand and in which case, configuration parameters needed by a wireless device to perform an SI request.

[0310] In an example, a base station may transmit SSBs over each serving cell (e.g., a PCell or an SCell) of multiple serving cells configured for a wireless device. The base station may transmit SSBs over some serving cells of the multiple serving cells and may not transmit SSBs over other serving cells of the multiple serving cells. A serving cell without SSBs may be referred to as an SSB-less serving cell. A serving cell with SSBs always transmitted by the base station maybe referred to as an always-on-SSB serving cell. In addition to always-on SSB and SSB-less, a base station may transmit SSBs over a serving cell based on indication from a wireless device, or from another base station, and / or triggered by the base station itself (e.g., by transmitting a SCell activation / deactivation MAC CE). When there is no indication from the wireless device or from another base station or there is no trigger from the base station, the base station may stop transmitting the SSBs. The SSBs transmitted / stopped upon a request may be referred to as on- demand SSBs.

[0311] FIG. 32 shows examples of a variety of SSB transmissions.

[0312] In an example, a base station may configure a serving cell (e.g., a PCell or a SCell, Cell 1 in FIG. 32) with always-on SSBs, in which case, the base station keeps transmitting the SSBs with periodicity (e.g., ssb- PeriodicitySen / ingCell) based on configuration parameters of the SSBs. The SSBs may be transmitted in a way that a number (e.g., indicated by ssb-PositionsInBurst of SSBs are comprised in a SSB burst and the SSB burst is transmitted periodically according to the periodicity, e.g., according to example of FIG. 31. In an example, the always- on SSBs may be mandatorily configured on a PCell, and optionally configured on a SCell. The wireless device may obtain time and / or frequency synchronization (and / or beam alignment) with the serving cell based on the periodically transmitted SSBs. Always transmitting SSBs may increase power consumption of the base station.

[0313] As shown in FIG. 32, a base station may configure a serving cell (e.g., a SCell, Cell 2 in FIG. 32) without SSB transmission, e.g., in order to reduce power consumption of the serving cell. The wireless device may refer to another serving cell (e.g., a PCell or PSCell, or a SCell, Cell 1 in FIG. 32) for obtaining time and / or frequency synchronization with this serving cell. The PCell / PSCell / SCell used as the reference (e.g., or a SSB reference cell) of SSBs of this serving cell may be configured by RRC messages of the serving cell. The SSB reference cell may be intra-band (in the same frequency band) deployed with this serving cell or may be inter-band (in different frequency bands) deployed withthis serving cell. The SSB-less configuration for a serving cell may be limited to cases when there is always an SSB reference cell in carrier aggregation (CA) or dual connectivity (DC) deployment and / or when 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 a serving cell without SSB transmissions may reduce power consumption of the base station.

[0314] As shown in FIG. 32, a base station may configure a serving cell (e.g., a SCell, e.g., Cell 3) with on-demand SSB transmissions, e.g., in order to provide SSBs for time / frequency synchronization and / or parallelly reduce power consumption of the serving cell especially when there is no SSB reference cell for this serving cell (e.g., due to a single cell deployment, or time / frequency synchronization error between the SSB reference cell and this serving cell being greater than the threshold). There are multiple ways of providing the on-demand SSBs for this serving cell.

[0315] As a first way (as shown in FIG. 32) of providing the on-demand SSBs for a serving cell, the base station may trigger to transmit the on-demand SSB based on receiving an uplink wake up signal (WUS) from a wireless device. The WUS may be based on existing technologies (e.g., a preamble, an SRS, and / or a SR, etc.), or a new signal designed specifically for the on-demand SSB request. The wireless device may trigger the transmission of the WUS based on traffic loading and / or power level of the wireless device. In an example, the wireless device may trigger the transmission of the WUS based on channel measurement of discovery reference signals (DRSs) (if configured) of the serving cell.

[0316] In an example, a DRS may be a simplified SSB with only PSS and without SSS and PBCH, a simplified SSB with only SSS and without PSS and PBCH, or a CSI-RS, or a position RS, or a newly defined RS specifically for the on- demand SSB request.

[0317] In an example, before triggering the on-demand SSB for the serving cell, the base station may (optionally) transmit the DRSs for facilitating the wireless device to perform the channel measurement (which may be used by the wireless device to determine whether to trigger the transmission of the WUS). When receiving the WUS (e.g., indicating wakeup), the base station may start to transmit the on-demand SSBs. When receiving the WUS (e.g., indicating go-to- sleep) or when not receiving the WUS indicating wakeup on a WUS occasion, the base station may stop (or skip) transmitting the on-demand SSBs. Allowing the wireless device to request on-demand SSB transmissions (or request stopping the on-demand transmissions) may enable the base station to stop SSBs transmissions for power / energy saving when there is no wireless device active in this serving cell.

[0318] As a second way (as shown in FIG. 32) of providing the on-demand SSBs for a serving cell, the base station may trigger to transmit the on-demand SSB by activating the SCell. The base station may activate the SCell for a wireless device by transmitting a SCell activation / deactivation MAC CE (e.g., based on examples of FIG. 21 A and / or FIG. 21 B.). Before the SCell is activated, the base station may skip (or may stop / refrain from) transmitting the on- demand SSBs. After the SCell is activated, the base station may start transmitting the on-demand SSBs. The base station may determine when / whether to activate the SCell (together with the on-demand SSB transmissions) based ontraffic load / request of wireless device(s) and / or requests from another base station via backhaul link In an example, the DRSs described above may be optionally transmitted by the base station. The wireless device may transmit channel measurements of the serving cell based on the DRSs to help the base station to decide when / whether to activate the serving cell.

[0319] During 3GPP Rel. 15 / 16 / 17 standardization work, a plurality of power saving technologies used for a wireless device have been specified, e.g., SCell dormancy, DRX, wake-up signal based DRX (where the wake-up signal is transmitted as a DCI with CRC scrambled by PS-RNTI, DCP, e.g.,), SSSG switch-based power saving, PDCCH skipping based on DCI, paging early indication (PEI) based paging monitoring, etc.

[0320] Recent low power receiver technologies have been developed to further reduce power consumption of a wireless device for communication with a base station on one or more cells. In an example, in addition to the plurality of power saving technologies specified in 3GPP Rel. 15 / 16 / 17 standard, a wireless device may be equipped with a low power receiver (LR), in addition to a main receiver (MR).

[0321] The MR of the wireless device may be used for receiving NR SSBs / PDCCHs / PDSCHs, RRM, RLM, BFR, CSI measurements, etc., as does a wireless device implemented according to 3GPP Rel.15 / 16 / 17 standards, while the LR may be used by the wireless device to monitor / receive a low power wake-up signal (LP-WUS) and / or a low power synchronization signal (LP-SS). The LP-SS / LP-WUS may be simpler than existing NR downlink signals (e.g., SSB, CS l_RS, PDCCH / PDSCH / DRMR, etc.). The LP-SS / LP-WUS may be transmitted with on-off keying (OOK), amplitude shift keying (ASK), and / or frequency shift keying (FSK) modulation. The LR may spend less power than the MR, e.g., when the LR uses non-coherent envelope based signal detection for receiving an LP-WUS and / or LP-SS, while the MR uses coherent detection for receiving BPSK / QPSK / QAM modulated NR channels / signals. The receiver used by the LR and based on the non-coherent envelop detection of the LP-WUS may be referred to as a lower power wake up receiver (LP-WUR).

[0322] The wireless device may not power on the MR for time / frequency synchronization, system information reception, and / or paging message reception, etc., before receiving the LP-WUS by using the LR, e.g., in RRC_I DLE state.

[0323] The wireless device may not use the MR for PDCCH monitoring (except when the wireless device periodically wakes up to perform RRM / RLM / BFD / CSI measurement / report), e.g., before receiving the LP-WUS by using the LR, e.g., in RRC_CONNECTED state.

[0324] When a paging ratio is low for the wireless device equipped with LR and MR, the wireless device may mostly power on the LR and power off the MR, therefore saving power consumption of the wireless device in RRC_I DLE state.

[0325] Similarly, when data arrival is sparse for the wireless device equipped with LR and MR, the wireless device may mostly use the LR for monitoring LP-WUS and skip monitoring PDCCHs by the MR, therefore saving power consumption of the wireless device in RRC_CONNECTED state.

[0326] FIG. 33 shows an example of power saving technologies of a wireless device using LR and MR In the example of FIG. 33, a wireless device may be equipped with an LR and an MR.

[0327] In an example, the LR and the MR may be two different receivers physically, e.g., with separate RF modules and / or baseband processors.

[0328] In an example, the LR and the MR may be two different receivers virtually, e.g., sharing some of the RF modules and / or the baseband processors.

[0329] In the example of FIG. 33, the wireless device may be configured (e.g., by broadcast message (SIB1 / SIB2 / ... ) or unicast message (e.g., UE specific RRC message) with one or more configuration parameters of a LP-WUS (and / or a LP-SS). The one or more configuration parameters may comprise a transmission periodicity (e.g., LP-WUS periodicity) of the LP-WUS, a value of a periodic time duration, during which the wireless device monitors the LP-WUS, a frequency resource indication (e.g., a number of RBs), and / or a number of symbols of the WUS.

[0330] In the example of FIG. 33, the wireless device may monitor (e.g., trying to detect a presence of the LP-WUS according to the one or more configuration parameters) the LP-WUS periodically by using the LR. The base station may not transmit the LP-WUS, e.g., when there is no paging / data transmission for the wireless device. Before receiving the LP-WUS by the LR, the wireless device may not power on the MR, or maintain the MR in a sleep mode (e.g., ultradeep sleep, deep sleep, light sleep, micro-sleep, etc.), or may not monitor PDCCHs of one or more cells by using the MR (e.g., except using the MR for RRM / RLM / B FR / CS I measurement over SSBs / CSI-RSs).

[0331] In the example of FIG. 33, in response to receiving the LP-WUS by using the LR, the wireless device may transition the MR from the sleep state to an active state (e.g., for time / frequency synchronization, paging / PEI / DCP / PDCCH monitoring, etc.). The wireless device may take some time (e.g., a transition gap, a ramp-up time, etc.) for the transitioning of the MR from the sleep state to the active state. Length of the transition gap may depend on the wireless device capability of waking up the MR and / or may depend on which sleep state the MR is in before receiving the LP-WUS. A typical ramp-up time for the MR transitioning from the ultra-deep sleep state to the active state may be 400 milliseconds, or 800 milliseconds. A typical ramp-up time for the MR transitioning from the deep sleep state to the active state may be several ten milliseconds. A typical ramp-up time for the MR transitioning from the light / micro sleep state to the active state may be several milliseconds, etc.

[0332] In an example, after the transition gap, the MR may start to perform time / frequency synchronization based on SSB / TRS / CSI-RS, e.g., if the wireless device is in RRCJDLE state or RRC_I NACTIVE state. After performing the time / frequency synchronization, the wireless device may monitor PEI to determine whether to monitor PO for receiving a paging message, if the PEI is configured by the base station, or the wireless device may monitor the PO for receiving the paging message, if the PEI is not configured by the base station.

[0333] In an example, after the transition gap, the MR may start to monitor PDCCHs of the cell, e.g., if DCP is not configured by the base station. If DCP is configured by the base station, the MR of the wireless device may monitorDCP and determine whether to monitor PDCCHs based on whether the DCP indicates a wake-up or a go-to-sleep (or whether the DCP indicates to start a DRX on duration timer of a DRX configuration of the wireless device.

[0334] Based on example of FIG. 33, compared with a wireless device implementing 3GPP Rel.15 / 16 / 17 power saving technologies, a wireless device, equipped with LP-WUR, may reduce power consumption for PDCCH monitoring and / or paging monitoring by using a LR (for a detection of a LP-WUS) to determine whether to wake up a MR for normal NRsignal / channel reception / monitoring.

[0335] In an example, the LP-WUS monitoring may be combined with DCP-based power saving operation for further reducing power consumption of the wireless device.

[0336] In an example, a base station may configure frequency resources of a LP-SS / LP-WUS in a NR carrier / band. There are several ways / scenario of the frequency resource configuration for the LP-SS / LP-WUS. FIG. 34A, FIG 34B and / or FIG. 34C show examples of the LP-SS / LP-WUS configuration in frequency domain.

[0337] FIG. 34A shows an example of frequency resource configuration of the LP-SS / LP-WUS. In the example of FIG. 34A, the frequency resources (e.g., Bandwidth) of the LP-SS / LP-WUS is configured to be located within a frequency carrier of a serving cell (e.g., cell 1 in the example of FIG. 34A). The frequency resources (e.g., Bandwidth) of the LP-SS / LP-WUS is configured to be outside of a frequency carrier of another cell (e.g., cell 2 in the example of FIG. 34A). Configuring the frequency resources of the LP-SS / LP-WUS within a bandwidth of a serving cell may reduce resource usage for the LP-SS / LP-WUS transmission or allow the wireless device to share / reuse one or more receiving parameters / configurations (e.g., RF filter, baseband processer, etc.,) of NR channels for receptions / monitoring the LP- SS / LP-WUS. However, sharing the bandwidth configured for NR channels with the LP-SS / LP-WUS may reduce resources for the NR channels, and / or increase scheduling limitation of the base station.

[0338] FIG. 34B shows an example of frequency resource configuration of the LP-SS / LP-WUS. In the example of FIG. 34B, the frequency resources (e.g., Bandwidth) of the LP-SS / LP-WUS is configured to partially overlap with (e.g., the edge of) a frequency carrier of a serving cell (e.g., cell 1 in the example of FIG. 34B). The frequency resources (eg., Bandwidth) of the LP-SS / LP-WUS is configured to be outside of a frequency carrier of another cell (e.g., cell 2 in the example of FIG. 34B). Configuring the frequency resources of the LP-SS / LP-WUS partially overlapping with a NR carrier bandwidth may solve the scheduling-limitation problem of FIG. 34A to some extent, since the overlapping part of the LP-SS / LP-WUS and the NR bandwidth only occurs at the edge of the NR bandwidth which does not impact too much on the frequency resources in the center of the NR bandwidth.

[0339] FIG. 34C shows an example of frequency resource configuration of the LP-SS / LP-WUS. In the example of FIG. 34C, the frequency resources (e.g., bandwidth) of the LP-SS / LP-WUS is configured to be outside of a frequency carrierof a serving cell (e.g., cell 1 in the example of FIG. 34C). The frequency resources (e.g., bandwidth) of the LP- SS / LP-WUS is configured to be outside of a frequency carrier of another cell (e.g., cell 2 in the example of FIG. 34C). In an example, the LP-SS / LP-WUS may be configured on the same frequency band of cell 1 , or on a frequency band different from cell 1. Configuring the frequency resources of the LP-SS / LP-WUS not overlapping with a NR carrierbandwidth may solve the scheduling-limitation problem of FIG. 34A or FIG. 34B entirely. However, using frequency resources, separately from the NR carrier bandwidth, for the LP-SS / LP-WUS, may increase deployment cost and complexity for network operators.

[0340] Different frequency allocation schemes / scenario, described above with respect to FIG. 34A, FIG. 34B and / or FIG. 34C may be beneficial for different wireless network operators in different conditions, and / or be up to the wireless network operators’ decisions. Allowing multiple frequency allocation schemes / scenario may enable the wireless network operators to flexibly deploy the LP-SS / LP-WUS suitable for them based on their interests.

[0341] In existing technologies, a base station may use beam forming technologies, e.g., which is commonly used for NR channel transmissions (e.g., as shown in FIG. 12A and / or FIG. 12B), for the transmission of the LP-SS / LP-WUS for improving the coverage A beam forming technology may be implemented based on a transmission configuration indicator (TCI) state for PDCCH / CORESET, e.g., as shown in FIG. 27, or for PDSCH, e.g., as shown in FIG. 28. The coverage of the LP-SS / LP-WUS may not easily be designed as same as the legacy NR channels, since the LP-SS / LP- WUS is transmitted with OOK modulation by the base station and / or is received based on non-coherent envelop detection by the wireless device. However, the NR channels / signals are designed with OFDM modulation and / or DM- RS-based coherent detection by the wireless device

[0342] In this specification, A NR channel / signal may be an SSB / PDSCH / PDCCH / CSI-RS / DM-RS for downlink transmission from the base station to the wireless device. A NR channel / signal may be a preamble / PUSCH / PUCCH / SRS / DM-RS for uplink transmission from the wireless device to the base station. The NR channel / signal, transmitted with large bandwidth and designed based on OFDM modulation and coherent detection, is different from the LP-SS / LP-WUS transmitted with narrow bandwidth and based on OOK modulation and non-coherent detection (or envelop detection).

[0343] In existing technologies, a Tx / Rx beam may be referred to as a transmission configuration indicator (TCI) state. A TCI state may be identified by a TCI state ID and / or may be associated with a reference signal (e.g., SSB / CSI- RS / SRS) When a NR channel / signal is indicated with a TCI state, the wireless device uses a spatial domain filter for receiving / transmitting the NR channel / signal as the same one used for receiving / transmitting the reference signal associated with the TCI state. NR channels / signals on different BWPs / cells may be configured / activated with different TCI states, e.g., when different BWPs / cells are deployed in different frequency bands, or with different central frequency, or with different number of TRPs. The wireless device may maintain activated TCI states on an active BWP per cell (or per cell group). A TCI state may be implemented based on the one or more examples with respect to FIG. 27 and / or FIG. 28.

[0344] When considering multiple frequency deployments of LP-SS / LP-WUS as shown in FIG. 34A, FIG. 34B and / or FIG. 34C, the wireless device, by using existing technologies, may have difficulties in determining a beam / TCI state used for receiving the LP-SS / LP-WUS.

[0345] FIG. 35 shows an example issue of beam determination for LP-SS / LP-WUS reception.

[0346] In the example of FIG. 35, a base station may transmit to a wireless device, RRC messages comprising configuration parameters of LP-SS and / or LP-WUS when the wireless device is equipped with or supports a LP-WUR. The RRC messages may further comprise configuration parameters of SSBs of one or more cells.

[0347] In an example, for PDCCHs / PDSCHs of each cell of the one or more cells, the base station may configure / activate one or more TCI states by implementing examples of FIG. 27 and / or FIG. 28. The wireless device may use the MR of the wireless device to receive, based on the one or more TCI states according to each cell, the PDCCHs / PDSCHs of each cell of the one or more cells.

[0348] The wireless device, when equipped with a LP-WUR, may use a LR of the wireless device to receive / monitor the LP-SS and / or the LP-WUS and use a MR of the wireless device to receive one or more NR channels / signals. The LP-WUR, LR, MR, LP-SS and / or LP-WUS may be implemented based on examples of FIG. 32.

[0349] In the example of FIG. 35, upon the LP-SS / LP-WUS being configured by the RRC messages at TO (and / or upon receiving a MAC CE / DCI indicating an activation of monitoring the LP-SS / LP-WUS), the wireless device may monitor / receive / detect the LP-SS / LP-WUS, e.g., between TO and T2 when the wireless device receives the LP-WUS indicating to monitor a PDCCH by the MR of the wireless device. In response to receiving the LP-WUS at T2 (e.g., based on examples of FIG. 33), the wireless device may start to measure / detect SSBs at T3 and / or may start to monitor the PDCCHsat T4.

[0350] In the example of FIG. 35, the wireless device, by implementing existing technologies, may be aligned with the base station regarding 3rdTx beam(s) for the SSBs and / or 4thTx beam(s) for the PDCCHs, e.g., based on examples of FIG. 27 and / or FIG. 28.

[0351] However, the wireless device, by using the existing technologies, may have difficulties in determining a beam / TCI state for receiving / monitoring the LP-SS / LP-WUS (between TO and T2 in the example of FIG. 35), when the base station transmits the LP-SS / LP-WUS with multiple beams (e.g., 1stTx beam(s) for the LP-SS, 2ndTx beam(s) for the LP-WUS). The base station may transmit the LP-SS / LP-WUS with a transmission beam different from a NR channel / signal (e.g., 3rdTx beam(s) for the SSBs, 4thTx beam(s) for the PDCCHs in FIG. 35), e.g., when the frequency resources of the LP-SS / LP-WUS are configured with different locations as shown in FIG. 34A, FIG. 34B and / or FIG. 34C.

[0352] Taking FIG. 34B and / or FIG. 34C as an example of frequency resource allocation for the LP-SS / LP-WUS, the wireless device may not know, by advance, a beam used for the transmission of the LP-SS / LP-WUS by the base station based on existing technologies. In existing technologies, the beam / TCI state is per BWP / cell managed (wherein a NR channel / signal of the BWP / cell is associated with a TCI state activated from the same TCI state pool configured for the BWP / cell based on examples of FIG. 27 and / or FIG. 28). However, the LP-SS / LP-WUS may not belong to any BWP / cell as shown in FIG. 34C or may not fully belong to any BWP / cell as shown in FIG. 34B.

[0353] By implementing existing technologies, the wireless device and the base station may misalign on the beam / T Cl used by the base station and by the wireless device. Existing technologies may increase latency of the LP-SS / LP-WUS transmission and / or increase the time used for waking up the wireless device to monitor / detect PDCCH for data transmission.

[0354] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising first parameters of one or more cells, wherein each cell of the one or more cells is associated with a respective plurality of TCI states. The one or more RRC messages comprise second parameters of a low power wake-up signal (LP-WUS) and / or low power synchronization signal blocks (LP-SS). The second parameters comprise at least one of: one or more TCI state indexes and a (TCI state / beam) reference cell indicator. The wireless device monitors / measures / detects, based on the reference cell indicator indicating a first cell of the one or more cells, the LP-SS / LP-WUS, with a spatial domain filter determined based on one or more first TCI states, of a first plurality of TCI states corresponding to the first cell, indicated by the one or more TCI state indexes.

[0355] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising first parameters of one or more cells. Each cell of the one or more cells is associated with a respective plurality of SSBs. The one or more RRC messages comprise second parameters of a LP-SS / LP-WUS, wherein the second parameters comprise a reference cell indicator. The wireless device monitors / measures / detects, based on the reference cell indicator indicating a first cell of the one or more cells, the LP-SS / LP-WUS, with a spatial domain filter determined based on at least one of a first plurality of SSBs corresponding to the first cell.

[0356] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising configuration parameters of a LP-SS / LP-WUS, wherein the configuration parameters comprise a reference cell indicator. The wireless device monitors / measures / detects, based on the reference cell indicator indicating a first cell of one or more cells, the LP-SS / LP-WUS, with a spatial domain filter determined based on at least one of a first plurality of SSBs / CS I -RSs corresponding to the first cell.

[0357] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising first parameters of reference signals of a first cell comprising first frequency resources. The one or more RRC messages comprise second parameters of a LP-SS / LP-WUS configured on second frequency resources. The wireless device monitors / measures / detects the LP-WUS, with a spatial domain filter determined based on at least one of the reference signals of the first cell in response to the second frequency resources being confined within (or partially overlapping with) the first frequency resources.

[0358] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising first parameters of reference signals (and / or TCI states) of a first cell comprising first frequency resources. The one or more RRC messages comprise second parameters of a LP-SS / LP-WUS configured on second frequency resources. The wireless device monitors / measures / detects the LP-WUS, with a spatial domain filter determined based on at least one of the reference signals (or the TCI states) of the first cell in response to the second frequency resources and the first frequency resources being configured within a same frequency band (or a same frequency range) and / or the first cell being a PCell.

[0359] By implementing the one or more example embodiments, a wireless device may determine a beam reference cell for monitoring / receiving the LP-SS / LP-WUS when the LP-SS / LP-WUS are transmitted with multiple beams, based on an (explicit / implicit) indication of the beam reference cell by the base station and / or based on whether the frequency resources of the LP-SS / LP-WUS are configured within a bandwidth of a BWP / cell (and / or within a same frequency band / range of the BWP / cell). Example embodiments may allow the base station to flexibly configure frequency resources of the LP-SS / LP-WUS (e.g., without limiting the frequency resources of LP-SS / LP-WUS confined by / within a bandwidth of a BWP / cell). Example embodiments may enable the base station to use beam forming technologies for the transmission of the LP-SS / LP-WUS, therefore improving the coverage of the LP-SS / LP-WUS and / or improving NR signals / channels (PDCCH / PDSCH / SSB / PUCCH / PUSCH) transmission throughput.

[0360] In existing technologies, a base station may transmit to a wireless device RRC messages comprising configuration parameters of a LP-SS / LP-WUS. The wireless device upon receiving the RRC messages may automatically enable / activate the LP-WUR of the wireless device. By enabling / activating the LP-WUR, the wireless device starts to use the LR of the wireless device for receiving / detecting / monitoring the LP-SS / LP-WUS. The wireless device does not wake up the MR of the wireless device for PDCCH monitoring before the wireless device receives / detects the LP-WUS. However, it is unclear by the existing technologies on how to disable / stop / deactivate the LP-SS / LP-WUS related function (or disable / deactivate / bypass the LP-WUR), e.g., when a large amount of data is available for delivery. Some existing technologies use a timer to control when to disable / stop / deactivate the LP-WUR reception / operation. Some existing technologies use RRC messages indicating the wireless device to disable / stop / deactivate the LP-WUR reception / operation. However, the existing technologies did not disclose the RRC signaling format(s) for which the wireless device and the base station have the same understanding of the wireless device behavior when receiving the RRC messages. The wireless device, by using existing technologies, may be misaligned with the base station regarding maintaining / keeping / releasing / clearing the LP-SS / LP-WUS configuration.

[0361] In an example, the wireless device, after receiving a first RRC message of a serving cell configuration comprising a LP-SS / LP-WUS configuration, receives a second RRC message of the serving cell configuration with the LP-SS / LP-WUS configuration being absent. The wireless device, in response to receiving the second RRC message and based on existing technologies, may maintain the LP-SS / LP-WUS configuration configured by the first RRC message, and continue to use the LP-WUR for the LP-SS / LP-WUS monitoring / detection. The wireless device does not wake up the MR for PDCCH monitoring before receiving the LP-WUS during the monitoring the LP-WUS. The existing technologies may increase data transmission latency when a large amount of data is waiting for delivery.

[0362] One or more example embodiments comprise a wireless device receiving from a base station one or more first RRC messages comprising a serving cell configuration of a cell. The one or more first RRC messages comprise a first field indicating a first periodicity value for SSBs of the cell and a second field indicating a configuration of LP-SS / LP- WUS. The wireless device receives, via the cell, the SSBs based on the first periodicity value. The wireless device monitors the LP-SS / LP-WUS according to the configuration. The wireless device receives one or more second RRCmessages of the serving cell configuration. The wireless device, based on receiving the one or more second RRC messages, receives / measures / detects the SSBs based on a predefined periodicity value, in response to the first field being absent in the one or more second RRC messages, and / or releases the configuration of the LP-SS / LP-WUS, in response to the second field being absent in the one or more second RRC messages.

[0363] One or more example embodiments comprise a wireless device receiving from a base station one or more first RRC messages comprising a serving cell configuration of a cell. The one or more first RRC messages comprise a field indicating a configuration of LP-SS / LP-WUS. The field is associated with a field tag being set to “Need R”. The wireless device monitors the LP-SS / LP-WUS according to the configuration. The wireless device receives one or more second RRC messages of the serving cell configuration. The wireless device, based on receiving the one or more second RRC messages, releases the configuration of the LP-SS / LP-WUS, in response to the field (with the “Need R” field tag) being absent in the one or more second RRC messages.

[0364] One or more example embodiments comprise a wireless device receiving from a base station one or more first RRC messages comprising a serving cell configuration of a cell. The one or more first RRC messages comprise an RRC IE with a SetupRelease type indicating a configuration of LP-SS / LP-WUS. The RRC IE is associated with a field tag being set to “Need M”. The wireless device monitors the LP-SS / LP-WUS according to the configuration in response to the SetupRelease type of the RRC IE being set to “setup”. The wireless device receives one or more second RRC messages of the serving cell configuration. The wireless device, based on receiving the one or more second RRC messages, maintains the configuration of the LP-SS / LP-WUS (and / or continue the LP-SS / LP-WUS monitoring), in response to the RRC IE being absent in the one or more second RRC messages and / or based on the RRC IE being associated with a “Need M” field tag. The wireless device, based on receiving the one or more second RRC messages, releases the configuration of the LP-SS / LP-WUS (and / or stop the LP-SS / LP-WUS monitoring), in response to the RRC IE being present and / or the SetupRelease type of the RRC IE being set to “release" in the one or more second RRC messages.

[0365] By implementing the one or more example embodiments, the wireless device determines whether to release the stored LP-SS / LP-WUS configuration parameters / values based on a field tag and / or a SetupRelease type value of a RRC IE configuring the LP-SS / LP-WUS configuration parameters / values in the RRC message. The wireless device stops LP-SS / LP-WUS monitoring based on the releasing. The wireless device starts to monitor PDCCH for downlink data reception and / or uplink data transmission based on stopping the LP-SS / LP-WUS monitoring. Example embodiments may align the base station and the wireless device regarding the processing of the RRC message, and therefore reduce data transmission / reception latency between the wireless device and / or the base station.

[0366] In existing technologies, a wireless device may be configured with a number of TCI states among which one or more TCI state may be activated for downlink reception and / or uplink transmission based on examples described above with respect to FIG 27 and / or FIG. 28. In an example, the number may be less than or equal to a predefined number (e.g., 64 for PDCCH transmission, 128 in total for all downlink transmissions of PDCCH / PDSCH / CSI-RSs, 64for uplink transmissions, etc.) in existing technologies. However, it is unclear how many TCI states / beams could be configured for the reception of the LP-SS / LP-WUS in existing technologies, given that the LR used for receiving the LP- SS / LP-WUS may not be advanced in the same level as the MR used for receiving the PDSCH / PDCCH and / or transmitting PUSCH / PUCCH. Reusing existing technologies to determine / configure TCI states / beams for the LP- SS / LP-WUS reception may increase power consumption of wireless devices.

[0367] One or more example embodiments may comprise receiving by a wireless device from a base station one or more RRC messages indicating a number of TCI states / beams for LP-SS / LP-WUS transmissions. The number is equal to or smaller than a fixed number.

[0368] In an example, the fixed number may be one of 4, 8, 16 and 32, which is smaller than the total number of TCI states configured for NR channels.

[0369] In an example, the fixed number may be equal to the maximum number (64) of TCI states used for PDCCH receptions, smaller than the maximum number (128) of TCI state used for downlink receptions.

[0370] By implementing the one or more example embodiments, the wireless device and the base station align on the maximum number of beams used for LP-SS / LP-WUS, wherein the maximum number is a predefined value which is smaller than the number used for NR channels.

[0371] One or more example embodiments comprise a wireless device receiving from a base station one or more first RRC messages comprising a request of a wireless device radio access capability information. The wireless device transmits to the base station one or more second RRC messages comprising the wireless device radio access capability information. The one or more second RRC messages comprise a first parameter indicating that the wireless device supports an activation of a LP-WUS monitoring by a RRC message and / or a second parameter indicating the maximum number of T Cl states configured for the LP-WUS monitoring.

[0372] In an example embodiment, the second parameter indicating the maximum number of TCI states configured for the LP-WUS monitoring may be separately indicated from a third parameter indicating a maximum number of TCI states configured on a cell (e.g., maxNumberConUguredTCIstatesPerCC) in existing technologies. The maximum number of TCI states configured for the LP-WUS monitoring may be smaller than maxNumberConUguredTCIstatesPerCC of the existing technologies.

[0373] By implementing the one or more example embodiments, the wireless device indicates to the base station the supported maximum TCI states / beams for monitoring / receiving LP-SS / LP-WUS. The base station accordingly configures / indicates / activates a number of TCI states / beams for the LP-SS / LP-WUS transmissions. Example embodiments may align the base station and the wireless device regarding the wireless device supported maximum TCI states / beams for the LP-SS / LP-WUS transmissions / receptions, therefore improving the coverage of the LP-SS / LP- WUS (e.g., by configuring a larger number of TCI states / beams for the LP-SS / LP-WUS) and / or reducing power consumption of the wireless device (e g., by configuring a smaller number of TCI states / beams for the LP-SS / LP-WUS).

[0374] In existing technologies, a wireless device may determine an initial / default TCI state for downlink reception of NR channels / signals of a cell, when multiple TCI states are configured for the cell by RRC messages and before one of the multiple TCI states indicated by a TCI state activation command (e.g., a MAC CE / DCI) is applied on the NR channels / signals by the wireless device. The initial / default TCI state may be determined based on an initial access procedure on the cell or a random access procedure on the cell for receiving a Ml B / SIB1 / RAR, e.g., based on the examples described above with respect to FIG. 28.

[0375] In existing technologies, when unified TCI state is supported / configured, each CORESET may be associated with an RRC parameter (e.g., followUnifiedTCI-state IE as shown in FIG. 27) indicating whether the wireless device uses the unified TCI state for receiving a DCI via the CORESET.

[0376] However, given the LP-SS / LP-WUS is different from PDCCH / CORESET (e.g., in terms of frequency / time domain resources, receiver algorithms, signal formats, etc.), the wireless device, by using existing technologies, may have difficulties in determining an initial / default TCI state for receiving the LP-SS / LP-WUS and / or in determining whether to follow unified TCI state for receiving the LP-SS / LP-WUS. Existing technologies may increase latency of the LP-WUS reception.

[0377] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising first parameters of a cell associated with (unified) TCI states and second parameters of a LP-SS / LP-WUS. The wireless device, in response to a TCI state indicator, indicating at least one of the TCI states, being absent in the second parameters, monitors / detects / measures the LP-SS / LP-WUS based on a (initial / default) TCI state determined based on a reception of at least one of: a MIB message, a SIB1 message, a downlink signal via an initial BWP of the cell and / or a downlink signal via a CORESET O of an active BWP of the cell.

[0378] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising first parameters of a cell associated with TCI states and second parameters of a LP-SS / LP- WUS. The wireless device, based on one or more criteria, monitors / detects / measures the LP-SS / LP-WUS with a spatial domain filter determined based on a reception of at least one of: a MIB message, a SIB1 message, a downlink signal via an initial BWP of the cell and / or a downlink signal via a CORESETflO of an active BWP of the cell.

[0379] By implementing the one or more example embodiments, the wireless device determines an initial / default TCI state / beam for reception of LP-SS / LP-WUS, e.g., when the base station does not explicitly indicate the TCI state / beam for the reception of the LP-SS / LP-WUS. The wireless device determines the initial / default TCI state / beam based on one or more criteria. The initial / default TCI state / beam may be the one used for Ml B / SIB1 reception and / or the one identified during an initial access procedure or a random access procedure. The initial / default TCI state / beam may be an activated / configured unified TCI state associated with a CORESET O of a cell. The one or more criteria may comprise whether an indication of the default / initial TCI state is received from the base station, whether the unified TCI state is activated, whether the wireless device is in a RRC J OLE state, a RRCJNACTIVE state or a RRC_CONNECTED state, whether the frequency resources of the LP-SS / LP-WUS are confined with a bandwidth of aBWP / cell, whether the frequency resources of the LP-SS / LP-WUS are configured on the same band of the BWP / cell, etc. Example embodiments may align the base station and the wireless device regarding TCI state / beam used for the LP-SS / LP-WUS, therefore improving the coverage of the LP-SS / LP-WUS and / or reducing power consumption of the wireless device.

[0380] One or more example embodiments comprise a wireless device receiving from a base station one or more RRC messages comprising first parameters of a cell associated with unified TCI states and second parameters of a LP- SS / LP-WUS. The second parameters comprise a third parameter indicating whether to follow a unified TCI state for the receptions of the LP-SS / LP-WUS. The wireless device, based on the third parameter indicating to follow the unified TCI state for the receptions of the LP-SS / LP-WUS, monitors / detects / measures the LP-SS / LP-WUS with a spatial domain filter determined based on an activated unified TCI state of the unified TCI states of the cell.

[0381] By implementing the one or more example embodiments, the wireless device determines whether to follow unified TCI state for receiving a LP-SS / LP-WUS by a first parameter and determines whether to follow unified TCI state for receiving a DCI via a CORESET. Example embodiments may simplify the implementation of the LP-WUR of the wireless device, reduce signaling overhead for beam indication of the LP-SS / LP-WUS, and / or improve reception quality of the LP-SS / LP-WUS.

[0382] FIG. 36 shows an example embodiment of beam management for LP-SS / LP-WUS reception.

[0383] In the example of FIG. 36, a wireless device (e.g., UE) receives, at TO, from a base station (e.g., gNB) one or more 1stRRC messages comprising a capability / assistance information request of the wireless device for power saving operation of the wireless device. The capability / assistance information request may be comprised in the one or more first RRC messages requesting the wireless device radio access capability information. The power saving operation may comprise a LP-SS / LP-WUS monitoring (e.g., by a LR of the wireless device) based on the examples described above with respect to FIG. 33.

[0384] In the example of FIG. 36, the wireless device transmits, at T2, one or more 2ndRRC messages comprising the wireless device capability / assistance information for the power saving operation.

[0385] In an example embodiment, the one or more 2ndRRC messages comprise a first parameter indicating that the wireless device supports an activation (or configuration) of an LP-WUS monitoring by a RRC message, a MAC CE, and / or a DCI.

[0386] In an example embodiment, the one or more 2ndRRC messages comprise a second parameter indicating the maximum number of TCI states / beams configured for the LP-WUS monitoring.

[0387] In an example embodiment, the maximum number of TCI states / beams configured for the LP-WUS monitoring, reported in the one or more 2ndRRC messages, may be different from the maximum number of TCI states configured on a cell and reported by the wireless device in existing technologies, e.g., maxNumberConfiguredTCIstatesPerCC.

[0388] In an example embodiment, the maximum number of TCI states / beams configured for the LP-WUS monitoring, reported in the one or more 2ndRRC messages, may be smaller than maxNumberConfiguredTCIstatesPerCC of the existing technologies.

[0389] In an example embodiment, the first parameter and / or the second parameter is per cell group indicated, wherein different cell groups are associated with different first parameters and / or different second parameters.

[0390] In an example embodiment, the first parameter and / or the second parameter is per frequency band indicated, wherein different frequency bands are associated with different first parameters and / or different second parameters.

[0391] In an example embodiment, the first parameter and / or the second parameter is per frequency band combination indicated, wherein different frequency band combinations are associated with different first parameters and / or different second parameters.

[0392] In an example embodiment, the first parameter and / or the second parameter is per frequency range indicated, wherein different frequency ranges are associated with different first parameters and / or different second parameters.

[0393] In the example of FIG. 36, the base station transmits to the wireless device, at T3, one or more 3rdRRC messages comprising configuration parameters of a LP-WUS configuration, wherein the configuration parameters indicate a number of TCI states, wherein the number is equal to or less than the maximum number indicated in the one or more 2ndRRC messages for the LP-SS / LP-WUS monitoring.

[0394] In an example embodiment, the LP-WUS configuration may be implemented based on examples of FIG. 33, FIG. 34A, FIG. 34B, FIG. 34C and / or FIG. 37 which will be described below in this specification.

[0395] In an example embodiment, the wireless device monitors the LP-SS / LP-WUS based on examples of FIG. 33 and / or FIG. 35.

[0396] By implementing the one or more example embodiments of FIG. 36, the wireless device indicates to the base station the supported / maximum TCI states / beams for monitoring / receiving LP-SS / LP-WUS. The base station accordingly configures / indicates / activates a number of TCI states / beams for the LP-SS / LP-WUS transmissions. Example embodiments may align the base station and the wireless device regarding the wireless device supported / maximum TCI states / beams for the LP-SS / LP-WUS transmissions / receptions, therefore improving the coverage of the LP-SS / LP-WUS (e.g., by configuring a larger number of TCI states / beams for the LP-SS / LP-WUS for a large area) and / or reducing power consumption of the wireless device (e.g., by configuring a smaller number of TCI states / beams for the LP-SS / LP-WUS for a small area).

[0397] FIG. 36 maybe modified to simplify the signaling for the TCI state / beam configuration. In an example embodiment, the maximum number of TCI states / beams for the LP-SS / LP-WUS monitoring may be (pre-)configured or predefined as a fixed value. The fixed value may be smaller than the values used for configuring TCI states for PDCCH / PDSCH of a cell in existing technologies.

[0398] In an example, the fixed value may be one of 4, 8, 16 and 32.

[0399] In an example, the fixed value may be equal to the maximum number (64) of TCI states used for PDCCH receptions, smaller than the maximum number (128) of TCI state used for downlink receptions.

[0400] By implementing the one or more example embodiments, the wireless device and the base station align on the supported / maximum number of beams used for LP-SS / LP- WUS, wherein the maximum number is a predefined value which is smaller than the number used for NR channels, without transmitting a wireless device capability indicating the supported / maximum number of TCI states / beams for the LP-SS / LP-WUS monitoring. Example embodiments may reduce signaling overhead for configuring the TCI states / beams used for the LP-SS / LP-WUS monitoring.

[0401] FIG. 37 shows an example embodiment of TCI state / beam configuration / operation for LP-SS / LP-WUS monitoring / reception, e.g., based on examples of FIG. 36.

[0402] In the example of FIG. 37, a wireless device receives from a base station one or more RRC messages comprising configuration parameters of a LP-SS / LP-WUS monitoring / reception. The configuration parameters may be comprised within one or more RRC lEs / parameters.

[0403] In an example, the one or more RRC messages may be implemented based on the one or more 3rdRRC messages of the examples of FIG. 36.

[0404] In the example of FIG. 37, the one or more RRC messages comprise a first field / parameter / RRC IE comprising, e.g., beam reference cell indication (or cell indication) as shown in FIG. 37, indicating which cell, of one or more cells (e.g., serving cells), is the source / reference cell of the beams / TCI states used for reception of the LP-SS / LP- WUS.

[0405] In an example (not shown in FIG. 37), the one or more RRC messages comprise serving cell configurations of one or more cells, wherein each BWP of a cell of the one or more cells is associated with a respective plurality of TCI states, e.g., based on examples of FIG. 27 and / or FIG. 28. The one or more cells may comprise a PCell and / or one or more SCells.

[0406] By implementing the example embodiment, configuring a beam reference cell for the LP-SS / LP-WUS reception may allow the base station to flexibly configure the frequency location of the LP-SS / LP-WUS (e.g , as shown in FIG. 34A, FIG. 34B and / or FIG. 34C) and / or reuse the TCI states / beams of NR channel of the beam / reference cell for the reception of the LP-SS / LP-WUS. Example embodiments may reduce signaling overhead for the beam / TCI state configuration for the LP-SS / LP-WUS.

[0407] Taking FIG. 34A and / or FIG. 34B as an example of LP-SS / LP-WUS frequency resource configuration, when the frequency resources of the LP-SS / LP-WUS are confined within the bandwidth of cell 1 , the base station may indicate cell 1 as the beam reference cell for the LP-SS / LP-WUS reception so that the wireless device may reuse the TCI state of cell 1 for the reception of the LP-SS / LP-WUS. In another example, when cell 1 is not configured with TCI states or is not configured with SSBs / CSI-RSs, the base station may indicate cell 2 as the beam reference cell for the LP-SS / LP-WUS reception even if the frequency resource of the LP-SS / LP-WUS does not overlap with the bandwidth of cell 2.

[0408] Similarly, taking FIG. 34C as an example of LP-SS / LP-WUS frequency resource configuration, when the frequency resources of the LP-SS / LP-WUS do not overlap with cell 1 or cell 2, the base station may indicate cell 1 as the beam reference cell for the LP-SS / LP-WUS reception so that the wireless device may reuse the T Cl state of cell 1 for the reception of the LP-SS / LP-WUS, e.g., when the frequency resource of the LP-SS / LP-WUS is in the same band of cell 1. In another example, when the frequency resource of the LP-SS / LP-WUS is in the same band of cell 2, the base station may indicate cell 2 as the beam reference cell for the LP-SS / LP-WUS reception, etc.

[0409] In the example of FIG. 37, the one or more RRC messages comprise a second field / parameter / RRC IE comprising, e.g., reference signals (RSs) indications (or indexes) as shown in FIG. 37, indicating which RSs, of a plurality of RSs of a reference cell (e.g., indicated by the beam reference cell indication as shown in FIG. 37), are the source / reference RSs of the beams / TCI states used for reception of the LP-SS / LP-WUS. The RSs may be SSBs / CSI- RSs.

[0410] In an example, the RSs may be a subset of the plurality of RSs of the reference cell.

[0411] In an example, the total number of the RSs used for the LP-SS / LP-WUS reception may be 4, 8, 16, which may be smaller than the total number of the plurality of RSs of the reference cell. Each of the RS indications may be an SSB / CSI-RS index. The total number of the plurality of RSs of the reference cell used for NR channel / signal reception may be 64 for SSBs or 128 for CSI-RSs.

[0412] By implementing the example embodiment, using the subset of the RSs of the cell, not the whole set of the RS of the cell, as the source / reference RSs of the beams / T Cl states used for the reception of the LP-SS / LP-WUS may simplify the receiver of the LP-WUR of the wireless device.

[0413] In the example of FIG. 37, the one or more RRC messages comprise a third field / parameter / RRC IE comprising, e.g., a number of beams / TCI states (or a beam / TCI state pool) as shown in FIG. 37, indicating a number of beams / TCI states used for reception of the LP-SS / LP-WUS.

[0414] In an example, a source / reference RS of each of the number of beams / T Cl states may be one of the RSs configured by the second parameter / IE of FIG. 37

[0415] In an example, the total number of the beams / TCI states may be 4, 8, 16, which may be smaller than the total number (e.g., 128) of the TCI states of a serving cell.

[0416] In an example, the total number of the beams / TCI states configured by the third field / parameter / RRC IE may be determined based on a wireless device’s capability for the LP-SS / LP-WUS reception, e g., based on examples of FIG. 36.

[0417] By implementing the example embodiment, configuring a set of beams / TCI states ,for the reception of the LP- SS / LP-WUS, smaller than the set of TCI states used for NR channel receptions, may simplify the receiver of the LP- WUR of the wireless device.

[0418] In the example of FIG. 37, the one or more RRC messages comprise a fourth field / parameter / RRC IE comprising, e.g., initial / default beam(s) / TCI state(s), indicating the beam(s) / TCI state(s) used for receptions of the LP- SS / LP-WUS upon the LP-SS / LP-WUS monitoring is configured / activated by the one or more RRC messages.

[0419] In an example, the initial / default beam(s) / TCI state(s) may be at least one of the number of beams / TCI states configured by the third field / parameter / RRC IE of FIG. 37.

[0420] In an example, the initial / default beam(s) / TCI state(s) may be at least one of the RSs configured by the second field / parameter / RRC IE of FIG. 37.

[0421] By implementing the example embodiment, configuring initial / default beam(s) / TCI state(s) for the reception of the LP-SS / LP-WUS may allow the wireless device to obtain the right beam(s) / TCI state(s) for monitoring the LP-SS / LP- WUS upon the LP-SS / LP-WUS monitoring is activated / configured by the one or more RRC messages. The wireless device, by implementing the example embodiment, does not wait for another MAC CE / DCI indicating a beam / TCI state for the LP-SS / LP-WUS monitoring. Therefore, the example embodiment may reduce the latency of LP-SS / LP-WUS monitoring and / or reduce power consumption of the wireless device.

[0422] In the example of FIG. 37, the one or more RRC messages comprise a fifth field / parameter / RRC IE comprising, e.g., foflowUnifiedTCI-State, indicating whether to use / apply a unified TCI state for receptions of the LP- SS / LP-WUS.

[0423] In an example, the followUnifiedTCi-State configured for the LP-SS / LP-WUS may be separately and / or differently configured from the followUnifiedTCi-State of a CORESET of a cell in existing technologies as shown in FIG. 27.

[0424] In an example, a CORESET of the cell may be associated with the followUnifiedTCi-State being set to “enabled” in which case, the wireless device applies the "indicated" DL only TCI or joint TCI for PDCCH reception on this CORESET. The base station may “indicate” a DL only TCI or joint TCI based on a MAC CE and / or a DCI, e.g., based on examples described above with respect to FIG. 28.

[0425] In an example embodiment, a LP-SS / LP-WUS may be associated with the followUnifiedTCi-State being set to “enabled” in which case, the wireless device applies the "indicated" DL only TCI or joint TCI for LP-SS / LP-WUS reception.

[0426] In an example embodiment, when the followUnifiedTCi-State is absent in the one or more RRC messages, the wireless device does not apply the "indicated" DL only TCI or joint TCI for LP-SS / LP-WUS reception. In this case, the wireless device uses / applies one or more beam(s) / TCI state(s) (e.g., the initial / default beam(s) / TCI state(s) as shown in FIG. 37) indicated by the one or more RRC messages for the receptions of the LP-SS / LP-WUS. In another example, the wireless device uses / applies an initial / default beam / TCI state based on one or more example embodiments of FIG. 39 which will be described later in this specification.

[0427] In an example, when the followUnifiedTCI-State associated with the LP-SS / LP-WUS configuration is absent in the one or more RRC messages, the wireless device determines whether to apply the “indicated” DL only TCI or joint TCI for LP-SS / LP-WUS reception based on a followUnifiedTCI-state of a CORESET (e.g. , CORESET O) of the cell.

[0428] By implementing the example embodiment, the wireless device may determine whether to follow a unified TCI state for monitoring the LP-SS / LP-WUS based on an explicit / implicit indication from the base station. Example embodiment may allow the wireless device to use the unified TCI state for the reception of the LP-SS / LP-WUS.

[0429] In the example of FIG. 37, the one or more RRC messages may further comprise one or more parameters / l Es / fields comprising, e.g., frequency resource indication, duty-cycle configuration for the reception of the LP-SS / LP-WUS. The frequency resource indication indicates the frequency resources of the LP-SS / LP-WUS (e.g., based on examples of FIG. 34A, FIG. 34B and / or FIG. 34C). The duty-cycle configuration indicates a duty-cycle configuration for monitoring the LP-SS / LP-WUS (e.g., based on examples of FIG. 33).

[0430] FIG. 38 shows an example embodiment of LP-SS / LP-WUS configuration / operation.

[0431] In the example of FIG. 38, a wireless device receives (e.g., by using the MR of the wireless device), at TO, from a base station one or more RRC messages comprising 1stRRC IE(s) comprising an LP-SS / LP-WUS configuration.

[0432] In an example, the 1stRRC IE(s) may be implemented based on examples of FIG. 37.

[0433] In an example, the 1stRRC IE(s) may indicate TCI state(s) / beam(s), frequency resources, time resources, etc., for a reception / measurement / monitoring of the LP-SS / LP-WUS.

[0434] In the example of FIG. 38, upon receiving the one or more RRC messages at TO, the wireless device starts to monitor / measure / receive the LP-SS / LP-WUS, e.g , by using the LR of the wireless device. During monitoring the LP- SS / LP-WUS and before detecting the LP-SS / LP-WUS, the wireless device does not monitor (by using the MR) PDCCHs of one or more cells.

[0435] In an example, the wireless device monitors the LP-WUS based on one or more beam(s) / TC I state(s) based on examples of FIG. 36, FIG. 37 and / or FIG. 39 which will be described later in this specification.

[0436] In the example of FIG. 38, upon detecting the LP-WUS at T1 , the wireless device starts to monitor SSBs at T2 and / or PDCCHs / PDSCHs at T3 of the one or more cells.

[0437] In an example, the wireless device may monitor SSBs and / or PDCCHs / PDSCHs using one or more beam(s) / TCI state(s) based on examples described above with respect to FIG. 27 and / or FIG. 28.

[0438] In the example of FIG. 38, the wireless device receives at T4 one or more RRC messages comprising 2ndRRC IE(s).

[0439] In the example of FIG. 38, the wireless device determines whether to release / maintain the LP-SS / LP-WUS configuration (received at TO and stored by the wireless device).

[0440] In the example of FIG. 38, the wireless device determines whether to release / maintain the LP-SS / LP-WUS configuration based on a field tag of the RRC IE(s) comprising the LP-SS / LP-WUS configuration.

[0441] In an example, the wireless device releases the LP-SS / LP-WUS configuration in response to the field tag, of the RRC IE(s) comprising the LP-SS / LP-WUS configuration, being set to “Need R” and the RRC IE(s) not being present in the one or more RRC messages received at T4. In response to releasing the LP-SS / LP-WUS configuration, the wireless device stops monitoring the LP-SS / LP-WUS. The wireless device, in response to releasing the LP-SS / LP- WUS configuration, may monitor PDCCHs of one or more serving cells for receiving and / or transmitting data.

[0442] In an example, the wireless device reconfigures the LP-SS / LP-WUS configuration in response to the field tag, of the RRC IE(s) comprising the LP-SS / LP-WUS configuration, being set to “Need R” and the RRC IE(s) being present in the one or more RRC messages received at T4.

[0443] Based on setting the field tag, of the RRC I E(s) comprising the LP-SS / LP-WUS configuration, to “Need R”, the example embodiments may align the base station and the wireless device regarding when to release the LP-SS / LP- WUS configuration.

[0444] In the example of FIG. 38, the wireless device determines whether to release / maintain the LP-SS / LP-WUS configuration based on a SetupRelease type of the RRC IE(s) comprising the LP-SS / LP-WUS configuration.

[0445] In an example, the wireless device starts to apply the LP-SS / LP-WUS configuration (or activates the LP- SS / LP-WUS configuration) in response to the SetupRelease type, of the RRC IE(s) comprising the LP-SS / LP-WUS configuration, being set to “Setup”, in the one or more RRC messages received at T4 (or at TO). In response to applying / activating the LP-SS / LP-WUS configuration, the wireless device starts to monitor the LP-SS / LP-WUS. The wireless device, in response to receiving the LP-WUS during monitoring the LP-SS / LP-WUS, may monitor PDCCHs of one or more serving cells for receiving and / or transmitting data.

[0446] In an example, the wireless device releases the LP-SS / LP-WUS configuration in response to the SetupRelease type, of the RRC IE(s) comprising the LP-SS / LP-WUS configuration, being set to “Release", in the one or more RRC messages received at T4. In response to releasing the LP-SS / LP-WUS configuration, the wireless device stops monitoring the LP-SS / LP-WUS. The wireless device, in response to releasing the LP-SS / LP-WUS configuration, may monitor PDCCHs of one or more serving cells for receiving and / or transmitting data.

[0447] Based on a SetupRelease type of the RRC IE(s) comprising the LP-SS / LP-WUS configuration, the example embodiments may align the base station and the wireless device regarding when to release the LP-SS / LP-WUS configuration.

[0448] FIG. 39 shows an example embodiment of beam management for LP-SS / LP-WUS reception.

[0449] In the example of FIG. 39, a wireless device receives from a base station one more RRC messages comprising configuration parameters of a LP-SS / LP-WUS configuration.

[0450] In an example, the one or more RRC messages may be implemented based on examples of FIG. 36, FIG. 37 and / or FIG. 38.

[0451] In the example of FIG. 39, the wireless device determines whether a 1stbeam / TCI state is indicated by the configuration parameters of the LP-SS / LP-WUS configuration.

[0452] In an example, the wireless device determines whether the 1stbeam / TCI state is available for the reception / monitoring the LP-SS / LP-WUS upon receiving the one or more RRC messages comprising the LP-SS / LP- WUS configuration (or indicating an activation of the LP-SS / LP-WUS configuration).

[0453] In an example, the wireless device determines whether the 1stbeam / T Cl state is indicated / available based on examples of FIG. 37.

[0454] In the example of FIG. 39, in response to the 1stbeam / TCI state being indicated / available based on the configuration parameters of the LP-SS / LP-WUS configuration, the wireless device starts to monitor the LP-SS / LP-WUS based on the 1stbeam / TCI state (e.g., with a spatial domain filter determined based on the 1stbeam / TCI state). The wireless device may start to monitor SSBs / PDCCHs with 2ndTCI state(s) in response to receiving the LP-WUS during monitoring the LP-WUS.

[0455] In an example, the wireless device determines an initial / default beam / TCI state for the reception / monitoring the LP-SS / LP-WUS in response to the 1stbeam / TCI state not being indicated by the configuration parameters of the LP-SS / LP-WUS configuration.

[0456] In an example embodiment, the wireless device determines the initial / default beam / TCI state, used for the reception / monitoring the LP-SS / LP-WUS, as the same one used for receiving a MIB message and / or a SIB1 message of the cell, e.g., before the 1stbeam / TCI state is indicated by the base station and / or is applied by the wireless device.

[0457] In an example embodiment, the wireless device determines the initial / default beam / TCI state, used for the reception / monitoring the LP-SS / LP-WUS, as the same one used for receiving PDCCH / PDSCH via an initial BWP of the cell.

[0458] In an example embodiment, the wireless device determines the initial / default beam / TCI state, used for the reception / monitoring the LP-SS / LP-WUS, as the same one used for receiving DCIs via CORESETWO of an active BWP (or an initial BWP) of the cell.

[0459] In an example embodiment, the wireless device determines the initial / default beam / TCI state, used for the reception / monitoring the LP-SS / LP-WUS, as the same one identified during an initial access procedure or a random access procedure, e.g., before the 1stbeam / TCI state is indicated by the base station and / or is applied by the wireless device.

[0460] In an example embodiment, the wireless device determines the initial / default beam / TCI state, used for the reception / monitoring the LP-SS / LP-WUS, as the activated / configured unified TCI state (e.g., associated with CORESET#0) of an active BWP of a cell, e.g., when the wireless device determines to apply the unified TCI state for the reception / monitoring the LP-SS / LP-WUS. In an example, the wireless device determines to apply the unified TCI state for the reception / monitoring the LP-SS / LP-WUS based on one or more example embodiments described above with respect to FIG. 37.

[0461] In an example embodiment, the wireless device determines the initial / default beam / TCI state, used for the reception / monitoring the LP-SS / LP-WUS, as the activated / configured unified TCI state of an active BWP of a cell, e.g.,when the frequency resources of the LP-SS / LP-WUS are confined within the bandwidth of the active BWP of the cell, or within the bandwidth of the cell, or within the same band of the BWP / cell, etc.

[0462] In an example embodiment, the wireless device determines the initial / default beam / TCI state based on the one or more example embodiments described above based on the wireless device being in an RRC_CONNECTED state.

[0463] In an example embodiment, the wireless device determines the initial / default beam / TCI state based on the wireless device’s implementation (which is transparent to the base station) based on the wireless device being in an RRCJDLE / INACTIVE state.

[0464] Example embodiments may align the base station and the wireless device regarding TCI state / beam used for the LP-SS / LP-WUS, therefore improving the coverage of the LP-SS / LP-WUS and / or reducing power consumption of the wireless device.

[0465] The one or more example embodiments of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39 may be combined as shown above and / or may be further combined to improve power consumption of the wireless device and / or improve LP- SS / LP-WUS coverage.

[0466] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more RRC messages comprising first parameters of one or more cells, wherein each cell of the one or more cells is associated with a respective plurality of TCI states, and second parameters of a low power wake-up signal (LP-WUS) and / or low power synchronization signal blocks (LP-SS). The second parameters comprise at least one of: one or more TCI state indexes and a reference cell indicator. The wireless device monitors / measures / detects, based on the reference cell indicator indicating a first cell of the one or more cells, the LP- SS / LP-WUS, with a spatial domain filter determined based on one or more first TCI states, of a first plurality of TCI states corresponding to the first cell, indicated by the one or more TCI state indexes.

[0467] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more RRC messages comprising first parameters of one or more cells. Each cell of the one or more cells is associated with a respective plurality of SSBs. The one or more RRC messages comprise second parameters of a LP-SS / LP-WUS, wherein the second parameters comprise a reference cell indicator. The wireless device monitors / measures / detects, based on the reference cell indicator indicating a first cell of the one or more cells, the LP-SS / LP-WUS, with a spatial domain filter determined based on at least one of a first plurality of SSBs corresponding to the first cell.

[0468] Based on the one or more examples FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more RRC messages comprising configuration parameters of a LP-SS / LP-WUS, wherein the configuration parameters comprise a reference cell indicator. The wireless device monitors / measures / detects, based on the reference cell indicator indicating a first cell of one or more cells, the LP-SS / LP-WUS, with a spatial domain filter determined based on at least one of a first plurality of SSBs corresponding to the first cell.

[0469] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more RRC messages comprising first parameters of reference signals of a first cell comprising first frequency resources and second parameters of a LP-SS / LP-WUS configured on second frequency resources. The wireless device monitors / measures / detects the LP-WUS, with a spatial domain filter determined based on at least one of the reference signals of the first cell in response to the second frequency resources being confined within the first frequency resources.

[0470] According to an example embodiment, the wireless device determines a primary cell, of the one or more cells, as the first cell, in response to the reference cell indicator not being present.

[0471] According to an example embodiment, the wireless device determines the first cell as a cell, of the one or more cells, within which the LP-WUS is configured / located, in response to the reference cell indicator not being present.

[0472] According to an example embodiment, the reference cell indicator comprises a physical cell identifier (PCI) of the first cell.

[0473] According to an example embodiment, the reference cell indicator comprises a serving cell index of the first cell.

[0474] According to an example embodiment, the first cell is one of a PCell and a SCell of the one or more cells.

[0475] According to an example embodiment, the first cell is a non-serving cell or a neighboring cell of a serving cell.

[0476] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more first RRC messages comprising a serving cell configuration of a cell. The one or more first RRC messages comprise a first field indicating a first periodicity value for SSBs of the cell and a second field indicating a configuration of LP-SS / LP-WUS. The wireless device receives, via the cell, the SSBs based on the first periodicity value. The wireless device monitors the LP-SS / LP-WUS according to the configuration. The wireless device receives one or more second RRC messages of the serving cell configuration. The wireless device, based on receiving the one or more second RRC messages, receives / measures / detects the SSBs based on a predefined periodicity value, in response to the first field being absent in the one or more second RRC messages, and / or releases the configuration of the LP-SS / LP-WUS, in response to the second field being absent in the one or more second RRC messages.

[0477] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more first RRC messages comprising a serving cell configuration of a cell. The one or more first RRC messages comprise a field indicating a configuration of LP-SS / LP-WUS. The wireless device monitors the LP-SS / LP-WUS according to the configuration. The wireless device receives one or more second RRC messages of the serving cell configuration. The wireless device, based on receiving the one or more second RRC messages, releases the configuration of the LP-SS / LP-WUS, in response to the field being absent in the one or more second RRC messages.

[0478] According to an example embodiment, the wireless device determines to receive the SSBs based on the predefined periodicity value, instead of the first periodicity value, in response to the first field being associated with a field tag being set to a first value.

[0479] According to an example embodiment, the first value is an “Need S”.

[0480] According to an example embodiment, the wireless device determines to release the configuration of the LP-SS / LP-WUS in response to the second field being associated with a field tag being set to a second value.

[0481] According to an example embodiment, the second value is a “Need R”.

[0482] According to an example embodiment, the wireless device stops monitoring the LP-SS / LP-WUS based on the releasing the configuration of the LP-SS / LP-WUS.

[0483] According to an example embodiment, the wireless device starts to monitor PDCCHs of the cell in response to stopping monitoring the LP-SS / LP-WUS.

[0484] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more first RRC messages comprising a request of or for a wireless device radio access capability information. The wireless device transmits to the base station one or more second RRC messages comprising the wireless device radio access capability information. The one or more second RRC messages comprise a first parameter indicating that the wireless device supports an activation of a LP-WUS monitoring by a RRC message and / or a second parameter indicating the maximum number of TCI states configured for the LP-WUS monitoring.

[0485] According to an example embodiment, the wireless device receives one or more third RRC messages comprising configuration parameters of an LP-WUS configuration, wherein the configuration parameters indicate a number of TCI states, wherein the number is equal to or less than the maximum number.

[0486] According to an example embodiment, the wireless device monitors the LP-WUS with a spatial domain filter determined based on at least one of the number of TCI states.

[0487] According to an example embodiment, the wireless device determines the at least one of the number of TCI states for the LP-WUS monitoring based on the one or more third RRC messages indicating the at least one of the number of TCI states for the LP-WUS monitoring.

[0488] According to an example embodiment, the first parameter and / or the second parameter is per cell group indicated, wherein different cell groups are associated with different first parameters.

[0489] According to an example embodiment, the first parameter and / or the second parameter is per frequency band indicated, wherein different frequency bands are associated with different first parameters.

[0490] According to an example embodiment, the first parameter and / or the second parameter is per frequency band combination indicated, wherein different frequency band combinations are associated with different first parameters.

[0491] According to an example embodiment, the first parameter and / or the second parameter is per frequency range indicated, wherein different frequency ranges are associated with different first parameters.

[0492] According to an example embodiment, the first parameter and / or the second parameter is per cell group indicated, wherein different cell groups are associated with different second parameters.

[0493] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more RRC messages comprising first parameters of a cell associated with TCI states and second parameters of a LP-SS / LP-WUS. The wireless device, in response to a TCI state indicator, indicating at least one of the TCI states, being absent in the second parameters, monitors / detects / measures the LP-SS / LP-WUS based on a default TCI state determined based on a reception of at least one of: a MIB message, a SIB1 message, a downlink signal via an initial BWP of the cell and / or a downlink signal via a CORESETflO of an active BWP of the cell.

[0494] Based on the one or more examples of FIG. 36, FIG. 37, FIG. 38 and / or FIG. 39, a wireless device receives from a base station one or more RRC messages comprising first parameters of a cell associated with TCI states and second parameters of a LP-SS / LP-WUS. The wireless device, based on one or more criteria, monitors / detects / measures the LP-SS / LP-WUS with a spatial domain filter determined based on a reception of at least one of: a MIB message, a SIB1 message, a downlink signal via an initial BWP of the cell and / or a downlink signal via a CORESET#0 of an active BWP of the cell.

[0495] According to an example embodiment, the spatial domain filter is determined based on an initial access procedure or a random access procedure.

[0496] According to an example embodiment, the one or more criteria comprise at least one of: a TCI state indicator, indicating a TCI state for the reception of the LP-SS / LP-WUS, not being present in the second parameters; before receiving a downlink signal indicating an activation of one or more of the TCI states; frequency resources of the LP- WUS being confined within the bandwidth of the cell; the cell being a PCell; and / or the wireless device being in an RRC-I DLE / INACTIVE / CON N ECTED state. The wireless device stops the LP-WUS monitoring in response to at least one of: deactivating the cell; and transmitting the cell to a dormant state.

[0497] According to an example embodiment, the wireless device stops the LP-WUS monitoring in response to an RRC reconfiguration of the cell.

[0498] According to an example embodiment, the wireless device stops the LP-WUS monitoring in response to: no activated TCI state being available; deactivating a TCI state of the one or more TCI states; and / or receiving an indication indicating a releasing of the one or more TCI states.

[0499] According to an example embodiment, the second parameters comprise a parameter indicating whether to follow / apply a unified TCI state for the reception of the LP-WUS.

[0500] According to an example embodiment, the TCI states, associated with the cell, configured by the one or more RRC messages, are unified TCI states.

[0501] According to an example embodiment, the wireless device receives a downlink signal (MAC CE / DCI) indicating an activation of a first unified TCI state of the unified TCI states.

[0502] According to an example embodiment, the wireless device monitors the LP-WUS based on the activated first unified TCI state in response to the parameter indicating to follow / apply the unified TCI state.

[0503] According to an example embodiment, the wireless device monitors and / or receives PDCCH / PDSCH based on the activated first unified TCI state in response to receiving the LP-WUS.

[0504] According to an example embodiment, the LP_WUS is transmitted based on an OOK, wherein, based on the OOK, the LPJ / VUS being transmitted indicates to wake up for monitoring PDCCHs of a cell and / or the LPJ / VUS not being transmitted indicates not to wake up for monitoring the PDCCHs.

[0505] According to an example embodiment, the wireless device receives the WUS based on an envelope detection of the LPJ / VUS based on the OOK.

[0506] According to an example embodiment, the wireless device does not wake up for monitoring the PDCCHs in response to not receiving the LPJ / VUS.

[0507] According to an example embodiment, the wireless device monitors, in response to receiving the LPJ / VUS, the PDCCHs of the one or more cells, using a MR (or a first receiver) of the wireless device.

[0508] According to an example embodiment, the wireless device receives a DCI during monitoring the PDCCHs, indicating an uplink grant for a PUSCH and / or a downlink scheduling for a PDSCH.

[0509] According to an example embodiment, the wireless device monitors, the LPJ / VUS, using a LR (or a second receiver) of the wireless device.

[0510] According to an example embodiment, the second parameters comprise at least one of: a transmission periodicity of the LPJ / VUS, a value of a periodic time duration, during which the wireless device monitors the LPJ / VUS, a number of RBs and / or a number of symbols of the WUS.

[0511] According to an example embodiment, the number is less than a total number of symbols of a slot.

[0512] According to an example embodiment, the number is equal to or greater than a total number of symbols of a slot.

[0513] According to an example embodiment, the second parameters comprise at least one of: a time offset of the periodic time duration, related to a time reference point (a system radio frame or a subframe), a time offset of a starting symbol of the LPJ / VUS related to a starting point of the periodic time duration and / or a time offset of an ending symbol of the LPJ / VUS related to an ending point of the periodic time duration.

Claims

CLAIMSWhat is claimed is:

1. A method comprising: receiving, by a wireless device, one or more radio resource control ( RRC) messages comprising at least one of: first parameters of reference signals (RSs) of a cell comprising one or more downlink bandwidth parts (BWPs), wherein a first downlink BWP, of the one or more downlink BWPs, comprises first frequency resources; and second parameters of a low power wake-up signal (LP-WUS) configured with second frequency resources; and monitoring, via the second frequency resources and for receiving the LP-WUS, the LP-WUS, using at least one of the RSs of the cell, based on: the LP-WUS being quasi-co-located (QCLed) with the at least one of the RSs of the cell; and the second frequency resources being within the first frequency resources of the first downlink BWP, wherein the first downlink BWP is an active downlink BWP of the cell; and receiving the LP-WUS based on the monitoring2. The method of claim 1 , wherein the one or more RRC messages indicate transmission configuration indicator (TCI) states of the cell.

3. The method of claim 2, further comprising monitoring the LP-WUS by using the at least one of the RSs, wherein the at least one of the RSs is used for a reception of at least one of: a system information block 1 (SIB1) of the cell; a downlink signal via an initial bandwidth part (BWP) of the cell; and a downlink signal via a control resource set (CORESET) O of an active BWP of the cell.

4. The method of claim 3, wherein the wireless device determines the at least one of the RSs based on a TCI state indicator being absent in the second parameters of the LP-WUS.

5. The method of claim 4, wherein the wireless device determines a default T Cl state, for receiving the LP-WUS, is QCLed with the at least one of the RSs, wherein the at least one of the RSs is used for reception of a master information block (MIB) of the cell.

6. The method of claim 5, wherein the default TCI state is determined based on an initial access procedure or a random access procedure.

7. The method of claim 5, wherein the wireless device determines the default TCI state, for monitoring or receiving the LP-WUS, based on one or more criteria comprising at least one of: a TCI state indicator, indicating a TCI state for the reception of the LP-WUS, not being present in the second parameters of the LP-WUS; before receiving a downlink signal indicating an activation of one or more of the TCI states;frequency resources of the LP-WUS being confined within the first downlink BWP of the cell; the cell being a primary cell (PCell); the wireless device being in an RRC-IDLE state; the wireless device being in an RRC_I NACTIVE state; and the wireless device being in an RRC_CONNECTED state.

8. The method of any one of claims 1 to 7, wherein the one or more RRC messages comprise configuration parameters of one or more cells comprising the cell, wherein each cell of the one or more cells is associated with a receptive plurality of TCI states.

9. The method of claim 8, wherein the second parameters of the LP-WUS comprise at least one of: a TCI state index; and a reference cell indicator.

10. The method of claim 9, wherein the wireless device monitors the LP-WUS based on: the reference cell indicator indicating a first cell of the one or more cells; and a first TCI state, of a first plurality of TCI states corresponding to the first cell, indicated by the TCI state index.

11. The method of claim 10, wherein the wireless device determines a primary cell, of the one or more cells, as the first cell, in response to the reference cell indicator not being present in the second parameters of the LP-WUS.

12. The method of claim 10, wherein the wireless device determines the first cell as a cell, of the one or more cells, within which the LP-WUS is configured or located, in response to the reference cell indicator not being present.

13. The method of claim 10, wherein the reference cell indicator comprises a physical cell identifier (PCI) of the first cell.

14. The method of claim 10, wherein the reference cell indicator comprises a serving cell index of the first cell.

15. The method of claim 10, wherein the first cell is one of a PCell and a SCell of the one or more cells.

16. The method of claim 10, wherein the first cell is a non-serving cell ora neighboring cell of a serving cell.

17. The method of any one of claims 1 to 16, further comprising transmitting, by the wireless device to a base station, one or more second RRC messages comprising wireless device radio access capability information, wherein the one or more second RRC messages comprise at least one of: a first parameter indicating that the wireless device supports the LP-WUS monitoring configured by the one or more RRC messages, wherein the LP-WUS is transmitted by the base station based on on-off-keying (OOK) signal; and a second parameter indicating a maximum number of TCI states, supported by the wireless device, for the LP- WUS monitoring.

18. The method of claim 17, wherein the one or more RRC messages indicate a number of TCI states for the LP- WUS monitoring, wherein the number is equal to or less than the maximum number.

19. The method of claim 18, further comprising monitoring the LP-WUS with a spatial domain filter determined based on at least one of the number of TCI states.

20. The method of claim 19, wherein the wireless device determines the at least one of the number of TCI states for the LP-WUS monitoring based on the one or more RRC messages indicating the at least one of the number of TCI states for the LP-WUS monitoring.

21. The method of any one of claims 17 to 20, wherein the second parameter of the one or more second RRC messages is per cell group indicated, wherein different cell groups are associated with different second parameters.

22. The method of any one of claims 17 to 20, wherein the second parameter of the one or more second RRC messages is per frequency band indicated, wherein different frequency bands are associated with different second parameters.

23. The method of any one of claims 17 to 20, wherein the second parameter of the one or more second RRC messages is per frequency band combination indicated, wherein different frequency band combinations are associated with different second parameters.

24. The method of any one of claims 17 to 20, wherein the second parameter of the one or more second RRC messages is per frequency range indicated, wherein different frequency ranges are associated with different second parameters.

25. The method of any one of claims 1 to 24, further comprising stopping the LP-WUS monitoring, via the second frequency resources, in response to at least one of: deactivating the cell; and transitioning the cell to a dormant state.

26. The method of any one of claims 1 to 24, further comprising stopping the LP-WUS monitoring, via the second frequency resources, in response to receiving an RRC reconfiguration of the cell.

27. The method of any one of claims 1 to 24, further comprising stopping the LP-WUS monitoring, via the second frequency resources, in response to: no activated TCI state being available; deactivating an active TCI state of the TCI states; and / or receiving an indication indicating a releasing of the TCI states28. The method of any one of claims 1 to 27, wherein the second parameters of the LP-WUS comprises a parameter indicating whether to follow, apply, or both follow and apply a unified TCI state, of TCI states of the cell, for the monitoring or reception of the LP-WUS.

29. The method of claim 28, further comprising receiving a downlink signal activating a first unified TCI state of the TCI states of the cell.

30. The method of claim 29, wherein the wireless device monitors the LP-WUS based on the activated first unified TCI state based on the parameter, comprised in the second parameters of the LP-WUS, indicating to follow / apply the unified TCI state.

31. The method of claim 30, further comprising monitoring and / or receiving PDCCH / PDSCH based on the activated first unified TCI state in response to receiving the LP-WUS.

32. The method of any one of claims 1 to 31 , wherein the LP-WUS is transmitted based on an on-off keying (OOK) signal, wherein, based on the OOK signal: the LP-WUS being transmitted indicates to wake up for monitoring PDCCHs of the cell; and the LP-WUS not being transmitted indicates not to wake up for monitoring the PDCCHs.

33. The method of claim 32, wherein the wireless device receives the LP-WUS based on an envelope detection of the LP-WUS based on the OOK signal.

34. The method of claim 33, wherein the wireless device does not wake up for monitoring the PDCCHs in response to not receiving the LP-WUS.

35. The method of any one of claims 1 to 34, further comprising monitoring, in response to receiving the LP-WUS, PDCCHs of the one or more cells, using a main receiver (MR) of the wireless device.

36. The method of claim 35, comprising receiving a DCI during monitoring the PDCCHs, indicating an uplink grant for a PUSCH and / or a downlink scheduling for a PDSCH.

37. The method of any one of claims 1 to 36, wherein the wireless device monitors, the LP-WUS, using a low-power receiver (LR) of the wireless device.

38. The method of any one of claims 1 to 37, wherein the second parameters of the LP-WUS comprise at least one of: a transmission periodicity of the LP-WUS; a value of a periodic time duration, during which the wireless device monitors the LP-WUS; a number of resource blocks (RBs); and a number of symbols of the LP-WUS.

39. The method of claim 38, wherein the number is less than a total number of symbols of a slot.

40. The method of claim 38, wherein the number is equal to or greater than a total number of symbols of a slot.

41. The method of any one of claims 1 to 40, further comprising determining whether the second frequency resources of the LP-WUS are within the first frequency resources of the first downlink BWP.

42. The method of claim 41 , wherein the wireless device does not monitor the LP-WUS via the second frequency resources in response to the second frequency resources not being within the first frequency resources of the first downlink BWP, wherein the first downlink BWP is the active downlink BWP of the cell.

43. The method of any one of claims 1 to 42, wherein the one or more RRC messages comprise parameters of a serving cell configuration of the cell, wherein the parameters comprise:a first field indicating a first periodicity value for synchronization signal blocks (SSBs); and a second field indicating a configuration of the LP-WUS;44. The method of claim 43, further comprising receiving the SSBs based on the first periodicity value.

45. The method of claim 44, wherein the wireless device monitors the LP-WUS according to the configuration of the LP-WUS.

46. The method of claim 45, further comprising receiving one or more second RRC messages of the serving cell configuration.

47. The method of claim 46, further comprising: based on receiving the one or more second RRC messages: receiving the SSBs based on a predefined periodicity value, in response to the first field being absent in the one or more second RRC messages; and releasing the configuration of the LP-WUS, in response to the second field being absent in the one or more second RRC messages.

48. The method of claim 47, wherein the wireless device determines to receive the SSBs based on the predefined periodicity value, instead of the first periodicity value, in response to: the first field, of the one or more RRC messages, being associated with a field tag being set to a first value; and the first field being absent in the one or more second RRC messages.

49. The method of claim 48, wherein the first value is a “Need S”.

50. The method of any one of claims 47 to 49, wherein the wireless device determines to release the configuration of the LP-WUS in response to: the second field, of the one or more RRC messages, being associated with a field tag being set to a second value; and the second field being absent in the one or more second RRC messages.

51. The method of claim 50, wherein the second value is a “Need R”.

52. The method of any one of claims 1 to 51 , wherein the one or more RRC messages comprise parameters of a serving cell configuration of the cell, wherein the parameters comprise a field indicating a configuration of the LP- WUS.

53. The method of claim 52, wherein the wireless device monitors the LP-WUS according to the configuration of the LP-WUS.

54. The method of claim 53, further comprising receiving one or more second RRC messages of the serving cell configuration of the cell.

55. The method of claim 54, further comprising based on receiving the one or more second RRC messages, releasing the configuration of the LP-WUS, in response to a second field being absent in the one or more second RRC messages.

56. The method of claim 55, wherein the wireless device determines to release the configuration of the LP-WUS in response to: the field, of the one or more RRC messages, being associated with a field tag being set to a value; and the field being absent in the one or more second RRC messages.

57. The method of claim 56, wherein the value is a “Need R”.

58. The method of any one of claims 55 to 57, further comprising stopping monitoring the LP-WUS based on the releasing the configuration of the LP-WUS.

59. The method of claim 58, further comprising monitoring PDCCH of the cell based on at least one of: the releasing the configuration of the LP-WUS; and the stopping monitoring the LP-WUS.

60. The method of any one of claims 1 to 59, wherein the wireless device is in an RRC_CONNECTED state.

61. The method of any one of claims 1 to 59, wherein the wireless device is in an RRC_I DLE or RRC_I NACTIVE state.

62. An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of 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 an apparatus, cause the apparatus to perform the method of any one of claims 1 to 61.

Images