Spatial filter with duplexing

Abstract

A method can include transmitting, by a wireless device and via a first physical random-access channel (PRACH) occasion, a preamble using a first spatial filter. The method can also include transmitting, in a transmission occasion, an uplink signal using a second spatial filter. The second spatial filter can be the same as the first spatial filter in response to (or when) both the transmission occasion and the PRACH occasion being in sub-band full-duplex (SBFD) symbols. The second spatial filter can be different from the first spatial filter in response to (or when) only one of the transmission occasion and the PRACH occasion being in SBFD symbols.

Description

TITLESpatial Filter with DuplexingCROSS REFERENCE TO RELATED APPLICATIONS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0023] FIG. 17A, FIG. 17B, and FIG. 17C illustrate aspects of example embodiments 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.

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

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

[0033] 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 radioenvironment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

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

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

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

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

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

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

[0040] 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 combinationthereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

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

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

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

[0044] 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 userequipment (U E), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

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

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

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

[0048] 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 basestations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

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

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

[0052] As illustrated in FIG. 1 B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG. 1 B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and 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 supportrouting 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.

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

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

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

[0056] As shown in FIG. 1 B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying 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. 1 B, gNB 160Amay 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.

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

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

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

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

[0061] 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 stacksillustrated 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.

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

[0063] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to 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.

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

[0065] Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearersprovided 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.

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

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

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

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

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

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

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

[0073] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 212 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] 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 ofone 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 includes, for example:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0113] 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 receivebandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

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

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

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

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

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

[0119] 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 maydetermine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.

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

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

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

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

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

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

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

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

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

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

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

[0131] 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 UCI 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0151] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels.For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS 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.

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

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

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

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

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

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

[0158] FIG. 11 B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11 B may span a resource block (RB)within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

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

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

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

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

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

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

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

[0168] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH)parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral)', cell-specific parameters (e.g., RACH-ConfigCommon),’ and / or dedicated parameters (e.g., RACH-configDedicated). The base station may 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.

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

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

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

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

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

[0174] 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 andindicated 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:

[0175] RA-RNTI= 1 + s_id + 14 x t_id + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id , where sjd may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g , 0 < tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 0 fjd < 8), and ul_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).

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

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

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

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

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

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

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

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

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

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

[0186] The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)).The base station 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0216] FIG. 17A shows an example timing diagram as per an aspect of an embodiment of the present disclosure In the example of FIG. 17A, a wireless device 1700 receives message(s) 1706. Wireless device 1700 may receive message(s) 1706 from a base station 1720.

[0217] Wireless device 1700 may be, for example, a sidelink wireless device. Wireless device 1700 may be, for example, a non-terrestrial network (capable) wireless device. Wireless device 1700 may be, for example, a network control repeater (NCR), e.g., NCR-mobile termination (MT) or NCR-forwarding (Fwd). Wireless device 1700 may be, for example, an integrated access and backhaul (IAB) node, e.g., IAB-MT. Wireless device 1700 may be an air-to-ground (ATG) wireless device. Wireless device 1700 may be an Internet-of-Things (loT) wireless device. Wireless device 1700 may be, for example, an intelligent reflective surface (IRS) or reflective intelligent surface (RIS) node.

[0218] Base station 1720 may be, for example, a satellite. Base station 1720 may be, for example, a gNB or an eNB. Base station 1720 may be, for example, a gNB-CU. Base station 1720 may be, for example, a gNB-DU. Base station 1720 may be, for example, an NCR. Base station 1720 may be, for example, an IAB node. Base station 1720 may be, for example, a sidelink device or node. Base station 1720 may be, for example, an intelligent reflective surface (IRS) or reflective intelligent surface (RIS) node.

[0219] Message(s) 1706 may be (or comprise) one or more radio resource control (RRC) messages. For example, the one or more RRC messages may be, or comprise, one or more RRC reconfiguration messages, one or more RRC setup messages, one or more RRC release messages, and / or one or more RRC resume messages.

[0220] Message(s) 1706 may be (or comprise), for example, one or more system information messages. For example, the one or more system information messages message may be (or comprise) one or moresystem information blocks (SIBs), one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks, and / or one or more master information blocks (M IBs).

[0221] Message(s) 1706 may be (or comprise), for example, a layer-2 message, such as, e.g., a MAC CE, a MAC sub-header, a MAC PDU, a MAC subPDU, a MAC payload, a MAC header, and / or any other type of message in a MAC layer.

[0222] Message(s) 1706 may be, for example, a layer-1 message, such as, e.g., a DCI, a PDCCH message, a PDSCH message, a sidelink message, a PSSCH message, a PSCCH message, an access link message, a control link message, and / or any other type of message in a lower layer (e.g., the physical layer).

[0223] Message(s) 1706 may indicate, or comprise, configuration parameters 1708. Configuration parameters 1708 may be, for example, RRC configuration parameters.

[0224] In an example, the configuration parameters 1708 may be for one or more cells.

[0225] Configuration parameters being for the one or more cells may comprise, be the same as, and / or referred to as follows: the configuration parameters being of the one or more cells, the configuration parameters being associated with the one or more cells, the configuration parameters being configured for the one or more cells, the configuration parameters being assigned to the one or more cells, and / or the like.

[0226] The one or more cells may comprise a cell. The wireless device may be camped on the cell. The wireless device camping on the cell may comprise or be the same as the wireless device being located in a geographical area covered by the cell, the wireless device being served by the cell, the wireless device being configured (e.g., by configuration parameters 1708) the cell, the wireless device receiving configuration parameters for the cell, and / or the like.

[0227] The cell may comprise one or more bandwidth parts (BWPs). The one or more BWPs may comprise one or more uplink BWPs and / or one or more downlink BWPs.

[0228] Configuration parameters 1708 may be of (e.g., for, associated with, or configured for) the one or more BWPs.

[0229] Configuration parameters 1708 may be of (e.g., for, associated with, or configured for) a BWP (or per each BWP) of the one or more BWPs of the cell .

[0230] The cell may be, for example, a serving cell (e.g., of the wireless device).

[0231] The cell may be, for example, a non-serving cell (e.g., a layer 1 or layer 2 triggered mobility (LTM) candidate cell, inter-cell beam management cell, inter-cell multi transmission and reception point (TRP) cell, and / or any other type of cell that is configured by configuration parameters 1708 as a non-serving cell).

[0232] The cell may be, for example, a special cell (SpCell). For example, the cell may be a primary cell (PCell) and / or a primary secondary cell (PSCell). For a master cell group, SpCell may be PCell. For a secondary cell group, SpCell may be PSCell.

[0233] The cell may be, for example, a deactivated cell (e.g., deactivated SCell, deactivated PSCell, and / or the like).

[0234] The cell may be, for example, an NTN cell. For example, the configuration parameters 1708 may comprise one or more NTN-specific / related configuration parameters.

[0235] The cell may be, for example, a licensed cell. For example, uplink (UL) and downlink (DL) communications via the cell may occur over licensed frequency bands (e.g., spectrum).

[0236] The cell may be, for example, an unlicensed cell. For example, the cell may be for shared spectrum channel access. For example, UL and DL communications via the cell may occur over unlicensed frequency bands (e.g., spectrum).

[0237] The cell may comprise (e.g., be configured with or associated with) one or more BWPs. For example, configuration parameters 1708 may indicate the one or more BWPs for the cell.

[0238] Configuration parameters 1708 may be (or comprise), for example, cell-specific configuration parameters. For example, configuration parameters 1708 may be transmitted to a plurality of wireless devices in the cell. Cell specific configuration parameters may be referred to as common configuration parameters, group-common configuration parameters, non / not dedicated configuration parameters, configuration parameters received before receiving dedicated configuration parameters, and / or the like.

[0239] Configuration parameters 1708 may be (or comprise), for example, BWP-specific configuration parameters. For example, configuration parameters 1708 may be applicable for a BWP, of the one or more BWPs, of the cell.

[0240] In an example, the configuration parameters 1708 may be (or comprise) wireless device specific configuration parameters. Wireless device specific configuration parameters may be referred to as, for example, dedicated configuration parameters, non / non-common configuration parameters, U E-specific configuration parameters, and / or the like.

[0241] In some embodiments, duplexing mode may be referred to as duplexing / duplexed / duplex (operation / operating) mode. For example, sub-band full duplex (SBFD) mode may be referred to as or be equivalent to SBFD operation, SBFD symbols, SBFD slots, and / or SBFD operating mode.

[0242] In some embodiments, “symbol’’ or “slot” may indicate a time unit, time interval, time duration, time period, and / or time window. In some embodiments, the terms “symbols” and “slots” may be used interchangeably.

[0243] FIG. 17B shows an example of a duplexing mode 1702 as per an aspect of an embodiment of the present disclosure. Duplexing mode 1702 may be, for example, a time division duplex (TDD) mode (or TDD operation) in which transmission time intervals (e.g., symbols in FIG. 17B) overlap in frequency (e.g., are in the same frequency or same band) and are transmitted on, or received on, at different times (e.g., different symbols and / or do not overlap in time). Duplexing mode 1702 may be for (e.g., of, associated with,configured for, applicable for) unpaired spectrum operation (e.g., communication in, on, or within unpaired spectrum).

[0244] The example of FIG. 17B illustrates five symbols. In an example, configuration parameters 1708 may indicate which of the five symbols are for downlink (DL) and which of the five symbols are for uplink (UL). For example, in the example of FIG. 17B, configuration parameters 1708 indicate that the first four symbols, of the five symbols, are DL symbols and that the fifth / last symbol, of the five symbols, is an UL symbol. Examples of how the configuration parameters 1708 indicate which symbols are uplink and downlink are provided below.

[0245] In an example, a symbol may be (e.g., configured or designated as) a DL symbol based on configuration parameters 1708 indicating that the symbol is to be for (e.g., of, for, associated with, or configured for) DL operation. For example, a symbol may be a DL symbol, for example, based on configuration parameters 1708 indicating the symbols to be for (e.g., of, for, associated with, or configured for) only DL operation and the symbol being one of the symbols. As another example, a symbol may be a DL symbol based on configuration parameters 1708 indicating that the symbol is a flexible symbol and one or more second configuration parameters (e.g., dedicated configuration parameters, MAC CE, DCI) indicating that the symbol is associated with (e.g., indicated for, for, of, and / or the like) DL operation.

[0246] In an example, a symbol may be an UL symbol based on configuration parameters 1708 indicating the symbol to be configured with (e.g., associated with, for, of) UL operation. For example, a symbol may be a UL symbol, for example, based on configuration parameters 1708 indicating the symbols to be configured with (e.g., associated with, for, of) only UL operation. As another example, a symbol may be a UL symbol based on configuration parameters 1708 indicating that the symbol is a flexible symbol and one or more second configuration parameters (e.g., dedicated configuration parameters, MAC CE, DCI) indicating that the symbol is associated with (e.g., indicated for, for, of, and / or the like) UL operation.

[0247] In an example, wireless device 1700 may receive message(s) 1710 from base station 1720. For example, wireless device 1700 may receive message(s) 1710 from base station 1720 via a DL symbol (e.g., any of the first four symbols of the five symbols shown in FIG. 17B). In another example, wireless device 1700 may transmit message(s) 1712 to base station 1720 via a UL symbol (e.g., the fifth / last symbol of the five symbols shown in FIG. 17B).

[0248] Configuration parameters 1708 may comprise a parameter (e.g., dl-UL-TransmissionPeriodicity) indicating a periodicity of DL-UL pattern for one or more symbols within a period. The DL-UL pattern may be referred to as a periodicity of a DL-UL pattern. For example, the parameter indicating the periodicity of DL-UL pattern may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B is a UL symbol.

[0249] Configuration parameters 1708 may comprise a parameter indicating a number of consecutive DL (e.g ., full DL, DL only) slots / symbols at the beginning of each DL-UL pattern. For example, the parameter indicating the number of consecutive DL slots / symbols at the beginning of each DL-UL pattern may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B is a UL symbol.

[0250] Configuration parameters 1708 may comprise a parameter indicating a number of consecutive DL symbols / slots at the beginning of a slot following a last (full) DL slot (e.g., as derived from the parameter indicating the number of consecutive full DL slots / symbols at the beginning of each DL-UL pattern).

[0251] Configuration parameters 1708 may comprise a parameter (e.g., nrofUplinkSlots) indicating a number of consecutive UL (e.g., full UL, UL only) slots / symbols at the end of each DL-UL pattern. For example, the parameter indicating a number of consecutive UL slots / symbols at the end of each DL-UL pattern may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B is a UL symbol.

[0252] Configuration parameters 1708 may comprise a parameter indicating a number of consecutive UL symbols at the end of the slot preceding the first full UL slot. The parameter indicating a number of consecutive UL symbols in the end of the slot preceding the first full UL slot may indicate that the first four symbols shown in FIG. 17B are DL symbols and the last symbol shown in FIG. 17B is a UL symbol.

[0253] According to the example of FIG. 17B in which duplexing mode 1702 is TDD, wireless device 1700 and / or base station 1720 may transmit and receive a signal on / in / via the same BWP / carrier but at different transmission time intervals (e.g., different symbols / slots). For example, wireless device 1700 may receive message(s) 1710 via the first symbol shown in FIG. 17B and / or transmit message(s) 1712 via the last symbol shown in FIG. 17B, which is a UL symbol. Wireless device 1700 may transmit and / or receive message(s) 1710 in / on / via the same carrier / BWP in the example of FIG. 17B using duplexing mode 1702.

[0254] In some embodiments, the terms "BWP,” "carrier," "band,” "bandwidth,” "component carrier,” “center frequency,” “center carrier,” “frequency,” and / or “band combination" may be used interchangeably.

[0255] FIG. 17C illustrates an example of a duplexing mode 1704 as per an aspect of an embodiment of the present disclosure. The duplexing mode 1704 may be a frequency division duplexing (FDD) mode in which transmission time intervals (e.g., symbols in FIG. 17C) overlap in time (e g., same symbol) and are transmitted on, or received on, different frequencies (e.g., different frequency bands and / or do not overlap in frequency). The duplexing mode 1704 may be for (e.g., of, associated with, configured for, applicable for) paired spectrum operation (e.g., communication in, on, or within paired spectrum).

