WO2025049721A1

WO2025049721A1 - Hybrid device and network entity for a wireless system

Info

Publication number: WO2025049721A1
Application number: PCT/US2024/044393
Authority: WO
Inventors: Nishithkumar TRIPATHI; Jeffrey H. Reed; Rahul Varma CHINTALAPATI
Original assignee: Virginia Tech Intellectual Properties Inc
Current assignee: Virginia Tech Intellectual Properties Inc
Priority date: 2023-08-29
Filing date: 2024-08-29
Publication date: 2025-03-06
Anticipated expiration: 2026-02-28

Abstract

The present disclosure is directed to a Hybrid Device and Network (HDN) entity for a wireless system. One general aspect includes an HDN entity that includes a processing unit configured to perform functions conventionally associated with a user equipment and to execute scheduling functions conventionally associated with a base station, where the scheduling functions may include allocating radio resources to one or more communication devices within a target coverage area of the HDN entity. The HDN entity also includes a control channel interface operably coupled to the processing unit. The control channel interface is configured to transmit and receive control signals used for managing the allocated radio resources for the one or more communication devices.

Description

HYBRID DEVICE AND NETWORK ENTITY FOR A WIRELESS SYSTEM CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63/579,379, titled “Hybrid Device and Network for a Wireless System,” filed August 29, 2023, the entire contents of which are hereby incorporated by reference herein. BACKGROUND [0002] Wireless communication systems have evolved significantly, with various advancements aimed at improving data transfer efficiency and user connectivity. A typical wireless system comprises several components, including communication devices, base stations, and core networks. The architecture of these systems has traditionally relied on integrated base stations, where user traffic is routed through a central unit before reaching its destination. This setup, while effective, introduces potential bottlenecks, such as long latency, particularly in scenarios requiring local data exchanges among devices within the same geographical area. [0003] In response to these challenges, to reduce costs, and to increase flexibility, disaggregated base stations have been developed, allowing for a separation of radio processing tasks between distributed units and central units. This architecture enables more flexible deployment options and can improve the overall efficiency of the wireless network. However, even with these advancements, the need to route all user traffic through a central unit remains a limiting factor. SUMMARY [0004] This Summary introduces a selection of concepts in a simplified form that are further described below in the Detailed Description. As such, this Summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. [0005] The present disclosure is directed to a Hybrid Device and Network (HDN) entity for a wireless system. One general aspect includes an HDN entity that includes a processing unit configured to perform functions conventionally associated with a User Equipment (UE) and to execute scheduling functions conventionally associated with a base station, where the scheduling functions may include allocating radio resources to one or more communication devices (e.g., UEs) within a target coverage area of the HDN entity. The HDN entity also includes a control channel interface operably coupled to the processing unit. The control channel interface is configured to transmit and receive control signals used for managing the allocated radio resources for one or more communication devices. [0006] Implementations may include one or more of the following features. The HDN entity where the processing unit is further configured to obtain the radio resources to be allocated to the one or more communication devices dynamically from a serving base station via a physical layer control channel. The physical layer control channel is a physical downlink control channel in an example implementation. The processing unit is further configured to obtain the radio resources to be allocated to the one or more communication devices semi-statically through radio resource control signaling from a serving base station. The radio resource control signaling is conducted via layer 3 signaling or access stratum signaling. [0007] In other aspects, the processing unit is further configured to allocate pre-configured or pre-provisioned radio resources to schedule the one or more communication devices. The processing unit is further configured to obtain information from one or more communication devices, where the information may include radio channel state information and user traffic information. The channel state information may include one or more of a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), a layer indicator, a Reference Signal R Power (RSRP), a Reference Signal Received Quality (RSRQ), or a Signal- to-Interference-plus-Noise-Ratio (SINR). The user traffic information may include one or more of an amount, a type, a priority, a delay statistic, and an Age of Information (AoI). [0008] The control channel interface is further configured to transmit a control channel that specifies the allocated radio resources. The allocated radio resources may include time frequency resources, transmit power, and beam configuration. The control channel transmitted by the control channel interface further specifies one or more transmission parameters, where the transmission parameters may include a modulation scheme, an effective coding rate, a packet size, and a precoding. [0009] The HDN entity may be configured to reside on an uncrewed/unmanned aerial vehicle or a drone. The HDN entity provides communication services to the one or more communication devices (e.g., UEs) within a coverage area when residing on the uncrewed/unmanned aerial vehicle or the drone. The HDN entity is configured to be located on or near a roadside unit of a vehicular infrastructure. The HDN entity is configured to provide vehicle-to-everything communication services when located on or near the roadside unit of the vehicular infrastructure. The processing unit is further configured to perform information forwarding or routing functions conventionally performed by a core network. The information for the one or more communication devices scheduled by the HDN entity is directly exchanged with a data network without user traffic traversing the a base station or a core network in some examples. The HDN entity may include a local data network interface configured to connect the HDN entity to a local gateway that provides access to a data network in one example. In another example, the HDN entity connects to the HDN gateway, and the HDN gateway connects via a wired connection to a local gateway that interfaces with a data network. Examples of local gateway include a User Plane Function (UPF) and Packet Data Network Gateway (P-GW), or a Combined Serving-Gateway (S-GW) and P-GW. [0010] One general aspect includes an HDN entity that includes a processing unit configured to perform functions conventionally associated with a user equipment. The HDN entity also includes a power amplifier configured to operate at a power rating higher than the power rating of power amplifiers typically used in smartphones. The power amplifier is configured to utilize power classes associated with higher maximum limits of Effective Isotropic Radiated Power (EIRP) compared to typical smartphone UE power classes. The power amplifier with a higher limit on the EIRP enables the HDN entity to transmit at increased power levels, thereby improving the link performance during communication with a base station and one or more communication devices. [0011] Another general aspect includes a method for managing wireless communication in an HDN entity within a wireless communication system. The method also includes detecting a base station within a coverage area of the HDN entity and determining whether the base station is a new base station. The base station is considered new if the base station is not aware of capability information of the HDN entity. The method also includes transmitting the capability information from the HDN entity to the base station if the base station is determined to be new. The capability information may include details of one or more operational capabilities of the HDN entity. The method also includes receiving configuration data from the base station. The configuration data specifies radio resources and operational parameters for the HDN entity. The method also includes allocating radio resources to one or more communication devices within the coverage area of the HDN entity based on the configuration data. The method also includes scheduling communications for the one or more communication devices using the allocated radio resources. The method may also include conveying a position of the HDN entity from the HDN entity to the base station. [0012] Another general aspect includes a Hybrid Radio and Core (HRC) entity. The HRC entity includes a processing unit configured to perform functions conventionally associated with an integrated or a disaggregated base station equipment and additionally a core network function. The processing unit can reside on a Non-Terrestrial Network (NTN) platform. The HRC entity can also include a logical interface operably coupled to the processing unit. The logical interface is configured to forward packets between two endpoints of a communication link served by one HRC entity or multiple HRC entities. BRIEF DESCRIPTION OF THE DRAWINGS [0013] The detailed description is described with reference to the accompanying figures. Entities represented in the figures are indicative of one or more entities and thus reference is made interchangeably to single or plural forms of the entities in the discussion. [0014] FIG. 1A depicts an architecture of a wireless system incorporating a Hybrid Device and Network (HDN) entity, according to an example implementation. [0015] FIG. 1B depicts an HDN entity mounted on an uncrewed/unmanned aerial vehicle (UAV), according to an example implementation. [0016] FIG. 1C depicts an HDN entity positioned inside or near a roadside unit (RSU), enabling vehicle-to-everything (V2X) communications with vehicles and other RSUs, according to an example implementation. [0017] FIG. 2 depicts a method for implementing a UE-based HDN entity when interacting with a new base station or other network component(s), according to an example implementation. [0018] FIG. 3 depicts a method for implementing a next generation node B (gNB) distributed unit (DU)-based HDN entity, according to an example implementation. [0019] FIG. 4 depicts an architecture of an example wireless system in which aspects of the present disclosure can be implemented. [0020] FIG. 5 depicts an example communication between a communication device and a base station, and an architecture of a disaggregated base station capable of implementing aspects of the present disclosure. [0021] FIG. 6 depicts an architecture of a non-terrestrial network in which aspects of the present disclosure can be implemented. [0022] FIG. 7 depicts an architecture of an HDN entity that is capable of implementing aspects of the present disclosure. DETAILED DESCRIPTION [0023] The present disclosure introduces a Hybrid Device and Network (HDN) entity within a wireless communication system, addressing the need for more efficient and localized data management networks and more spectrally efficient wireless communication in modern networks. Traditional wireless systems typically rely on centralized base stations and core networks to manage user traffic and network functions, which can lead to inefficiencies, especially in scenarios requiring rapid data processing or localized communication. When device-to-device communication, also known as sidelink communication, is used, there could be increased scheduling delay (if the base station allocates radio resources) or inefficient resource utilization (if the device randomly selects radio resources). The HDN entity solves this problem by integrating the functionalities of a User Equipment (UE) with those traditionally handled by the Radio Access Network (RAN) and Core Network (CN). This integration allows the HDN entity to perform tasks such as scheduling other devices and routing data directly to a local data network, bypassing the need for centralized processing. As a result, the HDN entity offers significant advantages over existing solutions, including reduced latency, enhanced coverage, improved data throughput, and greater flexibility in network deployment, particularly in challenging environments such as disaster recovery zones or remote areas. This streamlines network operations and provides a more responsive, efficient, and scalable solution for modern wireless communication systems. [0024] Turning to FIG. 1A, shown is an architecture depicting a wireless system 100A with an HDN entity 102 according to an example implementation. The HDN entity 102 performs various functions typically associated with both a UE and at least one network element, such as scheduling resources for other devices (e.g., other UEs) within its serving area. [0025] The wireless system 100A includes a communication device 104 that communicates with the HDN entity 102 through a radio interface protocol stack 106. The radio interface protocol stack 106 processes communication signals between the communication device 104 and the HDN entity 102, handling tasks such as modulation, channel coding, and scrambling. The HDN entity 102 also interfaces with a protocol stack 108 that manages higher layers of communication, such as packet data convergence and radio resource control, ensuring efficient data transmission and resource management. [0026] To connect with broader network infrastructure, the HDN entity 102 communicates with a base station 110 and a disaggregated base station 112. These base stations are part of a RAN (shown in FIG. 4), which facilitates the transmission of data between the communication devices 104 and a core network 114. The disaggregated base station 112 splits its functions across different hardware units, such as a Central Unit (CU) and a Distributed Unit (DU), increasing scalability and flexibility of deployment. [0027] The core network 114 serves as the backbone of the wireless system 100A, connecting to a data network 116 (such as the Internet or enterprise networks) and enabling broader data exchanges. The HDN entity 102 can also interface directly with a local gateway 118 and an HDN gateway 120. These gateways enable the HDN entity 102 to access to a local data network 122, allowing the HDN entity 102 to manage and route traffic locally without necessarily involving the core network 114. This local data exchange is crucial for applications requiring low latency, such as edge computing or local content delivery networks. [0028] Turning to FIG. 1B, shown is an architecture depicting a wireless system 100B where an HDN entity is mounted on an Uncrewed/Unmanned Aerial Vehicle (UAV) 124 according to an example implementation. This configuration allows the HDN entity 102 to provide wireless coverage and perform network functions from an aerial platform, extending coverage to areas that may be difficult for ground-based stations to reach. [0029] Similar to the wireless system 100A in FIG. 1A, the HDN entity 102 on the UAV 124 interacts with the communication device 104 via the radio interface protocol stack 106. The HDN entity 102 on the UAV 124 also interfaces with a protocol stack 108 to handle higher-layer functions. This setup is particularly beneficial in scenarios requiring temporary or mobile coverage, such as disaster recovery, events, or remote area connectivity. [0030] The HDN entity 102 on the UAV 124 connects to the base station 110 and the disaggregated base station 112 as in FIG. 1A, enabling integration with the terrestrial network infrastructure. The HDN entity 102 on the UAV 124 can also access the local data network 122 through the local gateway 118 and the HDN gateway 120, facilitating low-latency data processing and delivery. This configuration enables the UAV 124 to act as an airborne extension of a network, enhancing coverage and capacity, especially in challenging radio environments or areas beyond the typical cell coverage. [0031] Turning to FIG. 1C, shown is an architecture depicting a wireless system 100C where an HDN entity is positioned inside or near an RSU, enabling V2X communications with vehicles and other RSUs, according to an example implementation. The communication device 104 in this scenario is part of a vehicle 126, which interacts with the HDN entity 102 through the radio interface protocol stack 106. This setup supports V2X communications, enabling the HDN entity 102 to facilitate communications between vehicles, infrastructure, and networks. [0032] The HDN entity 102 communicates with the radio interface protocol stack 106 for managing higher-layer communication functions and integrates with the (integrated) base station 110 and/or a disaggregated base station 112 to ensure seamless connectivity with the wider network infrastructure, including the core network 114 and the data network 116. [0033] The HDN entity 102, located on or near a first RSU 128(1) (RSU₁), which in turn, may or may not be in communication with one or more additional RSUs, such as a second RSU 128(2) (RSU2). The HDN entity 102 accesses the local data network 122 via (i) the local gateway 118 (e.g., a UPF, a P-GW, or a combined S-GW and P-GW) or (ii) and the HDN gateway 120 and the local gateway 118. This configuration supports efficient V2X communication, which is particularly important for safety, traffic management, and autonomous vehicle operations. The HDN entity 102 facilitates the direct exchange of data between vehicles and local networks, optimizing data transfer speed, reducing latency, reducing transport bandwidth requirements for the backhaul, and reducing reliance on the central network infrastructure. [0034] Turning to FIG. 2, shown is a flow diagram depicting a method 200 for implementing a UE-based HDN entity when interacting with a new base station or other network component(s), according to an example implementation. It should be understood that the operations of the methods disclosed herein are not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be added, omitted, and/or performed simultaneously, without departing from the scope of the appended claims. [0035] It also should be understood that the illustrated methods disclosed herein can be ended at any time and need not be performed in their respective (or collective) entireties. Some or all operations of the methods disclosed herein, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer-storage media, as defined herein. The term “computer-readable instructions,” and variants thereof, as used in the description and claims, is used expansively herein to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like. [0036] Thus, it should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. [0037] For purposes of illustrating and describing the concepts and technologies of the present disclosure, the methods disclosed herein are described as being performed generally by one or more network elements, such as the HDN entity 102 or other elements illustrated and described above as part of the wireless systems 100A, 100B, 100C. It should be understood that additional and/or alternative systems, devices, and/or network nodes can provide the functionality described herein via execution of one or more modules, applications, and/or other software including, but not limited to, the module disclosed herein. Thus, the illustrated implementations are illustrative, and should not be viewed as limiting in any way. [0038] The method 200 will be described in context of the HDN entity 102 being a UE- based HDN entity (hereafter, in the description of FIG. 2, UE-based HDN entity 102). The method 200 enables a UE to assume the role of an HDN entity, facilitating enhanced communication capabilities when entering the coverage area of a new base station or otherwise when conditions warrant HDN operation. [0039] The method begins at block 202, where the UE-based HDN entity 102 determines whether it has entered the coverage area of a new base station. In this context, a “new” base station refers to a base station 110 that is not yet aware of the HDN capabilities of the UE-based HDN entity 102. If the UE-based HDN entity 102 is not in a new base station coverage area, the method 200 proceeds to block 204. [0040] At block 204, the method 200 involves assessing whether the UE-based HDN entity 102 should operate as an HDN entity. This decision can be based on several criteria, including whether the base station 110 has configured the UE-based HDN entity 102 to act as an HDN entity, whether the UE-based HDN entity 102 has been provisioned for HDN functionality, or if certain predefined conditions are met, such as the detection of a signal from another UE requiring connectivity. This step directs the subsequent actions the UE-based HDN entity 102 will take. [0041] If it is determined that the UE-based HDN entity 102 should operate as an HDN entity, the method 200 proceeds to block 206, where the UE-based HDN entity 102 evaluates the necessity of assuming the HDN role. If the UE-based HDN entity 102 decides that HDN operation is necessary, the method 200 advances; otherwise, the UE-based HDN entity 102 may reset or delay further evaluation by returning to the beginning of the method 200 after a predetermined period. [0042] Upon entering a new base station coverage area, as determined at block 202, the method proceeds to block 208, where the UE-based HDN entity 102 exchanges its HDN capabilities with the base station 110. This exchange ensures that the base station 110 is fully informed of the enhanced capabilities of the UE-based HDN entity 102, enabling the base station 110 to configure the UE-based HDN entity 102 appropriately for HDN operation. Furthermore, the HDN UE may optionally convey its position to the base station. [0043] Following the capability exchange, block 210 involves the UE-based HDN entity 102 verifying whether it has been configured by the base station 110 to operate as an HDN. This configuration check is used to determine whether the UE-based HDN entity 102 will continue with HDN operations or revert to standard operational mode. If the UE-based HDN entity 102 has been configured for HDN operation, the method 200 proceeds to block 212; otherwise, the method 200 may loop back to block 202 or enter a standby state. [0044] At block 212, the UE-based HDN entity 102 obtains specific HDN-related configurations from the base station 110. These configurations may include parameters such as the cell identifier to be used during HDN operation, as well as the allocation of radio resources that the UE-based HDN entity 102 will manage while acting as an HDN. This step ensures that the UE-based HDN entity 102 is correctly set up to perform its HDN functions within the network. [0045] Once configured, the UE-based HDN entity 102, at block 214, begins transmitting signals and channels as an HDN. This operation supports other UEs within the service area of the UE-based HDN entity 102 by providing essential functions such as synchronization signals and channel condition measurements. These transmissions maintain the overall quality and efficiency of the network. [0046] The method 200 then proceeds to block 216, where the UE-based HDN entity 102 tracks channel state information (CSI) and other relevant measurements. This tracking enables the UE-based HDN entity 102 to optimize its service to connected UEs, ensuring efficient use of resources and maintaining high network performance. [0047] At block 218, the UE-based HDN entity 102 allocates radio resources to UEs within its coverage area. This resource allocation allows for managing how data is transmitted and received, enabling the UE-based HDN entity 102 to facilitate seamless communication between UEs and the network or seamless communication among the UEs that are within the coverage area of the HDN (e.g., when UEs are outside the radio coverage of a base station such as in remote areas or in disaster situations). Furthermore, the HDN UE may report its position to the serving base station periodically or based on an event (e.g., during the initial capability exchange, after traversing a certain distance from the last reported position, and/or after an expiration of a timer). [0048] Following resource allocation, block 220 involves the exchange of user traffic between the UE-based HDN entity 102 and the UE(s) it serves. In this manner, continuous and efficient communication is maintained, allowing UEs to transmit and receive data as needed. Additionally, in support of continuous and efficient communication, a suitable handover is carried out. A handover may result in the change of a serving HDN UE for regular UEs or a change of the serving base station for a given HDN UE. [0049] At block 222, the method 200 includes facilitating the transfer of user traffic between the UE-based HDN entity 102 and either a local or non-local data network. This step involves managing the flow of data across different network segments, ensuring that user traffic is routed and handled efficiently, whether within a localized network or through broader network infrastructure. [0050] Turning to FIG. 3, shown is a flow diagram of a method 300 for activating and operating a gNB-DU-based HDN entity within a wireless communication network, according to an example implementation. The method 300 enables a gNB-DU to assume the role of an HDN entity (hereafter, in FIG. 3, the gNB-DU-based HDN entity 102), enhancing its capabilities to support local data transfer among UEs, gateway-like routing, edge computing, and efficient use of radio resources. [0051] The method begins at block 302, where the gNB-DU-based HDN entity 102 provides its HDN capabilities to the gNB-CU. This exchange of capabilities informs the gNB-CU of the gNB-DU-based HDN entity 102 enhanced functionalities, which may include support for local data transfer and other HDN-specific operations. The gNB-DU-based HDN entity 102 may send an F1 SETUP REQUEST message or a similar signaling message to initiate this exchange. Note that the gNB-DU incorporates some UE functionalities when it is used in the framework of Integrated Access and Backhaul (IAB). For example, an IAB-node has gNB-DU functionalities as well as selected UE functionalities. [0052] At block 304, the gNB-DU-based HDN entity 102 determines whether it needs to operate as an HDN entity. This decision can be based, at least in part, on the configuration or command received from the gNB-CU. If the gNB-CU has instructed the gNB-DU-based HDN entity 102 to act as an HDN entity, or if certain conditions are met (such as detecting signals from UEs looking for service), the gNB-DU-based HDN entity 102 proceeds with HDN operations. If the gNB-DU-based HDN entity 102 decides that HDN operation is not necessary, the method 300 may return to block 302 or enter a standby state. [0053] If the gNB-DU-based HDN entity 102 determines that it should act as an HDN entity, the method 300 proceeds to block 306, where the gNB-DU-based HDN entity 102 obtains the necessary HDN-related configuration from the gNB-CU. This configuration may include parameters such as the specific radio resources the gNB-DU-based HDN entity 102 should manage, as well as any relevant cell IDs or synchronization information required for HDN operation. [0054] With the configuration in place, at block 308, the gNB-DU-based HDN entity 102 transmits signals and channels as an HDN. These transmissions are used for supporting UEs within the HDN’s service area, providing synchronization signals, broadcast channels, and other necessary communications that enable UEs to connect and maintain service quality. [0055] At block 310, the gNB-DU-based HDN entity 102 tracks CSI and other relevant measurements. This tracking allows the gNB-DU-based HDN entity 102 to optimize its service, ensuring that the radio resources are used effectively and that the network performance remains high. The gNB-DU-based HDN entity 102 monitors these metrics continuously to adjust its operations as needed. [0056] At block 312, where the gNB-DU-based HDN entity 102 allocates and conveys radio resources to the UEs within its coverage area. This allocation is used for managing the communication channels used by the UEs, ensuring that data transmission and reception are handled efficiently. [0057] Following resource allocation, at block 314, the gNB-DU-based HDN entity 102 exchanges user traffic with the UEs. In this manner, the HDN functionality facilitates seamless communication between the UEs and the broader network infrastructure. [0058] At block 316, the method 300 includes facilitating user traffic transfer with a local or non-local data network. The gNB-DU HDN entity 102 manages the flow of data between the UE and the network, whether it involves local data exchange or routing information to a more centralized network location through the gNB-CU. While a traditional approach relies on the gNB-DU-to-gNB-CU connectivity for data transfer involving the data network (e.g., the Internet), the example implementation approach in this disclosure allows data transfer between the UE and the local or non-local data network without the packets passing through the gNB-CU. We further note that a gNB-DU or a gNB in a Non-Terrestrial Network (NTN) may behave like an HDN UE such that the gNB-DU or the gNB on the NTN platform implements its normal gNB-DU-like or gNB-like functions and supports an additional function of a core network. Such entity can be viewed as a hybrid radio and core (HRC) entity. In one example implementation of the HRC entity, the HRC entity implements the gNB functions and a core network function of local routing or packet forwarding by behaving like a gateway. Specifically, the gNB on an NTN platform may perform (i) regular gNB functions and (ii) an additional packet forwarding or packet routing function of a gateway (e.g., UPF, P-GW, or combined S-GW and P-GW) to reduce latency of data transfer for the UEs serviced by the gNB or gNB-DU residing on an NTN platform. In another example implementation of the HRC entity, the HRC entity implements the gNB functions and a core network function of edge computing. Specifically, the gNB on an NTN platform may perform (i) regular gNB functions and (ii) an additional edge computing function of an edge computing server to reduce the application layer latency of data transfer for the UEs serviced by the gNB or gNB-DU residing on an NTN platform. See FIG.6 for the example architecture of an NTN. [0059] Block 318 addresses the scenario where there may be a change in the serving gNB- CU. If a change in the gNB-CU occurs, the gNB-DU HDN entity 102 re-evaluates its need to act as an HDN, potentially restarting the method 300 by exchanging capabilities with the new gNB-CU. If there is no change, the gNB-DU HDN entity 102 continues its HDN operations as configured. [0060] Turning to FIG. 4, shown is a generic architecture of a wireless system 400. The wireless system 400 includes the communication device 104, a RAN 402, the core network 114, the data network 116, a management network 404, and a services network 408. The communication device 104 communicates with the base station(s) 110 of the RAN 402 using a radio interface, such as provided by the radio interface protocol stack 106. The communication device 104, as mentioned above, can be a UE, and examples of UEs include smartphones, smartwatches, Internet of Things (IoT) devices, or communication modules within systems such as self-driving cars or Augmented Reality (AR)/Virtual Reality (VR) headsets. [0061] The RAN 402 can include multiple base stations 110. The base stations 110 can communicate with each other via a transport network (shown as lines connected the base stations 110), depending on the generation of the wireless technology. For example, fourth generation (4G) Long Term Evolution (LTE) technology and fifth generation (5G) technology utilize interfaces like X2 and Xn for inter-BS communications, respectively. The base stations 110 may be referred to as an evolved Node B (eNodeB or eNB) in LTE and a next-generation Node B (gNB) in 5G. The RAN 402 can include auxiliary equipment 410, such as battery backup to supply the base station 110 with power, a cell site router (CSR) to connect the base station 110 with other network parts like the core network 114 and the management network 404, and remote electrical tilt equipment to adjust the tilt of the base station antennas. The base station 110 communicates with the communication device 104 using a technology-specific radio interface protocol stack (such as the radio interface protocol stack 106). [0062] The core network 114 can include various network elements and/or network functions (NFs). For example, a 4G LTE core network, known as the Evolved Packet Core (EPC), can include network elements such as a Mobility Management Entity (MME), a Home Subscriber Server (HSS), a Serving Gateway (S-GW), and a Packet Data Network Gateway (P- GW). A 5G core network, known as the Next Generation Core (NGC) or the 5G Core (5GC), includes NFs such as an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), and a User Plane Function (UPF). The MME and AMF maintain a Non-Access Stratum (NAS) signaling connection with the communication device 104 to exchange 4G/5G-specific signaling messages. The MME and AMF also manage UE mobility when the UE is in idle mode by tracking its geographic location, often referred to as a Tracking Area (TA), to send a page message to the UE when needed. The HSS/UDM creates authentication credentials for the UE to facilitate its authentication by the network. The P-GW/SMF assigns an IP address to the UE. The P-GW/UPF interfaces with the data network 116, such as the Internet or an enterprise network. [0063] The services network 408 provides operator-specific services. The IP Multimedia Subsystem (IMS) is an example of the services network 408. Both 4G and 5G networks can provide voice services using IMS. [0064] The management network 404 manages the RAN 402 and the core network 114. An Operations, Administration, and Maintenance (OAM) system is an example of the management network 404. The management network 404 can configure the base stations 110 and the NFs of the core network 114, for example. [0065] Turning to FIG. 5, shown is an example communication between a communication device and a base station, and an architecture of a disaggregated base station capable of implementing aspects of the present disclosure. The communication device 104 and the base station 110 communicate using the radio interface protocol stack 106. For example, a UE and an eNB communicate via an LTE-based radio interface protocol stack on the LTE-Uu radio interface. Similarly, a UE and a gNB communicate via a New Radio (NR)-based radio interface protocol stack on the NR-Uu radio interface. Both the LTE radio interface protocol stack and the 5G NR radio interface protocol stack have a physical (PHY) layer as Layer 1 protocol, Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) as Layer 2 protocols, and Radio Resource Control (RRC) as a Layer 3 protocol. 5G NR introduces a protocol called Service Data Adaptation Protocol (SDAP) compared to LTE. [0066] The PHY layer involves processes such as channel coding, modulation, scrambling, de-scrambling, demodulation, and decoding. The MAC layer/protocol at the base station 110 implements a scheduler to allocate radio resources to the communication device 104. The MAC layer also influences operations such as a random access procedure. The MAC layer works with the PHY layer to implement Hybrid Automatic Repeat Request (H-ARQ) procedures that carry out fast retransmissions to minimize redundancy and maximize throughput. The RLC layer/protocol carries out retransmissions when the lower layers cannot recover packet errors. The PDCP layer/protocol performs header compression and supports security mechanisms such as ciphering (i.e., encryption) and integrity protection. [0067] A base station 110 may be implemented in various ways. The base station 110 may be monolithic, with tightly coupled custom hardware and custom (often proprietary) software. Alternatively, the base station 110 may be disaggregated, as shown as the disaggregated base station 112. For example, in the disaggregated base station 112, one part, shown as base station part 1500(1), may implement the lower layers/protocols of the radio protocol stack, and another part, shown as base station part 2500(2) may implement the upper layers/protocols of the radio protocol stack. [0068] In one example architecture of the disaggregated base station 112, the base station part 1500(1) implements all Layer 3 and Layer 2 protocols and the baseband portion of the PHY layer, while the base station part 2 500(2) implements the Radio Frequency (RF) processing portion of the PHY layer. The base station part 2500(2) may be referred to as a Remote Radio Head (RRH) or Remote Radio Unit (RRU). A Centralized RAN (C-RAN) centralizes multiple base station parts 1 of multiple base stations at a relatively central location to derive cost and efficiency benefits. [0069] In another example architecture of a disaggregated base station 112, a base station part 1 500(1) implements the upper layers/protocols of the radio protocol stack such as RRC, SDAP, and PDCP, while a base station part 2500(2)implements the lower layers/protocols of the radio protocol stack such as RLC, MAC, and PHY. In this architecture, the base station part 1 500(1) may be referred to as a gNB-Central Unit (gNB-CU) and the base station part 2500(2) may be referred to as a gNB-Distributed Unit (gNB-DU) for a disaggregated gNB in 5G NR. In practice, the base station part 2 500(2) may be further divided into a baseband processing unit and an RF processing unit. [0070] Turning to FIG. 6, shown is a Non-Terrestrial Network (NTN) 600 including an NTN platform 602 and an NTN gateway 604, among other components described above. Examples of the NTN platform 602 include a satellite and a High-Altitude Platform Station (HAPS). Example satellites include Low Earth Orbit (LEO), Medium Earth Orbit (MEO), and Geostationary Earth Orbit (GEO) satellites. A satellite may be capable of generating one or more types of beams: Earth-fixed, Earth-moving, and quasi-Earth-fixed. An Earth-fixed beam covers a fixed geographic area on the Earth's surface continuously. An Earth-moving beam covers one geographic area at one instant and a different geographic area at another instant. A quasi-Earth-fixed beam covers one geographic area during one period and a different geographic area during another period. [0071] There are two main types of payloads: transparent and regenerative. A transparent payload means that the entire base station equipment is on the ground, and the NTN platform acts as a relay or a repeater. The transfer of user traffic for these types of payloads is briefly described below. [0072] For the network-to-UE user traffic transfer in the case of a transparent payload, the user traffic flows from the data network 116 to the core network 114. The core network 114 forwards the user traffic to the base station1 110(1), which constructs a technology-specific signal such as an LTE or NR signal for 4G and 5G, respectively. This technology-specific signal is sent to the NTN gateway 604 that forwards the signal to the NTN platform 602 using the radio interface protocol stack2106(2) on a feeder link. The NTN platform 602 performs tasks such as frequency conversion and power amplification and sends the signal to the communication device 104 on a service link or access link. [0073] For the UE-to-network user traffic transfer in the case of a transparent payload, the user traffic goes from the communication device 104 to the NTN platform 602 using the radio interface protocol stack₁ 106(1) on the service/access link. The NTN platform 602 performs tasks such as frequency conversion and power amplification and sends the signal to the NTN gateway 604. The NTN gateway 604 forwards the signal to the base station₁110(1). Finally, the base station₁110(1) forwards the user traffic to the data network 116 via the core network 114. [0074] For a regenerative payload, two scenarios may exist. In one scenario, the entire base station is on the NTN platform 602. In another scenario, the base station part 1500(1) is on the NTN platform 602, and base station part 2500(2) is on the ground. [0075] Consider the network-to-UE user traffic transfer in the case of a regenerative payload with the entire base station on the NTN platform 602. The user traffic flows from the data network 116 to the core network 114. The core network 114 forwards the user traffic to the NTN gateway 604 via a dedicated connection. The NTN gateway 604 forwards the user traffic to the NTN platform 602 using the radio interface protocol stack2106(2) on the feeder link. The base station₂110(2) on the NTN platform 602 performs technology-specific processing. The NTN platform 602 performs tasks such as power amplification and sends the user traffic to the communication device 104 on the service link or access link. [0076] Consider the UE-to-network user traffic transfer in the case of a regenerative payload with the entire base station on the NTN platform 602. The user traffic goes from the communication device 104 to the NTN platform 602 using the radio interface protocol stack 106(1) on the service/access link. The NTN platform 602 sends the signal received from the communication device 104 to the base station2 110(2). The base station2 110(2) performs technology-specific processing. The NTN platform 602 sends the signal via the feeder link to the NTN gateway 604, which forwards the signal to the core network 114 via the dedicated connection. The core network 114 forwards the user traffic to the data network 116. [0077] Consider the network-to-UE user traffic transfer in the case of a regenerative payload with the base station part 1500(1) on the NTN platform 602 and the base station part 2500(2) on the ground. The user traffic flows from the data network 116 to the core network 114. The core network 114 forwards the user traffic to the base station part 2 500(2), which performs technology-specific processing and conveys the user traffic to the NTN gateway 604. The NTN gateway 604 forwards the user traffic to the NTN platform 602 using the radio interface protocol stack2 106(2) on the feeder link. The base station part 1 500(1) performs technology-specific processing. The NTN platform 602 performs tasks such as power amplification and sends the user traffic to the communication device 104 on the service link or access link. [0078] Consider the UE-to-network user traffic transfer in the case of a regenerative payload with base station part 1500(1) on the NTN platform 602 and the base station part 2500(2) on the ground. The user traffic goes from the communication device 104 to the NTN platform 602 using the radio interface protocol stack₁ 106(1) on the service/access link. The NTN platform 602 sends the signal received from the communication device 104 to the base station part 1 500(1). The base station part 1 500(1) performs technology-specific processing. The NTN platform 602 sends the signal via the feeder link to the NTN gateway 604, which forwards the signal to the base station part 2 500(2). The base station part 2 500(2) performs technology- specific processing and sends the user traffic to the core network 114. The core network 114 forwards the user traffic to the data network 116. [0079] Turning to FIG. 7, shown is an architecture 700 of the HDN entity 102, according to an example implementation. The architecture 700 includes various components that enable the HDN entity 102 to perform its multifunctional roles within a wireless network. The HDN entity 102 includes a processing unit 702, which serves as the central component responsible for executing the various functions of the HDN entity 102, including scheduling tasks traditionally managed by a base station and processing edge computing tasks. [0080] Connected to the processing unit 702 is memory 704, which stores software and configuration data used operations performed by the HDN entity 102, including, for example, the radio resource allocation algorithms and application-specific data for edge computing tasks. The HDN entity 102 is also equipped with a power amplifier 706 that allows the HDN entity 102 to transmit signals with higher power compared to typical UE, thus improving communication reliability and range. [0081] The HDN entity 102 includes multiple interfaces for interaction with other network components and UEs. A radio interface 708 manages communication with base stations (e.g., the base station 110 and/or the disaggregated base station 112) and other UEs (e.g., the communication devices 104) using the enhanced capabilities of the HDN entity 102. Additionally, a control channel interface 710 is responsible for transmitting and receiving control signals, such as those used for scheduling and resource allocation. [0082] To support its role in edge computing, the HDN entity 102 also includes dedicated edge computing software 712, which processes data locally, allowing for quick decision-making without relying on the core network 114. The HDN entity 102 also includes a power management system 714 that efficiently manages the power supply to the power amplifier 706 and other components, ensuring that the HDN entity 102 operates within its power constraints while maintaining optimal performance. [0083] The HDN entity 102 integrates a local data network interface 716, which facilitates direct communication with local or edge data networks, enabling faster data transfer and reducing latency by bypassing the core network 114 as needed. The architecture 700 enables the HDN entity 102 to effectively function as both a UE and a network entity, providing enhanced communication services and support to other devices within its coverage area. [0084] It should be understood that many variations are possible based on the disclosure herein. Although features and elements are described above in particular combinations, each feature or element is usable alone without the other features and elements or in various combinations with or without other features and elements. [0085] The embodiments can be embodied or implemented in hardware, software, or a combination of hardware and software. If implemented in hardware, the embodiments can include at least one processing circuit, with at least one storage or memory device. The at least one processing circuit can include, for example, one or more processors and one or more storage or memory devices coupled to a local interface. The local interface can include, for example, a data bus with an accompanying address/control bus or any other suitable bus structure. The storage or memory device can store data or components that are executable by the processors of the processing circuit. [0086] In another example, if implemented in hardware, the embodiments can include as a circuit or state machine that employs any suitable hardware technology. The hardware technology can include, for example, one or more microprocessors, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits (ASICs) having appropriate logic gates, and/or programmable logic devices (e.g., field-programmable gate array (FPGAs), and complex programmable logic devices (CPLDs)). [0087] If implemented in software, each step or element can represent a module or group of code that includes program instructions to implement the specified logical function(s). The program instructions can be embodied in the form of, for example, source code that includes human-readable statements written in a programming language or machine code that includes machine instructions recognizable by a suitable execution system, such as a processor in a computer system or other system. [0088] Also, one or more of the components described herein that include software or program instructions can be embodied in any non-transitory computer-readable medium for use by or in connection with an instruction execution system such as, a processor in a computer system or other system. The computer-readable medium can contain, store, and/or maintain the software or program instructions for use by or in connection with the instruction execution system. [0089] A computer-readable medium can include a physical media, such as magnetic, optical, semiconductor, and/or other suitable media. Examples of a suitable computer-readable media include, but are not limited to, solid-state drives, magnetic drives, or flash memory. Further, any logic or component described herein can be implemented and structured in a variety of ways. For example, one or more components described can be implemented as modules or components of a single application. Further, one or more components described herein can be executed in one computing device or by using multiple computing devices. [0090] Further, any logic or applications described herein can be implemented and structured in a variety of ways. For example, one or more applications described can be implemented as modules or components of a single application. Further, one or more applications described herein can be executed in shared or separate computing devices or a combination thereof. For example, a plurality of the applications described herein can execute in the same computing device, or in multiple computing devices. Additionally, terms such as “application,” “service,” “system,” “engine,” “module,” and so on can be used interchangeably and are not intended to be limiting.

