Low-latency service transmission method, access point device and storage medium

Abstract

Embodiments of the present invention relate to the field of wireless communication technology and disclose a low-latency service transmission method, access point device, and storage medium. In the present invention, when each access point device in a multi-AP collaborative transmission mechanism has a low-latency service to be transmitted in itself or its associated site device, it notifies each access point device in the multi-AP collaborative set as a low-latency service holder. Upon receiving a notification from a low-latency service holder, it provides low-latency service transmission assistance to the low-latency service holder. Through collaborative transmission among the access points, the characteristics of multi-AP collaboration and low-latency services are fully integrated, achieving efficient and stable transmission of low-latency services in a wireless network.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of wireless communication technology, and in particular to a low-latency service transmission method, access point device, and storage medium. Background Art

[0002] Wi-Fi standards have consistently improved peak network speeds and capacity. However, in high-density scenarios such as airports, hotels, stadiums, and multi-residential apartment buildings, previous Wi-Fi standards have been unable to guarantee stable and low-latency performance. Emerging applications such as telemedicine, virtual reality (VR), online / multiplayer gaming, industrial control, logistics, robotics, and stereo / multi-speaker audio all place stringent requirements on network latency, requiring the network to transmit large amounts of data in real time and with predictable performance. Furthermore, many IoT applications require networks to support massive numbers of connected devices. These low-latency services require the network to transmit data in record time to ensure a smooth and real-time user experience. Excessive network latency can cause users to experience issues such as screen freezes, intermittent audio, and operational malfunctions, impacting normal service operations.

[0003] Wi-Fi 7 also proposes the R-TWT (Restricted-Target wake time) mechanism, which protects and prioritizes low-latency traffic by allocating R-TWT SP (Service Period) and overlapping quiet intervals. R-TWT enables the BSS to use enhanced medium access protection and resource reservation to provide more reliable predictable delays for delay-sensitive services on wireless links. The next generation of Wi-Fi technology, Wi-Fi 8, aims to provide ultra-high reliability (UHR: Ultra High Reliability) wireless communications. It is further developed based on IEEE 802.11be (i.e. Wi-Fi 7) to meet the stringent requirements of emerging applications such as Industry 4.0, Industrial Internet of Things, autonomous driving, and telemedicine. These applications require the network to be able to transmit large amounts of data with extremely low latency and extremely high reliability to ensure security and efficiency.

[0004] Wi-Fi 8, the next-generation Wi-Fi technology, prioritizes ultra-high data reliability. One of the key UHR challenges is reducing the tail of the latency distribution and jitter, essentially reducing the maximum value and fluctuation range of network transmission latency. Therefore, improving the reliability of low-latency service transmission is both a core research topic for Wi-Fi 8 and a current technological gap in this field. Summary of the Invention

[0005] The purpose of the embodiments of the present invention is to provide a low-latency service transmission method, access point device and storage medium, which combines the characteristics and advantages of multi-AP collaboration technology and the actual needs of current low-latency service processing, fully integrates the characteristics of multi-AP collaboration and low-latency services, and realizes efficient and stable transmission of low-latency services in wireless networks.

[0006] To solve the above technical problems, an embodiment of the present invention provides a low-latency service transmission method, including: when there is a low-latency service to be transmitted in itself or its associated site device, it notifies each access point device in the multi-AP collaborative set as a low-latency service holder; when receiving a notification from the low-latency service holder, it provides low-latency service transmission assistance to the low-latency service holder.

[0007] An embodiment of the present invention also provides an access point device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the above-mentioned low-latency service transmission method.

[0008] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned low-latency service transmission method when executed by a processor.

[0009] In an embodiment of the present invention, when each access point device in the multi-AP collaborative transmission mechanism has a low-latency service to be transmitted in itself or its associated site device, it notifies each access point device in the multi-AP collaborative set as a low-latency service holder; when receiving a notification from a low-latency service holder, it provides low-latency service transmission assistance to the low-latency service holder, and through collaborative transmission of each access point, efficient and stable transmission of low-latency services in the wireless network is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] One or more embodiments are exemplarily illustrated by pictures in the corresponding drawings. These exemplifications do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements. Unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0011] Figure 1 This is a flow chart of a low-latency service transmission method provided according to an embodiment of the present invention;

[0012] Figure 2 2 is a schematic diagram of processing a low-latency service to be transmitted in a polling manner according to an embodiment of the present invention;

[0013] Figure 3 2 is a schematic diagram of processing a low-latency service to be transmitted in a multi-user manner provided by an embodiment of the present invention;

[0014] Figure 4 is a schematic diagram of multi-AP collaborative beamforming according to an embodiment of the present invention;

[0015] Figure 5 FIG. 4 is a structural diagram of an access point device according to another embodiment of the present invention. DETAILED DESCRIPTION

[0016] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, each embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be understood by those skilled in the art that in each embodiment of the present invention, many technical details are provided to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in this application can be implemented. The division of the following embodiments is for convenience of description and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined with each other and referenced to each other under the premise that there is no contradiction.

[0017] One embodiment of the present invention relates to a low-latency service transmission method that can be applied to any access point device in a multi-AP collaborative transmission mechanism. In this embodiment, when there is a low-latency service to be transmitted in itself or its associated site device, each access point device in the multi-AP collaborative transmission mechanism notifies each access point device in the multi-AP collaborative transmission mechanism as a low-latency service holder; when receiving a notification from the low-latency service holder, it provides low-latency service transmission assistance to the low-latency service holder. It fully integrates the characteristics of multi-AP collaboration and low-latency services, and realizes efficient and stable transmission of low-latency services in wireless networks. The implementation details of the low-latency service transmission method of this embodiment are described in detail below. The following content is only the implementation details provided for the convenience of understanding and is not necessary for the implementation of this solution.

[0018] like Figure 1 As shown, in step 101, when there is a low-latency service to be transmitted in itself or its associated site device, it notifies each access point device in the multi-AP cooperation set (Multi-AP set) as a low-latency service holder;

[0019] Multi-AP coordination is a technology introduced to meet the needs of low-latency services and improve throughput. Similar to this, Wi-Fi protocols have also introduced new technologies and features, such as Orthogonal Frequency Division Multiple Access (OFDMA) and Multi-User Multiple Input Multiple Output (MU-MIMO). Multi-AP coordination, which utilizes coordinated transmission between multiple access points, can improve network performance in multi-AP environments, reduce interference and conflicts, and enhance coverage and quality. In this mechanism, when an AP and its associated STAs require low-latency service transmission, a timely reporting mechanism notifies other relevant APs for intelligent coordination and avoidance, significantly enhancing the reliability of low-latency service transmission. Wi-Fi 8 introduces multi-AP coordination, aiming to improve the performance of the entire wireless network system by enhancing collaboration between APs. This technology not only strengthens the interoperability between access points but also improves the throughput of the entire wireless network through refined resource scheduling and system optimization. Therefore, the introduction of multi-AP collaboration technology in Wi-Fi 8 provides strong support for the stability and reliability of low-latency service transmission. Combining the characteristics and advantages of multi-AP collaboration with the current practical needs of low-latency service processing, this paper proposes a new transmission solution. This solution fully integrates the characteristics of multi-AP collaboration and low-latency services. Through intelligent spectrum allocation, efficient routing planning, and refined traffic scheduling, it achieves efficient and stable transmission of low-latency services on wireless networks.

