Efficient uplink resource allocation for environmental iot devices based on environmental iot device segmentation capabilities

CN122935979APending Publication Date: 2026-10-16OMOWE GMBH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580021289.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-03-27
Filing Date
2025-03-21
Publication Date
2026-10-16

AI Technical Summary

Technical Problem

[0006]然而,其他约束可能会限制A-IoT装置对上行链路资源的使用,gNB应考虑这些约束,以确保所分配的上行链路资源确实可被A-IoT装置使用以避免浪费上行链路资源

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122935979A_ABST
    Figure CN122935979A_ABST
Patent Text Reader

Abstract

The present disclosure relates to methods and apparatus for enabling efficient allocation of uplink resources to a user equipment, UE (20), including a wireless device (25), such as an environmental IoT device, by taking into account the uplink data fragmentation capability of the wireless device (25).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically to methods and apparatus for efficiently allocating uplink resources to wireless devices by taking into account the uplink data segmentation capability of the wireless device (e.g., a wireless device for harvesting electrical energy). Background Technology

[0002] The Internet of Things (IoT) allows various devices to connect to the internet to send data, receive commands, or both. Tens of billions of IoT devices are already deployed, and the number of IoT devices globally is expected to grow rapidly. Therefore, massive connectivity is required. However, powering these billions of IoT devices is a significant challenge, and deploying power cables or regularly replacing / recharging batteries is not a feasible solution.

[0003] 3GPP (3rd Generation Partnership Project) is researching new IoT technologies to open up new markets within the 3GPP system. These new IoT technologies can offer several orders of magnitude higher connection counts and / or device density than existing 3GPP IoT technologies, while providing several orders of magnitude lower complexity and power consumption than existing 3GPP technologies such as Narrowband IoT (NB-IoT) and Long Term Evolution Machine Type Communications (LTE-MTC). More specifically, 3GPP is currently defining Ambient IoT (A-IoT) technologies (see, for example, Technical Report TR 38.848 V18.0.0) aimed at enabling ultra-low-power IoT devices, which can be battery-free devices without energy storage capabilities (performing backscatter transmission) or devices with energy storage that do not require manual replacement or recharging (performing wireless energy harvesting (EH) from one or more energy sources).

