Initial access procedure for an SBFD-aware ue

Abstract

A method comprises transmitting, by a wireless device and for an random access procedure to a cell, a preamble via a physical random access channel (PRACH) resource in one or more uplink symbols and / or one or more flexible symbols, and receiving one or more messages indicating to apply one or more subband full duplex (SBFD) configuration parameters for the initial access to the cell. The method further comprises, based on receiving the one or more messages, transmitting an uplink transmission via an uplink resource, for the random access procedure, using the one or more SBFD configuration parameters, wherein the uplink resource used for the uplink transmission overlaps with one or more SBFD symbols.

Description

Docket No.: 25-1015PCTTITLEInitial Access Procedure for an SBFD-Aware UECROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 747,607 , filed January 21 , 2025, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0016] FIG. 11B 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.: 25-1015PCT

[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] FIGS. 17A and 17B illustrate 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. 24 illustrates an aspect of an example embodiment according to the present disclosure.DETAILED DESCRIPTION

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

[0032] 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, atDocket No.: 25-1015PCTleast 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.

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

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

[0035] 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 = {cell 1 , cell2} are: {celH }, {cell2}, and {celH , cell2}. The phrase “based on” (or equally “based at least on") is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “inDocket No.: 25-1015PCTresponse 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.

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

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

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

[0039] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a softwareDocket No.: 25-1015PCTroutine 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.

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

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

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

[0043] 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, 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 userDocket No.: 25-1015PCTequipment (U E), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

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

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

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

[0047] 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 areas provided by macrocell base stations The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell baseDocket No.: 25-1015PCTstations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

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

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

[0051] As illustrated in FIG. 1B, 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 the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to supportDocket No.: 25-1015PCTrouting 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.

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

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

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

[0055] As shown in FIG. 1B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160ADocket No.: 25-1015PCTmay 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.

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

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

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

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

[0060] 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 stacksDocket No.: 25-1015PCTillustrated 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.

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

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

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

[0064] Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and aDocket No.: 25-1015PCTsecondary 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.

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

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

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

[0068] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG.4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the 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.Docket No.: 25-1015PCT

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

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

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

[0072] 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 MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.Docket No.: 25-1015PCT

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

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

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

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

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

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

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

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

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

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

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

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

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

[0086] 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 ofDocket No.: 25-1015PCTone 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:

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

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

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

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

[0091] - 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

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

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

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

[0095] 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 230 through which the NAS messages can be transported. The NAS messages may be transported using theDocket No.: 25-1015PCTAS 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.

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

[0097] 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., RRC_I DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0098] 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 to the base station currently serving the UE. The UE's serving base station may request a handover to a cellDocket No.: 25-1015PCTof 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.

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

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

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

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

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

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

[0105] A gNB, such as gNBs 160 in FIG. 1B, 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.

[0106] 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 Fsource 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.

[0107] 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 periodDocket No.: 25-1015PCTof 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.

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

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

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

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

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

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

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

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

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

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

[0118] 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 default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE mayDocket No.: 25-1015PCTdetermine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.

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

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

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

[0122] 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.: 25-1015PCTBWP. 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.

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

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

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

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

[0127] 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.: 25-1015PCT

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

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

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

[0131] 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.: 25-1015PCTdisclosure 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.

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

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

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

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

[0136] 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.: 25-1015PCTPSS. 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.

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

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

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

[0140] 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.: 25-1015PCT

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

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

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

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

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

[0146] 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.: 25-1015PCTDMRS 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.

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

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

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

[0150] 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.: 25-1015PCTFor 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.

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

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

[0153] 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.: 25-1015PCTperiodic, 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.

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

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

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

[0157] FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11B may span a resource block (RB)Docket No.: 25-1015PCTwithin 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.

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

[0159] 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 mayor 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.: 25-1015PCTon 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.

[0160] 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 (PM I), a channel quality indicator (CQI), and / or a rank indicator (Rl).

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

[0162] 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.: 25-1015PCT

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

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

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

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

[0167] 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.: 25-1015PCTparameters 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.

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

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

[0170] 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.: 25-1015PCTdetermine 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.

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

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

[0173] 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.: 25-1015PCTindicated 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:

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

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

[0176] 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.: 25-1015PCTan 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.

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

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

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

[0180] 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.: 25-1015PCTresponse 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.

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

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

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

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

[0185] 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.: 25-1015PCTThe 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).

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

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

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

[0189] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE'' in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313Docket No.: 25-1015PCTillustrated 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.

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

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

[0192] 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.: 25-1015PCT1403 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.

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

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

[0195] 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.: 25-1015PCTscheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

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

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

[0198] 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.: 25-1015PCTPUCCH 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”.

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

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

[0201] 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.: 25-1015PCT

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

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

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

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

[0206] 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.: 25-1015PCTfunctionalities 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.

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

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

[0209] 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.: 25-1015PCTmapping 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.

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

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

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

[0213] 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.: 25-1015PCT

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

[0215] When a new provisional matter is opened, the Docketing Team can double-click the “UPDATE BIB DATA” button below to update Docket Number, Title, Inventorship, etc.

[0216] In an example, a wireless device may receive one or more RRC / SIB messages indicating configuration parameters. The configuration parameters may comprise one or more UL / DL TDD (or TDD) configurations of / for a cell. The one or more UL / DL TDD configurations of / for the cell may be (or comprise) a cell-specific UL / DL TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon) of / for the cell. The one or more UL / DL TDD configuration of / for the cell may be (or comprise) a U E-specific UL / DL TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated). In an example, the cell-specific UL / DL TDD configuration for the cell may be broadcasted via a SIB1 or a SIB message. In an example, the U E-specific UL / DL TDD configuration for the cell may be transmitted via one or more messages (e.g., RRC, MAC CE, DCI).

[0217] The configuration parameters may be / comprise one or more TDD configuration parameters. The one or more TDD configuration parameters may comprise one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon) and / or one or more UE-specific TDD configuration parameters (e.g. TDD-UL-DL-ConfigurationDeicated).

[0218] For a serving cell (of the one or more serving cells), one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon) may indicate / configure slot format(s) of a plurality of slots.

[0219] The one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon) may indicate / configure the plurality of slots. The plurality of slots may comprise one or more consecutive slots. The plurality of slots may comprise one or more DL slots / symbols. The pluralityDocket No.: 25-1015PCTof slots may comprise one or more UL slots / symbols. The plurality of slots may comprise one or more flexible slots / symbols.

[0220] A first symbol / slot of the plurality of slots may be an Uplink (‘U7U L) symbol. An UL symbol may be used by the wireless device for uplink transmission(s), e.g., via the serving cell. The one or more UL slots / symbols may comprise the first symbol / slot.

[0221] A second symbol / slot of the plurality of slots may be a downlink (‘D7DL). A DL symbol may be used by the wireless device for downlink reception(s), e.g., via the serving cell. The one or more DL slots / symbols may comprise the second symbol / slot.

[0222] In some implementations, a third symbol in a slot of the plurality of slots may be a flexible (‘F’) symbol. The one or more flexible slots / symbols may comprise the third symbol / slot. Slot format / direction of the flexible symbol may be determined (by the wireless device and / or the base station) by other signaling, e.g., DCI format 2_0 and / or UL / DL grants and / or the one or more UE-specific TDD configuration parameters. The format 'F is used by the network to control UL / DL transmission / reception of each wireless device flexibly. For example, the network may assign a symbol with ‘F for a wireless device not to transmit to or receive from a base station, e.g., for interference control and / or power saving purposes. For example, the network may use a slot format ‘F’ on one or more symbols to selectively initiate / trigger random access (RA) for a particular wireless device. Other wireless devices may not be allowed to transmit or receive on the one or more symbols, resulting in reduced interference for the wireless device.

[0223] The one or more common TDD configuration parameters may comprise at least one of: a reference subcarrier spacing (SCS) .ref and / or at least one TDD pattern. The at least one TDD pattern may comprise a first TDD pattern (e.g., patteml) and / or a second TDD pattern (e.g., pattern?'). A TDD pattern of the at least one TDD pattern may be a TDD-UL-DL pattern

[0224] A TDD pattern (e.g., the first TDD pattern or the second TDD pattern) of the at least one TDD pattern may comprise at least one of: a slot configuration period of P msec (e.g., a TDD periodicity); a number of slots dslotswith only downlink symbols (e.g., DL slot(s)); a number of downlink symbols dsym(e.g., DL symbol(s)); a number of slots usiotswith only uplink symbols (e.g., UL slot(s)); a number of uplink symbols usym(e.g., UL symbol(s)). The one or more DL symbols / slots may comprise the number of slots dsiotsand / or the number of downlink symbols dsym. The one or more UL symbols / slots may comprise the number of slots usiotsand / or the number of uplink symbols usymFor example, the rest of slots / symbols in the TDD pattern (withing the slot configuration period P) not indicated by the TDD pattern as DL / UL slots / symbols may be flexible slots / symbols. The one or more flexible slots / symbols may comprise the rest of slots / symbols in the TDD pattern (withing the slot configuration period P) not indicated by the TDD pattern as DL / UL slots / symbols.Docket No.: 25-1015PCT

[0225] Corresponding to each TDD pattern of the at least one TDD pattern, a TDD periodicity (e.g., the corresponding slot configuration period of the TDD pattern) may comprise S = P. 2re(consecutive) slots with SCS configurationThe one or more consecutive slots may comprise S1= Pt.(consecutive) slots (of the first TDD pattern) and / or S2= P2.2re< (consecutive) slots (of the second TDD pattern). The TDD periodicity P may be a summation of a first TDD periodicity P (of the first TDD pattern) and a second TDD periodicity P2(of the first TDD pattern), e.g., P — P + P2.

[0226] From Stslots (1=1 corresponding to the first TDD pattern or i=2 corresponding to the second TDD pattern), a first / initial / starting / earliest dsiotsslots may comprise the one or more DL slots / symbols. From Stslots, a last / final / ending / latest usiotsslots may comprise the one or more UL slots / symbols. A dsymsymbols after the first dslotsslots may comprise the one or more DL symbols. A usymsymbols before the last usiotsslots may comprise the one or more UL symbols. A remaining (S' — dsiots—usiots)- ^symb ~ dsym— usymsymbols may comprise the one or more flexible symbols / slots.

[0227] FIGs. 17A and 17B show an example of subband full-duplex (SBFD) operation as per an aspect of an embodiment of the present disclosure. The figures show two examples of SBFD operations in a carrier. Other examples are also possible. The carrier may be a TDD carrier. The carrier may be an FDD carrier.

[0228] In an example, a SBFD operation of a cell may be referred as (or interchangeably used in some embodiments) a SBFD mode of the cell, a new enhanced duplex mode of the cell, a hybrid TDD / FDD mode of the cell, an enhanced duplexing operation of the cell, configuration one or more UL subbands (and / or one or more DL subbands) via the cell, and / or the like. Using the SBFD operation, a wireless device and / or a base station may reduce UL transmission latency or UL transmission capacity, as the wireless device may be allowed / configured to transmit UL signals / channels in / during SBFD symbols / slots.

[0229] In an example, a SBFD symbol may be referred as (or interchangeably used with) a flexible symbol in a SBFD carrier / serving cell / cell, a SBFD symbol of a carrier / serving cell / cell, a downlink / flexible symbol with a UL subband configured, a symbol (e.g., a downlink or a flexible symbol) with a UL subband configured, a time unit configured with a UL subband, a symbol referred as a SBFD operation, a symbol where a wireless device operates a SBFD operation, a symbol indicated to apply a SBFD operation or a UL band by one or more SBFD configuration parameters and one or more RRC messages indicating to enable the SBFD operation on the symbol, and / or the like. For example, a downlink symbol may be referred as a symbol indicated as downlink via one or more UL / DL TDD configurations. An uplink symbol may be referred as a symbol indicated as uplink via the one or more UL / DL TDD configurations. A flexible symbol may be referred as a symbol indicted as flexible via the one or more UL / DL TDD configurations. A non-SBFD symbol may refer a uplink symbol, a downlink symbol or a flexible symbol based on the one or more UL / DL TDD configurations, but not indicated as a SBFD symbol based on the one or more SBFDDocket No.: 25-1015PCTconfiguration parameters. A SBFD symbol may refer a symbol indicated for a SBFD operation based on the one or more SBFD configuration parameters.

[0230] In an example, a SBFD symbol may refer a symbol on a cell / carrier / serving cell. In the example, the cell / carrier / serving cell is enabled / indicated / configured with a SBFD operation. The symbol may be indicated as a downlink symbol or a flexible symbol on the cell / carrier / serving cell via one or more messages (e.g., tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated).

[0231] The SBFD symbols / slots are the DL slots / symbols (configured by the one or more configuration parameters) configured / indicated for the SBFD operation.

[0232] The one or more configuration parameters may configure a wireless device with the SBFD operation in the carrier. The one or more configuration parameters may comprise one or more SBFD configuration parameters. The one or more TDD configuration parameters may comprise one or more SBFD configuration parameters.

[0233] The wireless device may be in an RRC connected state. For example, the one or more SBFD configuration parameters may indicate / configure / enable the wireless device for the SBFD operation only when the wireless device is in the RRC connected state. The wireless device may perform a handover procedure (to handover from a source cell of the one or more serving cells to a target cell) based on the one or more SBFD configuration parameters.

[0234] The wireless device may be in an RRC idle / inactive state. For example, the one or more SBFD configuration parameters may indicate / configure / enable the wireless device for the SBFD operation when the wireless device is in the RRC idle / inactive state. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform an initial access procedure (e.g., a random access procedure for the initial access) based on the one or more SBFD configuration parameters. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform a small data transmission (SDT) procedure based on the one or more SBFD configuration parameters. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform SRS transmission for positioning procedure based on the one or more SBFD configuration parameters.

[0235] The one or more SBFD configuration parameters may comprise one or more cell-specific (or common) SBFD configuration parameters.

[0236] The one or more SBFD configuration parameters may comprise one or more UE-specific (or dedicated) SBFD configuration parameters.

[0237] The one or more SBFD configuration parameters may configure one or more SBFD or uplink (UL) subbands. In an example, the wireless device may determine one or more DL subbands based on the one or more UL subbands (e.g., frequency regions of an active downlink BWP excluding the one or more UL subbands and guard band(s) is considered as the one or more DL subbands). The one or more SBFDDocket No.: 25-1015PCTconfiguration parameters may configure / indicate a SBFD / UL subband time locations of a SBFD / UL subband (of the one or more SBFD / UL subbands). The one or more SBFD configuration parameters may configure / indicate a SBFD / UL subband frequency locations of the SBFD / UL subband. For example, the SBFD / UL subband time locations may be within a first period. The first period may be a SBFD period (or a SBFD periodicity). In an example, a set of contiguous PRBs are configured as a SBFD or UL subband, where the wireless device may determine SBUL (UL subband) based on the set of contiguous PRBs and SBUL (DL subband) based on the active downlink BWP and the set of contiguous PRBs.

[0238] The one or more SBFD configuration parameters may configure / indicate a set of SBFD symbols in time locations. The one or more SBFD configuration parameters may configure / indicate one or more DL subbands in a SBFD symbol, and / or one or more UL subbands in a SBFD symbol. The wireless device may determine one or more guard frequency region between a DL subband of the one or more DL subbands and a UL subband of the one or more UL subbands based on the one or more SBFD configuration parameters, e.g ., remaining PRBs not belonging to any DL subband or any UL subband, between two adjacent DL subband and UL subband, may be considered as a guard PRB for the guard frequency region.

[0239] The first period may be based on the at least one TDD pattern. For example, the first period may be the TDD periodicity. The first period may be larger than the TDD periodicity. The first period may be smaller than the TDD periodicity. The one or more SBFD configuration parameters may indicate / configure the first period.

[0240] The first period may be equal to a multiplication of a second value and the TDD periodicity. The one or more SBFD configuration parameters may indicate / configure the second value.

[0241] The first period may be based on the first TDD pattern. For example, the first period may be the first TDD periodicity P (of the first TDD pattern). Based on the one or more SBFD configuration parameters not indicating the first period, the wireless device may set the first period to a default value. The default value may be the first TDD periodicity.

[0242] The first period may be based on the second TDD pattern. For example, the first period may be the second TDD periodicity P2(of the second TDD pattern). Based on the one or more SBFD configuration parameters not indicating the first period, the wireless device may set the first period to the default value. The default value may be the second TDD periodicity.

[0243] In some examples, the default value may be a summation of the first TDD periodicity P1and the second TDD periodicity P2.

[0244] The one or more SBFD configuration parameters may further configure / indicate a second period. The second period may correspond to the second TDD pattern. The first period may correspond to the first TDD pattern. When the second period is absent from the one or more SBFD configuration parametersDocket No.: 25-1015PCT(e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the first TDD pattern.

[0245] It is noted that a SBFD subband, SBUL and UL subband are used interchangeably throughout the specification. SBFD subband DL, SBDL, and DL subband are used interchangeably throughout the specification.

[0246] In another example, when the second period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is configured within / correspond to the first TDD pattern and the second TDD pattern.

[0247] In another example, when the first period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the second TDD pattern and the second TDD pattern.

[0248] In another example, when the first period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the second TDD pattern.

[0249] The one or more SBFD configuration parameters may indicate that a slot / symbol of a set of slots / symbols comprise of at least one SBFD slot / symbol. The one or more SBFD configuration parameters may indicate that a slot / symbol of the set of slots / symbols comprise of at least one non-SBFD slot / symbol. The plurality of slots may comprise the set of slots / symbols. A slot / symbols of the set of slots / symbols may be a DL slot (of the one or more DL slots) or a flexible slot (of the one or more flexible slots / symbols).

[0250] An SBFD slot / symbol of the at least one SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols) configured for the SBFD operation. The SBFD slot / symbol may be within the SBFD time locations.

[0251] A non-SBFD slot / symbol of the at least one non-SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots) or an UL slots / symbol (of the one or more UL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols). The non-SBFD symbol / slot may not be within the SBFD time locations.

[0252] For the SBFD subband frequency locations, FIGs. 17A and 17B provide two examples (or configurations). As shown in FIG. 17A / 17B, a maximum number of UL subbands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is one.

[0253] A first example may correspond to a first (TDD) carrier. An UL subband in an SBFD symbol / slot may be located at one side (e.g., a lowest frequency region or a highest frequency region of a carrierDocket No.: 25-1015PCTfrequency range) of the first carrier. The first example may be referred to by a first type of SBFD operation. In the first type of the SBFD operation, the SBFD symbol / slot (e.g., a first type of SBFD symbol / slot) may correspond to / comprise a D-U or a U-D partitioning / configuration of frequency resources of the SBFD symbol / slot. The carrier may be the first carrier.

[0254] A second example may correspond to a second (TDD) carrier. An UL subband in an SBFD symbol / slot may be located at the middle part of the second carrier. The second example may be referred to by a second type of SBFD operation. In the second type of the SBFD operation, the SBFD symbol / slot (e.g., a second type of SBFD symbol / slot) may correspond to / comprise a D-U-D partitioning / configuration of frequency resources of the SBFD symbol. The carrier may be the second carrier.

[0255] The D-U or the U-D or the D-U-D partitioning of the frequency resources of the SBFD symbol may provide / indicate examples of the SBFD subband frequency location(s). The one or more SBFD configuration parameters may indicate / configure the SBFD subband frequency location(s). The SBFD subband frequency location(s) may correspond to each SBFD symbol / slot within the SBFD subband time locations. In an example, the one or more SBFD configuration parameters may be received via a cellspecific signaling such as SIB, MIB or via a common search space or via a group-common DCI.

[0256] The SBFD symbol / slot may comprise an UL subband and at least one DL subband. The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations. The SBFD subband frequency locations may comprise frequency locations of UL subband and / or frequency locations of DL subband(s) (e g., the at least one DL subband). The frequency locations of the UL subband may comprise at least one subband frequency-domain resources (e.g., PRBs or REs or subcarriers).

[0257] The frequency locations of UL subband may comprise a first set of resource blocks (RBs). The first set of RBs may comprise a first set of resource elements (REs) or a first set of subcarriers. The first set of resource blocks may comprise / be UL subband frequency resources (subcarriers). The first set of resource blocks may correspond to at least a cell-specific UL subband and / or a UE-specific UL subband. The UL subband frequency resources for each SBFD symbol / slot within the SBFD subband time locations may be the first set of RBs.

[0258] In the present disclosure, a set of RBs may interchangeably be used / referred to by “a set of PRBs’’ or "a set of subcarriers” or "a set of REs” or "a set of frequency resources”.

[0259] The frequency locations of DL subband(s) may comprise a second set of resource blocks (RBs). The second set of RBs may comprise a second set of resource elements (REs) or a second set of subcarrers. The second set of resource blocks may comprise / be DL subband frequency resources. The second set of resource blocks may correspond to at least cell-specific DL subband(s) and / or UE-specific DL subband(s). The DL subband(s) frequency resources may comprise / indicate (or be) the frequencyDocket No.: 25-1015PCTlocations of DL subband(s). The DL subbanci frequency resources for each SBFD symbol / slot within the SBFD subband time locations may be the second set of RBs.

[0260] In one example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the second set of RBs. The wireless device may determine / derive a third set of resource blocks (RBs) corresponding to frequency locations of Guardband(s). The frequency locations of Guardband(s) are not within the UL subband or DL subband(s). The third set of RBs may comprise a third set of REs or a third set of subcarriers.

[0261] In another example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the third set of RBs. The wireless device may determine / derive the second set of resource blocks (RBs), e.g., by excluding the first set of RBs and the third set of RBs from RBs of an active DL BWP (or the carrier).

[0262] In yet another example, the one or more SBFD configuration parameters may configure / indicate the second set of RBs and the third set of RBs. The wireless device may determine / derive the first set of resource blocks (RBs), e.g., by excluding the second set of RBs and the third set of RBs from RBs of an active UL BWP (or the carrier). The active UL BWP may correspond to / associated with the active DL BWP.

[0263] The frequency locations of Guardband(s)f or each SBFD symbol / slot within the SBFD subband time locations may be the third set of RBs.

[0264] One or more RBs of the active RBs of the active DL BWP (or the carrier) may comprise a set of (e.g , sum, union) the first set of RBs, the second set of RBs, and the third set of RBs. The first set of RBs may belong to RBs of the active UL BWP.

[0265] The second set of resource blocks / resource elements may comprise contiguous resource blocks / elements (e.g., for the D-U or U-D partitioning of the frequency resources) or non-contiguous blocks / elements (e.g., D-U-D partitioning of the frequency resources).

[0266] The third set of resource blocks / elements may be contiguous, e.g., when only one Guardband (e.g., the D-U or U-D partitioning of the frequency resources) is configured in the SBFD symbol / slot. The set of third resource blocks / elements may be non-contiguous, e.g., when at least two Guardbands (e.g., D-U-D partitioning of the frequency resources) are configured in the SBFD symbol / slot.

[0267] The one or more SBFD configuration parameters may indicate / configure Guardband(s) to reduce interference leakage between / among UL transmissions in the UL subband frequency resources in the SBFD symbol(s) / slot(s) (at a wireless device or a base station) and DL receptions in the DL subband frequency resources in the SBFD symbol(s) / slot(s) (at the wireless device or the base station).

[0268] As also shown in FIG. 20, the UL subband frequency resources (e.g., the first set of RBs) within the active UL BWP may also be referred to by UL usable PRBs. The UL usable PRBs may comprise UL usable resource blocks / elements. The wireless device may determine the UL usable PRBs (or the first setDocket No.: 25-1015PCTof RBs) as an intersection between the UL subband frequency resources configured via the SBFD configuration and the active UL BWP in the SBFD symbol(s) / slot(s). In an example, the wireless device may determine the UL usable PRBs based on the one or more SBFD configuration (e.g ., frequency location of a UL subband) and one or more guardbands that the wireless device is required for supporting a SBFD operation.

[0269] The DL subband(s) frequency resources (e.g., the second set of RBs) within the active DL BWP may also be referred to by DL usable PRBs. The DL usable PRBs may comprise DL usable resource blocks / elements. The wireless device may determine the DL usable PRBs as an intersection between the DL subband(s) frequency resources and active DL BWP in the SBFD symbol(s) / slot(s).

[0270] In some examples, the one or more SBFD configuration parameters may (explicitly or implicitly) configure / indicate the UL / DL usable PRBs within the active UL / DL BWP in the SBFD symbol(s) / slot(s).

[0271] The wireless device may use the UL usable PRBs for UL transmissions (e.g., transmission of UL signals / chan nels) during the at least one SBFD symbol / slot. During the at least one SBFD symbol / slot, DL receptions outside of the DL usable PRBs may not be allowed, e.g., the wireless device may not use the UL usable PRBs and / or the Guardband(s) for DL receptions during the at least one SBFD symbol / slot.

[0272] The wireless device may use the DL usable PRBs for DL receptions (e.g., reception of DL signals / channels) during at least one SBFD symbol / slot. UL transmissions outside the UL usable PRBs may not be allowed, e.g., the wireless device may not use the DL usable PRBs and / or the Guardband(s) for UL transmissions during at least one SBFD symbol / slot

[0273] For example, a maximum number of UL subbands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is a first number. The one or more SBFD configuration parameters may configure / indicate the first number. When the first number is absent / missing from the one or more SBFD configuration parameters, the wireless device may consider a default value for the first number. The default value may be one.

[0274] For example, the first number may be one. The first number may be more than one. The first number may be greater than or equal to one. In one example, if the first number is set to zero, the wireless device may consider / assume the SBFD symbol / slot as a DL symbol / slot or a flexible symbol / slot. In another example, if the first number is set to zero, the wireless device may consider / assume the SBFD symbol / slot as an UL symbol / slot.

[0275] In an example, the wireless device may receive one or more cell-specific configuration parameters comprising time and frequency location of SBFD subbands supported within a TDD carrier. For example, the wireless device may receive the one or more cell-specific configuration parameters via a SIB1 , a SIBx, and / or RRC messages. In an example, the SBFD subband time locations may be configured within a period. For example, when the one or more common TDD configuration parameters are provided, theDocket No.: 25-1015PCTperiod may be same as a periodicity indicated by the one or more common TDD configuration parameters. In case, the one or more common TDD configuration comprises a first periodicity (e.g ., comprised in the first TDD pattern, pattern 1 ) and a second periodicity (e.g., comprised in the second TDD pattern, pattern2), the period may be equal to a sum of the first periodicity and the second periodicity. In an example, when the one or more common TDD configuration parameters are not given for a TDD carrier, the wireless device may assume the period is determined based on one or more of : i) SSB periodicity of the TDD carrier, ii) a default value e.g., 20msec, ill) infinite i.e., no SBFD operation is allowed when the one or more common TDD configuration parameters are not configured / given / provided; iv) additional periodicity configuration parameter comprised in the one or more SBFD configuration parameters. For time domain configuration of the SBFD subbands (e.g., configuration of SBFD symbols), one or more parameters may be received by the wireless device. The one or more parameters may comprise one or more of : i) an index of a starting slot, an index of a starting symbol within the starting slot, an index of an ending slot, and an index of an ending symbol within the ending slot. One or more symbols between the starting symbol of the starting slot and the ending symbol of the ending slot may be considered as one or more SBFD symbols.

