Reduced latency scheduling request process

By associating the scheduling request resources with the data size, the scheduling request delay in the wireless communication network is reduced, and the problem of large round-trip delay in non-terrestrial networks is solved, and communication efficiency and user experience are improved.

CN119054392APending Publication Date: 2024-11-29QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034928.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-28
Filing Date
2023-04-26
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

The delay of scheduling requests in wireless communication networks is long, resulting in a decrease in network efficiency and user experience, especially in non-terrestrial network environments, which affects data transmission performance.

Method used

By associating a specific scheduling request resource with a specific buffered data size range, the scheduling requests equipped by the user can identify the required uplink resource size, thereby reducing traditional multiple round-trip communications and transmitting data directly to the network.

Benefits of technology

It reduces the delay of the scheduling process, improves the communication speed and network efficiency between user equipment and the network, and is suitable for traditional high-delay communication systems and delay-sensitive services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054392A_ABST
    Figure CN119054392A_ABST
Patent Text Reader

Abstract

Certain aspects of the present disclosure provide a method of wireless communication by a user equipment, the method comprising: determining an amount of data to be communicated to a network entity; selecting a resource for transmitting the scheduling request based on the data amount; and transmitting a scheduling request to the network entity using the selected resource.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Indian Provisional Patent Application No. 202221024980 filed on April 28, 2022, which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference in its entirety as if fully set forth below and for all applicable purposes. Background Art Technical Field

[0003] Aspects of the present disclosure relate to wireless communications, and more particularly to techniques for reducing latency of scheduling requests in wireless communication networks.

[0004] Related technical description

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with the multiple users.

[0006] Although wireless communication systems have made tremendous technological advances over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continuous desire to improve the technical performance of wireless communication systems, including, for example: increasing the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0007] One aspect provides a method of wireless communications by a user equipment, the method comprising: determining an amount of data to be transmitted to a network entity; selecting resources for transmitting a scheduling request based on the amount of data; and transmitting the scheduling request to the network entity using the selected resources.

[0008] On the other hand, a method for wireless communication by a network entity is provided, the method comprising: receiving a scheduling request using a preconfigured resource, wherein the preconfigured resource is one preconfigured resource of multiple preconfigured resources, and each corresponding preconfigured resource of the multiple preconfigured resources is associated with a corresponding amount of data for uplink transmission; and transmitting an uplink grant, wherein the uplink grant indicates one or more uplink resources for transmitting the amount of data associated with the preconfigured resources to the network entity.

[0009] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform the aforementioned method and those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the aforementioned method and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, the computer-readable storage medium comprising code for performing the aforementioned method and those described elsewhere herein; and an apparatus comprising means for performing the aforementioned method and those described elsewhere herein. For example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0010] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings depict certain features of the various aspects described herein and should not be considered to limit the scope of the disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example disaggregated base station architecture is depicted.

[0014] Figure 3 Aspects of an example base station and example user equipment are depicted.

[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0016] Figure 5 An example of a non-ground surface is depicted.

[0017] Fig. 6A and Figure 6B Depicted is an example architecture for a non-terrestrial network.

[0018] Figure 7 A process flow for communicating in a network between user equipment and a network entity is depicted.

[0019] Fig. 8A Another process flow for communicating in a network between user equipment and a network entity is depicted.

[0020] Figure 8B Depicts an example table of scheduling request resources.

[0021] Fig. 9 A method for wireless communication is described.

[0022] Fig.10 A method for wireless communication is described.

[0023] Fig.11 Aspects of an example communications device are depicted.

[0024] Fig.12 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0025] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for reducing latency of scheduling requests in a wireless communication network.

[0026] Generally speaking, before a user equipment sends data, it is transferred to a buffer to wait for scheduling and transmission. When data arrives at a transmit buffer (e.g., an L2 buffer) of the user equipment, the user equipment may not yet have uplink resources scheduled by the wireless communication network to transmit the buffered data. Therefore, the user equipment may transmit a scheduling request to the network, such as with respect to Figure 1 Those described, request resources for sending the buffered data.

[0027] In general, a scheduling request acts as a basic indication that the user equipment requires uplink resources from the network, but the network is generally unable to determine the extent of the resources required by the user equipment based on the received scheduling request. Therefore, the network will generally schedule a first uplink resource grant for the user equipment that is just large enough for the user equipment to transmit a buffer status report indicating the status of its transmit buffer. Upon receiving the buffer status report from the user equipment, the network may then schedule a second uplink resource grant with sufficient resources to transmit the data buffered by the user equipment and waiting to be sent. Upon receiving the grant, the user equipment may schedule and then send the buffered data. Figure 7 An example of this process is depicted and described in more detail below. Notably, this scheduling process requires two transmissions and receptions (eg, "round trips") between the user equipment and the network before the user equipment can initiate transmission of the buffered data.

[0028] In terrestrial networks, despite multiple scheduled data round trips due to the proximity of the user equipment to a network entity (such as a base station), the foregoing process can have sufficiently low latency in most scenarios. For example, the average round trip delay in a terrestrial network can be on the order of 2 milliseconds (ms) per round trip, or 4 ms overall for the foregoing process. However, for non-terrestrial networks where the user equipment and the network entity may be separated by a greater distance, the round trip delay may increase by several orders of magnitude.

[0029] For example, a non-terrestrial network using satellite-based network entities (e.g., base stations) may have a round trip time of about 500ms for a geosynchronous satellite, which means that there may be a total delay of about 1000ms for the aforementioned scheduling process. For another example, for low-orbit earth satellites, the round trip time may be between 8ms and 25ms depending on the orbit, which is still more than four times the round trip time on the ground (in the best case). Such delays may cause significant performance issues in the transmission of data between user equipment and the network, thereby reducing network efficiency and user experience.