[0256] FIG. 17C shows five symbols. Unlike FIG. 17B, each symbol, of the five symbols, illustrated in FIG. 17C may be both UL and DL symbols. For example, wireless device 1700 may transmit an uplink signal via any of the five symbols and receive a downlink signal via any of the five symbols. Wireless device 1700may transmit the uplink signal and receive the downlink signal on the same symbol(s) but on different frequencies, such as different BWPs or different carriers (e.g., downlink carrier, SUL, NUL). In duplexing mode 1704 (e.g., FDD), wireless device 1700 and / or base station 1720 does not receive the downlink signal and transmit the uplink signal on the same symbol(s) and the same BWP (or the same carrier).

[0257] For example, wireless device 1700 may transmit the UL signal on the first symbol shown in FIG. 17C via a UL BWP. Wireless device 1700 may receive the DL signal on the first symbol shown in FIG. 17C via a DL BWP. In the example of FIG. 17C, the UL BWP may be different from the DL BWP. For example, the UL BWP and the DL BWP may be separated in frequency domain as shown in FIG. 17C. The UL BWP and the DL BWP may not overlap in frequency domain as shown in FIG. 17C. The UL BWP and / or the DL BWP may be of, for, associated with, or configured for the same cell (e.g., the cell, a cell of the one or more cells).

[0258] Transmitting or receiving a signal or message via a BWP may be the same as or be referred to as transmitting or receiving the signal or message on, in, using, based on, with, within, and / or over the BWP.

[0259] The base station 1720 may receive the UL signal and / or transmit the DL signal.

[0260] In some embodiments, the duplexing mode 1702 and / or the duplexing mode 1704 may be referred to as a half-duplex mode or a non-SBFD (mode / operation).

[0261] FIG. 18 illustrates an example of a duplexing mode 1802 as per an aspect of an embodiment of the present disclosure. Duplexing mode 1802 may be an advanced duplexing mode in which transmitting time intervals (e.g., symbols in FIG. 17A, FIG 17B, FIG. 17C, or FIG 18) overlap in both frequency (e.g., same band, same BWP, same carrier) and time (e.g., same symbols). Duplexing mode 1802 may be, for example, sub-band full-duplex (SBFD) mode.

[0262] Duplexing mode 1802 may be different from duplexing mode 1702. Duplexing mode 1802 may be different from duplexing mode 1704.

[0263] Duplexing mode 1802 may be applicable for (e.g., associated with, configured for) unpaired spectrum operation (e.g., as in TDD operation as shown in FIG. 17B).

[0264] In another example, duplexing mode 1802 may be applicable for (e.g., associated with, configured for) paired spectrum operation (e.g., as in FDD operation as shown in FIG. 17C).

[0265] In some embodiments, “SBFD” may be (or comprise, refer to, be replaced with, be equivalent to) “advanced duplex,” “full duplex,” “partial full duplex,” “sub-band non-overlapping full duplex,” “flexible duplex,” and / or the like.

[0266] FIG. 18 illustrates five symbols. Each symbol, of the five symbols, may be DL symbol, UL symbol, flexible symbol, and / or SBFD symbol. Each symbol, of the five symbols, may be on (e.g., over, in, via, for, of, configured for, assigned with, and / or associated with) the same carrier or BWP.

[0267] In some embodiments, the terms “symbol” and “slot” may be used interchangeably.

[0268] In the example of FIG. 18, the five symbols may comprise a symbol 1804, a symbol 1806, a symbol 1808, a symbol 1810, and / or a symbol 1812.

[0269] Symbol 1804 may be a DL symbol. Symbol 1804 may be a DL symbol. Symbol 1812 may be a UL symbol.

[0270] A DL symbol may be a symbol via (e.g. , over, in, on) which a wireless device may receive a DL signal. DL symbol may be a symbol via (e.g., over, in, on) which a base station may transmit a DL signal. A base station may not receive a UL signal via DL symbol. A wireless device may not transmit a UL signal via DL symbol.

[0271] A UL symbol may be a symbol via (e.g., over, in, on) which a wireless device may transmit a UL signal A UL symbol may be a symbol via (e.g., over, in, on) which a base station may receive a UL signal. A base station may not transmit a DL signal via UL symbol. A wireless device may not receive a DL signal via UL symbol.

[0272] In some embodiments, the terms “operation” and “mode” may be used interchangeably. For example, SBFD mode and SBFD operation may be used interchangeably.

[0273] In an example, message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1804 is a DL symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1806 is a DL symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1812 is a UL symbol.

[0274] Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1808 is an SBFD symbol. Message(s) 1706 and / or configuration parameters 1708 may indicate that symbol 1810 is an SBFD symbol.

[0275] An SBFD symbol may be / comprise a symbol via (e.g., over, in, on) which a wireless device and / or a base station may transmit and receive DL and UL signal(s), respectively. For example, an SBFD symbol may comprise (or be associated with, configured with) one or more sub-bands. The wireless device may transmit signals via (e.g., over, in, on) one or more UL sub-bands, of the one or more sub-bands, and / or receive signals via (e.g., over, in, on) one or more DL sub-bands of the one or more sub-bands. The base station may transmit signals via (e.g., over, in, on) one or more DL sub-bands, of the one or more subbands, and receive signals via (e.g., over, in, on) one or more UL sub-bands of the one or more sub-bands

[0276] In the example of FIG. 18, symbol 1808 may be an SBFD symbol. Symbol 1810 may be an SBFD symbol. Symbol 1808 may comprise (e.g., be associated with, configured with, have, and / or the like) a subband 1814. Symbol 1808 may comprise a sub-band 1816. Symbol 1808 may comprise a sub-band 1818. Sub-band 1814 and sub-band 1818 may be DL sub-bands. Sub-band 1816 may be a UL sub-band. The one or more sub-bands may comprise sub-band 1814, sub-band 1816, and / or sub-band 1818.

[0277] A DL sub-band may comprise resource blocks (RBs) via (e.g., over, in, on) which a wireless device may receive DL signal(s). A DL sub-band may comprise RBs via (e.g., over, in, on) which a base station may transmit DL signal(s). A wireless device may not transmit UL signal(s) via (e.g., over, in, on) a DL subband of an SBFD symbol. A base station may not receive UL signal(s) via (e.g., over, in, on) a DL sub-band of an SBFD symbol. The RBs comprised in a DL sub-band may be referred to as DL usable PRBs. DL usable PRBs may be an intersection of DL BWP(s) and DL sub-band(s).

[0278] A UL sub-band may comprise RBs via (e.g., over, in, on) which a wireless device may transmit UL signal(s). A UL sub-band may comprise RBs via (e.g., over, in, on) which a base station may receive UL signal(s). A wireless device may not receive DL signal(s) via (e.g., over, in, on) a UL sub-band of an SBFD symbol. A base station may not transmit DL signal(s) via (e.g., over, in, on) a UL sub-band of an SBFD symbol. The RBs comprised in a UL sub-band may be referred to as UL usable PRBs. UL usable PRBs may be an intersection of UL BWP(s) and UL sub-bands.

[0279] A base station may transmit DL signals via (e.g., over, in, on) sub-band 1814 and / or sub-band 1818 of symbol 1808. A base station may receive UL signals via (e.g., over, in, on) sub-band 1816 of symbol 1808.

[0280] A wireless device may receive DL signals via (e.g., over, in, on) sub-band 1814 and / or sub-band 1818 of symbol 1808. A wireless device may transmit UL signals via (e.g., over, in, on) sub-band 1816 of symbol 1808.

[0281] In an example, wireless device 1700 may use SBFD symbols (e.g., symbol 1808 and symbol 1810) for either UL transmission or DL reception. Configuration parameters 1708 may indicate link direction for at least one SBFD symbol, of one or more SBFD symbols, configured or indicated by configuration parameters 1708. For example, configuration parameters 1708 may comprise a field or parameter indicate link direction (e.g., UL or DL) for the at least one SBFD symbol of the one or more SBFD symbols. In the example of FIG. 18, the one or more SBFD symbols may comprise symbol 1808 and symbol 1810

[0282] In another example, wireless device 1700 may determine link direction of an SBFD symbol based on whether a UL transmission or a DL reception is scheduled on the SBFD symbol. For example, configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) may indicate or schedule a UL transmission (e.g., PUSCH, PUCCH, SRS, and / or the like) via symbol 1808 (e.g., via sub-band 1816). Wireless device 1700 may determine link direction of symbol 1808 as UL based on configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) indicating or scheduling a UL transmission via symbol 1808. In another example, configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) may indicate or schedule a DL reception (e.g., CSI-RS, SSB, PDCCH, PDSCH, and / or the like) via symbol 1808 (e.g., via sub-band 1814 and / or sub-band 1818). Wireless device 1700 may determine link directionof symbol 1808 as DL based on configuration parameters 1708 (or another signal, e.g., MAC CE or DCI) indicating or scheduling a DL reception via symbol 1808.

[0283] In an example, configuration parameters 1708 may indicate symbol 1808 and / or symbol 1810 as SBFD symbols as follows: configuration parameters 1708 may indicate symbol 1808 and / or symbol 1810 as DL symbols (or LIL symbols or flexible symbols). Configuration parameters 1708 may comprise one or more configuration parameters for SBFD mode (e.g., SBFD-configuration, SBFD-DL-UL-configuration, and / or the like). The one or more configuration parameters for SBFD mode may indicate a sub-set of symbols configured by configuration parameters 1708 (as DL, UL, or flexible symbols) as SBFD symbols. For example, the one or more configuration parameters for SBFD mode may indicate symbol 1808 and / or symbol 1810 as SBFD symbols.

[0284] For example, configuration parameters 1708 may indicate symbol 1804, symbol 1806, symbol 1808, symbol 1810, and symbol 1812 as a DL symbol, a DL symbol, a DL symbol, a DL symbol, and a UL symbol, respectively. The one or more configuration parameters for SBFD mode may indicate symbol 1808 and symbol 1810 as SBFD symbols (e.g., based on indicating the one or more sub-bands for symbol 1808 and symbol 1810 or based on indicating at least one DL sub-band and / or at least one UL sub-band for symbol 1808 and symbol 1810). Symbol 1804 and symbol 1806 may be / remain DL symbols. Symbol 1812 may be / remain a UL symbol (e.g., after wireless device 1700 applies the one or more configuration parameters for SBFD mode).

[0285] The one or more sub-bands may comprise sub-band 1814, sub-band 1816, and sub-band 1818. Each of the one or more sub-bands may comprise one or more resource blocks (RBs). Each of the one or more RBs may be in (e.g., within, part of, associated with) the same carrier or BWP. For example, subband 1814, sub-band 1816, and sub-band 1818 may be in (e.g., within, part of, associated with) the same carrier or BWP.

[0286] Symbol 1808 may be for (e.g., configured with, associated with, of) DL operation and UL operation via (e.g., in, on, within, over) the same carrier / BWP. Symbol 1810 may be for (e.g., configured with, associated with, of) DL operation and UL operation via (e.g., in, on, within) the same carrier / BWP. For example, base station 1720 may transmit a first DL signal (e.g., to a first wireless device) via (e.g., in, on, within, over) symbol 1808 and receive a first UL signal (e.g., from a second wireless device) via (e.g., in, on, within) symbol 1808 via (e.g., in, on, within) in the same carrier or BWP (e.g., the first carrier / BWP). Base station 1720 may transmit a second DL signal (e.g., to a first wireless device) via (e.g., in, on, within) symbol 1810 and receive a second UL signal (e.g., from a second wireless device) via (e.g., in, on, within) symbol 1810 via (e.g., in, on, within) in the same carrier or BWP (e.g., the first carrier or BWP). For example, base station 1720 may transmit the second DL signal via (e.g., in, on, within, over) a sub-band 1814 within symbol 1810 and via (e.g., in, on, within, over) the first carrier / BWP; and receive the second ULsignal via (e.g., in, on, within, over) a sub-band 1816 within symbol 1810 and via (e.g., in, on, within, over) the first carrier / BWP.

[0287] Sub-band 1814 may comprise one or more first resource blocks (RBs). Sub-band 1816 may comprise one or more second RBs.

[0288] Symbol 1808 and symbol 1810 may be, for example, referred to as advanced duplexed or SBFD symbols. Sub-band 1814 may, for example, be referred to as a DL sub-band (e.g., within or of the first carrier / BWP and symbol 1808). Sub-band 1816 may, for example, be referred to as a UL sub-band (e.g., within or of the first carrier / BWP and the symbol 1808).

[0289] A DL sub-band may be a sub-band within (or of, for, associated with, or configured for) an SBFD symbol that is for (e.g., of, associated with, configured with, assigned with) DL operation. For example, the wireless device may receive DL signals via (e.g., on, in, within, over, using) DL sub-bands.

[0290] A UL sub-band may be a sub-band within (or of, for, associated with, or configured for) an SBFD symbol that is for (e.g., of, associated with, configured with, assigned with) for UL operation. For example, the wireless device may transmit UL signals via (e.g., on, in, within, over, using) UL sub-bands.

[0291] SBFD symbols may not be the same as flexible or flexible TDD symbols. For example, symbol 1808 and / or symbol 1810 may not be the same as (e.g., may be different from) flexible or flexible TDD symbols. Flexible (TDD) symbols are not configured or assigned (both) DL and UL for the same period of time / interval. Instead, flexible (TDD) symbols may be symbols that may be configured or assigned as DL symbols for some time period / interval and UL symbols for / at other time periods / intervals. Different from flexible TDD symbols, SBFD symbols may be for (e.g., of, associated with, configured with, assigned with) (both) UL and DL operation in / on / via a same carrier / BWP and at the same time interval / period. As an example, FIG. 18 illustrates that symbol 1808 is an SBFD symbol, which comprises a sub-band 1814 for (e.g., of, associated with, configured with, assigned with) for DL operation and a sub-band 1816 for (e.g., of, associated with, configured with, assigned with) UL operation. Base station 1720 may transmit and receive DL and UL signal(s), respectively, via a same SBFD symbol (e.g., symbol 1808). Base station 1720 may either transmit or receive DL or UL signal(s), respectively, (but not both) via a same flexible (TDD) symbol.

[0292] SBFD symbols may comprise one or more sub-bands. For example, SBFD symbols may comprise at least one DL sub-band and / or at least one UL sub-band (e.g., within the BWP / carrier). Flexible symbols may not comprise one or more sub-bands. For example, flexible symbols may not comprise DL sub-band and / or UL sub-band. For example, all of the BWP / carrier for (e.g., of, associated with, configured with, assigned with) the flexible symbol may be used only for either UL operation or DL operation.

[0293] Symbol 1804, symbol 1806, symbol 1808, symbol 1810, and symbol 1812 may for (e.g., of, associated with, configured with, assigned with) the same carrier / BWP (e.g., regardless of whether thesymbols are for (e.g., of, associated with, configured with, assigned with) DL operation, UL operation, and / or SBFD operation (e.g., both UL and DL operations)).

