User equipment (ue) supplemental bsr for reducing latency in high propagation delay networks

Abstract

This disclosure relates to techniques for reducing latency in high propagation delay wireless communication systems. A user equipment device (UE) can transmit a first buffer status report (BSR) to a base station (BS), the first BSR indicating an amount of uplink data buffered by the UE for transmission to the BS, and can subsequently transmit a first BSR update message to the BS, the first BSR update message indicating an additional amount of uplink data that the UE has buffered since transmitting the first BSR. The first BSR update message can be transmitted before expiration of a timer that authorizes transmission of a second BSR after the first BSR. The UE can receive an uplink grant from the BS, the uplink grant allocating resources for transmission of at least a portion of the uplink data buffered by the UE. The uplink grant can have a size based on the first BSR and the first BSR update message.

Description

Technical Field

[0001] This application relates to wireless communication, and more specifically to systems, apparatus, and methods for reducing delay in high propagation delay wireless communication systems.

[0002] Related technical descriptions

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment or UE) now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex applications that utilize these capabilities. Furthermore, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A (LTE-Advanced), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and BLUETOOTH. TM wait.

[0004] The introduction of an ever-growing number of features and functionalities into wireless communication devices necessitates continuous improvements to both wireless communication and the devices themselves. In particular, the integration of various network technologies with more traditional cellular network technologies can lead to new network characteristics. For example, introducing new categories of cellular base stations or repeater stations may introduce significantly larger and more variable propagation delays than those associated with more traditional base stations. These characteristics can degrade the user experience in such networks. Therefore, improvements are expected in this area. Summary of the Invention

[0005] This article provides implementation schemes for apparatus, systems, and methods for reducing latency in high propagation delay wireless communication systems.

[0006] According to the technology described herein, a wireless device can be configured to transmit a first buffer status report (BSR) to a base station, the first BSR indicating the amount of uplink data buffered by the wireless device for transmission to the base station. The wireless device can also transmit a first BSR update message to the base station, the first BSR update message indicating that, after transmitting the first BSR, the wireless device has buffered an additional amount of uplink data for transmission to the base station. The first BSR update message can be transmitted after transmitting the first BSR and before the timer for granting transmission of a second BSR following the first BSR expires. The wireless device can receive an uplink grant from the base station in response to the first BSR and the first BSR update message, the uplink grant allocating resources for transmission of at least a portion of the uplink data buffered by the wireless device. The uplink grant can have a size based on the first BSR and the first BSR update message.

[0007] In some scenarios, after the timer for authorizing the transmission of the second BSR expires, the wireless device may use the allocated resources to transmit uplink data and the second BSR to the base station, the second BSR indicating the amount of remaining uplink data to be transmitted to the base station.

[0008] In some scenarios, the wireless device can receive configuration information related to the BSR update message from the base station. The transmission of the first BSR update message can be based on the received configuration information.

[0009] In some scenarios, the configuration information can be received in one or more of the System Information Block (SIB), Radio Resource Control (RRC) Connection Establishment Message, RRC Reconfiguration Message, or RRC Recovery Message.

[0010] In some scenarios, the wireless device can provide the base station with a service type indication that identifies the type of uplink data service to be transmitted to the base station, wherein the configuration information is based on the service type indication.

[0011] In some scenarios, this configuration information can define how frequently the wireless device can transmit BSR update messages.

[0012] In some scenarios, the wireless device may transmit a second BSR update message to the base station, the second BSR update message indicating that the wireless device has buffered an additional amount of uplink data for transmission to the base station after transmitting the first BSR update message. The second BSR update message may be transmitted after transmitting the first BSR update message and before the timer for granting the transmission of the second BSR after the first BSR expires. The uplink grant may further respond to the second BSR update message, and the uplink grant may have a further size based on the second BSR update message.

[0013] Devices (such as baseband processors) and methods having features similar to those outlined above are also disclosed.

[0014] It should be noted that the technologies described herein can be implemented in and / or used in several different types of devices, including but not limited to base stations, access points, mobile phones, portable media players, tablets, wearable devices, unmanned aerial vehicles, unmanned flight controllers, automobiles and / or motor vehicles, and various other computing devices.

[0015] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0016] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0017] Figure 1 An exemplary (and simplified) wireless communication system according to some implementation schemes is shown.

[0018] Figure 2 An exemplary base station communicating with an exemplary wireless user equipment (UE) device according to some implementation schemes is shown.

[0019] Figure 3 An exemplary block diagram of a UE according to some implementation schemes is shown.

[0020] Figure 4 An exemplary block diagram of a base station according to some implementation schemes is shown.

[0021] Figure 5 This is a communication flowchart illustrating an example of a typical UL business call flow.

[0022] Figure 6 This is a communication flowchart illustrating an example of a UL service call flow according to some implementation schemes, where the 4-step RA process has been modified to reduce the delay between the initial authorization request and the reception of uplink data UL authorization.

[0023] Figure 7 This is a communication flowchart illustrating an example of a UL business call flow according to some implementation schemes, where the 4-step RA process has been modified to provide additional initial UL authorization.

[0024] Figure 8 This is a communication flow diagram illustrating an example of a UL service call flow including a BSR update message according to some implementation schemes.

[0025] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0026] acronym

[0027] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:

[0028] ·BS: Base Station

[0029] • BSR: Buffer Status Report

[0030] • CQI: Channel Quality Indicator

[0031] • CSI: Channel State Information

[0032] • CSI-RS: Channel State Information Reference Signal

[0033] DL: Downlink

[0034] GSM: Global System for Mobile Communications

[0035] ·IE: Information Elements

[0036] ·LI: Layer Indicator

[0037] LTE: Long Term Evolution

[0038] • MCS: Modulation and Coding Scheme

[0039] NR: New Radio

[0040] • PDSCH: Physical Downlink Shared Channel