[0004] The term "ultra-low power" or "A-IoT" device refers to a device with peak power consumption of less than 1 mW, or even less than 100 µW, or less than 10 µW. For example, current Ambient IoT aims to achieve A-IoT devices with the following characteristics: - Peak power consumption of approximately 1 µW, with energy storage, and no downlink (DL) amplification or uplink (UL) amplification in the device (the device's UL transmission is backscattered on an externally provided carrier). - Peak power consumption below a few hundred µW, with energy storage, and DL and / or UL amplification in the device (the UL transmission of the device can be generated internally by the device or backscattered on an externally provided carrier).

[0005] Currently, User Equipment (UE) seeking uplink resource allocation can rely on the Buffer State Reporting (BSR) procedure defined in TS 38.321V18.0.0. The BSR provides the serving base station (gNB) with information about the amount of uplink data present at the UE that the UE wishes to send. This enables the gNB to make informed decisions regarding uplink resource scheduling, allowing for efficient management of uplink data transmission.

[0006] However, other constraints may limit the use of uplink resources by A-IoT devices. gNBs should take these constraints into account to ensure that the allocated uplink resources are indeed available for use by A-IoT devices to avoid wasting uplink resources. Summary of the Invention

[0007] This disclosure aims to improve upon this situation. Specifically, this disclosure aims to address at least some of the limitations of the prior art discussed above. In particular, this disclosure aims to propose a solution for achieving efficient allocation of uplink resources to wireless devices by taking into account the uplink data segmentation capabilities of wireless devices (e.g., A-IoT devices).

[0008] In fact, in the context of environmental IoT, some wireless devices may not have uplink data segmentation capabilities. Wireless devices without uplink data segmentation capabilities will be unable to break down the uplink data they need to transmit into multiple uplink data packets. In other words, for wireless devices without uplink data segmentation capabilities, all available uplink data must be transmitted in a single uplink data packet. Therefore, if the amount of allocated uplink resources is less than the amount of available uplink data, such wireless devices will not be able to use the allocated uplink resources, and these allocated uplink resources will be wasted.

[0009] To this end, it is proposed to introduce means that enable the Radio Access Network (RAN) to determine whether a given radio device supports uplink data segmentation. Uplink resources can then be allocated by the RAN based on each radio device's uplink data segmentation capability, and this allocation should attempt to ensure that the amount of uplink resources allocated to radio devices that do not have uplink data segmentation capability is sufficient (or at least potentially sufficient) to transmit all uplink data available at that radio device.

[0010] According to a first aspect, this disclosure relates to a method for exchanging data in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the wireless device includes a communication unit configured to exchange data with a radio access network (RAN) of the wireless communication system, wherein the method includes: - Send an indication of the uplink data segmentation capability of the radio device to the RAN. - Receive the allocation of uplink resources determined by the RAN based on the indicated uplink data segmentation capability.

[0011] In some embodiments, the method according to the first aspect may further include one or more of the following optional features, considered individually or in any technically possible combination.

[0012] In some embodiments, the method according to the first aspect includes: sending a buffer status report (BSR) that includes an indication of the amount of uplink data the radio device may need to send to the RAN, wherein the allocation of uplink resources to the radio device is further determined by the RAN based on the BSR.

[0013] In some embodiments of the method according to the first aspect, the BSR is a predicted BSR, PBSR, wherein the PBSR is transmitted before the radio device has uplink data to be transmitted to the RAN.

[0014] In some embodiments of the method according to the first aspect, the indication of the amount of uplink data that the wireless device may need to transmit corresponds to the maximum amount of uplink data that the wireless device may need to transmit in response to receiving an uplink transmission trigger signal from the RAN.

[0015] In some embodiments of the method according to the first aspect, the uplink transmission trigger signal is received when the wireless device has not sent a prior uplink resource allocation request to the RAN.

[0016] In some embodiments of the method according to the first aspect, the uplink transmission trigger signal is a wake-up signal from the RAN that transitions the wireless device from sleep mode to active mode, or a signaling message received after receiving the wake-up signal from the RAN.

[0017] In some embodiments of the method according to the first aspect, the indication of the uplink data segmentation capability is sent in a user equipment (UE) capability message.

[0018] In some embodiments of the method according to the first aspect, the indication of the uplink data segmentation capability is provided as a single bit.

[0019] In some embodiments of the method according to the first aspect, the wireless device includes an energy harvesting unit configured to convert ambient energy into electrical energy stored in an energy storage unit of the wireless device.

[0020] According to a second aspect, this disclosure relates to a wireless device including at least one memory and at least one processor configured to perform a method according to any embodiment of the first aspect.

[0021] According to a third aspect, this disclosure relates to a user equipment (UE) that includes a wireless means according to any one of the embodiments of this disclosure.

[0022] According to a fourth aspect, this disclosure relates to a method for exchanging data in a wireless communication system, the method being implemented by a base station (BS) of a radio access network (RAN) of the wireless communication system, wherein the BS is configured to exchange data with a plurality of wireless devices, wherein the method includes: - Receive an indication of the uplink data segmentation capability of the wireless device from the wireless device. - Based on the received indication of the uplink data segmentation capability of the wireless device, determine the allocation of uplink resources to the wireless device.

[0023] In some embodiments, the method according to the fourth aspect may further include one or more of the following optional features, considered individually or in any technically possible combination.

[0024] In some embodiments, the method according to the fourth aspect includes: receiving a buffer status report (BSR) from the wireless device, the BSR including an indication of the amount of uplink data that the wireless device may need to send to the BS, wherein the allocation of uplink resources to the wireless device is further determined based on the received BSR.

[0025] In some embodiments of the method according to the fourth aspect, the BSR is the predicted BSR, PBSR, wherein the PBSR is received before the wireless device has uplink data to be transmitted to the RAN.

[0026] In some embodiments of the method according to the fourth aspect, the indication of the amount of uplink data that the wireless device may need to transmit corresponds to the maximum amount of uplink data that the wireless device may need to transmit in response to receiving an uplink transmission trigger signal from the BS.

[0027] In some embodiments of the method according to the fourth aspect, the uplink transmission trigger signal is received when the wireless device has not sent a prior uplink resource allocation request to the RAN.

[0028] In some embodiments of the method according to the fourth aspect, the uplink transmission trigger signal is a wake-up signal from the RAN that transitions the wireless device from sleep mode to active mode, or a signaling message received after receiving the wake-up signal from the RAN.

[0029] In some embodiments of the method according to the fourth aspect, the indication of the uplink data segmentation capability is received in a user equipment (UE) capability message.

[0030] In some embodiments of the method according to the fourth aspect, the indication of the uplink data segmentation capability is provided as a single bit.

[0031] In some embodiments of the method according to the fourth aspect, the wireless device includes an energy harvesting unit configured to convert ambient energy into electrical energy stored in an energy storage unit of the wireless device.

[0032] In some embodiments, the method according to the fourth aspect includes starting to send an energy harvesting signal to the wireless device before sending an uplink transmission trigger signal to the wireless device.

[0033] According to a fifth aspect, this disclosure relates to a base station (BS) including at least one memory and at least one processor configured to perform a method according to any embodiment of the fourth aspect.

[0034] According to a sixth aspect, this disclosure relates to a wireless communication system including at least one base station according to any embodiment of the present disclosure and at least one user equipment according to any embodiment of the present disclosure.

[0035] According to a seventh aspect, this disclosure relates to a computer program product comprising instructions that, when executed by at least one processor, configure the at least one processor to perform a method for exchanging data according to any embodiment of the present disclosure. The computer program product may use any programming language and may be in the form of source code, object code, or any intermediate form between source code and object code, such as a partially compiled form, or any other desired form.

[0036] According to an eighth aspect, this disclosure relates to a (non-transitory) computer-readable storage medium including instructions that, when executed by at least one processor, configure the at least one processor to perform a method for exchanging data according to any embodiment of the present disclosure. Attached Figure Description

[0037] The invention will be better understood by reading the following description, which is given by way of example only and is not limiting, and reference is made to the accompanying drawings, which illustrate: - Figure 1 Schematic representation of different possible topologies of wireless communication systems. - Figure 2 : A schematic representation of an example of a wireless device, - Figure 3 : A schematic representation of a BS example - Figure 4 and Figure 5 : Flowcharts showing examples of methods for exchanging data implemented by the UE's radio device and the BS, respectively. - Figure 6 and Figure 7 : Flowcharts showing other examples of methods for exchanging data implemented by the UE's wireless device and the BS, respectively.

[0038] In these accompanying figures, the same reference numerals denote the same or similar elements. For clarity, unless otherwise explicitly stated, the elements shown are not drawn to scale. Detailed Implementation

[0039] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. For example, although 3GPP terms, such as 5G NR, may be used in this disclosure to illustrate embodiments thereof, this should not be considered as limiting the scope of this disclosure.

[0040] Generally, all terms used herein should be interpreted according to their ordinary meaning in the relevant art, unless a different meaning is expressly given and / or implied in the context of their use. Unless otherwise expressly stated, all references to elements, devices, components, means, steps, etc., should be openly interpreted as referring to at least one instance of that element, device, component, means, step, etc. Furthermore, the order of steps in any method disclosed herein, particularly in the accompanying drawings, is provided for illustrative purposes only and is not intended to limit the disclosure. The disclosure may apply where the same steps are performed in a different order and / or where steps are performed in parallel or in combination, unless a step is explicitly described as occurring after or before another step and / or where it is implied that a step must occur after or before another step. Additionally, in a drawing, steps indicated by dashed boxes should be considered optional for the embodiments illustrated in that drawing. Where appropriate, any feature of any embodiment in the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment in the embodiments 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.

[0041] Figure 1 The illustration depicts an example of a wireless communication system, which could be, for example, a 5G NR wireless communication system. More specifically, Figure 1 The RAN represents the radio communication system used to exchange data with UE 20 via radio signals. For example, the RAN can send data (downlink DL) to UE 20, such as data received from the core network (CN, not shown in the figures). The RAN can also receive data (uplink UL) from UE 20, which can be forwarded to the CN.

[0042] exist Figure 1 In the example shown, the RAN includes one base station BS 30. Of course, the RAN can include more than one BS 30 to increase the coverage of the wireless communication system. Depending on the implemented wireless communication standard, each of these BSs can be referred to as an NB, eNodeB (or eNB), gNodeB (or gNB, in the case of a 5G NR wireless communication system), access point, etc.

[0043] exist Figure 1 The example shown represents only one UE 20, which includes a wireless device 25 that provides the UE 20 with wireless connectivity to the RAN of the wireless communication system. Figure 1 Part a) schematically illustrates an example of UE 20 directly exchanging data (useful data and control data) with RAN BS 30 (referred to as Topology 1 in TR 38.848 V18.0.0). Figure 1 Part b) schematically illustrates an example of UE 20 indirectly exchanging data (useful data and control data) with BS 30 of the RAN via one or more intermediate nodes 31 (referred to as Topology 2 in TR 38.848 V18.0.0). Each intermediate node 31 may be, for example, a repeater, an Integrated Access and Backhaul (IAB) node, another UE 20, a repeater, a Reconfigurable Smart Surface (RIS), etc.

