Low-latency service transmission method, access point equipment and storage medium
Through multi-AP collaboration technology, it realizes efficient and stable transmission of low-latency services in Wi-Fi networks, solving the problem of insufficient latency and stability of Wi-Fi technology in high-density scenarios, and meeting the low latency and high-latency of emerging applications Reliability requirements.
Patent Information
- Application Number
- CN202411130553.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2044-08-16
AI Technical Summary
Existing Wi-Fi technology cannot guarantee low latency and stability in high-density scenarios, and cannot meet the needs of emerging applications such as telemedicine, virtual reality and industrial Internet of Things for low latency and high reliability, especially in transmission. There are tail and jitter problems of delay distribution when large amounts of data.
Using multi-AP collaboration technology, through coordination and collaboration between access point devices, intelligent spectrum allocation, efficient routing planning and refined traffic scheduling of low-latency services are achieved, providing low-latency service transmission assistance, ensuring that it is in wireless networks. efficient and stable transmission.
It improves the reliability and stability of low-latency services, reduces the maximum value and fluctuation range of network transmission delay, meets the needs of emerging applications for low-latency and high reliability, and improves user experience and network performance.
Smart Images

Figure CN119095111A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of wireless communication technology, and in particular to a low-latency service transmission method, an access point device, and a storage medium. Background Art
[0002] Wi-Fi standards have been committed to improving the peak rate and capacity of the network. However, in high-density scenarios such as airports, hotels, stadiums, and multi-residential apartments, previous Wi-Fi standards cannot guarantee stable network latency and low latency performance. Some emerging applications, such as telemedicine, virtual reality (VR), online / multiplayer games, industrial control, logistics, robotics, stereo / multi-speaker audio, etc., have strict requirements on network latency and require the network to be able to transmit large amounts of data in real time and with predictability. In addition, many IoT applications also require the network to support massive device access. For this type of low latency traffic, the network needs to be able to transmit data in a very short time to ensure the smoothness and real-time experience of the user experience. If the network latency is too high, users may encounter problems such as screen freezes, intermittent sound, and operation failures, which will affect the normal operation of the business.
[0003] Wi-Fi7 also proposed 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 predictable delays with higher reliability for delay-sensitive services on wireless links. The next generation of Wi-Fi technology, Wi-Fi8, aims to provide ultra-high reliability (UHR: Ultra High Reliability) wireless communications. It is further developed on the basis of IEEE 802.11be (i.e. Wi-Fi7) to meet the stringent requirements of emerging applications such as Industry 4.0, Industrial Internet of Things, autonomous driving, telemedicine, etc. 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] The next generation of Wi-Fi technology, Wi-Fi 8, takes ultra-high reliability of data transmission as its core goal. One of the main topics of UHR is to reduce the tail and jitter of delay distribution, that is, to reduce the maximum value and fluctuation range of network transmission delay. Therefore, how to improve the reliability of low-latency service transmission is not only a core research topic of Wi-Fi 8, but also a technical 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, an access point device and a storage medium, which combine the characteristics and advantages of multi-AP collaboration technology and the actual needs of current low-latency service processing, fully integrate the characteristics of multi-AP collaboration and low-latency services, and realize 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, then notifying 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, providing 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 so that the at least one processor can 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 that is also in a multi-AP collaborative transmission mechanism has a low-latency service to be transmitted in itself or in 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 described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0011] Figure 1 is a flow chart of a low-latency service transmission method provided according to an embodiment of the present invention;
[0012] Figure 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 is a schematic diagram of processing a low-latency service to be transmitted in a multi-user manner provided according to an embodiment of the present invention;
[0014] Figure 4 is a schematic diagram of multi-AP collaborative beamforming provided according to an embodiment of the present invention;
[0015] Figure 5 It is a schematic structural diagram of an access point device according to another embodiment of the present invention. DETAILED DESCRIPTION
[0016] To make the purpose, technical scheme and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. However, it will be appreciated by those skilled in the art that in the embodiments of the present invention, many technical details are proposed in order 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 scheme claimed in the present application can be implemented. The division of the following embodiments is for the convenience of description, and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined and referenced with each other without contradiction.
[0017] An embodiment of the present invention relates to a low-latency service transmission method, which 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, low-latency service transmission assistance is provided to the low-latency service holder. The characteristics of multi-AP collaboration and low-latency services are fully integrated to achieve 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, each access point device in the multi-AP collaboration set (Multi-AP set) is notified as a low-latency service holder;
[0019] The multi-AP coordination mechanism is a technology introduced to meet the needs of low-latency services and improve throughput. Similarly, some new technologies and functions have been introduced in the Wi-Fi protocol, such as orthogonal frequency division multiple access (OFDMA), multi-user multiple input multiple output (MU-MIMO), etc. Among them, the multi-AP coordination mechanism is a technology that uses coordination and joint transmission between multiple access points to improve network performance in a multi-AP environment, reduce interference and conflicts, and improve coverage and quality. In the multi-AP coordination mechanism, when the AP and its associated STA have a demand for low-latency service transmission, through a timely reporting mechanism and notifying other related APs to conduct intelligent coordination and avoidance, the reliability of low-latency service transmission can be significantly enhanced. Wifi8 introduces the technology of multi-AP coordination, which aims to improve the performance of the entire wireless network system by enhancing the collaboration between APs. This technology not only strengthens the collaborative working ability between access points, but also improves the throughput of the entire wireless network through fine resource scheduling and system optimization. Therefore, the introduction of multi-AP collaboration technology in Wifi8 provides strong support for the stability and reliability of low-latency service transmission. Combining the characteristics and advantages of multi-AP collaboration technology and the actual needs of current 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, and realizes efficient and stable transmission of low-latency services in wireless networks through intelligent spectrum allocation, efficient routing planning and refined traffic scheduling.
[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, the 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 (Pre-transmission) before the multi-AP cooperative transmission is turned on, 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, when a notification is received from a low-latency service holder, low-latency service transmission assistance is provided to the low-latency service holder;
[0023] In one example, providing low-latency service transmission assistance to low-latency service holders may be one of the following or any combination thereof: providing transmission opportunities to 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 zeroing operations to low-latency service holders by priority or priority through coordinated beam forming, etc. There are many 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 that are also in a multi-AP collaborative transmission mechanism, the low-latency service holders are provided with competition priority that is beneficial to obtaining transmission opportunities in the competition, etc. These methods can all be regarded as assistance provided to low-latency service holders. Examples will be given below to illustrate them one by one.
[0024] As a low-latency service holder, if it is also a transmission opportunity holder, the following examples show how to coordinate the access point devices in the multi-AP collaborative transmission mechanism to provide low-latency service transmission assistance for 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 give priority to allocating TXOPs to the STA or AP with low-latency service requirements. After the low-latency service transmission is completed, the Sharing AP will evaluate whether to allocate the remaining TXOPs (if any) to other devices.
[0026] In one example, the transmission opportunity holder notifies each transmission coordinator by sending a broadcast message. In some cases, in order to coordinate the transmission needs within the network, the Sharing AP may use a broadcast to convey the low-latency service indication to the relevant APs, which usually belong to the same Multi-AP Set. Through this broadcast, the Sharing AP notifies other APs that it currently has low-latency services to be transmitted, and the relevant APs can decide whether to avoid it according to their own situation to give priority to the transmission of low-latency services.
[0027] In some cases, the low-latency service indication may also carry another instruction, that is, notifying the relevant APs that the Sharing AP stops the function of sharing TXOP to 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, the 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 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 be: when competing for transmission opportunities with the access point devices that are also in the multi-AP collaboration set, providing the low-latency service holder with competition priority that is beneficial to obtaining the transmission opportunity in the competition. That is, in some cases, when APs with multi-AP coordination functions form a Multi-AP set, if an AP has low-latency services to be transmitted, the AP should be allowed to obtain transmission opportunities first in the backoff strategy, that is, the AP with low-latency services to be processed should obtain TXOP first and become a Sharing AP. After the low-latency service transmission is completed, consider whether to share the remaining TXOP with other APs based on actual conditions. Regarding the way to give priority to TXOP for low-latency services, it can be, for example, to assign the low-latency service to the highest priority access category (AC for short, full name Access Category, the highest priority access category is such as AC_VO) or define a new AC with a shorter arbitration inter-frame spacing (AIFS for short, 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 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, allocate the transmission opportunities held by itself to the low-latency service holder. The following will give detailed examples and further explanations of these three categories of examples in turn.
[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 services to the Sharing AP to request a transmission opportunity. The Sharing AP can poll the APs in the Multi-AP set to see if there are low-latency services to be transmitted. At this time, the transmission opportunity is obtained by responding to the low-latency service inquiry frame sent by the transmission opportunity holder, which can be: obtaining the transmission opportunity by responding to the low-latency service inquiry frame sent by the transmission opportunity holder according to the preset polling mechanism;
[0033] Regarding the time point at which the Sharing AP starts sharing TXOP with other APs, the following example is given:
[0034] 1. Immediately after obtaining TXOP, the polling mechanism is started. If there is a low-latency service to be sent by the Shared AP, the TXOP will be 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 enabled.
[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 equipment, 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 are any low-latency services 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 to inquire 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 sent 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 the urgency of the low-latency service, the volume of the service, the priority, the time limit for sending the timeout, and other factors, 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 respective usage duration. The AP that obtains the right to use the TXOP, after receiving the Trigger frame sent by the Sharing AP, uses the TXOP for the transmission of low-latency services. 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, Sharing AP can be Coordinator AP or Coordinated AP. If Sharing AP is Coordinated AP, it should send LL Poll frame to Coordinator AP to ask whether it has low-latency services to be transmitted during polling. If Coordinator AP has relevant coordination instructions, it can also carry relevant instructions in Feedback frame. Similarly, there can be many factors for the polling order of Sharing AP. For example, when Multi-APset is established, priority is set for Coordinated AP, and polling is carried out in order from high to low priority. In some cases, the polling order can also be defined according to the frequency of transmitting low-latency services or emergency services, that is, Sharing AP or Coordinator AP records the number of low-latency service transmissions of APs in Multi-AP Set, and preferentially polls whether the AP with the highest number of low-latency service transmissions has low-latency services to be processed. If the number of low-latency service transmissions is the same, the polling order is random.
[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 may carry information about polling low-latency services in a trigger frame in the related technology, such as BSRP, BQRP (Bandwidth Query Report Polling), an initial control frame (ICF), a beamforming report polling frame (BFRP: Beamforming Report Poll), or a null data physical layer protocol data unit feedback report polling frame (NFRP: NDP feedback Report Poll), as shown in Table 1 below:
[0045]
[0046] Compared with the related technical solutions, this structure defines the B63 bit in the common information field (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 the polling low-latency service indication. When LL Poll = 1, it means that the trigger frame also contains an indication to inquire whether there is a low-latency service to be transmitted. When LL Poll = 0, the function of inquiring about the low-latency service is not started. In some cases, the LL Poll subfield can also be included in the trigger-related common information subfield (Trigger Dependent common info subfield) in the Common info field.
[0047] The second structure type defines a new trigger frame type for polling of low-latency services, adds an indication of LL-Poll in the Trigger Type Subfield in the Common Info field of the Trigger frame, and the specific value can be one of the reserved fields (i.e., 8 to 15 bits) in the relevant technology. For example, in Table 2 below, when the value is 8, it indicates LL-Poll. The format of the Trigger frame can reuse the existing buffer status report polling frame (BSRP frame) or polling frame (Poll frame), and is consistent 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) carrying 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 structure types are given as examples:
[0051] The first structure type: In some cases, the indication information of polling low-latency services can also be added to the existing BlackAckReq frame, for example, the indication of LL-Poll can be added to the BAR Control field of the BlockAckReq frame. As shown in Table 3 below, the indication of LL Poll can be added to the B0 bit in the base address register control field (BAR Control field). In addition, any bit from B5 to B11 can be selected to indicate the information of LL Poll.
[0052]
[0053] The second structure type: the LL Poll information is carried through the base address register type field (BAR Type field), as shown in Table 4 below:
[0054]
[0055] Among them, when the BAR Type value is 1, it indicates the LL Poll information. Similarly, other values can also be used, such as 4-5, 7-9, 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 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 also be defined, which is specifically used to poll low-latency services. Its structure can reuse the existing polling frame structure, in which 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) carrying a polling low-latency service indication, such as: start polling cache frame (CF-poll frame), service quality data frame (Qos Data), service quality null frame (Qos null), etc.
[0057] In some cases, it is also possible to add indication information for polling low-latency services in existing CF-poll, Qos Data, and Qos null frames, such as adding LL-Poll indication in Frame Control. Alternatively, a new type of data frame can be defined specifically for polling low-latency services, and its structure can reuse the existing data 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 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] For the feedback frame corresponding to the low-latency service polling frame, that is, the polling feedback frame, the following simple examples illustrate several different structural forms:
[0060] In one example, the polling feedback frame and the low-latency service polling frame are frames of the same type, 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 also 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., indicating that it has low-latency services to be sent;
[0062] In one example, the polling feedback frame carries relevant information about the low-latency service to be processed, that is, the information about the low-latency service can be added to the existing regular frame. While feeding back the information that there is a low-latency service to be sent, the feedback frame can also optionally carry other information about the low-latency service, such as the urgency of the low-latency service, the longest 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 longest 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 may also have the following three situations:
[0064] Type A: For example, a feedback frame of 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 or 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, by adding an LL poll indication to the AP PS Buffer State subfiled in the Qos Control field of the BSR frame. LL poll is used to indicate the low-latency service mode. When LL poll is configured to 1, it indicates that the current BSRframe is used to indicate cache information related to low-latency services. When LL poll is configured to 0, it indicates 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: confirmation frame (BA) for successful reception of a data block, 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 in 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, Qos null, etc. In some cases, when the Shared AP receives the LL Poll frame sent by the Sharing AP, it can reply with a CF-ACK frame, Qos Data, Qos null, etc. Data frame to indicate that it has low-latency services to be transmitted. It can also add an indication of low-latency services in the frame control field of the Data frame to notify the Sharing AP that it has low-latency services to be transmitted.
[0073] In addition, it should be noted that the RA field of all the above-mentioned types of feedback frames should be configured with the MAC address of the Sharing AP.
[0074] The relationship between LL poll and feedback frame described above can be one-to-one correspondence, that is, if the LL poll frame is of type A, it corresponds to the feedback frame of type A. It can also be any combination, that is, if the LL poll frame is of type A, its feedback frame can also be of type B or other types.
[0075] In one example, when acting as a transmission coordinator and after obtaining a transmission opportunity, when the low-latency service to be transmitted is completed, the transmission opportunity is returned to the transmission opportunity holder. 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 commonly used 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. And 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 the Shared AP can use in the Trigger frame, that is, the Shared AP needs to return the TXOP after the indicated time period ends. In this case, there is no need to feedback the LL End frame to notify the Sharing AP to return the TXOP.
[0076] When the access point device obtains the transmission opportunity as the transmission coordinator, generally speaking, three different processing methods can be exemplified. The first type of example has been completed above. Regarding the second type of transmission opportunity provision method, the second type is that the transmission opportunity holder triggers the transmission opportunity provision using a multi-user inquiry form. When acting as a transmission opportunity holder, and after receiving an inquiry feedback frame in response to a low-latency service inquiry frame issued by itself in the form of a multi-user inquiry by a low-latency service holder, if the low-latency service to be transmitted does not exist in itself or its associated site device, 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, the Sharing AP sends a Trigger frame to the relevant APs (AP2 and AP3) in the Multi-AP set, triggering them to feedback the low-latency service information. After an interval of xIFS time, the relevant AP sends a feedback frame carrying the low-latency service information to the Sharing AP. After receiving the feedback frame, 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 determines the right to use the TXOP based on factors such as the urgency of the low-latency service and the size of the service, and sends the relevant information to the relevant APs through the TriggerFrame. The Trigger frame should also include information such as the duration of the TXOP that the Shared AP can use. The 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, when the low-latency service to be transmitted is transmitted, the transmission opportunity is returned to the transmission opportunity holder. After the low-latency service is transmitted, or after the TXOP usage time 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.
[0079] Among them, the low-latency service inquiry frame is a trigger frame, the user general list field of the low-latency service inquiry frame carries the access point information of each non-transmission opportunity holder in the multi-AP collaborative transmission mechanism, and the RA field of the delayed service inquiry frame carries the broadcast address information; or, the low-latency service inquiry frame is a MU-related frame generated by 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 frames of the same type; or the inquiry feedback frame belongs to a CTS frame.
[0081] Among them, the time interval between frames is, Figure 3 As shown in , xIFS can be RIFS (Reduced Interframe Space) or 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 processing method, or it can be a MU-RTS frame or MU-BAR or GCR MU-BAR frame and 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 is applied between multiple APs, as follows Figure 3 AP2 and AP3 in it. And the available recursion field (RA field, RA stands for Recursion Available) should be the 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 elaborated here. The LL End frame fed back by the AP that has obtained the TXOP and has low-latency services to be sent can reuse the LL End frame format in the first type of processing method. In addition, when the Sharing AP receives the indication information about the low-latency service 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 the access point device obtains the transmission opportunity as a transmission coordinator, generally speaking, there are three different processing methods. The first and second examples have been completed above. Next, the third example 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 equipment, the transmission opportunity held by itself is allocated to the low-latency service holder. In some cases, when the Shared AP has low-latency services to be processed, it can also notify the relevant APs that it has low-latency services 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 the pending notification of low-latency services to Sharing AP, and Sharing AP decides how to coordinate APs and how to 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 indication frames to notify each AP to coordinate.
[0086] Among them, there are also the following ways to send low-latency service notification time nodes:
[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 related APs in the Set.
[0088] 2. Sharing AP sends a Trigger frame, which contains 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 will report the notification of low-latency services. The reporting method can be to report only to Sharing AP or to send it to the Multi-AP Set in a group.
[0089] 3. During the signaling interaction between the Sharing AP and the Shared AP, the Shared AP with low-latency services to be sent can also carry the information of the low-latency services when transmitting the frame to the Sharing AP, notifying it that there are low-latency services to be sent. After receiving the indication of the low-latency services, the Sharing AP determines whether to prioritize the allocation of TXOP to the low-latency services and triggers the transmission of the low-latency services through the Trigger frame.
[0090] In the above, the frame type transmitted between Sharing AP and Shared AP can be an indication frame for reporting low-latency service notification by a station device (i.e., STA, also referred to as a 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 of multiplexing.
[0091] In some cases, the Sharing AP in this embodiment can be a Coordinator AP or a Coordinated AP. Similarly, the Shared AP can be a Coordinator AP or a Coordinated AP.
[0092] In some cases, when the Sharing AP is a Coordinated AP, it can send a notification to the Coordinator AP that it has low-latency services to be transmitted, 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 there are multiple Shared APs with low-latency services to be processed and request TXOP, SharingAP can decide which AP to allocate TXOP to first based on the urgency of the low-latency services, the remaining timeout, priority, etc. If time requirements allow, Sharing AP can send the order of Shared APs that obtain TXOP in the Trigger frame (Trigger for LL), and APs with low-latency services to be processed can use TXOP in order. When the low-latency services to be transmitted have the same urgency, remaining timeout, priority, etc., Sharing AP decides the allocation of TXOP by itself or randomly selects an AP for allocation. This strategy can be applied in any of the above three methods, that is, when acting 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, the use order and usage 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 acting as a transmission opportunity holder and after receiving inquiry 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 according to the relevant information of the low-latency service to be processed in each inquiry feedback frame; or, when acting 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 according to the relevant information of the low-latency service to be processed in the low-latency service arrival frame.
[0094] In some cases, when a wired communication link is established between APs, the signaling transmission between them is no longer limited by the competition mechanism in the traditional wireless channel, and there is no need to compete for limited wireless resources to obtain transmission opportunities. On the contrary, based on stable and reliable wired transmission technology, APs can achieve direct and conflict-free data and signaling exchanges. This transformation has greatly promoted the flexibility and efficiency of multi-AP coordination and cooperation, making network management smoother and policy execution faster and more accurate. With the support of wired communication, multi-AP systems can share information and coordinate resources more effectively, thereby further improving overall network performance.
[0095] In one example, when there is a wired communication link between the access point devices in the multi-AP cooperative set, as a low-latency service holder, notify each access point device in the multi-AP cooperative set and wait for instructions issued by the cooperative access point device in the multi-AP cooperative set or the transmission opportunity holder in the multi-AP cooperative set. When wired communication can be established between APs, at least when wired transmission can be carried out between APs in the Multi-AP Set, the access point device (LL AP for short) of the low-latency service to be transmitted can send a low-latency service indication to the relevant AP to coordinate and ensure the transmission of the low-latency service. The following will illustrate it through 3 schemes:
[0096] Solution 1: LL AP sends a low-latency service indication to Sharing AP, requesting it to allocate TXOP to low-latency service for transmission. Sharing AP then feeds back the TXOP allocation to the relevant APs, where:
[0097] a) Sharing AP needs to send the allocation of TXOP to LL AP. The structure of this indication frame can reuse the design of Trigger frame in the first or second processing mode above.
[0098] b) The low-latency service indication sent by the LL AP can reuse the design of low-latency service reporting in the third type of processing above;
[0099] c) Optionally, the Sharing AP's allocation of TXOPs needs to be sent to the Coordinator AP so that the Coordinator AP can uniformly allocate APs in the Multi-AP Set to adapt to the transmission of low-latency services. If the current Sharing AP is the Coordinator AP, this operation does not need to be repeated.
[0100] d) If the LL AP is a Sharing AP, use the solution in c) and only report to the Coordinator AP.
[0101] Solution 2: LL AP sends low-latency service indication to Coordinator AP, which makes unified arrangements and sends indication information to related APs to coordinate the transmission of low-latency services.
[0102] a) The low-latency service indication frame sent by the LL AP can reuse the design of low-latency service reporting in the third type of 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 is in the form of the Triggerframe design in the first or second processing method above;
[0104] c) LL AP can be a Coordinator AP or a Coordinated AP. If the LL AP is a Coordinator AP, it can directly send instructions to the Sharing AP to apply for TXOP use.
[0105] Solution 3: Before competing for TXOP, LL AP can send low-latency service indication to Coordinator AP, and Coordinator AP allocates TXOP to LL AP. In other words, LL AP can directly obtain TXOP and become Sharing AP. Specifically:
[0106] a) The low-latency service indication frame sent by the LL AP can reuse the design of low-latency service reporting in the third type of processing method above;
[0107] b) The Coordinator AP shall send an allocation indication to the LL AP and all other APs in the Multi-AP Set, notifying them that the current TXOP has been occupied by the LL AP and asking other APs to give way. The indication frame reuses the design of the Trigger frame in the first or second processing method above.
[0108] The above mainly exemplifies a method of providing transmission opportunities for low-latency service holders in providing low-latency service transmission assistance to low-latency service holders when a notification from the low-latency service holder is received. In fact, there are far more ways to provide low-latency service transmission assistance to low-latency service holders than this.
[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 next operation to be performed. The operation can be at least one of the following or a free combination thereof:
[0110] Notify the relevant APs of the right to use the subsequent TXOPs, and optionally carry information such as the TXOP usage duration and resource configuration;
[0111] Notify related APs to perform preemption operations, stop the services currently transmitted using TXOP, and start transmitting low-latency services; if multiple APs have low-latency services to be processed, Sharing APs allow related APs with higher priority or more urgency to preempt based on factors such as the urgency of the low-latency services, the volume of services, the priority, and the time limit of data timeout;
[0112] Notify the relevant APs to modify their current working modes, such as capability mode or operating mode, working mode, number of working antennas, MCS configuration, Nss configuration, transmit power, etc.
[0113] Notify related APs to adjust spatial reuse or other multi-AP operations, such as coordinated-spatial reuse, coordinated beam forming, joint transmission, and other operations, and adapt to the relevant configuration updates of 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 a 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 AP can configure a higher transmission power, or a suitable MCS, working mode and other configurations for low-latency services, so as to transmit low-latency services with the optimal working configuration without causing interference to other devices. Accordingly, Sharing AP can also configure other Shared APs (APs without low-latency services to be processed) to adopt a lower transmission power (which can be a pre-configured power threshold designed based on low-latency services. When an AP without low-latency services recognizes that there is an AP with low-latency services to be processed in the Multi-AP Set, it will control its own transmission power within the pre-set power threshold. The threshold can be determined by communication between APs in the Set during the establishment of the Multi-AP set, or can be notified by Sharing AP, or included in the PHY capability element, or MAC Capability element or pre-configured in the buffer of the device), a lower working mode to reduce interference to low-latency service devices. If there are multiple APs with low-latency services to be processed, Sharing AP will tilt resources to related APs with higher priority or more urgency according to factors such as the urgency of the low-latency services, the volume of services, the priority, and the time limit of data timeout, and adjust the related APs.
[0116] In one example, for coordinated beamforming between multiple APs, Beamforming, referred to as C-BF, or collaborative beamforming, or collaborative beamforming), that is, providing beam coverage or beam zeroing operation for low-latency service holders according to priority or priority through coordinated beamforming, can be: adjusting the beam coverage of each access point device working in a multi-AP cooperative set through coordinated beamforming, 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 the beam zeroing operation without generating a low-latency service priority conflict, and at the same time ensures 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 a low-priority low-latency service avoids the site device of the high-priority low-latency service holder receiving the low-latency service through the beam zeroing operation, and at the same time ensures that the beam of the access point device holding the high-priority low-latency service 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 certain device by means of beamforming. Beam nulling refers to setting the beamforming weight to zero in one direction to avoid a certain device in that direction. Beam coverage can be called beamforming coverage, beamforming coverage, or coverage, or simply beamforming, or beamforming. Beam coverage and beam nulling are two operations of collaborative beamforming.
[0117] In some cases, at least one AP participating in the collaborative beamforming decides to cover certain terminals or avoid (nulling) certain terminals (or access points) according to whether the terminals (STAs) or access points involved in the C-BF have low-latency services or the priority of low-latency services. If it is not possible to cover a certain terminal and avoid another terminal at the same time during C-BF, then one of the two terminals in the above conflict is abandoned or retained according to whether the terminal has low-latency services or the priority of low-latency services of each terminal, and only one terminal in the conflict is covered during C-BF, or only the other terminal in the conflict is avoided.
[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 done 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 when forming the beam, 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 4, STA11 associated with AP1 and STA22 associated with AP2 are in conflict. AP2 cannot guarantee coverage of STA22 while avoiding STA11. If there is no LL transmission to STA22, and there is LL to STA21, or there is low latency to STA11, AP2 guarantees coverage of STA21 while avoiding STA11, and does not consider STA22 when performing C-BF.
[0119] In some cases, whether the AP or terminal has LL service, or the priority corresponding to the low-latency service, or the service type corresponding to the low-latency service, when performing C-BF, it includes an initial control frame (ICF frame) or an initial response frame (ICR frame), or a channel measurement result reporting frame. In some cases, a bit 0 indicates that there is no LL service, and 1 indicates that there is a low-latency service. The initial control frame (ICF frame) or the initial response frame (ICR frame) is used to transmit C-BF-related information, or negotiate C-BF, form an AP pair, or an AP group performs C-BF.
[0120] In some cases, C-BF is performed by sacrificing STA22 (not considering the transmission of STA22, or the advanced C-BF related device transmission, delaying the transmission of STA22), covering STA21 and avoiding STA11. When making this decision, AP2 needs to notify AP2 of the decision through ICF / ICR. When AP2 performs C-BF, STA11 notifies AP2 as soon as possible after completing the transmission, such as sending ACK, which is received by AP1 and AP2 at the same time. So that AP2 can continue the transmission of STA22 as soon as possible.
[0121] In some cases, AP1 and AP2 need to perform C-BF, where terminal STA1 is associated with AP1. Terminal STA22 is associated with AP2. When AP2 performs C-BF, it takes into account multiple surrounding devices (STA11, STA21 and STA23) at the same time. STA22 is associated with AP3. By judging whether AP3 has low-latency services to transmit to STA3, it decides whether to avoid the terminal.
[0122] The capability mode is described in detail below: Capability mode (or operating mode) is a parameter that reflects the working capability of STA (including AP and non-AP STA). It is divided into multiple levels, and each level contains multiple key elements. Different levels represent different working capabilities of STA. The higher the level, the stronger the transmission capability.
[0123] The Capability Mode includes at least one of the following elements: working mode, number of working antennas (number of antennas for transmission and / or number of antennas for reception), channel bandwidth, NSS (Number of Spatial Streams, supported number of receiving spatial streams, and / or supported number of transmitting spatial streams), MCS (Modulation and Coding Scheme), coding method, code rate, whether to support multi-RU scheduling, data rate, PPDU format (Physical Protocol Data Unit) and data packet size are all important factors affecting network performance. Optionally, dRU (Dynamic Resource Unit) related parameters are also an important part of Capability Mode, which 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 to use dRU, whether it can coexist with rRU (regular RU), pilot (reference signal) density and number, whether to share pilot with rRU, etc.). Optionally, related parameters such as seamless roaming, slave channel access (or non-primary channel access) and multi-AP coordination are also optional parameters in Capability Mode, for example, whether seamless roaming is supported, whether slave channel access is supported, the granularity of slave channel access, bandwidth, number of temporary primary channels, slave channel access type (TXOP duration and / or EDCA parameters) and other slave channel access related parameters. Optionally, in some cases, Capability Mode also includes related parameters of multi-link devices, specifically, the number of links of multi-link devices, such as link ID, STA ID, MLD ID, or a combination thereof. In some cases, Capability Mode may also include a multiple link element, or a basic multiple link element or a newly defined multilink element, which is used 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 the first multi-connection device associated with it. In some cases, the multilink element is used to indicate the connection status of the current terminal and the 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 HT-immediate BlockAck, disabled subchannel bitmap, etc.
[0124] 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 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: providing transmission opportunities for low-latency service holders, adjusting the working configuration of each access point device related to low-latency service through coordinated spatial multiplexing, and providing beam coverage or beam zeroing operations for low-latency service holders through coordinated beam forming. Through the collaborative transmission of each access point, efficient and stable transmission of low-latency services in wireless networks 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 wireless networks.
[0125] The steps of the above method are divided only for clear description. When implemented, 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 to the algorithm or process or introducing insignificant designs 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 at least one processor 501, and the instructions are executed by at least one processor 501 so that at least one processor 501 can execute the low-latency service transmission method as described above.
[0127] The memory 502 and the processor 501 are connected in a bus manner, and the bus may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors 501 and the memory 502 together. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. The data processed by the processor 501 is transmitted on a wireless medium via an antenna, and further, the antenna also receives data and transmits the data 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 can understand that all or part of the steps in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0131] Those skilled in the art will appreciate that the above-mentioned embodiments are specific examples for implementing the present invention, and 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 cooperative 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 a notification is received from the low-latency service holder, low-latency service transmission assistance is provided to the low-latency service holder.
2. 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 includes one of the following or any combination thereof: providing transmission opportunities for the low-latency service holder, adjusting the working configuration of each access point device related to the low-latency service through coordinated spatial multiplexing, and providing beam coverage or beam zeroing operations for the low-latency service holder according to priority or priority through coordinated beam forming.
3. The low-latency service transmission method according to claim 2, characterized in that: The providing a transmission opportunity for the low-latency service holder includes: When acting 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 form, when there is no low-latency service to be transmitted in the low-latency service holder or its associated site device, allocating the transmission opportunity held by the low-latency service holder to the low-latency service holder; or, When acting 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, when the low-latency service to be transmitted does not exist 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; or, When acting as a transmission opportunity holder, and after receiving the low-latency service arrival frame actively reported by the low-latency service holder, when the low-latency service to be transmitted does not exist in itself or its associated site equipment, the transmission opportunity held by itself is allocated to the low-latency service holder.
4. The low-latency service transmission method according to claim 3, characterized in that: The low-latency service polling frame is a trigger frame carrying a polling low-latency service indication; or, The low-latency service polling frame is a control frame carrying a polling low-latency service indication; or, The low-latency service polling frame is a data frame carrying a polling low-latency service indication; Among them, 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.
5. The low-latency service transmission method according to claim 3, 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 delay service inquiry frame carries broadcast address information; and / or, The low-latency service inquiry frame is a MU-related frame generated using multi-user technology; 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 frames of the same type; or, the inquiry feedback frame belongs to a CTS frame.
6. The low-latency service transmission method according to claim 3, characterized in that: 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; The relevant information of 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 longest waiting time for 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.
7. The low-latency service transmission method according to claim 6, characterized in that: The method further comprises: When acting 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 of use and duration of use of the transmission opportunities held by each low-latency service holder 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 acting as a transmission opportunity holder and after receiving multiple inquiry feedback frames responded by the low-latency service holders, if the low-latency service to be transmitted does not exist in the site equipment of itself or its associated site equipment, the order of use and the duration of use of the transmission opportunities held by itself are allocated to each of the low-latency service holders according to the relevant information of the low-latency service to be processed in each of the inquiry feedback frames; or, When acting as a transmission opportunity holder and after receiving low-latency service arrival frames actively reported by multiple low-latency service holders, when the low-latency service to be transmitted does not exist in itself or its associated site equipment, the order of use and duration of use of the transmission opportunity held by itself are allocated to each of the low-latency service holders according to the relevant information of the low-latency service to be processed in the low-latency service arrival frame.
8. The low-latency service transmission method according to claim 2, characterized in that: The step of 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.
9. The low-latency service transmission method according to claim 2, characterized in that: The providing beam coverage or beam nulling operation for the low-latency service holder according to priority or priority by means of coordinated beam forming includes: Adjusting the beam coverage of each access point device working in the multi-AP cooperative set by means of 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 zeroing without causing a low-latency service priority conflict, and at the same time ensures 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 party avoids the site device holding the high-priority low-latency service party receiving the low-latency service through beam zeroing, and at the same time ensure that the beam of the access point device holding the high-priority low-latency service party covers the site device receiving the low-latency service; The priority refers to the priority between low-latency services, or refers to the priority between the low-latency services and the non-low-latency services.
10. 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 also includes: When competing for transmission opportunities with the access point devices that are also in the multi-AP cooperative transmission mechanism, the low-latency service holder is provided with competition priority that is beneficial for obtaining the transmission opportunity in the competition.
11. 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, notify each access point device in the multi-AP collaborative set, and wait for the 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.
12. 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 11.
13. 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 described in any one of claims 1 to 11 is implemented.
Citation Information
Patent Citations
Shared wireless fidelity communication device for controlling operations of station during shared period
CN113498196A
Communication method and device, equipment and storage medium
CN116803176A
Low-delay service transmission method and system
CN117336876A
Sharing a transmission opportunity of a wireless communication medium
US20200260488A1
Resource allocation for low-latency transmission
US20230146617A1
Cited By
Communication methods, communication apparatus and readable storage medium
WO2026124403A1
Communication method and apparatus
WO2026130219A1
Unified framework for multi-access point coordination in the transmission phase
WO2026174796A1
Methods and apparatus for use in transmission opportunity sharing
WO2026180180A1