Claims

CLAIMS 1. A Hybrid Device and Network (HDN) entity, comprising: a processing unit configured to perform functions conventionally associated with a user equipment and to execute scheduling functions conventionally associated with a base station, wherein the scheduling functions comprise allocating radio resources to one or more communication devices within a target coverage area of the HDN entity; and a control channel interface operably coupled to the processing unit, wherein the control channel interface is configured to transmit and receive control information used for managing the allocated radio resources for the one or more communication devices.

2. The HDN entity of claim 1, wherein the processing unit is further configured to obtain the radio resources to be allocated to the one or more communication devices dynamically from a serving base station via a physical layer control channel.

3. The HDN entity of claim 2, wherein the physical layer control channel is a physical downlink control channel.

4. The HDN entity of claim 1, wherein the processing unit is further configured to obtain the radio resources to be allocated to the one or more communication devices semi- statically through radio resource control signaling from a serving base station.

5. The HDN entity of claim 4, wherein the radio resource control signaling is conducted via layer 3 signaling or access stratum signaling.

6. The HDN entity of claim 1, wherein the processing unit is further configured to allocate pre-configured or pre-provisioned radio resources to schedule the one or more communication devices.

7. The HDN entity of claim 1, wherein the processing unit is further configured to obtain information from the one or more communication devices, the information comprising channel state information and user traffic information.