[0294] In some embodiments, “slot" and “symbol” may be used interchangeably. Actions, methods, operations, aspects, and / or features corresponding to a “symbol” described in the present disclosure may be applicable (e.g., in a similar manner or extended) to a “slot” (or vice versa).

[0295] In some embodiments, a wireless device transmitting a signal via (e.g., on, in, within, over, using) an SBFD symbol (e.g., symbol 1808) may comprise the wireless device transmitting the signal via (e.g., on, in, within, over, using) on an UL sub-band (e.g., sub-band 1816) of the SBFD symbol (e.g., symbol 1808).

[0296] In some embodiments, a wireless device receiving a signal via (e.g., on, in, within, over, using) an SBFD symbol (e.g., symbol 1808) may comprise the wireless device receiving the signal via (e.g., on, in, within, over, using) a DL sub-band (e.g., sub-band 1814) of the SBFD symbol (e.g., symbol 1808).

[0297] In some embodiments, “SBFD” may refer to advanced duplex, full duplex, partial full duplex, enhanced duplex, and / or the like.

[0298] In some embodiments, “flexible symbols" and “flexible TDD symbols” may be used interchangeably.

[0299] In some embodiments, SBFD may be different from full duplexing. Full duplexing may comprise fully or partially overlapping UL and DL sub-bands. For example, sub-band 1814 and sub-band 1816 may be partially or fully overlapping (in frequency) in full duplexing. There may be no sub-bands in full duplexing. For example, the entire BWP or band may be for both UL transmission and DL reception at all times. SBFD may face inter-band self-interference. On the other hand, full duplexing may face intra-band self-interference. Full-duplexing may be referred to as in-band full-duplexing.

[0300] In some embodiments, in SBFD, DL and UL sub-bands may not be overlapping. For example, the sub-band 1814 and the sub-band 1816 may not overlap (e.g., partially overlap and / or fully overlap).

[0301] In some embodiments, SBFD mode may be referred to as SBFD scheme, SBFD method, SBFD technique, SBFD operation, SBFD symbols, and / or any other description of communication via SBFD symbols.

[0302] SBFD operation may be, for example, within a (TDD) carrier. An SBFD symbol may comprise an RB or a set of (consecutive) RBs for a same transmission / link direction (e.g., UL or DL). An SBFD symbol may be a symbol with sub-bands that a base station (e.g., gNB) uses for SBFD operation.

[0303] In some embodiments, “carrier” may refer to “center frequency.”

[0304] SBFD scheme may be within a single configured DL and / or UL BWP pair with aligned center frequencies. There may be a maximum number of UL sub-bands for SBFD operation in an SBFD symbol within a TDD carrier. An UL sub-band may be located at one side of the carrier or may be located at the middle part of the TDD carrier.

[0305] SBFD operation may be on / for unpaired spectrum (e.g., similar to TDD operation).

[0306] In an example, for unpaired spectrum (e.g., TDD and / or SBFD operation), if a wireless device is not provided (e.g., receives message(s) 1706 that do not comprise) configuration parameters 1708 or the one or more configuration parameters for SBFD mode, a BRACH occasion in a BRACH slot may be valid if the BRACH occasion does not precede a SS / RBCH block in the BRACH slot and starts at least A / gap symbols after a last SS / RBCH block reception symbol, and, if channelAccessMode = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the wireless device does not transmit. Candidate SS / RBCH block index of the SS / RBCH block corresponds to the SS / RBCH block index indicated by the one or more configuration parameters. In some embodiments, BRACH occasion may be the same as or refer to valid BRACH occasion.

[0307] In an example, unpaired spectrum (e.g., TDD and / or SBFD operation), if a wireless device is provided (e.g., receives message(s) 1706 comprising) configuration parameters 1708 (e.g., tdd-UL-DL- ConfigurationCommon) and / or the one or more configuration parameters for SBFD mode, a BRACH occasion in a BRACH slot is valid if the BRACH occasion is within UL symbols / slots (e.g., symbol 1812); if the BRACH occasion is within UL sub-bands of / in / within SBFD symbols / slots (e.g., sub-band 1816 in symbol 1808 or the UL sub-bands in symbol 1810); and / or if the BRACH occasion does not precede a SS / RBCH block in a BRACH slot and starts at least A / gap symbols after a last DL / SBFD symbol and at least A / gap symbols after a last SS / RBCH block symbol.

[0308] A / gap may indicate a number of symbols / slots based on subcarrier spacing of RA preamble. For example, for subcarrier spacing of 1 .25 kHz or 5 kHz, 15 kHz or 30 kHz or 60 kHz or 120 kHz, 480 kHz, and 960 kHz, A / gap may be 0, 2, 8, 16, respectively. A / gap may be 0 for preamble format B4.

[0309] In some embodiments, UL sub-bands and / or DL sub-bands (within an SBFD symbol) may be referred to as SBFD sub-bands. For example, sub-band 1814, sub-band 1816, and / or sub-band 1818 may be referred to as SBFD sub-bands.

[0310] Message(s) 1710 may comprise one or more DL messages. Message(s) 1710 may comprise one or more UL messages.

[0311] In the example of FIG. 18, sub-band 1814 may comprise reception resources. The reception resources may occupy sub-band 1814. Sub-band 1816 may comprise transmission resources. The transmission resources may occupy sub-band 1816 that may be different from sub-band 1814. In the example of FIG. 18, the reception resources are in a higher frequency sub-band (e.g., sub-band 1814) than the transmission resources. However, it should be noted that the transmission resources may be in a lower frequency sub-band with respect to the reception resources. For example, sub-band 1816 may be a higher sub-band than a sub-band 1818. Sub-band 1816 may comprise transmission resources.

[0312] In some embodiments, reception resources or transmission resources may occupy more than one sub-band. For example, in FIG. 18, reception resources occupy sub-band 1814 and sub-band 1818. For example, sub-band 1814 and sub-band 1818 comprise reception resources.

[0313] In some embodiments, transmission resources may be separated from reception resources by a guard band. The guard band may be frequency resources, or a gap in frequency resources, provided between the transmission resources and the reception resources. Separating the transmission (frequency) resources and the reception (frequency) resources with a guard band may help to reduce self-interference. Transmission resources and reception resources that are immediately adjacent to each other (e.g., symbol 1808 comprising sub-band 1814 and sub-band 1816 that are adjacent) may be considered as having a guard band width of zero. As an output signal from a wireless device may extend outside the transmission resources, the guard band may reduce interference experienced by the wireless device.

[0314] In some embodiments, SBFD operation may be for a base station. For example, transmission resources may correspond to UL resources and reception resources may correspond to DL resources.

[0315] SBFD may be referred to as sub-band FDD and / or “flexible duplex.”

[0316] SBFD allows for simultaneous transmission and reception of DL and UL on a sub-band basis. A full duplex or SBFD base station may conduct simultaneous transmission and reception on the same symbol (e.g., symbol 1808). SBFD may increase UL duty cycle, which leads to latency reduction (e.g., it is possible to transmit UL signals in DL-only symbols, which may enable latency savings) and UL coverage improvement. It may be possible to receive DL signals in UL-only symbols. Additionally, SBFD may enhance system capacity, resource utilization and spectrum efficiency. SBFD may enable flexible and dynamic UL / DL resource adaptation or adaption according to UL / DL traffic in a robust manner.

[0317] In some embodiments, the wireless device may be / referred to as an SBFD-aware wireless device (or an SBFD-capable wireless device). An SBFD-aware wireless device may refer to a wireless device that supports receiving (or operating / functioning with) information (e.g., configuration parameters 1708 and / or the one or more configuration parameters for SBFD mode) about an SBFD mode of a device with which it is communicating, e.g., such as a network node / gNB / base station. By supporting receiving (or operating / functioning with) such information, the wireless device may be aware, e.g., may receive signaling indicating times when the base station will operate in SBFD mode, when to schedule UL transmission outside a UL sub-band, or when to schedule DL reception within a UL sub-band (e.g., receive the one or more configuration parameters of / for SBFD mode).

[0318] In some embodiments, the SBFD-aware wireless device, configured with a UL sub-band (e.g., subband 1816) in an SBFD symbol (e.g., symbol 1808), does not expect to be scheduled with UL transmission outside the UL sub-band (e.g., sub-band 1816) and does not expect to be scheduled with DL reception within the UL sub-band in an SBFD symbol. In some embodiments, methods and apparatus may be relatedto scenarios where an SBFD-aware wireless device, configured with a UL sub-band in an SBFD slot or symbol, does not expect to be scheduled with UL transmission outside the UL sub-band and may be scheduled with DL reception within the UL sub-band in an SBFD slot or symbol. In other embodiments, methods and apparatus may be related to scenarios where an SBFD-aware wireless device, configured with a UL sub-band in an SBFD slot or symbol, does not expect to be scheduled with DL reception within a UL sub-band and may be scheduled with UL transmission outside a UL sub-band in the SBFD slot or symbol. In some embodiments, a base station may indicate to the wireless device, e.g., via a DCI, that the wireless device is scheduled for DL reception in the UL sub-band or scheduled for UL transmission outside of the UL sub-band (e.g., in a DL sub-band). The dynamic scheduling may allow for more flexibility and resource utilization

[0319] In an example, wireless device 1700 may be an SBFD-aware wireless device (or the wireless device may be SBFD-aware) based on transmitting a capability message to base station 1720, wherein the capability message indicates that wireless device 1700 is capable of receiving / supporting SBFD- related / specific parameters (e.g., SBFD-related configurations, configuration parameters, the one or more configuration parameters for SBFD mode, and / or the like).

[0320] An SBFD symbol may be a symbol where a base station (and / or a wireless device) may perform both DL and UL operations (e.g., transmit and receive signals). An SBFD symbol may be a symbol that is associated with / for / of / configured for SBFD mode. An SBFD symbol may be a symbol which is configured with / associated with / indicated with one or more UL sub-bands (e.g., sub-band 1816) and / or one or more DL sub-bands (e.g., sub-band 1814, sub-band 1818). Symbol 1808 and symbol 1810 are examples of SBFD symbols.

[0321] A non-SBFD symbol may be a symbol where a base station (and / or a wireless device) may perform DL-only or UL-only operations (e.g., transmit but not receive, or receive but not transmit). A non- SBFD symbol may be a symbol that is associated with / for / of / configured for non-SBFD mode. Symbol 1804, symbol 1806, and symbol 1812 are examples of non-SBFD symbols. A flexible (TDD) symbol is an example of a non-SBFD symbol. DL symbol, UL symbol, and / or flexible TDD symbol are examples of non- SBFD symbols.

[0322] A non-SBFD symbol / mode may be (or comprise) a symbol / mode that is not indicated (e g., by message(s) 1706 and / or configuration parameters 1708) as an SBFD symbol / mode. Duplexing mode 1702 (e.g., TDD) and duplexing mode 1704 (e.g., FDD) are examples of non-SBFD modes. Flexible symbol is an example of a non-SBFD symbol.

[0323] In some embodiments, transmitting an RA preamble may be referred to as, for example, PRACH transmission. An RA preamble may, for example, be referred to as Msg1 , Message 1 , PRACH, PRACH transmission, RACH, RACH transmission, preamble, MsgA PRACH, MsgA preamble, and / or the like. Msg1 1311 is an example of an RA preamble. Msg A 1331 and / or preamble 1341 are examples of an RA preamble.

[0324] FIG. 19 illustrates an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 19 may be used together with or independently from any of the examples of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, and FIG. 18.

[0325] In the example of FIG. 19, a wireless device (e.g., wireless device 1700) receives message(s) 1902. Message(s) 1902 may be, for example, the same as message(s) 1706. Message(s) 1902 may, for example, comprise message(s) 1706.

[0326] Message(s) 1902 may comprise or indicate configuration parameters 1904. Configuration parameters 1904 may be, for example, the same as configuration parameters 1708. In an example, configuration parameters 1904 may comprise configuration parameters 1708.

[0327] In the example of FIG. 19, configuration parameters 1904 may be for or per a BWP (e.g., UL BWP) of the cell. The wireless device may transmit and / or receive one or more signals via the BWP.

[0328] Configuration parameters 1904 may comprise or indicate a set 1906 for BFD. Set 1906 may be for (e.g., of, used for, configured for) beam failure detection (BFD). Set 1906 may be referred to as, for example, BFD-RS set. Set 1906 may comprise or indicate one or more reference signals (RSs) that a wireless device monitors for BFD. For example, set 1906 may comprise or indicate one or more indexes that indicate or identify the one or more RSs.

[0329] In some embodiments, RS(s) may be or comprise one or more of: SSB(s); cell defined (CD) SSB(s); non-CD SSB(s); CSI-RS(s); CRS(s); SRS(s); PRS(s); TRS(s); pathloss RS(s); and / or any other reference signal(s) or pilot signal(s).

[0330] A wireless device may determine a beam failure instance based on a radio link quality of the one or more RSs indicated by set 1906. For example, the wireless device may determine (e.g., a physical layer of the wireless device may inform higher layers of the wireless device of) a beam failure instance based on the radio link quality being worse than (e.g., below, lower than, smaller than, less than) a radio link quality threshold. The radio link quality threshold may be, for example, referred to as Q_out,LR. In an example, configuration parameters 1904 may comprise or indicate the radio link quality threshold. For example, configuration parameters 1904 may comprise a field or parameter indicating the radio link quality threshold.

[0331] The wireless device may determine (e.g., declare, consider, assume, detect) beam failure (e.g., BFD) when a number of beam failure instances reaches (or exceeds) a threshold (e.g., beamFailurelnstanceMaxCounf) and before a timer (e.g., beamFailureDetectionTimer) expires or within an expiry of timer.

[0332] In an example, configuration parameters 1904 may comprise or indicate the threshold and / or the timer. For example, configuration parameters 1904 may comprise a respective field each indicating the threshold and / or the timer.

[0333] Determining beam failure may comprise, be referred to, or be the same as, BFD, detecting beam failure, declaring beam failure, considering beam failure, and / or assuming beam failure.

[0334] In an example, configuration parameters 1904 may comprise or indicate a set 1910 for BFD. Set 1910 may be different from set 1906. Set 1910 may be for BFD. Set 1910 may be referred to as, for example, BFD-RS set. Set 1910 may comprise or indicate one or more RSs that a wireless device monitors for BFD. Set 1910 may comprise or indicate one or more RSs for radio link monitoring (e.g., BFD). For example, set 1910 may comprise or indicate one or more indexes that indicate or identify the one or more RSs.