[0276] In an example, a slot may comprise one or more SBFD symbols and one or more non-SBFD symbols. A second slot may comprise a plurality of SBFD symbols. A third slot may comprise a plurality of non-SBFD symbols. A SBFD symbol may be determined based on the time and frequency location of SBFD subbands. The SBFD subbands may comprise one or more downlink subbands and one uplink subband. Frequency locations of the SBFD subbands may be same across different slots of the TDD carrier. Frequency locations of the SBFD subbands may be indicated / configured based on a common RB grid (e.g., offset from a CRB #0, a first CRB). The frequency location of SBFD subbands may be configured via a cell-speicfic configuration parameter (e.g., via SIB1, SIBx, and / or RRC). The frequency location of SBFD subbands may comprise {a subcarrier spacing, a reference starting PRB that is an offset from a CRB#0} for each of one or more subcarrier spacings supported for the TDD carrier. The frequency location of the UL subband, for each subcarrier spacing (e.g., one of SCS-SpecificCarrierLisf) may comprise / indicate a starting RB and a bandwidth of the UL subband. The starting RB may be an offset from a CRB#0. The frequency location(s) of the one or more DL subbands, for the each subcarrier spacing (e.g., one of SCS-SpecificCarrierList), may comprise a starting RB and a bandwidth for each DL subband of the one or more DL subbands. The starting RB of the each DL subband may be an offset from the CRB#0.

[0277] In an example, one or more RBs that are comprised in an uplink subband and also comprised in an active UL BWP may be referred as UL usable PRBs. One or more second RBs that are comprised in one or more downlink subbands and also comprised in an active DL BWP may be referred as DL useable PRBs. For example, the wireless device may determine the UL usable PRBs and / or the DL usable PRBs based on the time and frequency location of SBFD subbands of the TDD carrier. For the frequencyDocket No.: 25-1015PCTlocations of the SBFD subbancis, frequency locations of the UL subbanci and the one or more DL subbands may be configured via cell-specific configuration parameters. The wireless device may determine guardband^), where each RB of the guard-band(s) may not be comprised in the UL subband and the one or more DL subband(s).

[0278] For a wireless device that supports a SBFD operation (e.g., a SBFD-aware UE), the wireless device may transmit uplink signal(s) via the UL usable PRBs during one or more SBFD symbols, may receive downlink signal(s) via the DL usable PRBs during one or more second SBFD symbols, may not transmit uplink signal(s) outside of UL usable PRBs during one or more third SBFD symbols, may not receive downlink signal(s) outside of DL usable PRBs during one or more fourth SBFD symbols, except for receiving RSs for cross-link interference (e.g , a zero-power CSI-RS, a SRS, etc).

[0279] During one or more SBFD symbols, a wireless device (a SBFD-aware UE) may determine a link direction (e.g., whether to receive downlink signal(s) or transmit uplink signal(s)) based on configured / scheduled transmission / reception. For example, if the wireless device receives a UL grant during the one or more SBFD symbols, the wireless device may transmit an uplink transmission during the one or more SBFD symbols.

[0280] For frequency resource allocation Type 0 for PDSCH or PUSCH in a single slot by DCI based scheduling (without repetition or TBoMS), when an assigned RBG overlaps with the subband boundary, only the PRBs within DL usable PRBs may be considered to be valid for PDSCH reception and only the PRBs within UL usable PRBs are considered to be valid for PUSCH transmission. SBFD aware UE does not expect to be assigned with a RBG for PDSCH which is fully outside DL usable PRBs or a RBG for PUSCH which is fully outside UL usable PRBs.

[0281] For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots (each transmission / reception within a slot has either all SBFD or all non-SBFD symbols) for an SBFD aware UE, the SBFD-aware UE may be configured with one of the configurations per each uplink BWP and / or each downlink BWP: i) Configuration 1 - The transmissions / receptions are restricted to SBFD symbols only or non-SBFD symbols only; and ii) Configuration 2 -- The transmissions / receptions may be in SBFD symbols and non-SBFD symbols.

[0282] For example, with the Configuration 1, the following behavior may be applied.

[0283] A) if a DCI schedules a PUSCH without a repetition, the DCI may indicate resources during either one or more SBFD symbols or one or more non-SBFD symbols;

[0284] B) if a DCI schedules a PUSCH with a repetition or a TB over multiple slot (TBoMS), each transmission of the repetition or TBoMS PUSCH may occur either during one or more SBFD symbols or non-SBFD symbols, where the wireless device may determine a symbol type (e.g., SBFD or non-SBFD) used for the each transmission based on a first (actual) PUSCH transmission indicated / scheduled by theDocket No.: 25-1015PCTDCI; The each transmission may follow the symbol type determined / indicated for the first PUSCH transmission.

[0285] C) for a configured grant configuration (e.g., Type 1) configured via RRC without activation DCI, a higher layer may indicate which symbol type to use, or follow a symbol type of a first CG occasion;

[0286] D) for a CG configuration (e.g., Type 2) configured via RRC with activation DCI, a symbol type may be determined based on the activation DCI. A first CG PUSCH activated by the activation DCI may determine the symbol type.

[0287] FIG. 18 illustrates an example as per an aspect of an embodiment of the present disclosure.

[0288] In an example, a wireless device may perform an initial access procedure to establish a RRC connection with a cell, e.g., as shown in FIG. 18. The wireless device may perform a cell search, where the wireless device may identify one or more physical cell identifiers and / or time / frequency tracking information of one or more cells. The wireless device may determine a suitable cell among the one or more cells. The wireless device may initiate obtain / acquire / receive a SIB1 (e.g., a first system information block) message from the suitable cell. The wireless device may initiate / start to perform the initial access procedure to the suitable cell (e g., the cell, CC19 in FIG. 18). Similar procedure of an initial access procedure may be performed during a handover and / or a Iayer1 / layer2 triggered mobility (LTM) switching from a source cell to a target cell.

[0289] A base station may transmit one or more SIB messages to the wireless device. The one or more SIB messages may be broadcasted and / or sent to the wireless device via RRC signaling. The wireless device may receive the one or more SIB messages at a time TO in FIG. 18. The one or more SIB messages may comprise configuration parameters for the initial access procedure. The configuration parameters may indicate a first set of PRACH occasions (ROs) of an uplink carrier (e.g., CC19). The configuration parameters may comprise a RACH-ConfigCommon IE. The wireless device may determine the first set of ROs based on the RACH-ConfigCommon for the uplink carrier, where each RO of the first set of ROs may be during one or more uplink symbols and / or one or more flexible symbols. The wireless device may determine the one or more uplink symbols and / or the one or more flexible symbols based on the one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon). The configuration parameters may indicate / comprise the one or more common TDD configuration parameters. The configuration parameter may, additionally / optionally, indicate one or more SBFD configuration parameters of the cell. The one or more SBFD configuration parameters may indicate a plurality of SBFD symbols of / on the cell and / or one or more downlink subbands and one uplink subband of the cell. A first RO of the first set of ROs may be during one or more uplink / flexible symbols. The first RO may or may not overlap, in time, with one or more SBFD symbols.Docket No.: 25-1015PCT

[0290] In an example, the wireless device may determine a set of UL usable PRBs, where a PRB of the set of UL PRBs belongs to the one uplink subband of the cell and belongs to an active UL BWP of the cell. The set of UL usable PRBs may be contiguous in frequency domain. The set of UL usable PRBs may be referred as a set of available uplink PRBs, a set of UL available PRBs, a set of schedulable UL PRBs, a set of SBFD-UL PRBs, and / or the like.

[0291] The base station may transmit the one or more SBFD configuration parameters based on the cell being enabled with a SBFD operation. The base station may enable the SBFD operation for one or more wireless devices in RRC_CONNECTED and may not enable the SBFD operation for an initial access procedure (e.g. , for devices in RRCJDLE and / or RRCJNACTIVE state). Alternatively, the base station may enable the SBFD operation for wireless devices in RRC_CONNECTED and / or RRCJNACTIVE and / or RRCJDLE state. For example, the configuration parameters may comprise / indicate a flag / a bit field / a field (e.g., a SBFD-rach-enabled) whether to enable the SBFD operation during the initial access procedure or not. When the flag / bit field / the field is not present or set to ‘FALSE / 0’ or ‘disabled’, the wireless device may not determine the second set of ROs that is additional ROs based on a SBFD operation being enabled for the initial access procedure When the flag / bit field / field is present and / or when the one or more SBFD configuration parameters are provided, the configuration parameters may, additionally / optionally, indicate whether a RACH-Config-Option1 is used or a RACH-Config-Option2 is used for the initial access procedure. I

[0292] When the RACH-Config-Option1 is used / enabled, the wireless device may determine a second set of ROs based on the RACH-ConfigCommon, where each RO of the second set of ROs may be during one or more downlink symbols and one or more SBFD symbols. The wireless device may determine the one or more downlink symbols based on the one or more common TDD configuration parameters. The wireless device may determine the one or more SBFD symbols based on the one or more SBFD configuration parameters.

[0293] When the RACH-Config-Option2 is used, the RACH-ConfigCommon may indicate the first set of ROs and a second RACH-ConfigCommon may indicate the second set of ROs. In the example, the one or more messages may further indicate the second RACH-ConfigCommon. The wireless device may determine the second set of ROs, based on the second RACH-ConfigCommon, where each RO of the second set of ROs overlap in time with the one or more SBFD symbols indicated by the one or more SBFD configuration parameters. A first RO of the second set of ROs may overlap one or more downlink, flexible and / or uplink symbols by the one or more common TDD configuration parameters. For example, In the example, the each RO of the second set of ROs may overlap in time with the one or more SBFD symbols and not overlap in time with non-SBFD symbol(s). In the example, alternatively / additionally, based on a higher layer configuration, a RO of the second set of ROs may overlap in time with one or more SBFDDocket No.: 25-1015PCTsymbols and one or more non-SBFD symbols, where the one or more SBFD symbols occur before the one or more non-SBFD symbols in time. The base station may configure to enable or disable the RO overlapping with the one or more SBFD symbols and the one or more non-SBFD symbols via the higher layer signaling.

[0294] In an example, when the RACH-Config-Option1 is used, the wireless device may determine a first RO of the second set of ROs as valid based on the following rules:

[0295] A) The first RO starts, in time, at least N symbols after a last downlink and non-SBFD symbol, where N may be determined based on a subcarrier spacing of an initial uplink BWP of the cell; and

[0296] B) The first RO starts, in time, at least N symbols after a SSB occasion of the cell; and

[0297] C) The first RO is during one or more downlink symbols configured by the one or more common TDD configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon)', and

[0298] D) The first RO is within the uplink subband of the cell in frequency domain and the first RO is within the set of usable UL PRBs of the cell; and

[0299] E) The first RO does not overlap, in time, with a SSB occasion of the cell.

[0300] In an example, when the RACH-Config-Option2 is used, the wireless device may determine a first RO of the second set of ROs as valid based on the following rules:

[0301] A) The first RO are during one or more SBFD symbols and may not overlap, in time, with non-SBFD symbols unless configured by higher layer otherwise; the first RO are during one or more SBFD symbols and one or more non-SBFD symbols where the one or more SBFD symbols occur before the one or more non-SBFD symbols, where the one or more non-SBFD symbols are uplink and / or flexible symbol(s) and the wireless device is configured by higher layer to apply this behavior; and

[0302] B) The first RO, in time, at least N symbols after a last downlink and non-SBFD symbol, where N may be determined based on a subcarrier spacing of an initial uplink BWP of the cell; and

[0303] B) The first RO starts, in time, at least N symbols after a SSB occasion of the cell; and

[0304] C) The first RO does not overlap, in time, with a SSB occasion of the cell; and

[0305] D) Option al ly / add itionally, the first RO is within the set of usable UL PRBs of the cell.

