Anchoring and Complementary Bandwidth Portions for Full-Duplex Operation

Abstract

Aspects of the present disclosure relate to managing bandwidth parts of wireless communications. A bandwidth part (BWP) among a plurality of BWPs of a carrier bandwidth is activated. One of a slot format or a signaling priority of the activated BWP is determined. Based on the determined slot format or signaling priority, a second BWP may be configured to be complementary to the activated BWP, where the second BWP is designated as a new BWP for a user equipment (UE) when the activated BWP is deactivated. Other aspects, embodiments, and features are also claimed and described.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority to U.S. Non - Provisional Patent Application No. 17 / 374,905, filed on July 13, 2021, and U.S. Provisional Patent Application No. 63 / 051,817, filed on July 14, 2020, the contents of which are incorporated herein by reference as if set forth in full below and for all applicable purposes. Technical Field

[0003] The techniques discussed below generally relate to wireless communication systems, and more particularly, to configuring a bandwidth part (BWP) for a scheduled entity in a network that supports full - duplex time - slot formats. Background Art

[0004] Wireless communication transmits from a scheduled entity such as a user equipment (UE) or other wireless communication device to a scheduling entity (such as a base station) in an uplink (UL) transmission and from the scheduling entity to the scheduled entity in a downlink (DL) transmission. Frequency - division duplexing (FDD) communication allows simultaneous two - way communication by separating the frequencies used for uplink (UL) and downlink (DL) transmissions. Separating the frequencies used for UL and DL transmissions allows UL transmissions to be isolated from DL transmissions in the frequency domain. During a full - duplex communication exchange, isolation in the frequency domain reduces interference from the transmitter to the receiver. Time - division duplexing (TDD) communication allows non - simultaneous two - way communication by using a set of frequencies for UL and DL transmissions in the frequency domain and designating some time slots for UL transmissions and other time slots for DL transmissions. In TDD half - duplex communication, UL and DL transmissions occur on the same frequency and are isolated from each other in time. Summary of the Invention

[0005] A summary of one or more aspects of the present disclosure is given below to provide a basic understanding of these aspects. This overview is not an extensive overview of all the expected 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 describe 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 presented later.

[0006] In one example, a user equipment (UE) in a wireless communication network is disclosed, where the UE includes: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, where the processor and the memory are configured to: receive a message indicating an active bandwidth part (BWP) of a plurality of BWPs for the carrier bandwidth of the UE; and communicate with a base station to configure a second BWP among the plurality of BWPs to be complementary to the active BWP based on a determined time slot format or signaling priority of the active BWP, where the second BWP is designated as a new BWP for the UE that is deactivated based on the active BWP.

[0007] In one example, a method for full-duplex communication in a user equipment (UE) is disclosed, where the method includes: receiving a message indicating an active bandwidth part (BWP) of a plurality of BWPs for the carrier bandwidth of the UE; and communicating with a base station to configure a second BWP among the plurality of BWPs to be complementary to the active BWP based on a determined time slot format or signaling priority of the active BWP, where the second BWP is designated as a new BWP for the UE that is deactivated based on the active BWP.

[0008] In one example, a scheduling entity in a wireless communication network is disclosed, including: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, where the processor and the memory are configured to: send a first message indicating an active bandwidth part (BWP) of a plurality of BWPs for the carrier bandwidth of the scheduled entity; and send a second message to the scheduled entity to configure a second BWP among the plurality of BWPs to be complementary to the active BWP based on a determined time slot format or signaling priority of the active BWP, where the second BWP is designated as a new BWP for the UE that is deactivated based on the active BWP.

[0009] In one example, a method for full-duplex communication in a scheduling entity is disclosed, including: sending a first message indicating an active bandwidth part (BWP) of a plurality of BWPs for the carrier bandwidth of the scheduled entity; and sending a second message to the scheduled entity to configure a second BWP among the plurality of BWPs to be complementary to the active BWP based on the determined time slot format or signaling priority of the active BWP, where the second BWP is designated as being deactivated based on the active BWP and is a new BWP for the UE.

[0010] After reviewing the following detailed description, these and other aspects of the present invention will be more fully understood. After reviewing the following description of specific exemplary embodiments in conjunction with the accompanying drawings, other aspects, features, and embodiments will become apparent to those of ordinary skill in the art. While features may be discussed with respect to certain embodiments and figures below, all embodiments may include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more of these features may also be used in accordance with the various embodiments discussed herein. In a similar manner, while exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in a variety of devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0012] Figure 2 is a conceptual diagram of an example of a radio access network (RAN) in accordance with some aspects of the present disclosure.

[0013] Figure 3A , 3B and 3C are schematic diagrams of a wireless communication network and interference sources of a full-duplex gNB, a half-duplex user equipment (UE), a first full-duplex UE, and a second full-duplex UE in accordance with some aspects of the present disclosure.

[0014] Figure 4 is a schematic diagram of wireless resource organization in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects of the present disclosure.

[0015] Figure 5A is a tabular description of multiple new radio (NR) operating bands (e.g., radio channels), UL operating band frequencies, DL operating band frequencies, and duplex modes associated with each of the NR operating bands in the NR operating band in accordance with some aspects of the present disclosure.

[0016] Figure 5B is a diagram illustrating an FDD FD modulation scheme in accordance with some aspects of the present disclosure.

[0017] Figure 5C is a diagram illustrating a TDD HD modulation scheme in accordance with some aspects of the present disclosure.

[0018] Figure 5D is a diagram illustrating a TDD FD modulation scheme in accordance with some aspects of the present disclosure.

[0019] Figures 6A–6C illustrate examples of full-duplex communication in unpaired spectrum.

[0020] Figure 7A FIG. is a schematic diagram of a base station (e.g., gNB) including a multi-panel antenna array configured for full-duplex communication according to some aspects of the present disclosure.

[0021] Figure 7B FIG. is for use according to some aspects of the present disclosure Figure 7A FIG. is a schematic diagram of an example of full-duplex wireless communication using the multi-panel antenna array shown.

[0022] Figure 8 FIG. is an illustration of a bandwidth part (BWP) of a component carrier (CC) bandwidth, where a complementary BWP is determined for an active anchor BWP according to some aspects of the present disclosure.

[0023] Figure 9 FIG. is an illustration of a BWP of a CC bandwidth, where a complementary BWP with a different subcarrier spacing is determined for an active anchor BWP according to some aspects of the present disclosure.

[0024] Figure 10 FIG. is an illustration of an active anchor BWP and a complementary BWP configured for transmission or reception of various DL and UL channels that can be implemented in a frequency division duplex (FDD) environment according to some aspects of the present disclosure.

[0025] Figure 11 FIG. is an illustration of a configuration where a complementary BWP is selected as an active anchor BWP and a previous active anchor BWP becomes a complementary BWP according to some aspects of the present disclosure.

[0026] Figure 12 FIG. is an illustration of a configuration showing selection of a new active anchor BWP and selection of a new complementary BWP according to some aspects of the present disclosure.

[0027] Figure 13 FIG. is a block diagram showing an example of a hardware implementation of a scheduled entity employing a processing system according to some aspects of the present disclosure.

[0028] Figure 14 FIG. is a block diagram showing an example of a hardware implementation of a scheduling entity employing a processing system according to some aspects of the present disclosure.

[0029] Figure 15 FIG. is a BWP management method for specifying an active anchor BWP and a complementary BWP in a scheduled entity (e.g., UE) according to some aspects of the present disclosure.

[0030] Figure 16 FIG. is a BWP management method for specifying an active anchor BWP and a complementary BWP in a scheduling entity (e.g., base station) according to some aspects of the present disclosure.

[0031] Figure 17is another method for BWP management to specify an active anchor BWP and a complementary BWP in a scheduled entity (e.g., UE) according to some aspects of the present disclosure.

[0032] Figure 18 is another method for BWP management to specify an active anchor BWP and a complementary BWP in a scheduling entity (e.g., base station) according to some aspects of the present disclosure. Detailed Description

[0033] The detailed description given below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring the concepts.

[0034] While aspects and embodiments are described herein by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases can arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or use cases can be generated by integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, AI-enabled devices, etc.). Although some examples may or may not be specifically directed to a use case or application, a wide applicability of the innovations described may occur. The scope of implementation can range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the innovation. In some practical settings, devices incorporating the aspects and features described may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily includes many components for analog and digital purposes (e.g., hardware components including antennas, radio frequency chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein can be practiced in devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated arrangements, end-user devices, etc. of various sizes, shapes, and configurations.

[0035] For frequency-division duplex (FDD) full-duplex (FD) communication to be achieved, the self-interference from the transmitter of a user equipment (UE) or a base station should be minimized to avoid saturating the sensitive amplifiers and the receiver front-ends of the UE and the base station. To isolate the signal transmitted by the transmitter from the receiver, the frequency band used by the transmitter can be separated from the frequency band used by the receiver. The gap between the two frequency bands can be referred to as a guard band. For time-division duplex (TDD) half-duplex (HD) communication, a guard band is not required because the transmission frequency band and the reception frequency band are the same. Therefore, the TDD HD scheme uses less bandwidth than the FDD FD scheme by using the same subchannels for transmission and reception at different times.

[0036] Work is underway to simultaneously use the same frequency resources for UL and DL in a given time slot. This usage can be referred to as TDD full-duplex or TDD FD in this document. Compared with TDD HD, a scheduled entity (e.g., a UE or other wireless communication device) capable of operating in the full-duplex mode may be able to use TDD FD to increase the amount of data transmitted because, like FDD FD, data can be sent and received simultaneously, and compared with FDD FD, data can be sent and received at the same frequency.

[0037] Scheduled entities (e.g., gNB or other network access nodes) may be early adopters of TDD FD. In this way, as scheduled entities with TDD FD capabilities are put into use, the radio access network will be ready to provide improved bandwidth usage for the scheduled entities. However, not all scheduled entities are capable of implementing TDD FD operation. For example, some scheduled entities may have an inexpensive front-end that includes a switch that couples the antenna to the scheduled entity receiver or the scheduled entity transmitter depending on the state of the switch. Such a design minimizes cost and complexity by eliminating relatively expensive and complex multiplexers and / or circulators at the front-end of the scheduled entity.

[0038] A scheduling entity capable of performing TDD FD operations may not be aware of the capabilities of the scheduled entities it serves and may seek to configure time slots for TDD FD operations. To configure a time slot for TDD FD operations, the scheduling entity may configure a time slot (including a set of OFDM symbols) to use the same frequency resource simultaneously (e.g., using a new radio operating band radio channel currently designated for TDD HD operations) for transmission and reception. The OFDM symbols used for TDD FD can be referred to as downlink - uplink (DU) symbols. The DU symbols can be different from uplink (UL) symbols, downlink (DL) symbols, and flexible (F) symbols. For example, DL symbols and UL symbols are respectively reserved for DL transmission and UL reception. DL transmission and UL reception are examples of one - way communication. DL transmission and UL reception can occur simultaneously at different frequencies (as in the case of FDD FD) or at different times at the same frequency (as in the case of TDD HD), but not simultaneously at the same frequency (as in the case of TDD FD). The F symbol is interpreted as either a UL symbol or a DL symbol and thus has the same characteristics as the DL symbol or UL symbol. The F symbol does not combine the characteristics of the UL symbol and the DL symbol.

[0039] Accordingly, the scheduling entity may configure a time slot having at least one downlink - uplink (DU) symbol reserved for downlink transmission to a scheduled entity (e.g., a UE or other wireless communication device) and uplink reception from the scheduled entity (e.g., a UE or other wireless communication device) at the same time and the same frequency. In this case, the behavior of non - TDD FD scheduled entities (referred to herein as scheduled entities, half - duplex scheduled entities, full - duplex aware scheduled entities, FD aware scheduled entities, half - duplex UEs, HD UEs, full - duplex aware UEs, or FD aware UEs) may be undefined. According to some aspects, compared to the traditional behavior in which an HD UE only reads the SlotFormatCombinationID (e.g., Figure 8 802), the behavior of an HD UE may not change when encountering a time slot formatted with at least one DU symbol.

[0040] Defining the behavior of non - TDD FD UEs when encountering DU symbols can enable non - TDD FD UEs (e.g., new or traditional TDD HD UEs, or full - duplex aware UEs) to continue operating in a wireless network environment where TDD FD transceivers are starting to be used and can provide for the continued and future use of low - cost non - TDD FD UEs in a TDD FD environment.

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

[0042] RAN 104 can implement any suitable wireless communication technology or technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate under 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 this hybrid RAN as the next-generation RAN, or NG-RAN. Of course, many other examples are possible within the scope of this disclosure.

[0043] As shown, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be differently referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), Node B (NB), eNode B (eNB), gNode B (gNB), transmission and reception point (TRP), or some other suitable term. In some examples, a base station may include two or more TRPs that may or may not be co-located. Each TRP can communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where RAN 104 operates according to LTE and 5G NR standards, one of the base stations in the RAN can be an LTE base station, while another base station can be a 5G NR base station.

