Rate matching on on-demand ssbs

Abstract

There is provided a method. The method comprises receiving, by a wireless device, a first physical downlink shared channel (PDSCH). One or more resource elements (REs), overlapping with resources of one or more on-demand synchronization signal (SS) physical broadcast channel (PBCH) blocks (SSBs) of a cell, are available or unavailable for receiving the first PDSCH, based on whether the one or more on-demand SSB are activated. The method further comprises transmitting a feedback corresponding to the first PDSCH.

Description

Docket No. 24-1248PCTTITLERate Matching on On-Demand SSBsCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 716,459, filed November5, 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 morePUCCH 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.Docket No. 24-1248PCT

[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. 17 illustrates an aspect of an example embodiment according to the present disclosure

[0024] FIG. 18 illustrates 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. 21 illustrates 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 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

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

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

[0035] 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 described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed 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.Docket No. 24-1248PCT

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

[0037] 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 capability(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 or a 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.

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

[0039] 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”) isDocket No. 24-1248PCT 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.

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

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

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

[0043] 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 otherDocket No. 24-1248PCT 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 LabVIEWMathScript. 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, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ 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.

[0044] FIG. 1 A 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.

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

[0046] 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), timedivision duplexing (TDD), and / or some combination of the two duplexing techniques.

[0047] 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 may be a telephone, smart phone, tablet, computer, laptop, sensor, meter,Docket No. 24-1248PCT wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wireless device 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.

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

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

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

[0051] The RAN 104 may be 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 areasDocket No. 24-1248PCT 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.

[0052] 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. 1 A. 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. 1A, 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.

[0053] 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. 1 B, 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. 1 A.

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

[0055] 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. 1 B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and theDocket No. 24-1248PCT 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- / inter-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.

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

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

[0058] 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 gNBs, illustrated as gNB 160A and gNB 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.

[0059] As shown in FIG. 1 B, 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 transportDocket No. 24-1248PCT 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. 1 B, gNB 160A may be 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.

[0060] 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 may be 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.

[0061] The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 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.

[0062] 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 gNB 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.

[0063] As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1 B 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.Docket No. 24-1248PCT

[0064] 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 may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1 B.

[0065] 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 (OS I) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MAGs) 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.

[0066] 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 U PF of a ON (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). 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 gNB 220. The SDAP 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.

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

[0068] 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 thatDocket No. 24-1248PCT 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.

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

[0070] 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 Hybrid Automatic 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.

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

[0072] 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 protocolDocket No. 24-1248PCT stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

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

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

[0075] 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 the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0076] 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 may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those 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 MACDocket No. 24-1248PCT 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.

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

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

[0079] -- 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;

[0080] -- 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;

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

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

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

[0084] 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 include, for example:

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

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

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

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

[0089] -- a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.Docket No. 24-1248PCT

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

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

[0092] -- 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;

[0093] - 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;

[0094] - 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;

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

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

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

[0098] 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 MAGs 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.

[0099] 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 may provide 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 230Docket No. 24-1248PCT 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.

[0100] 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 controlplane 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 (RLF); 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 .

[0101] 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. 2A and 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., RRCJDLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0102] 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. 1 B, the gNB 220 depicted in FIG. 2A and 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 toDocket No. 24-1248PCT the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

[0103] 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 may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

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

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

[0106] 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 theDocket No. 24-1248PCTUE 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.

[0107] RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be 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 may belong 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.

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

[0109] A gNB, such as gNBs 160 in FIG. 1 B, may be 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 SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0110] 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 (IFFT) block that transforms them into the time domain. The IFFT 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 timedomain 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 (PAPR). 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.Docket No. 24-1248PCT

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

[0112] 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 a baseline 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.

[0113] 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 numerology-independent 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.

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

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

[0116] 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,Docket No. 24-1248PCT 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.

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

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

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

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

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

[0122] A base station may semi-statically 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 defaultDocket No. 24-1248PCT 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.

[0123] 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 (b) 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.

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

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

[0126] 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 activeDocket No. 24-1248PCTBWP. 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.

[0127] 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 may be 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.

[0128] To provide for 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.

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

[0130] 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 aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

[0131] 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 (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL 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).Docket No. 24-1248PCT

[0132] 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 may be 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).

[0133] 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 selfscheduling. 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.

[0134] 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 UCI 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 UCI 1073, may be 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 may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061 , overloading may be prevented.

[0135] 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 theDocket No. 24-1248PCT 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.

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

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

[0138] 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. 11A). 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. 11A 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.

[0139] 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. 11 A) 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 after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.

[0140] 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 theDocket No. 24-1248PCTPSS. 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 cell-defining 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.

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

[0142] The PBCH may use a QPSK modulation and may use forward error correction (EEC). The EEC 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.

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

[0144] 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 spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.Docket No. 24-1248PCT

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

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

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

[0148] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with 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.

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

[0150] 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 configurableDocket No. 24-1248PCTDMRS patterns for data demodulation At least one downlink DMRS configuration may support a front- loaded DMRS pattern. A front-loaded DMRS may be mapped 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-MIMO, 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.

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

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

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

[0154] 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.Docket No. 24-1248PCTFor 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 may be mapped over one or more OFDM symbols (e.g. , one or two adjacent 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.

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

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

[0157] 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,Docket No. 24-1248PCT 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 RUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a RUSCH and a corresponding uplink DMRS.

[0158] 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, mini-slot, 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.

[0159] 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 co-located (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.

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

[0161] FIG. 11 B 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)Docket No. 24-1248PCT 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.

[0162] The three beams illustrated in FIG. 11 B may be configured for a 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 (FDM), 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.

[0163] CSI-RSs such as those illustrated in FIG. 11 B (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 basedDocket No. 24-1248PCT 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.

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

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

[0166] FIG. 12B illustrates examples of three uplink beam management procedures: U1 , 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 U 1 ). 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.Docket No. 24-1248PCT

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

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

[0169] 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 RRCJDLE state and / or an RRCJNACTIVE 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.

[0170] 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 3 1313, 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).

[0171] 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)Docket No. 24-1248PCT 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 broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to 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 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

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

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

[0174] 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 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) andDocket No. 24-1248PCT 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.

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

[0176] 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 preamble retransmission 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_TRANSMISSION_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) .

[0177] 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 andDocket No. 24-1248PCT 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 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-Response'Window) 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:

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

[0179] The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312). 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 3 1313 and the Msg 4 1314) may be used to increase the likelihood that the UE does not incorrectly use an identity 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).

[0180] 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 inDocket No. 24-1248PCT an RRCJDLE 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.

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

[0182] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, 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.

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

[0184] 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., recovery SearchSpaceld). 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 inDocket No. 24-1248PCT 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.

[0185] 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 may be 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.

[0186] 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 ACK / 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.

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

[0188] 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) may be multiplexed using FDM, 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.

[0189] 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)).Docket No. 24-1248PCTThe base station may transmit 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 or a 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).

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

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

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

[0193] 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 “PFFE” 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 1313Docket No. 24-1248PCT 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), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0194] 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 of 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 of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of 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_1 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.

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

[0196] FIG. 14A 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 time-frequency 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 CORESETDocket No. 24-1248PCT1403 occurs at a 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.

[0197] 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. A CORESET 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.

[0198] 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 CCEs at a 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).

[0199] As shown in FIG. 14B, the UE may determine a time-frequency resource for a 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., aDocket No. 24-1248PCT scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

[0200] 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 a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

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

[0202] 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 aDocket No. 24-1248PCTPUCCH 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”.

[0203] 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 for 1_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.

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

[0205] 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.Docket No. 24-1248PCT

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

[0207] 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 (MIMO) or multi-antenna processing, and / or the like.

[0208] 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 1522 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 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.

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

[0210] 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 theDocket No. 24-1248PCT 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 (e.g., 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.

[0211] 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 onboard 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.

[0212] 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 power to 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.

[0213] 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;Docket No. 24-1248PCT 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.

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

[0215] 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 complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on 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 time-domain 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.

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

[0217] 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 of physical, 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.Docket No. 24-1248PCT

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

[0219] In an example, a base station may transmit one or more SSBs in a SSB burst. The base station may periodically repeat transmissions of the SSB burst. In the specification, a SSB may represent a SS / PBCH block.

[0220] FIG. 17 shows an example of SSB transmission of a cell by a base station.

[0221] In the example shown in FIG. 17, a SCS of the cell is 15 kHz, and the cell is configured with a carrier frequency within a range of 3GHz<fc<=7GHz.

[0222] Also in the example of FIG. 17, the maximum number of candidate SSBs in a SSB burst is 8 (Lmax=8).

[0223] In FIG. 17, SSB#1 starts at symbol#2 of 70 symbols within 5 milliseconds (ms), SSB#2 starts at symbol#8, SSB#3 starts at symbol#16, SSB#4 starts at symbol#22, SSB#6 starts at symbol#36, and SSB#8 starts at symbol 50. The SSB#5 and SSB#7 are skipped or not transmitted in the SSB burst. The ssb-PositionsInBurst may indicate [1 1 1 1 0 1 0 1] for indicating transmission of SSBs#1-#4, SSB#6, and SSB#8, and skip or non-transmission of SSB#5 and SSB#7.

[0224] The SSB burst is transmitted in the first half (not the second half as shown in FIG. 17) of a radio frame of 10 ms. As shown in FIG. 17, the base station may repeat the SSB burst in every 20 ms A periodicity of the SSB transmission in this disclosure may refer a periodicity of the SSB burst. In one example, the SSB burst may be indicated / configured by ssb-periodicityServingCell or set to 5ms as a default.

[0225] In an example, the SSB / SSB burst (i.e., each SSB of the SSB burst) may be transmitted in a periodicityDocket No. 24-1248PCT

[0226] In the example shown in FIG. 17, a default periodicity of a SSB burst is 20 ms, e.g., before a wireless device receives a SIB1 message for an initial access of the cell.

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

[0228] The base station does not transmit the SSB burst in the remaining 15 ms of the each 20 ms.

[0229] In an example, a base station may transmit RRC messages (e.g., containing SIB1 and / or ServingCellConfigCommon IE) indicating cell specific configuration parameters of SSB transmission of a serving cell (e.g., a PCell or a SCell).

[0230] The cell specific configuration parameters may comprise a value for a transmission periodicity {ssb-PeriodicityServingCell) of a SSB burst, and locations of a number of SSBs (e.g., transmitted SSBs), of a plurality of candidate SSBs, comprised in the SSB burst. The plurality of candidate SSBs may be determined based on one or more configurations via e.g., MIB. For instance, in the example shown in FIG. 17, candidates illustrated as #1 to #8 may represent the plurality of candidate SSBs, and the base station transmits SSBs via #1 , #2, #3, #4, #6 and #8 candidates and does not transmit SSBs via #5 and #7.

[0231] The cell specific configuration parameters may comprise position indication of a SSB in a SSB burst (e.g., ssb-PositionsinBursf). The position indication may comprise a first bitmap (e.g., groupPresence) and a second bitmap (e.g., inOneGroup). The first and second bitmaps indicate locations of a number of SSBs comprised in a SSB burst. The position indication may also comprise a third bitmap (e.g., inOneGroup) indicating locations of a number of SSBs comprised in a SSB burst. For instance, in the example shown in FIG. 17, the third bitmap may indicate [1 , 1 , 1 , 1 , 0, 1 , 0, 1] where each bit indicated by the third bitmap corresponds to each of the plurality of candidate SSBs in the SSB burst. When the first bitmap and the second bitmap is used, a first bit of the second bitmap may represent a SSB index wit 0, 8, and so on, where exact indexes are determined based on the first bitmap. For example, if a first bit of the first bitmap is 1 and the first bit of the second bitmap is 1 , a SSB with 0 is transmitted. If a second bit of the first bitmap is and the first bit of the second bitmap is 1 , a SSB with index 8 is transmitted. The first bitmap and the second bitmap may represent up to 64 SSB indexes.

[0232] In an example, an index of a SSB of the SSBs in a SSB burst may be determined based on the plurality of candidate SSBs and / or a location, corresponding to the SSB, in the first bitmap (or based on the first bitmap and the second bitmap). A candidate SSB may refer a candidate resource (e.g., time / frequency resources comprising PSS / PBCH / SSS in FIG. 17) where a SSB may be transmitted. For example, a candidate SSB in #1 transmits an SSB. A candidate SSB in #5 does not transmit an SSB. For example, a first index of a first SSB transmission occurring in a slot O OFDM symbol 2-5 is 0, and a second index of a second SSB transmission occurring in the slot 0 OFDM symbol 9-12 is 1 The wireless device may determine a plurality of indexes for the plurality of candidate SSBs. In the example of FIG. 17, an index = 4Docket No. 24-1248PCT or 6 for SSB will not be used or the base station does not transmit SSB with an index of 4 or 6 in each SSB burst for the cell. A maximum index in a SSB burst may be predetermined / predefined for a frequency band that the cell operates or may be determined based on a size of the third bitmap (or the combination of the first bitmap and the second bitmap).

[0233] FIG. 17 illustrates resources occupied for a PSS, a PBCH and a SSS respectively. For example, PSS in slot #0 presents in a symbol #2 (i.e., the starting symbol of a SSB) occupying 126 REs (between subcarrier number #56 and subcarrier number #182, in frequency domain, relative to a starting subcarrier of the SSB (SSB #1 ) comprising the PSS, the PBCH and the SSS. The SSS in slot #0 presents in a symbol #4 (i.e., 3rdsymbol from the starting symbol of the SSB) occupying 126 REs in a same frequency location to the PSS (e.g., between #56 and #182 subcarrier number). The PBCH presents between a symbol #3 and a symbol #5 (i.e., 2ndsymbol from the starting symbol of the SSB and 4thsymbol from the starting symbol of the SSB). Frequency locations / resources (or subcarriers) of the PBCH are 20 PRBs from the starting subcarrier of the SSB (i.e., subcarrier number #0 to #239, in frequency domain, relative to the starting subcarrier of the SSB) during the symbol #3 and the symbol #5 (i.e., 2ndsymbol from the starting symbol of the SSB, and 4thsymbol from the starting symbol of the SSB0. Frequency locations / resources of the PBCH are between the subcarrier #0 to subcarrier #47 and subcarrier #192 to subcarrier #239 in the symbol #4 (i.e., 3rdsymbol from the starting symbol of the SSB), that excludes resources of the SSS in the symbol #4. The wireless device may determine a plurality of resource elements (REs) as ‘Set to O’, where the plurality of REs will be set to zero (0). For example, the plurality of REs

[0234] In the time domain, an a SSB (i.e., SS / PBCH block) may consist of 4 OFDM symbols, numbered in increasing order from 0 to 3 within the SSB, where PSS, SSS, and PBCH with associated DM-RS are mapped to symbols as described in above (e.g., PSS in the starting symbol of the SSB, SSS in the 3rdsymbol from the starting symbol, PBCH between 2ndsymbol and 4thsymbol from the starting symbol). In the frequency domain, a SSB may comprise of 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239 within the SSB. In an example, a center frequency of the SSB may be configured to the wireless device via an absoluteFrequencySSB (e.g., in frequencylnfoDL, ServingCellConfigCommon). In FIG. 17, the slot comprises two SSBs (SSB#0 and SSB#1), where time / frequency resource elements of SSB#0 present in symbols #2-#5 with 20 PRBs bandwidth, and time / frequency resource elements of SSB#1 present in symbols #8 - #1 1 with 20 PRBs bandwidth.

[0235] In an example, a wireless device may be configured with a ServingCellConfig (and / or FrequencylnfoDL) indicating configuration parameters of a serving cell. The configuration parameters may comprise one or more of: an absoluteFrequencySSB, an absolutFrequencyPointA, one or more SCS- SpecificCarrier for one or more subcarrier spacing that the serving cell supports. A SCS-SpecificCarrier may comprise an offsetToCarrier and a subcarrierSpacing and a carrierBandwidth. The wireless deviceDocket No. 24-1248PCT may determine frequency resources of an SSB based on the absoluteFrequencyPointA, the aboluteFrequencySSB and / or the offsetToCarrier of the subcarrierSpacing, where the subcarrierSpacing is a subcarrier spacing of the SSB. For example, a starting subcarrier / PRB location of the serving cell is determined based on the absolutFrequencyPointA. A starting subcarrier / PRB location of the SSB may be determined based on the absoluteFrequencySSB. Frequency resources of the SSB in relationship to PRBs of the serving cell may be determined based on the offsetToCarrier if configured, where the offsetToCarrier indicates a gap / offset (e.g., Kssb) between a starting subcarrier of the SSB and a starting subcarrier of a PRB determined based on the absolutFrequencyPointA. If the offsetToCarrier is not configured, the wireless device may determine the gap / offset (e.g., Kssb) based on a frequency difference between the SSB (e.g., determined based on the absoluteFrequencySSB) and a point A (e.g., a frequency location of a PRB index zero (0) in a common PRB grid).

[0236] The UE may assume that SS / PBCH blocks transmitted with the same block index on the same center frequency location are quasi co-located with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, and, when applicable, spatial Rx parameters.

[0237] In an example, a base station may transmit, for a cell, a Master Information Block (MIB) on a PBCH of a SSB, to indicate configuration parameters (for CORESET#0) for a wireless device monitoring PDCCH for receiving a SIB1 message. In an example, a SSB comprising the MIB indicating the configuration parameters for the CORESET#0 may be referred as a cell-defining SSB of the cell.

[0238] The base station may transmit a MIB message (i.e., a message comprising an MIB) with a transmission periodicity of 80 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.

[0239] In an example, a base station may transmit, for a cell, a Master Information Block (MIB) on a PBCH of a SSB without indicating configuration parameters for a CORESETO or without scheduling information for receiving a SIB1 for the cell. In an example, the SSB without configuration parameters for the CORESET#0 may be referred as a non-cell defining SSB.

[0240] In an example, the non-cell defining SSB may be transmitted via one or more non-channel raster of a frequency band or one or more channel rasters of the frequency band.

[0241] In an example, the cell defining SSB may be transmitted via one or more non-channel raster of a frequency band or one or more channel rasters of the frequency band.

[0242] In an example, a wireless device may receive one or more configuration parameters for the cell defining SSB via a SIB1 , and one or more serving cell configuration common parameters (e.g., ServingCellConfigCommon, ServingCellConfigCommonSIB) .Docket No. 24-1248PCT

[0243] In an example, a wireless device may receive one or more configuration parameters for non-cell defining SSBs via one or more configuration parameters for a downlink bandwidth part for a cell (e.g., BWP-DownlinkDedicated) or via a RRC release for a small data transmission (e.g., Suspend Config).

[0244] In an example, when a wireless device detects an SSB, and the PBCH in the SSB indicates that there is no associated SIB1 , the wireless device may be pointed to another frequency at which the wireless device can search for an SSB that is associated with an SIB1 as well as a frequency range in which the wireless device may assume that 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.

[0245] In an example, a base station may transmit a SIB1 message with a periodicity of 160 ms.Alternatively or additionally, the base station may transmit the same SIB1 message with variable transmission repetition periodicity within 160 ms.

[0246] The default transmission repetition periodicity of SIB1 is 20 ms.

[0247] The base station may determine an actual transmission repetition periodicity based on network implementation.

[0248] In an example, a base station may transmit SSBs over / via each serving cell (e.g., a PCell or an SCell) of multiple serving cells configured for a wireless device. In an example, a wireless device may be configured with a serving cell. A base station may transmit one or more SSB bursts, in different frequency resources, in each serving cell. For example, the base station may transmit a first set of SSBs on a first frequency resource of a serving cell. The first set of SSBs may be cell defining SSBs. In addition to the first set of SSBs, the base station may transmit a second set of SSBs on a second frequency resource of the serving cell. The second set of SSBs may be non-cell defining SSBs.

[0249] A wireless device may receive either the first set of SSBs or the second set of SSBs for an active BWP of the serving cell. The wireless device may switch from receiving the first set of SSBs to receiving the second set of SSBs (or vice versa) based on a BWP switching between a first BWP and a second BWP of the serving cell. For example, the first BWP is an initial BWP of the cell. The second BWP may be a noninitial BWP of the cell.

[0250] If configured, the base station may periodically transmit one or more SSBs of the first set of SSBs. If configured, the base station may periodically transmit one or more SSBs of the second set of SSBs. In the specification, one or more SSBs and / or a SSB burst that will be periodically transmitted once configured / indicated may be referred as {always-on SSBs and / or always-on SSB burst}, {normal SSBs and / or normal SSB burst}, {non-on-demand SSBs and / or non-on-demand SSB burst}, {cell-defining / non- cell defining SSBs and / or cell-defining / non-cell defining SSB burst} or {(semi-)statically / permanently activated SSBs and / or (semi-)statically / permanently activated SSBs} or {SSBs of a cell or a SSB-burst of a cell} or {periodic SSBs and / or a periodic SSB burst} or {SSB, SSB burst}.Docket No. 24-1248PCT

[0251] A SSB may be a cell defining SSB or a non-cell defining SSB. A cell defining SSB may comprise information of a CORESET #0 where the wireless device may receive scheduling DCIs for PDSCH(s) comprising a system information block 1 (SIB1 ). A wireless device may acquire a SIB1 using a cell defining SSB. A non-cell defining SSB may not comprise information of the CORESET #0. A non-cell defining SSB may not indicate a scheduling information for a SIB1 . A wireless device may not acquire SIB1 based on a non-cell defining SSB.

[0252] A center frequency of a SSB may be on a channel raster or may be on a non-channel rater. A wireless device may search one or more channel rasters to identify a SSB of a cell during an initial access procedure. A wireless device may determine a center frequency of a SSB of a primary cell being on a channel raster.

[0253] A base station may transmit cell defining SSBs and / or non-cell defining SSBs for a first cell of a plurality serving cells of a wireless device. The base station may skip transmission of any SSBs (either cell defining SSBs or non-cell defining SSBs) for a second cell of the plurality of cells of the wireless device. In the specification, the first cell may be referred as a (serving) cell or a normal (serving)cell or a (serving) cell with always-on SSBs, or a (serving) cell with SSBs or a SSB cell. The second cell may be referred as a (serving) cell without SSB, an SSB-less (serving) cell, a serving cell with no SSBs, a serving cell with on- demand SSBs, or a serving cell without cell defining / non-cell defining SSBs.

[0254] In an example, a base station may transmit on-demand SSBs via / 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 or by RRC configurations or by transmitting a DCI indicating activation / deactivation). The base station may activate transmission of the on-demand SSBs and / or deactivate transmission of the on-demand SSBs. The base station may transmit the on-demand SSBs when the base station activates the transmission of the on-demand SSBs. The base station may not transmit the on-demand SSBs when the base station deactivates the transmission of the on-demand SSBs. The base station may transmit the on-demand SSBs while the on-demand SSB transmission is deactivated for the wireless device. The base station may transmit the on-demand SSBs, when activated, in addition to cell-defining SSBs or non-cell defining SSBs of the serving cell. The base station may transmit the on- demand SSBs for the serving cell that is an SSB-less cell (e.g., no cell-defining SSBs or non-cell defining SSBs are transmitted over / via the serving cell). In another example, the base station may transmit the on- demand SSBs via the serving cell, where the on-demand SSBs are deactivated for the wireless device and the on-demand SSBs are activated for a second wireless device. A status of an on-demand SSB may be a UE-perspective such that a base station transmits an on-demand SSB for a cell at a given time, where a first wireless device may consider the on-demand SSB is activated, and a second wireless device may consider the on-demand SSB is deactivated . An indication of the status or activation / deactivation of the on-Docket No. 24-1248PCT demand SSB may be given to each wireless device respectively via UE-specific signaling such as RRC, MAC CE and / or DCI.

[0255] 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 / trigger may be referred to as on-demand SSBs. The SSBs may be activated / deactivated may be referred as on-demand SSBs or semi-persistent SSBs or temporary SSBs. In the specification, one or more SSBs and / or a SSB burst that will be transmitted / stopped based on one or more triggers via RRC / MAC-CE / DCI may be referred as {on-demand SSBs and / or on-demand SSB burst}, {non-legacy SSBs and / or non-legacy SSB burst}, {non-periodic cell-defining / non-cell defining SSBs and / or non-periodic cell-defining / non-cell defining SSB burst} or {semi-persistent SSBs and / or semi-persistent SSBs} or {additional SSBs of a cell or additional SSB-burst of a cell} or {aperiodic SSBs and / or aperiodic SSB burst}.

[0256] FIG. 18 shows examples of a variety of SSB transmissions.

[0257] In an example, a base station may configure a serving cell (e.g., a PCell or a SCell, Cell 1 in FIG. 18) with (always-on / periodic) SSBs, in which case, the base station keeps transmitting the SSBs with periodicity (e.g., ssb-PeriodicityServingCeP) based on configuration parameters of the SSBs.

[0258] The SSBs may be transmitted in a way that a number (e.g., indicated by ssb-PositionsInBursf) 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. 17

[0259] In an example, the (always-on) SSBs may be present / configured on a PCell, and optionally be present / configured on a SCell. A wireless device may consider the always-on SSBs (or normal SSBs or cell-defining SSBs) being available to identify one or more candidate cells to camp-on during RRCJDLE / inactive state. The wireless device may consider a primary cell (PCell) transmits periodically cell defining SSBs (CD-SSBs). For a secondary cell (SCell), the wireless device may not assume that CD- SSBs are always present. Based on configuration, the secondary cell may be configured with one set of CD-SSBs. The secondary cell may be configured with one set of non-cell defining SSBs (NCD-SSBs). The secondary cell may be configured with one or more CD-SSBs and / or one or more NCD-SSBs. The secondary cell may be configured with one or more on-demand SSBs (OD-SSBs). The secondary cell may be configured with one or more CD-SSBs and one or more OD-SSBs. The secondary cell may be configured with one or more NCD-SSBs and one or more OD-SSBs. In the example, based on implementation, options available to the secondary cell may be extended to the primary cell without loss of generality.

[0260] The wireless device may obtain time and / or frequency synchronization (and / or beam alignment) with the serving cell based on SSBs (of OD-SSBs, CD-SSBs or NCD-SSBs or any combinations thereof).Docket No. 24-1248PCT

[0261] As shown in FIG. 18, a base station may configure a serving cell (e.g., a SCell, Cell 2 in FIG. 18) 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. 18) for obtaining time and / or frequency synchronization with this serving cell. For example, the wireless device may determine a reference cell for an SSB-less serving cell (e.g., Cell 1 in FIG. 18) based on one or more configuration parameters. For example, the one or more configuration parameters for a frequency information of downlink (e.g., FrequencylnfoDL) may comprise a frequency location of CD-SSBs (e.g., absoluteFrequencySSB) when a cell comprises CD-SSBs. For the SSB-less serving cell, the frequency location of CD-SSBs may be absent (e.g., absoluteFrequencySSB is absent in FrequencylnfoDL). The one or more configuration parameters may comprise a cell index of the reference cell (e.g , referenceCell in frequencylnfoDL) when the cell does not comprise CD-SSBs (e.g., for the SSB-less serving cell). The cell may not comprise NCD-SSBs either. For the SSB-less serving cell, if the cell index of the reference cell is not present in the one or more configuration parameters, the wireless device may determine a reference cell among one or more cells operating in a same frequency band to the SSB-less serving cell.

[0262] The PCell / PSCell / SCell as a reference cell for an SSB-less SCell may be indicated / configured via RRC messages (e.g., ServingCellConfigCommon IE and / or FrequencylnfoDL) of the serving cell.

[0263] The 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 with this serving cell.

[0264] The SSB-less configuration for a serving cell may be limited to cases when there is always a 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 (PR).

[0265] As shown in FIG. 18, 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 parallel ly 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).

