SYSTEMS AND METHODS FOR PROVIDING SUB-BAND FULL-DUPLEX COVERAGE FOR LEGACY USER EQUIPMENT

A network device may receive an indication to enable sub-band full duplex uplink transmission for a first user equipment (UE), and may determine whether the first UE and a second UE are associated with a separation that is more than a threshold separation. The network device may enable the sub-band full duplex uplink transmission for the first UE based on determining that the first UE and the second UE are associated with a separation that is more than the threshold separation. The network device may deny the sub-band full duplex uplink transmission for the first UE based on determining that the first UE and the second UE are associated with a separation that is less than the threshold separation.

BACKGROUND

A radio access network (RAN) may utilize sub-band full-duplex to allow for transmit and receive at the same time. Sub-band full-duplex is beneficial to RAN capacity and uplink (UL) coverage enhancement over time division duplex (TDD), such as has been specified for fifth generation (5G) New Radio (5G NR) RANs. Sub-band full-duplex may enable the RAN to enhance UL coverage for some user equipment (UEs) in an otherwise downlink (DL) traffic dominated cell, which may be useful for uplink-intensive applications (e.g., for video transmission, voice-over-New-Radio (VoNR), etc.).

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Sub-band full-duplex operation (e.g., extended UL transmission (Tx)) is increasingly possible in fifth-generation (5G) RANs using advanced RAN devices (e.g., gNodeBs or gNBs). An advanced RAN device may enable sub-band full-duplex by providing spatial isolation (e.g., a using beam steering or other spatial multiplexing), frequency isolation (e.g., using sub-bands), receive (Rx) filtering (e.g., using sub-bands), beam nulling (e.g., using beam steering), self-cancelation (e.g., both analog (beam) and digital (baseband)), and/or the like. Sub-band full duplex can be enabled where cross-link interference (CLI) between UEs and/or RAN devices is minimized. Although a RAN device may provide sub-band full-duplex operation, legacy UEs may fail to include one or more features required to utilize the sub-band full-duplex. For example, legacy UEs may be unable to transmit and receive signals at the same time, may be unable to provide necessary information to assist a RAN device in provisioning of sub-band full-duplex, may be unable to perform radio frequency and/or digital filtering, may be unable to measure potential CLI with other legacy UEs and/or between two RAN devices, and the like.

Thus, current network and UE configurations consume computing resources (e.g., processing resources, memory resources, communication resources, and/or the like), networking resources, and/or other resources associated with enabling sub-band full-duplex (e.g., extended UL Tx) for a UE experiencing CLI with another UE (e.g., receiving DL signals), degrading performance of the other UE due to the CLI with the UE, degrading performance of the UE due to the CLI with the other UE, failing to enable sub-band full-duplex for UEs not experiencing CLI, and/or the like.

Some implementations described herein provide a system and method that provides sub-band full-duplex coverage for legacy UEs. For example, a network device (e.g., a RAN device) may receive an indication that a first UE requires extended uplink transmission, and may determine whether the first UE and a second UE are associated with a separation that does not produce CLI. The RAN device provides the extended uplink transmission to the first UE based on determining that the first UE and the second UE are associated with a separation that does not produce CLI, and does not provide the extended uplink transmission to the first UE when the separation will likely produce CLI. The RAN device may determine separation based on which beams are servicing the first UE and second UE, such that where a beam separation between a first beam serving the first UE is more than a threshold separation from a second beam serving the second UE, the RAN device may enable the extended uplink transmission to the first UE. The RAN device may also determine separation by calculating a distance between a location of the first UE and a location of the second UE (which may be useful, for example, where the first UE and second UE are served by the same beam, or where the first beam and second beam are within the threshold beam separation).

To avoid CLI associated with the transmissions by other RAN devices (e.g., at a cell edge), the system and method may include RAN devices that provide to neighboring RAN devices a notification identifying the regions in which it is providing extended uplink transmission to its served UEs. For example, the RAN device may include an information element in a cell resource coordination message sent to neighboring RAN devices that indicates locations where extended uplink transmission is scheduled. When determining whether to provide extended uplink transmission to a first UE, the RAN device may determine whether a beam separation between a first beam serving the first UE is more than a threshold separation from a region identified as being in use by a neighboring RAN device.

