Method, apparatus and related device for transmitting low latency data

Abstract

The application discloses a low-latency data transmission method, device and related equipment, and belongs to the technical field of communication. The low-latency data transmission method comprises the following steps: an access point sends a first frame to a station, the first frame is used for confirming whether there is low-latency traffic to be transmitted and / or acquiring communication channel resources required by the station for low-latency traffic transmission; and the access point receives a second frame from the station, and the second frame carries the communication channel resources required by the station for low-latency traffic transmission.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and in particular relates to a method, apparatus and related equipment for transmitting low-latency data. Background Technology

[0002] In wireless communication networks, the Low Latency Indication (LLI) mechanism can instruct low-latency traffic to be transmitted with low latency, preventing the urgent (low-latency) traffic from expiring, thereby improving the flexibility of the network transmission mechanism. In other words, LLI allows for flexible deployment of traffic scheduling strategies. A Station (STA), acting as a Transmission Opportunity Responder (TXOP Responder), sends a specific control response frame to an Access Point (AP), acting as a Transmission Opportunity Holder (TXOP Holder), upon detecting low-latency traffic, thus announcing the arrival of the low-latency traffic. Currently, some technical solutions define the Multi-STA Block Ack Frame (M-BA Frame) as the control response frame required by the LLI mechanism, and preliminarily define LLI elements in the M-BA Frame to identify the arrival of low-latency traffic. This technical solution has the following problems: the specific design of the LLI elements (such as field definitions, encoding schemes, and operating modes) is not clearly defined, which may cause communication channel resources to be unable to meet the requirements of low-latency traffic transmission. Summary of the Invention

[0003] This application provides a method, apparatus, and related equipment for transmitting low-latency data.

[0004] Firstly, a method for transmitting low-latency data is provided, executed by an access point, the method comprising:

[0005] The access point sends a first frame to the site. The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission.

[0006] The access point receives a second frame from the site, the second frame carrying the communication channel resources required by the site for low-latency traffic transmission.

[0007] Secondly, a method for transmitting low-latency data is provided, executed by a station, the method comprising:

[0008] The station receives a first frame from the access point, the first frame being used to confirm with the station whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the station for low-latency traffic transmission;

[0009] The station sends a second frame to the access point, the second frame carrying the communication channel resources required by the station for low-latency traffic transmission.

[0010] Thirdly, a low-latency data transmission device is provided, comprising:

[0011] The first transceiver module is used to send a first frame to the station. The first frame is used to confirm with the station whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the station for low-latency traffic transmission.

[0012] The first transceiver module is further configured to receive a second frame from the site, the second frame carrying communication channel resources required by the site for low-latency traffic transmission.

[0013] Fourthly, a low-latency data transmission device is provided, comprising:

[0014] The second transceiver module is used to receive a first frame from the access point. The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission.

[0015] The second transceiver module is further configured to send a second frame to the access point, the second frame carrying the communication channel resources required by the site for low-latency traffic transmission.

[0016] Fifthly, a low-latency data transmission apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0017] In a sixth aspect, an access point is provided, the access point including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0018] In a seventh aspect, an access point is provided, including a processor and a communication interface, wherein the communication interface is used to send a first frame to a station, the first frame being used to confirm with the station whether there is low-latency traffic to be transmitted and / or to obtain communication channel resources required by the station for low-latency traffic transmission; the communication interface is also used to receive a second frame from the station, the second frame carrying the communication channel resources required by the station for low-latency traffic transmission.

[0019] In an eighth aspect, a site is provided that includes a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0020] A ninth aspect provides a station, including a processor and a communication interface, wherein the communication interface is configured to receive a first frame from an access point, the first frame being configured to confirm to the station whether there is low-latency traffic to be transmitted and / or to obtain communication channel resources required by the station for low-latency traffic transmission; the station sends a second frame to the access point, the second frame carrying the communication channel resources required by the station for low-latency traffic transmission.

[0021] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0022] Eleventhly, a wireless communication system is provided, comprising: an access point and a site, wherein the access point is configured to perform the steps of the method described in the first aspect, and the site is configured to perform the steps of the method described in the second aspect.

[0023] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0024] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0025] In this embodiment, the access point sends a first frame to the site to confirm whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission. Confirming the existence of low-latency traffic to be transmitted via the first frame avoids incorrect entry into low-latency traffic transmission communication channel resource negotiation due to decoding errors in the received third frame, thus improving reliability. Furthermore, the access point can also instruct the site to provide feedback on the required communication channel resources for low-latency traffic transmission via the first frame, providing a basis for the low-latency traffic communication channel resource negotiation mechanism. The site can declare the required communication channel resources for low-latency traffic transmission via the second frame, providing a basis for the subsequent low-latency traffic communication channel resource negotiation mechanism between the access point and the site. The low-latency data transmission method provided in this embodiment can guarantee the low-latency traffic transmission requirements. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a schematic diagram of a network architecture of a communication system provided in an embodiment of this application;

[0028] Figure 2 This is a basic flowchart of an LLI mechanism provided in the embodiments of this application;

[0029] Figure 3 This is a diagram illustrating the problems associated with a related LLI mechanism;

[0030] Figure 4 This is a flowchart illustrating a low-latency data transmission method provided in an embodiment of this application;

[0031] Figure 5 This is a schematic diagram of the structure of a Frame Control field provided in an embodiment of this application;

[0032] Figure 6 This is a schematic diagram of the structure of an LLIICF provided in an embodiment of this application;

[0033] Figure 7 This is a schematic diagram of the structure of the first ultra-high reliability low latency indication user information field in an LLIICF frame provided in an embodiment of this application;

[0034] Figure 8This is a schematic diagram of the structure of an LLIM-BA frame provided in an embodiment of this application;

[0035] Figure 9 This is a schematic diagram of the structure of an LLI Information field provided in an embodiment of this application;

[0036] Figure 10 This is a schematic diagram illustrating the process of negotiating low-latency traffic communication channel resources between an access point and a site, as provided in an embodiment of this application.

[0037] Figure 11 This is a schematic diagram of the structure of a second ultra-high reliability low latency indication user information field provided in an embodiment of this application;

[0038] Figure 12 This is a schematic diagram of the structure of an LLI-Communication Resource ParametersElement provided in an embodiment of this application;

[0039] Figure 13 This is a schematic diagram of the structure of a Communication Resource Parameters field provided in an embodiment of this application;

[0040] Figure 14 This is one of the structural schematic diagrams of the low-latency data transmission device provided in the embodiments of this application;

[0041] Figure 15 This is a second schematic diagram of the structure of the low-latency data transmission device provided in the embodiments of this application;

[0042] Figure 16 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0043] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0044] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0045] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0046] The technical solutions provided in this application can be applied to wireless local area network (WLAN) systems, and are applicable to any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series protocols used in WLANs, such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, and future 802.11 protocols. The methods provided in this application can be implemented by communication devices in a wireless communication system or by chips or processors within those devices. Accordingly, the communication device supports communication using the IEEE 802.11 series protocols. Although the embodiments of this application are mainly illustrated using a network deploying IEEE 802.11 as an example, those skilled in the art will readily understand that the various aspects involved in this application can be extended to other networks employing various standards or protocols, such as Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to IEEE 802.11, mainly used in Europe), wide area network (WAN), WLAN, personal area network (PAN), wireless personal area network systems based on ultra-wideband (UWB), sensing systems, or other networks now known or to be developed in the future. The methods provided in the embodiments of this application can be applied to the IEEE 802.15 series protocols, such as the 802.15.4a protocol, the 802.15.4z protocol, or the 802.15.4ab protocol, or a future generation of UWB WPAN protocol, etc., which will not be listed one by one.The technical solutions provided in this application can also be applied to the following communication systems, such as Internet of Things (IoT) systems, Vehicle-to-X (V2X) systems, narrowband Internet of Things (NB-IoT) systems, devices used in V2X systems, IoT nodes and sensors in IoT systems, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities. Alternatively, they can also be applied to Long Term Evolution (LTE) systems, 5th-generation (5G) communication systems, and new communication systems that will emerge in future communication developments. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in this application can be applied to any suitable wireless network.

[0047] In the Wi-Fi protocol, a station (abbreviated as STA) includes access point stations (abbreviated as AP STA) and non-access point stations (abbreviated as non-AP station). For the sake of simplicity, access point stations are usually called access points (abbreviated as AP), and non-access point stations are called stations (abbreviated as STA).

[0048] For example, please refer to Figure 1 This illustration shows a schematic diagram of the network architecture of a communication system 100 provided in some embodiments of this application. The communication system 100 may include an access point AP 110 and a station STA 120 that accesses the network through the access point 110.

[0049] In this application embodiment, the access point can also be referred to as an access point device, and the site can also be referred to as a site device.

[0050] The communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between two non-AP STAs, or communication between a STA and a peer STA. Here, a peer STA can refer to a device that communicates with a STA on an equal footing. For example, a peer STA may be an AP or a non-AP STA.

[0051] An access point (AP) acts as a bridge connecting wired and wireless networks. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet. AP devices can be terminal devices with Wi-Fi chips (such as mobile phones) or network devices (such as wireless routers, wireless switches, or wireless repeaters).

[0052] It should be understood that the role of a STA in a communication system is not absolute. For example, in some scenarios, when a mobile phone connects to a router, it is a non-AP STA; when the mobile phone acts as a hotspot for other mobile phones, it plays the role of an AP.

[0053] Access points can support communication or sensing based on Wi-Fi protocols, such as 802.11b, 802.11a, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, or next-generation or later protocols.

[0054] The site can support communication or sensing based on Wi-Fi protocols, such as 802.11b, 802.11a, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, or next-generation or later protocols.

[0055] WLAN systems can provide high-speed, low-latency transmission. As WLAN application scenarios continue to evolve, WLAN systems will be applied to more scenarios or industries, such as the Internet of Things industry, the Internet of Vehicles industry, the banking industry, enterprise offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, shopping malls, squares, streets, production workshops and warehouses, etc. Of course, devices that support WLAN communication or sensing (such as access points or sites) can be sensor nodes in smart cities (such as smart water meters, smart electricity meters, and smart air monitoring nodes), smart devices in smart homes (such as smart cameras, projectors, displays, televisions, speakers, refrigerators, and washing machines), nodes in the Internet of Things (IoT), entertainment terminals (such as wearable devices for augmented reality (AR) and virtual reality (VR), smart devices in smart offices (such as printers, projectors, loudspeakers, and speakers), vehicle-to-everything (V2X) devices, infrastructure in daily life scenarios (such as vending machines, self-service navigation kiosks in supermarkets, self-service checkout machines, and self-service ordering machines), and equipment in large sports and music venues.

[0056] In this embodiment, an access point is a device with wireless communication capabilities, supporting communication or sensing using the WLAN protocol. It has the function of communicating or sensing with other devices in the WLAN network (such as non-AP STAs or other access points), and can also have the function of communicating or sensing with other devices. Alternatively, an access point acts as a bridge connecting wired and wireless networks, primarily connecting various wireless network clients together and then connecting the wireless network to the Ethernet. This wireless communication device can be a complete device, or a chip, processing system, or functional module installed within a complete device. Devices with these chips, processing systems, or functional modules can implement the methods and functions of this embodiment under the control of the chips, processing systems, or functional modules. The AP in this embodiment is a device providing services to non-AP STAs and can support 802.11 series protocols or subsequent protocols. For example, an access point can be an access point for terminals (such as mobile phones) to enter a wired (or wireless) network, mainly deployed in homes, buildings, and parks, with a typical coverage radius of tens to hundreds of meters; it can also be deployed outdoors. For example, an AP can be a communication server, router, switch, bridge, or other communication entity; APs can include various forms of macro base stations, micro base stations, repeater stations, etc.

[0057] In the embodiments of this application, the site can be a user terminal device supporting WLAN or Wi-Fi technology, a mobile phone, a tablet computer, a computer, a virtual reality (VR) device, an augmented reality (AR) device, a wireless device in industrial control, a set-top box, a wireless device in autonomous driving, a vehicle communication device, a wireless device in remote medical care, a wireless device in a smart grid, a wireless device in transportation safety, a wireless device in a smart city or a wireless device in a smart home, a wireless communication chip / application specific integrated circuit (ASIC) / system on chip (SOC), etc.

[0058] WLAN technology can support frequency bands including but not limited to: low frequency bands (e.g., 2.4GHz, 5GHz, 6GHz) and high frequency bands (e.g., 45GHz or 60GHz).

[0059] Figure 1 An exemplary embodiment shows one AP 110 and two non-AP STAs 120. Optionally, the communication system 100 may include multiple AP STAs and other numbers of non-AP STAs, which is not limited in this application embodiment.

[0060] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include an access point 110 and a station 120 with communication functions. The access point 110 and the station 120 may be the specific equipment mentioned above, which will not be repeated here. The communication equipment may also include other equipment in the communication system 100, such as network controllers, gateways and other network entities. This application embodiment does not limit this.

[0061] It should be understood that the terms “system” and “network” used in this application are often used interchangeably herein.

[0062] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0063] In this application embodiment, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including access points and sites). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0064] In this application embodiment, "protocol" may refer to standard protocols in the field of communication, such as Wi-Fi protocols and related protocols applied in future Wi-Fi communication systems, and this application does not limit it.

[0065] Access point 110 and site 120 can associate and communicate via wireless LAN technology. Association refers to the process of negotiating wireless link services between the STA and AP to establish a wireless link between them.

