Method and apparatus for reporting buffer status

By using artificial intelligence algorithms on the terminal device to predict the buffer size and send the BSR, the data transmission delay problem caused by the BSR process in the prior art is solved, and more efficient data transmission is achieved.

CN115804223BActive Publication Date: 2026-11-10TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202180042643.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-06-19
Filing Date
2021-04-14
Publication Date
2026-11-10
Estimated Expiration
2041-04-14

AI Technical Summary

Technical Problem

In existing technologies, there is a delay problem in the process of terminal devices sending buffer status reports (BSRs) to network nodes, which leads to increased data transmission latency.

Method used

The BSR process is optimized by predicting the buffer size at the terminal device and sending the predicted buffer status report (BSR), using artificial intelligence algorithms such as LSTM neural network models and Arima machine learning models, combined with logical channel priority and probability thresholds.

Benefits of technology

This reduces data transmission latency from terminal devices to network nodes and improves data transmission efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115804223B_ABST
    Figure CN115804223B_ABST
Patent Text Reader

Abstract

Embodiments of this disclosure provide methods and apparatus for buffer status reporting. A method performed at a terminal device may include: predicting (S101) a buffer size associated with data to be transmitted; and sending (S102) a buffer status report (BSR) including the predicted buffer size to a network node. A method performed at a network node may include: receiving (S201) a buffer status report (BSR) including the predicted buffer size associated with data to be received from the terminal device; and sending (S202) permission for the data based on the received BSR. This can reduce latency in data transmission from the terminal device to the network node.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure generally relates to wireless communication technology, and more particularly to a method and apparatus for reporting buffer status of a terminal device. Background Technology

[0002] This section provides information to facilitate a better understanding of aspects of this disclosure. Therefore, the statements in this section should be read in this context and should not be construed as an admission of anything in the prior art or anything not in the prior art.

[0003] In a communication system, when a terminal device has data to send to a network node (such as a base station), the terminal device can first report to the base station how much data it has. This information about how much data it has can be included in the buffer status report (BSR) from the terminal device to the network. Summary of the Invention

[0004] This summary is provided to illustrate the selection of concepts in a simplified form, which is further described in the detailed embodiments below. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0005] Certain aspects of this disclosure and its embodiments can provide solutions to these or other challenges. Various embodiments are presented herein to address one or more of the problems disclosed herein. Improved BSR mechanisms can be provided to reduce the latency of data transmission from the end device to the network node introduced by the BSR process.

[0006] A first aspect of this disclosure provides a method performed at a terminal device, comprising: predicting a buffer size associated with data to be transmitted; and sending a buffer status report (BSR) including the predicted buffer size to a network node.

[0007] In embodiments of this disclosure, the method further includes: receiving permission for the data to be sent; and sending the data.

[0008] In embodiments of this disclosure, the prediction is based on at least one of the following: the size, type, content, or required transmission rate of the data.

[0009] In embodiments of this disclosure, the prediction is based on at least one of the following: input data from application behavior, user behavior, radio conditions, or traffic behavior.

[0010] In embodiments of this disclosure, the user behavior includes mobility; and / or the business behavior includes business patterns.

[0011] In embodiments of this disclosure, the method further includes: predicting a probability associated with the predicted buffer size.

[0012] In embodiments of this disclosure, the BSR includes the probability.

[0013] In embodiments of this disclosure, the terminal device sends the BSR when the probability is equal to or greater than a threshold.

[0014] In embodiments of this disclosure, the threshold is configurable or fixed.

[0015] In embodiments of this disclosure, the prediction is made using artificial intelligence algorithms.

[0016] In embodiments of this disclosure, the prediction is made using a Long Short-Term Memory (LSTM) neural network model, an Arima machine learning model, and / or reinforcement learning.

[0017] In embodiments of this disclosure, the method further includes: receiving BSR prediction configuration for the terminal device or for multiple terminal devices.

[0018] In embodiments of this disclosure, the terminal device transmits the BSR in the uplink shared channel (UL-SCH).

[0019] In embodiments of this disclosure, the terminal device sends a scheduling request (SR) for the BSR.

[0020] In embodiments of this disclosure, the terminal device sends the SR according to the SR configuration.

[0021] In embodiments of this disclosure, the SR configuration is received from the network node or is pre-configured.

[0022] In embodiments of this disclosure, the BSR is configured for a logical channel or for a logical channel group.

[0023] In embodiments of this disclosure, the BSR is configured based on the priority of the logical channel or the logical channel group.

[0024] In embodiments of this disclosure, the BSR also includes a buffer size associated with the data allocated to the logical channel.

[0025] In this embodiment of the disclosure, the method further includes: reporting the terminal device's ability to support the BSR.

[0026] In embodiments of this disclosure, the BSR further includes: a predicted time point or time window for transmitting the data.

[0027] In embodiments of this disclosure, the BSR further includes: the predicted probability of a time point or time window for transmitting the data.

[0028] In embodiments of this disclosure, the predicted buffer size is included in the Media Access Control (MAC) control element (CE).

[0029] In embodiments of this disclosure, the method further includes receiving an indication as to whether the BSR, including the predicted buffer size, is enabled or disabled.

[0030] In embodiments of this disclosure, the method further includes: when the BSR, which includes the predicted buffer size, is disabled, sending a Buffer Status Report (BSR) that includes a buffer size associated with data allocated to the logical channel of the terminal device.

[0031] In embodiments of this disclosure, the indication includes a threshold of the probability of the predicted buffer size.

[0032] In embodiments of this disclosure, the method further includes: starting a timer after sending the BSR including the predicted buffer size; and / or stopping the timer after receiving the permission.

[0033] In embodiments of this disclosure, the method further includes: restarting the timer if the predicted buffer size is updated and the BSR including the predicted buffer size is retransmitted.

[0034] In embodiments of this disclosure, the method further includes: retransmitting the predicted BSR when the timer times out.

[0035] In embodiments of this disclosure, the BSR includes a predetermined logical channel identifier (LCID) to indicate the predicted buffer size.

[0036] In embodiments of this disclosure, the terminal device includes a user equipment (UE).

[0037] A second aspect of this disclosure provides a method performed at a network node, comprising: receiving a buffer status report (BSR) including a predicted buffer size associated with data to be received from a terminal device; and sending a license for the data based on the received BSR.

[0038] In embodiments of this disclosure, the method further includes: receiving the data.

[0039] In embodiments of this disclosure, the prediction is based on at least one of the following: the size, type, content, or required transmission rate of the data.

[0040] In embodiments of this disclosure, the prediction is based on at least one of the following: input data from application behavior, user behavior, radio conditions, or service behavior.

[0041] In embodiments of this disclosure, the user behavior includes mobility; and / or the business behavior includes business patterns.

[0042] In embodiments of this disclosure, the method further includes receiving a probability associated with the predicted buffer size.

[0043] In embodiments of this disclosure, the BSR includes the probability.

[0044] In embodiments of this disclosure, the terminal device sends the BSR when the probability is equal to or greater than a threshold.

[0045] In embodiments of this disclosure, the threshold is configurable or fixed.

[0046] In embodiments of this disclosure, the method further includes: configuring a priority for data transmission based on the probability. The priority is associated with the probability.

[0047] In embodiments of this disclosure, the prediction is made using artificial intelligence algorithms.

[0048] In embodiments of this disclosure, the prediction is made using a Long Short-Term Memory (LSTM) neural network model, an Arima machine learning model, and / or reinforcement learning.

[0049] In embodiments of this disclosure, the method further includes: sending BSR prediction configuration for a terminal device or for multiple terminal devices.

[0050] In embodiments of this disclosure, the terminal device transmits the BSR in the uplink shared channel (UL-SCH).

[0051] In embodiments of this disclosure, the terminal device sends a scheduling request (SR) for the BSR.

[0052] In embodiments of this disclosure, the terminal device sends the SR according to the SR configuration.

[0053] In embodiments of this disclosure, the SR configuration is sent from the network node or is pre-configured.

[0054] In embodiments of this disclosure, the BSR is configured for a logical channel or for a logical channel group.

[0055] In embodiments of this disclosure, the BSR is configured based on the priority of the logical channel or the logical channel group.

[0056] In embodiments of this disclosure, the BSR also includes a buffer size associated with the data allocated to the logical channel.

[0057] In embodiments of this disclosure, the method further includes: receiving the terminal device's ability to support the BSR, including the predicted buffer size.

[0058] In embodiments of this disclosure, the BSR further includes: a predicted time point or time window for transmitting the data.

[0059] In embodiments of this disclosure, the BSR further includes: the predicted probability of a time point or time window for transmitting the data.

[0060] In embodiments of this disclosure, the predicted buffer size is included in the Media Access Control (MAC) control element (CE).

[0061] In embodiments of this disclosure, the method further includes sending an indication as to whether the BSR, including the predicted buffer size, is enabled.

[0062] In embodiments of this disclosure, the method further includes: receiving a buffer status report (BSR) that includes a buffer size associated with data allocated to the logical channel of the terminal device when the BSR, which includes the predicted buffer size, is disabled.

[0063] In embodiments of this disclosure, the indication includes a threshold of the probability of the predicted buffer size.

[0064] In embodiments of this disclosure, the BSR includes a predetermined logical channel identifier (LCID) to indicate the predicted buffer size.

[0065] In embodiments of this disclosure, the method further includes scheduling another terminal device based on the predicted buffer size.

[0066] In embodiments of this disclosure, the network node includes a base station.

[0067] A third aspect of this disclosure provides a terminal device including: a processor; and a memory containing instructions executable by the processor, thereby enabling the terminal device to: predict a buffer size associated with data to be transmitted; and send a buffer status report (BSR) including the predicted buffer size to a network node.

[0068] In embodiments of this disclosure, the terminal device is operable to perform the method according to any embodiment of the first aspect.

[0069] A fourth aspect of this disclosure provides a network node comprising: a processor; and a memory containing instructions executable by the processor, thereby enabling the network node to: receive a buffer status report (BSR) including a predicted buffer size associated with data to be received from a terminal device; and send permission for the data based on the received BSR.

[0070] In embodiments of this disclosure, the network node is operable to perform the method according to any embodiment of the first aspect.

[0071] A fifth aspect of this disclosure provides a terminal device comprising: a prediction unit configured to predict the size of a buffer of data to be transmitted; and a transmission unit configured to transmit a buffer status report (BSR) including the predicted buffer size to a network node.

[0072] A sixth aspect of this disclosure provides a network node comprising: a receiving unit configured to receive a buffer status report (BSR) including a predicted buffer size associated with data to be received from a terminal device; and a sending unit configured to send a permission for the data based on the received BSR.

[0073] A seventh aspect of this disclosure provides a computer-readable storage medium for storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any embodiment of the first or second aspect.

[0074] The embodiments described herein offer numerous advantages. According to embodiments of this disclosure, the terminal device can predict the buffer size associated with the data to be transmitted and send a Buffer Status Report (BSR) including the predicted buffer size to the network node. That is, instead of actually allocating the data to any logical channel and then calculating a specific buffer size for that logical channel, the BSR can be predicted and sent to the network node. Thus, the time spent waiting for data to be allocated to any logical channel before the BSR is unnecessary, thereby reducing latency in data transmission from the terminal device to the network node. Attached Figure Description

[0075] The above and other aspects, features, and benefits of the various embodiments of this disclosure will become clearer by way of example from the following detailed description with reference to the accompanying drawings, in which similar reference numerals or letters are used to designate similar or equivalent elements. The illustrated drawings are provided to facilitate a better understanding of the embodiments of this disclosure and are not necessarily drawn to scale, wherein:

[0076] Figure 1This is an example diagram of the physical resource grid of a communication system;

[0077] Figure 2A This is an example structure of elements in a BSR;

[0078] Figure 2B This is an example structure of elements in a BSR;

[0079] Figure 3 This is an exemplary flowchart showing the UL sending;

[0080] Figure 4A This is an exemplary flowchart illustrating a method performed at a terminal device according to an embodiment of the present disclosure;

[0081] Figure 4B It is shown Figure 4A An exemplary flowchart of the additional steps of the method shown;

[0082] Figure 5A This is an exemplary flowchart illustrating a method performed at a network node according to an embodiment of the present disclosure;

[0083] Figure 5B It is shown Figure 5A An exemplary flowchart of the additional steps of the method shown;

[0084] Figure 6 This is an exemplary flowchart illustrating an overview of a process for sending a BSR according to an embodiment of the present disclosure;

[0085] Figure 7 This is a block diagram illustrating an exemplary apparatus suitable for practical terminal devices and network nodes according to embodiments of the present disclosure;