[0044] Figure 2 Examples of wireless devices 25 suitable for implementing any of the methods discussed in this disclosure at the UE 20 are illustrated schematically. Essentially, wireless device 25 corresponds to a device that provides wireless connectivity to a RAN of a wireless communication system and can be used to exchange data with said RAN. For example, wireless device 25 is an A-IoT device, i.e., a wireless device having a peak power consumption of less than 1 mW, or even less than 100 µW, or even less than 10 µW.

[0045] Such a wireless device 25 can be included in the UE 20, such as Figure 2 As shown. UE 20 can be, for example, a cellular phone, wireless modem, wireless communication device, handheld device, laptop computer, etc. In a preferred example, UE 20 can also be an Internet of Things (IoT) device, such as a wireless camera, smart sensor, smart meter, smart glasses, (manned or unmanned) vehicle, GPS device, etc., or any other device that can run applications that require exchanging data with a remote receiver via wireless device 25.

[0046] like Figure 2 As shown, the wireless device 25 includes one or more processors 250 and one or more memories 251. The one or more processors 250 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc. The one or more memories 251 may include any type of computer-readable volatile and non-volatile memory (hard disk, solid-state drive, optical disk, electronic storage, etc.). The one or more memories 251 may store a computer program product 252 in the form of a set of program code instructions to be executed by the one or more processors 250 to implement all or part of the steps of a method for exchanging data executed on the UE side according to any embodiment of the embodiments disclosed herein.

[0047] like Figure 2As shown, the wireless device 25 also includes a (wireless) communication unit 253 configured to exchange data (directly or indirectly) with the BS 30 of the RAN using radio signals. The communication unit 253 can implement one or more wireless communication protocols and can be, for example, a 3G, 4G, 5G, NR, WiFi, WiMax, or other transceivers. In a preferred embodiment, the (wireless) communication unit 253 includes a 5G NR wireless communication unit.

[0048] As discussed above, in some examples, communication unit 253 may not include either downlink (DL) amplification capability or uplink (UL) amplification capability (UL transmission is backscattered on an externally provided carrier). In other examples, communication unit 253 may include DL and / or UL amplification (UL transmission may be generated internally by the wireless device or backscattered on an externally provided carrier).

[0049] like Figure 2 As shown, the wireless device 25 also includes a wireless device energy harvesting unit 254 and an energy storage unit 255.

[0050] The energy storage unit 255 can be any type of electrical energy storage device and may include, for example, one or more capacitors, one or more batteries, etc. The energy storage unit 255 is used to provide power to other devices of the wireless device 25 that require power, such as one or more processors 250, one or more memories 251, and in some examples, (wireless) communication unit 253.

[0051] The energy harvesting unit 254 is configured to convert ambient energy into electrical energy stored in the energy storage unit 255. "Ambient energy" refers to energy from an external energy source to the wireless device 25, received at the wireless device 25 without any wires between the energy source and the wireless device 25. Therefore, the energy harvesting unit 254 enables the wireless device 25 to operate autonomously without requiring manual replacement or recharging of the energy storage unit 255. The energy harvesting unit 254 can harvest energy from various energy sources, including sunlight, heat, motion or vibration, radio frequency (RF), etc.

[0052] In a preferred embodiment, the energy harvesting unit 254 includes at least a radio unit configured to convert RF signals into electrical energy stored in the energy storage unit 255. These RF signals can be, for example, external RF signals, i.e., RF signals originating from an RF source outside the wireless communication system rather than within the system itself. For example, external RF signals can originate from external 3G, 4G, 5G, NR, WiFi, WiMax, Bluetooth, DAB, or other devices located near the wireless device 25. Alternatively or in combination, the RF signals can originate from within the wireless communication system, such as from a BS 30 within the RAN, which can transmit energy harvesting (RF) signals to the (A-IoT) wireless device 25 within its coverage area, and / or from a device separate from the BS 30 but deployed to perform energy harvesting at the (A-IoT) wireless device 25 of the wireless communication system. In some examples, when RF signals are used to harvest electrical energy into the energy storage unit 255, the energy harvesting unit 254 may be included in the (wireless) communication unit 253.

[0053] In some examples, the electrical energy collected by the energy harvesting unit 254 can be directly supplied to other devices of the wireless device 25. In this case, the energy storage unit 255 is optional and does not need to be included in the wireless device.