[0266] There are multiple ways of providing the on-demand SSBs for this serving cell.

[0267] As a first way (as shown in FIG. 18) 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.

[0268] 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.Docket No. 24-1248PCT

[0269] In an example, the wireless device may trigger the transmission of the WUS based on channel measurement of discovery reference signals (DRSs) (if configured / transmitted) of the serving cell. The 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.

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

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

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

[0273] As a second way (as shown in FIG. 18) of providing the on-demand SSBs for a serving cell, the base station may trigger to transmit the on-demand SSB before, after or with activating the SCell. The base station may activate the SCell for a wireless device by transmitting a SCell activation / deactivation MAC CE. The base station may activate the on-demand SSB for the wireless device by transmitting an on-demand activation / deactivation MAC CE, and / or RRC message(s) and / or DCI messages.

[0274] After the SCell is activated, the base station may skip (or may stop / refrain from) transmitting the on-demand SSBs or the base station may deactivate the on-demand SSBs for the wireless device.

[0275] After the SCell is activated, the base station may continue transmitting the on-demand SSBs. In another example, the base station may activate transmission of the on-demand SSBs after the SCell is activated. The base station may determine when / whether to activate the SCell (together with the on- demand SSB transmissions) based on traffic load / request of wireless device(s) and / or requests from another base station via backhaul link.

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

[0277] Alternatively, the base station may activate / start / resume transmission of the on-demand SSBs by transmitting one or more MAC CEs (and / or RRC messages and / or DCIs) activating / starting / resuming the transmission of the on-demand SSBs to the wireless device. The base station may deactivate / stop / halt / pause transmission of the on-demand SSBs by transmitting one or more second MACDocket No. 24-1248PCTCEs (and / or RRC messages and / or DCIs) deactivating / stopping / halting / pausing the transmission of the on- demand SSBs to the wireless device. When on-demand SSBs are activated (or deactivated) via RRC messages, it may be deactivated (or activated) via one or more MAC CEs and / or RRC messages.

[0278] For multiple ways of providing the on-demand SSBs for this serving cell, a base station may activate and / or deactivate transmission of on-demand SSB(s) before, after or with a SCell activation for a wireless device. The base station may activate and / or deactivate transmission of on-demand SSB(s) in a first time for a first wireless device while may activate and / or deactivate transmission of the on-demand SSB(s) in a second time for a second wireless device. The first time and the second time may be different. In an example, one or more indications, to activate / deactivate on-demand SSB(s), may work in a way that the base station may transmit an on-demand SSB via a serving cell at a time T, where the first wireless device may consider the on-demand SSB is deactivated at the time T while the second wireless device may consider the on-demand SSB is activated at the time T.

[0279] In an example, OD-SSBs are NCD-SSBs. In an example, a base station may activate or deactivate OD-SSBs without RRC reconfiguration of a cell. In an example, a wireless device may determine a status (e.g , active or inactive, started or stopped, activated or deactivated, transmitted or skipped, and / or the like) of OD-SSBs during RRC_CONNECTED to a serving cell based on one or more MAC CEs (and / or DCIs) and / or RRC messages.

[0280] In an example, a base station may configure one or more tracking reference signal (TRS) for an activation of a secondary cell to a wireless device. In an example, the one or more TRS may comprise one or more CSI-RSs. The one or more TRS may be QCL-ed with one or more SSBs of a reference cell, for time / frequency tracking, for the secondary cell that is an SSB-less cell.

[0281] In an example, one or more SSB configurations for a SCell may be configured to a wireless device. SSB(s) of the one or more SSB configurations may comprise CD-SSB(s), and / or NCD-SSB(s) and / or OD- SSB(s).

[0282] In an example, a wireless device may receive from a base station one or more RRC messages (e.g., RRCReconfiguration IE). The one or more RRC messages may comprise configuration parameters (e.g., comprised in CellG roupConfig IE) of cell group. The configuration parameters of a cell group may comprise SCell configuration parameters of a plurality of SCells (e.g., sCeliToAdd Mod List IE).

[0283] The SCell configuration parameters of each SCell may comprise a SCell index (sCelllndex), cell common parameters (comprised in ServingCellConfigComm IE) of the SCell, cell parameters (comprised in ServingCellConfig IE) dedicated for the UE of the SCell, and / or a SSB measurement timing configuration (SMTC) (e.g., smtc).

[0284] In an example, a smtc is associated with a periodicityAndOffset and a duration.Docket No. 24-1248PCT

[0285] The smtc indicates SSB periodicity / offset / duration configuration of target cell for an NR SCell addition. The base station (or the network) sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in sCellConfigCommon.

[0286] The smtc is based on the timing of the SpCell of associated cell group. In case of inter-RAT handover to NR, the timing reference is the NR PCell .

[0287] In case of intra-NR PCell change (standalone NR) or NR PSCell change (EN-DC), the timing reference is the target SpCell. If the smtc field is absent and absoluteFrequencySSB is included, the wireless device uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message.

[0288] If the SCell is an SSB-less SCell (i.e , the IE absoluteFrequencySSB in ServingCellConfigCommon is absent), the smtc field is absent.

[0289] In an example, for a cell measurement, a wireless device may set up the first SMTC in accordance with the received periodicityAndOffset parameter (comprising a value of Offset and a value of Periodicity} of SMTC.