[0066] In wireless communication networks, Low Latency Indication (LLI) mechanisms instruct low-latency traffic to be transmitted with low latency, preventing urgent (i.e., low-latency) traffic from expiring. This enhances the flexibility of network transmission mechanisms; in other words, LLI allows for flexible deployment of traffic scheduling strategies. In critical fields with extremely high real-time requirements, such as the Industrial Internet, autonomous driving, and virtual reality, LLI, with its millisecond-level low-latency transmission characteristics, has become a crucial data transmission method.

[0067] Taking an industrial internet scenario as an example, when an emergency occurs on-site, such as a sensor detecting unauthorized entry, the communication station (STA) needs to immediately declare this low-latency service request to the access point (AP), and the AP must respond quickly to mitigate risks. At this time, the STA, acting as a Transmission Opportunity Responder (TXOP Responder), sends a specific control response frame to the AP, acting as a Transmission Opportunity Holder (TXOP Holder), after detecting the low-latency traffic, thus announcing the arrival of the low-latency traffic. The transmission of this frame directly triggers the AP (TXOP Holder) to immediately allocate the necessary Transmission Opportunity (TXOP) and corresponding low-latency communication channel resources to the STA (TXOP Responder). Specifically, the STA (TXOP Responder) uses the LLI mechanism to request the necessary radio frequency resources from the AP (TXOP Holder) for transmitting the low-latency traffic, thereby ensuring that it can quickly complete data transmission. To strictly compress the transmission latency of low-latency traffic within the required range and avoid serious consequences due to expiration, the LLI mechanism needs to work in conjunction with a dynamic rate calculation mechanism. The aforementioned LLI mechanism can accurately calculate the minimum rate required to ensure timely transmission based on the specific characteristics and latency requirements of the service traffic, and dynamically adapt appropriate radio frequency resources accordingly, ensuring that low-latency traffic is always guaranteed timely and reliable transmission.

[0068] It should be noted that, in the embodiments of this application, the Transmission Opportunity Responder (TXOP Responder) and the site are interchangeable, and the Transmission Opportunity Holder (TXOP Holder) and the access point are interchangeable.

[0069] Figure 2 This is a basic flowchart of an LLI mechanism provided in the embodiments of this application. Figure 2As shown, when the STA (TXOPResponder) generates a low-latency traffic request during data reception, it will declare the low-latency request to the AP (TXOPHolder) after the current TXOP data reception is completed through a control response frame of a specific type to be determined (TBD). This control response frame can carry LLI elements to notify the TXOP Holder of the arrival of low-latency traffic.

[0070] Both TXOP Responder and TXOP Holder need to activate the dot11LowLatencyIndicationActivated primitive beforehand and declare support for low-latency transmission in the Ultra High Reliability Capabilities Element (UHR Capabilities Element), that is, the UHR Capabilities Element should have LLI Support=1 set.

[0071] Once the TXOP Holder receives the declaration of the arrival of this low-latency traffic, it must perform the following operations in the next TXOP phase:

[0072] (1) Immediately pause data transmission: Stop sending normal data streams to this TXOP Responder;

[0073] (2) Actively release the right to use TXOP: hand over channel control through pending signaling (such as ACK / RTS / CTS frames);

[0074] (3) Dynamically negotiate resources: Allocate dedicated low-latency traffic communication channel resources based on LLI requirements to realize low-latency data transmission of the traffic.

[0075] After obtaining the right to use TXOP, the TXOP Responder quickly seizes the channel and then directly sends low-latency traffic data (such as when a vehicle network recognizes a pedestrian suddenly crossing the road and forces the vehicle to activate the braking command within milliseconds).

[0076] Taking a specific communication scenario between TXOP Holder and TXOP Responder as an example, such as Figure 2As shown, the TXOP Holder successfully occupies the channel and becomes the data sender, while the TXOP Responder (such as an autonomous driving sensor) acts as the data receiver. When the TXOP Holder (such as the vehicle's main control unit) is sending a normal service data frame to the TXOP Responder, the TXOP Responder suddenly detects the occurrence of low-latency traffic (such as encountering a pedestrian crossing the road while driving). It needs to process and buffer this low-latency traffic first, and then quickly report it to the TXOP Holder. When the TXOP Holder finishes transmitting normal traffic, the TXOP Responder sends a control response frame carrying LLI elements back to the TXOP Holder to indicate that there is low-latency traffic that the TXOP Responder needs to process, and requests the communication channel resources required for low-latency transmission from the TXOP Holder.

[0077] Upon receiving the control response frame, the TXOP Holder negotiates with the TXOP Responder for the low-latency traffic communication channel resources required to handle the aforementioned low-latency traffic. Two scenarios exist: if the TXOP Responder agrees to the low-latency traffic communication channel resources allocated by the TXOP Holder, the buffered low-latency traffic is immediately transmitted to the TXOP Holder via the LLI mechanism; if the TXOP Responder does not agree to the low-latency traffic communication channel resources allocated by the TXOP Holder, further negotiation of low-latency traffic communication channel resources is required.

[0078] As can be seen from the above examples, the successful implementation of the LLI mechanism requires a complete low-latency traffic communication channel resource negotiation mechanism for both the TXOP Holder and TXOP Responder. However, the corresponding LLI mechanism improvement schemes have not yet further discussed the low-latency traffic communication channel resource negotiation mechanism. The following are corresponding improvement schemes for the LLI mechanism in related technologies:

[0079] (1) The LLI mechanism improvement scheme defines the Multi-STA Block Ack Frame (M-BAFrame) as the control response frame required by the LLI mechanism, and initially defines the LLI elements in the M-BAFrame.

[0080] (2) The LLI mechanism support scheme introduces the LLI Support field in UHR MAC Capabilities Elements.

[0081] (3) The low-latency traffic identification scheme designs a method for TXOP Holder to accurately identify low-latency transmission requirements.

[0082] The above improvement plan has the following shortcomings:

[0083] The key definition is vague: the required LLI elements are not clearly defined. Apart from indicating that the TXOP Responder buffers low-latency traffic and needs to transmit it to the TXOP Holder for processing, no related fields and their functions are defined. This may cause problems with communication channel resource incoordination. For example, the lack of RU Allocation declaration may cause the TXOP Holder to use the default configuration (such as MCS5+26-tone RU) to receive low-latency traffic, which cannot meet the transmission rate requirements of low-latency traffic.

[0084] Reliability risk: The lack of a low-latency traffic communication channel resource negotiation mechanism between TXOP Holder and TXOP Responder makes it impossible to guarantee the instant transmission requirements of low-latency traffic, thus causing a decline in communication reliability.

[0085] No priority guarantee: The LLI mechanism does not indicate the priority or traffic volume of low-latency traffic. After receiving the control response frame sent by the TXOP Responder, the TXOP Holder may ignore the low-latency traffic because it needs to process high-priority ordinary business traffic.

[0086] In summary, the LLI mechanism in related technologies has the following three interrelated problems that require further improvement:

[0087] Problem 1: Insufficient control signaling expression capabilities

[0088] The current LLI mechanism has certain limitations in its control signaling design. Its core challenge lies in the lack of standardized coding rules for LLI elements. The LLI mechanism merely conveys the existence of low-latency service requirements through control response frames, without specifying concrete resource configuration parameters. This leads to a situation where, when the TXOP Holder receives low-latency traffic, it may adopt a generic configuration—such as MCS5 modulation with a 26-tone narrowband RU—to meet the low-latency service transmission requirements. However, this default configuration may result in outdated low-latency traffic. Furthermore, the lack of clearly defined dynamic adaptation rules between service characteristics and RF parameters may increase the probability of RU resource contention in densely deployed scenarios, impacting communication stability.

[0089] Question 2: The low-latency traffic communication channel resource negotiation mechanism between TXOP Holder and TXOP Responder still needs to be established.

[0090] The LLI mechanism warrants further exploration in the negotiation of low-latency traffic communication channel resources. When there is a discrepancy between the general resource configuration of the TXOPHolder and the requirements of low-latency services (such as insufficient RU bandwidth), the TXOP Responder lacks an effective way to request parameter renegotiation and also struggles to initiate a low-latency service degradation process, thus affecting the continuity of low-latency traffic. For example, in VR scenarios, a 90fps video stream may experience a latency exceeding the 20ms threshold during transmission due to insufficient initial bandwidth allocation, potentially leading to a decrease in smoothness. The root cause lies in the lack of a corresponding low-latency traffic communication channel resource negotiation process for the LLI mechanism, i.e., a flexible adjustment mechanism for low-latency traffic communication channel resources. When resources are insufficient, the TXOP Holder can only refuse and cannot provide alternative solutions, making it difficult to achieve latency targets through appropriate transmission quality degradation. These limitations may reduce system fault tolerance, creating a chain reaction of challenges: "ambiguous requirements → resource configuration discrepancies → lack of negotiation paths → service quality fluctuations."

[0091] Question 3: The mechanism for differentiating the urgency of business needs improvement.

[0092] The LLI mechanism has room for optimization in terms of business priority management. Because traditional LLI elements do not integrate an expiration timestamp field, the TXOP Holder struggles to accurately identify the timeliness differences of various traffic flows. Industrial control commands (i.e., low-latency traffic with a latency threshold ≤ 5ms) and ordinary business traffic (latency threshold ≤ 50ms) may share the same priority during scheduling, potentially causing low-latency traffic to face resource contention pressure. In certain scenarios, due to the lack of priority identifiers, device control commands may be allocated to narrowband RUs for multiple transmissions, potentially exceeding the latency threshold and impacting system real-time performance. When multiple TXOPResponders concurrently request low-latency services, the TXOP Holder lacks a quantitative standard for prioritizing processing based on urgency, raising the possibility that low-latency traffic may be delayed in processing as regular data, posing a challenge to the reliability of latency-sensitive applications.

[0093] The problems with the LLI mechanism mentioned above are somewhat related. Figure 3 This is a diagram illustrating the relationships between problems inherent in a particular LLI mechanism. For example... Figure 3As shown, in the aforementioned LLI mechanism, during the stage where the TXOP Responder sends a control response frame carrying LLI to the TXOP Holder, signaling defects in the control response frame may cause the TXOP Responder to be unable to accurately declare the transmission requirements of low-latency traffic and the urgency of low-latency traffic transmission to be unquantifiable, which in turn leads to inaccurate resource allocation and requires negotiation of low-latency traffic communication channel resources. However, the lack of a low-latency traffic communication channel resource negotiation mechanism may ultimately lead to the expiration or transmission failure of low-latency traffic.

[0094] To address the problems discussed above, the embodiments of this application devise the following method:

[0095] To address issue 1, this application proposes a low-latency traffic indication method to assist the TXOP Responder in promptly notifying the TXOP Holder of the arrival of low-latency traffic. Furthermore, for the BA Information field of the M-BA frame, an LLI element is designed and improved within this field. This element includes communication channel resource information required by the TXOP Responder to transmit the low-latency traffic.

[0096] To address issue 2, this application embodiment designs a low-latency traffic communication channel resource negotiation mechanism. When the TXOPHolder receives a communication channel resource request from the TXOP Responder, if the current TXOP Holder cannot provide the required communication channel resources to the TXOP Responder due to resource overload, the TXOP Holder can negotiate a degraded low-latency traffic communication channel resource with the TXOP Responder through an LLI Initial Control Frame (LLIICF) until both parties are satisfied, and then the TXOP Responder transmits low-latency traffic to the TXOP Holder.

[0097] To address issue 3, this application proposes a dynamic priority classification method for low-latency traffic. Based on the expiration time limit of low-latency traffic represented by the Maximum Latency field of the LLI element and the priority of the Traffic Identifier (TID) of low-latency service data, the TXOP Holder can implement a dynamic priority classification method for the low-latency service requirements of multiple TXOP Responders to determine the receiving order of low-latency service data of the TXOP Holder, thereby ensuring that all low-latency service data can be accurately received by the TXOP Holder.

[0098] The low-latency data transmission method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0099] Figure 4 This is a flowchart illustrating a low-latency data transmission method provided in an embodiment of this application. Figure 4 As shown, the low-latency data transmission method includes at least one of steps 400 to 405.

[0100] It should be understood that the low-latency data transmission method involved in the embodiments of this application may include at least one of steps 400 to 405. Figure 4 Each step can be implemented as a separate embodiment, and Figure 4 The combination of any two steps can be implemented as an independent embodiment, but is not limited thereto.

[0101] Step 400: When the site detects the arrival of low-latency traffic, the site sends a third frame to the access point. The frame control field of the third frame includes a Low Latency Indicator (LLI) identifier, which is used to indicate the arrival of low-latency traffic.

[0102] It is understood that the embodiments in this application are improvements based on the LLI mechanism, such as... Figure 2 As shown, the access point is the Transmission Opportunity Holder (TXOP Holder), and the station is the Transmission Opportunity Responder (TXOP Responder). When the AP (TXOP Holder) uses the TXOP to transmit data to the STA (TXOP Responder), if the TXOP Responder detects the arrival of low-latency traffic, i.e., the STA has low-latency traffic to be transmitted, the TXOP Responder needs to temporarily occupy the channel occupied by the TXOP Holder in order to transmit the low-latency traffic to the TXOP Holder for processing as soon as possible.

[0103] When the AP (TXOP Holder) finishes transmitting normal traffic (such as data, signaling, or broadcast frames), the STA (TXOP Responder) needs to send a control response frame back to the TXOP Holder to notify the TXOP Holder that the TXOP Responder has successfully received the transmitted data.