[0044] RAN 104 is also shown as supporting wireless communications for multiple mobile devices. A mobile device may be referred to as a user equipment (UE) in the 3GPP standard, 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, cellular phone, terminal, user agent, mobile client, client, or some other suitable term. A UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0045] In this disclosure, a “mobile” device does not necessarily have the ability to move and may be stationary. The term mobile device or mobile equipment broadly refers to a variety of devices and technologies. A UE may include many hardware structural components whose size, shape, and arrangement facilitate communication; such components may 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 phones, cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide range of embedded systems, e.g., corresponding to the “Internet of Things” (IoT).

[0046] A mobile device may 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, a target tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device, such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. A mobile device may also be a digital home or smart home device, such as a home audio, video, and / or multimedia device, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. A mobile device may also be a smart energy device, a security device, a solar panel or solar panel array, a device for controlling municipal infrastructure for electricity (e.g., a smart grid), lighting, water, etc., industrial automation and enterprise equipment, a logistics controller, and / or agricultural equipment, etc. Further, a mobile device may provide connected medical or telemedicine support, such as telehealthcare. A telemedicine device may include a telemedicine monitoring device and a telemedicine management device, whose communication may be given priority processing or priority access over other types of information, e.g., in terms of priority access for transmitting critical service data and / or the relevant QoS for transmitting critical service data.

[0047] Wireless communication between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 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 from a base station (e.g., base station 108). Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of the present disclosure, the term uplink may refer to a point-to-point transmission initiated at a UE (e.g., UE 106).

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

[0049] The base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule 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.

[0050] As Figure 1 shown, 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, 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., grants), synchronization or timing information, or other control information from another entity such as the scheduling entity 108 in the wireless communication network.

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

[0052] Generally, the base station 108 can include a backhaul interface for communicating with the backhaul portion 120 of the wireless communication system 100. The backhaul portion 120 can provide a link between the base station 108 and the core network 102. In addition, in some examples, the backhaul network can provide an interconnection between the respective base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection using any suitable transmission network, a virtual network, etc.

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

[0054] Now referring to Figure 2 , as a non-limiting illustrative example, a schematic diagram of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 can be the same as the RAN 104 described above and Figure 1 shown in

[0055] The geographical area covered by the RAN 200 can be divided into multiple cellular areas (cells), and user equipment (UE) can uniquely identify these cellular areas (cells) based on an identifier broadcast over the geographical area from an access point or base station. Figure 2Cells 202, 204, 206, and 208 are shown, and each of these cells 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 base station. Radio links within a sector may be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by an antenna group, with each antenna responsible for communicating with UEs in a part of the cell.

[0056] Various base station arrangements may be used. 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 via a feeder cable. In the example shown, 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., a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNode B, etc.) because base station 218 supports a cell with a relatively small size. The cell size may be adjusted according to system design and component limitations.

[0057] It should be understood that the RAN 200 may include any number of radio base stations 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 Figure 1 shown in

[0058] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be an unmanned aircraft or a 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 necessarily be stationary, and the geographical area of a cell may move according to the position of a mobile base station such as the UAV 220.

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

[0060] On the other hand, in RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communication can be used for, for example, 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) can communicate with each other using sidelink signal 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 can each act as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and transmit 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) can also transmit sidelink signal 227 via a direct link (sidelink) without relaying the communication through base station 212. In this example, base station 212 can allocate resources to UEs 226 and 228 for sidelink communication.

[0061] To obtain a low block error rate (BLER) for transmission over the air interface while still achieving a very high data rate, channel coding can be used. That is, wireless communication can generally use suitable error-correcting block codes. In a typical block code, an information message or sequence is divided into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message can improve the reliability of the message, enabling any bit errors that may occur due to noise to be corrected.

[0062] Data encoding can be implemented in various ways. In the early 5G NR specifications, user data was encoded using quasi-cyclic low-density parity-check (LDPC) with two different base graphs: one base graph for large code blocks and / or high code rates, and the other base graph for other purposes. Control information and the physical broadcast channel (PBCH) were encoded using Polar coding based on nested sequences. For these channels, puncturing, shortening, and repetition were used for rate matching.

[0063] Aspects of the present disclosure can be implemented using any suitable channel code. Various implementations of the base station and the 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.

[0064] In the RAN 200, the ability of the UE to communicate independently of its location while moving is called mobility. Various physical channels between the UE and the RAN 200 are typically established, maintained, and released under the control of the access and mobility management function (AMF). In some cases, the AMF may include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF can manage the security context of the control plane and user plane functions in whole or in part.

[0065] In various aspects of the present disclosure, the RAN 200 can utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the connection of the 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 can monitor various parameters of the signals from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this period, 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 within a given time, the UE can perform a handover or hand over from the serving cell to the neighboring (target) cell. For example, the UE 224 can 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 from the neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given period of time, the UE 224 can send a report message indicating this situation to its serving base station 210. In response, the UE 224 can receive a handover command, and the UE can perform a handover to the cell 206.

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

[0067] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be unified, the synchronization signals may not identify a specific cell, but rather can identify an area of multiple cells operating at the same frequency and / or at the same timing. Implementing an uplink-based mobility framework using areas in a 5G network or other next-generation communication network can improve the efficiency of UEs and the network because the number of mobility messages that need to be exchanged between the UE and the network may be reduced.

[0068] In various embodiments, the air interface in radio access network 200 can use licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides exclusive use of a portion of the spectrum, typically 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 a license granted by the government. Although some technical rules generally still need to be followed to access unlicensed spectrum, in general, any operator or device can obtain access. Shared spectrum may be between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties, e.g., under conditions determined by the appropriate licensee to obtain access.

[0069] 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 utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and to provide multiplexing for DL transmissions from the base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification supports 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 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 can be utilized. Additionally, 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 utilized to provide multiplexed DL transmissions from the base station 210 to UEs 222 and 224.

[0070] Devices in the radio access network 200 can also use one or more duplexing algorithms. Duplexing refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full duplex means that the two endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex emulation is often used for wireless links that use time division duplexing (TDD). 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 transmissions in one direction, while at other times, the channel is dedicated to transmissions in the other direction, where the direction may change very quickly, e.g., several times per time slot. In a wireless link, a full-duplex channel typically relies on physical isolation of the transmitter and receiver, as well as suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by using 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, transmissions in different directions on a given channel are separated from each other using space division multiplexing (SDM). In other examples, full-duplex communication can be implemented 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 herein as sub-band full duplex (SBFD), also known as flexible duplex or TDDFD.

[0071] Figure 3A and 3B 3C is a schematic diagram of interference sources of the wireless communication network 300 and the full-duplex gNB 302 (e.g., a scheduling entity), the half-duplex UE 306, the first full-duplex UE 312, and the second full-duplex UE 308 according to some aspects of the present disclosure. In Figure 3A , the full-duplex gNB 302 is transmitting to the half-duplex UE 306. During the transmission from the full-duplex gNB 302 to the half-duplex UE 306, the full-duplex gNB 302 receives, at its receiver (not shown), self-interference 310 from its own transmission to the half-duplex UE 306, as well as interference from the adjacent gNB 304 and the uplink transmission from the second full-duplex UE 308. The half-duplex UE 306 also receives interference from the second full-duplex UE 308 and the adjacent gNB 304. Since it is a half-duplex UE, the half-duplex UE 306 does not transmit during the transmission from the full-duplex gNB 302 to the half-duplex UE 306. Therefore, the half-duplex UE 306 does not receive self-interference.

[0072] In Figure 3B , the full-duplex gNB 302 is transmitting a downlink transmission to the first full-duplex UE 312. During the transmission of the downlink transmission from the full-duplex gNB 302 to the first full-duplex UE 312, the full-duplex gNB 302 receives, at its receiver (not shown), the simultaneous uplink transmission from the first full-duplex UE 312. During the simultaneous downlink and uplink transmissions just mentioned, the first full-duplex UE 312 is receiving, at its receiver (not shown), self-interference 314 from its own transmission to the full-duplex gNB 302, as well as interference from the adjacent gNB 304 and interference from the second full-duplex UE 308.

[0073] In Figure 3C , the full-duplex gNB 302 is receiving an uplink transmission from the first full-duplex UE 312. During the time of transmitting the uplink transmission to the full-duplex gNB 302, the first full-duplex UE 312 is also receiving transmissions from multi-transmission and reception point (TRP) stations (e.g., macro cells, small cells, pico cells, femto cells, remote radio heads, relay nodes, etc.) (represented here as the multi-TRP radio transceiver station 318). In addition to the signals received from the multi-TRP radio transceiver station 318, the first full-duplex UE 312 also receives, at its receiver (not shown), self-interference 316 from its own transmission to the full-duplex gNB 302.

[0074] ForFigure 3A For the half-duplex UE 306, if the interference from the neighboring gNB 304 and the second full-duplex UE 308 is at a frequency different from the frequency occupied by the downlink transmission from the full-duplex gNB 302 to the half-duplex UE 306, the interference can be mitigated. Similarly, for Figure 3B and 3C the first full-duplex UE 312, if the self-interference 316 from the first full-duplex UE 312, the interference from the neighboring gNB 304, and / or the interference from the second full-duplex UE 308 are at frequencies different from the frequency occupied by the downlink transmission from the full-duplex gNB 302 to the half-duplex UE 306, the interference can be mitigated.

[0075] Reference will be made Figure 4 to the OFDM waveform schematically illustrated in

[0076] 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 SC-FDMA waveforms in substantially the same manner as described below. 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 SC-FDMA waveforms. Figure 4 Now referring to

[0077] The resource grid 404 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, the corresponding multiple resource grids 404 can be used for communication. The resource grid 404 is divided into multiple resource elements (REs) 406. An RE is 1 subcarrier × 1 symbol, which is the smallest discrete part of the time-frequency grid and contains a single complex value or signal representing data from a physical channel. Depending on the modulation used in a particular implementation, each RE can represent one or more information bits. In some examples, an RE block can 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 subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, and this number is independent of the digital scheme used. In some examples, depending on the digital scheme, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In this disclosure, it is assumed that a single RB such as RB 408 corresponds exactly to a single communication direction (transmission or reception of a given device).

[0078] A set of consecutive or non-consecutive resource blocks can be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A set of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission generally involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically uses only a subset of the resource grid 404. In some examples, an RB can be the smallest unit of resources 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 of the UE. An RB can be scheduled by a base station (e.g., a gNB, an eNB, etc.) or can be self-scheduled by a UE implementing D2D sidelink communication.

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

[0080] Each 1 ms subframe 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 can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Additional examples can include mini-slots, sometimes referred to as shortened transmission time intervals (TTIs), having a shorter duration (e.g., one to three OFDM symbols). These mini-slots or shortened transmission time intervals (TTIs) can be transmitted in some cases, occupying resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be used within a subframe or time slot.