[0030] Various aspects described herein overcome this technical problem by associating a specific scheduling request resource with a specific buffered data size range (at the user equipment) so that a first scheduling request transmitted by the user equipment to the network can not only identify the user equipment's need for uplink resources, but also identify an indication of the size of the required grant.

[0031] As a simple example, a first configured scheduling request resource may be associated with an amount of data in a transmit buffer of a user equipment that is below a first threshold. A second configured scheduling request resource may be associated with an amount of data in a transmit buffer of the user equipment that is between a first threshold and a second threshold. A third configured scheduling request resource may be associated with an amount of data in a transmit buffer of the user equipment that is greater than a second threshold. Fig. 8A and Figure 8B An example of this improved method is depicted and will be described in more detail below.Thus, by sending a scheduling request using a selected scheduling request resource associated with a particular transmit data buffer status, the user equipment informs the network of both its need for uplink resources and the relative size of that need, and advantageously omits the need to transmit a buffer status report or other secondary transmission indicating the size of its intended transmission.

[0032] Compared to the conventional method for scheduling uplink resources described above, the reduction of the second round trip time halves the latency of the scheduling process. Thus, by reducing the overhead associated with the conventional need to schedule multiple round trips for uplink data, the communication speed between the user equipment and the network is increased and the efficiency of the network is improved.

[0033] The method described in this article for reducing the latency of the resource scheduling process is beneficial not only for traditional high-latency communication systems (such as non-terrestrial networks), but also for delay-sensitive communication services used in terrestrial networks (such as ultra-reliable low-latency communication (URLLC) services).

[0034] Introduction to wireless communication networks

[0035] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0036] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0037] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device. For example, various functions of a network and various devices associated with and interacting with the network can be considered network entities.

[0038] In the depicted example, the wireless communication network 100 includes a base station (BS) 102, a user equipment (UE) 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190), which interoperate to provide communication services over various communication links (including wired and wireless links). In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 102), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground BSs) and user equipment.

[0039] Figure 1Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, etc.

[0040] BS 102 communicates wirelessly with UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0041] BS 102 may generally include: Node B, enhanced Node B (eNB), next generation enhanced Node B (ng-eNB), next generation Node B (gNB or gNodeB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission and reception point, etc. Each BS in BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and may overlap in some cases (e.g., small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, the BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (relatively small geographic area (e.g., a home)), and / or other types of cells.

[0042] Although BS102 is depicted as a single communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few examples. As another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS102) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functionality similar to that of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0043] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0044] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 600 MHz-6 GHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 26 GHz-41 GHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS180) configured to communicate using mmWave / near mmWave radio bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0045] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0046] Communications using higher frequency bands may have higher path loss and shorter range than lower frequency communications. Therefore, some base stations (e.g. Figure 1 180) may utilize beamforming 182 with UE 104 to improve path loss and range. For example, BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also send beamformed signals to base station 180 in one or more transmit directions 182". BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. Base station 180 and UE 104 may then perform beam training to determine the best receive direction and the best transmit direction for each of BS 180 and UE 104. It is noteworthy that the transmit direction and receive direction of BS 180 may be the same or different. Similarly, the transmit direction and receive direction of UE 104 may be the same or different.

[0047] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi station (STA) 152 via communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0048] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).

[0049] The EPC 160 may include various functional components, including, in the depicted example: a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0050] Generally speaking, user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0051] The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0052] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0053] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0054] Internet Protocol (IP) packets are delivered through UPF 195, which is connected to IP Services 197 and provides IP address allocation for UEs and other functions for 5GC 190. IP Services 197 may include, for example, the Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0055] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0056] Figure 2 An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0057] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals or both to one or more of the other units via a wireless transmission medium.

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

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

[0060] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RU 240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0061] The SMO framework 205 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

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

[0063] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0064] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0065] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0066] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 362) and wireless reception of data (e.g., data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0067] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0068] The transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS)).

[0069] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in the transceiver 332a-332t. Each modulator in the transceiver 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0070] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0071] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0072] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0073] At BS 102, uplink signals from UE 104 may be received by antennas 334 a-334 t, processed by demodulators in transceivers 332 a-332 t, detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340.

[0074] Memory 342 and memory 382 may store data and program codes for BS 102 and UE 104, respectively.

[0075] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0076] In various aspects, BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from antennas 334a-334t, transceivers 332a-332t, an RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and other aspects described herein.

[0077] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and other aspects described herein.

[0078] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0079] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0080] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0081] Wireless communication networks can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single Carrier Frequency Division Multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D The modulation symbols may be transmitted in the frequency domain using OFDM and in the time domain using SC-FDM.

[0082] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the subcarrier set are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the subcarrier set are dedicated to both DL and UL.

[0083] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X is used flexibly between DL / UL. The UE can be configured with the slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot configuration. The subframe may also include a microslot, which typically has fewer symbols than the entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0084] In general, the number of slots within a subframe is based on the slot configuration and parameter set. For slot configuration 0, different parameter sets (μ) 0 to 5 allow each subframe to have 1, 2, 4, 8, 16, and 32 slots, respectively. For slot configuration 1, different parameter sets 0 to 2 allow each subframe to have 2, 4, and 8 slots, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, while parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0085] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted in , a resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0086] like Figure 4A As illustrated, some of the REs carry data for the UE (eg, Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0087] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in an OFDM symbol.

[0088] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0089] A Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0090] Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent through the PBCH, and paging messages.

[0091] like Figure 4CAs illustrated, some of the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are also possible). The UE may send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. UE104 may also send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0092] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0093] Introduction to non-terrestrial networks