[0020] In the framework of the multi-AP cooperative transmission mechanism (Multi-AP Coordination), it can be divided into multiple steps, namely: exchange relevant information between APs that support multi-AP cooperation (Multi-AP discovery); reach a consensus between APs that support multi-AP cooperation (Coordinated Agreement) and form a multi-AP set (Multi-AP set, also known as Multi-AP group); there will be a cooperative access point device (Coordinator AP, or Master AP) in the Multi-AP set, which is used to coordinate the coordination work between the entire Multi-AP. Usually, Coordinator AP is the AP that initiates the establishment of the Multi-AP set; other participating APs in the Multi-AP set are called coordinated access point devices (CoordinatedAP, also known as Slave AP); some preparatory work before the multi-AP cooperative transmission is turned on (Pre-transmission), such as some configuration operations such as coordinated beamforming and joint transmission; multi-AP coordinated transmission (Multi-AP Coordinated Transmission) is initiated by a Sharing AP.

[0021] After reaching a consensus among multiple APs to form a Multi-AP set, the AP that successfully obtains the transmission opportunity (TXOP) and starts the multi-AP coordination operation is called the transmission opportunity holder (Sharing AP). It is the coordinator of the entire multi-AP transmission and is responsible for managing and controlling the transmission process. The other APs in the Multi-AP set are called transmission coordinators (Shared AP). These APs are coordinated by the transmission opportunity holder (Sharing AP) and actually participate in the multi-AP transmission. They are responsible for completing the data transmission task under the guidance of the Sharing AP.

[0022] In step 102, upon receiving a notification from a low-latency service holder, providing low-latency service transmission assistance to the low-latency service holder;

[0023] In one example, providing low-latency service transmission assistance to low-latency service holders may include one or any combination of the following: providing transmission opportunities for low-latency service holders, adjusting the working configuration of each access point device related to the low-latency service through coordinated spatial multiplexing, providing beam coverage or beam nulling operations to low-latency service holders based on priority or priority through coordinated beamforming, etc. There are various ways to provide low-latency service transmission assistance to low-latency service holders, for example, when competing for transmission opportunities with various access point devices in the same multi-AP collaborative transmission mechanism, providing low-latency service holders with competition priority that is beneficial for obtaining transmission opportunities in the competition, etc. These methods can all be considered as providing assistance to low-latency service holders. The following will illustrate each of these methods with examples.

[0024] As a low-latency service holder, if it is also a transmission opportunity holder, the following examples illustrate how to coordinate the various access point devices in the multi-AP collaborative transmission mechanism to provide low-latency service transmission assistance to itself:

[0025] In some cases, if the Sharing AP or its associated STA has low-latency services to transmit, the current TXOP holder (i.e., the Sharing AP) will prioritize allocating TXOPs to the STA or AP with low-latency services. After the low-latency services are transmitted, the Sharing AP will evaluate whether to allocate the remaining TXOPs (if any) to other devices.

[0026] In one example, the transmission opportunity holder can notify each transmission coordinator by sending a broadcast message. In some cases, to coordinate transmission needs within the network, Sharing APs can broadcast low-latency service indications to related APs, typically those belonging to the same Multi-AP Set. Through this broadcast, the Sharing AP notifies other APs that it currently has low-latency services to transmit. The related APs can then decide whether to avoid transmission to prioritize the low-latency services based on their own circumstances.

[0027] In some cases, the low-latency service indication may also carry another instruction, that is, notifying the relevant APs that the Sharing AP has stopped the function of sharing the TXOP with the OBSS AP.

[0028] In some cases, the broadcast frame may be a beacon frame, a probe response frame, or other control frame, management frame, or data frame used to transmit broadcast information between multiple APs. The indication of the low-latency service may be defined in the frame body of the beacon frame, probe response frame, or other control frame, management frame, or data frame.

[0029] In some cases, Sharing AP can be Coordinator AP or Coordinated AP. Optionally, when Sharing AP is Coordinated AP, it can send a notification to Coordinator AP that it has low-latency services to be transmitted, so that Coordinator AP can coordinate the work within the entire Multi-AP Set. Coordinator AP can send some assistance information or coordination information to Sharing AP.

[0030] In one example, providing low-latency service transmission assistance to the low-latency service holder may include providing the low-latency service holder with competitive priority that facilitates obtaining the transmission opportunity when competing for a transmission opportunity with the access point devices also in the multi-AP coordination set. Specifically, in certain situations, when APs with multi-AP coordination capabilities form a Multi-AP set, if an AP has low-latency services to transmit, the backoff strategy should allow that AP to obtain priority transmission opportunities. In other words, the AP with low-latency services to process should be given priority to obtain TXOPs and become a Sharing AP. After the low-latency service transmission is completed, the decision to share the remaining TXOPs with other APs will be considered based on the actual situation. Regarding how to give priority to TXOP for low-latency services, for example, the low-latency services may be assigned to the highest-priority access category (AC, full name Access Category, such as AC_VO) or a new AC may be defined with a shorter arbitration inter-frame spacing (AIFS, full name Arbitration Inter-Frame Spacing), a smaller contention window, and a longer TXOP to ensure priority transmission of low-latency services.

[0031] When the access point device acts as a transmission coordinator, and when there is a low-latency service to be transmitted in itself or its associated site device, examples are given for providing transmission opportunities for the low-latency service holder. The examples here can be divided into three categories. The first category is that the transmission opportunity holder uses polling to provide transmission opportunities, that is, as a transmission opportunity holder and after receiving a polling feedback frame in response to the low-latency service polling frame issued by the low-latency service holder in accordance with the polling form, when there is no low-latency service to be transmitted in itself or its associated site device, the transmission opportunity held by itself is allocated to the low-latency service holder; the second category is that the transmission opportunity holder uses a multi-user inquiry form to trigger the provision of transmission opportunities, that is, as a transmission opportunity holder The first type is to provide transmission opportunities through active reporting by the low-latency service holder, that is, as the transmission opportunity holder, and after receiving the inquiry feedback frame in response to the low-latency service inquiry frame sent by the low-latency service holder in the form of multi-user inquiry, when there is no low-latency service to be transmitted in itself or its associated site equipment, the transmission opportunity held by itself is allocated to the low-latency service holder. The following will give detailed examples and further explanations of these three categories of examples.

[0032] Regarding the first type of transmission opportunity provision method, that is, the transmission opportunity holder uses polling to provide transmission opportunities. In some cases, if the Shared AP or its associated STA has low-latency services to be transmitted, it can report the indication of the low-latency service to the Sharing AP to request a transmission opportunity. The Sharing AP can poll the AP in the Multi-AP set whether there is a low-latency service to be transmitted; at this time, the transmission opportunity is obtained by responding to the low-latency service query frame issued by the transmission opportunity holder, which can be: obtaining a transmission opportunity by responding to the low-latency service query frame issued by the transmission opportunity holder according to the preset polling mechanism;

[0033] Regarding the time point at which a Sharing AP starts sharing TXOPs with other APs, the following example is given:

[0034] 1. Immediately after obtaining TXOP, the polling mechanism is started. If there is a shared AP with a low-latency service to be sent, the TXOP is shared with the low-latency service first;

[0035] 2. After the Sharing AP completes its original transmission, if there are any remaining TXOPs, the polling mechanism is started.

[0036] In one example, when acting as a transmission coordinator and after receiving a low-latency service polling frame sent by a transmission opportunity holder according to a preset polling mechanism, if there is no low-latency service to be transmitted in itself or its associated site device, it does not respond to the low-latency service polling frame within a preset time, or sends a feedback frame corresponding to the low-latency service polling frame to the transmission opportunity holder to notify the transmission opportunity holder;

[0037] In some cases, the Sharing AP polls the APs in the group to see if there is any low-latency service to be transmitted. Figure 2 As shown: First, the Sharing AP (AP1) polls the APs (AP2 and AP3) in the Multi-AP Set in turn, that is, it sends polling frames (LL Poll) to the relevant APs one by one, asking whether they have low-latency services to be sent. After receiving the LL-Poll polling frame, the Shared AP sends a feedback frame (Feedback frame) to the Sharing AP after an interval of xIFS (a time interval). If the feedback is not received within the specified time, it means that the Shared AP has no low-latency services to be sent, or the Shared AP can also carry information that does not include low-latency services to be transmitted in the feedback frame. After obtaining the feedback information from the Shared AP, the Sharing AP decides which AP to share the TXOP with. If there are multiple Shared APs with low-latency services to be sent, the Sharing AP will decide the right to use the TXOP based on factors such as the urgency of the low-latency service, the volume of the service, the priority, and the time limit for sending the timeout, and send the relevant information to the relevant AP through the Trigger Frame. The Trigger frame should also include the duration of the TXOP that the Shared AP can use. If multiple Shared APs are allowed to use the TXOP, it should also include the order of use of the TXOP and the duration of use of each TXOP. The AP that obtains the right to use the TXOP uses the TXOP for the transmission of low-latency services after receiving the Trigger frame sent by the Sharing AP. After the low-latency service transmission is completed, or after the TXOP usage duration indicated in the Trigger frame is reached, the Shared AP sends an LL End frame to the Sharing AP to indicate that the low-latency service transmission is completed and return the right to use the TXOP. It should be noted that the time interval between frames. If Figure 2The xIFS shown in the figure may be RIFS (Reduced Interframe Space), SIFS (Short Interframe Space), or PIFS (PCF Interframe Space).

[0038] In some cases, a Sharing AP can be either a Coordinator AP or a Coordinated AP. If a Sharing AP is a Coordinated AP, it should prioritize sending LL Poll frames to the Coordinator AP to inquire whether it has any low-latency services to be transmitted during polling. If the Coordinator AP has relevant coordination instructions, it can also carry relevant instructions in the Feedback frame. Similarly, the polling order of Sharing APs can be affected by various factors. For example, when a Multi-AP set is established, a priority is set for the Coordinated AP, and polling is performed in descending order based on priority. In some cases, the polling order can also be defined based on the frequency of transmitting low-latency services or urgent services. That is, the Sharing AP or Coordinator AP side records the number of low-latency service transmissions by the APs in the Multi-AP Set, and prioritizes polling the AP with the highest number of low-latency service transmissions to see if it has any low-latency services to be processed. If the number of low-latency service transmissions is the same, the polling order is randomized.

[0039] The above process involves a low-latency service polling frame issued according to a preset polling mechanism and a feedback frame corresponding to the low-latency service polling frame. The following is a detailed example of these two frames:

[0040] First, for low-latency service polling frames issued according to the preset polling mechanism, the following three types can be used as examples:

[0041] Type A: The low-latency service polling frame issued according to the preset polling mechanism is a trigger frame (Trigger Frame) carrying a polling low-latency service indication, for example: BSRP (Buffer Status Report Poll, Buffer Status Report Poll) frame (Frame) and the like.

[0042] Among them, the polling low-latency service indication is used to indicate to the transmission coordinator whether the frame carrying the polling low-latency service indication is a low-latency service inquiry frame issued according to the preset polling mechanism, that is, the polling low-latency service indication is an identifier used to indicate whether the frame carrying the polling low-latency service indication is a low-latency service polling frame.

[0043] In view of the different ways of carrying the polling low-latency service indication, two trigger frames with different structures are given as examples:

[0044] The first structure type can carry information about polling low-latency services in trigger frames in related technologies, such as BSRP, BQRP (Bandwidth Query Report Polling), Initial Control Frame (ICF), Beamforming Report Poll (BFRP), or Null Data Physical Layer Protocol Data Unit Feedback Report Poll (NFRP), as shown in Table 1 below:

[0045]

[0046] Compared to related technical solutions, this structure defines bit B63 in the Common Infofield of the Trigger Frame as the Low-Latency Service Indication Subfield (LL Poll subfield). The Low-Latency Service Polling Frame (LL-Poll) is an indication of polling for low-latency service. When LL Poll = 1, it indicates that the trigger frame also contains an indication to inquire whether there is any low-latency service to be transmitted. When LL Poll = 0, the function of inquiring about low-latency service is not enabled. In some cases, the LL Poll subfield can also be included in the Trigger Dependent Common Info subfield in the Common Info field.

[0047] The second structure type defines a new trigger frame type for polling low-latency services. An LL-Poll indication is added to the Trigger Type Subfield in the Common Info field of the Trigger frame. The specific value can be one of the reserved fields (i.e., 8 to 15 bits) in the related art. For example, in Table 2 below, a value of 8 indicates LL-Poll. The format of this Trigger frame can reuse the existing Buffer Status Report Poll frame (BSRP frame) or Poll frame, maintaining consistency with its structure.

[0048]

[0049] Type B: The low-latency service polling frame issued according to the preset polling mechanism is a control frame (Control frame) that carries a polling low-latency service indication, such as a Block ACK request frame (BlockAckReq Frame), a Request To Send (RTS) frame, a Clear To Send (CTS) frame, etc.

[0050] In view of the different ways of carrying the polling low-latency service indication, two control frames with different structures are given as examples:

[0051] The first structure type: In some cases, it is also possible to add an indication of polling low-latency services to the existing BlackAckReq frame. For example, an LL-Poll indication can be added to the BAR Control field of the BlockAckReq frame. As shown in Table 3 below, the LL Poll indication can be added to bit B0 of the base address register control field (BAR Control field). Alternatively, any bit between B5 and B11 can be selected to indicate LL Poll information.

[0052]

[0053] The second structure type: The base address register type field (BAR Type field) carries LL Poll information, as shown in Table 4 below:

[0054]

[0055] Among them, when the BAR Type value is 1, it indicates LL Poll information. Similarly, other values can also be used, such as 4-5, 7-9, and 11-15. In addition to the BlockAckReq frame, the LL Poll information can also be configured in the FrameControl field of the Control frame. In this case, in addition to conveying the original information, the frame also contains information asking whether there is a low-latency service to be transmitted. In some cases, a new type of control frame can be defined, which is specifically used to poll low-latency services. Its structure can reuse the existing polling frame structure, where the Subtype value in the Frame control field needs to define a new value, which can be one of the existing Reserved bits, such as 0000, 0001, or 1111. In some cases, the LL Poll frame type can also be added to the Extension frame, for example, the Type field in its Frame control field is 11, and the Subtype field is one of 0010-1111.

