WO2024254782A1 - 无线通信的方法及设备 - Google Patents

无线通信的方法及设备 Download PDF

Info

Publication number
WO2024254782A1
WO2024254782A1 PCT/CN2023/100190 CN2023100190W WO2024254782A1 WO 2024254782 A1 WO2024254782 A1 WO 2024254782A1 CN 2023100190 W CN2023100190 W CN 2023100190W WO 2024254782 A1 WO2024254782 A1 WO 2024254782A1
Authority
WO
WIPO (PCT)
Prior art keywords
sta
txop
mac frame
stas
group
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/100190
Other languages
English (en)
French (fr)
Other versions
WO2024254782A9 (zh
Inventor
高宁
张军
罗朝明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202380099196.1A priority Critical patent/CN121359578A/zh
Priority to PCT/CN2023/100190 priority patent/WO2024254782A1/zh
Priority to EP23941019.4A priority patent/EP4730896A1/en
Publication of WO2024254782A1 publication Critical patent/WO2024254782A1/zh
Publication of WO2024254782A9 publication Critical patent/WO2024254782A9/zh
Priority to US19/411,639 priority patent/US20260095944A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access
    • H04W74/06—Scheduled access using polling

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a method and device for wireless communications.
  • EDCA Enhanced Distributed Channel Access
  • the embodiments of the present application provide a method and device for wireless communication, which introduces a STA grouping function in channel contention, makes TXOP allocation more efficient, and increases the frequency of use of multi-user uplink (MU UL), thereby reducing the delay of uplink and downlink data transmission and alleviating delay jitter.
  • a wireless communication method which is applied to a station STA, where the STA has uplink data to be transmitted, and the method includes:
  • the STA sends a first media access control MAC frame; wherein the first MAC frame is used to compete for a channel, and a channel competition result corresponding to the first MAC frame is associated with the grouping information of the STA.
  • a wireless communication method which is applied to an access point AP, and the method includes:
  • the AP receives a first media access control MAC frame sent by a station STA;
  • the first MAC frame is used to compete for a channel, and a channel competition result corresponding to the first MAC frame is associated with the grouping information of the STA, and the STA has uplink data to be transmitted.
  • a STA is provided, which is used to execute the method in the first aspect.
  • the STA includes a functional module for executing the method in the above-mentioned first aspect.
  • an AP is provided for executing the method in the second aspect.
  • the AP includes a functional module for executing the method in the above second aspect.
  • a STA comprising a processor and a memory; the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the STA executes the method in the above-mentioned first aspect.
  • an AP comprising a processor and a memory; the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the AP executes the method in the above-mentioned second aspect.
  • a device for implementing the method in any one of the first to second aspects above.
  • the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to second aspects described above.
  • a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to second aspects above.
  • a computer program product comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above.
  • a computer program which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects above.
  • the STA grouping function is introduced in the channel contention, the allocation of TXOP is more efficient, and the usage frequency of multi-user uplink (MU UL) is increased, thereby reducing the delay of uplink and downlink data transmission and alleviating delay jitter.
  • FIG1 is a schematic diagram of a communication system architecture applied in an embodiment of the present application.
  • Figure 2 is a schematic diagram of the QoS STA and Non-QoS STA channel access priority and timing provided by this application.
  • FIG3 is a schematic diagram of the timing relationship of the EDCA mechanism provided in the present application.
  • Figure 4 is a schematic diagram of the SU UL provided in this application.
  • Figure 5 is a schematic diagram of the MU UL provided in this application.
  • Figure 6 is a schematic diagram of the NDP Feedback Report mechanism provided in this application.
  • Figure 7 is a schematic diagram of the frame format of the NFRP Trigger frame provided in this application.
  • Figure 8 is a schematic diagram of the frame format of the common information (Common Info) field provided in this application.
  • Figure 9 is a schematic diagram of the frame format of the user information list (User Info List) field provided in this application.
  • FIG10 is a schematic diagram of the HE TB feedback NDP format provided by the present application.
  • FIG. 11 is a schematic diagram of the probability of a STA or AP obtaining a TXOP in a channel competition provided by the present application.
  • FIG. 12 is a schematic diagram of three stages of channel contention provided according to an embodiment of the present application.
  • FIG13 is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a G-RTS frame provided according to an embodiment of the present application.
  • Figures 15 to 20 are schematic diagrams of channel contention and data reception and/or transmission provided according to embodiments of the present application.
  • Figure 21 is a schematic block diagram of a STA provided according to an embodiment of the present application.
  • Figure 22 is a schematic block diagram of an AP provided according to an embodiment of the present application.
  • Figure 23 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • FIG. 24 is a schematic block diagram of a device provided according to an embodiment of the present application.
  • Figure 25 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • the wireless communication system may include: an access point (Access Point, AP) and a station (Station, STA).
  • AP Access Point
  • STA station
  • AP can be called AP STA, that is, in a sense, AP is also a STA. In some scenarios, STA can be called non-AP STA.
  • STA may include AP STA and Non-AP STA.
  • the communication in the communication system may be communication between AP and Non-AP STA, communication between Non-AP STA and Non-AP STA, or communication between STA and peer STA.
  • Peer STA may refer to a device that communicates with the STA peer.
  • peer STA may be AP or Non-AP STA.
  • AP is equivalent to a bridge connecting wired network and wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to Ethernet.
  • AP devices can be terminal devices (such as mobile phones) or network devices (such as routers) with wireless fidelity (Wireless-Fidelity, Wi-Fi) chips.
  • the role of STA in the communication system is not absolute.
  • the mobile phone when a mobile phone is connected to a router, the mobile phone is a Non-AP STA.
  • the mobile phone plays the role of an AP.
  • AP and Non-AP STA can be devices used in Internet of Vehicles, IoT nodes and sensors in Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.
  • IoT Internet of Things
  • Non-AP STA can support 802.11be.
  • Non-AP STA can also support 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a and other current and future 802.11 family wireless LAN standards.
  • the AP may be a device supporting the 802.11be standard.
  • the AP may also be a device supporting various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.
  • STA can be a mobile phone (Mobile Phone), tablet computer (Pad), computer, virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control (industrial control), set-top box, wireless device in self-driving, vehicle-mounted communication equipment, wireless device in remote medical, wireless device in smart grid (smart grid), wireless device in transportation safety (transportation safety), wireless device in smart city (smart city) or wireless device in smart home (smart home), wireless communication chip, ASIC (Application Specific Integrated Circuit), SOC (System on Chip), etc. that supports WLAN/WIFI technology.
  • the frequency bands supported by WLAN technology may include but are not limited to: low frequency bands (2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (45 GHz, 60 GHz).
  • the station and the access point support multi-band communication. For example, communicating on the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz bands at the same time, or communicating on different channels of the same band (or different bands) at the same time, improves the communication throughput and/or reliability between devices.
  • a device is generally called a multi-band device, or a multi-link device (MLD), sometimes also referred to as a multi-link entity or a multi-band entity.
  • MLD multi-link device
  • a multi-link device can be an access point device or a station device. If the multi-link device is an access point device, the multi-link device contains one or more APs; if the multi-link device is a station device, the multi-link device contains one or more non-AP STAs.
  • a multi-link device including one or more APs can be called an Access Point Multi-Link Device (AP MLD), and a multi-link device including one or more non-AP STAs can be called a Non-AP Multi-Link Device (Non-AP Multi-Link Device). Device, Non-AP MLD).
  • AP MLD Access Point Multi-Link Device
  • Non-AP Multi-Link Device Non-AP Multi-Link Device
  • an AP may include multiple APs
  • a Non-AP may include multiple STAs
  • multiple links may be formed between the APs in the AP and the STAs in the Non-AP
  • data communication may be performed between the APs in the AP and the corresponding STAs in the Non-AP through corresponding links.
  • the AP is a device deployed in a wireless local area network to provide wireless communication functions for STA.
  • the site may include: User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent or user device.
  • the site can also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and the embodiments of the present application are not limited to this.
  • both the station (STA) and the access point (AP) support the IEEE 802.11 standard.
  • the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
  • the "at least one or at least one” mentioned in the embodiments of the present application can mean “one or more”, and the "positive integer” mentioned in the embodiments of the present application can mean “1, 2, 3... and other values”, and the “non-negative integer” mentioned in the embodiments of the present application can mean “0, 1, 2, 3... and other values”, and the “integer” mentioned in the embodiments of the present application can mean “..., -3, -2, -1, 0, 1, 2, 3,... and other values”, which can be replaced with any possible value based on the requirements of the embodiment.
  • corresponding may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
  • pre-definition or “pre-configuration” can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including STA and network equipment), and the present application does not limit the specific implementation method.
  • pre-definition can refer to what is defined in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, for example, it may include a WiFi protocol and related protocols used in future WiFi communication systems, and the present application does not limit this.
  • EDCA Enhanced Distributed Channel Access
  • the IEEE 802.11e standard defines a channel access mechanism with enhanced quality of service (QoS): EDCA.
  • QoS quality of service
  • EDCA defines four different access categories (AC), namely AC_VO, AC_VI, AC_BE and AC_BK. As shown in Table 1, different ACs have different parameter settings, so they have different priorities when accessing the medium.
  • CW min indicates the minimum value of the contention window upper limit. The smaller the CW min, the higher the priority.
  • CW max indicates the maximum value of the contention window upper limit. The smaller the CW max, the higher the priority.
  • Transmission Opportunity (TXOP) Limit indicates the maximum duration of channel occupation
  • AIFSN Arbitration Interframe Space Number
  • Figure 2 shows a schematic diagram of QoS STA using four AC access channels. It can be seen that due to the different AIFSN parameters, the priorities of AC_VO, AC_VI, AC_BE, and AC_BK gradually decrease.
  • Figure 2 also shows the timing diagram of Non-QoS STA access channel, which is the traditional DCF mechanism.
  • the DCF mechanism contains two situations. One is that STA can send after detecting that the channel of priority interframe space (PIFS) is idle, and the other is that it can send after detecting that the channel of distributed interframe space (DIFS) is idle and backing off.
  • PIFS priority interframe space
  • DIFS distributed interframe space
  • the standard stipulates that the former can generally only be used to send some frames with special functions, such as beacon frames, because such frames need to have a higher sending priority; in addition, STA uses the latter to access the channel.
  • QoS STA can be a STA that supports the QoS EDCA mechanism
  • Non-QoS STA can be a STA that does not support the QoS EDCA mechanism
  • PIFS priority interframe space
  • DIFS distributed inter-frame spacing
  • AIFS arbitration interframe space
  • SIFS short interframe space
  • PIFS SIFS+1 ⁇ aSlotTime.
  • DIFS SIFS+2 ⁇ aSlotTime.
  • AIFS SIFS+AIFSN ⁇ aSlotTime.
  • single-user uplink transmission single user uplink, SU UL
  • single-user uplink transmission multi-user uplink, MU UL
  • the SU UL process is shown in Figure 4, which includes 1 AP and 3 STAs (Non-AP STAs). Each STA needs to compete for the channel through the EDCA mechanism first, and then send uplink (UL) low latency (LL) data and receive an ACK frame. Multiple STAs (Non-AP STAs) obtain TXOPs and send uplink data one by one in a serial manner. This SU UL uplink data transmission method will cause large uplink transmission delays and delay jitters, because STAs may not be able to compete for TXOPs in time.
  • MU UL The process of MU UL is shown in Figure 5, which includes 1 AP and n STAs (Non-AP STA).
  • the AP competes for TXOP through the EDCA mechanism.
  • the AP sends a trigger frame to each STA to allocate the resources required for each STA's uplink parallel transmission.
  • the n STAs (Non-AP STA) simultaneously send high-efficiency trigger-based physical layer protocol data units (HE TB PPDU) to transmit uplink data according to the allocated resources.
  • HE TB PPDU high-efficiency trigger-based physical layer protocol data units
  • the AP replies with a multi-STA block acknowledgment (Multi-STA BlockAck) frame to n STAs to confirm whether the transmission is successful.
  • This MU UL uplink transmission method can realize parallel uplink transmission (i.e., the time domain resources occupied by the uplink transmission are the same, but the frequency domain and/or spatial domain resources are different), and has higher transmission efficiency than SU UL.
  • NDP Null Data Physical Protocol Data Unit
  • the IEEE 802.11ax standard defines a MU UL detection mechanism that enables the AP to detect the STA (Non-AP STA) that needs to allocate resources before sending a trigger frame.
  • the MU UL detection mechanism in IEEE 802.11ax also defines two related frame structures: Null Data Physical Protocol Data Unit Feedback Report Polling (NFRP) trigger frame and High Efficiency Trigger Based Feedback Null Data Physical Protocol Data Unit (HE TB feedback NDP).
  • NFRP Null Data Physical Protocol Data Unit Feedback Report Polling
  • HE TB feedback NDP High Efficiency Trigger Based Feedback Null Data Physical Protocol Data Unit
  • the AP sends NFRP Trigger frames to all Non-AP STAs, triggering Non-AP STAs to send HE TB feedback NDP.
  • the AP can learn which Non-AP STAs need to participate in subsequent MU UL transmission by parsing HE TB feedback NDP.
  • the AP sends a NFRP Trigger frame to some Non-AP STAs, triggering the Non-AP STAs to send HE TB feedback NDP.
  • the AP can know which Non-AP STAs need to participate in the subsequent MU UL transmission, and then reasonably allocate resources to the Non-AP STAs in the subsequent Trigger frames, thereby completing the MU UL transmission.
  • the frame format of the NFRP trigger frame is shown in Figure 7, where the format of the common information (Common Info) field is shown in Figure 8, and the format of the user information list (User Info List) field is shown in Figure 9.
  • the NFRP trigger frame may include the following fields: frame control (occupying 2 bytes), duration (occupying 2 bytes), receiving address (Receiving Address, RA) (occupying 6 bytes), sending address (Transmission Address, TA) (occupying 6 bytes), common information (Common Info) (occupying 8 or more bytes), user information list (User Info list) (occupying a variable number of bytes), padding (occupying a variable number of bytes), frame check sequence (Frame Check Sequence, FCS) (occupying 4 bytes).
  • the Common Info field may include the following fields: Trigger Type (occupies 4 bits), Uplink Length (UL Length) (occupies 12 bits), More Trigger Frames (Trigger Frame, TF) (occupies 1 bit), Carrier Sense (Carrier Sense, CS) required (occupies 1 bit), Uplink Bandwidth (BandWidth, BW) (occupies 2 bits), Guard Interval (Guard Interval, GI) and High Efficiency Long Training Field (High Efficiency Long Training Field, HE-LTF) type (occupies 2 bits), Multiple Users multiple-in multiple-out (Multiple Users multiple-in multiple-out, MU-MIMO) HE-LTF mode (occupies 1 bit), Number of HE-LTF symbols and midamble period (occupies 3 bits), and the number of HE-LTF symbols.
  • Trigger Type occupies 4 bits
  • Uplink Length UL Length
  • CS Carrier Sense
  • CS Uplink Bandwidth
  • uplink space-time block code Space Time Block Code, STBC
  • LDPC low-density parity check
  • AP transmit power occupies 6 bits
  • Pre-FEC pre-forward error correction
  • Pre-FEC pre-forward error correction
  • AP transmit power occupies 6 bits
  • Pre-FEC pre-forward error correction
  • Packet Extension, PE packet extension
  • disambiguation occupies 1 bit
  • uplink spatial reuse occupies 16 bits
  • Doppler occupies 1 bit
  • uplink high efficiency signal field A2 High Efficiency SINGAL field-A2, HE-SIG-A2 reserved (occupies 9 bits), reserved (occupies 1 bit), trigger-related public information (occupies a variable number of bits).
  • the uplink bandwidth (UL BW) field indicates the bandwidth of the NDP feedback report response;
  • the UL STBC, LDPC Extra Symbol Segment, Pre-FEC Padding Factor, PE Disambiguity, UL Spatial Reuse and Doppler fields are reserved;
  • the Number Of HE-LTF Symbols and Midamble Periodicity fields indicate the number of HE-LTF symbols present in the NDP feedback report response and are set to 1;
  • the GI And HE-LTF Type field is set to 2; the Trigger Dependent Common Info field does not exist.
  • the user information list (User Info List) field may include the following fields: starting AID (occupying 12 bits), reserved (occupying 9 bits), feedback type (occupying 4 bits), reserved (occupying 7 bits), uplink target receive power (UL Target Receive Power) (occupying 7 bits), and the number of spatially multiplexed users (Number Of Spatially Multiplexed Users) (occupying 1 bit).
  • the starting AID field defines the first AID in the range of association identifiers (AIDs) that are planned to respond to the NFRP trigger frame;
  • the feedback type field indicates the type of feedback information carried by the HE TB feedback NDP;
  • the UL Target Receive Power field indicates the expected received signal power measured at the antenna connector of the AP and averaged on the antenna;
  • the Number Of Spatially Multiplexed Users field indicates the number of users in the same resource unit The number of STAs multiplexed on the same group of subcarriers in a Resource Unit (RU), encoded as the number of STAs - 1.
  • RU Resource Unit
  • HE TB feedback NDP is used to carry NDP feedback report information, and its frame format is shown in Figure 10.
  • HE TB feedback NDP includes the following fields: legacy short training field (L-STF), legacy long training field (L-LTF), legacy signal (L-SIG), repeat legacy signal (RL-SIG), High Efficiency Signal A (HE-SIG-A), High Efficiency short training field (HE-STF), High Efficiency long training field (HE-LTF), and packet extension (PE).
  • L-STF legacy short training field
  • L-LTF legacy long training field
  • L-SIG legacy signal
  • R-SIG repeat legacy signal
  • HE-SIG-A High Efficiency Signal A
  • HE-STF High Efficiency short training field
  • HE-LTF High Efficiency long training field
  • PE packet extension
  • the NDP format uses the HE TB PPDU format, but there is no data field, the PE field duration is 0 microseconds ( ⁇ s), there are 2 symbols of type 4x HE-LTF, and the guard interval (GI) used is 3.2 microseconds. Among them, the duration of 1x HE-LTF symbol is 3.2 microseconds, the duration of 2x HE-LTF symbol is 6.4 microseconds, and the duration of 4x HE-LTF symbol is 12.8 microseconds. The guard interval is not calculated in the duration.
  • RU_TONE_SET_INDEX different RU tone set indexes in the HE-LTF field are used to identify the AIDs and feedback information (FEEDBACK_STATUS) of different Non-AP STAs, where tone (TONE) can also be referred to as a subcarrier.
  • tone TONE
  • HE-LTF subcarrier mapping relationship in the HE TB feedback NDP can be shown in Table 2.
  • each RU_TONE_SET_INDEX corresponds to a Non-AP STA (AID).
  • each RU_TONE_SET_INDEX corresponds to two Non-AP STAs (AIDs), and these two Non-AP STAs are distinguished by different pre-assigned encoding matrices.
  • the Duration/ID field located in the Media Access Control (MAC) frame header is used to set the Network Allocation Vector (NAV) for the STA that receives the MAC frame.
  • NAV Network Allocation Vector
  • NAV duration settings for TXOP initiated under the EDCA mechanism.
  • Single Protection the time length indicated by NAV only includes the next data, management or response frame sent plus any additional overhead frames
  • Multiple Protection NAV can indicate that the time length can include multiple frames sent and received next.
  • WIFI Internet of Things
  • SU UL requires the sending station to obtain TXOP
  • MU UL requires the AP to obtain TXOP, otherwise, the station cannot send uplink data.
  • the probability of a station obtaining TXOP and the probability of AP obtaining TXOP will gradually decrease with the increase of the number of all stations, and gradually converge to a smaller fixed value.
  • the probability of STA or AP obtaining TXOP in a channel competition can be shown in Figure 11. Therefore, when the number of stations is large, the probability of the station executing SU UL and the AP executing MU UL will be very small, resulting in the delay of uplink data, causing large delay and delay jitter.
  • the present application proposes an EDCA enhancement scheme with STA grouping function, which introduces the STA grouping function in channel competition, makes the allocation of TXOP more efficient, and increases the usage frequency of multi-user uplink (MU UL), thereby reducing the delay of uplink and downlink data transmission and alleviating delay jitter.
  • the embodiment of the present application enhances the EDCA mechanism to reduce the transmission delay of uplink data in industrial scenarios.
  • the enhanced EDCA scheme includes four stages as shown in Figure 12: group initialization, media contention, media grant, and media use.
  • group initialization stage the AP allocates STAs with similar service cycles to different STA groups based on the statistical service rules of the STAs.
  • media contention stage STAs that need to send low-latency services will send specific frames according to the rules to compete for the ownership of TXOP.
  • the AP will reply with different frames based on the results of the MU UL detection, thereby granting TXOP to a certain STA or the AP itself.
  • the STA that obtains the TXOP needs to execute a specific transmission process according to the rules.
  • FIG13 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application.
  • the wireless communication method 200 may be interactively executed by a STA and an AP.
  • the STA may be a STA (Non-AP STA) as shown in FIG1
  • the AP may be an AP as shown in FIG1 , wherein the STA has uplink data to be transmitted.
  • the wireless communication method 200 may include at least part of the following contents:
  • the STA sends a first MAC frame; wherein the STA has uplink data to be transmitted, the first MAC frame is used to compete for a channel, and a channel competition result corresponding to the first MAC frame is associated with the grouping information of the STA;
  • the AP receives the first MAC frame sent by the STA.
  • FIG13 shows the steps or operations of the wireless communication method 200, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG13.
  • a "field” may also be referred to as a "field” or a "subfield.”
  • a field may occupy one or more bytes (byte/octet), or a field may occupy one or more bits (bit).
  • “medium” may also be referred to as “channel” and they may be interchangeable.
  • the AP can choose to force the TXOP to be obtained and then execute the more efficient MU UL process, thereby quickly meeting the uplink data transmission requirements of multiple STAs with similar occurrence cycles and reducing delays.
  • the uplink data described in the embodiments of the present application at least includes uplink delay-sensitive data.
  • the uplink data described in the embodiments of the present application may also include other data, such as non-delay-sensitive data.
  • delay-sensitive data may also be referred to as low-latency (LL) data, which is not limited in the embodiments of the present application.
  • the first MAC frame is a group request to send (Grouping-request to send, G-RTS) frame.
  • the first MAC frame may also be other frames, or the first MAC frame may be a newly defined MAC frame.
  • the first MAC frame is a G-RTS frame, which can be shown in FIG. 14.
  • the protocol version field indicates the version of the MAC frame.
  • the frame type field the value of 1 indicates that the frame is a control frame.
  • the frame subtype field the value of 15 indicates that the first MAC frame is a newly defined G-RTS frame.
  • the To DS field and the From DS field the values are both 0 and have no meaning.
  • the power management field indicates the power management mode of the STA.
  • the more data field indicates that there is data to be sent in the cache of a STA in the energy-saving mode.
  • the high throughput control field indicates whether the frame contains a high throughput control field.
  • the duration field indicates the value of the network allocation vector (NAV), which is used to protect the medium from being preempted.
  • Receive address field The address of the STA that receives the frame.
  • Transmit address field The address of the STA that sends the frame.
  • Frame check field Checks whether the control field of the frame is transmitted correctly.
  • one or more STAs associated with the same AP may form a STA group, and one or more STA groups may exist simultaneously, and each STA group has a unique identifier: STA group ID.
  • the AP pre-allocates m STA groups, or the physical AP MLD to which the AP belongs pre-allocates m STA groups, or the virtual AP MLD to which the AP belongs pre-allocates m STA groups.
  • STAs with the same or similar service cycles belong to different STA groups among the m STA groups.
  • the AP can allocate STAs with similar service cycles to different STA groups based on the statistical service rules of the STAs.
  • the grouping information of the STA includes but is not limited to at least one of the following:
  • the STA belongs to a STA group among the m STA groups
  • the STA belongs to a STA group among the m STA groups, an identifier of the STA group to which the STA belongs, and/or the number of STAs included in the STA group to which the STA belongs.
  • the grouping information of the STA is associated with the first field in the first MAC frame. That is, the grouping information of the STA can be obtained based on the first field in the first MAC frame. Specifically, the grouping information of the STA can be directly or indirectly obtained based on the first field in the first MAC frame.
  • the first field is a field for identifying the identity of the STA. That is, the AP can indirectly obtain the grouping information of the STA based on the first field in the first MAC frame.
  • the first field is a transmit address (TA) field or other address identification field.
  • the AP identifies the identity of the STA based on the transmit address (TA) field or other address identification field in the received first MAC frame, as shown in Figure 14, and then replies to different CTS frames based on whether the STA belongs to a certain STA group and the number of STA devices in the STA group, thereby granting TXOP to the STA or AP.
  • the first field is used to indicate the grouping information of the STA. That is, the AP can directly obtain the grouping information of the STA based on the first field in the first MAC frame.
  • the channel contention result corresponding to the first MAC frame is associated with the grouping information of the STA, including:
  • the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA; and/or,
  • the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the AP; and/or,
  • the channel contention-associated TXOP corresponding to the first MAC frame belongs to the STA.
  • the channel contention result corresponding to the first MAC frame is associated with the grouping information of the STA, including:
  • the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA; and/or,
  • the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the AP; and/or,
  • the channel contention-associated TXOP corresponding to the first MAC frame belongs to the STA.
  • the AP replies with a CTS frame to the STA, declaring that the TXOP belongs to the STA, that is, the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA.
  • the AP replies a CTS frame to the STA, declaring that the TXOP belongs to the STA, that is, the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA.
  • the AP sends a CTS-to-self frame, declaring that the TXOP belongs to the AP, that is, the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA.
  • the first threshold may be agreed upon by a protocol, or the first threshold may be configured by an AP, or the first threshold may be configured by a physical AP MLD to which the AP belongs, or the first threshold may be configured by a virtual AP MLD to which the AP belongs.
  • the TXOP used by the STA is a single protection (Single Protection) TXOP or a length-restricted multiple protection (Multiple Protection) TXOP
  • the TXOP used by the AP corresponding to the STA is a single protection (Single Protection) TXOP or a length-restricted multiple protection (Multiple Protection) TXOP.
  • STA and AP use Single Protection TXOP or length-restricted Multiple Protection TXOP.
  • the TXOP used by the STA is a single protection (Single Protection) TXOP or a length-limited multiple protection (Multiple Protection) TXOP
  • the TXOP used by the AP corresponding to the STA is a single protection (Single Protection) TXOP or a multiple protection (Multiple Protection) TXOP.
  • STA uses Single Protection TXOP or length-restricted Multiple Protection TXOP
  • AP can use any type of TXOP.
  • some or all of the STAs in the first STA group send uplink data in the TXOP after receiving the trigger frame sent by the AP.
  • the AP sends a trigger frame to some or all STAs in the first STA group, and then receives a trigger-based physical layer protocol data unit (TB PPDU) to obtain uplink data and reply with a block acknowledgment (BlockAck) frame or a multi-STA block acknowledgment (Multi-STA BlockAck) frame.
  • TB PPDU trigger-based physical layer protocol data unit
  • some or all STAs in the first STA group when the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the AP, some or all STAs in the first STA group send uplink data and receive downlink data in the TXOP after receiving the trigger frame sent by the AP.
  • the AP may receive uplink data first and then send downlink data, or may send downlink data first and then receive uplink data.
  • the AP sends a trigger frame to some or all STAs in the first STA group, then receives the TB PPDU to obtain uplink data and replies with a BlockAck frame or a Multi-STA BlockAck frame; further, when the AP uses the Multiple Protection TXOP or the Multiple Protection TXOP with limited length, if the TXOP duration is sufficient, the AP can also send downlink SU data or downlink MU data within the TXOP and receive the corresponding Ack frame or BlockAck frame. The AP can receive uplink data first and then send downlink data, or send downlink data first and then receive uplink data.
  • some or all STAs in the first STA group feedback uplink buffer status information (such as buffer status report (BSR)) after receiving the NFRP trigger frame sent by the AP, and the resources for some or all STAs in the first STA group to send uplink data in the TXOP are associated with the uplink buffer status information fed back by some or all STAs in the first STA group.
  • BSR buffer status report
  • the AP can first send an NFRP trigger frame to query the uplink low-latency cache status information (such as BSR) of some or all STAs in the relevant STA group, and then allocate resources based on this to perform MU UL transmission.
  • the uplink low-latency cache status information such as BSR
  • one or more STAs associated with the same AP may form a STA group.
  • Multiple STA groups may exist simultaneously, and each STA group has a unique identifier: STA group ID.
  • the STA that needs to send uplink data follows the EDCA mechanism to compete for the channel. If the STA allows the AP to change the grant of TXOP based on the packet information, it competes for the channel by sending a specific frame (i.e., the first MAC frame), otherwise, the STA cannot use the specific frame (i.e., the first MAC frame) to compete for the channel.
  • a specific frame i.e., the first MAC frame
  • the AP identifies the identity of the STA based on the TA field or other address identification field in the received specific frame (i.e., the first MAC frame), and then replies with different CTS frames based on whether the STA belongs to a certain STA group and the number of STAs in the STA group, thereby granting the TXOP to the STA or AP.
  • the AP replies with a CTS frame to the STA, announcing that the TXOP belongs to the STA. For another example, if the AP detects that the STA belongs to a certain STA group and the number of STAs in the STA group is less than or equal to a first threshold, the AP sends a CTS frame to the STA, announcing that the TXOP belongs to the STA.
  • the AP detects that the STA belongs to a certain STA group and the number of STAs in the STA group is greater than or equal to a first threshold, the AP sends a CTS-to-self frame, announcing that the TXOP belongs to the AP.
  • the STA and the AP must use the Single Protection TXOP or the length-restricted Multiple Protection TXOP; in another embodiment, the STA must use the Single Protection TXOP or the length-restricted Multiple Protection TXOP, and the AP can use any type of TXOP.
  • the AP in the medium use phase shown in FIG. 12 , after the AP obtains the TXOP, the AP shall send a Trigger frame to some or all STAs in the STA group, and then receive the TB PPDU to obtain the uplink data and reply with a BlockAck frame or Multi-STA BlockAck frame; further, when the AP uses Multiple Protection TXOP or Multiple Protection TXOP with limited length, if the TXOP duration is sufficient, the AP can also send downlink SU data or downlink MU data within the TXOP and receive the corresponding Ack frame or BlockAck frame. The AP can receive uplink data first and then send downlink data, or send downlink data first and then receive uplink data.
  • the STA grouping function is introduced in the channel contention, the allocation of TXOP is more efficient, and the usage frequency of multi-user uplink (MU UL) is increased, thereby reducing the delay of uplink and downlink data transmission and alleviating delay jitter.
  • Example 1 assume that a WLAN network contains 1 AP and 4 STAs (STA1, STA2, STA3, STA4). If the AP uses the Single Protection TXOP, the STAs also use the Single Protection TXOP. STA1 and STA2 belong to STA Group 1, STA3 belongs to STA Group 2, and STA4 does not belong to any STA Group. All STAs use the AC_VO access type in EDCA, and the frame interaction between the AP and the STA is shown in Figure 15.
  • STA4 first sends a G-RTS frame at the Arbitration Interframe Space (AIFS) time when the channel is idle.
  • AIFS Arbitration Interframe Space
  • the AP finds that STA4 does not belong to any STA Group, so it replies with a CTS frame to STA4 and grants TXOP to STA4.
  • STA4 receives the CTS frame sent by the AP, it finds that the receiving address of the CTS frame is its own address, so it determines that the channel competition is successful and the TXOP belongs to itself.
  • AIFS Arbitration Interframe Space
  • STA4 sends SU uplink data to the AP, and the AP replies with an Acknowledgement (Ack) frame to STA4 to confirm that the transmission is successful.
  • Ack Acknowledgement
  • Example 2 assume that a WLAN network contains 1 AP and 4 STAs (STA1, STA2, STA3, STA4). If the AP uses the Single Protection TXOP, the STAs also use the Single Protection TXOP. STA1 and STA2 belong to STA Group 1, STA3 belongs to STA Group 2, and STA4 does not belong to any STA Group. All STAs use the AC_VO access type in EDCA, and the frame interaction between the AP and the STA is shown in Figure 16.
  • STA3 first sends a G-RTS frame at the AIFS moment when the channel is idle. After receiving the G-RTS frame, AP finds that STA3 belongs to STA Group 2 and there is only one STA in STA Group 2, so it replies with a CTS frame to STA3 and grants TXOP to STA3. After STA3 receives the CTS frame sent by AP, it finds that the receiving address of the CTS frame is its own address, so it determines that the channel competition is successful and the TXOP belongs to itself. Subsequently, in STA3's TXOP, STA3 sends SU uplink data to AP, and AP replies with an Ack frame to STA3 to confirm that the transmission is successful. At this point, STA3's TXOP ends and the channel re-enters the idle state.
  • Example 3 assume that a WLAN network contains 1 AP and 4 STAs (STA1, STA2, STA3, STA4). If the AP uses the Single Protection TXOP, the STAs also use the Single Protection TXOP. STA1 and STA2 belong to Group 1, STA3 belongs to STA Group 2, and STA4 does not belong to any STA Group. All STAs use the AC_VO access type in EDCA, and the frame interaction between the AP and the STA is shown in Figure 17.
  • STA2 first sends a G-RTS frame when the channel is idle AIFS. After receiving the G-RTS frame, AP finds that STA2 belongs to STA Group 1 and there are two STAs in STA Group 2, so it replies with a CTS-to-self frame and grants TXOP to itself. After STA3 receives the CTS frame sent by AP, it finds that the receiving address of the CTS frame is not its own address but the address of AP, so it determines that the channel competition has failed and the TXOP belongs to AP.
  • the AP sends a Trigger frame to STA1 and STA2, triggering STA1 and STA2 to simultaneously send TB PPDU carrying MU uplink data, and replies with a Multi-STA BlockAck frame to confirm successful transmission.
  • Example 4 assume that a WLAN network contains 1 AP and 4 STAs (STA1, STA2, STA3, STA4). If the AP uses the Single Protection TXOP, the STAs also use the Single Protection TXOP. STA1 and STA2 belong to STA Group 1, STA3 belongs to STA Group 2, and STA4 does not belong to any STA Group. All STAs use the AC_VO access type in EDCA, and the frame interaction between the AP and the STA is shown in Figure 18.
  • STA2 first sends a G-RTS frame at the AIFS time when the channel is idle. After receiving the G-RTS frame, AP finds that STA2 belongs to STA Group 1 and there are two STAs in STA Group 2, so it replies with a CTS-to-self frame and grants TXOP to itself. After STA3 receives the CTS frame sent by AP, it finds that the receiving address of the CTS frame is not its own address but the address of AP, so it determines that the channel competition has failed and the TXOP belongs to AP.
  • the AP in order to further confirm the uplink low-latency service cache status in STA Group 1, the AP sends an NFRP trigger frame to all or part of the STAs in STA Group 1, and receives the TB feedback NDP, thereby confirming that STA1 and STA2 in STA Group 1 need to transmit uplink low-latency services. Subsequently, the AP sends a trigger frame to STA1 and STA2, triggering STA1 and STA2 to simultaneously send TB PPDU carrying MU uplink data, and replies to the Multi-STA BlockAck frame to confirm successful transmission.
  • Example 5 assume that a WLAN network contains 1 AP and 4 STAs (STA1, STA2, STA3, STA4). If the AP uses the TXOP of Multiple Protection with limited length, the STA uses the TXOP of Single Protection. STA1 and STA2 belong to STA Group 1, STA3 belongs to STA Group 2, and STA4 does not belong to any STA Group. All STAs use the AC_VO access type in EDCA, and the frame interaction between AP and STA is shown in Figure 19.
  • STA1 first sends a G-RTS frame at the AIFS moment when the channel is idle. After receiving the G-RTS frame, AP finds that STA1 belongs to STA Group 1 and there are two STAs in STA Group 2, so it replies with a CTS-to-self frame and grants TXOP to itself. After STA1 receives the CTS frame sent by AP, it finds that the receiving address of the CTS frame is not its own address but the address of AP, so it determines that the channel competition has failed and the TXOP belongs to AP.
  • AP sends a Trigger frame to STA1 and STA2, triggering STA1 and STA2 to simultaneously send TB PPDU carrying MU uplink data, and reply with a Multi-STA BlockAck frame to confirm successful transmission.
  • AP sends MU downlink data to STA1 and STA2, and STA1 and STA2 reply with a BlockAck frame through TB PPDU to confirm successful transmission.
  • the TXOP of AP ends and the channel re-enters the idle state.
  • Example 6 assume that a WLAN network contains 1 AP and 4 STAs (STA1, STA2, STA3, STA4). If the AP uses the Single Protection TXOP, the STAs also use the Single Protection TXOP. STA1 and STA2 belong to STA Group 1, STA3 belongs to STA Group 2, and STA4 does not belong to any STA Group. All STAs use the AC_VO access type in EDCA, and the frame interaction between the AP and the STA is shown in Figure 20.
  • STA2 first sends an RTS frame at the AIFS moment when the channel is idle. After receiving the RTS frame, the AP finds that it is not a G-RTS frame, so it does not trigger any grouping-related rules mentioned in this case, and determines the ownership of the TXOP according to the EDCA rules. Therefore, the AP replies with a CTS frame to STA2 and grants the TXOP to STA2. After STA2 receives the CTS frame sent by the AP, it finds that the receiving address of the CTS frame is its own address, and determines that the TXOP competition is successful. Subsequently, in STA2's TXOP, STA2 sends uplink SU UL data, and the AP replies with an ACK frame to confirm that the transmission is successful.
  • FIG21 shows a schematic block diagram of a STA 300 according to an embodiment of the present application.
  • the STA 300 has uplink data to be transmitted.
  • the STA 300 includes:
  • the communication unit 310 is used to send a first media access control MAC frame; wherein the first MAC frame is used to compete for a channel, and a channel competition result corresponding to the first MAC frame is associated with the grouping information of the STA.
  • the grouping information of the STA includes at least one of the following:
  • the STA belongs to a STA group among m STA groups
  • the STA belongs to a STA group among m STA groups, an identifier of the STA group to which the STA belongs, and/or the number of STAs included in the STA group to which the STA belongs;
  • the channel contention result corresponding to the first MAC frame is associated with the grouping information of the STA, including:
  • the transmission opportunity TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA;
  • the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the access point AP; and/or,
  • the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA;
  • some or all of the STAs in the first STA group send uplink data in the TXOP after receiving the trigger frame sent by the AP.
  • some or all of the STAs in the first STA group when the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the AP, some or all of the STAs in the first STA group send uplink data and receive downlink data within the TXOP after receiving the trigger frame sent by the AP.
  • some or all STAs in the first STA group feedback uplink cache status information after receiving the empty data physical protocol data unit feedback report polling NFRP trigger frame sent by the AP, and the resources for some or all STAs in the first STA group to send uplink data within the TXOP are associated with the uplink cache status information fed back by some or all STAs in the first STA group.
  • STAs with the same or similar service cycles belong to different STA groups among the m STA groups.
  • the packet information of the STA is associated with a first field in the first MAC frame.
  • the first field is a field used to identify the identity of the STA.
  • the first field is used to indicate grouping information of the STA.
  • the TXOP used by the STA is a single-protected TXOP or a length-limited multiple-protected TXOP
  • the TXOP used by the AP corresponding to the STA is a single-protected TXOP or a length-limited multiple-protected TXOP
  • the TXOP used by the STA is a single-protected TXOP or a length-limited multiple-protected TXOP
  • the TXOP used by the AP corresponding to the STA is a single-protected TXOP or a multiple-protected TXOP.
  • the uplink data includes at least uplink delay sensitive data.
  • the first MAC frame is a group request to send G-RTS frame.
  • the communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system on chip.
  • the processing unit may be one or more processors.
  • the STA 300 may correspond to the STA in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the STA 300 are respectively for realizing the corresponding process of the STA in the method 200 shown in Figure 13, which will not be repeated here for the sake of brevity.
  • FIG22 shows a schematic block diagram of an AP 400 according to an embodiment of the present application.
  • the AP 400 includes:
  • the communication unit 410 is configured to receive a first media access control MAC frame sent by a station STA;
  • the first MAC frame is used to compete for a channel, and a channel competition result corresponding to the first MAC frame is associated with the grouping information of the STA, and the STA has uplink data to be transmitted.
  • the grouping information of the STA includes at least one of the following:
  • the STA belongs to a STA group among m STA groups
  • the STA belongs to a STA group among m STA groups, an identifier of the STA group to which the STA belongs, and/or the number of STAs included in the STA group to which the STA belongs;
  • the communication unit 410 is further used to send a CTS frame that allows sending, wherein the CTS frame is used to declare that the transmission opportunity TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA; and/or,
  • the communication unit 410 is further configured to send a CTS-to-self frame, wherein the CTS-to-self frame is used to declare that the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the AP; and/or,
  • the communication unit 410 is further used to send a CTS frame, wherein the CTS frame is used to declare that the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the STA;
  • some or all of the STAs in the first STA group send uplink data in the TXOP after receiving the trigger frame sent by the AP.
  • some or all of the STAs in the first STA group when the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the AP, some or all of the STAs in the first STA group send uplink data and receive downlink data within the TXOP after receiving the trigger frame sent by the AP.
  • the AP 400 when the TXOP associated with the channel contention corresponding to the first MAC frame belongs to the AP, the AP 400 further includes: a processing unit 420;
  • the communication unit 410 is further configured to send a null data physical protocol data unit feedback report polling NFRP trigger frame, wherein the NFRP trigger frame is used to query uplink buffer status information of some or all STAs in the first STA group;
  • the processing unit 420 is configured to allocate multi-user uplink transmission resources in the TXOP to some or all STAs in the first STA group according to uplink buffer status information of some or all STAs in the first STA group.
  • STAs with the same or similar service cycles belong to different STA groups among the m STA groups.
  • the packet information of the STA is associated with a first field in the first MAC frame.
  • the first field is a field used to identify the identity of the STA.
  • the first field is used to indicate grouping information of the STA.
  • the TXOP used by the STA is a single-protected TXOP or a length-limited multiple-protected TXOP
  • the TXOP used by the AP corresponding to the STA is a single-protected TXOP or a length-limited multiple-protected TXOP
  • the TXOP used by the STA is a single-protected TXOP or a length-limited multiple-protected TXOP
  • the TXOP used by the AP corresponding to the STA is a single-protected TXOP or a multiple-protected TXOP.
  • the uplink data includes at least uplink delay sensitive data.
  • the first MAC frame is a group request to send G-RTS frame.
  • the communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system on chip.
  • the processing unit may be one or more processors.
  • the AP 400 according to the embodiment of the present application may correspond to the AP in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the AP 400 are respectively for realizing the corresponding processes of the AP in the method 200 shown in Figure 13, which will not be repeated here for the sake of brevity.
  • Fig. 23 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application.
  • the communication device 500 shown in Fig. 23 includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 500 may further include a memory 520.
  • the processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
  • the memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .
  • the communication device 500 may further include a transceiver 530 , and the processor 510 may control the transceiver 530 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
  • the transceiver 530 may include a transmitter and a receiver.
  • the transceiver 530 may further include an antenna, and the number of the antennas may be one or more.
  • the processor 510 may implement the functions of a processing unit in a STA, or the processor 510 may implement the functions of a processing unit in an AP, which will not be described in detail here for the sake of brevity.
  • the transceiver 530 may implement the function of a communication unit in a STA, which will not be described in detail here for the sake of brevity.
  • the transceiver 530 may implement the function of a communication unit in an AP, which will not be described in detail here for the sake of brevity.
  • the communication device 500 may specifically be the AP of the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the AP in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
  • the communication device 500 may specifically be a STA in an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the STA in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.
  • Fig. 24 is a schematic structural diagram of a device according to an embodiment of the present application.
  • the device 600 shown in Fig. 24 includes a processor 610, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.
  • the apparatus 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .
  • the processor 610 may implement the function of a processing unit in a STA, or the processor 610 may implement the function of a processing unit in an AP, which will not be described in detail here for the sake of brevity.
  • the apparatus 600 may further include an input interface 630.
  • the processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
  • the processor 610 may be located inside or outside the chip.
  • the input interface 630 may implement the function of a communication unit in a STA, or the input interface 630 may implement the function of a communication unit in an AP.
  • the apparatus 600 may further include an output interface 640.
  • the processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the processor 610 may be located inside or outside the chip.
  • the output interface 640 may implement the function of a communication unit in a STA, or the output interface 640 may implement the function of a communication unit in an AP.
  • the device can be applied to the AP in the embodiments of the present application, and the device can implement the corresponding processes implemented by the AP in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the device can be applied to the STA in the embodiments of the present application, and the device can implement the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.
  • FIG25 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in FIG25 , the communication system 700 includes a STA 710 and an AP 720.
  • the STA 710 may be used to implement the corresponding functions implemented by the STA in the above method, and the AP 720 may be used to implement the corresponding functions implemented by the AP in the above method, which will not be described in detail for the sake of brevity.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by the hardware integrated logic circuit in the processor or the instruction in the form of software.
  • the above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general processor can be a microprocessor or the processor can also be any conventional processor, etc.
  • the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software modules in the decoding processor can be executed.
  • the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory can be a random access memory (RAM), which is used as an external cache.
  • RAM Direct Rambus RAM
  • SRAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced SDRAM
  • SLDRAM Synchlink DRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
  • An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the AP in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the computer-readable storage medium can be applied to the STA in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
  • An embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the AP in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
  • the computer program product can be applied to the STA in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the AP in the embodiments of the present application.
  • the computer program runs on a computer, the computer executes the corresponding processes implemented by the AP in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the computer program can be applied to the STA in the embodiments of the present application.
  • the computer program runs on a computer, the computer executes the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical Functional division, in actual implementation, there may be other division methods, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种无线通信的方法及设备，在信道竞争中引入了STA分组功能，TXOP的分配更加高效，提高了多用户上行(MU UL)的使用频率，从而降低上下行数据传输的时延，并缓解时延抖动。该无线通信的方法，应用于STA，该STA存在待传输的上行数据，该方法包括：该STA发送第一MAC帧；其中，该第一MAC帧用于竞争信道，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联。

