Application time for semi-persistent or aperiodic subband full duplex indication

Abstract

A wireless communication device receives at least one of a semi-persistent subband full duplex (SBFD) indication or an aperiodic SBFD indication, and receives a downlink symbol or transmits an uplink symbol in a half-duplex mode after expiration of an application time counted from a start time associated with the at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication. A network entity transmits at least one of a semi-persistent subband full duplex (SBFD) indication or an aperiodic SBFD indication, and after expiration of an application time counted from a start time associated with the at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, receives an uplink symbol in an SBFD mode and transmits a downlink symbol.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority to pending U.S. Non - Provisional Application No. 17 / 985,013, filed on November 10, 2022, which is assigned to the assignee of the present application and is hereby incorporated by reference in its entirety as if fully set forth herein and for all applicable purposes. Technical Field

[0003] The techniques discussed below generally relate to wireless communication networks and, more specifically, to the identification of the application time for semi - persistent or aperiodic sub - band full - duplex indication. Background Art

[0004] In wireless communication systems (such as those specified according to the standards for 5G New Radio (NR)), base stations and user equipment use various duplex modes to exchange signals. Duplex modes include half - duplex and full - duplex. In half - duplex communication, only one node (e.g., user equipment (UE) or base station) can transmit or receive at a given time. In full - duplex communication, one or more nodes (e.g., UE and / or base station) can transmit and receive simultaneously (e.g., simultaneous transmission and reception at one node). An example of half - duplex communication is time - division duplex (TDD) communication. In 5G NR TDD, uplink signaling (e.g., from UE to base station) and downlink signaling (e.g., from base station to UE) are scheduled separately in time. Thus, uplink communication and downlink communication do not occur simultaneously. However, uplink communication and downlink communication can be transmitted on the same frequency (e.g., on the same carrier). An example of full - duplex communication is frequency - division duplex (FDD) communication. In 5G NR FDD, uplink signaling and downlink signaling are scheduled simultaneously in time; however, uplink and downlink can be transmitted at different frequencies (e.g., on different and separated carriers). An example of the full - duplex (FD) communication mode is sub - band full - duplex (SBFD). Summary of the Invention

[0005] The following presents an overview of one or more aspects of the present disclosure to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all the intended features of the present disclosure and is neither intended to identify the key or important elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a prelude to the more detailed description that is presented later.

[0006] In one example, a wireless communication device is described. The wireless communication device includes a memory and a processor coupled to the memory. According to the example, the processor is configured to: receive at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, receive a downlink symbol or transmit an uplink symbol in a half-duplex mode.

[0007] In another example, a method for wireless communication at a wireless communication device is described. In this example, the method includes: receiving at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, receiving a downlink symbol or transmitting an uplink symbol in a half-duplex mode.

[0008] In another example, a wireless communication device configured for wireless communication is described. The wireless communication device (e.g., apparatus) includes: means for receiving at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and means for, after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, receiving a downlink symbol or transmitting an uplink symbol in a half-duplex mode.

[0009] In yet another example, a non-transitory computer-readable medium storing computer-executable code is described. The computer-executable code includes code for causing a wireless communication device (e.g., apparatus) to: receive at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, receive a downlink symbol or transmit an uplink symbol in a half-duplex mode.

[0010] According to another example, a network entity is described. The network entity includes a memory and a processor coupled to the memory. In this example, the processor is configured to: transmit at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, receive an uplink symbol and transmit a downlink symbol in SBFD mode.

[0011] In another example, a method for wireless communication at a network entity is disclosed. The method includes: transmitting at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and receiving uplink symbols and transmitting downlink symbols in SBFD mode after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

[0012] In another example, a network entity (e.g., a device) configured for wireless communication is described. The network entity includes: at least one component for transmitting at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and a component for receiving uplink symbols and transmitting downlink symbols in SBFD mode after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

[0013] In another example, a non-transitory computer-readable medium storing computer-executable code is described. The computer-executable code includes code for causing a network entity (e.g., a device) to: transmit at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and receive uplink symbols and transmit downlink symbols in SBFD mode after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

[0014] After studying the following detailed description, these and other aspects of the present disclosure will be more fully understood. After reading the following description of specific, example embodiments of the present disclosure in conjunction with the drawings, other aspects, features, and embodiments of the present disclosure will become apparent to those skilled in the art. Although the features of the present disclosure may be discussed below with respect to certain embodiments and drawings, all embodiments of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, such features may be used in one or more of the various embodiments of the present disclosure discussed herein. In a similar manner, although example embodiments may be discussed below as device, system, or method embodiments, it should be appreciated that such example embodiments may be implemented in a variety of devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a schematic diagram of a wireless communication system in accordance with some aspects of the present disclosure.

[0016] Figure 2 Schematic diagram of an example of a radio access network (RAN) according to some aspects of the present disclosure.

[0017] Figure 3 Schematic diagram of an example of a decomposed base station architecture according to some aspects of the present disclosure.

[0018] Figure 4 Expanded view of an example subframe according to some aspects of the present disclosure, which shows an orthogonal frequency division multiplexing (OFDM) resource grid.

[0019] Figure 5 Block diagram of an example of a wireless communication system supporting beamforming and / or multiple-input multiple-output (MIMO) communication according to some aspects of the present disclosure.

[0020] Figure 6 Diagram illustrating an example of communication between a first network entity and a second network entity using a beamformed signal according to some aspects of the present disclosure.

[0021] Figure 7A and Figure 7B Schematic illustration of a wireless communication network according to some aspects of the present disclosure, including a network entity represented by a base station tower, a first half-duplex (HD) user equipment (UE), a second HD UE, and a third HD UE.

[0022] Figure 8A and Figure 8B Time-frequency resource diagram depicting various examples of full-duplex subbands according to some aspects of the present disclosure.

[0023] Figure 9 Call flow diagram illustrating two options for defining a start time from which to count an application time after receiving a semi-persistent SBFD indication or an aperiodic SBFD indication according to some aspects of the present disclosure.

[0024] Figure 10A and Figure 10B Diagram illustrating an example of uplink and downlink of subband full-duplex (SBFD) modulation specified according to two bandwidth parts (BWPs) according to some aspects of the present disclosure.

[0025] Figure 11 Block diagram of an example of a hardware implementation of a wireless communication device employing a processing system according to some aspects of the present disclosure.

[0026] Figure 12 Flowchart of an example process of wireless communication in a wireless communication network at a wireless communication device according to some aspects of the present disclosure.

[0027] Figure 13 FIG. 2 is a block diagram illustrating an example of a hardware implementation of a network entity employing a processing system in accordance with some aspects of the present disclosure.

[0028] Figure 14 FIG. 3 is a flow diagram illustrating an exemplary process of wireless communication in a wireless communication network at a network entity in accordance with some aspects of the present disclosure. DETAILED DESCRIPTION

[0029] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. It will be apparent, however, to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0030] While aspects and examples are described herein by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or uses may be generated via integrated chip examples and other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may be specifically or may not be specifically directed to a use case or application, a wide variety of applicability of the innovations described may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the innovations described. In some actual settings, devices incorporating the aspects and features described may also necessarily include additional components and features for the implementation and practice of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or user equipment (UE)), end-user devices, etc. of different sizes, shapes, and configurations.

[0031] This document describes techniques for setting a start time associated with the reception of a semi-persistent (SP) sub-band full-duplex (SBFD) indication or an aperiodic (AP) SBFD indication by a half-duplex (HD) wireless communication device (e.g., a UE). The SP SBFD indication or the AP SBFD indication can be conveyed from a full-duplex network entity (e.g., a gNB) to the HD wireless communication device. This document also describes apparatuses and methods for establishing an application time counted from the start time. The application time (also referred to herein as the switching time) can be the time used by the HD wireless communication device to reconfigure / retune RF and / or baseband parameters. The reconfiguration can be performed in response to a change in the bandwidth at the HD wireless communication device between a first bandwidth associated with a half-duplex downlink or uplink and a second bandwidth associated with an uplink sub-band or a downlink sub-band for SBFD communication.

[0032] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. Now referring to Figure 1 , by way of illustrative example and not limitation, various aspects of this disclosure are illustrated with reference to the wireless communication system 100. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the wireless communication system 100, the UE 106 can be enabled to perform data communication with an external data network 110 (such as, but not limited to, the Internet).

[0033] The RAN 104 can implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, the RAN 104 can operate according to a hybrid of 5G NR and the evolved universal terrestrial radio access network (eUTRAN) standard (commonly referred to as Long Term Evolution (LTE)). 3GPP refers to such a hybrid RAN as the next generation RAN or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0034] As illustrated, RAN 104 includes a plurality of network entities 108 (e.g., base stations, gNBs, TRPs, scheduling entities). Broadly, network entities can be implemented in a centralized or monolithic base station architecture, or alternatively, in a split base station architecture, and can include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non RT) RIC. In some examples, a network entity can be a network element in a radio access network responsible for radio transmission and reception to or from UEs in one or more cells. In different technologies, standards, or contexts, network entities may be differently referred to by those skilled in the art as base transceiver stations (BTSs), radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), access points (APs), Node Bs (NBs), eNode Bs (eNBs), gNode Bs (gNBs), transmission and reception points (TRPs), or some other suitable term. In some examples, a network entity can include two or more TRPs that can be co-located or non-co-located. Each TRP can communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to both the LTE and 5G NR standards, one of the network entities can be an LTE network entity and another network entity can be a 5G NR network entity.

[0035] RAN 104 is also illustrated as supporting wireless communication for a plurality of mobile devices. In 3GPP standards, a mobile device can be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, mobile phone, terminal, user agent, mobile client, client, or some other suitable term. A UE can be a device (e.g., a mobile device) that provides access to network services for a user.

[0036] Within this disclosure, a "mobile" device need not necessarily have the ability to move and can be stationary. The term mobile device or mobile equipment encompasses a wide variety of devices and technologies. A UE can include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablet computers, personal digital assistants (PDAs), and various embedded systems (e.g., corresponding to the "Internet of Things" (IoT)).

[0037] A mobile device can also be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, consumer and / or wearable devices (such as glasses, wearable cameras, virtual reality devices, smart watches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc.). A mobile device can also be a digital home or smart home device (such as home audio, video, and / or multimedia devices), appliances, vending machines, smart lighting devices, home security systems, smart meters, etc. A mobile device can also be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure devices that control electric power (e.g., smart grid), lighting, water supply, etc., industrial automation and enterprise equipment, logistics controllers, and / or agricultural equipment, etc. In addition, a mobile device can provide connected medical or telemedicine support, such as healthcare at a distance. Telemedicine devices can include telemedicine monitoring devices and telemedicine management devices, and their communication can be given priority or precedence over access to other types of information, e.g., in terms of priority access for the transmission of critical service data and / or related QoS for the transmission of critical service data.

[0038] Wireless communication between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions from a network entity (e.g., network entity 108) to one or more UEs (e.g., similar to UE 106) via the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" may refer to a point-to-multipoint transmission originating at a network entity (e.g., network entity 108). Another way to describe this scenario could be to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a network entity (e.g., network entity 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" can refer to a point-to-point transmission originating at a UE (e.g., UE 106).

[0039] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., network entity 108) allocates resources for communication among some or all of the devices and equipment within its service area or cell. Within the present disclosure, as further discussed below, the scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UE 106). That is, for the scheduled communication, multiple UEs 106 (which can be the scheduled entities) can utilize the resources allocated by the scheduling entity 108.

[0040] The network entity 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0041] As Figure 1 illustrated, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, including uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, a scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grant), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the scheduling entity 108. The scheduled entity 106 can also send uplink control information 118 (including but not limited to a scheduling request or feedback information or other control information) to the scheduling entity 108.

[0042] In addition, uplink control information 118 and / or downlink control information 114 and / or uplink traffic 116 and / or downlink traffic 112 may be transmitted on a waveform that may be time-divided into frames, sub-frames, time slots, and / or symbols. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per sub-carrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A sub-frame may refer to a duration of 1 ms. Multiple sub-frames or time slots may be grouped together to form a single frame or radio frame. Within the present disclosure, a frame may refer to a predetermined duration for wireless transmission (e.g., 10 ms), where each frame is composed of, for example, 10 sub-frames each of 1 ms. Of course, these definitions are not required, and any suitable scheme for organizing the waveform may be utilized, and the various time divisions of the waveform may have any suitable duration.

[0043] Generally, network entity 108 may include a backhaul interface for communicating with the backhaul portion 120 of wireless communication system 100. The backhaul portion 120 may provide a link between network entity 108 and core network 102. Additionally, in some examples, the backhaul network may provide an interconnection between corresponding network entities 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, virtual network, or the like using any suitable transport network.