[0086] Figure 8 This is a block diagram illustrating an apparatus / computer-readable storage medium according to embodiments of the present disclosure;

[0087] Figure 9 This is a schematic diagram illustrating units for a terminal device and a network node according to embodiments of the present disclosure;

[0088] Figure 10 This is a schematic diagram illustrating a wireless network according to some embodiments;

[0089] Figure 11 This is a schematic diagram illustrating a user equipment according to some embodiments;

[0090] Figure 12 This is a schematic diagram illustrating a virtualized environment according to some embodiments;

[0091] Figure 13This is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0092] Figure 14 This is a schematic diagram illustrating a host computer communicating with a user equipment via a base station through a partially wireless connection according to some embodiments;

[0093] Figure 15 This is a schematic diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments;

[0094] Figure 16 This is a schematic diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments;

[0095] Figure 17 These are schematic diagrams illustrating methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments; and

[0096] Figure 18 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. Detailed Implementation

[0097] Embodiments of this disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed merely to enable those skilled in the art to better understand and thus implement this disclosure, and not to impose any limitation on the scope of this disclosure. References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable with this disclosure should be included in or in any single embodiment of this disclosure. Rather, references to features and advantages are understood to indicate that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this disclosure. Furthermore, the features, advantages, and characteristics of this disclosure described may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize that this disclosure can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in all embodiments of this disclosure may be recognized in certain embodiments.

[0098] Generally, unless a different meaning is clearly given and / or implied in the context of its use, all terms used herein shall be interpreted according to their ordinary meaning in the relevant art. Unless otherwise expressly stated, all references to "a / an / element, device, component, apparatus, step, etc." shall be openly interpreted as referring to at least one instance of that element, device, component, apparatus, step, etc. Unless explicitly stated otherwise, a step is described as occurring after or before another step and / or it is implied that a step must occur after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0099] As used herein, the term "network" or "communication network" refers to a network that conforms to any suitable wireless communication standard. For example, wireless communication standards may include New Radio (NR), Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. In the following description, the terms "network" and "system" are used interchangeably. Furthermore, communication between two devices in a network may be performed according to any suitable communication protocol, including but not limited to wireless communication protocols defined by standards organizations such as the 3rd Generation Partnership Project (3GPP), or wired communication protocols.

[0100] As used herein, the term "network node" refers to a network device, network entity, network function, or any other device (physical or virtual) in a communications network. For example, a network node in a network may include a base station (BS), access point (AP), multi-cell / multicast coordination entity (MCE), server node / function (e.g., Service Capability Server / Application Server (SCS / AS), Group Communication Service Application Server (GCS AS), Application Function (AF)), open node / function (e.g., Service Capability Open Function (SCEF), Network Open Function (NEF)), Unified Data Management (UDM), Home Subscriber Server (HSS), Session Management Function (SMF), Access and Mobility Management Function (AMF), Mobility Management Entity (MME), controller, or any other suitable device in a wireless communications network. A BS may be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next-generation Node B (gNodeB or gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, or a low-power node (such as a femtosecond, picosecond, etc.).

[0101] Further examples of network nodes include multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceivers (BTS), transmission points, transmission nodes, location nodes, and / or the like.

[0102] Furthermore, the term "network node" can also refer to any suitable function that can be implemented in a network entity (physical or virtual) within a communication network. For example, a 5G system (5GS) can include multiple NFs, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Open Function), UPF (User Plane Function), NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Agent), etc. In other embodiments, depending on the specific network, network functions can include different types of NFs (e.g., PCRF (Policy and Charging Rules Function), etc.).

[0103] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. By way of example and not limitation, "terminal device" can refer to a mobile terminal, user equipment (UE), or other suitable device. A UE can be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). Terminal devices can include, but are not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop installed devices (LME), USB dongles, smart devices, wireless client devices (CPE), etc. In the following description, the terms "terminal device," "terminal," "user equipment," and "UE" are used interchangeably. As an example, a terminal device may refer to a UE configured to communicate according to one or more communication standards (such as 3GPP's LTE and / or NR standards) promulgated by the 3rd Generation Partnership Project (3GPP). As used herein, a "User Equipment" or "UE" may not necessarily have a "user" in relation to a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a communication network, a terminal device may be designed to send information to the network according to a predetermined schedule. Conversely, a UE may refer to a device intended for sale to a human user or operated by a human user but which may not initially be associated with a particular human user.

[0104] As yet another example, in the Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device can be a machine-to-machine (M2M) device, which in the 3GPP context can be referred to as a machine-type communication (MTC) device. As a specific example, a terminal device can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (such as refrigerators, televisions), personal wearable devices (such as watches), etc. In other cases, a terminal device can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0105] References to "an embodiment," "an embodiment," "an exemplary embodiment," etc., in the specification indicate that the described embodiment may include a specific feature, structure, or characteristic, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it can be assumed that implementing such a feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art, whether explicitly described or not.

[0106] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0107] As used herein, the phrase “at least one of A and / or B” should be understood as “A only, B only, or both A and B”. The phrase “A and / or B” should be understood as “A only, B only, or A and B”.

[0108] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used herein, the terms “comprising,” “including,” “having,” and / or “containing” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0109] It should be noted that the terms used in this article are for the convenience of describing and distinguishing nodes, devices, or networks. As technology develops, other terms with similar or identical meanings may also be used.

[0110] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0111] Figure 1 This is an example diagram illustrating the physical resource grid of a communication system.

[0112] Mobile broadband will continue to drive the demand for higher total service capacity and higher achievable end-user data rates in wireless access networks. Some future scenarios will require localized data rates of up to 10 Gbps. These demands for very high system capacity and very high end-user data rates can be met by networks where the distance between access nodes ranges from a few meters in indoor deployments to approximately 50 meters in outdoor deployments—an infrastructure density significantly higher than today's densest networks. The wide transmission bandwidth required to provide data rates of up to 10 Gbps and above may only be available from spectrum allocations in the millimeter-wave band. High-gain beamforming, typically achieved using array antennas, can be used to mitigate the increased path loss at higher frequencies. Such networks include, for example, new radio (NR) systems.

[0113] NR supports different sets of use cases and different sets of deployment scenarios. The latter includes deployments at low frequencies (hundreds of MHz) and very high frequencies (tens of GHz). NR Rel-15 defines two operating frequency ranges: FR (frequency range) 1 from 410 MHz to 7125 MHz, and FR2 from 24.250 GHz to 52.6 GHz. 3GPP (3rd Generation Partnership Project) RAN (Radio Access Network) is (in NR Rel-17) investigating how best to support NR operation on FR2 frequencies, from 52.6 GHz to 71 GHz; this research project includes the following objectives:

[0114] The study uses existing DL (downlink) / UL (uplink) NR waveforms to support the changes required for operation between 52.6 GHz and 71 GHz;

[0115] The study examines the applicable set of parameters, including subcarrier spacing, channel bandwidth (including maximum bandwidth), and their impact on the FR2 physical layer design, to support system functionality that takes into account practical RF impairments [RAN1, RAN4].

[0116] Identify potential critical issues with the physical signal / channel, if any [RAN1].

[0117] The study investigates channel access mechanisms, considering potential interference to / from other nodes, and assumes beam-based operation to comply with regulatory requirements for unlicensed spectrum applicable between 52.6 GHz and 71 GHz [RAN1].

[0118] Note: Identifying potential interference effects (if identified) may require interference mitigation solutions as part of the channel access mechanism.

[0119] like Figure 1As shown, similar to LTE (Long Term Evolution), NR uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink (i.e., from network nodes, gNB, eNB, or base stations to user equipment or UE). The basic NR physical resources on the antenna ports can therefore be considered as follows: Figure 1 The time-frequency grid shown illustrates a resource block (RB) within a 14-symbol time slot. A resource block corresponds to 12 consecutive subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain, starting from 0 at one end of the system bandwidth. During one OFDM symbol interval, each resource element corresponds to one OFDM subcarrier.

[0120] Different subcarrier spacing values ​​are supported in NR. The supported subcarrier spacing values ​​(also known as different parameter sets) are given by Δf = (15 × 2^μ) kHz, where μ ∈ (0, 1, 2, 3, 4). Δf = 15 kHz is the basic (or reference) subcarrier spacing also used in LTE.

[0121] In the time domain, downlink and uplink transmissions in NR are organized into 1ms-long subframes, each similar to LTE. A subframe is further divided into multiple time slots of equal duration. The time slot length for a subcarrier spacing Δf = (15 × 2 μ) kHz is 1 / 2 μms. For Δf = 15 kHz, each subframe has only one time slot, and each time slot consists of 14 OFDM symbols.

[0122] Downlink transmission is dynamically scheduled; that is, in each time slot, the gNB sends downlink control information (DCI) about which UE (User Equipment) to send data to and on which resource blocks in the current downlink time slot to send that data. This control information is typically transmitted in the preceding one or two OFDM symbols of each time slot in the NR. The control information is carried on the Physical Control Channel (PDCCH), and the data is carried on the Physical Downlink Shared Channel (PDSCH). The UE first detects and decodes the PDCCH, and if the PDCCH is successfully decoded, the UE decodes the corresponding PDSCH based on the downlink allocation provided by the decoded control information in the PDCCH.

[0123] In addition to PDCCH and PDSCH, other channels and reference signals are also transmitted in the downlink, including SSB (Synchronization Block) and CSI-RS (Channel State Information-Reference Signal).

[0124] Uplink data transmission carried on the Physical Uplink Shared Channel (PUSCH) can also be dynamically scheduled by the gNB by sending a DCI (Distributed Control Information Center). The DCI (sent in the DL region) always indicates the scheduling time offset so that the PUSCH can be transmitted in the time slots of the UL region.

[0125] As described in Section 5.4.5 of 3GPP TS 38.321 V 16.0.0, the Buffer Status Report (BSR) procedure is used to provide the serving gNB with information about the amount of UL data in the MAC (Media Access Control) entity. In the case of IAB (Integrated Access and Backhaul), the IAB-MT (Mobile Terminal) also uses it to provide its parent IAB-DU (Distributed Unit) with information about the amount of data expected to arrive at the IAB node from the MAC (Media Access Control) entities of its child nodes and / or UEs connected to it. This BSR is called a preemptive BSR.

[0126] For any BSR other than a preemptive BSR, the RRC configures the following parameters to control the BSR:

[0127] -periodicBSR-Timer;

[0128] -retxBSR-Timer (Retransmission BSR Timer);

[0129] -logicalChannelSR-DelayTimerApplied (Logical Channel SR - Delay Timer Applied);

[0130] -logicalChannelSR-DelayTimer (Logical Channel SR - Delay Timer);

[0131] -logicalChannelSR-Mask;

[0132] -logicalChannelGroup.

[0133] Each logical channel can be assigned to an LCG using a logicalChannelGroup. The maximum number of LCGs is eight. The MAC entity determines the amount of UL data available for each logical channel based on a data volume calculation process.

[0134] A BSR other than a preemptive BSR will be triggered if any of the following events occur:

[0135] - UL data for logical channels belonging to the LCG is available to the MAC entity; and, or

[0136] - This UL data belongs to a logical channel whose priority is higher than that of any logical channel containing available UL data belonging to any LCG; or

[0137] - None of the logical channels belonging to the LCG contain any usable UL data.

[0138] In this context, BSR will be referred to as "regular BSR" below;

[0139] - When UL resources are allocated and the number of padding bits is equal to or greater than the size of the Buffer Status Report MAC CE plus its subheading, the BSR will be referred to as the "Padding BSR" below.

[0140] -retxBSR-Timer times out, and at least one logical channel belonging to the LCG contains UL data. In this case, the BSR is referred to as "regular BSR" below.

[0141] -periodicBSR-Timer timeout, in which case the BSR will be referred to as "periodic BSR" below.

[0142] Note 1: When multiple logical channels simultaneously experience a regular BSR trigger event, each logical channel triggers a separate regular BSR.

[0143] If configured, a preemptive BSR can be triggered for specific IAB-MT cases if any of the following events occur:

[0144] - Provide UL licenses to sub-IAB nodes or UEs;

[0145] - Receive BSR from sub-IAB node or UE.

[0146] For a standard BSR, the MAC entity should:

[0147] 1> If the BSR is triggered for a logical channel whose logicalChannelSR-DelayTimerApplied is configured as true by the upper layer:

[0148] 2> Start or restart logicalChannelSR-DelayTimer.

[0149] 1> Otherwise:

[0150] 2> If it is running, stop logicalChannelSR-DelayTimer.