[0306] At the time TO, the wireless device may determine the first set of ROs and the second set of ROs based on the above.

[0307] At a time T1 , the wireless device may transmit a preamble using a valid RO of the first set of ROs and / or the second set of ROs. For example, based on a priority rule and / or parameter(s), the wireless device may determine the valid RO from the first set of ROs or the valid RO from the second set of ROs. For example, a RSRP threshold to indicate whether to use the first set of ROs or the second set of ROs may be configured via the configuration parameters. For example, the wireless device may determine to use or may use the second set of ROs (e.g., the valid RO is from the second set of ROs) based on a RSRPDocket No.: 25-1015PCTof a SSB of the cell is higher than or equal to the RSRP threshold. Otherwise, the wireless device may determine or may use the first set of ROs (e.g., the valid RO is from the first set of ROs).

[0308] The wireless device may receive a random access response (RAR) corresponding to the preamble at a time T2. The RAR may comprise an uplink grant for a RUSCH transmission. The RUSCH transmission may comprise a Msg3 payload. The PUSCH transmission scheduled via the RAR may be referred as a Msg3 PUSCH transmission. The wireless device may transmit the PUSCH transmission at a time T3. The wireless device may comprise / transmit contention resolution information via the Msg3 PUSCH. The base station may transmit a PDSCH at a time T4, where the PDSCH may comprise a Msg4 payload. The Msg3 payload may comprise information about the contention resolution. Based on the Msg4 payload, the wireless device may determine whether a random access procedure, initiated based on the preamble transmission, is successfully completed. The wireless device may transmit a HARQ-ACK feedback for the PDSCH, received at the time T4, at a time T5.

[0309] In an example, the configuration parameters may comprise a downlnkConfigCommon (e.g., via DownlinkConfigCommon IE), an uplinkConfigCommon (e.g., via UplinkConfigCommon IE). The uplinkConfigCommon may indicate parameters of an uplink carrier of the cell The UplinkConfigCommon IE may indicate the initial uplink BWP (initialUplinkBWP) via BWP-UplinkCommon IE. The initialUplinkBWP may comprise the rach-ConfigCommon. In the example, the initialUplinkBWP may comprise a parameter to enable the RACH-Config-Option1 and / or the RACH-Config-Option2 or disable either option for the cell. In case the parameter is not present, the wireless device may not apply the RACH-Config-Option1 (nor the RACH-Config-Option2).

[0310] In an example, the wireless device may determine a first set of ROs based on the rach-ConfigCommon of the initialUplinkBWP. In the example, the first set of ROs may be referred as a set of legacy ROs not associated with any feature. In the example, the wireless device may determine a second set of ROs based on the rach-ConfigCommon of the initialUplinkBWP, and the parameter indicating / enabling the RACH-Config-Option1 and the one or more SBFD configuration parameters of the cell. The second set of ROs may be referred as a set of SBFD ROs not associated with any feature.

[0311] In the example, the rach-ConfigCommon may comprise a rach-ConfigGeneric (via RACH-ConfigGeneric IE). The rach-ConfigGeneric may comprise a prach-Configurationlndex. The wireless device may determine the first set of ROs based on the rach-ConfigGeneric and the prach-Configurationlndex. The wireless device may determine the second set of ROs based on the rach-ConfigGeneric, the prach-Configurationlndex and the one or more SBFD configuration parameters.

[0312] In another example of determining the second set of ROs or the RACH-Config-Option2 is enabled, the one or more messages may further / additionally / optionally indicate a second rach-ConfigCommon comprised in the initialUplinkBWP. The wireless device may determine the second set of ROs based on theDocket No.: 25-1015PCTsecond rach-ConfigCommon. In an example, the set of RACH resources may comprise the first set of ROs and the second set of ROs. In the specification, a RACH resource may be referred as a RO. In the example, the second set of ROs may not be associated with any feature or a feature combination.

[0313] In another example of determining the second set of ROs, the one or more messages may further further / additionally / optionally indicate a second rach-ConfigGeneric comprised in the rach-ConfigCommon. The second rach-ConfigGeneric may indicate / comprise a second prach-Configurationlndex. The wireless device may determine the first set of ROs based on the rach-ConfigGeneric comprised in the rach-ConfigCommon and the prach-Configurationlndex of the rach-ConfigGeneric. The wireless device may determine the second set of ROs based on the second rach-ConfigGeneric comprised in the rach-ConfigCommon and the second prach-Configurationlndex of the second rach-ConfigGeneric. The in iti al U plin kB WP may comprise / indicate a first set of contiguous PRBs for a bandwidth part of the initial uplink BWP and / or a subcarrier spacing of the initial uplink BWP.

[0314] In an example, the initialUplinkBWP(e.g., the initial uplink BWP of the uplink carrier) may comprise / indicate a list of additional ROs (e.g., additionalRACH-ConfigList). An entry of the list of additional ROs may comprise parameters (e.g., rach-ConfigCommon(-F\7)) via RACH-ConfigCommon IE. An additional RACH config (e.g., the entry) of the additionalRACH-ConfigList may comprise / indicate one or more sets of RACH resources, where each set of RACH resources may be associated with a feature combination or a feature.

[0315] In an example, for example, based on the RACH-Config-Option1, the additional RACH config may indicate / comprise a featwe-rach-ConfigCommon (e.g., via RACH-ConfigCommon IE) and / or a rach-ConfigCommonTwoStepRA (e.g., via RACH-ConfigCommonTwoStepRA) . The wireless device may determine the set of ROs based on the feature-rach-ConfigCommon. The wireless device may determine the first set of ROs of the set of ROs, where each RO of the first set of ROs is during one or more uplin k / flexible symbols. The wireless device may determine the second set of ROs of the set of ROs, where each RO of the second set of ROs is during one or more SBFD symbols.

[0316] Alternatively, for example based on the RACH-Config-Option2, the additional RACH config may indicate / comprise a feature-rach-ConfigCommon (e.g., via RACH-ConfigCommon IE), a rach-ConfigCommonTwoStepRA (e.g., via RACH-ConfigCommonTwoStepRA), and / or a SBFD-feature-rach-ConfigCommon (e.g., via RACH-ConfigCommon IE). The wireless device may determine the set of ROs based on the featwe-rach-ConfigCommon and the SBFD-feature-rach-ConfigCommon . For example, the wireless device may determine the first set of ROs based on the feature-rach-ConfigCommon. The wireless device may determine the second set of ROs based on the SBFD-feature-rach-ConfigCommon.

[0317] A RACH-ConfigCommon IE may comprise / indicate a rach-ConfigGeneric (via RACH-ConfigGeneric IE), a RSRP threshold (rsrp-ThresholdSSB) , msg1 subcarrier spacing (msg1-Docket No.: 25-1015PCTSubcarrierSpacing), a msg3 transformprecoder (msg3-transformPrecoder), a list of feature combination preamble (e.g., featureCombinationPreambleList, Featurecombination). For example, the rach-ConfigCommon and / or the second rach-ConfigCommon may comprise a list of feature combination preamble (e.g., featureCombinationPreambleList, Featurecombination) respectively. The list of feature combination preamble may be present for the list of additional ROs (e.g., additionalRACH-ConfigList), but not for the rach-ConfigCommon (and / or the second rach-ConfigCommon). For example, an entry (e.g., a msg1-repetition-rach-ConfigCommon) of the list of additional ROs indicates a feature combination comprising a msg1 repetition (e.g., an entry of the featureCombinationPreamblesList (e.g., Featurecombination) indicates enabling a feature of ‘msg 1 -repetitions’), then RACH resources determined based on the entry of the list of additional ROs may be referred as RACH resources associated with the msg1 repetition or RACH resources with msg 1 -Repetitions set to ‘true. When the wireless device supports a msg1 -repetitions, the wireless device may determine a set of RACH resources / ROs configured with a msg 1 -repetitions (e.g., the set of RACH resources / ROs enabled / indicated with a msg 1 -repetitions feature enabled). The wireless device may determine the first set of ROs, among RACH resources, based on parameters of the RACH-ConfigCommon IE of the entry (e.g., the msg1-repetition-rach-ConfigCommon) of the list of additional ROs. The wireless device may determine the second set of ROs, among RACH resources, based on parameters of the RACH-ConfigCommon IE of the entry of the list of additional ROs, e.g., when the RACH-Config-Option1 is enabled. A mechanism to determine the first set of ROs and the second set of ROs, associated with a certain feature (e.g., msg 1 -repetitions), based on the msgl-repetition-rach-ConfigCommon may be similar to determining the first set of ROs and the second set of ROs based on the rach-ConfigCommon.

[0318] For example, an entry (e.g., a msg3-repetition-rach-ConfigCommon) of the list of additional ROs indicates a feature combination comprising a msg3 repetition (e.g., an entry of the featureCombinationPreamblesList (e.g., FeatureCombination) indicates enabling a feature of ‘msg3-repetitions’), then RACH resources determined based on the entry of the list of additional ROs may be referred as RACH resources associated with the msg3 repetition or RACH resources with msg3-Repetitions set to 'true. The wireless device may determine the first set of ROs, among RACH resources, based on parameters of the RACH-ConfigCommon IE of the entry (e.g., the msg3-repetition-rach-ConfigCommon) of the list of additional ROs. The wireless device may determine the second set of ROs, among RACH resources, based on parameters of the RACH-ConfigCommon IE of the entry of the list of additional ROs, e.g., when the RACH-Config-Option1 is enabled. A mechanism to determine the first set of ROs and the second set of ROs, associated with a certain feature (e.g., msg3-repetitions), based on the msg3-repetition-rach-ConfigCommon may be similar to determining the first set of ROs and the second set of ROs based on the rach-ConfigCommon.Docket No.: 25-1015PCT

[0319] A FeatureCombination may indicate to enable one or more features such as ‘redCap’ , ‘smallData’ , ‘nsag’, ‘msg3-Repetitions’, ‘msg1 -Repetitions', and / or 'eRedCap'.

[0320] The initialUpiinkBWP may indicate / comprise parameters indicating a first RSRP threshold for a Msg 1 repetition (e.g . , rsrp-ThresholdMsg1-RepetitionNum2) with a first number of repetitions (e.g., 2), a second RSRP threshold for a Msg1 repetition (e.g., rsrp-ThresholdMsg1-RepetitionNum2) with a second number of repetitions (e.g., 4), and / or a third RSRP threshold for a Msg 1 repetition (e.g., rsrp-ThresholdMsg1-RepetitionNum2') with a third number of repetitions (e.g., 8). The initialUplinkBWP may, additionally / optionally, indicate / comprise parameters indicating a fourth RSRP threshold for a Msg 1 repetition (e.g., rsrp-ThresholdMsg1-RepetitionNum2) with the first number of repetitions (e.g., 2), a fifth RSRP threshold for a Msg1 repetition (e.g., rsrp-ThresholdMsg1-RepetitionNum2) with the second number of repetitions (e.g., 4), and / or a sixth RSRP threshold for a Msg 1 repetition (e.g., rsrp-ThresholdMsg1 -RepetitionNum2') with the third number of repetitions (e.g., 8).

[0321] The first RSRP threshold for a Msg1 repetition, the second RSRP threshold for a Msg1 repetition, the third RSRP threshold for a Msg1 repetition, and / or the fourth RSRP threshold for a Msg1 repetition, the fifth RSRP threshold for a Msg1 repetition, the sixth RSRP threshold for a Msg1 repetition may be used by the wireless device to determine whether to select resources indicating a Msg1 repetition number 2, 4, or 8 and / or a RACH type between 'legacy' and ‘SBFD’ (or between the first set of ROs and the second set of ROs).

[0322] In the example, the first set of ROs and the second set of ROs may be configured / indicated via the one or more messages for each feature set (e.g., msg 1 -Repetitions, msg3-Repetitions, redCap, smallData, nsag, eRedCap). In the example, the first set of ROs and the second set of ROs may be configured / indicated for each set of feature combinations (e.g., a combination of various features such as msg 1 -Repetitions, msg3-Repetitions, redCap, smallData, nsag, eRedCap). For example, for a set of feature combinations, a feature rach-ConfigCommon (e.g., a feature-rach-ConfigCommon) may be provided for the initial uplink BWP and / or an uplink BWP of the uplink carrier of the cell. The feature rach-ConfigCommon may indicate a first set of ROs associated with the set of feature combinations and a second set of ROs associated with the set of feature combinations, similarly as determining the first set of ROs and the second set of ROs based on the rach-ConfigCommon.

[0323] For example, the wireless device may be configured with a list of the first set of ROs for various features. The wireless device may be additionally configured with a list of the second set of ROs for the various features. In an example, for a feature set, the wireless device may be configured with the first set of ROs only or the second set of ROs only or both the first set of ROs and the second set of ROs.Docket No.: 25-1015PCT

[0324] In the specification, the first set of ROs may refer a set of ROs associated with a set of feature combinations or not associated with any feature. The second set of ROs may be refer a second set of ROs associated with the set of feature combinations or not associated with any feature.

[0325] For example, the downlnkConfigCommon may comprise parameters of downlink frequency (e.g., frequencylnfoDL) and / or an initial downlink BWP (e.g., initialDownlinkBWPvia BWP-DownlinkCommon IE). The initial DownlinkBWP may comprise / indicate a second set of contiguous PRBs for a bandwidth part of the initial downlink BWP of the cell and / or a subcarrier spacing of the initial downlink BWP. The subcarrier spacing of the initial downlink BWP and the subcarrier spacing of the initial uplink BWP may be same at least when the initial downlink BWP and the initial uplink BWP are paired (e.g., in an unpaired spectrum). The initialDownlinkBWP may comprise cell specific parameters for a PDCCH (e.g., pdcch-ConfigCommon via PDCCH-ConfigCommon IE) and / or cell specific parameters for a PDSCH (e.g., pdsch-ConfigCommon via PDSCH-ConfigCommon IE).

[0326] The pdcch-ConfigCommon may indicate / comprise a control resource set with an index zero (e.g., controlResourceSetZero via ControlResourceSetZero IE), and / or a common coreset (e.g., commonControResoruceSet via Control ResourceSet IE), and / or a search space set with an index zero (e.g., a search SpaceZero via SearchSpaceZero IE), and / or a list of common search space sets (e.g., a list of SearchSpace lEs), and / or a search space identifier for receiving a SIB1 (e.g., searchSpaceSIBI via SearchSpaceld IE), and / or a search space identifier for receiving a SIBx (other than SIB1) (e.g., searchSpaceOtherSystemlnformation via SearchSpaceld IE), and / or a search space identifier for receiving a paging (e.g., pagingSeachSpace via SearchSpaceld IE), and / or a search space identifier for receiving a RAR (e.g., ra-SearchSpace via SearchSpaceld IE) and / or a flag to indicate whether to follow a unified TCI state for the downlink reception (e.g., followUnifiedTCI-State).

[0327] The pdsch-ConfigCommon may indicate / comprise a list of time domain resource allocation (e.g., pdsch-TimeDomainAllocationList via PDSCH-TimeDomainResourceAllocationList IE)

[0328] In the present disclosure, a temporary cell-RNTI (TC-RNTI) may refer an identifier carried via a MAC payload during a random access procedure. A size of the TC-RNTI is 16 bits. A random access response corresponding to a PRACH transmission with a preamble may comprise the MAC payload comprising the temporary C-RNTI (TC-RNTI) during an initial access procedure. Once a wireless device is received / configured with a C-RNTI, a RAR for the wireless device may not comprise a TC-RNTI. Based on whether a contention resolution is needed or not, a RAR for a preamble may comprise a TC-RNTI or not. A TC-RNTI may be referred as a temporary C-RNTI, temporary_C-RNTI, and / or the like.

[0329] In the present disclosure, a RACH resource may be referred as a PRACH resource, a RACH resource, a RO, a PRACH occasion, a rach resource, a RACH RO, a RACH occasion and / or the like. A set of RACH resources may be referred as a set of ROs, a set of rach resources, a set of PRACH occasions, aDocket No.: 25-1015PCTlist of ROs, a list of RACH resources, a group of ROs, a group of RACH resources, ROs based on a prach-Configurationlndex, ROs based on a rach-Config, a group of preambles, a set of preambles, one or more ROs, one or more preambles, a plurality of ROs, a plurality of preambles, etc.

[0330] In the specification, a set of ROs may comprise a first set of ROs and a second set of ROs.Alternatively, the set of ROs may comprise either the first set of ROs or the second set of ROs.

[0331] In the specification, the first set of ROs may be referred as a legacy RO set, a legacy set of ROs, a common set of ROs, a default set of ROs, legacy ROs, non-SBFD ROs, common ROs, a set of ROs, and / or the like. In the specification, the first set of ROs may comprise RACH resource(s) 252a (in FIG. 20). In an example, a first RO of the first set of ROs or the legacy set of ROs may be during or overlap, in time, with) one or more uplink symbols and / or one or more flexible symbols (based on TDD-UL-DL-Configuration Common).

[0332] The second set of ROs may be referred as an additional RO set for a SBFD-aware U E, an additional set of ROs for a SBFD operation, SBFD-ROs, ROs for a SBFD, SBFD operation ROs, a SBFD set of ROs, and / or the like. In the specification, the second set of ROs may comprise RACH resource(s) 252b. A second RO of the second set of ROs (or a SBFD set of ROs) is in one or more SBFD symbols (based on SBFD configuration parameters) (and / or the one or more SBFD symbols are downlink symbols and / or flexible symbols (based on TDD-UL-DL-ConfigurationCommon)).

[0333] In the specifications, a 4-step legacy set of ROs may refer a set of ROs used for 4-step RA procedure and / based on a legacy set of ROs. A 4-step SBFD set of ROs may refer a set of ROs used for 4-step RA procedure and / based on a SBFD set of ROs. A 2-step legacy set of ROs may refer a set of ROs used for 2-step RA procedure and / based on a legacy set of ROs. A 2-step SBFD set of ROs may refer a set of ROs used for 2-step RA procedure and / based on a SBFD set of ROs.

[0334] In the specification, a random access procedure is referred or initiated by transmitting a preamble or a PRACH via a RO. The RO is from the first set of ROs (or a legacy set of ROs, 4-step legacy RO set, 2-step legacy RO set) may refer that a RA symbol type of the random access procedure is a 'non-SBFD' ‘type A' or 'legacy'. The RO is from the second set of ROs (or a SBFD set of ROs, 4-step SBFD RO set, 2-step SBFD RO set) may refer that a RA type of the random access procedure is a ‘SBFD’ or 'type B’ . When the RO is from the first set of ROs, a RACH symbol type of the random access procedure may be set to 'legacy' or ‘type A' or 'non-SBFD'. When the RO is from the second set of ROs, a RACH symbol type of the random access procedure may be set to 'SBFD' or ‘type B'. The RACH symbol type is 'SBFD' or ‘type B' may refer that the random access procedure is based on the SBFD set of ROs / the second set of ROs or the preamble is from the SBFD set of ROs / the second set of ROs. The RACH symbol type is ‘non-SBFD’ or ‘legacy’ may refer that the random access procedure is based on the legacy set of ROs / the first set of ROs or the preamble is from the legacy set of ROs / the first set of ROs.Docket No.: 25-1015PCT

[0335] In the specification, a RACH symbol type of a random access procedure may be determined based on a set of ROs that the random access procedure is based on. The RACH symbol type of a random access procedure being ‘non-SBFD’ or ‘type A’ or ‘legacy’ may refer that the random access procedure has initiated based on a legacy set of ROs or a set of ROs that are common to a plurality of wireless devices of a cell, regardless of whether the plurality of wireless devices support a SBFD operation of the cell or not. The RACH symbol type of a random access procedure being ‘SBFD1or ‘type B1may refer that the random access procedure has initiated based on a SBFD set of ROs that are common to one or more wireless devices of the plurality of wireless devices of a cell, where each of the one or more wireless devices support a SBFD operation of the cell.