[0056] Type C: The low-latency service polling frame issued according to the preset polling mechanism is a data frame (Data frame) that carries a polling low-latency service indication, such as: start polling cache frame (CF-poll frame), quality of service data frame (Qos Data), quality of service empty frame (Qos null), etc.

[0057] In some cases, it is also possible to add indication information for polling low-latency services to existing CF-poll, Qos Data, and Qos null frames, such as adding an LL-Poll indication to Frame Control. Alternatively, a new type of data frame can be defined specifically for polling low-latency services. Its structure can reuse the existing data frame structure, where the Subtype value in the Frame control field needs to be defined with a new value, which can be one of the existing Reserved bits, such as 0101, 0110, 0111, 1101, etc.

[0058] In addition, it should be noted that the Random Access (RA) field of all the above types of LL-Poll frames should be configured with the Media Access Control (MAC) address of the Shared AP to be queried.

[0059] The following briefly describes the feedback frame corresponding to the low-latency service polling frame, i.e., the polling feedback frame, with several different structural forms:

[0060] In one example, the polling feedback frame and the low-latency service polling frame are of the same type of frame, that is, after receiving the polling frame, the Shared AP can feedback a same frame to indicate that it has a low-latency service to be sent;

[0061] In an example, a regular feedback frame may be replied, such as an acknowledgment character (ACK frame), a buffer status report frame (BSR frame) (corresponding to BSRP), a transmission confirmation frame (BA frame), a clear-to-send frame (CTS frame), a start polling confirmation frame (CF-ACK frame), an ICR frame, a QoS data frame, a QoS Null frame, etc., to indicate that a low-latency service is to be sent.

[0062] In one example, the polling feedback frame carries relevant information about the low-latency service to be processed, that is, it can be information about the low-latency service added to the existing regular frame. While feeding back the information that it has low-latency service to be sent, the feedback frame can optionally also carry other information about the low-latency service, such as the urgency of the low-latency service, the maximum waiting time or the latest sending time of the low-latency service, the business volume of the low-latency service, etc. That is, the relevant information about the low-latency service to be processed includes one of the following or any combination thereof: the urgency of the low-latency service to be processed, the maximum waiting time of the low-latency service to be processed, the latest sending time of the low-latency service to be processed, and the business volume of the low-latency service to be processed.

[0063] Specifically, corresponding to the polling frame, the feedback frame can also have the following three situations:

[0064] Type A: For example, a feedback frame belonging to the trigger frame type such as BSR. If the LL Poll frame is sent in the form of a trigger frame such as BSRP frame, ICF, BFRP (Beamforming Report Poll), or NFRP (NDP feedback Report Poll), its feedback frame can be a feedback frame in the form of a BSR frame, ACK, or Initial Control Response frame (ICR, full name Initial Control Response).

[0065] First, for the BSR frame, the Shared AP can carry information about low-latency services in the BSR frame, for example, in the AP PS Buffer State subfiled in the Qos Control field of the BSR frame, add an LL poll indication. LL poll is used to indicate the low-latency service mode. When LL poll is configured to 1, it means that the current BSR frame is used to indicate cache information related to low-latency services. When LL poll is configured to 0, it means that the current AP has no low-latency services to be sent. The structure of the Buffer State subfield of the access point (AP) in power save mode in the Qos Control field (the Buffer State subfield of the access point in power save mode is referred to as AP PSBuffer State subfiled) is as follows

[0066] As shown in Table 5:

[0067]

[0068] Type B: Control frame type, for example: a frame confirming the successful reception of a data block (BA), etc. In some cases, the feedback frame of the LL Poll frame can be a control frame such as BA, RTS, or CTS. Taking the BA frame as an example, when the Shared AP receives the LL Poll frame sent by the Sharing AP, it can reply with a BA frame to indicate that it has low-latency services to be transmitted. In some cases, the BA frame can also carry information about low-latency services. For example, as shown in Table 6 below, an indication of low-latency services can be added to the BA Control field in the Frame control field of the BAframe, such as the B0 bit in Table 6 indicating an indication of low-latency services. In some cases, 1 bit from B5 to B8 can also be used to indicate notification of low-latency services.

[0069]

[0070]

[0071] In some cases, an indication of a low-latency service may be added to the frame control field of other control frames to inform the Sharing AP that it has a low-latency service to be sent.

[0072] Type C: Data frame type, such as CF-ACK frame, Qos Data frame, or Qos null frame. In some cases, after receiving an LL Poll frame from a Sharing AP, a Shared AP can reply with a CF-ACK frame, Qos Data frame, or Qos null frame to indicate that it has pending low-latency services. It can also notify the Sharing AP of pending low-latency services by adding a low-latency service indication to the frame control field of the data frame.

[0073] In addition, it should be noted that the RA field of all the above-mentioned feedback frames should be configured with the MAC address of the Sharing AP.

[0074] The relationship between LL poll and feedback frames described above can be one-to-one, that is, if the LL poll frame is type A, the corresponding feedback frame is type A. It can also be any combination, that is, if the LL poll frame is type A, its feedback frame can also be type B or other types.

[0075] In one example, when acting as a transmission coordinator and obtaining a transmission opportunity, the transmission opportunity is returned to the transmission opportunity holder when the low-latency service to be transmitted is completed. That is, when a Shared AP with a low-latency service to be transmitted completes the transmission of the low-latency service, the Shared AP can send a low-latency service end frame (LL End frame) to the Sharing AP to notify it that the low-latency service transmission is completed and the TXOP is returned. The LL End frame can be a common feedback frame, such as an ACK frame, CF-ACK frame, BA frame, etc., or it can be a CF-end, Qos Data, Qos null, etc. frame. The RA field of the LL End frame should be configured with the MAC address of the Sharing AP. In some cases, the Sharing AP can also indicate the TXOP length that can be used by the Shared AP in the Trigger frame, that is, the Shared AP needs to return the TXOP after the indicated time period expires. In this case, there is no need to send back an LL End frame to notify the Sharing AP to return the TXOP.

[0076] When an access point device acts as a transmission coordinator to obtain a transmission opportunity, generally, three different processing methods can be exemplified. The first method has been exemplified above. Regarding the second method of providing transmission opportunities, the second method is for the transmission opportunity holder to trigger the provision of transmission opportunities using a multi-user query format. When, as a transmission opportunity holder, after receiving a query feedback frame in response to a low-latency service query frame issued by itself using a multi-user query format by a low-latency service holder, and the low-latency service to be transmitted does not exist on itself or its associated site devices, the transmission opportunity held by itself is allocated to the low-latency service holder.

[0077] In the second processing mode, the Sharing AP may multiplex the uplink multi-user physical protocol data unit (UL MU PPDU). In one example, Figure 3 As shown, Sharing AP sends a Trigger frame to the relevant APs (AP2 and AP3) in the Multi-AP set, triggering them to feedback information about low-latency services. After an interval of xIFS time, the relevant AP sends a feedback frame carrying low-latency service information to Sharing AP. After receiving the feedback frame, Sharing AP decides which AP to share the TXOP with. If there are multiple Shared APs with low-latency services to be sent, Sharing AP decides the right to use the TXOP based on factors such as the urgency of the low-latency services and the size of the services, and sends the relevant information to the relevant APs through TriggerFrame. The Trigger frame should also include information such as the duration of the TXOP that the Shared AP can use. AP that obtains the right to use the TXOP ( Figure 3 AP3) in the middle, after receiving the Trigger frame sent by the Sharing AP, uses TXOP for the transmission of low-latency services.