[0335] In an example, set 1910 may be for SBFD mode. For example, the one or more RSs indicated by set 1910 may be for SBFD mode (e.g., may be transmitted on SBFD symbols). For example, the one or more RSs indicated by set 1910 may be used by the wireless device to determine spatial filter for transmitting and / or receiving signals via SBFD symbols The one or more RSs indicated by set 1910 may be for determining BFD of RSs or beams associated with SBFD mode / symbols.

[0336] RS(s) or beam(s) being associated with SBFD mode or symbols may refer to a wireless device using the RS(s) or beam(s) to determine a spatial filter to transmit or receive signals via SBFD symbols.

[0337] In an example, configuration parameters 1904 may comprise or indicate set 1906 and / but not comprise / indicate set 1910. Set 1906 may comprise or indicate one or more RSs for BFD, e.g., for both SBFD and non-SBFD mode or symbols.

[0338] In an example, set 1906 may comprise or indicate set 1910.

[0339] In an example, configuration parameters 1904 may comprise or indicate a radio link monitoring configuration. The radio link monitoring configuration may comprise or indicate set 1906 and / or set 1910.

[0340] In an example, configuration parameters 1904 may comprise or indicate a field or parameter indicating with a single BFD-RS set is present, e.g., for both SBFD and non-SBFD modes, in configuration parameters 1904 or at least two BFD-RS sets are present, e.g., one each for SBFD and non-SBFD mode. For example, a first value (e.g., single, separate, 1 , 0, true, false, joint, and / or the like) of the field or parameter may indicate that a single BFD-RS set is present, e.g., for both SBFD and non-SBFD modes, in configuration parameters 1904. In response to the first value of the field or parameter, configuration parameters 1904 may comprise or indicate set 1906 but / and not set 1910. In another example, a second value (e.g., single, separate, 1 , 0, true, false, joint, and / or the like) of the field or parameter may indicate that at least two BFR-RS sets are present, e.g., one each for SBFD and non-SBFD mode, in configuration parameters 1904. In response to the second value of the field or parameter, configuration parameters 1904may comprise or indicate set 1906 (e.g., comprising one or more RSs for BFD-RS for non-SBFD mode) and set 1910 (e.g., comprising one or more RSs for BFD-RS for SBFD mode).

[0341] In an example, the wireless device may indicate whether the wireless device is capable of (e.g., supports or requests receiving) separate BFD-RS sets (e.g., the at least two BFD-RS sets), e.g., for SBFD and non-SBFD mode. For example, the wireless device may transmit a capability message (e.g., UE capability message), e.g., via PUSCH, indicating whether the wireless device is capable of (e.g., supports or requests receiving) separate BFD-RS sets (e.g., the at least two BFD-RS sets), e.g., for SBFD and non- SBFD mode. For example, the capability message may comprise a field or parameter indicating whether the wireless device is capable of (e.g., supports or requests) separate BFD-RS sets (e.g., the at least two BFD-RS sets), e.g., for SBFD and non-SBFD mode. A first value (e.g., single, separate, 1 , 0, true, false, joint, and / or the like) of the field or parameter may indicate that the wireless device is capable of (e.g., supports or requests receiving) separate BFD-RS sets (e.g., the at least two BFD-RS sets), e.g., for SBFD and non-SBFD mode. The wireless device may receive configuration parameters 1904 comprising or indicating set 1906 and set 1910 in response to transmitting the capability message comprising the field or parameter with the first value. A second value (e.g., single, separate, 1, 0, true, false, joint, and / or the like) of the field or parameter may indicate that the wireless device is not capable of (e.g., does not support or does not request receiving) separate BFD-RS sets (e.g., the at least two BFD-RS sets), e.g., for SBFD and non-SBFD mode. The wireless device may receive configuration parameters 1904 comprising or indicating set 1906 and / but not set 1910 in response to transmitting the capability message comprising the field or parameter with the second value.

[0342] In response to (or after) determining beam failure (e.g., in response to or after BFD), the wireless device may perform beam failure recovery (BFR). BFR may comprise determining a suitable beam. The wireless device may determine the suitable beam from one or more candidate RSs. For example, determining the suitable beam may comprise determining or selecting a candidate RS from one or more candidate RSs.

[0343] In an example, configuration parameters 1904 may comprise or indicate a configuration 1908. Configuration 1908 may comprise or indicate the one or more candidate RSs. For example, configuration 1908 may comprise or indicate one or more indexes that indicate or identify the one or more candidate RSs.

[0344] In an example embodiment, configuration parameters 1904 may comprise or indicate a configuration 1912. Configuration 1912 may comprise or indicate one or more second candidate RSs. For example, configuration 1912 may comprise or indicate indexes that indicate or identify the one or more second candidate RSs.

[0345] In an example, configuration 1908 may be associated with a first coreset pool index (e.g., a first TRP). For example, configuration parameters 1904 may comprise a parameter indicating the first coreset pool index (e.g., indicating that configuration 1908 is associated with the first coreset pool index) In an example, configuration 1912 may be associated with a second coreset pool index (e.g., a second TRP). For example, configuration parameters 1904 may comprise a parameter indicating the second coreset pool index (e.g., indicating that configuration 1908 is associated with the second coreset pool index).

[0346] In an example, configuration 1912 may be for SBFD mode and / or configuration 1908 may be for non-SBFD mode.

[0347] In another example, configuration 1908 may be for both SBFD and non-SBFD modes. For example, configuration 1908 may comprise or indicate one or more candidate RSs for both SBFD and non- SBFD modes (e.g., the one or more candidate RSs and the one or more second candidate RSs).

[0348] In an example, the one or more candidate RSs may comprise the one or more second candidate RSs.

[0349] In an example, configuration parameters 1904 may comprise or indicate configuration 1908 but / and not configuration 1912. Configuration 1908 may comprise or indicate one or more candidate RSs for both SBFD and non-SBFD modes, for example, based on configuration parameters 1904 comprising or indicating configuration 1908 but / and not configuration 1912.

[0350] In an example, configuration parameters 1904 may comprise a field (or parameter) that indicates whether a single BFD-RS set (e.g., set 1906) is present or at least two BFD-RS sets (e.g., set 1906 and set 1910) are present for non-SBFD and SBFD modes. For example, in response to the field being set to a first value (e.g., 1, true, yes, 0, false, no, separate, single, joint, and / or the like), configuration parameters 1904 may comprise or indicate a single BFD-RS set (e.g., set 1906) that indicates one or more RSs for BFD for both SBFD and non-SBFD modes. In another example, in response to the field being set to a second value (e.g , 1 , 0, true, false, yes, no, separate, single, joint, both, and / or the like) configuration parameters 1904 may indicate at least two BFD-RS sets (e.g., set 1906 and set 1910) that indicates one or more RSs for BFD for SBFD mode and one or more RSs for BFD for non-SBFD mode.

[0351] In an example, configuration parameters 1904 may comprise a field (or parameter) indicating whether a single configuration (e.g., configuration 1908), e.g., that indicates the one or more candidate RSs and the one or more second candidate RSs, is present or at least two configurations (e.g., configuration 1908 and configuration 1912), e.g., that each indicates the one or more candidate RSs and the one or more second candidate RSs, respectively, is present in configuration parameters 1904. For example, in response to the field being set to a first value (e.g., 1 , true, yes, 0, false, no, separate, single, joint, and / or the like), configuration parameters 1904 may comprise or indicate a single configuration (e.g , configuration 1908), e.g., that indicates both the one or more candidate RSs and the one or more second candidate RSs. Inanother example, in response to the field being set to a second value (e.g., 1 , true, yes, 0, false, no, separate, single, joint, and / or the like), configuration parameters 1904 may comprise or indicate at least two configurations (e.g., configuration 1908 and configuration 1912), e.g., that indicates the one or more candidate RSs and the one or more second candidate RSs, respectively.

[0352] In an example, configuration 1908 and / or configuration 1912 may be or comprise BFR configuration. For example, configuration 1908 and / or configuration 1912 may be BeamFailureRecoveryConfig, BeamFailureRecoveryRSConfig, CandidateBeamRS, and / or the like.

[0353] Configuration 1908 and / or configuration 1912 may each comprise or indicate: one or more random access (RA) resources; a value of the timer; and / or one or more candidate RSs.

[0354] As part of BFR, the wireless device may determine a suitable beam. A suitable beam may be referred to as, for example, a new beam.

[0355] As part of BFR, the wireless device may determine a candidate RS (e.g., the suitable beam) from the one or more candidate RSs and / or the one or more second candidate RSs.

[0356] In an example, the wireless device may determine beam failure in (e.g., on, of, for, or associated with) the cell.

[0357] In an example, the wireless device may determine beam failure in (e.g., on, of, for, or associated with) one or more BFD-RS sets (e.g., of the set 1906 and / or set 1910) of the cell.

[0358] In an example, the cell may be SpCell (e.g., PCell or a PSCell). The wireless device may perform an RA procedure, via the cell, for BFR (e.g., trigger BFR by performing the RA procedure via the cell), for example, in response to the cell being SpCell. In an example, the RA procedure may be contention-based RA procedure (CBRA). The wireless device may transmit a BFR MAC CE (e.g., the BFR MAC CE may indicate the candidate RS of the one or more candidate RSs and / or the one or more second candidate RSs) in response to the RA procedure being CBRA. A completion of the RA procedure may indicate a completion of BFR. For example, the wireless device may determine BFR to be complete based on completing the RA procedure.

[0359] In the example of FIG. 19, the wireless device may transmit a signal 1914. The wireless device may transmit signal 1914 for BFR. In an example, signal 1914 may be, for example, an RA preamble, Msg1 , Message 1 , PRACH, PRACH transmission, RACH, RACH transmission, preamble, MsgA PRACH, MsgA preamble, and / or the like.

[0360] In an example, the wireless device may transmit signal 1914 via PUCCH, PUSCH, and / or PRACH. Signal 1914 may be, for example, an SRS.

[0361] The wireless device may transmit signal 1914 for the RA procedure. The wireless device may perform the RA procedure for BFR. In an example, the wireless device may transmit signal 1914 using a spatial filter. The wireless device may perform the RA procedure via the cell.

[0362] The wireless device may transmit signal 1914 via a RACH occasion (RO).

[0363] In an example, the wireless device may determine the spatial filter based on the candidate RS of the one or more candidate RSs and / or the one or more second candidate RSs.

[0364] In another example, signal 1914 may be or comprise a Msg A or a Msg 3 (e.g., Msg A 1331 , Msg 3 1313). In an example, signal 1914 may comprise the BFR MAC CE.

[0365] The BFR MAC CE may comprise, for example, a truncated BFR MAC CE. The BFR MAC CE may indicate BFD for SpCell. For example, the BFR MAC CE comprise a field indicating BFR for SpCell. For example, the field may be set to 1 to indicate that beam failure is detected for SpCell when the BFR MAC CE is comprised in a MAC PDU as part of the RA procedure.

[0366] The BFR MAC CE may comprise a field indicating an index of the candidate RS of or from the one or more candidate RSs or the one or more second candidate RSs.

[0367] In an example, the wireless device may receive a signal 1916. Signal 1916 may indicate completion of BFR. For example, signal 1916 may indicate completion of the RA procedure. In an example, signal 1916 may be or comprise a PDCCH signal comprising a DCI. The DCI may be, for example, a DCI format with CRC scrambled by C-RNTI and / or MCS-C-RNTI. In another example, the DCI may schedule or indicate an uplink transmission with same HARQ process number as for a transmission of a first PUSCH with a toggled NDI field.

[0368] In an example, signal 1916 may comprise a random access response. Signal 1916 may correspond to signal 1914. For example, signal 1916 may comprise a preamble index that matches preamble index of signal 1914.

[0369] In an example, the wireless device may transmit a signal 1918. In an example as shown in FIG. 19, the wireless device may transmit signal 1918 via PUCCH. In an example, the wireless device may transmit signal 1918 via PUSCH. In an example, the wireless device may transmit signal 1918 via PRACH.

[0370] In an example, the wireless device may transmit signal 1918 via a transmission occasion. The transmission occasion may be PUSCH transmission occasion, PUCCH transmission occasion, RACH occasion (RO), and / or any other transmission occasion of or based on a channel over which the wireless device transmits signal 1918.

[0371] The wireless device may transmit signal 1918 after a number of symbols from the last symbol of signal 1916. In an example, the number of symbols may be 28. In an example, the number of symbols may correspond to two slots (e.g., for a sub-carrier spacing of 15 kHz).

[0372] In existing technologies, the wireless device may transmit signal 1918 using the spatial filter that the wireless device used to transmit signal 1914. Using a same spatial filter to transmit signal 1918 and signal 1914 may improve signal reliability since the wireless device knows that signal 1914 was successfully received by the base station (e.g., based on receiving signal 1916 corresponding to signal1914). However, this approach may not be suitable when using SBFD symbols For example, the wireless device may transmit signal 1914 via an RO that does not comprise any SBFD symbols and transmit the signal 1918 via a transmission occasion that may comprise one or more SBFD symbols. Using same spatial filters to transmit signal 1914 via the RO not comprising any SBFD symbols and to transmit signal 1918 via the transmission occasion comprising one or more SBFD symbols may be inefficient. This may be due to an increase in self-interference or cross link interference when using a spatial filter to transmit a signal via an SBFD symbol (e.g., symbol 1808 or symbol 1810), wherein the spatial filter may be designed (e.g., ideal, suitable, appropriate, or optimal) for non-SBFD symbols (e.g., UL only symbols like symbol 1812).

[0373] In light of the existing technologies, there is a need to improve spatial filter determination when transmitting signals via SBFD and / or non-SBFD symbols.

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

[0375] In an example embodiment, a wireless device transmits, via an RO, an RA preamble using a first spatial filter. The wireless device transmits, in a transmission occasion, an uplink signal using a second spatial filter, wherein: the second spatial filter is same as the first spatial filter in response both the transmission occasion and the RO comprising one or more SBFD symbols; and the second spatial filter is different from the spatial filter in response to only one of the transmission occasion and the RO comprising one or more SBFD symbols.