[0336] In the specification, a RACH symbol type of a random access procedure may be determined based on a set of ROs and / or a configuration option. For example, the RACH symbol type of a random access procedure may be one of {‘Type A’, ‘Type B', ‘Type C’}, where the ‘Type A' may refer a legacy set of ROs, the ‘Type B’ may refer a SBFD set of ROs based on a RACH-Config-Option1 (e.g., determine the legacy set of ROs and the SBFD set of ROs based on a prach-Configurationlndex) and the SBFD set of ROs is for a 4-step random access procedure, and ‘Type C may refer a SBFD set of ROs based on a RACH-Config-Option2 (e.g., determine the legacy set of ROs based on a first prach-Configurationlndex and the SBFD set of ROs based on a second prach-Configurationlndex that are common to one or more wireless devices of the plurality of wireless devices of a cell, where each of the one or more wireless devices support a SBFD operation of the cell) and the SBFD set of ROs is for a 4-step random access procedure. A RO from a set of ROs may be referred as a RACH type of a random access procedure, initiated based on a preamble via the RO, is one of Type A', ‘Type B’, ‘Type C'}.

[0337] In the specification, a RACH symbol type of a random access procedure may be determined based on a set of ROs and / or a configuration option. For example, the RACH (symbol) type of a random access procedure may be one of {‘Type T, ‘Type 1 -B', ‘Type 1-C, ‘Type 2’}, where the ‘Type T may refer a legacy set of ROs with a 4-step random access procedure, the ‘Type 1-B' may refer a SBFD set of ROs based on a RACH-Config-Option1 (e.g., determine the legacy set of ROs and the SBFD set of ROs based on a prach-Configurationlndex) with a 4-step random access procedure, and ‘Type 1-0 may refer a SBFD set of ROs based on a RACH-Config-Option2 (e.g., determine the legacy set of ROs based on a first prach-Configurationlndex and the SBFD set of ROs based on a second prach-Configurationlndex that are common to one or more wireless devices of the plurality of wireless devices of a cell, where each of the one or more wireless devices support a SBFD operation of the cell) and the SBFD set of ROs is for a 4-step random access procedure, and 'Type 2’ may refer a second legacy set of ROs with a 2-step random access procedure. A RO from a set of ROs may be referred as a RACH type of a random access procedure, initiated based on a preamble via the RO, is one of {'Type T, ‘Type 1-B', ‘Type 1-C, 'Type 2'}.Docket No.: 25-1015PCT

[0338] In the specification, the second set of ROs (or the SBFD set of ROs) may be determined based on a first random access resource configuration option (e.g., a RACH-Config-Option 1) or a second random access resource configuration option (e.g., a RACH-Config-Option 2). Based on the first option (e.g., the RACH-Config-Option 1), the first set of ROs and the second set of ROs may be determined based on a single prach-Configurationlndex. Based on the second option (e.g., the RACH-Config-Option 2), the second set of ROs may be determined based on a separate prach-Configurationlndex from a first prach-Configurationlndex used for the first set of ROs.

[0339] In the specification, a wireless device may apply a parameter may refer that the wireless device determines parameter(s) related to an uplink transmission or a downlink reception based on the parameter.

[0340] In the specifications, a field indicate one of a list may refer that the wireless device uses a value of the field as an index in the list to determine a parameter value. For example, if a field indicates 2, the wireless device may determine 3rdentry from the list and uses a parameter value in the 3rdentry of the list.

[0341] In the specification, the uplink transmission overlaps, in time, with one or more SBFD symbols may refer a case that the uplink transmission overlaps, in time, with SBFD symbols that are downlink symbols. If the uplink transmission overlaps, in time, with uplink and / or flexible symbols, this may be referred as the uplink transmission does not overlap with SBFD symbol(s) or overlap with non-SBFD symbols.Alternatively, the uplink transmission overlaps, in time, with one or more SBFD symbols may refer a case that the uplink transmission overlaps, in time, with SBFD symbols that are downlink and / or flexible symbols. If the uplink transmission overlaps, in time, with uplink and / or flexible symbols and the uplink transmission does not overlap, in time, with SBFD symbols, this may be referred as the uplink transmission does not overlap with SBFD symbol(s) or overlap with non-SBFD symbols. Either alternative may be considered for various embodiments of the specification.

[0342] In the specification, a RUSCH may be interchangeably used with a RUSCH transmission (or vice versa). A PUSCH transmission may refer an uplink transmission using a PUSCH channel. A PUSCH may refer an uplink transmission via / using a PUSCH channel. An uplink transmission may be via a PUSCH, a PUCCH or a SRS or a PRACH. A Msg3 PUSCH may refer a PUSCH comprising / conveying a payload of a Msg3.

[0343] In the specification, a SBFD symbol may be determined based on one or more SBFD configuration parameters of a cell. Other symbols, not indicated as SBFD symbols, may be considered as non-SBFD symbols. Non-SBFD symbols may be downlink, uplink and / or flexible symbols. An uplink subband may refer one or more PRBs of the cell, where the one or more PRBs are contiguous. UL usable PRBs may refer one or more second PRBs of the cell, where a PRB of the one or more second PRBs is comprised in the uplink subband of the cell and an active uplink BWP of the cell.Docket No.: 25-1015PCT

[0344] In the specification, a Msg3 PUSCH comprises a temporary C-RNTI (TC-RNTI) may refer a payload of the Msg3 PUSCH comprises the C-RNTI as a payload, and / or the PUSCH is CRC-scrambled with the TC-RNTI (e.g., the scrambling initialization of the PUSCH is by the TC-RNTI).

[0345] Existing technologies face several challenges. One of the challenges arises when a user equipment (UE) (a.k.a., a “wireless device” or “WD”) performs an initial access to a cell provided by a base station (“BS”). For example, at the time that the UE performs the initial access to the cell, the BS may not be aware whether the UE supports subband full duplex (SBFD). As a result, even when the UE is capable of supporting SBFD - hereinafter referred to as an “SBFD-aware UE” -, the UE may only use, for the initial access, resource(s) in non-SBFD symbols (e.g., conventional uplink and / or flexible symbols). This may prevent the UE from utilizing resources in SBFD symbols, leading to inefficiencies in the usage of available network resources.

[0346] In another example, an SBFD operation of the cell / the BS may require one or more UE functionalities such as, for example, supporting subband(s) within a BWP, supporting a plurality of power control parameters for an uplink transmission, supporting a plurality sets of random access resource sets, etc. The UE, however, may only support a subset of the one or more functionalities and may not support the full set of the one or more functionalities. Because, in existing technologies, the UE may be required to support the full set of the one or more functionalities to be able to properly utilize the resources in SBFD symbols during the initial access, the UE, which supports only a subset of the one or more functionalities, may not be able to utilize resources in SBFD symbols properly (e.g., may utilize the resources in SBFD symbols without coordination with the BS). This may result in packet drops and / or increased network usage, for example, due to retransmissions. Therefore, there is a need for a way to make the UE to utilize properly, for the initial access to the cell, resources in SBFD symbols when the UE is an SBFD-aware UE.

[0347] Accordingly, in one example of the embodiments of this disclosure, a method comprises receiving, by a wireless device and for a cell, one or more messages indicating: one or more first physical random access channel (PRACH) resources in one or more uplink symbols and / or one or more flexible symbols; one or more second PRACH resources in one or more subband full duplex (SBFD) symbols; and a plurality of downlink subbands of the cell, corresponding to a plurality of SBFD symbols, wherein the plurality of downlink subbands comprises a first downlink subband and a second downlink subband. The method further comprises determining, for an initial access to the cell, whether the wireless device supports SBFD, based on whether the wireless device supports at least one of the plurality of downlink subbands of the cell and an uplink subband of the cell. The method further comprises transmitting, for the initial access to the cell, a preamble via a PRACH resource of the one or more second PRACH resources, based on determining that the wireless device supports SBFD. The method further comprises receiving, via a set of physical resource blocks (PRBs) within an initial downlink bandwidth part, a random access responseDocket No.: 25-1015PCT(RAR) corresponding to the preamble, wherein the set of PRBs overlaps with the first downlink subband and does not overlap with the second downlink subband.

[0348] In an example, a method comprises receiving, by a wireless device and for a cell, one or more messages indicating: one or more first random access channel (RACH) resources in one or more uplink symbols and / or one or more flexible symbols; and one or more second RACH resources in one or more subband full duplex (SBFD) symbols. The method further comprises transmitting, for an initial access to the cell, a preamble via a RACH resource of either the one or more first RACH resources or the one or more second RACH resources, based on whether the wireless device supports: at least one of a plurality of downlink subbands of the cell for SBFD; and an uplink subband of the cell for SBFD.

[0349] In an example, a method comprises receiving, by a wireless device and for a cell, one or more messages indicating: one or more random access channel (RACH) resources in one or more subband full duplex (SBFD) symbols; a plurality of downlink subbands of the cell for SBFD; and an initial downlink bandwidth part (BWP) overlapping with one or more first downlink subbands of the plurality of downlink subbands. The method further comprises transmitting, for an initial access to the cell, a preamble via a RACH resource of the one or more PRACH resources, based on: whether the wireless device supports at least one of the plurality of downlink subbands of the cell and an uplink subband of the cell; and a number of the one or more first downlink subbands. The method further comprises receiving, via an initial downlink bandwidth part, a response corresponding to the preamble.

[0350] In an example, a method comprises receiving, by a wireless device and for a cell, one or more messages indicating a plurality of downlink subbands of the cell for SBFD; and transmitting, for an initial access to the cell, a preamble via a random access channel (RACH) resource of either i) one or more first RACH resources in one or more uplink symbols and / or one or more flexible symbols or ii) one or more second RACH resources in one or more subband full duplex (SBFD) symbols, based on: whether the wireless device supports at least one of the plurality of downlink subbands of the cell for SBFD and an uplink subband of the cell for SBFD; and a number of one or more downlink subbands that are in the plurality of downlink subbands and that overlap with an initial downlink bandwidth part (BWP) of the cell.

[0351] In an example, a method comprises receiving, by a wireless device and for a cell, one or more first messages indicating: one or more first physical random access channel (PRACH) resources in one or more uplink symbols and / or one or more flexible symbols; and one or more second PRACH resources in one or more subband full duplex (SBFD) symbols. The method further comprises initiating a random access procedure by (or and) transmitting a preamble via a PRACH resource (RO) of the one or more first ROs. The method further comprises receiving one or more second messages indicating to apply one or more SBFD configuration parameters for the random access procedure; and based on receiving the one or more second messages, transmitting an uplink transmission, for the random access procedure, using the one orDocket No.: 25-1015PCTmore SBFD configuration parameters, wherein the uplink transmission overlaps with one or more SBFD symbols.

[0352] In an example, a method comprises transmitting, by a wireless device and for an initial access to a cell, a preamble via a random access channel (RACH) resource (e.g., BRACH resource) in one or more uplink symbols and / or one or more flexible symbols. The method further comprises receiving one or more messages indicating to apply one or more subband full duplex (SBFD) configuration parameters for the initial access to the cell; and based on receiving the one or more messages, transmitting an uplink transmission via a RACH resource, for the initial access, using the one or more SBFD configuration parameters, wherein the RACH resource used for the uplink transmission overlaps with one or more SBFD symbols.

[0353] In an example, a method comprises receiving, by a wireless device and for a cell, one or more messages indicating: a plurality of subband full duplex (SBFD) symbols; physical resource blocks (PRBs) of an uplink subband of the cell; and one or more first physical random access channel (BRACH) resources (ROs) overlapping with one or more SBFD symbols of the plurality of SBFD symbols. The method further comprises determining (e.g., selecting) one or more second ROs from the one or more first ROs, wherein the one or more second ROs are valid. The method further comprises determining (e.g., selecting) an earliest RO from among: the one or more second ROs based on (e.g., in response to) one or more conditions not being met; or one or more third ROs included in the one or more second ROs, based on the one or more conditions being met, wherein each of the one or more third ROs overlaps (e g., fully overlaps) with the PRBs of the uplink subband of the cell. The method further comprises transmitting a preamble via the selected RO.

[0354] In an example, a method comprises determining (e.g., selecting), by a wireless device, a random access channel (RACH) resource (RO) from either a first set of one or more ROs or a second set of one or more ROs, depending on whether one or more conditions are met, wherein: both the first and second sets of ROs overlap with SBFD symbols; the second set of ROs is included in the first set of ROs; and the second set of ROs overlaps with physical resource blocks (PRBs) of an uplink subband of the cell. The method further comprises transmitting a preamble via the determined RO.

[0355] In an example, a method comprises receiving, by a wireless device and for a cell, one or more messages indicating: one or more first physical random access channel (PRACH) resources in one or more uplink symbols and / or one or more flexible symbols; and one or more second PRACH resources in one or more subband full duplex (SBFD) symbols. The method further comprises initiating a first random access procedure by transmitting a preamble via a PRACH resource of the one or more first (or second) PRACH resources; receiving a random access response (RAR) comprising a backoff indicator, wherein the backoff indicator indicates to use a different PRACH resource for the initial access. The method further comprises,Docket No.: 25-1015PCTbased on i) receiving the RAR comprising the backoff indicator and ii) the first random access procedure not being completed: stopping the first random access procedure; and initiating a second random access procedure by transmitting a second preamble via a PRACH of the one or more second (or first) PRACH resources.

[0356] In an example, a method comprises transmitting, by a wireless device and for an initial access to a cell, a first preamble via one of: a first random access channel (RACH) resource in one or more uplink symbols and / or one or more flexible symbols; and a second RACH resource in one or more one or more subband full duplex (SBFD) symbol. The method further comprises receiving a response (e.g., an RAR) to the preamble, wherein the response comprises an indicator (e.g., a backoff indicator) indicating to use a different RACH resource for the initial access. The method further comprises, based on receiving the response comprising the indicator, transmitting, for the initial access, a second preamble via another one of the first RACH resource and the second RACH resource.

[0357] Embodiments of this disclosure allow an SBFD-aware UE to properly utilize resources in SBFD symbols for an initial access to a cell, thereby improving the UE’s efficiency in using available network resources for the initial access. More specifically, in an example, the embodiments of this disclosure allow mutual / aligned understanding, between the UE and the BS, regarding required UE functionalities for utilizing resources in SBFD symbols, for the initial access.

[0358] FIG. 19 shows a process 1900 performed by a UE 1910 and a BS 1920 for UE 1910’s initial access to a cell provided by BS 1920.

[0359] In an example, the “initial access” may mean a UE's access to a cell provided by a BS before the UE is transitioned from a radio resource control (RRC) idle state to an RRC connected state in which the UE is connected to the BS. In an example, the initial access may comprise or may be a random access (RA) performed by a UE after the UE selects, during a cell search, a suitable BS based on receiving signals broadcasted by BS(s). In an example, the initial access may be referred as any of an initial access procedure, a RRC connection procedure, an association procedure to the BS / cell, a random access procedure before a RRC connection, a random access procedure without configured with UE-dedicated configuration parameters, a RRC connection establishment procedure, etc. In an example, UE 1910 may establish a RRC connection to BS 1920 during / via the initial access. Note that, in this disclosure, the expression “element(s)’1means one or more elements. For example, “BS(s)” means one or more BSs.

[0360] Process 1900 may begin with step 1902. Step 1902 comprises, during a cell search for the initial access, UE 1910 receiving, from BS 1920, synchronization signal block (SSB) 1932 broadcasted by BS 1920. SSB 1932 may comprise primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH). The PBCH may carry master information block (MIB) which contains information that UE 1910 needs to acquire the remaining system information broadcastedDocket No.: 25-1015PCTby BS 1920. The remaining minimum system information (RMSI) may comprise system information block (SIB) 1 (SIB1 ). Although not shown in FIG 19, step 1904 may comprise UE 1910 receiving one or more additional SIB(s) such as SIB2, SIB3, etc. SIB1 1904 may be transmitted via one or more broadcast messages and / or one or more RRC messages.

[0361] After performing step 1902, in step 1904, UE 1910 may receive, from BS 1920, SIB1 1934 using the information contained in the MIB of SSB 1932. SIB1 1934 may include a random-access configuration which may provide information about time and frequency resources in which a preamble transmission for the initial access may take place. One example of such resource is a physical random access channel (BRACH) resource. Even though FIG. 19 shows that SIB1 1934 is transmitted by BS 1920, in an embodiment, SIB1 193419 may be transmitted by another BS (e.g., a source BS) for a hand-over to BS 1920 from the another BS. For example, SIB 1934 19may be for a secondary cell group, and may be transmitted by a master cell group BS (i.e., a BS in the master cell group). The master cell group BS may be same as or different from BS 1920. In an example, SIB1 1934 may be received via UE-dedicated RRC signaling transmitted by another BS e.g., for hand-over and / or a cell group addition.

[0362] After receiving SIB1 1934, process 1900 may proceed to step 1906, which may be a part of a 4-step random access procedure. In an example, the 4-step random access procedure may comprise one or more of steps 19061919-1914. In step 1906, UE 1910 may transmit, to BS 1920, a preamble / Msg1 1936 via the resource(s) (e.g., a BRACH) indicated by SIB1 1934. Note that, in this disclosure, the expression “A / B” means A and / or B. For example, "preamble / Msg1” means preamble and / or Msg1.