[0094] In some cases, wireless communication networks (such as Figure 1 Communications in the wireless communication network 100 illustrated in FIG. 1 may be facilitated by one or more non-terrestrial devices. In such cases, the wireless communication network may be referred to as a non-terrestrial network (NTN). Non-terrestrial devices may include, for example, space satellites (e.g., Figure 1 satellite 140), balloons, spacecraft, aircraft (e.g., Figure 1 Equipment such as aircraft 145), drones, unmanned aerial vehicles, etc.

[0095] Figure 5 An example of a non-terrestrial network 500 including a satellite 140 in which aspects of the present disclosure may be practiced is depicted. In some examples, the non-terrestrial network 500 may implement aspects of the wireless communication system 100. For example, the non-terrestrial network 500 may include a BS 102, a UE 104, and a satellite 140. In the case of a terrestrial network, the BS 102 may serve a coverage area or cell 110, while in the case of a non-terrestrial network, the satellite 140 may serve a coverage area or cell 110. Some non-terrestrial networks may employ airborne platforms (e.g., drones or balloons) and / or spaceborne platforms (e.g., satellites).

[0096] As part of wireless communications in non-terrestrial network 500, satellite 140 may communicate with BS 102 and UE 104. In the case of a terrestrial network, UE 104 may communicate with BS 102 and UE 104 via a communication link (e.g., Figure 1 In the case of non-terrestrial network wireless communication, satellite 140 may be via communication link 520 (e.g., Figure 1 In some aspects, the satellite 140 may act as a relay for the BS 102 and the UE 104, relaying both data transmission and control signaling 515.

[0097] UE 104 may determine to connect to satellite 140 using a random access (RA) procedure (e.g., a four-step RA procedure or a two-step RA procedure). The initiation of the RA procedure may begin with the UE 104 sending a RA preamble (e.g., an NR preamble of the RA) to satellite 140 or BS 102. UE 104 may send the RA preamble on a physical random access channel (PRACH). In some PRACH designs, the RTD or frequency shift associated with non-terrestrial networks may not be estimated or accounted for. In certain networks such as terrestrial NR networks (e.g., 5G NR), SSBs sent by cells are sent on the same frequency interval (e.g., occupying the same frequency interval). In non-terrestrial networks 500, satellites may use multiple antennas to form multiple narrow beams, and the beams may operate on different frequency intervals to mitigate interference between beams.

[0098] In some cases, there may be different architectures for non-terrestrial networks, such as a transparent satellite-based non-terrestrial network architecture and a regenerative satellite-based non-terrestrial network architecture. An example of a transparent satellite-based non-terrestrial network architecture is shown in Fig. 6A , while an example of a non-terrestrial network architecture based on regenerative satellites is shown in Figure 6B In some cases, Fig. 6A and Figure 6B The non-terrestrial network architecture shown in Figure 5 The non-terrestrial network 500 shown in FIG.

[0099] Generally speaking, non-terrestrial network architectures based on transparent satellites (e.g., also known as bent-pipe satellite architectures, such as Fig. 6A ) involves satellite 140 receiving a signal from BS 102 through non-terrestrial network gateway 608 and relaying the signal to UE 104 in this example (or to another BS 102 in another example). In a non-terrestrial network architecture based on a regenerative satellite (such as Figure 6B), satellite 140 may be configured to relay signals like a bent pipe architecture, but may also use onboard processing to perform other functions, such as demodulating received signals, decoding received signals, re-encoding signals to be transmitted, or modulating signals to be transmitted, or a combination thereof.

[0100] For example, Fig. 6A As shown, in the transparent satellite-based non-terrestrial network architecture 600A, the communication between the data network 602 and the UE 104 may begin by transmitting data from the data network 602 to a user plane function (UPF) in the core network 191 via a communication link 604, such as Figure 1 195 in the 5GC 190 illustrated in FIG. In some cases, the communication link 604 between the data network 602 and the UPF in the core network 191 may be implemented using an N6 interface. The data may then be forwarded from the core network 191 to the BS 102 via a communication link 606, which in some aspects may be an NG interface. The data may then be transmitted to the UE 104 by the BS 102 via a non-terrestrial network gateway 608 and a satellite 140 over another interface (such as a Uu interface). For example, the non-terrestrial network gateway 608 may receive data from the BS 102 and may forward the data to the satellite 140 over a feeder link via a satellite radio interface (SRI). In some examples, the SRI on the feeder link is a Uu interface. The satellite 140 may then perform radio frequency filtering, frequency conversion, and amplification on the received data before relaying the data to the UE 104 over a service link 612 (e.g., via a Uu interface). Thus, the satellite 140 in the transparent satellite-based non-terrestrial network architecture 600A simply repeats data over the Uu radio interface from the feeder link 610 (between the non-terrestrial network gateway 608 and the satellite 140) to the service link 612 (e.g., between the satellite 140 and the UE 104), and vice versa. In other words, the data is not altered by the satellite 140 and is simply relayed to the UE 104.

[0101] exist Figure 6B In the regenerative satellite-based non-terrestrial network architecture 600B illustrated in FIG. 1 , data from the data network 602 may be transmitted directly from the core network 191 to the satellite 140 via the non-terrestrial network gateway 608 without first being processed by the BS 102 (e.g., in FIG. 1 ). Fig. 6A6). For example, the non-terrestrial network gateway 608 may transmit data to the satellite 140 over a feeder link 610 implementing SRI. After receiving the data, the satellite 140 may perform radio frequency filtering, frequency conversion and amplification, as well as demodulation / decoding, switching and / or routing, and coding / modulation. In other words, the satellite 140 may implement the functionality of a BS (e.g., BS 102) onboard the satellite 140. The satellite 140 then sends the data to the UE 104 over, for example, a Uu radio interface via a service link 612 between the UE 104 and the satellite 140.

[0102] Aspects related to the scheduling request process to reduce latency

[0103] Various aspects described herein provide a scheduling request resource that is configured to indicate a data transmission need of a sender device, such as a user equipment. Advantageously, such a scheduling request allows the network to determine (e.g., relatively or absolutely) the amount of data that the sender device wishes to send to the network without having to perform additional communications dedicated to determining the amount of data. Instead, the use of a particular resource serves as both an indication of the need to send data and an indication of the amount of data intended to be sent.

[0104] Advantageously, the various aspects described herein increase the communication speed between a sender device (e.g., user equipment) and a receiver device (e.g., a network entity), while also reducing communication overhead, and thereby improving network efficiency and utilization. The various aspects described herein are beneficial for any wireless communication network, including traditional high-latency communication systems (such as non-terrestrial networks) and delay-sensitive communication services for terrestrial networks (such as ultra-reliable low-latency communication (URLLC) services).

[0105] Figure 7 An example flow 700 of a conventional scheduling process is depicted in which a user equipment 104 (eg, through a network entity 102) requests resources from a network in order to send data to the network.

[0106] The process 700 begins at step 702, where the user equipment 104 transmits a scheduling request to the network entity 102. As described above, this first (or initial) scheduling request serves as a basic indication that the user equipment 104 requires uplink resources from the network.

[0107] Since the amount of uplink transmission resources required by the user equipment 104 cannot be determined based on the scheduling request received at step 702 (e.g., via the network entity 102), the network transmits a first uplink resource grant to the user equipment 104 via the network entity 102 at step 704, the first uplink resource grant being sufficient for the user equipment to transmit a buffer status report to the network.

[0108] The user equipment then transmits a buffer status report indicating the status of its transmit buffer to the network entity 102 using the first uplink grant.

[0109] When the buffer status report is received from the user equipment at step 706 (e.g., via the network entity 102), the network may then schedule a second uplink resource grant with sufficient resources for the user equipment 104 to transmit the data that is buffered and waiting to be sent (as indicated in the buffer status report). At step 708, the network entity 102 transmits the second uplink resource grant to the user equipment 104.

[0110] After receiving the second uplink resource grant, at step 708, the user equipment 104 transmits the buffered data using the granted uplink resources.

[0111] like Figure 7 As depicted in , the conventional scheduling process requires two transmissions and receptions between the user equipment 104 and the network entity 102, and therefore two communication round trips (steps 702 and 704, followed by steps 706 and 708) before the user equipment 104 is able to send its buffered data at step 710.

[0112] Fig. 8A A process flow 800 is depicted for communicating in a network between a network entity 102 and a user equipment 104 to reduce latency in a scheduling request. In some aspects, the network entity 102 may be relative to Figure 1 and Figure 3 An example of a base station 102 is depicted and described. Similarly, user equipment 104 may be an example of a base station 102. Figure 1 and Figure 3 An example of a user equipment 104 is depicted and described. However, in other aspects, the user equipment 104 may be another type of wireless communication device, and the network entity 102 may be another type of network entity or network node, such as those described herein.

[0113] Flow 800 begins at step 802, where the user equipment 104 determines its transmit buffer state. In one example, the user equipment 104 may determine the current state of one or more transmit buffers, such as the amount of data currently stored in the one or more transmit buffers. However, the current determination of the buffer state may not reflect the amount of data that will be buffered when the user equipment is able to actually send data. Therefore, in another example, the user equipment 104 may determine the expected or target state of one or more transmit buffers at some future point in time.

[0114] For example, the user equipment 104 may determine the type and / or distance of the network entity based on system information broadcast (SIB) parameters. In the case of a non-terrestrial network entity, the type may be "satellite" (e.g., Figure 5 140 in geosynchronous orbit), and the distance may be based on the orbital altitude (e.g., 22,236 miles for a satellite in geosynchronous orbit). Based on this information, user equipment 104 may calculate an approximate round-trip time for the communication (e.g., approximately 540 ms for a satellite in geosynchronous orbit). In conjunction with this determination, the user equipment may estimate the time it takes to reach the destination in a round trip (e.g., Fig. 8A 804 and step 806 in ). In some cases, the application layer of the user equipment 104 may estimate the expected data accumulation.

[0115] For example, in the case of a voice call, the user equipment may determine that 30 byte packets will be generated every 20 ms, and therefore for a round trip time of 540 ms, the user equipment 104 will subsequently accumulate approximately 810 bytes in one or more transmit buffers.

[0116] Flow 800 then proceeds to step 804, where the user equipment 104 transmits a scheduling request to the network entity 102 using a scheduling request (SR) resource, which indicates to the network the amount of data that the user equipment 104 intends to transmit. For example, the scheduling request resource may be Figure 8B Any resource from resources 1-3 in the example.

[0117] Generally speaking, the indication of the amount of data may be a relative indication, such as a data range (e.g., from x bytes to y bytes) or a specific indication (e.g., z bytes). Figure 8B A simple example is depicted in which scheduling request resources 1-3 (in column 808) are each configured to indicate an amount of data in a buffer of the user equipment, as indicated in column 810. Based on receiving any of the configured scheduling request resources, the network may then allocate uplink resources based on the indicated amount of data, as indicated in column 812.

[0118] Specifically, in Figure 8B In the example of , the first configured scheduling request resource (in row 1 of the table) indicates that the amount of data in the transmit buffer of the user equipment 104 is below a first threshold, which in this example is referred to as a "low threshold". Therefore, when receiving the first configured scheduling request resource (e.g., SRR_1), the network may allocate an uplink grant sized according to a data threshold, which in this example is a "small grant size". In one example, the small grant size may be equal to or less than the low threshold (e.g., in bits, bytes, etc.).

[0119] The second configured scheduling request resource (in row 2 of the table) indicates that the amount of data in the transmit buffer of the user equipment 104 is between the first threshold and the second threshold, which in this example is referred to as the "high threshold". Therefore, when receiving the second configured scheduling request resource (e.g., SRR_2), the network may allocate an uplink grant sized according to the data threshold, which in this example is the "medium grant size". In one example, the medium grant size may be equal to or greater than the low threshold and less than the high threshold.

[0120] The third configured scheduling request resource (in row 3 of the table) indicates that the amount of data in the transmit buffer of the user equipment 104 is greater than the second threshold. Therefore, when receiving the second configured scheduling request resource (e.g., SRR_3), the network may allocate an uplink grant sized according to the data threshold, which in this example is a "large grant size". In one example, the large grant size may be equal to or greater than the high threshold.

[0121] More generally, the network may define and configure any number of grant sizes associated with any number of scheduling request resources. Figure 8B The example table in may have any number of rows and associated thresholds or other definitions (eg, relative versus specific indications of buffer size).

[0122] In some aspects, the network (e.g., via the network entity 102) may dynamically use predefined scheduling request resources (such as in Figure 8B In the example of ), the user equipment (e.g., 104) is configured. In other aspects, the user equipment 104 may include a pre-configured set of predefined scheduling resources. In some cases, the network may dynamically overwrite or update the pre-configured set of predefined scheduling request resources.

[0123] Then, flow 800 proceeds to step 806 where the network entity 102 transmits an uplink grant to the user equipment 104 based on the scheduling request resource received from the user equipment 104 in step 804 .

[0124] Finally, the flow proceeds to step 808 , where the user equipment 104 transmits data to the network entity 102 using the uplink resources granted at step 806 .

[0125] and Figure 7 Compared to the example in Fig. 8AIn the example, there is only one communication round trip (step 804 and step 806) before the user equipment 104 can send data, which therefore reduces the latency of the communication and reduces the overhead of the communication, thereby improving the network efficiency of the communication as described above. In addition, since the user equipment 104 needs to make fewer communications, this reduces power usage and extends battery life when the user equipment 104 is a mobile device. Similarly, in the case where the network entity 102 is a non-terrestrial network entity such as a satellite, the overall power budget for the communication can be reduced by eliminating unnecessary round trip communications.

[0126] Example Operation of User Equipment

[0127] Fig. 9 The method for use by a UE such as Figure 1 and Figure 3 Method 900 for performing wireless communications with a UE 104).

[0128] Method 900 begins at step 902, where an amount of data to be transmitted to a network entity is determined.

[0129] In some aspects, determining the amount of data to be transmitted to the network entity comprises determining the amount of data stored in a data buffer within the user equipment. In some aspects, the data buffer comprises a layer 2 (L2) transmit buffer.

[0130] In some aspects, determining the amount of data to be transmitted to the network entity includes determining an estimated amount of data stored in the data buffer after a scheduling request interval. In some aspects, the scheduling request interval includes a first time interval associated with transmitting a scheduling request to the network entity and a second time interval associated with receiving an uplink grant from the network entity.

[0131] Method 900 then proceeds to step 904, where a resource for transmitting the scheduling request is selected based on the amount of data.

[0132] In some aspects, selecting the resource for transmitting the scheduling request based on the amount of data includes selecting the resource from a plurality of preconfigured resources, and each respective preconfigured resource of the plurality of preconfigured resources is associated with a respective data amount range.

[0133] Method 900 then proceeds to step 906 where a scheduling request is transmitted to a network entity using the selected resources.

[0134] In some aspects, method 900 further includes receiving an uplink grant from the network entity, the uplink grant indicating one or more uplink resources for transmitting the amount of data to the network entity.

[0135] In some aspects, method 900 further includes transmitting the amount of data to the network entity using one or more uplink resources indicated by the uplink grant.

[0136] In some aspects, method 900 further comprises receiving, from a network entity, a configuration indicating a plurality of pre-configured resources. In some aspects, the configuration is received via radio resource control (RRC) signaling.

[0137] In some aspects, method 900 also includes receiving a system information block message from a network entity; estimating a distance between the network entity and the user equipment based on the system information block message; and estimating the first time interval and the second time interval based on the estimated distance between the network entity and the user equipment.

[0138] In some aspects, method 900 also includes selecting a resource for transmitting the scheduling request further based on the type of network entity. In some aspects, the network entity includes a non-terrestrial network entity, such as a satellite, an aircraft, etc. In some aspects, the network entity includes a terrestrial network entity, such as a fixed installation base station. In some aspects, the network entity includes a terrestrial mobile network entity, such as a mobile base station (or aspects of a base station).

[0139] In some aspects, method 900 further comprises determining the type of the network entity based on a system information block (SIB) message received from the network entity.

[0140] In some aspects, method 900 further comprises selecting the resource for transmitting the scheduling request further based on a type of data service between the user equipment and the network entity. In some aspects, the data service comprises an ultra-reliable low latency communication service.

[0141] In one aspect, method 900 or any aspect related thereto may be performed by an apparatus such as Fig.11 The method 900 is performed by a communication device 1100, which includes various components that are operable, configured or adapted to perform the method 900. The device 1100 is described in more detail below.

[0142] It should be noted that Fig. 9 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0143] Example Operations of Network Entities