[0078] In one example, when acting as a transmission coordinator and, after obtaining a transmission opportunity, completing the transmission of the pending low-latency service, the transmission opportunity is returned to the transmission opportunity holder. After the low-latency service is transmitted, or after the TXOP usage duration indicated in the Trigger frame has expired, the Shared AP sends an LL End frame to the Sharing AP to indicate the completion of the low-latency service transmission and to return the TXOP usage rights.

[0079] Among them, the low-latency service inquiry frame is a trigger frame. The user common list field of the low-latency service inquiry frame carries the access point information of each non-transmission opportunity holder in the multi-AP cooperative transmission mechanism, and the RA field of the delayed service inquiry frame carries broadcast address information; or, the low-latency service inquiry frame is an MU-related frame generated using multi-user technology;

[0080] The MU-related frame belongs to one of the following: a MU-RTS frame, a MU-BAR frame, or a GCR MU-BAR frame; the inquiry feedback frame and the low-latency service inquiry frame are the same type of frame; or the inquiry feedback frame is a CTS frame.

[0081] Among them, the time interval between frames, such as Figure 3 As shown in , xIFS can be RIFS (Reduced Interframe Space), SIFS (Short Interframe Space), or PIFS (PCF Interframe Space). The format of the Trigger frame sent by the Sharing AP can reuse the Trigger frame introduced in the first type of processing method, or it can be a MU-RTS frame, MU-BAR, GCR MU-BAR frame, or other MU-related frames. It should be noted that the User Info List field of the Trigger frame should be the information of the Shared AP in the Multi-APset, and the MU-RTS / CTS frame exchange mechanism should be applied between multiple APs, as shown below. Figure 3 AP2 and AP3 in the Multi-APset. And the available recursion field (RA field, RA stands for Recursion Available) should be a broadcast address (Broadcast address). The Feedback frame sent by the Shared AP can reuse the feedback frame format in the first type of processing method, which will not be described in detail here. The LL End frame fed back by the AP that has obtained TXOP and has low-latency services to send can reuse the LL End frame format in the first type of processing method. In addition, when the Sharing AP receives indication information about low-latency services from other APs in the Multi-APset, it sends a Trigger frame to inform the relevant APs (which can be all Shared APs or one or more related Shared APs) of the next operation to be performed. The function of the Trigger frame can reuse the function and format of the Trigger frame in the first type of processing method.

[0082] When an access point device acts as a transmission coordinator to obtain a transmission opportunity, generally speaking, there are three different processing methods. The examples of the first and second categories have been completed above. Next, the third category is that the transmission coordinator actively reports the current low-latency service arrival status to the transmission opportunity holder. That is, as a transmission opportunity holder and after receiving the low-latency service arrival frame actively reported by the low-latency service holder, when there is no low-latency service to be transmitted in itself or its associated site devices, it allocates its own transmission opportunity to the low-latency service holder. In some cases, when a Shared AP has low-latency service to be processed, it can also notify the relevant APs that it has low-latency service to be processed by actively reporting itself, waiting for the Sharing AP to coordinate with other APs and allocate TXOPs to them.

[0083] Specifically, the third type of processing can be summarized into two forms:

[0084] 1. Shared AP only reports notifications of pending low-latency services to Sharing AP, which then decides how to coordinate APs and allocate TXOPs.

[0085] 2. APs in the Multi-AP Set send notifications of low-latency services to each other. APs can avoid low-latency services based on their own transmission conditions. Optionally, Sharing APs can also coordinate the entire system and send an indication frame to notify each AP to coordinate.

[0086] The time node for sending low-latency service notifications can be as follows:

[0087] 1. In the early stage of establishing a Multi-AP Set, the APs in the Set can send some of the AP's own configuration information, including notifications of whether there are low-latency services to be processed, to the relevant APs in the Set.

[0088] 2. The Sharing AP sends a Trigger frame, which includes an indication of a time period. During this time period, if the AP in the Multi-AP Set has low-latency services to be transmitted, it reports the notification of low-latency services. The reporting method can be to report only to the Sharing AP or to send it to the group within the Multi-AP Set.

[0089] 3. During the signaling interaction between a Sharing AP and a Shared AP with a low-latency service to be sent, the Shared AP can also carry information about the low-latency service when transmitting a frame to the Sharing AP to notify it that a low-latency service is to be sent. After receiving the indication of the low-latency service, the Sharing AP determines whether to prioritize allocating TXOP to the low-latency service and triggers the transmission of the low-latency service through a Trigger frame.

[0090] The frame type transmitted between the Sharing AP and the Shared AP can be an indication frame for reporting low-latency service notification by the station device (i.e., STA, also known as terminal or terminal device) in the existing low-latency service transmission, i.e., LowLatency Indication. The indication frame can be a control frame, a management frame, or a data frame, or a frame type introduced in the first type of processing method.

[0091] In some cases, the Sharing AP in this embodiment can be either a Coordinator AP or a Coordinated AP. Similarly, the Shared AP can be either a Coordinator AP or a Coordinated AP.

[0092] In some cases, when the Sharing AP is a Coordinated AP, it can send a notification that it has low-latency services to be transmitted to the Coordinator AP, so that the Coordinator AP can coordinate the work within the entire Multi-AP Set. The Coordinator AP can send some assistance information or coordination information to the Sharing AP.

[0093] In some cases, when multiple Shared APs have pending low-latency services and request a TXOP, SharingAP can determine which AP to prioritize for TXOP allocation based on factors such as the urgency of the low-latency services, the remaining timeout period, and the priority level. If time constraints permit, SharingAPs can send the order of Shared APs obtaining TXOPs in the Trigger frame (Trigger for LL). APs with pending low-latency services can use the TXOP in that order. When the low-latency services to be transmitted have the same urgency, remaining timeout period, and priority level, SharingAPs can independently determine the TXOP allocation or randomly select an AP for allocation. This strategy can be applied in any of the above three ways, that is, when serving as a transmission opportunity holder and after receiving polling feedback frames responded by multiple low-latency service holders, there is no low-latency service to be transmitted in itself or its associated site equipment, then the order of use and duration of the transmission opportunities held by itself are allocated to each low-latency service holder according to the relevant information of the low-latency service to be processed in each polling feedback frame; or, when serving as a transmission opportunity holder and after receiving query feedback frames responded by multiple low-latency service holders, in itself or its associated site equipment When there is no low-latency service to be transmitted, the order of use and duration of the transmission opportunities held by itself are allocated to each low-latency service holder based on the relevant information of the low-latency service to be processed in each inquiry feedback frame; or, when serving as a transmission opportunity holder and after receiving low-latency service arrival frames actively reported by multiple low-latency service holders, when there is no low-latency service to be transmitted in itself or its associated site equipment, the order of use and duration of the transmission opportunities held by itself are allocated to each low-latency service holder based on the relevant information of the low-latency service to be processed in the low-latency service arrival frame.