[0044] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to the 5G standard (e.g., 5G Core (5GC)). In other examples, core network 102 may be configured according to the 4G evolved packet core (EPC) or any other suitable standard or configuration.

[0045] Now referring to Figure 2 , by way of illustrative example and not limitation, a schematic illustration of an example of a radio access network (RAN) 200 in accordance with some aspects of the present disclosure is provided. In some examples, RAN 200 may be the same as RAN 104 described above and illustrated in Figure 1 .

[0046] The geographical area covered by RAN 200 may be divided into several cellular areas (cells), and user equipment (UE) may uniquely identify these cellular areas (cells) based on an identifier broadcast from one access point or network entity within the geographical area. Figure 2Cells 202, 204, 206, and 208 are illustrated, where each may include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same network entity. Radio links within a sector may be identified by a single logical identity belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by multiple sets of antennas, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0047] Various network entity arrangements may be utilized. For example, in Figure 2 , two base stations (Base Station 210 and Base Station 212) are shown in Cells 202 and 204. A third base station (Base Station 214) is shown as controlling a Remote Radio Head (RRH) 216 in Cell 206. That is, a base station may have an integrated antenna or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, Cells 202, 204, and 206 may be referred to as macro cells because Base Stations 210, 212, and 214 support cells with large dimensions. Additionally, Base Station 218 is shown in Cell 208, which may overlap with one or more macro cells. In this example, Cell 208 may be referred to as a small cell (e.g., small cell, micro cell, pico cell, femto cell, home base station, home Node B, home eNode B, etc.) because Base Station 218 supports a cell with a relatively small dimension. Cell sizing may be performed according to system design and component constraints.

[0048] It should be understood that the RAN 200 may include any number of network entities (e.g., base stations, gNBs, TRPs, scheduling entities) and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of a given cell. Base Stations 210, 212, 214, 218 provide a wireless access point to the core network for any number of mobile devices. In some examples, Base Stations 210, 212, 214, and / or 218 may be the same as or similar to the scheduling entity 108 described above and illustrated in Figure 1 .

[0049] Figure 2 Also included is an Unmanned Aerial Vehicle (UAV) 220, which may be a drone or quadcopter. The UAV 220 may be configured to act as a base station or, more specifically, as a mobile base station. That is, in some examples, a cell may not have to be stationary, and the geographical area of the cell may move according to the position of a mobile base station such as the UAV 220.

[0050] Within the RAN 200, a cell may include UEs that can communicate with one or more sectors of each cell. Additionally, each base station 210, 212, 214, 218, and 220 may be configured to provide an access point to the core network 102 (see Figure 1 ) to all UEs in the respective cell. For example, UEs 222 and 224 may be in communication with base station 210, UEs 226 and 228 may be in communication with base station 212, UEs 230 and 232 may be in communication with base station 214 via RRH 216, UE 234 may be in communication with base station 218, and UE 236 may be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as or similar to the UE / scheduled entity 106 described above and illustrated in Figure 1 . In some examples, a UAV 220 (e.g., a quadcopter) may be a mobile network entity and may be configured to act as a UE. For example, the UAV 220 may operate within cell 202 by communicating with base station 210.

[0051] In another aspect of the RAN 200, sidelink signals may be used between UEs without relying on scheduling or control information from a base station. Sidelink communication may be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signal 237 without relaying the communication through a base station. In some examples, each of UEs 238, 240, and 242 may act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and convey sidelink signal 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of a base station (e.g., base station 212) may also convey sidelink signal 227 via a direct link (sidelink) without transporting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communication.

[0052] To obtain a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel decoding can be used. That is, wireless communications can generally utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., codec) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message can improve the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0053] Data decoding can be implemented in a variety of ways. In the early 5G NR specifications, quasi-cyclic low-density parity-check (LDPC) was used to decode user data using two different base graphs: one base graph for large code blocks and / or high code rates, and another for other cases. Polar decoding was used to decode control information and the physical broadcast channel (PBCH) based on nested sequences. For these channels, rate matching was performed using puncturing, shortening, and repetition.

[0054] Aspects of the present disclosure can be implemented using any suitable channel code. Various specific implementations of the base station and UE can include suitable hardware and capabilities (e.g., encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communication.

[0055] In the RAN 200, the ability of the UE to communicate while moving (independent of its location) is referred to as mobility. The various physical channels between the UE and the RAN 200 are generally established, maintained, and released under the control of the access and mobility management function (AMF). In some scenarios, the AMF can include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF can manage the security context for both the control plane function and the user plane function, either in whole or in part.

[0056] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to effect movement and handover (i.e., the connection of a UE is transferred from one radio channel to another radio channel). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signals from its serving cell as well as various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another cell, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell by a given amount of time, the UE may perform a handover or handoff from the serving cell to the neighboring (target) cell. For example, the UE 224 may move from the geographical area corresponding to its serving cell 202 to the geographical area corresponding to the neighboring cell 206. When the signal strength or quality of the neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 by a given amount of time, the UE 224 may send a report message indicating this situation to its serving base station 210. In response, the UE 224 may receive a handover command, and the UE may perform a handover to the cell 206.

[0057] In a network configured for UL-based mobility, the network may utilize the UL reference signals from each UE to select a serving cell for each UE. In some examples, the base stations 210, 212, and 214 / 216 may broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). The UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signal, derive the carrier frequency and slot timing from these synchronization signals, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) may be concurrently received by two or more cells within the RAN 200 (e.g., base stations 210 and 214 / 216). Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine the serving cell for the UE 224. As the UE 224 moves through the RAN 200, the RAN 200 may continue to monitor the uplink pilot signal transmitted by the UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0058] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 may be unified, the synchronization signal may not identify a specific cell, but rather may identify a zone of multiple cells operating on the same frequency and / or using the same timing. The use of zones in 5G networks or other next-generation communication networks enables an uplink-based mobility framework and improves the efficiency of both the UE and the network, as the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0059] In various embodiments, the air interface in radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although some technical rules typically still need to be adhered to for accessing unlicensed spectrum, generally any operator or device can obtain access. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required for accessing the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, the license holder of a portion of licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with conditions determined by a suitable licensee for access).

[0060] The electromagnetic spectrum is typically subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is typically (interchangeably) referred to as the “sub-6 GHz” band. Regarding FR2, a similar naming issue sometimes occurs, which is typically (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the “millimeter wave” band.

[0061] The frequency between FR1 and FR2 is generally referred to as the mid-band frequency. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designations FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus the characteristics of FR1 and / or FR2 can be effectively extended to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0062] Taking the above aspects into account, unless otherwise specifically stated, it should be understood that if terms such as "below 6 GHz" are used herein, they can generally represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if terms such as "millimeter wave" are used herein, this term can generally represent frequencies that can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band.

[0063] Devices communicating in the radio access network 200 can utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexes DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). Additionally, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes. In addition, time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes can be used to multiplex DL transmissions from the base station 210 to UEs 222 and 224.

[0064] Devices in the radio access network 200 can also utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link where two endpoints can communicate with each other in two directions. Full duplex means that two endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex emulation is often implemented using time-division duplexing (TDD) for wireless links. In TDD, transmissions in different directions on a given channel are separated from each other using time-division multiplexing. That is, in some scenarios, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction can change very quickly, e.g., several times per time slot. In a wireless link, a full-duplex channel generally relies on physical isolation of the transmitter and receiver and appropriate interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency-division duplexing (FDD) or space-division duplexing (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectra). In SDD, space-division multiplexing (SDM) is used to separate transmissions in different directions on a given channel. In other examples, full-duplex communication can be achieved within unpaired spectra (e.g., within a single-carrier bandwidth), where transmissions in different directions occur in different sub-bands of the carrier bandwidth. This type of full-duplex communication can be referred to as sub-band full-duplex (SBFD) in this document, and is also known as flexible duplexing.

[0065] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in various ways. In a 5G NR system or network, network entities, network entities, mobility elements of the network, radio access network (RAN) nodes, core network entities, network elements, or network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit-receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0066] A centralized base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0067] Base station type operations or network designs may consider the aggregation characteristics of base station functionality. For example, split base stations may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration advocated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may achieve flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0068] Figure 3 is a schematic diagram of an exemplary split base station architecture 300 in accordance with some aspects of the present disclosure. The split base station 300 architecture may include one or more central units (CUs) 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more split base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with a respective UE 342 via one or more radio frequency (RF) access links. In some embodiments, the UE 342 may be served simultaneously by multiple RUs 340. For example, the UE 342 may be the same as or similar to any of the UEs or scheduled entities illustrated and described in conjunction with Figure 1 and Figure 2 and any of the UEs or scheduled entities illustrated and described in conjunction with

[0069] Each of the units (i.e., CU 310, DU 330, RU 340, and the near RT RIC 325, non-RT RIC 315, and SMO framework 305) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or transmit signals, or both, to one or more of the other units over a wireless transmission medium.

[0070] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may utilize an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0071] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially according to a functional split (such as the functional split defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0072] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, the RUs 340 controlled by the DU 330 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both at least partially based on a functional split such as a lower layer functional split. In such an architecture, the RUs 340 may be implemented to handle over-the-air (OTA) communication with one or more UEs 342. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RUs 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0073] The SMO framework 305 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 310, DU 330, RU 340, and the near RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 311, via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0074] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near RT RIC 325 (such as via the A1 interface). The near RT RIC 325 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near RT RIC 325.

[0075] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 315 may monitor the long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 305 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0076] Reference will be made Figure 4 to the OFDM waveform schematically illustrated to describe various aspects of the present disclosure. Those of ordinary skill in the art should understand that the various aspects of the present disclosure can be applied to the SC-FDMA waveform in substantially the same manner as described hereinbelow. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to the SC-FDMA waveform.

[0077] Now refer to Figure 4 , an expanded view of an exemplary subframe 402 is illustrated, which shows an OFDM resource grid according to some aspects of the present disclosure. However, as will be readily appreciated by those skilled in the art, the physical (PHY) transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in OFDM symbols in the horizontal direction; and frequency is in subcarriers of the carrier in the vertical direction.

[0078] The resource grid 404 can be used to schematically represent the time - frequency resources for a given antenna port. That is, in a multiple - input multiple - output (MIMO) implementation with multiple available antenna ports, the corresponding multiple resource grids 404 can be available for communication. The resource grid 404 is divided into multiple resource elements (REs) 406. An RE (which is 1 sub - carrier × 1 symbol) is the smallest discrete part of the time - frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more information bits. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply as a resource block (RB) 408, which contains any suitable number of consecutive sub - carriers in the frequency domain. In one example, an RB may include 12 sub - carriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 408) fully corresponds to communication in a single direction (transmission or reception for a given device).

[0079] A set of consecutive or non - consecutive resource blocks may be referred to herein as a resource block group (RBG), a sub - band, or a bandwidth part (BWP). A set of sub - bands or BWPs may span the entire bandwidth. Scheduling the downlink transmission, uplink transmission, or sidelink transmission of a scheduled entity (e.g., a UE) may involve scheduling one or more resource elements 406 within one or more sub - bands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of the resource grid 404. In some examples, an RB may be the smallest resource unit that can be allocated to a UE. Therefore, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. An RB can be scheduled by a scheduling entity such as a network entity (e.g., a base station, gNB, TRP, scheduling entity), or can be self - scheduled by a UE implementing D2D sidelink communication.

[0080] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of sub - frame 402, with some sub - carriers illustrated above and below RB 408. In a given implementation, sub - frame 402 can have a bandwidth corresponding to any number of one or more RBs 408. Additionally, in this illustration, RB 408 is shown as occupying less than the entire duration of sub - frame 402, although this is only one possible example.

[0081] Each 1 - ms sub - frame 402 can be composed of one or more adjacent time slots. In Figure 4In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots (sometimes referred to as shortened transmission time intervals (TTIs)) having a shorter duration (e.g., 1 to 3 OFDM symbols). These mini-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or a time slot.

[0082] An expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. Generally, the control region 412 may carry control channels, and the data region 414 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The structure illustrated is merely exemplary in nature, and different time slot structures may be utilized, and these time slot structures may include one or more regions in each of the control region and the data region.

[0083] Although not illustrated in Figure 4 various resource elements 406 within the RB 408 may be scheduled to carry one or more physical channels, the one or more physical channels including control channels, shared channels, data channels, etc. Other resource elements 406 within the RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control channel and / or data channel within the RB 408.