[0104] When the STA (TXOP Responder) needs to transmit low-latency traffic, unlike receiving ordinary traffic, the TXOP Responder needs to embed LLI-related information in the feedback control response frame. This control response frame with embedded LLI-related information is the third frame. In this embodiment, the LLI-related information includes at least one of the following: an LLI identifier and LLI information. The LLI identifier indicates a low-latency transmission requirement, i.e., the arrival of low-latency traffic. The LLI information is specific information about the low-latency traffic, including at least one of the following: whether there is low-latency traffic to be transmitted, whether the access point provides communication channel resources for low-latency traffic transmission, and the communication channel resources required by the station for low-latency traffic transmission.

[0105] Step 401: The access point receives a third frame from the site. The third frame includes a Low Latency Indicator (LLI) identifier, which is used to indicate a low latency transmission requirement.

[0106] The access point receives the third frame from the site, thus knowing that the site has low-latency traffic to be transmitted.

[0107] It should be noted that steps 400 and 401 are optional. In the case where the low-latency data transmission method provided in this application includes steps 400 and 401, the STA actively informs the access point of the existence of low-latency transmission requirements through the third frame.

[0108] Optionally, the third frame is a control response frame, which includes one of the following:

[0109] Acknowledgment of ACK frame;

[0110] Clear the sending of CTS frames;

[0111] Power-saving PS polling frames;

[0112] Block confirmation BA frame;

[0113] Multi-site block confirmation of M-BA frames.

[0114] The third frame is a control response frame from the station (TXOP Responder) to the access point (TXOP Holder). The specific type of this frame is influenced by the information transmitted by the TXOP Holder, that is, by the information sent by the access point to the station before sending the third frame. For example, embodiments of this application provide the following different types of third frames:

[0115] (1) When the TXOP Holder transmits a data frame to the TXOP Responder, the control response frame that the TXOP Responder needs to send is an acknowledgment frame (abbreviated as ACK frame).

[0116] (2) When the TXOP Holder transmits a Request-to-SendFrame (RTS Frame) or a Multi-user RTS Frame (MU-RTS Frame) to the TXOP Responder, the control response frame that the TXOP Responder needs to send is a Clear-to-SendFrame (CTS Frame).

[0117] (3) When the TXOP Holder transmits a beacon frame with a traffic indication map (TIM) to the TXOPResponder in power save (PS) mode to indicate that the TXOP Holder's register stores normal traffic that needs to be transmitted to the TXOP Responder, the control response frame that the TXOP Responder needs to return is a PS poll frame.

[0118] (4) When the TXOP Holder transmits a block acknowledgment session, the control response frame that the TXOP Responder needs to send back is a block acknowledgment frame (BA Frame).

[0119] (5) When the TXOP Holder sends an ICF to the TXOP Responder for subsequent action negotiation, the TXOP Responder can feed back the negotiation result to the TXOP Holder through the M-BA Frame.

[0120] In the control response frames primarily used above, BA Frame and M-BA Frame have BA Control and BA Information fields as their frame bodies, making it easy to embed LLI-related information into the BA Information field. However, ACK Frame, CTS Frame, and PS-Poll Frame lack a frame body. This means that if the STA (TXOP Responder) uses the traditional ACK Frame, CTS Frame, or PS-Poll Frame as its control response frame when low-latency traffic is to be transmitted, LLI-related information cannot be directly embedded into the frame body of these frames. Furthermore, in BA Frame and M-BA Frame, if LLI-related information is only used to indicate the arrival of low-latency traffic without including low-latency traffic communication channel resources, it may prevent the AP (TXOP Holder) and TXOP Responder from negotiating low-latency traffic communication channel resources.

[0121] It should be noted that all of the above-mentioned types of third frames (various control response frames) contain a FrameControl field. The LLI identifier of the third frame can be included in the FrameControl field of the third frame.

[0122] Figure 5 This is a schematic diagram of the structure of a Frame Control field provided in an embodiment of this application. For example... Figure 5 As shown, the Frame Control field includes the following subfields: Protocol Version, Type, SubType, To DS, From DS, More Fragments, Retry, Power Management, More Data, Protected Frame, and Whether to Carry HTC (+HTC).

[0123] Optionally, the LLI identifier is located in the frame control field of the third frame. The frame control field includes a first subfield and a second subfield, which together serve as a low latency indicator identifier.

[0124] The first subfield is the More Data subfield, and the second subfield is the Protected Frame subfield.

[0125] In this embodiment, all types of third frames in the low-latency scenario contain a frame control field. By selecting the meaning of the encoded combination in the frame control field, a low-latency indicator can be carried in each type of third frame. The "More Data" subfield in the frame control field indicates whether there is excess traffic waiting to be transmitted at the STA (TXOP Responder), and the arrival of low-latency traffic also means that there is low-latency traffic waiting to be transmitted. The "Encryption Protection Frame" subfield indicates whether the frame body of the frame needs to be encrypted, while ACK Frame, CTS Frame, and PS-Poll Frame do not have a frame body; at the same time, the frame bodies of BAFrame and M-BA Frame do not need to be encrypted. The "Encryption Protection Frame" subfield is equivalent to a reserved subfield in each type of third frame, so the value of the "Encryption Protection Frame" subfield will not have a significant impact on the control response frame. By combining the "More Data" subfield and the "Encryption Protection Frame" subfield in the frame control field as low-latency indicator, the field encoding meaning of the control response frame in the existing protocol can be aligned, and possible ambiguity can be avoided.

[0126] This application does not limit the encoding combination and meaning of more data subfields and encrypted protection frame subfields in the embodiments.

[0127] In some embodiments, when both the More Data Subfield and the Encryption Protection Frame Subfield are set to 1, the More Data Subfield and the Encryption Protection Frame Subfield are used to indicate the arrival of low-latency traffic and trigger low-latency traffic communication channel resource negotiation.

[0128] That is, (More Data, Protected Frame) = (1,1), which means that low-latency traffic has arrived and triggered low-latency traffic communication channel resource negotiation.

[0129] In some embodiments, when both the More Data Subfield and the Encryption Protection Frame Subfield are 0, the More Data Subfield and the Encryption Protection Frame Subfield are used to indicate that the access point can continue to occupy the Transmission Opportunity (TXOP) to transmit data or signaling to the site.

[0130] That is, (More Data, Protected Frame) = (0,0), which means that under normal circumstances, the TXOP Holder continues to occupy the TXOP to transmit data or signaling to the TXOP Responder.

[0131] When the value of the More Data subfield is 1 and the value of the Encryption Protection Frame subfield is 0, the More Data subfield and the Encryption Protection Frame subfield are used to indicate the arrival of normal traffic and that the access point can continue to occupy the TXOP to transmit data or signaling to the site.

[0132] That is, (More Data, Protected Frame) = (1,0), which means that the TXOP Responder notifies the TXOP Holder of the arrival of normal traffic. Regardless of the transmission needs of the normal traffic, the TXOP Holder continues to occupy the TXOP to transmit data or signaling to the TXOP Responder.

[0133] When the value of the More Data subfield is 0 and the value of the Encryption Protection Frame subfield is 1, the More Data subfield and the Encryption Protection Frame subfield are used to instruct the access point to discard the third frame and instruct the site to retransmit the third frame.

[0134] That is, (More Data, Protected Frame) = (0,1), indicating that the third frame is an invalid signaling, and TXOPHolder needs to discard the control response frame and request TXOP Responder to retransmit the control response frame.

[0135] It should be noted that the above-described encoding combinations of more data subfields and encrypted protection frame subfields provided in the embodiments of this application, as well as the corresponding functions of each encoding combination, are applicable to devices that support 802.11bn features.

[0136] In some embodiments, the method further includes:

[0137] If the access point is a Pre-UHR device, the access point discards the third frame when the value of the more data subfield is 0 and the value of the encryption protection frame subfield is 1, or when the value of the more data subfield is 1 and the value of the encryption protection frame subfield is 0, or when the values ​​of both the more data subfield and the encryption protection frame subfield are 1.

[0138] It should be noted that Ultra High Reliability (UHR) devices are devices that support ultra-high reliability. UHR is a feature of 802.11bn, so UHR devices also indicate devices that support the 802.11bn protocol. Pre-UHR devices, on the other hand, indicate devices designed based on the 802.11be protocol or earlier.

[0139] For compatibility reasons, if the access point is a Pre-UHR device, the access point will discard the third frame if the value of the more data subfield is 0 and the value of the encryption protection frame subfield is 1; if the access point is a Pre-UHR device, the access point will discard the third frame if the value of the more data subfield is 1 and the value of the encryption protection frame subfield is 0; if the access point is a Pre-UHR device, the access point will discard the third frame if both the value of the more data subfield and the value of the encryption protection frame subfield are 1.

[0140] Understandably, the More Data subfield and the Encryption Protection Frame subfield are used to indicate that the access point can continue to occupy the Transmission Opportunity (TXOP) to transmit data or signaling to the site, only when both the More Data subfield and the Encryption Protection Frame subfield have a value of 0.

[0141] In this embodiment, the access point (TXOP Holder) receives a third frame from the station (TXOP Responder). The frame control field of the third frame includes a Low Latency Indicator (LLI) identifier, which indicates the arrival of low-latency traffic. This method clarifies that the LLI identifier used to indicate the arrival of low-latency traffic is located in the frame control field of the third frame, thereby adapting to various types of control response frames.

[0142] The low-latency traffic indication method provided in this application embodiment allows a site to proactively notify the access point of the arrival of low-latency traffic, enabling the network to instantly detect the occurrence of time-sensitive services.

[0143] Current technical solutions do not clearly define the specific design of LLI elements (such as field definitions, encoding schemes, and operating methods), nor do they specify the AP (TXOP Holder) receiving data carrying such information. Figure 5 The subsequent workflow after the control response frame of the LLI identifier shown is designed in this application embodiment to meet the transmission requirements of low-latency traffic. This mechanism enables the TXOP Responder and TXOP Holder to agree on how to use existing communication channel resources (such as RU, MCS, etc.) to transmit the low-latency traffic.

[0144] Step 402: The access point sends a first frame to the site. The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission.

[0145] It should be noted that, in the embodiments of this application, communication channel resources and communication resource parameters can be used interchangeably.

[0146] In some embodiments, after the AP (TXOP Holder) receives a third control response frame carrying an LLI identifier arrival indication, the AP (TXOP Holder) first needs to send a first frame to the STA (TXOP Responder) to confirm whether the STA (TXOP Responder) has low-latency traffic to be transmitted, in case the received control response frame is decoded incorrectly. Optionally, the first frame is also used to indicate to the STA the required communication channel resources for low-latency traffic transmission. That is, after step 401, step 402 is executed.

[0147] In other embodiments, the AP sends a first frame to the STA, actively inquiring whether the STA has a low-latency transmission requirement. The STA responds with the low-latency transmission requirement and simultaneously carries the required communication channel resources for low-latency traffic transmission. That is, step 402 is the first step of this low-latency data transmission method, and steps 400 and 401 do not exist before step 402.

[0148] In some embodiments, the first frame is a Low Latency Indication Initial Control Frame (LLIICF) frame.

[0149] The first frame includes a first Ultra-High Reliability Low Latency Indicator User Info (UHR LLI-User Info) field, which includes a Low Latency Indicator Request (LLI Solicited) subfield.

[0150] The Low Latency Indication Request subfield is used for at least one of the following:

[0151] Confirm that the site has low-latency traffic to be transmitted; or,

[0152] Instructs the site to provide feedback on the communication channel resources required for low-latency traffic transmission.

[0153] Understandably, the AP (TXOP Holder) sends the first frame to the STA (TXOP Responder), which is a Low Latency Indication Initial Control Frame (LLIICF). Figure 6 This is a schematic diagram of the structure of an LLIICF provided in an embodiment of this application.

[0154] Optionally, the LLIICF includes a Frame Control field, a Duration field, a Receive Address (RA) field, a Transmit Address (TA) field, an Ultra-Reliability Variant Common Info (UHR) field, a First Ultra-Reliability Low-Latency Indicator User Info (UHR LLI-User Info(v1)) field, a Padding field, and a Frame Check Sequence (FCS) field.

[0155] The UHR LLI-User Info(v1) field contains information about low-latency traffic that the TXOP Holder consults with the TXOP Responder. Figure 7 This is a schematic diagram illustrating the structure of the first ultra-high reliability low latency indication user information field in an LLIICF frame provided in this application embodiment. The first ultra-high reliability low latency indication user information field is used to indicate relevant information about low latency traffic obtained by the access point from the site.

[0156] Optionally, the first ultra-high reliability low latency indication user information field includes: an association identifier (AID) subfield, a feedback type subfield, a primary access type (Primary AC) subfield, a low latency indication request (LLI Solicited) subfield, and a reserved subfield.

[0157] Optionally, the encoding method and meaning of the LLI Solicited field are as follows:

[0158] When the LLI Solicited subfield is set to 00, the first frame is used to confirm whether the site has low-latency traffic to be transmitted. Alternatively, the first frame is used to confirm whether the site has low-latency traffic to be transmitted, and if the site has low-latency traffic to be transmitted, to instruct the site to provide the necessary communication channel resources for low-latency traffic transmission.

[0159] When the value of the LLI Solicited subfield is 11, the LLI Solicited subfield is used to indicate that the communication channel resources required by the site for low-latency traffic transmission cannot be provided.

[0160] The remaining encoded values ​​of the LLI Solicited subfield can be considered as reserved fields.

[0161] Step 403: The station receives a first frame from the access point. The first frame is used to confirm with the station whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the station for low-latency traffic transmission.

[0162] That is, the STA (TXOP Responder) receives the first frame from the AP (TXOP Holder). The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission.

[0163] In one embodiment, when the LLI Solicited field is encoded as 00, the first frame is used to confirm whether there is low-latency traffic to be transmitted at the site.