[0290] The first subframe of each SMTC occasion occurs at a system frame number (SFN) and subframe of the NR SpCell meeting the following condition, wherein a structure of a frame and a structure of a subframe may be implemented based on example of FIG. 7:SFN mod T= (FLOOR (Offset / 10)); if the Periodicity is larger than sf5: subframe = Offset mod 10; else: subframe = Offset or (Offset +5); with T= CE\L(Periodicityl'\0).

[0291] In an example, the base station (or the network) may configure the wireless device in RRC_CONNECTED to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in a measObject (e.g. maximum number of beams to be averaged and beam consolidation thresholds) and in a reportConfig (rsType to be measured, SS / PBCH block or CSI-RS). measObject and / or reportConfig is configured by the base station for the wireless device in one or more RRC messages.

[0292] The cell common parameters of the SCell may comprise downlink common configuration parameters (e.g., comprised in DownlinkConfigCommon IE), SSB burst configuration (ssb- PositionsinBurst), SSB periodicity (ssb-periodicityServingCell), SSB subcarrier spacing (ssbSubcarrrierSpacing) and SSB transmission power (ss-PBCH-BlockPower).Docket No. 24-1248PCT

[0293] The downlink common configuration parameters of the SCell may comprise downlink frequency information (e.g., comprised in Frequency InfoDL), configuration parameters of initial downlink BWP etc. The downlink frequency information of the SCell may comprise a parameter (absoluteFrequencySSB) indicating the frequency of the SSB to be used for this SCell.

[0294] If the parameter (absoluteFrequencySSB) is absent, the wireless device obtains timing reference from the SpCell or an SCell if applicable as described in TS 38.213, or from the SpCell or an SCell indicated by referenceCell, or from the "default cell" if the referenceCell is absent.

[0295] The parameter is an ARFCN (absolute radio frequency channel number) value (AFRCN-ValueNR) specified for NR system. The downlink frequency information of the SCell may comprise a parameter (absoluteFrequencyPointA) indicating the absolute frequency position of the reference resource block (Common RB 0) of the SCell.

[0296] The downlink frequency information of the SCell may comprise a parameter (referenceCell) indicating a reference cell, i.e. the cell which provides the timing reference and AGC source for this SCell, if this SCell is an SSB-less SCell. If the reference cell is an SCell or PSCell, it should be an activated SCell or activated PSCell. If this field (referenceCell is absent, a "default cell" is the reference cell.

[0297] FIG. 19 shows an example of on-demand SSB transmissions for a SCell.

[0298] In an example, on-demand SSB transmissions may be used by a base station for network energy saving (operation / configuration / mode / state) on a SCell. When there are no / less active wireless devices in a SCell, the base station may stop always-on SSB transmissions via the SCell or may not transmit / configure the always-on SSB transmissions.

[0299] In an example, when the base station determines to activate the SCell for a wireless device, the base station may trigger on-demand SSB transmissions for the wireless device.

[0300] In an example, when a wireless device determines to trigger the on-demand SSB transmissions for a SCell, the wireless device may transmit uplink signals indicating a trigger of the on-demand SSB transmission on the SCell.

[0301] In the example of FIG. 19, on-demand SSBs may be transmitted on an SCell from time instance A to time instance B. The wireless device may receive, in a slot, from a base station a signaling / command indicating / triggering transmissions of the on-demand SSBs.

[0302] In an example, the time instance A when the on-demand SSBs are transmitted / start to be transmitted via the SCell may be determined as at least one of: a number (T) of slots after the slot where the wireless device receives the signaling / command from the base station to trigger the on-demand SSB transmissions or transmits HARQ-ACK corresponding to the signaling / command; the slot where the base station provides / transmits the signaling / command to trigger the on-demand SSB transmissions; the time when the current scenario (e.g., Scenario# 1 during which the SCell is configured to the wireless device butDocket No. 24-1248PCT before the wireless device receives a SCell activation command) transitions to the next scenario (e.g., Scenario# 2 during which the UE has received the SCell activation command); or the first transmission occasion of on-demand SSB burst T slots after the slot where the wireless device receives the signaling / command from the base station to trigger the on-demand SSB transmissions or transmits HARQ- ACK corresponding to the signaling / command.

[0303] In an example, the time instance B may be determined based on examples of FIG. 20 which will be described later in this specification.

[0304] In the example of FIG. 19, the on-demand SSBs may be transmitted in different cases (e.g., Case 1 , Case 2), in terms of whether always-on SSBs are transmitted via the SCell.

[0305] In the example of FIG. 19, in a Case 2, the base station may transmit always-on SSBs (e.g., legacy SSBs, non-on-demand SSBs, non-on-demand SSB burst(s)) periodically on the SCell regardless of whether the SCell is in an activated state or in a deactivated state if the always-on SSBs are configured on the SCell.

[0306] In the example of FIG. 19, for on-demand SSBs configured with Case 1 , the base station does not transmit always-on SSBs via the SCell before the SCell is activated or before the on-demand SSBs are transmitted or after / before the SCell is activated. In Case 1 , the base station may not transmit non-on- demand SSBs on the SCell. When the base station transmits the on-demand SSBs via the SCell, the on- demand SSBs may be only SSBs on the SCell.

[0307] In the example of FIG. 19, for on-demand SSBs configured with Case 2, the base station transmits always-on SSBs (e.g., with periodicity P1) via the SCell regardless of whether the on-demand SSBs are transmitted or not and / or regardless of whether the SCell is in the activated state or in the deactivated state. The base station transmits the on-demand SSBs (e.g., with periodicity P2) from time instance A to time instance B. After the on-demand SSBs are completed, e.g., at time instance B, the base station may stop the on-demand SSB transmission and continue the always-on SSBs transmissions.

[0308] In the example of FIG. 19, the time instance A on which the on-demand SSBs are transmitted on the SCell may be based on an on-demand SSB triggering / command / signaling.

[0309] In an example, the on-demand SSB triggering / command / signaling may be a RRC message, a MAC CE and / or a DCI.

[0310] In an example, depending on whether the wireless device receives the on-demand SSB triggering / command / signaling before or after the wireless device receives a SCell activation command, there may be two scenarios.

[0311] For example, in a first scenario (Scenario 1) of on-demand SSB triggering, after a SCell is configured (e.g., by RRC messages) and before the SCell is activated, the base station transmits the on- demand SSB triggering / command / signaling indicating transmission of the on-demand SSBs via the SCellDocket No. 24-1248PCT before the wireless device receives, and / or the base station transmits, a SCell Activation / deactivation MAC CE (or a SCell activation command) indicating an activation of the SCell. The wireless device, based on the on-demand SSBs (with a transmission periodicity P1 ), may perform downlink synchronization, AGC tuning and / or L3 measurement / report for the SCell.

[0312] In an example, the on-demand SSBs may be transmitted with shorter periodicity than the legacy / always-on SSBs on the SCell. Based on the L3 measurement / report of the SCell, the base station may transmit the SCell activation / deactivation MAC CE indicating the activation of the SCell.

[0313] In an example, the wireless device may determine that the SCell is a known cell based on the L3 measurement / report obtained on the on-demand SSBs of the SCell and when the wireless device receives the MAC CE.

[0314] In an example, the wireless device may determine whether a SCell is a known cell or a unknow cell.

[0315] In an example, the wireless device may activate the SCell with a shorter SCell activation delay based on determining that the SCell is a known cell. During the SCell activation delay, the wireless device may continue using the on-demand SSBs for L1 CSI report.

[0316] After the wireless device transmits a valid L1 CSI report, based on the on-demand SSBs, of the SCell to the base station, the wireless device completes the SCell activation after which the SCell is considered, by the wireless device, in the activated state.

[0317] Receiving the on-demand SSB command / trigger and / or the on-demand SSBs, before the SCell activation command is received, may enable the wireless device to reduce SCell activation delay.

[0318] For example, in a second scenario (Scenario 2) of on-demand SSB triggering, after a SCell is configured (e.g., by RRC messages), the base station transmits the on-demand SSB triggering / command / signaling, together with a SCell activation command and / or after / before the SCell activation command, indicating transmission of the on-demand SSBs via the SCell. The wireless device, based on receiving the SCell activation command the on-demand SSB triggering / command / signaling, may perform downlink synchronization, AGC tuning and / or L3 measurement / report based on the on-demand SSBs, for the activation of the SCell or during the SCell is active.

[0319] In an example, the on-demand SSBs may be transmitted with shorter periodicity than the legacy / always-on SSBs on the SCell. In an example, before receiving the SCell activation command, the wireless device may determine that the SCell is an unknow SCell (e.g., if no always-on SSBs are configured for the SCell). Based on the L3 measurement / report of the SCell, the wireless device may determine that the SCell is a known cell based on the L3 measurement / report obtained on the on-demand SSBs of the SCell.Docket No. 24-1248PCT

[0320] In an example, the wireless device may activate the SCell with a longer SCell activation delay compared with scenario 1 . During the SCell activation delay, the wireless device may continue using the on-demand SSBs for L1 CSI report. After the wireless device transmits valid L1 CSI report, based on the on-demand SSBs, of the SCell to the base station, the wireless device completes the SCell activation after which the SCell is in the activated state.

[0321] Receiving the on-demand SSB command / trigger together with the SCell activation command may enable the wireless device to reduce power consumption of L1 / L3 measurement for the SCell.

[0322] In an example, different scenarios (e.g., Scenario 1 and Scenario 2) may be applied by the base station for different purposes.

[0323] In an example, the base station may use Scenario 1 for on-demand SSB triggering for a SCell when the base station is able to predict / estimate a time for the SCell activation, e.g., based on traffic pattern of the wireless device, power limitation of the wireless device, moving speed of the wireless device, location of the wireless device, etc.

[0324] In an example, the base station may use Scenario 2 for on-demand SSB triggering for a SCell when the base station is not able to predict / estimate a time for the SCell activation.

[0325] FIG. 20 shows an example of on-demand SSB transmissions for a SCell, e.g., based on examples of FIG. 19. The base station and / or the wireless device may determine, based on multiple options (e.g., Option 1 , Option 1A, Option 2, Option 3, Option 4, etc.), the time duration, of on-demand SSB transmission, between time instance A and time instance B during which the on-demand SSBs are transmitted on a SCell.

[0326] In the example of FIG. 20, in Option 1 , the base station, after transmitting the on-demand SSB trigger (e.g., after the time gap as described above with respect to FIG. 19), may start to transmit the on- demand SSBs with a periodicity (P1) from time instance A. The base station may keep transmitting the on- demand SSBs after the on-demand SSB trigger. The wireless device may determine / assume one or more on-demand SSB bursts of the on-demand SSB after the time instance A in Option 1 . The base station may continue the periodic transmission of the on-demand SSBs at least during the SCell being active.

[0327] In the example of FIG. 20, in Option 1A, the base station, after transmitting the on-demand SSB trigger (e.g., after the time gap), may transmit the on-demand SSBs with a periodicity (P1) from time instance A to time instance B. The base station and / or the wireless device determine the time instance B based on an indication (e.g., on-demand SSB turn-off indication) from the base station indicating that the on-demand SSBs are stopped on the SCell. The base station may stop the on-demand SSBs from time instance B. The wireless device may determine / assume one or more on-demand SSB bursts of the on- demand SSB after the time instance A until the on-demand SSB being deactivated by the base station (or receiving the indication).Docket No. 24-1248PCT

[0328] In the example of FIG. 20, in Option 2, the base station, after transmitting the on-demand SSB trigger (e.g., after the time gap), may transmit the on-demand SSBs from time instance A to time instance B. The base station and / or the wireless device determine the time instance B based on a time duration indicated by the on-demand SSB trigger. The base station may stop the on-demand SSBs from time instance B.

[0329] In the example of FIG. 20, in Option 3, the base station, after transmitting the on-demand SSB trigger (e.g., after the time gap), may transmit the on-demand SSBs from time instance A to time instance B. The base station and / or the wireless device determine the time instance B based on a total number of transmissions of the on-demand SSBs / SSB bursts indicated by the on-demand SSB trigger. The base station may stop the on-demand SSBs from time instance B. In an example, a base station may transmit N (N>=1) times of on-demand SSB burst(s) based on Option 3 from a time instance A. The wireless device may consider / assume / determine the on-demand SSB burst(s) as active or being transmitted from the time instance A, and during N times of a periodicity of the on-demand SSB burst(s).

[0330] In the example of FIG. 20, in Option 4, the base station, after transmitting the on-demand SSB trigger (e.g., after the time gap), may transmit the on-demand SSBs from time instance A to time instance B. The base station and / or the wireless device may determine the time instance B based on Options 1A / 2 / 3. The base station may stop the on-demand SSBs from time instance B and transmit second SSBs (e.g., another set of SSBs) with different periodicity, e.g., P2. This case may be referred to as an SSB periodicity adaptation (e.g., from P1 to P2) In an example, a base station may transmit on-demand SSB burst(s) with a first periodicity (P1 in FIG. 20) from a time instance A to a time instance B. After the time instance B, the base station may transmit the on-demand SSB burst(s) with a second periodicity (P2 in FIG. 20). Option 4 illustrates this scenario. The wireless device may assume the first periodicity of the on- demand SSB burst(s) from the time instance A to the time instance B and the second periodicity of the on- demand SSB burst(s) after the time instance B

[0331] Examples of FIG. 19 and / or FIG. 21 may be combined for different purposes, e.g., trade- off / balance among network energy saving of the base station, L3 measurement accuracy, SCell activation delay and / or power consumption of the wireless device. In an example, Case 1 of FIG. 19 may be combined with Scenario 1 (and / or with option 1A / 2 / 3 of FIG. 20) to reduce both power consumption of the base station and / or the wireless device and / or SCell activation delay. Case 2 of FIG. 19 may be combined with Scenario 2 0 (and / or with option 1 A / 2 / 3 of FIG. 20) to improve L3 measurement accuracy of the wireless device and / or reduce power consumption of the wireless device, etc.

[0332] In an example, there are multiple ways of providing an indication of deactivation of on-demand SSB transmission for a serving cell for a wireless device. A first example (lnd-Option#1) is to use an on-Docket No. 24-1248PCT demand activation / deactivation MAC CE that indicates a deactivation of on-demand SSB. For example, the first example may be used to support Option 1A in FIG. 20.

[0333] A second example (Ind-Option #1A) is to use a RRC message that configures a status of the on- demand SSB as deactivated. The RRC message may comprise configuration parameters of the on- demand SSB with a status flag to indicate whether the on-demand SSB is active or inactive (or deactivated). For example, the second example may be used to support Option 1 in FIG. 20. The RRC may reconfigure the configuration parameters to change the status from activated to deactivated or vice versa. In an example, if the base station configures a plurality of on-demand SSB configurations for the wireless device for the serving cell, only one SSB configuration of the plurality of on-demand SSB configurations may be activated at a given time. Until on-demand SSB based on the one SSB configuration is deactivated, the wireless device may not expect to receive another RRC message indicating another on-demand SSB configuration of the plurality of on-demand SSB configurations are activated.

[0334] In another example, the base station may transmit one or more RRC messages comprising an active on-demand SSB configuration index and one or more on-demand SSB configurations, where each of the one or more on-demand SSB configurations may comprise an on-demand SSB configuration index. The active on-demand SSB configuration index may indicate an on-demand SSB configuration of the one or more on-demand SSB configurations, that is activated by RRC message(s) indicating activation / deactivation of on-demand SSB. For example, the active on-demand SSB configuration index may indicate a pre-fixed value (e.g., 0) or a pre-determined value (e.g., a maximum number of on-demand SSB configurations, a maximum value, (or a some of the maximum value and 1), that an on-demand SSB configuration index may have, a reserved value). When the RRC message(s) indicates different value of on-demand SSB configuration, previous on-demand SSB is deactivated and aa new on-demand SSB configuration indicated by the RRC message(s) is activated. When the active on-demand SSB configuration index indicates the pre-fixed value or the pre-determined value, the wireless device may determine that on-demand SSB(s) are deactivated.

[0335] A third example (Ind-Option #2) is to transmit / configure one or more RRC messages comprising a parameter of N, where N may represent a number on-demand SSB bursts to be transmitted after the on- demand SSB is activated For example, the third example may be used to support Option 2 in FIG 20. The parameter N may be an integer value. The wireless device may determine N number of on-demand SSB bursts are transmitted after the on-demand SSB is activated. For example, if the on-demand SSB is activated in a middle of an on-demand SSB burst, the wireless device may start counting at a next available on-demand SSB burst where the wireless device determines an earliest on-demand SSB (or an on-demand SSB with a lowest SSB index of the on-demand SSB burst) is activated. The wireless device may count N full on-demand bursts after the on-demand SSB is activated. The wireless device may determine that theDocket No. 24-1248PCT on-demand SSBs are deactivated a time T, where i) T is at the moment (T_m) that the wireless device has counted N full on-demand SSB bursts or II) T_m + d (e.g., d = K slots) or ill) T is at the movement that the wireless device may determine an earliest on-demand SSB of an on-demand SSB burst (or an on-demand SSB with a lowest SSB index of the on-demand SSB burst) where the on-demand SSB burst is a next configured on-demand SSB burst if not deactivated. If this option is used, N may be also used for performing L3 RRM measurements before the serving cell is activated. For example, the wireless device may measure N samples of transmissions of the on-demand SSB before sending a report of the L3 RRM measurement on the on-demand SSB. For example, when the wireless device receives a SCell activation MAC CE which is completed before receiving N times of transmissions of the on-demand SSB, the wireless device may deactivated transmission of the on-demand SSB at earlier time between {a first time when the wireless device completes the serving cell activation based on the SCell activation MAC CE, a second time determined based on N transmissions of the on-demand SSB}. For example, the wireless device may not be required to perform measurement (e.g., L3 RRM) based on the on-demand SSB after the serving cell is activated when Ind-Option #2 is used.

[0336] A fourth example (Ind-Option #3) is to transmit / configure one or more RRC messages comprising a parameter of an on-demand transmission window. For example, the wireless device may determine one or more on-demand SSB bursts will be transmitted during the on-demand transmission window after the on- demand SSB is activated. The wireless device may determine that the on-demand SSB transmission will be deactivated after the on-demand transmission window after the after the on-demand SSB is activated The on-demand transmission window may be multiple of a periodicity of the on-demand SSB burst (e.g., M times of the periodicity) or may be a number of slots or subframes or frames. The fourth example may be used to support option 1 or Option 3 in FIG. 20. If this option is used, the on-demand SSB transmission window may be also used for performing L3 RRM measurements before the serving cell is activated. For example, the wireless device may measure M samples of transmissions of the on-demand SSB, during the on-demand SSB transmission window, before sending a report of the L3 RRM measurement on the on- demand SSB. For example, when the wireless device receives a SCell activation MAC CE which is completed before the end of the on-demand SSB transmission window, the wireless device may deactivated transmission of the on-demand SSB at earlier time between {a first time when the wireless device completes the serving cell activation based on the SCell activation MAC CE, a second time determined based on the on-demand SSB transmission window e.g., an end time of the on-demand SSB transmission window}. For example, the wireless device may not be required to perform measurement (e.g., L3 RRM) based on the on-demand SSB after the serving cell is activated when Ind-Option #3 is used.

[0337] In a fifth example (Ind-Option #4), the wireless device may determine that the on-demand SSB transmission is deactivated when the wireless device receives a SCell deactivation MAC CE for the servingDocket No. 24-1248PCT cell. The wireless device may determine that the on-demand SSB transmission will be deactivated at a same time, and / or after that the serving cell is deactivated based on the SCell deactivation MAC CE. The fifth example (Ind-Option #4) may be used in a combination with other example(s). The fifth example may be used as a default behavior. For example, when the wireless device receives the SCell deactivation MAC CE and the on-demand SSB transmission is still activated, the wireless device may determine the on- demand SSB transmission is also deactivated. The on-demand SSB transmission may be deactivated before receiving the SCell deactivation MAC CE or before deactivating the serving cell.

[0338] In a sixth example (Ind-Option #4A), the wireless device may determine that the on-demand SSB transmission is deactivated when the wireless device determines a timer for SCell deactivation (e.g., a sCellDeactivationTimer) is expired for the serving cell. The wireless device may determine that the on- demand SSB transmission is deactivated at a same time and / or after that the serving cell is deactivated based on expiry of the sCellDeactivationTimer. The wireless device may determine / consider that the on- demand SSB transmission is deactivated after the serving cell is deactivated. In another example, the wireless device may determine that the on-demand SSB transmission is deactivated in response to switching a dormant BWP of the serving cell. The wireless device may determine to activate / re-activate the on-demand transmission of the serving cell in response to switching to a non-dormant BWP of the serving cell while the sCellDeactviationTimeris running. This will allow on-demand SSB to be active while the serving cell is actively used for the wireless device.

[0339] For the Ind-Option #4 and Ind-Option #4, (i.e., if on-demand SSB is deactivated upon the serving cell is deactivated), the on-demand SSB may be referred as a semi-periodic SSB or a semi-periodic RS or a semi-persistent SSB. The wireless device may consider that the on-demand SSB, that is the semiperiodic SSB, is active while the serving cell is active. The wireless device may assume / consider / monitor the on-demand SSB transmission during the serving cell is active, if / since the on-demand SSB has been activated.

[0340] Alternatively, the wireless device may determine that the on-demand SSB transmission is still active / activated while the active BWP of the serving cell is a dormant BWP. The wireless device, however, may not perform any measurements based on the on-demand SSB on the dormant BWP. Alternatively, the wireless device may be configured with a status of the on-demand SSB transmission via the dormant BWP (i.e., when the dormant BWP is an active BWP of the serving cell). The wireless device may determine the status of the on-demand SSB transmission via the dormant BWP (i.e., when the dormant BWP is an active BWP of the serving cell) based on one or more measurement configurations on the dormant BWP. For example, if the wireless device is configured with L1-RSRP measurement based on the on-demand SSB on the dormant BWP, the wireless device may consider that the on-demand SSB transmission is active on the dormant BWP. If there is no measurement configuration on the dormant BWP utilizing the on-demand SSB,Docket No. 24-1248PCT the wireless device may assume / consider that the on-demand SSB transmission will be deactivated during the active BWP being the dormant BWP.

[0341] In another implementation of the sixth example (Ind-Option #4B), the wireless device may determine that the on-demand SSB transmission is deactivated when the wireless device is configured with a timer for a BWP inactivity timer (e.g., a bwp-lnactivityTimer) that is expired for a BWP of the serving cell. In the example, an on-demand SSB configuration parameters for the on-demand SSB transmission may be associated with the BWP. The BWP may not be a default BWP indicated by defaultDownlinkBWP-ld in a ServingCellConfig of the serving cell. In response to switching to the default BWP of the serving cell, the wireless device may determine the on-demand SSB transmission via the BWP is deactivated. The wireless device may determine that the on-demand SSB transmission will be deactivated at a same time that the BWP is deactivated or switched to another BWP or the BWP becomes non-active BWP based on expiry of the bwp-lnactivityTimer. Similar example may be applied to a case when the wireless device receives a downlink control command to switch from the BWP to another BWP (e.g., the BWP becomes inactive or an active BWP is not the BWP). In an example, the example may be used when on-demand SSB configurations are comprised in a BWP (e.g., BWP-DowniinkDedicated IE may comprise the on-demand SSB configurations).

[0342] In a seventh example (Ind-Option #5), the wireless device may determine that the on-demand SSB transmission will be deactivated at a same ti me / after / around when the wireless device completes the serving cell activation (i.e. , when the wireless device determines that the serving cell is activated).

[0343] In an eighth example (Ind-Option #6), the base station may transmit a DCI that is a U E-specific or a group-common to indicate activation / deactivation of the on-demand SSB transmission.

[0344] In an example, the base station may transmit one or more second RRC messages indicating / comprising configuration parameter(s) to indicate which indication option (or which example method) is used for deactivating an on-demand SSB transmission for the serving cell. The parameter(s) may indicate the indication option for both activation and deactivation of the on-demand SSB transmission or only indicate the indication option for the deactivation. For example, of the parameter(s) indicates the indication option for both activation and deactivation of the on-demand SSB transmission, the first example uses the on-demand SSB activation / deactivation MAC CE to activate / deactivate the on-demand SSB transmission. The second example uses the RRC messages. The third example may be used with the first example or the second example of the activation of the on-demand SSB transmission, while the third example is used for the deactivation. The fifth / sixth example is used, the wireless device may determine the on-demand SSB transmission is activated when the serving cell is activated (for the fourth example) or a sCellDeactivationTimer is running (for the fifth example) and the on-demand SSB has been activated by the first example and / or the second example. If the seventh example is used, other example(s) may be used toDocket No. 24-1248PCT activate the on-demand SSB transmission. If the eighth example may be used to indicate either activation or deactivation of the on-demand SSB transmission .

[0345] In an example, different option may be configured in different Cases / Scenarios shown in FIG. 19. For example, if a measurement object is configured for the serving cell, where the measurement object indicates on-demand SSB, Ind-Option #3, Ind-Option #4 or Ind-Option #5 may be used. For example, for Case #2 in FIG. 19, any option may be considered. For Case #1 in FIG. 19, options (e.g., Ind-Option #4 or #4A) that may not deactivate the on-demand SSB during the serving cell is active may be used.

[0346] These embodiments may reduce signaling overhead and / or minimizing cases where the wireless device may not be able to perform measurements due to the on-demand SSB transmissions are deactivated while the serving cell is active.

[0347] In an example, the indication of deactivation (and / or activation) of on-demand SSB transmission may be transmitted via the serving cell and / or another serving cell (e.g., PCell, SCell).

[0348] In an example, a time instance A and / or a time instance B in FIG. 20 may be indicated to a wireless device via one or more RRC messages / configuration parameters and / or MAC CE and / or DCI. For example, one or more on-demand SSB configuration may be comprised in a serving Cell Config of a serving cell and / or bwp-Dedicated in a BWP-downlink of a BWP of the serving cell. For example, a wireless device may be configured with a cell that is a serving cell. The cell may be configured with a plurality of downlink BWPs comprising a first BWP and a second BWP. The wireless device may receive one or more RRC messages comprising configuration parameters of the first BWP and the second BWP. In the example, configuration parameters of the first BWP may comprise first on-demand SSB configuration(s). In an example, the second BWP may comprise second on-demand SSB configuration(s).

[0349] For example, an on-demand SSB configuration of the first on-demand SSB configuration(s) or the second on-demand SSB configuration(s) may comprise one or more parameters indicating a) a subcarrier spacing of on-demand SSB; b) physical cell identifier scrambled / used in the on-demand SSB; c) time domain location of an on-demand SSB burst e.g., a SFN offset and / or a half frame index; d) downlink transmit power of the on-demand SSB; e) an index of the on-demand SSB configuration; and f) bitmap(s) of on-demand SSB transmissions in an on-demand SSB burst; g) initial status / state of the on-demand SSB; h) a BWP index where the on-demand SSB will be transmitted / activated; and j) a center frequency of the on- demand SSB (absoluteSSBFrequency).

[0350] In an example, a current active BWP of the cell is a third BWP that is different from the first BWP and the second BWP. The third BWP may not comprise or may not be configured with on-demand SSB configuration(s). When an on-demand SSB configuration is associated with a BWP (e.g., the on-demand SSB configuration is provided for the BWP or comprised in a bwp-Dedicated of the BWP), and the BWP is not active, the wireless device may consider on-demand SSB transmission based on the on-demand SSBDocket No. 24-1248PCT configuration is deactivated For example, when the third BWP is active, the wireless device may consider / determine that on-demand SSB transmissions based on the first on-demand SSB configurations and the second on-demand SSB configurations are deactivated.

[0351] When the wireless device receives a downlink command (e.g., RRC, MAC CE, DCI) indicating to switch to the first BWP, the wireless device may determine that on-demand SSB transmission based on the first on-demand SSB configuration(s) of the first BWP being activated based on a condition. For example, the condition may comprise a case where an initial status of on-demand SSB of the first on-demand SSB configuration(s) being ‘activated’. If an on-demand SSB configuration of the first on-demand SSB configuration(s), where the on-demand SSB configuration is indicated to be used for the first BWP, is configu red / i nd icated with an initial status of ‘activated’ or ‘active’, the wireless device may determine to activate or may assume that on-demand SSB transmissions via the first BWP based on the first BWP being activated or the first BWP becoming an active BWP. For example, the condition may comprise a parameter (e.g., activating in a BWP switching) indicating activating on-demand SSBs in a BWP switching.

[0352] When the wireless device receives a downlink command indicating switching to the second BWP from the first BWP, the wireless device may deactivate on-demand SSB transmission based on the first on- demand SSB configuration(s). In the example, the wireless device may, optionally / additionally , activate on- demand SSB transmission based on the second on-demand SSB configuration(s) based on the condition.

[0353] In an example, the first BWP and the second BWP may be different from an initial DL BWP. A BWP index of the first BWP may not be zero (0). A BWP index of the second BWP may not be zero (0). In the example, the initial DL BWP (BWP with a BWP index = zero(0)) of the serving cell may not be configured / indicated with SSB configuration(s) (e.g., the initial DL BWP does not comprise CD-SSB or NCD-SSB). The first BWP may be a first active DL BWP (indicated by firstActiveDownlinkBWP-ld in the ServingCellConfig). The BWP index of the first BWP may be firstActiveDownlinkBWP-ld. Alternatively, the second BWP may be the first active DL BWP.

[0354] In the example, the wireless device may be configured with one or more random access resources for the first BWP and / or the second BWP based on the first on-demand SSB configuration(s) and / or the second on-demand SSB configuration(s).

[0355] In case the initial DL BWP of the serving cell does not transmit a SSB or the serving cell is a SSB- less SCell , when the wireless device receives a PDCCH order initiating a random access procedure in the third BWP and the third BWP is not configured with a random access resource (and / or PUSCH for Type-2 random access procedure), the wireless device may switch to the first active downlink BWP (e.g., to the first BWP or the second BWP).

[0356] In the example, the wireless device may be switching to the first active downlink BWP if the initial DL BWP is not configured with a random access resource (and / or PUSCH for Type-2 random accessDocket No. 24-1248PCT procedure). If the initial DL BWP is configured with the random access resource (and / or PUSCH for Type-2 random access procedure), the wireless device may switch to the initial DL BWP.

[0357] In an example, if the serving cell is an SSB-less SCell or in the Case #1 of FIG. 19, a wireless device may expect to be configured with on-demand SSB configuration parameters / on-demand SSB transmission at least on an initial downlink BWP of the serving cell. For example, the on-demand SSB configuration parameters may be comprised in a ServingCellConfig and / or BWP-common of the serving cell. For example, the on-demand SSB configuration parameters may be comprised in a BWP of the initial downlink BWP. In the example, ServingCellConfig of the serving cell may indicate a firstActiveDownlinkBWP-ld = zero (e.g. , indicating the initial downlink BWP). The serving cell may be activated with the initial downlink BWP. In another example, with the Case #1 of FIG. 19, the wireless device may consider a default downlink BWP may be same as a first active downlink BWP (e.g., a defaultDownlinkBWP-ld in the ServingCellConfig is same to the firstActiveDownlinkBWP-ld). In an example, a wireless device may not be configured with on-demand SSB (configuration parameters / transmissions) for a dormant BWP of a serving cell. The wireless device may not perform measurements based on the on-demand SSB when the dormant BWP of the serving cell is an active BWP of the serving cell. The wireless device may deactivate one or more on-demand SSB transmissions in response to receiving a downlink command to switch to the dormant BWP of the serving cell.

[0358] This may allow low overhead and reduce unnecessary frequency retuning to perform measurements when on-demand SSB transmissions become outside of an active BWP

[0359] In an example, when receiving the PDSCH scheduled with SI-RNTI and the system information indicator in DCI is set to 0, a wireless device may assume that no SS / PBCH block, after puncturing if applicable, is transmitted in REs used by the wireless device for a reception of the PDSCH. The wireless device may not perform a rate matching around the SS / PBCH block for receiving PDSCH comprising SIB(s) and a scheduling DCI indicates that the SIB(s) is a SIB1 (by the system information indicator being set to 0).

[0360] When receiving the PDSCH scheduled with SI-RNTI and the system information indicator in DCI is set to 1 , RA-RNTI, MSGB-RNTI, P-RNTI or TC-RNTI, the wireless device may assume SS / PBCH block transmission according to ssb-PositionsinBurst, and if the PDSCH resource allocation overlaps with PRBs containing SS / PBCH block transmission resources the wireless device may assume that the PRBs containing SS / PBCH block transmission resources, after puncturing if applicable, are not available for PDSCH in the OFDM symbols where SS / PBCH block is transmitted. A wireless device may expect a configuration provided by ssb-PositionsinBurst in ServingCellConfigCommon to be same as a configuration provided by ssb-PositionsinBurst in SIB1.Docket No. 24-1248PCT

[0361] When receiving PDSCH scheduled by PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, CS- RNTI, G-RNTI, G-CS-RNTI, MCCH-RNTI, Multicast MCCH-RNTI or PDSCHs with SPS, the REs, corresponding to the configured or dynamically indicated resources, are not available for PDSCH. Furthermore, the wireless device may assume SS / PBCH block transmission according to ssb- PositionsInBurst if the PDSCH resource allocation overlaps with PRBs containing SS / PBCH block transmission resources, after puncturing if applicable, and the wireless device may assume that the PRBs containing SS / PBCH block transmission resources, after puncturing if applicable, are not available for PDSCH in the OFDM symbols where SS / PBCH block associated with the same PCI is transmitted.

[0362] A wireless device may not be expected to handle the case where PDSCH DM-RS REs are overlapping, even partially, with any RE(s) not available for PDSCH.

[0363] The procedures for PDSCH scheduled by PDCCH with DCI format 1_1 described in this section equally apply to PDSCH scheduled by PDCCH with DCI format 1_2, by applying only the parameters of rateMatchPatternGroupI DCI-1 -2, rateMatchPatternGroup2DCI-1-2 instead of rateMatchPatternGroupI and rateMatchPatternGroup2. The procedures for PDSCH scheduled by PDCCH with DCI format 1_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1_3. The procedures for PDSCH scheduled by PDCCH with DCI format 1_0 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4_0, by applying only the parameters of rateMatchPatternToAddModList configured in pdsch-ConfigMCCH or pdsch-ConfigMTCH. The procedures for PDSCH scheduled by PDCCH with DCI format 1_0 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4_1 , and the procedures for PDSCH scheduled by DCI format 1_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4_2 by applying only the parameters of rateMatchPatternToAddModList, rateMatchPatternGroupI and rateMatchPatternGroup2 configured in pdsch-ConfigMulticast.

[0364] A wireless device may be configured with any of the following higher layer parameters indicating REs declared as not available for PDSCH.

[0365] i) rateMatchPatternToAddModList given by PDSCH-Config, by pdsch-ConfigMulticast, by ServingCellConfig or by ServingCellConfigCommon, or by pdsch-ConfigMCCH or pdsch-ConfigMTCH and configuring up to 4 RateMatchPattern(s) per BWP and up to 4 RateMatchPattern(s) per serving-cell. The RateMatchPatterns configured for MBS multicast are counted into the ones that are configured per BWP. The RateMatchPattern(s) configured for MBS broadcast or for MBS multicast in RRC_INACTIVE_state is counted into the ones that are configured per serving-cell.

[0366] In the example, a RateMatchPattern may contain

[0367] a) within a BWP, when provided by PDSCH-Config or pdsch-ConfigMulticast or within a serving cell when provided by ServingCellConfig or ServingCellConfigCommon, or by pdsch-ConfigMCCH orDocket No. 24-1248PCT pdsch- ConfigMTCH, a pair of reserved resources with numerology provided by higher layer parameter subcarrierSpacing given by RateMatchPattern when configured per serving cell or by numerology of associated BWP when configured per BWP. The pair of reserved resources are respectively indicated by an RB level bitmap (higher layer parameter resourceBlocks given by RateMatchPattern) with 1RB granularity and a symbol level bitmap spanning one or two slots (higher layer parameters symbolstnResourceBlock given by RateMatchPattern) for which the reserved RBs apply. A bit value equal to 1 in the RB and symbol level bitmaps indicates that the corresponding resource is not available for PDSCH. For each pair of RB and symbol level bitmaps, a UE may be configured with a time-domain pattern (higher layer parameter periodicity And Pattern given by RateMatchPattern), where each bit of periodicity And Pattern corresponds to a unit equal to a duration of the symbol level bitmap, and a bit value equal to 1 indicates that the pair is present in the unit. The periodicityAndPattern can be {1 , 2, 4, 5, 8, 10, 20 or 40} units long, but maximum of 40 msec. The first symbol of periodicityAndPattern every 40 msec / P periods is a first symbol in frame n_f mod 4 = 0, where P is the duration of periodicityAndPattern in units of msec. When periodicityAndPattern is not configured for a pair, for a symbol level bitmap spanning two slots, the bits of the first and second slots correspond respectively to even and odd slots of a radio frame, and for a symbol level bitmap spanning one slot, the bits of the slot correspond to every slot of a radio frame. The pair can be included in one or two groups of resource sets (higher layer parameters rateMatchPatternGroupI and rateMatchPatternGroup2). The rateMatchPattemToAddModList given by ServingCellConfig or ServingCellConfigCommon configuration in numerology p applies only to PDSCH of the same numerology p.

[0368] b) within a BWP, a frequency domain resource of a CORESET configured by ControlResourceSet with controlResourceSetld or ControlResourceSetZero and time domain resource determined by the higher layer parameters monitoringSlotPeriodicityAndOffset, duration and monitoringSymbolsWithinSlot of all searchspace-sets configured by SearchSpace and time domain resource of search-space-set zero configured by searchSpaceZero associated with the CORESET as well as CORESET duration configured by ControlResourceSet with controlResourceSetld or ControlResourceSetZero. This resource not available for PDSCH may be included in one or two groups of resource sets (higher layer parameters rateMatchPatternGroupI and rateMatchPatternGroup2).