In this way, the system and method provide sub-band full-duplex coverage for legacy UEs. For example, the RAN device may address the potential for CLI so that legacy UEs may benefit from sub-band full-duplex (e.g., by receiving more UL throughput and coverage). The RAN device may utilize beam or UE positioning to identify potential CLI between UEs, and to enable sub-band full-duplex for UEs not likely to experience CLI. The RAN device may enhance spatial information sharing with other RAN devices to avoid inter-cell CLI. Thus, the RAN device may conserve computing resources, networking resources, and/or other resources that would have otherwise been consumed by enabling sub-band full-duplex (e.g., extended UL Tx) for a UE experiencing CLI with another UE (e.g., receiving DL signals), degrading performance of the other UE due to the CLI with the UE, degrading performance of the UE due to the CLI with the other UE, failing to enable sub-band full-duplex for UEs not experiencing CLI, and/or the like.

FIGS.1A-1Fare diagrams of an example100associated with providing sub-band full-duplex coverage for legacy UEs. As shown inFIGS.1A-1F, example100includes UEs105(e.g., a first UE105-1and a second UE105-2), RAN devices110, and a core network115. Further details of the UEs105, the RAN devices110, and the core network115are provided elsewhere herein.

As shown inFIG.1A, and by reference number120, the RAN device110may receive an indication that the first UE105-1should be provided the ability to use extended uplink (UL) transmission (Tx) (e.g., sub-band full-duplex). For example, the first UE105-1may utilize an application (e.g., a VoNR application) that may benefit from extended UL Tx in a cell served by the RAN device110. The first UE105-1may generate the indication that the first UE105-1is requesting extended UL Tx (e.g., based on the first UE105-1utilizing the application). The first UE105-1may provide the indication that the first UE105-1is requesting extended UL Tx to the RAN device110, and the RAN device110may receive the indication that the first UE105-1is requesting extended UL Tx. In some implementations, the RAN device110may not receive the indication that the first UE105-1is requesting extended UL Tx, but rather may determine that the first UE105-1should be provided extended UL Tx, such as based on usage of the cell and the RAN device110by the first UE105-1, or by another notification (e.g., from elements of core network115).

As further shown inFIG.1A, and by reference number125, the RAN device110may receive information associated with the second UE105-2being served. For example, the second UE105-2may be served by the same RAN device110as UE105-1, and may be engaged in transmissions over the RAN (e.g., by utilizing a streaming application associated with downlink (DL) traffic). The second UE105-2may generate the information associated with the second UE105-2(e.g., identification of the second UE105-2, a UE type of the second UE105-2, and/or the like) based on the second UE105-2utilizing the application. The second UE105-2may provide the information associated with the second UE105-2to the RAN device110, and the RAN device110may receive the information associated with the second UE105-2. In some implementations, the RAN device110may not receive the information associated with the second UE105-2, but rather may determine the information associated with the second UE105-2based on usage of the cell and the RAN device110by the second UE105-2, or by another notification (e.g., from elements of core network115).

As further shown inFIG.1A, and by reference number130, the RAN device110may determine whether the first UE105-1and the second UE105-2are associated with a separation that will not produce CLI (e.g., any CLI will be below a level that negatively impacts communications). In order to determine whether to serve the first UE105-1with the extended UL Tx, in some implementations the RAN device110may determine whether the first UE105-1and the second UE105-2are associated with a threshold level of beam separation. For example, a first beam may be serving the first UE105-1, and is providing service in a first region of the cell associated with the RAN device110. A second beam may be serving the second UE105-2, and is providing service in a second region of the cell that is different than the first region. The RAN device110may determine that the first UE105-1and the second UE105-2are associated with a threshold level of beam separation and thus no CLI should exist between the first UE105-1and the second UE105-2(e.g., because the first region and second region are sufficiently spatially separated).