[0084] In some examples, the time slot 410 may be utilized for broadcast, multicast, groupcast, or unicast communication. For example, broadcast, multicast, or groupcast communication may refer to a point-to-multipoint transmission from one device (e.g., a network entity, UE, or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast or groupcast communication is delivered to multiple intended receiving devices. Unicast communication may refer to a point-to-point transmission from one device to a single other device.

[0085] In an example of cellular communication over a cellular carrier via the Uu interface, for DL transmission, a scheduling entity (e.g., a network entity) may allocate one or more REs 406 (e.g., within the control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels such as the Physical Downlink Control Channel (PDCCH). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL transmission and UL transmission. The PDCCH may further carry Hybrid Automatic Repeat Request (HARQ) feedback transmissions such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those of ordinary skill in the art, where for accuracy, the integrity of packet transmission may be verified at the receiving side, for example, using any suitable integrity check mechanism such as a checksum or a Cyclic Redundancy Check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, while if not, a NACK may be sent. In response to a NACK, the transmitting device may transmit a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.

[0086] The network entity may further allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals such as Demodulation Reference Signals (DMRS); Phase Tracking Reference Signals (PT-RS); Channel State Information (CSI) Reference Signals (CSI-RS); and Synchronization Signal Blocks (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, or 160 ms). The SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Control Channel (PBCH). The UE may use the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the Physical Cell Identity (PCI) of the cell.

[0087] The PBCH in SSB may also include a master information block (MIB) containing various system information and parameters for decoding system information blocks (SIBs). The SIB can be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide the minimum system information (SI) for initial access. Examples of the system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of the remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The network entity may also send other system information (OSI).

[0088] In UL transmission, the scheduled entity (e.g., UE) may utilize one or more REs 406 to the scheduling entity to carry UL control information (UCI) including one or more UL control channels such as the physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmission. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule an uplink transmission. Herein, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmission. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as CSI report), or any other suitable UCI.

[0089] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data. Such data may be carried on one or more traffic channels, such as, for DL transmission, on the physical downlink shared channel (PDSCH); or for UL transmission, on the physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS. In some examples, the PDSCH may carry multiple SIBs, not limited to SIB1 discussed above. For example, OSI may be provided in these SIBs (e.g., SIB2 and above SIBs).

[0090] In an example of sidelink communication on a sidelink carrier via a Proximity Services (ProSe) PC5 interface, the control region 412 of slot 410 may include a Physical Sidelink Control Channel (PSCCH) that includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) towards a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). The data region 414 of slot 410 may include a Physical Sidelink Shared Channel (PSSCH) that includes sidelink data transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier via the SCI. Other information may also be transmitted via various resource elements (REs) 406 within slot 410. For example, HARQ feedback information may be transmitted from a receiving sidelink device to a transmitting sidelink device in a Physical Sidelink Feedback Channel (PSFCH) within slot 410. Additionally, one or more reference signals, such as sidelink SSB, sidelink CSI-RS, sidelink SRS, and / or sidelink positioning reference signal (PRS), may be transmitted within slot 410.

[0091] These physical channels described above are typically multiplexed and mapped to transport channels for handling at the Medium Access Control (MAC) layer. The transport channels carry information blocks referred to as transport blocks (TBs). Based on the Modulation and Coding Scheme (MCS) and the number of resource blocks (RBs) in a given transmission, the transport block size (TBS) (which may correspond to the number of bits of information (e.g., the amount of bits of information)) can be a controlled parameter.

[0092] As described above in connection with Figures 1 to 4 the channels or carriers described are not necessarily all the channels or carriers that may be used between a scheduling entity and a scheduled entity. One of ordinary skill in the art will recognize that, in addition to the illustrated channels or carriers, other channels or carriers (such as other traffic, control, and feedback channels) may be used.

[0093] In some aspects of the present disclosure, a scheduling entity and / or a scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 5FIG. is a block diagram illustrating an example of a wireless communication system 500 that supports beamforming and / or MIMO in accordance with some aspects of the present disclosure. In a MIMO system, a first network entity 502 (e.g., a transmitter) includes a plurality of transmit antennas 504 (e.g., N transmit antennas), and a second network entity 506 (e.g., a receiver) includes a plurality of receive antennas 508 (e.g., M receive antennas). Accordingly, there are N×M signal paths 510 from the transmit antennas 504 to the receive antennas 508. Each of the first network entity 502 and the second network entity 506 may be implemented, for example, within a scheduling entity, a scheduled entity, or any other suitable wireless communication device.

[0094] The use of such multi-antenna techniques enables a wireless communication system to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also referred to as layers) on the same time-frequency resource. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially pre-coding each data stream (i.e., multiplying the data stream by different weights and phase shifts) and then transmitting each spatially pre-coded stream over multiple transmit antennas on the downlink. The spatially pre-coded data streams arrive at the UEs with different spatial characteristics, which enables each UE to recover one or more data streams destined for that UE. On the uplink, each UE transmits a spatially pre-coded data stream, which enables the base station to identify the source of each spatially pre-coded data stream.

[0095] The number of data streams or layers corresponds to the transmit rank. In general, the rank of a wireless communication system 500 (MIMO system) is limited by the number of transmit antennas 504 or receive antennas 508 (whichever is lower). Additionally, the channel conditions at the UE and other considerations (such as the available resources at the base station) can also affect the transmit rank. For example, the rank assigned to a particular UE on the downlink (and thus the number of data streams) can be determined based on a rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) at each of the receive antennas and the measured signal-to-interference-plus-noise ratio (SINR). For example, the RI can indicate the number of layers that can be supported under the current channel conditions. The base station can use the RI and resource information (e.g., the available resources and data volume to be scheduled for the UE) to assign a transmit rank to the UE.

[0096] In one example, as Figure 5As shown, rank-2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will transmit one data stream from each transmit antenna 504. Each data stream reaches each receive antenna 508 along a different signal path 510. The second network entity 506 can then use the received signals from each receive antenna 508 to reconstruct the data stream.

[0097] Beamforming is a signal processing technique that can be used at the first network entity 502 or the second network entity 506 to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the first network entity 502 and the second network entity 506. Beamforming can be achieved by combining signals communicated via antennas 504 or 508 (e.g., antenna elements of an antenna array module) such that some signals experience constructive interference while other signals experience destructive interference. To produce the desired constructive / destructive interference, the first network entity 502 or the second network entity 506 can apply amplitude and / or phase offsets to the signals transmitted or received from each of the antennas 504 or antennas 508 associated with the first network entity 502 or the second network entity 506.

[0098] In a 5G New Radio (NR) system, especially in systems above 6 GHz or millimeter wave systems, beamformed signals can be used for most downlink channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH). Additionally, broadcast control information (such as SSB, Slot Format Indicator (SFI), and paging information) can be sent in a beam scanning manner so that all scheduled entities (e.g., UEs) in the coverage area of a Transmission and Reception Point (TRP) (e.g., gNB) can receive the broadcast control information. Further, for UEs configured with beamforming antenna arrays, beamformed signals can also be used for uplink channels (including the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH)).

[0099] A base station (e.g., gNB) may generally be able to communicate with a UE using transmission beams (e.g., downlink transmission beams) of different beam widths. For example, the base station may be configured to utilize a wider beam when communicating with a moving UE and a narrower beam when communicating with a stationary UE. The UE may also be configured to receive signals from the base station using one or more downlink receiving beams. In some examples, to select one or more downlink transmission beams and one or more downlink receiving beams for communication with the UE, the base station may transmit a reference signal (such as an SSB or CSI-RS) on each of the multiple downlink transmission beams in a beam scanning manner. The UE may use one or more downlink receiving beams on the UE to measure the reference signal received power (RSRP) on each of the downlink transmission beams in the downlink transmission beams, and send a beam measurement report to the base station, where the beam measurement report indicates the RSRP of each of the measured downlink transmission beams in the downlink transmission beams. The base station may then select one or more serving downlink beams (e.g., downlink transmission beams and downlink receiving beams) for communication with the UE based on the beam measurement report. The resulting selected downlink transmission beam and downlink receiving beam may form a downlink beam pair link. In other examples, when the channel is reciprocal, the base station may derive a specific downlink beam for communication with the UE based on uplink measurements of one or more uplink reference signals (such as sounding reference signals (SRS)).

[0100] Similarly, uplink beams (e.g., uplink transmission beams at the UE and uplink receiving beams at the base station) may be selected by measuring the RSRP of the received uplink reference signal (e.g., SRS) or downlink reference signal (e.g., SSB or CSI-RS) during uplink or downlink beam scanning. For example, the base station may determine the uplink beam through uplink beam management via SRS beam scanning measured at the base station or through downlink beam management via SSB / CSI-RS beam scanning measured at the UE. The selected uplink beam may be indicated by the selected SRS resource (e.g., time-frequency resource for SRS transmission) when implementing uplink beam management, or by the selected SSB / CSI-RS resource when implementing downlink beam management. For example, the selected SSB / CSI-RS resource may have a spatial relationship with the selected uplink transmission beam (e.g., uplink transmission beam for PUCCH, SRS, and / or PUSCH). The resulting selected uplink transmission beam and uplink receiving beam may form an uplink beam pair link.

[0101] Figure 6FIG. is an illustration of an example of communication between a first network entity (e.g., a radio access network (RAN) node, a gNB (hereinafter referred to as network entity 604)) that uses a beamformed signal and a second network entity (e.g., a wireless communication device, a UE) (hereinafter referred to as UE 602) in accordance with some aspects of the present disclosure. The first network entity 604 may be Figure 1 , Figure 2 , Figure 3 and / or Figure 5 any of the network entities (e.g., a base station, a gNB, a TRP, a scheduling entity, a CU / DU / RU) exemplified in Figure 1 , Figure 2 , Figure 3 and / or Figure 5 any of the UEs or scheduled entities exemplified in

[0102] The network entity 604 may generally be capable of communicating with the UE 602 using one or more transmit beams, and the UE 602 may further be capable of communicating with the network entity 604 using one or more receive beams. As used herein, the term transmit beam refers to a beam that may be used on the network entity 604 for downlink or uplink communication with the UE 602. Additionally, the term receive beam refers to a beam that may be used on the UE 602 for downlink or uplink communication with the network entity 604.

[0103] In Figure 6 the example shown, the network entity 604 is configured to generate a plurality of transmit beams 606a - 606h, each transmit beam associated with a different spatial direction. Additionally, the UE 602 is configured to generate a plurality of receive beams 608a - 608e, each receive beam associated with a different spatial direction. It should be noted that although some beams are illustrated as being adjacent to each other, such an arrangement may be different in different aspects. For example, the transmit beams 606a - 606h transmitted during the same symbol period may not be adjacent to each other. In some examples, the network entity 604 and the UE 602 may each transmit more or less beams that are distributed in all directions (e.g., 360 degrees) and three-dimensionally. Additionally, the transmit beams 606a - 606h may include beams with varying beam widths. For example, the network entity 604 may transmit certain signals (e.g., SSB) on a wider beam, while transmitting other signals (e.g., CSI-RS) on a narrower beam.

[0104] The network entity 604 and the UE 602 may use a beam management procedure to select one or more transmit beams 606a - 606h on the network entity 604 and one or more receive beams 608a - 608e on the UE 602 for communicating uplink and downlink signals therebetween. In one example, during initial cell capture, the UE 602 may perform a P1 beam management procedure to scan the multiple transmit beams 606a - 606h over the multiple receive beams 608a - 608e to select a beam pair link (e.g., one of the transmit beams 606a - 606h and one of the receive beams 608a - 608e) for the physical random access channel (PRACH) procedure for initial access to the cell. For example, periodic SSB beam scanning may be implemented on the network entity 604 at a specific interval (e.g., based on SSB periodicity). Thus, the network entity 604 may be configured to scan or transmit SSBs on each of the multiple wider transmit beams 606a - 606h during a beam scanning interval. The UE 602 may measure the reference signal received power (RSRP) of each SSB transmitted on each of the transmit beams 606a - 606h or receive beams 608a - 608e of the UE 602. The UE 602 may select the transmit beam and the receive beam based on the measured RSRP. In an example, the selected receive beam may be the receive beam on which the highest RSRP is measured, and the selected transmit beam may have the highest RSRP measured on the selected receive beam.

[0105] After completing the PRACH procedure, network entity 604 and UE 602 may perform a P2 beam management procedure for beam refinement at network entity 604. For example, network entity 604 may be configured to scan or transmit CSI-RS on each of a plurality of narrower transmission beams 606a-606h. Each of the narrower CSI-RS beams may be a sub-beam (not shown) of a selected SSB transmission beam (e.g., within the spatial direction of the SSB transmission beam). Transmission of the CSI-RS transmission beam may occur periodically (e.g., as configured by the gNB via radio resource control (RRC) signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via medium access control-control element (MAC-CE) signaling), or aperiodically (e.g., as triggered by the gNB via downlink control information (DCI)). UE 602 may be configured to scan a plurality of CSI-RS transmission beams 606a-606h on a plurality of receive beams 608a-608e. Then UE 602 may perform beam measurements (e.g., RSRP, SINR, etc.) on the CSI-RS received on each of the receive beams 608a-608e to determine the corresponding beam quality of each of the CSI-RS transmission beams 606a-606h, as measured on each of the receive beams 608a-608e.