[0369] A configured group rateMatchPatternGroupI or rateMatchPatternGroup2 contains a list of indices of RateMatchPattern(s) forming a union of resource-sets not available for a PDSCH dynamically if a corresponding bit of the 'Rate matching indicator1field of the DCI format 1_1 scheduling the PDSCH is equal to 1 . The REs corresponding to the union of resource-sets configured by RateMatch Pattern^) that are not included in either of the two groups are not available for a PDSCH scheduled by a DCI format 1 _0, a PDSCH scheduled by a DCI format 1_1 , and PDSCHs with SPS. When receiving a PDSCH scheduled byDocket No. 24-1248PCT a DCI format 1_0 or PDSCHs with SPS activated by a DCI format 1_0, the REs corresponding to configured resources in rateMatchPattemGroupI or rateMatchPatternGroup2 are not available for the scheduled PDSCH or the activated PDSCHs with SPS. When receiving PDSCHs with SPS activated by a DCI format 1_1 , the REs corresponding to configured resources in rateMatchPattemGroupI or rateMatchPatternGroup2 are not available for the PDSCHs with SPS if a corresponding bit of the Rate matching indicator field of the DCI format 1_1 activating the PDSCHs with SPS is equal to 1.

[0370] For a bitmap pair included in one or two groups of resource sets, the dynamic indication of availability for PDSCH applies to a set of slot(s) where the rateMatchPatternToAddModList is present among the slots of scheduled PDSCH.

[0371] If a wireless device monitors PDCCH candidates of aggregation levels 8 and 16 with the same starting CCE index in noninterleaved CORESET spanning one OFDM symbol:1) and if a detected PDCCH scheduling the PDSCH has aggregation level 8, the resources corresponding to the aggregation level 16 PDCCH candidate are not available for the PDSCH, 2) when at least one of the PDCCH candidates of aggregation levels 8 and 16 linked as indicated by higher layer parameter searchSpaceLinkingld, the PDCCH candidates of aggregation level 16 and any other PDCCH candidate(s) linked with any of the PDCCH candidates of aggregation level 8 and 16 are not available for the PDSCH reception at the wireless device, if a detected PDCCH scheduling the PDSCH is associated with the PDCCH candidates of aggregation level 8 or 16.

[0372] If a PDSCH scheduled by a PDCCH would overlap with resources in the CORESET containing the PDCCH, the resources corresponding to a union of the detected PDCCH that scheduled the PDSCH and associated PDCCH DM-RS are not available for the PDSCH. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, the resources corresponding to a union of the two PDCCH candidates scheduling the PDSCH and the associated PDCCH DM-RS are not available for the PDSCH. When precoderGranularity configured in a CORESET where the PDCCH was detected is set to 'allContiguousRBs', the associated PDCCH DM-RS are DM-RS in all REGs of the CORESET. Otherwise, the associated DM-RS are the DMRS in REGs of the PDCCH.

[0373] If a wireless device is provided resourceBlocks and symbolstnResourceBlock in RateMatchPattern, or if the wireless device is additionally provided periodicityAndPattern in RateMatchPattern, the wireless device may determine a set of RBs in symbols of a slot that are not available for PDSCH reception scheduled by a DCI format. If a PDCCH candidate that provides a DCI format is mapped to one or more REs that overlap with REs of any RB in the set of RBs in symbols of the slot, the UE does not expect to monitor the PDCCH candidate.