As further shown inFIG.1A, and by reference number135, the RAN device110may enable the use of extended UL Tx for the first UE105-1based on the first UE105-1and the second UE105-2being associated with a separation that is not expected to produce CLI. For example, if the RAN device110determines that the first UE105-1and the second UE105-2are associated with a beam separation that is more than a threshold amount of beam separation, the

RAN device110may provide the extended UL Tx to the first UE105-1. In some implementations, the RAN device may enable the extended UL Tx for the first UE105-1by scheduling the first UE105-1to use certain of the available sub-bands for uplink transmissions (e.g., sub-bands that would normally be used for downlink transmissions). The RAN device may provide scheduling information to the first UE105-1that contains indications that certain of the available sub-bands are to be used for uplink transmissions. The extended UL Tx may provide improved uplink services to the first UE105-1(e.g., improved upload bandwidth) and an application in use on the first UE105-1.

In some implementations, the RAN device110may determine locations of the first UE105-1and the second UE105-2, and use these locations to determine whether CLI may exist between the first UE105-1and the second UE105-2if extended UL Tx is provided to the first UE105-1. For example, when the beam separation between the beams serving the first UE and second UE is below the beam separation threshold (e.g., where the first UE and second UE are being served by the same beam, or the first beam and second beam are serving adjacent regions), it may still be possible to provide extended UL Tx if the actual distance between the first UE and second UE is more than a distance threshold that would produce unacceptable levels of CLI.

As shown inFIG.1B, and by reference number140, the RAN device110may calculate a distance between a first location of the first UE105-1and a second location of the second UE105-2. In some implementations, when calculating the distance between the first location of the first UE105-1and the second location of the second UE105-2, the RAN device110may utilize a UE positioning process to receive a first estimated location of the first UE105-1and a second estimated location of the second UE105-2. The RAN device110may then calculate the distance based on the first estimated location of the first UE105-1and the second estimated location of the second UE105-2. The UE positioning process may provide the estimated UE locations with a particular accuracy (e.g., less than ten meters and with a latency of less than ten milliseconds).

As further shown inFIG.1B, and by reference number145, the RAN device110may determine whether the distance exceeds a distance threshold. For example, the RAN device110may establish a distance threshold (e.g., in meters) for the calculated distance between the first location of the first UE105-1and the second location of the second UE105-2. In some implementations, the RAN device110may determine that the distance exceeds the distance threshold. Alternatively, the RAN device110may determine that the distance fails to exceed the distance threshold.

As further shown inFIG.1B, and by reference number150, if the RAN device110determines that the distance exceeds the distance threshold, the RAN device110may determine that there is not expected to be CLI between the first UE105-1and the second UE105-2(e.g., since they are spaced far enough apart to prevent CLI). When the RAN device110determines that there is not expected to be CLI between the first UE105-1and the second UE105-2, the

RAN device110may provide the extended UL Tx to the first UE105-1.

In some implementations, the distance determinations described above may be performed by the RAN device after determining that the beam separation threshold is not exceeded by the beams serving the first UE and second UE. In other implementations, the RAN device may perform the distance determinations described above as an alternative to doing the beam separation determinations described above (and with reference toFIG.1A). The use of either/both operations may depend on factors such as: cell loading, cell size, beam count, RAN device capabilities, etc.

If the RAN device determines that first UE105-1and second UE105-2are not sufficiently separated (and therefore there is a possibility for CLI), the RAN device my deny the use of enhanced UL Tx. In some implementations, this denial may take the form of retaining the normal DL/UL use of available sub-bands by the first UE105-1. In some implementations, a response message may be provided with an indication of the denial. In some implementations, denial may occur after enhanced UL Tx has been enabled for the first UE105-1, such as if the location of the first UE105-1changes and/or the location of the second UE105-2changes, resulting in a separation that is no longer above the threshold for potential CLI.

In some implementations, the RAN device110may use DL reference signal received power (RSRP) reports from the UEs in its serving cell to ensure that CLI from extended UL Tx is not impacting communications with the RAN device. For example, if other UEs in the service cell report increased RSRP during the times when a UE is using enhanced UL Tx, that is an indication that CLI is being caused by those UL transmissions, and the RAN device should end the enhanced UL Tx. As shown inFIG.1C, and by reference number155, the RAN device110may receive an RSRP report from the second UE105-2. In some implementations, the RAN device110may request that the second UE105-2measure the DL RSRP and provide the DL RSRP report to the RAN device110. In some implementations, the second UE105-2may periodically report its RSRP automatically to the RAN device110.