[0041] • PMI: Precoding Matrix Indicator

[0042] • PRACH: Physical Random Access Channel

[0043] RACH: Random Access Channel

[0044] • RAT: Radio Access Technology

[0045] RF: Radio Frequency

[0046] ·RI: Rank Indicator

[0047] ·RO: RACH timing

[0048] • RSRP: Reference Signal Received Power

[0049] ·RX: Receive

[0050] • SINR: Signal-to-Interference-plus-Noise Ratio

[0051] •SR: Scheduling Request

[0052] •SSB: Synchronization Signal Block

[0053] TX: Transmission

[0054] UE: User Equipment

[0055] ·UL: Uplink

[0056] UMTS: Universal Mobile Telecommunications System

[0057] the term

[0058] The following is a glossary of terms that will appear in this disclosure:

[0059] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In a later example, the second computer system may provide program instructions to the first computer system for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0060] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0061] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. Generally, the term "computer system" can be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.

[0062] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Telephones), tablet computers (e.g., iPads) TM Samsung Galaxy TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TMThis includes wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily transportable by the user and capable of wireless communication.

[0063] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.

[0064] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0065] Base station (BS) — The term “base station” has the full range of its usual meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless telephone system or radio system.

[0066] A processing element (or processor) is a component or combination of components capable of performing the functions of a device (such as a user equipment device or a cellular network device). A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0067] Wi-Fi—The term “Wi-Fi” encompasses the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are distinct from cellular networks.

[0068] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to directly perform that action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0069] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0070] For ease of description, various components may be described as performing one or more tasks. Such descriptions shall be interpreted as including the phrase “configured to”. The statement that a component is configured to perform one or more tasks is expressly intended not to invoke the interpretation of paragraph 6 of section 112 of title 35 of the United States Code.

[0071] Figure 1 and Figure 2 —Exemplary Communication System

[0072] Figure 1 Exemplary (and simplified) wireless communication systems that can implement various aspects of this disclosure according to some embodiments are shown. It should be noted that... Figure 1 The system described is merely one example of a possible system, and this implementation can be carried out in any of a variety of systems as needed.

[0073] As shown in the figure, this exemplary wireless communication system includes a base station 102 that communicates with one or more (e.g., any number) user equipments 106A, 106B, etc., up to 106N, via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE) or UE device. Therefore, user equipment 106 is referred to as a UE or UE device.

[0074] Base station 102 may be a transceiver base station (BTS) or a cell site, and may include hardware and / or software for implementing wireless communication with UEs 106A to 106N. If base station 102 is implemented in the context of LTE, it may be referred to as an "eNodeB" or "eNB". If base station 102 is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB". Base station 102 may also be equipped to communicate with network 100 (e.g., the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet, and various other possible networks). Therefore, base station 102 facilitates communication between user equipments and / or between user equipments and network 100. The communication area (or coverage area) of a base station may be referred to as a "cell". Also as used herein, in relation to a UE, a base station may sometimes be considered to represent the network, taking into account both uplink and downlink communication of the UE. Therefore, a UE communicating with one or more base stations in the network may also be understood as a UE communicating with the network.

[0075] Base station 102 and user equipment can be configured to communicate via a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (WCDMA), LTE, LTE-A Advanced, LAA / LTE-U, 5G NR, 3GPP2, CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, etc.

[0076] Base station 102 and other similar base stations operating according to the same or different cellular communication standards may thus provide, as one or more cell networks, continuous or near-continuous overlapping services to UE 106 and similar devices over a geographic area via one or more cellular communication standards.

[0077] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, UE 106 can be configured to communicate using either or both of the 3GPP cellular communication standards or the 3GPP2 cellular communication standards. In some implementations, UE 106 can be configured to perform techniques for reducing latency in multi-beam wireless communication systems, such as the various methods described herein. UE 106 can also be configured, or alternatively configured, to use WLAN, BLUETOOTH, etc. TM It can communicate with one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0078] Figure 2 An exemplary user equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 according to some embodiments is illustrated. UE 106 can be a device with wireless network connectivity, such as a mobile phone, handheld device, wearable device, computer or tablet, unmanned aerial vehicle (UAV), unmanned flight controller (UAC), automobile, or virtually any type of wireless device. UE 106 may include a processor (processing element) configured to execute program instructions stored in memory. UE 106 can perform any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as any of an FPGA (Field Programmable Gate Array), integrated circuit, and / or various other possible hardware components configured to perform (e.g., individually or in combination) any of or any portion of any of the method embodiments described herein. UE 106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, UE 106 can be configured to communicate using two or more of CDMA2000, LTE, LTE-A, 5G NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0079] UE 106 may include one or more antennas communicating using one or more wireless communication protocols according to one or more RAT standards. In some embodiments, UE 106 may share one or more portions of the receive chain and / or transmit chain among multiple wireless communication standards. The shared radio components may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Typically, the radio components may include any combination of baseband processors, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio components may use the aforementioned hardware to implement one or more receive chains and transmit chains.

[0080] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or CDMA2000 1xRTT (or LTE or NR, or LTE or GSM), and for communication using Wi-Fi and BLUETOOTH. TM Each component communicates independently. Other configurations are also possible.

[0081] Figure 3 — Block diagram of an exemplary UE device

[0082] Figure 3A block diagram of an exemplary UE 106 according to some embodiments is shown. As shown, UE 106 may include a System-on-Chip (SOC) 300, which may include parts for various purposes. For example, as shown, SOC 300 may include a processor 302 capable of executing program instructions for UE 106, and display circuitry 304 capable of performing graphics processing and providing display signals to a display 360. SOC 300 may also include sensor circuitry 370, which may include components for sensing or measuring any of a variety of possible characteristics or parameters of UE 106. For example, sensor circuitry 370 may include motion sensing circuitry configured to detect motion of UE 106, for example, using a gyroscope, accelerometer, and / or any of a variety of other motion sensing components. As another possibility, sensor circuitry 370 may include one or more temperature sensing components, for example, for measuring the temperature of each of one or more antenna panels and / or other components of UE 106. Any of a variety of other possible types of sensor circuitry may also or alternatively be included in UE 106 as needed. Processor 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310) and / or other circuitry or devices, such as display circuitry 304, radio components 330, connector I / F 320, and / or display 360. MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