[0054] Figure 3 An example of a BS 30 is schematically shown that is suitable for implementing any of the methods discussed in this disclosure that are performed by the RAN.

[0055] like Figure 3 As shown, BS 30 includes one or more processors 300 and one or more memories 301. The one or more processors 300 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc. The one or more memories 301 may include any type of computer-readable volatile and non-volatile memory (hard disk, solid-state drive, optical disk, electronic storage, etc.). The one or more memories 301 may store a computer program product 302 in the form of a set of program code instructions to be executed by the one or more processors 300 to implement all or part of the steps of a method for exchanging data executed on the RAN side according to any embodiment of the embodiments disclosed herein.

[0056] like Figure 3As shown, BS 30 also includes a wireless communication unit 303 configured to exchange data with UE 20 using radio signals, and more specifically with the (wireless) communication unit 253 of the wireless device 25 included in these UEs 20. The wireless communication unit 303 may be, for example, a 3G, 4G, 5G, NR, WiFi, WiMax, or other transceivers. In a preferred embodiment, the wireless communication unit 303 of BS 30 includes a 5G NR transceiver. In some examples, the wireless communication unit 303 may also transmit a carrier wave to the wireless device 25 performing uplink backscatter transmission.

[0057] like Figure 3 As shown, in some examples, BS 30 may also include a network communication unit 304 configured to exchange data with other base stations in the RAN and / or with the CN. Network communication unit 305 may support one or more suitable communication protocols, which may be wired (including optical) and / or wireless.

[0058] like Figure 3 As shown, in some examples, BS 30 may also include an energy harvesting signal generator 305 that generates an energy harvesting (RF) signal that enables wireless devices 25 within its coverage area to harvest electrical energy in their energy storage units 255 via their energy harvesting units 254. The energy harvesting (RF) signal may take any suitable form that enables the energy harvesting unit 254 to store electrical energy in the energy storage units 255 of the wireless device 25. The choice of a particular energy harvesting (RF) signal format is specific to and non-limiting embodiments of this disclosure. As mentioned above, such energy harvesting (RF) signals may, when present, be generated alternatively or in combination by other devices separate from BS 30 of the RAN.

[0059] As discussed above, this disclosure aims to achieve efficient allocation of uplink resources to wireless devices 25 by further considering constraints that may limit some wireless devices 25's use of allocated uplink resources. For example, some wireless devices 25 may not have uplink data segmentation capabilities. Wireless devices without uplink data segmentation capabilities will be unable to break down the uplink data they need to transmit into multiple uplink data packets. In other words, for wireless devices without uplink data segmentation capabilities, all available uplink data must be transmitted in a single uplink data packet. Therefore, if the amount of allocated uplink resources is less than the amount of available uplink data, such wireless devices will be unable to use the allocated uplink resources, and these uplink resources will be wasted.

[0060] Therefore, it is recommended to introduce means that enable the RAN to determine whether a given radio device 25 supports uplink data segmentation in order to attempt to ensure that the amount of uplink resources allocated to the radio device 25 is compatible with the uplink data segmentation capability of the radio device 25.

[0061] We now provide examples of signaling policies that can be implemented to enable the RAN to determine the uplink data segmentation capability of radio device 25.

[0062] Explicit Uplink Data Segmentation Capability Report

[0063] Figure 4 This diagram illustrates the steps of an exemplary embodiment of a method 40 for exchanging data implemented by the wireless device 25 of the UE 20. Figure 5 The diagram illustrates the corresponding steps of an exemplary embodiment of a method 50 for exchanging data implemented by the BS 30 of the RAN.

[0064] like Figure 4 As shown, the method 40 for exchanging data includes step S40: sending an indication to the RAN of the uplink data segmentation capability of the radio device 25. In other words, the radio device 25 explicitly informs the RAN whether it supports uplink data segmentation.

[0065] For example, an indication of uplink data segmentation capability can be provided to the RAN as a single bit. For instance, a bit value '1' indicates that radio device 25 does not support uplink data segmentation, while a bit value '0' indicates that radio device 25 supports uplink data segmentation. More generally, the uplink data segmentation capability indication can use any suitable format, and the choice of a particular format is specific to, but not limiting, embodiments of this disclosure.

[0066] It should be noted that the uplink data segmentation capability indication can be sent in any type of signaling message, and the selection of a particular type of signaling message corresponds to a specific but non-limiting embodiment of this disclosure. For example, the radio device 25 can send the uplink data segmentation capability indication in a UE capability message (Radio Resource Control RRC message).

[0067] like Figure 4 As shown, the method 40 for exchanging uplink data includes step S41: the receiving wireless device 25 allocates uplink resources that can be used to transmit uplink data. For example, the allocated uplink resources may be configured licensed CG uplink resources or dynamically licensed uplink resources.

[0068] As discussed above (and below), the allocated uplink resources are determined by the RAN based on the received uplink data fragmentation capability indication. Specifically, the amount of uplink resources allocated to radio device 25 should be compatible with the uplink data fragmentation capability of radio device 25. If radio device 25 supports uplink data fragmentation, the amount of uplink resources allocated can be unrestricted. Conversely, if radio device 25 does not support uplink data fragmentation, the RAN should attempt to ensure that the amount of uplink resources allocated to radio device 25 enables it to transmit all available uplink data without fragmentation. In other words, if radio device 25 does not support uplink data fragmentation, the amount of allocated uplink resources should be equal to or greater than the amount of uplink data available at radio device 25 (because otherwise the uplink resources would be wasted as they would not be usable by radio device 25).

[0069] Therefore, at least when the radio device 25 does not support uplink data segmentation, the RAN should be able to determine or estimate the amount of uplink data that the radio device 25 may need to transmit, so as to allocate a compatible amount of uplink resources to the radio device 25.

[0070] exist Figure 4 In the example, the method 40 for exchanging data includes an optional step S42: the wireless device 25 sends a BSR to the RAN.