[0151] For regular and periodic BSRs, the MAC entity should:

[0152] 1> If a MAC PDU containing a BSR is to be constructed when multiple LCGs have data available for transmission:

[0153] 2> Report a long BSR for all LCGs with data available for transmission.

[0154] 1> Otherwise:

[0155] 2> Report a short BSR.

[0156] For filling BSRs, the MAC entity should:

[0157] 1> If the number of padding bits is equal to or greater than the size of the short BSR plus its sub-header, but less than the size of the long BSR plus its sub-header:

[0158] 2> If multiple LCGs have data available for transfer when the BSR is being constructed:

[0159] 3> If the number of padding bits equals the short BSR plus the size of its subheading:

[0160] 4> Report a short truncated BSR for the LCG with the highest priority logical channel that has data available for transmission.

[0161] 3> Otherwise:

[0162] 4> Report long truncated BSRs of LCGs, which have logical channels with data available for transmission. Among these LCGs, they follow descending order of the highest priority logical channel (with or without data available for transmission), and if the priorities are the same, they are ordered in ascending order of LCGID.

[0163] 2> Otherwise:

[0164] 3> Report a short BSR.

[0165] 1> Otherwise, if the number of padding bits is equal to or greater than the length of the BSR plus the size of its subheading:

[0166] 2> Report a long BSR for all LCGs with data available for transmission.

[0167] For preemptive BSRs, the MAC entity should:

[0168] 1> Report preemptive BSR.

[0169] For a BSR triggered by a retxBSR-Timer timeout, the MAC entity considers the logical channel that triggered the BSR to be the highest priority logical channel with data available for transmission at the time the BSR was triggered.

[0170] The MAC entity should:

[0171] 1> If the buffer status reporting procedure determines that at least one BSR other than a preemptive BSR has been triggered and has not been canceled:

[0172] 2> If, as a result of logical channel prioritization, the UL-SCH resource is available for a new transmission and the UL-SCH resource can accommodate the BSR, MAC, CE, and their sub-headers:

[0173] 3> Instructions for generating BSR MAC CE during multiplexing and assembly processes;

[0174] 3> Start or restart periodicBSR-Timer unless all generated BSRs are long or short truncated BSRs;

[0175] 3> Start or restart retxBSR-Timer.

[0176] 2> If a regular BSR has been triggered and logicalChannelSR-DelayTimer is not running:

[0177] 3> If there are no UL-SCH resources available for the new transmission; or

[0178] 3> If the MAC entity has a configured uplink license and triggers a regular BSR for a logical channel whose logicalChannelSR-Mask is set to false; or

[0179] 3> If the UL-SCH resources available for the new transmission do not meet the LCP mapping constraints configured for the logical channel that triggered the BSR (see section 5.4.3.1):

[0180] 4> Trigger a scheduling request.

[0181] 1> If the buffer status reporting procedure determines that at least one preemptive BSR has been triggered and not canceled:

[0182] 2> If, as a result of logical channel prioritization, the UL-SCH resource is available for a new transmission, and the UL-SCH resource can accommodate a preemptive BSR MAC CE plus its sub-header:

[0183] 3> Instructs the multiplexing and assembly process to generate a preemptive BSR MAC CE.

[0184] 2> Otherwise:

[0185] 3> Trigger a scheduling request.

[0186] Note 2: The UL-SCH resource is considered available if the MAC entity has an active configuration for any type of configured uplink license, or if the MAC entity has received a dynamic uplink license, or if both of these conditions are met. If the MAC entity has determined that the UL-SCH resource is available at a given point in time, this does not need to imply that the UL-SCH resource is available at that point in time.

[0187] For cases where a preemptive BSR is being sent, a MAC PDU can contain one BSR MACCE for the preemptive BSR and one BSR MAC CE for a BSR other than the preemptive BSR. A MAC PDU that does not contain a BSR MAC CE for the preemptive BSR can contain at most one BSR MAC CE, even if multiple events trigger the BSR. Regular BSRs and periodic BSRs should take precedence over filling BSRs.

[0188] Once permission is received to transmit new data on any UL-SCH, the MAC entity will restart the retxBSR-Timer.

[0189] When the UL clearance can accommodate all pending data available for transmission but is insufficient to accommodate a BSR MAC CE plus its sub-header, all triggered BSRs except for the preemptive BSR can be cancelled. When transmitting a MAC PDU (Protocol Data Unit), regardless of any LBT (Listen-After-Speak) failure indication from a lower layer, all BSRs except those triggered before MAC PDU assembly should be cancelled, and this PDU includes a long or short BSR MAC CE containing the buffer state up to (and including) the last event that triggered a BSR before MAC PDU assembly. When a MAC PDU is transmitted and this PDU includes the corresponding preemptive BSR MAC CE, the preemptive BSR should be cancelled.

[0190] Note 3: MAC PDU assembly can occur at any point in time between uplink granted reception and the actual transmission of the corresponding MAC PDU. BSR and SR can be triggered after the assembly of a MAC PDU containing a BSR MAC CE, but before the transmission of that MAC PDU. Alternatively, BSR and SR can be triggered during MAC PDU assembly.

[0191] Note 4: Preemptive BSR can be used for dual-connectivity IAB nodes. The network implementation determines one or more associated MAC entities and the associated expected data volume. For dual-connectivity IAB nodes, ambiguity may exist in the preemptive BSR calculation and interpretation when BH (backhaul) RLC (radio link control) channels mapped to different egress cell groups are not mapped to different ingress LCGs.

[0192] Note 5: If the HARQ (Hybrid Automatic Repeat Request) process is configured with a cg-RetransmissionTimer, and if the BSR has been included in the MAC PDU for transmission by the HARQ process but has not yet been transmitted by the lower layer, then the BSR content is handled depending on the UE implementation.

[0193] Figure 2A This is an example structure of elements in a BSR; Figure 2B This is another exemplary structure for elements in a BSR. The 5-bit and 8-bit buffer size fields are respectively as follows: Figure 2A and 2B As shown in the image.

[0194] Buffer Status Report (BSR) MAC CE includes any:

[0195] - Short BSR format (fixed size); or

[0196] - Long BSR format (variable size); or

[0197] - Short Truncated BSR format (fixed size);

[0198] - Long Truncated BSR format (variable size); or

[0199] - Pre-emptive BSR format (variable size).

[0200] The BSR format is identified by a MAC subheader with an LCID, including the fields defined in the BSR MAC CE as follows:

[0201] -LCG ID: The Logical Channel Group ID field identifies the logical channel group whose buffer status is being reported. The field is 3 bits long;

[0202] -LCGi: For long BSR format, this field indicates the presence of the buffer size field for logical channel group i. An LCGi field set to 1 indicates that the buffer size field for logical channel group i is reported. An LCGi field set to 0 indicates that the buffer size field for logical channel group i is not reported. For long truncated BSR format, this field indicates whether data is available for logical channel group i. An LCGi field set to 1 indicates that logical channel group i has available data. An LCGi field set to 0 indicates that logical channel group i has no available data.

[0203] - Buffer Size: The buffer size field is calculated according to the data volume calculation process in TS (Technical Specification) 38.322 V 16.0.0 and 38.323 V 16.0.0 after the MAC PDU has been constructed (i.e., after the logical channel prioritization process, which may result in a value of zero for the buffer size field). The data volume is indicated in bytes. The size of the RLC and MAC headers is not considered in the buffer size calculation. This field is 5 bits long for short BSR and short truncated BSR formats. This field is 8 bits long for long BSR and long truncated BSR formats. Tables 1 and 2 show the values ​​for the 5-bit and 8-bit buffer size fields, respectively. For long BSR and long truncated BSR formats, the buffer size field is included in ascending order based on LCGi. For long truncated BSR formats, the number of included buffer size fields has been maximized without exceeding the number of padding bits. For preemptive BSRs, the buffer size field identifies the total amount of IAB-MT data expected to arrive at the node where the preemptive BSR is triggered. The preemptive BSR format is the same as the long BSR format.

[0204] Note 1: For preemptive BSR, if configured, the LCG to be reported, the expected data volume calculation, the exact time for reporting preemptive BSR, and the associated LCH are determined by the implementation.

[0205] Note 2: To determine the expected changes in IAB-MT buffer occupancy (which will be reported as a preemptive BSR), the mapping of LCG between the ingress and egress links of the IAB node is determined based on the implementation.

[0206] Note 3: The number of buffer size fields in long BSR and long truncated BSR formats can be zero.

[0207] Table 1. Buffer size levels (in bytes) in the 5-bit buffer size field of 3GPP TS 38.321 V 16.0.0

[0208]

[0209] Table 2 shows the buffer size levels (in bytes) of the 8-bit buffer size field in 3FPP TS 38.321 V 16.0.0.

[0210]

[0211]

[0212]

[0213] Figure 3 This is an exemplary flowchart illustrating UL transmission.

[0214] like Figure 3 As shown, the transmission delay of UL packets using dynamic licensing can be estimated by considering the following delay components:

[0215] UL Delay = SR Transmission Time + SR Processing Time + Permitted Transmission Time + UE Processing / Encoding Time + Data Transmission Time + gNB Processing / Decoding (1)

[0216] Preemptive BSRs are introduced in NR Rel-16 for Integrated Access and Backhaul-Mobility Termination (IAB-MT) to indicate to their parent IAB node that new data will be received from their child node. As described in Section 5.4.5 of TS 38.321 V 16.0.0, for IAB-MT, a preemptive BSR can be triggered under the following conditions:

[0217] -UL licenses are provided to sub-IAB nodes or UEs;

[0218] - Receive BSR from sub-IAB node or UE.

[0219] For IAB-MT, preemptive BSR is an optional feature. This feature is activated if IAB-MT receives the RRC (Radio Resource Control) parameter usePreBSR (use preemptive BSR) set to "True".

[0220] By utilizing the preemptive BSR in the IAB-MT, its parent node can schedule the permission for this IAB-MT before new data arrives. Therefore, the delay caused by SR / BSR transmission to its parent node is avoided. In other words, the delay components "SR transmission time + SR processing time + permission transmission time + UE processing time" in formula (1) can be saved.

[0221] However, information about the accurate buffer size in the logical channel of the sub-IAB node or UE is still necessary. That is, for the sub-IAB node, or especially the UE, "SR transmission time + SR processing time + permitted transmission time + UE processing time" is unavoidable.

[0222] Figure 4A This is an exemplary flowchart illustrating a method performed at a terminal device according to an embodiment of the present disclosure. Optional steps are shown in dashed boxes.

[0223] like Figure 4A As shown, the method performed at the terminal device may include: S101, predicting the buffer size associated with the data to be transmitted; and S102, sending a buffer status report (BSR) including the predicted buffer size to the network node.

[0224] According to embodiments of this disclosure, a terminal device can predict the buffer size associated with the data to be transmitted and send a Buffer Status Report (BSR) including the predicted buffer size to a network node. That is, instead of actually allocating data to any logical channel and then calculating the specific buffer size in that logical channel, the BSR can be predicted and transmitted to the network node. This eliminates the need to wait for data to be allocated to any logical channel before the BSR, thereby reducing data transmission latency from the terminal device to the network node, regardless of whether the terminal device is an IAB-MT.

[0225] According to embodiments of this disclosure, the predicted buffer size can be obtained in any type of terminal device. This is beneficial for future 3GPP releases and even 6G (sixth generation) to support extremely high data rates in UL.

[0226] In embodiments of this disclosure, the terminal device sends a scheduling request (SR) for a buffer scheduler (BSR). Specifically, the terminal device sends the SR according to a specific SR configuration for the predicted buffer size.

[0227] In embodiments of this disclosure, the SR configuration is received from a network node or pre-configured. For example, according to any communication standard or 3GPP TS, the SR configuration may be fixed in the terminal device.

[0228] In embodiments of this disclosure, the terminal device transmits a BSR in an uplink shared channel (UL-SCH), which may correspond to an SR that is licensed or already available to the terminal device.

[0229] Specifically, the predicted buffer size is included in the Media Access Control (MAC) control element (CE).

[0230] In embodiments of this disclosure, the BSR is configured for a logical channel, or a logical channel group.

[0231] In embodiments of this disclosure, the BSR is configured based on the priority of a logical channel or logical channel group. That is, a logical channel or logical channel group with a higher priority can be configured with a BSR that includes a predicted buffer size.

[0232] In embodiments of this disclosure, the terminal device includes a user equipment (UE).

[0233] In embodiments of this disclosure, the method further includes: S103, receiving permission for data to be transmitted; and S104, transmitting the data.