[0106] Then UE 602 may generate and send a layer 1 (L1) measurement report to network entity 604, which includes the corresponding beam indices (e.g., CSI-RS resource indicator (CRI)) and beam measurements (e.g., RSRP, SINR) of one or more of the CSI-RS transmission beams 606a-606h on one or more of the receive beams 608a-608e. Network entity 604 may then select one or more CSI-RS transmission beams on which to send unicast downlink control information and / or user data traffic to UE 602. In some examples, the selected CSI-RS transmission beam has the highest RSRP from the L1 measurement report. Transmission of the L1 measurement report may occur periodically (e.g., as configured by the gNB via RRC signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via MAC-CE signaling), or aperiodically (e.g., triggered by the gNB via DCI).

[0107] UE 602 can further select corresponding receive beams on UE 602 for each selected serving CSI-RS transmission beam to form corresponding downlink beam pair links (BPLs) for each selected serving CSI-RS transmission beam. For example, UE 602 can utilize beam measurements obtained during the P2 procedure or perform a P3 beam management procedure to obtain new beam measurements of the selected CSI-RS transmission beams to select corresponding receive beams for each selected transmission beam. In some examples, the selected receive beam to be paired with a particular CSI-RS transmission beam can be the receive beam on which the highest RSRP is measured for that particular CSI-RS transmission beam.

[0108] In some examples, network entity 604 can configure UE 602 to perform SSB beam measurements and provide an L1 measurement report including beam measurements of SSB transmission beams 606a - 606h. For example, network entity 604 can configure UE 602 to perform SSB beam measurements and / or CSI-RS beam measurements for beam failure detection (BFD), beam failure recovery (BFR), cell reselection, beam tracking (e.g., for a moving UE 602 and / or network entity 604), or other beam optimization purposes.

[0109] Furthermore, when the channel is reciprocal, uplink beam management schemes can be used to select transmission and receive beams. In an example, UE 602 can be configured to scan or transmit on each of a plurality of receive beams 608a - 608e. For example, UE 602 can transmit SRS on each beam in different beam directions. Additionally, network entity 604 can be configured to receive uplink beam reference signals on a plurality of transmission beams 606a - 606h. Then network entity 604 can perform beam measurements (e.g., RSRP, SINR, etc.) of the beam reference signals on each of the transmission beams 606a - 606h to determine the corresponding beam quality of each of the receive beams 608a - 608e as measured on each of the transmission beams 606a - 606h.

[0110] Network entity 604 can then select one or more transmission beams on which to convey downlink control information and / or user data traffic to UE 602. In some examples, the selected transmission beam has the highest RSRP. UE 602 can then use, for example, the P3 beam management procedure as described above to select corresponding receive beams for each selected serving transmission beam to form corresponding beam pair links (BPLs) for each selected serving transmission beam.

[0111] In addition to the L1 measurement report, the UE 602 may also utilize beam reference signals to estimate the channel quality of the channel between the network entity 604 and the UE 602. For example, the UE 602 may measure the SINR of each received CSI-RS and generate a CSI report based on the measured SINR. The CSI report may include, for example, a channel quality indicator (CQI), a rank indicator (RI), a precoding matrix indicator (PMI), and / or a layer indicator (LI). The scheduling entity may use the CSI report to select a rank, as well as a precoding matrix and an MCS for the scheduled entity for future downlink transmissions to the scheduled entity. The MCS may be selected from one or more MCS tables, each associated with a particular type of decoding (e.g., polar decoding, LDPC, etc.) or modulation (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (QAM), 64QAM, 256QAM, etc.). The LI may be used to indicate which column of the precoding matrix of the reported PMI corresponds to the strongest layer codeword corresponding to the reported maximum broadband CQI.

[0112] In one example, a single CSI-RS transmission beam (e.g., transmission beam 606d) on the network entity 604 and a single reception beam (e.g., reception beam 608c) on the UE 602 may form a single BPL for communication between the network entity 604 and the UE 602. In another example, multiple CSI-RS transmission beams (e.g., transmission beams 606c, 606d, and 606e) on the network entity 604 and a single reception beam (e.g., reception beam 608c) on the UE 602 may form corresponding BPLs for communication between the network entity 604 and the UE 602. In another example, multiple CSI-RS transmission beams (e.g., transmission beams 606c, 606d, and 606e) on the network entity 604 and multiple reception beams (e.g., reception beams 608c and 608d) on the UE 602 may form multiple BPLs for communication between the network entity 604 and the UE 602. In this example, the first BPL may include transmission beam 606c and reception beam 608c, the second BPL may include transmission beam 608d and reception beam 608c, and the third BPL may include transmission beam 608e and reception beam 608d.

[0113] The network entity (e.g., gNB) may be a full-duplex network entity, and the UE (e.g., wireless communication device) may be a full-duplex or half-duplex UE. By way of example, aspects of the present disclosure may be directed to full-duplex (FD) network entities and half-duplex (HD) UEs. Figure 7A and Figure 7Bis a schematic illustration of a wireless communication network 700 including an FD network entity 702 (commonly represented as a base station tower and associated antenna arrays), an HD UE 720, a first HD UE 726, and a second HD UE 728, according to some aspects of the present disclosure. The FD network entity 702 can be Figure 1 , Figure 2 , Figure 3 , Figure 5 and / or Figure 6 any one of the network entities illustrated in Figure 1 , Figure 2 , Figure 3 , Figure 5 and / or Figure 6 (e.g., network entity, base station, gNB, TRP, scheduling entity, CU / DU / RU), and the HD UE 720, the first HD UE 726, and the second HD UE 728 can be

[0114] In Figure 7A and Figure 7B , the FD network entity 702 includes a first antenna array 704 facing a first direction, a second antenna array 706 facing a second direction, and a third antenna array 708 facing a third direction. The first direction, the second direction, and the third direction can be angularly separated from each other by approximately 120 degrees, thereby providing 360-degree coverage around the tower of the FD network entity 702.

[0115] Each of the first antenna array 704, the second antenna array 706, and the third antenna array 708 can be divided into two panels (e.g., the third antenna array 709 is depicted as having a first panel 710 and a second panel 712) with a physical separation (not shown) therebetween. As shown, each of the two panels can be a subarray of antenna elements. A given panel can transmit and / or receive a beam or a beam group. Each of the first antenna array 704, the second antenna array 706, and the third antenna array 708 can be configured for MU-MIMO operation. More specifically, any one or more of the first antenna array 704, the second antenna array 706, and the third antenna array 708 can be configured for downlink / uplink (DL / UL) MU-MIMO (i.e., full duplex, including subband full duplex) operation. Of course, any one or more of the first antenna array 704, the second antenna array 706, and the third antenna array 708 can be configured for DL MU-MIMO (e.g., simultaneous downlink transmission of signals to at least two UEs) or for UL MU-MIMO (e.g., simultaneous uplink reception of signals from at least two UEs) operation.

[0116] In Figure 7A andFigure 7B In Figure 7B , the third antenna array 708 of the FD network entity 702 is depicted as being configured with a first panel 710 and a second panel 712. In this example, the first panel 710 and the second panel 712 are laterally shifted from each other (e.g., they do not overlap). The first panel 710 is illustrated as a transmitting panel and the second panel 712 is illustrated as a receiving panel.

[0117] Turning Figure 7A , the FD network entity 702 may participate in communication with a UE (not shown) inside or in front of the building 716. The FD network entity 702 may simultaneously (or substantially simultaneously) participate in communication with the HD UE 720. During the time when the first signal 714 is transmitted in full duplex from the first panel 710 to the UE inside or in front of the building 716 simultaneously (or substantially simultaneously) and the second signal 722 is received from the HD UE 720 at the second panel 712, a portion of the energy of the first signal 714 may be reflected from the building 716. The energy of the first signal 714 reflected from the building 716 is referred to herein as the reflected first signal 718. The reflected first signal 718 may be reflected towards the FD network entity 702 and may be received as interference at the second panel 712 of the third antenna array 708 of the FD network entity 702. Additionally, the self-interference 721 from the transmission of the first signal 714 to the UE inside or in front of the building 716 may also be received as interference at the second panel 712. Other interference sources may include interference from adjacent network entities (not shown). Since it is a half-duplex UE, the HD UE 720 does not receive during the time when it uplink-transmits the second signal 722 to the FD network entity 702; thus, the HD UE 720 does not receive self-interference.

[0118] Turning Figure 7B ( Figure 7A simplified version of Figure 7B ) in which the building 716 is omitted (and thus, the type of interference represented by the reflected first signal 718 in Figure 7B is omitted). The first HD UE 726, self-interference 727, and second HD UE 728 are shown. Figure 7A This may more clearly depict the operation of the FD network entity 702 with the first HD UE 726 and the second HD UE 728. As described similarly in connection with Figure 7A , the FD network entity 702 may simultaneously (or substantially simultaneously) transmit a third signal 724 from the first panel 710 to the first HD UE 726 and receive a fourth signal 730 from the second HD UE 728 at the second panel 712, where the third signal 724 and the fourth signal 730 are at different frequencies within a given bandwidth. Such simultaneous (or near-simultaneous) transmission and reception may be implemented using, for example, SBFD. Figure 7B This may more clearly depict the operation of the FD network entity 702 with the first HD UE 726 and the second HD UE 728. As described similarly in connection with Figure 7A , the FD network entity 702 may simultaneously (or substantially simultaneously) transmit a third signal 724 from the first panel 710 to the first HD UE 726 and receive a fourth signal 730 from the second HD UE 728 at the second panel 712, where the third signal 724 and the fourth signal 730 are at different frequencies within a given bandwidth. Such simultaneous (or near-simultaneous) transmission and reception may be implemented using, for example, SBFD. Figure 7A As described similarly in connection with Figure 7A , the FD network entity 702 may simultaneously (or substantially simultaneously) transmit a third signal 724 from the first panel 710 to the first HD UE 726 and receive a fourth signal 730 from the second HD UE 728 at the second panel 712, where the third signal 724 and the fourth signal 730 are at different frequencies within a given bandwidth. Such simultaneous (or near-simultaneous) transmission and reception may be implemented using, for example, SBFD.

[0119] Figure 8A and Figure 8B are time - frequency resource diagrams depicting various examples of full - duplex sub - bands according to some aspects of the present disclosure. Figure 8A is a diagram illustrating two examples of in - band full - duplex (IBFD) 800 multiplexing according to some aspects of the present disclosure. In Figure 8A the example shown, time is illustrated along the horizontal axis and frequency is illustrated along the vertical axis. The first example 802 of IBFD is depicted on the left, and the second example 804 is depicted on the right. In the first example 802, the UL time - frequency resource 806 completely overlaps with a portion of the DL time - frequency resource 808. In the second example 804, the UL time - frequency resource 810 partially overlaps with a portion of the DL time - frequency resource 812. Thus, a device employing IBFD 800 multiplexing (e.g., a network entity, a base station, a gNB, a scheduling entity, and / or a UE, a scheduled entity) can transmit and receive on the same time and frequency resources. That is, the device can transmit and receive simultaneously at the same frequency (or multiple frequencies) at the same time (or multiple times). The UL and DL share the same time and frequency resources. The overlap in the time - frequency resources can be complete (as in the first example 802) or partial (as in the second example 804).

[0120] Figure 8B is a diagram illustrating two examples of sub - band full - duplex (SBFD) 814 multiplexing according to some aspects of the present disclosure. In Figure 8B the example shown, time is illustrated along the horizontal axis and frequency is illustrated along the vertical axis. The first example 816 of SBFD is depicted on the left, and the second example 818 of SBFD is depicted on the right. In the first example 816, the UL sub - band 820 is frequency - division multiplexed between a first DL sub - band 822 (i.e., a set of higher - frequency downlink resources) and a second DL sub - band 824 (i.e., a set of lower - frequency downlink resources). An upper guard band 826 is interposed between the UL sub - band 820 and the first DL sub - band 822. A lower guard band 828 is interposed between the UL sub - band 820 and the second DL sub - band 824. All frequencies are non - overlapping. In the second example 818, the SBFD UL sub - band 830 and the DL sub - band 834 are spaced apart by a guard band 832. Again, all frequencies are non - overlapping. Thus, a device employing SBFD 814 multiplexing (e.g., a network entity, a base station, a gNB, a scheduling entity, and / or a UE, a scheduled entity) can transmit and receive at the same time but in different sub - bands or BWPs of the same carrier bandwidth (i.e., in different frequency resources in the unpaired spectrum within the same carrier bandwidth). Since there is no overlap between the frequencies of the uplink and the downlink, SBFD as illustrated in the first example 816 and the second example 818 can be referred to as non - overlapping SBFD.