[0374] In an example, a ServingCellConfigCommon of a serving cell may comprise one or more first rate match patterns (first rateMatchPattern(s)}. A PDSCH-Config of a BWP-dedicated for a BWP of the servingDocket No. 24-1248PCT cell may comprise one or more second rate match patterns (second rateMatchPattern(s.) . A rate match group (e.g., rateMatchPatternGroupI or rateMatchPatternGroup2) may comprise one or more cell level rate match patterns (e.g., cellLevel rateMatchPattern(s)) and one or more BWP level rate match pattern(s) (e.g., bwpLevel rateMatchPattern(s)).

[0375] One or more configuration parameters of a rate match pattern rateMatchPattern) is illustrated in FIG. 21 . A rateMatchPatternld indicates an identifier of the rateMatchPattern. Each rate match pattern may indicate bitmaps for time / frequency resources (e.g., bitmaps') and / or a control resource set (CORESET) (e.g., by controlResourceSet-r16 or by control ResourceSet). The bitmaps may indicate rate matching patterns by a pair of bitmaps resourceBlocks and symbolsInResourceBlock to define the rate match pattern within one or two slots, and a third bitmap periodicityAndPattern to define the repetition pattern with which the pattern defined by the above bitmap pair occurs.

[0376] The resourceBlocks may indicate a resource block level bitmap in the frequency domain. A bit in the bitmap set to 1 indicates that the wireless device may apply rate matching in the corresponding resource block in accordance with the symbolsInResourceBlock bitmap. If used as cell-level rate matching pattern, the bitmap identifies “common resource blocks (CRB)". If used for MBS broadcast CFR, the bitmap identifies "physical resource blocks" inside the MBS broadcast CFR. If used as BWP-level rate matching pattern, the bitmap identifies "physical resource blocks" inside the BWP or MBS multicast CFR. The first / leftmost bit corresponds to resource block 0, and so on.

[0377] The symbolsInResourceBlock may indicate a symbol level bitmap in time domain. It indicates with a bit set to true that the wireless device may rate match around the corresponding symbol. This pattern may recur (in time domain) with the configured periodicityAndPattern. For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot. For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot. For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on.

[0378] The periodicityAndPattern may indicate a time domain repetition pattern at which the pattern defined by symbolsInResourceBlock and resourceBlocks recurs. This slot pattern repeats itself continuously. Absence of this field may indicate the value 10msec with a single occurrence based on the symbolsInResourceBlock (e.g., a first slot with index.= 0 with oneSlot, a first slot with index = 0 and a second slot with index = 1 with twoSlots).Docket No. 24-1248PCT

[0379] The subcarrierSpacing may indicate a SubcarrierSpacing for this resource pattern. If the field is absent, the wireless device may apply the SCS of the associated BWP. The value kHz15 corresponds to pi=0, the value kHz30 corresponds to pi=1 , and so on. If the rate match pattern is for a cell level, this field may be present always.

[0380] The controlResourceSet may be used as a PDSCH rate matching pattern, i.e. , PDSCH reception rate matches around it. In frequency domain, the resource is determined by the frequency domain resource of the CORESET with the corresponding CORESET ID. Time domain resource is determined by the parameters of the associated search space of the CORESET. If the field controlResourceSetld-r16 is present, the wireless device may ignore the controlResourceSetld (without suffix) for the rate match pattern.

[0381] In the present disclosure, a wireless device performing a rate match a downlink channel (e.g., a PDCCH, a PDSCH) around one or more resource elements (REs) may refer that the wireless device do not use / map the one or more resources for the downlink channel or that the wireless device may assume the one or more resources are not used / mapped / available for the downlink channel or that the wireless device may assume that the one or more resources are set to zero (0) or that the wireless device may assume that the one or more resources are punctured. Performing the rate match may be done by mapping signals / bits for the downlink channel are mapped to scheduled REs excluding the one or more REs or puncturing (e.g., removed signals / bits) information of the downlink channel from the one or more REs after mapping signals / bits for the downlink channel to the scheduled REs without excluding the one or more REs.

[0382] In the present disclosure, a wireless device may assume / consider / determine a resource element (RE) is available or unavailable for a PDSCH. The wireless device may assume that information of data carried via the PDSCH is not mapped to the RE if the RE is considered / assumed / determined as not available for the PDSCH. The wireless device may assume / consider / determine that the information of data carried via the PDSCH is mapped to the RE if the RE is available for the PDSCH. The wireless device may determine the RE is available or unavailable for the PDSCH, where the RE overlaps in time and frequency with one or more scheduled REs for the PDSCH. The one or more scheduled REs of the PDSCH may be indicated dynamically via DCI format(s) or may be configured via RRC message(s).

[0383] In the present disclosure, a wireless device may assume / consider / determine a RE is available or unavailable for a PDCCH candidate. The wireless device may skip receiving / monitoring the PDCCH candidate based on the RE being considered / determined / assumed as not available or being unavailable for the PDCCH candidate. The wireless device may receive the PDCCH candidate otherwise. The wireless device may determine the RE is / as available or unavailable for the PDCCH candidate, where the RE overlaps in time and frequency with one or more REs of the PDCCH candidate.Docket No. 24-1248PCT

[0384] In the present disclosure, a resource of a downlink control / data (or REs of a PDCCH candidate or PDSCH, or resources of a PDCCH candidate or a PDSCH, configured / scheduled resources for a PDCCH candidate or a PDSCH) overlaps with a resource of a SSB (or REs of a SSB, or resources of a SSB, configured / scheduled resources for a SSB) based on the resource of the downlink control / data overlaps with the resource of the SSB in a time and a frequency domain.

[0385] In the present disclosure, a SSB that is not on-demand SSB may be referred as an always-on SSB or a normal SSB or a cell defining SSB or a non-cell defining SSB or a SSB. A base station may transmit one or more SSBs in a SSB burst via a cell. The base station may periodically transmit the SSB burst based on a periodicity. A SSB of the one or more SSBs in a SSB burst may be referred as a SSB with an index. Indexes of the one or more SSBs in the SSB burst may start from 0 to N-1 where N is a maximum number of SSBs in a single SSB burst in a given frequency range and / or subcarrier spacing of the cell.

[0386] Example embodiments of the present disclosure for an on-demand SSB (and / or a semi-periodic SSB) may be applied to an on-demand RS that is configured to be activated or deactivated. The RS may be a SSB or a CSI-RS or a PRS. In the present disclosure, resources of an on-demand rate matching pattern may be determined based on an on-demand SSB configuration without explicit configuration parameters from a base station.

[0387] One or more on-demand SSBs, if activated, may be transmitted periodically. One or more MAC CEs and / or DCIs may activate transmission on-demand SSB transmission. A wireless device may start receiving or expect to receive one or more on-demand SSBs in a next SSB burst (or a first SSB burst) after completing / finishing to apply the one or more MAC CEs and / or DCIs (or after finishing activation).

[0388] One or more second MAC CEs and / or DCIs may deactivate on-demand SSB transmission. If deactivated, the one or more SSBs of a SSB burst will be stopped or be skipped or not be transmitted via the cell, for the wireless device. The wireless device may stop receiving or expect to stop receiving the one or more SSBs in a next SSB (or a first SSB burst) after completing / finishing to apply the one or more second MAC CEs and / or DCIs deactivating the on-demand SSBs. In the present disclosure, unless otherwise noted, a state of an on-demand SSB burst / transmission is from a UE-perspective. The wireless device may determine the on-demand SSB transmission is deactivated, while a base station may continue transmission of the on-demand SSB transmission.

[0389] For example, a periodicity of on-demand SSBs is 10msec if activated. The wireless device may receive a MAC CE activating the on-demand SSBs at a time N that becomes effective at N+m. The wireless device may start to receiving one or more SSBs of the on-demand SSBs at K*10msec >= (N+m) / 10 where K is a smallest number satisfying the condition. Similarly, the wireless device may stop receiving one or more SSBs of the on-demand SSBs at K*10msec >= (N+m) / 10 where K is a smallest number satisfying the condition if the wireless device receives the deactivation MAC CE at the time N thatDocket No. 24-1248PCT are competeted in N+m. After activation, the wireless device may expect to measure or receive or receive or measure one or more SSBs of the on-demand SSBs or one or more SSB bursts of the on-demand SSBs until a time instance B or receiving a deactivation indication as illustrated in FIG. 20.

[0390] In the specification, an active (or activated, being transmitted, enabled, semi-persistently periodic, etc) on-demand SSB of a cell may be referred as an SSB that is an on-demand SSB and the SSB may be transmitted between a time instance A and a time instance B based on scenario / option 1 , 1 A, or 2 in FIG. 20. In other time duration(s), the on-demand SSB of the cell may be referred as an inactive on-demand SSB, a deactivated on-demand SSB, inactive SSB, inactive on-demand SSB, deactive on-demand SSB, deactive SSB, skipped SSB, not present SSB, stopped SSB, and / or the like.

[0391] For example, if an on-demand SSB of a cell is configured with a scenario / option 3 with a small number N, the on-demand SSB may not be used for measurement based on a semi-persistent RS or a periodic RS (e.g., periodic L1-RSRP, RRM, beam failure related measurement, beam recovery related measurement). If the on-demand SSB of the cell is configured with a scenario / option 4 in FIG. 21 , the on- demand SSB of the cell may be referred as an NCD-SSB of the cell.

[0392] In the specification, an on-demand SSB or an on-demand SSB burst may be referred as or determined based on whether the on-demand SSB or the on-demand SSB burst may be adapted in terms of a periodicity of the on-demand SSB transmission (e.g., infinite periodicity may refer the on-demand SSB transmission is disabled / deactivated).

[0393] In the specification, a wireless device may receive one or more downlink signals / channels of a PDCCH, a PDSCH or a CSI-RS based on a TCI state and / or transmit one or more uplink signals / channels of a PUCCH, a PUSCH, a SRS, or a PRACH based on a TCI state. An uplink transmission may refer an uplink signal / channel. A downlink reception may refer a downlink signal / channel. A wireless device may determine a pathloss for an uplink transmission for a PUCCH, a PUSCH, an SRS or a PRACH of an uplink transmission.

[0394] In the present disclosure, a cell comprises a SSB may refer that a base station transmits the SSB via / on the cell.

[0395] In the present disclosure, an on-demand RS (e.g., SSB) may be a semi-periodic RS (e.g., SSB) or a semi-persistent RS (e.g., SSB) but is not a periodic RS (e.g., SSB). A RS is a semi-periodic RS, where a wireless device may expect that the RS is maintained as active until a serving cell of RS is deactivated, after the RS is activated. In another example, a RS is a semi-periodic / semi-persistent RS, where a wireless device may expect that the RS is maintained as active where the wireless device is configured to perform measurements on the RS for radio link monitoring, and / or beam management, and / or beam failure recovery and / or radio resource monitoring. The RS may be a SSB or a CSI-RS or a PRS. In an example, an on-demand SSB that is maintained as active until a serving cell of the on-demand SSB is deactivated,Docket No. 24-1248PCT after being activated, may be referred as a ‘semi-periodic SSB' or a ‘semi-persistent SSB’ The semiperiodic SSB, that is the second on-demand SSB, may be activated before the serving cell is activated, or during the serving cell is activated or after the serving cell is activated. In an example, a semi-periodic SSB, that is an on-demand SSB, may be referred as a first type on-demand RS (e.g., type1-od-SSB) or a semiperiodic on-demand SSB or a semi-persistent on-demand SSB. A non-semi-periodic SSB, that is an on- demand SSB, may be referred as a second type on-demand SSB (e.g., type2-od-SSB) or a non-semi- periodic on-demand SSB or a non-semi-persistent on-demand SSB.

[0396] In an example, a wireless device may expect to receive periodically and continuously a RS that is a periodic RS. The periodic RS may not be activated and / or deactivated via one or more downlink control commands (e.g., MAC CE, DCI). The periodic RS may not be deactivated via one or more downlink control commands (e.g., MAC CE, DCI, RRC). In an example, a base station may transmit a periodic RS periodically for a serving cell of a wireless device regardless of the serving cell is activated or deactivated for the wireless device. An on-demand RS may be activated and / or deactivated via one or more downlink control commands (e.g., MAC CE, DCI, RRC).

[0397] In the present disclosure, a wireless device is configured with a parameter may refer that the wireless device receives one or more RRC messages indicating the parameter.

[0398] In the present disclosure, an on-demand rate matching pattern may be referred as an on-demand SSB rate matching pattern, an OD-SSB rate matching pattern, a rate matching pattern that may be activated or deactivated, an activatable rate matching pattern, a zero-power on-demand SSB resource set, a zero-power SSB resource set, a SSB rate matching resource set, a rate-matching on-demand SSB resource set, a rate matching pattern indicating a SSB configuration, and / or the like.

[0399] In the present disclosure, a wireless device may determine an on-demand RS (e.g., an on-demand SSB) being deactivated / activated may refer that the wireless device determines the on-demand RS (e.g., the on-demand SSB) transmission being deactivated / activated.

[0400] In the present disclosure, an on-demand SSB may be referred as an on-demand SSB burst, an on- demand SSB transmission, a SSB with an on-demand SSB transmission, etc.

[0401] In the present disclosure, a wireless device may not perform a rate matching based on resource may refer that the wireless device may assume that the resource are not considered as unavailable for a reception of one or more PDSCH and / or one or more PDCCH candidates.

[0402] The wireless device may receive one or more PDCCH candidates via resources that are not considered as unavailable. The wireless device may skip monitoring a PDCCH candidate based on resources of the PDCCH candidate overlaps, in time and frequency domains, with unavailable resources. The wireless device may assume no data is mapped on resource element(s) that is considered / determined as unavailable for a reception of a PDSCH. The wireless device may determine one or more resourceDocket No. 24-1248PCT elements for a reception of a PDSCH based on scheduled resource elements scheduled by a DCI format or configured and one or more resource elements that are not unavailable (e.g., excluding the one or more resource elements from the scheduled resource elements).

[0403] In existing technologies, a wireless device may determine one or more REs overlapping with resources of a SSB of a cell as unavailable for a downlink shared channel (PDSCH). A base station may map, on / over resources, information of the downlink control channel or a downlink control channel (PDCCH) candidate not overlapping with the one or more REs that overlaps with the SSB in time / frequency domains. The base station may map, on / over resources, information / bits of data of the downlink shared channel (PDSCH) by excluding the one or more REs or perform a rate matching around the one or more REs for the PDSCH resource allocation. In the existing technologies, the wireless device may continuously determine the one or more REs as unavailable regardless of whether the SSB is actually transmitted or not transmitted by the base station. This may reduce available resources for the wireless device.

[0404] In another existing technology, a base station may transmit one or more RRC messages indicating a plurality of rate match pattern configurations. In an example, a rate match pattern configuration of the plurality of ratch match pattern configurations may indicate one or more PRBs in one or more symbols in a slot or two slots with a periodicity. A wireless device may determine one or more REs indicated by any of the plurality of rate match pattern configurations as unavailable for a PDCCH and / or a PDSCH resource mapping.

[0405] The base station may configure the plurality of rate match pattern configurations for the wireless device to determine one or more second REs overlapping with resources of SSB(s) as unavailable. Once configured, the wireless device may continuously determine the one or more second REs as unavailable regardless of whether the base station actually transmits the SSB(s) or not. This may reduce available resources for the wireless device. Moreover, the rate match pattern configurations may not be flexible to accommodate various transmitted SSB patterns in a SSB burst. This may require configuring a plurality of rate match pattern configurations for the wireless device, where resources of the plurality of rate match pattern configurations may indicate more resources than actually transmitted SSB resources. This existing technology may result in lower resource utilization and increased overhead.

[0406] Embodiments of the present disclosure are related to an approach for solving the problems described above. These and other features of the present disclosure are described below.

[0407] In an example, a wireless device may receive one or more RRC messages indicating on-demand SSB transmission of a cell. The on-demand SSB transmission may be activated or deactivated based on one or more first downlink control commands (e.g., via MAC CE, RRC, DCI, etc.). The one or more RRC messages may further indicate configuration parameters of a rate matching pattern. Resources indicated by the rate matching pattern may overlap, in time and frequency domains, with the on-demand SSBDocket No. 24-1248PCT transmission of the cell The resources indicated by the rate matching pattern may indicate resources of the on-demand SSB transmission. The wireless device may skip monitoring one or more PDCCH candidates that overlap, in time and frequency domains, with the resources indicated by (determined based on, of, or associated with) the rate matching pattern, while the on-demand SSB transmission of the cell is deactivated for the wireless device. For example, the one or more first downlink control commands may indicate that the on-demand SSB transmission is deactivated for the wireless device, where configured / scheduled resources of the on-demand SSB transmission overlap, in time / frequency domain(s), with the resources indicated by the rate matching pattern.

[0408] In the example, the wireless device may receive one or more second downlink control command indicating an activation of the rate matching pattern. Skipping the monitoring of the one or more PDCCH candidates may be further based on the one or more second downlink control command indicating the activation of (or indicating the enablement of, triggering to use, starting to use, starting to apply, etc.) the rate matching pattern. The wireless device may start applying (or may use or may assume) the rate matching pattern (or may assume on-demand SSB is transmitted) in response to receiving the one or more second downlink command control indicating the activation (or indicating the enablement of, triggering to use, starting to use, starting to apply, etc.) of the rate matching pattern.

[0409] In the example, the wireless device may determine that the cell is deactivated based on receiving one or more MAC CEs and / or RRC messages deactivating the on-demand SSB transmission. In the example, the wireless device may receive one or more third downlink control command indicating a deactivation of the rate matching pattern. The wireless device may monitor one or more second PDCCH candidates, where resources of the one or more second PDCCH candidates overlap, in time / frequency domain(s), with resources indicated by the rate matching pattern. The resources indicated by the rate matching pattern are based on the one or more third downlink control command indicating the deactivation of the rate matching pattern. The wireless device may stop applying (or may not use or may not assume) the rate matching pattern (or may assume that no on-demand SSB is transmitted) in response to receiving the one or more third downlink command control indicating the deactivation.

[0410] In the example, the one or more second downlink control command may be transmitted via RRC, MAC CE and / or DCI.

[0411] In the example, the one or more third downlink control command may be transmitted via RRC, MAC CE and / or DCI.

[0412] In the example, the wireless device may receive configuration parameters of the rate matching pattern (e.g., via RRC messages), where the configuration parameters of the rate matching pattern may indicate at least one on-demand SSB configuration Alternatively, the configuration parameters of the rate matching pattern may indicate a periodicity of an on-demand SSB burst, a center frequency of an on-Docket No. 24-1248PCT demand SSB, and transmitted SSBs (or positions of scheduled / configured SSBs) in the on-demand SSB burst of the serving cell.

[0413] In existing technologies, rate matching pattern configurations or rate matching operation are / is based on semi-static configurations for resources used / allocated for SSB transmission. When the SSB transmission becomes on-demand or activated / deactivated, existing technologies may result in resource underutilization. For example, some resources are not used for transmission of a SSB when SSB transmission is deactivated, but the resources are not available for downlink control / data channels based on the rate matching pattern configurations. The implementation of the existing technologies may result in low resource utilization efficiency.

[0414] In the present disclosures, the wireless device may perform a rate matching based on on-demand SSB and / or an on-demand rate matching pattern. More specifically, in an example, the wireless device may perform the rate matching based on a transmission of the on-demand SSB if the on-demand SSB is activated or the on-demand rate matching pattern if the on-demand rate matching pattern is activated.

[0415] FIG. 22 illustrates an example as per an aspect of an embodiment of the present disclosure. In FIG 22, the base station (BS) transmits on-demand SSBs (and / or on-demand SSB bursts) between a first time T1 and a second time T4. FIG. 22 illustrates an on-demand SSB burst as a SSB. Each on-demand SSB burst (e.g., a SSB in FIG. 22) may comprise one or more on-demand SSBs. FIG. 22 shows activation / deactivation status of on-demand SSBs at the base station, a first wireless device (UE #1), and a second wireless device (UE #2) in a time domain.

[0416] BS periodically transmit / repeat an on-demand SSB burst based on a periodicity (P1 ).

[0417] BS activates the on-demand SSB / on-demand SSB burst transmission before the first time T1 for UE #1 . UE #1 determines that the on-demand SSB transmission is activated at the first time T 1 or before the first time T1 . On-demand SSB bursts for UE #1 between the first time T1 and a time T3 are on-demand SSB bursts that UE #1 consider as activated / transmitted. BS deactivates the on-demand SSB / on-demand SSB burst transmission before the time T3 or at the time T3 for UE#1 . UE #1 considers that the on-demand SSB / on-demand SSB burst transmission is deactivated after the time T3 or at the time T3. UE #1 may not measure or perform monitoring the on-demand SSB / on-demand SSB burst after the time T3 based on the on-demand SSB / on-demand SSB burst being deactivated. BS schedules a downlink data or control after the time T3 and before the second time T4. At BS (or BS perspective), resources of the downlink data or control (DL#1) may overlap with resources of first on-demand SSB burst after the time T3. Without additional indication, UE #1 may consider / determine no on-demand SSB transmission after the time T3 while BS transmits the first on-demand SSB burst after the time T3. This may lead a conflict in resource mapping between downlink data / control and the on-demand SSB transmission.Docket No. 24-1248PCT

[0418] BS activates the on-demand SSB / on-demand SSB burst transmission to UE#2 at a time T2 or before the time T2. UE #2 may determine that on-demand SSB transmission is activated after or at the time T2. BS deactivates the on-demand SSB / on-demand SSB burst transmission to UE #2 at a time T4 or before the time T4. UE #2 may determine that on-demand SSB transmission is deactivated after or at the time T4.

[0419] Based on existing technologies, however, UE #1 may determine that the resources of DL#1 may not overlap with resources of the first on-demand SSB burst as UE #1 assumes no on-demand SSB transmission or as UE #1 is not aware of the first on-demand SSB burst transmission by the base station. Based on existing technologies, UE #1 may consider the resources of DL#1 , that overlap with the resources of the first on-demand SSB, as available, where BS may not be able to utilize the resources for the downlink data or control as BS uses the resources for the first on-demand SSB for UE#2.

[0420] In another existing technology, BS may configure one or more rate matching patterns to cover resources of on-demand SSB transmissions to UE #1 and UE #2. The another existing technology, however, may not deactivate the one or more rate matching patterns. UE #1 and UE #2, after the second time T4, may continue performing a rate matching around resources configured by the one or more rate matching patterns. This leads inefficient resource utilization.

[0421] Existing technologies may not dynamically enable / activate or disable / deactivate rate matching resources (or unavailable resources) for a downlink control / data via a cell based on an actual on-demand SSB transmission by the base station.

[0422] FIG. 23 illustrates an example as per an aspect of an embodiment of the present disclosure. A wireless device (UE) may receive one or more RRC messages, for a serving cell (CC#1) at a time TO. The one or more RRC messages may comprise / indicate (i.e. , comprise and / or indicate) configuration parameters. The configuration parameters may comprise an on-demand SSB configuration (e.g., a frequency of the on-demand SSB, periodicity of the on-demand SSB transmission, an initial state of the on- demand SSB, etc.). The on-demand SSB configuration may be included in a set or list of on-demand SSB configurations. The configuration parameters may comprise one or more on-demand rate matching pattern configurations.

[0423] In the present disclosure, an on-demand rate matching pattern may be referred to as a rate matching pattern / configuration that may be activated or inactivated by a downlink command control (e.g., via RRC, MAC CE, DCI).

[0424] The one or more on-demand rate matching patterns may be comprised in a configuration (e.g., servingCellConfig) of the serving cell. The one or more on-demand rate matching patterns may be separately configured from ‘rateMatchPattern’ of the servingCellConfig. The one or more on-demand rate matching patterns may indicate a rateMatchPattern of ‘rateMatchPattern' of the servingCellConfig’, whereDocket No. 24-1248PCT an on-demand rate match pattern may be activated or deactivated via one or more downlink control commands. More details are shown in FIGs. 24A and24B.

[0425] The ‘rateMatchPattern’ may comprise a resourceBlock, a symbolsinResourceBlock, and / or a periodicity And Patern. The ‘rateMatchPatern’ may be used once it’s configured to the wireless device, and may be activated based on the configuration and may not be deactivated via one or more downlink command control such as MAC CE or DCI. The ‘rateMatchPattern’ may be released via RRC message(s) / signaling / procedure.

[0426] For example, an on-demand rate matching pattern / config u ration of the one or more rate matching patterns may comprise / indicate an index of an on-demand SSB configuration. The wireless device may determine resources of a SSB of the on-demand SSB transmission based on the on-demand SSB configuration indicated by the index.

[0427] For example, when the wireless device is configured with a single on-demand SSB configuration for the serving cell and / or a BWP of the serving cell, the index of the on-demand SSB configuration may be indicated as zero (0). Alternatively, the on-demand rate matching pattern / configu ration may comprise a flag to indicate to use the single on-demand SSB configuration for a rate matching (e.g., the flag is set to TRUE / 1 ) or not to use the single on-demand SSB configuration for the rate matching (e.g., the flag is set to FALSE / 0).

[0428] The on-demand SSB configuration may comprise one or more parameters indicating a) a subcarrier spacing of on-demand SSB; b) physical cell identifier scrambled / used in the on-demand SSB; c) time domain location of an on-demand SSB burst e.g., a SFN offset and / or a half frame index; d) downlink transmit power of the on-demand SSB; e) an index of the on-demand SSB configuration; and f) bitmap(s) of on-demand SSB transmissions in an on-demand SSB burst; g) initial status of the on-demand SSB; h) a BWP index where the on-demand SSB will be transmitted / activated; and / or j) a center frequency of the on- demand SSB (absoluteSSBFrequency).