[0081] An expanded view of one of the time slots 410 shows the time slot 410 including a control region 412 and a data region 414. Generally, the control region 412 can carry control channels, and the data region 414 can carry data channels. Of course, a time slot can contain all DL, all UL, or at least one DL portion and at least one UL portion. As Figure 4 shown, the structure is merely exemplary in nature, and different time slot structures can be used and can include each of one or more control regions and data regions.

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

[0083] In some examples, the time slot 410 can be used for broadcast, multicast, groupcast, or unicast communication. For example, broadcast, multicast, or groupcast communication can refer to a point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communication is transmitted to all devices, while multicast or groupcast communication is transmitted to multiple intended recipient devices. Unicast communication can refer to a point-to-point transmission from one device to a single other device.

[0084] In an example of cellular communication over a cellular carrier via the Uu interface, for DL transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within the control region 412) to carry DL control information including one or more DL control channels (such as the Physical Downlink Control Channel (PDCCH)) to one or more scheduled entities (e.g., UEs). 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 RE allocations for DL and UL transmissions. The PDCCH may also carry 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 the integrity of a packet transmission can be checked at the receiving side to ensure accuracy, e.g., 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 send a HARQ retransmission, which can implement chase combining, incremental redundancy, etc.

[0085] The base station 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 a Demodulation Reference Signal (DMRS); a Phase Tracking Reference Signal (PT-RS); a Channel State Information (CSI) Reference Signal (CSI-RS); and a Synchronization Signal Block (SSB). The SSB may be broadcast at regular intervals based on a period (e.g., 5, 10, 20, 40, 80, or 160 milliseconds). The SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Control Channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the channel (system) bandwidth center in the frequency domain, and identify the Physical Cell Identity (PCI) of the cell.

[0086] The PBCH in SSB may also include a Master Information Block (MIB), which includes 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. Together, the MIB and SIB1 provide the minimum system information (SI) for initial access. Examples of the system information transmitted 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) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also transmit other system information (OSI).

[0087] In UL transmission, the scheduled entity (e.g., UE) may utilize one or more REs 406 to carry UL control information (UCI) to the scheduling entity. The UCI includes 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 transmissions. 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 for the scheduling entity to schedule an uplink transmission. Here, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI) that can schedule resources for uplink packet transmission. The UCI may also include HARQ feedback, channel state feedback (CSF), such as a CSI report, or any other suitable UCI.

[0088] In addition to control information, one or more REs 406 (e.g., within the data region 414) may be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, e.g., for DL transmission, the Physical Downlink Shared Channel (PDSCH); or for UL transmission, 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.

[0089] 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) to 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 traffic transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier via the SCI. Other information may also be transmitted on various 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 may be transmitted within slot 410, such as a sidelink SSB, sidelink CSI-RS, sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0090] The physical channels described above are typically multiplexed and mapped to transport channels for processing at the Medium Access Control (MAC) layer. The transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS) may correspond to the number of bits of information that can be a controlled parameter.

[0091] The channels or carriers described above and Figures 1 - 4 illustrated are not necessarily all of the channels or carriers that may be used between a scheduling entity (e.g., base station 108) and a scheduled entity (e.g., one of the plurality of UEs 106), and one of ordinary skill in the art will recognize that other channels or carriers may be used in addition to the channels or carriers shown, such as other traffic, control, and feedback channels.

[0092] Figure 5A is a tabular description 500 of multiple New Radio (NR) operating bands 502 (e.g., radio channels), UL operating band frequencies 504, DL operating band frequencies 506, and duplex modes 508 associated with each of the NR operating bands 502, in accordance with certain aspects of the present disclosure.

[0093] Figure 5B is a diagram illustrating an FDD FD modulation scheme 510 in accordance with some aspects of the present disclosure. In Figure 5BIn the example shown, time is shown along the horizontal axis and frequency is shown along the vertical axis. Multiple Physical Uplink Shared Channels (PUSCH) 512 and uplink control channels 514 are depicted as occupying the UL operating band identified as nx UL FDD Multiple downlink data channels 516 (e.g., Physical Downlink Shared Channel (PDSCH)) and downlink control channels 518 are depicted as occupying the DL operating band identified as nx DL FDD The UL operating band nx UL FDD and the DL operating band nx DL FDD are described as being separated in frequency by a guard band 520. The paired use of the nx UL FDD uplink operating band and the nx DL FDD operating band of a given nx operating band can be referred to as paired spectrum. The nomenclature "nx" represents any one of the NR operating bands 502 designated for the FDD duplex mode 508. A subgroup 522 of all NR operating bands 502 designated for the FDD duplex mode 508 is shown in Figure 5A The operating bands are exemplary and not restrictive.

[0094] Figure 5C is a diagram showing a TDD HD modulation scheme 530 according to some aspects of the present disclosure. In Figure 5C the example shown, time is shown along the horizontal axis and frequency is shown along the vertical axis. Multiple downlink data channels 532 and downlink control channels 534 are depicted as occupying the operating band identified as ny UL&DL TDD A single operating band ny UL&DL TDD is used for both the uplink and the downlink by separating UL and DL information in time (e.g., they do not occupy the same time slot simultaneously). The unpaired use of the nxUL FDD uplink operating band and the nx DL FDD operating band (both at the same frequency, or in the same band, of a given nx operating band) can be referred to as unpaired spectrum. The Physical Uplink Shared Channel (PUSCH) 536 and the uplink control channel 538 are depicted as occupying a single operating band ny UL&DL TDD The nomenclature "ny" represents any one of the NR operating bands 502 designated for the TDD duplex mode 508. A subgroup 523 of all NR operating bands 502 designated for the TDD duplex mode 508 is shown in Figure 5A The operating bands are exemplary and non - restrictive.

[0095] Figure 5DFIG. is a diagram illustrating a TDD FD modulation scheme 540 according to some aspects of the present disclosure. In Figure 5D the example shown, time is shown along the horizontal axis, and frequency is shown along the vertical axis. As Figure 5D shown in the example diagram of, a full-duplex network may use sub-band full-duplex (SBFD) in an unpaired spectrum (e.g., as Figure 6C shown), where transmissions in different directions are carried in different sub-bands or BWPs of the carrier bandwidth. Multiple downlink data channels 544 and downlink control channels 542, as well as multiple PUSCHs 546 and uplink control channels 548, are all depicted as occupying the operating band identified as nz UL&DL FD . A single operating band nz UL&DL FD is used for both the uplink and the downlink, without separating UL and DL information in time (e.g., they do occupy the same time slot simultaneously). The nomenclature "nz" indicates any one of the NR operating bands 502 designated for the TDD duplex mode 508. A subgroup 523 of all NR operating bands 502 designated for the TDD duplex mode 508 is shown in Figure 5A . A first guard band 550 and a second guard band 552 are depicted in Figure 5D . The first guard band 550 and the second guard band 552 may be of the same bandwidth or different bandwidths. One or both of the first guard band 550 and the second guard band 552 may be zero-bandwidth guard bands. The first guard band 550 and the second guard band 552 (individually or jointly) in the unpaired spectrum may be smaller than the guard band 520 in the paired spectrum.

[0096] FIGS. 6A–6C illustrate examples of full-duplex communication in an unpaired spectrum. In Figure 6A –6C, the horizontal direction is time and the vertical direction is frequency. Here, the carrier bandwidth 602 (or a set of one or more active bandwidth parts (BWPs)) is shown along the frequency axis, and the time slot 604 is shown along the time axis.

[0097] Figure 6A and 6B illustrate in-band full-duplex (IBFD) communication, while Figure 6C illustrates sub-band full-duplex (SBFD) communication. For IBFD communication, as Figure 6A and 6B shown, downlink and uplink transmissions occur on the same time and frequency resources. For example, the downlink resource 606 assigned to downlink direction transmission overlaps in time and frequency with the uplink resource 608 assigned to uplink direction transmission. The overlap may be complete (as Figure 6A shown) or partial (as Figure 6B shown).

[0098] For SBFD communication, as Figure 6C shown, the carrier bandwidth 602 (or active BWP) can be divided into sub-bands 610a and 610b. Each sub-band 610a and 610b can be allocated for communication in a single direction. For example, sub-band 610a can be allocated for downlink transmission, while sub-band 610b can be allocated for uplink transmission. Thus, the downlink resources 606 allocated for downlink direction transmission overlap with the uplink resources 608 allocated for uplink direction transmission in time rather than in frequency. The downlink resources 606 can also be separated from the uplink resources 608 in the frequency domain by a guard band 612 to isolate uplink and downlink transmissions in frequency.

[0099] Figure 7A is a schematic diagram of a base station 702 (e.g., gNB) including a multi-panel antenna array 700 configured for full-duplex communication according to some aspects of the present disclosure. The antenna array 700 is divided into two panels (panel 1 704, panel 2 706) with a physical separation 708 therebetween. Each of the two panels can be an antenna sub-array. A given panel can transmit and / or receive beams or beam groups. In one example, the panels can be physically separated from each other by a selected distance to provide improved isolation between simultaneous transmission (Tx) and reception (Rx) operations in full-duplex mode, thereby reducing at least a portion of the self-interference generated by signals from simultaneous transmit / receive. The multi-panel antenna configuration shown in FIG. 7A can also be applied to a UE to implement full-duplex communication (e.g., SBFD) at the UE.

[0100] Figure 7B is an example of sub-band full-duplex (SBFD) wireless communication 710 using the Figure 7A multi-panel antenna array 700 shown according to certain aspects. In the Figure 7B example shown, time is in the horizontal direction in units of time slots 712a - 712d, each time slot including a plurality of OFDM symbols; and frequency is in the vertical direction. Here, the carrier bandwidth 714 (or one or more sets of active BWPs) is shown along the frequency axis. The carrier bandwidth 714 (or active BWP) can be divided into multiple sub-bands 750a - 750c for sub-band FD operation.

[0101] In the Figure 7BIn the example shown, in time slot 712a, the antenna array 700 is first configured for downlink (DL) communication (e.g., DL burst 716 and DL data section 718). The DL burst 716 may include DL control sent within the first few symbols of time slot 712a. The DL control may include, for example, a physical downlink control channel (PDCCH) carrying DCI that may be related to time slot 712a or previous or subsequent time slots. In the example, the DCI may include common DCI or UE-specific DCI. The common DCI may include, for example, common control information broadcast to a group of UEs or all UEs in the cell. The UE-specific DCI may include, for example, HARQ feedback information (e.g., ACK / NACK), scheduling information for scheduling downlink data transmission and / or uplink transmission in time slot 712a or subsequent time slots (e.g., time slots 712b, 712c, and / or 712d), and other suitable information. The DL burst 716 may also include various DL reference signals (e.g., SSB and / or CSI-RS). In this example, both panel 1 704 and panel 2 706 may be configured for DL transmission. The DL data section 718 may include DL data carried, for example, within the PDSCH. In addition to the DL data, the DL data section 718 may also include DL reference signals (e.g., DMRS) for demodulating and decoding the DL data.

[0102] Time slot 712a may also include a common uplink (UL) burst 722 at the end of time slot 712a. The common UL burst 722 may include, for example, a PUCCH carrying UCI and other UL signals. As Figure 7B shown, the end of the DL data section 718 may be temporally separated from the start of the UL burst 722. This time interval 720 may sometimes be referred to as a gap, guard period, guard interval, and / or various other suitable terms. This separation may provide time for the base station and the UE to perform the handover between transmission and reception, and vice versa. In this example, both panel 1 704 and panel 2 706 may be configured for UL transmission during the UL burst 722.

[0103] In time slots 712b and 712c, the antenna array 700 is configured for both DL communication and UL communication. For example, in time slots 712b and 712c, the carrier bandwidth 714 (or active BWP) is shown to be divided between uplink transmission and downlink transmission. Sub-bands 750a and 750b are allocated for downlink transmission, while sub-band 750c is allocated for uplink transmission. In Figures 7A - 7BIn an example operation of the sub-band full-duplex configuration shown, panel 1 704 may be configured for DL transmission at two edges of the carrier bandwidth 714 (or active BWP) (e.g., sub-bands 750a and 750b), and panel 2 706 may be configured for UL reception in the middle of the carrier bandwidth 714 (or active BWP) (e.g., sub-band 750c).