[0121] The present disclosure relates to the setting of a start time and the establishment of an application time associated with a semi-persistent (SP) SBFD indication or an aperiodic (AP) SBFD indication received by a half-duplex wireless communication device (e.g., a UE) from a full-duplex network entity (e.g., a gNB). The half-duplex wireless communication device may need to change baseband parameters in response to an SP SBFD indication or an AP SBFD indication because, for example, a first bandwidth associated with a half-duplex downlink may be greater than a second bandwidth associated with a downlink or uplink sub-band of an SBFD symbol or time slot.

[0122] Figure 9 Call flow diagram 900 illustrates two options for defining a start time from which to count an application time (e.g., the time used by a half-duplex UE to reconfigure its transmitter / receiver to accommodate a bandwidth change between half-duplex (HD) and sub-band full-duplex (SBFD) operation or vice versa) after receiving a semi-persistent SBFD indication or an aperiodic SBFD indication. At 906, a full-duplex network entity 902 (e.g., a gNB) conveys a message containing a semi-persistent SBFD indication or an aperiodic SBFD indication to a half-duplex wireless communication device 904 (e.g., a UE). For example, the message may include at least one of MAC-CE, DCI, or RRC signaling (e.g., via cell common indication).

[0123] At 908, according to the first option, the half-duplex wireless communication device 904 sets a start time from which to count the application time. The application time may be the time used by the half-duplex wireless communication device 904 to reconfigure its transmitter / receiver to accommodate a bandwidth change between half-duplex HD and SBFD operation or vice versa. According to the first option, the start time may be defined as the end of the message. For example, the start time may be defined as the end of at least one of MAC-CE, DCI, or RRC signaling. If the first option is utilized, the half-duplex wireless communication device 904 may start a clock (e.g., an application time clock) (not shown) and start counting the application time.

[0124] At 910, the half-duplex wireless communication device 904 sends an ACK for the MAC-CE or DCI, as appropriate. Generally, and in response to RRC signaling, no ACK is sent.

[0125] At 912, according to the second option, the half-duplex wireless communication device 904 is set to start counting the application time (e.g., the time used by the half-duplex wireless communication device 904 to reconfigure its transmitter / receiver to accommodate the bandwidth change between half-duplex HD and SBFD operations or vice versa). According to the second option, the start time can be defined as the end of the ACK associated with the MAC-CE or DCI, as the case may be. If the second option is utilized, the half-duplex wireless communication device 904 may start a clock (e.g., an application time clock) (not shown) and start counting the application time.

[0126] Associated with receiving the semi-persistent SBFD indication or the aperiodic SBFD indication at 906, at 912, the half-duplex wireless communication device may update certain parameters and / or retune various RF and / or baseband parameters according to the requirements imposed on the half-duplex wireless communication device 904 associated with the bandwidth change between HD and SBFD operations.

[0127] At 916, the clock set to start counting the application time from the start time defined by option 1 at 908 or option 2 at 912 expires.

[0128] At 918, the half-duplex wireless communication device 904 transmits or receives a first symbol after reconfiguration for the bandwidth change at 914. According to some aspects, the selection of the first option or the second option may be preconfigured (e.g., via an original equipment manufacturer (OEM) based on one or more criteria or specifications).

[0129] Figure 10A and Figure 10B is a diagram illustrating an example of time division multiplexing between HDDL 1002, SBFD 1000, and HD UL 1004. HDDL 1002 is before SBFD 1000 (UL / DL) in the time domain, and HD UL 1004 is after SBFD 1000 (UL / DL) in the time domain. SBFD 1000 (UL / DL) does not overlap with HDDL 1002 or HD UL 1004 in time. SBFD 1000 (e.g., UL sub-band 1020, first DL sub-band 1022, and second DL sub-band 1024) is similar to the first example 816 of the UL sub-band 820, first DL sub-band 822, and second DL sub-band 824 shown and described in connection with Figure 8B Although the following example utilizes the SBFD 1000 UL sub-band 1020, first DL sub-band 1022, and second DL sub-band 1024, the example can be extended to as described in connection with Figure 8BSecond example 818 of the SBFD UL sub-band 830 and DL sub-band 834 shown and described. In fact, all aspects described herein can be applied to SBFD sub-bands having two or three different sub-bands or BWPs within a given carrier bandwidth 1012.

[0130] In Figure 10A and Figure 10B the example shown, time is illustrated along the horizontal axis and frequency is illustrated along the vertical axis. In Figure 10A the various modulated uplinks and downlinks are subdivided according to the first bandwidth part (BWP) designation definition. In Figure 10B the various modulated uplinks and downlinks are subdivided according to the second bandwidth part (BWP) designation definition.

[0131] In Figure 10A and Figure 10B the UL sub-band 1020 is frequency division multiplexed between the first DL sub-band 1022 and the second DL sub-band 1024. In this example, the second DL sub-band 1024 occupies a bandwidth including frequencies greater than the frequencies occupied by the bandwidth of the UL sub-band 1020, and the second DL sub-band 1024 occupies a bandwidth including frequencies less than the frequencies occupied by the UL sub-band 1020. An upper guard band 1026 may be interposed between the UL sub-band 1020 and the first DL sub-band 1022. A lower guard band 1028 may be interposed between the UL sub-band 1020 and the second DL sub-band 1024. The UL sub-band 1020, the first DL sub-band 1022, and the second DL sub-band 1024 do not overlap in frequency.

[0132] In Figure 10A and Figure 10Bdepicts a first application time 1030 and a second application time 1032. According to some aspects, the first application time 1030 and the second application time 1032 may be referred to as a first switching time and a second switching time. The first application time 1030 can be a time that can be used by a half-duplex UE to update certain parameters and / or retune various RF and / or baseband parameters (e.g., adjust the -3dB points of various high-pass, low-pass, and / or band-pass filters) to switch between a first bandwidth (e.g., the first bandwidth accommodating the HDDL 1002 signal) and a second bandwidth (e.g., the UL sub-band 1020 or the relatively smaller bandwidth in the first DL sub-band 1022 and / or the second DL sub-band 1024) for the transmitter and / or receiver. Conversely, the second application time 1032 can be a time that can be used by a half-duplex UE to update certain parameters and / or retune various RF and / or baseband parameters (e.g., adjust the -3dB points of various high-pass, low-pass, and / or band-pass filters) to switch between the second bandwidth and the first bandwidth for the transmitter and / or receiver. The first application time 1030 can be the same as, less than, or greater than the second application time.

[0133] According to some aspects, rules can be established and / or specific values can be defined to represent the first application time 1030 and the second application time 1032. Rules and / or specific values can be defined to cover various SBFD symbol or time slot patterns.

[0134] For example, according to some aspects, the values of the first application time 1030 and the second application time 1032 can be pre-configured (e.g., via an original equipment manufacturer (OEM) based on one or more standards or specifications). In Figure 10A the example, the carrier bandwidth 1012 can be divided into a first BWP 1006 (BWP0), a second BWP 1008 (BWP1), and a third BWP 1010 (BWP2). The BWPs can have misaligned center frequencies. According to one example, the first BWP 1006, the second BWP 1008, and the third BWP 1010 can be equal. According to another example, the first BWP 1006 and the third BWP 1010 can be equal and can be greater than, equal to, or less than the second BWP 1008. According to another example, the first BWP 1006, the second BWP 1008, and the third BWP 1010 can be unequal. In an example where there are two or more bandwidth values for two or more BWPs of the time-frequency resources for SBFD 1000 modulation, the first application time 1030 and / or the second application time 1032 can depend on the minimum bandwidth or the maximum bandwidth of the two or more BWPs.

[0135] According to another aspect, the first application time 1030 and the second application time 1032 may depend on the subcarrier spacing (SCS) of at least one of the first BWP 1006, the second BWP 1008, or the third BWP 1010. In an example where there are two or more SCS values for two or more BWPs of the time-frequency resources modulated for SBFD 1000, the first application time 1030 and / or the second application time 1032 may depend on the minimum SCS or the maximum SCS of the two or more BWPs.

[0136] According to another aspect, the first application time 1030 and / or the second application time 1032 may be configured by a network entity (e.g., gNB) for a wireless communication device based on the capabilities of the wireless communication device. For example, the wireless communication device may report its capabilities to the network entity, and the network entity may configure the application time based on the reported capabilities. The network entity may then send the configured application time (e.g., the first application time 1030 and / or the second application time 1032) to the wireless communication device. According to some aspects, the network entity may configure one application time, such as in a case where the first application time 1030 is the same as the second application time 1032, or in a case where only one of the first application time 1030 or the second application time 1032 is updated or otherwise configured. According to some aspects, the network entity may configure two application times, such as in a case where the first application time 1030 is different from the second application time. For example, the capabilities may be adjusted according to the sizes of the DL and UL BWPs, according to the sizes of the SCSs associated with the DL and UL BWPs, and / or according to a given pair of DL and / or UL BWPs and SCSs.

[0137] As described above, and as Figure 10A and Figure 10B illustrated, there may be multiple BWPs for HD and / or FD symbols and / or time slots. In Figure 10A the example, the carrier bandwidth 1012 is divided into a set having a first BWP 1006, a second BWP 1008, and a third BWP 1010; the center frequencies of the BWPs are not aligned. In Figure 10BIn the example, in the carrier bandwidth 1012, the subbands modulated by SBFD 1000 are divided into a first pair including UL BWP1 1014 and DL BWP1 1016, where DL BWP1 1016 is a discontinuous DL BWP. The first pair of UL BWP1 1014 and DL BWP1 1016 may have aligned center frequencies. In other words, the center frequency of the continuous UL BWP1 1014 may be aligned with the center frequency of the discontinuous DL BWP1 1016. The concept of BWP pairs can be extended to consider a second pair formed by BWP1 (i.e., the combination of UL BWP1 1014 and DL BWP1 1016) and BWP2 (i.e., DL / UL BWP2 1018). In the example of the second pair of BWPs, DL / UL BWP2 1018 is depicted as being equal to the carrier bandwidth 1012. However, in other examples, DL / UL BWP2 1018 may not be equal to the carrier bandwidth 1012.

[0138] According to Figure 10A and Figure 10B both examples, the first application time 1030 and the second application time 1032 can be established according to the set (e.g., Figure 10A ) and paired (e.g., Figure 10B ) grouping of BWPs. In combination with the set and paired grouping of BWPs, the first application time 1030 and the second application time 1032 can depend on the subcarrier spacing (SCS) of at least one of UL BWP1 1014, DL BWP1 1016, or DL / UL BWP2 1018. In examples where there are two or more SCS values for two or more BWPs in a set formed by BWP0 1006, BWP1 1008, and BWP1 1010, a first pair formed by UL BWP1 1014 and DL BWP1, or a second pair formed by BWP1 (i.e., the combination of UL BWP1 1014 and DL BWP1 1016) and BWP2 (i.e., DL / UL BWP2 1018), the first application time 1030 and / or the second application time 1032 can depend on the minimum SCS or the maximum SCS of a given set or pair. According to some aspects, as described above, the first application time 1030 and the second application time 1032 can be the same or different, and can change, for example, depending on whether the change in the bandwidth of the transmitter and / or receiver is a change from a first bandwidth associated with an SBFD signal to a second bandwidth associated with an HD signal.

[0139] According to another example, a first fixed (e.g., predetermined) value associated with a first application time 1030 for switching from HD to SBFD and a second fixed value associated with a second application time 1032 for switching from SBFD to HD can be established (where a BWP is defined as a set (e.g., Figure 10A ), or a pair (e.g., Figure 10B )). According to one aspect, a switching delay (e.g., application time) of 8 time slots can be referred to as a type 1 BWP switching delay, a switching delay of 18 time slots can be referred to as a type 2 BWP switching delay, and a switching delay of, for example, 3 time slots can be referred to as a new type (e.g., type 3 BWP switching delay). The type 3 BWP switching delay can be utilized, where the switching delay can be shorter than the switching delay associated with the type 1 or type 2 BWP switching delay. The type 3 BWP switching delay can be a switching delay that can be optimized in instances where, for example, non-BW-related parameters associated with a target DL and UL BWP pair / set do not change relative to corresponding non-BW-related parameters associated with a source DL and UL BWP pair / set. In such examples, it may not be necessary to update certain parameters and / or retune various RF and / or baseband parameters. Either the first application time 1030 or the second application time 1032 can correspond to a type 1, type 2, or type 3 BWP switching delay. As indicated above, the duration of the application time can be defined in connection with a switch between a pair of target and source DL and UL BWP sets or a DL and UL BWP pair including HD and FD BWPs (i.e., where the HD and FD DL and UL BWP sets or pairs can each be associated with different BWP switching delay types). According to such examples, the application time can be defined for switching between target and source DL and UL BWPs corresponding to various BWP types.