[0094] In certain situations, when wired communication links are established between APs, signaling transmission between them is no longer constrained by the competition mechanisms of traditional wireless channels, eliminating the need to compete for limited wireless resources. Instead, based on stable and reliable wired transmission technology, APs can exchange data and signaling directly and without conflict. This shift significantly improves the flexibility and efficiency of multi-AP coordination, enabling smoother network management and faster and more accurate policy execution. With the support of wired communication, multi-AP systems can more effectively share information and coordinate resource scheduling, further improving overall network performance.

[0095] In an example, when there is a wired communication link between the access point devices in a multi-AP cooperative set, as a low-latency service holder, each access point device in the multi-AP cooperative set is notified, waiting for an instruction issued by a cooperative access point device in the multi-AP cooperative set or a transmission opportunity holder in the multi-AP cooperative set. When wired communication can be established between APs, at least when wired transmission is possible between APs in the Multi-AP Set, the access point device (LL AP for short) with low-latency services to be transmitted can coordinate by sending a low-latency service indication to the relevant AP to ensure the transmission of low-latency services. The following will illustrate it with three examples:

[0096] Solution 1: The LL AP sends a low-latency service indication to the Sharing AP, requesting it to allocate a TXOP for low-latency service transmission. The Sharing AP then provides feedback on the TXOP allocation to the relevant APs.

[0097] a) Sharing AP's TXOP allocation needs to be sent to LL AP. The structure of this indication frame can reuse the Trigger frame design in the first or second processing method above.

[0098] b) The low-latency service indication sent by the LL AP can reuse the low-latency service reporting design in the third processing method above;

[0099] c) Optional, Sharing AP on TXOP allocation, need to be sent to the Coordinator AP, so that the Coordinator AP on the Multi-AP Set of AP unified deployment to adapt to the transmission of low-latency services. If the current Sharing AP is the Coordinator AP, there is no need to repeat this operation.

[0100] d) If the LL AP is a Sharing AP, use the solution in c) and report only to the Coordinator AP.

[0101] Solution 2: The LL AP sends a low-latency service indication to the Coordinator AP, which then coordinates the transmission of the low-latency service. The Coordinator AP then sends the indication information to related APs to coordinate the transmission of the low-latency service.

[0102] a) The low-latency service indication frame sent by the LL AP can reuse the low-latency service reporting design in the third processing method above;

[0103] b) The Coordinator AP shall send an allocation indication to the Sharing AP and LL AP, and optionally to other APs in the Multi-AP set. The indication frame shall reuse the design of the Triggerframe in the first or second processing method above.

[0104] c) An LL AP can be either a Coordinator AP or a Coordinated AP. If the LL AP is a Coordinator AP, it can directly send an instruction to the Sharing AP to apply for TXOP use.

[0105] Solution 3: Before competing for TXOPs, the LL AP can send a low-latency service indication to the Coordinator AP, which then allocates TXOPs to the LL AP. This means that the LL AP can directly obtain the TXOP and become a Sharing AP. Specifically:

[0106] a) The low-latency service indication frame sent by the LL AP can reuse the low-latency service reporting design in the third processing method above;

[0107] b) The Coordinator AP should send an allocation indication to the LL AP and all APs in the other Multi-AP Set, notifying them that the current TXOP has been occupied by the LL AP and asking other APs to give way. The form of the indication frame reuses the design of the Trigger frame in the first or second type of processing above.

[0108] The above mainly gives an example of providing low-latency service transmission assistance to low-latency service holders, which is to provide transmission opportunities to low-latency service holders when receiving a notification from the low-latency service holders. In fact, there are far more ways to provide low-latency service transmission assistance to low-latency service holders.

[0109] In one example, when the Sharing AP receives the indication information about the low-latency service from other APs in the Multi-AP set, it sends a Trigger frame to inform the relevant APs (which can be all Shared APs or one or more related Shared APs) of the operation to be performed next. The operation can be at least one of the following or a free combination thereof:

[0110] Notify the relevant APs of their right to use the subsequent TXOPs, optionally carrying information such as the TXOP duration and resource allocation;

[0111] Notify related APs to preempt, stop the services currently being transmitted using the TXOP, and start transmitting low-latency services. If multiple APs have low-latency services to process, the Sharing AP allows the AP with higher priority or more urgency to preempt based on factors such as the urgency of the low-latency service, the volume of the service, the priority, and the data timeout limit.

[0112] Notify relevant APs to modify their current operating modes, such as capability mode or operating mode, operating mode, number of working antennas, MCS configuration, NSS configuration, transmit power, etc.

[0113] Notify relevant APs to adjust spatial reuse or other multi-AP operations, such as coordinated-spatial reuse, coordinated beam forming, and joint transmission, to adapt to configuration updates related to low-latency service transmission.

[0114] In one example, for coordinated spatial reuse between multiple APs, that is, adjusting the working configuration of each access point device related to the low-latency service through coordinated spatial reuse, it can be: when receiving a notification from the low-latency service holder, as a transmission opportunity holder, configure a higher transmission power for each low-latency service holder in the multi-AP collaborative transmission mechanism, select the most suitable MCS configuration and working mode.

[0115] Sharing APs can configure higher transmission power, or appropriate MCS, operating mode, and other configurations for low-latency services, enabling them to transmit low-latency services with the optimal operating configuration without interfering with other devices. Accordingly, Sharing APs can also configure other Shared APs (APs without pending low-latency services) to use lower transmission power (this can be a pre-configured power threshold designed for low-latency services. Upon identifying an AP in a Multi-AP Set with pending low-latency services, an AP without pending low-latency services will control its transmission power within this pre-set power threshold. This threshold can be determined by communication between APs within the Set during Multi-AP Set establishment, notified by Sharing APs, or included in a PHY capability element, MAC capability element, or pre-configured buffer on the device) and a lower operating mode to reduce interference with devices with low-latency services. If multiple APs have pending low-latency services, Sharing APs will allocate resources to APs with higher priority or more urgency based on factors such as the urgency of the low-latency services, traffic volume, priority, and data timeout period, and adjust the allocation of these APs.

[0116] In one example, for coordinated beamforming between multiple APs, Beamforming (abbreviated as C-BF, or coordinated beamforming, or coordinated beamforming) is to provide beam coverage or beam nulling operation for low-latency service holders according to priority or priority through coordinated beamforming. It can be: adjusting the beam coverage of each access point device working in a multi-AP cooperative set through coordinated beamforming to ensure that the signal coverage of the access point device of the non-low-latency service holder avoids the site device receiving the low-latency service of the low-latency service holder through beam nulling operation without generating a low-latency service priority conflict, while ensuring that the beam coverage of the access point device of the low-latency service holder covers the site device receiving the low-latency service; or, ensuring that the beam coverage of the access point device holding the low-priority low-latency service avoids the site device receiving the low-latency service of the high-priority low-latency service holder through beam nulling operation, while ensuring that the beam coverage of the access point device holding the high-priority low-latency service holder covers the site device receiving the low-latency service; wherein the priority refers to the priority between low-latency services, or refers to the priority between low-latency services and non-low-latency services. Beam coverage refers to covering a specific device through beamforming. Beam nulling refers to setting the beamforming weight in a direction to zero, thereby avoiding a specific device in that direction. Beam coverage can also be called beamforming coverage, beamforming coverage, or simply coverage, or simply beamforming or beamforming. Beam coverage and beam nulling are two operations in collaborative beamforming.