[0144] Fig.10 shows a method for use by a network entity such as Figure 1 and Figure 3 BS102 or as relative to Figure 2 A method 1000 for wireless communications performed by a decomposed base station) as discussed.

[0145] Method 1000 begins at step 1002, where a scheduling request is received (e.g., from a user equipment) using a preconfigured resource. In some aspects, the preconfigured resource is one of a plurality of preconfigured resources, each respective preconfigured resource of the plurality of preconfigured resources being associated with a respective amount of data for uplink transmission. In some aspects, each respective amount of data is associated with a range of amounts of data, such as relative to a range of amounts of data. Figure 8B As described in the examples.

[0146] Method 1000 then proceeds to step 1004, where an uplink grant is transmitted (e.g., to a user equipment). In some aspects, the uplink grant indicates one or more uplink resources for transmitting an amount of data associated with the preconfigured resources to a network entity. For example, as relative to Figure 8B As described, pre-configured resources (such as SR resources 1-3) may indicate an amount of data that the user equipment has (or is expected to have) buffered and waiting to be transmitted to the network entity.

[0147] In some aspects, method 1000 also includes receiving the amount of data using one or more uplink resources indicated by the uplink grant. For example, the amount of data may be received from the user equipment, such as in Fig. 8A In the example.

[0148] In some aspects, method 1000 also includes transmitting a configuration indicating a plurality of pre-configured resources. In some aspects, the configuration is transmitted via radio resource control (RRC) signaling. For example, the configuration can be transmitted to a user equipment.