[0071] As described above, the Buffer Status Reporting (BSR) procedure is defined in TS 38.321 V18.0.0, and the BSR is used to provide the serving base station 30 of the RAN with information about the amount of uplink data that the radio device 25 wishes to send to the RAN. In the current case, if the radio device 25 has indicated that it does not support uplink data fragmentation, the RAN can use the BSR to ensure that the amount of uplink resources allocated to the radio device 25 is sufficient to send the amount of uplink data indicated in the BSR without fragmentation.

[0072] In some examples, the BSR can be the predicted BSR, or PBSR. The PBSR represents the amount of uplink data that the radio device 25 expects to send to the RAN in the future. "Predicted" means that the PBSR corresponds to a prior estimate of the amount of uplink data that the radio device 25 may need to send during the next uplink transmission before the estimated amount of uplink data has actually arrived at the radio device's uplink data buffer.

[0073] The BSR procedure requires radio device 25 to trigger the Random Access Channel (RACH) procedure and / or the Scheduling Request (SR) procedure. This requires the exchange of several signaling messages between radio device 25 and the RAN. Subsequently, the RAN can trigger uplink data transmission and directly allocate uplink resources to radio device 25, wherein the amount of uplink resources allocated is determined based on the PBSR previously received from radio device 25, without the need for further signaling message exchange between the RAN and radio device 25.

[0074] For example, PBSR is determined by the wireless device 25 based on at least one characteristic of the uplink data to be transmitted by the wireless device 25.

[0075] For example, at least one characteristic of the uplink data to be transmitted may include service category (priority level, latency requirements, etc.) and / or type of radio device 25 and / or type of service running on UE 20. For example, based on the type of service running on the UE, radio device 25 can predict the amount of uplink data it may need to transmit in each uplink data transmission.

[0076] Alternatively or in combination, the radio device 25 may use the history of past uplink data transmissions to predict the amount of uplink data it may need to transmit during the next uplink data transmission. Alternatively or in combination, if the UE 20 periodically generates uplink data of a predetermined size to be transmitted, the radio device 25 may predict the amount of uplink data it may need to transmit during the next uplink transmission based on the approximate time gap between uplink data transmissions triggered by the RAN (this approximate time gap may be estimated, or previously agreed with the RAN, or it may be determined as the average or maximum time gap observed between past uplink transmissions triggered by the RAN).

[0077] Any estimation method can be used to predict the amount of uplink data that can be sent in the next uplink data transmission, and the choice of a particular method corresponds to a particular but non-limiting embodiment of this disclosure.

[0078] In a preferred embodiment, if the wireless device 25 does not support uplink data segmentation, the PBSR transmitted by the wireless device 25 may be conservative; that is, the PBSR may correspond to the maximum amount of uplink data that the wireless device 25 may need to transmit during the next uplink data transmission. However, particularly if the wireless device 25 supports uplink data segmentation, the PBSR may also correspond to, in other examples, the average or minimum amount of uplink data that the wireless device 25 may need to transmit in each uplink transmission triggered by the RAN.

[0079] It should be noted that the PBSR sent can correspond to either a static configuration or a dynamic configuration.

[0080] The term "static configuration" means that the PBSR remains valid for all subsequent uplink transmissions triggered by the RAN, unless overridden by a new static configuration sent by the same radio device 25. With static configuration, the PBSR does not need to be sent before each future uplink transmission triggered by the RAN, and can even be sent only once to the RAN (or at least once per serving BS 30).

[0081] The term "dynamic configuration" means that PBSR remains valid only for a predetermined number of subsequent uplink transmissions, and in some cases, it may remain valid only for a single subsequent uplink transmission.

[0082] PBSRs can be sent in any type of signaling message, and the selection of a particular type of signaling message corresponds to a specific but non-limiting embodiment of this disclosure.

[0083] For example, a signaling message with a PBSR can be sent shortly after RAN certification of radio device 25. For example, the PBSR can be included (possibly along with an uplink data segmentation capability indication) in a UE capability message sent by radio device 25. Including the PBSR in the UE capability message can be used, for example, for static configuration of the PBSR.

[0084] According to another example, the radio device 25 may send a PBSR during an ongoing uplink transmission or at the end of an ongoing uplink transmission (e.g., before the radio device 25 transitions to sleep mode). Such a PBSR sent during or at the end of an ongoing uplink transmission will be used for the next uplink transmission triggered by the RAN. Such a PBSR transmission scheme can be used, for example, for the dynamic configuration of PBSRs, but it can also be used for their static configuration (unless overridden by a new static configuration) if the sent PBSRs are to remain valid for all subsequent uplink transmissions.

[0085] It should be noted that in some embodiments, the static and dynamic configuration methods of the PBSR can also be combined. For example, the radio device 25 may (e.g., in a UE capability message) send a static configuration of the PBSR to be used by default. Subsequently, the radio device 25 may (e.g., during or at the end of an ongoing uplink transmission) send a dynamic configuration of the PBSR that temporarily replaces the static configuration (e.g., only for a predetermined number of triggered uplink transmissions).

[0086] The PBSR can use any suitable format, and the choice of a particular format is specific to, but not limiting, embodiments of this disclosure. In some cases, the format may depend on whether it corresponds to a static or dynamic configuration. For example, the PBSR format may be based on the format of the BSR Media Access Control MAC Control Element CE.

[0087] It should be noted that other methods can be used to enable the RAN to determine or estimate the amount of uplink data that a radio device 25 without uplink data segmentation capability may need to transmit, so as to allocate a compatible amount of uplink resources to the radio device 25.