[0083] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH). TM(e.g., Wi-Fi, GPS, etc.). UE device 106 may include at least one antenna (e.g., 335a) and may include multiple antennas (e.g., shown by antennas 335a and 335b) for performing wireless communication with base stations and / or other devices. Antennas 335a and 335b are shown by way of example, and UE device 106 may include fewer or more antennas. In general, one or more antennas are collectively referred to as antenna 335. For example, UE device 106 may use antenna 335 to perform wireless communication via radio circuitry 330. As described above, in some embodiments, the UE may be configured to use multiple wireless communication standards for wireless communication.

[0084] UE 106 may include hardware and software components for implementing methods for reducing latency in multi-beam wireless communication systems, such as those described further herein. The processor 302 of UE device 106 may be configured to implement some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Furthermore, as... Figure 3 As shown, processor 302 may be coupled to and / or interoperable with other components to perform techniques for reducing latency in multi-beam wireless communication systems according to the various embodiments disclosed herein. Processor 302 may also implement various other applications and / or end-user applications running on UE 106.

[0085] In some implementations, radio component 330 may include a separate controller dedicated to controlling communications for various corresponding RAT standards. For example, such as Figure 3 As shown, radio component 330 may include Wi-Fi controller 352, cellular controller (e.g., LTE-A and / or NR controller) 354, and BLUETOOTH. TM Controller 356, and in at least some embodiments, one or more of these controllers may be implemented as corresponding integrated circuits (referred to as ICs or chips), which communicate with each other and with the SOC 300 (more specifically with the processor 302). For example, Wi-Fi controller 352 may communicate with cellular controller 354 via a cell-ISM link or WCI interface, and / or BLUETOOTH TMController 356 can communicate with cellular controller 354 via a cell-ISM link or the like. Although three separate controllers are shown within radio component 330, other implementations with fewer or more similar controllers for various different RATs may be implemented in UE device 106. In some implementations, cellular controller 354 may include a baseband processor configured to implement or cause UE 106 to implement one or more processes or portions thereof disclosed herein.

[0086] Furthermore, implementation schemes in which the controller can perform functions associated with various radio access technologies are envisioned. For example, according to some implementation schemes, in addition to hardware and / or software components for performing cellular communications, the cellular controller 354 may also include hardware and / or software components for performing one or more activities associated with Wi-Fi, such as Wi-Fi preamble detection, and / or the generation and transmission of Wi-Fi physical layer preamble signals.

[0087] Figure 4 — Block diagram of an exemplary base station

[0088] Figure 4 A block diagram of an exemplary base station 102 according to some implementation schemes is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0089] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106. Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices such as UE device 106. In some cases, network port 470 may be coupled to the telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).

[0090] Base station 102 may include at least one antenna 434 and possibly multiple antennas. Antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be designed to communicate via various wireless telecommunication standards, including but not limited to NR, LTE, LTE-A WCDMA, CDMA2000, etc. Processor 404 of base station 102 may be configured to implement and / or support implementation of some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. In the case of certain RATs (e.g., Wi-Fi), base station 102 can be designed as an access point (AP), in which case network port 470 can be implemented to provide access to a wide area network and / or a local area network, for example, it may include at least one Ethernet port, and radio component 430 can be designed to communicate according to the Wi-Fi standard.

[0091] High propagation delay network

[0092] As various network technologies are integrated with more traditional cellular network technologies, new network characteristics may emerge. As an example, introducing new categories of cellular base stations or repeater stations may introduce significantly larger and more variable propagation delays than those associated with more traditional base stations.

[0093] For example, 3GPP has participated in several research projects on integrating non-terrestrial networks (NTNs) into the 3GPP ecosystem. See, for example, 3GPP TR 38.811, 3GPP TR 22.822, and 3GPP Work Project 860046 (sNR_NTN_solutions). In such systems, the propagation delay between a UE, such as UE 106, and the non-terrestrial network can be significantly greater than the propagation delay between the UE and a traditional terrestrial base station. Additionally, such systems may include cells covering a larger geographical area than traditional cells, which can lead to large differences in propagation delay between two points within the cell. In other words, in such systems, a UE located at the first point in the cell may experience significantly greater propagation delay compared to a UE located at the second point in the same cell. Such delays and differences can be multiplied by the need for multiple round-trip communications.

[0094] Figure 5This is a communication flow diagram illustrating an example of a typical UL service call flow. As shown in the diagram, a UE such as UE 106 can communicate with a base station such as BS102.

[0095] UE 106 may transmit an Initial Authorization Request 502 for reporting authorization to BS102. In some scenarios, the Initial Authorization Request 502 may represent or include a Scheduling Request (SR) for requesting BSR authorization, as defined by 3GPP standards. In other scenarios, the Initial Authorization Request 502 may represent or include a Random Access Initiation (RA) message configured to initiate a procedure for random access communication with BS102. As an example, such an RA Initiation message may include or consist of an RA preamble (sometimes referred to as MSG1), as defined by 3GPP standards. Such messages may initiate RACH procedures, such as the 4-step or 2-step RACH procedures defined by 3GPP standards. Regardless of the format used, the Initial Authorization Request 502 may transmit a simplified request for resource allocation to allow for the transmission of more detailed reports or resource requests. Because the Initial Authorization Request 502 initiates a new communication exchange, it may consist of predefined values. For example, an SR may consist of a single bit, while MSG1 may consist of a predefined preamble. These signals do not include uplink data payloads. As used herein, the term "uplink data" refers to the payload data of UE 106, as distinguished from control signaling, etc. For example, BSR is not considered uplink data.