[0104] In each sub-band FD time slot 712b and 712c, DL sub-bands 750a and 750b respectively include DL bursts 724 and 734, which may include PDCCH carrying DCI and / or DL reference signals in the initial or start part of time slots 712b and 712c. After DL bursts 724 and 734, time slots 712b and 712c respectively include DL data portions 726 and 736 for transmitting DL data within sub-bands 750a and 750b. For example, DL data may be transmitted within a PDSCH. In addition to DL data, DL data portions 726 and 736 may also include DL reference signals (e.g., DMRS) for demodulating and decoding DL data.

[0105] In the uplink (UL) sub-band 750c, time slots 712b and 712c respectively include UL data portions 728 and 738 for transmitting UL data. For example, UL data may be transmitted within a PUSCH. After UL data portions 728 and 738, UL sub-band 750c of time slots 712b and 712c respectively includes UL bursts 730 and 740. UL bursts 730 and 740 may include, for example, PUCCH containing UCI and / or other UL signals. A guard band 732 is further provided between UL sub-band 750c and DL sub-bands 750a and 750b to mitigate self-interference between simultaneous DL transmissions in DL sub-bands 750a and 750b and UL transmissions in UL sub-band 750c.

[0106] Time slots 712b and 712c are sub-band FD time slots that frequency-division multiplex uplink and downlink transmissions. Figures 7A - 7B The sub-band full-duplex time slot configuration shown is merely exemplary, and other configurations of sub-band full-duplex time slots may be used in various aspects of the present disclosure. For example, other configurations including UL and DL sub-bands (e.g., Figure 4 the configuration shown or other suitable sub-band configurations) may be adopted for sub-band full-duplex time slots in various aspects.

[0107] During time slot 712d, the antenna array 700 is configured for UL communication. For example, time slot 712d includes a UL data portion 742 followed by a UL burst 744. The UL data portion 742 and the UL burst 744 may include UL control information and / or UL data, as described above. In this example, both panel 1 704 and panel 2 706 may be configured for UL reception. Time slots 712a and 712d are half-duplex TDD time slots that time-division multiplex DL transmissions and UL transmissions using TDM.

[0108] In some aspects of the present disclosure, one or more time slots may be flexible time slots that include one or more flexible symbols that may be configured as half-duplex symbols (e.g., all UL or all DL) or sub-band full-duplex symbols (e.g., including UL and DL transmissions). For example, in time slot 712b, the DL burst 724 may be configured to occupy all sub-bands 750a - 750c of time slot 712b. Accordingly, the symbols corresponding to the DL burst 724 may be flexible symbols that may be configured as half-duplex symbols to enable DL communication across all sub-bands 750a - 750c. Similarly, the UL burst 730 may be configured to occupy all sub-bands 750a - 750c of time slot 712b. Accordingly, the symbols corresponding to the UL burst 730 may be flexible symbols that may be configured as half-duplex symbols to enable UL communication across all sub-bands 750a–750c.

[0109] In sub-band full-duplex operation, the time slot format may be classified according to the duplex mode of the base station. For example, a time slot may be classified as a half-duplex time slot that includes symbols dedicated to TDM-based DL transmission or UL transmission (e.g., time slot 712a or 712b). Additionally, a time slot may be classified as a full-duplex (or sub-band full-duplex) time slot (e.g., time slot 712b or 712c) that includes a mixture of FDM-based DL and UL transmissions. A time slot may be further classified as a flexible time slot that may be partially or fully configurable (e.g., one or more symbols may be flexible symbols).

[0110] In various aspects of the present disclosure, to accommodate low-latency and / or high-reliability traffic, such as ultra-reliable low-latency communication (URLLC), a base station operating in sub-band full-duplex mode may dynamically change the time slot format of the time slots between half-duplex and sub-band full-duplex and / or may change the flexible symbols within the flexible time slots between half-duplex and sub-band full-duplex. A time slot format indicator (SFI) that indicates the time slot format of a time slot may be signaled, for example, via DCI mapped to the PDCCH or a media access control (MAC) control element (MAC-CE) mapped to the PDSCH.

[0111] Figure 8FIG. 800 is an illustration of bandwidth parts (BWPs) 804-810 of a component carrier (CC) bandwidth 802, where a complementary BWP is determined for an active anchor BWP according to some aspects of the present disclosure. Generally, a BWP is configured as a subset or a portion of the total carrier bandwidth (e.g., 802). A BWP forms a contiguous set of common resource blocks (CRBs) within the full component carrier bandwidth 802. In other words, within the carrier bandwidth, a BWP starts at a CRB and can span a contiguous set of CRBs. Each BWP can be associated with its own numerology (e.g., subcarrier spacing SCS and cyclic prefix CP). A UE can be configured with up to four downlink BWPs and up to four uplink BWPs for each serving cell. In the case of supplementary uplink (SUL), there can be up to four additional uplink BWPs on the SUL carrier.

[0112] To achieve reasonable UE battery consumption, only one BWP is active in the downlink and only one BWP is active in the uplink on an active serving cell under typical operation at a given time. The active BWP defines the operating bandwidth of the UE within the cell operating bandwidth, and all other BWPs configured for the UE are deactivated. On a deactivated BWP, the UE does not send or receive any data. For TDD, the BWP pair (active UL BWP and active DL BWP) must have the same center frequency and switch simultaneously. For FDD, the DL and UL BWPs switch independently. When needed, the network can dynamically switch the UE to the desired BWP. Through bandwidth adaptation (BA), the receive and transmit bandwidths of the UE do not need to be as large as the cell bandwidth and can be adjusted. The bandwidth can be commanded to change, where, for example, the UE can use a narrower BW to monitor the control channel and receive a small / medium amount of data (to save power). Alternatively or additionally, when a large amount of data is to be scheduled, the UE can switch to the full bandwidth or a large bandwidth. The position can be moved in the frequency domain (e.g., to increase scheduling flexibility) and the subcarrier spacing can be commanded to change (e.g., to allow for different services).

[0113] BA is achieved by configuring a BWP for the UE and telling the UE which of the configured BWPs is the current active BWP. To enable BA on the primary cell (PCell), the gNB configures UL and DL BWPs for the UE. To enable BA on secondary cells (SCells) in the case of carrier aggregation (CA), the gNB configures at least a DL BWP for the UE, i.e., there may or may not be any UL BWP for the SCell. The UE receives PDCCH and PDSCH in the DL BWP according to the SCS and CP length configured for the DL BWP. The UE transmits PUCCH and PUSCH in the UL BWP according to the SCS and CP length configured for the UL BWP. It is assumed that the UE receives / sends within the active DL / UL BWP using the associated numerology. For the downlink, it is expected that the UE does not receive PDSCH, PDCCH, or CSI-RS (except for radio resource management (RRM)) outside the active BWP. For the uplink, the UE may not send PUSCH or PUCCH outside the active BWP and for the active cell, and the UE may not send SRS outside the active BWP.

[0114] For each DL BWP or UL BWP in a set of DL BWPs or UL BWPs, multiple parameters can be provided for the UE separately, including but not limited to the SCS using the field subcarrier Spacing , the cyclic prefix using the field cyclic Prefix , the index in the respective BWP - Id set of DL BWPs or UL BWPs, the set of common and dedicated BWP parameters, and / or the starting PRB position of the BWP and the number of consecutive RBs forming the BWP. Since PRBs are the resource blocks for actual transmission / reception, the PRB set can belong to and form the BWP. The PRBs of a specific subcarrier configuration defined in the BWP are numbered from 0 to (the size of the BWP - 1).

[0115] The network (e.g., via the gNB) can implement BWP switching using RRC (re)configuration, where the network includes first Active Downlink BWP - Id and / or first Active Uplink BWP - Id for the serving primary cell (SpCell) or SCell in the RRC (re)configuration. After receiving the RRC (re)configuration of first Active Downlink BWP - Id and / or first Active Uplink BWP - Id of the SpCell, the UE can activate the ones separately indicated by first Active Downlink BWP - Id and / or first Active Uplink BWP - IdIndicated downlink BWP and / or uplink BWP. For SCell, after receiving the RRC reconfiguration, the UE may not immediately activate the downlink BWP and / or uplink BWP, but activate the corresponding BWP when the SCell is activated. BWP switching can be controlled by the PDCCH indicating downlink assignment or uplink grant.

[0116] Alternatively or additionally, the network may configure an inactivity timer ( bwp - Inactivity Timer ) which is used to switch the active downlink BWP after the amount of inactivity specified in the timer field bwp - Inactivity Timer . Expiration of the inactivity timer associated with the cell may switch the active BWP to the network-configured default BWP (if configured). If no default downlink BWP is configured, the active downlink BWP is switched to the initial downlink BWP. In some examples, the MAC entity may perform BWP switching when initiating a random access (RA) procedure on the serving cell. If no physical random access channel (PRACH) opportunity is configured for the active UL BWP, the MAC layer may switch the active UL BWP to the initial uplink BWP. If a PRACH opportunity is configured for the active UL BWP, there is no need to switch the active UL BWP. For DL, if the serving cell is a SpCell and if the BWP - Id of the active DL BWP is BWP - Id different from that of the active UL BWP, a switch may occur.

[0117] One of the drawbacks of BWP switching is that the switching time between the active BWP and another BWP may take too much time. In full-duplex (FD) mode operation, due to the differences between half-duplex (HD) time slots and FD time slots and the different frequency formats of FD time slots, the UE may need to frequently switch the active BWP. In the Figure 8 example, the UE may be configured with multiple BWPs (804 - 810) such that for each active BWP 808 (anchor BWP), a complementary BWP 810 is associated with the active anchor BWP 808. In such a configuration, the switching delay between the current active anchor BWP (anchor BWP) 808 and the complementary BWP 810 may be very small compared to switching to other configured BWPs (e.g., 804, 806). According to some aspects of the present disclosure, the complementary BWP 810 configuration may or may not depend on the active anchor BWP 808 configuration.

[0118] If a complementary BWP (e.g., 810) is dependent on an active anchor BWP (e.g., 808), then the complementary BWP bandwidth frequency and allocation can depend on UE capabilities. For example, since BWP switch latency can be the result of UE procedures (e.g., RF tuning), configuring the complementary BWP to share a common bandwidth with the active anchor BWP may help reduce RF tuning requirements. If the complementary BWP (e.g., 810) is independent of the active anchor BWP (e.g., 808), the UE can be configured to switch from the active anchor BWP to the complementary BWP in a shorter time frame. For example, the UE can be configured to perform RF tuning for both the active anchor BWP and the complementary BWP and then be configured to switch to the pre-tuned complementary BWP at a given time.

[0119] Figure 9 FIG. 900 is an illustration of BWPs (904 - 910) of the CC bandwidth 902, where, according to some aspects of the present disclosure, a complementary BWP 910 with a different subcarrier spacing (SCS) is determined for the active anchor BWP 906. In this example, the complementary BWP 910 can be configured with a different SCS to support a quick switch from the active anchor BWP 906 to a more latency - constrained transmission mode, such as ultra - reliable low - latency communication (URLLC) transmission. In some examples, the active anchor BWP 906 and the complementary BWP 910 can be configured with certain configuration sets to operate in different formats or operating environments. In one example, each BWP can be configured with a slot format to operate in the following manner: where the active anchor BWP (e.g., 906) is configured for half - duplex (HD) slots, and the complementary BWP (e.g., 910) is configured for full - duplex (FD) slots. In another example, the BWP can be configured using a UL BW threshold, where the active anchor BWP 906 is configured in an FD slot with a smaller UL band and is associated with the complementary BWP in an FD slot with a larger UL band. In some examples, the BWP can be configured to operate using different bandwidth priorities, where the active anchor BWP (e.g., 906) can be configured to operate in a low - priority signaling environment, while the complementary BWP (e.g., 910) can be configured to operate in a high - priority signaling environment (e.g., URLLC).