[0376] Using example embodiments of the present disclosure, the wireless device may transmit the RA preamble and the uplink using the same spatial filter (only) when both the RO and the transmission occasion comprise one or more SBFD symbols. As a result, the wireless device may use the correct (SBFD-based) spatial filter for transmitting the uplink signal. This may reduce self-interference, cross-link interference, and / or one or more signal failures and retransmissions. Using example embodiments of the present disclosure, the wireless device may transmit the RA preamble and the uplink using different spatial filters when only one of the RO or the transmission occasion comprises one or more SBFD symbols. As a result, the wireless device may not use a spatial filter suitable for SBFD symbols to transmit an uplink signal via a transmission occasion not comprising an SBFD symbol, or use a spatial filter suitable for non-SBFD symbols to transmit an uplink signal via a transmission occasion comprising one or more SBFD symbols. This may reduce self-interference, cross-link interference, and / or one or more signal failures and retransmissions.

[0377] FIG. 20 illustrates an example flow diagram as per an aspect of an embodiment of the present disclosure The example of FIG. 20 may be used together with any of the examples of FIG. 1A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG.10B, FIG. 11A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG. 18, and FIG. 19.

[0378] According to the example of FIG. 20, a wireless device may transmit signal 1914 via an RO. The wireless device may transmit signal 1914 to a base station. The wireless device may transmit signal 1914 via a cell. The wireless device may transmit signal 1914 via a BWP of the cell. The cell may be same as the cell described above in connection with any of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11A, FIG. 11 B, FIG.12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG. 18, and FIG. 19.

[0379] The wireless device may transmit signal 1914 via a BWP of the cell. The BWP may be the same as the BWP described above in connection with any of FIG. 1A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11A, FIG. 11 B, FIG.12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 130, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 160, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 170, FIG. 18, and FIG. 19.

[0380] The wireless device may transmit signal 1914 for (e.g., as part of) the RA procedure. The RA procedure may be for BFR.

[0381] The wireless device may transmit signal 1914 via an RO. For example, configuration parameters 1904, configuration 1908, and / or configuration 1912 may comprise or indicate the RO.

[0382] In an example, configuration parameters 1904 may indicate one or more RSs. The one or more RSs may be, for example, one or more SSBs, one or more CSI-RSs, and / or a combination thereof. The wireless device may determine (e.g., select, choose, pick, apply, use, and / or the like) an RS of the one or more RSs. The wireless device may determine the RS of the one or more RSs based on a radio link quality of the RS.

[0383] Radio link quality may be (or comprise), for example, reference signal received power (RSRP), reference signal received quality (RSRQ), channel state information (BLER), signal to noise ratio (SNR), block error rate (BLER), received signal strength indicator (RSSI), received signal power, and / or any other term that may indicate signal strength.

[0384] The wireless device may determine the RS based on the radio link quality of the RS being greater than (e.g., above, higher than, better than, more than, and / or the like) a power threshold. Configuration parameters 1904 may indicate the power threshold. The power threshold may be, for example, rsrp- ThresholdSSB. The power threshold may be, for example, an RSRP threshold. The power threshold may be for selecting an RS (e.g., SSB) for the RA procedure.

[0385] The wireless device may determine the RS for the RA procedure. In an example, configuration parameters 1904 may indicate an association between the RS and the RO. The wireless device maydetermine the RO based on determining the RS (or based on the RS). For example, configuration parameters 1904 may comprise a field indicating RO(s) associated with the RS in which the wireless device may transmit signal 1914. The RO(s) may comprise the RO. In an example, the field may be ra-ssb- OccasionMasklndex, ssb-SharedRO-Masklndex, msgA-SSB-SharedRO-Masklndex, ssb-perRACH- OccasionAndCB-PreamblesPerSSB, msgA-CB-PreamblesPerSSB-PerSharedRO, msgA-SSB-PerRACH- OccasionAndCB-PreamblesPerSSB, and / or ra-OccasionList. In an example, the field may define RO(s), on which preambles are allocated for a feature or a combination of features, associated with the RS in which the wireless device may transmit signal 1914. In an example, the field may indicate or define a number of RSs mapped to each RO and a number of contention-based RA preambles mapped to each RS.

[0386] In an example, signal 1914 may comprise one or more repetitions of an RA preamble. The wireless device may determine a number of repetitions of the RA preamble based on the radio link quality of the RS. For example, the wireless device may determine the number of repetitions based on a comparison of the radio link quality with one or more RSRP thresholds. The one or more RSRP thresholds may comprise, for example, rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and / or rsrp- ThresholdMsg1-RepetitionNum8. When signal 1914 comprises more than one repetitions of an RA preamble (e.g., when the number is greater than one), the wireless device may transmit signal 1914 via more than one ROs. For example, the more than one ROs may comprise the RO.

[0387] The wireless device may transmit signal 1914 using a spatial filter 2002. For example, spatial filter 2002 may be the spatial filter described above, e g., in connection to FIG. 19.

[0388] In an example, the wireless device may transmit signal 1918 via a transmission occasion. The transmission occasion may be the transmission occasion described above, e.g., in connection to FIG. 19.

[0389] In an example, configuration parameters 1904 may comprise or indicate the transmission occasion. For example, signal 1918 may comprise configured (UL) grant transmission. Configuration parameters 1904 may comprise or indicate a configured grant configuration that indicates the transmission occasion. In another example, the transmission occasion may be indicated by dynamic signaling (e.g., MAC CE or DCI). For example, the wireless device may receive a DCI indicating or scheduling transmission of signal 1918. The DCI may indicate the transmission occasion. For example, the DCI may comprise a field that indicates a pointer (e.g., codepoint or other type of pointer) to a configuration parameter (indicated by configuration parameters 1904) to determine the transmission occasion.

[0390] The wireless device may determine which spatial filter to use to transmit signal 1918 based on whether both the RO and the transmission occasion comprise one or more SBFD symbols (or only one of the RO and the transmission occasion comprise one or more SBFD symbols).

[0391] In an example, the RO may comprise one or more SBFD symbols. The transmission occasion may comprise one or more SBFD symbols. For example, the RO and the transmission occasion may both comprise one or more SBFD symbols (e.g., like symbol 1808 and symbol 1810).

[0392] The wireless device may transmit signal 1918 using spatial filter 2002 (e.g., same spatial filter used to transmit signal 1914) in response to both the RO and the transmission occasion comprising one or more SBFD symbols.

[0393] In an example, only one of the RO and the transmission occasion may comprise one or more SBFD symbols. For example, the RO may comprise one or more SBFD symbols and the transmission occasion may not comprise any SBFD symbols. For example, the transmission occasion may comprise one or more SBFD symbols and the RO may not comprise any SBFD symbols.

[0394] The wireless device may transmit signal 1918 using a spatial filter 2004 in response to (only) one of the RO and the transmission occasion comprising one or more SBFD symbols. For example, the wireless device may transmit signal 1918 using spatial filter 2004 in response to not both the RO and the transmission occasion comprising one or more SBFD symbols.

[0395] The wireless device may transmit signal 1918 using spatial filter 2004, for example, in response to the RO comprising one or more SBFD symbols and the transmission occasion not comprising one or more (or any) SBFD symbols. The wireless device may transmit signal 1918 using spatial filter 2004, for example, in response to the RO not comprising one or more (or any) SBFD symbols and the transmission occasion comprising one or more SBFD symbols.

[0396] In an example, spatial filter 2004 may be different from spatial filter 2002.

[0397] In some embodiments, spatial filter 2004 may be the same as spatial filter 2002.

[0398] In an example, the wireless device may determine spatial filter 2004 based on a TCI state indicated by a downlink control information (DCI). The TCI state indicated by the DCI may be referred to as, for example, an indicated TCI state or a current indicated TCI state. The TCI state may be the one indicated by a last (e.g., previous or most recent) DCI.

[0399] In an example, the DCI may schedule or indicate transmission of signal 1918.

[0400] In an example, configuration parameters 1904 may comprise or indicate a plurality of TCI states.The wireless device may receive an activation command (e.g., a TCI state activation / deactivation MAC CE) that activates one or more TCI states of the plurality of TCI states. For example, the activation command may indicate a mapping between one or more codepoints and the one or more TCI states. The DCI may indicate a TCI state, of the one or more TCI states, for example, based on indicating a codepoint, of the one or more codepoints, that corresponds to the TCI state. The DCI may indicate the codepoint based on comprising a field indicating the codepoint.

[0401] In an example, each TCI state, of the plurality of TCI states, may be associated with a TCI state ID of a plurality of TCI state IDs. For example, each TCI state ID, of the plurality of TCI state IDs may identify (e.g., indicate, be associated with, be configured for, or be linked to in any other way) a respective TCI state of the plurality of TCI states.

[0402] In an example embodiment, the wireless device may determine spatial filter 2004 based on a TCI state that is identified by a TCI state ID that is lowest (e.g., least, smallest, and / or the like) among the plurality of TCI state IDs.

[0403] In an example embodiment, the wireless device may determine spatial filter 2004 based on a TCI state that is identified by a TCI state ID that is highest (e.g., largest, biggest, greatest, most, and / or the like) among the plurality of TCI state IDs.

[0404] In an example embodiment, the wireless device may determine spatial filter 2004 based on a TCI state that is identified by a TCI state ID that is second lowest among the plurality of TCI state IDs.

[0405] In an example embodiment, the wireless device may determine spatial filter 2004 based on a TCI state that is identified by a TCI state ID that is second highest among the plurality of TCI state IDs.

[0406] In an example, the wireless device may determine spatial filter 2004 based on a TCI state, of the plurality of TCI states, that is indicated for SBFD mode.

[0407] In an example, the wireless device may determine spatial filter 2004 based on a TCI state, of the plurality of TCI states, that is indicated for non-SBFD mode.

[0408] In an example, configuration parameters 1904 (or a MAC-CE or DCI) may indicate which TCI state, of the plurality of TCI states, to use for transmitting signal 1914 when only one of the RO and the transmission occasion comprise one or more SBFD symbols. The wireless device determines spatial filter 2004 based on the TCI state, of the plurality of TCI states, indicated by configuration parameters 1904 (or the MAC CE or DCI).

[0409] In an example, the wireless device may receive message(s) 1902 and / or signal 1916 via the cell The wireless device may transmit signal 1914 and / or signal 1918 via the cell.

[0410] In an example, the wireless device may receive message(s) 1902 and / or signal 1916 via the BWP of cell. The wireless device may transmit signal 1914 and / or signal 1918 via the BWP of the cell.

[0411] In an example, the wireless device may initiate the RA procedure based on triggering BFR. The wireless device may initiate the RA procedure for BFR. The wireless device may initiate the RA procedure for BFR based on the cell being SpCell (e.g., PCell or PSCell).

[0412] In an example, the wireless device may trigger the RA procedure (for BFR) based on: detecting beam failure on both BFD-RS sets (e.g., set 1906 and set 1910); detecting beam failure on at least one BFD-RS set (e.g., set 1906 and / or set 1910); detecting beam failure on set 1906; detecting beam failure on set 1910; and / or the cell being SpCell.

[0413] FIG. 21 illustrates an example flow diagram as per an aspect of an embodiment of the present disclosure. The example of FIG. 21 may be used together with or independently from any of the examples of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11 A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG. 18, FIG. 19, and FIG. 20.

[0414] In the example of FIG. 21 , a wireless device receives message(s) 1902 comprising or indicating configuration parameters 1904. Configuration parameters 1904 may comprise or indicate set 1906 for BFD; configuration 1908; set 1910 for BFD; and / or configuration 1912. Set 1910 may be, for example, for BFD associated with SBFD mode. Configuration 1912 may be for SBFD mode. Set 1906 may be, for example, for BFD associated with non-SBFD mode. Configuration 1908 may be for non-SBFD mode.

[0415] In an example, the wireless device may detect beam failure. The wireless device may detect beam failure for set 1906; set 1910; and / or both set 1906 and set 1910.

[0416] In an example, the wireless device may detect beam failure for set 1906 (and not set 1910). The wireless device may trigger BFR for set 1906 using configuration 1908 based on detecting beam failure for set 1906 (e.g., only set 1906 and not set 1910).

[0417] In an example, the wireless device may detect beam failure for set 1910 (and not set 1906). The wireless device may trigger BFR for set 1910 using configuration 1912 based on detecting beam failure for set 1910 (e.g., only set 1910 and not set 1906).

[0418] In an example, the wireless device may detect beam failure for set 1906 and set 1910 (e.g., concurrently or simultaneously for both set 1906 and set 1910). The wireless device may perform step 2102 based on detecting beam failure for set 1906 and set 1910 (e.g., concurrently or simultaneously for both set 1906 and set 1910).

[0419] Step 2102 may comprise the wireless device triggering BFR for set 1906 Step 2102 may comprise the wireless device triggering BFR for set 1910. Step 2102 may comprise the wireless device triggering BFR for both set 1906 and set 1910 concurrently.

[0420] Step 2102 may comprise the wireless device triggering BFR for set 1906 and / or set 1910 using configuration 1908 and / or configuration 1912.

[0421] Step 2102 may comprise the wireless device initiating an RA procedure. The RA procedure may be same as any of the RA procedures described in connection with any of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11 A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG 17B, FIG. 17C, FIG. 18, FIG. 19, and FIG 20. The RA procedure may be for BFR.

[0422] Step 2102 may comprise the wireless device determining one or more RA resources to transmit an RA preamble for the RA procedure. In an example, configuration 1908 and / or configuration 1912 may indicate RA resources. Step 2102 may comprise the wireless device determining the one or more RA resources from the RA resources.

[0423] Step 2102 may comprise determining one or more RA resources from RA resources indicated by configuration 1908.

[0424] Step 2102 may comprise determining one or more RA resources from RA resources indicated by configuration 1912.

[0425] Step 2102 may comprise selecting (or determining) a candidate RS from the one or more candidate RSs (e.g., indicated by configuration 1908) and / or the one or more second candidate RSs (e.g., indicated by configuration 1912).

[0426] Step 2102 may comprise transmitting the RA preamble via the one or more RA resources. In an example, the one or more RA resources may comprise or indicate an index (e.g., preamble index) of the RA preamble. For example, the wireless device may transmit the RA preamble identified by or associated with the index. In an example, the one or more RA resources may indicate a subcarrier spacing (e.g., Msg1 -subcarrierspacing} for transmitting the RA preamble. For example, the wireless device may transmit the RA preamble with / using the subcarrier spacing. In an example, the one or more RA resources may comprise or indicate one or more ROs to transmit the RA preamble. For example, the wireless device may transmit the RA preamble via the one or more ROs The one or more ROs may be same as or comprise the RO described above in the examples of FIG. 19 and / or FIG. 20.

[0427] In some embodiments, triggering BFR for a set using a configuration may comprise the wireless device perform an RA procedure for BFR. For example, the wireless device may transmit an RA preamble for the RA procedure. The wireless device may transmit the RA preamble using one or more RA resources that are determined based on the configuration. For example, the configuration may indicate one or more ROs. The wireless device may transmit the RA preamble via the one or more ROs based on triggering BFR for the set using the configuration.