[0149] In some aspects, method 1000 further comprises transmitting (e.g., to a user equipment) a system information block message, wherein the system information block message indicates an attribute of a network entity. In some aspects, the attribute is a distance from the network entity to the user equipment. In some aspects, the attribute is a type of the network entity. In some aspects, the network entity comprises a non-terrestrial network entity, such as a satellite, an aircraft, etc. In some aspects, the network entity comprises a terrestrial network entity, such as a fixed-install base station. In some aspects, the network entity comprises a terrestrial mobile network entity, such as a mobile base station (or aspects of a base station). The method of claim 19, wherein the network entity receives the data volume via an ultra-reliable low-latency communication service.

[0150] In one aspect, method 1000 or any aspect related thereto may be performed by an apparatus such as Fig.12 The method 1000 is performed by a communication device 1200 that includes various components that are operable to, configured to, or adapted to perform the method 1000. The device 1200 is described in more detail below.

[0151] It should be noted that Fig.10 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0152] Example Communication Device

[0153] Fig.11 Depicted are aspects of an example communication device 1100. In some examples, the communication device 1100 is user equipment, such as described above with respect to Figure 1 and Figure 3 UE 104 is described.

[0154] The communication device 1100 includes a processing system 1102 coupled to a transceiver 1108 (e.g., a transmitter and / or a receiver). The transceiver 1108 is configured to transmit and receive signals for the communication device 1100, such as the various signals described herein, via an antenna 1110. The processing system 1102 may be configured to perform processing functions for the communication device 1100, including processing signals received by the communication device 1100 and / or to be transmitted by the communication device.