[0096] In response to receiving the initial grant request 502, BS102 may transmit a limited UL grant 504 to UE 106. The limited UL grant 504 may identify sufficient UL resources for UE 106 to transmit more detailed reports or resource requests. For example, the limited UL grant 504 may include a UL grant for UE 106 to transmit a BSR or similar report. As another example, if the initial grant request 502 includes an RA preamble, the limited UL grant 504 may include an RA response (sometimes also referred to as MSG2) or components thereof, as defined by 3GPP standards, which may include a UL grant for UE 106 to transmit further grant requests such as an RRC connection request. The limited UL grant 504 allocates sufficient resources for UE 106 to transmit more detailed reports or resource requests but insufficient resources to transmit uplink data payloads. For example, in some scenarios, the limited UL grant 504 may allocate sufficient resources for UE 106 to transmit approximately 60 bytes or some similar value (e.g., significantly less than one MB).

[0097] In response to receiving a limited UL grant 504, UE 106 may transmit an extended UL grant request 506 to BS102. For example, the extended UL grant request 506 may include a buffer status report (BSR) that reports the amount of data buffered by UE 106 for transmission to BS102. The BSR may represent a request to transmit a certain amount of data to BS102. In some scenarios, the BSR 506 may be formatted as defined by 3GPP standards. As another example, if the limited UL grant 504 includes an RA response, the extended UL grant request 506 may include an RRC connection request (sometimes referred to as MSG3), as defined by 3GPP standards, which may include UL grants for UE 106 to transmit further communication.

[0098] In response to receiving an extended grant request 506, BS106 may transmit a UL grant 508 to UE106. The UL grant 508 may identify UL resources that UE106 may use to transmit uplink data. For example, the UL grant 508 may identify UL resources that UE106 may use to transmit at least a portion of the amount of data identified in the BSR included in the extended grant request 506. The UL grant 508 may be significantly larger than the limited UL grant 504. For example, in some scenarios, the UL grant 508 may allocate sufficient resources for UE106 to transmit many MB (e.g., up to 80 MB).

[0099] In response to receiving UL authorization 508, UE 106 may transmit uplink data 510 to BS102. As shown, uplink data 510 may represent one or more transmissions of uplink data, and in some scenarios, may also include one or more responses from BS102, such as ACK / NACK messages.

[0100] In receiving Figure 5 Between any signal in the signal diagram and the transmission of the next subsequent signal, the receiving device will introduce some processing delay due to the processing of the received signal. The duration of this delay is generally unaffected by the signal propagation time. Therefore, the processing delay can remain relatively constant across networks of different sizes. In contrast, the flight time required for each individual signal to travel from UE106 to BS102 (or vice versa) is defined as the propagation delay, and it will increase with the distance between UE106 and BS102. Therefore, compared to the delay experienced in geographically smaller cells, the processing delay during procedures such as... Figure 5As illustrated, geographically larger cells can experience significantly longer delays. Furthermore, geographically larger cells can experience significant differential delays, meaning that BS102 will experience significantly longer propagation delays when communicating with UE 106 at a first location within that cell than it would experience when communicating with a second UE at a second location within that cell. As an example, NTN-supported cells can have sufficiently large geographical sizes that such propagation and differential delays become so large that when performing operations such as... Figure 5 The BSR authorization process shown has a negative impact on user experience.

[0101] Furthermore, such long round-trip propagation delays can amplify the impact of bursts in two-way communication, such as when UE 106 transmits large amounts of data and must wait for confirmation of the entire dataset before performing additional communication. The extended propagation delay exacerbates the impact of such waiting times.

[0102] Therefore, if Figure 5 The procedure shown can be adapted to networks with high propagation delays to reduce the delay between the initial authorization request and the reception of uplink data UL authorization, which would be advantageous. It would also be advantageous if the procedure could be adapted to smooth the signal flow to reduce burstiness.

[0103] Figure 6 —A modified PRACH to reduce latency

[0104] One approach to reducing the delay between the initial grant request and the reception of uplink data UL grants in high propagation delay networks is to provide the initial uplink data UL grant immediately in response to the initial request (e.g., before UE 106 transmits a BSR or similar report / request). This initial uplink data UL grant allows UE 106 to receive the data before... Figure 5 The process shown allows for the earlier transmission of at least a portion of its uplink data.

[0105] Figure 6 This is a communication flowchart illustrating an example of a UL service call flow according to some implementation schemes, where the 4-step RA process has been modified to reduce the delay between the initial authorization request and the reception of uplink data UL authorization.

[0106] As shown in the figure, UE 106 can initiate a call flow by transmitting an RA initiation message 602 (such as an RA preamble or similar message) to BS 102. The difference between the RA initiation message 602 and the initial authorization request 502 is that the RA initiation message 602 can be configured to indicate the type or size of the UL authorization that should be authorized (e.g., requested authorization) in response to the RA initiation message 602. Therefore, subsequent authorizations may not be limited to... Figure 5Limited authorization provided during the process.

[0107] As an example, RA Initiation Message 602 can be configured to indicate the type or size of the desired UL authorization by including a specific preamble sequence. For instance, a traditional RA Initiation Message currently defined by 3GPP standards may consist of a preamble sequence randomly selected from a set of sequences available in the cell (e.g., based on cyclic shift and PRACH root sequence index). In contrast, in Figure 6 In its specific implementation, UE 106 may intentionally select a specific preamble sequence (e.g., by intentionally selecting the PRACH root sequence index and cyclic shift). Specifically, the first preamble sequence may indicate that RA initiation message 602 is requesting limited UL authorization, for example, with... Figure 5 The process is consistent with the traditional procedure shown. A second, distinct preamble sequence indicates that the RA-initiated message 602 is requesting an extended UL grant, which includes the allocation of sufficient resources for UE 106 to transmit uplink data. In some implementations, the size of the grant requested by the second preamble sequence can be predetermined. In some implementations, other preamble sequences can be used to request UL grants of different sizes. In some scenarios, the association between available preambles and UL grant requests can be configured in the "PRACH-config" information element (IE).