[0088] For example, the RAN can estimate the PBSR for radio device 25 without the radio device 25 transmitting the PBSR. Essentially, everything described above regarding determining the PBSR for radio device 25 can also be applied to the RAN side. According to another example, the RAN can progressively learn the PBSR for a given radio device 25 that lacks uplink data segmentation capabilities. For example, the RAN can iteratively increase the amount of uplink resources allocated to the radio device 25 until the radio device 25 successfully uses the allocated uplink resources (this implies that uplink resources are sacrificed to some extent during the initial iterations of this learning phase). Therefore, the amount of uplink resources allocated to the radio device 25 in the previous iteration is compatible with the amount of uplink data that the radio device 25 needs to transmit (without segmentation). This amount of uplink resources allocated in the previous iteration can then be used as the PBSR for subsequent (initial) uplink resource allocations for the radio device 25.

[0089] Typically, uplink resources allocated to the wireless device 25 can be indicated to the wireless device 25 in any type of signaling message, and the selection of a particular type of signaling message corresponds to a particular but non-limiting embodiment of this disclosure.

[0090] In some examples, the allocated uplink resources can be indicated in the uplink transmission trigger signal sent by the RAN (particularly if the amount of allocated uplink resources is determined by the RAN based on the PBSR received from radio device 25 or estimated by the RAN). The purpose of the uplink transmission trigger signal is to indicate to radio device 25 that it may initiate uplink data transmission on the uplink resources allocated to radio device 25.

[0091] To reduce the power consumption of the wireless device 25, it can be placed in sleep mode. In this case, the wireless device 25 needs to transition to active mode to perform uplink data transmission. This transition can be triggered by the RAN by sending a wake-up signal to the wireless device 25. In this case, the uplink transmission trigger signal can correspond to the wake-up signal that transitions the wireless device 25 from sleep mode to active mode, or it can be sent by the RAN after it has already sent a wake-up signal to the wireless device 25.

[0092] As discussed above, Figure 5 The diagram illustrates corresponding steps of an exemplary embodiment of a method 50 for exchanging data, which can be implemented in a wireless device 25. Figure 4 The method 40 for exchanging data shown is implemented by BS 30.

[0093] like Figure 5 As shown, the method 50 for exchanging data includes step S50: receiving an indication of uplink data segmentation capability from the wireless device 25 (sent by the wireless device 25 during step S40). As discussed above, the uplink data segmentation capability indication can be received, for example, via a UE capability message, and in some cases can consist of a single bit.

[0094] The method 50 for exchanging data further includes step S51: determining the allocation of uplink resources to the wireless device 25 based on the received indication of the uplink data segmentation capability of the wireless device 25. All previously described for determining the amount of uplink resources to be allocated to the wireless device based on its uplink data segmentation capability applies similarly.

[0095] Specifically, if the wireless device 25 does not support uplink data segmentation, the BS 30 should attempt to ensure that the amount of uplink resources allocated to the wireless device 25 is sufficient for it to send all available uplink data without segmentation.

[0096] For this purpose, at least when the wireless device 25 does not support uplink data segmentation, the BS 30 should be able to determine or estimate the amount of uplink data that the wireless device 25 may need to transmit, so as to be able to allocate a compatible amount of uplink resources to the wireless device 25.

[0097] exist Figure 5 In the example, it is assumed in a non-limiting manner that the wireless device 25 sends a BSR (or PBSR) to the BS 30, and the method 50 for exchanging data includes the optional step S52: the BS 30 receives the (P)BSR from the wireless device 25, such that the allocation of uplink resources can be determined based on the received (P)BSR.

[0098] Generally, any method can be used to predict the amount of uplink data that the wireless device 25 may need to transmit, and the choice of a particular method corresponds to a specific but non-limiting embodiment of this disclosure. For example, as discussed above, in some cases, the BS 30 can unilaterally estimate the PBSR for a given wireless device 25 without the wireless device 25 transmitting the PBSR.

[0099] As discussed above, BS 30 sends an indication of the allocated uplink resources to radio device 25. Typically, the indication of the uplink resources allocated to radio device 25 can be indicated in any type of signaling message, and the selection of a particular type of signaling message corresponds to a specific, but not limiting, embodiment of this disclosure.

[0100] In some examples, the indication of allocated uplink resources may be included in an uplink transmission trigger signal sent by BS 30 to radio device 25. In some cases, the uplink transmission trigger signal may correspond to a wake-up signal that transitions radio device 25 from sleep mode to active mode, or a signaling message sent after sending a wake-up signal to radio device 25 (to transition radio device 25 to active mode before sending the uplink transmission trigger signal).

[0101] In the example where BS 30 includes a power harvesting signal generator 305, BS 30 can, for example, begin sending a power harvesting (RF) signal to wireless device 25 before sending an uplink transmission trigger signal to wireless device 25. In some cases, the power harvesting (RF) signal can be used as a wake-up signal to switch wireless device 25 to an active mode.

[0102] Implicit uplink data segmentation capability determination

[0103] Figure 6 This diagram illustrates the steps of an exemplary embodiment of a method 60 for exchanging data implemented by the wireless device 25 of the UE 20. Figure 7 The diagram illustrates the corresponding steps of an exemplary embodiment of a method 70 for exchanging data implemented by the BS 30 of the RAN.

[0104] basically, Figure 6 and Figure 7 The example shown is the same as Figure 4 and Figure 5 The examples shown are similar, so that unless otherwise explicitly stated, previous references Figure 4 and Figure 5 All of the above applies similarly to Figure 6 and Figure 7The only difference lies in how BS 30 determines whether a given radio device 25 supports uplink data fragmentation. Figure 4 and Figure 5 In the example shown, wireless device 25 explicitly indicates to BS 30 whether it supports uplink data fragmentation. Conversely, in Figure 6 and Figure 7 In the example shown, BS30 determines whether wireless device 25 supports uplink data segmentation based on the type of wireless device 25 among a variety of different wireless device types. This type can be explicitly indicated by wireless device 25 or can be determined by BS30 in other ways.