[0234] According to embodiments of this disclosure, a terminal device can receive permission to transmit data regardless of whether the data is already ready in the logical channel. Therefore, as long as the data is ready in the logical channel, it can be transmitted without any delay.

[0235] In embodiments of this disclosure, the prediction is based on at least one of the following: the size, type, content, or required transmission rate of the data.

[0236] According to embodiments, the terminal device can make a prediction immediately upon obtaining the data itself or at least some information about the data (e.g., size, type, content, or required transmission rate). For example, the terminal device could be a mobile phone transmitting a multimedia file selected by the user, or a vehicle automatically transmitting status report messages. When a multimedia file is selected, or when the text of the status report message is generated, or even before the data is assigned to a specific logical channel, the terminal device can predict the buffer size and send a BSR including the predicted buffer size to reduce latency.

[0237] In embodiments of this disclosure, predictions are based on at least one of the following: input data from application behavior, user behavior, radio conditions, or service behavior.

[0238] In embodiments of this disclosure, user behavior includes mobility; and / or business behavior includes business patterns.

[0239] According to embodiments, the terminal device can even make predictions before obtaining the data itself or information about the data. For example, when a user launches social software / application, the terminal device can predict that the user is about to start a video call or upload a video blog. The terminal device can send a BSR (Broadcast Request) and receive permission in advance based on such a prediction, even before actual data is generated. Then, when the terminal device generates the data stream for the video call or video blog and allocates it to any logical channel, it can send it immediately. Furthermore, based on the transmission rate of the continuous data stream, permission for future transmission portions of the data stream can always be obtained in advance, which can reduce latency and improve the continuity of video calls / video blogs.

[0240] In other examples, predictions can be based on user mobility, such as the user's location (e.g., in an office, at home, or at an amusement park). Predictions can also be based on the quality of radio conditions. Furthermore, predictions can be based on any information about the service pattern, such as whether it is mMTC (massive machine-type communication), URLLC (ultra-reliable low-latency communication), or eMBB (enhanced mobile broadband). In other examples, the service pattern can be reflected by the service bit rate range, packet arrival interval, packet size, etc. A specific service type may have a specific bit rate range and / or packet arrival interval and / or packet size. Based on such information, the terminal device is able to determine the associated service type.

[0241] In embodiments of this disclosure, the prediction is performed using artificial intelligence algorithms.

[0242] In embodiments of this disclosure, predictions are made using a Long Short-Term Memory (LSTM) neural network model, an Arima machine learning model, and / or reinforcement learning.

[0243] According to artificial intelligence algorithms, even when it is difficult to obtain a fixed / accurate mathematical mapping relationship, continuous prediction can be made automatically based on multiple environmental parameters.

[0244] like Figure 4A As shown, the method further includes: S105, predicting the probability associated with the predicted buffer size.

[0245] Such a probability (i.e., the confidence level of the prediction) can serve as the basis for further actions by terminal devices and network nodes to avoid allocating communication resources for data with a fairly low probability of transmission.

[0246] In embodiments of this disclosure, the BSR includes the probability, enabling network nodes to determine whether to grant permission to the terminal device based on the probability.

[0247] In embodiments of this disclosure, the terminal device sends a BSR when the probability is equal to or greater than a threshold. That is, when the probability is quite low, the terminal device does not send such a prediction buffer size at all.

[0248] In embodiments of this disclosure, the threshold is configurable or fixed.

[0249] In embodiments of this disclosure, the BSR further includes: the predicted time point or time window for transmitting data. Specifically, the BSR further includes: the probability of the predicted time point or time window for transmitting data.

[0250] like Figure 4A As shown, the method further includes: S106, reporting the terminal device's ability to support BSR; S107, receiving BSR prediction configuration for the terminal device or for multiple terminal devices; S108, receiving an indication of whether BSR, including the predicted buffer size, is enabled or disabled; S109, when BSR, including the predicted buffer size, is disabled, sending a buffer status report (BSR) including the buffer size associated with the data allocated to the logical channel of the terminal device.

[0251] In embodiments of this disclosure, the indication includes a threshold for the probability of the predicted buffer size.

[0252] According to embodiments of this disclosure, the BSR prediction configuration can be specific to a terminal device or shared by multiple terminal devices. Furthermore, when the prediction buffer size is disabled, the terminal device can still use a regular BSR with the actual buffer size.

[0253] In embodiments of this disclosure, the BSR also includes the buffer size associated with the data allocated to the logical channel. That is, the BSR may also include the actual buffer size in the logical channel containing the allocated data.

[0254] Specifically, the BSR includes a predefined Logical Channel Identifier (LCID) to indicate the predicted buffer size, distinguishing it from the actual buffer size. Alternatively or additionally, the BSR may contain specific fields / bits to indicate which buffer size is predicted.

[0255] Figure 4B It is shown Figure 4A An exemplary flowchart of the additional steps of the method shown.

[0256] like Figure 4BAs shown, the method further includes: S110, starting a timer after sending a BSR including the predicted buffer size; S111, stopping the timer after receiving permission; S112, restarting the timer if the predicted buffer size is updated and a BSR including the predicted buffer size is retransmitted; and / or S113, retransmitting the predicted BSR when the timer times out.

[0257] According to embodiments of this disclosure, a terminal device may use at least one timer for predicting the buffer size. For example, if the timer does not time out, the same predicted buffer size cannot be retransmitted. However, if a new predicted or actual buffer size, different from the one sent, is obtained before permission, the new predicted or actual buffer size can be sent and the timer can be restarted.

[0258] According to embodiments of this disclosure, the principles and details regarding how to provide the predicted buffer size have been described above. In such embodiments, latency caused by BSR in the communication system can be reduced.

[0259] Figure 5A This is an exemplary flowchart illustrating a method performed at a network node according to an embodiment of the present disclosure.

[0260] like Figure 5A As shown, the method performed at the network node may include: S201, receiving a buffer status report (BSR) including a predicted buffer size associated with data to be received from the terminal device; and S202, sending permission for the data based on the received BSR.

[0261] In embodiments of this disclosure, the method further includes: S203, receiving data.

[0262] In embodiments of this disclosure, network nodes include base stations.

[0263] According to embodiments of this disclosure, a network node can grant communication resources to a terminal device based on a predicted buffer size. That is, instead of waiting for the actual buffer size associated with data allocated to a logical channel for the terminal device, the network node can send the grant in advance. Thus, the time spent waiting for data to be allocated to any logical channel before the BSR is unnecessary, thereby reducing latency in data transmission from the terminal device to the network node.

[0264] like Figure 5A As shown, the method further includes: S204, receiving a probability associated with the predicted buffer size; and S205, configuring a priority for data transmission based on the probability. This priority is associated with the probability. For example, the higher the probability, the higher the priority may be. Furthermore, the priority may be proportional to the probability.

[0265] According to embodiments of this disclosure, data transmission with a higher probability of prediction can be permitted earlier than data transmission with a lower probability of prediction. This can then improve the efficiency of communication resources.

[0266] like Figure 5A As shown, the method further includes: S206, receiving the terminal device's ability to support a BSR including a predicted buffer size; S207, sending a BSR prediction configuration for the terminal device or multiple terminal devices; S208, sending an indication of whether the BSR including the predicted buffer size is enabled or disabled; and S209, when the BSR including the predicted buffer size is disabled, receiving a buffer status report (BSR) including the buffer size associated with the data allocated to the logical channel of the terminal device.

[0267] According to embodiments of this disclosure, the BSR prediction configuration can be specific to a terminal device or shared by multiple terminal devices. Furthermore, when the prediction buffer size is disabled, the terminal device can still use a regular BSR with the actual buffer size.

[0268] Figure 5B It is shown Figure 5A An exemplary flowchart of the additional steps of the method shown.

[0269] like Figure 5B As shown, the method further includes: S210, scheduling another terminal device based on the predicted buffer size. For example, the other terminal device may be located near the current terminal device.

[0270] According to embodiments of this disclosure, network nodes can also proactively schedule other terminal devices adjacent to the terminal device (e.g., in the same cell, office, or home) based on predictions from the terminal device. The latency of other terminal devices can be further reduced, and they can anticipate planned communication resources even before they send their BSRs.

[0271] Figure 6 This is an exemplary flowchart illustrating an overview of a process for sending a BSR according to an embodiment of the present disclosure.

[0272] like Figure 6 As shown, in S601, the UE can be configured with a predicted BSR, for example, the UE is capable of and enabled to send a BSR that includes the predicted buffer size. Then the process proceeds to S602.

[0273] In S602, the UE predicts the arrival of new data and determines whether the probability of the new data arriving is higher than or equal to a threshold X%. If yes, the process proceeds to S603. If no, the process proceeds to S604.

[0274] In S603, the UE triggers a BSR prediction. Then the process proceeds to S605.

[0275] In S605, the UE determines whether there are available UL-SCH resources. If yes, the process proceeds to S607. If no, the process proceeds to S606.

[0276] In S606, the UE triggers the SR. Then the process proceeds to S608.

[0277] In S608, the UE receives a new license for the BSR from the gNB. The process then proceeds to S607.

[0278] In S607, the UE generates a predicted BSRMAC CE, which includes the predicted buffer size associated with possible new data, and sends it to the gNB. The process then proceeds to S609.

[0279] In S609, the UE receives a new permission for data from the gNB. The process then proceeds to S610.

[0280] In S610, the UE waits for data to arrive. Then, when the data arrives, the process proceeds to S611.

[0281] In S611, the UE sends a normal / regular BSR plus data to the gNB.

[0282] In S604, the UE waits for data to arrive. Then, when the data arrives, the process proceeds to S612.

[0283] In S612, the UE triggers a regular BSR. Then the process proceeds to S613.

[0284] In S613, the UE determines whether there are available UL-SCH resources. If yes, the process proceeds to S614. If no, the process proceeds to S615.

[0285] In S615, the UE triggers the SR. Then the process proceeds to S616.

[0286] In S616, the UE receives a new license for the BSR from the gNB. The process then proceeds to S614.

[0287] In S614, the UE generates a standard BSR MACCE that includes the actual buffer size associated with the arriving new data and sends it to the gNB. The process then proceeds to S617.

[0288] In S617, the UE receives a new permission for data from the gNB. The process then proceeds to S618.

[0289] In S618, the UE sends data to the gNB.

[0290] By using the aforementioned predictive BSR, the embodiments of this disclosure significantly extend preemptive BSR functionality to non-IAB scenarios. In IAB scenarios, once data arrives at one of the downstream nodes, it can generally be determined that data will be present at the UL node. In other scenarios, determining that UL data will be present before it reaches the UL UE buffer is not so easy. However, in many cases, it is possible to predict that data will arrive, and this can be exploited using preemptive BSR.

[0291] According to embodiments of this disclosure, when configuring predictive BSR for a UE, at a high level, the algorithm can be:

[0292] 1. Configure the UE in the gNB to apply predictive BSR.

[0293] Configuration can include the prediction algorithm, when / how often the prediction is completed (e.g., per time slot), trigger threshold (prediction data volume, confidence level), and timer settings (prediction BSR - disable timer).

[0294] 2. The UE initiates a prediction of the amount of data in the UL buffer.

[0295] If the predicted buffer level exceeds the threshold, a predicted BSR is triggered.

[0296] -If UL resources for sending the predicted BSR are available

[0297] - Send Predicted BSR

[0298] -Start the prediction disable timer

[0299] -otherwise

[0300] - Send an SR, and in the permission received as a response to the SR, send a predicted BSR.

[0301] 3. When the predicted BSR is sent, the algorithm continues from (2).

[0302] No new prediction BSR can be sent until the prediction prohibition timer expires (or the prediction change exceeds a certain threshold).

[0303] According to embodiments of this disclosure, SR-BSR-data latency is reduced by triggering a predicted BSR earlier than triggering a normal / regular BSR. It also allows control over the amount or number of predicted BSRs sent.

[0304] Furthermore, in the following embodiments, more details will be described regarding how to design the mechanism for predictive BSR. These embodiments are applicable to both IAB and non-IAB scenarios. The term preemptive BSR can also be used interchangeably as predictive BSR or early BSR, etc. Any similar terms are equally applicable. A normal / regular BSR refers to a BSR that carries the actual data buffer size of the LCH or LCG. It can be any of the following existing BSR MAC CEs.

[0305] - Short BSR (fixed size); or

[0306] - Long BSR (variable size); or

[0307] - Short truncated BSR (fixed size);

[0308] - Long truncated BSR (variable size);

[0309] In the first embodiment, when a preemptive BSR is configured for the UE, a preemptive BSR can be triggered if any of the following events occur:

[0310] - The UE anticipates that new data will arrive, which triggers a regular BSR upon arrival;

[0311] -When the UE determines that new data will arrive, this will trigger a regular BSR.

[0312] In the second embodiment, when a preemptive BSR is configured for the UE, there exists a prediction function implemented at the UE to predict whether and / or when new data will arrive at the UE, which will trigger a regular BSR upon arrival. The prediction function can use input data from application behavior, user behavior (e.g., mobility), radio conditions, service behavior (e.g., service patterns), etc., to estimate the arrival of new data with a probability of X%.

[0313] Based on the above embodiments, the prediction algorithm configured by the gNB for the UE includes the conditions under which the algorithm applies. This could be, for example, when the UE changes from IDLE to ACTIVE, or when the UE screen is unlocked. It should be understood that the UE can also perform predictions in the IDLE state.

[0314] In the third embodiment, when a preemptive BSR is configured for the UE, a preemptive BSR can be triggered if the UE predicts that new data will arrive at the UE with a probability of >= X% (which will trigger a regular BSR), wherein X is configured to the UE or hardcoded in any standard or specification.

[0315] In the fourth embodiment, when a preemptive BSR is configured for the UE, if the UE determines that new data will arrive at the UE according to the corresponding service mode (which will trigger a regular BSR), a preemptive BSR can be triggered.

[0316] In the fifth embodiment, for the UE MAC entity, if at least one preemptive BSR is triggered and not canceled,

[0317] If the UL-SCH resource is available for a new transmission and the UL-SCH resource can accommodate a preemptive BSRMAC CE with its child header:

[0318] >Instructions for multiplexing and reassembly processes generate preemptive BSR MAC CE.

[0319] Otherwise:

[0320] > Trigger scheduling request.

[0321] In the sixth embodiment, when a preemptive BSR is configured for the UE, if at least one preemptive BSR is triggered and not canceled, the UE can be configured with a specific SR configuration, and there are no UL-SCH resources available for new transmissions that can accommodate the preemptive BSR MAC CE plus its sub-header. The UE MAC can use this specific SR configuration to trigger a scheduling request.

[0322] In the seventh embodiment, preemptive BSR can be configured per LCH or LCG (Logical Channel or Logical Channel Group). In this case, prediction of new data can be performed per LCH or LCG. One LCH or LCG associated with a high-priority index can be configured with preemptive BSR, while another LCH or LCG associated with a low-priority index may not be configured with preemptive BSR. An LCH / LCG priority index threshold can be configured for the UE. In this case, preemptive BSR can be applied to LCH / LCGs associated with priority indices above the configured threshold, while preemptive BSR will not be applied to LCH / LCGs associated with priority indices below the configured threshold.

[0323] In the eighth embodiment, preemptive BSR MAC CE and regular BSR MAC CE (i.e., the actual buffer size carrying LCH / LCG) can be included in the same MAC PDU.

[0324] In the ninth embodiment, other ordinary BSR MAC CEs are not allowed to be carried in the same MACPDU as preemptive BSRs.

[0325] In the tenth embodiment, the predicted or determined buffer size (BS) at the triggering of a preemptive BSR for an LCH or LCG and the actual BS at the triggering of a regular BSR for another LCG or LCG can be included together in the same BSR MAC CE. In this case, a new BSR MAC CE format can be defined accordingly. The new format may include specific fields / bits, or LCH ID values, to indicate which is the prediction and which is the actual value.

[0326] In the eleventh embodiment, a UE capability bit is defined to indicate whether the UE supports preemptive BSR.

[0327] In the twelfth embodiment, whenever the UE has predicted that data of a certain amount Y will arrive with a probability of X%, the UE is allowed to trigger a preemptive BSR, regardless of the values ​​of X and / or Y. In this case, the UE can include information X or X and Y to the gNB via a preemptive BSR MACCE. Since the existing preemptive BSR MACCE does not include a prediction probability field, a new preemptive BSR MACCE format can be defined accordingly. Upon receiving the BSR, the gNB can decide whether to allocate resources to the UE; and if so, whether to allocate sufficient resources to accommodate the UE's possible data or only a portion of the resources (e.g., X% of Y), since the prediction from the UE side is not 100%. In this new preemptive BSR MACCE format, the UE can include the time parameter it needs to allocate for its transmission. The time can be a specific future time symbol / slot or time window. The time parameter can also have an associated probability, which describes the probability that data will arrive in the buffer at that possible moment.

[0328] In the thirteenth embodiment, for the UE, the gNB can configure the priority of data arrival predictions in the BSR report. For example, data arrival probabilities between 0 and P% will be classified as low priority, percentages between P% and Q% will be classified as medium priority, and percentages between Q% and 100% will be classified as high priority, where 0% is the lowest priority. <P<Q<100。

[0329] In the fourteenth embodiment, the preemptive BSR MAC CE carries an estimated / predicted buffer size (BS) for configuring the LCH / LCG with the preemptive BSR.

[0330] In the fifteenth embodiment, the preemptive BSR MAC CE carries an estimated / predicted buffer size (BS) for an LCH configured with a preemptive BSR and at least one BS (i.e., the actual BS of available data) for an LCH / LCG not configured with a preemptive BSR.

[0331] In the sixteenth embodiment, a preemptive prohibition timer is defined. This timer starts when a preemptive BSR MACCE is sent. If the UE receives permission (in response to the preemptive BSR), the timer stops. While the timer is running, no new preemptive BSR MACCEs can be sent for the same LCH / LCG that triggered the original preemptive BSR. This timer is used to prevent the UL from being flooded by newly predicted preemptive BSRs.

[0332] In another embodiment, if the new prediction indication is significantly different from the previous preemptive BSR, the preemptive inhibit timer is stopped. The change may relate to the size of the predicted data, the prediction time when the data arrives, or the confidence level of the prediction (e.g., the prediction probability).

[0333] In another embodiment, a retransmission timer is used in a preemptive BSR. This is used to update forecasts in a controlled manner. Compared to a preemptive BSR disable timer, a retransmission timer can update and report previous forecasts even if the new forecast does not meet the normal trigger threshold. In this way, it can indicate that a new forecast indicates less data or a less reliable forecast than previously reported.

[0334] In another embodiment, the prediction algorithm used by the UE can be configured. In some cases, this may be a UE-specific algorithm, or it may be a specific publicly available algorithm. Algorithms available in the appropriate 3GPP specifications can be hardcoded.

[0335] In another embodiment, the UE reports the UE prediction results to the gNB.

[0336] In the above embodiments, the UE includes the conditions for the prediction to occur, such as the BSR probability X of Y bytes after time Z when the UE state changes from IDLE to ACTIVE.

[0337] In the above embodiments, the gNB can use the UE prediction report described in the above embodiments and use these parameters to configure another UE (in the same cell).

[0338] In another embodiment, in order to distinguish preemptive BSR MAC CEs from ordinary BSR MAC CEs, a new logical channel ID (LCID) is defined to identify preemptive BSR MAC CEs.

[0339] Based on these detailed embodiments of the present disclosure, it can be more clearly illustrated how to apply the specific methods of predicting BSR in different situations.

[0340] Figure 7 This is a block diagram illustrating an exemplary apparatus suitable for implementing terminal devices and network nodes according to embodiments of the present disclosure.

[0341] like Figure 7 As shown, terminal device 100 may include: processor 101; and memory 102. Memory 102 contains instructions executable by processor 101, thereby enabling terminal device 100 to: predict the buffer size associated with data to be transmitted; and send a buffer status report (BSR) including the predicted buffer size to network nodes.

[0342] In embodiments of this disclosure, terminal device 100 is operable to perform actions according to the embodiments described above (such as...). Figures 4A-4B The method of any of the ones shown in 6.

[0343] like Figure 7 As shown, network node 200 may include: processor 201; and memory 202. Memory 202 contains instructions executable by processor 201, thereby enabling network node 200 to: receive a buffer status report (BSR) including a predicted buffer size associated with data to be received from a terminal device; and send permission for the data based on the received BSR.

[0344] In embodiments of this disclosure, terminal device 100 is operable to perform actions according to the embodiments described above (such as...). Figure 5A-6 The method of any of these (as shown).

[0345] Processors 101 and 201 can be any type of processing component, such as one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), application-specific digital logic, etc. Memory 102 and 202 can be any type of storage component, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage devices, etc.

[0346] Figure 8 This is a block diagram illustrating an apparatus / computer-readable storage medium according to embodiments of the present disclosure.

[0347] like Figure 8 As shown, a computer-readable storage medium 700 or any other type of product stores instructions 701, which, when executed by at least one processor, cause the at least one processor to perform the actions described above (such as...). Figure 4A-6 The method of any of these (as shown).

[0348] Furthermore, this disclosure may also provide a carrier containing the aforementioned computer program, wherein the carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device, such as RAM (Random Access Memory), ROM (Read Only Memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0349] Figure 9 This is a schematic diagram illustrating units for terminal devices and network nodes according to embodiments of the present disclosure.

[0350] like Figure 9 As shown, the terminal device 100 may include: a prediction unit 8101 configured to predict the buffer size associated with the data to be transmitted; and a transmission unit 8102 configured to send a buffer status report (BSR) including the predicted buffer size to a network node.

[0351] In embodiments of this disclosure, terminal device 100 is operable to perform actions according to the embodiments described above (such as...). Figures 4A-4B The method of any of the ones shown in 6.

[0352] like Figure 9 As shown, network node 200 may include: a receiving unit 8201 configured to receive a buffer status report (BSR) including a predicted buffer size associated with data to be received from a terminal device; and a sending unit 8202 configured to send permission for the data based on the received BSR.

[0353] In embodiments of this disclosure, network node 200 is operable to perform actions according to the embodiments described above (such as...). Figure 5A-6 The method of any of these (as shown).

[0354] The term “unit” may have the conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, outputs and / or display functions, and so on, such as those described herein.

[0355] Through these units, network node 100 can be deployed with any computing and storage resources from at least one network node / device / entity / apparatus associated with the communication system, without requiring a fixed processor or memory. Virtualization and network computing technologies (such as cloud computing) can be further introduced to improve the efficiency of network resource utilization and network flexibility.

[0356] The techniques described herein can be implemented by various means, such that means for implementing one or more functions of the corresponding apparatus described through embodiments include not only prior art means, but also means for implementing one or more functions of the corresponding apparatus described through embodiments, and may include separate means for each individual function, or means that can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For firmware or software, implementation can be achieved by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0357] In particular, these functional units can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualization functions instantiated on a suitable platform (e.g., on cloud infrastructure).

[0358] Figure 10 This is a schematic diagram illustrating a wireless network according to some embodiments.

[0359] Although the subjects described herein can be implemented using any suitable components in any suitable type of system, the embodiments disclosed herein are relative to wireless networks (such as...). Figure 10 The example wireless network shown is described below. For simplicity, Figure 10 The wireless network depicted only includes network 1006, network nodes 1060 (corresponding to network node 200) and 1060b, and WDs 1010, 1010b, and 1010c (corresponding to terminal device 100). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). Among the components shown, network node 1060 and wireless device (WD) 1010 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0360] Wireless networks can include any type of communications, telecommunications, data, cellular and / or radio network or other similar system and / or interface with it. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0361] Network 1006 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0362] Network node 1060 and WD 1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In various embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in communication of data and / or signals via wired or wireless connections.

[0363] As used herein, a network node is a device capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless devices and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations can be classified based on the coverage they provide (or in other words, their transmit power levels), and can then be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU) (sometimes also called a remote radio headend (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS). Other examples of network nodes include multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured to, arranged to, and / or operable to enable wireless devices to access wireless networks and / or provide access to wireless networks to wireless devices or provide some service to wireless devices that have access to wireless networks.

[0364] exist Figure 10 In the network node 1060, processing circuitry 1070, device-readable medium 1080, interface 1090, auxiliary equipment 1084, power supply 1086, power supply circuitry 1087, and antenna 1062 are included. Although in Figure 10The network node 1060 shown in the example wireless network can represent a device comprising a combination of the illustrated hardware components, but other embodiments may include network nodes having different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, although the components of network node 1060 are depicted as a single box located within a larger box or nested within multiple boxes, in practice, a network node may include multiple different physical components constituting a single illustrated component (e.g., device-readable medium 1080 may include multiple separate hard disk drives and multiple RAM modules).

[0365] Similarly, network node 1060 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each with its own respective components. In some cases where network node 1060 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In this case, each unique NodeB and RNC pair may be considered a separate network node in some circumstances. In some embodiments, network node 1060 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 1080 for different RATs), and some components may be reused (e.g., the same antenna 1062 may be shared by RATs). Network node 1060 may also include multiple sets of various illustrated components for integrating different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies) into network node 1060. These wireless technologies can be integrated into the same or different chips or chipsets and other components within the network node 1060.