[0164] In one embodiment, when the LLI Solicited field is encoded as 00, the first frame is used to confirm whether there is low-latency traffic to be transmitted at the site, and if there is low-latency traffic to be transmitted at the site, it instructs the site to provide the required communication channel resources for low-latency traffic transmission. Thus, when the access point receives the first frame, it can obtain the communication channel resources required by the site for low-latency traffic transmission.

[0165] In this embodiment, the access point (TXOP Holder) sends a first frame (LLIICF) to the site (TXOP Responder). The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission. Confirming the existence of low-latency traffic to be transmitted via the first frame prevents decoding errors in the received third frame. The access point can also use the first frame to instruct the site to provide feedback on the required communication channel resources for low-latency traffic transmission, providing a basis for a low-latency traffic communication channel resource negotiation mechanism.

[0166] Step 404: The station sends a second frame to the access point, which carries the communication channel resources required by the station for low-latency traffic transmission.

[0167] Step 405: The access point receives a second frame from the site, which carries the communication channel resources required by the site for low-latency traffic transmission.

[0168] Understandably, when a site receives the first frame from the access point, and there is low-latency traffic to be transmitted, it generates a second frame and then sends the second frame to the access point.

[0169] In some embodiments, a station determines the communication channel resources it requires for low-latency traffic transmission, and the second frame carries these communication channel resources. These communication channel resources may implicitly indicate the presence of low-latency traffic to be transmitted.

[0170] In some embodiments, the second frame carries the communication channel resources required by the site for low-latency traffic transmission, and also carries a Low Latency Indicator (LLI) identifier, which is used to indicate low-latency transmission requirements.

[0171] In some embodiments, the second frame carries communication channel resources required by the site for low-latency traffic transmission and first confirmation information, which is used to confirm whether there is low-latency traffic to be transmitted. It should be noted that the first confirmation information is the information indicated in the LLI information field of the second frame, which is different from the aforementioned LLI identifier.

[0172] To address the issues that existing control response frames only use LLI elements to identify the arrival of low-latency traffic, resulting in insufficient expressive power, signaling defects in control response frames that may prevent the TXOP Responder from accurately declaring the transmission needs of low-latency traffic and the inability to quantify the urgency of low-latency traffic transmission, and the lack of a low-latency traffic communication channel resource negotiation mechanism, this application proposes a Low-Latency Traffic Indication Multi-Site Block Acknowledgment (LLIM-BA) frame, where the second frame can be an LLIM-BA frame.

[0173] Figure 8 This is a schematic diagram of the structure of an LLI M-BA frame provided in an embodiment of this application. For example... Figure 8 As shown, an LLI M-BA frame includes at least one of the following fields: Frame Control field, Duration field, Receive Address (RA), Transmit Address (TA), Block Acknowledgment Control (BA Control) field, LLI Information field, or Frame Check Sequence (FCS) field. The LLI Information field embeds the low-latency traffic communication channel resource information required by the STA (TXOPResponder).

[0174] Optionally, the LLIM-BA frame includes an LLI information field;

[0175] The LLI information field is used to indicate at least one of the following:

[0176] Is there low-latency traffic to be transmitted?

[0177] Whether to accept the communication channel resources provided by the access point for low-latency traffic transmission; or,

[0178] The communication channel resources required by the site for low-latency traffic transmission.

[0179] Figure 9 This is a schematic diagram of the structure of an LLI Information field provided in an embodiment of this application. For example... Figure 9 As shown, the LLI Information field includes at least one of the following: Associated Identifier Traffic Identifier Information (AID TID Info) field, Block Ack Starting Sequence Control field, or LLI Feedback element, etc. In the Block Ack Starting Sequence Control field of the LLI Information field, a value of 1 for the Feedback Type subfield indicates that the M-BA Frame is an LLI M-BA Frame and can be used as the second frame; a value of 0 for the Feedback Type subfield indicates that the M-BA Frame is a regular M-BA Frame.

[0180] Optionally, the LLI information field includes LLI feedback elements, such as Figure 9 As shown, LLI feedback elements include at least one of the following:

[0181] The Low Latency Response (LLI Response) subfield is used to indicate whether low-latency traffic exists or to provide feedback to the access point on whether to accept the communication channel resources provided by the access point for low-latency traffic transmission.

[0182] The Resource Unit Allocation (RU Allocation) subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0183] The Maximum Latency subfield indicates the maximum allowed latency for transmitting low-latency traffic;

[0184] The Data Volume subfield indicates the size of the data storage space for low-latency traffic;

[0185] The Time Granularity subfield indicates the length of the time step.

[0186] The Uplink Forward Error Correction Coding Type (UL FEC Coding Type) subfield is used to indicate the encoding method for low-latency traffic;

[0187] The Uplink Ultra-High Reliability Modulation and Coding Scheme (UL UHR-MCS) subfield indicates the modulation and coding scheme required for transmitting low-latency traffic; or,

[0188] The UL Target Receive Power subfield indicates the signal reception power of the access point.

[0189] In some embodiments, the LLI Response subfield may indicate whether the site agrees to / accepts the communication channel resources (also referred to as low-latency traffic communication channel resources) provided by the access point for low-latency traffic transmission.

[0190] Optionally, the encoding method for LLI Response fields is as follows:

[0191] The value of the LLI Response subfield is 1, which indicates agreement / acceptance of the communication channel resources provided by the access point for low-latency traffic transmission; or, it indicates the first confirmation message, that is, to confirm the existence of low-latency traffic to the TXOP Holder.

[0192] The value of the LLI Response subfield is 0, which indicates disagreement / rejection of the communication channel resources provided by the access point for low-latency traffic transmission; or, it indicates the first confirmation message, that is, denying the existence of low-latency traffic to the TXOP Holder.

[0193] Understandably, a site can use the LLI Response subfield in the LLI Information field of the LLI M-BA frame to indicate whether there is low-latency traffic to be transmitted or whether it accepts communication channel resources provided by the access point for low-latency traffic transmission.

[0194] The station can use at least one of the following subfields in the LLI information field of the LLI M-BA frame: Resource Unit Allocation (RU Allocation), Maximum Latency, Data Volume, Time Granularity, Uplink Forward Error Correction Coding Type (UL FEC Coding Type), Uplink Ultra-Reliable Modulation and Coding Scheme (UL UHR-MCS), and Uplink Target Receive Power (UL Target Receive Power) to provide feedback to the access point on the communication channel resources required for low-latency traffic transmission.

[0195] The RU Allocation subfield indicates the radio frequency resources required to transmit low-latency traffic for the TXOP Responder;

[0196] The Maximal Latency subfield represents the binary code of the longest allowed delay for transmitting the low-latency traffic, which is also the expiration time limit of the low-latency traffic. If the transmission delay exceeds the time limit corresponding to the Maximal Latency, the low-latency traffic is at risk of expiring. By designing the Maximal Latency subfield in the LLI M-BA frame, the urgency of low-latency traffic transmission can be quantified, thereby indicating the priority of low-latency traffic.

[0197] The Data Volume subfield represents the data storage space for low-latency traffic, in bits.

[0198] The Time Granularity subfield indicates the time step length. Optionally, the Time Granularity field is encoded as follows: 00 → time step length is 16μs; 01 → time step length is 160μs; 10 → time step length is 1.6ms; 11 → reserved.

[0199] It should be noted that the maximum latency threshold for transmitting this low-latency traffic is the product of the binary code of the maximum allowed latency for transmitting this low-latency traffic and the time step length:

[0200] Latancy max =Maximal Latency×Time Granularity

[0201] The UL FEC Coding Type subfield indicates the encoding method of this low-latency traffic. Optionally, the encoding method of the UL FEC Coding Type field is: 1 → Low-Density Parity Check Code (LDPC Code); 0 → Binary Convolutional Code (BCC).

[0202] The UL UHR-MCS subfield indicates the MCS used to transmit this low-latency traffic;

[0203] The UL Target Receive Power subfield indicates the signal receiving power of the TXOP Holder.

[0204] In this embodiment, a station can use at least one of the following subfields in the LLI information field of the LLI M-BA frame: Resource Unit Allocation (RU Allocation), Maximum Latency, Uplink Forward Error Correction Coding Type (UL FEC Coding Type), Uplink Ultra-Reliable Modulation and Coding Scheme (UL UHR-MCS), Uplink Target Receive Power (UL Target Receive Power), Time Granularity, and Data Volume. This allows the LLI element in the LLI M-BA frame to not only identify the arrival of low-latency traffic but also to declare the communication channel resources required for low-latency traffic transmission. Furthermore, the Maximum Latency subfield quantifies the urgency of low-latency traffic transmission, providing a basis for subsequent negotiation mechanisms between access points and stations regarding low-latency traffic communication channel resources.

[0205] The low-latency traffic indication method provided in this application embodiment may include the foregoing steps and at least one of the embodiments. For example, step 400 may be implemented as a standalone embodiment, step 401 may be implemented as a standalone embodiment, and so on; the combination of step 400 and step 401 may be implemented as a standalone embodiment, the combination of steps 400 to 405 may be implemented as a standalone embodiment, and so on, but is not limited thereto.

[0206] In some embodiments, the LLI identifier in the third frame is used to indicate the existence of low-latency traffic to be transmitted; the first ultra-high reliability low-latency indication user information field in the first frame is used to indicate whether the site has low-latency traffic to be transmitted, and to indicate that the site provides the communication channel resources required for low-latency traffic transmission if low-latency traffic to be transmitted exists; the LLI information field in the second frame is used to indicate whether low-latency traffic to be transmitted exists, and the communication channel resources required for low-latency traffic transmission by the site, or to indicate whether low-latency traffic to be transmitted does not exist.

[0207] Optionally, if the third frame is an M-BA frame, both the third frame and the second frame are Low Latency Traffic Indication Multi-Site Block Acknowledgment (LLI) M-BA frames.

[0208] It should be noted that the third frame can be an ACK frame, a CTS frame (clear transmission), a PS polling frame (power saving), or a BA frame (block acknowledgment). When the third frame is an ACK frame, a CTS frame, a PS polling frame, or a BA frame, the LLI identifier in the frame control field indicates the arrival of low-latency traffic.

[0209] If the third frame is an M-BA frame, the third frame can be an LLI M-BA frame provided in the embodiments of this application.

[0210] Optionally, if the third frame is an LLI M-BA frame, the Feedback Type subfield in the LLI Information field of the third frame is set to 1, indicating that the M-BA frame is an LLI M-BA frame, and the LLI Response subfield is used to indicate the existence of low-latency traffic to be transmitted; while the values ​​of the other subfields in the LLI Information field can be default values ​​or empty. Both the third and second frames can indicate the low-latency transmission requirement, i.e., whether there is low-latency traffic to be transmitted, through the LLI identifier in the frame control field and / or the LLI Response subfield in the LLI Information field.

[0211] In this embodiment, the access point receives a second frame from the site. The second frame carries the communication channel resources required by the site for low-latency traffic transmission. The second frame is an LLI M-BA frame. The LLI information field of the LLI M-BA frame can be used to declare the communication channel resources required by the site for low-latency traffic transmission. Through the LLI M-BA frame, the site can not only indicate the arrival of low-latency traffic, but also declare the required communication channel resources for low-latency traffic transmission, and quantify the urgency of low-latency traffic transmission, thus providing a basis for the subsequent negotiation mechanism of low-latency traffic communication channel resources between the access point and the site.

[0212] Optionally, before the site sends the second frame to the access point, the method further includes:

[0213] The site determines the communication channel resources required for low-latency traffic transmission.

[0214] In some embodiments, the site determines the required communication channel resources for low-latency traffic transmission, including at least one of the following:

[0215] The size of the data storage space for the site to acquire low-latency traffic, the priority of low-latency traffic, and the urgency of low-latency traffic;

[0216] The site determines the maximum allowable latency for transmitting low-latency traffic and the encoding method for the low-latency traffic based on the urgency of the low-latency traffic.

[0217] The site determines the minimum rate required to transmit the low-latency traffic based on the data storage space required for the low-latency traffic and the maximum allowable latency for transmitting the low-latency traffic, and then determines the actual transmission rate based on the minimum rate; or,

[0218] Based on the actual transmission rate, the site determines the modulation and coding scheme used for transmitting low-latency traffic, as well as the radio frequency resources required for transmitting low-latency traffic.

[0219] When the STA (TXOP Responder) detects low-latency traffic, it first needs to determine the data volume, priority (TID), and urgency (T) of the low-latency traffic.

[0220] The site determines the maximum allowable latency for transmitting low-latency traffic and the encoding method for the low-latency traffic based on the urgency of the low-latency traffic. This application embodiment provides a correspondence between urgency level and the maximum latency and encoding method for low-latency traffic, exemplarily where the value of T is:

[0221] 0 indicates normal; correspondingly, Maximum Latency = 10ms; UL FEC Coding Type = 1 / 0.

[0222] 1 indicates urgency; correspondingly, Maximum Latency = 2ms; UL FEC Coding Type = 1 / 0.

[0223] 2 indicates a very urgent situation; correspondingly, Maximum Latency = 400 μs; UL FEC Coding Type = 0.

[0224] 3 indicates the most urgent situation; correspondingly, Maximum Latency = 80 μs; UL FEC Coding Type = 0.

[0225] It is understandable that the higher the urgency of the low-latency service detected by the site, the higher the requirement for transmission latency of the site. LDPC Code may introduce additional channel decoding latency, so the above correspondence was designed.

[0226] The site determines the minimum rate required to transmit the low-latency traffic based on the data volume of the low-latency traffic and the maximum allowable latency for transmitting the low-latency traffic. For example, the minimum rate required to transmit this low-latency traffic... for:

