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

Abstract

Embodiments of the present application relate to wireless communication technology, and disclose a low-latency service transmission method, an access point and a storage medium. In the present application, when serving as a transmission opportunity holder, an access point device in the mechanism of multi-AP cooperative transmission sends a multi-user request to send frame for inquiring low-latency service information to each transmission opportunity receiver in a multi-AP cooperative set, and determines the allocation of the transmission opportunity through a clear to send frame carrying low-latency service information fed back; when serving as a transmission opportunity receiver, low-latency service information is generated according to the low-latency service existing in the access point device itself or a station device associated with the access point device, and a clear to send frame carrying the low-latency service information is sent to the transmission opportunity holder. Through reasonable allocation of the transmission opportunity, the actual demand of current low-latency service processing is met, the characteristics of multi-AP cooperation and low-latency service are fully integrated, and efficient and stable transmission of low-latency service in a wireless network is realized.

Description

TECHNICAL FIELD

[0001] The embodiment of the present application relates to wireless communication technology, in particular to a low-latency service transmission method, an access point and a storage medium. BACKGROUND

[0002] Low-latency services in network communication require data transmission delay to be extremely low and response time to be extremely short. Such services have extremely high real-time requirements, and any slight delay can have a significant impact on service effectiveness. Typical low-latency services include online games, real-time audio and video calls, financial transactions, remote control, etc. In these applications, the real-time performance and stability of data transmission are directly related to user experience and service efficiency. Therefore, low-latency services have extremely high requirements for network performance, and network devices and systems need to be able to provide fast and reliable data transmission services. In order to meet these needs, modern network technology is constantly developing and innovating, including the use of efficient encoding algorithms, optimization of network protocols, and improvement of transmission speed, to minimize data transmission delay and improve the performance and experience of low-latency services.

[0003] The inventor finds that at least the following problems exist in the related art: The mechanism of multi-AP cooperative transmission aims to enhance the cooperation capability between APs to improve the performance of the entire wireless network system, but how to coordinate and respond to low-latency services in each device in the mechanism of multi-AP cooperative transmission is still a technical blank in the field at present. SUMMARY

[0004] The purpose of the embodiment of the present application is to provide a low-latency service transmission method, an access point and a storage medium, which combines the characteristics and advantages of multi-AP cooperation technology, reasonably allocates transmission opportunities to meet the actual needs of current low-latency service processing, fully integrates the characteristics of multi-AP cooperation and low-latency services, and realizes efficient and stable transmission of low-latency services in wireless networks.

[0005] To solve the above technical problems, the embodiment of the present application provides a low-latency service transmission method applied to an access point device in a multi-AP cooperative transmission mechanism, including: when acting as a transmission opportunity holder, sending a multi-user request to send frame for inquiring low-latency service information to each transmission opportunity waiting party in a multi-AP cooperative set, and determining the allocation of transmission opportunities through the clear to send frame carrying the low-latency service information fed back by each transmission opportunity waiting party; when acting as a transmission opportunity waiting party, after receiving the multi-user request to send frame, generating the low-latency service information according to the low-latency service existing in itself or a station device associated with itself, and sending the clear to send frame carrying the low-latency service information to the transmission opportunity holder.

[0006] The embodiment of the present application also provides an access point, comprising: at least one processor; and a memory connected with 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 perform the low-latency service transmission method.

[0007] The embodiment of the present application also provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the low-latency service transmission method.

[0008] In the embodiment of the present application, the access point device which is also in the mechanism of the multi-AP cooperative transmission, when being the transmission opportunity holder, sends a multi-user request to send frame for inquiring low-latency service information to each transmission opportunity waiter in the multi-AP cooperative set, and determines the allocation of the transmission opportunity through the clear to send frame carrying the low-latency service information fed back by each transmission opportunity waiter; when being the transmission opportunity waiter, after receiving the multi-user request to send frame, generates the low-latency service information according to the low-latency service existing in the station device associated with the station device itself or the station device itself, and sends the clear to send frame carrying the low-latency service information to the transmission opportunity holder. The actual demand of the current low-latency service processing is met by reasonably allocating the transmission opportunity, the characteristics of the multi-AP cooperation and the low-latency service are fully integrated, and the efficient and stable transmission of the low-latency service in the wireless network is realized. BRIEF DESCRIPTION OF DRAWINGS

[0009] One or more embodiments are illustrated by way of example in the figures that are part of this document, and which illustrate by way of example the principles of the embodiments. The same reference numbers in different drawings represent the same elements or the similar elements, unless otherwise indicated. The drawings in the accompanying materials are not intended to be to scale.

[0010] Figure 1 is a flow chart of a low-latency service transmission method according to an embodiment of the present application;

[0011] Figure 2 is a schematic diagram of a frame exchange mechanism related to a multi-user request according to an embodiment of the present application;

[0012] Figure 3 is a schematic diagram of a frame exchange mechanism when a block acknowledgement frame carrying return information in a reserved bit according to an embodiment of the present application;

[0013] Figure 4 is a schematic diagram of a frame exchange mechanism when a station device is a receiver of a low-latency service according to an embodiment of the present application;

[0014] Figure 5Fig. 1 is a schematic diagram of a frame exchange mechanism when a return frame is a CF-End frame carrying return information according to an embodiment of the present application;

[0015] Figure 6 Fig. 2 is a schematic diagram of a frame exchange mechanism when a low-latency service is notified of completion according to an embodiment of the present application;

[0016] Figure 7 Fig. 3 is a schematic diagram of an access point according to another embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below with reference to the drawings. However, those skilled in the art can understand that, in the embodiments of the present application, many technical details are presented in order to make the reader better understand the present application. However, the technical solutions claimed by the present application can be implemented even without these technical details and based on various changes and modifications of the following embodiments. 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 application, and the embodiments can be combined and referenced with each other on the premise of not contradicting.