[0366] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by a network node. Operations performed by the processing circuit 1070 may include: processing information acquired by the processing circuit 1070, such as by converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information; and making a determination as a result of said processing.

[0367] Processing circuitry 1070 may include a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of one or more of hardware, software, and / or coded logic operable to provide network node 1060 functionality, either alone or in conjunction with other network node 1060 components (e.g., device-readable medium 1080). For example, processing circuitry 1070 may execute instructions stored in device-readable medium 1080 or in memory within processing circuitry 1070. Such functionality may include providing any of the various wireless features, capabilities, or benefits discussed herein. In some embodiments, processing circuitry 1070 may include a system-on-a-chip (SoC).

[0368] In some embodiments, the processing circuitry 1070 may include one or more of a radio frequency (RF) transceiver circuitry 1072 and a baseband processing circuitry 1074. In some embodiments, the RF transceiver circuitry 1072 and the baseband processing circuitry 1074 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 1072 and the baseband processing circuitry 1074 may be on the same chip or chipset, board, or unit.

[0369] In some embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 1070, which executes instructions stored on memory within device-readable medium 1080 or processing circuitry 1070. In alternative embodiments, some or all of the functions may be provided by processing circuitry 1070 without executing instructions stored on separate or discrete device-readable media, such as in a hard-wired manner. In any of those embodiments, processing circuitry 1070 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 1070 alone or other components of network node 1060, but are enjoyed by network node 1060 as a whole and / or generally by end users and wireless networks.

[0370] Device-readable medium 1080 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent memory, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, optical disc (CD), or digital video disk (DVD)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by processing circuitry 1070. Device-readable medium 1080 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions that can be executed by processing circuitry 1070 and utilized by network node 1060. Device-readable medium 1080 may be used to store any calculations performed by processing circuitry 1070 and / or any data received via interface 1090. In some embodiments, processing circuitry 1070 and device-readable medium 1080 may be considered integrated.

[0371] Interface 1090 is used in wired or wireless communication of signaling and / or data between network node 1060, network 1006, and / or WD 1010. As shown, interface 1090 includes a port / terminal 1094 for sending and receiving data to and from network 1006, for example, via a wired connection. Interface 1090 also includes radio front-end circuitry 1092 that can be coupled to antenna 1062 or, in some embodiments, is part of antenna 1062. Radio front-end circuitry 1092 includes a filter 1098 and an amplifier 1096. Radio front-end circuitry 1092 can be connected to antenna 1062 and processing circuitry 1070. Radio front-end circuitry 1092 can be configured to modulate signals communicating between antenna 1062 and processing circuitry 1070. Radio front-end circuitry 1092 can receive digital data to be transmitted to other network nodes or WDs via a wireless connection. The radio front-end circuit 1092 can use a combination of filter 1098 and / or amplifier 1096 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 can collect radio signals, which are then converted into digital data by the radio front-end circuit 1092. The digital data can be passed to processing circuitry 1070. In other embodiments, the interface may include different components and / or different combinations of components.

[0372] In some alternative embodiments, network node 1060 may not include a separate radio front-end circuitry 1092; instead, processing circuitry 1070 may include radio front-end circuitry and may be connected to antenna 1062 without a separate radio front-end circuitry 1092. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1072 may be considered part of interface 1090. In other embodiments, interface 1090 may include one or more ports or terminals 1094, radio front-end circuitry 1092, and RF transceiver circuitry 1072 as part of a wireless unit (not shown), and interface 1090 may communicate with baseband processing circuitry 1074, which is part of a digital unit (not shown).

[0373] Antenna 1062 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1062 may be coupled to radio front-end circuitry 1090 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals from devices within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 1062 may be detachable from network node 1060 and can be connected to network node 1060 via an interface or port.

[0374] Antenna 1062, interface 1090, and / or processing circuitry 1070 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 1062, interface 1090, and / or processing circuitry 1070 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0375] Power supply circuitry 1087 may include or be coupled to power management circuitry and is configured to provide power to components of network node 1060 to perform the functions described herein. Power supply circuitry 1087 may receive power from power source 1086. Power source 1086 and / or power supply circuitry 1087 may be configured to provide power to the respective components of network node 1060 in a manner suitable for each component (e.g., at the voltage and current levels required by each respective component). Power source 1086 may be included in or outside of power supply circuitry 1087 and / or network node 1060. For example, network node 1060 may be connectable to an external power source (e.g., a power outlet) via input circuitry or an interface (e.g., a cable), whereby the external power source provides power to power supply circuitry 1087. As yet another example, power source 1086 may include a power source in the form of a battery or battery pack connected to or integrated into power supply circuitry 1087. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0376] Alternative embodiments of network node 1060 may include, except Figure 10 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of the network node, including any of the functions described herein and / or any functions necessary to support the topics described herein. For example, network node 1060 may include a user interface device to allow information to be input into and output from network node 1060. This allows users to perform diagnostic, maintenance, repair, and other management functions of network node 1060.

[0377] As used herein, a wireless device (WD) means a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with network nodes and / or other wireless devices. Unless otherwise stated, the term WD may be used interchangeably with User Equipment (UE) herein. Wireless communication may involve sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information over the air. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network according to a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WD include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop built-in equipment (LEE), laptop installed equipment (LME), smart devices, wireless client devices (CPE), in-vehicle wireless terminal devices, etc. A WD can support device-to-device (D2D) communication (e.g., by implementing 3GPP standards for auxiliary link communication), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case, can be referred to as a D2D communication device. As another specific example, in the Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As an example, a WD can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, a WD can represent a vehicle or other device capable of monitoring and / or reporting its operating status or other functions associated with its operation. As described above, a WD can represent a wirelessly connected endpoint, in which case the device can be referred to as a wireless terminal. Furthermore, as mentioned above, the WD can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0378] As shown in the figure, the wireless device 1010 includes an antenna 1011, an interface 1014, processing circuitry 1020, a device-readable medium 1030, a user interface device 1032, an auxiliary device 1034, a power supply 1036, and a power circuit 1037. The WD 1010 may include one or more of the components shown for different wireless technologies supported by the WD 1010 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies can be integrated with other components in the WD 1010 into the same or different chipsets.

[0379] Antenna 1011 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 1014. In some alternative embodiments, antenna 1011 may be detached from WD 1010 and may be connected to WD 1010 via an interface or port. Antenna 1011, interface 1014, and / or processing circuitry 1020 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 1011 may be considered as an interface.

[0380] As shown in the figure, interface 1014 includes radio front-end circuitry 1012 and antenna 1011. Radio front-end circuitry 1012 includes one or more filters 1018 and amplifiers 1016. Radio front-end circuitry 1014 is connected to antenna 1011 and processing circuitry 1020 and is configured to modulate the signal transmitted between antenna 1011 and processing circuitry 1020. Radio front-end circuitry 1012 may be coupled to antenna 1011 or be part of antenna 1011. In some embodiments, WD 1010 may not include separate radio front-end circuitry 1012; instead, processing circuitry 1020 may include radio front-end circuitry and may be connected to antenna 1011. Similarly, in some embodiments, some or all of RF transceiver circuitry 1022 may be considered part of interface 1014. Radio front-end circuitry 1012 can receive digital data to be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry 1012 may use a combination of filters 1018 and / or amplifiers 1016 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 can collect radio signals, which are then converted into digital data by radio front-end circuitry 1012. The digital data can then be passed to processing circuitry 1020. In other embodiments, the interface may include different components and / or different combinations of components.

[0381] Processing circuitry 1020 may include a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of one or more of hardware, software, and / or coding, operable to provide WD1010 functionality, alone or in combination with other WD1010 components (e.g., device-readable medium 1030). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1020 may execute instructions stored in device-readable medium 1030 or in memory within processing circuitry 1020 to provide the functionality disclosed herein.

[0382] As shown in the figure, the processing circuit 1020 includes one or more of an RF transceiver circuit 1022, a baseband processing circuit 1024, and an application processing circuit 1026. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of WD 1010 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be on a separate chip or chipset. In alternative embodiments, some or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined into a single chip or chipset, and the RF transceiver circuit 1022 may be on a separate chip or chipset. In yet another alternative embodiment, some or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be on the same chip or chipset, and the application processing circuit 1026 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuitry 1022 may be part of interface 1014. The RF transceiver circuitry 1022 may modulate the RF signals used for processing circuitry 1020.

[0383] In some embodiments, some or all of the functions described herein as being performed by the WD or UE may be provided by processing circuitry 1020 executing instructions stored on device-readable medium 1030, which in some embodiments may be a computer-readable storage device medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry 1020 without executing instructions stored on separate or discrete device-readable storage media, such as in a hard-wired manner. In any of those particular embodiments, processing circuitry 1020 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 1020 alone or other components of WD 1010, but may also be enjoyed by WD 1010 as a whole and / or generally by the end user and wireless network.

[0384] The processing circuit 1020 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by the WD. These operations performed by the processing circuit 1020 may include: processing information acquired by the processing circuit 1020, such as by converting the acquired information into other information, comparing the acquired or converted information with information stored in the WD 1010, and / or performing one or more operations based on the acquired or converted information; and making a determination as a result of said processing.

[0385] Device-readable medium 1030 is operable for storing computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 1020. Device-readable medium 1030 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., optical disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions usable by processing circuitry 1020. In some embodiments, processing circuitry 1020 and device-readable medium 1030 may be considered integrated.

[0386] User interface device 1032 can provide components that allow a human user to interact with WD 1010. This interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 1032 is operable to generate output to the user and allow the user to provide input to WD 1010. The type of interaction may vary depending on the type of user interface device 1032 installed in WD 1010. For example, if WD 1010 is a smartphone, the interaction may be via a touchscreen; if WD 1010 is a smart meter, the interaction may be via a screen providing usage information (e.g., gallons used) or a speaker providing audible alarms (e.g., if smoke is detected). User interface device 1032 may include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device 1032 is configured to allow information input to WD 1010 and is connected to processing circuitry 1020 to allow processing circuitry 1020 to process the input information. User interface device 1032 may include, for example, a microphone, proximity sensor or other sensor, keys / buttons, touch display, one or more cameras, USB port, or other input circuitry. User interface device 1032 is also configured to allow information output from WD 1010 and to allow processing circuitry 1020 to output information from WD 1010. User interface device 1032 may include, for example, a speaker, display, vibration circuitry, a universal serial bus (USB) port, a headphone jack, or other output circuitry. Using one or more input and output interfaces, devices, and circuitry of user interface device 1032, WD 1010 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0387] The auxiliary device 1034 is operable to provide more specific functions that the WD may not typically be able to perform. This may include dedicated sensors for measurements for various purposes, interfaces for additional communication types such as wired communication, etc. The inclusion and type of components of the auxiliary device 1034 may vary depending on the embodiment and / or scenario.

[0388] In some embodiments, power supply 1036 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. WD 1010 may also include power circuitry 1037 for delivering power from power supply 1036 to various parts of WD 1010 that require power from power supply 1036 to perform any function described or indicated herein. In some embodiments, power circuitry 1037 may include power management circuitry. Power circuitry 1037 may additionally or alternatively be operable to receive power from an external power source; in this case, WD 1010 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface (e.g., a power cable). In some embodiments, power circuitry 1037 may also be operable to deliver power from an external power source to power supply 1036. This may be used, for example, to charge power supply 1036. Power circuitry 1037 may perform any formatting, conversion, or other modifications to the power from power supply 1036 to suit the power supplied to the various components of WD 1010.

[0389] Figure 11 This is a schematic diagram illustrating a user device according to some embodiments.

[0390] Figure 11 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in relation to a human user who owns and / or operates the associated device. Instead, a UE may refer to a device intended for sale to or operated by a human user but which may not or initially may not be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may refer to a device not intended for sale to or operated by an end user, but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 1100 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 11 As shown, UE 1100 is an example of a WD configured to communicate according to one or more communication standards (such as 3GPP's GSM, UMTS, LTE, and / or 5G standards) issued by the 3rd Generation Partnership Project (3GPP). As previously stated, the terms WD and UE are used interchangeably. Therefore, although... Figure 11 This is for UE, but the components discussed in this article also apply to WD, and vice versa.

[0391] exist Figure 11In this embodiment, UE 1100 includes processing circuitry operatively coupled to an input / output interface 1105, a radio frequency (RF) interface 1109, a network connectivity interface 1111, a memory 1115 (including random access memory (RAM) 1117, read-only memory (ROM) 1119, and storage medium 1121, etc.), a communication subsystem 1131, a power supply 1133, and / or any other component or any combination thereof. Storage medium 1121 includes an operating system 1123, application programs 1125, and data 1127. In other embodiments, storage medium 1121 may include other similar types of information. Some UEs may utilize... Figure 11 All components shown, or only a subset of these components. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0392] exist Figure 11 In this embodiment, processing circuitry 1101 can be configured to process computer instructions and data. Processing circuitry 1101 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in memory, such as one or more hardware-implemented state machines (e.g., in the form of discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) and appropriate software; or any combination thereof. For example, processing circuitry 1101 may include two central processing units (CPUs). Data may be information in a form suitable for computer use.