[0227]

[0228] Generally speaking, in order to ensure that low-latency traffic can be promptly transmitted from the TXOP Responder to the TXOP Holder for processing, the TXOP Responder needs to be adaptively incremented. If the increment factor is β (β∈[1.5,5]), then the actual transmission rate can be determined based on the minimum rate. This is the actual transmission rate of the low-latency traffic. for:

[0229]

[0230] Based on the actual transmission rate The STA (TXOP Responder) can determine the modulation and coding scheme (MCS) and the corresponding resource unit allocation (RU) scheme required for transmitting the low-latency traffic. Then, it can pass the determined low-latency traffic communication channel resources to the AP (TXOP Holder) through the second frame (LLI M-BA Frame).

[0231] In this embodiment, the site determines the communication channel resources required for low-latency traffic transmission based on the data storage space size of the low-latency traffic, the priority of the low-latency traffic, and / or the urgency of the low-latency traffic. The communication channel resources determined by this scheme can match the actual low-latency service requirements of the site. By carrying the communication channel resources in the second frame and sending them to the access point, the access point can obtain the communication channel resources required by the site for low-latency traffic transmission, and thus further determine whether the site's low-latency traffic transmission requirements can be met.

[0232] Optionally, the method further includes:

[0233] The access point sends a first acknowledgment frame back to the site. The first acknowledgment frame is used to indicate the communication channel resources for low-latency traffic transmission.

[0234] Access points receive low-latency traffic based on communication channel resources;

[0235] After receiving the low-latency traffic transmitted by the site, the access point sends a second acknowledgment frame back to the site.

[0236] Correspondingly, the station receives a first acknowledgment frame from the access point, which is used to indicate the communication channel resources for low-latency traffic transmission;

[0237] After the first interval, the site transmits low-latency traffic to the access point;

[0238] The station receives a second acknowledgment frame from the access point; or, the station receives a fourth frame from the access point, the fourth frame being used to negotiate new communication channel resources for low-latency traffic transmission.

[0239] It should be noted that the access point indicates the communication channel resources for low-latency traffic transmission in the first confirmation frame. These communication channel resources for low-latency traffic transmission can be the communication channel resources fed back by the station, that is, the communication channel resources required by the access point for low-latency traffic transmission. Alternatively, these communication channel resources can be the communication channel resources allocated by the access point to the STA after considering the STA's needs, its own communication channel resource usage, and the needs of other STAs.

[0240] In some embodiments, when the access point determines that it can provide the communication channel resources required by the site for low-latency traffic transmission, it sends a first acknowledgment frame to the site after a first interval. This first acknowledgment frame indicates the availability of communication channel resources for low-latency traffic transmission. After the first interval, the access point receives the low-latency traffic transmitted by the site. After the access point has received all the low-latency traffic transmitted by the site, it sends a second acknowledgment frame to the site after another first interval. This second acknowledgment frame indicates that the access point has finished receiving all the low-latency traffic transmitted by the site.

[0241] In some embodiments, if the access point determines that it cannot provide the communication channel resources required by the site for low-latency traffic transmission, a fourth frame is sent to the site. The fourth frame is used to negotiate new communication channel resources for low-latency traffic transmission.

[0242] Correspondingly, the station receives a fourth frame from the access point, which is used to negotiate new communication channel resources for low-latency traffic transmission.

[0243] The fourth frame is also an LLIICF frame. The access point can write communication channel resources in the fourth frame that can be provided to the station (TXOPResponder) for transmitting low-latency traffic. The field containing the above communication channel resources is the second Ultra-High Reliability Low Latency Indicator User Information (UHR LLI-User Info(v2)) field, which replaces the first Ultra-High Reliability Low Latency Indicator User Information (UHR LLI-User Info(v1)) in the first frame mentioned above. That is, although the fourth frame and the first frame are both LLIICF frames, the frame structure of the fourth frame is different from that of the first frame. Figure 11 This is a schematic diagram of the structure of a second ultra-high reliability low latency indication user information field provided in an embodiment of this application.

[0244] Optionally, the fourth frame is an LLIICF frame, which includes a second Ultra-High Reliability Low Latency Indicator User Info (UHR LLI-User Info) field. This field indicates at least one of the following:

[0245] Unable to provide the communication channel resources required by the site for low-latency traffic transmission;

[0246] Communication channel resources available for sites to transmit low-latency traffic.

[0247] Understandably, when an access point determines that it cannot provide the communication channel resources required by a site for low-latency traffic transmission, the access point sends a fourth frame to the site. The fourth frame is used to negotiate new communication channel resources for low-latency traffic transmission. That is, it can negotiate communication channel resources with the site by carrying communication channel resources available for the site to transmit low-latency traffic, or it can implicitly instruct the site to adjust the communication channel resources required for low-latency traffic transmission by feeding back "unable to provide the communication channel resources required by the site for low-latency traffic transmission", or it can carry the indication information "unable to provide the communication channel resources required by the site for low-latency traffic transmission" and communication channel resources available for the site to transmit low-latency traffic.

[0248] In some embodiments, the second ultra-high reliability low latency indication user information field includes at least one of the following:

[0249] The Resource Unit Allocation (RU Allocation) subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0250] The Uplink Forward Error Correction Coding Type (UL FEC Coding Type) subfield is used to indicate the encoding method for low-latency traffic;

[0251] The Uplink Ultra-High Reliability Modulation and Coding Scheme (UL UHR-MCS) subfield indicates the modulation and coding scheme used for transmitting low-latency traffic; or,

[0252] The UL Target Receive Power subfield indicates the signal reception power of the access point.

[0253] Each field in the aforementioned second ultra-high reliability low latency indicator user information field represents the communication channel resources provided by the access point that are available for the site to transmit low-latency traffic. For an understanding of each field in the second ultra-high reliability low latency indicator user information field in this embodiment, please refer to the relevant descriptions of the same sub-fields in the LLI Feedback element of the LLI information field in the second frame of the aforementioned embodiment; further details will not be repeated here.

[0254] In some embodiments, the second ultra-high reliability low latency indication user information field further includes at least one of the following:

[0255] Associated Identifier (AID) subfield;

[0256] Feedback Type subfield;

[0257] Primary Access Category (Primary AC) subfield; or,

[0258] Low Latency Indication Request (LLI Solicited) subfield.

[0259] For understanding the various fields in the second ultra-high reliability low latency indicator user information field in this embodiment, please refer to the relevant descriptions of the same subfields in the first ultra-high reliability low latency indicator user information field in the previous embodiment, which will not be repeated here.

[0260] In some embodiments, when the value of the Low Latency Indication Request (LLI Solicited) subfield in the second ultra-high reliability low latency indication user information field is 11, it indicates that the access point cannot provide the communication channel resources required by the site for low-latency traffic transmission.

[0261] In this embodiment, when the access point determines that it cannot provide the communication channel resources required by the site for low-latency traffic transmission, the access point sends a fourth frame to the site. This fourth frame is an LLIICF frame. The Ultra-Reliable Low Latency Indicator User Information field in this frame is supplemented with a Resource Unit Allocation (RU) subfield, a Maximum Latency subfield, an Uplink Forward Error Correction Coding Type (UL FEC Coding Type) subfield, and an Uplink Ultra-Reliable Modulation and Coding Scheme (UL UHR-MCS) subfield to indicate the communication channel resources available from the access point for transmitting low-latency traffic. The site obtains the communication channel resources available from the access point for low-latency traffic transmission through this fourth frame, thus achieving negotiation of low-latency traffic communication channel resources between the access point and the site.

[0262] In some embodiments, the method further includes at least one of the following:

[0263] The access point receives a fifth frame from the site. The fifth frame indicates at least one of the following: whether the site accepts the communication channel resources provided by the access point for low-latency traffic transmission, and the new required communication channel resources for low-latency traffic transmission; the fifth frame is an LLI M-BA frame and has the same frame structure as the second frame.

[0264] If, in the fifth frame, the station indicates that it accepts the communication channel resources provided by the access point for low-latency traffic transmission, or if the access point determines that it can provide the communication channel resources required by the station for low-latency traffic transmission, a third acknowledgment frame is sent back to the station after a first interval; after the first interval, the access point receives the low-latency traffic; after receiving the low-latency traffic transmitted by the station, the access point sends back a fourth acknowledgment frame to the station after another first interval; or...

[0265] If the fifth frame indicates that the station does not accept the communication channel resources provided by the access point for low-latency traffic transmission, or if the access point determines that it cannot provide the communication channel resources required by the station for low-latency traffic transmission, the access point sends a fourth frame to the station again to continue negotiating new communication channel resources for low-latency traffic transmission.

[0266] The understanding of the third confirmation frame can be referenced to the first confirmation frame, and the understanding of the fourth confirmation frame can be referenced to the second confirmation frame.

[0267] Correspondingly, the station sends a fifth frame to the access point. The fifth frame is used to indicate at least one of the following: whether the station accepts the communication channel resources provided by the access point for low-latency traffic transmission, and the new required communication channel resources for low-latency traffic transmission. The fifth frame is an LLI M-BA frame and has the same frame structure as the second frame.

[0268] The station receives a third acknowledgment frame from the access point; after a first interval, the station transmits low-latency traffic to the access point; the station receives a fourth acknowledgment frame; or,

[0269] The site receives the fourth frame sent again by the access point and continues to negotiate new communication channel resources for low-latency traffic transmission.

[0270] In other words, after receiving the fourth frame from the access point, the station obtains the communication channel resources that the access point can provide for low-latency traffic transmission, which are carried in the fourth frame, and compares them with the communication channel resources required by the station for low-latency traffic transmission. The station determines whether to accept the communication channel resources provided by the access point for low-latency traffic transmission, and indicates this through the LLI Response subfield in the LLI feedback element of the fifth frame.

[0271] If the station agrees to the communication channel resources carried in the fourth frame, it sets the value of the LLI Response subfield in the LLI feedback element of the fifth frame to 1. Conversely, if the station does not agree to the communication channel resources carried in the fourth frame, it sets the LLI Response subfield in the LLI feedback element of the fifth frame to 0, and can use the LLI feedback element of the fifth frame to provide feedback on the re-determined, downgraded communication channel resources required for low-latency traffic transmission.

[0272] The access point receives a fifth frame from the site. This fifth frame is an LLI M-BA frame and has the same frame structure as the second frame. The fifth frame indicates whether the site accepts the communication channel resources provided by the access point for low-latency traffic transmission. This can be understood as: the fifth frame instructing the site to accept the communication channel resources provided by the access point for low-latency traffic transmission; or, the fifth frame instructing at least one of the following: the site does not accept the communication channel resources provided by the access point for low-latency traffic transmission, and a new, required communication channel resource for low-latency traffic transmission is requested.

[0273] Here, the new required communication channel resources for low-latency traffic transmission are the communication channel resources that have been downgraded from the communication resources indicated by the required communication channel resources carried in the second frame after negotiation with the access point.

[0274] If, in the fifth frame, the station indicates that it accepts the communication channel resources provided by the access point for low-latency traffic transmission, or if the access point determines that it can provide the communication channel resources required by the station for low-latency traffic transmission, after a first interval, the access point sends a third acknowledgment frame to the station; after the first interval, the access point receives the low-latency traffic; after receiving the low-latency traffic transmitted by the station, after the first interval, the access point sends a fourth acknowledgment frame to the station; or...

[0275] If the fifth frame indicates that the site does not accept the communication channel resources provided by the access point for low-latency traffic transmission, or if the access point determines that it cannot provide the communication channel resources required by the site for low-latency traffic transmission, the access point will send a fourth frame to the site to continue negotiating new communication channel resources for low-latency traffic transmission. The negotiation process ends when the access point and the site reach an agreement on the low-latency traffic communication channel resources.

[0276] This application provides a low-latency traffic communication channel resource negotiation mechanism. When the AP (TXOPHolder) cannot meet the low-latency traffic transmission requirements due to resource limitations, this mechanism triggers a bidirectional degradation negotiation process via LLIICF. The access point and the site interact via LLIICF and LLIM-BA frames, where the communication channel resources carried can be degraded, thus realizing a bidirectional degradation negotiation process. This progressive negotiation mode ensures that both parties can reach a feasible solution under resource-constrained conditions, avoiding the risk of service interruption while guaranteeing the core requirement of low-latency transmission. This mechanism significantly improves service continuity in resource-constrained scenarios, enabling the network to have elastic adaptability.

[0277] Figure 10 This is a schematic diagram illustrating a process for negotiating low-latency traffic communication channel resources between an access point and a site, as provided in an embodiment of this application. Figure 10 As shown, the AP (TXOP Holder) and STA (TXOP Responder) negotiate low-latency traffic communication channel resources, including:

[0278] Step 1000: After detecting the arrival of low-latency traffic, the site sends a third frame to the access point. The frame control field of the third frame includes a Low Latency Indicator (LLI) identifier, which is used to indicate a low-latency transmission request, i.e., the arrival of low-latency traffic.

[0279] Step 1001: The access point receives the third frame and obtains the low-latency traffic arrival indication;

[0280] Step 1002: The access point sends a first frame (LLIICF) to the site. The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission. The value of the LLI Solicited field of the first frame is 00, which means that the access point is asking the TXOP Responder whether it has low-latency traffic waiting to be transmitted.

[0281] Step 1003: The station receives the first frame and determines the communication channel resources required by the station for low-latency traffic transmission;

[0282] Step 1004: The station sends a second frame (LLIM-BA frame) to the access point. This second frame contains the communication channel resources required by the station for low-latency traffic transmission. The LLI Information field of this LLI-BA frame contains the communication channel resources requested by the TXOPResponder for transmitting low-latency traffic.