[0018] An embodiment of the present application relates to a low-latency service transmission method, which can be applied to each access point device in a multi-AP cooperative transmission mechanism. In the embodiment, when serving as a transmission opportunity holder, the access point device in the multi-AP cooperative transmission mechanism sends a multi-user request to send frame for inquiring low-latency service information to each transmission opportunity receiver in the multi-AP cooperative set, and determines the allocation of the transmission opportunity according to the clear to send frame carrying the low-latency service information fed back by each transmission opportunity receiver; when serving as a transmission opportunity receiver, after receiving the multi-user request to send frame, the access point device generates low-latency service information according to the low-latency service existing in the access point device itself or a station device associated with the access point device, and sends the clear to send frame carrying the low-latency service information to the transmission opportunity holder. The actual demand of the low-latency service processing is satisfied by reasonably allocating the transmission opportunity, the characteristics of the multi-AP cooperation and the low-latency service are fully integrated, and the efficient and stable transmission of the low-latency service in the wireless network is realized. In the following, the corresponding low-latency service processing mechanism will be proposed for different scenarios. It is particularly stated that the present application does not impose restrictions on the signaling interaction mode between the access point (AP) and the station device (STA) in the same basic service set (BSS). That is to say, when the station device has low-latency service to be transmitted, the AP associated with the station device is aware of the situation by default, and the way in which the STA reports the low-latency service of the station device is not specifically specified or limited in the embodiment. The implementation details of the low-latency service transmission method of the embodiment will be specifically described below, and the following content is only the implementation details provided for the convenience of understanding, and is not necessary for implementing the present application.

[0019] As shown in Figure 1 the embodiment, when serving as a transmission opportunity holder, the access point device in the multi-AP cooperative transmission mechanism sends a multi-user request to send frame for inquiring low-latency service information to each transmission opportunity receiver in the multi-AP cooperative set in step 101.

[0020] The mechanism of Multi-AP Coordinated Transmission is a huge and complex concept, under which there are multiple possible situations and corresponding countermeasures, such as: Multi-AP discovery, used to support the exchange of relevant information between APs for Multi-AP coordination; Coordinated Agreement, used to reach an agreement between APs for Multi-AP coordination and form a Multi-AP set (also known as Multi-AP group or multi-AP coordination set); there will be a Coordinator AP (also known as Master AP) in the Multi-AP set, which is used to coordinate the work between devices in the Multi-AP set, and usually the Coordinator AP is the AP that initiates the establishment of the Multi-AP coordination set; other participating APs in the Multi-AP set are called Coordinated APs (also known as Slave APs); Pre-transmission, used for some preparation work before Multi-AP Coordinated Transmission, such as some configurations for Coordinated Beamforming, Joint Transmission, etc.; Multi-AP Coordinated Transmission, initiated by a Sharing AP, after reaching an agreement between APs to form a Multi-AP set, the AP that successfully obtains a Transmission Opportunity (TXOP) and starts Multi-AP coordination operation is called a Sharing AP. It is the coordinator of the entire Multi-AP transmission, responsible for managing and controlling the transmission process. While the other APs in the Multi-AP set are called Shared APs. These APs are coordinated by the Sharing AP and actually participate in Multi-AP transmission, and they are responsible for completing the data transmission task under the guidance of the Sharing AP.

[0021] The following will be described in detail the specific way of extending the frame exchange mechanism of multi-user request to send / clear to send (MU-RTS / CTS) to the mechanism of coordinating time division multiple access in multi-AP cooperation, wherein the mechanism of coordinating time division multiple access (C-TDMA, also referred to as C-OFDMA) means that, in the multi-AP cooperation mechanism, the AP (i.e. Sharing AP) obtaining the TXOP can share the TXOP with other APs (Shared APs) in need in the multi-AP cooperation set for their own or their associated STA transmission of urgent or required traffic.

[0022] The multi-user request related frame exchange mechanism is as shown in Figure 2 The Sharing AP can send a multi-user request to send (MU-RTS) frame carrying an indication (referred to as LL Poll, wherein LL is the abbreviation of low latency traffic) for inquiring low latency traffic information to the relevant Shared APs, i.e. transmission opportunity waiters 1 and 2 (Shared AP1 and Shared AP2), as shown in the figure. The Shared AP1 and Shared AP2 receive the MU-RTS frame inquiring whether there is low latency traffic to be transmitted, and simultaneously feed back a clear to send (CTS) frame after a certain time interval, wherein the Shared AP (Shared AP2) having low latency traffic can carry low latency traffic information (LL Notification) to inform the Sharing AP. The Sharing AP can allocate TXOP to the Shared AP2 having low latency traffic to be processed according to the actual situation after receiving the CTS, and carries relevant information through a trigger (Trigger) frame. The Shared AP2 receives the Trigger frame for allocating TXOP to it, and sends a Trigger frame for low latency traffic to the associated STA (STA1 and STA2) having low latency traffic to be transmitted. Figure 2 The STA receives the notification of being able to send low latency traffic, and sends a data packet of low latency traffic. After receiving a block acknowledgement (BA) frame from the Shared AP2, the Shared AP2 needs to send a notification frame to the Sharing AP to inform the Sharing AP that the low latency traffic transmission is completed, and the TXOP can be returned.

[0023] The following will be described in detail the specific way of extending the frame exchange mechanism of multi-user request to send / clear to send (MU-RTS / CTS) to the mechanism of coordinating time division multiple access in multi-AP cooperation, wherein the mechanism of coordinating time division multiple access (C-TDMA, also referred to as C-OFDMA) means that, in the multi-AP cooperation mechanism, the AP (i.e. Sharing AP) obtaining the TXOP can share the TXOP with other APs (Shared APs) in need in the multi-AP cooperation set for their own or their associated STA transmission of urgent or required traffic.

[0024] The overall design idea of the first type of design is to use the traditional MU-RTS (Multi-User Request To Send) frame structure and improve it on this basis. The indication of inquiring low-latency service information is carried by the reserved bits in the multi-user request to send frame. The function is expanded by multiplexing the reserved bits to adapt to the demand for low-latency service inquiry in the multi-AP cooperation mechanism. Specifically, the main structure and type identifier of the MU-RTS frame are reserved to ensure compatibility with the traditional MU-RTS frame. At the same time, without increasing additional complexity, new information is conveyed by modifying or reallocating several reserved bits.

