CN116208299A

CN116208299A - UWB-based multi-user data transmission scheduling method, device, system and medium

Info

Publication number: CN116208299A
Application number: CN202310049725.9A
Authority: CN
Inventors: 王金朋; 董宗宇
Original assignee: Hangzhou Youzhilian Technology Co ltd
Current assignee: Hangzhou Youzhilian Technology Co ltd
Priority date: 2023-02-01
Filing date: 2023-02-01
Publication date: 2023-06-02
Anticipated expiration: 2043-02-01
Also published as: CN116208299B

Abstract

The embodiment of the invention discloses a multi-user data transmission scheduling method, a device, a system and a medium based on UWB, wherein the method comprises the following steps: generating scheduling information by combining configuration information of a high-level APP and information of each tag device in a system; wherein, the scheduling information comprises configured synchronous cycle and data cycle and corresponding time slots; according to the scheduling information, the corresponding sending time slot and/or receiving time slot of the synchronous cycle allocated to the base station itself and each tag device complete the interaction of the control message so as to establish UWB connection with each tag device; the corresponding sending time slot and/or receiving time slot of the data cycle distributed for the base station by the scheduling information through the UWB connection completes the data transmission message interaction process with each tag device and obtains the verification result of the transmitted data; and if the check result is error and the maximum retransmission times do not exceed a threshold value, starting an ARQ data retransmission process.

Description

UWB-based multi-user data transmission scheduling method, device, system and medium

Technical Field

The embodiment of the invention relates to the technical field of Ultra Wideband (UWB) communication, in particular to a multi-user data transmission scheduling method, device, system and medium based on UWB.

Background

Because UWB has excellent characteristics of strong multipath resistance, anti-interference capability, high time resolution, low power consumption, high-speed data transmission and the like, UWB can use lower power to transmit farther distances and has good multipath interference resistance and penetration capability in the data transmission field. Specifically, the bandwidth available for UWB can be up to 1G or more, even several G or more, the wider the bandwidth, the stronger the multipath resolution and the stronger the interference immunity; the high time resolution is the reason that UWB transmission is of nanosecond level, and the high time resolution is also the reason that high-precision positioning can be achieved, and the high time resolution is applied to a data transmission function, so that rapid data transmission can be achieved; the low power consumption means that the frequency band of UWB is allocated to 3.1 GHz-10.6 GHz, the total frequency band is 7.5GHz, the FIRA prescribes that the power of UWB is smaller than-41.3 dBm and is far lower than the limited power of Bluetooth low power consumption (Bluetooth Low Energy, BLE) and Wi-Fi, and the UWB can transmit a longer distance by using lower power. Furthermore, the transmission rate of UWB can range from a few Mbit/s to several hundred Mbit/s, even theoretically up to 1GBit/s, well above BLE and Wi-Fi. The current UWB technology is mainly applied to ranging or positioning systems, and no description is made on UWB-based data transmission in protocol standards IEEE 802.15.4, IEEE 802.15.4z and the FIRA alliance, but only description is made on a media access control layer (Media Access Control, MAC) function, and no description is made on a MAC layer scheduling function based on UWB data transmission, so that no prior art scheme exists.

Disclosure of Invention

In view of this, the embodiments of the present invention expect to provide a multi-user data transmission scheduling method, apparatus, system and medium based on UWB, which can improve the efficiency and success rate of data transmission.

The technical scheme of the embodiment of the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a multi-user data transmission scheduling method based on UWB, where the method is applied to a base station, and the method includes:

generating scheduling information by combining configuration information of a high-level APP and information of each tag device in a system; wherein, the scheduling information comprises configured synchronous cycle and data cycle and corresponding time slots;

according to the scheduling information, the corresponding sending time slot and/or receiving time slot of the synchronous cycle allocated to the base station itself and each tag device complete the interaction of the control message so as to establish UWB connection with each tag device;

the corresponding sending time slot and/or receiving time slot of the data cycle distributed for the base station by the scheduling information through the UWB connection completes the data transmission message interaction process with each tag device and obtains the verification result of the transmitted data;

and if the check result is error and the maximum retransmission times do not exceed a threshold value, starting an ARQ data retransmission process.

In a second aspect, an embodiment of the present invention provides a multi-user data transmission scheduling method based on UWB, where the method is applied to any one of tag devices, and the method includes:

receiving and analyzing a control message sent by a base station to obtain time domain synchronization information and scheduling information, and completing time domain synchronization with the base station according to the time domain synchronization information;

based on the scheduling information, in a data cycle corresponding to each tag device, transmitting and/or receiving a data message to the base station through the UWB connection at a transmission time slot and/or a reception time slot corresponding to each tag device;

transmitting or receiving corresponding data confirmation information to the base station by a transmitting time slot and/or a receiving time slot configured for the tag equipment in a data cycle corresponding to each tag equipment;

and if the check result in the data confirmation message is an error, starting a data retransmission flow of ARQ and transmitting or receiving retransmitted data to the base station in a data cycle configured for each tag device and a corresponding transmitting time slot and/or receiving time slot.

In a third aspect, an embodiment of the present invention provides a base station apparatus including: the device comprises a generation part, a establishment part, a first UWB data transmission interaction part and a first retransmission part; wherein,,

The generation part is configured to combine configuration information of the high-level APP and information of each tag device in the system to generate scheduling information; wherein, the scheduling information comprises configured synchronous cycle and data cycle and corresponding time slots;

the establishing part is configured to complete the interaction of control messages with each tag device in the corresponding sending time slot and/or receiving time slot of the synchronous cycle allocated to the base station according to the scheduling information so as to establish UWB connection with each tag device;

the first UWB data transmission interaction part is configured to complete a data transmission message interaction process with each tag device and obtain a verification result of transmitted data through the UWB connection at a corresponding sending time slot and/or receiving time slot of a data cycle allocated by the scheduling information for the base station itself;

the first retransmission part is configured to start an ARQ data retransmission procedure if the check result is erroneous and the maximum number of retransmissions does not exceed a threshold.

In a fourth aspect, an embodiment of the present invention provides a tag device apparatus, including: a synchronization section, a second UWB data transmission interaction section, a transmission or reception section, and a second retransmission section; wherein,,