[0108] As a second example, the RA Initiation Message 602 can be configured to indicate the type or size of the desired UL authorization based on the RACH timing (RO) on which the RA Initiation Message 602 is transmitted. The RACH timing is the area specified in the time and frequency domains that can be used for the transmission of the RACH preamble. In LTE, for all possible RACH preambles, only one RO exists, specified by the RRC message (SIB2). However, in NR, the Synchronization Signal (SSB) is associated with different beams, and UE 106 can select a specific beam and use that beam to transmit PRACH. To enable the network to determine which beam UE 106 has selected, 3GPP defines a specific mapping between SSBs and ROs. By detecting the RO on which UE 106 transmits PRACH, BS102 can determine which SSB beam UE 106 has selected. In this example, the selected RO can further indicate the type or size of the desired UL authorization. For example, transmitting the RA Initiation Message 602 on the first RO can indicate that the RA Initiation Message 602 is requesting a limited UL authorization, such as with... Figure 5The process is consistent with the conventional procedure shown. Transmitting RA Initiation Message 602 on a second, different RO can indicate that RA Initiation Message 602 is requesting an extended UL grant, which includes the allocation of sufficient resources for UE 106 to transmit uplink data. In some implementations, the size of the grant requested by the second RO can be predetermined. In some implementations, other ROs can be used to request UL grants of different sizes. In some scenarios, the association between available ROs and UL grant requests can be configured in the "PRACH-config" IE.

[0109] Other methods may also be used, or alternatively, to configure RA Initiation Message 602 to indicate the type or size of the desired UL license. A notable feature of the above examples is that RA Initiation Message 602 continues to consist of a preamble sequence compatible with existing 3GPP standards. For example, RA Initiation Messages configured according to any of the examples above do not include additional bits, fields, or other messages for conveying the type or size of the desired UL license. Specifically, RA Initiation Message 602 may not include a BSR and may not include a MAC header.

[0110] In some scenarios, UE 106 may determine the type or size of the UL authorization to be requested based on one or more factors, such as the amount of data buffered for transmission to BS102, data type, quality of service (QoS), propagation between UE 106 and BS102, and / or the type of network, cell, or BS. For example, in some scenarios, UE 106 may request an extended UL authorization in response to determining that BS102 is an NTNBS, and thus is expected to exhibit high propagation latency. In contrast, UE 106 may request a limited UL authorization in response to determining that BS102 is a traditional terrestrial BS. UE 106 may configure RA initiation message 602 accordingly.

[0111] In response to receiving RA Initiation Message 602, BS102 may transmit UL Authorization 604 to UE 106. UL Authorization 604 identifies UL resources that UE 106 can use to transmit data consistent with the request indicated by RA Initiation Message 602. Figure 6 As shown, UL Authorization 604 is an extended UL Authorization that identifies UL resources that UE 106 can use to transmit uplink data.

[0112] exist Figure 6In this scenario, UE 106 may transmit uplink data message 606 to BS 102 in response to receiving UL authorization 604. Uplink data message 606 may include some or all of the data buffered by UE 106 for transmission to BS 102 using the resources identified in UL authorization 604. Uplink data message 606 may also include a BSR, which reports the remaining amount of buffered data for transmission to BS 102. For example, the BSR may include or consist of a MAC control element (CE) included in uplink data message 606.

[0113] In response to receiving an uplink data message 606 including a BSR, BS102 may transmit an additional UL grant 608, which identifies UL resources that can be used by UE 106 to transmit at least a portion of the buffered data reported by the BSR.

[0114] In response to receiving an additional UL authorization 608, UE 106 may transmit an uplink data message 610 to BS102. As shown, uplink data message 610 may represent one or more transmissions of uplink data, and in some scenarios, may also include one or more responses from BS102, such as ACK / NACK messages.

[0115] It should be understood that similar procedures can be used to update the 2-step RA process. For example, in the 2-step RA process, the RA initiation message can be configured to indicate the type or size of the requested UL authorization, for example, using any of the methods described above. In some scenarios, such methods can be used to request an authorization larger than that requested in the RA initiation message of the 2-step RA process in other ways.

[0116] Figure 7 —Modified PRACH for initial uplink data UL authorization

[0117] Another approach to reducing the delay between the initial grant request and the reception of uplink data UL grants in high propagation delay networks, and to reduce burstiness, is to provide an additional fixed initial UL grant immediately in response to the initial request (e.g., before UE 106 transmits a BSR or similar report / request). This additional initial UL grant allows UE 106 to receive data more efficiently than the initial grant request. Figure 5 The process shown allows for the earlier transmission of at least a portion of its uplink data.

[0118] Figure 7 This is a communication flowchart illustrating an example of a UL business call flow according to some implementation schemes, where the 4-step RA process has been modified to provide additional initial UL authorization.

[0119] As shown in the figure, UE 106 can initiate a call flow by transmitting an RA initiation message 702 (such as an RA preamble or similar message) to BS102. In some scenarios, the RA initiation message 702 can be combined with... Figure 5 The initial authorization request is similar to or the same as 502.

[0120] In response to receiving the RA Initiation Message 702, BS102 may transmit the configured grant 704 to UE 106. For example, the configured grant 704 may be included in the RA response or may be broadcast in the SIB. The configured grant 704 identifies UL resources that can be used by UE 106 to transmit uplink data. In some scenarios, the size of the configured grant 704 may be fixed or predetermined.