As further shown inFIG.1C, and by reference number160, the RAN device110may determine whether the DL RSRP increases when the first UE105-1is utilizing the extended UL Tx. For example, the second UE105-2may measure a first DL RSRP during a first time period when the first UE105-1is not utilizing the extended UL Tx, and may measure a second DL RSRP during a second time period when the first UE105-1is utilizing the extended UL Tx. The second UE105-2may provide the first DL RSRP and the second DL RSRP in reports to the RAN device110. The RAN device110may determine whether the second DL RSRP is greater than the first DL RSRP to determine whether the DL RSRP increases when the first UE105-1is utilizing the extended UL Tx. The RAN device110may determine that the DL RSRP increases when the first UE105-1is utilizing the extended UL Tx (e.g., when the second DL RSRP is greater than the first DL RSRP). Alternatively, the RAN device110may determine that the DL RSRP fails to increase when the first UE105-1is utilizing the extended UL Tx (e.g., when the second DL RSRP is not greater than the first DL RSRP).

As further shown inFIG.1C, and by reference number165, the RAN device110may determine that the DL RSRP fails to increase when the first UE105-1is utilizing the extended UL Tx (e.g., when the second DL RSRP is not greater than the first DL RSRP), indicating that there is no CLI being caused by the first UE's use of extended UL Tx, and may continue to provide the extended UL Tx to the first UE105-1. Alternatively, as shown by reference number170, the RAN device110may determine that the DL RSRP increases when the first UE105-1is utilizing the extended UL Tx (e.g., when the second DL RSRP is greater than the first DL RSRP), and conclude that this indicates CLI is being produced due to the use of extended UL Tx by the first UE105-1. The RAN device110may then terminate the use of extended UL Tx by the first UE105-1based on the DL RSRP increasing.

In some implementations, the system and method may include facilities to allow RAN devices110to provide to each other a notification identifying the regions in which they are providing sub-band full duplex uplink transmissions to its served UEs105. This may be useful to avoid CLI associated with the transmissions between UEs105and other RAN devices110(e.g., at a cell edge). Each RAN device110may then use this uplink information to adjust determinations of whether to allow a UE105to perform extended UL Tx. For example, each RAN device110may include an information element in a cell resource coordination message sent to neighboring RAN devices that indicates those locations where extended uplink transmission is scheduled. When determining whether to provide extended uplink transmission to the first UE105-1, the RAN device110may determine whether a beam separation between a first beam serving the first UE105-1is more than the threshold separation from a region identified as being in use by a neighboring RAN device110.

In some implementations, the indication of which locations are using extended UL Tx may be done using a bitmap where each bit is associated with a specific region, and reflects whether enhanced UL Tx has been enabled for that region. Receiving RAN devices110may then use the bitmap (and a translation mechanism such as a lookup table) to adjust their preexisting information on the DL/UL pattern being used by the RAN device110providing the indication. In some implementations, the indication may include a partial or full DL/UL pattern associated with providing RAN device110that reflects the instances where enhanced UL Tx is enabled. Other types of indications would also be possible.

As shown inFIG.1D, the RAN device110-1may provide service to a first cell (e.g., Cell1) and another RAN device110-2may provide service to a second cell (e.g., Cell2). The first UE105-1may be located within the first cell and the second UE105-2may be located in the second cell, but are proximate to each other due to their locations near the edges of Cell1and Cell2, respectively.

As further shown inFIG.1D, and by reference number175, the RAN device110-1may receive a translation mapping that allows the RAN device110-1to translate indications of enhanced UL Tx usage from other RAN devices (including RAN device110-2) into spatial information relative to RAN device110-1. For example, an operations, administration, and maintenance (OAM) function of the core network115may provide, to the RAN device110-1(e.g., and the other RAN device110-2, although not shown) the translation mapping. In some implementations, the translation mapping may be a lookup table that maps information in the usage indications (e.g., bit fields) to spatial information.