[0140] As a first example, consider a switch between a first BWP set and a second BWP set, which can have a switching latency of 18 time slots (e.g., type 2) due to different non-BW-related baseband parameters (including, for example, pdcch-config, pdsch-config, sps-config, radioLinkMonitoringConfig, etc.) for the first BWP set (e.g., source) and the second BWP set (e.g., target). As a second example, consider a switch between a third BWP set and the second BWP set, which can have a switching latency of 3 time slots (e.g., type 3) since the same non-BW-related baseband parameters are associated with both the third BWP set and the second BWP set. According to the second example, it will not be necessary to change or tune the non-BW-related baseband parameters, thereby reducing the switching time. Thus, the type 3 BWP switching delay (i.e., latency, application time) of the second example can be associated with a shorter (compared to type 1 and type 2) and optimized BWP switching latency.

[0141] According to another example, the application time may depend only on the target BWP type (e.g., a set or pair of HD or FD BWPs).

[0142] According to yet another example, the application time may be configured by a network entity (e.g., gNB) based on the radio communication device capabilities for each DL / UL BWP and SCS pair for a given source / target BWP type. For example, if the source and target BWP sets or pairs have different types, the radio communication device may only have the capability for an application time of 18 time slots or 8 time slots. However, if the source and target BWP sets or pairs have the same type (i.e., non-BW baseband parameters do not need to be retuned or changed between the source and target BWP sets or pairs), the radio communication device may have the capability for an application time of 1 or 3 time slots.

[0143] Figure 11 FIG. is a block diagram illustrating an example of a hardware implementation of a radio communication device 1100 (e.g., a user equipment, a scheduled entity) employing a processing system 1114 in accordance with some aspects. The radio communication device 1100 may be similar to, for example Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 and / or any one of the radio communication devices, UEs, or scheduled entities of FIG. 7.

[0144] In accordance with various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1114 that includes one or more processors such as processor 1104. Examples of processor 1104 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, the radio communication device 1100 may be configured to perform any one or more of the functions described herein. That is, the processor 1104 as utilized in the radio communication device 1100 may be used to implement, for example, any one or more of the methods or processes described and illustrated in Figure 9 , Figure 10A , Figure 10B and / or Figure 12 .

[0145] In this example, a processing system 1114 can be implemented using a bus architecture, which is generally represented by bus 1102. Bus 1102 can include any number of interconnected buses and bridges, depending on the specific application and overall design constraints of the processing system 1114. Bus 1102 communicatively couples various circuits of one or more processors (generally represented by processor 1104), memory 1105, and a computer-readable medium (generally represented by computer-readable medium 1106) together. Bus 1102 can also link various other circuits (such as a timing source, peripherals, voltage regulators, and power management circuits), which are well known in the art and will not be described further herein.

[0146] Bus interface 1108 provides an interface between bus 1102 and RF and / or baseband circuitry 1109 (e.g., low-pass, band-pass, high-pass filters). RF and / or baseband circuitry 1109 is operatively coupled to transceiver 1110. For example, transceiver 1110 can be a wireless transceiver. Transceiver 1110 provides components for communicating with various other devices via a transmission medium (e.g., an air interface). Transceiver 1110 can also be coupled to one or more antenna arrays 1120. Transceiver 1110 can be a wireless transceiver. Bus interface 1108 further provides an interface between bus 1102 and user interface 1112 (e.g., a keypad, a display, a touch screen, speakers, a microphone, control features, etc.). Of course, such a user interface 1112 is optional and can be omitted in some examples.

[0147] One or more processors, such as processor 1104, are responsible for managing bus 1102 and general processing, including executing software stored on computer-readable medium 1106. Software should be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, executing threads, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software can reside on computer-readable medium 1106. When executed by processor 1104, the software causes processing system 1114 to perform the various processes and functions described herein for any particular device.

[0148] The computer-readable medium 1106 can be a non-transitory computer-readable medium and can be referred to as a computer-readable storage medium or a non-transitory computer-readable medium. The non-transitory computer-readable medium can store computer-executable code (e.g., processor-executable code). The computer-executable code can include code for causing a computer (e.g., a processor) to implement one or more functions described herein. The non-transitory computer-readable medium includes, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 1106 can reside within the processing system 1114, be located external to the processing system 1114, or be distributed across multiple entities including the processing system 1114. The computer-readable medium 1106 can be embodied in a computer program product or article of manufacture. By way of example, the computer program product or article of manufacture can include the computer-readable medium in a packaging material. In some examples, the computer-readable medium 1106 can be a part of the memory 1105. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure, depending on the particular application and overall design constraints imposed on the overall system. The computer-readable medium 1106 and / or the memory 1105 can also be used to store data manipulated by the processor 1104 when executing software. For example, the memory 1105 can store the start time memory location 1115 and the application time memory location 1116.

[0149] In some aspects of the present disclosure, the processor 1104 may include communication and processing circuitry 1141 configured for various functions, including communicating, for example, with network entities (e.g., gNB, base station, scheduled entity), a network core (e.g., 5G core network), and another wireless communication device (e.g., UE, scheduled entity), or any other entity (such as, for example, local infrastructure or an entity communicating with the wireless communication device 1100 via the Internet (such as a network provider)). In some examples, the communication and processing circuitry 1141 may include one or more hardware components providing a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). Additionally, the communication and processing circuitry 1141 may be configured to receive a configuration corresponding to multiple bandwidth parts (BWPs) associated with half-duplex mode and SBFD mode, the configuration being based on each DL / UL BWP - subcarrier spacing pair and the capabilities of the wireless communication device for a given source or target BWP type. The communication and processing circuitry 1141 may be further configured to execute communication and processing instructions 1151 (e.g., software) stored on a computer-readable medium 1106 to implement one or more functions described herein.

[0150] In some aspects of the present disclosure, the processor 1104 may include semi-persistent subband full-duplex (SBFD) indication or aperiodic SBFD indication receiving circuitry 1142, which is configured for various functions, including receiving at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication. The semi-persistent SBFD indication or the aperiodic SBFD indication may be received from a network entity (e.g., gNB, base station, scheduling entity). According to some examples, the application time may depend on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication. According to some examples, the application time may be associated with a switch between half-duplex mode and SBFD mode. The application time may be fixed. According to some examples, the application time may depend on the subcarrier spacing of multiple downlink and uplink subbands of SBFD communication. According to some aspects, the application time may be associated with a switch between half-duplex mode and SBFD mode and be at least one of the following: defined in conjunction with a switch between a target BWP type and a source BWP type, or depend on the target BWP type. According to some aspects, the application time may be associated with a bandwidth change between half-duplex mode and SBFD mode and may depend on whether the value of a non-BWP related baseband parameter changes in response to a switch between half-duplex mode and SBFD mode. In some examples, the value of a non-BWP related RF and / or baseband parameter may be changed in the RF and / or baseband circuitry 1109.

[0151] According to some aspects, the SBFD mode may include multiple sub-bands, each of the multiple sub-bands having a different center frequency. The application time may be configured by a network entity (e.g., gNB) for a wireless communication device. The wireless communication device may report its capabilities to the network entity. The network entity may configure a specific application time for the wireless communication device based on the capabilities of the wireless communication device. According to some examples, the wireless communication device may receive a configuration that allocates the application time. The configuration may be based on the capabilities of the wireless communication device. In some examples, the capabilities may be determined on a per DL / UL BWP-subcarrier spacing pair basis. The semi-persistent SBFD indication or aperiodic SBFD indication receiving circuit 1142 may be further configured to execute semi-persistent SBFD indication or aperiodic SBFD indication receiving instructions 1152 (e.g., software) stored on a computer-readable medium 1106 to implement one or more functions described herein.

[0152] In some aspects of the present disclosure, the processor 1104 may include a start time / application time establishment and counting circuit 1143, which is configured for various functions, including, for example, receiving a downlink symbol or transmitting an uplink symbol after the expiration of the application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication. For example, the start time may be stored in a start time memory location 1115 in the memory 1105 of the wireless communication device 1100. For example, the application time may be stored in an application time memory location 1116 in the memory 1105 of the wireless communication device 1100.

[0153] In some aspects, the start time / application time establishment and counting circuit 1143 may be further configured to obtain the start time. In some examples, the start time may coincide with at least one of the following: the end of a media access control-control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, or the end of a first acknowledgement (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI. In some examples, the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned. The start time / application time establishment and counting circuit 1143 may be further configured to execute start time / application time establishment and counting instructions 1153 (e.g., software) stored on a computer-readable medium 1106 to implement one or more functions described herein.

[0154] In some aspects of the present disclosure, the processor 1104 may include receive (RX) / transmit (TX) downlink (DL) or uplink (UL) communication circuitry 1144 that is configured for various functions, including, for example, receiving or transmitting downlink communication or uplink communication in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode after the expiration of an application time counted from a start time. The RX / TX DL / UL communication circuitry 1144 may be further configured to execute RX / TX DL / UL communication instructions 1154 (e.g., software) stored on a computer-readable medium 1106 to implement one or more of the functions described herein.

[0155] Figure 12 is a flowchart illustrating an example process 1200 (e.g., method) of wireless communication in a wireless communication network at a wireless communication device according to some aspects of the present disclosure. As described below, in certain specific implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be required for the specific implementation of all embodiments. In some examples, process 1200 may be performed by the wireless communication device 1100 illustrated and described in conjunction with Figure 11 The wireless communication device 1100 may be similar to, for example, Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 9 and / or Figure 11 any one of the wireless communication devices, UEs, or scheduled entities. In some examples, process 1200 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0156] At block 1202, the wireless communication device may receive at least one of a semi-persistent subband full-duplex (SBFD) indication or an aperiodic SBFD indication. For example, the semi-persistent or aperiodic SBFD indication receiving circuitry 1142 illustrated and described above in conjunction with Figure 11 may provide the components for receiving at least one of a semi-persistent subband full-duplex (SBFD) indication or an aperiodic SBFD indication.

[0157] At block 1204, the wireless communication device may receive downlink symbols or transmit uplink symbols in a half-duplex mode after the expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication. For example, in conjunction with Figure 11The illustrated and described start / application time establishment and counting circuit 1143 may provide a component for receiving a downlink symbol or transmitting an uplink symbol after the expiration of an application time counted from a start time associated with at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication. According to some aspects, the start time may coincide with at least one of the following: the end of a media access control-control element (MAC-CE) carrying at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication, or the end of a first acknowledgment (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI. According to some aspects, the application time may depend on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication. According to some aspects, the application time may be associated with a handover between a half-duplex mode and an SBFD mode. The application time may be fixed. In some examples, the application time may be configured by a network entity (e.g., gNB, scheduling entity) to a wireless communication device. In one example, the wireless communication device may report its capabilities to the network entity. The network entity may determine a specific application time and configure the specific application time for the wireless communication device (e.g., based on the reported capabilities of the wireless communication device).

[0158] At block 1206, the wireless communication device may optionally receive or transmit downlink communication or uplink communication, respectively, according to the SBFD mode in a configured downlink / uplink (DL / UL) bandwidth part (BWP) after the expiration of the application time counted from the start time. For example, in conjunction with Figure 11The illustrated and described RX / TX DL / UL communication circuitry 1144 may provide components for receiving or transmitting downlink communication or uplink communication, respectively, in a configured downlink / uplink (DL / UL) bandwidth part (BWP) after the expiration of an application time counted from a start time, according to an SBFD mode. In some examples, the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP may be a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP may be aligned. In some examples, a wireless communication device may receive a configuration that allocates an application time, based on the capabilities of the wireless communication device per DL / UL BWP-subcarrier spacing pair. In some examples, a wireless communication device may receive a configuration corresponding to multiple bandwidth parts (BWPs) associated with a half-duplex mode and an SBFD mode. The configuration may be based on the capabilities of the wireless communication device per DL / UL BWP-subcarrier spacing pair and for a given source or target BWP type.

[0159] Figure 13 is a block diagram illustrating an example of a hardware implementation of a network entity 1300 (e.g., gNB, base station, scheduling entity) employing a processing system 1314 according to some aspects. The network entity 1300 may be similar to, for example Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , FIG. 7, and / or Figure 9 any one of the network entities or scheduling entities of.

[0160] The processing system 1314 may be substantially the same as the processing system 1114 illustrated in Figure 11 , including a bus interface 1308, RF and / or baseband circuitry 1309, a bus 1302, a memory 1305, a processor 1304, and a computer-readable medium 1306. According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1314 that includes one or more processors, such as processor 1304. Additionally, the network entity 1300 may include a user interface 1312, a transceiver 1310, and one or more antenna arrays 1320, which are substantially similar to those described above in Figure 11 . For example, the transceiver 1310 may be a wireless transceiver. The processor 1304 utilized in the network entity 1300 may be used to implement any one or more of the processes described herein and illustrated in, for example Figure 9 , FIG. 10, and / or Figure 14 .

[0161] In some aspects of the present disclosure, the processor 1304 may include communication and processing circuitry 1341 configured for various functions, including communicating, for example, with a wireless communication device (e.g., a UE), a network core (e.g., a 5G core network), and another network entity (e.g., a gNB, a base station, a scheduling entity) or any other entity (such as, for example, a local infrastructure or an entity communicating with the network entity 1300 via the Internet (such as a network provider)). In some examples, the communication and processing circuitry 1341 may include one or more hardware components providing a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). Additionally, the communication and processing circuitry 1341 may be configured to transmit a configuration corresponding to multiple bandwidth parts (BWPs) associated with half-duplex mode and SBFD mode, the configuration being based on each DL / UL BWP-subcarrier spacing pair and for the capabilities of a wireless communication device of a given source or target BWP type. The communication and processing circuitry 1341 may be further configured to execute communication and processing instructions 1351 (e.g., software) stored on a computer-readable medium 1306 to implement one or more functions described herein.