[0428] In some embodiments, triggering BFR for a set using a configuration may comprise the wireless device transmitting a BFR MAC CE comprising one or more indexes of one or more candidate RSs indicated by the configuration. For example, the configuration may indicate a plurality of candidate RSs. The wireless device may transmit the BFR MAC CE indicating one or more indexes of one or more candidate RSs from the plurality of candidate RSs (e.g., the one or more candidate RSs and / or the one or more second candidate RSs). Each index, of the one or more indexes, may correspond to or identify a respective candidate RS of the one or more candidate RSs. The wireless device may determine the one or more candidate RSs, from the plurality of candidate RSs, based on a radio link quality of each candidateRS, of the one or more candidate RSs, being above (e.g., greater than or higher than) a power threshold In an example, the configuration may indicate the power threshold. In another example, configuration parameters 1904 may indicate the power threshold.

[0429] Transmitting via a symbol may comprise transmitting on the symbol. Transmitting via a symbol may comprise transmitting in the symbol. Transmitting via a symbol may comprise transmitting during the symbol. Transmitting via a symbol may comprise transmitting using the symbol. Transmitting via a symbol may comprise transmitting based on the symbol.

[0430] Receiving via a symbol may comprise receiving on the symbol. Receiving via a symbol may comprise receiving in the symbol. Receiving via a symbol may comprise receiving during the symbol. Receiving via a symbol may comprise receiving using the symbol. Receiving via a symbol may comprise receiving based on the symbol.

[0431] A set (e.g., set of RSs) being for SBFD mode may comprise / refer to the set being of, for, associated with, or configured for SBFD mode.

[0432] In some embodiments, “SBFD mode” and “SBFD symbol(s)" may be used interchangeably. For example, based on the context, “SBFD mode” may be used in place of “SBFD symbol(s)” and vice versa.

[0433] In some embodiments, BFR may refer to a BFR procedure.

[0434] In some embodiments, “beam” and “RS" may mean the same and / or may be used interchangeably.

[0435] In some embodiments, beams / RSs being associated with SBFD mode / symbols may refer to the wireless device using the beams / RSs to transmit and / or receive signals via SBFD symbols. In some embodiments, beams / RSs being associated with SBFD mode / symbols may refer to the wireless device determining spatial filter(s) to transmit and / or receive signal via SBFD symbols.

[0436] In some embodiments, beams / RSs being associated with non-SBFD mode / symbols may refer to the wireless device using the beams / RSs to transmit and / or receive signals via non-SBFD symbols. In some embodiments, beams / RSs being associated with non-SBFD mode / symbols may refer to the wireless device determining spatial filter(s) to transmit and / or receive signal via non-SBFD symbols.

[0437] In some embodiments, spatial filter may refer to (or comprise, be the same as, be equivalent to, be identical to, and / or the like) spatial domain filter, spatial domain transmission filter, spatial domain reception filter, TX beam, RX beam, and / or any other parameter that may be used by the wireless device to determine directional / spatial relation / parameters for transmitting and / or receiving signals.

[0438] In some embodiments, a configuration being for SBFD mode may refer to a wireless device using parameter(s) indicated by the configuration for determining parameters for transmitting and / or receiving signals via SBFD symbols. For example, a configuration for SBFD mode may indicate an RS. The wirelessdevice may use the RS to determine a spatial filter for transmitting (or receiving) a signal via an SBFD symbol.

[0439] In some embodiments, a configuration being for non-SBFD mode may refer to a wireless device using parameter(s) indicated by the configuration for determining parameters for transmitting and / or receiving signals via non-SBFD symbols. For example, a configuration for non-SBFD mode may indicate an RS. The wireless device may use the RS to determine a spatial filter for transmitting (or receiving) a signal via a non-SBFD symbol.

[0440] In some embodiments, RA resource(s) may comprise or indicate: root sequence index, e.g., for generating an RA preamble; RA channel (RACH) configuration; one or more power thresholds for determining an RS for an RA procedure; one or more RACH occasions (ROs); one or more mapping between one or more RSs and the one or more ROs; one or more RA prioritization values; one or more sub-carrier spacing values for Msg 1 or RA preamble transmission; and / or any other parameters required by the wireless device to perform and / or complete the RA procedure.

[0441] In some embodiments, transmitting or receiving a signal using a spatial filter may be the same as transmitting or receiving the signal based on / with / via the spatial filter.

[0442] In some embodiments, radio link monitoring may comprise BFD.

[0443] In some embodiments, BFD may comprise radio link monitoring.

[0444] In some embodiments, determining a spatial filter based on an RS may comprise using beam correspondence to determine the spatial filter using / based on the RS. For example, the RS may indicate a spatial direction / relation or beam. The wireless device may use a reception beam or a spatial domain reception filter to receive the RS. The wireless device may use beam correspondence to determine a spatial filter (e.g., spatial domain transmission filter) using the reception beam or the spatial domain reception filter.

[0445] In some embodiments, transmitting a signal via a cell may refer to (or be the same as) transmitting the signal on, in, to, toward, for, or within the cell.

[0446] In some embodiments, receiving a signal via a cell may refer to (or be the same as) receiving the signal on, in, to, toward, for, or within the cell.

[0447] In some embodiments, transmitting a signal via a BWP may refer to (or be the same as) transmitting the signal in, on, within, to, for, or with the BWP (e.g., using one or more resources that are within the BWP).

[0448] In some embodiments, receiving a signal via a BWP may refer to (or be the same as) receiving the signal in, on, within, to, for, or with the BWP (e.g., using one or more resources that are within the BWP).

[0449] In some embodiments, RO may refer to PRACH occasion, RA occasion, RA transmission resource, RA resource, RB, time resource for transmitting RA preamble, frequency resource for transmitting RA preamble, time and / or frequency resource for transmitting RA preamble, and / or the like.

[0450] In some embodiments, detecting beam failure on a BFD-RS set and detecting beam failure for the BFD-RS set may mean or refer to the same.

[0451] In some embodiments, detecting beam failure on a BFD-RS set may comprise detecting beam failure using one or more radio link qualities of one or more RSs comprised or indicated by the BFD-RS set. For example, detecting beam failure on set 1906 may comprise determining or detecting a number of beam failure instances to be greater than or equal to a threshold, e.g., wherein beam failure instance is determined based on the one or more radio link qualities being less than or equal to a radio link quality (e.g., power or RSRP) threshold.

[0452] In some embodiments, detecting beam failure may comprise determining beam failure, considering beam failure, assuming beam failure, and / or the like.

[0453] In some embodiments, determining beam failure, considering beam failure, assuming beam failure, detecting beam failure, beam failure detection (BFD), and / or other terms / phrases that refer to a wireless device and / or a base station determining beam failure may be used interchangeably.

[0454] In some embodiments, initiating an RA procedure may comprise: triggering the RA procedure; starting the RA procedure; completing the RA procedure; performing the RA procedure; requesting to perform the RA procedure; indicating to a base station to perform the RA procedure; receiving an indicating to perform the RA procedure (e.g., PDCCH order, DCI, and / or any other control command that may indicate the RA procedure or an RA preamble for the RA procedure); and / or the like.

[0455] In some embodiments, performing an RA procedure via a cell may be the same as performing the RA procedure for, on, to, associated with, over, and / or in the cell.

[0456] In some embodiments, transmitting a signal via an RO may comprise, be the same as, or be referred to as transmitting the signal on, in, over, with, using, based on, or at the RO.

[0457] In some embodiments, a BFD-RS set may be referred to as failure detection set, radio link monitoring set, and / or any other set indicating or comprising RSs to monitor for detecting radio link or beam failure.

[0458] In some embodiments, determining beam failure for a set (e.g., set 1906 and / or set 1910) indicated by configuration parameters (e.g., configuration parameters 1904) of a cell may comprise, indicate, be referred to, or be the same as determining beam failure in (e.g., on, of, for, or associated with) the cell.

[0459] In some embodiments, transmitting a signal using a spatial filter may be the same as transmitting the signal with, based on, or from the spatial filter.

[0460] An example method comprising: transmitting, by a wireless device and via / on a first random access channel (RACH) occasion (RO), a random access (RA) preamble using a first spatial filter; and transmitting, in a transmission occasion, an uplink signal using a second spatial filter, wherein: the second spatial filter is same as the first spatial filter in response to both the transmission occasion and the RO comprising one or more sub-band full-duplex (SBFD) symbols; and the second spatial filter is different from the first spatial filter in response to only one of the transmission occasion and the RO comprising one or more SBFD symbols.

[0461] The above example method, can, in another example method, further comprise receiving one or more messages.

[0462] One or more of the above example methods, wherein the one or more messages are one of: one or more RRC messages; and / or one or more system information messages.

[0463] One or more of the above example methods, wherein the one or more messages indicate one or more configuration parameters.

[0464] One or more of the above example methods, wherein the one or more configuration parameters are one or more radio resource control (RRC) configuration parameters.

[0465] One or more of the above example methods, wherein receiving the one or more messages is via a base station.

[0466] One or more of the above example methods, wherein transmitting the RA preamble is to the base station.

[0467] One or more of the above example methods, wherein transmitting the uplink signal is to the base station.

[0468] One or more of the above example methods, wherein the base station is: a gNB; a gNB-CU; a gNB-DU; a satellite; an IAM mode; an NCR; and / or an NTN payload.

[0469] One or more of the above example methods, wherein the one or more configuration parameters is for / of a cell.

[0470] One or more of the above example methods, wherein transmitting the RA preamble is via the cell.

[0471] One or more of the above example methods, wherein transmitting the uplink signal is via the cell.

[0472] One or more of the above example methods, wherein the cell is: a serving cell; a primary cell; a secondary cell; a special cell; a primary secondary cell; an NTN cell; an LTM candidate cell; and / or a nonserving cell.

[0473] One or more of the above example methods, wherein the one or more configuration parameters indicate: a first set of RSs for determining (or detecting) beam failure; and / or a second set of RSs for determining beam failure.

[0474] One or more of the above example methods, wherein: the first set of RSs is associated with non- SBFD mode; and the second set of RSs is associated with SBFD mode.

[0475] One or more of the above example methods, further comprising determining beam failure based on monitoring one or more reference signals from: the first set of RSs; and / or the second set of RSs.

[0476] One or more of the above example methods, wherein the one or more configuration parameters indicate a single set of RSs for determining beam failure.

[0477] One or more of the above example methods, wherein the single set of RSs is associated with: SBFD mode; and non-SBFD mode.

[0478] One or more of the above example methods, further comprising determining beam failure based on monitoring one or more RSs from the single set of RSs.

[0479] One or more of the above example methods, wherein the one or more configuration parameters indicate: a first set of candidate RSs for BFR; and a second set of candidate RSs for BFR.

[0480] One or more of the above example methods, wherein the first set of candidate RSs is associated with a first coreset pool index; and the second set of candidate RSs is associated with a second coreset pool index

[0481] One or more of the above example methods, further comprising selecting an RS from: the first set of candidate RSs; and / or the second set of candidate RSs.

[0482] One or more of the above example methods, further comprising selecting the RS from: the first set of candidate RSs in response to determining beam failure using the first set of RSs for determining beam failure; and the second set of candidate RSs in response to determining beam failure using the second set of RSs for determining beam failure.

[0483] One or more of the above example methods, wherein the RACH occasion is associated with the RS.

[0484] One or more of the above example methods, wherein the one or more configuration parameters indicate the association between the RS and the RACH occasion.

[0485] One or more of the above example methods, wherein the one or more configuration parameters indicate an association between the RS and the RA preamble.

[0486] One or more of the above example methods, wherein transmitting the RA preamble is for an RA procedure.

[0487] One or more of the above example methods, wherein the RA procedure is for beam failure recovery.

[0488] One or more of the above example methods, further comprising receiving a downlink signal indicating completion of beam failure recovery.

[0489] One or more of the above example methods, wherein the downlink signal is at least one of: a physical downlink control channel (PDCCH) reception comprising downlink control information (DCI) format with cyclic redundancy check (CRC) scrambled by C-RNTI and / or MCS-C-RNTI; a PDCCH reception that indicates completion of the RA procedure; and / or a PDCCH reception with a DCI format scheduling an uplink transmission with a same HARQ process number as for a transmission of a first PUSCH and having a toggled NDI field value.

[0490] One or more of the above example methods, wherein the transmitting the uplink signal is after a first number of symbols from a last symbol of the downlink signal.

[0491] One or more of the above example methods, wherein the first number of symbols is 28.

[0492] One or more of the above example methods, wherein a subcarrier spacing configuration for determining the first number of symbols is a smallest of SCS configurations of an active downlink BWP for receiving the downlink signal and of active BWPs of serving cells.

[0493] One or more of the above example methods, wherein the one or more configuration parameters indicate: a first set of RA resources; and a second set of RA resources for SBFD mode.

[0494] One or more of the above example methods, wherein a single RA configuration indicates: the first set of RA resources; and the second set of RA resources.

[0495] One or more of the above example methods, wherein: a first RA configuration indicates the first set of RA resources; and a second RA configuration indicates the second set of RA resources.

[0496] One or more of the above example methods, wherein the first RA configuration and the second RA configuration are not simultaneously enabled.

[0497] One or more of the above example methods, further comprising determining the RO based on: the first set of RA resources in response to determining beam failure using the first set of RSs for determining beam failure; and the second set of RA resources in response to determining beam failure using the second set of RSs for determining beam failure.

[0498] One or more of the above example methods, wherein the second filter is determined based on the RS in response to only one of the transmission occasion and the RO comprising one or more SBFD symbols.

[0499] One or more of the above example methods, wherein the one or more configuration parameters indicate association between the second filter and the RS.

[0500] One or more of the above example methods, wherein the one or more configuration parameters indicate plurality of TCI states.

[0501] One or more of the above example methods, wherein the second filter is determined based on a first TCI state of the plurality of TCI states.

[0502] One or more of the above example methods, wherein the first TCI state is associated with SBFD mode.

[0503] One or more of the above example methods, wherein the first TCI state is identified by a lowest TCI state ID among a plurality of TCI state IDs identifying the plurality of TCI states.

[0504] One or more of the above example methods, wherein the first TCI state is identified by a second lowest TCI state ID among a plurality of TCI state IDs identifying the plurality of TCI states.

[0505] One or more of the above example methods, wherein the first TCI state is a current / indicated TCI state.

[0506] One or more of the above example methods, wherein a control command indicates the first TCI state.