[0025] The existing MU-RTS frame contains several unused reserved bits, such as UL length, GI and HE-LTF type, MU-MIMO HE-LTF mode, number of HE-LTF symbols and midamble periodicity, UL STBC, LDPC extra symbol segment, AP Tx power, pre-FEC padding factor, PE disambiguity, UL spatial reuse, Doppler, UL HE-SIG A2 reserved (i.e. UL length, GI And HE-LTF Type, MU-MIMO HE-LTF Mode, Number of HE-LTF symbols and Midamble periodicity, UL STBC, LDPC Extra Symbol Segment, AP Tx Power, Pre-FEC Padding Factor, PE Disambiguity, UL Spatial Reuse, Doppler, UL HE-SIG A2 Reserved) and reserved fields in the common information field (Common info field); UL FEC coding type, UL HE-MCS, UL DCM, SS allocation RA-RU information, UL target receive power (i.e. UL FEC Coding Type, UL HE-MCS, UL DCM, SS Allocation RA-RU information, UL Target Receive Power) and reserved fields in the user information field (User info field). One of these bits (or a combination of multiple bits to provide higher flexibility) can be used to mark whether the MU-RTS frame carries information inquiring low-latency services.

[0026] For example, if one or more bits are set to 1, it indicates that the MU-RTS frame is not only used for the conventional request to send purpose, but also inquires whether the related APs in the multi-AP cooperation set have low-latency service requirements. The related APs can determine whether to report the status of their low-latency services according to this information in the response (CTS or similar frame). The advantage of this design structure is its low implementation cost and wide compatibility. For devices of previous Wifi versions, the above reserved bits will not be parsed, while devices of new versions or supporting multi-AP cooperation will identify the corresponding bits and obtain the related information of low-latency services. This scheme directly extends the existing MU-RTS frame structure without introducing a new frame type or complex processing logic.

[0027] The overall design idea of the second type of design is to specially design a new type of MU-RTS frame for the multi-AP cooperation mechanism, i.e., a multi-AP specific MU-RTS frame, which can optimize resource allocation and scheduling strategies in a multi-AP environment by defining a new trigger frame. In the trigger type subfield in the common information field in the multi-user request to send frame of the second type of design, there is an indication field for inquiring low-latency service information. That is, a new type indication is added to the trigger type subfield in the common information (CommonInfo) field of the new type of MU-RTS frame, and the specific value can be any reserved bit from the 8th bit to the 15th bit.

[0028] The multi-AP specific MU-RTS frame in the second type of design will include a series of fields specially designed for multi-AP cooperation, including but not limited to AP identifiers, cooperation mode indicators, resource allocation information, etc. In particular, for the inquiry of low-latency service requirements, two implementation methods are provided in this scheme: one method is similar to the first design idea described above, which multiplexes the traditional reserved bits, but here these reserved bits are explicitly reserved in the newly defined MU-RTS frame structure, and are used to represent specific inquiry intentions, such as inquiring whether there is a low-latency service requirement to be transmitted. The other more concise way is to perform implicit inquiry, i.e., without directly setting specific bits to represent the inquiry of low-latency services, but when sending this specific MU-RTS frame, it implies the intention of inquiring whether all related APs have low-latency service requirements. The receiver decides whether to report the status of its low-latency services according to this implicit inquiry when responding.

[0029] The access point device in the mechanism of multi-AP cooperative transmission, when as a transmission opportunity waiter, in step 102, after receiving a multi-user request to send frame, generates low-delay service information according to the low-delay service existing in itself or the station device associated with itself, and sends a clear to send frame carrying the low-delay service information to the transmission opportunity holder, so that the transmission opportunity holder determines the allocation of the transmission opportunity through the clear to send frame carrying the low-delay service information fed back by each transmission opportunity waiter.

[0030] The following will take two different structures of the clear to send frame carrying the low-delay service information as examples:

[0031] The overall design idea of the first type of design is to use the traditional CTS (clear to send) frame structure and improve it on this basis, and to realize the indication of low-delay service by changing the meaning of one or more bits. In the traditional CTS frame used to reply to the MU-RTS frame, there are 8 bits in the Frame control field that do not play an actual role and are uniformly configured as 0, which are respectively named: To DS, From DS, More Frag, Retry, Power Management, More data, Protected frame (To DS, From DS, More Frag, Retry, Power Management, More data, Protected frame) field and +HTC subfield. On this basis, one or more bits of the above 8 bits can be selected to carry the indication information of low-delay service. In one example, the low-delay service information in the clear to send frame is carried by the power management subfield in the Frame Control field, which is used to indicate the existence of low-delay service. If the current AP has low-delay service to be processed, the power management (Power management) subfield in the CTS frame can be configured as 1. This scheme has the advantages of multiplexing the existing structure, good compatibility, and low modification cost. Alternatively, another way is to set all the above-mentioned 8 bits that do not play an actual role to 1 to represent the existence of low-delay service to be transmitted in the current device, that is, the To DS, From DS, More Frag, Retry, Power Management, More data, Protected frame and +HTC subfields in the Frame control field in the CTS frame are all set to 1, which indicates that there is low-delay service to be transmitted in the current device. This scheme can reduce the impact of interference, is simple and easy to implement.

[0032] The overall design idea of the second type of design is to design a new type of CTS frame, which is specially used for transmission in the multi-AP cooperation mechanism. The control frame extension field for carrying low-latency service information exists in the frame control field of this clear to send frame, so that this CTS frame can not only carry the indication of the existence of low-latency service, but also increase other information of low-latency service, and implicitly indicate that the sender of the CTS frame is an AP. The new type of CTS frame can be used as an extension of the control frame, and its structure can follow the structure of the CTS, but its Framecontrol field can be modified as shown in Table 1 below:

[0033] The protocol version is filled in according to the actual situation, and the values of the Type, Subtype, Control frame extension fields are as follows, wherein when the Control Frame Extension field is configured as 1100, it indicates a new type of CTS, that is, M-AP CTS. Optionally, other reserved fields can also be used to indicate M-AP CTS, such as one of 1101-1111. As shown in Table 2 below:

[0034]

[0035] The B12-B15 bits in the Control frame field of the M-AP CTS are configured as 0 by default. Optionally, these 4 bits can also be used to convey other information, for example, one or more or all 4 bits are used to indicate the existence of low-latency service. In addition, other low-latency service related information indications can also be added, for example, timing information of low-latency service such as duration, acceptable maximum delay, emergency degree and other timing related information, so as to better coordinate between APs. In addition, the priority information of low-latency service can also be added in the frame, so as to perform priority scheduling when multiple services are concurrent, for example, using a field to represent the priority level of the service. The second design scheme has strong information carrying capacity and can provide more service information, which is helpful for multi-AP cooperation, but a new frame structure needs to be designed, which may increase the implementation complexity and compatibility problems.