[0363] After receiving preamble 1936 transmitted by UE 1910, in step 1908, BS 1920 may transmit a response 1938 (e.g., a random access response (RAR) / Msg2) corresponding to the preamble. Response 1938 (e.g., RAR / Msg2) may contain an initial uplink grant and / or a time advance (TA) command for timing adjustment. Response 1938 may also include a random access preamble identifier that matches the identifier of preamble 1936. In addition to transmitting response 1938, based on receiving preamble 1936, BS 1920 may assign a temporary identifier (e.g., temporary cell radio network temporary identifier ("TC-RNTI”) to UE 1910. UE 1910 may monitor one or more downlink control information (DCI) scheduling the RAR, wherein the DCI is scrambled via a random access RNTI (RA-RNTI).

[0364] In case response 1938 includes an initial uplink grant, after receiving response 1938, in step 1912, UE 1910 may transmit, to BS 1920, uplink (UL) signal(s) 1942 (e.g., Msg3), for example, on physical uplink shared channel (BUSCH). UL signal(s) 1942 may comprise the TC-RNTI for a contention resolution. Then, after receiving UL signal(s) 1942, in step 1914, BS 1920 may transmit downlink (DL) signal(s) 1944 (e.g., Msg4) to UE 1910. DL signal(s) 1944 may contain medium access control (MAC) data which is for contention resolution. DL signal(s) 1944 may also contain the identifier (e.g., temporary cell-RNTI, TC-RNTI) of UE 1910, confirming that BS 1920 correctly identified UE 1910 and the contention has beenDocket No.: 25-1015PCTresolved. UE 1910 may set a C-RNTI based on the TC-RNTI based on receiving the DL signal(s) 1944 and / or based on the contention resolution has been completed. UE 1910 may use the C-RNTI for communicating with BS after step 1914.

[0365] In existing technologies, UE 1910 generally uses resources in UL symbol(s) or flexible symbol(s) (hereinafter, “UL / flexible symbol(s)”) for transmitting, for the initial access to the cell of BS 1920, preamble 1936 and UL signal(s) 1942. However, in case UE 1910 is an SBFD-aware UE, resources in SBFD symbol(s) may also be used for transmitting preamble 1936 and / or UL signal(s) 1942. Thus, there may be a scenario where an SBFD-aware UE may not utilize available network resources in SBFD symbols, leading to inefficiencies in the network resource usage, for the initial access. In order to solve this problem, according to the embodiments of this disclosure, processes 2000-2200 are provided for UE 1910's initial access to the cell provided by BS 1920.

[0366] FIG. 20 shows a process 2000 for UE 1910's initial access (e.g., for a random access or for a random access procedure) to the cell provided by BS 1920, according to an embodiment of this disclosure. Process 2000 may begin with step 2002. Step 2002 comprises UE 1910 receiving, from BS 1920 and for the cell, message(s) 2052 indicating random access channel (RACH) resource(s) 252a in UL / flexible symbol(s) and RACH resource(s) 252b in SBFD symbols. In an example, RACH resource(s) 252a may overlap with SBFD symbol(s). In another example, RACH resource(s) 252a may not overlap with SBFD symbol(s). In an example, RACH resource(s) 252b may overlap with UL symbol(s), but, in a different example, RACH resource(s) 252b may not overlap with UL symbol(s). In the example, RACH resource(s) 252a may belong to a legacy set of ROs (e.g., a first set of ROs, a set of RACH resources). RACH resource(s) 252b may belong to a SBFD set of ROs (e.g., a second set of ROs, an additional set of RACH resources).

[0367] In an example, message(s) 2052 (e.g., including SIB1 1934) may also indicate any one or more of: a plurality of DL subbands 252c of the cell, an UL subband 252d of the cell, an initial DL bandwidth part (BWP) 252e, an initial UL BWP 252f, and / or configuration parameter(s) 252g for determining PRBs used for receiving DL signal(s). Plurality of DL subbands 252c may be for SBFD, and may comprise at least a first DL subband and a second DL subband. More specifically, in an example, plurality of DL subbands 252c may consist of the first DL subband and the second DL subband. In an example, message(s) 2052 may indicate configuration parameter(s) 252g by including configuration parameter(s) 252g.

[0368] In an example, message(s) 2052 may indicate one or more SBFD configuration parameters indicating a plurality of SBFD symbols of the cell. In an example, message(s) 2052 may indicate one or more TDD UL / DL configuration parameters (e.g., tdd-UL-DL-ConfigCommon) indicating one or more downlink symbols and / or one or more flexible symbols and / or one or more uplink symbols of the cell.Docket No.: 25-1015PCT

[0369] Message(s) 2052 may be a single message providing all of the above indications (e.g , any one or more of 252a-252g). Alternatively, message(s) 2052 may be a plurality of messages, and any one or any combination of the plurality of messages may indicate any one of the above indications (e.g., any one or more of 252a-252g). In an example, message(s) 2052 may comprise any one or any combination of: SIB1 (e.g., SIB1 1934), SIBx, and / or one or more radio resource control (RRC) messages.

[0370] After receiving message(s) 2052, in an optional step 2004, UE 1910 may determine whether UE 1910 supports at least one of plurality of DL subbands 252c of the cell and uplink subband 252d of the cell. The RACH resource via which preamble 2056 is transmitted may be selected from either RACH resource(s) 252a in UL / flexible symbol(s) or RACH resource(s) 252b in SBFD symbol(s), based on the determination. How the RACH resource via which preamble 2056 is transmitted is selected from RACH resource(s) 252a or from RACH resource(s) 252b, based on the determination, is explained below in detail with respect to step 2006.

[0371] In step 2006, UE 1910 may transmit, for the initial access, a preamble 2056 (e.g., preamble / Msg1 1936) via a RACH resource of either RACH resource(s) 252a or RACH resource(s) 252b, based on whether UE 1910 supports, for SBFD, at least one of plurality of DL subbands 252c of the cell and uplink subband 252d of the cell. In an example, the transmission of preamble 2056 may correspond to an initiation of a random access procedure.

[0372] In an example, based on (e.g., in response to, if, only if, or when, etc.) that UE 1910 supports at least one of plurality of DL subbands 252c of the cell and uplink subband 252d of the cell, the RACH resource via which preamble 2056 is transmitted may be selected, for example, by UE 1910, from RACH resource(s) 252b in SBFD symbols. Note that, in this disclosure, any instance of “based on” may be replaced with “in response to," “if,” “only if,” or “when.”

[0373] On the contrary, based on UE 1910 not supporting at least one of plurality of DL subbands 252c of the cell (e.g., supporting only one DL subband where the cell is configured with more than one DL subband) or not supporting UL link subband 252d of the cell, the RACH resource via which preamble 2056 is transmitted may be selected, for example, by UE 1910, from RACH resource(s) 252a in uplink / flexible symbols.

[0374] UE 1910 may be considered as supporting at least one of plurality of DL subbands 252c of the cell based on UE 1910 being able to determine available / usable downlink physical resource blocks (PRBs) within at least one of plurality of DL subbands 252c and UE 1910 being able to receive, during SBFD symbol(s), DL signal(s) (e.g., data and / or control) via the available / usable downlink PRBs. Note that, in this disclosure, any instance of “available / usable downlink PRBs,” “available downlink PRBs,” or “usable downlink PRBs” may be referred as “a set of usable DL PRBs,” “usable DL PRBs,” “available DL PRBs,” “a set of available DL PRBs,” “a DL usable set of PRBs,” “a DL set of available PRBs," “DL usable PRBs," etc.Docket No.: 25-1015PCT

[0375] Similarly, UE 1910 may be considered as supporting UL subband 252d of the cell based on UE 1910 being able to determine available / usable uplink PRBs within UL subband 252d of the cell and UE 1910 being able to transmit, during SBFD symbol(s), UL signal(s) (e.g., data) via the available / usable uplink PRBs. Note that, in this disclosure, any instance of “available / usable uplink PRBs,” “available uplink PRBs," or “usable uplink PRBs” may be referred as “a set of usable UL PRBs,” “usable UL PRBs, available UL PRBs,” “a set of available UL PRBs,” “a UL usable set of PRBs,” “a UL set of available PRBs,” “UL usable PRBs, etc.”

[0376] In an example, message(s) 2052 may further a parameter of a RSRP threshold (e.g., SBFD-RSRP-ThresholdSSB). UE 1910 may measure one or more RSRPs of one or more SSBs of the cell. UE 1910 may determine a RSRP of the one or more RSRPs, wherein the RSRP is a highest value among the one or more RSRPs. UE 1910 may compare / determine whether the RSRP is larger than or equal to (or smaller than or equal to, or larger than, or smaller than) the RSRP threshold. The RACH resource(s) 2052b may be selected further based on the RSRP being larger than or equal to (or smaller than or equal to, or larger than, or smaller than) the RSRP.

[0377] In an example, message(s) 2052 may indicate that RACH resource(s) 2052a and RACH resource(s) 2052b are associated with a feature combination. The feature combination may indicate one or more of: ‘msg 1 -repetitions', ‘msg3-repetitions’, ‘smallData’, ‘redCap’, ‘eRedCap’, and 'nsag'. For example, ‘msg 1 -repetitions’ may indicate that UE1910 may transmit a plurality of repetitions of preamble 2056 via a plurality of RACH resources. 'msg3-repetitions' may indicate that UE1910 may transmit a plurality of repetitions of Msg3 PUSCH 1942 via a plurality of PUSCH transmissions. 'smallData' may indicate that the random access procedure is for a small data transmission. 'redCap' and’eRedCap' may indicate UE1910 supports a reduced capability. Message(s) 2052 may indicate one or more feature combinations, where each feature combination may indicate one or more sets of RACH resources and a unique combination of the features. For example, a first set of RACH resources of the one or more sets of RACH resources may comprise RACH resources 2052a (e.g., one or more RACH resources overlapping, in time, with u pl in k / flexible symbols). For example, a second set of RACH resources may comprise RACH resources 2052b (e.g., one or more RACH resources overlapping, in time, with SBFD symbols).

[0378] In an example, UE1910 may support ‘msg 1 -repetitions' and / or ‘msg3-repetitions’. In the example, Message(s) 2052 may indicate a first RSRP threshold indicating a RSRP threshold to determine a Msg1 repetition number as K1 (e.g., K1 = 2) for the RACH resource(s) 2052a (or the first set of RACH resources). Message(s) 2052 may indicate a second RSRP threshold indicating a RSRP threshold to determine a Msg1 repetition number as K1 (e.g., K1 = 2) for RACH resource(s) 2052b (or the second set of RACH resources). In an example, the second RSRP threshold may be larger than or equal to (or smaller than or equal to, smaller than, larger than) the first threshold. Message(s) 2052 may further indicate a third RSRPDocket No.: 25-1015PCTthreshold indicating a RSRP threshold to determine a Msg1 repetition number as K2 (e.g., K2 = 4) for RACH resource(s) 2052a (or the first set of RACH resources). Message(s) 2052 may indicate a fourth RSRP threshold indicating a RSRP threshold to determine a Msg1 repetition number as K2 (e.g., K2 =4) for RACH resource(s) 2052b (or the second set of RACH resources). In the example, the fourth RSRP threshold may be larger than or equal to (or smaller than or equal to, smaller than, larger than) the third threshold. The third RSRP threshold and the fourth RSRP threshold may be smaller than the first RSRP threshold and the second RSRP threshold. Message(s) 2052 may indicate a fifth RSRP threshold indicating a RSRP threshold to determine a Msg1 repetition number as K3 (e.g., K3 = 8) for the RACH resource(s) 2052a (or the first set of RACH resources). Message(s) 2052 may indicate a sixth RSRP threshold indicating a RSRP threshold to determine a Msg1 repetition number as K3 (e.g , K3 = 8) for the RACH resource(s) 2052b (or the second set of RACH resources). In the example, the fifth RSRP threshold may be larger than or equal to (or smaller than or equal to, smaller than, larger than) the sixth threshold. The fifth RSRP threshold and the sixth RSRP threshold may be smaller than the third RSRP threshold and the fourth RSRP threshold.

[0379] In an example, the selecting / determining of the RACH resource(s) 2052b may be further based on the RSRP of the SSB being larger than or equal to the RSRP threshold.

[0380] If the RSRP of the SSB being smaller than the RSRP threshold and UE 1910 supports 'msg1-repetitions’ , UE1910 may determine one or more repetitions numbers based on the RSRP and the first / second / third / fourth / fifth / sixth RSRP thresholds. For example, UE 1910 may determine a first list of repetition numbers based on the RSRP and the first / third / fifth RSRP thresholds. For example, UE1910 may determine a second list of repetition numbers based on the RSRP and the second / fourth / sixth RSRP thresholds. For example, if the RSRP is less than the fifth threshold, K3 is added to the first list of the repetition numbers. If the RSRP is less than the third threshold, K2 is added to the first list of repetition numbers. If the RSRP is less than the first threshold, K1 is added to the first list of repetition numbers. Similarly, if the RSRP is less than the sixth threshold, K3 is added, if RSRP is less than the fourth threshold, K2 is added, and if RSRP is less than the second threshold, K1 is added to the second set of repetition numbers. UE 1910 may determine a first number of the first set of repetition numbers where the first number is a largest number of the first set of repetition numbers. UE 1910 may determine a second number of the second set of repetition numbers where the second number is a largest number of the second set of repetition numbers.

[0381] In the example, the selecting / determining the RACH resource(s) 2052b may be further based on the second number being smaller than or equal to (or larger than or equal to, smaller than, larger than) the first number and the RSRP is smaller / lower than the RSRP threshold. UE 1910 may determine the secondDocket No.: 25-1015PCTnumber as a number of repetition for a preamble. UE 1910 may transmit the second number of repetitions for the preamble 2056.

[0382] In another example, the selecting / determining of RACH resource(s) 2052b may be further based on a first number (e.g., msg 1 -Repetition Num configured for a featurecombinationpreambles, of featureCombinationPreambleList, indicating the first set of RACH resources) of maximum repetitions of the first set of RACH resources comprising the RACH resource(s) 2052a and a second number (e.g., msg1-RepetitionNum configured for a featurecombinationpreambles, of featureCombinationPreambleList, indicating the second set of RACH resources) of maximum repetitions of the second set of RACH resources comprising the RACH resource(s) 2052b. For example, message(s) 2052 may indicate the first number for the first set of RACH resources. Message(s) 2052 may indicate the second number for the second set of RACH resources. For example, UE 1910 may determine the first set of RACH resources, or the second set of RACH resources based on comparison of the first number and the second number. For example, UE 1910 may determine the second set of RACH resources based on the second number being larger than or equal to (or smaller than or equal to, larger than, smaller than) the first number. The selecting / determining of RACH resource(s) 2052b may be based on determining the second set of RACH resources. Based on the determining the second set of RACH resources, UE1910 may determine a set of repetition numbers based on the RSRP of the SSB, and the second / third / sixth RSRP thresholds. For example, if the RSRP is less than the sixth threshold, K3 is added, if RSRP is less than the fourth threshold, K2 is added, and if RSRP is less than the second threshold, K1 is added to the set of repetition numbers. UE1910 may determine a repetition number as a largest number of the set of repetition numbers. UE 1910 may use the repetition number for transmitting the preamble 2056.

[0383] In yet another example, the selecting / determining of the RACH resource(s) 2052b may be further based on whether the RSRP of the SSB being larger than or equal to the RSRP threshold. In the example, the selecting / determining of the RACH resource(s) 2052b is further response to the RSRP of the SSB being larger than or equal to the RSRP threshold. In this case, the RACH resource(s) 2052b may not be associated with a feature and / or a feature combination and / or a feature combination preambles (e.g., featurecombinationpreambles). When the RSRP of the SSB being smaller than the RSRP threshold, UE 1910 may determine a set of RACH resources, of one or more sets of RACH resources configured to an active uplink BWP of the cell, where the set of RACH resources is configured with a largest number of repetitions for a msg1 (e.g., msg1-RepetitionNum associated with the set of RACH resources is a largest among one or more msg 1 -Repetition Nums associated with the one or more sets of RACH resources). The selecting / determining the RACH resource(s) 2052b may be further based on the set of RACH resources comprising the RACH resource(s) 2052b. Otherwise, UE 1910 may select / determine the RACH resource(s) 2052a.Docket No.: 25-1015PCT

[0384] In the specification, UE 1910 selects the RACH resource(s) 2052b may be referred as a random access procedure, based on the 2056, with a RACH symbol type of ‘SBFD’, ‘Type 1-B’, ‘Type 1-C, ‘Type B’, ‘Type C or the random access procedure is based on a SBFD set of ROs. In the specification, UE 1910 selects the RACH resource(s) 2052a may be referred as a random access procedure, based on the 2056, with a RACH symbol type of ‘legacy, ‘Type T, ‘Type 2', ‘Type A’ or the random access procedure is based on a legacy set of ROs.

[0385] UE 1910 may determine a RACH symbol type of the random access procedure for the preamble 2056. Based on the RACH symbol type, UE 1910 may determine a number of repetitions for the preamble 2056 based on either the first / third / fifth RSRP thresholds or the second / fourth / sixth RSRP thresholds. Based on the selecting / determining the RACH resource(s) 2052a (i.e., the RACH symbol type is 'legacy'), UE 1910 may determine the number of repetitions based on the first / third / fifth RSRP thresholds as described in above. Based on the selecting / determining the RACH resource(s) 2052b (i.e., the RACH symbol type is ‘SBFD), UE 1910 may determine the number of repetitions based on the second / fourth / sixth RSRP thresholds as described in above.

[0386] Based on / in response to determining / selecting RACH resource(s) 2052a, UE 1910 may perform a procedure illustrated in FIG. 1 without applying one or more SBFD configuration parameters (e.g., plurality of DL subbands 252c for SBFD, UL subband 252d for SBFD, the plurality of SBFD symbols of the cell). UE 1910 may communicate with BS 1920 not based on plurality of DL subbands 252c and / or UL subband 252d and / or the plurality of SBFD symbols of the cell based on / in response to determining / selecting the RACH resource(s) 252a. For example, UE 1910 may receive RAR / Msg2 1938 at the step 1908 (and / or Msg4 PDSCH at the step 1914) via the initial downlink BWP 2052e, where resources of RAR / Msg2 1938 (and / or Msg4 PDSCH at the step 1914) may overlap, in frequency, with PRB(s) outside of the first and second DL subbands (e.g., PRB(s) not belonging to any DL subband of the cell) and overlap, in time, with downlink and / or flexible symbols. The resources of RAR / Msg2 1938 (and / or Msg4 PDSCH at the step 1914) may (or may not) overlap, in time, with one or more SBFD symbols of the plurality of SBFD symbols. For example, UE 1910 may determine the cell does not comprise a SBFD symbol during the initial access procedure. For example, UE 1910 may not enable the one or more SBFD configuration parameters in communicating with BS 1920.

[0387] On the other hand, UE 1910 may communicate with BS 1920 based on (applying) plurality of DL subbands 252c and / or UL subband 252d and / or the plurality of SBFD symbols of the cell based on / in response to determining / selecting the RACH resource(s) 252b. UE 1910 may determine DL usable PRBs based on plurality of DL subbands 252c and / or UL usable PRBs based on UL subband 252d during plurality of SBFD symbols. UE 1910 may communicate with BS 1920 via initial downlink BWP 2052e and initial uplink BWP 2052f, without determining the DL usable PRBs and / or UL usable PRBs, during one orDocket No.: 25-1015PCTmore non-SBFD symbols The DL usable PRBs may refer a set of downlink PRBs overlapping, in frequency, with both a DL subband (e.g., one of plurality of DL subbands 252c) and an active downlink BWP (e.g., initial downlink BWP 2052e). The UL usable PRBs may refer a set of uplink PRBs overlapping, in frequency, with UL subband 2052d and an active uplink BWP (e.g., initial uplink BWP 2052f) . For example, UE 1910 may receive RAR / Msg2 1938 at the step 1908 (and / or Msg4 PDSCH at the step 1914) via the DL usable PRBs, where resources of RAR / Msg2 1938 (and / or Msg4 PDSCH at the step 1914) may overlap, in frequency, with the plurality of DL subbands 252c; and overlap, in time, with SBFD symbols. The resources of RAR / Msg2 1938 (and / or Msg4 PDSCH at the step 1914) may not overlap, in time, with non-SBFD symbols. For example, resources of Msg 3 PUSCH at the step 1942 and / or resources of a PUCCH transmission corresponding to Msg4 PDSCH may overlap, in time, with the plurality of SBFD symbols and may not overlap, in time, with non-SBFD symbols. BS 1920 may transmit one or more messages for the random access procedure based on the RACH resource(s) 252b such that resources of the one or more messages overlap, in time, with the plurality of SBFD symbols and do not overlap, in time, with non-SBFD symbols. BS 1920 may indicate a first behavior or a second behavior via RRC / SIB signaling to UE 1910. For example, BS 1920 schedules / transmits the one or more messages overlapping, in time, with the plurality of SBFD symbols based on the first behavior. BS 1920 schedules / transmits the one or more messages overlapping, in time, with the plurality of SBFD symbols and / or downlink symbols and / or flexible symbols based on the second behavior. The first behavior or the second behavior may be applied for the random access procedure based on RACH resource(s) 252b.

[0388] Referring back to FIG. 20, after step 2006 is performed, process 2000 may proceed to step 2008. In step 2008, UE 1910 may receive, for / after / during the initial access to the cell of BS 1920, DL signal(s) 2058 (e.g., Msg2 / RAR such as Msg2 / RAR 1938, Msg4 such as Msg4 1942, MsgB, etc.) corresponding to preamble 2056 that is transmitted to BS 1920. In an example, UE 1910 may receive DL signal(s) 2058 via a set of physical resource blocks (PRBs) within initial DL bandwidth part (BWP) 252e.

[0389] The set of PRBs (hereinafter, “the set of DL PRBs”) via which UE 1910 receives DL signal(s) 2058 may be determined / configured / selected in various ways. In an example, the set of DL PRBs may include a PRB that is outside of the first DL subband and / or outside of the second DL subband (e.g., when UE 1910 does not support SBFD, when UE 1910 selects the RACH resource(s) 252a, and / or when reception of DL signal(s) 2058 does not overlap in SBFD symbol(s)). In another example, the set of DL PRBs may overlap with only one of the first and second DL subband (e.g., when UE 1910 supports one DL subband of the first and second DL subband, when UE supports SBFD, when UE1910 selected the RACH resource(s) 252b, when reception of DL signal(s) 2058 overlaps in SBFD symbol(s) in time domain). In the example, the set of DL PRBs may refer the aval lable / usable downlink PRBs of the one of the first and second DL subband. In a different example, the set of DL PRBs may overlap with both the first and second DL subbands (e.g.,Docket No.: 25-1015PCTwhen UE 1910 supports the first and second DL subband, when UE supports SBFD, when UE1910 selected the RACH resource(s) 252b, when reception of DL signal(s) 2058 overlaps in SBFD symbol(s))). In the example, the set of DL PRBs may refer the aval lable / usable downlink PRBs of both the first and the second DL subbands.

[0390] After step 2008 is performed, process 2000 may proceed to step 2010. In step 2010, UE 1910 may transmit UL signal(s) 2060 (e.g., Msg3 / Msg3 PUSCH 1940, MsgA PUSCH, PUSCH, PUCCH, etc.) via a set of PRBs within initial UL BWP 252f (hereinafter, “the set of UL PRBs”). In an example, the set of UL PRBs may comprise a PRB that is outside of UL subband 252d (e.g., when UE 1910 does not support SBFD, when UE 1910 selects the RACH resource(s) 252a, when transmission of UL signal(s) 2060 does not overlap in SBFD symbol(s)). In a different example, the set of UL PRBs may overlap with UL subband 252d (e.g., when UE1910 support SBFD, when UE1910 selected the RACH resource(s) 252b, when transmission of UL signal(s) 2060 overlaps in SBFD symbol(s) in time domain).

[0391] Referring back to step 2004, in an example, optional step 2004 may be a sub-step of determining whether UE 1910 supports SBFD. More specifically, in an example, UE 1910 may determine whether UE 1910 supports SBFD or not based on whether UE 1910 supports at least one of plurality of DL subbands 252c of the cell and UL subband 252d of the cell. In an example, UE 1910 may determine that UE 1910 supports SBFD based on UE 1910 supporting at least one of plurality of DL subbands 252c of the cell and UL subband 252d of the cell while UE 1910 may determine that UE 1910 does not support SBFD based on UE 1910 not supporting at least one of plurality of DL subbands 252c of the cell or UL subband 252d of the cell.

[0392] UE 1910 may support at least one of plurality of DL subbands 252c of the cell based on UE 1910 supporting the first DL subband or the second DL subband of plurality of DL subbands 252c or based on UE 1910 supporting both the first DL subband and the second DL subband. UE1910 may receive a DCI scheduling a PDSCH via a first set of PRBs. Based on supporting a DL subband of the cell, the first set of PRBs may overlap, in frequency domain, with the DL subband and the first set of PRBs does not overlap, in frequency domain with another DL subband of the cell. UE 1910 receives the PDSCH via a second set of PRBs that is determined based on the available / usable downlink PRBs within the DL subband and the first set of PRBs. Based on supporting the first and the second DL subbands of the cell, the first set of PRBs may overlap, in frequency domain, with the first DL subband and the second DL subband. UE 1910 may receive the PDSCH via a third set of PRBs that is determined based on the available / usable downlink PRBs within the first DL subband and the second DL subband, and the first set of PRBs.

[0393] In this example, the RACH resource for transmitting preamble 2056 may be selected from among RACH resource(s) 252a and RACH resource(s) 252b, based on whether UE 1910 supports SBFD For instance, if UE 1910 supports SBFD, the RACH resource may be selected from RACH resource(s) 252bDocket No.: 25-1015PCTwhile, if LIE 1910 does not support SBFD, the RACH resource may be selected from RACH resource(s) 252a. In the example, RACH resource(s) 252a and RACH resource(s) 252b may be indicated / configured via a configuration parameter IE (RACH-ConfigCommon IE). More specifically, a rach-ConfigCommon (via RACH-ConfigCommon IE) of the cell may indicate RACH resource(s) 252a and RACH resource(s) 252b. UE 1910 may determine RACH resource(s) 252a and RACH resource(s) 252b based on a prach-Configurationlndex of the rach-ConfigCommon. In the example, RACH resource(s) 252a and RACH resource(s) 252b may be associated with a feature combination. The feature combination may comprise one or more of { The feature combination indicates one or more of {‘msg 1 -repetitions’ (msg 1 / preamble repetition), ‘msg3-repetitions’ (msg3 RUSCH repetition), ‘smallData’ (small data transmission), ‘redcap’ (reduced capability), ‘eRedCap’ (enhanced reduced capability), 'nsag'}. A set of RACH resources may comprise RACH resource(s) 252a, wherein the set of RACH resources may be utilized / shared / determined for a plurality of UEs served via the cell, regardless of whether the plurality of UEs support SBFD (operation) or not. A additional set of RACH resources may comprise RACH resource(s) 252b, wherein the additional set of RACH resources may be utilized / shared / determined for one or more UEs that receives the message(s) 252. The rach-ConfigCommon may indicate the set of RACH resources and the additional set of RACH resources.

[0394] In the above-described examples, the RACH resource via which preamble 2056 is transmitted is selected from RACH resource(s) 252a or RACH resource(s) 252b, depending on whether the following condition is satisfied - UE 1910 supports at least one of plurality of DL subbands 252c and UL subband 252d. However, in a different example, a different condition may be used instead of or in addition to the above condition.

[0395] More specifically, there may be a scenario where initial DL BWP 252e overlaps the first DL subband but does not overlap the second DL subband. In this scenario, if UE 1910 supports only the second DL subband but not the first DL subband, UE 1910 may be considered as not supporting SBFD (i.e., not considered as an SBFD-aware UE), and, as a result, the RACH resource via which preamble 2056 is transmitted may be selected from RACH resource(s) 252a. On the contrary, if UE 1910 supports only the first DL subband but not the second DL subband, UE 1910 may be considered as supporting SBFD (i.e., considered as an SBFD-aware UE), and, as a result, the RACH resource via which preamble 2056 is transmitted may be selected from RACH resource(s) 252b. In this example, whether UE 1910 supports SBFD or not (and / or whether the RACH resource via which preamble 2056 is transmitted is selected from RACH resource(s) 252a or RACH resource(s) 252b) may be determined not only based on whether UE 1910 supports at least one DL subband and an uplink subband, but also based whether UE 1910 supports the DL subband that overlaps with initial DL BWP 252e.Docket No.: 25-1015PCT

[0396] Alternatively, there may be a scenario where initial DL BWP 252e overlaps with both the first and second DL subbands. In this example, contrary to the example in the above paragraph, no additional condition may be required. More specifically, for instance, if plurality of DL subbands 252c consists of the first and second DL subbands, and if UE 1910 supports at least one of the first and second DL subbands, it means that UE 1910 supports at least one DL subband overlapping initial DL BWP 252e. Thus, the condition of UE 1910 supporting at least one DL subband and uplink subband 252d may be sufficient to determine that UE 1910 supports SBFD.

[0397] Referring back to step 2008, the set of PRBs via which DL signal(s) 2058 are received by UE 1910 (a.k.a., “the set of DL PRBs” or “the DL PRB set”) may be determined based on configuration parameter(s) 252g that UE 1910 receives from BS 1920 Initial DL BWP 252e may overlap with the first and second DL subbands.

[0398] In an example, the DL PRB set may be determined based on selecting one of the first and second DL subbands. For simple explanation purpose, let’s assume that the first DL subband is selected. There are different ways for UE 1910 to select the first DL subband for determining the DL PRB set. In one example, configuration parameter(s) 252g may indicate to UE 1910, either implicitly or explicitly, the first DL subband, and UE 1910, based on receiving configuration parameter(s) 252g, may select the first DL subband and determine the DL PRB set such that the DL PRB set overlaps, in frequency, with the first DL subband (but not overlaps, in frequency, with the second DL subband). In the specification, the DL PRB set overlaps with the initial downlink BWP 252e in frequency domain.

[0399] In an example, configuration parameter(s) 252g may include an index of the first DL subband. In this example, based on finding the index of the first DL subband in configuration parameter(s) 252g, UE 1910 may select the first DL subband and determine the DL PRB set such that the DL PRB set overlaps the first DL subband (but not the second DL subband).

[0400] In another example, configuration parameter(s) 252g may include a starting PRB index (and / or a frequency location, a starting PRB offset, a PRB offset, an offset, ARFCN, a starting common PRB (CRB) index / offset, etc.) of the first DL subband and a starting PRB index (and / or a frequency location, ARFCN, etc.) of the second DL subband. In this example, UE 1910 may select the first DL subband from among the first and second DL subbands, based on one or more of: the starting PRB index (and / or a frequency location, ARFCN, etc.) of the first DL subband, the starting PRB index (and / or a frequency location, ARFCN, etc.) of the second DL subband, a number of PRBs in the first DL subband, and a number of PRBs in the second DL subband.

[0401] More specifically, in an example, a lower / smaller index may be assigned / given (e.g., by UE 1910 and / or BS 1920) to the first DL subband based on the starting PRB index of the first DL subband being less / smaller / lower than the starting PRB index of the second DL subband, while a higher / greater / largerDocket No.: 25-1015PCTindex may be assigned / given (e.g , by UE 1910 and / or BS 1920) to the second DL subband based on the starting PRB index of the second DL subband being greater / higher / larger than the starting PRB index of the first DL subband. In this example, based on the index of the first DL subband being lower / less / smaller than the index of the second DL subband, UE 1910 may select the first DL subband and determine the DL PRB set such that the DL PRB set overlaps the first DL subband (but not the second DL subband).

[0402] In another example, a higher / greater / larger index may be assigned / given (e.g., by UE 1910 and / or BS 1920) to the first DL subband based on the starting PRB index of the first DL subband being greater / higher / larger than the starting PRB index of the second DL subband, while a lower / less / smaller index may be assigned / given (e.g., by UE 1910 and / or BS 1920) to the second DL subband based on the starting PRB index of the second DL subband being lower / less / smaller than the starting PRB index of the first DL subband. In this example, based on the index of the first DL subband being higher / greater / larger than the index of the second DL subband, UE 1910 may select the first DL subband and determine the DL PRB set such that the DL PRB set overlaps the first DL subband (but not the second DL subband).

[0403] In a different example, a lower / smaller index may be assigned / given (e.g., by UE 1910 and / or BS 1920) to the first DL subband based on a number of PRBs in the first DL subband is higher / greater / more than or equal to a number of PRBs in the second DL subband, while a higher / greater / larger index may be assigned / given (e.g., by UE 1910 and / or BS 1920) to the second DL subband based on a number of PRBs in the second DL subband is lower / less / smaller than a number of PRBs in the first DL subband. In this example, based on the index of the first DL subband being lower / less / smaller than the index of the second DL subband, UE 1910 may select the first DL subband and determine the DL PRB set such that the DL PRB set overlaps the first DL subband (but not the second DL subband).

[0404] In a different example, a higher / greater index may be assigned / given (e.g., by UE 1910 and / or BS 1920) to the first DL subband based on a number of PRBs in the first DL subband being higher / greater / more than or equal to a number of PRBs in the second DL subband, while a lower / smaller index may be assigned / given (e.g., by UE 1910 and / or BS 1920) to the second DL subband based on a number of PRBs in the second DL subband is lower / less / smaller than a number of PRBs in the first DL subband. In this example, based on the index of the first DL subband being higher / greater / larger than the index of the second DL subband, UE 1910 may select the first DL subband and determine the DL PRB set such that the DL PRB set overlaps the first DL subband (but not the second DL subband).

[0405] In a different example, only when on a number of PRBs in the first DL subband and the number of PRBs in the second DL subband are the same, the index of the first DL subband and / or the index of the second DL subband may be determined based on the starting PRB index of the first DL subband and the starting PRB index of second DL subband, as described in the above-described methods of selecting the first DL subband based on the starting PRB indexes of the first and second DL subbands. For example,Docket No.: 25-1015PCTwhen both DL subbands have a same number of PRBs, a lower (or higher) index may be given to a DL subband with lower starting PRB index.

[0406] In an example, UE 1910 may determine first DL usable PRBs of the first DL subband, where each PRB of the first DL usable PRBs overlaps both with the first DL subband and initial DL BWP 252e (or an active BWP) of the cell in frequency domain. UE 1910 may determine second DL usable PRBs of the second DL subband, where each PRB of the second DL usable PRBs overlaps with the second DL subband initial DL BWP 252e (or the active BWP) of the cell in frequency domain. UE 1910 may determine the first DL subband based on / in response to a first number of the first DL usable PRBs being larger / greater / more than or equal to a second number of the second DL usable PRBs. UE 1910 may determine the second DL subband based on / in response to the second number of the second DL usable PRBs being larger / great / more than the first number of the first DL usable PRBs. In the example, the first DL subband is configured with a smaller starting PRB index compared to the second DL subband.

[0407] As explained above, in an example, the first DL subband may be selected (e.g., by UE 1910 and / or BS 1920), for determining the DL PRB set, from among the first and second DL subbands based on configuration parameter(s) 252g indicating the first DL subband. However, in another example, UE 1910 may not receive configuration parameter(s) 252g from BS 1920. In such example, UE 1910 may select the first DL subband for determining the DL PRB set, based on determining an absence of configuration parameter(s) 252g (e.g., failing to receive configuration parameter(s) 252g). Then, in selecting the first DL subband from among the first and second DL subbands, the above-described methods of selecting the first DL subband based on the starting PRB indexes of the first and second DL subbands and / or the number of PRBs in each of the first and second DL subband may be applied.

[0408] After determining / selecting / configuring the DL PRB set such that the DL PRB set overlaps, in frequency, with the first DL subband and the initial downlink BWP 252e, but does not overlap, in frequency, with the second DL subband, during one or more SBFD symbols of the cell, UE 1910 may monitor resource(s) (e.g., physical downlink control channel (PDCCH) resources / candidates) overlapping with the first DL subband but skip monitoring resource(s) (e.g., PDCCH resources / candidates) overlapping with the second DL subband and / or not overlapping with the DL PRB set (e.g., outside of the DL PRB set). During one or more SBFD symbols of the cell UE 1910 may receive DL signal(s) 2058 via the DL PRB set. In an example, UE 1910 may receive a DCI scheduling a PDSCH resource via a first set of PRBs during one or more SBFD symbols. The first set of PRBs may comprise a PRB that is outside of the DL PRB set (or outside of the DL PRB set or that is not overlapping, in frequency, with the DL PRB set). The wireless device may determine a second set of PRBs, where each of the second set of PRBs belongs to both the DL PRB set and first set of PRBs. The wireless device may receive a PDSCH via the PDSCH resource based on / within the second set of PRBs during the one or more SBFD symbols.Docket No.: 25-1015PCT

[0409] As mentioned above, in an example, DL signal(s) 2058 may be an RAR corresponding to preamble 2056. In such example, before receiving DL signal(s) 2058, UE 1910 may receive a DCI scheduling PDSCH, and after receiving the DCI, UE 1910 may receive the PDSCH comprising the RAR.

[0410] In an example, the DCI may indicate a transport block (TB) scaling factor (e.g., within a TB scaling field in DCI format 1_0) for the RAR. The TB scaling factor may be one of {'00', ‘01 ‘10’} based on resources of the PDSCH overlapping with non-SBFD symbols in a time domain. Alternatively, the TB scaling factor may be one of {'00', ‘0T, ‘10’, ‘11’} based on resources of the PDSCH overlapping with SBFD symbols in a time domain. Here, ‘00’ may indicate that a scaling factor S is 1, ‘01’ may indicate that the scaling factor S is 0.5, ‘10’ may indicate that the scaling factor S is 0.25, and ‘1 T may indicate that the scaling factor S is smaller than ‘0.25’.

[0411] In an example, the DCI indicates a transport block (TB) scaling factor (e.g., within a TB scaling field in DCI format 1_0) for the RAR. The TB scaling factor may be one of {’00', ‘01’, ‘10’} based on the RAR corresponding to RACH resource(s) #252a (e.g., legacy RO, a legacy RACH resource, a RACH resource of the first set of RACH resources). Alternatively, the TB scaling factor may be one of {‘00’, ‘0T, ‘10’, ‘11’} based on the RAR corresponding to RACH resource(s) #252b (e.g., SBFD RO, a SBFD RACH resource, a RACH resource of the second set of RACH resources).

[0412] In an example, the TB scaling factor may be one of {'00’, ‘01’, ‘10’, ‘11’} based on the RAR corresponding to RACH resource(s) #252b (SBFD RO) and resources of the PDSCH overlapping with SBFD symbols in a time domain, and the TB scaling factor may be one of {‘00’, ‘01’, ‘10’} in other cases (either select RACH resource(s) #252a or receive RAR during non-SBFD symbol).

[0413] The DCI may indicate a transport block (TB) scaling factor (e.g., within a TB scaling field in DCI format 1_0) for the RAR, the TB scaling factor may be one of {’00’, ‘01’, ‘10’}; and a scaling factor S may be determined based on whether resources of the PDSCH overlaps with SBFD symbols in a time domain.

[0414] In an example, based on the resources of the PDSCH not overlapping with the SBFD symbols, the scaling factor S is determined from one of {1 , 0.5, 0.25}, and / or based on the resources of the PDSCH overlapping with the SBFD symbols, the scaling factor S is determined from one of {1 , 0.5, 0.25, X} where X is not any of {1, 0.5, 0.25}.

[0415] In an example, the DCI indicates a transport block (TB) scaling factor (e.g., within a TB scaling field in DCI format 1_0) for the RAR, the TB scaling factor may be one of {'00', ‘01 ’, '10'}, and

[0416] a scaling factor S may be determined based on whether the RAR corresponds to RACH resource(s) #252b or RACH resource(s) #252a.

[0417] In an example, based on the RAR corresponding to RACH resource(s) #252a, the scaling factor S is determined from one of {1 , 0.5, 0.25}, and / or based on the RAR corresponding to RACH resource(s) #252b, the scaling factor S is determined from one of {1 , 0.5, 0.25, X} where X is not 1 , 0.5, 0.25.Docket No.: 25-1015PCT

[0418] In an example, the scaling factor S may be one of {1 , 0.5, 0.25, X}, where X is not any of {1 , 0.5, 0.25}, based on the RAR corresponding to RACH resource(s) #252b (SBFD RO) and resources of the PDSCH overlapping with SBFD symbols in a time domain; and / or the scaling factor S may be one of {1, 0.5, 0.25} in other cases (either select RACH resource(s) #252a or receive RAR during non-SBFD symbol).

[0419] In an example, the method may comprise determining a TB size (TBS) of the RAR based on the DCI and the scaling factor S, wherein the TBS of the RAR is derived as a first number of information (Ninfo), determined based on a number of resource elements (NRE) of the PDSCH, and / or scaled by the scaling factor S (e.g., Ninfo_new = Ninfo * S), Qmis a modulation order, and R is a target code rate, wherein Qmand R are determined based on i) an MCS index field indicated by an uplink grant and ii) a MCS table (e.g., by looking up values corresponding to a field within the MCS table, indicated by an index value of the MCS index field).

[0420] Ninf0= f S,NRE,R, Qm)

[0421] As explained above, in step 2004, UE 1910 may determine whether UE 1910 supports SBFD depending on whether UE 1910 supports at least one of plurality of DL subbands 252c and uplink subband 252d. Similarly, in step 2006, UE 1910 may determine whether to select the RACH resource for transmitting preamble 2056 from RACH resource(s) 252a or RACH resource(s) 252b, depending on whether UE 1910 supports at least one of plurality of DL subbands 252c and uplink subband 252d .

[0422] However, in an example, there may be an additional condition for determining whether UE 1910 supports SBFD or whether to select the RACH resource for transmitting preamble 2056 from RACH resource(s) 252a or sRACH resource(s) 252b. One example of such additional condition is a number of DL subbands, among plurality of DL subbands 252c, that overlap initial DL BWP 252e.

[0423] In an example, when initial DL BWP 252e overlaps with the first and second DL subbands, but UE 1910 supports only one (e.g., the first DL subband) of the first and second DL subbands and uplink subband 252d, in step 2006, UE 1910 may select the RACH resource for transmitting preamble 2056 from RACH resource(s) 252a. On the contrary, when initial DL BWP 252e overlaps with the first and second DL subbands, and UE 1910 supports both of the first and second DL subbands and uplink subband 252d, in step 2006, UE 1910 may select the RACH resource for transmitting preamble 2056 from RACH resource(s) 252b. For example, when initial DL BWP 252e overlaps with the first and second DL subbands, and UE 1910 supports both of the first and second DL subbands and uplink subband 252d, in step 2006, UE 1910 may be allowed to select the RACH resource(s) 252b or may be allowed to transmit preamble 2056 via the RACH resource(s) 252b.

[0424] In an example, when initial DL BWP 252e overlaps with the first and second DL subbands, but UE 1910 supports only one (e.g., the first DL subband) of the first and second DL subbands and uplink subband 252d, in step 2004, UE 1910 may determine that UE 1910 does not support SBFD, for / during theDocket No.: 25-1015PCTinitial access. On the contrary, in this example, when initial DL BWP 252e overlaps with the first and second DL subbands, and UE 1910 supports both of the first and second DL subbands and uplink subband 252d, in step 2004, UE 1910 may determine that UE 1910 supports SBFD, for / during the initial acess.

[0425] In an example, one or more non-initial DL BWPs of the cell may be configured to UE 1910 by BS 1920 (e.g., via RRC signaling, downlink messages, MAC CEs and / or DCIs) such that each of the one or more non-initial DL BWPs overlaps, in frequency, with 1) both the first and second DL subbands; or 2) one of the first DL subband and the second DL subband (for discussion, the first DL subband may be assumed as the one).

