System and method for buffer control in ultra-wideband communications

Abstract

A method for buffer control in UWB communications in a UWB device is provided. The method includes receiving an indication of a buffer status from another UWB device; and deriving a data transfer control message based on the indication of the buffer status in the other UWB device. The data transfer control message may include an updated time slot allocation for the other UWB device. The method may also include sending the data transfer control message to the other UWB device.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 481,327, filed January 24, 2023, and U.S. Provisional Application No. 63 / 512,210, filed July 6, 2023, which are incorporated herein by reference in their entireties. Technical Field

[0003] The present disclosure relates to ultra-wideband (UWB) communications between UWB devices, and more particularly, to systems and methods for buffer control in UWB communications. Background Art

[0004] Ultra-wideband (UWB) is a wireless communication technology that uses a wide bandwidth, typically around 500 MHz or greater, or a 10 dB bandwidth greater than 20% of the center frequency. Pulsed UWB (IR-UWB) is a specific case of UWB in which signals are transmitted using extremely short pulses (measured in nanoseconds). Pulsed UWB is particularly well-suited for ranging or sensing applications because the pulses are robust to multipath. Another advantage of IR-UWB is its ability to transmit data with low power consumption and low latency.

[0005] Ranging is the process of determining the distance between two devices using UWB technology. The Fine Ranging (FiRa) consortium was established to ensure interoperability between UWB-enabled devices and enable a variety of use cases. FiRa initially focused on ranging, but in recent years has introduced data transfer functionality. Initially, data transfer was introduced as an add-on to ranging sessions: short packets were piggybacked onto ranging messages. However, the buffer status used for data transfer, i.e., reflecting the data queues for transmission and reception, is typically unknown to all UWB devices in the communication, and this can lead to buffer overflows, data loss, or data interference during data transfer. Therefore, improved buffer control is needed to obtain up-to-date information about buffer status from UWB devices. Summary of the Invention

[0006] Embodiments of the present disclosure provide a method for buffer control in UWB communications in a UWB device. The method includes: receiving an indication of a buffer status from another UWB device; and deriving a data transfer control message based on the indication of the buffer status in the other UWB device. The data transfer control message may include an updated time slot allocation for the other UWB device. The method may also include sending the data transfer control message to the other UWB device.

[0007] In some embodiments, the indication of the buffer status comprises a buffer status report that is part of a link layer control packet sent by the other UWB device.

[0008] In some embodiments, the method further includes sending a buffer status request to another UWB device before receiving the buffer status report, the buffer status request including a command requesting a buffer status in the other UWB device. The buffer status report includes a buffer status response responded by the UWB device to the buffer status request.

[0009] In some embodiments, the buffer status report includes an indication of buffer status of a receiver buffer and a transmitter buffer in the other UWB device; and the data transfer control message includes at least one of a timeslot allocation for the receiver buffer and the transmitter buffer or a request for connection termination.

[0010] In some embodiments, the buffer status report includes an indication of the buffer status of at least a receiver buffer and a transmitter buffer for a normal connection, or an indication of the buffer status of a receiver buffer and a transmitter buffer for a secure connection; and the data transfer control message includes a time slot allocation for the receiver buffer and the transmitter buffer for a normal connection, or a time slot allocation for the receiver buffer and the transmitter buffer for a secure connection.

[0011] In some embodiments, the link layer control packet is a dedicated buffer control message and includes: a header field in which all bits indicate the message type of a buffer status report; and a service data unit (SDU) indicating the content of the buffer status report.

[0012] In some embodiments, the link layer control packet is an ACK / NACK control message and includes a header field where a portion of the bits indicate a message type of the ACK / NACK control message and additional bits indicate a buffer status.

[0013] In some embodiments, the buffer status request is part of a link layer control packet, and the link layer control packet includes: a header field in which all bits indicate the message type of the buffer status request; and a service data unit (SDU) indicating the content of the buffer status request.

[0014] In some embodiments, the data transfer control message includes a command to terminate a connection with another UWB device.

[0015] In some embodiments, the indication of the usage of the buffer includes a set of configuration parameters transmitted by the other UWB device over a non-UWB channel, the set of configuration parameters reflecting the status of the buffer in the other UWB device.

[0016] In some embodiments, the non-UWB channel comprises a Bluetooth Low Energy channel.

[0017] In some embodiments, the method further includes sending user data to another UWB device based on the updated time slot allocation.

[0018] In some embodiments, the indication of the buffer status is part of a message sent by another UWB device.

[0019] In some embodiments, the indication of the buffer status is sent by an upper layer of another UWB device to an upper layer of the UWB device.

[0020] Embodiments of the present disclosure provide a UWB device. The UWB device includes: a transceiver operable to perform UWB communication; a memory for storing program instructions and a buffer status of another UWB device; and a processor coupled to the transceiver and the memory. The processor is operable to execute program instructions, which, when executed by the processor, cause the UWB device to perform the following operations to facilitate time slot allocation, thereby supporting data communication from / to another UWB device. The operations include: receiving an indication of a buffer status from another UWB device; and deriving a data transfer control message based on the indication of the buffer status in the other UWB device. The data transfer control message includes an updated time slot allocation for the other UWB device. The operations also include sending the data transfer control message to the other UWB device.

[0021] In some embodiments, the indication of the buffer status comprises a buffer status report that is part of a link layer control packet sent by the other UWB device.

[0022] In some embodiments, the UWB device further includes sending a buffer status request to another UWB device before receiving the buffer status report, wherein the buffer status request includes a command requesting a buffer status in the other UWB device. The buffer status report includes a buffer status response responded by the UWB device to the buffer status request.

[0023] In some embodiments, the buffer status report includes an indication of buffer status of a receiver buffer and a transmitter buffer in the other UWB device, and the data transfer control message includes commands for time slot allocations of the receiver buffer and the transmitter buffer.

[0024] In some embodiments, the link layer control packet includes: a header field indicating a message type of the buffer status report; and a service data unit (SDU) indicating content of the buffer status report.

[0025] In some embodiments, the buffer status request is part of a link layer control packet, and the link layer control packet includes: a header field indicating a message type of the buffer status request; and a service data unit (SDU) indicating the content of the buffer status request.

[0026] Embodiments of the present disclosure provide a method for buffer control in UWB communications in a UWB device. The method includes: configuring a buffer status; transmitting an indication of the buffer status to another UWB device; receiving a data transmission control message from the other UWB device, the data transmission control message including an updated time slot allocation for the buffer based on the indication of the buffer status; and transmitting data in a time slot allocated according to the updated time slot allocation.