8. The HDN entity of claim 7, wherein the channel state information comprises one or more of a channel quality indicator, a precoding matrix indicator, a rank indicator, a layer indicator, a reference signal received power, a reference signal received quality, or a signal-to- interference-plus-noise-ratio.

9. The HDN entity of claim 7, wherein the user traffic information comprises one or more an amount, a type, a priority, a delay statistic, and an age of information.

10. The HDN entity of claim 1, wherein the control channel interface is further configured to transmit a control channel that specifies the allocated radio resources, the allocated radio resources comprising one or more of time frequency resources, transmit power, or beam configuration.

11. The HDN entity of claim 10, wherein the control channel transmitted by the control channel interface further specifies one or more transmission parameters, the transmission parameters comprising a modulation scheme, an effective coding rate, a packet size, and a precoding.

12. The HDN entity of claim 1, wherein the HDN entity is configured to reside on an uncrewed/unmanned aerial vehicle or a drone.

13. The HDN entity of claim 12, wherein the HDN entity provides communication services to the one or more communication devices within a coverage area when residing on the uncrewed/unmanned aerial vehicle or the drone.

14. The HDN entity of claim 1, wherein the HDN entity is configured to be located on or near a roadside unit of a vehicular infrastructure.

15. The HDN entity of claim 14, wherein the HDN entity is configured to provide vehicle-to-everything communication services when located on or near the roadside unit of the vehicular infrastructure.