[0121] The transmission of the configured grant 704 may be based on one or more factors. For example, if BS102 has a specific type or is included in a specific type of network (such as NTN), BS102 may transmit the configured grant 704 in response to receiving the RA Initiation Message 702. As another example, BS102 may transmit the configured grant 704 based on cell size or the propagation delay observed within the cell in response to receiving the RA Initiation Message 702.

[0122] In response to receiving the configured grant 704, UE 106 may transmit an uplink data message 708 to BS 102. As shown, uplink data message 708 may represent one or more transmissions of uplink data, and in some scenarios, may also include one or more responses from BS 102, such as ACK / NACK messages. In some scenarios, uplink data message 708 may also include a BSR, which reports the amount of buffered data remaining for transmission to BS 102. For example, the BSR may include or consist of a MAC control element (CE) included in uplink data message 708.

[0123] In some scenarios, the configured grant 704 can be configured such that the allocated resources (and therefore the uplink data message 708) occur shortly after the transmission of the RRC connection establishment message (not shown) from BS102 to UE106. If the RRC connection is not completed (e.g., due to a failure to resolve contention for UE106), BS102 may discard the configured grant 704.

[0124] In response to receiving the RA Initiation Message 702, BS102 may also transmit a Limited UL Authorization 706, such as an RA response, to UE 106. In some scenarios, the Limited UL Authorization 706 can be combined with... Figure 5The limited UL authorization 504 is similar to or the same as the limited UL authorization 706. The limited UL authorization 706 identifies sufficient UL resources for UE 106 to transmit more detailed reports or resource requests.

[0125] In response to receiving a limited UL authorization 706, UE 106 can complete the RA procedure, for example, by exchanging RRC connection request and RRC connection establishment messages with BS102, essentially as a combination of Figure 5 As outlined.

[0126] In response to receiving an uplink data message 708 including a BSR, BS102 may transmit an additional UL grant 710 to UE 106, which may identify UL resources that UE 106 may use to transmit uplink data.

[0127] In response to receiving an additional UL authorization 710, UE 106 may transmit an uplink data message 712 to BS102. As shown, the uplink data message 712 may represent one or more transmissions of uplink data, and in some scenarios, may also include one or more responses from BS102, such as ACK / NACK messages.

[0128] Figure 7 The call flow shown can be used in comparison Figure 5 The call flow shown provides uplink data authorization to UE 106 at an earlier stage. This allows initial data transmission to begin more quickly and also reduces burstiness.

[0129] As Figure 7 As shown in the possible variations of the call flow, BS102 may send a configured grant, such as configured grant 704, in response to receiving an SR from UE 106. This would provide similar benefits, allowing initial data transmission to begin more quickly and reducing burstiness.

[0130] Figure 8 —Supplementing BSR

[0131] Another approach to reduce latency and smooth signal flow in high propagation delay networks is to provide a BSR update message before the BSR timer expires to signal additional data buffered at the UE. This BSR update message allows for more real-time reporting of buffer status to compensate for the increased propagation delay.

[0132] Once an RRC connection is established between UE 106 and BS102, a typical procedure involves UE 106 reporting periodic BSRs, which are performed by the network. This periodic reporting allows the UE to report buffered data at regular intervals to receive uplink data grants as needed. However, this procedure is designed and optimized for legacy networks and may exhibit problems when applied unmodified to networks with high propagation delays. For example, if the propagation delay is too high, the time between transmitting a BSR and receiving a grant can become excessively long, as a large amount of additional data can enter the buffer during this period. This can result in large and infrequent transmission windows.

[0133] Figure 8 This is a communication flow diagram illustrating an example of a UL service call flow including a BSR update message according to some implementation schemes.

[0134] As shown in the figure, UE 106 can transmit BSR 802 to BS102, requesting uplink data UL authorization. BSR 802 can transmit the amount of data buffered at UE 106 for transmission to BS102.

[0135] Following the transmission of BSR 802, UE 106 may buffer additional data to be transmitted to BS102. However, if the BSR timer has not yet expired, UE 106 may not be allowed to transmit another BSR. If BSR update messages are permitted and configured for use by UE 106, UE 106 may, for example, transmit BSR update message 804 to BS102 in response to determining that the additional buffered data has reached a threshold amount. BSR update message 804 may be transmitted before the BSR timer expires and may indicate to BS102 that additional data has been buffered by UE 106 after the transmission of BSR 802. For example, in some scenarios, BSR update message 804 may indicate that the additional data buffered by UE 106 has at least reached a threshold amount. In some scenarios, BSR update message 804 may explicitly indicate the amount of additional data buffered by UE 106 after the transmission of BSR 802, or may explicitly indicate the total amount of data currently buffered by UE 106. In some scenarios, the BSR update message 804 may be transmitted only if UL authorization has not yet been received in response to BSR 802 and / or if the BSR timer has not expired since the transmission of BSR 802. In some scenarios, the BSR update message 804 may include or consist of a MAC CE.

[0136] In some scenarios, UE 106 may transmit one or more additional BSR update messages (not shown) before the BSR timer expires, for example, when buffering additional data.

[0137] In response to receiving both BSR 802 and BSR Update Message 804, BS102 may transmit UL Grant 806 to UE 106, which identifies the resources allocated for transmitting at least a portion of the buffered data reported in BSR 802 and BSR Update Message 804. In some scenarios, BS102 may treat the BSR Update Message as a long BSR. The size of the uplink grant (or, in other words, the amount of resources allocated by the uplink grant) may be based on BSR 802 and BSR Update Message 804. For example, the size of the uplink grant may be based on the amount of data buffered at UE 106 for transmission to BS102, as indicated by BSR 802 and BSR Update Message 804.