[0426] In case a BWP of the one or more non-initial DL BWPs overlaps, in frequency, with both the first and second DL subbands, after receiving, from BS 1920, an indication indicating the BWP, UE 1910 may select one of the first and second DL subbands for receiving DL signal(s) (e.g., for a non-initial access). In the example, UE 1910 may support one DL subband that is one of the first and second DL subbands. UE1910 may select the one of the first and second DL subbands based on UE1910 supporting one DL subband and not supporting two DL subbands within the BWP.

[0427] In an example, in case a control resource set (coreset) of the cell of BS 1920 is configured with and / or overlaps, in frequency, with the first DL subband, UE 1910 may select the first DL subband for receiving DL signal(s) (e.g., for a non-initial access). On the contrary, in case the coreset of the cell of BS 1920 is configured with and / or overlaps the second DL subband, UE 1910 may select the second DL subband for receiving DL signal(s) (e.g., for a non-initial access). In this example, the coreset of the cell of BS 1920 may overlap only one of the first and second DL subbands. BS 1920 may configure the coreset of the cell, to UE 1910, based on a capability of UE 1910 such that the coreset of the cell of BS 1920 overlaps, in frequency, with only one of the first and second DL subbands.

[0428] Alternatively, BS 1920 may configure the BWP of the one or more non-initial DL BWPs based on a capability of UE 1910. When UE 1910 supports more than one DL subband, BS 1920 may configure a BWP overlapping, in frequency, with both the first and second DL subbands. When UE 1910 supports one DL subband, BS1920 may configure a BWP overlapping, in frequency, with one of the first and second DL subbands. BS 1920 may configure a BWP to UE 1910 such that the BWP (downlink BWP) overlaps, in frequency, with a number of DL subbands, where the number of DL subbands is determined based on the capability of UE 1910.