[0162] In some aspects of the present disclosure, the processor 1304 may include semi-persistent subband full-duplex (SBFD) indication or aperiodic SBFD indication transmission circuitry 1342 configured for various functions, including transmitting at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication. The semi-persistent SBFD indication or the aperiodic SBFD indication may be transmitted to a wireless communication device (e.g., a UE, a scheduled entity). According to some examples, the application time may depend on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication. According to some examples, the application time may be associated with a switch between half-duplex mode and SBFD mode. The application time may be fixed. According to some examples, the application time may depend on the subcarrier spacing of multiple downlink and uplink subbands of SBFD communication. According to some aspects, the application time may be associated with a switch between half-duplex mode and SBFD mode and may be at least one of: defined in conjunction with a switch between a target BWP type and a source BWP type, or depending on the target BWP type. According to some aspects, the application time may be associated with a bandwidth change between half-duplex mode and SBFD mode and may depend on whether the value of a non-BWP related baseband parameter changes in response to a switch between half-duplex mode and SBFD mode. In some examples, the value of the non-BWP related baseband parameter may be changed in the RF and / or baseband circuitry 1309.

[0163] According to some aspects, the SBFD mode may include a plurality of sub-bands, each of the plurality of sub-bands having a different center frequency. The application time may be configured by a network entity for a wireless communication device. The wireless communication device may report its capabilities to the network entity. The network entity may configure a specific application time for the wireless communication device based on the capabilities of the wireless communication device. According to some examples, the network entity may send and the wireless communication device may receive a configuration that allocates the application time. The configuration may be based on the capabilities of the wireless communication device. In some examples, the capabilities may be determined on a per DL / UL BWP-subcarrier spacing pair basis. The semi-persistent SBFD indication or non-periodic SBFD indication transmission circuit 1342 may be further configured to execute semi-persistent SBFD indication or non-periodic SBFD indication reception instructions 1352 (e.g., software) stored on a computer-readable medium 1306 to implement one or more of the functions described herein.

[0164] In some aspects of the present disclosure, the processor 1304 may include a start time / application time establishment and counting circuit 1343, which is configured for various functions, including, for example, transmitting a downlink symbol or receiving an uplink symbol after the expiration of the application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the non-periodic SBFD indication. For example, the start time may be stored in a start time memory location 1315 in the memory 1305 of the network entity 1300. For example, the application time may be stored in an application time memory location 1316 in the memory 1305 of the network entity 1300.

[0165] In some aspects, the start time / application time establishment and counting circuit 1343 may be further configured to obtain the start time. In some examples, the start time may coincide with at least one of the following: the end of a media access control-control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the non-periodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the non-periodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the non-periodic SBFD indication, or the end of a first acknowledgment (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI. In some examples, the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned. The start time / application time establishment and counting circuit 1343 may be further configured to execute start time / application time establishment and counting instructions 1353 (e.g., software) stored on a computer-readable medium 1306 to implement one or more of the functions described herein.

[0166] In some aspects of the present disclosure, the processor 1304 may include receive (RX) / transmit (TX) downlink (DL) or uplink (UL) communication circuitry 1344, respectively, which is configured for various functions, including, for example, receiving or transmitting uplink communication or downlink communication in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode after the expiration of an application time counted from a start time. The RX / TX DL / UL communication circuitry 1344 may be further configured to execute RX / TX DL / UL communication instructions 1354 (e.g., software) stored on a computer-readable medium 1306 to implement one or more of the functions described herein.

[0167] Figure 14 is a flowchart illustrating an example process 1400 (e.g., method) of wireless communication in a wireless communication network at a network entity according to some aspects of the present disclosure. As described below, in certain specific implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be required for the specific implementation of all embodiments. In some examples, the process 1400 may be performed by the network entity 1300 illustrated and described in conjunction with Figure 13 The network entity 1300 may be similar to, for example, Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 9 and / or Figure 13 any one of the network entities, gNB, or scheduling entity of

[0168] At block 1402, the network entity may send at least one of a semi-persistent subband full-duplex (SBFD) indication or an aperiodic SBFD indication. For example, the semi-persistent or aperiodic SBFD indication sending circuitry 1342 shown and described above in conjunction with Figure 13 may provide the components for sending at least one of a semi-persistent subband full-duplex (SBFD) indication or an aperiodic SBFD indication.

[0169] At block 1404, the network entity may transmit downlink symbols and receive uplink symbols in the SBFD mode after the expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication. For example, in conjunction with Figure 13The illustrated and described start / application time establishment and counting circuit 1343 may provide components for transmitting a downlink symbol or receiving an uplink symbol after the expiration of an application time counted from a start time associated with at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication. According to some aspects, the start time may coincide with at least one of the following: the end of a media access control-control element (MAC-CE) carrying at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of a semi-persistent SBFD indication or an aperiodic SBFD indication, or the end of a first acknowledgment (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI. According to some aspects, the application time may depend on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication. According to some aspects, the application time may be associated with a switch between a half-duplex mode and an SBFD mode. The application time may be fixed. In some examples, the application time may be configured by a network entity for a wireless communication device. In one example, the wireless communication device may report its capabilities to the network entity. The network entity may determine a specific application time and configure the specific application time for the wireless communication device (e.g., based on the reported capabilities of the wireless communication device).

[0170] At block 1406, the network entity may receive and transmit uplink communication and downlink communication, respectively, in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode after the expiration of the application time counted from the start time. For example, in conjunction with Figure 13 The illustrated and described RX / TX DL / UL communication circuit 1344 may provide components for receiving or transmitting uplink communication or downlink communication, respectively, in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode after the expiration of the application time counted from the start time. In some examples, the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP may be a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP may be aligned. In some examples, the network entity may transmit a configuration allocating the application time, which is based on the capabilities of the wireless communication device for each DL / UL BWP-subcarrier spacing pair. In some examples, the network entity may transmit a configuration corresponding to multiple bandwidth parts (BWPs) associated with the half-duplex mode and the SBFD mode. The configuration may be based on each DL / UL BWP-subcarrier spacing pair and the capabilities of the wireless communication device for a given source or target BWP type.

[0171] Of course, in the above example, Figure 11 the circuitry included in processor 1104 and / or Figure 13 the circuitry included in processor 1304 is provided merely as an example. Other components for performing the described processes or functions may be included within various aspects of the present disclosure, including but not limited to those stored in Figure 11 computer-readable medium 1106 and / or Figure 13 computer-readable medium 1306 or Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , FIG. 7, Figure 9 , Figure 11 and / or Figure 13 any other suitable devices or components described in any of them and utilizing instructions of processes and / or algorithms such as those described herein with respect to Figure 9 , Figure 12 and / or Figure 14 .

[0172] An overview of aspects of the present disclosure is provided below:

[0173] Aspect 1: A wireless communication device, the wireless communication device comprising: a memory; and a processor coupled to the memory, the processor being configured to: receive at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and receive a downlink symbol or transmit an uplink symbol in a half-duplex mode after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

[0174] Aspect 2: The wireless communication device according to aspect 1, wherein the start time coincides with at least one of: an end of a media access control-control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, an end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, an end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, an end of a first acknowledgment (ACK) associated with the MAC-CE, or an end of a second ACK associated with the DCI.

[0175] Aspect 3: The wireless communication device according to aspect 1 or 2, wherein the processor is further configured to: after the expiration of the application time counted from the start time, receive or transmit downlink communication or uplink communication respectively according to the SBFD mode in a configured downlink / uplink (DL / UL) bandwidth part (BWP).

[0176] Aspect 4: The wireless communication device according to any one of aspects 1 to 3, wherein the SBFD modes corresponding to the discontinuous downlink bandwidth part (BWP) and the uplink BWP are fixed modes, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned.

[0177] Aspect 5: The wireless communication device according to any one of aspects 1 to 4, wherein the application time depends on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication.

[0178] Aspect 6: The wireless communication device according to any one of aspects 1 to 5, wherein the processor is further configured to: receive a configuration that allocates the application time, the configuration being based on the capabilities of the wireless communication device for each DL / UL BWP - subcarrier spacing pair.

[0179] Aspect 7: The wireless communication device according to any one of aspects 1 to 6, wherein the application time is associated with the switching between the half - duplex mode and the SBFD mode, and the application time is fixed.

[0180] Aspect 8: The wireless communication device according to any one of aspects 1 to 7, wherein: the SBFD mode is composed of a plurality of sub - bands, and each of the plurality of sub - bands has a different center frequency.

[0181] Aspect 9: The wireless communication device according to any one of aspects 1 to 8, wherein the application time is associated with the bandwidth change between the half - duplex mode and the SBFD mode, and depends on whether the value of the non - BWP - related baseband parameter changes in response to the switching between the half - duplex mode and the SBFD mode.

[0182] Aspect 10: The wireless communication device according to any one of aspects 1 to 9, wherein the application time is associated with the switching between the half - duplex mode and the SBFD mode, and is at least one of the following: defined in combination with the switching between a target BWP switching delay type and a source BWP switching delay type, or depends on the target BWP switching delay type.

[0183] Aspect 11: The wireless communication device according to any one of Aspects 1 to 10, wherein the processor is further configured to: receive a configuration corresponding to a plurality of bandwidth parts (BWPs) associated with a half-duplex mode and an SBFD mode, the configuration being based on each DL / UL BWP-subcarrier spacing pair and the capabilities of the wireless communication device for a given source or target BWP type.

[0184] Aspect 12: A method for wireless communication at a wireless communication device, the method comprising: receiving at least one of a semi-persistent subband full-duplex (SBFD) indication or an aperiodic SBFD indication; and receiving a downlink symbol or transmitting an uplink symbol in a half-duplex mode after the expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

[0185] Aspect 13: The method according to Aspect 12, wherein the start time coincides with at least one of the following: the end of a media access control-control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a first acknowledgment (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI.

[0186] Aspect 14: The method according to Aspect 12 or 13, the method further comprising: after the expiration of the application time counted from the start time, receiving or transmitting downlink communication or uplink communication in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode, respectively.

[0187] Aspect 15: The method according to Aspect 12, wherein the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned.

[0188] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the application time depends on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication.

[0189] Aspect 17: The method according to any one of aspects 12 to 16, the method further comprising: receiving a configuration for allocating the application time, the configuration being based on the capabilities of the wireless communication device for each DL / UL BWP-subcarrier spacing pair.

[0190] Aspect 18: The method according to any one of aspects 12 to 17, wherein the application time is associated with a handover between a half-duplex mode and an SBFD mode, and the application time is fixed.

[0191] Aspect 19: The method according to any one of aspects 12 to 18, the method further comprising: receiving a configuration corresponding to a plurality of bandwidth parts (BWPs) associated with a half-duplex mode and an SBFD mode, the configuration being based on each DL / UL BWP-subcarrier spacing pair and the capabilities of the wireless communication device for a given source or target BWP type.

[0192] Aspect 20: A network entity, the network entity comprising: a memory; and a processor coupled to the memory, the processor being configured to: transmit at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and after the expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, receive an uplink symbol and transmit a downlink symbol in an SBFD mode.

[0193] Aspect 21: The network entity according to aspect 20, wherein the start time coincides with at least one of: the end of a media access control-control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a first acknowledgement (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI.

[0194] Aspect 22: The network entity according to aspect 20 or 21, wherein the processor is further configured to: after the expiration of the application time counted from the start time, receive and transmit uplink communication and downlink communication respectively in a configured downlink / uplink (DL / UL) bandwidth part (BWP) in an SBFD mode.

[0195] Aspect 23: The network entity according to any one of Aspects 20 to 22, wherein the SBFD mode corresponding to the discontinuous downlink bandwidth part (BWP) and the uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned.

[0196] Aspect 24: The network entity according to any one of Aspects 20 to 23, wherein the application time depends on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication.

[0197] Aspect 25: The network entity according to any one of Aspects 20 to 24, wherein the processor is further configured to: transmit a configuration that allocates the application time, the configuration being based on the capabilities of the wireless communication device for each DL / UL BWP - subcarrier spacing pair.

[0198] Aspect 26: The network entity according to any one of Aspects 20 to 25, wherein the application time is associated with the handover between the half - duplex mode and the SBFD mode, and the application time is fixed.

[0199] Aspect 27: The network entity according to any one of Aspects 20 to 26, wherein: the SBFD mode consists of a plurality of sub - bands, and each of the plurality of sub - bands has a different center frequency.

[0200] Aspect 28: The network entity according to any one of Aspects 20 to 27, wherein the application time is associated with the bandwidth change between the half - duplex mode and the SBFD mode, and depends on whether the value of the non - BWP - related baseband parameter changes in response to the handover between the half - duplex mode and the SBFD mode.

[0201] Aspect 29: The network entity according to any one of Aspects 20 to 28, wherein the application time is associated with the handover between the half - duplex mode and the SBFD mode, and is at least one of the following: defined in combination with the handover between the target BWP type and the source BWP type, or depends on the target BWP type.

[0202] Aspect 30: The network entity according to any one of Aspects 20 to 29, wherein the processor is further configured to: transmit a configuration corresponding to a plurality of bandwidth parts (BWP) associated with the half - duplex mode and the SBFD mode, the configuration being based on each DL / UL BWP - subcarrier spacing pair and for the capabilities of the wireless communication device for a given source or target BWP type.

[0203] Aspect 31: A method for wireless communication at a network entity, the method comprising: transmitting at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication; and receiving an uplink symbol and transmitting a downlink symbol in SBFD mode after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

[0204] Aspect 32: The method according to aspect 31, wherein the start time coincides with at least one of: the end of a media access control-control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a first acknowledgement (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI.

[0205] Aspect 33: The method according to aspect 31 or 32, the method further comprising: after expiration of the application time counted from the start time, receiving or transmitting uplink communication or downlink communication respectively in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode.

[0206] Aspect 34: The method according to any one of aspects 31 to 33, wherein the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned.

[0207] Aspect 35: The method according to any one of aspects 31 to 34, wherein the application time depends on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication.

[0208] Aspect 36: The method according to any one of aspects 31 to 35, wherein the processor is further configured to: transmit a configuration allocating the application time, the configuration being based on the capabilities of a wireless communication device for each DL / UL BWP-subcarrier spacing pair.

[0209] Aspect 37: The method according to any one of aspects 31 to 36, wherein the application time is associated with a handover between a half-duplex mode and the SBFD mode, and the application time is fixed.

[0210] Aspect 38: The method according to any one of aspects 31 to 37, wherein: The SBFD mode consists of a plurality of subbands, each of the plurality of subbands having a different center frequency.

[0211] Aspect 39: The method according to any one of aspects 31 to 38, wherein the application time is associated with a bandwidth change between the half-duplex mode and the SBFD mode and depends on whether the value of a non-BWP related baseband parameter changes in response to a switch between the half-duplex mode and the SBFD mode.

[0212] Aspect 40: The method according to any one of aspects 31 to 39, wherein the application time is associated with a switch between the half-duplex mode and the SBFD mode and is at least one of the following: defined in combination with a switch between a target BWP type and a source BWP type, or depends on the target BWP type.

[0213] Aspect 41: The method according to any one of aspects 31 to 40, the method further comprising: transmitting a configuration corresponding to a plurality of bandwidth parts (BWPs) associated with the half-duplex mode and the SBFD mode, the configuration being based on each DL / UL BWP-subcarrier spacing pair and on the capabilities of a wireless communication device for a given source or target BWP type.

[0214] Aspect 42: An apparatus configured for wireless communication, the apparatus comprising at least one component for performing the method according to any one of aspects 12 to 19 or aspects 31 to 41.

[0215] Aspect 43: A non-transitory computer-readable medium storing computer-executable code, comprising code for causing an apparatus to perform the method according to any one of aspects 12 to 19 or aspects 31 to 41.

[0216] Certain aspects of a wireless communication network have been presented with reference to exemplary embodiments. As will be readily understood by those skilled in the art, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0217] By way of example, various aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile communications (GSM). Various aspects can also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA 2000 and / or Evolution-Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0218] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration". Any particular implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior to or better than other aspects of the disclosure. Similarly, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" is used herein to refer to either a direct or an indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For instance, a first object can be coupled to a second object even if the first object never makes direct physical contact with the second object. The term "circuitry" is used broadly, and is intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the performance of the functions described in this disclosure, without limitation as to the type of electronic circuitry) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the performance of the functions described in this disclosure).

[0219] Figures 1 to 14 One or more of the components, steps, features, and / or functions illustrated therein can be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added without departing from the novel features disclosed herein. Figures 1 to 14 The illustrated apparatus, devices, and / or components can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0220] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. It should be understood that, based on design preferences, the specific order or hierarchy of steps in these methods can be rearranged. The appended method claims present the elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented, unless specifically recited herein. Although some of the examples illustrated herein depict only the time domain and the frequency domain, additional domains such as the spatial domain are also contemplated in the present disclosure.