[0138] In response to receiving UL Authorization 806, UE 106 may transmit Uplink Data Message 808 to BS 102. Uplink Data Message 808 may include some or all of the data buffered by UE 106 for transmission to BS 102 using the resources identified in UL Authorization 806. If UE 106 has buffered additional data, and if the BSR timer has expired, Uplink Data Message 808 may also include a BSR, which reports the remaining amount of buffered data for transmission to BS 102. For example, the BSR may include or consist of a MAC CE included in Uplink Data Message 808.

[0139] Following the transmission of uplink data message 808 with a BSR, UE 106 may again buffer additional data for transmission to BS 102. If the BSR timer has not expired and if a UL grant has not been received in response to uplink data message 808, UE 106 may transmit a second BSR update message 810 to BS 102. The second BSR update message 810 may be similar to BSR update message 804.

[0140] In response to receiving a BSR included in uplink data message 808 and a second BSR update message 810, BS102 may transmit a second UL grant 812 to UE 106, the grant size of which is allocated resources for transmitting at least a portion of the buffered data reported in the BSR included in uplink data message 808 and the second BSR update message 810, for example, the grant size is based on the BSR included in uplink data message 808 and the second BSR update message 810.

[0141] In response to receiving the second UL authorization 812, UE 106 may transmit a second uplink data message 814 to BS 102. For example... Figure 8As shown in the example, the second uplink message 814 may include all data buffered by the UE 106 for transmission to the BS 102 using the resources identified in the second UL grant 812, such that the second uplink message 814 does not include an additional BSR. In other scenarios, an additional BSR may be included as needed.

[0142] In some scenarios, the network (e.g., BS102 and / or other network components) may provide configuration information regarding the BSR update messages used by UE 106 based on various factors, such as the base station type of BS102, network type, propagation delay between BS102 and UE 106 and / or one or more other UEs, and / or the capabilities of UE 106. For example, the network may configure the number or frequency at which UE 106 can transmit BSR update messages. In some scenarios, the network may approve / disapprove UE 106 and / or other UEs' use of BSR update messages. In some scenarios, UE 106 may provide BS102 with an indication of whether UE 106 supports the functionality used for transmitting BSR update messages, for example, as a UE capability indication.

[0143] In some scenarios, configuration information related to BSR update messages can be transmitted to UEs (such as UE 106) in the cell before the transmission of BSR 802 or BSR update message 804. For example, BS102 can broadcast configuration information about BSR update messages in a predefined System Information Block (SIB). This allows configuration information to be received by multiple UEs (e.g., all UEs) in the cell. As another example, BS102 can provide configuration information to UE 106, for example, based on the service type indication sent by the UE, in an RRC connection establishment message (e.g., RA MSG4) or in an RRC reconfiguration message. This allows for more dynamic reconfiguration of BSR update messages for individual UEs.

[0144] Such service type indications help the network determine whether the uplink data service to be transmitted by UE 106 has a type that is likely to quickly fill the data buffer at UE 106. The network can therefore provide configuration information for BSR update messages, or can choose not to configure such messages based on these service type indications. For example, UE 106 may provide an indication of an Industrial Internet of Things (IIOT) service type. In response, the network may determine not to configure BSR update messages for UE 106 because the service is unlikely to generate a large amount of uplink data. As another example, UE 106 may provide an indication that its buffer is full. In response, the network may determine to provide an aggressive configuration for BSR update messages, such as allowing a large number and / or frequent BSR update messages. As yet another example, UE 106 may provide an indication of some intermediate data type. In response, the network may determine to provide a non-aggressive configuration for BSR update messages, such as allowing less frequent and / or less large numbers of BSR update messages.

[0145] In some scenarios, such instructions can be provided as in Internet Explorer. Other formats are also envisioned.

[0146] In some scenarios, when switching to a high propagation delay network, configuration information can be transmitted to UE106. For example, BS102 may provide configuration information to UE106 in an RRC recovery message in response to UE106 switching from a network that is not a high propagation delay network to BS102's network.

[0147] It should be understood that, for all the foregoing examples, BS102 may allocate as many available resources as possible for use by UE 106 in response to receiving any kind of authorization request (e.g., limited authorization request, full authorization request, BSR, BSR update message, etc.). In some scenarios, BS102 may not provide the uplink authorization of the size requested by the authorization request; for example, BS102 may not allocate sufficient resources to transmit all data buffered at UE 106 for transmission to BS102. For example, in some scenarios, sufficient resources may not be available.

[0148] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0149] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0150] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, in some embodiments, the subject matter may be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other embodiments, the subject matter may be implemented using one or more custom-designed hardware devices such as ASICs. In still other embodiments, the subject matter may be implemented using one or more programmable hardware elements such as FPGAs.

[0151] In some embodiments, a non-transitory computer-readable storage medium (e.g., a non-transitory memory element) may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any method embodiments described herein, or any combination of such subsets.

[0152] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or a set of processors) and a memory medium (or memory elements), wherein the memory medium stores program instructions, and wherein the processor is configured to read from and execute the program instructions, wherein the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset or any combination of such subsets of any method embodiments described herein). The device may be implemented in any of a variety of forms.

[0153] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A baseband processor configured to perform operations including: Transmit a service type indication to the base station that identifies the type of uplink data service to be transmitted to the base station; Receive configuration information related to a Buffer Status Report (BSR) update message from the base station, wherein the configuration information is based on the service type indication; A first BSR is transmitted to the base station, the first BSR indicating the amount of uplink data buffered by the wireless device for transmission to the base station; A first BSR update message is transmitted to the base station, the first BSR update message indicating that the wireless device has buffered an additional amount of uplink data to transmit to the base station after transmitting the first BSR, wherein the first BSR update message is transmitted after transmitting the first BSR and before the timer expires, wherein the transmission of a second BSR after the first BSR is prohibited before the timer expires, wherein the transmission of the first BSR update message is based on received configuration information. as well as In response to the first BSR and the first BSR update message, an uplink grant is received from the base station to allocate resources for transmitting at least a portion of the uplink data buffered by the radio device, wherein the uplink grant has a size based on the amount of uplink data indicated by the first BSR and the additional amount of uplink data indicated by the first BSR update message.