[0117] In some cases, at least one AP participating in collaborative beamforming decides to cover certain terminals or avoid (nulling) certain terminals (or access points) based on whether the terminals (STAs) or access points involved in C-BF have low-latency services or the priority of low-latency services. If it is not possible to simultaneously cover a terminal and avoid another terminal during C-BF, then one of the two conflicting terminals is discarded or retained based on whether the terminal has low-latency services or the priority of the low-latency services of each terminal. Only one of the conflicting terminals is covered during C-BF, or only the other terminal is avoided during C-BF.

[0118] In some cases, if a terminal needs to be covered and a neighboring terminal needs to be avoided at the same time, it cannot be completed at the same time. The reason is that the two terminals are too close to each other, and the beamforming cannot null (avoid) a terminal at the same time during beamforming, and cannot achieve such fine control. Or, from the perspective of AP2 that is doing beamforming, the two terminals are almost together and cannot be physically distinguished. For example, Figure 4STA11 associated with AP1 and STA22 associated with AP2 conflict. AP2 cannot guarantee coverage for STA22 while avoiding STA11. If there is no LL transmission to STA22, but LL is provided to STA21, or low latency is provided to STA11, AP2 guarantees coverage for STA21 while avoiding STA11. STA22 is not considered during C-BF.

[0119] In some cases, whether the AP or terminal has LL service, the priority corresponding to the low-latency service, or the service type corresponding to the low-latency service is included in the initial control frame (ICF frame) or initial response frame (ICR frame), or the channel measurement result reporting frame when performing C-BF. In some cases, a bit 0 indicates no LL service, and a bit 1 indicates the presence of low-latency service. The initial control frame (ICF frame) or initial response frame (ICR frame) is used to transmit C-BF-related information, negotiate C-BF, form an AP pair, or perform C-BF on an AP group.

[0120] In some cases, C-BF can be performed at the expense of STA22 (by ignoring STA22's transmission or delaying STA22's transmission by devices that are more advanced than C-BF). This allows STA21 to be bypassed, avoiding STA11. When this decision is made, AP2 must notify it via ICF / ICR. When AP2 performs C-BF, STA11 should notify AP2 as soon as possible after completing its transmission, for example by sending an ACK, which is received by both AP1 and AP2. This allows AP2 to resume STA22's transmission as quickly as possible.

[0121] In some cases, AP1 and AP2 need to perform C-BF, with terminal STA1 associated with AP1 and terminal STA22 associated with AP2. When performing C-BF, AP2 considers multiple surrounding devices (STA11, STA21, and STA23). STA22 is associated with AP3, and determines whether to avoid the terminal by determining whether AP3 has low-latency services to transmit to STA3.

[0122] The capability mode is described in detail below. Capability mode (also known as operating mode) is a parameter that reflects the operating capabilities of a STA (including APs and non-AP STAs). It is divided into multiple levels, each of which includes several key elements. Different levels represent different STA operating capabilities, with higher levels indicating greater transmission capabilities.

[0123] The Capability Mode includes at least one of the following elements: operating mode, number of operating antennas (number of antennas used for transmission and / or number of antennas used for reception), channel bandwidth, NSS (Number of Spatial Streams, supported number of receive spatial streams and / or supported number of transmit spatial streams), MCS (Modulation and Coding Scheme), coding method, code rate, support for multi-RU scheduling, data rate, PPDU format (Physical Protocol Data Unit), and packet size, all of which are important factors affecting network performance. Optionally, DRU (Dynamic Resource Unit)-related parameters are also an important part of the Capability Mode. They determine whether the network device supports DRU functions and the supported DRU modes and features (including DRU granularity, bandwidth, size, bandwidth that can be scheduled for use, whether it can coexist with rRU (regular RU), pilot (reference signal) density and number, and whether pilots are shared with rRUs). Optionally, parameters related to seamless roaming, secondary channel access (or non-primary channel access), and multi-AP coordination are also optional parameters in the Capability Mode, for example, whether seamless roaming is supported, whether secondary channel access is supported, the granularity of secondary channel access, bandwidth, number of temporary primary channels, secondary channel access type (TXOP duration and / or EDCA parameters), and other secondary channel access related parameters. Optionally, in some cases, the Capability Mode also includes parameters related to multi-link devices, specifically, the number of links of the multi-link device, such as link ID, STA ID, MLD ID, or a combination thereof. In some cases, the Capability Mode may also include a multiple link element, or a basic multiple link element, or a newly defined multilink element, to indicate whether the relevant link is enabled / enabled or not. In some cases, the multilink element is used to indicate the connection status of the current terminal and its associated first multi-connection device. In some cases, the multilink element is used to indicate the connection status of the current terminal and a second multi-connection device other than the first multi-connection device associated with it. Optionally, whether to support downlink MU-MIMO is also an optional parameter in Capability Mode.Optionally, the Capability mode should also include: Maximum PPDU duration, maximum MCS, whether to use Low Density Parity Check Code (LDPC), whether to use the immediate block acknowledgment mechanism (HT-immediate BlockAck), disabled subchannel bitmap, etc.

[0124] In this embodiment, when each access point device in the multi-AP collaborative transmission mechanism has a low-latency service to be transmitted in itself or its associated site device, it will notify each access point device in the multi-AP collaborative set as a low-latency service holder. When receiving a notification from a low-latency service holder, it provides low-latency service transmission assistance to the low-latency service holder. For example, it provides transmission opportunities for the low-latency service holder, adjusts the working configuration of each access point device related to the low-latency service through coordinated spatial multiplexing, and provides beam coverage or beam nulling operations for the low-latency service holder through coordinated beamforming. Through the collaborative transmission of each access point, efficient and stable transmission of low-latency services in the wireless network is achieved. The characteristics of multi-AP collaboration and low-latency services are fully integrated to achieve efficient and stable transmission of low-latency services in the wireless network.

[0125] The steps of the above method are divided only for the purpose of clear description. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this application; adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are all within the scope of protection of this application.

[0126] Another embodiment of the present invention relates to an access point device, such as Figure 5 As shown, it includes at least one processor 501; and a memory 502 that is communicatively connected to the at least one processor; wherein the memory 502 stores instructions that can be executed by the at least one processor 501, and the instructions are executed by the at least one processor 501 so that the at least one processor 501 can execute the low-latency service transmission method as described above.

[0127] The memory 502 and processor 501 are connected using a bus. The bus can include any number of interconnected buses and bridges, connecting various circuits of one or more processors 501 and memory 502. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits. These are all well known in the art and are therefore not described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be a single component or multiple components, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by the processor 501 is transmitted over a wireless medium via an antenna. Furthermore, the antenna receives data and transmits it to the processor 501.

[0128] The processor 501 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 502 can be used to store data used by the processor 501 when performing operations.