[0105] For example, the type of wireless device 25 can correspond to the type of A-IoT device. For instance, Section 4.3 of Technical Report TR 38.848 V18.0.0 primarily defines different types of A-IoT devices based on power storage capacity and independent signal generation / amplification capability. Currently, Technical Report TR 38.848 V18.0.0 defines three different types: Type A (no power storage, no independent signal generation / amplification), Type B (power storage, no independent signal generation), and Type C (power storage, independent signal generation). However, more A-IoT device types can be defined, such as subtypes of Type B and Type C, to more precisely define power storage capacity.

[0106] exist Figure 6 In the example shown, in a non-limiting manner, the wireless device 25 explicitly indicates its type to the RAN, and the method 60 for exchanging data includes step S60: sending to the RAN an indication of the type of wireless device 25 among a variety of possible different wireless device types.

[0107] For example, an indication of the wireless device type can be provided to the RAN as a bit vector. For example, a bit vector can consist of two bits, and: - A bit vector value '00' indicates a Type A environment IoT device. - The bit vector value '01' indicates a Type B environment IoT device. - The bit vector value '10' indicates a Type C environment IoT device. - The bit vector value '11' can be reserved for future use (e.g., for IoT devices in a Type D environment).

[0108] Of course, depending on the number of different wireless device types, different numbers of bits can be considered for a bit vector. Furthermore, any suitable format can be used to indicate the type of wireless device, and the choice of a particular format corresponds to a specific, but not limiting, embodiment of this disclosure.

[0109] It should be noted that the radio device type can be sent in any type of signaling message, and the selection of a particular type of signaling message corresponds to a specific but non-limiting embodiment of this disclosure. For example, radio device 25 can send the radio device type in a UE capability message.

[0110] Suppose that the RAN can determine whether the radio device 25 supports uplink data segmentation based on the type of the radio device. For example, as will be discussed below, the RAN can use a predetermined mapping between various radio device types and their corresponding uplink data segmentation capabilities.

[0111] like Figure 6 As shown, the method 60 for exchanging data includes step S61: receiving an allocation of uplink resources. For example, the allocated uplink resources may be CG uplink resources or dynamically licensed uplink resources.

[0112] As mentioned above Figure 4 and Figure 5 As discussed, the allocation of uplink resources is determined by the RAN based on the uplink data segmentation capability of radio device 25 (in the current case, this uplink data segmentation capability is determined based on the type of radio device). Furthermore, as previously discussed, the allocation of uplink resources can be received in any suitable signaling message. For example, the allocation of uplink resources can be received in an uplink transmission trigger signal.

[0113] All the previous statements regarding the determination of uplink resource allocation based on the uplink data segmentation capability of wireless device 25 are similarly applicable to... Figure 6 and Figure 7 Example in [the text]. Figure 6 In the example shown, it is assumed in a non-limiting manner that the determination of uplink resource allocation further utilizes a BSR or PBSR sent by the radio device 25, and the method 60 for exchanging data includes the optional step S62: sending a (P)BSR to the RAN.

[0114] As discussed above, Figure 7 The diagram illustrates corresponding steps of an exemplary embodiment of a method 70 for exchanging data, which can be implemented in a wireless device 25. Figure 6 The method 60 for exchanging data shown is implemented by BS 30.