[0120] In some examples, the complementary BWP (e.g., 910) can be identified by the active anchor BWP (e.g., 906) using a flag or bit in the BWP configuration indicating whether the BWP is complementary. In other examples, a BWP index can be used in the anchor BWP to find the information element (IE) indicating the complementary BWP.

[0121] As described above, the UE may switch from an active anchor BWP to a complementary BWP via RRC reconfiguration, timer expiration, via MAC-CE, and / or UE sleep indication under various configurations including DCI signaling indicating the complementary BWP. In some aspects, the present disclosure provides additional BWP switching techniques and techniques for switching, including but not limited to switching based on slot format and / or signaling priority. Figure 10 is an illustration 1000 of an active anchor BWP 1014 and a complementary BWP 1016 that may be implemented in a full-duplex environment and configured for transmission or reception of various DL and UL channels according to some aspects of the present disclosure.

[0122] Figure 10 Examples of show features similar to those discussed above in connection with Figure 7B where a full-duplex antenna array may transmit a combination of DL control and DL data (similar to DL control 1010 and DL data 1012) and UL data (e.g., PUSCH 1018) and UL control 1020 in which DL transmission and UL reception are configured. When the antenna array only receives UL data (e.g., PUSCH 1022) and UL control 1024, both panels may be configured for UL reception. In one example, the UE may switch from an anchor BWP (e.g., 1014) to a complementary BWP (e.g., 1016) and switch back when the UE transitions from an HD to an FD slot, and then switch back to HD again.

[0123] In some examples, the UE may also switch to a complementary BWP according to a specific format of an FD slot. In other examples, the UE may switch to a complementary BWP according to the priority of signaling, e.g., when the complementary BWP is configured with a larger SCS than the active anchor BWP. During operation, if the subcarrier spacing matches, the UE may switch to a complementary BWP when operating in a URLLC environment and may use the anchor BWP when the UE operates via enhanced mobile broadband (eMBB).

[0124] Figure 11 is an illustration of a configuration 1100 according to some aspects of the present disclosure, which shows that the complementary BWP 1110 is selected as the active anchor BWP 1118 and the previously active anchor BWP 1106 becomes the complementary BWP 1114. As described above, during operation, the UE may switch from an active anchor BWP to a complementary BWP based on characteristics such as slot format and / or signaling priority. Once the UE switches to a complementary BWP, the complementary BWP becomes active and is considered the "new" active anchor BWP. This is shown in Figure 11As shown, for multiple BWPs (1104 - 1110) of CC bandwidth 1102, BWP 1106 is the active anchor BWP and BWP 1110 is the complementary BWP.

[0125] In this example, once the UE switches to the complementary BWP 1100 (as shown by the arrow in the figure), the complementary BWP 1100 is subsequently configured as the new active anchor BWP, and the previous active anchor BWP 1106 is configured as the complementary BWP. Thus, in one configuration, the active BWP and the complementary BWP can effectively be "paired" with each other, and the UE can switch back and forth between the two until a new condition, instruction, and / or operating environment causes a new active anchor BWP to be selected. By effectively pairing the active anchor BWP with the complementary BWP, this can reduce the processing requirements on the UE, as the UE should already have RF tuning information available for each BWP under normal operating conditions.

[0126] In some examples, the UE can utilize other configurations to manage the switching between the active anchor BWP and the complementary BWP and vice versa. In some examples, when the UE (e.g., via the gNB) receives an instruction to switch to the complementary BWP, the instruction can include additional data indicating the new complementary BWP. This additional data can be received via a DCI including extra bits (e.g., two extra bits) pointing to the new complementary BWP. Alternatively or additionally, the extra bits indicating the active anchor BWP in the DCI can also indicate the new complementary BWP in a combined manner of RRC configuration. In some examples, the RRC configuration can be used to configure multiple BWPs (e.g., four BWPs), where each BWP can be assigned an associated complementary BWP. For example, BWP 1110 can be designated as the complementary BWP of BWP 1106, BWP 1104 can be designated as the complementary BWP of BWP 1108, and so on.

[0127] During operation, after the complementary BWP is activated and becomes the new anchor BWP, the new complementary BWP does not need to be ready to operate simultaneously with the handover and is preferably specified at a time after the handover until the traditional handover time period. If the UE switches the complementary BWP to a new active anchor BWP (e.g., 1110), the UE can be configured to keep the previously active anchor BWP as the complementary BWP of the new active anchor BWP. Alternatively or additionally, a new complementary BWP can be configured for the new active anchor BWP as previously discussed above.

[0128] Figure 12FIG. 1200 is a diagrammatic illustration of a configuration in accordance with some aspects of the present disclosure, which shows a selected new active anchor BWP and a selected new complementary BWP. In this example, the UE is configured with a plurality of BWPs (1204 - 1210) for the CC bandwidth 1202, where BWP 1204 is designated as the active anchor BWP and BWP 1208 is designated as the complementary BWP. In some operating environments (e.g., via an instruction from the gNB), the UE can switch from the active anchor BWP to a non - complementary BWP. This is shown by the arrow in Figure 12 where the UE switches from the previous active anchor BWP 1204 to the new active anchor BWP 1210. In some examples, the UE can designate an existing complementary BWP as the new active anchor BWP. Alternatively or additionally, the UE can use RRC configuration to switch the previous complementary BWP (e.g., 1208) to a new complementary BWP (e.g., 1206) associated with the new active anchor BWP (e.g., 1210). In another example, the UE can receive data indicating the new complementary BWP (e.g., 1206), which can be the same BWP or a different BWP from the previous complementary BWP (e.g., 1208). The data indicating the new complementary BWP can be received via DCI, MAC - CE, or RRC.

[0129] Figure 13 FIG. is a block diagram showing an example of a hardware implementation of a scheduled entity employing a processing system in accordance with some aspects of the present disclosure. For example, the scheduled entity 1300 can be a user equipment (UE) or other scheduled entity, such as Figure 1 , 2 and / or any one or more of those shown in FIGS. 1 - 3.

[0130] In accordance with various aspects of the present disclosure, an element or any portion of an element, or any combination of elements can be implemented with a processing system 1314 including one or more processors, such as processor 1304. Examples of processor 1304 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, the scheduled entity 1300 can be configured to perform any one or more of the functions described herein. That is, the processor 1304, as used in the scheduled entity 1300, can be used to implement any one or more of the methods or processes described and illustrated herein.

[0131] The processor 1304 can be implemented via a baseband or modem chip in some cases, and in other implementations (e.g., in these scenarios where they can work together to implement the examples discussed herein), the processor 1304 can include multiple devices distinct from the baseband or modem chip. And as described above, various hardware arrangements and components other than the baseband modem processor can be used in the implementation, including radio frequency chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0132] In this example, the processing system 1314 can be implemented with a bus architecture, generally represented by the bus 1302. The bus 1302 can include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system 1314. The bus 1302 communicatively couples various circuits together, including one or more processors (generally represented by the processor 1304), a memory 1305, and a computer-readable medium (generally represented by the computer-readable medium 1306). The bus 1302 can also connect various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further herein.

[0133] The bus interface 1308 provides an interface between the bus 1302 and the transceiver 1310. The transceiver 1310 can be a wireless transceiver. The transceiver 1310 provides a unit for communicating with various other devices via a transmission medium (e.g., an air interface). The transceiver 1310 can be further coupled to one or more antennas / antenna arrays / antenna modules 1320. The bus interface 1308 further provides an interface between the bus 1302 and the user interface 1312 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, control functions, etc.). Of course, such a user interface 1312 is optional and can be omitted in some examples. In addition, the bus interface 1308 also provides an interface between the bus 1302 and the power supply 1328, as well as an interface between the bus 1302 and the application processor 1330, and the application processor 1330 can be independent of the modem (not shown) or the processing system 1314 of the scheduling entity 1300.

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

[0135] Computer-readable medium 1306 may be a non-transitory computer-readable medium and may be referred to as a computer-readable storage medium or a non-transitory computer-readable medium. A non-transitory computer-readable medium may store computer-executable code (e.g., processor-executable code). The computer-executable code may include code for causing a computer (e.g., a processor) to implement one or more of the functions described herein. Non-transitory computer-readable media include, 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 programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1306 may reside within processing system 1314, external to processing system 1314, or be distributed across multiple entities including processing system 1314. Computer-readable medium 1306 may be embodied in a computer program product or a manufactured article. For example, a computer program product or a manufactured article may include a computer-readable medium in a packaging material. In some examples, computer-readable medium 1306 may be part of memory 1205. Those skilled in the art will recognize how best to implement the described functions presented throughout this disclosure in light of a particular application and the overall design constraints imposed on the overall system. Computer-readable medium 1306 and / or memory 1305 may also be used to store data that is manipulated by processor 1304 when executing the software.

[0136] In some aspects of the present disclosure, the processor 1304 may include communication and processing circuitry 1341 configured for various functions, including, for example, functions of units for communicating with a scheduling entity (e.g., a base station or other wireless communication device), a network core (e.g., a 5G core network), other scheduling entities, or any other entity (e.g., a local infrastructure or an entity communicating with the scheduled 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 that provide a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing transmitted signals). Additionally, the communication and processing circuitry 1341 may be configured to receive and process uplink traffic and uplink control messages (e.g., similar to Figure 1 the uplink traffic 116 and uplink control 118) via the antenna / antenna array / antenna module 1320 and the transceiver 1310 and process and transmit downlink traffic and downlink control messages (e.g., similar to the downlink traffic 112 and downlink control 114). In some examples, the communication and processing circuitry 1341 may also be configured to send a message to a scheduling entity indicating that a time slot may be formatted to reserve at least one downlink - uplink (DU) symbol for simultaneous downlink and uplink transmissions at the same time and the same frequency. In some examples, the communication and processing circuitry 1341 may also be configured to receive and process a message from a scheduling entity indicating a DU symbol or DU time slot interpretation that the scheduled entity may use to interpret the DU symbol or DU time slot.