[0507] One or more of the above example methods, wherein the control command is: a downlink control information (DCI); or a MAC CE.

[0508] FIG. 22 shows an example of a network-controlled repeater communicating with a base station and a wireless device as per an aspect of an embodiment of the present disclosure. The network-controlled repeater (NCR) may be a repeater that enables wireless amplifying-and-forwarding functionality. The NCR may be capable of receiving and applying side control information from a base station. The base station may be a gNB. For example, the base station may be a gNB-centralized unit (CU) and / or a gNB-distributed unit (DU). The base station may be, for example, the same base station as described in connection with any of FIG. 1A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG.8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11 A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG. 18, FIG. 19, FIG. 20, and FIG. 21.

[0509] The NCR may comprise an NCR mobile termination (NCR-MT). The NCR may comprise an NCR forwarding or RF forwarding (NCR-Fwd). The NCR-MT may communicate with the base station to receive side control information via a control link.

[0510] The NCR-Fwd may perform amplifying-and-forwarding of signals between the base station and a wireless device via an NCR-Fwd backhaul link and an NCR-Fwd access link, respectively.

[0511] In some embodiments, NCR-Fwd backhaul link may be referred to as backhaul link. In some embodiments, NCR-Fwd access link may be referred to as access link.

[0512] The NCR-Fwd may support multiple beams towards the wireless device. The NCR-Fwd may support multiple beams in the NCR-Fwd backhaul link, and the multiple beams may be different from beams in the control link. The behavior of the NCR-Fwd may be controlled according to the side control information received from the base station.

[0513] An NCR-MT may establish SRBs and, optionally, DRB(s) with the base station. The establishment of DRB(s) may be used to transport 0AM traffic.

[0514] A signal that the NCR-Fwd forwards may be associated to a cell that the NCR-MT is connected to via the control link. The NCR-Fwd may forward other signals to the wireless device. The cell may be the same as the cell described above in any of the examples of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11 A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG. 18, FIG. 19, FIG. 20, and FIG. 21.

[0515] An NCR may be the same as or comprise any of the wireless devices described in the examples of FIG 1A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG. 18, FIG. 19, FIG. 20, and FIG. 21.

[0516] RRC signaling (e.g., message(s) 1902, message(s) 1706) may be utilized to configure the NCR- MT to receive side control information from the base station The RRC signaling may be used by the NCR- Fwd to determine whether and how to amplify-and-forward RF signals. If the side control configuration is removed, the NCR-Fwd may cease its amplifying-and-forwarding function.

[0517] The base station may transmit a MAC CE to the NCR to configure the NCR-Fwd backhaul link and the NCR-Fwd access link of the NCR-Fwd.

[0518] When the NCR-MT is in RRC_CONNECTED state, the NCR-Fwd may amplify-and-forward RF signals based on the side control information received from the base station.

[0519] When the NCR-MT transitions from RRC_CONNECTED state to RRCJNACTIVE state, the NCR- Fwd may continue to amplify-and-forward RF signals in accordance with a last side control information received from the base station. When the NCR-MT is in RRCJNACTIVE state, the NCR-Fwd may cease to amplify-and-forward RF signals if no suitable cell is detected, or if the NCR-MT selects a different cell than the last serving cell on which side control configuration was received.

[0520] When the NCR-MT in RRCJNACTIVE state determines degradation of the NCR-Fwd backhaul link beam, then the NCR-Fwd may cease amplifying-and-forwarding RF signals, and the NCR-MT may attempt to resume its RRC connection (with cause value mo-Signalling).

[0521] When the NCR-MT transitions from RRC_CONNECTED state to RRCJDLE, the NCR-Fwd may cease any amplifying-and-forwarding of RF signals.

[0522] The NCR-MT may detect RLF on the control link. When RLF is detected, the NCR-MT may perform an RRC re-establishment procedure. During the RRC re-establishment procedure, the NCR-Fwd may cease to amplify-and-forward RF signals. After successfully performing the RRC re-establishmentprocedure, the NCR-MT waits for new side control configuration for the NCR-Fwd to resume the amplifying- and-forwarding of RF signals.

[0523] The NCR-MT may perform Beam Failure Detection (BFD) and Beam Failure Recovery (BFR), e.g., as described in FIGs. 19-21. Once the NCR-MT detects beam failure in the control link, the NCR-Fwd may cease amplifying-and-forwarding RF signals until BFR is completed.

[0524] The NCR-Fwd may transmit or receive after the NCR-MT receives on the control link an indication for one or more beams for the NCR-Fwd to use for transmissions or receptions over corresponding one or more time resources on the NCR-Fwd access link. A timing for transmission and reception by the NCR-Fwd on the NCR-Fwd backhaul link may follow a frame timing for transmission and reception, respectively, by the NCR-MT.

[0525] When the NCR-MT performs a link recovery procedure (e.g., BFR, radio link failure recovery, and / or the like), the NCR-Fwd may not transmit or receive until the link recovery procedure is complete.

[0526] The NCR may be provided, through the NCR-MT, tdd-UL-DL-ConfigurationCommon (e.g., configuration parameters 1708) and may be additionally provided tdd-UL-DL-ConfigurationDedicated. The NCR-Fwd may receive on the NCR-Fwd backhaul link or may transmit on the NCR-Fwd access link in symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL- ConfigurationDedicated. The NCR-Fwd may receive on the access link or transmit on the backhaul link in symbols indicated as uplink by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL- ConfigurationDedicated.

[0527] If the NCR does not support simultaneous transmissions on control link and the NCR-Fwd backhaul link, the NCR-Fwd does not transmit over a time resource if the NCR-MT transmits over the time resource.

[0528] When the NCR simultaneously receives via both the control link and the NCR-Fwd backhaul link in a set of symbols, a TCI state for receptions on the NCR-Fwd backhaul link may be same as a TCI state for receptions on the control link in the set of symbols. When the NCR simultaneously transmits via both the control link and the NCR-Fwd backhaul link in a set of symbols, a spatial filter for transmissions on the NCR-Fwd backhaul link may be same as a spatial filter for transmissions on the control link in the set of symbols.

[0529] FIG. 23 shows an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 23 may be used together with or independently from any of the examples of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11 A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG 18, FIG. 19, FIG. 20, and FIG. 21 , and FIG. 22.

[0530] In the example of FIG. 23, an NCR receives configuration parameters (e.g configuration parameters 1708, configuration parameters 1904) from a base station. The configuration parameters indicate a plurality of symbols. In the example of FIG. 23, the plurality of symbols comprises a symbol 2302, a symbol 2304, a symbol 2306, a symbol 2308, and a symbol 2310. The configuration parameters may comprise one or more configuration parameters for SBFD mode. The configuration parameters and / or the one or more configuration parameters for SBFD mode may indicate symbol 2302, symbol 2304, symbol 2306, symbol 2308, and symbol 2310 as DL, DL, SBFD, SBFD, and UL symbols, respectively.

[0531] Symbol 2302, symbol 2304, symbol 2306, symbol 2308, and symbol 2310 may be the same as, for example, symbol 1804, symbol 1806, symbol 1808, symbol 1810, and symbol 1812, respectively.

[0532] Symbol 2302, symbol 2304, symbol 2306, symbol 2308, and symbol 2310 may be for control and / or NCR-Fwd backhaul link. For example, the configuration parameters and / or the one or more configuration parameters for SBFD mode may indicate symbol 2302, symbol 2304, symbol 2306, symbol 2308, and symbol 2310 for the control and / or NCR-Fwd backhaul link. For example, the NCR may communicate with the base station via symbol 2302, symbol 2304, symbol 2306, symbol 2308, and / or symbol 2310.

[0533] The plurality of symbols may comprise a symbol 2312, symbol 2314, a symbol 2316, a symbol 2318, and a symbol 2320. The configuration parameters and / or the one or more configuration parameters for SBFD mode may indicate symbol 2312, symbol 2314, symbol 2316, symbol 2318, and symbol 2320 for the NCR-Fwd access link. For example, the NCR may communicate with a wireless device via symbol 2312, symbol 2314, symbol 2316, symbol 2318, and / or symbol 2320.

[0534] Symbol 2312, symbol 2314, symbol 2316, symbol 2318, and symbol 2320 may be the same as, for example, symbol 1804, symbol 1806, symbol 1808, symbol 1810, and symbol 1812, respectively.

[0535] In an example, the configuration parameters and / or one or more configuration parameters for SBFD mode may indicate symbol 2312, symbol 2314, symbol 2316, symbol 2318, and symbol 2320 as DL, DL, SBFD, SBFD, and UL symbols, respectively.

[0536] The NCR may receive via the control and / or the NCR-Fwd backhaul link via DL symbols or DL subbands of SBFD symbols (e.g., symbol 2302, symbol 2304, DL sub-bands of symbol 2306, or DL sub-band of symbol 2308). The wireless device may transmit via the control and / or NCR-Fwd backhaul link via UL symbols or UL sub-bands of SBFD symbols (e.g., UL sub-band of symbol 2306, UL sub-band of symbol 2308, or symbol 2310).

[0537] In the implementation of existing technologies, the NCR may transmit on the NCR-Fwd access link via DL symbols or DL sub-bands of SBFD symbols (e.g., symbol 2312, symbol 2314, DL sub-bands of symbol 2316, or DL sub-band of symbol 2318) and receive on the NCR-Fwd access link via UL symbols orUL sub-bands of SBFD symbols (e.g., UL sub-band of symbol 2316, UL sub-bands of symbol 2318, or symbol 2320).

[0538] The implementation of existing technologies may be suitable when both the NCR and the wireless device are SBFD-aware. However, when the wireless device is not SBFD-aware (e.g., does not support or is not capable of receiving SBFD-related configuration parameters like the one or more configuration parameters for SBFD mode), the wireless device may not be able to receive data via DL sub-bands of SBFD symbols (e.g., DL sub-bands of symbol 2316 or DL sub-band of symbol 2318). This may be due to the configuration parameters indicating symbol 2316 and symbol 2318 as UL symbols and the one or more configuration parameters for SBFD mode (which the wireless device did not receive) indicating symbol 2316 and symbol 2318 as SBFD symbols. As a result, the wireless device may determine (e.g., consider or treat) symbol 2316 and symbol 2318 as UL symbols and may not receive DL signals via symbol 2316 and symbol 2318. Not receiving the DL signals may result in increased network latency, one or more retransmissions of the DL signals resulting in increased power consumption at the wireless device and / or the NCR, and / or reduction in battery life of the wireless device and / or the NCR.

[0539] In light of the existing technologies, there is a need to improve communications via an NCR-Fwd access link when an NCR is an SBFD-aware wireless device.

[0540] In an example embodiment, an NCR receives configuration parameters indicating a first symbol as SBFD symbol, wherein the first symbol comprises a DL sub-band; and a UL sub-band; and a second symbol as a DL symbol. The NCR receives, from a base station, a signal to forward to a wireless device. The wireless device forwards, to the wireless device and via an NCR-Fwd access link, the signal via / on: the DL sub-band of the first symbol in response to the wireless device being SBFD-aware; and the second symbol in response to the wireless device not being SBFD-aware.

[0541] Example embodiments may reduce instances of a wireless device not receiving a signal due to a misunderstanding of a symbol type. Using example embodiments an NCR transmits / forwards DL signals via DL sub-bands of SBFD symbols via an NCR-Fwd access link to a wireless device, if the wireless device is SBFD-aware. As a result, the wireless device may receive the DL signals.

[0542] FIG. 24 shows an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 24 may be used together with or independently from any of the examples of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11 A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG. 17C, FIG. 18, FIG. 19, FIG. 20, FIG. 21 , FIG. 22, and FIG. 23.

[0543] In the example of FIG. 24, an NCR receives a signal from a base station. The NCR may receive the signal, from the base station, to forward to a wireless device. In an example, the NCR may receive thesignal to forward to a wireless device 2400, e.g., via an NCR-Fwd access link 2402. In an example, the NCR may receive the signal to forward to a wireless device 2410, e.g., via an NCR-Fwd access link 2404.

[0544] In an example, the NCR may receive the signal from a base station via a DL symbol (e.g., symbol 2302, symbol 2304) or a DL sub-band of an SBFD symbol (e.g., symbol 2306, symbol 2308).

[0545] In an example, the NCR may determine which (type of) symbol (e.g., DL symbol, LIL symbol, or SBFD symbol) to forward the signal to a wireless device based on whether the wireless device is SBFD- aware.

[0546] In the example of FIG. 24, wireless device 2400 may be SBFD-aware. For example, wireless device 2400 may be capable of (or support) receiving (or receive) SBFD-related configuration parameters (e.g , the one or more configuration parameters for SBFD mode).

[0547] In the example of FIG. 24, wireless device 2410 may not be SBFD-aware. For example, wireless device 2410 may not be capable of (or support) receiving (or may not receive) SBFD-related configuration parameters (e.g., the one or more configuration parameters for SBFD mode). In another example, wireless device 2410 may not be SBFD-aware based on not (yet) receiving SBFD-related configuration parameters (e.g , the one or more configuration parameters for SBFD mode). The wireless device 2410 may be or become SBFD-aware in response to or after receiving SBFD-related configuration parameters (e.g., the one or more configuration parameters for SBFD mode).

[0548] The NCR may forward the signal to wireless device 2400 on NCR-Fwd access link 2402 and via DL sub-band(s) of SBFD symbol(s) (e.g., symbol 2316 or symbol 2318) in response to wireless device 2400 being SBFD-aware.

[0549] The NCR may forward the signal to wireless device 2410 on NCR-Fwd access link 2404 and via DL symbol(s) (e.g., symbol 2312 or symbol 2314) in response to wireless device 2410 not being SBFD- aware.

[0550] FIG. 25 shows an example as per an aspect of an embodiment of the present disclosure. The example of FIG. 25 may be used together with or independently from the examples of FIG. 1 A, FIG. 1 B, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4A, FIG. 4B, FIG. 5A, FIG. 5B, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10A, FIG. 10B, FIG. 11A, FIG. 11 B, FIG. 12A, FIG. 12B, FIG. 13A, FIG. 13B, FIG. 13C, FIG. 14A, FIG. 14B, FIG. 15, FIG 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 17A, FIG. 17B, FIG 17C, FIG. 18, FIG 19, FIG. 20, FIG. 21 , FIG. 22, FIG. 23, and FIG. 24.