[0115] like Figure 7 As shown, the method 70 for exchanging data includes step S70: determining the type of wireless device 25 among a variety of different wireless device types. As discussed above, step S70 may involve: BS 30 receiving an explicit indication of the wireless device type from wireless device 25 ( Figure 6(Step S60 in the example). However, in other examples, the type of a wireless device can also be determined without requiring the wireless device 25 to send such an instruction. According to a non-limiting example, the corresponding types of multiple wireless devices 25 can be stored in a database. In this case, BS 30 can retrieve the type of a given wireless device 25 from the database based on, for example, an identifier of the given wireless device 25.

[0116] like Figure 7 As shown, the method 70 for exchanging data includes step S71: determining the uplink data segmentation capability of the wireless device 25 based on a determined type of the wireless device 25. For example, BS 30 may use a predetermined mapping between various different wireless device types and their corresponding uplink data segmentation capabilities. For example, the mapping between various different wireless device types and their corresponding uplink data segmentation capabilities may be predefined (e.g., specified by a standard).

[0117] Table 1 presents a non-limiting example of the mapping between various wireless device types and their corresponding uplink data segmentation capabilities. In this example, four (four) different wireless device types are considered in a non-limiting manner, such as types A, B, C, and D discussed above. Of course, in other examples, different numbers of wireless device types may be considered. Table 1

[0118] In the examples in Table 1, if the determined wireless device type corresponds to type A or type B, then BS 30 considers that the corresponding wireless device 25 does not support uplink data segmentation, and the allocation of uplink resources should take into account this lack of uplink data segmentation support. Conversely, if the determined wireless device type corresponds to type C or type D, then BS 30 considers that the corresponding wireless device 25 supports uplink data segmentation.

[0119] The method 70 for exchanging data further includes step S72: determining the allocation of uplink resources to the wireless device 25 based on the uplink data segmentation capability determined for the wireless device 25. All of the previous description of determining the amount of uplink resources to be allocated to the wireless device based on its uplink data segmentation capability applies similarly.

[0120] Specifically, if the wireless device 25 does not support uplink data segmentation, the BS 30 should attempt to ensure that the amount of uplink resources allocated to the wireless device 25 is sufficient for it to send all available uplink data without segmentation.

[0121] For this purpose, at least when the wireless device 25 does not support uplink data segmentation, the BS 30 should be able to determine or estimate the amount of uplink data that the wireless device 25 may need to transmit, so as to be able to allocate a compatible amount of uplink resources to the wireless device 25.

[0122] exist Figure 7 In the example, it is assumed in a non-limiting manner that the wireless device 25 sends a BSR (or PBSR) to the BS 30, and the method 70 for exchanging data includes the optional step S73: the BS 30 receives the (P)BSR from the wireless device 25, such that the allocation of uplink resources can be determined based on the received (P)BSR.

[0123] Generally, any method can be used to predict the amount of uplink data that the wireless device 25 may need to transmit, and the choice of a particular method corresponds to a specific but non-limiting embodiment of this disclosure. For example, as discussed above, in some cases, the BS 30 can unilaterally estimate the PBSR for a given wireless device 25 without the wireless device 25 transmitting the PBSR.

[0124] As discussed above, BS 30 sends an indication of the allocated uplink resources to radio device 25. Typically, the indication of the uplink resources allocated to radio device 25 can be indicated in any type of signaling message, and the selection of a particular type of signaling message corresponds to a specific, but not limiting, embodiment of this disclosure.

[0125] In some examples, the indication of allocated uplink resources may be included in an uplink transmission trigger signal sent by BS 30 to radio device 25. In some cases, this uplink transmission trigger signal may correspond to a wake-up signal that transitions radio device 25 from sleep mode to active mode, or a signaling message sent after a wake-up signal is sent to radio device 25.

[0126] In the example where BS 30 includes a power harvesting signal generator 305, BS 30 can, for example, begin sending a power harvesting (RF) signal to wireless device 25 before sending an uplink transmission trigger signal to wireless device 25. In some cases, the power harvesting (RF) signal can be used as a wake-up signal to switch wireless device 25 to an active mode.

[0127] It should be emphasized that this disclosure is not limited to the exemplary embodiments described above. Variations of the exemplary embodiments described above are also within the scope of this disclosure.

[0128] For example, this disclosure is made primarily with regard to a wireless device 25 including an energy harvesting unit 254 configured to convert ambient energy into electrical energy stored in an energy storage unit 255. However, in some cases, this disclosure can also be applied to wireless devices 25 that do not include such an energy harvesting unit and operate solely using the energy storage unit 255 (which may be rechargeable or non-rechargeable). This disclosure can also be applied to wireless devices 25 that do not include an energy storage unit and operate solely using the energy harvesting unit 254 (which directly supplies the harvested electrical energy to other devices of the wireless device 25).

Claims

1. A method (40) for exchanging data in a wireless communication system, said method being implemented by a wireless device (25) of said wireless communication system, wherein, The wireless device includes a communication unit (253) configured to exchange data with the radio access network (RAN) of the wireless communication system, wherein the method includes: - (S40) Send an indication of the uplink data segmentation capability of the radio device to the RAN. - (S41) Receive the allocation of uplink resources determined by the RAN based on the indicated uplink data segmentation capability.

2. The method (40) according to claim 1, comprising: (S42) Send a buffer status report (BSR), the BSR including an indication of the amount of uplink data that the radio device may need to send to the RAN, wherein the allocation of uplink resources to the radio device is further determined by the RAN based on the BSR.

3. The method (40) according to claim 2, wherein, The BSR is the predicted BSR, PBSR, wherein the PBSR is transmitted before the wireless device has the uplink data to be transmitted to the RAN.

4. The method (40) according to claim 3, wherein, The indication of the amount of uplink data that the wireless device may need to transmit corresponds to the maximum amount of uplink data that the wireless device may need to transmit in response to receiving an uplink transmission trigger signal from the RAN.

5. The method (40) according to any one of the preceding claims, wherein, The indication of the uplink data segmentation capability is sent in the User Equipment (UE) capability message.

6. The method (40) according to any one of the preceding claims, wherein, The indication of the uplink data segmentation capability is provided as a single bit.

7. The method (40) according to any one of the preceding claims, wherein, The wireless device includes an energy harvesting unit (254) configured to convert ambient energy into electrical energy stored in an energy storage unit (255) of the wireless device.

8. A wireless device (25) comprising at least one memory and at least one processor, said at least one processor being configured to perform the method (40) according to any one of the preceding claims.

9. A user equipment (UE) (20) comprising the wireless device according to claim 8.

10. A method (50) for exchanging data in a wireless communication system, said method being implemented by a base station BS (30) of a radio access network RAN ​​of said wireless communication system, wherein, The BS is configured to exchange data with multiple wireless devices (25), wherein the method includes: - (S50) Receive from the wireless device an indication of the uplink data segmentation capability of the wireless device. - (S51) Based on the received indication of the uplink data segmentation capability of the wireless device, determine the allocation of uplink resources to the wireless device.

11. The method (50) according to claim 10, comprising: (S52) Receive a buffer status report (BSR) from the wireless device, the BSR including an indication of the amount of uplink data that the wireless device may need to send to the BS, wherein the allocation of uplink resources to the wireless device is further determined based on the received BSR.

12. The method (50) according to claim 11, wherein, The BSR is the predicted BSR, PBSR, wherein the PBSR is received before the wireless device has the uplink data to be transmitted to the RAN.

13. The method (50) according to claim 12, wherein, The indication of the amount of uplink data that the wireless device may need to send corresponds to the maximum amount of uplink data that the wireless device may need to send in response to receiving an uplink transmission trigger signal from the BS.

14. The method (50) according to any one of claims 10 to 13, wherein, The indication of the uplink data segmentation capability is received in the user equipment (UE) capability message.

15. The method (50) according to any one of claims 10 to 14, wherein, The indication of the uplink data segmentation capability is provided as a single bit.

16. The method (50) according to any one of claims 10 to 15, wherein, The wireless device includes an energy harvesting unit (254) configured to convert ambient energy into electrical energy stored in an energy storage unit (255) of the wireless device.

17. A base station BS (30) comprising at least one memory and at least one processor, said at least one processor being configured to perform the method (50) according to any one of claims 10 to 16.

18. A wireless communication system comprising at least one base station (30) according to claim 17 and at least one user equipment (20) according to claim 9.

19. A computer program product (252, 302) comprising instructions that, when executed by at least one processor, configure the at least one processor to perform the method (40) according to any one of claims 1 to 7 or the method (50) according to any one of claims 10 to 16.

20. A computer-readable storage medium comprising instructions that, when executed by at least one processor, configure the at least one processor to perform the method (40) according to any one of claims 1 to 7 or the method (50) according to any one of claims 10 to 16.