[0429] The wireless device may determine rate matching resources, corresponding to resource of transmission of SSB, based on the on-demand SSB configuration. For example, symbols in a slot, one or more slots, PRBs in the symbols, and a periodicity of the on-demand SSB burst are determined based on the on-demand SSB configuration. The wireless device may determine resources of a candidate SSB that is indicated as transmitted based on the bitmap(s) of the on-demand SSB transmission in the on-demand SSB burst (e.g., ssb-PositionsinBursf) . For example, Lmax may be 4 for the cell and ssb-PositionsinBurst may indicate a SSB index = 0 and a SSB index = 2. In this example, SSBs having SSB index = 0 and 2 will be transmitted in every 20 msec, and the wireless device may determine that resources, of symbols #2 - #5 with 20 PRBs in a slot #0 and a slot #1 (in FIG. 17), will be used for a first SSB with the SSB index = 0 and a second SSB with the SSB index = 2.Docket No. 24-1248PCT

[0430] Alternatively, the on-demand rate matching pattern may comprise / indicate configuration parameters for determining resources based on an on-demand SSB configuration: a) a subcarrier spacing of on-demand SSB; b) a center frequency of the on-demand SSB; c) time domain location of an on-demand SSB burst e.g., a SFN offset and / or a half frame index; d) periodicity of on-demand SSB burst; and / or e) bitmap(s) of on-demand SSB transmissions in an on-demand SSB burst. Similar to the above example, the wireless device may determine rate matching resources based on the configuration parameters. The wireless device may determine resources of on-demand SSBs based on the configuration parameters, and may determine the resources as the rate matching resources.

[0431] Alternatively, the on-demand rate matching pattern may comprise configuration parameters of: a) a starting PRB index; b) one or two starting symbols in a slot; and / or c) L-bit sized bitmap, where each bit maps to a slot, the left most of the L-bit size bitmap maps to the first slot determined based on a periodicity, and 2ndbit maps to the second slot in the period; and / or d) the periodicity where the L-bit sized bitmap repeats. The wireless device may determine resources for a rate matching based on the configuration parameters. For example, a set of PRBs may be determined between a first PRB with the starting PRB index and a second PRB with the starting PRB index + 20. Time domain aspects of the resources may be determined based on the one or two starting symbols in the slot and the L-bit sized bitmap. For example, if there are two resources in a slot, two starting symbols in the slot may be indicated. For example, symbol #2 and symbol #8 (in FIG. 17) may be indicated as the two starting symbols. The wireless device may determine the time domain aspects based on the one or two starting symbols and a size of SSB in a time domain (e.g., 4 symbols). For example, if the one starting symbol indicates symbol #8, the time domain aspects of the resources, in the slot, may be determined as the symbol #8 - #11 . For example, if two starting symbols indicate symbol #2 and #8, the time domain aspects of the resources, in the slot, may be determined as the symbols #2-#5 and symbols #8-#11 . The slot may be determined based on the L-bit size bitmap and the periodicity. For example, if the periodicity is 10 msec, and Lmax is 4 for the serving cell, 2 bits bitmap indicates whether a first slot with a slot index = 0 and a second slot with a slot index = 1 are used for the rate matching. For example, the bitmap may be

[0010] to indicate to use the first slot.

[0432] In another example, the on-demand rate matching pattern may comprise configuration parameters of: a) a starting PRB index; b) bitmap(s) of on-demand SSB transmissions in an on-demand SSB burst (e.g., ssb-PositionsInBurs and / or c) a periodicity of the on-demand rate matching pattern.

[0433] For multiple implementation examples of configuration parameters of the on-demand rate matching pattern, the on-demand rate matching pattern / configuration may additionally / optionally comprise an initial status / state of the on-demand rate matching pattern / configuration. For example, the initial status / state may be set to TRUE / 1 to indicate that the on-demand rate matching pattern / configuration is initialized as active based on one or more RRC messages indicating the on-demand rate matching pattern. The initialDocket No. 24-1248PCT status / state may be set to FALSE / 0 to indicate that the on-demand rate matching pattern / configu ration is initialized as inactive based on the one or more RRC messages.

[0434] For example, the initial status / state may be applied when the serving cell is activated. For example, the initial status / state may be applied when an active BWP of the serving cell is not a dormant BWP. If the initial status / state is set to TRUE / 1 , the wireless device may apply the on-demand rate matching pattern for receiving downlink data / control when the serving cell is activated. For example, if the initial status / state is set to FALSE / 0, the wireless device may not apply the on-demand rate matching pattern for receiving downlink data / control at least until the wireless device receives another message to activate or enable the on-demand rate matching pattern.

[0435] In an example, the base station may indicate whether to perform a rate matching on the on- demand SSB or not via configuration parameters of an on-demand SSB configuration. For example, a flag / field indicating to enable or disable the rate matching for / on the on-demand SSB may be comprised in the on-demand SSB configuration. For example, the flag / field may indicate i) the rate matching being enabled for both activated and deactivated transmission of the on-demand SSB, ii) rate matching being enabled only for activated transmission of the on-demand SSB; or ill) rate matching not being enabled for either activated or deactivated transmission of the on-demand SSB. Based on i), the wireless device is expected to consider resources of a transmission of the on-demand SSB as unavailable for a reception of one or more PDSCHs and / or monitoring one or more PDCCH candidates regardless of a state / status of the transmission of the on-demand SSB. Based on ii), the wireless device is expected to consider resources of a transmission of the on-demand SSB as unavailable for a reception of one or more PDSCHs and / or monitoring one or more PDCCH candidates, where a state / status of the transmission of the on-demand SSB indicates activation of the on-demand SSB or the transmission of the on-demand SSB is activated.Based on iii), the wireless device is not expected to consider resources of a transmission of the on-demand SSB as unavailable for a reception of one or more PDSCHs and / or monitoring one or more PDCCH candidates regardless of a state / status of the transmission of the on-demand SSB. In the example, activation or deactivation of performing the rate matching may be determined based on whether the serving cell is activated and / or the transmission of the on-demand SSB is activated. For example, with i), performing the rate matching is activated / enabled when the serving cell is activated. With ii), performing the rate matching is activated / enabled when the transmission of on-demand SSB is activated. With iii), performing the rate matching is deactivated when the serving cell is activated.

[0436] In FIG. 23, the wireless device may be configured with the serving cell at the time TO. Alternatively, the wireless device may be configured with the serving cell prior to the time TO.

[0437] At time T1 , the wireless device may, optionally, receive a first downlink control command (Downlink Common #1). The downlink control command may be transmitted via a RRC message, a MAC CE and / or aDocket No. 24-1248PCTDCI format. In another example, without the first downlink control command, an initial state of the on- demand SSB configuration may indicate ‘active' / 'activated' / 'enabled’. In case the initial state of the on- demand SSB configuration is set to TRUE / 1 , the wireless device may determine that the on-demand SSB transmission is activated at the RRC configuration.

[0438] The first downlink control command may indicate an activation of an on-demand SSB transmission. Configuration parameters of the on-demand SSB transmission may be determined based on the on- demand SSB configuration provided at the time TO. Resources of one or more SSBs of the on-demand SSB burst based on the on-demand SSB configuration may be same as (e.g., the on-demand rate matching pattern indicates the index of the on-demand SSB configuration) or may be different from the on- demand rate matching pattern. In the example, the first downlink control command may be received when the serving cell is deactivated. For example, the wireless device may receive the first downlink control command via a primary cell (e.g., PCell, PSCell , etc.). For example, the wireless device may receive the first downlink control command via an active secondary serving cell. Based on the first downlink command control, the wireless device may determine that the on-demand SSB transmission via the serving cell is activated. The wireless device may start measurements based on the on-demand SSB when the on- demand SSB is activated. The wireless device may determine that the on-demand SSB burst is transmitted periodically until the time instance B (in FIG. 20).

[0439] At a time T2, the wireless device may receive a SCell activation / deactivation MAC CE indicating activation of the serving cell. The wireless device may determine the serving cell is activated based on the SCell activation / deactivation MAC CE. After the time T2, the wireless device may activate the serving cell. In an example, when the serving cell is activated and the initial status / state of the on-demand rate matching pattern is indicated as ‘active’ / ’activated’ / ’enabled’ or is set to TRUE / 1 , the wireless device may determine that the on-demand rate matching pattern is enabled / activated based on the serving cell being activated.

[0440] When the on-demand rate matching pattern is enabled / activated, the wireless device may determine that resources indicated by the on-demand rate matching pattern are not available for downlink control / data channels. The wireless device may skip monitoring one or more PDCCH candidates that overlap, in time / frequency domain, with resources indicated by the on-demand rate matching pattern. If there are a plurality of on-demand rate matching patterns, the initial status / state may be configured independently for each of the plurality of on-demand rate matching patterns. If there are a plurality of ‘activated' / 'enabled’ / ‘active on-demand rate matching patterns of the serving cell, the wireless device may determine resources, as unavailable for downlink control / data, that is indicated by any active on-demand rate matching pattern of the plurality of active on-demand rate matching patterns.

[0441] If the initial status / state indicates ‘inactive’ / ‘deactivated’ / ‘disabled’ or is set to FALSE / 0, the wireless device may determine that the on-demand rate matching pattern is disabled for the serving cell.Docket No. 24-1248PCTThe wireless device may determine resources indicated by the 'deactivated' / 'inactive' / 'disabled' on- demand rate matching pattern as available for downlink control / data unless the resources are indicated by another active on-demand rate matching pattern or a ‘rateMatchPattern’ of the serving cell.

[0442] At a time T3, the wireless device may optionally receive a second downlink control command (Downlink Command #2). The time T3 may correspond to the time instance B in FIG. 20. The wireless device may determine the time T3 based on receiving explicit downlink control command(s) from the base station and / or based on one or more timers (e.g., sCellDeactivationTimer, bwp-lnactivityTimer, etc.). For example, one or more options illustrated in FIG. 20 to determine the time instance B may be used to indicate deactivation of the on-demand SSB.

[0443] At a time T4, the wireless device may receive a third downlink control command (Downlink Command #3). The third downlink control command may activate the one or more on-demand rate matching patterns. The third downlink control command may activate one or more second on-demand rate matching patterns of the one or more on-demand rate matching patterns. The third downlink control command may deactivate one or more third on-demand rate matching patterns of the one or more on- demand rate matching patterns.

[0444] The wireless device may determine a resource element as available for receiving a PDCCH candidate or a PDSCH based on any one or more of the followings: a) the resource element does not overlap, in time / frequency domain, with any on-demand rate matching pattern(s), configured for the serving cell and / or active BWP of the serving cell, that are activated; and b) the resource element does not overlap, in time / frequency domain, with any, applicable, rateMatchPattern configured for the serving cell and / or active BWP of the serving cell; c) the resource element does not overlap with resources of a CD-SSB or a NCD-SSB (or a semi-periodic SSB) of the serving cell if any; d) for PDSCH, additionally, the resource element does not overlap with additional zero-power CSI-RS resource set (e.g., ZP-CSI- RS_ResourceSet(s)) indicated by a scheduling DCI for the PDSCH; e) the resource element does not overlap with resources of an activated transmission of the on-demand SSB of the serving cell if any; and / or f) the resource element does not overlap with resources of an indicated transmission of the on-demand SSB, for performing a rate matching, of the serving cell if any. The wireless device may determine the resource element as available when the resource element does not overlap, in time / frequency domain, with any active rate matching resource(s). The wireless device may determine ‘applicable’ ‘rateMatchPattern’ based on a scheduling DCI for the PDSCH. For example, the scheduling DCI may indicate a rateMatchPatternGroup comprising one or more rateMatchPatterns of configured rateMatchPatterns.