[0283] Step 1005: The access point receives the second frame and determines whether it can provide the communication channel resources required by the site for low-latency traffic transmission (i.e., determine whether the low-latency requirement of the site can be met). If the access point determines that it can provide the communication channel resources required by the site for low-latency traffic transmission, it jumps to step 1010. If the access point determines that it cannot provide the communication channel resources required by the site for low-latency traffic transmission, it executes step 1006.

[0284] Step 1006: The access point sends a fourth frame (LLIICF) to the site. The fourth frame is used to negotiate new communication channel resources for low-latency traffic transmission. Optionally, the fourth frame indicates at least one of the following through the second ultra-high reliability low latency indication user information field: the communication channel resources required by the site for low-latency traffic transmission cannot be provided; or the communication channel resources available for the site to transmit low-latency traffic are available.

[0285] Step 1007: The station receives the fourth frame and determines whether the new low-latency traffic communication channel resources provided by the access point meet the station's low-latency traffic transmission requirements, or the station downgrades the low-latency traffic transmission requirements and determines new low-latency traffic transmission requirements, that is, determines the new required communication channel resources for low-latency traffic transmission.

[0286] Step 1008: The station sends a fifth frame (LLIM-BA frame) to the access point. The fifth frame is used to indicate that the station accepts the communication channel resources provided by the access point for low-latency traffic transmission; or, the fifth frame is used to indicate at least one of the following: the station does not accept the communication channel resources provided by the access point for low-latency traffic transmission, and new communication channel resources for low-latency traffic transmission are required; the fifth frame has the same frame structure as the second frame.

[0287] Step 1009: The access point receives the fifth frame;

[0288] If the fifth frame indicates that the station accepts the communication channel resources provided by the access point for low-latency traffic transmission, then step 1010 is executed;

[0289] If the fifth frame indicates that the station does not accept at least one of the communication channel resources provided by the access point for low-latency traffic transmission and the new required communication channel resources for low-latency traffic transmission, the station and the access point continue to negotiate new communication channel resources for low-latency traffic transmission, i.e., jump to step 1006 to continue execution.

[0290] Step 1010: After passing through a short interframe space (SIFS), the access point sends an ACK frame back to the station.

[0291] Step 1011: The site receives the ACK frame and confirms that the access point agrees to the communication channel resources requested by the site for low-latency traffic transmission;

[0292] Step 1012: The site transmits low-latency traffic to the access point through one SIFS;

[0293] Step 1013: After receiving the low-latency traffic transmitted by the site, the access point sends back an ACK frame to the site after one SIFS.

[0294] Steps 1000 and 1001 are optional.

[0295] Steps 1006 to 1009 are the relevant steps when the access point cannot meet the low-latency traffic transmission requirements of the site due to factors such as limited communication channel resources.

[0296] Steps 1010 to 1013 are the steps by which the access point agrees to the site's application for communication channel resources, and the completion of step 1013 signifies the end of the low-latency traffic transmission process.

[0297] For an understanding of the above steps, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0298] The low-latency traffic indication method provided in this application embodiment may include the foregoing steps and at least one of the embodiments. For example, step 1000 may be implemented as a standalone embodiment, step 1001 may be implemented as a standalone embodiment, and so on...; the combination of step 1000 and step 1001 may be implemented as a standalone embodiment, the combination of steps 1000 to 1005 and steps 1010 to 1013 may be implemented as a standalone embodiment, and so on, but is not limited thereto.

[0299] The low-latency traffic indication method provided in this application includes a Low-Latency Indicator (LLI) identifier in the frame control field of the third frame. The station can proactively notify the access point of the arrival of low-latency traffic, enabling the network to instantly detect the occurrence of time-sensitive services. The access point sends a first frame (LLIICF frame) to the station to confirm the existence of low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the station for low-latency traffic transmission. Confirming the existence of low-latency traffic to be transmitted via the first frame avoids incorrect entry into low-latency traffic transmission communication channel resource negotiation due to decoding errors in the received third frame, thus improving reliability. Furthermore, the access point can also instruct the station to provide feedback on the required communication channel resources for low-latency traffic transmission via the first frame, providing a foundation for the low-latency traffic communication channel resource negotiation mechanism. The station can use the Resource Unit Allocation (RUAllocation) subfield, Maximum Latency subfield, Uplink Forward Error Correction Coding Type (UL FECCoding Type) subfield, and Uplink Ultra-High Reliability Modulation and Coding Scheme (UL) in the LLI information field of the second frame (LLI M-BA frame). The LLI element in the LLI M-BA frame is used to represent the communication channel resources required by the site for low-latency traffic transmission. This is achieved by using at least one of the following subfields: UHR-MCS, UL Target Receive Power, Time Granularity, and Data Volume. This allows the LLI element to not only identify the arrival of low-latency traffic but also declare the communication channel resources required for low-latency traffic transmission. Furthermore, the Maximum Latency subfield quantifies the urgency of low-latency traffic transmission, providing a foundation for subsequent low-latency traffic communication channel resource negotiation between the access point and the site. This application also provides a low-latency traffic communication channel resource negotiation mechanism. When the AP cannot meet the low-latency traffic transmission requirements due to resource limitations, this mechanism triggers a bidirectional degradation negotiation process via LLIICF. The access point and the site interact with the LLI M-BA frame via LLIICF, where the communication channel resources carried can be downgraded, thus realizing a bidirectional degradation negotiation process. This progressive negotiation model ensures that both parties can reach a feasible solution even under resource-constrained conditions, avoiding the risk of business interruption while guaranteeing the core requirement of low-latency transmission. This mechanism significantly improves business continuity in resource-constrained scenarios and enables the network to have elastic adaptability.

[0300] When multiple STAs (TXOP Responders) transmit low-latency traffic to the AP (TXOP Holder), the TXOP Holder needs to determine the order in which these low-latency traffic are processed. The TXOP Holder's traffic scheduling order must ensure that each low-latency traffic does not become outdated, and the TXOP Holder also needs to provide communication channel resources that meet the aforementioned low-latency traffic transmission requirements.

[0301] In the current TXOP, the AP (TXOP Holder) receives control response frames with LLI identifiers from M STAs (TXOP Responders). For each TXOP Responder, the TXOP Holder queries their needs via the first frame (LLIICF). Each TXOP Responder... m Each of the (m∈{1,2,...,M}) packets reported its maximum latency (t) to the TXOP Holder via the second frame (LLI M-BAFrame). m and data volume m .

[0302] In some embodiments, when the access point receives a third frame from M sites, after the access point receives a second frame from each site, the method further includes:

[0303] The access point determines the low-latency traffic reception order and the final communication channel resources to be used based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of each station.

[0304] The access point broadcasts a beacon frame, which carries the order of low-latency traffic reception and the communication channel resources to be used.

[0305] Where M is a positive integer greater than 1.

[0306] In order to successfully receive the low-latency traffic to be transmitted by the STA (TXOP Responder), the AP (TXOP Holder) first sorts the traffic according to the maximum transmission delay, data capacity, and traffic identifier (TID) priority to determine the receiving order of each low-latency traffic.

[0307] In some embodiments, the receiving order of each low-latency traffic is defined as follows:

[0308] (1) Let {r1,r2,...,r MThe order is based on the maximum time delay T = [t1, t2, ..., t]. M Rearrange from smallest to largest;

[0309] (2) In low-latency traffic with maximum latency, the data capacity d m The larger the value, the sooner the TXOP Holder receives the corresponding low-latency traffic;

[0310] (3) In data capacity d m Under the same conditions, the higher the TID of the low-latency traffic, the earlier the TXOP Holder receives the corresponding low-latency traffic; after the above sorting operation, the TXOP Holder determines the order in which to receive low-latency traffic as follows:

[0311] {r a(1) ,r a(2) ,...,r a(M)}

[0312] Where a(M) represents the sorted result order.

[0313] In this embodiment, based on the expiration time, data capacity, and TID priority of low-latency traffic represented by the Maximum Latency field of the LLI element, the AP (TXOP Holder) can establish a multi-dimensional service evaluation model. This model enables a dynamic priority classification method for the low-latency service requirements of multiple STAs (TXOP Responders) to determine the receiving order of low-latency service data for the TXOP Holder, thereby ensuring that all low-latency service data can be accurately received by the TXOP Holder. This dynamic priority classification method for low-latency traffic innovatively integrates service characteristics and network status, ensuring high-timeliness services while also considering overall network performance, guaranteeing that all low-latency service data receives transmission guarantees commensurate with its criticality level.

[0314] After the access point determines the order of receiving low-latency traffic, it determines the final communication channel resources to be used.

[0315] In some embodiments, the communication channel resources to be finally adopted are determined based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of each station, including at least one of the following:

[0316] Based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of each station, determine the minimum rate for receiving M low-latency traffic packets.

[0317] The final receive rate is determined based on the minimum rate of receiving M low-latency traffic streams; or,

[0318] Based on the receiving rate, the final modulation and demodulation scheme (MCS) and radio frequency resources to be adopted are determined.

[0319] Optionally, the access point determines the minimum rate R for receiving M low-latency traffic packets. min ,include:

[0320] After determining the order in which low-latency traffic is received, R min The formula must be satisfied:

[0321]

[0322] Here, max(a) represents the maximum value of all elements of vector a.

[0323] Understandably, the minimum rate R for low-latency traffic min M equations need to be satisfied; these M equations must satisfy the first constraint condition, namely: the data transmission time required to receive all low-latency traffic from the first m sites cannot exceed r. a(m) Maximal Latency a(m) ,

[0324] The constraint condition can be expressed as:

[0325]

[0326] Therefore, the minimum rate R of low-latency traffic min The above formula must be satisfied.

[0327] Optionally, the access point determines the minimum rate R for receiving M low-latency traffic streams. min Determine the final receiving rate R H ,include:

[0328] Final receiving rate R H Minimum rate R of low-latency traffic min The following formula applies between them:

[0329] R H =β2R min

[0330] For example, the multiplication factor β2 ∈ [1.5, 5].

[0331] The aforementioned final receiving rate R H Minimum rate R of low-latency traffic min The formulas between these factors take into account the overhead required for low transmission latency and the time-varying attenuation factors of the communication channel. The access point then determines the final receiving rate R. HThe final modulation and demodulation scheme (MCS) and radio frequency resources (RU) are determined. It is understood that other communication channel resources in the final adopted communication channel resources can be directly determined from the communication channel resources carried in the LLI information field of the second frame.

[0332] In this embodiment, the access point determines the final communication channel resources to be used based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of at least one station. Based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of each station, the minimum rate for receiving M low-latency traffic packets is determined; then, based on the minimum rate for receiving the M low-latency traffic packets, the final receiving rate is determined; and finally, based on the receiving rate, the final modulation and demodulation scheme (MCS) and radio frequency resources to be used are determined. This method for determining the final communication channel resources ensures that the access point can provide the communication channel resources required for low-latency traffic transmission carried in the second frame of each station.

[0333] After the access point determines the low-latency traffic reception order and the final communication channel resources to be used, the access point broadcasts a beacon frame, which carries the low-latency traffic reception order and the final communication channel resources to be used.

[0334] At this point, the AP (TXOP Holder) needs to report the determined communication channel resources to the STA (TXOP Responder). The TXOP Holder can temporarily use a beacon frame to broadcast the above parameters to M TXOP Responders. The LLI (Communication Resource Parameters) element is embedded in the Frame Body field of the Beacon Frame. Figure 12 This is a schematic diagram of the structure of an LLI-CommunicationResource Parameters Element provided in an embodiment of this application. For example... Figure 12 As shown, the LLI communication resource parameter elements include the Element ID field, the Length field, the Element ID Extension field, the User Info field, and the Communication Resource Parameters field.

[0335] In some embodiments, the beacon frame includes LLI communication resource parameter elements, which include:

[0336] The User Info field is used to indicate the order in which low-latency traffic is received;

[0337] The Communications Resource Parameters field indicates the communication channel resources ultimately used.

[0338] The user information field indicates the order in which the access point receives low-latency traffic; the communication resource parameter field indicates the communication channel resources ultimately used by the access point.

[0339] Optionally, the user information field includes M associated identifier traffic identifier information (AID TID Info) elements;

[0340] The associated identifier and traffic identifier information element includes the associated identifier (AID) subfield, the acknowledgment (ACK) type subfield, and the traffic identifier (TID) subfield.

[0341] Figure 13 This is a schematic diagram of the structure of a Communication Resource Parameters field provided in an embodiment of this application.

[0342] Optionally, the communication resource parameter fields include:

[0343] The Resource Unit Allocation (RU Allocation) subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0344] The Uplink Forward Error Correction Coding Type (UL FEC Coding Type) subfield is used to indicate the encoding method for low-latency traffic;

[0345] The Uplink Ultra-High Reliability Modulation and Coding Scheme (UL UHR-MCS) subfield indicates the modulation and coding scheme used to transmit low-latency traffic;

[0346] The UL Target Receive Power subfield indicates the signal reception power of the access point.

[0347] Each field in the above communication resource parameter fields represents the communication channel resources ultimately used by the access point.

[0348] For the various fields in the communication resource parameter field in this embodiment, you can refer to the relevant descriptions of the same subfields in the LLI Feedback element of the LLI information field of the second frame in the aforementioned embodiment, and the same technical effect can be achieved. For the same content, we will not repeat it here.

[0349] Optionally, after the access point broadcasts the beacon frame, the method further includes:

[0350] After the first interval, the access point sends buffer status reports to the corresponding stations one by one to poll the BSRP trigger frame according to the low-latency traffic reception order.

[0351] After receiving the first reply frame from the corresponding site, the access point receives the low-latency traffic transmitted by the corresponding site, and after receiving the low-latency traffic, after a first interval, sends a second reply frame to the corresponding site.

[0352] The access point processes low-latency traffic. After processing, it sends a buffer status report polling trigger frame to the next station until the low-latency traffic of M stations has been processed.

[0353] The first response frame is an ACK frame, and the second response frame is either an ACK frame or a BA frame.

[0354] After the AP (TXOP Holder) finishes transmitting the beacon frame carrying the LLI-Communications Resource Element, the information exchange process between the AP (TXOP Holder) and STA (TXOP Responder) is as follows:

[0355] (1) After one SIFS, the TXOP Holder sends a Buffer Status Report Poll Trigger Frame (BSRP Trigger Frame) to the corresponding TXOP Responder one by one according to the low-latency traffic reception order determined by the User Info field in the LLI communication resource parameter element.

[0356] (2) The TXOP Responder is in a silent state before receiving the BSRP Trigger Frame. After receiving the BSRPTrigger Frame, it sends an ACK Frame back to the TXOP Holder after one SIFS.

[0357] (3) After another SIFS, the TXOP Responder transmits low-latency traffic data frames to the TXOP Holder.

[0358] (4) After receiving the low-latency traffic data frame, the TXOP Holder sends an ACK Frame or BA Frame to the TXOP Responder after one SIFS. After receiving the ACK Frame or BA Frame, the TXOP Responder immediately re-enters the silent state after one SIFS.

[0359] (5) The TXOP Holder processes low-latency traffic information during transmission;

[0360] (6) The TXOP Holder sends a traditional BSRP Trigger Frame to the next TXOP Responder and returns to step (2).

[0361] Correspondingly, the method also includes at least one of the following:

[0362] The station receives beacon frames, which carry the order of low-latency traffic reception and the communication channel resources to be used.

[0363] The station receives a BSRP trigger frame from the access point's buffer status report polling, and after a first interval, sends a first reply frame to the access point.

[0364] After the first interval, low-latency traffic is transmitted to the access point; or,

[0365] The site receives a second response frame from the access point and enters a silent state after the first interval.

[0366] In this embodiment of the application, when multiple STAs (TXOP Responders) transmit low-latency traffic to the AP (TXOP Holder), the access point determines the low-latency traffic reception order and the final communication channel resources to be used based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of each station; the access point also broadcasts a beacon frame, wherein the beacon frame carries the low-latency traffic reception order and the final communication channel resources to be used;

[0367] Furthermore, the access point and the site transmit low-latency traffic. Under this mechanism, low-latency traffic transmission between the AP and multiple STAs is achieved.

[0368] The low-latency data transmission method provided in this application can be executed by a low-latency data transmission device. This application uses an example of a low-latency data transmission device executing the low-latency data transmission method to illustrate the low-latency data transmission device provided in this application.

[0369] This application provides a low-latency data transmission device. As an example, a low-latency data transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be an access point, a station, etc. Exemplarily, the access point may include, but is not limited to, the type of access point 110 listed above, and the station may include, but is not limited to, the type of station 120 listed above. This application does not impose specific limitations.

[0370] The low-latency data transmission device includes a transceiver module and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The transceiver module can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0371] Figure 14 This is one of the structural schematic diagrams of the low-latency data transmission device provided in the embodiments of this application. For details, see [link to specific diagram]. Figure 14 When the low-latency data transmission device is an access point device or a component in an access point device, the low-latency data transmission device 1400 includes a first transceiver module 1401.

[0372] The first transceiver module 1401 is used to send a first frame to the station. The first frame is used to confirm with the station whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the station for low-latency traffic transmission.

[0373] The first transceiver module 1401 is also used to receive a second frame from the station, the second frame carrying the communication channel resources required by the station for low-latency traffic transmission.

[0374] Optionally, the second frame may also include: a Low Latency Indicator (LLI) identifier, which is used to indicate a low latency transmission requirement.

[0375] Optionally, the first transceiver module 1401 is also used for:

[0376] Receive a third frame from the site. The third frame includes a Low Latency Indicator (LLI) identifier, which is used to indicate a low latency transmission requirement.

[0377] Optionally, the LLI identifier is located in the frame control field of the third frame. The frame control field includes a first subfield and a second subfield, which together serve as a low latency indicator identifier.

[0378] The first subfield is the "More Data" subfield, and the second subfield is the "Encryption Protection Frame" subfield.

[0379] Optionally, when both the More Data Subfield and the Encryption Protection Frame Subfield are set to 1, the More Data Subfield and the Encryption Protection Frame Subfield are used to indicate the arrival of low-latency traffic and trigger low-latency traffic communication channel resource negotiation.

[0380] Optionally, the third frame is a control response frame, which includes one of the following:

[0381] Acknowledge ACK frame;

[0382] Clear the sending of CTS frames;

[0383] Power-saving PS polling frames;

[0384] Block confirmation BA frame;

[0385] Multi-site block confirmation of M-BA frames.

[0386] Optionally, if the third frame is an M-BA frame, both the third and second frames are Low Latency Traffic Indication Multi-Site Block Acknowledgment (LLIM-BA) frames.

[0387] Optionally, the LLIM-BA frame includes an LLI information field;

[0388] The LLI information field is used to indicate at least one of the following:

[0389] Is there low-latency traffic to be transmitted?

[0390] Whether to accept the communication channel resources provided by the access point for low-latency traffic transmission; or,

[0391] The communication channel resources required by the site for low-latency traffic transmission.

[0392] Optionally, the LLI information field includes an LLI feedback element, which includes at least one of the following:

[0393] The low-latency response subfield is used to indicate whether low-latency traffic exists or to provide feedback to the access point on whether to accept the communication channel resources provided by the access point for low-latency traffic transmission.

[0394] The resource unit allocation subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0395] The maximum delay subfield indicates the maximum allowed delay for transmitting low-latency traffic;

[0396] The data capacity subfield indicates the size of the data storage space for low-latency traffic;

[0397] The time granularity subfield is used to indicate the length of the time step;

[0398] The uplink forward error correction coding type subfield is used to indicate the coding method for low-latency traffic;

[0399] The uplink ultra-high reliability modulation and coding scheme subfield indicates the modulation and coding scheme required for transmitting low-latency traffic; or,

[0400] The uplink target received power subfield is used to indicate the signal received power of the access point.

[0401] Optionally, the first frame is a low-latency indication initial control frame (LLIICF frame).

[0402] The first frame includes a first ultra-high reliability low latency indication user information field, which includes a low latency indication request subfield.

[0403] The Low Latency Indication Request subfield is used for at least one of the following:

[0404] Confirm that the site has low-latency traffic to be transmitted; or,

[0405] Instructs the site to provide feedback on the communication channel resources required for low-latency traffic transmission.

[0406] Optionally, the first transceiver module 1401 is also used for:

[0407] The access point sends a first acknowledgment frame back to the site. The first acknowledgment frame is used to indicate the communication channel resources for low-latency traffic transmission.

[0408] Access points receive low-latency traffic based on communication channel resources;

[0409] After receiving the low-latency traffic transmitted by the site, the access point sends a second acknowledgment frame back to the site.

[0410] Optionally, the apparatus further includes: a first processing module, configured to determine the low-latency traffic reception order and the final communication channel resources to be used based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of each station;

[0411] The first transceiver module 1401 is also used to broadcast beacon frames, which carry the low-latency traffic reception order and the communication channel resources ultimately used.

[0412] Where M is a positive integer greater than 1.

[0413] Optionally, the first processing module is used to perform at least one of the following:

[0414] Based on the communication channel resources required by each station for low-latency traffic transmission carried in the second frame of each station, determine the minimum rate for receiving M low-latency traffic packets.

[0415] The final receiving rate is determined based on the minimum rate at which M low-latency traffic streams are received.

[0416] Based on the receiving rate, the final modulation and demodulation scheme (MCS) and radio frequency resources to be adopted are determined.

[0417] Optionally, the beacon frame includes LLI communication resource parameter elements, which include at least one of the following:

[0418] The user information field is used to indicate the order in which low-latency traffic is received; or...

[0419] The communication resource parameter field indicates the communication channel resources ultimately used.

[0420] Optionally, the user information field includes M associated identifier traffic identifier information elements;

[0421] The associated identifier and traffic identifier information elements include: associated identifier subfield, acknowledgment type subfield, and traffic identifier subfield.

[0422] Optionally, the communication resource parameter field includes at least one of the following:

[0423] The resource unit allocation subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0424] The uplink forward error correction coding type subfield is used to indicate the coding method for low-latency traffic;

[0425] The uplink ultra-high reliability modulation and coding scheme subfield indicates the modulation and coding scheme used for transmitting low-latency traffic; or,

[0426] The uplink target received power subfield is used to indicate the signal received power of the access point.

[0427] Optionally, the first transceiver module 1401 is also used for:

[0428] After the first interval, according to the low-latency traffic reception order, buffer status reports are sent to the corresponding stations one by one to poll the BSRP trigger frames.

[0429] After receiving the first reply frame from the corresponding site, the system receives the low-latency traffic transmitted by the corresponding site, and after receiving the low-latency traffic and after a first interval, sends the second reply frame to the corresponding site.

[0430] The first processing module is also used to process low-latency traffic. After processing is completed, the first transceiver module 1401 is also used to send a buffer status report polling trigger frame to the next station until the processing of low-latency traffic of M stations is completed.

[0431] The low-latency data transmission device provided in this application embodiment can achieve... Figure 4 The method for transmitting low-latency data includes at least one step in the embodiments and at least one of the embodiments, and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0432] Figure 15 This is a second schematic diagram of the low-latency data transmission device provided in this application embodiment. For details, see [link to specific diagram]. Figure 15 When the low-latency data transmission device is a site device or a component in a site device, the low-latency data transmission device 1500 includes a second transceiver module 1501.

[0433] The second transceiver module 1501 is used to receive a first frame from the access point. The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission.

[0434] The second transceiver module 1501 is also used to send a second frame to the access point, the second frame carrying the communication channel resources required by the site for low-latency traffic transmission.

[0435] Optionally, the second frame may also include: a Low Latency Indicator (LLI) identifier, which is used to indicate a low latency transmission requirement.

[0436] Optionally, the second transceiver module 1501 is also used for:

[0437] When a site detects the arrival of low-latency traffic, the site sends a third frame to the access point. The third frame includes a Low Latency Indicator (LLI) identifier, which is used to indicate a low-latency transmission request.

[0438] Optionally, the LLI identifier is located in the frame control field of the third frame. The frame control field includes a first subfield and a second subfield, which together serve as a low latency indicator identifier.

[0439] The first subfield is the "More Data" subfield, and the second subfield is the "Encryption Protection Frame" subfield.

[0440] Optionally, when both the More Data Subfield and the Encryption Protection Frame Subfield are set to 1, the More Data Subfield and the Encryption Protection Frame Subfield are used to indicate the arrival of low-latency traffic and trigger low-latency traffic communication channel resource negotiation.

[0441] Optionally, the third frame is a control response frame, and the third frame includes one of the following:

[0442] Acknowledge ACK frame;

[0443] Clear the sending of CTS frames;

[0444] Power-saving PS polling frames;

[0445] Block confirmation BA frame;

[0446] Multi-site block confirmation of M-BA frames.

[0447] Optionally, if the third frame is an M-BA frame, both the third and second frames are Low Latency Traffic Indication Multi-Site Block Acknowledgment (LLIM-BA) frames.

[0448] Optionally, the LLIM-BA frame includes an LLI information field;

[0449] The LLI information field is used to indicate at least one of the following:

[0450] Is there low-latency traffic to be transmitted?

[0451] Whether to accept the communication channel resources provided by the access point for low-latency traffic transmission; or,

[0452] The communication channel resources required by the site for low-latency traffic transmission.

[0453] Optionally, the LLI information field includes an LLI feedback element, which includes at least one of the following:

[0454] The low-latency response subfield is used to indicate whether low-latency traffic exists or to provide feedback to the access point on whether to accept the communication channel resources provided by the access point for low-latency traffic transmission.

[0455] The resource unit allocation subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0456] The maximum delay subfield indicates the maximum allowed delay for transmitting low-latency traffic;

[0457] The data capacity subfield indicates the size of the data storage space for low-latency traffic;

[0458] The time granularity subfield is used to indicate the length of the time step;

[0459] The uplink forward error correction coding type subfield is used to indicate the coding method for low-latency traffic;

[0460] The uplink ultra-high reliability modulation and coding scheme subfield indicates the modulation and coding scheme required for transmitting low-latency traffic; or,

[0461] The uplink target received power subfield is used to indicate the signal received power of the access point.

[0462] Optionally, the device further includes:

[0463] The second processing module 1502 is used to determine the required communication channel resources for low-latency traffic transmission.

[0464] Optionally, the second processing module 1502 is used to perform at least one of the following:

[0465] Obtain the data storage space size, priority, and urgency level of low-latency traffic;

[0466] Based on the urgency of the low-latency traffic, determine the maximum allowable delay for transmitting the low-latency traffic and the encoding method for the low-latency traffic;

[0467] Based on the data storage space size of the low-latency traffic and the maximum allowable latency for transmitting the low-latency traffic, determine the minimum rate required to transmit the low-latency traffic, and then determine the actual transmission rate based on the minimum rate; or,

[0468] Based on the actual transmission rate, determine the modulation and coding scheme used for transmitting low-latency traffic, as well as the radio frequency resources required for transmitting low-latency traffic.