The synchronization part is configured to receive and analyze the control message sent by the base station to acquire time domain synchronization information and scheduling information, and complete time domain synchronization with the base station according to the time domain synchronization information;

the second UWB data transmission interaction part is configured to send and/or receive data messages to the base station in the data cycle corresponding to each tag device through the UWB connection at the sending time slot and/or the receiving time slot corresponding to each tag device based on the scheduling information;

the transmitting or receiving part is configured to transmit or receive a corresponding data acknowledgement message to the base station in a transmitting time slot and/or a receiving time slot configured for the transmitting or receiving part in a data cycle corresponding to each tag device;

and the second retransmission part is configured to start an ARQ data retransmission flow and send or receive retransmitted data to the base station in a data cycle configured for each tag device and a corresponding sending time slot and/or receiving time slot if the check result in the data confirmation message is an error.

In a fifth aspect, an embodiment of the present invention provides a network node device, including: wireless communication circuitry, memory, and a processor; the components are coupled together by a bus system; wherein,,

The wireless communication circuit includes: UWB communication means for enabling the network node device to perform UWB communication and/or for data transmission;

the memory is used for storing a computer program capable of running on the processor;

the processor is configured to execute the steps of the UWB-based multi-user data transmission scheduling method according to the first or second aspect when the computer program is executed.

In a sixth aspect, an embodiment of the present invention provides a multi-user data transmission scheduling system based on UWB, where the system includes: a base station and all tag devices within the signal coverage range of the base station; wherein,,

the base station being configured to perform the steps of the UWB-based multi-user data transmission scheduling method of the first aspect;

any one of the tag devices is configured to perform the steps of the UWB-based multi-user data transmission scheduling method of the second aspect.

In a seventh aspect, an embodiment of the present invention provides a computer storage medium storing a UWB-based multi-user data transmission scheduler, where the UWB-based multi-user data transmission scheduler, when executed by at least one processor, implements the steps of the UWB-based multi-user data transmission scheduling method of the first or second aspect.

The embodiment of the invention provides a multi-user data transmission scheduling method, a device, a system and a medium based on UWB, wherein a base station generates scheduling information according to configuration information and information of each tag device in the system before data transmission, and based on the scheduling information, the scheduling information and information such as time slot index and the like used for time domain synchronization are transmitted to each tag device through control information in a transmission time slot corresponding to the configured synchronization cycle; in the data transmission process, according to the scheduling information, completing a data transmission message interaction process based on UWB with each tag device in a data cycle and a corresponding time slot distributed by a base station for the base station; judging whether data need to be retransmitted or not according to the data verification result in the UWB-based data transmission process, and if the data verification result is an error, starting an ARQ data retransmission flow. Through UWB high-efficiency data transmission and ARQ retransmission mechanism, the efficiency and success rate of data transmission are improved, and the base station and each tag device can enter a Sleep mode on the time slot without data transmission, so that the power consumption is saved.

Drawings

Fig. 1 is a schematic diagram of a wireless communication system capable of implementing the technical scheme of the embodiment of the present invention;

Fig. 2 is a schematic diagram of a hardware structure of a network node device according to an embodiment of the present invention;

fig. 3 is a schematic flow chart of a multi-user data transmission scheduling method based on UWB according to an embodiment of the present invention;

fig. 4 is a schematic diagram of time domain structure provided in an embodiment of the present invention;

fig. 5 is a schematic diagram of configuration of a beacon frame according to an embodiment of the present invention;

FIG. 6 is a flow chart of a scheduling configuration for a one-to-many scenario provided by an embodiment of the present invention;

FIG. 7 is a flowchart of UWB-based ARQ scheduling for one-to-many scenarios provided by an embodiment of the present invention;

FIG. 8 is a flow chart of a scheduling configuration for a one-to-one scenario provided by an embodiment of the present invention;

FIG. 9 is a flowchart of UWB-based ARQ scheduling for a one-to-one scenario provided by an embodiment of the present invention;

FIG. 10 is a flowchart of another multi-user data transmission scheduling method based on UWB according to the embodiment of the present invention;

fig. 11 is a schematic diagram of a base station apparatus according to an embodiment of the present invention;

fig. 12 is a schematic diagram of a label device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

Referring to fig. 1, which shows a schematic diagram of a wireless communication system 100 that can be adapted for use in the solution set forth in the examples of the present invention, it is noted that the wireless communication system shown in fig. 1 is just one example of a possible system, and that the embodiments of the present disclosure can be implemented in any of a variety of systems as desired.

As shown in fig. 1, the wireless communication system 100 includes: one base station 11 and one or more movable Tag devices (tags) in the signal coverage area of the base station 11 (as shown by the oval in fig. 1), in the embodiment of the present invention, 3 Tag devices are taken as examples, and may be respectively marked as Tag21, tag22 and Tag23, where the upper dashed oval can be understood as a one-to-many networking of the base station 11 with Tag devices Tag21 and Tag22, and the lower dashed oval can be understood as a one-to-one networking of the base station 11 with Tag device Tag 23. In some non-limiting examples, base stations 11 and Tag21, tag22, and Tag23 may be collectively referred to as wireless communication devices, which may communicate wirelessly using any of a variety of wireless communication technologies, possibly including Ultra-wideband (UWB) communication technologies (e.g., IEEE 802.15.4z compliant), wi-Fi (e.g., IEEE 802.11), and/or other technologies based on WPAN or WLAN wireless communications.