As further shown inFIG.1D, and by reference number180, the RAN device110-1may receive a notification from RAN device110-2identifying the regions in which RAN device110-2is providing extended uplink transmission to its served UEs105. For example, the other RAN device110-2may be serving the second UE105-2, and may generate the notification to include a first value indicating that enhanced UL Tx is scheduled to be utilized for the second UE105-2in its region, and a second value indicating that is not scheduled to be utilized for the second UE105-2in its region. In some implementations, the indication may be provided as an information element in a cell resource coordination message sent between RAN devices (e.g., over an Xn interface). In one example, the indication may comprise a synchronization signal block (SSB) resource indication information element, which may be included in cell resource coordination message.

As shown inFIG.1E, and by reference number185, the RAN device110-1may determine whether CLI will likely exist between the first UE105-1and the second UE105-2based on the notification from RAN device110-2. For example, the RAN device110-1may identify, by applying the indications of enhanced UL Tx usage in the notification to the translation mapping, spatial information associated with the usage by second UE105-2of radio resources. The RAN device110-1may determine whether CLI will likely exist between the first UE105-1and the second UE105-2based on the spatial information (e.g., a region of operation, coordinates, etc.), similar as has been described above. For example, the RAN device110-1may determine a separation between the first UE105-1and second UE105-2, such by determining whether a beam separation (which may be based on service regions) is more than a beam separation threshold.

As further shown inFIG.1E, and by reference number190, the RAN device110-1may provide the extended UL Tx to the first UE105-1based on determining that CLI will likely not occur between the first UE105-1and the second UE105-2due to the existence of separation over the threshold.

As shown inFIG.1F, and by reference number195, the RAN device110-1may deny extended UL Tx for the first UE105-1based on determining that CLI will likely occur between the first UE105-1and the second UE105-2due to the separation being less than the threshold.

In this way, the RAN device110provides sub-band full-duplex coverage for legacy UEs105. For example, the RAN device110may address the CLI issues associated with uplink transmission in downlink sub-bands without the need to modify the legacy UE's existing radio interface, so that legacy UEs105may obtain the benefits of sub-band full-duplex (e.g., more UL throughput). Thus, the RAN device110may conserve computing resources, networking resources, and/or other resources that would have otherwise been consumed by enabling sub-band full-duplex (e.g., extended UL Tx) for a UE105experiencing CLI with another UE105(e.g., receiving DL signals), degrading performance of the other UE105due to the CLI with the UE105, degrading performance of the UE105due to the CLI with the other UE105, failing to enable sub-band full-duplex for UEs105not experiencing CLI, and/or the like.

As indicated above,FIGS.1A-1Fare provided as an example. Other examples may differ from what is described with regard toFIGS.1A-1F. The number and arrangement of devices shown inFIGS.1A-1Fare provided as an example. In practice, there may be additional devices, fewer devices, different devices, or differently arranged devices than those shown inFIGS.1A-1F. Furthermore, two or more devices shown inFIGS.1A-1Fmay be implemented within a single device, or a single device shown inFIGS.1A-1Fmay be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) shown inFIGS.1A-1Fmay perform one or more functions described as being performed by another set of devices shown inFIGS.1A-1F.

FIG.2is a diagram of an example environment200in which systems and/or methods described herein may be implemented. As shown inFIG.2, the example environment200may include the UE105, the RAN device110, the core network115, and a data network255. Devices and/or networks of the example environment200may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

The UE105includes one or more devices capable of receiving, generating, storing, processing, and/or providing information, such as information described herein. For example, the UE105can include a mobile phone (e.g., a smart phone or a radiotelephone), a laptop computer, a tablet computer, a desktop computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smart watch or a pair of smart glasses), a mobile hotspot device, a fixed wireless access device, customer premises equipment, an autonomous vehicle, or a similar type of device.