[0036] In one example, in order to ensure that the AP or STA devices in the OBSS can effectively identify the data transmission of low latency service, an optimized strategy is to embed the indication of low latency service into the PHY Preamble (physical layer preamble), that is, the low latency service information is carried by the physical layer preamble. The devices of the OBSS can be enabled to timely perceive the existence of low latency service traffic, thereby triggering the corresponding avoidance mechanism or optimizing the transmission strategy. In this way, not only can the transmission delay of low latency service be significantly reduced, but also the stability and efficiency of the entire network environment can be effectively maintained. Specifically, the identification of the existence of low latency service (LL Notification) can be configured in the HE-SIG-A of the preamble, which is used to indicate that the current device contains low latency service to be transmitted. The Sharing AP can allocate the use right of TXOP according to the actual situation after detecting the LL Notification. The LL Notification can be configured in the HE-SIG-A1 subfield or the reserved bit of the HE-SIG-A2 subfield, for example, in the B14 bit of the HE-SIG-A1 subfield. For example, when the bit is configured as 0, it indicates that the current PPDU contains low latency service, and when the bit is 1, it indicates that there is no low latency service. In some cases, for the EHT Preamble, the LL Notification can be configured in the EHT-SIG. In some cases, for the preamble of the next generation of wifi standard, the LL Notification can be configured in the signal (SIG) field or other fields thereof.

[0037] In one example, when acting as a transmission opportunity waiter, after receiving the multi-user request to send frame, when there is no low latency service in the device itself or the station device associated with the device, a clear to send frame is not fed back. That is, when the MU-RTS sent by the Sharing AP contains information (LL Poll) inquiring whether there is low latency service. If the Shared AP has low latency service, a CTS frame is fed back; if not, no CTS frame is fed back. The CTS frame at this time can follow the existing CTS frame in the protocol without any modification. An LL Poll field is added in the MU-RTS frame to inquire whether there is low latency service. The design of the MU-RTS frame can follow the design mentioned in the above. After receiving the MU-RTS frame, if the Shared AP has low latency service, a CTS frame is sent; if not, no CTS frame is sent.

[0038] In addition to the 1 bit mentioned above, the indication of low latency traffic (LL Notification) can also be expressed in other forms, such as: the AC category corresponding to the low latency traffic. The AC category can be a new AC category designed for low latency traffic, or an existing category with higher priority, such as AC_VO, AC_VI, etc. It can also be the priority corresponding to the low latency traffic or a priority-related parameter. However, if the above forms are used to indicate the low latency traffic, more bits are needed for indication.

[0039] In the mechanism of the multi-AP cooperative transmission of the present embodiment, two types of Trigger frames are involved. One is sent by the Sharing AP to indicate how to allocate the TXOP. The other is sent by the Shared AP that obtains the TXOP usage right to the STAs associated with itself to inform them that they can send low latency traffic. It should be noted that the Trigger frame is only sent when the associated STA of the Shared AP has low latency traffic to be transmitted. If the Shared AP itself needs to transmit low latency traffic, the Trigger frame does not need to be sent. In the present embodiment, the design of the above two types of Trigger frames will be described.

[0040] Regarding the first type of Trigger frame, the Trigger Frame is a new type of trigger frame, which is specially used by the Sharing AP to send to one or more Shared APs to indicate the allocation of the TXOP in the multi-AP cooperative mechanism. When acting as the transmission opportunity holder, after deciding the allocation of the transmission opportunity, the configuration information for allocating the transmission opportunity is generated, and the trigger frame carrying the configuration information is sent to the transmission opportunity waiting party. For example: the configuration information can be a new value configured in the Trigger Type Subfield in the Common info field, which can be selected from the existing reserved bits, such as one of 8-15.

[0041] The configuration information includes: a user of the use right of the transmission opportunity, and a valid period of the use right of the transmission opportunity; in other words, the trigger frame should include one or any combination of the following elements: a) a time length of the TXOP that can be used, so that the shared AP knows the time window that can be used. The relevant device can only use the TXOP for its own data transmission within the TXOP use time length, and the TXOP is automatically returned after the time length is exceeded. b) If the TXOP is allocated to multiple devices, the trigger frame should include the order of TXOP use and the TXOP use time length of each device, so that each device uses the TXOP in order. c) Frequency band information that can be used, if the conditions allow, the resources on different frequency domains within the TXOP can also be allocated to the corresponding shared AP for use. So that the transmission between the shared APs is in a frequency division state.

[0042] The information contained in the above trigger frame can be configured in the common info field or in the user info list. If the TXOP is allocated to multiple shared APs, the shared APs allocated with the TXOP should be included in the user info list.

[0043] Regarding the second type of trigger frame, when acting as a transmission opportunity waiting party, after obtaining the use right of the transmission opportunity, a trigger frame carrying notification information is sent to each station device associated with itself and having low latency business; wherein the notification information is used to notify the station device that it can use the use right of the transmission opportunity to transmit low latency business. Specifically: after the shared AP receives the trigger frame indicating that the TXOP can be used by the sharing AP, if the associated STA has low latency business to be transmitted, another trigger frame is sent to the low latency business to inform it that the TXOP can be used for low latency business transmission. The trigger frame can be in the same format as the trigger frame mentioned above for APs, or can be a trigger frame in the existing protocol or other forms of frame or a newly defined type of trigger frame, which is not particularly limited, as long as it has the action of notifying the relevant STA to transmit low latency business.

[0044] In the multi-AP cooperation mechanism, when the low latency business transmission is completed, the TXOP needs to be returned to the sharing AP. That is, when acting as a transmission opportunity waiting party, after the low latency business existing in itself or the station device associated with itself is completed, the transmission opportunity is returned to the transmission opportunity holder;