[0155] The processing system 1102 includes one or more processors 1120. In various aspects, the one or more processors 1120 may represent Figure 3 One or more of the receive processor 358, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380 described herein. The one or more processors 1120 are coupled to the computer-readable medium / memory 1130 via the bus 1106. In some aspects, the computer-readable medium / memory 1130 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1120, cause the one or more processors 1120 to perform operations with respect to Fig. 9 The method 900 described herein or any aspect related thereto. It should be noted that reference to a processor performing a function of the communication device 1100 may include one or more processors performing that function of the communication device 1100.

[0156] In the depicted example, computer readable medium / memory 1130 stores code (e.g., executable instructions) for determining 1131, code for selecting 1132, code for transmitting 1133, code for receiving 1134, and code for estimating 1135. Processing of codes 1131-1135 may cause communication device 1100 to perform operations relative to Fig. 9 The described method 900 or any aspect related thereto.

[0157] The one or more processors 1120 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1130, including circuits for determining 1121, circuits for selecting 1122, circuits for transmitting 1123, circuits for receiving 1124, and circuits for estimating 1125. Processing performed by circuits 1121-1125 may enable the communication device 1100 to perform operations relative to Fig. 9 The described method 900 or any aspect related thereto.

[0158] The various components of the communication device 1100 may provide for performing Fig. 9 Means for sending, transmitting, or outputting for sending may include: Figure 3 The transceiver 354 and / or antenna 352 and / or Fig.11 The transceiver 1108 and antenna 1110 of the communication device 1100 in FIG. 1 may include Figure 3 The transceiver 354 and / or antenna 352 and / or Fig.11 The transceiver 1108 and antenna 1110 of the communication device 1100.

[0159] Fig.12 Aspects of an example communications device are depicted.

[0160] The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208 (e.g., a transmitter and / or a receiver) and / or a network interface 1212. The transceiver 1208 is configured to transmit and receive signals for the communication device 1200 via an antenna 1210, such as the various signals described herein. The network interface 1212 is configured to transmit and receive signals for the communication device 1200 via a communication link (such as the various signals described herein). Figure 2 The processing system 1202 may be configured to obtain and transmit signals for the communication device 1200 using the backhaul link, midhaul link, and / or fronthaul link described herein. The processing system 1202 may be configured to perform processing functions of the communication device 1200, including processing signals received by the communication device 1200 and / or to be transmitted by the communication device.

[0161] The processing system 1202 includes one or more processors 1220. In various aspects, the one or more processors 1220 may represent Figure 3One or more of the receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340 described herein. The one or more processors 1220 are coupled to the computer-readable medium / memory 1230 via the bus 1206. In some aspects, the computer-readable medium / memory 1230 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1220, cause the one or more processors 1220 to perform operations with respect to Fig.10 The method 1000 described herein or any aspect related thereto. It should be noted that reference to a processor of the communication device 1200 performing a function may include one or more processors of the communication device 1200 performing the function.