The RAN device110may support, for example, a cellular radio access technology (RAT). The RAN device110may include one or more base stations (e.g., base transceiver stations, radio base stations, node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cellular sites, cellular towers, access points, transmit receive points (TRPs), radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar types of devices) and other network entities that can support wireless communication for the UE105. The RAN device110may transfer traffic between the UE105(e.g., using a cellular RAT), one or more base stations (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and/or the core network115. The RAN device110may provide one or more cells that cover geographic areas.

In some implementations, the RAN device110may perform scheduling and/or resource management for the UE105covered by the RAN device110(e.g., the UE105covered by a cell provided by the RAN device110). In some implementations, the RAN device110may be controlled or coordinated by a network controller, which may perform load balancing, network-level configuration, and/or other operations. The network controller may communicate with the RAN device110via a wireless or wireline backhaul. In some implementations, the RAN device110may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. In other words, the RAN device110may perform network control, scheduling, and/or network management functions (e.g., for uplink, downlink, and/or sidelink communications of the UE105covered by the RAN device110).

In some implementations, the core network115may include an example functional architecture in which systems and/or methods described herein may be implemented. For example, the core network115may include an example architecture of a 5G next generation (NG) core network included in a 5G wireless telecommunications system. While the example architecture of the core network115shown inFIG.2may be an example of a service-based architecture, in some implementations, the core network115may be implemented as a reference-point architecture and/or a 4G core network, among other examples.

As shown inFIG.2, the core network115may include a number of functional elements. The functional elements may include, for example, a network slice selection function (NSSF)205, a network exposure function (NEF)210, an authentication server function (AUSF)215, a unified data management (UDM) component220, a policy control function (PCF)225, an application function (AF)230, an access and mobility management function (AMF)235, a session management function (SMF)240, and/or a user plane function (UPF)245. These functional elements may be communicatively connected via a message bus250. Each of the functional elements shown inFIG.2is implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of the functional elements may be implemented on physical devices, such as an access point, a base station, and/or a gateway. In some implementations, one or more of the functional elements may be implemented on a computing device of a cloud computing environment.

The NSSF205includes one or more devices that select network slice instances for the UE105. By providing network slicing, the NSSF205allows an operator to deploy multiple substantially independent end-to-end networks potentially with the same infrastructure. In some implementations, each slice may be customized for different services.

The NEF210includes one or more devices that support exposure of capabilities and/or events in the wireless telecommunications system to help other entities in the wireless telecommunications system discover network services.

The AUSF215includes one or more devices that act as an authentication server and support the process of authenticating the UE105in the wireless telecommunications system.

The UDM220includes one or more devices that store user data and profiles in the wireless telecommunications system. The UDM220may be used for fixed access and/or mobile access in the core network115.

The PCF225includes one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and/or mobility management, among other examples.

The AF230includes one or more devices that support application influence on traffic routing, access to the NEF210, and/or policy control, among other examples.

The AMF235includes one or more devices that act as a termination point for non-access stratum (NAS) signaling and/or mobility management, among other examples.

The SMF240includes one or more devices that support the establishment, modification, and release of communication sessions in the wireless telecommunications system. For example, the SMF240may configure traffic steering policies at the UPF245and/or may enforce user equipment IP address allocation and policies, among other examples.

The UPF245includes one or more devices that serve as an anchor point for intraRAT and/or interRAT mobility. The UPF245may apply rules to packets, such as rules pertaining to packet routing, traffic reporting, and/or handling user plane QoS, among other examples.

The message bus250represents a communication structure for communication among the functional elements. In other words, the message bus250may permit communication between two or more functional elements.

The data network255includes one or more wired and/or wireless data networks. For example, the data network255may include an IP Multimedia Subsystem (IMS), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network such as a corporate intranet, an ad hoc network, the Internet, a fiber optic-based network, a cloud computing network, a third-party services network, an operator services network, and/or a combination of these or other types of networks.

FIG.3is a diagram of example components of a device300, which may correspond to the UE105, the RAN device110, the NSSF205, the NEF210, the AUSF215, the UDM220, the PCF225, the AF230, the AMF235, the SMF240, and/or the UPF245. In some implementations, the UE105, the RAN device110, the NSSF205, the NEF210, the AUSF215, the UDM220, the PCF225, the AF230, the AMF235, the SMF240, and/or the UPF245may include one or more devices300and/or one or more components of the device300. As shown inFIG.3, the device300may include a bus310, a processor320, a memory330, an input component340, an output component350, and a communication component360.

The bus310includes one or more components that enable wired and/or wireless communication among the components of the device300. The bus310may couple together two or more components ofFIG.3, such as via operative coupling, communicative coupling, electronic coupling, and/or electric coupling. The processor320includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, and/or another type of processing component. The processor320is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the processor320includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

The memory330includes volatile and/or nonvolatile memory. For example, the memory330may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory). The memory330may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection). The memory330may be a non-transitory computer-readable medium. Memory330stores information, instructions, and/or software (e.g., one or more software applications) related to the operation of the device300. In some implementations, the memory330includes one or more memories that are coupled to one or more processors (e.g., the processor320), such as via the bus310.