[0137] In some embodiments where communication involves receiving information, the communication and processing circuitry 1341 may obtain information from components of the wireless communication device 1300 (e.g., from the transceiver 1310 that receives information via radio frequency signaling or some other type of signaling suitable for the application communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1341 may output the information to another component of the processor 1304, the memory 1305, or the bus interface 1302. In some examples, the communication and processing circuitry 1341 may receive one or more signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry 1341 may receive information via one or more channels. In some examples, the communication and processing circuitry 1341 may include the functions of units for receiving. In some examples, the communication and processing circuitry 1341 may include the functions of units for processing, including units for demodulation, units for decoding, etc.

[0138] In some embodiments where communication involves sending (e.g., transmitting) information, the communication and processing circuitry 1341 can obtain information (e.g., from another component of the processor 1304, the memory 1305, or the bus interface 1302), process (e.g., modulate, encode, etc.) the information, and output the processed information. For example, the communication and processing circuitry 1341 can output the information to the transceiver 1310 (e.g., which sends the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1341 can send one or more of signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry 1341 can send information via one or more channels. In some examples, the communication and processing circuitry 1341 can include the functionality of a unit for sending (e.g., a unit for transmitting). In some examples, the communication and processing circuitry 1341 can include the functionality of units for generating, including a unit for modulating, a unit for encoding, etc.

[0139] In some examples, the communication and processing circuitry 1341 can be configured to transmit (e.g., send / receive) beamformed signals at millimeter wave frequencies or frequencies below 6 GHz via the transceiver 1310 and an antenna array (not shown).

[0140] In some aspects of the present disclosure, the communication and processing circuitry 1341 can be configured for various functions, including, for example, obtaining a duplex mode from a scheduling entity (e.g., a base station) that wirelessly communicates with a scheduled entity. The duplex mode can be, for example, full duplex, half duplex, or full duplex aware. The communication and processing circuitry 1341 can further be configured to execute communication and processing instructions (software) 1351 stored on the computer-readable medium 1306 to implement one or more of the functions described herein.

[0141] In some aspects of the present disclosure, the processor 1304 may include BWP management circuitry 1342 configured for various functions, including, for example, determining an active anchor BWP and determining an associated complementary BWP, as described above. The complementary BWP may be determined by the scheduled entity 1300 using, for example, a time slot format and / or signaling priority. Alternatively or additionally, the BWP management circuitry 1342 may receive and process BWP data provided on the bus interface 1302 via the transceiver 1310 (e.g., received from a scheduling entity) and / or preconfigured instructions 1307 of the memory 1305, e.g., if the scheduled entity is an HD or FD-aware scheduled entity. The BWP management circuitry 1342 may be configured to continuously select and / or reselect the active anchor BWP and / or the complementary BWP during operation. The BWP management circuitry 1342 may further be configured to execute BWP management instructions (software) 1352 stored on a computer-readable medium 1306 to implement one or more of the functions described herein.

[0142] Figure 14 is a block diagram illustrating an example of a hardware implementation of a scheduled entity employing a processing system according to some aspects of the present disclosure. The scheduled entity 1400 may be, for example, a base station, eNB, gNB, or network access node, as Figure 1 and 2 shown in any one or more of 3.

[0143] The processing system 1414 may be substantially the same as the Figure 13 processing system 1314 shown, including a bus interface 1408, a bus 1402, a memory 1405, a processor 1404, and a computer-readable medium 1406. According to various aspects of the present disclosure, an element, or any part of an element, or any combination of elements may be implemented with a processing system 1414 including one or more processors, such as the processor 1404. Additionally, the scheduled entity 1400 may include a user interface 1412, a transceiver 1410, an antenna / antenna array / antenna module 1420, an application processor 1430, and a power supply 1428 substantially similar to those described above Figure 13 herein. That is, the processor 1404 as used in the scheduled entity 1400 may be used to implement any one or more of the processes described herein. The transceiver 1410 may be a wireless transceiver.

[0144] In some aspects of the present disclosure, the processor 1404 may include communication and processing circuitry 1441, which may be similarly configured as described above in connection with Figure 13The communication and processing circuitry 1341 discussed. In some examples, the communication and processing circuitry 1441 may be configured for various functions, including communicating, for example, with a scheduled entity (e.g., a UE), a network core (e.g., a 5G core network), other scheduled entities, or any other entity, such as a local infrastructure or an entity (such as a network provider) communicating with the scheduling entity 1400 via the Internet. In some examples, the communication and processing circuitry 1441 may also be configured to send a message to the scheduled entity indicating that a time slot may be formatted as at least one downlink - uplink (DU) symbol reserved for downlink and uplink transmissions at the same time and the same frequency. In some examples, the communication and processing circuitry 1441 may also be configured to send a message to the scheduled entity indicating the DU symbol or DU time slot interpretation that the scheduled entity may use to interpret the DU symbol or DU time slot. In some examples, the communication and processing circuitry 1441 may include one or more hardware components that provide a physical structure for performing 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 1441 may be configured to receive and process downlink traffic and downlink control (e.g., similar to Figure 1 the downlink traffic 112 and downlink control 114) and process and send uplink traffic and uplink control (e.g., similar to uplink traffic 116 and uplink control 118). The communication and processing circuitry 1441 may further be configured to execute communication and processing instructions (software) 1451 stored on a computer - readable medium 1406 to implement one or more of the functions described herein.

[0145] In some aspects of the present disclosure, the processor 1404 may include BWP management circuitry 1442 configured for various functions, including, for example, functions for determining an active anchor BWP and configuring an associated complementary BWP, as discussed above. The complementary BWP may be determined by the scheduling entity 1400 using, for example, time slot format and / or signaling priority. Alternatively or additionally, the BWP management circuitry 1442 may send BWP data to the scheduled entity (e.g., 1300) via the transceiver 1410. The BWP management circuitry 1442 may be configured to continuously select and / or re - select an active anchor BWP and / or a complementary BWP for the scheduled entity during operation. The BWP management circuitry 1442 may also be configured to execute BWP management instructions (software) 1452 stored on a computer - readable medium 1406 to implement one or more of the functions described herein.

[0146] Figure 15Method 1500 for BWP management to specify an active anchor BWP and a complementary BWP in a scheduled entity (e.g., UE) according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in specific embodiments within the scope of the present disclosure, and some of the illustrated features may not be necessary for the embodiments of all examples. In some examples, method 1500 may be performed by Figure 13 the scheduled entity 1300 shown. In some examples, method 1500 may be performed by any suitable device or unit for performing the functions or algorithms described below.

[0147] In block 1502, a scheduled entity (e.g., UE) may receive a message indicating an active bandwidth part (BWP) (e.g., 1106) of multiple BWPs for the carrier bandwidth of the UE. For example, the transceiver 1310 and the communication and processing circuitry 1341, shown and described in conjunction with Figure 13 may provide a unit for receiving a message indicating an active bandwidth part (BWP) of multiple BWPs for the carrier bandwidth of the UE.

[0148] In block 1504, the scheduled entity may communicate with the base station to configure a second BWP (e.g., 1110) among the multiple BWPs to be complementary to the active BWP based on the slot format or signaling priority of the determined active BWP, where the second BWP is designated as a new BWP of the UE that is deactivated based on the active BWP. In some examples, the slot format includes at least one of a half-duplex slot or a full-duplex slot. The signaling priority may include at least one of low-priority signaling and high-priority signaling. For example, the communication and processing circuitry 1341 and the BWP management circuitry 1342, shown and described in conjunction with Figure 13 may provide a unit for communicating with the base station to configure a second BWP among the multiple BWPs to be complementary to the active BWP based on the determined slot format or the signaling priority of the active BWP, where the second BWP is designated as a new BWP of the UE when the active BWP is deactivated.

[0149] In some examples, the second BWP has a bandwidth that at least partially overlaps with the activated BWP. In some examples, configuring the second BWP may include performing radio frequency (RF) tuning on the activated BWP and the second BWP. The second BWP may include a different / larger subcarrier spacing than the activated BWP. In some examples, the second BWP may be activated when the activated BWP is deactivated during a ultra-reliable low-latency communication (URLLC) operating mode. During an enhanced mobile broadband (eMBB) operating mode, the second BWP may be deactivated and the activated BWP may be reactivated. During a transition of the UE from a half-duplex time slot to a full-duplex time slot, the second BWP may be activated when the activated BWP is deactivated.

[0150] In some examples, configuring the second BWP (e.g., 1110) to be complementary to the activated BWP (e.g., 1106) may include modifying one or more bits in the second BWP configuration to indicate that the second BWP is complementary, or modifying the BWP index associated with the activated BWP to indicate that the second BWP is complementary. The second BWP may be activated when the activated BWP is deactivated, and the activated BWP may be configured to be complementary to the second BWP. In some examples, the second BWP may be activated when the activated BWP is deactivated, and may receive downlink control information (DCI) for indicating another BWP among multiple BWPs that is complementary to the second BWP. In some examples, the second BWP may be activated when the activated BWP is deactivated, and may receive radio resource control (RRC) data indicating another BWP among multiple BWPs that is complementary to the second BWP.

[0151] In some examples, when an active BWP (e.g., 1204) is deactivated, a third BWP (e.g., 1210) among multiple BWPs can be activated, and based on the determined slot format or signaling priority, a second BWP can be configured to be complementary to the third BWP, where the second BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated. In some examples, when an active BWP is deactivated and a third BWP (e.g., 1210) among multiple BWPs is activated, based on the determined slot format or signaling priority, a fourth BWP (e.g., 1206) can be configured to be complementary to the third BWP, where the fourth BWP can be designated as the BWP to which the UE will switch when the third BWP is deactivated. In some examples, when a third BWP among multiple BWPs is activated and the active BWP is deactivated, data indicating that one of the multiple BWPs is complementary to the third BWP can be received, where the indicated one BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated. In some examples, receiving data indicating that one of the multiple BWPs is complementary can include receiving data via one of a downlink control information (DCI), a MAC control element (MAC-CE), or a radio resource control (RRC) transmission. For example, in conjunction with Figure 13 the BWP management circuitry 1342 shown and described can provide units for activating / deactivating, designating, and / or configuring BWPs to be complementary to corresponding BWPs.

[0152] Figure 16 is a BWP management method for designating an active anchor BWP and complementary BWPs in a scheduling entity (e.g., a base station) according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in specific embodiments within the scope of the present disclosure, and some of the illustrated features may not be necessary for the implementation of all examples. In some examples, method 1600 may be performed by Figure 14 the scheduling entity 1400 shown. In some examples, method 1600 may be performed by any suitable device or unit for performing the functions or algorithms described below.

[0153] In block 1602, a scheduling entity (e.g., a base station, e.g., a gNB) can send a message to activate a bandwidth part (BWP) of multiple BWPs of the carrier bandwidth of the scheduled entity. For example, in conjunction with Figure 14 the transceiver 1410, the communication and processing circuitry 1441, and the BWP management circuitry 1442 shown and described can provide units for sending a message to activate a bandwidth part (BWP) of multiple BWPs of the carrier bandwidth of the scheduled entity.

[0154] In block 1604, the scheduling entity may send a second message to the scheduled entity to configure a second BWP among multiple BWPs as complementary to the active BWP based on the slot format or signaling priority of the determined active BWP, where the second BWP is designated as a new BWP of the UE that is deactivated based on the active BWP. For example, transceiver 1410, communication and processing circuitry 1441, and BWP management circuitry 1442 shown and described in conjunction with Figure 14 may provide a unit for sending the slot format or signaling priority of the determined active BWP.

[0155] In some examples, the second BWP has a bandwidth that at least partially overlaps with the active BWP. The second BWP may also include a subcarrier spacing that is greater than that of the active BWP. In some examples, the second BWP may be configured to be activated when the active BWP is deactivated during a ultra-reliable low-latency communication (URLLC) operation mode. In some examples, the slot format may include at least one of half-duplex and full-duplex slots, and the second BWP is configured to be activated when the active BWP is deactivated during a transition from a half-duplex slot to a full-duplex slot.

[0156] In some examples, the second BWP may be configured to be complementary to the active BWP by one or more bits modified in a second BWP configuration indicating that the second BWP is complementary, or by a modified BWP index associated with the active BWP indicating that the second BWP is complementary. In some examples, the second BWP may be configured to be activated when the active BWP is deactivated, and the active BWP may be configured to be complementary to the second BWP. In some examples, when the active BWP is deactivated, the second BWP may be activated, and downlink control information (DCI) may be sent to indicate another BWP among multiple BWPs that is complementary to the second BWP, or radio resource control (RRC) data may be sent to indicate another BWP among multiple BWPs that is complementary to the second BWP.

[0157] In some examples, when the active BWP is deactivated, a message may be sent to activate a third BWP among multiple BWPs, where the second BWP may be configured to be complementary to the third BWP based on the determined slot format or signaling priority, where the second BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated, the fourth BWP may be configured to be complementary to the third BWP based on the determined slot format or signaling priority, where the fourth BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated, or data indicating that one of the multiple BWPs is complementary to the third BWP may be sent, where the indicated one BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0158] Figure 17 is a method 1700 for BWP management that specifies an active anchor BWP and complementary BWPs in a scheduled entity (e.g., a UE) according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in specific embodiments within the scope of the present disclosure, and some of the illustrated features may not be necessary for the embodiments of all examples. In some examples, method 1700 may be performed by Figure 13 the scheduled entity 1300 shown. In some examples, method 1700 may be performed by any suitable device or unit for performing the functions or algorithms described below.

[0159] In block 1702, a scheduled entity (e.g., a UE) may activate a bandwidth part (BWP) of multiple BWPs for the carrier bandwidth of the UE (e.g., 1106, 1204). For example, in conjunction with Figure 13 the communication and processing circuitry 1341 and BWP management circuitry 1342 shown and described may provide the unit for activation.

[0160] In block 1704, the scheduled entity may determine one of the slot format or signaling priority of the active BWP. In some examples, the slot format includes at least one of a half-duplex slot or a full-duplex slot. The signaling priority may include at least one of low-priority signaling and high-priority signaling. For example, in conjunction with Figure 13 the BWP management circuitry 1342 shown and described may provide the unit for determining one of the slot format or signaling priority of the active BWP.

[0161] In block 1706, the scheduled entity may configure a second BWP to be complementary to the active BWP (e.g., 1110) based on the determined slot format or signaling priority, where the second BWP is designated as the BWP to which the UE will switch when the active BWP (e.g., 1106) is deactivated. For example, in conjunction with Figure 13The shown and described BWP management circuitry 1342 can provide units for configuring a second BWP to be complementary to an active BWP. In some examples, the second BWP has a bandwidth that at least partially overlaps with the active BWP. In some examples, configuring the second BWP can include performing radio frequency (RF) tuning on the active BWP and the second BWP. The second BWP can include a different / larger subcarrier spacing than the active BWP. In some examples, the second BWP can be activated when the active BWP is deactivated during a ultra-reliable low-latency communication (URLLC) operation mode. During an enhanced mobile broadband (eMBB) operation mode, the second BWP can be deactivated and the active BWP can be reactivated. During a transition of the UE from a half-duplex time slot to a full-duplex time slot, the second BWP can be activated when the active BWP is deactivated.

[0162] In some examples, configuring a second BWP (e.g., 1110) to be complementary to an active BWP (e.g., 1106) can include modifying one or more bits in the second BWP configuration to indicate that the second BWP is complementary, or modifying the BWP index associated with the active BWP to indicate that the second BWP is complementary. The second BWP can be activated when the active BWP is deactivated, and the active BWP can be configured to be complementary to the second BWP. In some examples, the second BWP can be activated when the active BWP is deactivated, and can receive downlink control information (DCI) for indicating another BWP among a plurality of BWPs that is complementary to the second BWP. In some examples, the second BWP can be activated when the active BWP is deactivated, and can receive radio resource control (RRC) data indicating another BWP among a plurality of BWPs that is complementary to the second BWP.

[0163] In some examples, when an active BWP (e.g., 1204) is deactivated, a third BWP among multiple BWPs (e.g., 1210) can be activated, and based on the determined slot format or signaling priority, a second BWP can be configured to be complementary to the third BWP, where the second BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated. In some examples, when an active BWP is deactivated and a third BWP among multiple BWPs (e.g., 1210) is activated, based on the determined slot format or signaling priority, a fourth BWP (e.g., 1206) can be configured to be complementary to the third BWP, where the fourth BWP can be designated as the BWP to which the UE will switch when the third BWP is deactivated. In some examples, when an active BWP is deactivated and a third BWP among multiple BWPs is activated, data indicating that one of the multiple BWPs is complementary to the third BWP can be received, where the indicated one BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated. In some examples, receiving data indicating that one of the multiple BWPs is complementary can include receiving the data via one of downlink control information (DCI), MAC control element (MAC-CE), or radio resource control (RRC) transmission. For example, the BWP management circuit 1342 shown and described in conjunction with Figure 13 can provide units for activating / deactivating, designating, and / or configuring BWPs to be complementary to corresponding BWPs.

[0164] Figure 18 is a BWP management method for designating an active anchor BWP and a complementary BWP in a scheduling entity (e.g., a base station) according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be necessary for the embodiments of all examples. In some examples, method 1800 can be performed by Figure 14 the scheduling entity 1400 shown. In some examples, method 1800 can be performed by any suitable device or unit for performing the functions or algorithms described below.

[0165] In block 1802, a scheduling entity (e.g., a base station, e.g., a gNB) can activate one bandwidth part (BWP) of multiple BWPs of a carrier bandwidth for a scheduled entity (e.g., a UE). For example, the communication and processing circuit 1441 and the BWP management circuit 1442 shown and described in conjunction with Figure 14 can provide units for activating a BWP among multiple BWPs of a carrier bandwidth for a scheduled entity.

[0166] In block 1804, determine one of the slot format or signaling priority of the active BWP. In some examples, the slot format includes at least one of a half-duplex slot and a full-duplex slot. For example, the BWP management circuit 1442 described in connection with Figure 14 the display and description may provide a unit for determining the slot format or signal priority.

[0167] In block 1806, configure a second BWP complementary to the active BWP based on the determined slot format or signaling priority. In some examples, the second BWP has a bandwidth that at least partially overlaps with that of the active BWP. The second BWP may include a larger subcarrier spacing than the active BWP. In some examples, the second BWP may be activated when the active BWP is deactivated during a ultra-reliable low-latency communication (URLLC) operation mode. During the transition from a half-duplex slot to a full-duplex slot, the second BWP may be activated when the active BWP is deactivated. In some examples, the second BWP may be configured to be complementary to the active BWP by modifying one or more bits in the second BWP configuration to indicate that the second BWP is complementary, or modifying the BWP index associated with the active BWP to indicate that the second BWP is complementary. For example, the communication and processing circuit 1441 and the BWP management circuit 1442 described in connection with Figure 14 the display and description may provide a unit for configuring the second BWP to be complementary to the active BWP.

[0168] In block 1808, the second BWP is sent to the scheduled entity, where the second BWP is designated as the BWP to which the UE will switch when the active BWP is deactivated. In some examples, the second BWP may be configured to be activated when the active BWP is deactivated, and the active BWP may be configured to be complementary to the second BWP. In some examples, the second BWP may be configured to be activated when the active BWP is deactivated, and may send downlink control information (DCI) indicating another BWP among multiple BWPs complementary to the second BWP, or may send radio resource control (RRC) data indicating another BWP among multiple BWPs complementary to the second BWP. For example, the communication and processing circuit 1441, the BWP management circuit 1442, and the transceiver 1410 described in connection with Figure 14 the display and description may provide a unit for sending the second BWP to the scheduled entity, where the second BWP is designated as the BWP to which the UE will switch when the active BWP is deactivated.

[0169] In some examples, a third BWP among multiple BWPs may be activated when the active BWP is deactivated, and based on the determined slot format or signaling priority, a second BWP may be configured to be complementary to the third BWP, where the second BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated. Based on the determined slot format or signaling priority, a fourth BWP may be configured to be complementary to the third BWP, where the fourth BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated, or send complementary data among the multiple BWPs to the third BWP, where the indicated one BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0170] Of course, in the above examples, the circuits included in the processor are provided only as examples, and other units for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in a computer-readable medium, or any one Figure 1 、 2 and / or any other suitable device or unit described in 3, and utilize, for example, the processes and / or algorithms described herein with respect to Figures 8 - 12 and 15 - 16.