16. The HDN entity of claim 1, wherein the processing unit is further configured to perform information forwarding or routing functions conventionally performed by a core network, wherein the information for the one or more communication devices scheduled by the HDN entity is directly exchanged with a data network without user traffic traversing the base station or a centralized core network.

17. The HDN entity of claim 16, further comprising a local data network interface configured to connect the HDN entity to a local gateway that provides access to a data network.

18. The HDN entity of claim 16, further comprising a radio interface configured to connect the HDN entity to an HDN gateway via a wireless connection, wherein the HDN gateway connects via a wired connection to a local gateway that interfaces with a data network.

19. A Hybrid Device and Network (HDN) entity, comprising: a processing unit configured to perform functions conventionally associated with a user equipment; and a power amplifier configured to operate at a power rating higher than the power rating of power amplifiers typically used in smartphones, the power amplifier being configured to utilize power classes associated with higher maximum limits of effective isotropic radiated power, wherein the power amplifier enables the HDN entity to transmit at increased power levels, thereby improving the link performance during communication with a base station and one or more communication devices.

20. A method for managing wireless communication in a Hybrid Device and Network (HDN) entity within a wireless communication system, the method comprising: detecting a base station within a coverage area of the HDN entity; determining whether the base station is a new base station, wherein the base station is considered new if the base station is not aware of capability information of the HDN entity; transmitting the capability information from the HDN entity to the base station if the base station is determined to be new, the capability information comprising details of one or more operational capabilities of the HDN entity; receiving configuration data from the base station, the configuration data specifying radio resources and operational parameters for the HDN entity; allocating radio resources to one or more communication devices within the coverage area of the HDN entity based on the configuration data; and scheduling communications for the one or more communication devices using the allocated radio resources.

21. The method of claim 20, further comprising conveying a position of the HDN entity from the HDN entity to the base station.

22. A Hybrid Radio and Core (HRC) entity, comprising: a processing unit configured to perform functions conventionally associated with an integrated or a disaggregated base station equipment and additionally a core network function, wherein the processing unit resides on a Non-Terrestrial Network (NTN) platform; and a logical interface operably coupled to the processing unit, wherein the logical interface is configured to forward packets between two endpoints of a communication link served by one HRC entity or multiple HRC entities.

23. The HRC entity of claim 22, wherein the HRC entity is configured to perform a core network function of packet forwarding and routing.

24. The HRC entity of claim 22, wherein the HRC entity is configured to perform a core network function of edge computing.