[0393] In the described embodiments, the input / output interface 1105 may be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 1100 may be configured to use an output device via the input / output interface 1105. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to or output from the UE 1100. The output device may be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 1100 may be configured to use an input device via the input / output interface 1105 to allow a user to capture information into the UE 1100. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a scroll wheel, a smart card, etc. A presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, another similar sensor, or any combination thereof. Input devices can be accelerometers, magnetometers, digital cameras, microphones, and optical sensors.

[0394] exist Figure 11 In this configuration, RF interface 1109 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network connectivity interface 1111 can be configured to provide a communication interface to network 1143a. Network 1143a can encompass wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 1143a may include a Wi-Fi network. Network connectivity interface 1111 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). Network connectivity interface 1111 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). Transmitter and receiver functions can share circuit components, software, or firmware, or alternatively, can be implemented separately.

[0395] RAM 1117 may be configured to interface with processing circuitry 1101 via bus 1102 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 1119 may be configured to provide computer instructions or data to processing circuitry 1101. For example, ROM 1119 may be configured to store immutable low-level system code or data for basic system functions (such as basic input and output (I / O), booting, or receiving keystrokes from a keyboard) stored in non-volatile memory. Storage medium 1121 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette tape, or flash memory drive. In one example, storage medium 1121 may be configured to include operating system 1123, application 1125 such as a web browser application, widget or gadget engine, or another application, and data file 1127. Storage medium 1121 can store any one or a combination of various operating systems for use by UE 1100.

[0396] Storage medium 1121 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (e.g., a subscriber identity module (SIM) or a removable user identity (RUIM) module), other memory, or any combination thereof. Storage medium 1121 can allow UE 1100 to access computer-executable instructions, applications, etc., stored on a transient or non-transient storage medium to offload or upload data. Articles of manufacture (such as those utilizing a communication system) can be tangibly embodied in storage medium 1121, which may include device-readable media.

[0397] exist Figure 11In this embodiment, processing circuitry 1101 can be configured to communicate with network 1143b using communication subsystem 1131. Networks 1143a and 1143b can be the same network or different networks. Communication subsystem 1131 can be configured to include one or more transceivers for communicating with network 1143b. For example, communication subsystem 1131 can be configured to include one or more remote transceivers for communicating with another device (e.g., another WD, UE, or radio access network (RAN) base station) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include transmitter 1133 and / or receiver 1135 to implement transmitter or receiver functions (e.g., frequency allocation, etc.) suitable for the RAN link, respectively. Furthermore, the transmitter 1133 and receiver 1135 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0398] In the illustrated embodiment, the communication functions of the communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (such as using a Global Positioning System (GPS) to determine location), another similar communication function, or any combination thereof. For example, the communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1143b may include wired and / or wireless networks (such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof). For example, the network 1143b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1113 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1100.

[0399] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 1100 or may be partitioned among multiple components of UE 1100. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 1131 may be configured to include any of the components described herein. Additionally, the processing circuitry 1101 may be configured to communicate with any such component via bus 1102. In another example, any such component may be represented by program instructions stored in memory that perform the corresponding functions described herein when executed by the processing circuitry 1101. In another example, the functionality of any such component may be partitioned between the processing circuitry 1101 and the communication subsystem 1131. In yet another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0400] Figure 12 This is a schematic diagram illustrating a virtualized environment according to some embodiments.

[0401] Figure 12 This is a schematic block diagram illustrating a virtualization environment 1200 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices, or any other type of communication equipment) or components thereof, and relates to an implementation where at least a portion of functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0402] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more hardware nodes 1230. Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0403] These functionalities can be implemented by one or more applications 1220 (which may also be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), which are operable to implement certain features, functionalities, and / or benefits of some embodiments disclosed herein. Application 1220 runs in a virtualization environment 1200, which provides hardware 1230 including processing circuitry 1260 and memory 1290. Memory 1290 contains instructions 1295 executable by the processing circuitry 1260, thereby enabling application 1220 to provide one or more features, benefits, and / or functionalities disclosed herein.

[0404] The virtualization environment 1200 includes general-purpose or special-purpose network hardware devices 1230, which include one or more processors or processing circuits 1260. These processors or processing circuits 1260 may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or a special-purpose processor. Each hardware device may include a memory 1290-1, which may be a non-persistent memory for temporarily storing instructions 1295 or software executable by the processing circuitry 1260. Each hardware device may include one or more network interface controllers (NICs) 1270 (also referred to as network interface cards), which include a physical network interface 1280. Each hardware device may also include a non-transitory, persistent machine-readable storage medium 1290-2 in which software 1295 and / or instructions executable by the processing circuitry 1260 are stored. Software 1295 may include any type of software including software for instantiating one or more virtualization layers 1250 (also referred to as hypervisors), software for executing virtual machines 1240, and software that allows them to perform functions, features, and / or benefits associated with some of the embodiments described herein.

[0405] Virtual machine 1240 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of instances of virtual device 1220 can be implemented on one or more virtual machines 1240, and can be implemented in different ways.

[0406] During operation, the processing circuitry 1260 executes software 1295 to instantiate a hypervisor or virtualization layer 1250 (which may sometimes be referred to as a virtual machine monitor (VMM)). The virtualization layer 1250 can present a virtual operating platform to the virtual machine 1240 that appears to be networked hardware.

[0407] like Figure 12As shown, hardware 1230 can be a standalone network node with general or specific components. Hardware 1230 may include antenna 12225 and may implement some functions through virtualization. Alternatively, hardware 1230 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) in which many hardware nodes work together and are managed by management and orchestration (MANO) 12100, which in particular oversees the lifecycle management of application 1220.

[0408] In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to integrate many types of network devices into industry-standard, high-capacity server hardware, physical switches, and physical storage, which can reside in data centers and client devices.

[0409] In the context of NFV, virtual machine 1240 can be a software implementation of a physical machine. Virtual machine 1240 runs programs as if they were executing on a physical, non-virtualized machine. Each virtual machine 1240 and the portion of the hardware 1230 that executes that virtual machine (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other virtual machines 1240) form a separate virtual network element (VNE).

[0410] Still within the context of NFV, a Virtual Network Function (VNF) is responsible for handling specific network functions running on top of one or more virtual machines 1240 on the hardware network infrastructure 1230, and interacting with... Figure 12 The application 1220 corresponds to this.

[0411] In some embodiments, each of the one or more radio units 12200, including one or more transmitters 12220 and one or more receivers 12210, may be coupled to one or more antennas 12225. The radio unit 12200 may communicate directly with the hardware node 1230 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0412] In some embodiments, some signaling can be implemented using a control system 12230, which can alternatively be used for communication between hardware node 1230 and radio unit 12200.

[0413] Figure 13 This is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments.

[0414] refer to Figure 13According to an embodiment, a communication system includes a telecommunications network 1310, such as a 3GPP-type cellular network, comprising an access network 1311, such as a radio access network, and a core network 1314. The access network 1311 includes multiple base stations 1312a, 1312b, and 1312c, such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, and 1313c. Each base station 1312a, 1312b, and 1312c can be connected to the core network 1314 via a wired or wireless connection 1315. A first UE 1391 located in coverage area 1313c is configured to wirelessly connect to or be paged by the corresponding base station 1312c. A second UE 1392 located in coverage area 1313a can wirelessly connect to the corresponding base station 1312a. Although multiple UEs 1391 and 1392 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 1312.

[0415] Telecommunications network 1310 is itself connected to host computer 1330, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. Host computer 1330 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 1321 and 1322 between telecommunications network 1310 and host computer 1330 may extend directly from core network 1314 to host computer 1330, or may be via optional intermediate network 1320. Intermediate network 1320 may be one of public, private, or hosted networks, or a combination of several of them; intermediate network 1320 (if any) may be a backbone network or the Internet; in particular, intermediate network 1320 may include two or more subnetworks (not shown).

[0416] Figure 13The communication system as a whole implements the connection between connected UEs 1391 and 1392 and host computer 1330. This connection can be described as an over-the-top (OTT) connection 1350. Host computer 1330 and connected UEs 1391 and 1392 are configured to use access network 1311, core network 1314, any intermediate network 1320, and possibly other infrastructure (not shown) as intermediaries to transmit data and / or signaling via OTT connection 1350. OTT connection 1350 can be transparent in the sense that the participating communication devices through which OTT connection 1350 passes are unaware of the routes of uplink and downlink communications. For example, it may not be necessary to inform base station 1312 of the past routes of incoming downlink communications containing data originating from host computer 1330 that will be forwarded (e.g., handed over) to connected UE 1391. Similarly, base station 1312 does not need to know the future route of outgoing uplink communication from UE 1391 to host computer 1330.

[0417] Figure 14 This is a schematic diagram illustrating a host computer communicating with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0418] Now refer to Figure 14 This section describes example implementations of the UE, base station, and host computer according to embodiments discussed in the preceding paragraphs. In the communication system 1400, the host computer 1410 includes hardware 1415, which includes a communication interface 1416 configured to establish and maintain wired or wireless connections to interfaces with different communication devices of the communication system 1400. The host computer 1410 also includes processing circuitry 1418, which may have storage and / or processing capabilities. Specifically, the processing circuitry 1418 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The host computer 1410 also includes software 1411, which is stored in or accessible by the host computer 1410 and executable by the processing circuitry 1418. The software 1411 includes a host application 1412. Host application 1412 is operable to provide services to remote users such as UE 1430, which is connected via an OTT connection 1450 terminated between UE 1430 and host computer 1410. When providing services to remote users, host application 1412 can provide user data sent using OTT connection 1450.

[0419] The communication system 1400 also includes a base station 1420, which is provided in the telecommunications system and includes hardware 1425 enabling it to communicate with the host computer 1410 and the UE 1430. Hardware 1425 may include a communication interface 1426 for establishing and maintaining wired or wireless connections to different communication devices of the communication system 1400, and for establishing and maintaining connections at least with the coverage area served by the base station 1420. Figure 14 The radio interface 1427 of the UE1430 (not shown) is for the wireless connection 1470. The communication interface 1426 can be configured to facilitate a connection 1460 to the host computer 1410. The connection 1460 can be direct or can be via the core network of a telecommunications system (…). Figure 14 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1425 of base station 1420 also includes processing circuitry 1428, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 1420 also has software 1421 stored internally or accessible via an external connection.

[0420] The communication system 1400 also includes the previously mentioned UE 1430. Its hardware 1435 may include a radio interface 1437 configured to establish and maintain a wireless connection 1470 with a base station serving the coverage area currently occupied by the UE 1430. The hardware 1435 of the UE 1430 also includes processing circuitry 1438, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE 1430 further includes software 1431 stored in or accessible by the UE 1430 and executable by the processing circuitry 1438. The software 1431 includes a client application 1432. The client application 1432 is operable to provide services to human or non-human users via the UE 1430 with the support of a host computer 1410. In host computer 1410, the executing host application 1412 can communicate with the executing client application 1432 via OTT connection 1450 terminated between UE 1430 and host computer 1410. In providing services to the user, client application 1432 can receive request data from host application 1412 and provide user data in response to the request data. OTT connection 1450 can transmit both request data and user data. Client application 1432 can interact with the user to generate the user data it provides.

[0421] Notice, Figure 14The host computer 1410, base station 1420, and UE 1430 shown can be respectively connected to Figure 13 The host computer 1330, base stations 1312a, 1312b, and 1312c, and UEs 1391 and 1392 are similar to or identical to each other. That is to say, the internal working principles of these entities can be as follows: Figure 14 As shown, independently, the surrounding network topology can be Figure 13 As it is.