[0045] In which, the transmission opportunity is returned to the transmission opportunity holder, which can be: after the expiration of the effective period of the right to use the transmission opportunity, the transmission opportunity is automatically returned to the transmission opportunity holder; in other words, in the Trigger Frame of the Sharing AP allocating TXOP, the use time of TXOP has been indicated. After the corresponding time is over, the TXOP is automatically returned to the Sharing AP. This way is simple and direct, and is suitable for the transmission scene of predetermined time length. Or it can be: a return frame carrying return information is sent to the transmission opportunity holder to return the transmission opportunity to the transmission opportunity holder; the Shared AP feeds back a return frame to the Sharing AP after completing the TXOP use, informing that the TXOP use is completed. This method is suitable for the case where the TXOP use time is not configured, and can also be used for the case where the TXOP is returned in advance. For example, the transmission is completed before the time specified by the Sharing AP, and the TXOP can be returned in advance to save more resources.

[0046] Regarding the design of the return frame, the following schemes can be used:

[0047] 1. The return frame is a Block Acknowledgement Frame (BA) frame carrying return information in the reserved bit. The information of TXOP return is added in the BA frame, for example, the reserved bit in the BA control field or the reserved bit in the BA type of the BA control field, and the indication of returning TXOP is added.

[0048] In the BA control field, there are some reserved bits which are not used at present. One or more of the bits can be selected to indicate the return of TXOP. When the Shared AP completes the low-latency service transmission, a specific value (for example, setting a bit to 1) can be set in these reserved bits to indicate that the TXOP has been returned. Similarly, there are also some reserved bits in the BA type field of the BA control field. A type can be specially set for the BA frame returning TXOP, and one or more reserved bits can be selected to be specially used for the BA frame returning TXOP. Alternatively, the BA frame can carry two kinds of information at the same time, which can be used as an acknowledgement frame of feedback acceptance data and also can inform the Sharing AP to return the TXOP. As follows Figure 3As shown, the Sharing AP can send a multi-user request to send frame carrying an indication for inquiring low latency traffic information to the relevant Shared AP. After a certain time interval, transmission opportunity waiters 1 and 2 simultaneously feed back clear to send frames, wherein the Shared AP with low latency traffic can carry low latency traffic information to inform the Sharing AP. After receiving the CTS, the Sharing AP can preferentially allocate TXOP to the Shared AP 2 with low latency traffic to be processed according to actual conditions, and carry relevant information through a trigger frame. After receiving the trigger frame for allocating TXOP to the Shared AP 2, the Shared AP 2 can send a trigger frame for low latency traffic to the associated STA with low latency traffic to be transmitted. After receiving the notification that the STA can send low latency traffic, the STA sends a data packet of low latency traffic, and completes transmission after receiving a block acknowledgement (BA) frame fed back by the Shared AP 2. The BA can be sent to the STA and the Sharing AP at the same time to represent two meanings. In this case, there can be wired communication between the Shared AP and the Sharing AP, or in the case of wireless communication, the information of returning TXOP can be added to the PHY preamble. Such design enables the BA frame to not only complete the function of data reception confirmation, but also deliver the information of TXOP return without increasing additional frames, thereby improving communication efficiency.

[0049] 2. In some cases, the TXOP return information can also be carried in the form of a feedback block acknowledgement (Multi-STA BA) frame sent by a multi-connection station device. The TXOP return information and the originally returned BA information can be simultaneously carried in the BA information field. The BA information field of the Multi-STA BA frame contains a plurality of per AID TID information (Per AID TID Info) subfields, wherein AID is the full name of "Association Identifier", indicating the association identifier of a user; TID is the full name of "Traffic Identifier", indicating the traffic identifier. Each AID TID Info subfield corresponds to a reply to a device. The feedback content for low latency traffic (such as LL Data) can be generated according to the existing protocol rules. The TXOP return information fed back to the Sharing AP can be designed as follows, wherein the AID TID Info subfield structure is as follows:

[0050]

[0051] Wherein, Ack Type represents the type of acknowledgement frame.

[0052] Wherein, in the AID TID Info subfield corresponding to the Sharing AP, the AID 11 subfield should be configured as 0, and the Ack type subfield and the TID subfield can use the reserved combination in the existing protocol to represent TXOP return. For example, Ack type subfield = 0, TID subfiled = 14, or Ack type subfield = 0, TID subfiled = 15, or other reserved combinations. At the same time, the TXOP return option is added in several acknowledgement context options of the Multi-STA BA frame. When the receiver of the Multi-STA BA frame is an AP, AID 11 subfield = 0, Ack type subfield = 0, TID subfiled = 14 (take this combination as an example), then it represents TXOP return, and in this case, the AID TID info subfield does not contain the Block Ack Starting Sequence Control subfield and the Block Ack Bitmap subfield. And the RA field of the Multi-STA BA frame should be the broadcast address.

[0053] In addition, in the above case, when the sender of the Multi-STA BA frame is an associated STA of the Shared AP, that is, the low-latency service is at the Shared AP side, and the STA is the receiver of the low-latency service. The following Figure 4 For example, the low-latency service data (LL Data) frame sent by the transmission opportunity waiting party 2 (Shared AP2) should contain an indication indicating that it feeds back TXOP return information. Optionally, in this case, the station device (STA) can also send a BA frame to the Shared AP2, and the Shared AP2 can send a feedback frame carrying TXOP return information to the transmission opportunity holder (Sharing AP) alone.

[0054] 3, The return frame is a contention free end (CF-End) frame carrying return information, and the CF-End frame is used to indicate the return of TXOP. In this case, the CF-End frame has a new meaning, and when the sender of the CF-End frame is the AP of Wifi8 or the AP supports multi-AP cooperation or the AP is a member of the multi-AP cooperation set, the CF-End frame can be sent as a signal to return the TXOP, and the frame structure of the CF-End frame is the same as that in the traditional protocol, as shown in the following formula Figure 5 The sharing AP can send a multi-user request to send frame carrying an indication for inquiring low-latency service information to the relevant shared AP. After a certain time interval, the transmission opportunity waiting party 1 and the transmission opportunity waiting party 2 simultaneously feed back the clear to send frame, wherein the shared AP with low-latency service can carry low-latency service information to inform the sharing AP. After receiving the CTS, the sharing AP can preferentially allocate the TXOP to the shared AP 2 with low-latency service to be processed according to the actual situation, and carry the relevant information through the trigger frame. After receiving the trigger frame for allocating the TXOP to the shared AP 2, the shared AP 2 can send a trigger frame for low-latency service to the associated STA with low-latency service to be transmitted. After receiving the notification that the STA can send the low-latency service data packet, the shared AP 2 needs to send a CF-End frame to the sharing AP to inform the sharing AP that the low-latency service transmission is completed, and the TXOP can be returned.