[0221] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims, wherein the reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more". The term "some", unless specifically stated otherwise, means one or more. A phrase referring to "at least one" in a list of items means any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. Structure A and / or B is intended to cover: A; B; and A and B. As used herein, the word "obtain" can mean, for example, acquire, compute, construct, derive, determine, receive, and / or retrieve. The foregoing list is exemplary and not restrictive. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No element of any claim should be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the phrase "step for".

Claims

1. A wireless communication device, the wireless communication device comprising: a memory; and a processor coupled to the memory, the processor being configured to: receive at least one of a semi-persistent sub-band full duplex (SBFD) indication or an aperiodic SBFD indication, and receive a downlink symbol or transmit an uplink symbol in a half-duplex mode after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

2. The wireless communication device according to claim 1, wherein the start time coincides with at least one of the following: the end of a media access control - control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a first acknowledgement (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI.

3. The wireless communication device according to claim 1, wherein the processor is further configured to: receive or transmit downlink communication or uplink communication respectively in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode after expiration of the application time counted from the start time.

4. The wireless communication device according to claim 1, wherein the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned.

5. The wireless communication device according to claim 1, wherein the application time depends on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication.

6. The wireless communication device according to claim 1, wherein the processor is further configured to: receive a configuration that allocates the application time, the configuration being based on the capabilities of the wireless communication device for each DL / UL BWP - subcarrier spacing pair.

7. The wireless communication device according to claim 1, wherein the application time is associated with a switch between a half-duplex mode and the SBFD mode, and the application time is fixed.

8. The wireless communication device according to claim 1, wherein: the SBFD mode is composed of a plurality of sub-bands, each of the plurality of sub-bands having a different center frequency.

9. The wireless communication device according to claim 1, wherein the application time is associated with a bandwidth change between a half-duplex mode and an SBFD mode and depends on whether a value of a non-BWP related baseband parameter changes in response to a handover between the half-duplex mode and the SBFD mode.

10. The wireless communication device according to claim 1, wherein the application time is associated with a handover between a half-duplex mode and an SBFD mode and is at least one of the following: defined in combination with a handover between a target BWP handover delay type and a source BWP handover delay type, or depends on the target BWP handover delay type.

11. The wireless communication device according to claim 1, wherein the processor is further configured to: receive a configuration corresponding to a plurality of bandwidth parts (BWPs) associated with a half-duplex mode and an SBFD mode, the configuration being based on each DL / UL BWP-subcarrier spacing pair and for the capabilities of the wireless communication device for a given source or target BWP type.

12. A method for wireless communication at a wireless communication device, the method comprising: receiving at least one of a semi-persistent sub-band full-duplex (SBFD) indication or an aperiodic SBFD indication, and receiving a downlink symbol or transmitting an uplink symbol in a half-duplex mode after expiration of an application time counted from a start time associated with at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication.

13. The method according to claim 12, wherein the start time coincides with at least one of the following: the end of a media access control-control element (MAC-CE) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a radio resource control (RRC) cell common indication carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi-persistent SBFD indication or the aperiodic SBFD indication, the end of a first acknowledgement (ACK) associated with the MAC-CE, or the end of a second ACK associated with the DCI.

14. The method according to claim 12, the method further comprising: receiving or transmitting downlink communication or uplink communication respectively in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to the SBFD mode after expiration of the application time counted from the start time.

15. The method according to claim 12, wherein the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned.

16. The method according to claim 12, wherein the application time depends on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication.

17. The method according to claim 12, the method further comprising: receiving a configuration that allocates the application time, the configuration being based on the capabilities of the wireless communication device for each DL / UL BWP - subcarrier spacing pair.

18. The method according to claim 12, wherein the application time is associated with a handover between a half - duplex mode and an SBFD mode, and the application time is fixed.

19. The method according to claim 12, the method further comprising: receiving a configuration corresponding to a plurality of bandwidth parts (BWPs) associated with the half - duplex mode and the SBFD mode, the configuration being based on each DL / UL BWP - subcarrier spacing pair and the capabilities of the wireless communication device for a given source or target BWP type.

20. A network entity, the network entity comprising: a memory; and a processor coupled to the memory, the processor being configured to: send at least one of a semi - persistent sub - band full - duplex (SBFD) indication or an aperiodic SBFD indication, and after the expiration of an application time counted from a start time associated with at least one of the semi - persistent SBFD indication or the aperiodic SBFD indication, receive an uplink symbol and send a downlink symbol in SBFD mode.

21. The network entity according to claim 20, wherein the start time coincides with at least one of the following: the end of a media access control - control element (MAC - CE) carrying at least one of the semi - persistent SBFD indication or the aperiodic SBFD indication, the end of a radio resource control (RRC) cell - common indication carrying at least one of the semi - persistent SBFD indication or the aperiodic SBFD indication, the end of a downlink control information (DCI) carrying at least one of the semi - persistent SBFD indication or the aperiodic SBFD indication, the end of a first acknowledgement (ACK) associated with the MAC - CE, or the end of a second ACK associated with the DCI.

22. The network entity according to claim 20, wherein the processor is further configured to: after the expiration of the application time counted from the start time, receive and send uplink communication and downlink communication respectively in a configured downlink / uplink (DL / UL) bandwidth part (BWP) according to SBFD mode.

23. The network entity according to claim 20, wherein the SBFD mode corresponding to a discontinuous downlink bandwidth part (BWP) and an uplink BWP is a fixed mode, and the center frequencies of the discontinuous downlink bandwidth part (BWP) and the uplink BWP are aligned.

24. The network entity according to claim 20, wherein the application time depends on a first subcarrier spacing associated with downlink communication and a second subcarrier spacing associated with uplink communication.

25. The network entity according to claim 20, wherein the processor is further configured to: Transmit a configuration that allocates the application time, the configuration being based on the capabilities of the wireless communication device for each DL / UL BWP - subcarrier spacing pair.

26. The network entity according to claim 20, wherein the application time is associated with a handover between a half - duplex mode and an SBFD mode, and the application time is fixed.

27. The network entity according to claim 20, wherein: The SBFD mode consists of a plurality of sub - bands, each of the plurality of sub - bands having a different center frequency.

28. The network entity according to claim 20, wherein the application time is associated with a bandwidth change between a half - duplex mode and an SBFD mode and depends on whether the value of a non - BWP - related baseband parameter changes in response to the handover between the half - duplex mode and the SBFD mode.

29. The network entity according to claim 20, wherein the application time is associated with a handover between a half - duplex mode and an SBFD mode and is at least one of the following: Defined in combination with a handover between a target BWP type and a source BWP type, or Depends on the target BWP type.

30. The network entity according to claim 20, wherein the processor is further configured to: Transmit a configuration corresponding to a plurality of bandwidth parts (BWPs) associated with a half - duplex mode and an SBFD mode, the configuration being based on each DL / UL BWP - subcarrier spacing pair and for the capabilities of a wireless communication device of a given source or target BWP type.

Images