It should be noted that in the wireless communication system 100 shown in fig. 1, the term "wireless communication device" may also be referred to by those skilled in the art as a Mobile Station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a remote device, a mobile subscriber station, an access terminal (Access Termination, AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology; and the wireless communication device need not have mobility capabilities in some examples, but may be stationary; further, a wireless communication device may include several hardware structural components that are sized, shaped, and arranged to facilitate wireless communication, such components may include antennas, antenna arrays, radio frequency (RadioFrequency, RF) chains, amplifiers, one or more processors, and so forth, that are electrically coupled to each other. Additionally, in some non-limiting examples, in addition to the printers, PDAs, cameras, access points, speaker systems, and wireless networks described above, other non-limiting examples of wireless communication devices include mobile devices, cellular (cell) phones, smart phones, session initiation protocol (Session Initiation Protocol, SIP) phones, laptops, personal computers (Personal Computer, PCs), notebooks, netbooks, smartbooks, tablet devices, and a wide variety of embedded systems, e.g., corresponding to "internet of things" (IoT). Additionally, the wireless communication device may be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GlobalPositioning System, GPS) device, an object tracking device, an unmanned aerial vehicle, a multi-axis aircraft, a four-axis aircraft, a remote control device, a consumer and/or wearable device (such as eyeglasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, and the like. Additionally, the wireless communication device may also be a digital home or smart home device, such as a home audio, video and/or multimedia device, appliance, vending machine, smart lighting device, home security system, smart meter, etc. Additionally, the wireless communication device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device (e.g., smart grid) that controls power, lighting, water, etc.; industrial automation and enterprise equipment; a logistics controller; agricultural equipment; military defenses, vehicles, airplanes, boats, weapons, and the like.

For the wireless communication system 100 shown in fig. 1, in some examples, the base station 11 and the Tag devices Tag21, tag22, and Tag23 may also be collectively referred to as network node devices within the wireless communication system 100. For any of these network node devices, see fig. 2, which shows an example of the composition that can implement a network node device 200, the network node device 200 may comprise at least: a processor 210, a memory 220, a wireless communication circuit 230, and a power supply 240; the components may be connected by various suitable types of buses, such as a power bus, a control bus, a status signal bus, and the like. The power supply 240 provides power to the components within the network node device 200.

In some examples, the processor 210 may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (FieldProgrammable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The disclosure in connection with the embodiments of the present invention may be directly embodied as a hardware decode processor executing or a combination of hardware and software modules executing in the decode processor. The software modules may be located in memory 220.

In some examples, memory 220 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a Read-only memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct memory bus RAM (Direct RambusRAM, DRRAM). The memory 220 of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

In some examples, wireless communication circuitry 230 may include communication components capable of wireless communication using multiple wireless communication standards or Radio Access Technologies (RATs), such as UWB communication component 231 shown in fig. 2; wherein said UWB communication means 231 is for enabling the network node device 200 to perform UWB communication and/or for data transmission, e.g. according to the IEEE 802.15.4 protocol. Of course, in other examples, the wireless communication circuit 230 may further include a communication component capable of performing wireless communication according to a communication protocol other than UWB, which is not described herein.

In some examples, the base stations 11 and the

tags

21, 22 and 23 in the wireless communication system 100 shown in fig. 1 may also be collectively referred to as UWB devices, which may be divided into two types, i.e., master and Slave (Slave), for clarity of the following description of the technical scheme. The Master refers to a base station for realizing data transmission, and has the functions of networking, sending data and receiving data; the Slave is a Tag device for data transmission, and any one of Tag devices Tag21, tag22 and Tag23 in the wireless communication system 100 shown in fig. 1 mainly realizes a function of pairing with a Master, transmitting data and receiving data. From the above description, it is known that UWB-based data transmission can be divided into two scenes, i.e., one-to-many and one-to-one, and can be understood as one Master and multiple Slave scenes, one Master and one Slave.

With reference to fig. 1 and fig. 2, the embodiment of the present invention provides a multi-user data transmission scheduling scheme based on UWB, and it is expected that by scheduling, the advantage of UWB technology can be fully utilized, so that each Tag device (Tag) can perform efficient transmission of data with the base station 11 through UWB and adopts an automatic retransmission request (Automatic Repeat Request, ARQ) technology for data with transmission errors, so as to improve the success rate of data transmission. Based on this, referring to fig. 3, there is shown a multi-user data transmission scheduling method flow based on UWB, which can be applied to the base station 11, the method includes:

s301: generating scheduling information by combining configuration information of a high-level APP and information of each tag device in a system; wherein, the scheduling information comprises configured synchronous cycle and data cycle and corresponding time slots;

s302: according to the scheduling information, the corresponding sending time slot and/or receiving time slot of the synchronous cycle allocated to the base station itself and each tag device complete the interaction of the control message so as to establish UWB connection with each tag device;

s303: the corresponding sending time slot and/or receiving time slot of the data cycle distributed for the base station by the scheduling information through the UWB connection completes the data transmission message interaction process with each tag device and obtains the verification result of the transmitted data;

S304: and if the check result is error and the maximum retransmission times do not exceed a threshold value, starting an ARQ data retransmission process.

For the technical scheme shown in fig. 3, before data transmission, a base station generates scheduling information according to configuration information and information of each tag device in a system, and based on the scheduling information, sends the scheduling information and information such as time slot index for time domain synchronization to each tag device in a configured sending time slot corresponding to a synchronization cycle through a control message; in the data transmission process, according to the scheduling information, completing a data transmission message interaction process based on UWB with each tag device in a data cycle and a corresponding time slot distributed by a base station for the base station; judging whether data need to be retransmitted or not according to the data verification result in the UWB-based data transmission process, and if the data verification result is an error, starting an ARQ data retransmission flow. Through UWB high-efficiency data transmission and ARQ retransmission mechanism, the efficiency and success rate of data transmission are improved, and the base station and each tag device can enter a Sleep mode on the time slot without data transmission, so that the power consumption is saved.

It should be noted that, the technical solution of the embodiment of the present invention may also be understood as dividing the processing of the entire scheduling scheme into two phases, namely, an access phase and a data transmission phase. In the access phase, finishing the interaction of control messages between the base station and each tag device to establish UWB connection; while during the data transmission phase, the interworking of UWB-based data transmission and ARQ-based data retransmission is completed. It can be understood that, at present, for UWB connection, one UWB device can support connection between one base station and a plurality of tag devices, and based on this feature, the embodiment of the present invention is described by using the base station as a Master and the tag devices as Slave. In this way, in the access stage, the base station only performs pairing connection and data interaction with the tag device with connection relation, so that the scheduling complexity of UWB can be greatly reduced. For the solution shown in fig. 3, it may be represented as a complete scheduling procedure, where the contents described in steps S301-S302 are in the foregoing access phase; s303 to S304 are in a data transmission phase, i.e. a procedure based on UWB data transmission and ARQ retransmission.

For the technical solution shown in fig. 3, in some possible implementations, the configuration information of the high-level APP and the information of each tag device in the system are combined to generate scheduling information; the scheduling information comprises configured synchronous circulation, data circulation and corresponding time slots, and specifically, the configuration information and information of each tag device in the system comprise address identifiers, numbers, device types and divided time domain information of a base station and each tag device; wherein, referring to fig. 4, which shows a schematic diagram of time domain structure, the time domain is divided into blocks, cyclic Round and time slots Slot, one Block is set to contain Nround (Number Round Per Block) cyclic Round, one cyclic Round contains Mslot (Number Slot Per Round) time slots Slot, and the period of one time Slot is set to Tslot (time Slot period, for example, 1 ms); the time length of the single cycle Round is tslot×mslot and the time length of the single Block is tslot×mslot×nround.

The generation of scheduling information, specifically, the configuration of tag devices to different Round for scheduling using time division multiple access (Time Division Multiple Access, TDMA). Referring to fig. 5, a schematic diagram of a configuration of a Beacon frame including Beacon Round for synchronization and Data Round for Data transmission is shown. For the procedure of one Data transmission, each of the illustrated

blocks

0 and 1 is configured such that one Beacon Round and 3 Data rounds can be contained in one Block. In the implementation process, the allocation of the Beacon Round and the Data Round needs to be divided reasonably, and the allocation can be dynamically configured to meet different scene requirements.

In some examples, the scheduling information may specifically be a synchronization cycle, a data cycle, and a corresponding time slot allocated for the base station itself and each tag device in each Block, so that each tag device completes a time domain synchronization and data transmission procedure with the base station in the corresponding time slot. In detail, reasonable allocation of Beacon Round and Data Round is performed according to the number of tag devices in the wireless communication system 100 shown in fig. 1, and the number of slots in each Round needs to ensure that the interaction process of time domain synchronization or Data transmission between the base station and all the tag devices can be completed; each Block includes 2 times of Data rounds as many as tag devices in the system, that is, each tag device corresponds to two Data rounds, and in each Data Round, a process of transmitting or receiving Data with a base station can be completed once.

It should be noted that, for the interaction in the wireless network, the transmission is performed in a frame manner, the beacon frame refers to a management frame periodically sent in the network, so as to realize the synchronization and dormancy of the devices in the network, the beacon frame is sent by the coordinator, and once the node receives the beacon frame, the node joins the network according to the stipulation of the coordinator and sends or receives data according to the stipulation time interval of the coordinator. Sometimes the beacon frames may be transmitted during a common time interval during which devices receiving the beacon frames may compete together to join the network for communication with the coordinator; the coordinator is a base station in the embodiment of the present invention.

For the technical solution shown in fig. 3, in some possible implementations, the interaction of the control message with each tag device according to the scheduling information in the corresponding transmission time slot and/or the receiving time slot of the synchronization cycle allocated to the base station itself, so as to establish UWB connection with each tag device includes:

according to the scheduling information, sending control information to each tag device in a sending time slot corresponding to the synchronous cycle;

and receiving a control confirmation message returned by each tag device corresponding to the receiving time slot corresponding to the synchronous cycle so as to establish UWB connection.

For the implementation manner, the base station generates scheduling information according to the configuration information and the information of each tag device in the system, encapsulates the scheduling information and the time domain synchronization information into a control message, and sends the control message to each tag device, wherein the control message specifically carries a time slot index of time domain synchronization, a sending time slot of a control confirmation message, an address identifier of each tag device, a data cycle allocated to each tag device, and a corresponding sending and/or receiving time slot.

In order to avoid time domain error accumulation between UWB devices, in a specific implementation, a base station transmits a control message once at intervals, and in the case that a control acknowledgement message fed back by a tag device is not received, the tag device is set to a loss of gait. Furthermore, the time domain synchronization performed during the access phase typically occupies a duration of one Round, and only the transmission scheduling information and the time domain synchronization are performed on the Beacon Round, and no UWB-based data transmission is performed.

For the technical solution shown in fig. 3, in some possible implementations, the completing, by the UWB connection, a data transmission message interaction process with each tag device and obtaining a verification result of the transmitted data in a corresponding transmission time slot and/or a reception time slot of a data cycle allocated by the scheduling information for the base station itself includes:

according to the scheduling information, completing interaction of data messages with each tag device in a sending time slot and/or a receiving time slot corresponding to the data cycle allocated to the base station itself;

based on the interaction of the data messages, the transmitted data is checked and the check result is sent to each tag device through a data confirmation message or the data confirmation message of each tag device is waited to be received.

For the technical solution shown in fig. 3, in some possible implementations, if the check result is an error and the maximum retransmission number does not exceed the threshold, the ARQ data retransmission process is started, including:

and if the check result is wrong, judging whether the maximum retransmission times reach a threshold value:

if not, starting the data retransmission flow based on ARQ; otherwise, ending the flow of data transmission;

and if the verification result is passed, continuing to sequentially send or receive the data to be sent or ending the flow of data transmission.

Note that the automatic repeat request ARQ, which may also be referred to as a cyclic automatic request, refers to automatically sending a request for retransmitting an error frame when a receiving end of a data transmission receives an information (frame) containing check error data. The ARQ functions to automatically retransmit the data frame with the check error, including three forms, namely, a waiting type ARQ, a back-off N-step ARQ, and a selective retransmission ARQ. The waiting ARQ means that after a sender sends out a data packet or a data frame, the sender waits for a receipt signal from a receiver, where the receipt signal may be a data acknowledgement message, where the message carries an acknowledgement flag of the sent data, and if the acknowledgement flag passes, the sender is notified that the data frame has been correctly received, and the negative acknowledgement signal notifies that the data frame received by the sender has an error. The transmitting end transmits the next data frame after receiving the data confirmation mark as passing, and retransmits the transmitted data frame after receiving the confirmation mark as error until receiving the data confirmation mark as passing. The back-off N-step ARQ means that data frames are continuously transmitted, and the transmitting end does not have to wait for receipt signals after transmitting one data frame. After a round trip delay (i.e., the time required to send out a data frame and to receive a receipt for that data frame), another N-1 data frames have been sent. When the acknowledgement flag of the received data is error, the transmitting end returns to the data frame corresponding to the acknowledgement flag, and retransmits the data frame and the following N-1 data frames which have been transmitted during the round trip delay period, so that the transmitting end needs to have a buffer to store the data frames. At the receiving end, N-1 received data frames following the erroneously received data frame are discarded regardless of their correctness, so that only one data frame is stored at the receiving end. The selective repeat ARQ is also continuously transmitted, but the transmitting end retransmits only those data frames corresponding to the acknowledgement flag of the data as error. In general, the data frames must be sent to the receiving end in the correct order, so a buffer is needed at the receiving end to store the data frames without errors after verification.

For the technical solution shown in fig. 3, for an example of multi-user data transmission based on UWB, referring to fig. 6, a scheduling configuration flow chart of one-to-many scenario is shown, taking the base station 11 as a Master and Tag devices Tag21 and Tag22 as Slave as examples, and after both sides of data transmission enter a connected state, a flow of receiving and transmitting data starts. Taking a Block containing 1 Beacon Round and 4 Data rounds as an example, where Beacon Round 0 shown in fig. 6 is a Beacon cycle for synchronization, data Round 1, data Round 2, data Round 3, and Data Round 4 are Data cycles for Data transmission, a one-to-many scenario scheduling configuration flow is as follows:

step 1: the base station 11 generates scheduling information according to the configuration, and sends the scheduling information to Tag devices Tag21 and Tag22 through a control message CTRL;

and generating scheduling information according to the configuration, wherein the scheduling information is that Data is sent to the Tag21 on the Data Round 1, the Data sent by the Tag21 is received on the Data Round 2, the Data is sent to the Tag22 on the Data Round 3, the Data sent by the Tag22 is received on the Data Round 4, and the generated scheduling information is broadcast and sent to the Tag21 and the Tag22 on the Beacon Round 0 through the control message CTRL.

Step 2: after receiving the CTRL message, tag21 and Tag22 analyze the CTRL message to acquire scheduling information and time domain synchronization information, complete time domain synchronization according to the time domain synchronization information, and reply a control confirmation message CTRL_CON on a time slot corresponding to a configured synchronization cycle according to the scheduling information;

step 3: the base station 11 turns on Tx on Data Round 1, and sends Data to Tag21;

step 4: tag21 opens Rx reception Data on Data Round 1 according to the schedule information;

step 5: tag21 opens Tx to send Data on Data Round 2, tag21 sends Data, and enters Sleep power saving state in the rest time;

step 6: the base station 11 turns on Rx on Data Round 2 to receive Data;

step 7: the base station 11 turns on Tx on Data Round 3 to send Data to Tag 22;

step 8: tag22 opens the Data of Rx receiving base station 11 on Data Round 3 according to the scheduling information;

step 9: tag22 turns on Tx on Data Round 4, sending Data to base station 11;

step 10: the base station 11 turns on Rx on the Data Round 4 to receive Data of Tag 22;

step 11: after receiving the control message, the base station 11 enters the next Block, starts to send the control message on the beacon frame, and enters the next round of scheduling configuration flow.

Note that Tx represents Data output, i.e., transmit Data, and RX represents Data input, i.e., receive Data.

In connection with the scheduling configuration flow described in fig. 6, the base station 11 is used as a transmitting end for the access phase based on UWB multi-user data transmission. For the data transmission stage, the base station 11 may be used as a transmitting end or a receiving end of data transmission, and after the base station 11 and Tag devices Tag21 and Tag22 enter a connection state, a flow of transmitting and receiving data starts. During data transmission, if there is a data transmission error or loss, an ARQ retransmission mechanism is started. Taking a Block containing 1 Beacon Round and 4 Data rounds as an example. In addition, it should be noted that, in the data transmission process, the transmission time slot of the transmitting end is the receiving time slot of the receiving end, and the scheduling information of the transmission time slot and the receiving time slot has a corresponding relationship. Referring to fig. 7, which shows a one-to-many scenario UWB-based ARQ scheduling flow diagram, the detailed flow steps are as follows:

s701: the base station 11 generates scheduling information according to the configuration information, and broadcasts and sends the scheduling information to the Tag21 and the Tag22 at the Slot 0 of the Beacon Round 0 through the control message;

the configuration of the scheduling cycle is shown in fig. 6, and the scheduling information specifically includes: the base station 11 sends a control message at Slot 0 of Beacon Round 0, the base station 11 receives a control confirmation message sent by Tag21 at Slot 1 of Beacon Round 0, and receives a control confirmation message sent by Tag22 at Slot 2; data is sent to the Tag21 on the Data Round 1, the Tag21 Data is received on the Data Round 2, the Data is sent to the Tag22 on the Data Round 3, the Data of the Tag22 is received on the Data Round 4, the generated Slot 0 of the scheduling information Beacon Round 0 is sent to the Tag21 and the Tag22 through CTRL message broadcasting, and the Tag21 and the Tag22 reply control confirmation messages at the Slot 1 and the Slot 2 of the Beacon Round 0 respectively. The allocation of time slots in each data cycle is shown in the flowchart of fig. 7, and will not be described here.

S702: receiving a control confirmation message sent by Tag21 at Slot 1 of Beacon Round 0;

s703: receiving a control confirmation message sent by the Tag22 at the Slot 2 of the Beacon Round 0;

for the steps S702 and S703, it should be noted that, after the Tag devices Tag21 and Tag22 are powered on, according to the broadcast signals configured on the allocated frequency points for performing the blind detection on the base station 11, after the blind detection is successful, performing time domain synchronization after authentication and address matching are successful, and analyzing the scheduling information to obtain the data cycle and the corresponding time slot allocated for the Tag devices themselves; after the time domain synchronization is completed, a control confirmation message ctrl_con is replied to the base station 11, wherein the ctrl_con message carries an address identifier of the Tag21 or the Tag22, and the ctrl_con message is sent, and the Tag21 and the Tag22 enter a connection state. The specific time domain synchronization algorithm is described above and will not be repeated here. The base station 11 enters a connection state after receiving the ctrl_con message, and enters a data transmission stage according to the configuration. The base station 11 periodically transmits a CTRL message, and if the transmitted ctrl_con message of the tag device is not received, the state of the tag device is marked as an out-of-step state, and at this time, the UWB connection between the base station 11 and the tag device fails to be established.

S704: the base station 11 opens Tx on Slot 0 of Data Round 1, sends Data message Data to Tag21, and after the Data transmission is completed, needs to open Rx on Slot 2 of Data Round 1, and waits for receiving Data acknowledgement message ACK;

S705: tag21 sends a Data acknowledgement message ACK to base station 11 at Slot 1 of Data Round 1;

tag21 opens Rx on Slot 0 of Data Round 1, prepares to receive Data, performs CRC check on the Data carried in the Data message after receiving the Data message, fills the check result into the acknowledgement flag field, and sends the acknowledgement flag field to base station 11 through Data acknowledgement message ACK. If the check is wrong, the confirmation mark is set to be wrong and Data retransmission is automatically requested, and Tag21 needs to open Rx at Slot 2 of Data Round 1 to wait for receiving the retransmitted Data; if the check passes, the confirmation flag is passed, the DATA retransmission is not required to be requested, and the flow of receiving the DATA sent through the DATA message or ending the DATA transmission can be continued.

It should be noted that, for the receiving end of the data transmission, cyclic redundancy check (Cyclic Redundancy Check, CRC) check is required to be performed on the received data, and if the CRC check result is that the check is passed, the acknowledgement flag is passed; if the CRC check result is a check error, the validation flag is an error.

The CRC check refers to checking each data frame in the analyzed data, and the basic idea is that before a transmitting end transmits the data, a CRC check code which can be single bit or multi-bit is generated and is attached to the tail end of effective data and is transmitted to a receiving end in a serial mode; and after receiving the data, the receiving end performs CRC check, and the correctness of the data is judged according to the check result. The CRC code is generated by expanding the effective data to be used as a dividend, using a specified polynomial as a divisor, and performing modulo-two division to obtain the remainder, namely the check code; the data received by the receiving end comprises effective data and CRC check codes, the CRC check is carried out after the data is received, the received data is expanded to be used as a dividend, a specified polynomial is used as a divisor, the modulo two division is carried out, the remainder is 0, and the data check is passed; otherwise, the data check error is indicated.

S706: the base station 11 receives the ACK message and analyzes the ACK message to obtain an acknowledgement mark, and retransmits the acknowledgement mark as error Data to the Tag21 at the Slot2 of the Data Round 1;

the base station 11 determines whether to retransmit according to the confirmation mark, if the confirmation mark is passed, the retransmission is not performed; if the confirmation flag is wrong, the retransmitted Data is sent at the Slot2 of the Data Round 1, and meanwhile, the Tag21 receives the Data retransmitted by the base station 11 at the Slot2 of the Data Round 1 and performs a check and returns a Data confirmation message, which can refer to the operation after the Data message is sent in step S704, and detailed description thereof is omitted.

S707: tag21 sends Data to base station 11 at Slot 0 of Data Round 2, and opens Rx to receive ACK message;

s708: the base station 11 opens Rx at Slot 0 of Data Round 2, receives Data, checks after receiving the Data message, and sends the check result to Tag21 at Slot 1 of Data Round 2 through the ACK message;

s709: tag21 receives and parses the ACK message to obtain an acknowledgement flag, and if the acknowledgement flag is wrong, retransmits Data to base station 11 on Slot2 of Data Round 2;

after receiving the ACK message at Slot 1 of Data Round 2, tag21 parses to obtain an acknowledgement flag, determines whether Data needs to be retransmitted according to the acknowledgement flag, if so, ARQ retransmission is adopted, and accordingly, base station 11 receives Data retransmitted by Tag21 at Slot2 of Data Round 2 and performs verification of the retransmitted Data again.

S710: the base station 11 turns on Tx on Slot 0 of Data Round 3, and sends a DATA message to the Tag 22;

s711: tag22 checks the received DATA message and sends an ACK message at Slot 1 of DATA Round 3;

the Tag22 opens the Data of the Rx receiving base station 11 on the Slot 0 of the Data Round 3 according to the scheduling information; and performing CRC (cyclic redundancy check) on the received Data to acquire a check result, if the check result is a check error, confirming that the check mark is an error, and if the Tag22 needs to open Rx at Slot2 of Data Round 3, receiving the retransmitted Data.

S712: the base station 11 sends the retransmitted Data to the Tag22 at Slot2 of Data Round 3;

the base station 11 receives the ACK message at the Slot 1 of the Data Round 3 and analyzes the ACK message to acquire an acknowledgement mark, determines whether to retransmit according to the acknowledgement mark, and does not retransmit if the acknowledgement mark passes; if the data acknowledgement flag is erroneous, retransmission of the data is performed on the designated time slot according to the scheduling information. Accordingly, tag22 receives the retransmitted Data at Slot2 of Data Round 3.

S713: tag22 sends a DATA message to base station 11 at Slot 0 of Data Round 4 and opens Rx to wait for receiving ACK message;

s714: the base station 11 opens Rx at Slot 0 of Data Round 4, receives Data message of Tag22, checks the Data carried in the Data message, and replies ACK message at Slot 1 of Data Round 4;

S715: after receiving the ACK message on Slot 1 of Data Round 4, tag22 determines whether to retransmit DATA according to the acknowledgement flag;

if retransmission is needed, the Data is retransmitted on Slot 2 of Data Round 4, and accordingly, the base station 11 receives and verifies the Data retransmitted by Tag22 on Slot 2 of Data Round 4.

Based on the foregoing technical solutions and illustration, for a one-to-one scenario, it may be understood that a Master corresponds to a Slave scenario, and referring to fig. 8, a base station 11 is taken as a Master, and Tag devices Tag23 are taken as a Slave for illustration, and after the base station 11 and the Tag23 establish UWB connection, they enter a connection state, and then a Data receiving and sending flow may begin, and for an example, a Block contains 1 Beacon Round and 2 Data Round, the one-to-one scenario scheduling configuration flow is as follows:

step 1: the base station 11 generates scheduling information according to the configuration;

the specific scheduling information is that Data is sent to the Tag23 on the Data Round 1, the Tag23 Data is received on the Data Round 2, the scheduling information is sent to the Tag23 on the Beacon Round 0 through the CTRL message, and the Tag23 receives the CTRL message and then performs synchronous time domain and analysis of the scheduling information so as to acquire the Data cycle and the time slot allocated for itself.

Step 2: the base station 11 turns on Tx on Data Round 1, and sends Data to Tag 23;

step 3: tag23 opens Rx on Data Round 1 to receive Data according to the scheduling information;

step 4: tag23 turns on Tx transmit Data on Data Round 2;

step 5: the base station 11 turns on Rx on Data Round 2 to receive Data;

step 6: after receiving the control message, the base station 11 enters the next Block, starts to send the control message on the beacon frame, and enters the next round of scheduling flow.

Referring to fig. 9, which shows a flowchart of UWB-based ARQ scheduling for one-to-one scenario, the scheduling configuration is shown in fig. 8, and the detailed flow of one-to-one scenario supporting ARQ scheduling is as follows:

s901: the base station 11 sends a control message CTRL at Slot 0 of Beacon Round according to the scheduling configuration;

specifically, the scheduling is configured to send Data to Tag23 on Data Round 1, receive Tag23 Data on Data Round 2, and send generated scheduling information to Tag23 through CTRL message at Slot 0 of Beacon Round.

S902: the Tag23 sends a control confirmation message CTRL_CON at the Slot 1 of the Beacon Round according to the scheduling information;

s903: the base station 11 turns on Tx on Slot 0 of Data Round 1, and sends a Data message Data;

accordingly, after receiving the CTRL message, tag23 synchronizes time sequence operation and analyzes scheduling information, opens Rx on Slot 0 of Data Round 1 to receive Data according to the scheduling information, and opens a timer.

S904: after receiving the DATA message, tag23 performs CRC check, encapsulates the check result into an ACK message, and replies the ACK message to base station 11 on Slot 1 of DATA Round 1; the ACK message carries an acknowledgement mark of the received data and indicates whether the received data is correctly received or not;

s905: the base station 11 determines whether retransmission needs to be initiated according to the received ACK message, and if retransmission is required, the base station sends the retransmitted Data to the Tag23 on the Slot2 of the Data Round 1; accordingly, tag23 receives the retransmitted Data on Slot2 of Data Round 1;

s906: tag23 sends a DATA message to base station 11;

tag23 sends a DATA message at Slot 0 of Data Round 2 and opens Rx to wait for receiving an ACK message; accordingly, the base station 11 turns on Rx at Slot 0 of Data Round 2 and receives the Data message sent by Tag 23.

S907: after receiving the DATA message, the base station 11 checks and replies an ACK message at Slot 1 of DATA Round 2;

s908: after receiving the ACK message on Slot 1 of Data Round 2, tag23 determines whether Data needs to be retransmitted according to the confirmation mark, and if so, the Data is retransmitted on Slot2 of Data Round 2; accordingly, the base station 11 receives Data retransmitted by the Tag23 at Slot2 of Data Round 2.

Based on the same inventive concept as described above, referring to fig. 10, another multi-user data transmission scheduling method based on UWB provided by an embodiment of the present invention is shown, and the method may be applied to any one of the tag devices in the wireless communication system 100 shown in fig. 1, and may include:

S1001: receiving and analyzing a control message sent by a base station to obtain time domain synchronization information and scheduling information, and completing time domain synchronization with the base station according to the time domain synchronization information;

s1002: based on the scheduling information, in a data cycle corresponding to each tag device, transmitting and/or receiving a data message to the base station through the UWB connection at a transmission time slot and/or a reception time slot corresponding to each tag device;

s1003: transmitting or receiving corresponding data confirmation information to the base station by a transmitting time slot and/or a receiving time slot configured for the self in a data cycle corresponding to each tag device;

s1004: and if the check result in the data confirmation message is an error, starting a data retransmission flow of ARQ and transmitting or receiving retransmitted data to the base station in a data cycle configured for each tag device and a corresponding transmitting time slot and/or receiving time slot.

For the technical solution shown in fig. 10, in some possible implementations, the receiving the control message sent by the base station and analyzing the control message to obtain time domain synchronization information and scheduling information, and completing time domain synchronization with the base station according to the time domain synchronization information includes:

receiving and analyzing a control message sent by a base station to obtain time domain synchronization information and scheduling information;

And finishing time domain synchronization with the base station in a synchronization cycle configured by the scheduling information and a corresponding time slot according to the time domain synchronization information.

For the above implementation manner, in some examples, the time domain synchronization with the base station is completed in the synchronization cycle configured by the scheduling information and the corresponding time slot according to the time domain synchronization information, specifically, for each tag device, after receiving the control message, the tag device analyzes the control message to obtain the scheduling information and the time domain synchronization information, replies a control confirmation message on the configured synchronization cycle and the corresponding time slot according to the scheduling information, and completes the time domain synchronization with the base station according to the time domain synchronization information, so that the base station and each tag device enter a connection state.

After each tag device acquires the time domain synchronization information, the time domain synchronization may be performed according to the following algorithm:

firstly, the synchronization can be performed on the Block according to the Block index=physiolocounter/(mslot×nround); then synchronize for the loop according to Round index= (physiolocounter (mslot×nround))/Mslot; finally, the time slots are synchronized according to Slot Index = physlotcount% Mslot. Through the three formulas, the blocks, the loops and the time slots between each tag device and the base station in the time domain can be synchronized.

For the technical solution shown in fig. 10, in some possible implementations, if the check result in the data acknowledgement message is an error, starting a data retransmission flow of ARQ and transmitting or receiving retransmitted data to the base station in a data cycle configured for each tag device and a corresponding transmission time slot and/or a corresponding reception time slot, including:

if the check result is wrong, automatically requesting retransmission and receiving or transmitting the retransmitted data in the corresponding transmitting time slot and/or receiving time slot;

and if the verification result is passed, continuing to receive or transmit the data to be transmitted or ending the data transmission flow.

For the technical solution shown in fig. 10 and the examples thereof, which belong to the same inventive concept as the technical solution shown in fig. 3, the technical solution shown in fig. 10 and the examples thereof are not described in detail, and the description of the technical solution shown in fig. 3 is referred to above, and the embodiments of the present invention will not be repeated.

Based on the same inventive concept as the foregoing technical solution, referring to fig. 11, there is shown a base station apparatus 1100 provided by an embodiment of the present invention, the base station apparatus 1100 includes: a generating section 1101, a setting-up section 1102, a first UWB data transmission interaction section 1103, and a first retransmission section 1104; wherein,,

The generating part 1101 is configured to generate scheduling information by combining configuration information of the high-level APP and information of each tag device in the system; wherein, the scheduling information comprises configured synchronous cycle and data cycle and corresponding time slots;

the establishing part 1102 is configured to complete the interaction of the control message with each tag device in the corresponding sending time slot and/or receiving time slot of the synchronization cycle allocated to the base station according to the scheduling information so as to establish UWB connection with each tag device;

the first UWB data transmission interaction portion 1103 is configured to complete a data transmission message interaction process with each tag device and obtain a verification result of the transmitted data through the UWB connection at a corresponding transmission time slot and/or a receiving time slot of a data cycle allocated by the scheduling information for the base station itself;

the first retransmission part 1104 is configured to start an ARQ data retransmission process if the check result is erroneous and the maximum number of retransmissions does not exceed a threshold.

In some examples, the setup portion 1102 is configured to:

In some examples, the first UWB data transmission interaction portion 1103 is configured to:

Based on the same inventive concept as the foregoing technical solution, referring to fig. 12, there is shown a tag device apparatus 1200 provided in an embodiment of the present invention, where the tag device apparatus 1200 includes: a synchronization section 1201, a second UWB data transmission interaction section 1202, a transmission or reception section 1203, and a second retransmission section 1204; wherein,,

the synchronization part 1201 is configured to receive and parse a control message sent by a base station to obtain time domain synchronization information and scheduling information, and complete time domain synchronization with the base station according to the time domain synchronization information;

The second UWB data transmission interaction part 1202 is configured to send and/or receive data messages to the base station in the data cycle corresponding to each tag device through the UWB connection in the sending time slot and/or the receiving time slot corresponding to each tag device based on the scheduling information;

the transmitting or receiving section 1203 is configured to transmit or receive a corresponding data acknowledgement message to the base station in a transmission slot and/or a reception slot configured for itself in a data cycle corresponding to each tag device;

the second retransmission portion 1204 is configured to start a data retransmission procedure of ARQ and transmit or receive retransmitted data to the base station in a data cycle configured for each tag device and a corresponding transmission slot and/or reception slot if a check result in the data acknowledgement message is an error.

In some examples, the synchronization portion 1201 is configured to:

In some examples, the second retransmission portion 1204 is configured to:

It will be appreciated that in this embodiment, a "part" may be a part of a circuit, a part of a processor, a part of a program or software, etc., and of course may be a unit, or a module may be non-modular.

In addition, each component in the present embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional modules.

The integrated units, if implemented in the form of software functional modules, may be stored in a computer-readable storage medium, if not sold or used as separate products, and based on such understanding, the technical solution of the present embodiment may be embodied essentially or partly in the form of a software product, which is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or processor to perform all or part of the steps of the method described in the present embodiment. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Accordingly, the present embodiment provides a computer storage medium storing a UWB-based multi-user data transmission scheduling program, where the UWB-based multi-user data transmission scheduling program when executed by at least one processor implements the steps of the UWB-based multi-user data transmission scheduling method in the above technical solution.

It should be understood that the exemplary solutions of the transmitting apparatus 1100 and the receiving apparatus 1200 are the same as the solutions of the foregoing UWB-based multi-user data transmission scheduling method, and therefore, for details of the solutions of the transmitting apparatus 1100 and the receiving apparatus 1200 that are not described in detail, reference may be made to the descriptions of the solutions of the foregoing UWB-based multi-user data transmission scheduling method. The embodiments of the present invention will not be described in detail.

It should be noted that: the technical schemes described in the embodiments of the present invention may be arbitrarily combined without any collision.

The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A multi-user data transmission scheduling method based on UWB, wherein the method is applied to a base station, the method comprising:

2. The method according to claim 1, wherein said interacting with each tag device according to said scheduling information in corresponding transmission time slots and/or reception time slots of a synchronization cycle allocated for the base station itself to complete control messages to establish UWB connections with each tag device comprises:

3. The method according to claim 1, wherein the step of completing a data transmission message interaction process with each tag device and obtaining a verification result of transmitted data through the UWB connection at a corresponding transmission slot and/or reception slot of a data cycle allocated by the scheduling information for the base station itself comprises:

4. A multi-user data transmission scheduling method based on UWB, wherein the method is applied to any one of tag devices, the method comprising:

5. The method of claim 4, wherein the receiving the control message sent by the base station and parsing to obtain the time domain synchronization information and the scheduling information, performing time domain synchronization with the base station according to the time domain synchronization information, comprises:

6. The method according to claim 4, wherein if the check result in the data confirmation message is an error, starting the data retransmission flow of ARQ and transmitting or receiving the retransmitted data to the base station in the data cycle and the corresponding transmission time slot and/or reception time slot configured for each tag device, comprises:

7. A base station apparatus, characterized in that the base station apparatus comprises: the device comprises a generation part, a establishment part, a first UWB data transmission interaction part and a first retransmission part; wherein,,

8. A tag device apparatus, the tag device apparatus comprising: a synchronization section, a second UWB data transmission interaction section, a transmission or reception section, and a second retransmission section; wherein,,

9. A network node device, the network node device comprising: wireless communication circuitry, memory, and a processor; the components are coupled together by a bus system; wherein,,

the processor is configured to perform the steps of the UWB-based multi-user data transmission scheduling method of any one of claims 1 to 3 or of any one of claims 4 to 6 when the computer program is run.

10. A UWB-based multi-user data transmission scheduling system, the system comprising: a base station and all tag devices within the signal coverage range of the base station; wherein,,

the base station configured to perform the steps of the UWB-based multi-user data transmission scheduling method of any of claims 1 to 3;

any of the tag devices is configured to perform the steps of the UWB-based multi-user data transmission scheduling method of any of claims 4 to 6.

11. A computer storage medium storing a UWB-based multi-user data transmission scheduler, which when executed by at least one processor implements the steps of the UWB-based multi-user data transmission scheduling method of any one of claims 1 to 3 or of any one of claims 4 to 6.