Description

无线通信的方法及设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种无线通信的方法及设备。
背景技术
在无线局域网(Wireless Local Area Networks，WLAN)中，为了提升信道接入性能，引入了增强分布式信道接入(Enhanced Distributed Channel Access，EDCA)机制。然而，在一些场景下，站点(Station，STA)的数量较多，现阶段的EDCA机制性能还有待进一步提升。
发明内容
本申请实施例提供了一种无线通信的方法及设备，在信道竞争中引入了STA分组功能，TXOP的分配更加高效，提高了多用户上行(MU UL)的使用频率，从而降低上下行数据传输的时延，并缓解时延抖动。
第一方面，提供了一种无线通信的方法，应用于站点STA，该STA存在待传输的上行数据，该方法包括：
该STA发送第一媒体接入控制MAC帧；其中，该第一MAC帧用于竞争信道，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联。
第二方面，提供了一种无线通信的方法，应用于接入点AP，该方法包括：
该AP接收站点STA发送的第一媒体接入控制MAC帧；
其中，该第一MAC帧用于竞争信道，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联，该STA存在待传输的上行数据。
第三方面，提供了一种STA，用于执行上述第一方面中的方法。
具体地，该STA包括用于执行上述第一方面中的方法的功能模块。
第四方面，提供了一种AP，用于执行上述第二方面中的方法。
具体地，该AP包括用于执行上述第二方面中的方法的功能模块。
第五方面，提供了一种STA，包括处理器和存储器；该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，使得该STA执行上述第一方面中的方法。
第六方面，提供了一种AP，包括处理器和存储器；该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，使得该AP执行上述第二方面中的方法。
第七方面，提供了一种装置，用于实现上述第一方面至第二方面中的任一方面中的方法。
具体地，该装置包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该装置的设备执行如上述第一方面至第二方面中的任一方面中的方法。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
通过上述技术方案，在信道竞争中引入了STA分组功能，TXOP的分配更加高效，提高了多用户上行(MU UL)的使用频率，从而降低上下行数据传输的时延，并缓解时延抖动。
附图说明
图1是本申请实施例应用的一种通信系统架构的示意性图。
图2是本申请提供的QoS STA和Non-QoS STA信道接入优先级和定时示意图。
图3是本申请提供的EDCA机制定时关系的示意图。
图4是本申请提供的SU UL的示意图。
图5是本申请提供的MU UL的示意图。
图6是本申请提供的NDP Feedback Report机制的示意图。
图7是本申请提供的NFRP Trigger帧的帧格式的示意图。
图8是本申请提供的公共信息(Common Info)字段的帧格式的示意图。
图9是本申请提供的用户信息列表(User Info List)字段的帧格式的示意图。
图10是本申请提供的HE TB feedback NDP格式的示意图。
图11是本申请提供的STA或AP在一次信道竞争中获得TXOP的概率的示意图。
图12是根据本申请实施例提供的信道竞争的三个阶段的示意图。
图13是根据本申请实施例提供的一种无线通信的方法的示意性流程图。
图14是根据本申请实施例提供的一种G-RTS帧的示意性图。
图15至图20分别是根据本申请实施例提供的信道竞争以及数据接收和/或发送的示意性图。
图21是根据本申请实施例提供的一种STA的示意性框图。
图22是根据本申请实施例提供的一种AP的示意性框图。
图23是根据本申请实施例提供的一种通信设备的示意性框图。
图24是根据本申请实施例提供的一种装置的示意性框图。
图25是根据本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。针对本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)或其他通信系统等。
请参考图1，其示出了本申请一个实施例提供的无线通信系统的示意图。如图1所示，该无线通信系统可以包括：接入点(Access Point，AP)和站点(Station，STA)。
在一些场景中，AP可以或称AP STA，即在某种意义上来说，AP也是一种STA。在一些场景中，STA或可称为非AP STA(Non-AP STA)。
在一些实施例中，STA可以包括AP STA和Non-AP STA。通信系统中的通信可以是AP与Non-AP STA之间通信，也可以是Non-AP STA与Non-AP STA之间通信，或者STA与peer STA之间通信。其中，peer STA可以指与STA对端通信的设备。例如，peer STA可能为AP，也可能为Non-AP STA。
AP相当于一个连接有线网和无线网的桥梁，主要作用是将各个无线网络客户端连接到一起，然后将无线网络接入以太网。AP设备可以是带有无线保真(Wireless-Fidelity，Wi-Fi)芯片的终端设备(如手机)或者网络设备(如路由器)。
应理解，STA在通信系统中的角色不是绝对的，例如，在一些场景中，手机连接路由的时候，手机是Non-AP STA，手机作为其他手机的热点的情况下，手机充当了AP的角色。
AP和Non-AP STA可以是应用于车联网中的设备，物联网(Internet of Things，IoT)中的物联网节点、传感器等，智慧家居中的智能摄像头，智能遥控器，智能水表电表等，以及智慧城市中的传感器等。
在一些实施例中，Non-AP STA可以支持802.11be制式。Non-AP STA也可以支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种当前以及未来802.11家族的无线局域网制式。
在一些实施例中，AP可以为支持802.11be制式的设备。AP也可以为支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种当前以及未来的802.11家族的WLAN制式的设备。
在本申请实施例中，STA可以是支持WLAN/WIFI技术的手机(Mobile Phone)、平板电脑(Pad)、电脑、虚拟现实(Virtual Reality，VR)设备、增强现实(Augmented Reality，AR)设备、工业控制(industrial control)中的无线设备、机顶盒、无人驾驶(self driving)中的无线设备、车载通信设备、远程医疗(remote medical)中的无线设备、智能电网(smart grid)中的无线设备、运输安全(transportation safety)中的无线设备、智慧城市(smart city)中的无线设备或智慧家庭(smart home)中的无线设备、无线通信芯片、ASIC(Application Specific Integrated Circuit，专用集成电路)、SOC(System on Chip，系统级芯片)等。
WLAN技术可支持频段可以包括但不限于：低频段(2.4GHz、5GHz、6GHz)、高频段(45GHz、60GHz)。
站点和接入点之间存在一个或多个链路。在一些实施例中，站点和接入点支持多频段通信。例如，同时在2.4GHz，5GHz，6GHz，45GHz以及60GHz频段上进行通信，或者同时在同一频段(或不同频段)的不同信道上通信，提高设备之间的通信吞吐量和/或可靠性。这种设备通常称为多频段设备，或称为多链路设备(Multi-Link Device，MLD)，有时也称为多链路实体或多频段实体。多链路设备可以是接入点设备，也可以是站点设备。如果多链路设备是接入点设备，则多链路设备中包含一个或多个AP；如果多链路设备是站点设备，则多链路设备中包含一个或多个non-AP STA。
包括一个或多个AP的多链路设备可称为接入点多链路设备(Access Point Multi-Link Device，AP MLD)，包括一个或多个non-AP STA的多链路设备可称为非接入点多链路设备(Non-AP Multi-Link  Device，Non-AP MLD)。
在本申请实施例中，AP可以包括多个AP，Non-AP包括多个STA，AP中的AP和Non-AP中的STA之间可以形成多条链路，AP中的AP和Non-AP中的对应STA之间可以通过对应的链路进行数据通信。
AP是一种部署在无线局域网中用以为STA提供无线通信功能的设备。站点可以包括：用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、用户代理或用户装置。可选地，站点还可以是蜂窝电话、无绳电话、测量启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digita1Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，本申请实施例对此并不限定。
在一些实施例中，站点(STA)和接入点(AP)均支持IEEE 802.11标准。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。本申请的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。
应理解，本申请实施例中提到的“至少一个或至少之一”可以表示“一个或多个”，以及本申请实施例中提到的“正整数”可以表示“1,2,3…等取值”，本申请实施例中提到的“非负整数”可以表示“0,1,2,3…等取值”，本申请实施例中提到的“整数”可以表示“…,-3,-2,-1,0,1,2,3,…等取值”，可以基于实施例需求替换为可能的任意取值。
应理解，本申请实施例所示的图和/或表仅为示例，具体的，在一些情况下，本申请实施例所示的图和/或表所包含的部分信息可以单独构成可选地实施例，例如，表中的每一行或每一列可以单独构成可选地实施例，本申请对此并不限定。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，“预定义”或“预配置”可以通过在设备(例如，包括STA和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
本申请实施例中，所述“协议”可以指通信领域的标准协议，例如可以包括WiFi协议以及应用于未来的WiFi通信系统中的相关协议，本申请对此不做限定。
为便于更好的理解本申请实施例，对本申请相关的增强的分布式信道接入(Enhanced Distributed Channel Access，EDCA)机制进行说明。
IEEE 802.11e标准中定义了一种服务质量(Quality of Service，QoS)增强的信道接入机制：EDCA。EDCA相比传统的分布式协调功能(Distributed Coordination Function，DCF)，定义四种不同的接入类别(Access Category，AC)，分别为AC_VO、AC_VI、AC_BE和AC_BK。如表1所示，不同的AC具有不同的参数设置，从而在接入媒介时有不同的优先级。
表1 EDCA参数设置表格
其中，
CWmin：指示竞争窗口上限的最小值，越小的CWmin具有更高的优先级；
CWmax：指示竞争窗口上限的最大值，越小的CWmax具有更高的优先级；
传输机会(Transmission Opportunity，TXOP)限制(Limit)：指示占用信道的最大时长；
仲裁帧间空间编号(Arbitration Interframe Space Number，AIFSN)：指示STA在检测到信道空闲短帧间间隔(Short Interframe Space，SIFS)时间后需要再等待的时隙(slot)的个数，之后STA才能开始随机退避流程。越小的AIFSN具有更高的优先级。
图2中给出了QoS STA使用四种AC接入信道的示意图，可以看到由于AIFSN参数的不同，AC_VO、AC_VI、AC_BE、AC_BK的优先级是逐渐降低的。
另外，图2中也给出了Non-QoS STA接入信道的定时示意图，也就是传统的DCF机制。DCF机制含有两种情况，一种是STA在检测到优先帧间间隔(priority interframe space，PIFS)的信道空闲后即可发送，另一种是在检测到分布式帧间间隔(Distributed Inter-frame Spacing，DIFS)的信道空闲后且进行退避后才可以发送。标准中规定，前者一般只能发送部分特殊功能的帧时使用，比如信标帧，因为此类帧需要有较高的发送优先级；除此之外，STA都使用后者来接入信道。
需要说明的是，在图2中，QoS STA可以是支持QoS EDCA机制的STA，Non-QoS STA可以是不支持QoS EDCA机制的STA。
优先帧间间隔(priority interframe space，PIFS)、分布式帧间间隔(Distributed Inter-frame Spacing，DIFS)、仲裁帧间空间(Arbitration Interframe Space，AIFS)和短帧间间隔(Short Interframe Space，SIFS)之间的定时关系如图3所示。
PIFS＝SIFS+1×aSlotTime。
DIFS＝SIFS+2×aSlotTime。
AIFS＝SIFS+AIFSN×aSlotTime。
为便于更好的理解本申请实施例，对本申请相关的单用户上行传输(single user uplink，SU UL)与单用户上行传输(multi-user uplink，MU UL)流程进行说明。
SU UL的流程如图4所示，图4中包含1个AP和3个STA(Non-AP STA)。每个STA都需要先通过EDCA机制竞争信道，然后再发送上行(Uplink，UL)低时延(low latency，LL)数据并接收确认(Acknowledgement，ACK)帧。多个STA(Non-AP STA)之间是以串行的方式一个接一个地获得TXOP并发送上行数据。这种SU UL的上行数据传输方式会导致上行传输的时延和时延抖动较大，因为STA不一定能够及时竞争到TXOP。
MU UL的流程如图5所示，图5中包含1个AP和n个STA(Non-AP STA)。首先，AP通过EDCA机制竞争到TXOP，其次，AP发送触发(Trigger)帧至每个STA，给每个STA分配各自上行并行传输所需的资源，然后，n个STA(Non-AP STA)根据所分配的资源同时发送高效的基于触发的物理层协议数据单元(High Efficiency Trigger Based Physical layer protocol data unit，HE TB PPDU)以传输上行数据，最后，AP回复多STA块确认(Multi-STA BlockAck)帧至n个STA确认传输是否成功。这种MU UL的上行传输方式能够实现并行上行传输(即上行传输所占用的时域资源相同、频域和/或空域资源不同)，相比SU UL具有更高的传续效率。
为便于更好的理解本申请实施例，对本申请相关的空数据物理协议数据单元(Null Data Physical Protocol Data Unit，NDP)反馈报告(Feedback Report)机制进行说明。
IEEE 802.11ax标准定义了一套MU UL探测机制，这个机制使得AP能够在发送触发(Trigger)帧之前探测需要分配资源的STA(Non-AP STA)。
IEEE 802.11ax中的MU UL探测机制还定义了两个相关的帧结构：空数据物理协议数据单元反馈报告轮询(Null Data Physical Protocol Data Unit Feedback Report Polling，NFRP)触发帧和高效基于触发反馈的空数据物理协议数据单元(High Efficiency Trigger Based Feedback Null Data Physical Protocol Data Unit，HE TB feedback NDP)。AP发送NFRP Trigger帧至全部Non-AP STA，触发Non-AP STA发送HE TB feedback NDP，AP通过解析HE TB feedback NDP就可以得知有哪些Non-AP STA需要参与后续的MU UL传输。
如图6所示，AP发送NFRP Trigger帧至某些Non-AP STA，触发Non-AP STA发送HE TB feedback NDP，AP通过解析HE TB feedback NDP就可以得知有哪些Non-AP STA需要参与后续的MU UL传输，进而在后续的Trigger帧中合理分配资源给Non-AP STA，从而完成MU UL传输。
为便于更好的理解本申请实施例，对本申请相关的NFRP触发帧进行说明。
NFRP触发帧的帧格式如图7所示，其中，公共信息(Common Info)字段的格式如图8所示，用户信息列表(User Info List)字段的格式如下图9所示。
具体的，如图7所示，NFRP触发帧可以包括如下字段：帧控制(占用2个字节)、时长(占用2个字节)、接收地址(Receiving Address，RA)(占用6个字节)、发送地址(Transmission Address，TA)(占用6个字节)、公共信息(Common Info)(占用8个或更多字节)、用户信息列表(User Info list)(占用字节数可变(variable))、填充(padding)(占用字节数可变(variable))、帧校验序列(Frame Check Sequence，FCS)(占用4个字节)。
具体的，如图8所示，公共信息(Common Info)字段可以包括如下字段：触发类型(Trigger Type)(占用4个比特)、上行长度(UL Length)(占用12个比特)、更多触发帧(Trigger Frame，TF)(占用1个比特)、需要载波侦听(Carrier Sense，CS)(占用1个比特)、上行带宽(BandWidth，BW)(占用2个比特)、保护间隔(Guard Interval，GI)和高效率长训练域(High Efficiency Long Training Field，HE-LTF)类型(占用2个比特)、多用户多输入多输出(Multiple Users multiple-in multiple-out，MU-MIMO)HE-LTF模式(占用1个比特)、HE-LTF符号数量和中间码周期(占用3个比特)、上行空时分组码(Space Time Block Code，STBC)(占用1个比特)、低密度奇偶校验(low-density parity check，LDPC)额外符号段(占用1个比特)、AP发送功率(占用6个比特)、预前向纠错(Pre-Forward Error Correction，Pre-FEC)填充因子(占用2个比特)、数据包扩展(Packet Extension，PE)消歧(disambiguity)(占用1个比特)、上行空间重用(占用16个比特)、多普勒(doppler)(占用1个比特)、上行高效率信号字段A2(High Efficiency-SINGAL field-A2，HE-SIG-A2)预留(占用9个比特)、预留(占用1个比特)、触发相关公共信息(占用比特数可变(variable))。
其中，上行带宽(UL BW)字段表示NDP反馈报告响应的带宽；UL STBC、LDPC Extra Symbol Segment、Pre-FEC Padding Factor、PE Disambiguity、UL Spatial Reuse和Doppler字段被保留；Number Of HE-LTF Symbols和Midamble Periodicity字段指示NDP反馈报告响应中存在的HE-LTF符号数，并设置为1；GI And HE-LTF Type字段设置为2；Trigger Dependent Common Info字段不存在。
具体的，如图9所示，用户信息列表(User Info List)字段可以包括如下字段：起始AID(占用12个比特)、保留(占用9个比特)、反馈类型(占用4个比特)、保留(占用7个比特)、上行目标接收功率(UL Target Receive Power)(占用7个比特)、空分复用用户的数量(Number Of Spatially Multiplexed Users)(占用1个比特)。
其中，起始AID(Staring AID)字段：定义了计划响应NFRP触发帧的关联标识符(Association Identifier，AID)范围的第一个AID；反馈类型(Feedback Type)字段：指示HE TB feedback NDP所携带的反馈信息的类型；UL Target Receive Power字段：表示预期的在AP的天线连接器处测量并在天线上平均的接收信号功率；Number Of Spatially Multiplexed Users字段：表示在同一资源单元 (Resource Unit，RU)中复用在同一组子载波上的STA数量，编码为STA数-1。
为便于更好的理解本申请实施例，对本申请相关的HE TB feedback NDP进行说明。
HE TB feedback NDP用于携带NDP feedback report信息，其帧格式如图10所示。
具体的，HE TB feedback NDP包括以下字段：传统短训练字段(legacy short training field，L-STF)、传统长训练字段(legacy long training field，L-LTF)、传统信号(legacy signal，L-SIG)、重复传统信号(repeat legacy signal，RL-SIG)、高效信号A(High Efficiency Signal A，HE-SIG-A)、高效短训练字段(High Efficiency short training field，HE-STF)、高效长训练字段(High Efficiency long training field，HE-LTF)、数据包扩展(Packet Extension，PE)。
其中，如图10所示，2个4x HE-LTF类型的HE-LTF符号，每个符号16μs(2HE-LTF symbols with16μs per symbol using 4x HE-LTF)。
具体的，NDP格式采用了HE TB PPDU格式，只是没有数据(Data)字段，PE字段时长为0微秒(μs)，有2个类型为4x HE-LTF的符号，所使用的保护间隔(GI)是3.2微秒。其中1x HE-LTF符号持续时长为3.2微秒，2x HE-LTF符号持续时长为6.4微秒，4x HE-LTF符号持续时长为12.8微秒，时长均未计算保护间隔。
具体的，HE-LTF字段中的不同RU通集合索引(RU_TONE_SET_INDEX)用于标识不同Non-AP STA的AID以及反馈信息(FEEDBACK_STATUS)，其中，通(TONE)也可以称之为子载波。具体的，HE TB feedback NDP中HE-LTF子载波映射关系可以如表2所示。
表2

简单来说，当NFRP Trigger帧中的空间复用用户的数量(Number Of Spatially Multiplexed Users)字段取值为0时，每个RU_TONE_SET_INDEX对应一个Non-AP STA(AID)。当BW为20MHz时，对于使用RU_TONE_SET_INDEX＝1的Non-AP STA来说，反馈信息FEEDBACK_STATUS＝1对应HE-LTF中的第–113,–77,–41,6,42,78子载波有能量，其他子载波都没有能量；反馈信息FEEDBACK_STATUS＝0对应HE-LTF中的第–112,–76,–40,7,43,79子载波有能量，其他子载波都没有能量。当BW为40MHz或80MHz时，将20MHz的子载波映射关系分别扩展1倍和3倍，从而可以映射更多的Non-AP STA(AID)。当NFRP Trigger帧中的Number Of Spatially Multiplexed Users字段取值为1时，每个RU_TONE_SET_INDEX对应两个Non-AP STA(AID)，这两个Non-AP STA通过预先分配好的不同的与编码矩阵来区分。
为便于更好的理解本申请实施例，对本申请相关的单一保护(Single Protection)和多重保护(Multiple Protection)进行说明。
位于媒体接入控制(Media Access Control，MAC)帧帧头的时长/标识(Duration/ID)字段用于给接收该MAC帧的STA设置网络分配向量(Network Allocation Vector，NAV)，收到该MAC帧的STA在NAV时间内认为信道是繁忙的。
在EDCA机制下发起的TXOP有两类持续时间设置：Single Protection和Multiple Protection。在 Single Protection中，NAV指示的时间长度仅仅包含接下来发送的一个数据、管理或响应帧另外加上任何额外的开销帧；在Multiple Protection中，NAV可以指示时间长度可以包含接下来发送和接收的多个帧。
为便于理解本申请实施例的技术方案，以下对本申请所解决的问题进行说明。
在工业场景中，为了提高不同生产设备之间的协作和更高程度的自动化，工厂中的设备一般都需要通过网络链接在一起，组成物联网(Internet of Things，IOT)网络。WIFI相比其他无线通信方式具有频谱免授权、普及度广，吞吐量高等优点。但是，现有的WIFI中的信道访问机制EDCA并不适用于存在众多站点设备的工业IOT场景。因为，在WIFI中有两种发送上行数据的方法：SU UL和MU UL。SU UL需要发送站点获得TXOP，MU UL需要AP获得TXOP，否则，这个站点无法发送上行数据。然而，一个站点获得TXOP的概率和AP获得TXOP的概率会随着全部站点的数量的增加而逐步减小，逐渐收敛于一个较小的固定值，STA或AP在一次信道竞争中获得TXOP的概率可以如图11所示。所以，当站点数量较多时，站点执行SU UL和AP执行MU UL的概率都会很小，从而导致上行数据迟迟无法，造成较大的时延和时延抖动。
之所以会存在这个问题，是因为现有的EDCA机制在设计之初就没有考虑到MU UL。MU UL的前提是AP获得TXOP，但是，在EDCA机制下，随着Non-AP STA数量的增加，需要发送上行数据的站点越来越多，AP获得TXOP概率反而越来越小，这就让MU UL发生的机会变得越来越小，上行数据的发送延迟也随之变得越来越大。
基于上述问题，本申请提出了一种具有STA分组功能的EDCA增强方案，在信道竞争中引入了STA分组功能，TXOP的分配更加高效，提高了多用户上行(MU UL)的使用频率，从而降低上下行数据传输的时延，并缓解时延抖动。
本申请实施例对EDCA机制进行了增强，以降低工业场景下上行数据的传输时延。增强的EDCA方案包含如图12所示的四个阶段：分组初始化、媒介竞争、媒介授予和媒介使用。在分组初始化阶段，AP依据统计得到的STA的业务规律来将业务周期相似的STA分配到不同的STA组。在媒介竞争阶段，需要发送低时延业务的STA会按照规则发送特定的帧来争抢TXOP的归属。在媒介授予阶段，AP会依据MU UL探测的结果来回复不同的帧，从而将TXOP授予某一个STA或AP自身。在媒介使用阶段，获得TXOP的STA需要按照规则执行特定的传输流程。
为便于理解本申请实施例的技术方案，以下通过具体实施例详述本申请的技术方案。以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
图13是根据本申请实施例的无线通信的方法200的示意性流程图，该无线通信的方法200可以由STA和AP交互执行，STA可以是如图1所示的STA(Non-AP STA)，AP可以是如图1所示的AP，其中，该STA存在待传输的上行数据。具体的，如图13所示，该无线通信的方法200可以包括如下内容中的至少部分内容：
S210，STA发送第一MAC帧；其中，该STA存在待传输的上行数据，该第一MAC帧用于竞争信道，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联；
S220，AP接收该STA发送的该第一MAC帧。
应理解，图13示出了无线通信的方法200的步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其他操作或者图13中的各个操作的变形。
在本申请实施例中，“字段”也可以称之为“域(field)”或“子域(subfield)”。一个字段可以占用一个或多个字节(byte/octet)，或者，一个字段可以占用一个或多个比特(bit)。
在本申请实施例中，“媒介”也可以称之为“信道”，可以相互替换。
需要说明的是，在WIFI中有两种发送上行数据的方法：单用户上行传输(single user uplink，SU UL)和多用户上行传输(multi-user uplink，MU UL)。SU UL需要发送站点获得TXOP，MU UL需要AP获得TXOP。但是，在工业场景中，站点(STA)的数量一般会很多，即参与EDCA信道竞争的设备会很多，导致这个站点(STA)或者AP获得TXOP的概率变得很小，上行数据迟迟无法发送，最终造成较大的时延和时延抖动。基于上述问题，本申请实施例提出了具有STA分组功能的增强EDCA方案，当分组中的任意一个STA将要获得TXOP时，AP可以选择强制获得TXOP进而执行效率较高的MU UL流程，从而快速满足多个有相似的发生周期的STA的上行数据发送需求，降低时延。
在一些实施例中，本申请实施例所述的上行数据至少包括上行时延敏感数据。当然，本申请实施例所述的上行数据也可以包括其他数据，如非时延敏感数据。
需要说明的是，时延敏感数据也可以称之为低时延(LL)数据，本申请实施例对此并不限定。
在一些实施例中，该第一MAC帧为组请求发送(Grouping-request to send，G-RTS)帧。当然， 该第一MAC帧也可以为其他帧，或者，该第一MAC帧为新定义的MAC帧。
具体例如，第一MAC帧为G-RTS帧，其可以如图14所示，G-RTS帧中的帧控制字段包括以下字段：协议版本、帧类型(＝1)、帧子类型(＝15)、发送到分布系统(distribution system，DS)(to DS)、来自分布系统(from DS)、电源管理(Power Management)、更多数据、含有高吞吐控制。其中，协议版本字段：指示MAC帧的版本。帧类型字段：取值为1表示该帧为控制帧。帧子类型字段：取值为15表示该第一MAC帧为新定义的G-RTS帧。To DS字段和From DS字段：取值均为0无含义。电源管理字段：指示STA的电源管理模式。更多数据字段：指示一个在节能模式下的STA的缓存中还有待发送的数据。含有高吞吐控制字段：指示该帧中是否含有高吞吐控制字段。时长字段：指示网络分配矢量(network allocation vector，NAV)的取值，用于保护媒介不被抢占。接收地址字段：接收该帧的STA的地址。发送地址字段：发送该帧的STA的地址。帧校验字段：校验该帧控制字段是否传输正确。
在一些实施例中，可以预先分配m个STA组，m为正整数，且m＝1，或，m≥2。具体例如，关联到同一个AP的一个或多个STA可以组成一个STA组，可以同时存在一个或多个STA组，每个STA组具有唯一的标识符：STA组ID。
具体例如，AP预先分配m个STA组，或者，AP所属的物理AP MLD预先分配m个STA组，或者，AP所属的虚拟AP MLD预先分配m个STA组。
在一些实施例中，在m≥2的情况下，业务周期相同或相近的STA分别属于m个STA组中不同的STA组。具体例如，AP可以依据统计得到的STA的业务规律来将业务周期相似的STA分配到不同的STA组。
在一些实施例中，该STA的分组信息包括但不限于以下至少之一：
该STA是否属于该m个STA组中的STA组；
在该STA属于该m个STA组中的STA组的情况下，该STA所属的STA组的标识，和/或，该STA所属的STA组内包含的STA的数量。
在一些实施例中，该STA的分组信息与该第一MAC帧中的第一字段关联。也即，可以基于第一MAC帧中的第一字段获取STA的分组信息。具体的，可以基于第一MAC帧中的第一字段直接或间接获取STA的分组信息。
在一些实施例中，该第一字段为用于标识该STA的身份的字段。也即，AP可以基于第一MAC帧中的第一字段间接获取STA的分组信息。可选地，第一字段为发送地址(TA)字段或其他地址标识字段。具体例如，AP基于收到的第一MAC帧中的发送地址(TA)字段或其他地址标识字段识别出该STA的身份，如图14所示，然后依据该STA是否属于某一个STA组以及STA组中的STA设备数量回复不同的CTS帧，从而将TXOP授予STA或AP。
在一些实施例中，该第一字段用于指示该STA的分组信息。也即，AP可以基于第一MAC帧中的第一字段直接获取STA的分组信息。
在一些实施例中，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联，包括：
在该STA属于该m个STA组中的第一STA组且该第一STA组内的STA数量小于第一阈值的情况下，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有；和/或，
在该STA属于该m个STA组中的第一STA组且该第一STA组内的STA数量大于或等于第一阈值的情况下，该第一MAC帧对应的信道竞争关联的TXOP归AP所有；和/或，
在该STA不属于该m个STA组中的任意一个STA组的情况下，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有。
在一些实施例中，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联，包括：
在该STA属于该m个STA组中的第一STA组且该第一STA组内的STA数量小于或等于第一阈值的情况下，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有；和/或，
在该STA属于该m个STA组中的第一STA组且该第一STA组内的STA数量大于第一阈值的情况下，该第一MAC帧对应的信道竞争关联的TXOP归AP所有；和/或，
在该STA不属于该m个STA组中的任意一个STA组的情况下，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有。
具体例如，在STA不属于m个STA组中的任意一个STA组的情况下，AP回复CTS帧至该STA，宣告TXOP归该STA所有，也即，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有。
具体例如，在STA属于m个STA组中的第一STA组且该第一STA组内的STA数量小于或等于第一阈值的情况下，AP回复CTS帧至该STA，宣告TXOP归该STA所有，也即，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有。
具体例如，在STA属于m个STA组中的第一STA组且该第一STA组内的STA数量大于或等于第一阈值的情况下，AP发送CTS至自身(CTS-to-self)帧，宣告TXOP归AP所有，也即，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有。
在一些实施例中，该第一阈值可以由协议约定，或者，该第一阈值可以由AP配置，或者，该第一阈值可以由AP所属的物理AP MLD配置，或者，该第一阈值可以由AP所属的虚拟AP MLD配置。
在一些实施例中，该STA使用的TXOP为单一保护(Single Protection)的TXOP或长度受限的多重保护(Multiple Protection)的TXOP，和/或，该STA对应的AP使用的TXOP为单一保护(Single Protection)的TXOP或长度受限的多重保护(Multiple Protection)的TXOP。
具体例如，STA和AP使用Single Protection的TXOP或者长度受限的Multiple Protection的TXOP。
在一些实施例中，该STA使用的TXOP为单一保护(Single Protection)的TXOP或长度受限的多重保护(Multiple Protection)的TXOP，和/或，该STA对应的AP使用的TXOP为单一保护(Single Protection)的TXOP或多重保护(Multiple Protection)的TXOP。
具体例如，STA使用Single Protection的TXOP或者长度受限的Multiple Protection的TXOP，而AP可以使用任意类型的TXOP。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的触发帧之后在该TXOP内发送上行数据。
具体例如，当AP获得TXOP后，AP发送触发(Trigger)帧至第一STA组中的部分或全部STA，随后接收基于触发的物理层协议数据单元(Trigger Based physical layer protocol data unit，TB PPDU)获得上行数据并回复块确认(BlockAck)帧或者多STA块确认(Multi-STA BlockAck)帧。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的触发帧之后在该TXOP内发送上行数据和接收下行数据。例如，AP可以先接收上行数据后发送下行数据，也可以先发送下行数据后接收上行数据。
具体例如，当AP获得TXOP后，AP发送触发(Trigger)帧至第一STA组中的部分或全部STA，随后接收TB PPDU获得上行数据并回复块确认(BlockAck)帧或者多STA块确认(Multi-STA BlockAck)帧；进一步地，当AP使用Multiple Protection的TXOP或者长度受限的Multiple Protection的TXOP时，如果TXOP的时长充足，那么AP也可以在TXOP内发送下行SU数据或者下行MU数据，并接收相应的Ack帧或BlockAck帧。AP可以先接收上行数据后发送下行数据，也可以先发送下行数据后接收上行数据。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的NFRP触发帧之后反馈上行缓存状态信息(如缓存状态报告(Buffer Status Report，BSR))，且该第一STA组中的部分或全部STA在TXOP内发送上行数据的资源与该第一STA组中的部分或全部STA反馈的上行缓存状态信息关联。
具体例如，当AP获得TXOP后，可以先发送NFRP触发帧查询相关STA组中的部分或全部STA的上行低时延缓存状态信息(如BSR)，然后并依据此分配资源执行MU UL传输。
在一些实施例中，在如图12所示的分组初始化阶段，关联到同一个AP的一个或多个STA可以组成一个STA组，可以同时存在多个STA组，每个STA组具有唯一的标识符：STA组ID。
在一些实施例中，在如图12所示的媒介竞争阶段，需要发送上行数据的STA遵循EDCA机制进行信道竞争。如果STA允许AP依据分组信息来改变TXOP的授予，则通过发送特定帧(即第一MAC帧)来竞争信道，否则，STA不能使用特定帧(即第一MAC帧)来竞争信道。
在一些实施例中，在如图12所示的媒介授予阶段，AP基于收到的特定帧(即第一MAC帧)中的TA字段或其他地址标识字段识别出STA的身份，然后依据STA是否属于某一个STA组以及STA组中的STA数量回复不同的CTS帧，从而将TXOP授予STA或AP。
具体例如，如果STA不属于任何STA组，则AP回复CTS帧至该STA，宣告TXOP归该STA所有。具体又例如，如果AP探测到STA属于某一个STA组且STA组中的STA的数量小于或等于第一阈值，则AP发送CTS帧至该STA，宣告TXOP归该STA所有。具体再例如，如果AP探测到STA属于某一个STA组且STA组中的STA的数量大于或等于第一阈值，则AP发送CTS-to-self帧，宣告TXOP归AP所有。
在一些实施例中，在如图12所示的媒介使用阶段，STA和AP必须使用Single Protection的TXOP或者长度受限的Multiple Protection的TXOP；在另一种实施例中，STA必须使用Single Protection的TXOP或者长度受限的Multiple Protection的TXOP，而AP可以使用任意类型的TXOP。
在一些实施例中，在如图12所示的媒介使用阶段，当AP获得TXOP后，AP应当发送Trigger帧至STA组中的部分或全部STA，随后接收TB PPDU获得上行数据并回复BlockAck帧或者 Multi-STA BlockAck帧；进一步地，当AP使用Multiple Protection的TXOP或者长度受限的Multiple Protection的TXOP时，如果TXOP的时长充足，那么AP也可以在TXOP内发送下行SU数据或者下行MU数据，并接收相应的Ack帧或BlockAck帧。AP可以先接收上行数据后发送下行数据，也可以先发送下行数据后接收上行数据。
因此，在本申请实施例中，在信道竞争中引入了STA分组功能，TXOP的分配更加高效，提高了多用户上行(MU UL)的使用频率，从而降低上下行数据传输的时延，并缓解时延抖动。
以下通过具体实施例详述本申请技术方案。
实施例1，假设一个WLAN网络中包含1个AP和4个STA(STA1,STA2,STA3，STA4)。如果AP使用Single Protection的TXOP，STA也使用Single Protection的TXOP。STA1和STA2属于STA Group 1，STA3属于STA Group 2，STA4不属于任何STA Group。所有STA使用EDCA中的AC_VO接入类型，则AP和STA之间的帧交互如图15所示。
具体的，如图15所示，STA4在信道空闲仲裁帧间空间(Arbitration Interframe Space，AIFS)时刻最先发送G-RTS帧，AP收到该G-RTS帧后，发现STA4不属于任何STA Group，所以回复CTS帧至STA4，将TXOP授予STA4。STA4收到AP发送的CTS帧后，发现该CTS帧的接收地址为自己的地址，所以判断信道竞争成功，TXOP归自己所有。随后，在STA4的TXOP中，STA4发送SU上行数据至AP，AP回复确认(Acknowledgement，Ack)帧至STA4确认传输成功。至此，STA4的TXOP结束，信道重新进入空闲状态。
实施例2，假设一个WLAN网络中包含1个AP和4个STA(STA1,STA2,STA3，STA4)。如果AP使用Single Protection的TXOP，STA也使用Single Protection的TXOP。STA1和STA2属于STA Group 1,STA3属于STA Group 2，STA4不属于任何STA Group。所有STA使用EDCA中的AC_VO接入类型，则AP和STA之间的帧交互如图16所示。
具体的，如图16所示，STA3在信道空闲AIFS时刻最先发送G-RTS帧，AP收到该G-RTS帧后，发现STA3属于STA Group 2且STA Group 2中仅有一个STA，所以回复CTS帧至STA3，将TXOP授予STA3。STA3收到AP发送的CTS帧后，发现该CTS帧的接收地址为自己的地址，所以判断信道竞争成功，TXOP归自己所有。随后，在STA3的TXOP中，STA3发送SU上行数据至AP，AP回复Ack帧至STA3确认传输成功。至此，STA3的TXOP结束，信道重新进入空闲状态。
实施例3，假设一个WLAN网络中包含1个AP和4个STA(STA1,STA2,STA3，STA4)。如果AP使用Single Protection的TXOP，STA也使用Single Protection的TXOP。STA1和STA2属于Group 1，STA3属于STA Group 2，STA4不属于任何STA Group。所有STA使用EDCA中的AC_VO接入类型，则AP和STA之间的帧交互如图17所示。
具体的，如图17所示，STA2在信道空闲AIFS时刻最先发送G-RTS帧，AP收到该G-RTS帧后，发现STA2属于STA Group 1且STA Group 2中有两个STA，所以回复CTS-to-self帧，将TXOP授予自己。STA3收到AP发送的CTS帧后，发现该CTS帧的接收地址不是自己的地址而是AP的地址，所以判断信道竞争失败，TXOP归AP所有。随后，在AP的TXOP中，AP发送Trigger帧至STA1和STA2，触发STA1和STA2同时发送TB PPDU携带MU上行数据，并回复多STA块确认(Multi-STA BlockAck)帧确认传输成功。
实施例4，假设一个WLAN网络中包含1个AP和4个STA(STA1,STA2,STA3，STA4)。如果AP使用Single Protection的TXOP，STA也使用Single Protection的TXOP。STA1和STA2属于STA Group 1，STA3属于STA Group 2，STA4不属于任何STA Group。所有STA使用EDCA中的AC_VO接入类型，则AP和STA之间的帧交互如图18所示。
具体的，如图18所示，STA2在信道空闲AIFS时刻最先发送G-RTS帧，AP收到该G-RTS帧后，发现STA2属于STA Group 1且STA Group 2中有两个STA，所以回复CTS-to-self帧，将TXOP授予自己。STA3收到AP发送的CTS帧后，发现该CTS帧的接收地址不是自己的地址而是AP的地址，所以判断信道竞争失败，TXOP归AP所有。
随后，在AP的TXOP中，AP为了进一步确认STA Group 1中的上行低时延业务缓存状态，发送NFRP触发帧至STA Group 1中的全部或部分STA，并接收TB feedback NDP，从而确认STA Group 1中的STA1和STA2需要传输上行低时延业务。随后，AP发送触发帧至STA1和STA2，触发STA1和STA2同时发送TB PPDU携带MU上行数据，并回复Multi-STA BlockAck帧确认传输成功。
实施例5，假设一个WLAN网络中包含1个AP和4个STA(STA1,STA2,STA3，STA4)。如果AP使用长度受限的Multiple Protection的TXOP，STA使用Single Protection的TXOP。STA1和STA2属于STA Group 1，STA3属于STA Group 2，STA4不属于任何STA Group。所有STA使用EDCA中的AC_VO接入类型，则AP和STA之间的帧交互如图19所示。
具体的，如图19所示，STA1在信道空闲AIFS时刻最先发送G-RTS帧，AP收到该G-RTS帧后，发现STA1属于STA Group 1且STA Group 2中有两个STA，所以回复CTS-to-self帧，将TXOP授予自己。STA1收到AP发送的CTS帧后，发现该CTS帧的接收地址不是自己的地址而是AP的地址，所以判断信道竞争失败，TXOP归AP所有。随后，在AP的TXOP中，AP发送Trigger帧至STA1和STA2，触发STA1和STA2同时发送TB PPDU携带MU上行数据，并回复Multi-STA BlockAck帧确认传输成功。之后，AP发送MU下行数据至STA1和STA2，STA1和STA2通过TB PPDU回复BlockAck帧确认传输成功。至此，AP的TXOP结束，信道重新进入空闲状态。
实施例6，假设一个WLAN网络中包含1个AP和4个STA(STA1,STA2,STA3，STA4)。如果AP使用Single Protection的TXOP，STA也使用Single Protection的TXOP。STA1和STA2属于STA Group 1，STA3属于STA Group 2，STA4不属于任何STA Group。所有STA使用EDCA中的AC_VO接入类型，则AP和STA之间的帧交互如图20所示。
具体的，如图20所示，STA2在信道空闲AIFS时刻最先发送RTS帧，AP收到该RTS帧后，发现不是G-RTS帧，所以不触发任何本案所提的与分组相关的规则，依据EDCA的规则确定TXOP的归属。所以AP回复CTS帧至STA2，将TXOP授予STA2。STA2收到AP发送的CTS帧后，发现该CTS帧的接收地址是自己的地址，判断TXOP竞争成功。随后，在STA2的TXOP中，STA2发送上行SU UL数据，AP回复ACK帧确认传输成功。
上文结合图13至图20，详细描述了本申请的方法实施例，下文结合图21至图25，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图21示出了根据本申请实施例的STA 300的示意性框图。该STA 300存在待传输的上行数据，如图21所示，该STA 300包括：
通信单元310，用于发送第一媒体接入控制MAC帧；其中，该第一MAC帧用于竞争信道，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联。
在一些实施例中，该STA的分组信息包括以下至少之一：
该STA是否属于m个STA组中的STA组；
在该STA属于m个STA组中的STA组的情况下，该STA所属的STA组的标识，和/或，该STA所属的STA组内包含的STA的数量；
其中，该m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
在一些实施例中，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联，包括：
在该STA属于m个STA组中的第一STA组且该第一STA组内的STA数量小于第一阈值的情况下，该第一MAC帧对应的信道竞争关联的传输机会TXOP归该STA所有；和/或，
在该STA属于m个STA组中的第一STA组且该第一STA组内的STA数量大于或等于第一阈值的情况下，该第一MAC帧对应的信道竞争关联的TXOP归接入点AP所有；和/或，
在该STA不属于m个STA组中的任意一个STA组的情况下，该第一MAC帧对应的信道竞争关联的TXOP归该STA所有；
其中，该m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的触发帧之后在该TXOP内发送上行数据。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的触发帧之后在该TXOP内发送上行数据和接收下行数据。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的空数据物理协议数据单元反馈报告轮询NFRP触发帧之后反馈上行缓存状态信息，且该第一STA组中的部分或全部STA在TXOP内发送上行数据的资源与该第一STA组中的部分或全部STA反馈的上行缓存状态信息关联。
在一些实施例中，在m≥2的情况下，业务周期相同或相近的STA分别属于该m个STA组中不同的STA组。
在一些实施例中，该STA的分组信息与该第一MAC帧中的第一字段关联。
在一些实施例中，该第一字段为用于标识该STA的身份的字段。
在一些实施例中，该第一字段用于指示该STA的分组信息。
在一些实施例中，该STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，该STA对应的AP使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP。
在一些实施例中，该STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，该STA对应的AP使用的TXOP为单一保护的TXOP或多重保护的TXOP。
在一些实施例中，该上行数据至少包括上行时延敏感数据。
在一些实施例中，该第一MAC帧为组请求发送G-RTS帧。
在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的STA 300可对应于本申请方法实施例中的STA，并且STA 300中的各个单元的上述和其它操作和/或功能分别为了实现图13所示方法200中STA的相应流程，为了简洁，在此不再赘述。
图22示出了根据本申请实施例的AP 400的示意性框图。如图22所示，该AP 400包括：
通信单元410，用于接收站点STA发送的第一媒体接入控制MAC帧；
其中，该第一MAC帧用于竞争信道，该第一MAC帧对应的信道竞争结果与该STA的分组信息关联，该STA存在待传输的上行数据。
在一些实施例中，该STA的分组信息包括以下至少之一：
该STA是否属于m个STA组中的STA组；
在该STA属于m个STA组中的STA组的情况下，该STA所属的STA组的标识，和/或，该STA所属的STA组内包含的STA的数量；
其中，该m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
在一些实施例中，在该STA属于m个STA组中的第一STA组且该第一STA组内的STA数量小于第一阈值的情况下，该通信单元410还用于发送允许发送CTS帧，其中，该CTS帧用于宣告该第一MAC帧对应的信道竞争关联的传输机会TXOP归该STA所有；和/或，
在该STA属于m个STA组中的第一STA组且该第一STA组内的STA数量大于或等于第一阈值的情况下，该通信单元410还用于发送CTS至自身帧，其中，该CTS至自身帧用于宣告该第一MAC帧对应的信道竞争关联的TXOP归该AP所有；和/或，
在该STA不属于m个STA组中的任意一个STA组的情况下，该通信单元410还用于发送CTS帧，其中，该CTS帧用于宣告该第一MAC帧对应的信道竞争关联的TXOP归该STA所有；
其中，该m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归该AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的触发帧之后在该TXOP内发送上行数据。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归该AP所有的情况下，该第一STA组中的部分或全部STA在接收到该AP发送的触发帧之后在该TXOP内发送上行数据和接收下行数据。
在一些实施例中，在该第一MAC帧对应的信道竞争关联的TXOP归该AP所有的情况下，该AP400还包括：处理单元420；
该通信单元410还用于发送空数据物理协议数据单元反馈报告轮询NFRP触发帧，其中，该NFRP触发帧用于查询该第一STA组中的部分或全部STA的上行缓存状态信息；
该处理单元420用于根据该第一STA组中的部分或全部STA的上行缓存状态信息为该第一STA组中的部分或全部STA分配该TXOP中的多用户上行传输资源。
在一些实施例中，在m≥2的情况下，业务周期相同或相近的STA分别属于该m个STA组中不同的STA组。
在一些实施例中，该STA的分组信息与该第一MAC帧中的第一字段关联。
在一些实施例中，该第一字段为用于标识该STA的身份的字段。
在一些实施例中，该第一字段用于指示该STA的分组信息。
在一些实施例中，该STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，该STA对应的AP使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP。
在一些实施例中，该STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，该STA对应的AP使用的TXOP为单一保护的TXOP或多重保护的TXOP。
在一些实施例中，该上行数据至少包括上行时延敏感数据。
在一些实施例中，该第一MAC帧为组请求发送G-RTS帧。
在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的AP 400可对应于本申请方法实施例中的AP，并且AP 400中的各个单元的上述和其它操作和/或功能分别为了实现图13所示方法200中AP的相应流程，为了简洁，在此不再赘述。
图23是本申请实施例提供的一种通信设备500示意性结构图。图23所示的通信设备500包括处理器510，处理器510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
在一些实施例中，如图23所示，通信设备500还可以包括存储器520。其中，处理器510可以从存储器520中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器520可以是独立于处理器510的一个单独的器件，也可以集成在处理器510中。
在一些实施例中，如图23所示，通信设备500还可以包括收发器530，处理器510可以控制该收发器530与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器530可以包括发射机和接收机。收发器530还可以进一步包括天线，天线的数量可以为一个或多个。
在一些实施例中，处理器510可以实现STA中的处理单元的功能，或者，处理器510可以实现AP中的处理单元的功能，为了简洁，在此不再赘述。
在一些实施例中，收发器530可以实现STA中的通信单元的功能，为了简洁，在此不再赘述。
在一些实施例中，收发器530可以实现AP中的通信单元的功能，为了简洁，在此不再赘述。
在一些实施例中，该通信设备500具体可为本申请实施例的AP，并且该通信设备500可以实现本申请实施例的各个方法中由AP实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该通信设备500具体可为本申请实施例的STA，并且该通信设备500可以实现本申请实施例的各个方法中由STA实现的相应流程，为了简洁，在此不再赘述。
图24是本申请实施例的装置的示意性结构图。图24所示的装置600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
在一些实施例中，如图24所示，装置600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
在一些实施例中，处理器610可以实现STA中的处理单元的功能，或者，处理器610可以实现AP中的处理单元的功能，为了简洁，在此不再赘述。
在一些实施例中，该装置600还可以包括输入接口630。其中，处理器610可以控制该输入接口630与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。可选地，处理器610可以位于芯片内或芯片外。
在一些实施例中，输入接口630可以实现STA中的通信单元的功能，或者，输入接口630可以实现AP中的通信单元的功能。
在一些实施例中，该装置600还可以包括输出接口640。其中，处理器610可以控制该输出接口640与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。可选地，处理器610可以位于芯片内或芯片外。
在一些实施例中，输出接口640可以实现STA中的通信单元的功能，或者，输出接口640可以实现AP中的通信单元的功能。
在一些实施例中，该装置可应用于本申请实施例中的AP，并且该装置可以实现本申请实施例的各个方法中由AP实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该装置可应用于本申请实施例中的STA，并且该装置可以实现本申请实施例的各个方法中由STA实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，本申请实施例提到的装置也可以是芯片。例如可以是系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图25是本申请实施例提供的一种通信系统700的示意性框图。如图25所示，该通信系统700包括STA 710和AP 720。
其中，该STA 710可以用于实现上述方法中由STA实现的相应的功能，以及该AP 720可以用于实现上述方法中由AP实现的相应的功能，为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
在一些实施例中，该计算机可读存储介质可应用于本申请实施例中的AP，并且该计算机程序使得计算机执行本申请实施例的各个方法中由AP实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该计算机可读存储介质可应用于本申请实施例中的STA，并且该计算机程序使得计算机执行本申请实施例的各个方法中由STA实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
在一些实施例中，该计算机程序产品可应用于本申请实施例中的AP，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由AP实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该计算机程序产品可应用于本申请实施例中的STA，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由STA实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
在一些实施例中，该计算机程序可应用于本申请实施例中的AP，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由AP实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该计算机程序可应用于本申请实施例中的STA，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由STA实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑 功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。针对这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (40)

  1. 一种无线通信的方法，其特征在于，应用于站点STA，所述STA存在待传输的上行数据，所述方法包括：
    所述STA发送第一媒体接入控制MAC帧；其中，所述第一MAC帧用于竞争信道，所述第一MAC帧对应的信道竞争结果与所述STA的分组信息关联。
  2. 如权利要求1所述的方法，其特征在于，
    所述STA的分组信息包括以下至少之一：
    所述STA是否属于m个STA组中的STA组；
    在所述STA属于m个STA组中的STA组的情况下，所述STA所属的STA组的标识，和/或，所述STA所属的STA组内包含的STA的数量；
    其中，所述m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
  3. 如权利要求1或2所述的方法，其特征在于，
    所述第一MAC帧对应的信道竞争结果与所述STA的分组信息关联，包括：
    在所述STA属于m个STA组中的第一STA组且所述第一STA组内的STA数量小于第一阈值的情况下，所述第一MAC帧对应的信道竞争关联的传输机会TXOP归所述STA所有；和/或，
    在所述STA属于m个STA组中的第一STA组且所述第一STA组内的STA数量大于或等于第一阈值的情况下，所述第一MAC帧对应的信道竞争关联的TXOP归接入点AP所有；和/或，
    在所述STA不属于m个STA组中的任意一个STA组的情况下，所述第一MAC帧对应的信道竞争关联的TXOP归所述STA所有；
    其中，所述m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
  4. 如权利要求3所述的方法，其特征在于，
    在所述第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，所述第一STA组中的部分或全部STA在接收到所述AP发送的触发帧之后在所述TXOP内发送上行数据。
  5. 如权利要求3所述的方法，其特征在于，
    在所述第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，所述第一STA组中的部分或全部STA在接收到所述AP发送的触发帧之后在所述TXOP内发送上行数据和接收下行数据。
  6. 如权利要求3至5中任一项所述的方法，其特征在于，
    在所述第一MAC帧对应的信道竞争关联的TXOP归AP所有的情况下，所述第一STA组中的部分或全部STA在接收到所述AP发送的空数据物理协议数据单元反馈报告轮询NFRP触发帧之后反馈上行缓存状态信息，且所述第一STA组中的部分或全部STA在TXOP内发送上行数据的资源与所述第一STA组中的部分或全部STA反馈的上行缓存状态信息关联。
  7. 如权利要求2至6中任一项所述的方法，其特征在于，
    在m≥2的情况下，业务周期相同或相近的STA分别属于所述m个STA组中不同的STA组。
  8. 如权利要求1至7中任一项所述的方法，其特征在于，
    所述STA的分组信息与所述第一MAC帧中的第一字段关联。
  9. 如权利要求8所述的方法，其特征在于，
    所述第一字段为用于标识所述STA的身份的字段。
  10. 如权利要求8所述的方法，其特征在于，
    所述第一字段用于指示所述STA的分组信息。
  11. 如权利要求1至10中任一项所述的方法，其特征在于，
    所述STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，所述STA对应的AP使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP。
  12. 如权利要求1至10中任一项所述的方法，其特征在于，
    所述STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，所述STA对应的AP使用的TXOP为单一保护的TXOP或多重保护的TXOP。
  13. 如权利要求1至12中任一项所述的方法，其特征在于，
    所述上行数据至少包括上行时延敏感数据。
  14. 如权利要求1至13中任一项所述的方法，其特征在于，
    所述第一MAC帧为组请求发送G-RTS帧。
  15. 一种无线通信的方法，其特征在于，应用于接入点AP，所述方法包括：
    所述AP接收站点STA发送的第一媒体接入控制MAC帧；
    其中，所述第一MAC帧用于竞争信道，所述第一MAC帧对应的信道竞争结果与所述STA的分 组信息关联，所述STA存在待传输的上行数据。
  16. 如权利要求15所述的方法，其特征在于，
    所述STA的分组信息包括以下至少之一：
    所述STA是否属于m个STA组中的STA组；
    在所述STA属于m个STA组中的STA组的情况下，所述STA所属的STA组的标识，和/或，所述STA所属的STA组内包含的STA的数量；
    其中，所述m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
  17. 如权利要求15或16所述的方法，其特征在于，所述方法还包括：
    在所述STA属于m个STA组中的第一STA组且所述第一STA组内的STA数量小于第一阈值的情况下，所述AP发送允许发送CTS帧，其中，所述CTS帧用于宣告所述第一MAC帧对应的信道竞争关联的传输机会TXOP归所述STA所有；和/或，
    在所述STA属于m个STA组中的第一STA组且所述第一STA组内的STA数量大于或等于第一阈值的情况下，所述AP发送CTS至自身帧，其中，所述CTS至自身帧用于宣告所述第一MAC帧对应的信道竞争关联的TXOP归所述AP所有；和/或，
    在所述STA不属于m个STA组中的任意一个STA组的情况下，所述AP发送CTS帧，其中，所述CTS帧用于宣告所述第一MAC帧对应的信道竞争关联的TXOP归所述STA所有；
    其中，所述m个STA组是预先分配的STA组，m为正整数，且m＝1，或，m≥2。
  18. 如权利要求17所述的方法，其特征在于，在所述第一MAC帧对应的信道竞争关联的TXOP归所述AP所有的情况下，所述第一STA组中的部分或全部STA在接收到所述AP发送的触发帧之后在所述TXOP内发送上行数据。
  19. 如权利要求17所述的方法，其特征在于，在所述第一MAC帧对应的信道竞争关联的TXOP归所述AP所有的情况下，所述第一STA组中的部分或全部STA在接收到所述AP发送的触发帧之后在所述TXOP内发送上行数据和接收下行数据。
  20. 如权利要求17至19中任一项所述的方法，其特征在于，
    在所述第一MAC帧对应的信道竞争关联的TXOP归所述AP所有的情况下，所述方法还包括：
    所述AP发送空数据物理协议数据单元反馈报告轮询NFRP触发帧，其中，所述NFRP触发帧用于查询所述第一STA组中的部分或全部STA的上行缓存状态信息；
    所述AP根据所述第一STA组中的部分或全部STA的上行缓存状态信息为所述第一STA组中的部分或全部STA分配所述TXOP中的多用户上行传输资源。
  21. 如权利要求16至20中任一项所述的方法，其特征在于，
    在m≥2的情况下，业务周期相同或相近的STA分别属于所述m个STA组中不同的STA组。
  22. 如权利要求15至21中任一项所述的方法，其特征在于，
    所述STA的分组信息与所述第一MAC帧中的第一字段关联。
  23. 如权利要求22所述的方法，其特征在于，
    所述第一字段为用于标识所述STA的身份的字段。
  24. 如权利要求22所述的方法，其特征在于，
    所述第一字段用于指示所述STA的分组信息。
  25. 如权利要求15至24中任一项所述的方法，其特征在于，
    所述STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，所述STA对应的AP使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP。
  26. 如权利要求15至24中任一项所述的方法，其特征在于，
    所述STA使用的TXOP为单一保护的TXOP或长度受限的多重保护的TXOP，和/或，所述STA对应的AP使用的TXOP为单一保护的TXOP或多重保护的TXOP。
  27. 如权利要求15至26中任一项所述的方法，其特征在于，
    所述上行数据至少包括上行时延敏感数据。
  28. 如权利要求15至27中任一项所述的方法，其特征在于，
    所述第一MAC帧为组请求发送G-RTS帧。
  29. 一种站点STA，其特征在于，所述STA存在待传输的上行数据，所述STA包括：
    通信单元，用于发送第一媒体接入控制MAC帧；其中，所述第一MAC帧用于竞争信道，所述第一MAC帧对应的信道竞争结果与所述STA的分组信息关联。
  30. 一种接入点AP，其特征在于，包括：
    通信单元，用于接收站点STA发送的第一媒体接入控制MAC帧；
    其中，所述第一MAC帧用于竞争信道，所述第一MAC帧对应的信道竞争结果与所述STA的分组信息关联，所述STA存在待传输的上行数据。
  31. 一种站点STA，其特征在于，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，使得所述STA执行如权利要求1至14中任一项所述的方法。
  32. 一种接入点AP，其特征在于，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，使得所述AP执行如权利要求15至28中任一项所述的方法。
  33. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至14中任一项所述的方法。
  34. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求15至28中任一项所述的方法。
  35. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，当所述计算机程序被执行时，如权利要求1至14中任一项所述的方法被实现。
  36. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，当所述计算机程序被执行时，如权利要求15至28中任一项所述的方法被实现。
  37. 一种计算机程序产品，其特征在于，包括计算机程序指令，当所述计算机程序指令被执行时，如权利要求1至14中任一项所述的方法被实现。
  38. 一种计算机程序产品，其特征在于，包括计算机程序指令，当所述计算机程序指令被执行时，如权利要求15至28中任一项所述的方法被实现。
  39. 一种计算机程序，其特征在于，当所述计算机程序被执行时，如权利要求1至14中任一项所述的方法被实现。
  40. 一种计算机程序，其特征在于，当所述计算机程序被执行时，如权利要求15至28中任一项所述的方法被实现。
PCT/CN2023/100190 2023-06-14 2023-06-14 无线通信的方法及设备 Ceased WO2024254782A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202380099196.1A CN121359578A (zh) 2023-06-14 2023-06-14 无线通信的方法及设备
PCT/CN2023/100190 WO2024254782A1 (zh) 2023-06-14 2023-06-14 无线通信的方法及设备
EP23941019.4A EP4730896A1 (en) 2023-06-14 2023-06-14 Wireless communication method and device
US19/411,639 US20260095944A1 (en) 2023-06-14 2025-12-08 Method for wireless communication, sta, and ap

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/100190 WO2024254782A1 (zh) 2023-06-14 2023-06-14 无线通信的方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/411,639 Continuation US20260095944A1 (en) 2023-06-14 2025-12-08 Method for wireless communication, sta, and ap

Publications (2)

Publication Number Publication Date
WO2024254782A1 true WO2024254782A1 (zh) 2024-12-19
WO2024254782A9 WO2024254782A9 (zh) 2025-11-27

Family

ID=93851087

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/100190 Ceased WO2024254782A1 (zh) 2023-06-14 2023-06-14 无线通信的方法及设备

Country Status (4)

Country Link
US (1) US20260095944A1 (zh)
EP (1) EP4730896A1 (zh)
CN (1) CN121359578A (zh)
WO (1) WO2024254782A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20250234375A1 (en) * 2024-01-15 2025-07-17 Qualcomm Incorporated Access point (ap)-aided downlink transmission opportunity (txop) preemption by stations (stas) with low-latency uplink traffic

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102883460A (zh) * 2011-07-15 2013-01-16 中兴通讯股份有限公司 一种业务数据传输方法及系统
CN103096440A (zh) * 2011-11-07 2013-05-08 中兴通讯股份有限公司 一种无线信道接入方法及系统
WO2015113204A1 (zh) * 2014-01-28 2015-08-06 华为技术有限公司 一种数据传输方法及站点
US20160374112A1 (en) * 2015-06-16 2016-12-22 Qualcomm Incorporated Transmission opportunity contention for multiple user operation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102883460A (zh) * 2011-07-15 2013-01-16 中兴通讯股份有限公司 一种业务数据传输方法及系统
CN103096440A (zh) * 2011-11-07 2013-05-08 中兴通讯股份有限公司 一种无线信道接入方法及系统
WO2015113204A1 (zh) * 2014-01-28 2015-08-06 华为技术有限公司 一种数据传输方法及站点
US20160374112A1 (en) * 2015-06-16 2016-12-22 Qualcomm Incorporated Transmission opportunity contention for multiple user operation

Also Published As

Publication number Publication date
CN121359578A (zh) 2026-01-16
WO2024254782A9 (zh) 2025-11-27
US20260095944A1 (en) 2026-04-02
EP4730896A1 (en) 2026-04-22

Similar Documents

Publication Publication Date Title
US11129160B2 (en) Method and apparatus for transmitting data frame in WLAN system
JP6470417B2 (ja) 無線ｌａｎシステムにおけるトリガフレームの受信後の上りリンク伝送方法及び装置
US12150075B2 (en) Wireless communication method using multilink, and wireless communication terminal using same
US10004109B2 (en) Method and apparatus for recovering data unit in wireless communication system
WO2015194727A1 (ko) 프레임을 전송하는 방법 및 장치
EP4376478A1 (en) Method and apparatus for nstr communication in communication system supporting multiple links
WO2024137384A1 (en) Cross-link request to send (rts)-clear to send (cts)
US20260095944A1 (en) Method for wireless communication, sta, and ap
WO2022210090A1 (ja) アクセスポイント装置、ステーション装置および通信方法
US20250126637A1 (en) Dynamic sub-channel pre-allocation
US20240188135A1 (en) Channel backoff in a wireless network
US20260101334A1 (en) Wireless communication method and device
US20250344241A1 (en) Prioritized channel access for low latency wireless traffic
WO2025036277A1 (zh) 通信方法和通信装置
JP2026029145A (ja) ステーション装置、アクセスポイント装置
JP2026009635A (ja) アクセスポイント装置および通信方法
KR20260004858A (ko) 무선 랜 시스템에서 채널 접속을 위한 방법 및 장치
WO2026013949A1 (ja) アクセスポイント装置および通信方法
JP2024172978A (ja) アクセスポイント装置及びステーション装置
KR20260030392A (ko) 무선 랜 시스템에서 프리앰션을 위한 방법 및 장치
KR20260025776A (ko) 저지연 무선 통신 방법 및 이를 사용하는 무선 통신 단말
KR20260010272A (ko) 무선 랜 시스템에서 우선순위 기반 채널 접속을 위한 방법 장치
WO2024189759A1 (ja) アクセスポイント装置、ステーション装置および通信方法
JP2023114923A (ja) 通信装置および通信方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23941019

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023941019

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023941019

Country of ref document: EP

Effective date: 20260114

ENP Entry into the national phase

Ref document number: 2023941019

Country of ref document: EP

Effective date: 20260114

ENP Entry into the national phase

Ref document number: 2023941019

Country of ref document: EP

Effective date: 20260114

ENP Entry into the national phase

Ref document number: 2023941019

Country of ref document: EP

Effective date: 20260114

WWP Wipo information: published in national office

Ref document number: 2023941019

Country of ref document: EP