[0027] In some embodiments, the indication of the buffer status comprises at least one of: a buffer status report, which is part of a link layer control packet; or a set of configuration parameters, transmitted over a non-UWB channel, the set of configuration parameters reflecting the buffer status in another UWB device.

[0028] In some embodiments, the method includes transmitting the indication of the buffer status without receiving a buffer status request including a command requesting the buffer status.

[0029] Those skilled in the art will appreciate the scope of the present disclosure and become aware of additional aspects thereof after reading the following detailed description of the preferred embodiments and the associated drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure and together with the description serve to explain the principles of the disclosure.

[0031] Figure 1A An exemplary system of a controller ultra-wideband (UWB) device and a controlled UWB device for implementing buffer control according to aspects of the present disclosure is shown.

[0032] Figure 1B An exemplary signaling diagram illustrating a controller UWB device and a plurality of controlled UWB devices implementing buffer control according to aspects of the present disclosure is shown.

[0033] Figure 1C An exemplary architecture of a UWB device for implementing buffer control according to aspects of the present disclosure is shown.

[0034] Figure 1D An architecture of two UWB devices in communication for implementing buffer control according to aspects of the present disclosure is shown.

[0035] Figure 1E An exemplary architecture of a UWB device with multiple buffers for implementing buffer control according to aspects of the present disclosure is shown.

[0036] Figure 2A A frame structure used in UWB communications according to some aspects of the present disclosure is shown.

[0037] Figure 2B Shown are packets used in UWB communication.

[0038] Figure 2C Shown is a message field of a packet used in UWB communication.

[0039] Figures 3A to 3E Each shows an exemplary packet and message fields of a packet for implementing buffer control in UWB communications according to aspects of the present disclosure.

[0040] Figure 4 Another exemplary signaling diagram implementing buffer control using non-UWB channels or out-of-band (OOB) techniques according to aspects of the present disclosure is shown.

[0041] Figure 5A and 5B Each shows a method for implementing buffer control in UWB communications according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0042] The various embodiments described below provide the necessary information to enable a person of ordinary skill in the art to practice the embodiments and illustrate the best modes for practicing the embodiments. After reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will appreciate applications of these concepts not specifically described herein. It should be understood that these concepts and applications are within the scope of the present disclosure and the appended claims.

[0043] It will be understood that although the terms "first," "second," etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used solely to distinguish between different elements. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of this disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0044] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the present disclosure. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are also intended to include the plural forms. It will be further understood that when used herein, the terms "comprises," "comprising," and / or "includes," "including," clearly indicate the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0045] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. It will be further understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and relevant prior art, and should not be interpreted in an idealized or overly formal sense unless expressly defined herein. In addition, similar reference numerals denote similar features throughout the specification and drawings.

[0046] It should be understood that the blocks in each signaling diagram or flowchart, and the combination of the signaling diagrams or flowcharts, can be executed by computer program instructions. Since the computer program instructions can be implemented in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device produce means for performing the functions described in conjunction with one or more blocks of each signaling diagram or flowchart. Since the computer program instructions can be stored in a computer-usable or computer-readable memory, which can be directed to the computer or other programmable data processing device to implement the functions in a specific manner, the instructions stored in the computer-usable or computer-readable memory can produce a product that includes instructions for performing the functions described in conjunction with one or more blocks of each signaling diagram or flowchart. Since the computer program instructions can be implemented in a computer or other programmable data processing device, the instructions that produce a program executed by the computer as a series of operational steps are executed by the computer or other programmable data processing device, and the instructions that operate the computer or other programmable data processing device provide the steps for performing the functions described in conjunction with one or more blocks of each signaling diagram or flowchart.

[0047] Each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing one or more specific logical functions. Furthermore, it should be noted that in some alternative implementations, the functions mentioned in the blocks may occur in a different order. For example, two blocks shown in succession may be executed substantially simultaneously or in reverse order, depending on the corresponding functions.

[0048] Hereinafter, embodiments are described in detail with reference to the accompanying drawings. Furthermore, although a communication system using ultra-wideband (UWB) is described in conjunction with the embodiments, the embodiments may also be applied to other communication systems having similar technical backgrounds or features, as an example. For example, communication systems using Bluetooth or ZigBee may be included. Furthermore, as determined by one of ordinary skill in the art, the embodiments may be modified within such scope without significantly departing from the scope of this disclosure, and such modifications may be applicable to other communication systems.

[0049] UWB may refer to a short-range, high-rate wireless communication technology that uses a wide frequency band of several GHz or more, low spectrum density, and short pulse width (e.g., 1 nsec to 4 nsec) in a baseband state. UWB may mean the frequency band itself to which UWB communication is applied. UWB can achieve secure and accurate ranging between devices. Therefore, UWB achieves relative position estimation based on the distance between two devices, or achieves accurate position estimation of a device based on the distance from a fixed device (whose position is known, also referred to as an anchor device). The present disclosure assumes that a user carries a device that can communicate via UWB (referred to as a "UWB-enabled device" or simply a "UWB device"). More generally, the present disclosure assumes communication between two UWB devices.

[0050] In data transmission, the controller UWB device (or simply the controller) acts as a central scheduler to decide how time slots (or interchangeably in the present disclosure, time slots) can be allocated for data transmission with the controllable UWB devices (or simply the controllable devices) in two directions: downlink (DL, from the controller to the controllable device) and uplink (UL, from the controllable device to the controller). The controllable UWB device sends and receives data in the form of frames, which are transmitted in the time slots allocated by the controller UWB device. Although the controller knows that its own data is to be transmitted to the controllable device (and therefore it can allocate time slots accordingly), it is not aware of the data queues in the controllable device. For example, if the controllable device needs more time slots for data transmission or has completed its data transmission, the controller has no information. Currently, there is no way to inform the controller of the data queues in the controllable device(s).

[0051] To address this issue, the present disclosure provides a new signaling scheme to support buffer status reporting from a slave UWB device and early termination of connections between UWB devices. This signaling scheme will enhance current signaling schemes to make data transfer more efficient. The proposal encompasses signaling during connection establishment, as well as more dynamic signaling during the connection lifecycle, allowing for more immediate release of the connection when appropriate (when there is no more content to transmit).

[0052] Embodiments of the present disclosure provide a feedback mechanism implemented between a controller UWB device and a controlled UWB device to help the controller UWB device confirm the buffer status in the controlled UWB device and thus more accurately allocate time slots for data transmission. In the present disclosure, a UWB device (e.g., a controlled UWB device) can send a buffer status report to another UWB device (e.g., a controller UWB device) to report the buffer status. The UWB device can send a buffer status report voluntarily or in response to a buffer status request sent by another UWB device. The other UWB device can transmit a data transmission control message accordingly to maintain or adjust the time slot allocation. For example, the buffer status report may include information about the occupancy of the buffer for receiving and transmitting data, so that the other UWB device can decide to change or maintain the time slot allocation of the UWB device, and / or terminate the connection. Therefore, the controller UWB device and the controlled UWB device can transmit data in the time slot allocated based on the buffer status of the controlled UWB device.