[0171] An overview of examples of the present disclosure is provided below.

[0172] Example 1: A method for full - duplex communication in a user equipment (UE), including: receiving a message for indicating an active BWP among multiple bandwidth parts (BWPs) of the UE; and communicating with a base station to configure a second BWP among the multiple BWPs to be complementary to the active BWP based on the determined slot format or signaling priority of the active BWP, where the second BWP is designated as a new BWP for the UE based on the active BWP being deactivated.

[0173] Example 2: The method of Example 1, wherein the second BWP has a bandwidth that at least partially overlaps with the active BWP.

[0174] Example 3: The method of Example 1 and / or 2, wherein configuring the second BWP includes performing radio frequency (RF) tuning on the active BWP and the second BWP.

[0175] Example 4: The method of any one of Examples 1 to 3, wherein the second BWP includes a sub - carrier spacing different from that of the active BWP.

[0176] Example 5: The method of any one of Examples 1 to 4, wherein the second BWP includes a larger sub - carrier spacing than the active BWP.

[0177] Example 6: The method of any one of Examples 1 to 5, wherein during the ultra-reliable low-latency communication (URLLC) operation mode, a second BWP is activated when the activated BWP is deactivated.

[0178] Example 7: The method of any one of Examples 1 to 6, further comprising deactivating the second BWP and reactivating the activated BWP during the enhanced mobile broadband (eMBB) operation mode.

[0179] Example 8: The method of any one of Examples 1 to 7, wherein the time slot format includes at least one of a half-duplex time slot or a full-duplex time slot.

[0180] Example 9: The method of any one of Examples 1 to 8, further comprising communicating with a base station to configure the second BWP to be activated when the activated BWP is deactivated during a transition of the UE from a half-duplex time slot to a full-duplex time slot.

[0181] Example 10: The method of any one of Examples 1 to 9, wherein the signaling priority includes at least one of low-priority signaling and high-priority signaling.

[0182] Example 11: The method of any one of Examples 1 to 10, wherein configuring the second BWP to be complementary to the activated BWP includes modifying one or more bits in the second BWP configuration to indicate that the second BWP is complementary.

[0183] Example 12: The method of any one of Examples 1 to 11, wherein configuring the second BWP to be complementary to the activated BWP includes modifying the BWP index associated with the activated BWP to indicate that the second BWP is complementary.

[0184] Example 13: The method of any one of Examples 1 to 12, further comprising activating the second BWP when the activated BWP is deactivated, and configuring the activated BWP to be complementary to the second BWP.

[0185] Example 14: The method of any one of Examples 1 to 13, further comprising activating the second BWP when the activated BWP is deactivated, and receiving downlink control information (DCI) for indicating another BWP among multiple BWPs that is complementary to the second BWP.

[0186] Example 15: The method of any one of Examples 1 to 14, further comprising activating the second BWP when the activated BWP is deactivated, and receiving radio resource control (RRC) data for indicating another BWP among multiple BWPs that is complementary to the second BWP.

[0187] Example 16: The method of any one of Examples 1 to 15 further includes activating a third BWP among a plurality of BWPs when the activated BWP is deactivated, and configuring a second BWP to be complementary to the third BWP based on the determined slot format or signaling priority, where the second BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0188] Example 17: The method of any one of Examples 1 to 16 further includes activating a third BWP among a plurality of BWPs when the activated BWP is deactivated, and configuring a fourth BWP to be complementary to the third BWP based on the determined slot format or signaling priority, where the fourth BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0189] Example 18: The method of any one of Examples 1 to 17 further includes activating a third BWP among a plurality of BWPs when the activated BWP is deactivated, and receiving data for indicating one BWP among a plurality of BWPs that is complementary to the third BWP, where the indicated one BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0190] Example 19: In the method of any one of Examples 1 to 18, receiving data for indicating that one BWP among a plurality of BWPs is complementary includes receiving data via one of downlink control information (DCI), MAC control element (MAC-CE), or radio resource control (RRC) transmission.

[0191] Example 20: A scheduled entity in a wireless communication network includes: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, where the processor and the memory are configured to execute the method of any one of Examples 1 to 19.

[0192] Example 21: A device configured for wireless communication includes units for executing the method of any one of Examples 1 to 19.

[0193] Example 22: A non-transitory computer-readable medium has instructions stored therein, the instructions being executable by one or more processors of a wireless communication device in a wireless communication network to execute the method of any one of Examples 1 to 19.

[0194] Example 23: A method for full-duplex communication in a scheduling entity, comprising: sending a first message for indicating active bandwidth parts (BWPs) of multiple BWPs for a carrier bandwidth of a scheduled entity; and sending a second message to the scheduled entity to configure a second BWP among the multiple BWPs to be complementary to the active BWP based on a time slot format or signaling priority of the determined active BWP, wherein the second BWP is designated as a new BWP for the UE that is deactivated based on the active BWP.

[0195] Example 24: The method of Example 23, wherein the second BWP is configured with a bandwidth that at least partially overlaps with the active BWP.

[0196] Example 25: The method of Example 23 and / or 24, wherein configuring the second BWP includes processing data related to radio frequency (RF) tuning on the active BWP and the second BWP.