[0445] The wireless device may determine a resource element as unavailable for receiving a PDCCH candidate or a PDSCH based on one or more of: a) the resource element overlaps, in time / frequency domain, with any on-demand rate matching pattern(s), configured for the serving cell and / or active BWP ofDocket No. 24-1248PCT the serving cell, that are activated; b) the resource element overlaps, in time / frequency domain, with any, applicable, rateMatchPattern configured for the serving cell and / or active BWP of the serving cell; c) the resource element overlaps with resources of a CD-SSB or a NCD-SSB (or a semi-periodic SSB) of the serving cell if any; d) for PDSCH, additionally, the resource element does not overlap with additional zeropower CSI-RS resource set (e.g., ZP-CSI-RS_ResourceSet(s)) indicated by a scheduling DCI for the PDSCH; e) the resource element overlaps with resources of an activated transmission of the on-demand SSB of the serving cell if any; and / or f) the resource element overlaps with resources of an indicated transmission of the on-demand SSB, for performing a rate matching, of the serving cell if any. The wireless device may determine the resource element as unavailable when the resource element overlaps, in time / frequency domain, with any active rate matching resource(s). In the above examples, that a resource element overlaps with resources may refer that the resource element overlaps, in time and frequency domains, with the resources.

[0446] At a time T5, the wireless device may receive a fourth downlink control command (Downlink Command #4). The fourth downlink control command may deactivate the one or more on-demand rate matching patterns. The fourth downlink control command may deactivate one or more second on-demand rate matching patterns of the one or more on-demand rate matching patterns. The fourth downlink control command may activate (e.g., reactivate) one or more third on-demand rate matching patterns of the one or more on-demand rate matching patterns.

[0447] The third downlink command control command and the fourth downlink control command may be carried via the same downlink control command (e.g., both via MAC CE format, DCI format, or RRC messages). Alternatively, different downlink control command formats may be used for activation and deactivation respectively. One or more downlink control command formats may be used for either or both of the third downlink command control command and the fourth downlink control command.

[0448] Events shown in FIG. 23 are intended for illustrative purposes only and do not restrict timing relationship between events shown in FIG. 23. For example, the third downlink control command may be transmitted / received before determining that the on-demand SSB transmission is deactivated (e.g., at the time T2).

[0449] For example, if the wireless device receives the third downlink control command before the time T3, the wireless device may activate the on-demand rate matching pattern based on the third downlink control command. Later, if the wireless device receives one or more downlink control command to indicate a deactivation of the OD-SSB, the wireless device may determine that the OD-SSB is deactivated while maintaining the active status / state of the on-demand rate matching pattern.

[0450] In a first example, the third downlink control command and / or the fourth downlink control command may be transmitted via a rate matching activation / deactivation MAC CE. The rate matchingDocket No. 24-1248PCT activation / deactivation MAC CE may comprise one or more fields indicating or comprising one or more of: a) one or more serving cell indexes indicating one or more serving cells where the MAC CE is applied for activating / deactivating one or more on-demand rate matching patterns configured for the respective serving cell; b) for each serving cell of the one or more serving cells: I) a BWP index indicating a BWP of the serving cell where the MAC CE is applied for activating / deactivating one or more on-demand rate matching patterns configured for the respective BWP. (Note that this field may be present if the one or more on- demand rate matching patterns are configured for the respective BWP. Otherwise, this field may not be configured); ii) one or more identifier (e.g., rateMatchPattern-ld) to indicate the one or more on-demand rate matching patterns; and / or iii) one or more flags to indicate activation (e.g., set as TRUE / 1) or deactivation (e.g , set as FALSE / 0) where each flag of the one or more flags may correspond to each on- demand rate matching pattern of the one or more on-demand rate matching patterns.

[0451] Alternatively, a single flag / bit may be used to activate or deactivate the one or more on-demand rate matching patterns for the each serving cell / BWP.

[0452] Alternatively, the MAC CE may activate or deactivate performing a rate matching on resources of a transmission of the on-demand SSB for the each serving cell / BWP. For example, a field of the MAC CE may indicate enablement or disablement of performing a rate matching for the resources of the transmission of the on-demand SSB for the each serving cell / BWP. The field may indicate i) enabling the rate matching for both activated and deactivated transmission of the on-demand SSB; ii) enabling the rate matching for only activated transmission of the on-demand SSB; or iii) disabling the rate matching for the transmission of the on-demand SSB. In the example, the on-demand rate matching pattern may be considered to indicate the resources of the transmission of the on-demand SSB.

[0453] Alternatively, in an example, the one or more on-demand rate matching patterns may be grouped into one or more groups, where a single / bit flag may be used to activate / deactivate each group, and the field may comprise K bits where K indicates a number of groups. In this example, the MAC CE activating the one or more second on-demand rate matching pattern may additionally indicate iv) a duration, where the wireless device may assume that one or more second on-demand rate matching patterns, of the one or more on-demand rate matching patterns, are active for the duration after receiving the MAC CE.

[0454] The wireless device may receive the rate matching activation / deactivation MAC CE at a slot n via a first serving cell (e.g., PCell, the serving cell, SCell, etc.). The wireless device may transmit a PUCCH with HARQ-ACK information in a slot m corresponding to a PDSCH carrying the rate matching activation / deactivation MAC CE. The wireless device may determine that resources, indicated by the one or more on-demand rate matching patterns that are activated by the rate matching activation / deactivation MAC CE, as unavailable for downlink data / control starting from the first slot (e.g., slot k) that is after the slot m + 3 * N(subframe,u,slot) + (power (2, u) / power (2, u of k_mac))* k_mac. In the example, u is a subcarrierDocket No. 24-1248PCT spacing configuration for the PUCCH (or of an active UL BWP where the PUCCH is transmitted) and ‘u of k_mac' is the subcarrier spacing configuration for k_mac. 'u of k_mac' may be determined as zero / 0 for a frequency range 1 (e.g., frequency below than 7 GHz). N(subframe, u, slot) is a number of slots, based on the subcarrier spacing of the PUCCH (u), in a subframe (e.g., 1 msec). Similarly, the wireless device may determine second resources, indicated by one or more second on-demand rate matching patterns that are deactivated by the rate matching activation / deactivation MAC CE, as available for downlink data / control starting from the first slot (e.g., slot k) that is after the slot m + 3 * N(subframe,u,slot) + (power (2, u) / power (2, u of k_mac))* k_mac.

[0455] In a second example, the third downlink control command and / or the fourth downlink control command may be transmitted via a rate matching group-common DCI. The wireless device may be configured with configuration parameters indicating a) a size of the group-common DCI; b) RNTI used to receive the group-common DCI; c) one or more positions in the group-common DCI. The wireless device may determine one or more fields based on the one or more positions in the group-common DCI, and each field of the one or more fields may correspond to each group of on-demand rate matching pattern(s) or each BWP or each serving cell. For example, a position in the group-common DCI may be configured for each serving cell (e.g., via servingCellConfig), for each BWP, for each group of on-demand rate matching pattern(s). Each field of the one or more fields may activate / deactivate one or more on-demand rate matching patterns of the each serving cell (if a position is configured for each serving cell) or for each BWP (if a position is configured for each BWP) or for each group of on-demand rate matching pattern(s) (if a position is configured for each group). Alternatively, each field of the one or more fields may activate / deactivate performing a rate matching based on one or more on-demand SSB configurations / resources / transmissions of the each serving cell (if a position is configured for each serving cell) or for each BWP (if a position is configured for each BWP).

[0456] In a third example, the third downlink control command and / or the fourth downlink control command may be transmitted via an on-demand SSB group-common DCI. Similar to the second example, configuration parameters to read the group DCI may be configured. For example, a position for each serving cell may be configured. The wireless device may receive a field activating or deactivating one or more on-demand SSB configurations (or the field activating or deactivating performing a rate matching on the one or more on-demand SSB configurations) for each serving cell of one or more serving cells, configured with on-demand SSB(s). The on-demand SSB group-common DCI may indicate whether the base station transmits the on-demand SSB or not for the serving cell. The wireless device may determine that the base station will periodically transmit the on-demand SSB based on receiving the on-demand SSB group-common DCI indicating activation / enabling the one or more SSB configurations of the serving cell. For example, the wireless device may receive the on-demand SSB group-common DCI at a slot n. TheDocket No. 24-1248PCT wireless device may determine that the on-demand SSB transmission of the one or more on-demand SSB configurations is activated for rate matching purpose after the first slot that occurs after / at a slot k (k = n + d) (e.g., d is a processing gap for different subcarrier spacing of the serving cell, e.g., d = 3 for 15 kHz). The wireless device may determine resources of a SSB of the one or more SSB configurations as unavailable for PDCCH candidate(s) and / or PDSCH after / at the slot k. The wireless device may determine a rate matching pattern, for the serving cell, corresponding to resources comprising resource(s) of each of the one or more on-demand SSB configurations is activated at the slot k based on the on-demand SSB group- common DCI.

[0457] The wireless device may not perform measurements or may receive on-demand SSB(s) from the base station in case the wireless device determines that on-demand SSB transmission is deactivated (e.g., based on the time instance B in FIG. 20). In the example, the on-demand SSB group-common DCI may indicate that the base station is transmitting the on-demand SSB. The on-demand SSB group-common DCI may be used to determine resources for a reception of one or more PDSCHs and / or monitoring PDCCH candidates, but the on-demand SSB group-common DCI may not be used for determining whether to perform measurements or not based on transmissions of the on-demand SSB of the serving cell. The wireless device may determine resources of the on-demand SSB as unavailable for PDCCH candidates and PDSCH reception in such cases. The on-demand SSB group-common DCI may indicate that an on- demand SSB transmission is activated or deactivated from the base station. The on-demand SSB group- common DCI may not change a status / state of the on-demand SSB transmission from the wireless device perspective. The wireless device may determine the status / state of the on-demand SSB transmission based on one or more examples in FIG. 18-20. In the example, the wireless device may determine resources, (1) of a transmitted on-demand SSB or (2) of an on-demand SSB indicated as being active by the on-demand SSB group-common DCI, as unavailable for receiving PDCCH candidate(s) and / or PDSCH(s). For example, an on-demand SSB may be dropped due to collision with a CD-SSB or an NCD- SSB or for other reasons (e.g., overlap with uplink symbols or overlap with reserved resource, etc.). The wireless device may not determine the resources of the dropped on-demand SSB as unavailable as the on- demand SSB has not been transmitted.

[0458] In a fourth example, the third downlink control command may be transmitted via a cell DTX / DRX group-common DCI (e.g., DCI format 2_9). For example, the wireless device may be configured with a separate position (e.g., rate-Match-activation-PositionlnDCI), in the cell DTX / DRX group-common DCI, for each serving cell from a position, in the cell DTX / DRX group-common DCI, of a cell DTX / DRX indication. The wireless device may determine a field for activating / deactivating one or more rate matching patterns of the serving cell based on the separate position (e.g., rate-Match-activation-PositionlnDCI).Docket No. 24-1248PCT

[0459] In a fifth example, the third downlink control command may be transmitted via a scheduling DCI format. For example, a DCI format (e.g., a non-fallback DCI format such as DCI format 1_1 , 0_1 , 1 _2, 0_2, 1_3, 0_3, 1_4, 0_4) may comprise a field for a scheduled serving cell. A size of the field may be 1 bit to activate or deactivate one or more on-demand rate matching patterns of the scheduled cell and / or enabl ing / disabl Ing performing of a rate matching on activated transmission of the on-demand SSB of the serving cell. For example, L bits may activate and / or deactivate L groups of on-demand rate matching patterns of the scheduled cell (each bit corresponds to each group) and / or L bits may activate and / or deactivate L on-demand rate matching patterns of the scheduled cell. Once an on-demand rate matching pattern is activated by the scheduling DCI, the wireless device may determine resources indicated by the on-demand rate matching pattern as unavailable until the on-demand rate matching pattern is deactivated by another scheduling DCI (or some other downlink control command).

[0460] In a sixth example, the wireless device may apply an on-demand rate matching pattern for dynamically scheduled PDSCH only. For example, a scheduling DCI may indicate whether to apply one or more first on-demand rate matching patterns in receiving one or more PDSCHs scheduled by the scheduling DCI. The wireless device may be configured, via RRC messages / signaling, one or more second on-demand rate matching patterns comprising the one or more first on-demand rate matching patterns. Based on the scheduling DCI indicating to apply the one or more first on-demand rate matching patterns, the wireless device may determine resources indicated by any of the one or more first rate matching patterns as unavailable for receiving the one or more PDSCHs. The wireless device may determine the resources of the one or more first rate matching patterns based on configuration parameters of the one or more first on-demand first rate matching patterns. For example, an on-demand rate matching pattern may be referred to as on-demand SSB rate matching resource set, rate matching resource set of on-demand SSB, OD-SSB-RateMatch-ResourceSet and / or the like.

[0461] In an example, via the serving cell, the wireless device may receive a scheduling DCI at a slot p where the slot p occurs before the slot k. The wireless device may determine that an on-demand rate matching pattern of the serving cell is activated (or deactivated in case deactivation) after the slot k based one or more signaling mechanisms in the above. The scheduling DCI may schedule a PDSCH at a slot q where the slot q occurs after the slot k The wireless device may determine the resources, indicated by the one or more on-demand rate matching patterns that are activated (or deactivated in case deactivation) by the rate matching activation / deactivation MAC CE, as available (or unavailable in case deactivation) for receiving the scheduling DCI via the serving cell as the slot p occurs before the slot k. The wireless device may determine the resources as unavailable (or available in case deactivation) for receiving the PDSCH as the slot q occurs after the slot k.Docket No. 24-1248PCT

[0462] In an example, the scheduling DCI may schedule one or more PDSCHs via a plurality of slots starting from a slot r to a slot q. In the example, the slot r may occur before the slot k. The slot q may occur after the slot k. For example, the scheduling DCI may schedule a PDSCH via the plurality of slots. The wireless device may determine whether to assume the resources as available or unavailable based on a first slot of the one or more PDSCHs. Based on the slot r occurring before the slot k, the wireless device may determine that the resources are available (or unavailable in case deactivation) for the one or more PDSCHs. Alternatively, the wireless device may determine the resources as available for PDSCH(s) occurring before the slot k and the resources as unavailable (or available in case of deactivation) for second PDSCH(s) occurring after / at the slot k. A PDSCH resource mapping would not utilize the resources based on the resources being unavailable. A PDSCH resource mapping may utilize the resources based on the resources being available.

[0463] In the example, the one or more PDSCHs may be configured via RRC messages (e.g., SPS PDSCH(s)). For a PDSCH occasion of a SPS PDSCH, the wireless device may determine a rule that is similar to a rule applied for the scheduling DCI case. For example, if a SPS configuration configures a periodic single-slot SPS PDSCH occurring periodically, for each SPS PDSCH occasion, the wireless device may determine the resources as available or unavailable based on a slot of the each SPS PDSCH occasion and the slot k. If a SPS configuration configures a periodic multi-slot SPS PDSCH occurring periodically or multiple PDSCHs over multiple slots, the wireless device may use the first slot of each multislot SPS PDSCH occasion or the multiple PDSCHs occasion to determine whether to assume the resources as available or unavailable for receiving data via the SPS configuration.

[0464] In the present disclosure, a downlink control / data may be transmitted via a PDCCH, a PDSCH. Similar mechanisms may be also applied to a downlink RS such as CSI-RS. The wireless device may not receive a CSI-RS if resources of the CSI-RS overlap in time / frequency domain with resources of the on- demand rate matching pattern or resources considered as unavailable

[0465] In an example, a wireless device may receive one or more RRC messages, for a serving cell, indicating whether to apply an on-demand rate matching pattern for one or more channels. For example, the one or more RRC messages may indicate to apply the on-demand rate matching pattern for a PDSCH only, where the wireless device may determine resources of the on-demand rate matching will be unavailable for receiving one or more PDSCHs via the serving cell. For example, the one or more RRC messages may indicate to apply the on-demand rate matching for a PDCCH (or a PDCCH candidate) and a PDSCH. The wireless device may skip monitoring PDCCH candidates and / or may determine resources of the on-demand rate matching pattern as unavailable for receiving PDCCH candidates and / or PDSCHs. The one or more RRC messages may indicate to apply the on-demand rate matching pattern for a dynamically scheduled PDSCH only. In such a case, the wireless device may not determine resources ofDocket No. 24-1248PCT the on-demand rate matching pattern as unavailable for receiving PDCCH candidates and / or SPS PDSCH(s).

[0466] In an example, a wireless device may determine resources of an on-demand rate matching as unavailable for receiving a dynamically scheduled PDSCH only, a PDSCH only, or both PDCCH candidate and a PDSCH. The wireless device may not determine to skip one or more PDCCH candidates based on the on-demand rate matching pattern. The wireless device may determine the resource of the on-demand rate matching pattern as unavailable for receiving a PDSCH.

[0467] Example embodiments may allow dynamically configuring (e.g., enabling and / or disabling) resources of on-demand SSBs as unavailable for other downlink signal receptions based on whether such resources are used for transmitting on-demand SSBs or are not used by a base station. Example embodiments may allow maintain UE-specific status of on-demand SSB transmissions while allowing a base station to efficiently multiplex on-demand SSB transmission (if transmitted) and downlink channels.

[0468] There are multiple ways to configure an on-demand rate matching pattern that indicates resources overlapping, in time / frequency domains, with resources of on-demand SSB transmission(s). FIGs. 24A - 25B illustrate a few examples

[0469] FIG. 24A illustrates an example that a rateMatchPattern, comprised in a ServingCellConfigCommon, may, optionally, indicate an on-demand SSB configuration for a rate matching or may, optionally, indicate that the rateMatchPattern is an on-demand rate matching pattern with an initial status.

[0470] In an example, configuration parameters of the ServingCellConfigCommon, where the configuration parameters are common for a plurality of wireless devices associated with a serving cell of the ServingCellConfigCommon, may comprise one or more rate matching patterns (RateMatchPattern(s)). The configuration parameters of the ServingCellConfigCommon may further / optionally comprise one or more on-demand SSB configurations (OD-SSB Config(s)). Each on-demand SSB configuration of the one or more on-demand SSB configurations may comprise an index. The wireless device, configured with the serving cell, may perform a rate matching or may determine resources indicated by the one or more rate matching patterns regardless of an active BWP of the serving cell. The wireless device may determine resources of the one or more rate matching patterns, as unavailable based on the one or more rate matching patterns being active. The wireless device may determine that a rate matching pattern is active based on 1) receiving the configuration parameters comprising the rate matching pattern and 2) that either i) the rate matching pattern is not an on-demand rate matching pattern (e.g., without state / status flag) or II) the rate matching pattern is activated by one or more downlink control commands.