[0162] In the depicted example, the computer readable medium / memory 1230 stores code (e.g., executable instructions) for receiving 1231, code for transmitting 1232, and code for configuring 1233. Processing of the codes 1231-1233 may cause the communication device 1200 to perform operations relative to Fig.10 The method 1000 described herein or any aspect related thereto.

[0163] The one or more processors 1220 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1230, including circuits for receiving 1221, circuits for transmitting 1222, and circuits for configuring 1223. Processing performed by circuits 1221-1223 may cause the communication device 1200 to perform operations such as those described above with respect to Fig.10 The described method 1000 or any aspect related thereto.

[0164] The various components of the communication device 1200 may be provided for performing Fig.10 Means for sending, transmitting, or outputting for sending may include: Figure 3 The transceiver 332 and / or antenna 334 and / or Fig.12 The transceiver 1208 and antenna 1210 of the communication device 1200 in FIG. 1 may include Figure 3 The transceiver 332 and / or antenna 334 and / or Fig.12 The transceiver 1208 and antenna 1210 of the communication device 1200 in FIG.

[0165] Sample Clauses

[0166] Specific implementation examples are described in the following numbered clauses:

[0167] Clause 1: A method of wireless communication by a user equipment, the method comprising: determining an amount of data to be transmitted to a network entity; selecting resources for transmitting a scheduling request based on the amount of data; and transmitting the scheduling request to the network entity using the selected resources.

[0168] Clause 2: The method of clause 1, further comprising: receiving an uplink grant from the network entity, the uplink grant indicating one or more uplink resources for transmitting the amount of data to the network entity.

[0169] Clause 3: The method of clause 2, further comprising transmitting the amount of data to the network entity using the one or more uplink resources indicated by the uplink grant.

[0170] Clause 4: A method according to any one of clauses 1 to 3, wherein: selecting the resource for transmitting the scheduling request based on the data volume includes selecting the resource from a plurality of preconfigured resources, and each respective preconfigured resource in the plurality of preconfigured resources is associated with a respective data volume range.

[0171] Clause 5: The method of clause 4, further comprising: receiving a configuration indicative of the plurality of pre-configured resources from the network entity.

[0172] Clause 6: A method as described in clause 5, wherein the configuration is received via radio resource control (RRC) signaling.

[0173] Clause 7: A method as described in any of clauses 1 to 6, wherein determining the amount of data to be transmitted to a network entity comprises determining the amount of data stored in a data buffer within the user equipment.

[0174] Clause 8: The method of clause 7, wherein the data buffer comprises an L2 transmit buffer.

[0175] Clause 9: A method as described in any of clauses 1 to 8, wherein determining the amount of data to be transmitted to the network entity comprises determining an estimated amount of data stored in a data buffer after a scheduling request interval.

[0176] Clause 10: The method of clause 9, wherein the scheduling request interval comprises a first time interval associated with transmitting the scheduling request to the network entity and a second time interval associated with receiving an uplink grant from the network entity.

[0177] Clause 11: The method according to Clause 10 further includes: receiving a system information block message from the network entity; estimating the distance between the network entity and the user equipment based on the system information block message; and estimating the first time interval and the second time interval based on the estimated distance between the network entity and the user equipment.

[0178] Clause 12: The method of any of clauses 1 to 11, further comprising: selecting the resource for transmitting the scheduling request further based on a type of the network entity.

[0179] Clause 13: The method of clause 12, further comprising determining the type of the network entity based on a system information block (SIB) message received from the network entity.

[0180] Clause 14: The method of clause 12, wherein the network entity comprises a non-terrestrial network entity.

[0181] Clause 15: The method of clause 14, wherein the non-terrestrial network entity comprises a satellite.

[0182] Clause 16: A method as recited in any of clauses 1 to 15, further comprising selecting the resource for transmitting the scheduling request further based on a type of data service between the user equipment and the network entity.

[0183] Clause 17: The method of clause 16, wherein the data service comprises an ultra-reliable low-latency communication service.

[0184] Clause 18: A method of wireless communication by a network entity, the method comprising: receiving a scheduling request using a preconfigured resource, wherein the preconfigured resource is one of a plurality of preconfigured resources, each respective preconfigured resource of the plurality of preconfigured resources being associated with a respective amount of data for uplink transmission; and transmitting an uplink grant, wherein the uplink grant indicates one or more uplink resources for transmitting the amount of data associated with the preconfigured resources to the network entity.

[0185] Clause 19: The method of clause 18, further comprising: receiving the amount of data from the user equipment using the one or more uplink resources indicated by the uplink grant.

[0186] Clause 20: A method as recited in any one of clauses 18 to 19, further comprising transmitting to the user equipment a configuration indicative of the plurality of pre-configured resources.

[0187] Clause 21: A method as set forth in clause 20, wherein the configuration is transmitted via radio resource control (RRC) signaling.

[0188] Clause 22: A method as described in any of clauses 18 to 21, further comprising transmitting a system information block message to the user equipment, wherein the system information block message indicates a property of the network entity.

[0189] Clause 23: The method of clause 22, wherein the attribute is a distance from the network entity to a user equipment.

[0190] Clause 24: The method of clause 22, wherein the attribute is a type of the network entity.

[0191] Clause 25: A method as described in any of clauses 18 to 24, wherein the network entity comprises a non-terrestrial network entity.

[0192] Clause 26: The method of clause 25, wherein the non-terrestrial network entity comprises a satellite.

[0193] Clause 27: A method as described in any of clauses 19 to 26, wherein the network entity receives the amount of data via an ultra-reliable low-latency communication service.

[0194] Clause 28: A method according to any one of clauses 18 to 27, wherein each respective data volume is associated with a data volume range.