[0429] In another example, a downlink BWP of the cell, to UE 1910, is configured such that the BWP overlaps, in frequency, with both the first and second DL subbands where UE 1910 supports one of the first and second DL subbands, UE 1910 may 1) skip monitoring one or more PDCCH candidates, where each of the one or more PDCCH candidates overlap in time with one or more SBFD symbols of the cell and overlap in frequency with both the first and second DL subbands; 2) skip receiving / dropping / not receiving aDocket No.: 25-1015PCTPDSCH, where resources of the PDSCH overlaps with one or more second SBFD symbols of the cell and both the first and second DL subbands in time / frequency domain; 3) skip receiving / dropping / not receiving downlink signal(s) such as CSI-RS, PRS, SSB, DM-RS, PT-RS, etc., where resources of the downlink signal(s) overlaps with one or more second SBFD symbols of the cell and both the first and second DL subbands in time / frequency domain. In the example, a PDCCH candidate of the one or more PDCCH candidates may belong to a common search space (CSS) of the cell. For example, the common search space may be one or more of: a typeO-PDCCH CSS, typeOA-PDCCH CSS, typel-PDCCH CSS, typelA-PDCCH CSS, type2-PDCCH CSS, a CSS for receiving a SIB1 , a CSS for receiving SIBx, a CSS for receiving a RAR, a CSS for receiving paging, a CSS for receiving Msg B. The CSS may be associated with a coreset #0 (e.g., the initial downlink BWP 252e, a coreset with index = 0).

[0430] In an example, when the coreset (“first coreset”) of the cell of BS 1920 overlaps with the first DL subband, UE 1910 may receive configuration parameter(s) indicating an additional coreset overlapping the second DL subband (but not the first DL subband). In a different example, when the coreset (“first coreset") of the cell of BS 1920 overlaps with the second DL subband, UE 1910 may receive configuration parameter(s) indicating an additional coreset overlapping the first DL subband (but not the second DL subband). In these examples, UE 1910 may select one of the first and second DL subbands for receiving DL signal(s) (e.g., for a non-initial access) during a time slot, based on search space(s) being configured for monitoring during the time slot. For instance, UE 1910 may select the first DL subband based on the search space(s) being associated with the first coreset overlapping the first DL subband and the second DL subband based on the search space(s) being associated with the second coreset.

[0431] In an example, BS 1920 may configure one or more search space sets, associated with the coreset #0, such that each search space set of the one or more search space sets indicate monitoring occasions overlapping with non-SBFD symbols. UE 1910 may not determine (or may determine no case) that a PDCCH candidate of a CSS, associated with the coreset #0, overlaps, in time domain, with one or more SBFD symbols of the plurality of SBFD symbols of the cell. A CSS or a search space set is associated with the coreset #0, where a coreset index configured for the CSS or the search space set is zero / 0. In an example, BS 1920 may configure a first search space for monitoring a RAR (e.g, ra-SearchSpace) to UE 1910. One or more candidates of the first search space may not overlap, in time, with one or more SBFD symbols of the plurality of SBFD symbols of the cell. BS 1920 may configure a second search space for monitoring a RAR (e.g., ra-SearchSpace2) to UE1910. One or more second candidates of the second search space may overlap (at least partially), in time, with one or more second SBFD symbols of the plurality of SBFD symbols of the cell. Based on / in response to selecting the RACH resource(s) 252a, UE 1910 may monitor the first search space to receive a RAR (Msg2 / RAR 1928) corresponding to the preamble 1928. Based on / in response to selecting the RACH resource(s) 252b, UE 1910 may monitor theDocket No.: 25-1015PCTsecond search space to receive a RAR (Msg2 / RAR 1928) corresponding to the preamble 1936. In an example, the second search space may comprise one or more monitoring occasions, where each monitoring occasion overlaps, in time, with the plurality of SBFD symbols of the cell and may not overlap, in time, with non-SBFD symbols of the cell. In an example, UE 1910 may be configured with the second search space based on / in response to the RACH resource(s) 252a and the RACH resource(s) 252b overlapping in time / frequency domain or in response to a first RNTI corresponding to the RACH resource(s) 252a and a second RNTI corresponding to the RACH resource(s) 252b being the same. UE 1910 may be configured with the second search space, where the RACH resource(s) 252a and the RACH resource(s) 252b may lead a same RA-RNTI value. UE 1910 may monitor the first search space for the RAR corresponding to the preamble 1928 via the RACH resource(s) 252b, when the second search space is not configured to UE 1910.

[0432] As explained above with respect to process 2000, in step 2006, UE 1910 may transmit preamble 2056 via the RACH resource and whether to select the RACH resource from RACH resource(s) 252a or RACH resource(s) 252b may depend on whether UE 1910 satisfies condition(s) such as, for example, whether UE 1910 supports SBFD and / or whether UE 1910 supports at least one of plurality of DL subbands 252c of the cell and uplink subband 252d of the cell.

[0433] However, according to an embodiment, UE 1910 may select, e.g., by default, the RACH resource for preamble transmission from RACH resource(s) 252a. In this embodiment, after, during, or before transmitting preamble 2056 via the RACH resource selected from RACH resource(s) 252a, UE 1910 may receive, from BS 1920, message(s) indicating to apply the one or more SBFD configuration parameters (e.g., plurality of DL subbands 252c for SBFD, UL subband 252d for SBFD, the plurality of SBFD symbols of the cell), for the initial access (e.g., a random access, a random access procedure, etc.) to the cell of BS 1920. In this disclosure, for simple referencing purpose, this message(s) is referred to as “SBFD-apply-indication-message(s).” In an example, the SBFD-apply-indication message(s) may be included in message(s) 2052. In an example, the SBFD-apply-indication message(s) may be transmitted via RRC signaling, MAC CE(s) (e.g., RAR (e.g., Msg2 / RAR 1938), RAR MAC CE, etc.), SIB1, SIBx, and / or DCI(s).

[0434] The RAR MAC CE carrying the SBFD-apply-indication message(s) may comprise a bitfield, and the value of the bitfield may indicate whether applying the one or more SBFD configuration parameters for the initial access is enabled / activated / configured or not. For example, if the value of the bitfield is equal to 1 , it may indicate that applying the one or more SBFD configuration parameters for the initial access is enabled / activated / configured. On the contrary, if the value of the bitfield is equal to 0, it may indicate that applying the one or more SBFD configuration parameters for the initial access is not enabled / activated / configured. In an example, the bitfield may be a reserved bitfield (e g., ‘R’, or reserved or set to a predetermined value (e.g., 0), for example, for a second cell configured without SBFD (operation)).Docket No.: 25-1015PCTIn the example, a RAR MAC CE IE may comprise a bit field (e.g., 1 bit), where the bit field may indicate a) the SBFD-apply-indication to enable or disable applying (or apply or not apply) the one or more SBFD configuration parameters, based on / in response the RAR MAC CE is used, during the initial access, for a RAR response of the cell enabled / configured with the one or more SBFD configuration parameters; or b) a reserved bit based on / in response to the RAR MAC CE is used, during a initial access of a second cell, for a second RAR response of the second cell not enabled / configured with one or more second SBFD configuration parameters.

[0435] During a non-initial access procedure, the bitfield may be used for indicating a timing advance group (TAG) of multiple TAGs of the cell in case the cell is configured with the multiple TAGs. During an initial access procedure, the bitfield may be used for indicating whether to apply the one or more SBFD configuration parameters for a random access procedure during the initial access procedure. Applying the one or more SBFD configuration parameters for the random access procedure may comprise any one or any combination of applying the one or more SBFD configuration parameters for transmitting and / or receiving a Msg3 RUSCH, a Msg4 PDSCH, a DCI indicating / scheduling a retransmission of a Msg3 PUSCH, and a HARQ-ACK PUCCH for PDSCH (4-step) or at least one of Msg B PDSCH and a HARQ-ACK PUCCH for Msg B (2-step).

[0436] In an example, the RAR MAC CE may be scheduled / comprised via / in a PDSCH scheduled / indicated by in a DCI. A DCI format of the DCI may comprise one or more bits (e.g., a bitfield) enabling / activating (or disabling / deactivating) applying the one or more SBFD configuration parameters.

[0437] In an example, the SBFD-apply-indication message(s) may comprise configuration parameter(s) indicating, enabling (or indicating of enablement of), or activating (or indicating activation of) applying the one or more SBFD configuration parameters (or ’the SBFD configuration parameter(s)’) for UE 1910’s initial access to the cell. The configuration parameter(s) may correspond to a flag. The value of the flag may indicate activation or enablement of SBFD application during a RACH . The flag may be included in a parameter or an information element (IE) (e.g., RACH-Generic, RACH-ConfigCommori), indicating RACH resource(s) 252a and / or a parameter or an IE (e.g., RACH-Generic, RACH-ConfigCommori), indicating RACH resource(s) 252b.

[0438] In an example, the SBFD configuration parameter(s) may indicate any one or any combination of: a frequency hopping offset (e.g., of startingPRB and secondHopPRB) of a PUSCH via SBFD symbols, power control parameter(s) (e.g., msg3-DeltaPreamble, new POAIphaSets comprising pO, alpha, a closed loop index, pathloss offset, etc.), repetition configuration parameter(s) (e.g., rsrp-ThresholdMsg3-SBFD), PRB(s) of a DL subband of the cell, PRB(s) of an UL subband of the cell, parameters (e.g., a starting slot index, a starting symbol, an ending slot index and an ending symbol) for a plurality of SBFD symbols of the cell.Docket No.: 25-1015PCT

[0439] In an example, group(s) of the SBFD configuration parameter(s) may comprise any one or any combination of: Msg3 PUSCH power configuration, Msg3 PUSCH hopping configuration, Msg3 PUSCH repetition configuration, uplink subband configuration, downlink subband configuration, Msg4 PDSCH reception configuration, HARQ-ACK PUCCH for Msg 4, Msg A PUSCH power configuration, MsgA PUSCH hopping configuration, MsgB PDSCH reception configuration, HARQ-ACK PUCCH for MsgB.

[0440] Based on receiving the SBFD-apply-indication-message, UE 1910 may transmit, for the initial access, UL signal(s) (i.e., UL transmission(s)) (e.g., ULsignal(s) 260), using the SBFD configuration parameter(s). Here, the UL signal(s) may be transmitted via RACH resource(s) in SBFD symbols. In an example, the UL signal(s) may comprise any one or any combination of: a Msg3 PUSCH, and a HARQ-ACK PUCCH for PDSCH (4-step) or at least one of MsgA PUSCH, and a HARQ-ACK PUCCH for Msg B (2-step).

[0441] In an example, Msg3 PUSCH power configuration comprises one or more of: msg3-De / taPreamble, deltaPreamble, msg3-Alpha, a default delta preamble value compared to a transmission power used for the preamble transmission; and / or Msg3 PUSCH hopping configuration comprises one or more of: a starting PRB of a hop, hopping frequency offset, msgA-preambleReceivedTargetPower

[0442] In an example, UE 1910 may determine transmission power of the Msg3 PUSCH based on power control parameter(s) such as, for example, msg3-deltaPremable.

[0443] In an example, UE 1910 may receive configuration parameter(s) indicating any one or more of: 1) a first msg3-deltaPreamble is for a first Msg 3 PUSCH transmission via non-SBFD symbols, wherein the first msg3-deltaPreamble corresponds to a RACH in one or more uplink symbols and / or one or more flexible symbols, 2) a second msg3-deltaPreamble is for a second Msg 3 PUSCH transmission via SBFD symbols, wherein the second msg3-deltaPreamble corresponds to a RACH in one or more SBFD symbols, 3) a third msg3-deltaPreamble is for a third Msg 3 PUSCH transmission via non-SBFD symbols, wherein the third msg3-deltaPreamble corresponds to a RACH in one or more SBFD symbols, and / or 4) a fourth msg3-deltaPreamble is for a fourth Msg 3 PUSCH transmission via SBFD symbols, wherein the fourth msg3-deltaPreamble corresponds to a RACH in one or more uplink symbols and / or one or more flexible symbols.

[0444] In an example, UE 1910 may determine the first, second, third, and / or fourth msg3-deltaPreambles based on absence of the one or more power control parameters.

[0445] In an example, the transmission of the msg 3 PUSCH based on the one or more SBFD configuration parameters indicates a capability that the wireless device supports an SBFD operation for the cell.

[0446] In an example, UE 1910 may receive a Msg 4 PDSCH, for the initial access (e.g. a random access procedure) corresponding to preamble 1936, based on the one or more SBFD configuration parameters. UE 1910 may monitor one or more PRBs within a downlink subband (and / or with the DL usable PRBs) ofDocket No.: 25-1015PCTthe cell based on the Msg 4 PDSCH overlapping with one or more SBFD symbols, where the one or more PRBs are comprised in frequency resources indicated by a DCI scheduling the Msg 4 PDSCH. UE 1910 may determine the usable DL PRBs of the cell, during the one or more SBFD symbols. UE 1910 may monitor the Msg4 PDSCH within the usable DL PRBs. UE 1910 may monitor one or more PDCCH candidates for a ra-SearchSpace via the initial downlink BWP 2052e. UE1910 may monitor the one or more PDCCH candidates which may overlap in frequency domain with outside of the downlik subband.Alternatively or additionally, UE 1910 may monitor one or more first PDCCH candidates to receive the DCI, scheduling the Msg 4 PDSCH, within the downlink subband (and / or within the DL usable PRBs) of the cell, where the wireless device is configured to skip monitoring one or more second PDCCH candidates overlapping with PRB(s) outside of the downlink subband. In an example, the uplink transmission may be a HARQ-ACK PUCCH corresponding to the Msg 4 PDSCH. The downlink subband may be the first DL subband or the second DL subband. UE 1910 may determine the downlink subband based on one or more embodiments of the specification.