[0055] 4, The return frame is an acknowledgement (ACK) frame carrying return information,

[0056] The ACK frame can also be used to indicate the return of TXOP. When the sender is the AP of Wifi8 or the AP supports multi-AP cooperation or the AP is a member of the multi-AP cooperation set, the ACK frame can be sent as a signal to return the TXOP, and the specific process is similar to the CF-end frame, which will not be described here.

[0057] The following will illustrate the specific way of extending the buffer status report polling / buffer status report (BSRP / BSR) frame exchange mechanism to the coordination time division multiple access (C-TDMA) mechanism in multi-AP cooperation,

[0058] In one example, in the frame exchange process of buffer status report polling / buffer status report using time division multiple access technology, when as a transmission opportunity holder, a buffer status report polling frame for inquiring low latency service information is sent to each transmission opportunity waiters in the multi-AP cooperation set, when as a transmission opportunity waiter, after receiving the buffer status report polling frame for inquiring low latency service information, low latency service information is generated according to the low latency service existing in the station device itself or the station device associated with the station device itself, and a buffer status report frame carrying the low latency service information is sent to the transmission opportunity holder. For example:

[0059] As shown in Figure 6 Sharing AP1 (BSS1) sends a buffer status report polling (BSRP) frame to Shared AP1 (BSS2) and Shared AP2 (BSS3) in the multi-AP cooperation set. In this BSRP frame, LL-Poll information is contained, which is used to inquire whether Shared AP1 and Shared AP2 have low latency services to be transmitted. After receiving the BSRP frame, Shared AP1 (BSS2) and Shared AP2 (BSS3) feed back a buffer status report (BSR) frame to feed back the buffer information of the services to be transmitted. If there is low latency service to be transmitted, for example, Shared AP2 (BSS3) in the figure, the indication of the low latency service is carried in the BSR frame, and the buffer information of the low latency service is reported. After receiving the BSR frame fed back by the related AP, the sharing AP decides the use of the TXOP, and informs the related AP through a trigger frame to allow it to use the TXOP. As shown in Figure 6In the example shown, the Sharing AP sends a Trigger frame to Shared AP2 to inform it that it can use the TXOP to transmit low latency traffic. After receiving the Trigger frame that allocates the TXOP to it, Shared AP2 can send a Trigger frame to the associated STA that has low latency traffic to be transmitted (in this example, the STA of BSS3 has low latency traffic to be transmitted, and if Shared AP2 itself has low latency traffic to be transmitted, it can directly transmit the low latency traffic, and this step can be omitted). After receiving the notification that it can transmit low latency traffic, the STA transmits a data packet of low latency traffic, and completes the transmission after receiving the feedback confirmation frame BA from Shared AP2. After completing the transmission of low latency traffic, Shared AP2 sends a notification frame (TXOP Return frame) to the Sharing AP to inform the Sharing AP that the transmission of low latency traffic is complete, and the TXOP can be returned. The design of the TXOP return frame is the same as described in the above embodiment, and will not be described again. The information about the LL-Poll can be defined as the LL Poll subfield in the B63 bit of the Common info field in the BSRP frame, and when LL Poll = 1, it indicates that the BSRP contains an indication of whether there is low latency traffic to be transmitted, and when LL Poll = 0, it indicates that the function of querying low latency traffic is not started. In some cases, the LL Poll subfield can also be included in the Trigger Dependent common info subfield in the Common info field. In addition, in the above steps of exchanging the BSRP / BSR frame, there can also be another form, for example, the BSRP carries the information of the LL-poll, and the Shared AP that has low latency traffic feeds back the BSR, which contains the buffer information of the low latency traffic. The Shared AP that does not have low latency traffic does not feed back the BSR. This method can reduce the signaling transmission and save the air interface resources.

[0060] Regarding the indication of the LL Notification in the BSR frame, there can be the following forms:

[0061] 1. Using the AP PS Buffer State subfield (where PS stands for Power Save) to convey the information of BSR, for example: in the AP PS Buffer State subfield in the Qos Control field in the frame, the indication of LL Notification is added, which can use the B0 reserved bit of the frame. The LL Notification is used to indicate whether there is low latency service in the buffer, when the LL Notification is configured as 1, it indicates that the current BSR frame is used to indicate the low latency service related buffer information. When the LL Notification is configured as 0, it indicates that the current AP has no low latency service to be sent. In addition, for the quality of service null data (Qos null) frame, the LL Notification can also be indicated by the reserved bit (Bit 7) in the Qos Control field.

[0062] 2. Using the BSR control subfield BSR control subfield to convey the information of BSR, for example:

[0063] (1) The BSR control subfield in the buffer status report frame (BSR control subfield) can use the adjacent channel interference bitmap subfield and the incremental transmission identifier subfield to express the low latency service information, specifically:

[0064]

[0065] The format of the buffer status report control subfield is shown in Table 4: wherein the access category index bitmap subfield (ACI Bitmap, ACI: Access Category Index) is a bitmap indicating the current available commands, the delta transmission identifier subfield (Delta TID) is a transaction identifier (TID) indicating the type of the ACI command. The Queue Size High and Queue Size All fields are used to indicate the maximum or all sizes or maximum or all remaining spaces of the specific queue. The ACI High is usually used to indicate the maximum number of ACI commands that can be temporarily stored. The scaling factor is a scaling factor or a scaling factor. Here is the structure of the BSR control subfield, which can reuse the conventional structure, but set the ACI Bitmap subfield and the Delta TID subfield to 0 to implicitly express the LL notification. Of course, other specific values can also be used to express the existence of low-latency services, such as ACI Bitmap = 0, Delta TID subfield = 1 or 2; or ACI Bitmap = 1, Delta TID subfield = 2 or 3; or ACI Bitmap = 2, Delta TID subfield = 3. Correspondingly, the buffer information of the low-latency service should be included in the Queue Size All subfield.