[0129] Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0130] That is, those skilled in the art will understand that all or part of the steps in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a program, which is stored in a storage medium and includes a number of instructions for causing a device (which may be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., various media that can store program code.

[0131] Those skilled in the art will appreciate that the above-mentioned embodiments are specific examples for implementing the present invention, and that in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present invention.

Claims

1. A low-latency service transmission method, characterized in that: Applicable to access point devices in a multi-AP collaborative transmission mechanism, including: When there is a low-latency service to be transmitted in itself or its associated site device, it notifies each access point device in the multi-AP collaboration set as the low-latency service holder; When receiving a notification from the low-latency service holder, providing low-latency service transmission assistance to the low-latency service holder; The providing low-latency service transmission assistance to the low-latency service holder includes: providing a transmission opportunity to the low-latency service holder; The providing a transmission opportunity for the low-latency service holder includes: When serving as a transmission opportunity holder, and after receiving a polling feedback frame in response to a low-latency service polling frame issued by the low-latency service holder in a polling manner, when there is no low-latency service to be transmitted in itself or its associated site device, before the end of the usage time of the currently held transmission opportunity, allocate the transmission opportunity held by itself to the low-latency service holder; or, When serving as a transmission opportunity holder, and after receiving an inquiry feedback frame in response to a low-latency service inquiry frame issued by the low-latency service holder in the form of a multi-user inquiry, if there is no low-latency service to be transmitted in the site device of the low-latency service holder or the site device associated with the low-latency service holder, the transmission opportunity held by the low-latency service holder is allocated to the low-latency service holder before the usage time of the currently held transmission opportunity expires; or, When serving as a transmission opportunity holder and, after receiving a low-latency service arrival frame proactively reported by the low-latency service holder, there is no low-latency service to be transmitted in the site device or its associated site device, the transmission opportunity held by the site device is allocated to the low-latency service holder before the current transmission opportunity usage period expires; The polling feedback frame carries relevant information of the low-latency service to be processed; the query feedback frame carries relevant information of the low-latency service to be processed; and the method further includes: When serving as a transmission opportunity holder and after receiving polling feedback frames responded by multiple low-latency service holders, if the low-latency service to be transmitted does not exist in itself or its associated site equipment, the order and duration of use of the transmission opportunities held by itself are allocated to each low-latency service holder according to the relevant information of the low-latency service to be processed in each polling feedback frame; or When serving as a transmission opportunity holder and after receiving query feedback frames responded by multiple low-latency service holders, if the low-latency service to be transmitted does not exist in the site device itself or its associated site equipment, the order and duration of use of the transmission opportunities held by itself are allocated to each low-latency service holder according to the relevant information of the low-latency service to be processed in each query feedback frame; or When serving as a transmission opportunity holder and after receiving low-latency service arrival frames proactively reported by multiple low-latency service holders, if there is no low-latency service to be transmitted in itself or its associated site equipment, the order and duration of use of the transmission opportunities held by itself are allocated to each low-latency service holder according to the relevant information of the low-latency service to be processed in the low-latency service arrival frame; When the transmission coordinator, as well as the low-latency service holder, obtains the transmission opportunity and completes the transmission of the low-latency service to be transmitted, the transmission opportunity is returned to the transmission opportunity holder.

2. The low-latency service transmission method according to claim 1, characterized in that: The low-latency service polling frame is a trigger frame carrying a low-latency service polling indication; or, The low-latency service polling frame is a control frame carrying a low-latency service polling indication; or, The low-latency service polling frame is a data frame carrying a polling low-latency service indication; The polling low-latency service indication is an identifier used to indicate whether the frame carrying the polling low-latency service indication is the low-latency service polling frame; The polling feedback frame and the low-latency service polling frame are frames of the same type; or, The polling feedback frame is one of the following: a BSR frame, an ACK frame, an ICR frame, a BA frame, a CF-ACK frame, a Qos data frame, and a QosNull frame.

3. The low-latency service transmission method according to claim 1, characterized in that: The low-latency service inquiry frame is a trigger frame, the user general list field of the low-latency service inquiry frame carries access point information of each non-transmission opportunity holder in the multi-AP cooperation set, and the RA field of the delayed service inquiry frame carries broadcast address information; and / or, The low-latency service inquiry frame is an MU-related frame generated using multi-user technology; The MU-related frame is one of the following: a MU-RTS frame, a MU-BAR frame, or a GCR MU-BAR frame; The query feedback frame and the low-latency service query frame are frames of the same type; or, the query feedback frame is a CTS frame.

4. The low-latency service transmission method according to claim 1, characterized in that: The relevant information of the low-latency service to be processed includes one or any combination of the following: The urgency of the low-latency service to be processed, the maximum waiting time of the low-latency service to be processed, the latest sending time of the low-latency service to be processed, and the business volume of the low-latency service to be processed.

5. The low-latency service transmission method according to claim 1, characterized in that: Providing low-latency service transmission assistance to the low-latency service holder further includes one of the following or any combination thereof: adjusting the working configuration of each access point device related to the low-latency service through coordinated spatial multiplexing, providing beam coverage or beam nulling operation for the low-latency service holder according to priority or priority through coordinated beam forming; The adjusting the working configuration of each access point device related to the low-latency service by means of coordinated spatial multiplexing includes: When receiving a notification from the low-latency service holder, as a transmission opportunity holder, a higher transmission power is configured for each low-latency service holder in the multi-AP collaborative transmission mechanism, the most suitable MCS configuration and working mode are selected, and a lower transmission power is configured for the non-low-latency service holder, and a working mode is selected to reduce interference to the low-latency service holder.

6. The low-latency service transmission method according to claim 5, characterized in that: The providing beam coverage or beam nulling operation for the low-latency service holder according to priority or priority through coordinated beam forming includes: Adjusting the beam coverage of each access point device working in the multi-AP cooperative set by coordinated beam forming, so as to ensure that the signal coverage of the access point device of the non-low-latency service holder avoids the site device of the low-latency service holder receiving the low-latency service through beam nulling without generating a low-latency service priority conflict, while ensuring that the beam of the access point device of the low-latency service holder covers the site device receiving the low-latency service; or, Ensure that the beam coverage of the access point device holding the low-priority, low-latency service avoids the site device holding the high-priority, low-latency service and receiving the low-latency service by beam nulling, and at the same time ensure that the beam of the access point device holding the high-priority, low-latency service covers the site device receiving the low-latency service; Here, the priority refers to the priority between low-latency services, or refers to the priority between the low-latency services and non-low-latency services.

7. The low-latency service transmission method according to claim 1, characterized in that: The providing low-latency service transmission assistance to the low-latency service holder further includes: When competing for transmission opportunities with the access point devices in the multi-AP cooperative transmission mechanism, the low-latency service holder is provided with a competition priority that is beneficial for obtaining the transmission opportunity in the competition.

8. The low-latency service transmission method according to claim 1, characterized in that: The method further comprises: When there is a wired communication link between the access point devices in the multi-AP collaborative transmission mechanism, as a low-latency service holder, each access point device in the multi-AP collaborative set is notified, waiting for an instruction issued by the collaborative access point device in the multi-AP collaborative transmission mechanism or the transmission opportunity holder in the multi-AP collaborative transmission mechanism.

9. An access point device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the low-latency service transmission method as described in any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the low-latency service transmission method according to any one of claims 1 to 8 is implemented.

Images