[0195] Clause 29: An apparatus, the apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method of any one of clauses 1 to 28.

[0196] Clause 30: An apparatus comprising means for performing the method of any one of clauses 1 to 28.

[0197] Clause 31: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 28.

[0198] Clause 32: A computer program product embodied on a computer readable storage medium, the computer readable storage medium comprising code for performing the method according to any of clauses 1 to 28.

[0199] Additional considerations

[0200] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may omit, replace or add various processes or components as appropriate. For example, the described methods may be performed in a different order than the described order, and various actions may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality or structures and functionality other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0201] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0202] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0203] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, etc. In addition, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determining" may include resolving, selecting, choosing, establishing, etc.

[0204] The method disclosed herein includes one or more actions for implementing the method. The method actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. In addition, the various operations of the method described above can be performed by any suitable component that can perform the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0205] The following claims are not intended to be limited to the various aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless explicitly stated, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.SC § 112 (f) unless the element is explicitly stated using the phrase "member for...". All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly stated in the claims, anything disclosed herein is not intended to be disclosed to the public.

Claims

1. A method for wireless communication by a user equipment, the method comprising: determining an amount of data to be transmitted to a network entity; selecting a resource for transmitting the scheduling request based on the amount of data; as well as A scheduling request is transmitted to the network entity using the selected resources.

2. The method according to claim 1, further comprising: An uplink grant is received from the network entity, the uplink grant indicating one or more uplink resources for transmitting the amount of data to the network entity.

3. The method according to claim 2, further comprising: The amount of data is transmitted to the network entity using the one or more uplink resources indicated by the uplink grant.

4. The method according to claim 1, wherein: selecting the resource for transmitting the scheduling request based on the amount of data comprises selecting the resource from a plurality of preconfigured resources, and Each respective preconfigured resource of the plurality of preconfigured resources is associated with a respective data volume range.

5. The method according to claim 4, further comprising: A configuration indicative of the plurality of preconfigured resources is received from the network entity. The method of claim 5 , wherein the configuration is received via radio resource control (RRC) signaling.

7. The method of claim 1, wherein determining the amount of data to be transmitted to a network entity comprises determining the amount of data stored in a data buffer within the user equipment. The method of claim 7 , wherein the data buffer comprises an L2 transmit buffer.

9. The method of claim 1, wherein determining the amount of data to be transmitted to a network entity comprises determining an estimated amount of data stored in a data buffer after a scheduling request interval.

10. The method of claim 9, wherein the scheduling request interval comprises a first time interval associated with transmitting the scheduling request to the network entity and a second time interval associated with receiving an uplink grant from the network entity.

11. The method according to claim 10, further comprising: receiving a system information block message from the network entity; estimating a distance between the network entity and the user equipment based on the system information block message; as well as The first time interval and the second time interval are estimated based on an estimated distance of the network entity from the user equipment.

12. The method according to claim 1, further comprising: The resource for transmitting the scheduling request is selected further based on a type of the network entity.

13. The method according to claim 12, further comprising: The type of the network entity is determined based on a system information block (SIB) message received from the network entity.

14. The method of claim 12, wherein the network entity comprises a non-terrestrial network entity.

15. The method of claim 14, wherein the non-terrestrial network entity comprises a satellite.

16. The method according to claim 1, further comprising: The resource for transmitting the scheduling request is selected further based on a type of data service between the user equipment and the network entity.

17. The method of claim 16, wherein the data service comprises an ultra-reliable low-latency communication service.

18. A user equipment configured for wireless communication, the user equipment comprising: a memory including computer executable instructions; and a processor configured to execute the computer executable instructions and cause the user equipment to: determining an amount of data to be transmitted to a network entity; selecting a resource for transmitting the scheduling request based on the amount of data; as well as A scheduling request is transmitted to the network entity using the selected resources.

19. A method for wireless communication by a network entity, the method comprising: receiving a scheduling request using a preconfigured resource, wherein the preconfigured resource is one preconfigured resource of a plurality of preconfigured resources, each respective preconfigured resource of the plurality of preconfigured resources being associated with a respective amount of data for uplink transmission; as well as An uplink grant is transmitted, wherein the uplink grant indicates one or more uplink resources for transmitting an amount of data associated with the preconfigured resources to the network entity.

20. The method according to claim 19, further comprising: The amount of data is received using the one or more uplink resources indicated by the uplink grant.

21. The method according to claim 19, further comprising: A configuration indicative of the plurality of pre-configured resources is transmitted.

22. The method of claim 21, wherein the configuration is transmitted via radio resource control (RRC) signaling.

23. The method according to claim 19, further comprising: Transmits system information block messages, The system information block message indicates the attribute of the network entity.

24. The method of claim 23, wherein the attribute is a distance from the network entity to a user equipment.

25. The method of claim 23, wherein the attribute is a type of the network entity.

26. The method of claim 19, wherein the network entity comprises a non-terrestrial network entity.

27. The method of claim 26, wherein the non-terrestrial network entity comprises a satellite.

28. The method of claim 20, wherein the network entity receives the amount of data via an ultra-reliable low-latency communication service.

29. The method of claim 19, wherein each respective data volume is associated with a data volume range.

30. A network entity configured for wireless communication, the network entity comprising: a memory including computer executable instructions; and a processor configured to execute the computer executable instructions and cause the network entity to: receiving a scheduling request using a preconfigured resource, wherein the preconfigured resource is one preconfigured resource of a plurality of preconfigured resources, each respective preconfigured resource of the plurality of preconfigured resources being associated with a respective amount of data for uplink transmission; as well as An uplink grant is transmitted, wherein the uplink grant indicates one or more uplink resources for transmitting an amount of data associated with the preconfigured resources to the network entity.