[0066] (2) Design a new BSR control subfield to convey the information of BSR, specifically: define a new low-latency service control ID (Control ID) in the A-control subfield (A-Control subfield) in the HT control field (HT Control field, wherein HT is the abbreviation of High Throughput, which means high channel). One of the existing reserved bits can be used, such as 7-14. This new frame can be called low-latency buffer status report (LowLatency Buffer Status Report, abbreviated as LL-BSR) frame, but this subfield only reports the buffer information of the low-latency service. In other words, the reserved bit of the buffer status report frame carries the low-latency service control ID, and the frame carrying the low-latency service control ID is only used to report the low-latency service information;

[0067] (3) Convey the information of BSR through a specific wireless access control (abbreviated as AC) category, for example:

[0068] If the low latency traffic is classified into a specific AC category, there is no need to increase the indication of the LLNotification, because the buffer data information corresponding to different AC categories will be reported in the BSR report. In other words, when the low latency traffic is classified into a specific radio access control category, the buffer status report frame sent to the transmission opportunity holder carries the buffer data information corresponding to different radio access control categories respectively. The specific BSR frame type can be a Qos null frame, a Qos data frame, or a management frame (Management frame), but needs to include at least one field containing BSR information in 1-4 above, and if multiple fields are included, the information needs to be consistent. In addition, the BSR can also carry other low latency traffic related information indications, such as adding timing information of low latency traffic, such as duration, acceptable maximum delay, emergency level, priority and other related information, so as to better coordinate between APs.

[0069] The technical features mentioned above can not only be applied to the Coordinated-FDMA strategy, but also be applied to other multi-AP cooperation mechanisms, such as coordinated spatial reuse (C-SR, full name Coordinated Spatial reuse). In the coordinated spatial reuse strategy, the mechanism of exchanging MU-RTS / CTS or BSRP / BSR frames can also be used to obtain information about which AP has low latency traffic to be transmitted. The design of MU-RTS / CTS and BSRP / BSR frames will not be repeated here. In an example, after receiving the low latency traffic information, when the coordinated spatial reuse supports auxiliary processing of low latency traffic, the related parameters of the device with low latency traffic and the AP device in the multi-AP cooperation set are adjusted according to the coordinated spatial reuse strategy; wherein the related parameters of the device with low latency traffic include one or any combination of the following: spatial reuse threshold, transmission power upper limit, working mode, interaction team information, working state information, and state information corresponding to the multi-AP cooperation group. Specifically:

[0070] After obtaining the information of low latency traffic to be transmitted by the relevant AP, in the OBSS PD-based spatial reuse mode, the Sharing AP or the Coordinator AP can send a Trigger frame to adjust the OBSS PD level, the upper limit of transmission power, the operating mode (such as the capability mode or the operating mode) and the like of the Shared AP or the Coordinated AP. In the PSR mode, the Sharing AP or the Coordinator AP can send a PSR opportunity for low latency traffic to the Shared AP or the Coordinated AP having low latency traffic to be processed.

[0071] In addition, the MU-RTS / CTS or BSRP / BSR frame exchange mechanism mentioned above can also be applied to the stage of forming the multi-AP cooperation mechanism, for example:

[0072] 1) Obtain, through the MU-RTS / CTS or BSRP / BSR frame exchange mechanism, information such as whether the surrounding AP supports multi-AP cooperation, which mode of multi-AP cooperation is supported, such as coordinated spatial reuse, coordinated FDMA, coordinated beamforming, coordinated r-TWT, joint transmission (i.e., Coordinated spatial reuse, Coordinated-FDMA, Coordinated Beamforming, Coordinated r-TWT, Joint transmission) and the like.

[0073] 2) Obtain, through the MU-RTS / CTS or BSRP / BSR frame exchange mechanism, whether the relevant AP agrees to join the multi-AP cooperation set.

[0074] 3) Obtain the current working state information of the relevant APs through the MU-RTS / CTS or BSRP / BSR frame exchange mechanism, including but not limited to the following information: Capability mode, 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, i.e., number of supported receiving spatial streams, and / or number of supported transmitting spatial streams), MCS (Modulation and Coding Scheme), coding mode, code rate, whether to support multi-RU scheduling, data rate, PPDU format (Physical Protocol Data Unit), and data packet size, etc., which are important factors affecting network performance. dRU (Dynamic Resource Unit) related parameters, seamless roaming, channel access (or non-primary channel access).

[0075] After the multi-AP cooperation group is formed, if the working environment or other factors change, the state of the multi-AP cooperation set can also be modified through the MU-RTS / CTS or BSRP / BSR frame exchange mechanism, for example, to inquire whether there are relevant APs to exit the multi-AP cooperation set. The design of the MU-RTS / CTS and BSRP / BSR frames will not be described here.

[0076] In the embodiment, the access point devices that are also in the mechanism of multi-AP cooperative transmission, when acting as a transmission opportunity holder, send a multi-user request to send frame to each transmission opportunity waiter in the multi-AP cooperation set to inquire low-latency service information, and determine the allocation of the transmission opportunity through the clear to send frame carrying the low-latency service information fed back by each transmission opportunity waiter; when acting as a transmission opportunity waiter, after receiving the multi-user request to send frame, generate low-latency service information according to the low-latency service existing in itself or the station devices associated with itself, and send a clear to send frame carrying the low-latency service information to the transmission opportunity holder. Through reasonable allocation of the transmission opportunity to meet the actual needs of current low-latency service processing, the characteristics of multi-AP cooperation and low-latency service are fully integrated, and efficient and stable transmission of low-latency service in the wireless network is realized.

[0077] The step division of the above method is only for the purpose of clear description, and in implementation, one step can be combined or some steps can be split and decomposed into multiple steps, as long as the same logical relationship is included, and all are within the protection scope of the present application; adding irrelevant modifications or introducing irrelevant designs in the algorithm or flow, but not changing the core design of the algorithm and flow, are within the protection scope of the present application.

[0078] Each module involved in the embodiment is a logic module. In actual application, one logic unit can be one physical unit, or a part of one physical unit, or a combination of multiple physical units. In addition, in order to highlight the innovative part of the application, units not closely related to solving the technical problems proposed in the application are not introduced in the embodiment, but this does not mean that there are no other units in the embodiment.