[0469] Optionally, the first frame is a low-latency indication initial control frame (LLIICF frame).

[0470] The first frame includes a first ultra-high reliability low latency indication user information field, which includes a low latency indication request subfield.

[0471] The Low Latency Indication Request subfield is used for at least one of the following:

[0472] Confirm that the site has low-latency traffic to be transmitted; or,

[0473] Instructs the site to provide feedback on the communication channel resources required for low-latency traffic transmission.

[0474] Optionally, the second transceiver module 1501 is also configured to perform at least one of the following:

[0475] The station receives a first acknowledgment frame from the access point, which is used to indicate the communication channel resources for low-latency traffic transmission;

[0476] After the first interval, the site transmits low-latency traffic to the access point;

[0477] The station receives a second acknowledgment frame from the access point; or, the station receives a fourth frame from the access point, the fourth frame being used to negotiate new communication channel resources for low-latency traffic transmission.

[0478] Optionally, the fourth frame is an LLIICF frame, which includes a second ultra-high reliability low latency indicator user information field. This second ultra-high reliability low latency indicator user information field is used to indicate at least one of the following:

[0479] The site cannot provide the communication channel resources required for low-latency traffic transmission; or,

[0480] Communication channel resources available for sites to transmit low-latency traffic.

[0481] Optionally, the second ultra-high reliability low latency indicator user information field includes at least one of the following:

[0482] The resource unit allocation subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0483] The maximum delay subfield is a binary code indicating the longest delay allowed for transmitting low-latency traffic.

[0484] The uplink forward error correction coding type subfield is used to indicate the coding method for low-latency traffic;

[0485] The uplink ultra-high reliability modulation and coding scheme subfield indicates the modulation and coding scheme used for transmitting low-latency traffic; or,

[0486] The uplink target received power subfield is used to indicate the signal received power of the access point.

[0487] Optionally, the second transceiver module 1501 is also configured to perform at least one of the following:

[0488] Send a fifth frame to the access point. The fifth frame is used to indicate at least one of the following: whether the site accepts the communication channel resources provided by the access point for low-latency traffic transmission, and the new required communication channel resources for low-latency traffic transmission. The fifth frame is an LLI M-BA frame and has the same frame structure as the second frame.

[0489] The station receives a third acknowledgment frame from the access point; after a first interval, the station transmits low-latency traffic to the access point; the station receives a fourth acknowledgment frame; or...

[0490] The system receives a fourth frame sent by the access point to continue negotiating new communication channel resources for low-latency traffic transmission.

[0491] Optionally, the second transceiver module 1501 is also configured to perform at least one of the following:

[0492] Receive beacon frames, which carry the order of low-latency traffic reception and the final communication channel resources used;

[0493] Receive the buffer status report polling BSRP trigger frame from the access point, and after the first interval, send the first reply frame to the access point;

[0494] After the first interval, low-latency traffic is transmitted to the access point; or,

[0495] After receiving the second reply frame from the access point and entering a silent state after the first interval, the system receives the second reply frame from the access point.

[0496] Optionally, the beacon frame includes LLI communication resource parameter elements, which include at least one of the following:

[0497] The user information field is used to indicate the order in which low-latency traffic is received; or...

[0498] The communication resource parameter field indicates the communication channel resources ultimately used.

[0499] Optionally, the user information field includes M associated identifier traffic identifier information elements;

[0500] The associated identifier and traffic identifier information element includes the associated identifier subfield, the acknowledgment type subfield, and the traffic identifier subfield.

[0501] Optionally, the communication resource parameter field includes at least one of the following:

[0502] The resource unit allocation subfield is used to indicate the radio frequency resources required for transmitting low-latency traffic;

[0503] The uplink forward error correction coding type subfield is used to indicate the coding method for low-latency traffic;

[0504] The uplink ultra-high reliability modulation and coding scheme subfield indicates the modulation and coding scheme used for transmitting low-latency traffic; or,

[0505] The uplink target received power subfield is used to indicate the signal received power of the access point.

[0506] The low-latency data transmission device provided in this application embodiment can achieve... Figure 4 The method for transmitting low-latency data includes at least one step in the embodiments and at least one of the embodiments, and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0507] Figure 16 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 16 As shown, this application embodiment also provides a communication device 1600, including a processor 1601 and a memory 1602. The memory 1602 stores a program or instructions that can run on the processor 1601. For example, when the communication device 1600 is an access point, the program or instructions, when executed by the processor 1601, implement the various steps of the communication method embodiment on the access point side described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here. For example, when the communication device 1600 is a station, the program or instructions, when executed by the processor 1601, implement the various steps of the communication method embodiment on the station side described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0508] In some embodiments, the communication device 1600 may further include a transceiver, and the processor 1601 may control the transceiver to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0509] The transceiver may include a transmitter and a receiver. The transceiver may further include antennas, which may be one or more.

[0510] This application embodiment also provides an access point, including a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement, for example... Figure 4 or Figure 10 The corresponding steps in the low-latency data transmission method embodiment are shown. This access point embodiment corresponds to the above-described access point-side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this access point embodiment and achieve the same technical effect. The access point can be... Figure 14 The device shown is a low-latency data transmission device.

[0511] This application embodiment also provides a station, including a processor and a communication interface, the communication interface and the processor being coupled, the processor being used to run programs or instructions to implement, for example... Figure 4 or Figure 10 The corresponding steps in the low-latency data transmission method embodiment are shown. This site embodiment corresponds to the above-described site-side method embodiment; all implementation processes and methods of the above-described method embodiments can be applied to this site embodiment and achieve the same technical effect. The site can be... Figure 15 The device shown is a low-latency data transmission device.

[0512] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0513] The processor is either the processor in the access point or the processor in the site in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0514] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0515] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0516] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0517] This application also provides a communication system, including an access point and a station. The access point can be used to execute the steps of the above-described communication method, and the station can also be used to execute the steps of the above-described communication method. The communication system implements the various processes of the above-described communication method embodiments and achieves the same technical effects; therefore, to avoid repetition, it will not be described again here.

[0518] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0519] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause a terminal or network-side device to execute the methods of the various embodiments of this application.

[0520] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for transmitting low-latency data, characterized in that, include: The access point sends a first frame to the site. The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission. The access point receives a second frame from the site, the second frame carrying the communication channel resources required by the site for low-latency traffic transmission.

2. The method according to claim 1, characterized in that, The second frame also includes: a Low Latency Indicator (LLI) identifier, which is used to indicate a low latency transmission requirement.

3. The method according to claim 1 or 2, characterized in that, Before the access point sends the first frame to the station, it also includes: The access point receives a third frame from the site, the third frame including a Low Latency Indicator (LLI) identifier, the LLI identifier being used to indicate a low latency transmission requirement.

4. The method according to claim 3, characterized in that, The LLI identifier is located in the frame control field of the third frame. The frame control field includes a first subfield and a second subfield, which together serve as the low latency indicator identifier. The first subfield is the "More Data" subfield, and the second subfield is the "Encryption Protection Frame" subfield.

5. The method according to any one of claims 3-4, characterized in that, The third frame is a control response frame, which includes one of the following: Acknowledge ACK frame; Clear the sending of CTS frames; Power-saving PS polling frames; Block confirmation BA frame; Multi-site block confirmation of M-BA frames.

6. The method according to claim 5, characterized in that, In the case that the third frame belongs to the M-BA frame, both the third frame and the second frame are Low Latency Traffic Indication Multi-Site Block Acknowledgment (LLIM-BA) frames.

7. The method according to claim 6, characterized in that, The LLIM-BA frame includes an LLI information field; The LLI information field is used to indicate at least one of the following: Is there low-latency traffic to be transmitted? Whether to accept the communication channel resources provided by the access point for low-latency traffic transmission; or, The site requires communication channel resources for low-latency traffic transmission.

8. The method according to claim 7, characterized in that, The LLI information field includes an LLI feedback element, which includes at least one of the following: The low-latency response subfield is used to indicate whether low-latency traffic exists or to provide feedback to the access point on whether to accept the communication channel resources provided by the access point for low-latency traffic transmission. The resource unit allocation subfield is used to indicate the radio frequency resources required to transmit the low-latency traffic; The maximum delay subfield is used to indicate the maximum allowed delay for transmitting the low-latency traffic; The data capacity subfield indicates the size of the data storage space for the low-latency traffic; The time granularity subfield is used to indicate the length of the time step; The uplink forward error correction coding type subfield is used to indicate the coding method of the low-latency traffic; The uplink ultra-high reliability modulation and coding scheme subfield is used to indicate the modulation and coding scheme required for transmitting the low-latency traffic; or, The uplink target received power subfield is used to indicate the signal received power of the access point.

9. The method according to any one of claims 1-8, characterized in that, The first frame is a Low Latency Indication Initial Control Frame (LLIICF) frame; The first frame includes a first ultra-high reliability low latency indication user information field, which includes a low latency indication request subfield. The low latency indication request subfield is used for at least one of the following: Confirm whether the site has low-latency traffic to be transmitted; or, The system instructs the station to provide feedback on the communication channel resources required for low-latency traffic transmission.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: The access point sends a first confirmation frame back to the station, the first confirmation frame being used to indicate the communication channel resources for the low-latency traffic transmission; The access point receives low-latency traffic based on the communication channel resources; After receiving the low-latency traffic transmitted by the site, the access point sends a second confirmation frame back to the site.

11. The method according to any one of claims 1 to 10, characterized in that, If the access point receives a third frame from M of the stations, after the access point receives a second frame from each of the stations, the method further includes: The access point determines the low-latency traffic reception order and the final communication channel resources to be used based on the communication channel resources required by each of the stations for low-latency traffic transmission carried in the second frame of each station. The access point broadcasts a beacon frame, which carries the low-latency traffic reception order and the final communication channel resources used. Where M is a positive integer greater than 1.

12. The method according to claim 11, characterized in that, The step of determining the final communication channel resources to be used based on the communication channel resources required by each of the stations for low-latency traffic transmission carried in the second frame of each station includes at least one of the following: Based on the communication channel resources required by each of the stations for low-latency traffic transmission carried in the second frame of each station, determine the minimum rate for receiving M low-latency traffic streams. The final receiving rate is determined based on the minimum rate of receiving M low-latency traffic streams; or, Based on the received rate, the final modulation and demodulation scheme (MCS) and radio frequency resources to be adopted are determined.

13. The method according to claim 11 or 12, characterized in that, The beacon frame includes LLI communication resource parameter elements, which include at least one of the following: A user information field is used to indicate the order in which the low-latency traffic is received; or... The communication resource parameter field is used to indicate the communication channel resources ultimately adopted.

14. The method according to claim 13, characterized in that, The user information field includes M associated identifier traffic identifier information elements; The associated identifier traffic identifier information element includes: associated identifier subfield, confirmation type subfield, and traffic identifier subfield.

15. The method according to claim 13, characterized in that, The communication resource parameter field includes at least one of the following: The resource unit allocation subfield is used to indicate the radio frequency resources required to transmit the low-latency traffic; The uplink forward error correction coding type subfield is used to indicate the coding method of the low-latency traffic; The uplink ultra-high reliability modulation and coding scheme subfield is used to indicate the modulation and coding scheme used to transmit the low-latency traffic; or, The uplink target received power subfield is used to indicate the signal received power of the access point.

16. The method according to any one of claims 11-15, characterized in that, After the access point broadcasts the beacon frame, the method further includes: After the first interval, the access point sends a buffer status report polling BSRP trigger frame to the corresponding station one by one according to the low latency traffic reception order. After receiving the first reply frame from the corresponding site, the access point receives the low-latency traffic transmitted by the corresponding site, and after receiving the low-latency traffic, sends a second reply frame to the corresponding site after a first interval. The access point processes the low-latency traffic, and after processing, sends a buffer status report polling trigger frame to the next station until the low-latency traffic of the M stations has been processed.

17. A method for transmitting low-latency data, characterized in that, include: The station receives a first frame from the access point, the first frame being used to confirm with the station whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the station for low-latency traffic transmission; The station sends a second frame to the access point, the second frame carrying the communication channel resources required by the station for low-latency traffic transmission.

18. The method according to claim 17, characterized in that, The second frame also includes: a Low Latency Indicator (LLI) identifier, which is used to indicate a low latency transmission requirement.

19. The method according to claim 17 or 18, characterized in that, Before the station receives the first frame from the access point, the method further includes: When a site detects the arrival of low-latency traffic, the site sends a third frame to the access point. The third frame includes a Low Latency Indicator (LLI) identifier, which is used to indicate a low-latency transmission request.

20. A low-latency data transmission device, characterized in that, include: The first transceiver module is used to send a first frame to the station. The first frame is used to confirm with the station whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the station for low-latency traffic transmission. The first transceiver module is further configured to receive a second frame from the site, the second frame carrying communication channel resources required by the site for low-latency traffic transmission.

21. A low-latency data transmission device, characterized in that, include: The second transceiver module is used to receive a first frame from the access point. The first frame is used to confirm with the site whether there is low-latency traffic to be transmitted and / or to obtain the communication channel resources required by the site for low-latency traffic transmission. The second transceiver module is further configured to send a second frame to the access point, the second frame carrying the communication channel resources required by the site for low-latency traffic transmission.

22. A communication device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the low-latency data transmission method as described in any one of claims 1 to 16, or to implement the steps of the low-latency data transmission method as described in any one of claims 17 to 19.

23. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the low-latency data transmission method as described in any one of claims 1 to 16, or implement the steps of the low-latency data transmission method as described in any one of claims 17 to 19.

Images