[0053] The buffer status report and buffer status request can each be in a link layer control packet, where the header indicates the message type (e.g., buffer status message). In some embodiments, the header may also include information about the buffer status (e.g., usage and / or occupancy). In some embodiments, the buffer status is included in the service data unit (SDU) of the packet. In some embodiments, the UWB device includes more than one buffer for receiving data (e.g., for normal (or general) communication and safety communication) and more than one buffer for transmitting data (e.g., for normal communication and safety communication). The SDU may include a bitmap indicating the usage of all buffers. The link layer control packet can be generated and processed by the UWB device at the link layer level, without having to be processed by upper layers (e.g., at the application layer).

[0054] In some embodiments, prior to data transmission, UWB devices may exchange a buffer status report as part of a parameter with each UWB device to configure the UWB devices and determine time slot allocation by one of the UWB devices (e.g., a controller). In some embodiments, this exchange is performed over an out-of-band (OOB) channel, such as a Bluetooth channel. The proposed system and method can facilitate more efficient and accurate time slot allocation in UWB communications and dynamically meet the actual needs of the controlled UWB device. As a result, more stringent application requirements can be met while reducing the risk of buffer overflows. This can result in shorter communications, saving time, battery life, and cost. In addition, direct communication between UWB devices at the link layer level can further reduce communication time and cost. In some embodiments, the method and system can be implemented between a user mobile device (e.g., a controlled device) and a UWB device (e.g., a controller) installed at a point of sale (POS). The user mobile device can be the controlled UWB device, and the UWB device installed at the POS can be the controller UWB device. The disclosed method and system can optimize data transfer between controller and controlled UWB devices and can potentially reduce payment time.

[0055] Figure 1AAn exemplary system 100 for implementing buffer control in UWB communications according to one embodiment of the present disclosure is depicted. System 100 may include a UWB device 102 that wirelessly communicates with another UWB device 104, as symbolically illustrated by wireless link 114. UWB device 102 may be a controller UWB device (or simply controller), and UWB device 104 may be a controlled UWB device (or simply controlled device) in wireless communication. UWB device 102 may be an onboard computer or a mobile device. In some embodiments, UWB device 104 is a mobile device. For example, UWB device 102 may be a device installed at a point of sale for contactless payment, and UWB device 104 may be a user mobile device. It should be noted that the terms "mobile device," "mobile handset," "wireless handset," and "user equipment (UE)" are used interchangeably hereinafter to refer to wireless communication devices capable of voice and / or data communication. Some examples of such mobile handsets include smartphones, tablet computers, and wearable devices. It is observed here that the UWB device 102 may not necessarily be a separate computing unit (in the form of hardware or software) dedicated to performing buffer control functionality. In one embodiment, the functionality of the UWB device 102 may be implemented in a physical computing / data processing unit or (non-physical) server software already existing in the cloud. The wireless link 114 may include a UWB communication interface. The wireless link 114 may also support other types of wireless connections, such as a Bluetooth communication interface, a Wi-Fi communication interface, a cellular network connection (e.g., 4G, 5G) interface, a near field communication (NFC) interface, a ZigBee communication interface, or a combination thereof.

[0056] Control unit 124 / 126 is one of the mobile applications installed in UWB devices 102 / 104, respectively. In addition to control unit 124 / 126, UWB devices 102 and 104 may each have one or more mobile applications (e.g., controller application 106 / controller application 116) resident therein. These mobile applications are software modules that may be pre-packaged with the respective UWB devices 102 / 104 or may have been downloaded by a user to the memory (not shown) of the respective UWB devices 102 / 104. For example, UWB device 102 may also store other controller-specific applications in its memory (not shown), such as applications that facilitate Ethernet-based communications, applications that interact with the cloud, and the like. In some embodiments, control units 124 and 126 perform buffer control for UWB communications. For example, control units 124 and 126 may generate and process control packets transmitted between UWB devices 102 and 104 to implement buffer control functionality. A detailed description is included below. Mobile applications and control units (e.g., 124 and 126) can be executed by a processor under the control of a mobile operating system (e.g., controller operating system 110 and controlled device operating system 120, respectively). The UWB device 102 can include a relatively high-power controller central processing unit (CPU) 112 that executes the controller operating system 110. The UWB device 102 can further include a wireless interface 108 to facilitate wireless communication with the UWB device 104 via a wireless link 114. Applications (e.g., 106 and 124) can utilize the wireless interface 108 as needed.

[0057] Due to the battery-powered nature of mobile devices, in some embodiments, the processor of the UWB device 104 (e.g., the slave CPU 122) can be designed to conserve battery power, such as being a relatively low-power CPU. The UWB device 104 can communicate wirelessly with the UWB device 102 via its own wireless interface 118. The wireless interface units 108 and 118 can wirelessly transmit data or information between the UWB device 102 and the UWB device 104 using the wireless link 114 as shown.

[0058] Thus, in operation, device-generated signals can be wirelessly transmitted from one UWB device (e.g., UWB device 102) to another UWB device (e.g., UWB device 104) for further processing by the CPU of the other UWB device (e.g., CPU 122), and vice versa. Specifically, a signal can be transmitted from the wireless interface of one UWB device (e.g., wireless interface 108 of UWB device 102) to the wireless interface of another UWB device (e.g., wireless interface 118 of UWB device 104) via wireless link 114. A device-generated signal (e.g., a voluntary signal or a response to a request) from a UWB device (e.g., UWB device 102 or 104) can be provided by the wireless interface (e.g., wireless interface 108) in a wireless format recognized by the device and ultimately delivered to the other wireless interface (e.g., wireless interface 118) via wireless link 114. The resulting wireless "link" between wireless interfaces 108 and 118 is symbolically illustrated by a bidirectional arrow. As discussed above, wireless link 114 may represent a hybrid wireless communication method that combines UWB communication with one or more wireless communications other than UWB (e.g., Bluetooth, Wi-Fi, and / or cellular data). As will be discussed in further detail below, control units 124 and 126 may collect buffer-related information and generate link layer (LL) control messages / packets containing requests for the buffer status of another UWB device or indications of its own buffer status. A wireless interface (e.g., wireless interface 108 or 118) may transmit or receive physical layer packets containing LL control messages in the form of device-generated signals. A CPU (e.g., CPU 112 or 122) may generate LL control messages related to buffer control (e.g., requests for buffer status and / or voluntary reporting of buffer status) and process received LL control messages (e.g., requests for buffer status and / or responses to such requests with information about buffer status). By handling buffer control directly at the link layer level, UWB devices (eg, UWB devices 102 and 104) may not need to process packets from upper layers (eg, application layers or software). Packet processing can be more efficient, thereby reducing transmission time and cost.