[0079] Another embodiment of the application relates to an access point, as shown in the accompanying drawings, comprising at least one processor 501; and a memory 502 connected with the at least one processor in communication; wherein the memory 502 stores instructions executable by the at least one processor 501, and the instructions are executed by the at least one processor 501 to enable the at least one processor 501 to perform the low-latency service transmission method as described above. Figure 7

[0080] The memory 502 and the processor 501 are connected in a bus manner, the bus can include any number of interconnected buses and bridges, and the bus connects one or more processors 501 and various circuits of the memory 502 together. The bus can also connect various other circuits such as peripheral devices, voltage stabilizers, and power management circuits together, which are well known in the art, and therefore, they will not be 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, which provide 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 through an antenna, and further, the antenna also receives data and transmits the data to the processor 501.

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

[0082] Another embodiment of the application relates to a computer readable storage medium storing a computer program. The computer program is executed by the processor to implement the method embodiments described above.

[0083] ​That is, a person skilled in the art can understand that all or part of the steps in the above-mentioned embodiment methods can be completed by instructing relevant hardware through a program stored in a storage medium, including a plurality of instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0084] A person of ordinary skill in the art can understand that the above-mentioned embodiments are specific embodiments for implementing the present application, and in actual applications, various changes can be made in form and details without departing from the spirit and scope of the present application.

Claims

1. A low-latency service transmission method, characterized in that, Access point devices used in multi-AP cooperative transmission mechanisms include: When acting as a transmission opportunity holder, the allocation of transmission opportunities is determined by sending multi-user request transmission frames to each transmission opportunity waiting party in the multi-AP cooperative set to inquire about low-latency service information, and by receiving clear transmission frames carrying the low-latency service information from each of the transmission opportunity waiting parties. When acting as a transmission opportunity waiter, after receiving the multi-user request to send frame, it generates low-latency service information based on the low-latency services existing in itself or its associated site equipment, and sends the clearing send frame carrying the low-latency service information to the transmission opportunity holder. Wherein, the indication for querying the low-latency service information in the multi-user request sending frame is carried by the reserved bit in the multi-user request sending frame; or, the trigger type subfield in the public information field of the multi-user request sending frame contains an indication field for querying low-latency service information. The low-latency service information is carried by a physical layer preamble. The physical layer preamble contains an identifier indicating the presence of a low-latency service, which indicates that the current device contains a low-latency service to be transmitted. The transmission opportunity holder determines the allocation of the transmission opportunity after detecting the identifier.

2. The low-latency service transmission method according to claim 1, characterized in that, The low-latency service information in the cleared transmission frame is also carried by the power management subfield in the frame control field; or, the low-latency service information in the cleared transmission frame is also carried by the control frame extension field in the frame control field.

3. The low-latency service transmission method according to claim 1, characterized in that, The method further includes: When acting as a transmission opportunity waiting party, after receiving the multi-user request to send frame, if the low-latency service is not available in itself or its associated site equipment, it will not send back the clearing frame.

4. The low-latency service transmission method according to claim 1, characterized in that, The method further includes: When acting as the holder of a transmission opportunity, after deciding on the allocation of the transmission opportunity, configuration information for allocating the transmission opportunity is generated, and a trigger frame carrying the configuration information is sent to the transmission opportunity waiting party. The configuration information includes: the user of the right to use the transmission opportunity and the validity period of the right to use the transmission opportunity; When acting as a waiting party for a transmission opportunity, after obtaining the right to use the transmission opportunity, it sends a trigger frame carrying notification information to each site device that has the low-latency service and is associated with itself. The notification information is used to inform the site equipment that it can utilize the right to use the transmission opportunity to transmit the low-latency service.

5. The low-latency service transmission method according to claim 4, characterized in that, The method further includes: When acting as a waiting party for a transmission opportunity, the transmission opportunity shall be returned to the holder of the transmission opportunity after the low-latency service existing in its own or its associated site equipment has been transmitted. The step of returning the transmission opportunity to the holder of the transmission opportunity includes: Upon the expiration of the right to use the transmission opportunity, the transmission opportunity will be automatically returned to the holder of the transmission opportunity; or, Send a return frame carrying return information to the holder of the transmission opportunity to return the transmission opportunity to the holder of the transmission opportunity; The return frame is either a block acknowledgment frame carrying return information in the reserved bits, or an ACK frame carrying return information, or a CF-End frame carrying return information.

6. The low-latency service transmission method according to claim 1, characterized in that, The method further includes: During the frame exchange of buffer status report polling / buffer status report using time division multiple access technology, when acting as a transport opportunity holder, a buffer status report polling frame for querying low-latency service information is sent to each transport opportunity waiting party in the multi-AP cooperative set. In the frame exchange process of buffer status report polling / buffer status report using time division multiple access technology, when acting as a transmission opportunity waiting party, after receiving the buffer status report polling frame used to inquire about low-latency service information, it generates the low-latency service information based on the low-latency services existing in itself or its associated site equipment, and sends a buffer status report frame carrying the low-latency service information to the transmission opportunity holder.

7. The low-latency service transmission method according to claim 6, characterized in that, The buffer status report control subfield in the buffer status report frame uses the access category index bitmap subfield and the incremental transmission identifier subfield to express the low-latency service information; or, The reserved bits of the buffer status report frame carry a low-latency service control ID, and the frame carrying the low-latency service control ID is only used to report the low-latency service information. Sending a buffer status report frame carrying the low-latency service information to the transmission opportunity holder includes: When the low-latency service is classified into a specified radio access control category, the buffer status report frame sent to the transmission opportunity holder carries buffer data information corresponding to each of the different radio access control categories.

8. The low-latency service transmission method according to claim 1, characterized in that, The method further includes: Upon receiving the low-latency service information, when the collaboration space reuse strategy supports auxiliary operations on the low-latency service information, the relevant parameters of the device containing the low-latency service and the AP devices in the multi-AP collaboration set are adjusted according to the collaboration space reuse strategy. The relevant parameters of the device with the low latency service include one of the following or any combination thereof: spatial multiplexing threshold, transmission power limit, working mode, interaction clustering information, working status information, and status information corresponding to the multi-AP cooperation set.

9. An access point, 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 to enable the at least one processor to perform 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 the processor, it implements the low-latency service transmission method according to any one of claims 1 to 8.

Images