[0422] exist Figure 14 The OTT connection 1450 has been abstractly depicted to illustrate communication between host computer 1410 and UE 1430 via base station 1420, without explicitly referencing any intermediate devices or the precise routing of messages via those devices. The network infrastructure can determine the route, which can be configured to be hidden from UE 1430, the service provider operating host computer 1410, or both. When the OTT connection 1450 is active, the network infrastructure can further make decisions by dynamically altering the route (e.g., based on load balancing considerations or network reconfiguration).

[0423] The wireless connection 1470 between UE 1430 and base station 1420 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in the various embodiments improve the performance of OTT services provided to UE 1430 using OTT connection 1450, in which wireless connection 1470 forms the final segment. More precisely, the teachings of these embodiments can improve the latency and power consumption of network connection reactivation, thereby providing benefits such as reduced user latency and enhanced rate control.

[0424] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved thereon by one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection 1450 between host computer 1410 and UE 1430 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 1450 may be implemented in software 1411 and hardware 1415 of host computer 1410, or in software 1431 and hardware 1435 of UE 1430, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices traversed by the OTT connection 1450; the sensors may participate in the measurement procedure by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities from which software 1411, 1431 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not necessarily affect base station 1420, and it may be unknown or imperceptible to base station 1420. Such processes and functions are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 1410 to measure throughput, propagation time, latency, etc. Measurements can be implemented in such a way that software 1411 and 1431, while monitoring message propagation time, errors, etc., prompts the use of OTT connection 1450 to send messages (especially empty messages or "dummy" messages).

[0425] Figure 15 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0426] The communication system includes a host computer, a base station, and a user interface (UE), which can be referenced. Figure 13 and Figure 14 Those described. For the sake of simplicity in this disclosure, this section only includes those... Figure 15 Referring to the accompanying drawings. In step 1510, the host computer provides user data. In sub-step 1511 of step 1510 (which may be optional), the host computer provides user data by executing a host application. In step 1520, the host computer initiates a transmission carrying user data to the UE. In step 1530 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0427] Figure 16This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0428] The communication system includes a host computer, a base station, and a user interface (UE), which can be referenced. Figure 13 and Figure 14 Those described. For the sake of simplicity in this disclosure, this section only includes those... Figure 16 Refer to the accompanying drawings. In step 1610, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1620, the host computer initiates a transmission carrying user data to the UE. Based on the teachings of the embodiments described throughout this disclosure, the transmission can be performed via a base station. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

[0429] Figure 17 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0430] The communication system includes a host computer, a base station, and a user interface (UE), which can be referenced. Figure 13 and Figure 14 Those described. For the sake of simplicity in this disclosure, this section only includes those... Figure 17 Referring to the accompanying drawings. In step 1710 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data. In sub-step 1721 of step 1720 (which may be optional), the UE provides user data by executing a client application. In sub-step 1711 of step 1710 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 1730 (which may be optional). In step 1740 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0431] Figure 18 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0432] The communication system includes a host computer, a base station, and a user interface (UE), which can be referenced. Figure 13 and Figure 14Those described. For the sake of simplicity in this disclosure, only those described herein are included. Figure 18 Refer to the accompanying drawings. In step 1810 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1820 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1830 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0433] Generally, the various exemplary embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that these blocks, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0434] Therefore, it should be understood that at least some aspects of the exemplary embodiments of this disclosure can be practiced in various components such as integrated circuit chips and modules. It should also be understood that the exemplary embodiments of this disclosure can be implemented in devices embodied as integrated circuits, wherein the integrated circuits may include circuitry (and possibly firmware) for embodying at least one or more of a data processor, digital signal processor, baseband circuitry, and radio frequency circuitry configurable to operate according to the exemplary embodiments of this disclosure.

[0435] It should be understood that at least some aspects of the exemplary embodiments of this disclosure may be embodied in computer-executable instructions, which are executed by one or more computers or other devices, such as in one or more program modules. Typically, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type when executed by a processor in a computer or other device. The computer-executable instructions may be stored on a computer-readable medium such as a hard disk, optical disk, removable storage medium, solid-state memory, RAM, etc. Those skilled in the art will understand that the functionality of a program module may be combined or distributed as needed in various embodiments. Additionally, functionality may be wholly or partially embodied in firmware or hardware equivalents such as integrated circuits, field-programmable gate arrays (FPGAs), etc.

[0436] This disclosure includes any novel features or combinations of features expressly disclosed herein, or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure will become apparent to those skilled in the art when read in conjunction with the accompanying drawings, in light of the foregoing description. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.

[0437] The block diagrams and flowcharts of the methods and apparatus described above illustrate exemplary embodiments. It should be understood that each block of the block diagrams and flowcharts, as well as combinations of blocks in the block diagrams and flowcharts, can be implemented by various means including computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed on the computer or other programmable data processing apparatus, they create means for implementing the functions specified in the flowcharts.

[0438] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order or sequence shown, or that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the subject matter described herein, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of different embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0439] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any implementation or the scope that may be claimed, but rather as descriptions of features that may be specific to particular embodiments of a particular implementation. Certain features described in the context of different embodiments in this specification may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as operating in certain combinations, or even initially stated so, in some cases one or more features of a claimed combination may be removed from the claimed combination, and the claimed combination may be for sub-combinations or variations thereof.

[0440] It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. The above embodiments are for description and not limitation of this disclosure, and it should be understood that various modifications and variations can be made without departing from the spirit and scope of this disclosure, as will be readily apparent to those skilled in the art. Such modifications and variations are considered to be within the scope of this disclosure and the appended claims. The scope of protection of this disclosure is defined by the appended claims.

Claims

1. A method executed at a terminal device, comprising: Predict (S101) the buffer size associated with the data to be sent; Send a buffer status report (BSR) including the predicted buffer size to the network node (S102); The method further includes: Predict (S105) the probability associated with the predicted buffer size; When the probability is equal to or greater than the threshold, the terminal device sends the BSR; when the probability is less than the threshold, the terminal device does not send the BSR.

2. The method according to claim 1, further comprising: Receive (S103) permission for the data to be sent; as well as Send the data (S104).

3. The method according to claim 1 or 2, wherein, The prediction is based on at least one of the following: the size, type, content, or required transmission rate of the data.

4. The method according to claim 1 or 2, wherein, The prediction is based on at least one of the following: Input data from application behavior, user behavior, radio conditions, or business behavior.

5. The method according to claim 4, in, The user behavior includes mobility; and / or The business activities mentioned above include business models.

6. The method according to claim 1, wherein, The BSR includes the probability.

7. The method according to claim 6, wherein, The threshold can be configurable or fixed.

8. The method according to any one of claims 1-2 and 5-7, wherein, The prediction was made using an artificial intelligence algorithm.

9. The method according to claim 8, in, The predictions are made using a Long Short-Term Memory (LSTM) neural network model, an Arima machine learning model, and / or reinforcement learning.

10. The method according to any one of claims 1-2 and 5-7, further comprising: Receive (S107) BSR prediction configuration for the terminal device or for multiple terminal devices.

11. The method according to any one of claims 1-2 and 5-7, wherein, The terminal device transmits the BSR in the uplink shared channel UL-SCH.

12. The method according to claim 11, wherein, The terminal device sends a scheduling request (SR) for the BSR.

13. The method according to claim 12, wherein, The terminal device sends the SR according to the SR configuration.

14. The method according to claim 13, wherein, The SR configuration is received from the network node or is pre-configured.

15. The method according to any one of claims 1-2 and 5-7, wherein, The BSR is configured for use on a logical channel or for a logical channel group.

16. The method according to claim 15, in, The BSR is configured based on the priority of the logical channel or the logical channel group.

17. The method according to claim 15, in, The BSR also includes the buffer size associated with the data allocated to the logical channel.

18. The method according to any one of claims 1-2 and 5-7, further comprising: The report (S106) describes the terminal device's ability to support the BSR.

19. The method according to any one of claims 1-2 and 5-7, wherein, The BSR also includes: the predicted time point or time window for sending the data.

20. The method according to claim 19, wherein, The BSR also includes the predicted probability of the time point or time window for sending the data.

21. The method according to any one of claims 1-2 and 5-7, wherein, The predicted buffer size is included in the Media Access Control (MAC) control element CE.

22. The method according to any one of claims 1-2 and 5-7, further comprising: Receive (S108) an indication of whether the BSR, including the predicted buffer size, is enabled or disabled.

23. The method of claim 22, further comprising: When the BSR, which includes the predicted buffer size, is disabled, a Buffer Status Report (BSR) is sent (S109) including the buffer size associated with the data of the logical channel allocated to the terminal device.

24. The method according to claim 22, in, The indication includes a threshold for the probability of the predicted buffer size.

25. The method according to claim 2, further comprising: After sending the BSR including the predicted buffer size, start timer (S110); and / or The timer is stopped (S111) upon receiving the permission.

26. The method of claim 25, further comprising: If the predicted buffer size is updated and the BSR including the predicted buffer size is retransmitted, then the timer is restarted (S112).

27. The method according to claim 25 or 26, further comprising: When the timer expires, the predicted BSR is retransmitted (S113).

28. The method according to any one of claims 1-2 and 5-7, in, The BSR includes a predetermined logical channel identifier (LCID) to indicate the predicted buffer size.

29. The method according to any one of claims 1-2 and 5-7, wherein, The terminal device includes a user equipment (UE).

30. A method executed at a network node, comprising: The receiving (S201) includes a buffer status report (BSR) of the predicted buffer size associated with the data to be received from the terminal device; Based on the received BSR, send (S202) a license for the data; The method further includes: The BSR includes a probability associated with the predicted buffer size; Based on the probability, the transmission of the data is configured with a priority (S205); wherein the priority is associated with the probability.

31. The method of claim 30, further comprising: Receive the data (S203).

32. The method according to claim 30 or 31, wherein, The prediction is based on at least one of the following: the size, type, content, or required transmission rate of the data.

33. The method according to claim 30 or 31, wherein, The prediction is based on at least one of the following: Input data from application behavior, user behavior, radio conditions, and business behavior.

34. The method according to claim 33, in, The user behavior includes mobility; and / or The business activities mentioned above include business models.

35. The method according to any one of claims 30-31 and 34, wherein, The prediction was made using an artificial intelligence algorithm.

36. The method according to claim 35, in, The predictions are made using a Long Short-Term Memory (LSTM) neural network model, an Arima machine learning model, and / or reinforcement learning.

37. The method according to any one of claims 30-31 and 34, further comprising: Send (S207) for BSR prediction configuration of terminal device or multiple terminal devices.

38. The method of claim 37 further includes receiving a scheduling request (SR) for the BSR sent by the terminal device.

39. The method according to any one of claims 30-31 and 34, wherein, The BSR is configured for use on a logical channel or for a logical channel group.

40. The method according to claim 39, in, The BSR is configured based on the priority of the logical channel or the logical channel group.

41. The method according to any one of claims 30-31, 34, in, The BSR also includes the buffer size associated with the data allocated to the logical channel.

42. The method according to any one of claims 30-31 and 34, further comprising: The terminal device receives (S206) the ability to support the BSR, including the predicted buffer size.

43. The method according to any one of claims 30-31 and 34, wherein, The BSR also includes: the predicted time point or time window for sending the data.

44. The method according to claim 43, wherein, The BSR also includes the predicted probability of the time point or time window for sending the data.

45. The method according to any one of claims 30-31 and 34, wherein, The predicted buffer size is included in the Media Access Control (MAC) control element CE.

46. ​​The method according to any one of claims 30-31 and 34, further comprising: Send (S207) an indication as to whether the BSR, including the predicted buffer size, is enabled or disabled.

47. The method of claim 46, further comprising: When the BSR, which includes the predicted buffer size, is disabled, a buffer status report (BSR) including the buffer size associated with the data allocated to the logical channel of the terminal device is received (S208).

48. The method according to claim 46, in, The indication includes a threshold for the probability of the predicted buffer size.

49. The method according to any one of claims 30-31 and 34, in, The BSR includes a predetermined logical channel identifier (LCID) to indicate the predicted buffer size.

50. The method according to any one of claims 30-31 and 34, further comprising: Another terminal device is scheduled based on the predicted buffer size (S209).

51. The method according to any one of claims 30-31, 34, wherein, The network nodes include base stations.

52. A terminal device (100), comprising: Processor (101); as well as The memory (102) contains instructions executable by the processor (101), thereby enabling the terminal device (100) to perform the method according to any one of claims 1 to 29.

53. A network node (200), comprising: Processor (201); as well as A memory (202) contains instructions executable by the processor (201), thereby enabling the network node (200) to perform the method according to any one of claims 30 to 51.

54. A computer-readable storage medium (700) storing instructions (701) that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 51.

Citation Information

Patent Citations

  • User equipment

    US20190110224A1