[0059] Figure 1BAn exemplary embodiment of a controller UWB device communicating with one or more controllable UWB devices according to some embodiments of the present disclosure is shown. Controller 102a (e.g., controller UWB device) may be an instance of UWB device 102. Controllable devices #1 104-1, ..., and controllable devices #n 104-n may represent n controllable UWB devices, each of which is an instance of UWB device 104 (n is a positive integer). In some embodiments, after establishing a UWB connection between controller 102a and a controllable device (e.g., controllable devices #1 104-1, ..., and / or controllable devices #n 104-n), controller 102a may transmit a buffer status request message 132 to each controllable device (e.g., controllable devices #1 104-1, ..., and / or controllable devices #n 104-n). As will be described in detail later, the buffer status request message 132 includes an LL control message that inquires about the buffer status (eg, usage and / or occupancy) of each of the controllables #1, . . . , and the controllables #n.

[0060] Upon receiving the buffer status request message 132, the controllers (e.g., controller #1 104-1, ..., and / or controller #n 104-n) may transmit a buffer status response message 134 (e.g., a buffer status report message) to the controller 102a. The buffer status response message 134 may include an LL control message indicating the usage of one or more buffers in the corresponding controller. For example, the LL control message may include the usage of one or more buffers for receiving data and the usage of one or more buffers for transmitting data. After receiving the buffer status response message 134, the controller 102a may determine the time slot to be allocated to each of the controllers (e.g., controller #1 104-1, ..., and controller #n 104-n) and generate a data transfer control message 136 (e.g., a data transfer phase control message or DTPCM) based on the buffer status(es) provided in the buffer status response message 134. The data transfer control message may include updated time slot assignments (e.g., determined by controller 102a) for the slaves (e.g., slave #1 104-1, ..., and / or slave #n 104-n). For example, the updated time slot assignments may include time slots assigned for receiving data and / or transmitting data by the slaves based on buffer status provided by the slaves. In some embodiments, the time slots assigned to the slaves for receiving data are determined based at least on the buffer usage / occupancy of the slaves' receiver buffers, and the time slots assigned to the slaves for receiving data are determined based at least on the buffer usage / occupancy of the slaves' transmitter buffers. Thus, the slaves may transmit data 138 in the assigned (e.g., updated) time slots for transmitting data, and / or controller 102a may transmit data 140 to the slaves in the assigned (e.g., updated) time slots for receiving data. In some embodiments, the data transfer control message may additionally or alternatively include a command to terminate the connection early (if the slave reports that it has no data to transmit). A slave receiving the data transfer control message 136 may terminate the connection.

[0061] In some embodiments, a controller (e.g., controller #1 104-1, ..., and / or controller #n 104-n) sends a buffer status report message to controller 102a without any buffer status request message 132. For example, after establishing a UWB connection between controller 102a and a controller (e.g., controller #1 104-1, ..., and / or controller #n 104-n), the controller may voluntarily send a buffer status report message to controller 102a. The buffer status report message may include an LL control message indicating the usage and occupancy of one or more buffers for receiving data and one or more buffers for transmitting data in the corresponding controller. After receiving the buffer status report message, controller 102a may generate a data transfer control message (e.g., a data transfer phase control message or DTPCM) 136 based on the buffer status(es) provided in the buffer status report message for use in slave time slot allocation and / or early termination of the connection, as described above.

[0062] Figure 1C FIG2 shows an architectural diagram (eg, a layered view) of a UWB device 101 according to some embodiments of the present disclosure. The UWB device 101 may be an example of the UWB devices 102 and 104. Figure 1C , a UWB device 101 may include one or more upper layers 103, a UWB control interface (UCI) 105, a secure element (SE) interface 109, a link layer 111, a media access control (MAC) layer 113, a physical (PHY) layer 115, a UWB radio interface 117, and a control module 119. In some embodiments, the UCI 105, the link layer 111, the MAC layer 113, the PHY layer 115, the SE interface 109, and the UWB radio interface 117 may be referred to as a UWB system (UWBS) 107.

[0063] The PHY layer 115 is configured to transmit data (e.g., packets, such as control packets and data packets) using its interfaces, such as the UWB radio interface 117. The PHY layer 115 provides an electrical, mechanical, and / or programmatic interface with the transmission medium. The MAC layer 113 is configured to control the hardware responsible for interacting with wired, optical, and / or wireless transmission media. The link layer 111 is configured to provide methods and communication protocols that are limited to the link to which the UWB device 101 is connected. For example, the link layer 111 generates packets by framing data bits such as the source and destination addresses, information for detecting and controlling transmission errors, the message type, and an indication of the buffer status for the data stream. The SE interface 109 allows the UWB S107 to communicate directly with the SE via the link layer 111, the MAC layer 113, the PHY layer 115, and the SE interface 109. The upper layer 103 may include layers above the link layer 111, such as the network layer, the transport layer, the session layer, the presentation layer, and the application layer, each of which has its own corresponding functionality for UWB system communication. The upper layer 103 communicates with the UWBS 107 through the UCI 105 . The UCI 105 may allow a host (eg, the UWB device 101 ) to configure and control the UWBS 107 and collect information forming the UWBS 107 , and may allow the UWBS 107 to receive configuration parameters from the upper layer 103 .

[0064] Control module 119 can control the functions of link layer 111. For example, control module 119 can control the generation, reception, and analysis of link layer control messages. Control module 119 can be a dedicated entity for controlling link layer 111, or it can be part of a more general control entity of UWB device 101 for controlling various other layers. For example, control module 119 can perform some or all of the functions of control unit 124 (and / or control unit 126). For example, control module 119 can include any suitable hardware and / or software capable of controlling link layer 111. Control module 119 can allow packets transmitted between two UWB devices to be parsed and executed at the link layer level, without having to transmit and parse the packets at higher layers. In some embodiments, control module 119 is communicatively connected to upper layer 103 to collect / receive configuration inputs. On the transmitter side, control module 119 can use the collected / received information to construct a link layer (LL) header and append the LL header to the LL packet data unit (PDU). On the receiver side, the control module 119 may use the collected / received information to parse the received LL header and determine the actions to be performed accordingly.

[0065] UCI 105 may configure the data to be transmitted based on information collected from upper layers 103. The data to be transmitted may further be used to determine buffer status. In some embodiments, UWB device 101 may include commands in UCI 105 to provide information about the data to be transmitted, or more generally, to configure data transmission. For example, the commands may include information collected by UCI 105 regarding the size of the complete data message to be transmitted, the connection type for transmission, and / or possible proposals for time slot allocation. UCI 105 may transmit data and / or parameters to UWBS 107 for control module 119 to construct frames for various layers.

[0066] Figure 1D A hierarchical view of two UWB devices in communication according to some embodiments of the present disclosure is shown. Specifically, Figure 1D A data plane showing packet exchange and a control plane showing control packet exchange between UWB device 121 and UWB device 123 are shown. UWB device 121 may be an instance of one of UWB devices 102 and 104, and UWB device 123 may be an instance of the other of UWB devices 102 and 104. UWB devices 121 and 123 include control modules (e.g., control modules 119a and 119b), respectively, which are instances of control module 119. UWB device 121 may include a link layer 111a, a MAC layer 113a, a PHY layer 115a, and an upper layer 103a; and UWB device 123 may include a link layer 111b, a MAC layer 113b, a PHY layer 115b, and an upper layer 103b. The link layer (e.g., 111a and 111b), the MAC layer (113a and 113b), the PHY layer (115a and 115b), and the upper layer (103a and 103b) may be examples of the link layer 111, the MAC layer 113, the PHY layer 115, and the upper layer 103, respectively. Dashed lines represent the exchange of control packets, and dash-dotted lines represent the exchange of packets. In some embodiments, the upper layer 103a includes or is coupled to a receiver ("RX") buffer 151a and a transmitter ("TX") buffer 152a; and the upper layer 103b includes or is coupled to an RX buffer 151b and a TX buffer 152b. The UWB device 121 or 123 may collect usage / occupancy information for the corresponding RX and TX buffers (e.g., 151a and 152a, or 151b and 152b) and may transmit the information to lower layers, such as the corresponding link layer, MAC layer, and PHY layer, for use in constructing control messages.

[0067] like Figure 1DAs shown in FIG, when UWB devices 121 and 123 communicate, packets may be transmitted through the link layer (e.g., link layer 111a or 111b), the MAC layer (e.g., MAC layer 113a or 113b), the PHY layer (e.g., PHY layer 115a or 115b), and transmitted to the upper layer (e.g., upper layer 103a or 103b) of each UWB device (e.g., UWB device 121 or 123). The exchange of data packets is represented by arrow 125 between the upper layers of UWB devices 121 and 123. Control packets may be transmitted through the link layer, MAC layer, and PHY layer of each UWB device. In some embodiments, the control packets are processed by the corresponding control module (e.g., control module 119a or 119b) and are not further transmitted to the upper layers of the corresponding UWB device. For example, a control module (e.g., control module 119a) is configured to generate LL control messages / packets containing indications of buffer status (e.g., usage and / or occupancy) of a corresponding UWB device (e.g., RX buffer 151a and TX buffer 152a of UWB device 121), and may also receive, parse, and analyze LL control messages / packets containing indications of buffer status (e.g., RX buffer 151b and TX buffer 152b) from another UWB device (e.g., UWB device 123). In various embodiments, the buffer status of one or both of the RX and TX buffers is transmitted in an LL control message. The control module (e.g., control module 119a) may also determine an action based on the received indications of buffer status, such as adjusting the time slot allocation of the UWB device (e.g., UWB device 121), terminating the connection, etc. The exchange of control packets between the control modules of UWB devices 121 and 123 is represented by arrow 127.

[0068] Figure 1E 14. A scenario is shown in which a UWB device 131 has more than one buffer for receiving data and more than one buffer for transmitting data according to some embodiments of the present disclosure. The UWB device 131 may be an instance of the UWB device 102 or 104. In a layered view, the UWB device 131 may include an upper layer 133, a UCI 135, a link layer 141, a MAC layer 143, a PHY layer 145, a UWB radio interface 147, an SE interface 139, and a control module 149. The link layer 141, the MAC layer 143, the PHY layer 145, the SE interface 139, the UCI 135, the control module 149, and the UWB radio interface 147 may be referred to as a UWBS 137. These parts of the UWB device 131 may be connected to Figure 1C The corresponding parts shown in FIG are similar and are not described in detail again. Figure 1EAs shown in FIG, UWB device 131 includes more than one buffer for receiving data and more than one buffer for transmitting data. For example, UWB device 131 may include a TX buffer 161 for transmitting data for normal communication (e.g., from / to upper layer 133 via UCI), and an RX buffer 162 for receiving data for normal communication. UWB device 131 may also include a TX buffer 163 for transmitting data for secure communication (e.g., from / to a secure element via SE interface 139), and an RX buffer 164 for receiving data for secure communication. In other words, UWB device 131 may include multiple buffers to handle multiple qualities of service. In some embodiments, a single LL control message may be used to indicate the status of one or more buffers (e.g., each buffer), as described in detail below.

[0069] Figure 2A The process of forming packets for transmission through different layers of a UWB device is shown. Packets containing various data, such as user data, may be transmitted from upper layers (e.g., upper layers 103 and / or 133) and / or a secure element to a UWB radio interface (e.g., UWB radio interface 117 and / or 147). Figure 2A As shown in FIG, on the transmitter side, a data payload (e.g., LL SDU) may be provided to a UWBS (e.g., UWBS 107 and / or 137) via UCI (e.g., UCI 105 and / or 135) and then to a link layer (e.g., link layer 111 and / or 141). The payload may be segmented, and an LL header may be appended to the segments. The LL header and segments may be from an LL packet data unit (PDU). The LL PDU may then be transmitted to the MAC layer (e.g., MAC layer 113 and / or 143). The LL PDU may then be embedded in a MAC payload (or MAC SDU or MSDU). The MSDU may be appended to the MAC header and MAC footer to form a MAC frame or MAC protocol data unit (MPDU). The MPDU may be transmitted to the PHY layer (e.g., PHY layer 115 and / or 145). The MPDU may then be embedded in a PHY payload (or physical layer aggregation procedure SDU or PSDU). The PSDU may be appended to a PHY header and a synchronization header (or SHR) to form a physical layer protocol data unit or (PPDU). The PPDU may then be transmitted to another UWB device (over a UWB radio interface or SE interface).

[0070] On the receiver side, a packet from another UWB device may be received at the PHY layer (e.g., PHY layer 115 and / or 145) and may be parsed at the PHY layer level, the MAC layer level (e.g., MAC layer 113 and / or 143), and the link layer level (e.g., link layer 111 and / or 141). For example, a link layer PDU may be received at the link layer and may be processed.

[0071] The slave UWB device may transmit data to the controller UWB device in the buffer(s) in its PPDU. In an embodiment of the present disclosure, when the number of time slots allocated to the slave UWB device for transmitting data is updated (e.g., in a data transfer control message), the slave UWB device may transmit data (e.g., data 138) to the controller UWB device in the allocated / updated time slots. When the number of time slots allocated to the slave UWB device for receiving data is updated (e.g., in a data transfer control message), the controller UWB device may transmit data (e.g., data 140) to the slave UWB device in the allocated / updated time slots.

[0072] Figure 2B The conventional design of LL packet is shown, which includes an LL header for connectionless (CL) mode. The LL header usually contains at least the following information: the type of LL packet, a sequence number, a segment (or link) indicator, the size of the actual packet payload, and an indicator of the logical connection to which the packet belongs. Figure 2C Shown Figure 2B The existing definitions of message fields in LL packets are shown in . Figure 2B and 2C As shown in , existing LL packets, such as LL control messages, do not have a field for indication of buffer status.

[0073] Embodiments of the present disclosure introduce a novel LL control message that includes an indication of a buffer status. The LL control message may be referred to as a buffer status message, which queries or provides the buffer status of a controlled UWB device (e.g., UWB device 104). The buffer status message may include a buffer status request message, which is transmitted by a controller UWB device (e.g., UWB device 102) and received by a controlled UWB device (e.g., UWB device 104) for the controller UWB device to request the buffer status of the controlled UWB device. The buffer status message may also include a buffer status report message, which is transmitted by a controlled UWB device to the controller UWB device to report the buffer status of the controlled UWB device. The buffer status report message may be sent voluntarily (or proactively) by the controlled UWB device, or may be a response to a buffer status request message. Specifically, when the buffer status report message is sent as a response, the buffer status report message may also be referred to as a buffer status response message. In some embodiments, the slave UWB device may also send a buffer status request message to the controller UWB device to request the controller UWB device to provide its buffer status (eg, usage and / or occupancy).

[0074] The disclosed LL control messages, such as buffer status messages, can be distinguished from other LL control messages by their LL headers and / or content. For example, a buffer status request message may include an indication in its LL header that it is a buffer status message or a buffer status request message, and may have no content. In some embodiments, the content of the buffer status request message includes an indication of the current time slot allocation for the controlled UWB device, the size of the data to be transmitted to the controlled UWB device, etc. The buffer status report message and / or buffer status response message may indicate information such as the current buffer status of the controlled UWB device(s), whether the current time slot allocation is sufficient, whether the connection with the controller UWB device should be terminated, etc.

[0075] Figures 3A to 3E Various examples of LL packet header structures in a buffer status response message or a buffer status report message according to some embodiments of the present disclosure are shown. Figure 3AAn LL packet structure 300 of an exemplary LL control message in CL mode according to an embodiment of the present disclosure is shown. An LL control message may include an LL header (e.g., a CL header) and an SDU. The Message_Type field of an LL control message, typically containing 6 bits of data, may indicate that the LL control message, e.g., an LL packet, is a buffer status message. The SDU field of the LL control message may indicate the buffer status of a UWB device (e.g., a slave UWB device). As described above, LL control messages may be transmitted from a slave UWB device to a controller UWB device, and vice versa.

[0076] The Message_Type field can be defined to distinguish buffer status messages from other LL control messages. In some embodiments, different types of buffer status messages are distinguished. For example, 0x00-0x7F can be used to indicate data messages, and 0x80-0xFF can be used to indicate various LL control messages as follows:

[0077] 0x80-0x8F: Control messages for managing connection establishment

[0078] 0x90-0x9F: Control messages related to connection maintenance

[0079] 0xA0-0xAF: Control messages related to connection release

[0080] 0xB0-0xBF: Control messages related to buffer status:

[0081] ○0xB0: Buffer status request

[0082] ○0xB1: Buffer status response

[0083] ○0xB2: Buffer status report

[0084] The SDU field of the LL control message can indicate the buffer status of the UWB device. For example, message 0x0 indicates "No more content to transmit, no retransmissions expected, the connection can be closed." Message 0x1 can indicate "Rx (receiver) buffer occupancy is above a threshold (e.g., 50%)." In some embodiments, such an indication of the Rx buffer can be used to instruct the controller to reduce the data transmission rate. Message 0x2 can indicate "Tx (transmitter) buffer occupancy is above a threshold (e.g., 50%)." In some embodiments, such an indication of the Tx buffer can be used to request more allocated time slots from the controller to avoid buffer overflow. 0x3 can indicate "There is still data to transmit, the current time slot allocation is good, no change is required." Messages 0x4-0xFF can indicate RFU (reserved for future use).

[0085] Figure 3BAnother LL packet header structure 302 of an exemplary LL control message according to some embodiments is shown. The LL packet header structure 302 may be a more generalized form of the LL packet header structure 300. In some embodiments, instead of having a source address and a destination address, the LL packet header structure 302 may include a connection identifier to characterize the connection between the source and the destination. In some embodiments, the transmission Figure 3A and 3B A UWB device (eg, a slave UWB device) that receives an LL control message in the LL control message may include a buffer for receiving data and a buffer for transmitting data.

[0086] Figure 3C Another LL packet header structure 304 is shown for an exemplary LL control message according to some embodiments. Figure 3C A UWB device (eg, a slave UWB device) that receives LL control messages in the LL control message may include more than one buffer for receiving data and more than one buffer for transmitting data. Figure 3A and 3B The LL control message shown in Figure 3C The SDU of the LL control message in the bitmap may indicate the buffer status of more than one buffer for receiving data and more than one buffer for transmitting data. For example, the SDU may indicate the usage and occupancy of all buffers.

[0087] For example, returning a reference Figure 1E As described in the UWB device, the UWB device may include a buffer for transmitting data for normal communication, a buffer for receiving data for normal communication, a buffer for transmitting data for secure communication, and a buffer for receiving data for secure communication. In some embodiments, as Figure 3C As shown in , the SDU of the LL control message indicates the buffer status of all buffers for normal and security connections.

[0088] Figure 3D Another LL packet header structure 306 is shown for an exemplary LL control message according to some embodiments. Figure 3D An alternative method for indicating buffer status by adding additional bits to existing LL control messages is presented. The additional bits can fully indicate the buffer status, and the buffer status message content is not required in the SDU. For example, 2 bits of data can be added to the current Message_Type field of an existing LL control message (e.g., an ACK / NACK LL control message) to produce an 8-bit Message_Type field. These 2 bits can fully indicate the buffer status of the UWB device, and the buffer status message content is not required in the LL control message.

[0089] In some embodiments, the buffer status message can be embedded in other existing control messages. For example, additional fields and / or additional bits can be added to existing control messages to indicate the buffer status of the UWB device. In one example, a new field can be added to the existing command SET_APP_CONFIG_CMD. The command can provide the size of the data message to be transmitted. The field can be BUFFER_INDICATION_FIELD (or similar) to indicate the size of the data message to be transmitted.

[0090] Figure 3E Another LL packet header structure 308 of an exemplary LL control message according to some embodiments is shown. In some embodiments, a UWB device (eg, a controller UWB device) may Figure 3E The LL control message in the LL packet is transmitted to another UWB device (e.g., a slave UWB device) to request a buffer status report / response message. The Message_type field may indicate whether the LL packet is a buffer status message or a buffer request message, and the content may be empty. In alternative embodiments, the content may include an indication of the current time slot allocation of the slave UWB device, the size of the data to be transmitted to the slave UWB device, etc.

[0091] Return Reference Figure 1B As described, a UWB device (e.g., a controller UWB device) may adjust or maintain the time slot allocation for data transmission of another UWB device (e.g., a controlled UWB device), and / or terminate the connection with the other UWB device if neither the controller nor the controlled UWB device has more data to transmit. The controller UWB may determine an operation and transmit an operation command to the controlled UWB device in a data transfer control message (e.g., DTPCM). The controlled UWB device may transmit its data in the updated time slot according to the command, or disconnect from the controller UWB device.

[0092] Figure 4 A signaling diagram illustrating a controller UWB device and a controlled UWB device exchanging buffer status information using out-of-band (OOB) technology according to some embodiments of the present disclosure. In some embodiments, the exchange of buffer status information is performed before the UWB connection / communication begins.

[0093] like Figure 4As shown in FIG, UWB device 1 and UWB device 2 may represent a controller UWB device and a controlled UWB device, respectively. In step 402, UWB device 1 and UWB device 2 may first discover their environment using non-UWB technology, so-called out-of-band (OOB) technology. In some embodiments, Bluetooth Low Energy is considered OOB. Then, in step 404, the two devices may establish an OOB channel for communication. In step 406, using the OOB communication channel, the two devices exchange a minimum set of parameters for operating UWB functions. For example, the two devices may exchange: basic information regarding the UWB configuration, such as the channel to be used; UWB parameters, such as the block and slot duration to be used, PHY and MAC mode, etc. In some embodiments, the UWB configuration information / parameters also include (multiple) buffer status report messages as part of this OOB exchange. For example, the controlled UWB device and / or the controller UWB device may use OOB technology to exchange the predicted size of the data message to be transmitted in the UWB communication. In some embodiments, the operations performed in steps 402 through 406 are part of step 418 , ie, the OOB procedure prior to the initial UWB transaction.

[0094] During step 418, e.g., discovery and / or parameter exchange, the two devices may also select one of them as the controller UWB device (e.g., UWB device 1) and the other as the slave UWB device (e.g., UWB device 2). The controller UWB device may then use the parameters received from the slave to determine / update the time slot allocation for the slave UWB device, as described above.

[0095] UWB devices 1 and 2 may be conditioned to initiate UWB communication in steps 408 and 410, respectively. Then, in step 412, UWB operations (e.g., ranging, communication, etc.) may begin. UWB operations may include any suitable operations, such as ranging, communication, etc. During UWB operations, the controller UWB device may utilize the OOB channel and / or the UWB radio interface to request additional input from the controlee regarding the state of data communication, such as the size of new data to be transmitted or any other data to be transmitted, so that the controller UWB device can control the data connection with the controlee UWB device. The controller UWB device may then update the time slot allocation accordingly and / or terminate the session if no more data needs to be transmitted. After the OOB signaling exchange is complete, the controller UWB device and the controlee UWB device may continue UWB operations (e.g., ranging, communication, etc.) in step 416. In some embodiments, the operations performed in step 414 are part of step 420, i.e., the OOB procedures that provide side information and support ongoing UWB transactions.

[0096] Figure 5A5 is a flow chart of a method 500 for implementing buffer control in a UWB system for a UWB device (e.g., a controller UWB device) according to some embodiments of the present disclosure. The method 500 is merely an example and is not intended to limit the present disclosure beyond what is explicitly recited in the claims. Additional operations may be provided before, during, and after the method 500, and some of the operations described may be replaced, removed, or moved around for additional embodiments of the method 500. For ease of illustration, the method 500 is described in conjunction with Figure 1B and 3A To 3E description Figure 5A .

[0097] At step 502, an indication of a buffer status is received from another UWB device. Figure 1B , the controller UWB device 102a may receive a buffer status report message (or buffer status response message 134) from a controlled UWB device (e.g., controlled UWB device #1 104-1). The buffer status report message (or buffer status response message 134) may include usage of one or more buffers in the controlled UWB device. Figures 3A to 3D Description.

[0098] At step 504, a data transfer control message is derived based on the indication of the buffer status in the other UWB device, the data transfer control message including the updated time slot allocation for the other UWB device. Return to Reference Figure 1B , the controller UWB device 102a may derive a data transfer control message based on an indication of the usage of the buffer(s) in the controlled UWB device (e.g., the controlled UWB device #1 104-1). The data transfer control message, such as a data transfer phase control message (DTPCM), may include updated time slot allocations and / or connection terminations for the controlled UWB device, as well as commands allowing the controlled UWB device to transmit data in the newly allocated time slots. In some embodiments, the newly allocated time slots may include time slots for transmitting data to the controlled UWB device, as well as time slots for the controlled UWB device to transmit data. In some embodiments, the time slot allocated to the controlled UWB device to receive data (e.g., from the controller UWB device 102a) is determined based at least on the buffer usage / occupancy of the receiver buffer of the controlled UWB device (e.g., the number of data queues in the receiver buffer), and the time slot allocated to the controlled UWB device to transmit data is determined based at least on the buffer usage / occupancy of the transmitter buffer of the controlled UWB device (e.g., the number of data queues in the transmitter buffer).

[0099] At step 506, the data transfer control message is sent to another UWB device. Figure 1B, the controller UWB device 102a may transmit a data transfer control message to the controlled UWB device (e.g., the controlled UWB device #1 104-1), so that the controlled UWB device may accordingly follow the command in the data transfer control message. In some embodiments, the controller UWB device 102a may transmit data in the newly allocated time slot to the controlled UWB device.

[0100] Figure 5B 5 is a flow chart of a method 501 for implementing buffer control in a UWB system for a UWB device (e.g., a slave UWB device) according to some embodiments of the present disclosure. The method 501 is merely an example and is not intended to limit the present disclosure beyond what is explicitly recited in the claims. Additional operations may be provided before, during, and after the method 501, and some of the operations described may be replaced, removed, or moved around for additional embodiments of the method 501. For ease of illustration, the method 501 is described in conjunction with Figure 1B 、 1C , 1E, 2A and 3A to 3E description Figure 5B .

[0101] At step 503, the buffer state is configured. Return to reference Figure 1C , the controlled UWB device can configure its buffer status (e.g., usage, occupancy, etc.) through, for example, UCI (e.g., UCI 105 or 135) from an upper layer (e.g., upper layer 103 or 133). The buffer status can be constructed as an LL control message, return to reference Figures 3A to 3E Description.

[0102] At step 505, an indication of the buffer status is transmitted to another UWB device. Figure 1B and 3A At 3E, the slave UWB device (e.g., slave #1 UWB device 104-1) may transmit a buffer status report message (or buffer status response message 134) to the controller UWB device 102a. The buffer status report message (or buffer status response message) may include an indication of the buffer status in the slave UWB device.

[0103] At step 507, a data transfer control message is received from another UWB device, the data transfer control message including an updated time slot allocation based on the indication of the buffer status. Return to Reference Figure 1B , a slave UWB device (e.g., slave #1 UWB device 104-1) may receive a data transfer control message, such as DTPCM 136, from the controller UWB device 102a. The data transfer control message includes updated time slot assignments for the slave UWB device and / or connection termination with the slave UWB device.

[0104] At step 509, data is transmitted in the time slots allocated according to the updated time slot allocation. Figure 1B , the slave UWB device (eg, slave #1 UWB device 104 - 1 ) may transmit data in the time slot allocated by the data transfer control message.

[0105] Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present disclosure, and all such improvements and modifications fall within the scope of the concepts disclosed herein and the appended claims.

Claims

1. A method for buffer control in ultra-wideband (UWB) communication in an UWB device, comprising: receiving an indication of a buffer status from another UWB device; deriving a data transfer control message based on the indication of the buffer status in the other UWB device, the data transfer control message including an updated time slot allocation for the other UWB device; as well as The data transfer control message is sent to the other UWB device.

2. The method of claim 1, wherein the indication of the buffer status comprises a buffer status report that is part of a link layer control packet sent by the other UWB device. The method of claim 1, wherein the indication of the buffer status is part of a message sent by a UWB system of one UWB device to the other UWB device. The method of claim 1, wherein the indication of the buffer status is sent by an upper layer of the UWB device to an upper layer of the other UWB device.

3. The method of claim 2 , further comprising sending a buffer status request to the other UWB device before receiving the buffer status report, the buffer status request comprising a command requesting the buffer status in the other UWB device, The buffer status report includes a buffer status response responded by the UWB device to the buffer status request.

4. The method according to claim 2, wherein: The buffer status report includes an indication of buffer status of a receiver buffer and a transmitter buffer in the other UWB device; and The data transfer control message includes at least one of a time slot allocation for the receiver buffer and the transmitter buffer or a request for connection termination.

5. The method according to claim 2, wherein: The buffer status report includes an indication of a buffer status of at least a receiver buffer and a transmitter buffer for a normal connection, or an indication of a buffer status of a receiver buffer and a transmitter buffer for a secure connection; and The data transfer control message includes time slot allocations of the receiver buffer and the transmitter buffer for the normal connection, or time slot allocations of the receiver buffer and the transmitter buffer for the secure connection.

6. The method of claim 2, wherein the link layer control packet is a dedicated buffer control message and comprises: a header field, wherein all bits indicate the message type of the buffer status report; and a service data unit (SDU) indicating the content of the buffer status report.

7. The method of claim 2, wherein the link layer control packet is an ACK / NACK control message and includes a header field, wherein a portion of the bits indicates a message type of the ACK / NACK control message and additional bits indicate the buffer status.

8. The method according to claim 3, wherein: The buffer status request is part of a link layer control packet, and The link layer control packet includes: a header field, in which all bits indicate a message type of the buffer status request; and a service data unit (SDU) indicating content of the buffer status request.

9. The method of claim 1, wherein the data transfer control message includes a command to terminate a connection with the other UWB device.

10. The method of claim 1, wherein the indication of buffer usage comprises a set of configuration parameters transmitted by the other UWB device over a non-UWB channel, the set of configuration parameters reflecting the buffer status in the other UWB device. The method of claim 10 , wherein the non-UWB channel comprises a Bluetooth Low Energy channel.

12. The method of claim 1, further comprising sending user data to the other UWB device based on the updated time slot allocation.

13. An ultra-wideband (UWB) device, comprising: a transceiver operable to perform UWB communications; a memory for storing program instructions and a buffer state of another UWB device; as well as a processor coupled to the transceiver and the memory, wherein the processor is operable to execute the program instructions, which, when executed by the processor, cause the UWB device to perform the following operations to facilitate time slot allocation to support data communication with the other UWB device: receiving an indication of a buffer status from the other UWB device; deriving a data transfer control message based on the indication of the buffer status in the other UWB device, the data transfer control message including an updated time slot allocation for the other UWB device; as well as The data transfer control message is sent to the other UWB device.

14. The UWB device of claim 13, wherein the indication of the buffer status comprises a buffer status report that is part of a link layer control packet sent by the other UWB device.

15. The UWB device of claim 14 , further comprising sending a buffer status request to the other UWB device before receiving the buffer status report, the buffer status request comprising a command requesting the buffer status in the other UWB device, The buffer status report includes a buffer status response responded by the UWB device to the buffer status request.

16. The UWB device according to claim 14, wherein: The buffer status report includes an indication of buffer status of a receiver buffer and a transmitter buffer in the other UWB device; and The data transfer control message includes commands for time slot allocation for the receiver buffer and the transmitter buffer.

17. The UWB device according to claim 14, wherein the link layer control packet comprises: A header field indicating the message type of the buffer status report; and a service data unit (SDU) indicating the content of the buffer status report.

18. The UWB device according to claim 15, wherein: The buffer status request is part of a link layer control packet, and The link layer control packet includes: a header field indicating a message type of the buffer status request; and a service data unit (SDU) indicating content of the buffer status request.

19. A method for buffer control in ultra-wideband (UWB) communication in an UWB device, comprising: Configure the buffer status; transmitting an indication of the buffer status to another UWB device; receiving a data transfer control message from the other UWB device, the data transfer control message including an updated time slot allocation for the buffer based on the indication of the buffer status; as well as Data is transmitted in time slots allocated according to the updated time slot allocation.

20. The method of claim 19, wherein the indication of the buffer status comprises at least one of: Buffer Status Report, which is part of a link layer control packet, or A set of configuration parameters is transmitted via a non-UWB channel, wherein the set of configuration parameters reflects the buffer status in the other UWB device.

Images