[0551] In the example of FIG. 25, an NCR receives configuration 2502 from a base station. For example, configuration parameters 1708 may comprise configuration 2502. In an example, configuration 2502 may comprise configuration parameters 1708. Configuration 2502 may indicate, for example, five symbols as DL, UL, or flexible symbols. In the example of FIG. 25, configuration 2502 may indicate the first four symbols as DL (or flexible) symbols and the fifth symbol as UL symbol.

[0552] In an example, configuration parameters 1708 may indicate a pattern of DL (or flexible) and UL symbols. In the example of FIG. 25, the pattern may indicate that first four symbols are DL (or flexible) symbols and fifth symbol as UL symbol. As a result, configuration 2502 may indicate first symbol, second symbol, third symbol, fourth symbol, fifth symbol, of the five symbols, as DL (or flexible) symbol, DL (or flexible) symbol, DL (or flexible) symbol, DL (or flexible) symbol, and UL symbol, respectively.

[0553] The NCR may receive configuration 2504. Configuration 2504 may comprise the one or more configuration parameters for SBFD mode. The one or more configuration parameters for SBFD mode may indicate the third and the fourth symbol, of the five symbols, as SBFD symbol. The one or more configuration parameters for SBFD mode may indicate a pattern for / of SBFD symbols. In the example of FIG 25, the pattern may indicate third and fourth symbols, in five symbols, to be SBFD symbols. As a result, configuration 2504 may indicate first symbol, second symbol, third symbol, fourth symbol, and fifth symbol as DL (or flexible) symbol, DL (or flexible) symbol, SBFD symbol, SBFD symbol, and UL symbol, respectively.

[0554] The five symbols may comprise, for example, symbol 2302, symbol 2304, symbol 2306, symbol 2308, and symbol 2310 (in the order shown in FIG. 23).

[0555] The five symbols may comprise, for example, symbol 2312, symbol 2314, symbol 2316, symbol 2318, and symbol 2320 (in the order shown in FIG. 23).

[0556] In an example, the NCR may receive a signal 2506 to forward to wireless device 2400. The NCR may use configuration 2504 to receive signal 2506 based on wireless device 2400 being SBFD-aware (e g., intended recipient of a signal being SBFD-aware). Using configuration 2504 to receive signal 2506 may comprise the NCR using DL symbol(s) and / or DL sub-bands of SBFD symbols to receive signal 2506.

[0557] The NCR may forward signal 2506 to wireless device 2400 using configuration 2504 based on wireless device 2400 being SBFD-aware. Using configuration 2504 to forward signal 2506 may comprise the NCR forwarding signal 2506 via UL symbols (e.g., fifth symbol) or UL sub-bands of SBFD symbols.

[0558] In an example, the NCR may receive a signal 2508 to forward to wireless device 2410. The NCR may use configuration 2502 (and not configuration 2504) to receive signal 2508 based on wireless device 2410 not being SBFD-aware (e.g., intended recipient of a signal not being SBFD-aware). Using configuration 2502 to receive signal 2508 may comprise the NCR using DL symbol(s) (e.g., first symbol, second symbol, third symbol, or fourth symbol) (e.g., and not DL sub-band(s) of SBFD symbol(s)) to receive signal 2508.

[0559] The NCR may forward signal 2508 to wireless device 2410 using configuration 2502 (and not configuration 2504) based on wireless device 2410 not being SBFD-aware. Using configuration 2502 to forward signal 2508 may comprise the NCR forwarding signal 2508 via UL symbols (e.g., fifth symbol) (and not UL sub-band(s) of SBFD symbol(s)).

[0560] In an example, signal 2506 and / or signal 2508 may be (or comprise) PDCCH, PDSCH, CSI-RS, SSB, SIB, MIB, and / or any other signal that may be received by a wireless device from a base station via downlink.

[0561] The NCR may forward signal 2506 to wireless device 2400 via NCR-Fwd access link 2402. The NCR may forward signal 2508 to wireless device 2410 via NCR-Fwd access link 2404.

[0562] The NCR may use configuration 2502 to not only forward signals via NCR-Fwd access link 2404 but also transmit and / or receive signals via NCR-Fwd backhaul. This may be useful for receiving an entire signal. For example, the base station may transmit a CSI-RS to the NCR via a first symbol (across the entire band). Based on using configuration 2502, the NCR may determine (e.g ., consider or treat) the first symbol as DL symbol. As a result, the NCR may receive the CSI-RS via the entire band of the first symbol.

[0563] If the NCR uses configuration 2504 to receive the CSI-RS, as may be the case in the existing technologies, the NCR receives the CSI-RS only on DL sub-band(s) of the first symbol and may not receive the CSI-RS on UL sub-band(s) of the first symbol. As a result, the NCR may forward an incomplete CSI-RS to a wireless device (e.g., wireless device 2410).

[0564] In some embodiments, transmitting via a link (e.g., control link, NCR-Fwd backhaul link, NCR-Fwd access link) may be the same as (or equivalent to) transmitting on the link, transmitting in the link, transmitting using the link, transmitting based on the link, transmitting with the link, and / or the like.

[0565] In some embodiments, receiving via a link (e.g., control link, NCR-Fwd backhaul link, NCR-Fwd access link) may be the same as (or equivalent to) receiving on the link, receiving in the link, receiving using the link, receiving based on the link, receiving with the link, and / or the like.

[0566] In some embodiments, forwarding a signal may comprise transmitting the signal.

[0567] In an example, symbol 2302 may be same as symbol 1804.

[0568] In an example, symbol 2312 may be same as symbol 1804.

[0569] In an example, symbol 2304 may be same as symbol 1806.

[0570] In an example, symbol 2314 may be same as symbol 1806.

[0571] In an example, symbol 2306 may be same as symbol 1808.

[0572] In an example, symbol 2316 may be same as symbol 1808.

[0573] In an example, symbol 2308 may be same as symbol 1810.

[0574] In an example, symbol 2318 may be same as symbol 1810.

[0575] In an example, symbol 2310 may be same as symbol 1812.

[0576] In an example, symbol 2320 may be same as symbol 1812.

[0577] In some embodiments, NCR may be equivalent to (or identical to) reflective intelligent surface (RIS) or intelligent reflective surface (IRS). Intelligent reflecting surface (IRS) may be an enabling technology to engineer a radio signal propagation in wireless networks. By smartly tuning signal reflectionvia several (e.g., tens of, hundreds of, or thousands of) low-cost passive reflecting elements, IRS may be capable of dynamically altering wireless channels to enhance communication performance. IRS-aided hybrid wireless network comprising both active and passive components may achieve sustainable capacity growth cost-effectively. In some embodiments, NCR, IRS, and / or RIS may be used interchangeably.

[0578] An example embodiment comprising: receiving, by a network control repeater, configuration parameters indicating: a first symbol as sub-band full duplex (SBFD) symbol, wherein the first symbol comprises: a DL sub-band; and an UL sub-band; and a second symbol as a DL symbol; receiving, from a base station, a signal to forward to a wireless device; and forwarding / transmitting, to the wireless device and via an access link, the signal via / on: the downlink sub-band of the first symbol in response to the wireless device being SBFD-aware; and the second symbol in response to the wireless device not being SBFD-aware.

Claims

1. CLAIMSWhat is claimed is:

1. A method comprising: transmitting, by a wireless device and via a first physical random-access channel (PRACH) occasion, a preamble using a first spatial filter; transmitting, in a transmission occasion, an uplink signal using a second spatial filter, wherein: the second spatial filter is same as the first spatial filter in response to both the transmission occasion and the PRACH occasion being in sub-band full-duplex (SBFD) symbols; and the second spatial filter is different from the first spatial filter in response to only one of the transmission occasion and the PRACH occasion being in SBFD symbols2. The method of claim 1 , further comprising receiving one or more messages.

3. The method of claim 2, wherein the one or more messages are at least one of: one or more radio resource control (RRC) messages; or one or more system information messages.

4. The method of any one of claims 2 to 3, wherein the one or more messages indicate one or more configuration parameters.

5. The method of claim 4, wherein the one or more configuration parameters are one or more radio resource control (RRC) configuration parameters.

6. The method of any one of claims 2 to 5, wherein receiving the one or more messages is via a base station.

7. The method of claim 6, wherein transmitting the preamble is to the base station.

8. The method of any one of claims 6 to 7, wherein transmitting the uplink signal is to the base station.

9. The method of any one of claims 6 to 8, wherein the base station is at least one of: a gNodeB (gNB); a gNB-central unit (CU); a g N B-distributed unit (DU); a satellite; an integrated access and backhaul (IAB) node; a network-controlled repeater; or a non-terrestrial network (NTN) payload.

10. The method of any one of claims 4 to 9, wherein the one or more configuration parameters is for or of a cell.11 . The method of claim 10, wherein transmitting the preamble is via the cell.

12. The method of any one of claims 10 to 11 , wherein transmitting the uplink signal is via the cell.

13. The method of any one of claims 10 to 12, wherein the cell is at least one of: a serving cell; a primary cell; a secondary cell; a special cell; a primary secondary cell; a non-terrestrial network cell; a layer 1 or layer 2 triggered mobility (LTM) candidate cell; or a non-serving cell.

14. The method of any one of claims 4 to 13, wherein the one or more configuration parameters indicate: a first set of RSs for determining beam failure; and a second set of RSs for determining beam failure.

15. The method of claim 14, wherein: the first set of RSs is associated with non-SBFD mode; and the second set of RSs is associated with SBFD mode.

16. The method of claim 15, further comprising determining beam failure based on monitoring one or more reference signals from at least one of: the first set of RSs; or the second set of RSs.

17. The method of any one of claims 4 to 16, wherein the one or more configuration parameters indicate a single set of RSs for determining beam failure.

18. The method of claim 17, wherein the single set of RSs is associated with:SBFD mode; and non-SBFD mode.

19. The method of claim 17, further comprising determining beam failure based on monitoring one or more RSs from the single set of RSs.

20. The method of any one of claims 14 to 19, wherein the one or more configuration parameters indicate: a first set of candidate RSs for beam failure recovery; and a second set of candidate RSs for beam failure recovery.

21. The method of claim 20, wherein: the first set of candidate RSs is associated with non-SBFD mode; and the second set of candidate RSs is associated with SBFD mode.

22. The method of claim 21 , wherein: the first set of candidate RSs is associated with a first coreset pool index; andthe second set of candidate RSs is associated with a second coreset pool index.

23. The method of any one of claims 20 to 22, further comprising selecting an RS from: the first set of candidate RSs; and the second set of candidate RSs.

24. The method of claim 23, further comprising selecting the RS from: the first set of candidate RSs in response to determining beam failure using the first set of RSs for determining beam failure; and the second set of candidate RSs in response to determining beam failure using the second set of RSs for determining beam failure.

25. The method of claim 24, wherein the PRACH occasion is associated with the RS.

26. The method of claim 25, wherein the one or more configuration parameters indicate the association between the RS and the PRACH occasion.

27. The method of any one of claims 25 to 26, wherein the one or more configuration parameters indicate an association between the RS and the preamble.

28. The method of any one of claims 16 to 27, wherein transmitting the preamble is for a random-access procedure.

29. The method of claim 28, wherein the random-access procedure is for beam failure recovery.

30. The method of claim 29, further comprising receiving a downlink signal indicating completion of beam failure recovery.31 . The method of claim 30, wherein the downlink signal is at least one of: a physical downlink control channel (PDCCH) reception comprising downlink control information (DCI) format with cyclic redundancy check (CRC) scrambled by C-RNTI, MCS-C-RNTI, or both the C- RNTI and the MCS-C-RNTI; a PDCCH reception that indicates completion of the random-access procedure; or a PDCCH reception with a DCI format scheduling an uplink transmission with a same HARQ process number as for a transmission of a first PUSCH and having a toggled NDI field value.

32. The method of claim 31 , wherein the transmitting the uplink signal is after a first number of symbols from a last symbol of the downlink signal.

33. The method of claim 32, wherein the first number of symbols is 28.

34. The method of any one of claims 32 to 33, wherein a subcarrier spacing configuration for determining the first number of symbols is a smallest of SCS configurations of an active downlink BWP for receiving the downlink signal and of active BWPs of serving cells.

35. The method of any one of claims 24 to 34, wherein the one or more configuration parameters indicate: a first set of random-access resources; anda second set of random-access resources for SBFD mode.

36. The method of claim 35, wherein a single random-access configuration indicates: the first set of random-access resources; and the second set of random-access resources.

37. The method of any one of claims 35 to 36, wherein: a first random-access configuration indicates the first set of random-access resources; and a second random-access configuration indicates the second set of random-access resources.

38. The method of claim 37, wherein the first random-access configuration and the second randomaccess configuration are not simultaneously enabled.

39. The method of any one of claims 35 to 38, further comprising determining the PRACH occasion based on: the first set of random-access resources in response to determining beam failure using the first set of RSs for determining beam failure; and the second set of random-access resources in response to determining beam failure using the second set of RSs for determining beam failure.

40. The method of any one of claims 24 to 39, wherein the second filter is determined based on the RS in response to only one of the transmission occasion and the PRACH occasion being in one or more SBFD symbols.41 . The method of claim 40, wherein the one or more configuration parameters indicate association between the second filter and the RS.

42. The method of any one of claims 24 to 41 , wherein the one or more configuration parameters indicate plurality of TCI states.

43. The method of claim 42, wherein the second filter is determined based on a first TCI state of the plurality of TCI states.

44. The method of claim 43, wherein the first TCI state is associated with SBFD mode.

45. The method of any one of claims 43 to 44, wherein the first TCI state is identified by a lowest TCI state ID among a plurality of TCI state IDs identifying the plurality of TCI states.

46. The method of any one of claims 43 to 44, wherein the first TCI state is identified by a second lowest TCI state ID among a plurality of TCI state IDs identifying the plurality of TCI states.

47. The method of any one of claims 43 to 46, wherein the first TCI state is a current TCI state, an indicated TCI state, or both.

48. The method of any one of claims 43 to 47, wherein a control command indicates the first TCI state.

49. The method of claim 48, wherein the control command is: a downlink control information (DCI); ora medium access control (MAC) control element (CE).

50. A method comprising: receiving, by a network control repeater, configuration parameters indicating: a first symbol as sub-band full duplex (SBFD) symbol, wherein the first symbol comprises: a downlink sub-band; and an uplink sub-band; and a second symbol as a downlink symbol; receiving, from a base station, a signal to forward to a wireless device; and forwarding or transmitting, to the wireless device and via an access link, the signal via or on: the downlink sub-band of the first symbol in response to the wireless device being SBFD-aware; and the second symbol in response to the wireless device not being SBFD-aware.51 . An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 50.

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

Images