[0447] UE 1910 may transmit a PUCCH comprising a HARQ-ACK feedback (e.g., the HARQ-ACK PUCCH) corresponding to the Msg4 PDSCH. The HARQ-ACK feedback may indicate ACK or NACK of the Msg4 PDSCH reception. A DCI scheduling the Msg4 PDSCH may indicate a HARQ-ACK feedback timing (e.g., PDSCH-to-HARQ_feedback timing indicator in a DCI format 1_0 used for the DCI). The DCI may, additionally, indicate a PUCCH resource index (e.g., PUCCH resource indicator'm the DCI format 1_0). In an example, UE 1910 may determine the PUCCH transmission overlaps, in time, with the plurality of SBFD symbols. Based on UE 1910 selecting the RACH resource(s) 252b and / or based on UE 1910 being indicated / configured / enabled to apply the one or more SBFD configuration parameters (e.g., via SBFD-apply-indication-message), UE 1910 may determine a PUCCH resource for the PUCCH transmission based on the PUCCH resource index via the DCI and the uplink subband 2052d (and configuration parameter(s) 2052g). The configuration parameter(s) 2052g may comprise / indicate a first set of parameters for a first PUCCH transmission via non-SBFD symbols (or when UE1910 is configured to not to apply the one or more SBFD configuration parameters). The configuration parameter(s) 2052g may comprise / indicate a second set of parameters for a second PUCCH transmission via SBFD symbols (or when UE1910 is configured to apply the one or more SBFD configuration parameters).

[0448] For example, the first set of parameters may comprise : a) a first starting PUCCH resource index (e.g., PUCCH-ResourceCommon') indicating an indexof a table, where the table comprise a list of {a PUCCH format, a first symbol of a PUCCH within a slot, a number of symbols used for a PUCCH transmission, a PRB offset indicating a starting PRB of an lowest indexed PUCCH resource, a set of additional parameters}. Based on the first starting PUCCH resource index and the table, UE 1910 may determine a first set of PUCCH resources (e.g., up to 8 PUCCH resources). The PUCCH resource index ofDocket No.: 25-1015PCTthe DCI may indicate one value of the first set of PUCCH resources, when the first set of parameters is used / applied. For example, the PRB offset may be applied based on the initial uplink BWP 2052f; b) a first initial power (e.g., pO-nominal) to indicate a parameter to determine a first transmission power of the PUCCH via non-SBFD symbols.

[0449] For example, the second set of parameters may comprise : a) a second starting PUCCH resource index (e.g., PUCCH-ResourceCommon2) indicating an index of the table. Based on the second starting PUCCH resource index and the table, UE 1910 may determine a second set of PUCCH resources (e.g., up to 8 PUCCH resources). The PUCCH resource index of the DCI may indicate one value of the set of PUCCH resources, when the second set of parameters is used / applied. In an example, the PRB offset may be applied based on the usable UL PRBs (that are determined based on the UL subband 2052d and the initial uplink BWP 2052f); a second initial power (e.g., p0-nominal2) to indicate a parameter to determine a second transmission power of the PUCCH via SBFD symbols; c) additional PRB offset to indicate additional PRB offset to determine a lowest indexed PUCCH resource of the second set of PUCCH resources. If the additional PRB offset is not provided, UE 1910 may determine zero / 0 for the additional PRB offset or may determine the additional offset based on a first starting PRB index of the initial uplink BWP 2052f and a second starting PRB index of the uplink subband 2052d.

[0450] In an example, UE 1910 may determine / apply the first set of parameters for the PUCCH transmission in response to / based on the PUCCH transmission overlaps, in time, with non-SBFD symbols or with uplink / flexible symbol(s) or UE 1910 being configured to disable to apply the one or more SBFD configuration parameters or the PUCCH transmission corresponds to the RACH resource(s) 252a.Otherwise, UE 1910 may determine / apply the second set of parameters for the PUCCH transmission.

[0451] In another example, UE 1910 may determine determine / apply the second set of parameters for the PUCCH transmission in response to / based on a condition. The condition may comprise one or more of: a) the PUCCH transmission overlaps, in time, with the plurality of SBFD symbols and the PUCCH transmission corresponding to the RACH resource(s) 2052b; or b) UE 1910 being configured to apply the one or more SBFD configuration parameters and the PUCCH transmission overlapping, in time, with SBFD symbols; c) the PUCCH transmission corresponds to the RACH resource(s) 252b (e.g., the random access procedure is based on a SBFD set of ROs) and the PUCCH transmission overlapping, in time, with the plurality of SBFD symbols and downlink symbol(s); d) the Msg4 PDSCH overlaps, in time, with the plurality of SBFD symbols, where the Msg4 PDSCH is a PDSCH for the HARQ-ACK feedback of the PUCCH transmission and the PUCCH transmission overlaps, in time, with the plurality of SBFD symbols; e) the first set of PUCCH resources may not overlap, in frequency, with the usable UL PRBs (e.g., the first set of PUCCH resources may present outside of the UL subband 2052d); f) a C-RNTI or a TC-RNTI assigned to UE 1910 may be larger than or equal to a value (e.g., RNTIs for SBFD-aware UEs may be separatelyDocket No.: 25-1015PCTconfigured from RNTIs for legacy UEs In this example, UE 1910 may apply the first set of parameters in response to / based on the condition has not been met / satisfied. For example, UE 1910 may apply the first set of parameters for the PUCCH transmission when the PUCCH transmission overlaps, in time, with non-SBFD symbols, the PUCCH transmission is associated with RACH resource(s) 252a (e.g., a legacy set of ROs), the Msg4 PDSCH corresponding to the PUCCH transmission may overlap, in time, with non-SBFD symbols, or the PUCCH transmission overlaps, in time, with uplink and / or flexible symbols.

[0452] In the specification, a SBFD symbol of the cell may refer a symbol of the plurality of SBFD symbols of the cell, where the symbol may be a downlink symbol indicated via one or more TDD UL / DL configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon) of the cell. In the specification, alternatively, a SBFD symbol of the cell may refer a symbol of the plurality of SBFD symbols of the cell, where the symbol may be a downlink symbol or a flexible symbol indicated via one or more TDD UL / DL configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon') of the cell.

[0453] FIG. 21 shows a process 2100 for UE 1910’s initial access to the cell provided by BS 1920, according to an embodiment of this disclosure. Process 2100 may begin with an optional step 2102. Step 2102 comprises UE 1910 receiving, from BS 1920 and for the cell, message(s) 2152 indicating one or more of: a plurality of SBFD symbols 352a, PRBs 352b of an UL subband of the cell, and / or a set 352c of RACH resources overlapping SBFD symbols of the plurality of SBFD symbols 352a.

[0454] After receiving message(s) 2152, in an optional step 2104, UE 1910 may select / determine a first set of RACH resources from set 352c of RACH resources, based on whether a RACH resource in set 352c is valid or not. For example, UE 1910 may select / determine the first set of RACH resources such that only valid RACH resources within set 352c are included in the first set of RACH resources.

[0455] After the first set of RACH resources is selected / determined, in step 2106, UE 1910 may select / determine a RACH resource, for preamble transmission, from either the first set of RACH resources or a second set of RACH resources depending on whether condition(s) are met. For example, the RACH resource is selected / determined from the first set of RACH resources based on the condition(s) not being met. On the contrary, the RACH resources may be selected / determined from the second set of RACH resources based on the condition(s) being met.

[0456] The second set of RACH resources may be a subset of the first set of RACH resources. In an example, the second set of RACH resources may only comprise RACH resources that 1) are included in the first set of RACH resources and 2) overlap with PRBs 352b of the UL subband of the cell. The first set of RACH resources may include RACH resources that do not overlap with PRBs 352b of the UL subband of the cell.

[0457] In selecting / determining the RACH resource in step 2106, UE 1910 may select / determine the earl iest / fi rst RACH resource among RACH resources included in the first set or the second set.Docket No.: 25-1015PCT

[0458] In an example, message(s) 2152 may indicate whether to enable or disable selecting / determining the RACH resource from the second set of RACH resources. In this example, the condition(s) may include that UE 1910 received message(s) 2152 indicating enablement of selecting / determining the RACH resource from the second set of RACH resources. In other words, in case message(s) 2152 does not indicate enablement of selecting / determining the RACH resource from the second set of RACH resources (and / or indicates disablement of selecting / determining the RACH resource from the second set of RACH resources), UE 1910 may determine that the condition(s) are not met, and thus select / determine the RACH resource from the first set of RACH resources. On the contrary, in case message(s) 352 indicates enablement of selecting / determining the RACH resource from the second set of RACH resources, UE 1910 may determine that the condition(s) are met, and thus select / determine the RACH resource from the second set of RACH resources.

[0459] In an example, instead of or in addition to the indication of message(s) 2152 regarding enabling or disabling of selecting / determining the RACH resource from the second set of RACH resources, the condition(s) may comprise that UE 1910 supports SBFD (or supports at least one of the plurality of DL subbands of the cell and an UL subband of the cell, or supports all DL subbands that overlap...

Claims

Docket No.: 25-1015PCTCLAIMS1. A method comprising:receiving, by a wireless device and for a cell, one or more messages indicating:one or more first physical random access channel (PRACH) resources in one or more uplink symbols and / or one or more flexible symbols;one or more second PRACH resources in one or more subband full duplex (SBFD) symbols;a plurality of downlink subbands of the cell, corresponding to a plurality of SBFD symbols, wherein the plurality of downlink subbands comprises a first downlink subband and a second downlink subband; anda flag indicating use the one or more second PRACH resources for a random access procedure;determining, for an initial access to the cell, whether the wireless device supports SBFD, based on whether the wireless device supports the plurality of downlink subbands of the cell and an uplink subband of the cell; andtransmitting, for the random access procedure to the cell, a preamble via a PRACH resource of the one or more second PRACH resources, based on the flag and determining that the wireless device supports SBFD; andreceiving, via a set of physical resource blocks (PRBs) within an initial downlink bandwidth part during the random access procedure, a downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) corresponding to the preamble, wherein the set of PRBs: overlaps with the first downlink subband and the initial downlink bandwidth part; and does not overlap with PRBs outside of the first downlink subband, wherein the PRBs overlap with the second downlink subband.

2. The method of claim 1 , wherein the one or more messages further indicate a control resource set (coreset) overlapping with the first downlink subband and the PRBs.

3. The method of claim 2, further comprising skipping monitoring one or more physical downlink control channel (PDCCH) candidates of a plurality of PDCCH candidates, wherein each of the one or more PDCCH candidates overlaps with the PRBs and the initial downlink bandwidth part.

4. The method of claim 3, wherein the plurality of PDCCH candidates is for the DCI.

5. The method of claim 4, wherein the plurality of PDCCH candidates is of a common search space (CSS).

6. The method of any one of claims 1-5, wherein the PDSCH is within the first downlink subband.Docket No.: 25-1015PCT7. The method of any one of claims 1-6, wherein the PDSCH comprises at least one of random access response and a Msg 4 (contention resolution identifier).

8. The method of any one of claims 1-7, wherein the one or more first PRACH resources are configured with a feature combination.

9. The method of claim 8, wherein the one or more messages further indicates a configuration option of:a first configuration option to configure the one or more second PRACH resources; and a second configuration option to configure the one or more second PRACH resources.

10. The method of claim 9, wherein the one or more second PRACH resources are configured with the feature combination based on the configuration option being the first configuration option.

11. The method of claim 9, wherein the one or more second PRACH resources are configured with the feature combination or are configured with a second feature combination based on the configuration option being the second configuration option.

12. The method of claim 11, wherein the second feature combination is different from the feature combination.

13. The method of any one of claims 8-12, wherein the feature combination indicates one or more of: msg 1 -repetitions;msg3-repetitions;smallData;redCap;eRedCap; andnsag.

14. The method of any one of claims 11-13, wherein the second feature combination indicates one or more of:msg 1 -repetitions;msg3-repetitions;smallData;redCap;eRedCap; andnsag.

15. The method of any one of claims 8-14, wherein the one or more messages indicate a PRACH configuration index configured with the feature combination, wherein the one or more first PRACH resources and the one or more second PRACH resources are determined based on the PRACH configuration index.

16. The method of claim 15, wherein the one or more messages indicate:Docket No.: 25-1015PCTa first PRACH configuration index configured with the feature combination, wherein the one or more first PRACH resources are determined based on the first PRACH configuration index; and a second PRACH configuration index configured with the first feature combination, wherein the one or more second PRACH resources are determined based on the second PRACH configuration index.

17. The method of any one of claims 1-16, wherein the one or more messages are at least one of one or more radio resource control (RRC) messages, one or more system information block (SIB) messages, one or more medium access control control elements (MAC CEs), and one or more downlink control information (DCIs).

18. A method comprising:transmitting, by a wireless device and for an random access procedure to a cell, a preamble via a physical random access channel (PRACH) resource in one or more uplink symbols and / or one or more flexible symbols;receiving one or more messages indicating to apply one or more subband full duplex (SBFD) configuration parameters for the initial access to the cell; andbased on receiving the one or more messages, transmitting an uplink transmission via an uplink resource, for the random access procedure, using the one or more SBFD configuration parameters, wherein the uplink resource used for the uplink transmission overlaps with one or more SBFD symbols.

19. The method of claim 18, comprising receiving one or more messages indicating:one or more first PRACH resources, wherein each of the one or more first PRACH resources overlaps with one or more uplink symbols and / or one or more flexible symbols; andone or more second PRACH resources, wherein each of the one or more second PRACH resources overlaps with in one or more second SBFD symbols.

20. The method of claim 18 or 19, wherein the random access procedure is initiated by or with transmitting the preamble.

21. The method of claim 19 or 20, wherein the one or more messages indicating to apply the one or more SBFD configuration parameters for the random access procedure to the cell are same as the one or more messages indicating the one or more first and second PRACH resources.

22. The method of any one of claims 19-21, wherein:the one or more SBFD configuration parameters indicate one or more of:a frequency hopping offset of a physical uplink shared channel (PUSCH) via SBFD symbols;one or more power control parameters for the PUSCH;Docket No.: 25-1015PCTone or more repetition configuration parameters;one or more PRBs of a downlink subband of the cell;one or more second PRBs of an uplink subband of the cell; andparameters for a plurality of SBFD symbols of the cell; andthe plurality of SBFD symbols comprises the one or more SBFD symbols and the one or more second SBFD symbols.

23. The method of any one of claims 19-22, wherein the one or more messages indicating to apply the one or more SBFD configuration parameters for the random access procedure to the cell are transmitted via any one or more of: radio resource control (RRC) signaling, one or more medium access control (MAC) control elements (CEs), or downlink control information (DCI).

24. The method of any one of claims 19-23, wherein the one or more messages indicating to apply the one or more SBFD configuration parameters for the random access procedure to the cell comprise one or more configuration parameters indicating to enable applying the one or more SBFD configuration parameters for the random access procedure.

25. The method of claim 24, wherein the one or more configuration parameters indicating to enable applying the one or more SBFD configuration parameters for the random access procedure comprise one or more of:a flag indicating to use the one or more second PRACH resources for the random access procedure;a flag in parameters (RACH-Generic) indicating the one or more first PRACH resources and the one or more second PRACH resources;a flag in a first common RACH configuration indicating the one or more first PRACH resources; and / ora flag in a second common RACH configuration indicating the one or more second PRACH resources.

26. The method of any one of claims 24-25, wherein the one or more configuration parameters indicating to enable applying the one or more SBFD configuration parameters for the random access procedure are included a system information block 1 (SIB1 ), other system information block (s)(SIB(s), other Sl(s)), or RRC message(s).

27. The method of any one of claims 18-26, wherein the uplink transmission is for:any one or more of: a random access preamble, a preamble, a PRACH, a Msg3 PUSCH, and a HARQ-ACK PUCCH for PDSCH; orat least one of a random access preamble, a preamble, a PRACH, MsgA PUSCH, and a HARQ- ACK PUCCH for Msg B.Docket No.: 25-1015PCT28. The method of any one of claims 18-27, wherein the one or more SBFD configuration parameters comprise one or more of: Msg3 PUSCH power configuration, Msg3 PUSCH hopping configuration, Msg3 PUSCH repetition configuration, uplink subband configuration, downlink subband configuration, Msg4 PDSCH reception configuration, HARQ-ACK PUCCH for Msg 4, Msg A PUSCH power configuration, MsgA PUSCH hopping configuration, MsgB PDSCH reception configuration, HARQ- ACK PUCCH for MsgB.

29. The method of claim 28, wherein:Msg3 PUSCH power configuration comprises one or more of msg3-DeltaPreamble, deltaPreamble, msg3-Alpha, a default delta preamble value compared to a transmission power used for the preamble transmission; and / orMsg3 PUSCH hopping configuration comprises one or more of: a starting PRB of a hop, hopping frequency offset, msgA-preambleReceivedTargetPower.

30. The method of any one of claims 18-29, wherein the one or more SBFD configuration parameters are applied for at least one of: transmission of a PRACH, transmission of a preamble, transmission of a Msg3 PUSCH, reception of a Msg4 PDSCH, and transmission of a HARQ-ACK PUCCH for PDSCH, reception of a Msg B PDSCH, and transmission of a HARQ-ACK PUCCH for Msg B.

31. A method comprising:receiving, by a wireless device, one or more radio resource control (RRC) messages indicating, for an uplink bandwidth part of a cell:a first set of PRACH resources, wherein each PRACH resource in the first set of PRACH resources overlaps with one or more uplink symbols and / or one or more flexible symbols; a second set of PRACH resources, wherein each PRACH resource in the second set of PRACH resources overlaps with a subband full duplex (SBFD) symbol;a first threshold value for determining a PRACH resource type;a first set of threshold values for determining a number of preamble repetitions; and a second set of threshold values for determining a number of preamble repetitions; determining the PRACH resource type based on the first threshold;after determining the PRACH resource type, transmitting preamble repetitions via one or more PRACH resources, wherein:the one or more PRACH resources via which the preamble repetitions are transmitted are from the first set of PRACH resources, and a number of the transmitted preamble repetitions is determined based on the first set of threshold values; orDocket No.: 25-1015PCTthe one or more PRACH resources via which the preamble repetitions are transmitted are from the second set of PRACH resources, and the number of the transmitted preamble repetitions is determined based on the second set of threshold values.

32. The method of claim 31 , wherein:the one or more PRACH resources via which the preamble repetitions are transmitted are either from the first set of PRACH resources or the second set of PRACH resources, based on the PRACH resource type; andthe number of transmitted preamble repetitions is determined based on either the first set of threshold values or the second set of threshold values, in response to which one of the first set or the second set of PRACH resources from which the one or more PRACH resources are from.

33. The method of claim 31 or 32, comprising selecting the one or more PRACH resources from the first set of PRACH resources, in response to the PRACH resource type being the first type.

34. The method of claim 31 or 32, selecting the one or more PRACH resources from the second set of PRACH resources, in response to the PRACH resource type being the second type.

35. The method of any one of claims 31-34, wherein the first threshold value is a reference signal received power (RSRP) threshold.

36. The method of any one of claims 31-35, wherein the one or more messages further indicate a second threshold for selecting a synchronization signal block (SSB) for a random access procedure.

37. The method of claim 36, wherein the random access procedure is initiated by transmitting the preamble repetitions.

38. The method of any one of claims 31-37, wherein the first set of PRACH resources is associated with a first feature combination comprising a support of msg1 -repetitions.

39. The method of claim 38, wherein the one or more RRC messages further comprise:a first PRACH configuration index for the first set of PRACH resources; anda parameter indicating one of a first configuration option and a second configuration option for determining the second set of PRACH resources.

40. The method of claim 39, wherein the second set of PRACH resources is associated with the first feature combination based on the parameter being set to the first configuration option.

41. The method of claim 39, wherein the second set of PRACH resources is associated with a second feature combination comprising a support of msg 1 -repetitions.

42. The method of claim 41 , wherein the second feature combination is same as or different from the first feature combination.

43. The method of any one of claims 39-42, comprising determining:the first set of PRACH resources based on the first PRACH configuration index; andDocket No.: 25-1015PCTthe second set of PRACH resources based on the first PRACH configuration index in response to the parameter being set to the first configuration option.

44. The method of any one of claims 39-42, wherein the one or more RRC messages further indicate a second PRACH configuration index based on the parameter being set to the second configuration option.

45. The method of claim 44, comprising determining the second set of PRACH resources is based on the second PRACH configuration index, in response to the parameter being set to the second configuration option.

46. An apparatus comprising:one or more processors; andmemory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1-45.

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

Images