[0471] A rate matching pattern (e.g., rateMatchPattern) of the one or more rate matching patterns (e.g., rateMatchPattern(s)) may comprise configuration parameters of a) patternType; and / or b) ControlDocket No. 24-1248PCT resourceSetld. More details of each parameter are provided in FIG. 21 . Additionally / optionally, the rate matching pattern may indicate / comprise an index to indicate an on-demand SSB configuration, of the one or more on-demand SSB configurations (OD-SSB Config(s)). For example, based on the rate matching pattern indicating the index of the on-demand SSB configuration, the wireless device may determine resources, of an on-demand SSB transmission based on the on-demand SSB configuration, as unavailable, in response to receiving an indication that activates / enables the on-demand SSB transmission. For example, the wireless device may receive the indication from another base station and / or another serving cell. For example, the indication may be transmitted via RRC, MAC CE and / or DCI.

[0472] For example, a serving base station or a source cell may configure a ServingCellConfigCommon for a target cell or a target base station. An initial state / status of one or more on-demand SSB configurations of the target cell or the target base station may be configured in the ServingCellConfigCommon for the target cell / target base station. In response to switching to the target cell or target base station, the wireless device may apply the initial state / status of the one or more on-demand SSB configurations of the target cell. For example, in case the initial state / status indicates (or is set to) ‘activated / TRUE / r, the wireless device may determine that the target cell / target base station are transmitting SSBs based on the one or more on-demand SSB configurations. Otherwise (e.g., set to ‘deacti vated / FALSE / 0’) , the wireless device may determine that the target cell / target base station are not transmitting SSBs based on the one or more on-demand SSB configurations. The one or more on-demand SSB configurations of the ServingCellConfigCommon may be applied to a plurality of wireless devices associated a corresponding serving cell. On-demand SSBs are activated in a cell-common / specific way for the corresponding serving cell.

[0473] In the example, the wireless device may determine the rate matching pattern as an on-demand rate matching pattern for resources (1) overlapping with on-demand SSB transmissions or (2) that are determined based on the on-demand SSB configuration indicated in the rate matching pattern In case the rate matching pattern indicates bitmap(s) of the patternType comprising resourceBlocks and symbolsInResourceBlock and optionally periodicity Andpattern, the wireless device may determine resources indicated by the patternType (or resourceBlocks and symbolsInResourceBlock, and optionally periodicityAndpattern) as unavailable for receiving PDCCH candidates and / or PDSCHs. Additionally, if the indicated on-demand SSB configuration is activated or the on-demand SSB transmission of the on-demand SSB configuration is activated, the wireless device may determine second resources, based on the on- demand SSB configuration, as unavailable for receiving PDCCH candidates and / or PDSCH. The second resources may overlap, in time / frequency domains, with resources of on-demand SSB based on the on- demand SSB configuration.Docket No. 24-1248PCT

[0474] In another example, the rate matching pattern may comprise / indicate an initial status / state of the rate matching pattern instead of indicating the on-demand SSB configuration. For example, resources of on-demand SSBs may be configured via the patternType of the rate matching pattern. The initial status / state of the rate matching pattern may be set to TRUE / 1 to use the rate matching pattern at the configuration. The initial status / state of the rate matching pattern may be set to FALSE / 0 to not use the rate matching pattern at the configuration. The rate matching pattern may be activated / enabled via one or more downlink control commands (e.g., RRC, MAC CE, DCI).

[0475] FIG. 24B illustrates another configuration example of an on-demand rate matching pattern / resource. For example, a servingCellConfig of the serving cell may comprise one or more downlink BWPs. The servingCellConfig may comprise one or more rate matching patterns. Similar to FIG. 24A, a rate matching pattern of the one or more rate matching pattern may comprise an index to an on-demand SSB configuration or may comprise an initial status of the rate matching pattern. In contrast to FIG. 24A, examples of FIG. 24B may indicate the wireless device specific (UE-specific) configurations.

[0476] Configuration parameters of a BWP (e.g., BWP-DownlinkDedicated) may comprise parameters of a PDSCH (e g., PDSCH-Config). Parameters of the PDSCH may comprise one or more rate matching patterns (RateMatchPattern(s)). Similar to FIG. 24A, a rate matching pattern of the one or more rate matching pattern may comprise / indicate an index of an on-demand SSB configuration. The configuration parameters of the BWP may, optionally, comprise one or more on-demand SSB configurations. The index of the on-demand SSB configuration may indicate an on-demand SSB configuration of the one or more on- demand SSB configurations.

[0477] Alternatively, the rate matching pattern may comprise / indicate an initial status / state of the rate matching pattern.

[0478] In contrast to FIG. 24A, where the on-demand SSB transmission is cell-commonly activated or deactivated, in case the one or more on-demand SSB configurations are provided in the BWP, the base station may activate or deactivate an on-demand SSB transmission for the wireless device, where the base station may not activate or may not deactivate the on-demand SSB transmission for a second wireless device at the same time (i.e., activation / deactivation of the on-demand SSB transmission is UE-specific). To enable / activate the rate matching pattern comprising the index of the on-demand SSB configuration or the initial status / state, the base station may transmit additional downlink control commands as per one or more examples illustrated in FIG. 23.

[0479] FIG. 25A illustrates an example of an on-demand rate matching pattern. In the example, a base station may configure one or more separate rate matching patterns for on-demand rate matching procedure from one or more rate matching patterns (rateMatch Pattern). In some examples provided in this disclosure, the on-demand rate matching procedure may involve a wireless device determining resources indicated byDocket No. 24-1248PCT a rate matching pattern as available or unavailable based on one or more downlink control command and / or based on activation / deactivation of the rate matching pattern.

[0480] For example, the one or more separate rate matching patterns may be referred to as On-Demand- RateMatchPattern(s). An On-Demand-RateMatchPattern may comprise configuration parameters (e.g., patternType) similar to those of a rateMatchPattern. The On-Demand-RateMatchPattern may comprise a patternType2 to indicate resources corresponding to on-demand SSB transmissions of the serving cell.

[0481] For example, configuration parameters of the patternType2 may comprise a) a center frequency of a SSB to indicate a center frequency of the on-demand SSB; b) transmitted SSBs in an on-demand SSB burst (e.g., ssbPositionsInBurst),' c) a periodicity of the on-demand SSB burst; and / or d) a subcarrier spacing of the SSB. The wireless device may determine resources of the patternType2 based on applying the configuration parameters of the pattemType2 for SSB transmission e.g., according to FIG. 17.

[0482] In an example, one or more On-Demand-RateMatchPatterns may be comprised in a BWP- DownlinkDedicated instead of comprised in a PDSCH-Config as shown in FIG. 25B.

[0483] In an example, a wireless device may receive one or more RRC messages indicating one or more rate matching resource sets for SSB (rateMatching-SSBResourceSef) for a serving cell or a BWP of the serving cell. A rate matching resource set may comprise / indicate one or more configuration parameters of an on-demand SSB configuration (e.g., a center frequency aboluteFrequencySSB, a periodicity ssb- Periodicity, transmitted SSBs in a SSB burst ssbPositionsInBurst, a time offset ssb-TimeOffset). The wireless device may determine resources for rate matching based on the on-demand SSB configuration. The wireless device may receive a scheduling DCI comprising one or more bits, where each bit indicates whether to apply or not apply a corresponding rate matching resource for SSB in receiving PDSCH scheduled by the scheduling DCI. A size of the one or more bits may be determined based on a number of the one or more rate matching resource sets configured the serving cell or the BWP of the serving cell.

[0484] In an example, a wireless device may receive configuration parameters indi...

Claims

Docket No. 24-1248PCTCLAIMS1. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating an on-demand synchronization signal (SS) physical broadcast channel (PBCH) block (SSB) of a cell, wherein the on-demand SSB is configured to be activated or deactivated; receiving first downlink control information (DCI) scheduling a first physical downlink shared channel (PDSCH); receiving the first PDSCH, wherein: resources of the first PDSCH are configured not to comprise one or more resource elements(REs) overlapping with resources of the on-demand SSB; and the one or more REs are unavailable for receiving the first PDSCH based on: the on-demand SSB being activated; and the first DCI being scrambled with a first radio network temporary identifier (RNTI); and transmitting a feedback corresponding to the first PDSCH.

2. A method comprising: receiving, by a wireless device, a first physical downlink shared channel (PDSCH), wherein one or more resource elements (REs), overlapping with resources of one or more on-demand synchronization signal (SS) physical broadcast channel (PBCH) blocks (SSBs) of a cell, are available or unavailable for receiving the first PDSCH, based on whether the one or more on-demand SSB are activated; and transmitting a feedback corresponding to the first PDSCH.

3. The method of claim 2, further comprising: receiving, by the wireless device, one or more radio resource control (RRC) messages indicating the one or more on-demand SSBs, wherein the one or more on-demand SSBs are configured to be activated or deactivated; and receiving first downlink control information (DCI) scheduling the first PDSCH.

4. The method of claim 2 or 3, wherein the one or more REs are unavailable for receiving the first PDSCH, based on the one or more on-demand SSBs being activated.

5. The method of claim 4, wherein the one or more REs are unavailable for receiving the first PDSCH, further based on the first DCI being scrambled with a first radio network temporary identifier (RNTI).

6. The method of claim 4 or 5, wherein resources of the first PDSCH are configured not to comprise the one or more REs.

7. The method of any one of claims 3-6, wherein: the one or more RRC messages indicate an on-demand SSB configuration; andDocket No. 24-1248PCT the on-demand SSB configuration indicate one or more of: a center frequency of the one or more on-demand SSBs; a periodicity of an on-demand SSB burst, wherein the on-demand SSB burst comprises the one or more on-demand SSBs; and a position indication of each of the one or more on-demand SSBs that are configured to be transmitted in the on-demand SSB burst; and a subcarrier spacing of the one or more on-demand SSBs.

8. The method of claim 7, further comprising determining one or more symbols of the resources of the one or more on-demand SSBs based on the position indication of each of the one or more on-demand SSBs.

9. The method of claim 7 or 8, further comprising determining one or more physical resource blocks (PRBs) of the resources of the one or more on-demand SSBs based on the center frequency of the one or more SSBs comprised in the on-demand SSB configuration.

10. The method of any one of claims 5-9, further comprising determining that the one or more REs are unavailable for receiving the first PDSCH, based on: the one or more on-demand SSBs being activated; and the first DCI being scrambled with the first RNTI.11 . The method of any one of claims 3 and 7-9, wherein the one or more REs are available for receiving the first PDSCH, based on: the one or more on-demand SSBs being deactivated; or the first DCI being scrambled with a second RNTI.

12. The method of claim 11 , further comprising determining that the one or more REs are available for receiving the first PDSCH, based on: the one or more on-demand SSBs being deactivated; or the first DCI being scrambled with the second RNTI.

13. The method of claim 10, further comprising determining, for receiving the first PDSCH, that no data is mapped on the one or more REs, based on the determining the one or more REs are unavailable.

14. The method of claim 13, further comprising determining one or more second REs for receiving the first PDSCH based on excluding the determined unavailable one or more REs from scheduled resources by the first DCI.

15. The method of any one of claims 5-14, wherein the first RNTI is one of: a PDCCH with CRC scrambled by cell-RNTI (C-RNTI), modulation and coding scheme-RNTI (MCS-C-RNTI), configured scheduling-RNTI (CS-RNTI), group-RNTI (G-RNTI), group-CS-RNTI (G-CS-RNTI), multicast channel- RNTI (MCCH-RNTI), or Multicast MCCH-RNTI.Docket No. 24-1248PCT16. The method of any one of claims 11-15, wherein the second RNTI is one of: a system information- RNTI (SI-RNTI), random access-RNTI (RA-RNTI), message B-RNTI (MSGB-RNTI), paging-RNTI (P- RNTI) or temporary cell-RNTI (TC-RNTI).

17. The method of any one of claims 2-16, wherein : the feedback is transmitted via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); and the feedback is a hybrid automatic repeat request (HARQ) acknowledgement or negative acknowledgement.

18. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating an on-demand synchronization signal (SS) physical broadcast channel (PBCH) block (SSB) of a cell, wherein the on-demand SSB is configured to be activated or deactivated; receiving a first physical downlink shared channel (PDSCH), based on determining whether one or more resource elements (REs) overlapping with resources of the on-demand SSB and the first PDSCH are available, wherein: a first downlink control information (DCI) schedules the first PDSCH; the one or more REs are unavailable, based on: the on-demand SSB being activated; and the first DCI being scrambled with a first RNTI; and transmitting a feedback corresponding to the first PDSCH.

19. A method comprising: receiving, by a wireless device, a first physical downlink shared channel (PDSCH), based on determining whether one or more resource elements (REs) overlapping with resources of an on- demand synchronization signal (SS) physical broadcast channel (PBCH) block (SSB) and the first PDSCH are available; and transmitting a feedback corresponding to the first PDSCH.

20. The method of claim 19, wherein: a first downlink control information (DCI) schedules the first PDSCH; and the one or more REs are unavailable, based on: the on-demand SSB being activated; and the first DCI being scrambled with a first RNTI.21 . The method of claim 19 or 20, further comprising receiving, by the wireless device, one or more radio resource control (RRC) messages indicating the on-demand SSB of a cell, wherein the on-demand SSB is configured to be activated or deactivated.Docket No. 24-1248PCT22. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating: an on-demand synchronization signal (SS) physical broadcast channel (PBCH) block (SSB) of a cell, wherein the on-demand SSB is configured to be activated or deactivated; and a rate matching pattern, wherein resources associated with the rate matching pattern overlap, in time and / or frequency domains, with resources of the on-demand SSB of the cell; receiving a downlink control command indicating indication an activation of the rate matching pattern, wherein the on-demand SSB is deactivated; and based on the downlink control command: skipping monitoring one or more physical downlink control channel (PDCCH) candidates overlapping, in the time and / or frequency domains, with the resources associated with the rate matching pattern; and determining that no data is mapped on one or more resource elements, of scheduled resource elements, of a physical downlink shared channel (PDSCH), wherein the one or more resource elements overlap, in the time and / or frequency domains, with the resources associated with the rate matching pattern.

23. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating: one or more on-demand synchronization signal (SS) physical broadcast channel (PBCH) blocks (SSBs) of a cell, wherein the one or more on-demand SSBs are configured to be activated or deactivated; and a rate matching pattern, wherein resources associated with the rate matching pattern overlap, in time and / or frequency domains, with resources of the one or more on-demand SSBs of the cell; and based on activation of the rate matching pattern, skipping monitoring one or more physical downlink control channel (PDCCH) candidates overlapping, in the time and / or frequency domains, with the resources associated with the rate matching pattern.

24. The method of claim 23, further comprising receiving a downlink control command indicating the activation of the rate matching pattern, wherein the one or more on-demand SSBs are deactivated.

25. The method of claim 24, wherein the monitoring of the one or more PDCCH candidates is skipped based on the downlink control command.

26. The method of claim 24 or 25, further comprising, based on the downlink control command, determining that no data is mapped on one or more resource elements, of scheduled resource elements, of a physical downlink shared channel (PDSCH), wherein the one or more resourceDocket No. 24-1248PCT elements overlap, in the time and / or frequency domains, with the resources associated with the rate matching pattern.

27. The method of any one of claims 23-26, wherein: the rate matching pattern is an on-demand rate matching pattern; and the rate matching pattern is configured to be activated or deactivated.

28. The method of any one of claims 23-27, wherein the monitoring of the one or more PDCCH candidates is skipped based on the one or more on-demand SSBs being deactivated for the wireless device.

29. The method of any one of claims 23-28, wherein the one or more on-demand SSBs are transmitted by a base station via the cell while the one or more on-demand SSBs are deactivated for the wireless device.

30. The method of any one of claims 23-29, wherein: the rate matching pattern comprises an index of an on-demand SSB configuration; and the on-demand SSB configuration comprises: a center frequency of the one or more on-demand SSBs; a periodicity of an on-demand SSB burst; transmitted SSBs in the on-demand SSB burst; and / or a subcarrier spacing of the one or more on-demand SSBs.31 . The method of any one of claims 23-30, further comprising determining, based on the activation of the rate matching pattern, that the resources associated with the rate matching pattern are unavailable for receiving a physical downlink shared channel (PDSCH).

32. The method of any one of claims 24-31 , wherein the downlink command control is received by the wireless device while the one or more on-demand SSBs are deactivated for the wireless device.

33. The method of any one of claims 24-31 , wherein the downlink command control is received by the wireless device while the one or more on-demand SSBs are activated for the wireless device.

34. The method of any one of claims 24-33, further comprising: receiving a second downlink command control indicating deactivation of the one or more on-demand SSBs; and determining that transmission of the one or more on-demand SSBs is deactivated based on the second downlink command control.

35. The method of claim 34, further comprising maintaining that the rate matching pattern is activated after the one or more on-demand SSB are deactivated.

36. The method of any one of claims 24-35, wherein: the downlink command control is an RRC message;Docket No. 24-1248PCT the RRC message indicates or comprises an initial state of the rate matching pattern; and the initial state of the rate matching pattern indicates whether the rate matching pattern is activated or deactivated.

37. The method of claim 36, further comprising determining, based on the initial state indicating that the rate matching pattern is activated, the resources associated with the rate matching pattern as being unavailable for downlink control and / or downlink data.

38. The method of claim 36, further comprising not determining the resources associated with the rate matching pattern as unavailable for downlink control and / or downlink data based on the initial state indicating that the rate matching pattern is deactivated.

39. The method of any one of claims 24-35, wherein: the downlink command control is a DCI format; the DCI format is a scheduling DCI, scrambled via C-RNTI; and the DCI format comprises a field for indicating an activation or deactivation of the rate matching pattern.

40. The method of any one of claims 23-39, wherein the rate matching pattern is comprised in a configuration of the cell, a configuration for a particular bandwidth part, or a PDSCH configuration.41 . A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating: one or more on-demand synchronization signal (SS) physical broadcast channel (PBCH) blocks (SSBs) of a cell, wherein the one or more on-demand SSBs are configured to be activated or deactivated; and a control resource set (CORESET) with an index 0; determining resources of the one or more on-demand SSBs, that are activated, as unavailable for receiving downlink data; and receiving downlink control via the CORESET with the index 0, wherein the CORESET overlaps, in time and / or frequency domains, with the resources of the on-demand SSB, that are activated.

42. The method of claim 41 , further comprising receiving the downlink control via a search space set associated with the CORESET.

43. The method of claim 42, wherein the search space set is a common search space.

44. The method of claim 42 or 43, further comprising monitoring one or more PDCCH candidates of the search space set for the receiving the downlink control.

45. The method of any one of claims 41-44, wherein the downlink control is scrambled using a SI-RNTI or a C-RNTIDocket No. 24-1248PCT46. The method of any one of claims 41-45, wherein the downlink data does not comprise a system information block 1 .

47. The method of any one of claims 41-46, further comprising receiving a PDSCH comprising the downlink data, wherein the PDSCH is scrambled with a C-RNTI.

48. 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 -47.

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

Images