[0197] Example 26: The method of any one of Examples 23 to 25, wherein the second BWP includes a subcarrier spacing different from that of the active BWP.

[0198] Example 27: The method of any one of Examples 23 to 26, wherein the second BWP includes a larger subcarrier spacing than the active BWP.

[0199] Example 28: The method of any one of Examples 23 to 27, wherein the second BWP is configured to be activated when the active BWP is deactivated during a ultra-reliable low-latency communication (URLLC) operation mode.

[0200] Example 29: The method of any one of Examples 23 to 28, further comprising configuring the second BWP to be deactivated and reactivating the active BWP during an enhanced mobile broadband (eMBB) operation mode.

[0201] Example 30: The method of any one of Examples 23 to 29, wherein the time slot format includes at least one of a half-duplex time slot and a full-duplex time slot.

[0202] Example 31: The method of any one of Examples 23 to 30, further comprising configuring the second BWP to be activated when the active BWP is deactivated during a transition from a half-duplex time slot to a full-duplex time slot.

[0203] Example 32: The method of any one of Examples 23 to 31, wherein the signaling priority includes at least one of low-priority signaling and high-priority signaling.

[0204] Example 33: The method of any one of Examples 23 to 32, wherein configuring the second BWP to be complementary to the active BWP includes modifying one or more bits in the second BWP configuration to indicate that the second BWP is complementary.

[0205] Example 34: The method of any one of Examples 23 to 33, wherein configuring the second BWP to be complementary to the activated BWP includes modifying the BWP index associated with the activated BWP to indicate that the second BWP is complementary.

[0206] Example 35: The method of any one of Examples 23 to 34, further comprising configuring the second BWP to be activated when the activated BWP is deactivated, and configuring the activated BWP to be complementary to the second BWP.

[0207] Example 36: The method of any one of Examples 23 to 35, further comprising configuring the second BWP to be activated when the activated BWP is deactivated, and transmitting downlink control information (DCI) for indicating another BWP among a plurality of BWPs that is complementary to the second BWP.

[0208] Example 37: The method of any one of Examples 23 to 36, further comprising configuring the second BWP to be activated when the activated BWP is deactivated, and transmitting radio resource control (RRC) data for indicating another BWP among a plurality of BWPs that is complementary to the second BWP.

[0209] Example 38: The method of any one of Examples 23 to 37, further comprising configuring a third BWP among a plurality of BWPs to be activated when the activated BWP is deactivated, and configuring the second BWP to be complementary to the third BWP based on a determined slot format or signaling priority, wherein the second BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0210] Example 39: The method of any one of Examples 23 to 38, further comprising configuring a third BWP among a plurality of BWPs to be activated when the activated BWP is deactivated, and configuring a fourth BWP to be complementary to the third BWP based on a determined slot format or signaling priority, wherein the fourth BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0211] Example 40: The method of any one of Examples 23 to 39, further comprising configuring a third BWP among a plurality of BWPs to be activated when the activated BWP is deactivated, and receiving data for indicating one BWP among a plurality of BWPs that is complementary to the third BWP, wherein the indicated one BWP is designated as the BWP to which the UE will switch when the third BWP is deactivated.

[0212] Example 41: The method of any one of Examples 23 to 40, wherein transmitting data for indicating that one of a plurality of BWPs is complementary includes transmitting the data via one of downlink control information (DCI), MAC control element (MAC-CE), or radio resource control (RRC) transmission.

[0213] Example 42: A scheduling entity in a wireless communication network, comprising: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, wherein the processor and the memory are configured to perform the method of any one of Examples 23 to 41.

[0214] Example 43: An apparatus configured for wireless communication, comprising units for performing the method of any one of Examples 23 to 41.

[0215] Example 44: A non-transitory computer-readable medium having instructions stored therein, the instructions executable by one or more processors of a wireless communication device in a wireless communication network to perform the method of any one of Examples 23 to 41.

[0216] Several aspects of a wireless communication network have been presented with reference to exemplary embodiments. Those skilled in the art will readily appreciate that the various aspects described throughout this disclosure can be extended to other telecommunication systems, network architectures, and communication standards.

[0217] By way of example, the various aspects can be implemented in 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 (GSM). The various aspects can also be extended to systems defined by the Third 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 telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0218] In this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior 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 a direct or 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 do not directly physically contact each other. For example, a first object can be coupled to a second object even if the first object never directly physically contacts the second object. The terms "circuit" and "circuitry" are used in a broad sense and are intended to include both hardware implementations of electrical devices and conductors which, when connected and configured, are capable of performing the functions described in this disclosure, but are not limited to the type of electronic circuits, as well as software implementations of information and instructions which, when executed by a processor, perform the functions described in this disclosure.

[0219] Figures 1 - 18 One or more of the components, steps, features, and / or functions shown therein may 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 may also be added without departing from the novel features disclosed herein. Figures 1 - 14 The apparatus, device, and / or components shown therein may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may 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 an exemplary process. Based on design preferences, it is understood that the specific order or hierarchy of steps in the method can be rearranged. The accompanying method claims present the elements of the steps in an example order and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

[0221] The foregoing description is provided to enable a person of ordinary skill 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, where elements recited in the singular are 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 a list of at least one of an item refers to any combination of those items, including a single member. For 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. Similarly, a phrase referring to "a and / or b" is intended to cover: a; b; and a and b. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure, known or later coming to be known to those of ordinary skill in the art, are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. A user equipment (UE) in a wireless communication network, comprising: A wireless transceiver; A memory; And A processor communicatively coupled to the wireless transceiver and the memory, wherein the processor and the memory are configured to: Communicate with a base station to configure an active bandwidth part (BWP) among a plurality of BWPs for a carrier bandwidth of the UE, wherein the active BWP is configured to be in a first full-duplex (FD) time slot having a first uplink (UL) band; Based on one or more of operating conditions, preconfigured criteria, network-provided information, and / or the capabilities of the UE, configure a second BWP among the plurality of BWPs to be complementary to the active BWP, wherein the second BWP is configured to be in a second FD time slot having a second UL band, and the first UL band is less than the second UL band; Communicate the configured second BWP to the base station; Receive scheduling information from the base station on the active BWP, the scheduling information identifying the second BWP that is activated in response to deactivation of the active BWP; and Activate the second BWP in response to deactivation of the active BWP.

2. The UE according to claim 1, wherein, The second BWP has a bandwidth that at least partially overlaps with the active BWP.

3. The UE according to claim 1, wherein, The second BWP includes a subcarrier spacing different from that of the active BWP.

4. The UE according to claim 1, wherein, The processor and the memory are configured to communicate with the base station to configure the second BWP to be complementary to the active BWP by: Receiving a second BWP configuration including one or more bits for indicating that the second BWP is complementary, or Receiving a modified BWP index for indicating that the second BWP is complementary and associated with the activated BWP.

5. The UE according to claim 1, wherein, The processor and the memory are configured to configure the active BWP to be complementary to the second BWP.

6. The UE according to claim 1, wherein, The processor and the memory are further configured to: Receive downlink control information (DCI) indicating another BWP among the plurality of BWPs that is complementary to the second BWP; or Receive radio resource control (RRC) signaling indicating another BWP among the plurality of BWPs that is complementary to the second BWP.

7. The UE according to claim 1, wherein, The processor and the memory are further configured to communicate with the base station to configure the second BWP to be complementary to the active BWP based on the ability of the UE to switch to the second BWP among the plurality of BWPs faster than another BWP among the plurality of BWPs.

8. A method for full-duplex (FD) communication in a user equipment (UE), comprising: Communicate with a base station to configure an active bandwidth part (BWP) among a plurality of BWPs for a carrier bandwidth of the UE, wherein the active BWP is configured to be in a first FD time slot having a first uplink (UL) band; Based on one or more of operating conditions, preconfigured criteria, network-provided information, and / or the capabilities of the UE, configure a second BWP among the plurality of BWPs to be complementary to the active BWP, wherein the second BWP is configured to be in a second FD time slot having a second UL band, and the first UL band is less than the second UL band; Communicate the configured second BWP to the base station; Receive scheduling information from the base station on the active BWP, the scheduling information identifying the second BWP that is activated in response to deactivation of the active BWP; and Activate the second BWP in response to deactivation of the active BWP.

9. The method according to claim 8, wherein, The second BWP has at least partially overlapping bandwidth with the active BWP.

10. The method according to claim 8, wherein, The second BWP includes a subcarrier spacing different from that of the active BWP.

11. The method according to claim 8, wherein, Communicating with the base station to configure the second BWP to be complementary to the active BWP includes: Receiving downlink control information (DCI) indicating another BWP among the plurality of BWPs that is complementary to the second BWP; or Receiving radio resource control (RRC) signaling indicating another BWP among the plurality of BWPs that is complementary to the second BWP.

12. A scheduling entity in a wireless communication network, comprising: A wireless transceiver; A memory; And A processor communicatively coupled to the wireless transceiver and the memory, wherein the processor and the memory are configured to: Communicate with a scheduled entity to configure an active bandwidth part (BWP) among a plurality of BWPs for the carrier bandwidth of the scheduled entity, wherein the active BWP is configured to be in a first full-duplex (FD) time slot having a first uplink (UL) band; and Receive, from the scheduled entity, information for configuring a second BWP among the plurality of BWPs to be complementary to the active BWP based on one or more of operating conditions, preconfigured criteria, network-provided information, and / or the capabilities of the scheduled entity, wherein the second BWP is configured to be in a second FD time slot having a second UL band, and the first UL band is less than the second UL band; and Send control information associated with the active BWP to the scheduled entity, the control information identifying the second BWP configured to be activated by the scheduled entity in response to deactivation of the active BWP to maintain communication continuity in the FD operation.

13. The scheduling entity according to claim 12, wherein, The second BWP has at least partially overlapping bandwidth with the active BWP.

14. The scheduling entity according to claim 12, wherein, The second BWP includes a subcarrier spacing different from that of the active BWP.

15. The scheduling entity according to claim 12, wherein, The processor and the memory are configured to communicate with the scheduled entity to configure the second BWP to be complementary to the activated BWP by: Sending a second BWP configuration including one or more bits for indicating that the second BWP is complementary, or Sending a modified BWP index associated with the activated BWP for indicating that the second BWP is complementary.

16. The scheduling entity according to claim 12, wherein, The active BWP is configured to be complementary to the second BWP.

17. The scheduling entity according to claim 12, wherein, The processor and the memory are further configured to: Send downlink control information (DCI) indicating another BWP among the plurality of BWPs that is complementary to the second BWP; or Send radio resource control (RRC) signaling indicating another BWP among the plurality of BWPs that is complementary to the second BWP.

18. A method for full-duplex (FD) communication in a scheduling entity, comprising: Communicate with the scheduled entity to configure the active bandwidth part (BWP) among multiple BWPs for the carrier bandwidth of the scheduled entity, wherein the active BWP is configured to be in a first full-duplex (FD) time slot having a first uplink (UL) band; and Receive, from the scheduled entity, information for configuring a second BWP among the multiple BWPs to be complementary to the active BWP, based on one or more of operating conditions, pre-configured criteria, network-provided information, and / or the capabilities of the scheduled entity, wherein the second BWP is configured to be in a second FD time slot having a second UL band, and the first UL band is less than the second UL band; and Send control information associated with the active BWP to the scheduled entity, the control information identifying the second BWP configured to be activated by the scheduled entity in response to deactivation of the active BWP to maintain communication continuity in the FD operation.

19. The method according to claim 18, wherein, The second BWP has at least partially overlapping bandwidth with the active BWP.

20. The method according to claim 18, wherein, The second BWP includes a subcarrier spacing different from that of the active BWP.

21. The method according to claim 18, wherein, Configuring the second BWP to be complementary to the activated BWP includes: Sending downlink control information (DCI) indicating another BWP among the multiple BWPs that is complementary to the second BWP; or Sending radio resource control (RRC) signaling indicating another BWP among the multiple BWPs that is complementary to the second BWP.

Images