2. The baseband processor of claim 1, further configured to perform operations including: After the timer for authorizing the transmission of the second BSR expires, uplink data and the second BSR are transmitted to the base station using the allocated resources. The second BSR indicates the amount of remaining uplink data to be transmitted to the base station.

3. The baseband processor of claim 1, wherein the configuration information is received in one or more of a System Information Block (SIB), a Radio Resource Control (RRC) Connection Establishment message, an RRC Reconfiguration message, or an RRC Recovery message.

4. The baseband processor according to claim 1, wherein the configuration information defines how frequently the wireless device can transmit BSR update messages.

5. The baseband processor of claim 1, further configured to perform operations including: A second BSR update message is transmitted to the base station, the second BSR update message indicating that the wireless device has buffered an additional amount of uplink data to transmit to the base station after transmitting the first BSR update message, wherein the second BSR update message is transmitted after transmitting the first BSR update message and before the timer for the transmission of the second BSR after authorizing the first BSR expires, wherein the uplink authorization is further responsive to the second BSR update message, and wherein the uplink authorization has a further size based on the second BSR update message.

6. A wireless device, comprising: antenna; A radio component, the radio component being operatively coupled to the antenna; and A processor, the processor being operatively coupled to the radio component; The wireless device is configured as follows: Transmit a service type indication to the base station that identifies the type of uplink data service to be transmitted to the base station; Receive configuration information related to a Buffer Status Report (BSR) update message from the base station, wherein the configuration information is based on the service type indication; A first BSR is transmitted to the base station, the first BSR indicating the amount of uplink data buffered by the wireless device for transmission to the base station; A first BSR update message is transmitted to the base station, the first BSR update message indicating that the wireless device has buffered an additional amount of uplink data to transmit to the base station after transmitting the first BSR, wherein the first BSR update message is transmitted after transmitting the first BSR and before the timer expires, wherein the transmission of a second BSR after the first BSR is prohibited before the timer expires, wherein the transmission of the first BSR update message is based on received configuration information. as well as In response to the first BSR and the first BSR update message, an uplink grant is received from the base station to allocate resources for transmitting at least a portion of the uplink data buffered by the radio device, wherein the uplink grant has a size based on the amount of uplink data indicated by the first BSR and the additional amount of uplink data indicated by the first BSR update message.

7. The wireless device of claim 6, wherein the wireless device is further configured to: After the timer for authorizing the transmission of the second BSR expires, uplink data and the second BSR are transmitted to the base station using the allocated resources. The second BSR indicates the amount of remaining uplink data to be transmitted to the base station.

8. The wireless device of claim 6, wherein the configuration information is received in one or more of a System Information Block (SIB), a Radio Resource Control (RRC) Connection Establishment message, an RRC Reconfiguration message, or an RRC Recovery message.

9. The wireless device of claim 6, wherein the configuration information defines how frequently the wireless device can transmit BSR update messages.

10. The wireless device of claim 6, wherein the processor is further configured to cause the wireless device to: A second BSR update message is transmitted to the base station, the second BSR update message indicating that the wireless device has buffered an additional amount of uplink data to transmit to the base station after transmitting the first BSR update message, wherein the second BSR update message is transmitted after transmitting the first BSR update message and before the timer for the transmission of the second BSR after authorizing the first BSR expires, wherein the uplink authorization is further responsive to the second BSR update message, and wherein the uplink authorization has a further size based on the second BSR update message.

11. A method for performing wireless communication within a high propagation delay network, the method comprising: By wireless devices: Transmit a service type indication to the base station that identifies the type of uplink data service to be transmitted to the base station; Receive configuration information related to a Buffer Status Report (BSR) update message from the base station, wherein the configuration information is based on the service type indication; A first BSR is transmitted to the base station of the network, the first BSR indicating the amount of uplink data buffered by the wireless device for transmission to the base station; A first BSR update message is transmitted to the base station, the first BSR update message indicating that the wireless device has buffered an additional amount of uplink data to transmit to the base station after transmitting the first BSR, wherein the first BSR update message is transmitted after transmitting the first BSR and before the timer expires, wherein the transmission of a second BSR after the first BSR is prohibited before the timer expires, wherein the transmission of the first BSR update message is based on received configuration information. as well as In response to the first BSR and the first BSR update message, an uplink grant is received from the base station to allocate resources for transmitting at least a portion of the uplink data buffered by the radio device, wherein the uplink grant has a size based on the amount of uplink data indicated by the first BSR and the additional amount of uplink data indicated by the first BSR update message.

12. The method of claim 11, further comprising: After the timer for authorizing the transmission of the second BSR expires, uplink data and the second BSR are transmitted to the base station using the allocated resources. The second BSR indicates the amount of remaining uplink data to be transmitted to the base station.

13. The method of claim 11, wherein the configuration information is received in one or more of a System Information Block (SIB), a Radio Resource Control (RRC) Connection Establishment message, an RRC Reconfiguration message, or an RRC Recovery message.

14. The method of claim 11, further comprising: A second BSR update message is transmitted to the base station, the second BSR update message indicating that the wireless device has buffered an additional amount of uplink data to transmit to the base station after transmitting the first BSR update message, wherein the second BSR update message is transmitted after transmitting the first BSR update message and before the timer for the transmission of the second BSR after authorizing the first BSR expires, wherein the uplink authorization is further responsive to the second BSR update message, and wherein the uplink authorization has a further size based on the second BSR update message.

Images