The input component340enables the device300to receive input, such as user input and/or sensed input. For example, the input component340may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and/or an actuator. The output component350enables the device300to provide output, such as via a display, a speaker, and/or a light-emitting diode. The communication component360enables the device300to communicate with other devices via a wired connection and/or a wireless connection. For example, the communication component360may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.

FIG.4is a flowchart of an example process400for providing sub-band full-duplex coverage for legacy UEs. In some implementations, one or more process blocks ofFIG.4may be performed by a network device (e.g., the RAN device110). In some implementations, one or more process blocks ofFIG.4may be performed by another device or a group of devices separate from or including the network device, such as a UE (e.g., the UE105-1). Additionally, or alternatively, one or more process blocks ofFIG.4may be performed by one or more components of the device300, such as the processor320, the memory330, the input component340, the output component350, and/or the communication component360.

As shown inFIG.4, process400may include receiving an indication to enable sub-band full duplex uplink transmission for a first UE (block410). For example, the network device may receive an indication to enable sub-band full duplex uplink transmission for a first UE, as described above.

As further shown inFIG.4, process400may include determining whether the first UE and a second UE are associated with a separation that is more than a threshold separation (block420). For example, the network device may determine whether the first UE and a second UE are associated with a separation that is more than a threshold separation, as described above. In some implementations, determining whether the first UE and a second UE are associated with a separation that is more than a threshold separation includes determining whether a first beam serving the first UE and a second beam serving the second UE have a beam separation that is more than a threshold beam separation. In some implementations, determining whether the first UE and a second UE are associated with a separation that is more than a threshold separation includes calculating a distance between a first location of the first UE and a second location of the second UE, and determining whether the distance exceeds a distance threshold.

As further shown inFIG.4, process400may include enabling the sub-band full duplex uplink transmission for the first UE based on determining that the first UE and the second UE are associated with a separation that is more than the threshold separation (block430). For example, the network device may enable the sub-band full duplex uplink transmission for the first UE based on determining that the first UE and the second UE are associated with a separation that is more than the threshold separation, as described above.

As further shown inFIG.4, process400may include denying the sub-band full duplex uplink transmission for the first UE based on determining that the first UE and the second UE are associated with a separation that is less than the threshold separation (block440). For example, the network device may deny the sub-band full duplex uplink transmission for the first UE based on determining that the first UE and the second UE are associated with a separation that is less than the threshold separation, as described above.

In some implementations, process400includes receiving a DL RSRP from the second UE, determining whether the DL RSRP increases during a time period when the first UE is utilizing the sub-band full duplex uplink transmission, and denying the sub-band full duplex uplink transmission by the first UE based on determining that the DL RSRP increased during the time period.

In some implementations, process400includes receiving a notification that identifies sub-band full duplex uplink transmission usage information by another network device, determining based on the sub-band full duplex uplink information whether the first UE and a third UE are separated by more than the threshold, and denying the use of sub-band full duplex uplink transmission by the first UE based on determining that the first UE and third UE are not separated by more than the threshold. In some implementations, the notification of sub-band full duplex uplink transmission usage information is included in a cell resource coordination message. In some implementations, process400includes receiving a translation mapping to allow the network device to translate the sub-band full duplex uplink transmission usage information into spatial information relative to the network device.