WO2022033283A1 - 一种信道竞争方法及相关装置 - Google Patents

一种信道竞争方法及相关装置 Download PDF

Info

Publication number
WO2022033283A1
WO2022033283A1 PCT/CN2021/107596 CN2021107596W WO2022033283A1 WO 2022033283 A1 WO2022033283 A1 WO 2022033283A1 CN 2021107596 W CN2021107596 W CN 2021107596W WO 2022033283 A1 WO2022033283 A1 WO 2022033283A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
time period
time
cca
channel
Prior art date
Application number
PCT/CN2021/107596
Other languages
English (en)
French (fr)
Inventor
李伊青
李云波
郭宇宸
淦明
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to AU2021323746A priority Critical patent/AU2021323746B2/en
Priority to JP2023510452A priority patent/JP2023537151A/ja
Priority to EP21855336.0A priority patent/EP4191902A4/en
Priority to BR112023002705A priority patent/BR112023002705A2/pt
Priority to CN202180055788.4A priority patent/CN116114296A/zh
Priority to MX2023001856A priority patent/MX2023001856A/es
Priority to KR1020237008043A priority patent/KR20230048390A/ko
Priority to CA3189314A priority patent/CA3189314A1/en
Publication of WO2022033283A1 publication Critical patent/WO2022033283A1/zh
Priority to US18/168,048 priority patent/US20230199850A1/en

Links

Images

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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a channel contention method and related devices.
  • the continuous technological goal of the evolution of the next generation wireless local area network (WLAN) or cellular network is to continuously improve the throughput rate.
  • the protocol of the WLAN system is mainly discussed in the Institute of Electrical and Electronics Engineers (IEEE, institute of electrical and electronics engineers) standard group, based on the previous standard protocol IEEE 802.11a/b/g/n/ac/ax, etc., the next generation WiFi
  • IEEE 802.11be takes extremely high throughput (EHT) as a technical goal, which involves the key technology multi-link (multi-link) communication.
  • multi-link communication The core idea of multi-link communication is that WLAN devices supporting the next-generation IEEE 802.11 standard have the ability to transmit and receive in multiple frequency bands (multi-band), thereby using a larger bandwidth for data transmission, thereby significantly improving throughput.
  • multi-frequency bands include but are not limited to: 2.4GHz WiFi frequency band, 5GHz WiFi frequency band and 6GHz WiFi frequency band.
  • a frequency band that a communication device accesses and transmits can be called a link, and multiple frequency bands that a communication device accesses and transmits can be called a multi-link.
  • the next-generation IEEE 802.11 standard station device that supports multiple links at the same time is called a multi-link device (MLD), and a multi-link device can support multi-link communication.
  • MLD multi-link device
  • the access point (AP) multi-link device includes AP1 and AP2, and the non-Access Point Station (non-Access Point Station, non-AP STA) MLD includes non- - APSTA1 and non-APSTA2.
  • AP1 communicates with non-APSTA1 through link 1
  • AP2 communicates with non-APSTA2 through link 2.
  • the communication between the AP MLD and the STA MLD is multi-link communication.
  • the channel interference may affect the idleness of other links.
  • Channel assessment (clear channel assessment, CCA), which may determine that other links are in a blindness period (or, deaf period). Among them, the blind state means that the information on the channel cannot be monitored.
  • the non-STR MLD can set the medium sync delay timer for other links, In this counter, the energy detection (ED) threshold of (to be decided, TBD) is used to perform CCA on other links. If the CCA detection of one of the other links fails, it means that the overlapping basic service set (overlapping basic service set, OBSS) frame is being transmitted on the link. When the transmission of the OBSS frame ends, the non-STR MLD starts to contend for the channel and starts enhanced distributed channel access (EDCA).
  • ED energy detection
  • the transmission opportunity (TXOP) corresponding to the link may not end, which results in an acknowledgement (ACK) frame corresponding to the OBSS frame after the non-STR MLD accesses the channel. Collision. Therefore, how to avoid inter-frame collision and interference during EDCA has become a technical problem that needs to be solved urgently.
  • the present application provides a channel competition method and related apparatus, which can support multi-link devices that cannot transmit and receive at the same time, reduce the problems of inter-frame collision and interference when performing channel competition, and improve communication efficiency.
  • an embodiment of the present application provides a channel contention method, the method comprising:
  • the first non-access point station of the first multi-link device After the data transmission on the first link is completed or an acknowledgment block corresponding to the data is received on the first link, the first non-access point station of the first multi-link device is within the first time period Perform idle channel assessment CCA detection on the second link, and the start time corresponding to the first time period is the same as the time when the data transmission on the first link is completed;
  • the first non-access point station When the CCA detection on the second link fails, the first non-access point station performs channel contention on the second link according to a second time period.
  • performing idle channel assessment CCA detection on the second link within the first time period includes:
  • the first non-access point site adjusts the CCA threshold to obtain an adjusted CCA threshold, where the adjusted CCA threshold is lower than the CCA threshold;
  • the first non-access point station performs the CCA detection on the second link according to the adjusted CCA threshold within the first time period.
  • a more stringent CCA threshold may be used to perform CCA detection on the second link, so as to avoid the subsequent determination that the data transmission on the second link is completed. Then prepare for the problem of inter-frame collision and interference caused by channel contention on the second link.
  • the CCA threshold includes an energy detection threshold or an in-frame detection threshold.
  • performing channel contention on the second link according to the second time period includes:
  • the first non-access point station will start the second time period after the end time corresponding to the second time period.
  • the first non-access point station will be after the end time corresponding to the first time period or the first time period. After the end time corresponding to the two time periods, channel contention is performed on the second link.
  • the method further includes:
  • the first non-access point station updates the network configuration vector NAV according to the radio frame, and obtains the updated NAV, wherein the radio frame is when the data is being transmitted on the first link or when the A radio frame sent to a second non-access point station on the second link when the acknowledgment block corresponding to the data is being transmitted on the first link, where the second non-access point station is the non-access point sites other than the first non-access point site in the first multilink device;
  • the first non-access point station performs channel contention on the second link according to the updated NAV.
  • channel competition is implemented on the second link according to the updated NAV, so as to avoid causing channel competition on the second link after it is determined that the data transmission on the second link is completed. Therefore, the problem of inter-frame collision and interference is reduced, and the communication efficiency is improved.
  • performing channel contention on the second link according to the updated NAV includes:
  • the first non-access point station If the updated NAV is less than the time when the data transmission is completed on the first link or the time when the acknowledgment block is received on the first link, the first non-access point station then perform the CCA detection on the second link within the first time period; when the CCA detection on the second link fails, the first non-access point station performing channel contention on the second link during the second time period; or,
  • the first non-access point station If the updated NAV is greater than the time when the data transmission on the first link is completed or the time when the acknowledgment block is received on the first link, the first non-access point station Then, channel contention is performed on the second link when the updated NAV backs off to zero.
  • the second time period is an extended inter-frame interval EIFS time.
  • an embodiment of the present application provides a communication apparatus, which is applied in a first multi-link device, where the communication apparatus may be the first multi-link device or a chip in the first multi-link device, such as Wi-Fi chips, including:
  • the processing unit is configured to, after the data transmission on the first link is completed or after receiving the acknowledgment block corresponding to the data on the first link, the first non-access point site of the first multi-link device is Perform idle channel assessment CCA detection on the second link within a first time period, and the start time corresponding to the first time period is the same as the time when the data transmission on the first link is completed;
  • the processing unit is further configured to, when the CCA detection on the second link fails, the first non-access point station conducts a channel on the second link according to a second time period compete.
  • the processing unit when performing idle channel assessment CCA detection on the second link within the first time period, is configured to adjust the CCA threshold to obtain an adjusted CCA threshold, where the adjusted CCA threshold is lower than the CCA threshold; performing the CCA detection on the second link according to the adjusted CCA threshold within the first time period.
  • the CCA threshold includes an energy detection threshold or an in-frame detection threshold.
  • the processing unit is configured to connect the second link after the end time corresponding to the second time period channel contention;
  • the processing unit is configured to be after the end time corresponding to the first time period or the second time period Channel contention is performed on the second link after the corresponding end time.
  • the processing unit is further configured to update the network configuration vector NAV according to the radio frame, and obtain the updated NAV, wherein the radio frame is when the data is being transmitted on the first link or A radio frame sent to a second non-access point station on the second link when the acknowledgment block corresponding to the data is being transmitted on the first link, the second non-access point station is a non-access point site other than the first non-access point site in the first multi-link device; and performs channel competition on the second link according to the updated NAV.
  • the processing unit is configured to: performing the CCA detection on the second link within the first time period; when the CCA detection on the second link fails, the first non-access point station will perform the CCA detection on the second link according to the second a time period in which channel contention is performed on the second link; or,
  • the processing unit is configured to: When the updated NAV backs off to zero, channel contention is performed on the second link.
  • the second time period is an extended inter-frame interval EIFS time.
  • an embodiment of the present application provides a communication device, specifically a first multi-link device, where the first multi-link device has a function of implementing the behavior of the first multi-link device in the above method.
  • the hardware implementation can also be implemented by hardware executing the corresponding software implementation.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the first multi-link device includes a processor and a transceiver, the processor being configured to support the first multi-link device to perform the corresponding functions in the above method.
  • the transceiver is used to support the communication of the first multi-link device, and to receive the information, frames, data packets or instructions involved in the above method.
  • the first multilink device may also include a memory for coupling with the processor that holds program instructions and data necessary for the first multilink device.
  • an embodiment of the present application provides a wireless communication system, where the system includes the first multilink device described in the third aspect above.
  • an embodiment of the present application provides a chip or a chip system, including an input and output interface and a processing circuit, the input and output interface is used for exchanging information or data, and the processing circuit is used for running instructions, so that the installation of the An apparatus of a chip or a system of chips performs the channel contention method of any one of the above-mentioned aspects.
  • embodiments of the present application provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and the instructions can be executed by one or more processors on a processing circuit.
  • the computer When running on a computer, the computer is caused to perform the channel contention method described in any of the above aspects.
  • the present application provides a computer program product comprising instructions that, when executed on a computer, cause the computer to execute the channel contention method described in any one of the preceding aspects.
  • the present application provides a system-on-chip
  • the system-on-chip includes a processor, and is configured to support a device on which the system-on-chip is installed to implement the channel contention method described in any one of the foregoing aspects, such as processing the channel contention method described above
  • the frame and/or information involved in the .
  • the chip system further includes a memory for storing necessary program instructions and data of the data sending device.
  • the system-on-chip may consist of chips, or may include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of a scenario of multi-link communication provided by an embodiment of the present application
  • Fig. 2a is a schematic diagram of NAV setting provided by an embodiment of the present application.
  • Fig. 2b is another schematic diagram of the NAV setting provided by the embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a wireless communication system provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a multi-link device provided by an embodiment of the present application.
  • FIG. 5 is another schematic structural diagram of a multi-link device provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a contention channel provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another contention channel provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a channel contention method provided by an embodiment of the present application.
  • FIG. 9 is a schematic time sequence diagram of a channel contention method provided by an embodiment of the present application.
  • FIG. 10 is another schematic sequence diagram of a channel contention method provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another channel contention method provided by an embodiment of the present application.
  • FIG. 12 is another schematic sequence diagram of a channel contention method provided by an embodiment of the present application.
  • FIG. 13 is another schematic sequence diagram of the channel contention method provided by the embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 15 is another schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • TXOP Transmission Opportunity
  • the TXOP duration refers to a period of time during which a station (here a station may refer to an access point or a non-access point station) obtains a transmission opportunity and performs data transmission without interference.
  • a site that obtains TXOP can be called a TXOP holder (TXOP holder).
  • TXOP duration includes the duration required by the TXOP holder to transmit one or more data and the corresponding immediate response frame (the immediate response frame here may refer to an acknowledgment frame or a block acknowledgment, etc.).
  • the TXOP duration cannot exceed an upper limit, which is called the TXOP limit (TXOP limit).
  • the value of the TXOP limit is subject to national and/or regional regulations.
  • the AP may broadcast the value of the TXOP limit through a beacon frame or a probe response frame.
  • the TXOP limit is also related to the access category (access category, AC, or called access type) contending for the transmission opportunity.
  • Table 1 shows the values of the TXOP limit corresponding to four different access types.
  • AC_VO indicates that the access type (or access type) is a voice (voice) stream
  • AC_VI indicates that the access type is a video (video) stream
  • AC_BE indicates that the access type is a best effort stream
  • AC_BK indicates that the access type is a best effort stream.
  • Type is background stream.
  • Table 1 Description of TXOP limit corresponding to different access types
  • AC AC_BK AC_BE AC_VI AC_VO TXOP limit 2.528ms 2.528ms 4.096ms 2.080ms
  • the priority of the voice stream is greater than the priority of the video stream is greater than the priority of the best effort stream is greater than the priority of the background stream, that is, the priority order from high to low is: AC_VO, AC_VI, AC_BE, AC_BK. Understandably, the higher the priority, the higher the ability to preempt the channel.
  • data transmission and “transmission data” in the embodiments of the present application generally refer to communication, where “data” generally refers to communication information, which is not limited to data information, but may also be signaling information and the like.
  • NAV Network allocation vector
  • Virtual carrier sense is a kind of carrier sense, which is to know the channel situation through control information instead of actually detecting the physical channel. Specifically, the virtual carrier senses the relevant information carried in the medium access control (MAC) frame to implement logical prediction, that is, each frame carries the duration information of the next frame of the sending site, The associated stations make predictions of channel occupancy based on this duration information. If a station does not hear the duration information, for example, when monitoring the carrier, the duration field of this frame has been transmitted, the station can only rely on the physical layer detection.
  • MAC medium access control
  • Virtual carrier sense can be implemented using the network allocation vector NAV.
  • NAV is essentially a countdown timer that gradually decreases over time, and when the countdown reaches 0, the medium is considered to be idle. Therefore, the virtual carrier sense technology sets and updates the timing value of the NAV with the appropriate value at the appropriate time. Specifically, after a station receives a frame, if the receiving address of the frame is not the station, the station can update the NAV according to the duration field in the received frame. If the receiving address of the frame is this station, it means that this station is the receiving station, and the NAV cannot be updated.
  • the NAV value is calculated from the end time of the received frame.
  • the above-mentioned duration field can be used to inform other non-receiving stations of the length of time the channel is occupied, preventing other non-receiving stations from accessing the channel and transmitting data.
  • a value in the duration field can be set so that the TXOP duration does not exceed the TXOP limit.
  • FIG. 2a is a schematic diagram of the NAV setting provided by the embodiment of the present application.
  • the sending station obtains the TXOP, it sets the value of the duration field in the first transmission frame (request to send (RTS) frame in Figure 2a), so that the TXOP duration does not exceed the TXOP limit.
  • the value of the duration field is set in the subsequent frame, so that the end time point corresponding to the duration field in the subsequent frame is the same as the end time point corresponding to the duration field of the previous frame.
  • the RTS frame includes a duration field
  • the aggregation media access control protocol unit (aggregation MAC protocol data unit, A-MPDU) 1 includes a duration field
  • A-MPDU2 also includes a duration field.
  • the value of the duration field of the A-MPDU1 is greater than the value of the duration field of the A-MPDU1
  • the value of the duration field of the A-MPDU1 is greater than the value of the duration field of the A-MPDU2.
  • the end time point of the NAV corresponding to any one frame of the RTS frame, A-MPDU1 and A-MPDU2 is the same time point.
  • the RTS frame, A-MPDU1 and A-MPDU2 correspond to any one of the frames.
  • the end time points of the NAVs are all the same time point. It is understandable that in FIG. 2a, the value of the duration field carried in the RTS frame may be the same as the TXOP duration.
  • FIG. 2b is another schematic diagram of the NAV setting provided by the embodiment of the present application.
  • the value of the duration field set in the first sending frame (the RTS frame in Figure 2b) is less than the TXOP limit, or the TXOP duration set for the first time is less than the TXOP limit
  • the value of the duration field can be set in subsequent frames, so that the current TXOP duration exceeds the end time point of the previous TXOP duration, but from the first set TXOP duration, the total TXOP duration cannot exceed the TXOP limit.
  • the RTS frame includes a duration field
  • the A-MPDU1 includes a duration field.
  • the end time point 1 of the NAV corresponding to the RTS frame is earlier than the end time point 2 of the NAV corresponding to the A-MPDU1. That is, after the non-receiving station updates the NAV according to the duration field included in the RTS frame and the duration field included in the A-MPDU1, the end time point 1 of the NAV corresponding to the RTS frame is earlier than the end time point 2 of the NAV corresponding to the A-MPDU1 . Moreover, the end time point 1 of the NAV corresponding to the RTS frame and the end time point 2 of the NAV corresponding to the A-MPDU1 are both earlier than the TXOP limit.
  • the technical solutions of the embodiments of the present application may be applied to a wireless communication system, and the wireless communication system may be a wireless local area network (wireless local area network, WLAN) or a cellular network.
  • the methods involved in the embodiments of the present application may be implemented by a communication device in a wireless communication system or a chip or processor in the communication device.
  • the communication device may be a wireless communication device that does not support STR.
  • the communication device may be called It is a multi-link device or a multi-band device. Compared with communication devices that only support single-link transmission, multi-link devices have higher transmission efficiency and greater throughput.
  • a multi-link device includes one or more affiliated stations (affiliated STAs), and an affiliated station is a logical station that can work on a link.
  • the affiliated station may be an access point (access point, AP) or a non-access point station (non-access point station, non-AP STA).
  • this application refers to a multi-link device whose site is an AP as a multi-link AP or a multi-link AP device or an AP multi-link device (AP multi-link device, AP MLD).
  • a multi-link device that is a non-AP STA may be called a multi-link STA or a multi-link STA device or a STA multi-link device (STA multi-link device, STA MLD).
  • STA multi-link device STA multi-link device, STA MLD.
  • a multi-link device includes a subordinate station is also briefly described as "a multi-link device includes a station” in this embodiment of the present application.
  • a multi-link device may include multiple logical sites, each logical site works on one link, but allows multiple logical sites to work on the same link.
  • the link identifier mentioned below represents a station working on a link, that is, if there are more than one station on a link, more than one link identifier is required to represent them.
  • the link mentioned below sometimes also refers to the station operating on that link.
  • a link identifier may be used to identify a link or a station on a link.
  • the AP multi-link device and the STA multi-link device may negotiate or communicate the correspondence between the link identifier and a link or a station on a link. Therefore, in the process of data transmission, there is no need to transmit a large amount of signaling information to indicate the link or the stations on the link, and the link identifier can be carried, which reduces signaling overhead and improves transmission efficiency.
  • a management frame such as a beacon frame
  • each link identification The information field may suggest a correspondence between a link ID and a station operating on a link.
  • Each link identification information field includes a link identification, and also includes: one or more of MAC address, operation set, and channel number, wherein one or more of MAC address, operation set, and channel number can indicate a link .
  • the AP multi-link device and the STA multi-link device negotiate multiple link identification information fields.
  • the AP multi-link device or the STA multi-link device will use the link identifier to represent a site in the multi-link device.
  • the link identifier can also represent the MAC address of the site, the working set of operations , one or more attributes in the channel number.
  • the MAC address may also be replaced with an association identifier (association identifier, AID) of the AP multi-link device after the association.
  • the link ID (it is a digital ID)
  • the meaning of the representation includes not only the operation set where the link is located, the channel number, but also the ID of the site working on the link. , such as the MAC address of the site or the associated identification AID.
  • Multilink devices can follow the IEEE 802.11 series of protocols for wireless communication, such as very high throughput sites, or IEEE 802.11be-based or compatible IEEE 802.11be-enabled sites to communicate with other devices.
  • the channel contention method provided by the embodiment of the present application can be applied to a scenario where one node and one or more nodes perform data transmission; it can also be applied to a single-user uplink/downlink data transmission scenario, and a multi-user uplink/downlink data transmission scenario.
  • downlink data transmission scenarios it can also be applied to device to device (device to device, D2D) data transmission scenarios.
  • any of the above nodes may be an AP multi-link device, or may be a multi-link non-AP device.
  • data transmission between an AP multi-link device and one or more non-AP multi-link devices; or data transmission between a non-AP multi-link device and one or more AP multi-link devices or a scenario of data transmission between a non-AP multi-link device and a non-AP multi-link device; or a scenario of data transmission between an AP multi-link device and an AP multi-link device this application implements the The example does not limit this.
  • a channel contention method provided by the embodiment of the present application can also be applied to a legacy site that only supports transmission on a single link, which is not limited herein.
  • FIG. 3 is a schematic structural diagram of a wireless communication system provided by an embodiment of the present application.
  • FIG. 3 takes a wireless local area network as an example.
  • the wireless communication system includes: an AP multi-link device 100 and one or more non-AP multi-link devices (such as the non-AP multi-link device 200, non-AP multi-link device 200 in FIG. -AP multi-link device 300, non-AP multi-link device 400).
  • the AP multi-link device is a multi-link device that provides services for the non-AP multi-link device, and the non-AP multi-link device can communicate with the AP multi-link device using multiple links, thereby achieve the effect of increasing throughput.
  • the numbers of AP multi-link devices and non-AP multi-link devices in FIG. 3 are only exemplary.
  • a multi-link device (such as any one of AP multi-link device 100 , non-AP multi-link device 200 , non-AP multi-link device 300 , and non-AP multi-link device 400 in FIG. 3 )
  • Multi-link device is a device with wireless communication function
  • the device can be a complete device, and can also be a chip or processing system installed in the complete device. Under the control of a chip or a processing system, the methods and functions of the embodiments of the present application are implemented.
  • the non-AP multi-link device in the embodiment of the present application has a wireless transceiver function, can support 802.11 series protocols, and can communicate with the AP multi-link device or other non-AP multi-link devices.
  • a non-AP multilink device is any user communication device that allows a user to communicate with an AP and thus with a WLAN.
  • the non-AP multilink device may be a tablet, desktop, laptop, notebook, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant , PDA), mobile phones and other user equipment that can be networked, or IoT nodes in the Internet of Things, or in-vehicle communication devices in the Internet of Vehicles, etc.; non-AP multi-link devices can also be the chips and processing systems in these terminals.
  • the AP multi-link device in the embodiment of the present application is an apparatus for providing services for the non-AP multi-link device, and can support the 802.11 series of protocols.
  • the AP multi-link device may be a communication entity such as a communication server, router, switch, and network bridge, or the AP multi-link device may include various forms of macro base station, micro base station, relay station, etc.
  • the AP multi-link device The chips and processing systems in these various forms of devices can also be used to implement the methods and functions of the embodiments of the present application.
  • multi-link devices can support high-speed and low-latency transmission.
  • multi-link devices can also be used in more scenarios, such as sensor nodes in smart cities ( For example, smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, TVs, stereos, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment Terminals (such as AR, VR and other wearable devices), smart devices in smart office (such as printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (such as vending machines, commercial Super self-service navigation desk, self-service cash register equipment, self-service ordering machine, etc.).
  • the specific forms of the non-AP multi-link device and the AP multi-link device are not limited in the embodiments of the present application, which are only exemplary descriptions herein.
  • the 802.11 protocol may be a protocol that supports 802.11be or is compatible with 802.11be.
  • FIG. 4 is a schematic structural diagram of a multi-link device provided by an embodiment of the present application.
  • the IEEE 802.11 standard focuses on the 802.11 physical layer (PHY) and media access control (MAC) layers in multi-link devices.
  • the multiple non-AP STAs included in the multi-link device are independent of each other at the low MAC (low MAC) layer and the PHY layer, and are also independent of each other at the high MAC (high MAC) layer.
  • FIG. 5 is another schematic structural diagram of a multi-link device provided by an embodiment of the present application.
  • non-AP multi-link devices can adopt a structure with independent high MAC layers, while AP multi-link devices adopt a structure shared by high MAC layers; it can also be non-AP multi-link devices.
  • the AP multi-link device adopts the structure of the high MAC layer shared by each other; the non-AP multi-link device and the AP multi-link device can also use the high MAC layer shared structure; It may be that both the non-AP multi-link device and the AP multi-link device adopt a structure in which the high MAC layer is independent of each other.
  • This embodiment of the present application does not limit the schematic diagram of the internal structure of the multi-link device, and FIG. 4 and FIG. 5 are only exemplary descriptions.
  • both the high MAC layer and the low MAC layer may be implemented by a processor in a chip system of a multi-link device, and may also be implemented by different processing modules in a chip system respectively.
  • the multi-link device in this embodiment of the present application may be a single-antenna device or a multi-antenna device.
  • it may be a device with more than two antennas.
  • This embodiment of the present application does not limit the number of antennas included in the multi-link device.
  • the multi-link device may allow services of the same access type to be transmitted on different links, and even allow the same data packets to be transmitted on different links; it may also not allow services of the same access type It is transmitted on different links, but allows services of different access types to be transmitted on different links.
  • the frequency band in which the multi-link device operates may include one or more frequency bands among sub 1GHz, 2.4GHz, 5GHz, 6GHz, and high frequency 60GHz.
  • FIG. 6 is a schematic diagram of a contention channel provided by an embodiment of the present application.
  • the AP MLD includes AP1 and AP2, and the AP MLD does not include AP3.
  • AP3 can be a single device or belong to other AP MLDs.
  • AP1 works on link 1 (link1)
  • AP2 works on link 2 (link2).
  • Non-AP MLD includes non-AP STA1 and non-AP STA2, non-AP MLD does not include non-AP STA3, non-AP STA3 can be a single device, or it can belong to other non-AP MLD.
  • non-AP STA1 works on link 1 (link1)
  • non-AP STA2 and non-AP STA3 work on link 2 (link2).
  • the non-AP STA1 sends a Request-To-Send (RTS) frame to AP1 on Link 1.
  • RTS Request-To-Send
  • AP1 receives the request to send frame on link 1, it can reply to the non-AP STA1 on link 1 with a Clear-To-Send (CTS) frame.
  • CTS Clear-To-Send
  • the non-AP STA1 receives the idle transmission frame on link 1, it can send a data frame to AP1 on link 1.
  • AP1 can send an acknowledgment block (block ACK) to non-AP STA1 on link 1.
  • block ACK acknowledgment block
  • channel interference may affect the CCA of link 2. This may fail to monitor the channel information of link 2, that is, link 2 is in a blindness period (or, deaf period). Among them, the blind state means that the information on the channel cannot be monitored. Further, when there is data transmission on link 1, even if non-AP STA2 sends a request to send frame on link 2, it may be unable to receive the request to send frame due to channel interference. Therefore, this may cause the non-AP STA2 to miss the refresh of the network allocation vector (NAV).
  • NAV network allocation vector
  • non-AP STA3 begins to contend for the channel. Further, the non-AP STA3 sends a request to send frame on link 2, and the non-AP STA3 also receives an idle send frame on link 2. Next, non-AP STA3 may send data frames to AP2 on link 2. At this time, a request-to-send frame is being transmitted on link 2. That is, the data frame sent by non-AP STA3 to AP2 on link 2 collides with the request-to-send frame on link 2. Therefore, the collision problem caused in this case is the blind problem.
  • the non-STR MLD can set a media synchronization delay (medium sync delay) timer.
  • the energy detection (ED) threshold of to be decided, TBD) performs CCA on other links. If the CCA detection of one of the other links fails, it means that the overlapping basic service set (overlapping basic service set, OBSS) frame is being transmitted on the link.
  • the non-STR MLD starts to contend for the channel and starts enhanced distributed channel access (EDCA). That is, after the transmission of the OBSS frame is completed, a request to send frame is sent on the link.
  • EDCA enhanced distributed channel access
  • the transmission opportunity (TXOP) corresponding to the OBSS frame on the link has not yet ended, that is, the acknowledgment block corresponding to the OBSS frame is being transmitted on the link.
  • the acknowledgement block corresponding to the OBSS frame on the link collides with the request-to-send frame on the link.
  • FIG. 7 is a schematic diagram of still another contention channel provided by an embodiment of the present application.
  • STR AP MLD includes AP1 and AP2, STR AP MLD does not include AP3, AP3 can be a single device, or it can belong to other AP MLD.
  • AP1 works on link 1 (link1)
  • AP2 and AP3 work on link 2 (link2).
  • non-STR non-AP MLD includes non-AP STA1 and non-AP STA2
  • non-STR non-AP MLD does not include non-AP STA3, non-AP STA3 can be a single device or belong to other non-AP MLDs.
  • non-AP STA1 works on link 1 (link1)
  • non-AP STA2 and non-AP STA3 work on link 2 (link2).
  • non-AP STA1 When non-AP STA1 sends an uplink PPDU to AP1 on link 1, link 2 is in a blind state due to the small frequency interval between link 1 and link 2 (see blindness for non-AP STA shown in Figure 7). 2).
  • the non-AP STA2 starts the medium sync delay timer. That is, the end time of the uplink PPDU on link 1 is aligned/same as the start time of the media synchronization delay.
  • the non-AP STA2 uses a TBD (To be Decided) energy detection (ED) threshold, such as -82dbm to -62dbm, to perform CCA detection on link 2.
  • TBD To be Decided
  • ED energy detection
  • the non-AP STA2 determines that link 2 is in a busy state. Referring to FIG. 7 , the non-AP STA2 determines that the link 2 is in a busy state means that the non-AP STA2 considers that the link 2 is in the "CCA busy state" before the end time of the downlink PPDU (TA is AP3, RA is the non-AP STA3).
  • the end time of the downlink PPDU is also the start time of "CCA detection passed", "CCA detection passed” means that the non-AP STA2 determines or detects that link 2 is no longer in a busy state. In this case, the non-AP STA2 starts to back off. That is, after the downlink PPDU transmission on Link 2 is completed, the non-AP STA2 starts EDCA on Link 2. Referring to FIG. 7 , the start time of the non-AP STA2 back off on the link 2 is the time when the downlink PPDU transmission is completed, which is different from the start time of the non-AP STA2 back off in FIG. 9 .
  • the non-AP STA2 may miss the packet header, resulting in failure to update the NAV. Therefore, the non-AP STA2 cannot start EDCA on link 2 after the updated NAV ends.
  • the start time of the downlink PPDU on link 2 (TA is AP3, RA is non-AP STA3) is located in the blindness for non-AP STA2 shown in Figure 7. At this time, the non-AP STA2 cannot detect or DL PPDU received.
  • non-AP STA2 may send a request to send frame to AP2 on link 2.
  • the aforementioned request to send frame can refer to the RTS in Figure 7 (TA is non-AP STA2, RA is AP2).
  • TXOP transmission opportunity
  • the acknowledgment block corresponding to the downlink PPDU is being transmitted on link 2 (perhaps the acknowledgment block is not a non-STR non-AP).
  • the aforementioned acknowledgement block can refer to BA in Figure 7 (TA is non-AP STA3, RA is AP3).
  • the start time of the acknowledgment block corresponding to the downlink PPDU on link 2 is aligned with/same as the start time of the request to send frame sent to AP2 on link 2, that is, the uplink and downlink PPDU of link 2 corresponds to The acknowledgment block collided with the request-to-send frame sent to AP2 on link 2.
  • collision specifically means that the acknowledgment block corresponding to the downlink PPDU on link 2 and the duration of the request-to-send frame sent to AP2 on link 2 at least overlap.
  • the aforementioned non-AP STA2 "misses the packet header" means that the non-AP STA2 does not detect or receive the packet header of the PPDU.
  • the packet header of the PPDU that is, the preamble, at least includes fields such as L-LTF, L-STF, and L-SIG.
  • the packet header of the PPDU is not detected, which is equivalent to that the non-AP STA2 considers that there is no start of a PPDU (no start of a PPDU).
  • the present application proposes a channel contention method, which can support multi-link devices that cannot transmit and receive at the same time to reduce inter-frame collision and interference when performing channel competition problems and improve communication efficiency.
  • a channel contention method provided by an embodiment of the present application will be described in detail below with reference to FIG. 8 to FIG. 13 .
  • the embodiments of the present application describe the method by using the first multi-link device.
  • one or more multi-link devices among the first multi-link device and the second multi-link device in the embodiments of the present application do not support simultaneous transmission and reception (STR ).
  • supporting STR described in this application may refer to the multi-link device having the STR capability, and using the STR capability in this communication;
  • not supporting STR may refer to the multi-link device not having the STR capability , or it can mean that the multi-link device has the STR capability, but does not use the STR capability in this communication.
  • the multi-link device can implement switching between STR and non-STR in some cases, that is, switching from supporting STR to not supporting STR, or switching from supporting STR to supporting STR.
  • a channel contention method provided by an embodiment of the present application will be described by taking an example that the first multi-link device does not support STR and the second multi-link device supports STR.
  • the first multi-link device mentioned in this embodiment of the present application may be the non-AP multi-link device 200 in FIG. 3
  • the second multi-link device may be the AP multi-link device 100 in FIG. 3 .
  • the first non-access point site mentioned in the embodiments of this application may be any STA in the non-AP multi-link device 200
  • the second non-access point site is another STA in the non-AP multi-link device 200 STA.
  • the first access point mentioned in the embodiment of this application is any AP in the AP multi-link device 100 .
  • the embodiments of the present application take two links as an example for description. In practical applications, there may be multiple (more than two) links. For the implementation of multiple links, reference may be made to the two links provided in the embodiments of the present application. The realization method of the road will not be repeated here.
  • FIG. 8 is a schematic diagram of a channel contention method provided by an embodiment of the present application.
  • a channel contention method provided by an embodiment of the present application includes but is not limited to the following steps:
  • the first non-access point station of the first multi-link device responds to the data within the first time period.
  • the second link performs clear channel assessment CCA detection.
  • the data transmitted on the first link may be wireless frames, such as data frames, management frames, etc., which are not limited herein.
  • the start time corresponding to the first time period is aligned with/same as the time when the data transmission on the first link is completed.
  • the first non-access point station performs CCA detection on the second link within the first time period.
  • the start time corresponding to the first time period is earlier than the time when the acknowledgment block corresponding to the data is received on the first link.
  • the "alignment” in this embodiment of the present application may refer to synchronization in time, for example, the transmission start moment is aligned (ie, the same) and/or the transmission end moment is aligned (ie, the same).
  • “alignment”, “synchronization”, “simultaneous” and “same time” in the embodiments of the present application do not mean absolutely the same in the strict sense. Different parameters, different access times, transceiver processing capabilities and other factors, the “alignment”, “synchronization” or “simultaneous” here are allowed to have a slight offset, such as not exceeding the short inter-frame interval SIFS time.
  • the first time period is a time period corresponding to a countdown timer. At the moment when the data transmission on the first link is completed, the first non-access point station starts a countdown timer.
  • the "first time period" begins when the UL PPDU transmission on Link 1 ends.
  • the start time corresponding to the first time period may be the start time corresponding to the media synchronization delay timer (MediumSyncDelay timer, you can refer to the relevant description of the media synchronization delay timer in 802.11-20/1009r1).
  • the end time corresponding to the time period may be the end time corresponding to the media synchronization delay timer. That is, it can be understood that the first non-access point station starts the media synchronization delay timer based on the time when the data transmission on the first link is completed.
  • start time corresponding to the first time period may also be set by the second multi-link device or the first access point of the second multi-link device.
  • the second multi-link device may set start times corresponding to the same or different first time periods.
  • the first access point works on the second link.
  • the first non-access point station performs channel competition on the second link according to the second time period.
  • the start moment of the second time period is aligned with/same as the end moment of the CCA.
  • the start time of the CCA detection is aligned/same as the time when the data transmission on the first link is completed, or the start time of the CCA detection is aligned/same as the time when the acknowledgment block corresponding to the data is received on the first link. It should be noted that, at the moment before the start time of the second time period, when the first non-access point station performs CCA detection on the second link, the CCA detection fails; after the start time of the second time period For a moment, when the first non-access point station performs CCA detection on the second link, the CCA detection passes.
  • the aforementioned first non-access point site is, for example, the non-AP STA2 in FIG. 9 .
  • the aforementioned CCA detection failure refers to the CCA Busy state on link 2 in FIG. 9 , and the CCA Busy state is in the “second time period” in FIG. 9 . continued before.
  • the aforementioned CCA detection pass refers to the state after the CCA Busy on link 2 in Figure 9 ends. At this time, it can be understood as a non-CCA Busy, that is, CCA Idle. After switching from CCA Busy to CCA Idle, it enters the "second time period". ".
  • the second time period may be the extended inter-frame interval EIFS time.
  • the EIFS time may be aSIFSTime+AckTxTime+aSIFSTime.
  • aSIFSTime is a short time interval SIFS time
  • AckTxTime is the time for sending an acknowledgement (Ack) frame.
  • the minimum value of the second time period may be aSIFSTime+AckTxTime+aSIFSTime.
  • channel competition can be performed on the second link according to 802.11-20/1009r1.
  • the solution “according to 802.11-20/1009r1" here refers to the solution described in FIG. 7 above.
  • the scheme of FIG. 7 is different from the scheme described in FIG. 9 .
  • channel contention can only be performed after the “second time period”, that is, the non AP STA2 back off shown in FIG. 9 .
  • the solution according to FIG. 9 can reduce possible collisions.
  • performing channel contention on the second link may include: the first non-access point site adopts a carrier sense multiple access (carrier sense multiple access) with collision avoidance on the second link. sense multiple access with collision avoidance, CSMA/CA) mechanism for channel competition or enhanced distributed channel access (enhanced distributed channel access, EDCA) mechanism for channel competition, which is not limited here.
  • CSMA/CA carrier sense multiple access with collision avoidance
  • EDCA enhanced distributed channel access
  • the CSMA/CA mechanism is used in 802.11, which is also called distributed coordination. Function (distributed coordination function, DCF).
  • DCF distributed coordination function
  • the CSMA/CA mechanism is as follows: Before sending data, the non-access point station needs to perform clear channel access (CCA) on the wireless medium. If the wireless medium is idle for a period of time (eg, distributed inter-frame space (DIFS)), the non-access point station can start a random backoff procedure. If the wireless medium is busy during this period, the non-access point station needs to wait for the wireless medium to become idle and remain idle for a period of time (eg DIFS), and then start the random backoff process.
  • CCA clear channel access
  • DIFS distributed inter-frame space
  • the backoff time in the random backoff process is equal to the product of a random backoff value and a slot time.
  • the random backoff value is a value randomly selected from a uniformly distributed contention window [0, CW]. Understandably, the backoff time in the random backoff process is equal to the initial value of the backoff counter in the channel competition.
  • contention window contention window
  • CW contention window
  • the EDCA mechanism is an enhancement of DCF, which allows services of different access levels to have different EDCA parameter sets.
  • the EDCA parameter set includes parameters such as CWmin, CWmax, and arbitration inter-frame space (AIFS).
  • the EDCA parameters of different access classes are shown in Table 2.
  • AC_VO indicates that the access class is voice (voice) stream
  • AC_VI indicates that the access class is video (video) stream
  • AC_BE indicates that the access class is best effort (best effort) flow
  • AC_BK indicates that the access class is a background flow.
  • the random backoff process is basically the same as that of DCF, the difference is that AIFS replaces DIFS in DCF, that is, when the channel returns to idle, the random backoff process must be kept idle in AIFS.
  • performing idle channel evaluation CCA detection on the second link within the first time period includes: the first non-access point site adjusts the CCA threshold to obtain an adjusted CCA threshold, where the adjusted CCA threshold is lower than the adjusted CCA threshold. The previous CCA threshold; the first non-access point station performs the CCA detection on the second link according to the adjusted CCA threshold within the first time period.
  • the CCA threshold includes an energy detection threshold or an in-frame detection threshold.
  • the energy detection threshold before adjustment may be -82dbm to -62dbm.
  • the in-frame detection threshold before adjustment can be -72dbm.
  • the adjusted in-frame detection threshold may be a value lower than -72dbm, for example, the adjusted in-frame detection threshold may be -82dbm.
  • CCA includes CCA or enhanced CCA other than the enhanced CCA.
  • the CCA other than the enhanced CCA is a manner of performing CCA detection on the link according to the energy detection threshold before adjustment or the detection threshold in the frame before adjustment.
  • the first non-access point station may perform CCA detection on the second link in the first time period, including: the first non-access point station performs enhanced CCA on the second link in the first time period Detection or CCA detection in addition to the enhanced CCA.
  • the first non-access point station may perform channel contention on the second link according to the second time period.
  • CCA detection fails includes: the intensity of the detected signal is greater than the aforementioned CCA threshold, which is recorded as CCA busy at this time.
  • the aforementioned CCA threshold is, for example, an energy detection threshold (CCA-ED) or a midamble detection threshold (midamble-ED).
  • CCA detection passed means that the strength of the detected signal is not greater than the CCA threshold mentioned above, which is recorded as CCA Idle at this time.
  • CCA-ED energy detection threshold
  • midamble-ED midamble detection threshold
  • the CCA-ED When the received signal strength exceeds the CCA-ED threshold, the CCA-ED shall detect a channel busy condition as given by dot11OFDMEDTThreshold for the primary 20MHz channel and dot11OFDMEDTThreshold for the secondary 20MHz channel (if present).
  • the CCA-ED thresholds for the operational level requiring CCA-ED shall comply with the criteria in D.2.5. (CCA-ED shall detect a channel busy condition when the received signal strength exceeds the CCA-ED threshold as given by dot11OFDMEDThreshold for the primary 20MHz channel and dot11OFDMEDThreshold for the secondary 20MHz channel(if present).
  • the CCA-ED thresholds for the classes requiring CCA-ED are subject to the criteria in D.2.5.
  • performing channel competition on the second link according to the second time period includes: if the end time corresponding to the second time period is earlier than the end time corresponding to the first time period, the first non-access point site The channel contention is performed on the second link after the end time corresponding to the second time period.
  • the aforementioned "when the CCA detection on the second link fails, the first non-access point station performs channel competition on the second link according to the second time period" means: After the first non-access point station (non AP STA2 in FIG. 9 ) detects that CCA Busy is converted to non-CCA Busy (CCA Idle), the second time period (the content described in FIG.
  • the first non-access point station After the end time corresponding to the segment is earlier than the end time corresponding to the first time segment”), the first non-access point station starts to back off (non AP STA2 back off in FIG. 9 ). This is different from the solution in Fig. 7.
  • the solution in Fig. 7 starts immediately after the first non-access point station (non AP STA2 in Fig. 7) detects that CCA Busy is converted to non-CCA Busy (CCA Idle). back off.
  • the first non-access point station will start the second time period after the end time corresponding to the first time period or after the end time corresponding to the second time period.
  • Channel contention is performed on the two links.
  • the aforementioned "when the CCA detection on the second link fails, the first non-access point station performs channel competition on the second link according to the second time period" means: After the first non-access point station (non AP STA2 in FIG.
  • Non-AP STA2 in FIG. 10 detects that CCA Busy is converted to non-CCA Busy (CCA Idle), at the two time points of the first time period and the end time of the second time period
  • One of the first non-access point stations can start back off (non-AP STA2 in FIG. 10 back off). This is different from the solution in Fig. 7.
  • the solution in Fig. 7 starts immediately after the first non-access point station (non AP STA2 in Fig. 7) detects that CCA Busy is converted to non-CCA Busy (CCA Idle). back off.
  • the first non-access point station may start to back off at the end time corresponding to the second time period. If the end time corresponding to the second time period is later than the end time corresponding to the first time period, the first non-access point station may start to back off at the end time corresponding to the first time period, or at the end time corresponding to the second time period Start backing off.
  • FIG. 8 is only a process of the channel contention method provided by the embodiment of the present application, and the channel contention method of the present application may also be implemented by other processes.
  • the sequence flow of the channel contention method of the present application will be briefly introduced below with reference to several specific examples. Among them, the following specific examples are only examples for the convenience of understanding. In practical applications, the sequence flow of the channel contention method of the present application may be more or less than the flow of the following specific examples.
  • the first multi-link device (such as non-AP MLD) includes non-AP STA1 and non-AP STA2, the first multi-link device does not include non-AP STA3, non-AP STA3 can be a single device or belong to other non-AP MLDs.
  • non-AP STA1 works on link 1 (link1)
  • non-AP STA2 and non-AP STA3 work on link 2 (link2).
  • the second multi-link device (such as AP MLD) includes AP1 and AP2, the second multi-link device does not include AP3, and AP3 may be a single device or may belong to other AP MLDs.
  • AP1 works on link 1, AP2 and AP3 work on link 2; the first multi-link device does not support STR, and the second multi-link device supports STR.
  • FIG. 9 is a schematic time sequence diagram of a channel contention method provided by an embodiment of the present application.
  • non-AP STA1 sends uplink PPDU to AP1 on link 1. Since the frequency interval between link 1 and link 2 is small, when there is data transmission on link 1, channel interference may affect to the CCA to link 2. As a result, the channel information of link 2 cannot be monitored, that is, link 2 is in a blind state.
  • the aforementioned blind state is the blindness for non AP STA2 shown in FIG. 9. In the embodiment described in FIG.
  • the transmission time of the uplink PPDU on link 1 is aligned/same as the blind state start time of link 2, and the end time of the uplink PPDU on link 1 is aligned with the blind state end time of link 2/ same. Therefore, when the uplink PPDU transmission on Link 1 is complete, AP1 can send an acknowledgment block on Link 1 to non-AP STA1. In addition, after the transmission of the uplink PPDU on the link 1 is completed, the link 2 is in a non-blind state, that is, the channel information of the link 2 can be monitored.
  • the non-AP STA2 may start timing based on the start time corresponding to the first time period. That is, the non-AP STA2 starts a countdown timer, and the time period corresponding to the countdown timer is the time period corresponding to the first time period. During the first time period, the non-AP STA2 may perform CCA detection on link 2.
  • CCA detection is performed on link 2 since AP3 is sending downlink PPDUs to non-AP STA3 on link 2, the CCA detection on link 2 fails.
  • This "CCA detection failed” is the "CCA Busy” shown in FIG. 9 . It can be understood that after the transmission of the downlink PPDU is completed, the CCA detection of link 2 is passed.
  • the “detection by CCA” is the end of "CCA Busy" in Fig. 9, that is, the start of "CCA idle”.
  • the end time of the downlink PPDU transmission is the same/aligned with the time when the CCA detection of link 2 passes, and the start time corresponding to the second time period is the same as the time when the CCA detection of link 2 passed/ Align.
  • the link 2 is transmitting the acknowledgment block BA corresponding to the downlink PPDU.
  • the time when link 2 finishes transmitting the acknowledgment block corresponding to the downlink PPDU is earlier than the end time corresponding to the second time period
  • the end time corresponding to the second time period is earlier than the end time corresponding to the first time period
  • the non-AP STA2 is in the The backoff starts at the end time corresponding to the second time period. In this case, the problems of inter-frame collision and interference are avoided.
  • FIG. 10 is a schematic time sequence diagram of a channel contention method provided by an embodiment of the present application.
  • the non-AP STA1 sends an uplink PPDU to AP1 on link 1. Since the frequency interval between the frequency bands of link 1 and link 2 is small, when there is data transmission on link 1, channel interference may affect the to CCA detection on link 2. As a result, the channel information of link 2 cannot be monitored, that is, link 2 is in a blind state.
  • the aforementioned blind state is the blindness for non AP STA2 shown in FIG. 10. In the embodiment described in FIG.
  • the transmission time of the uplink PPDU on link 1 is aligned/same as the start time of the blind state of link 2, and the end time of the uplink PPDU on link 1 is aligned with the end time of the blind state of link 2/ same. Therefore, when the uplink PPDU transmission on Link 1 is complete, AP1 can send an acknowledgment block on Link 1 to non-AP STA1. In addition, after the transmission of the uplink PPDU on the link 1 is completed, the link 2 is in a non-blind state, that is, the channel information of the link 2 can be monitored.
  • the non-AP STA2 may start timing based on the start time corresponding to the first time period. That is, the non-AP STA2 starts a countdown timer, and the time period corresponding to the countdown timer is the time period corresponding to the first time period. During the first time period, the non-AP STA2 may perform CCA detection on link 2.
  • CCA detection is performed on link 2 since AP3 is sending downlink PPDUs to non-AP STA3 on link 2, the CCA detection on link 2 fails.
  • This "CCA test failed” is "CCA Busy” shown in FIG. 10 . It can be understood that after the transmission of the downlink PPDU is completed, the CCA detection of link 2 is passed.
  • the “detection by CCA” is the end of "CCA Busy” in Fig. 10, that is, the start of "CCA idle”.
  • the end time of the downlink PPDU transmission is the same/aligned with the time when the CCA detection of link 2 passes, and the start time corresponding to the second time period is the same as the time when the CCA detection of link 2 passed/ Align. Further, within the second time period, link 2 is transmitting the acknowledgment block corresponding to the downlink PPDU.
  • the time when link 2 completes transmission of the acknowledgment block corresponding to the downlink PPDU is earlier than the end time corresponding to the second time period, and the end time corresponding to the second time period is later than the end time corresponding to the first time period, and the non-AP STA2 is in The backoff starts at the end time corresponding to the second time period or the end time corresponding to the first time period. In this case, the problems of inter-frame collision and interference are also avoided.
  • FIG. 11 is a schematic diagram of still another channel contention method provided by an embodiment of the present application.
  • another channel contention method provided by an embodiment of the present application includes but is not limited to the following steps:
  • the first non-access point station updates the network configuration vector NAV according to the radio frame to obtain the updated NAV.
  • the wireless frame is a wireless frame sent to the second non-access point station on the second link when the data is being transmitted on the first link or when the acknowledgment block corresponding to the data is being transmitted on the first link.
  • the second non-access point station is a non-access point station other than the first non-access point station in the first multi-link device.
  • the radio frame is a radio frame received when the second link is in a blind state, and the first non-access point station can update the network configuration vector NAV according to the radio frame to obtain the updated NAV.
  • the radio frame may include, for example, a block acknowledgement, a data frame, a management frame, a trigger (trigger) frame, and the like, which is not limited herein.
  • the first non-access point station may update the network configuration vector NAV according to the duration information carried in the radio frame to obtain the updated NAV.
  • the duration information is greater than the NAV, that is, the updated NAV is greater than the NAV.
  • the radio frame may include a duration (duration) field, where the duration field is used to indicate the duration information, and the first non-access point station may update the network configuration vector NAV according to the duration field included in the radio frame, to obtain Updated NAV.
  • the specific update method is not limited in this application.
  • the first non-access point station sends PPDUs on the second link.
  • the point station can update the network configuration vector NAV according to the block acknowledgment carried by the PPDU to obtain the updated NAV.
  • the block acknowledgment carries duration information, that is, the first non-access point station can update the network configuration vector NAV according to the duration information carried in the block acknowledgment to obtain an updated NAV.
  • the first non-access point station performs channel contention on the second link according to the updated NAV.
  • performing channel competition on the second link according to the updated NAV including: if the updated NAV is less than the moment when the data transmission is completed on the first link or an acknowledgment block is received on the first link time, the first non-access point station performs CCA detection on the second link within the first time period; when the CCA detection on the second link fails, the first non-access point station checks the second link according to the second time segment with channel contention on the second link; or,
  • the first non-access point station If the updated NAV is greater than the moment when the data transmission is completed on the first link or the moment when the acknowledgment block is received on the first link, the first non-access point station then backs off the updated NAV to zero on the first link. Channel contention is performed on the two links.
  • the first time period reference may be made to the description of the first time period in step 801 in FIG. 8 , and details are not repeated here.
  • the second time period reference may be made to the description of the second time period in step 802 in FIG. 8 , and details are not repeated here.
  • the CCA detection fails, the first non-access point station performs channel competition on the second link according to the second time period, you can refer to the relevant description of step 802 in FIG. 8, and will not be repeated here.
  • the first non-access point station starts to back off according to the updated NAV.
  • the updated NAV backoff no matter whether the data on the first link has been transmitted or not, when the updated NAV backoff is 0, the first non-access point station can perform channel contention on the second link .
  • the first non-access point station performs CCA detection on the second link other than the enhanced CCA. When the CCA detection on the second link passes, the first non-access point station may perform frame exchange on the second link.
  • the time when the updated NAV backoff is 0 may be earlier or later than or equal to the time when the data transmission on the first link is completed, which is not limited here. Further, at the moment when the data transmission on the first link is completed, the first non-access point station starts a countdown timer, and the time period corresponding to the countdown timer is the first time period.
  • the first non-access point station can start a countdown timer, and the time period corresponding to the countdown timer is the a period of time.
  • the first non-access point station may perform channel competition within the first time period. Further, when the updated NAV backoff is 0, the first non-access point station may perform CCA detection other than the enhanced CCA on the second link within the first time period. When the CCA detection is passed, the first non-access point station may perform frame exchange on the second link.
  • FIG. 11 is only a process of the channel contention method provided by the embodiment of the present application, and the channel contention method of the present application may also be implemented by other processes.
  • the sequence flow of the channel contention method of the present application will be briefly introduced below with reference to several specific examples. Among them, the following specific examples are only examples for the convenience of understanding. In practical applications, the sequence flow of the channel contention method of the present application may be more or less than the flow of the following specific examples.
  • the first multi-link device (such as non-AP MLD) includes non-AP STA1 and non-AP STA2, the first multi-link device does not include non-AP STA3, non-AP STA3 can be a single device or belong to other non-AP MLDs.
  • non-AP STA1 works on link 1 (link1)
  • non-AP STA2 and non-AP STA3 work on link 2 (link2).
  • the second multi-link device (such as AP MLD) includes AP1 and AP2, the second multi-link device does not include AP3, and AP3 may be a single device or may belong to other AP MLDs.
  • AP1 works on link 1, AP2 and AP3 work on link 2; the first multi-link device does not support STR, and the second multi-link device supports STR.
  • FIG. 12 is a schematic time sequence diagram of a channel contention method provided by an embodiment of the present application.
  • non-AP STA1 sends PPDU1 to AP1 on link 1. Since the frequency interval between link 1 and link 2 is small, when there is data transmission on link 1, channel interference may affect the CCA to link 2. As a result, the channel information of link 2 cannot be monitored, that is, link 2 is in a blind state. 12, it can be seen that the transmission time of PPDU1 on link 1 is aligned/same as the blind state start time of link 2, and the end time of PPDU1 on link 1 is aligned/same as the blind state end time of link 2.
  • AP1 can send Acknowledgement Block 1 to non-AP STA1 on Link 1.
  • the link 2 is in a non-blind state, that is, the channel information of the link 2 can be monitored.
  • the non-AP STA2 may start timing based on the start time corresponding to the first time period. That is, the non-AP STA2 starts a countdown timer, and the time period corresponding to the countdown timer is the time period corresponding to the first time period.
  • AP3 is sending PPDU2 to non-AP STA3 on link 2. 12
  • the transmission time of PPDU2 on link 2 is later than the start time of link 2 blind state, and the reception time of PPDU2 on link 2 is earlier than the end time of link 2 blind state. That is, PPDU2 is received by non-AP STA3 when link 2 is in the blind state.
  • the non-AP STA3 receives the PPDU2, the non-AP STA2 can update the NAV according to the PPDU2.
  • the receiving end time of the PPDU2 on the link 2 may be earlier or later than or equal to the end time of the blind state of the link 2, which is not limited herein.
  • the CCA detection of the link 2 is passed.
  • the end time of the PPDU2 transmission is the same/aligned with the time when the CCA detection of link 2 passes.
  • the non-AP STA3 receives the PPDU2, it can send an acknowledgement block 2 to the AP3 on the second link.
  • the non-AP STA2 updates the NAV again according to this acknowledgement block 2.
  • the non-AP STA2 can back off according to the updated NAV again.
  • the non-AP STA2 performs CCA detection on the second link except the enhanced CCA.
  • the first non-access point station may perform frame exchange on the second link.
  • the first non-access point station starts at the corresponding start time of the first time period. Start timing for the benchmark. That is, when the data transmission on the first link is completed, the first non-access point station starts a countdown timer, and the time period corresponding to the countdown timer is the first time period.
  • the end time of the NAV corresponding to the PPDU2 is earlier than the end time of the NAV corresponding to the acknowledgment block 2 .
  • the non-AP STA2 can also update the NAV again according to the other PPDUs.
  • FIG. 13 is a schematic time sequence diagram of a channel contention method provided by an embodiment of the present application.
  • non-AP STA1 sends PPDU1 to AP1 on link 1. Since the frequency interval between link 1 and link 2 is small, when there is data transmission on link 1, channel interference may affect the CCA to link 2. As a result, the channel information of link 2 cannot be monitored, that is, link 2 is in a blind state. 13, it can be seen that the transmission time of PPDU1 on link 1 is aligned/same as the blind state start time of link 2, and the end time of PPDU1 on link 1 is aligned/same as the blind state end time of link 2.
  • AP1 can send Acknowledgement Block 1 to non-AP STA1 on Link 1.
  • the link 2 is in a non-blind state, that is, the channel information of the link 2 can be monitored.
  • AP3 is sending PPDU2 to non-AP STA3 on link 2. It can be understood that the sending time of the PPDU2 is later than the starting time of the blind state of the link 2, and the receiving time of the PPDU2 is earlier than the ending time of the blind state of the link 2. That is, this PPDU2 is a PPDU received when Link2 is in the blind state. Further, when the non-AP STA3 receives the PPDU2, the non-AP STA2 updates the NAV according to the PPDU2. In addition, when the non-AP STA3 receives the PPDU2, it can send an acknowledgement block 2 to the AP3 on the second link. The non-AP STA2 may update the NAV again according to this acknowledgment block 2.
  • the non-AP STA2 can back off according to the updated NAV again.
  • the non-AP STA2 performs CCA detection on the second link except the enhanced CCA.
  • the first non-access point station may perform frame exchange on the second link.
  • the receiving end time of the PPDU2 on the link 2 may be earlier or later than or equal to the end time of the blind state of the link 2, which is not limited herein.
  • the first non-access point station starts at the corresponding start time of the first time period. Start timing for the benchmark. That is, when the data transmission on the first link is completed, the first non-access point station starts a countdown timer, and the time period corresponding to the countdown timer is the first time period.
  • the end time of the NAV corresponding to the PPDU2 is the same as the end time of the NAV corresponding to the confirmation block 2 .
  • the non-AP STA2 can also update the NAV again according to the other PPDUs.
  • the CCA detection described in the foregoing embodiments at least includes detection on the primary 20MHz channel (Primary 20MHz channel) occupied by the PPDU.
  • Primary 20MHz channel Primary 20MHz channel
  • the EDCA TXOP is only obtained based on the activity of the primary channel.
  • Idle medium in this subclause means “idle primary channel”.
  • busy medium refers to “busy primary channel”.
  • an EDCA TXOP may limit the transmission width during the TXOP or deny channel access based on the CCA status on the secondary channel, secondary 40MHz channel or secondary 80MHz channel . (When a STA and the BSS, of which the STA is a member, both support multiple channel widths, an EDCA TXOP is obtained based solely on activity of the primary channel.
  • Idle medium in this subclause means “idle primary channel.”
  • busy medium means “busy primary channel.”
  • FIG. 14 is a schematic structural diagram of a communication apparatus provided in an embodiment of the present application.
  • the communication apparatus 1400 may be the first multi-link device in the foregoing embodiment, and may also be a chip or a processing system in the first multi-link device, and may implement the method and method of any one of the foregoing embodiments. Function. Due to differences in integration levels, the communication device 1400 may include one or more of the components shown in FIG. 14 .
  • the components shown in FIG. 14 may include: at least one processor 1401 , memory 1402 , transceiver 1403 , and communication bus 1404 . Among them, processors, transceivers, memories, etc. are connected through a bus.
  • the embodiments of the present application do not limit the specific connection medium between the above components.
  • the processor 1401 is the control center of the communication device 1400, and may be a processor or a general term for multiple processing elements.
  • the processor 1401 is a central processing unit (central processing unit, CPU), may also be a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or is configured to implement one or more integrated circuits of the embodiments of the present application , for example: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA).
  • the processor 1401 can execute various functions of the communication device by running or executing software programs stored in the memory 1402 and calling data stored in the memory 1402 .
  • the processor 1401 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 14 .
  • the communication apparatus 1400 may include multiple processors, such as the processor 1401 and the processor 1405 shown in FIG. 14 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more communication devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the memory 1402 may be read-only memory (ROM) or other type of static storage communication device that can store static information and instructions, random access memory (RAM) or other type of static storage communication device that can store information and instructions.
  • Type of dynamic storage communication device it can also be Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, Optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage communication devices, or capable of carrying or storing desired program code in the form of instructions or data structures and Any other medium that can be accessed by a computer, but is not limited to this.
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • Optical disc storage including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 1402 can exist independently and is connected to the processor 1401 through the communication bus 1404 .
  • the memory 1402 may also be integrated with the processor 1401. Wherein, the memory 1402 is used for storing the software program for executing the solution of the present application, and the execution is controlled by the processor 1401 .
  • the transceiver 1403 is used for communication with other devices (eg, the second multi-link device). Of course, the transceiver 1403 may also be used to communicate with a communication network, such as an Ethernet network, a radio access network (RAN), a wireless local area network, and the like.
  • the transceiver 1403 may include a receiving unit to implement a receiving function, and a transmitting unit to implement a transmitting function.
  • the communication bus 1404 can be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external communication device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus and the like.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is shown in FIG. 14, but it does not mean that there is only one bus or one type of bus.
  • the communication apparatus 1400 may be a complete device, and the communication apparatus may include: a processor 1401 , a memory 1402 , a transceiver 1403 and a communication bus 1404 .
  • other components may also be included, such as a display screen, a user interface or a signal detector.
  • the communication apparatus 1400 is a first multi-link device, and can be used to implement the methods and functions related to the first multi-link device in the foregoing embodiments.
  • instructions are stored in the memory, and when the processor calls the instructions, the above-mentioned methods and functions are implemented, for example, the processor is used to generate signaling or frames, and the transceiver is used to transmit signaling or frames.
  • the processor is used to execute step S141 or S201, etc.
  • the transceiver is used to execute step S142, S202 or S207, etc.
  • the communication apparatus 1400 may be a system-on-a-chip or a processing system in the first multi-link device, so that a device on which the system-on-a-chip or processing system is installed implements the methods and functions in the foregoing embodiments.
  • the communication device 1400 may include some components as shown in FIG. 14 .
  • the communication device 1400 includes a processor, which may be coupled with the memory, and call and execute the instructions in the memory, thereby configuring the system on which the chip system or processing system is installed.
  • the device implements the methods and functions in the foregoing embodiments.
  • the memory may be a component in a chip system or a processing system, or may be a component of an external coupling link of the chip system or the processing system.
  • the chip system or the processing system is installed in the first multi-link device, so that the first multi-link device can implement the corresponding methods and functions in the foregoing embodiments.
  • the chip system or processing system can support 802.11 series protocols for communication, such as 802.11be, 802.11ax, 802.11ac and so on.
  • the chip system can be installed in devices in various scenarios that support WLAN transmission, and the devices in the WLAN transmission scenario have been introduced in the specification of this application, and will not be repeated here.
  • the first multi-link device or the second multi-link device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided according to each function, or two or more The functions are integrated in a processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 15 is another schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication apparatus 1500 may be a chip or a processing system in a multi-link device, and the communication apparatus 1500 may perform the operations of the first multi-link device in the foregoing method embodiments.
  • the communication apparatus 1500 includes: a processing unit 1501 .
  • the communication apparatus 1500 is a non-access point station in the first multi-link device.
  • the processing unit 1501 may be used to control and manage the actions of the communication device 1500 . For example, CCA detection is performed on the second link during the first time period.
  • the processing unit 1501 may also execute programs or instructions stored in the storage unit, so that the communication apparatus 1500 implements the methods and functions involved in any of the foregoing embodiments.
  • processing unit 1501 described above may be used to perform, for example, step 801 in FIG. 8 , or step 801 in FIG. 8 and/or other processes for the techniques described herein.
  • step 801 in FIG. 8 or step 801 in FIG. 8 and/or other processes for the techniques described herein.
  • all relevant contents of the steps involved in the above method embodiments can be cited in the functional descriptions of the corresponding functional modules, which will not be repeated here.
  • the communication apparatus 1500 may be the communication apparatus shown in FIG. 14 , and the processing unit 1501 may be the processor 1401 in FIG. 14 .
  • the communication apparatus 1500 may include a transceiver unit, and the transceiver unit may be the transceiver 1403 in FIG. 14 .
  • the communication apparatus 1500 may further include a memory, and the memory is used for storing program codes and data corresponding to the communication apparatus 1500 executing any one of the methods for channel competition between multi-link devices provided above.
  • the descriptions of all the relevant contents of the components involved in the above-mentioned FIG. 14 can be referred to the functional descriptions of the corresponding components of the communication apparatus 1500 , which are not repeated here.
  • the communication device 1500 may also be a chip or a processor, wherein the processing unit 1501 is a processing circuit in the chip or the processor, and the transceiver unit may be an input/output circuit in the chip or the processor, and the input/output circuit It is an interface for the chip or processor and other coupling components to communicate with each other or exchange data, which can ensure that signaling or data information or program instructions are input into the chip or processor for processing, and the processed data or signaling is output to other coupled components and control the first multi-link device on which the chip or processor is mounted to perform functions.
  • the processing unit 1501 is a processing circuit in the chip or the processor
  • the transceiver unit may be an input/output circuit in the chip or the processor, and the input/output circuit It is an interface for the chip or processor and other coupling components to communicate with each other or exchange data, which can ensure that signaling or data information or program instructions are input into the chip or processor for processing, and the processed data or signaling is output to other coupled components and control the first multi-link
  • Embodiments of the present application further provide a computer-readable storage medium, where computer program codes are stored in the computer-readable storage medium.
  • the electronic device executes any one of the implementations in FIG. 8 and FIG. 11 . example method.
  • the embodiments of the present application also provide a computer program product, which, when the computer program product runs on a computer, causes the computer to execute the method of any one of the embodiments in FIG. 8 and FIG. 11 .
  • An embodiment of the present application also provides a communication device, which can exist in the form of a chip, and the structure of the device includes a processor and an interface circuit, where the processor is used to communicate with other devices through the interface circuit, so that the device executes The method in any one of the above embodiments in FIG. 8 and FIG. 11 .
  • An embodiment of the present application further provides a communication system, including a first multi-link device and a second multi-link device, where the first multi-link device and the second multi-link device can perform the operations shown in FIG. 8 and FIG. 11 above.
  • the steps of the methods or algorithms described in conjunction with the disclosure of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • the software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory (Random Access Memory, RAM), flash memory, Erasable Programmable Read-Only Memory (Erasable Programmable ROM, EPROM), electrically erasable programmable Programmable read-only memory (Electrically EPROM, EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM), or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist in the core network interface device as discrete components.
  • the functions described in this application may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer-readable storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本申请提供了一种信道竞争方法及相关装置，该方法包括：在第一链路上数据传输完成后或在所述第一链路上接收到所述数据对应的确认块后，第一多链路设备的第一非接入点站点在第一时间段内对第二链路进行空闲信道评估CCA检测，所述第一时间段对应的开始时刻与所述第一链路上所述数据传输完成的时刻相同；当对所述第二链路的所述CCA检测不通过时，所述第一非接入点站点根据第二时间段，在所述第二链路上进行信道竞争。实施本申请实施例，实现在信道竞争时避免了帧间碰撞和干扰。

Description

一种信道竞争方法及相关装置
本申请要求于2020年08月14日提交中国专利局、申请号为202010820609.9、申请名称为“一种信道竞争方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种信道竞争方法及相关装置。
背景技术
目前，下一代无线局域网(wireless local area network，WLAN)或蜂窝网发展演进的持续技术目标是不断提高吞吐率。WLAN系统的协议主要在电气和电子工程师协会(IEEE，institute of electrical and electronics engineers)标准组中进行讨论，基于之前的标准协议IEEE 802.11a/b/g/n/ac/ax等，下一代WiFi标准IEEE 802.11be将极高吞吐率(extremely high throughput，EHT)作为技术目标，其涉及到关键技术多链路(multi-link)通信。多链路通信的核心思想是支持下一代IEEE 802.11标准的WLAN设备拥有在多频段(multi-band)发送和接收的能力，从而使用更大的带宽进行数据传输，进而显著提升吞吐率。其中，多频段包括但不限于：2.4GHz WiFi频段、5GHz WiFi频段以及6GHz WiFi频段。通信设备进行接入和传输的一个频段可以称为一条链路，通信设备进行接入和传输的多个频段便可以称为多链路。将同时支持多条链路的下一代IEEE 802.11标准站设备称为多链路设备(multi link device，MLD)，多链路设备可支持多链路通信。示例性的，参见图1，图1为本申请实施例提供的一种多链路通信的场景示意图。如图1所示，接入点(access point，AP)多链路设备(multi-link device)包括AP1和AP2，非接入点站点(non-Access Point Station,non-AP STA)MLD包括non-APSTA1和non-APSTA2。其中，AP1与non-APSTA1通过链路1通信，AP2与non-APSTA2通过链路2通信。可以理解的，AP MLD与STA MLD之间的通信即为多链路通信。
然而，由于某些多链路设备可能在某些情况下不支持在多条链路上同时发送和接收(simultaneous transmit and receive，STR)，所以当non-STR(非同时发送和接收)的多链路设备(这里指不支持STR的多链路设备)所支持的多个频段之间的频率间隔较近时，在一条链路上传输数据时，信道干扰可能影响到对其他链路的空闲信道评估(clear channel assessment，CCA)，从而可能确定出其他链路处于盲状态(blindness period，或，deaf period)。其中，盲状态指无法监听到信道上的信息。在这种情况下，现有方案中，在标准802.11-20/1009r1中提出可以在数据传输完成后，针对其他链路，non-STR MLD可以设置媒体同步时延(medium sync delay)计时器，在该计数器内采用(to be decided，TBD)的能量检测(energy detection，ED)阈值对其他链路进行CCA。若其他链路中有某条链路的CCA检测不通过，则意味着该链路上正在传输重合基本服务集合(overlapping basic service set，OBSS)帧。当该OBSS帧传输结束后，non-STR MLD开始竞争信道，启动增强分布式信道接入(enhanced distributed channel access，EDCA)。
然而，当该OBSS帧传输结束后，该链路对应的传输机会(transmission opportunity，TXOP)可能还未结束，这导致在non-STR MLD接入信道后与该OBSS帧对应的应答(ACK) 帧发生碰撞。因此，在进行EDCA时如何避免帧间碰撞和干扰成为目前亟需解决的技术问题。
发明内容
本申请提供了一种信道竞争方法及相关装置，可以支持不能同时收发的多链路设备在进行信道竞争时减少帧间碰撞和干扰的问题，提高了通信效率。
第一方面，本申请实施例提供一种信道竞争方法，所述方法包括：
在第一链路上数据传输完成后或在所述第一链路上接收到所述数据对应的确认块后，第一多链路设备的第一非接入点站点在第一时间段内对第二链路进行空闲信道评估CCA检测，所述第一时间段对应的开始时刻与所述第一链路上所述数据传输完成的时刻相同；
当对所述第二链路的所述CCA检测不通过时，所述第一非接入点站点根据第二时间段，在所述第二链路上进行信道竞争。
可理解的，本方案中，在第一链路上数据传输完成后或在第一链路上接收到该数据对应的确认块后，在对第二链路进行CCA检测时，当第二链路的CCA检测不通过，实现根据第二时间段，在第二链路上进行信道竞争，避免了在确定第二链路上的数据传输完成后在第二链路上进行信道竞争时导致的帧间碰撞和干扰的问题，从而减少了帧间碰撞和干扰的问题，提高了通信效率。
可选的，所述在第一时间段内对第二链路进行空闲信道评估CCA检测，包括：
所述第一非接入点站点调整CCA阈值，得到调整后的CCA阈值，所述调整后的CCA阈值低于所述CCA阈值；
所述第一非接入点站点在所述第一时间段内根据所述调整后的CCA阈值，对所述第二链路进行所述CCA检测。
可理解的，本方案中，在对第二链路进行CCA检测时，可以采用更加严格的CCA阈值对第二链路进行CCA检测，从而为后续避免在确定第二链路上的数据传输完成后在第二链路上进行信道竞争时导致的帧间碰撞和干扰的问题做准备。
可选的，所述CCA阈值包括能量检测阈值或帧中检测阈值。
可选的，所述根据第二时间段，在所述第二链路上进行信道竞争，包括：
若所述第二时间段对应的结束时刻早于所述第一时间段对应的结束时刻，所述第一非接入点站点则在所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争；
若所述第二时间段对应的结束时刻晚于所述第一时间段对应的结束时刻，所述第一非接入点站点则在所述第一时间段对应的结束时刻之后或所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争。
可理解的，本方案中，实现了在不同情况下，在第一时间段对应的结束时刻之后或第二时间段对应的结束时刻之后在第二链路上进行信道竞争，避免了在确定第二链路上的数据传输完成后在第二链路上进行信道竞争时导致的帧间碰撞和干扰的问题，从而减少了帧间碰撞和干扰的问题，提高了通信效率。
可选的，所述方法还包括：
所述第一非接入点站点根据无线帧，更新网络配置向量NAV，得到更新后的NAV，其中，所述无线帧为在所述第一链路上正在传输所述数据时或在所述第一链路上正在传输所述数据对应的所述确认块时在所述第二链路上发送给第二非接入点站点的无线帧，所述 第二非接入点站点为所述第一多链路设备中除所述第一非接入点站点之外的非接入点站点；
所述第一非接入点站点根据所述更新后的NAV，对所述第二链路进行信道竞争。
可理解的，本方案中，实现了根据更新后的NAV，对第二链路进行信道竞争，避免了在确定第二链路上的数据传输完成后在第二链路上进行信道竞争时导致的帧间碰撞和干扰的问题，从而减少了帧间碰撞和干扰的问题，提高了通信效率。
可选的，所述根据所述更新后的NAV，对所述第二链路进行信道竞争，包括：
若所述更新后的NAV小于在所述第一链路上所述数据传输完成的时刻或在所述第一链路上接收到所述确认块的时刻，所述第一非接入点站点则在所述第一时间段内对所述第二链路进行所述CCA检测；当对所述第二链路的所述CCA检测不通过时，所述第一非接入点站点根据所述第二时间段，在所述第二链路上进行信道竞争；或，
若所述更新后的NAV大于在所述第一链路上所述数据传输完成的时刻或在所述第一链路上接收到所述确认块的时刻，所述第一非接入点站点则在所述更新后的NAV退避至零时在所述第二链路上进行信道竞争。
可理解的，本方案中，实现了在不同情况下，对第二链路进行信道竞争，避免了在确定第二链路上的数据传输完成后在第二链路上进行信道竞争时导致的帧间碰撞和干扰的问题，从而减少了帧间碰撞和干扰的问题，提高了通信效率。
可选的，所述第二时间段为经扩展的帧间间隔EIFS时间。
第二方面，本申请实施例提供一种通信装置，应用于第一多链路设备中，该通信装置可以为第一多链路设备或第一多链路设备中的芯片，比如Wi-Fi芯片，包括：
处理单元，用于在第一链路上数据传输完成后或在所述第一链路上接收到所述数据对应的确认块后，第一多链路设备的第一非接入点站点在第一时间段内对第二链路进行空闲信道评估CCA检测，所述第一时间段对应的开始时刻与所述第一链路上所述数据传输完成的时刻相同；
所述处理单元，还用于当对所述第二链路的所述CCA检测不通过时，所述第一非接入点站点根据第二时间段，在所述第二链路上进行信道竞争。
可选的，在第一时间段内对第二链路进行空闲信道评估CCA检测时，所述处理单元，用于调整CCA阈值，得到调整后的CCA阈值，所述调整后的CCA阈值低于所述CCA阈值；在所述第一时间段内根据所述调整后的CCA阈值，对所述第二链路进行所述CCA检测。
可选的，所述CCA阈值包括能量检测阈值或帧中检测阈值。
可选的，在根据第二时间段，在所述第二链路上进行信道竞争时，
若所述第二时间段对应的结束时刻早于所述第一时间段对应的结束时刻，所述处理单元，用于在所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争；
若所述第二时间段对应的结束时刻晚于所述第一时间段对应的结束时刻，所述处理单元，用于在所述第一时间段对应的结束时刻之后或所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争。
可选的，所述处理单元，还用于根据无线帧，更新网络配置向量NAV，得到更新后的NAV，其中，所述无线帧为在所述第一链路上正在传输所述数据时或在所述第一链路上正 在传输所述数据对应的所述确认块时在所述第二链路上发送给第二非接入点站点的无线帧，所述第二非接入点站点为所述第一多链路设备中除所述第一非接入点站点之外的非接入点站点；根据所述更新后的NAV，对所述第二链路进行信道竞争。
可选的，在根据所述更新后的NAV，对所述第二链路进行信道竞争时，
若所述更新后的NAV小于在所述第一链路上所述数据传输完成的时刻或在所述第一链路上接收到所述确认块的时刻，所述处理单元，用于在所述第一时间段内对所述第二链路进行所述CCA检测；当对所述第二链路的所述CCA检测不通过时，所述第一非接入点站点根据所述第二时间段，在所述第二链路上进行信道竞争；或，
若所述更新后的NAV大于在所述第一链路上所述数据传输完成的时刻或在所述第一链路上接收到所述确认块的时刻，所述处理单元，用于在所述更新后的NAV退避至零时在所述第二链路上进行信道竞争。
可选的，所述第二时间段为经扩展的帧间间隔EIFS时间。
第三方面，本申请实施例提供了一种通信装置，具体为第一多链路设备，该第一多链路设备具有实现上述方法中第一多链路设备行为的功能，该功能可以通过硬件实现，也可以通过硬件执行响应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，第一多链路设备包括处理器和收发器，该处理器被配置为支持第一多链路设备执行上述方法中相应的功能。该收发器用于支持第一多链路设备的通信，接收上述方法中所涉及的信息，帧，数据分组或者指令。该第一多链路设备还可以包括存储器，该存储器用于与处理器耦合，其保存第一多链路设备必要的程序指令和数据。
第四方面，本申请实施例提供了一种无线通信系统，该系统包括上述第三方面所述的第一多链路设备。
第五方面，本申请实施例提供一种芯片或芯片系统，包括输入输出接口和处理电路，所述输入输出接口用于交互信息或数据，所述处理电路用于运行指令，以使得安装所述芯片或芯片系统的装置执行上述任意一方面的信道竞争方法。
第六方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，该指令可以由处理电路上的一个或多个处理器执行。当其在计算机上运行时，使得计算机执行上述任意一方面所述的信道竞争方法。
第七方面，本申请提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任意一方面所述的信道竞争方法。
第八方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于支持安装该芯片系统的装置实现上述任意一方面所述的信道竞争方法，例如处理上述所述的信道竞争方法中所涉及的帧和/或信息。在一种可能的设计中，该芯片系统还包括存储器，该存储器，用于保存数据发送设备必要的程序指令和数据。该芯片系统可以由芯片构成，也可以包含 芯片和其他分立器件。
附图说明
下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
其中：
图1是本申请实施例提供的一种多链路通信的场景示意图；
图2a是本申请实施例提供的NAV设置的一示意图；
图2b是本申请实施例提供的NAV设置的另一示意图；
图3是本申请实施例提供的无线通信系统的一架构示意图；
图4是本申请实施例提供的多链路设备的一结构示意图；
图5是本申请实施例提供的多链路设备的另一结构示意图；
图6是本申请实施例提供的一种竞争信道的示意图；
图7是本申请实施例提供的又一种竞争信道的示意图；
图8是本申请实施例提供的一种信道竞争方法的示意图；
图9是本申请实施例提供的信道竞争方法的一时序示意图；
图10是本申请实施例提供的信道竞争方法的又一时序示意图；
图11是本申请实施例提供的又一种信道竞争方法的示意图；
图12是本申请实施例提供的信道竞争方法的又一时序示意图；
图13是本申请实施例提供的信道竞争方法的又一时序示意图；
图14是本申请实施例提供的通信装置的一结构示意图；
图15是本申请实施例提供的通信装置的又一结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
为便于理解本申请实施例的技术方案，下面将对本申请实施例所涉及的部分名词(或术语)的含义进行简单说明：
一、传输机会(transmission opportunity，TXOP)
TXOP时长是指一个站点(这里的站点可以指接入点或非接入点站点)获得一个传输机会后，不受干扰地进行数据传输的一段时间。获得TXOP的站点可以称为TXOP持有者(TXOP holder)。TXOP时长包括TXOP持有者传输一个或多个数据以及对应的立即响应帧(这里的立即响应帧可以指确认帧或块确认等)所需要的时长。受国家和地域法规约束，该TXOP时长不能超过一个上限，这个上限就称为TXOP limit(TXOP极限)。TXOP limit的数值受各国家和/或各地域法规约束。
可选的，AP可通过信标(beacon)帧或者探测响应(probe response)帧来广播TXOP limit的数值。
可选的，TXOP limit还与竞争到传输机会的接入类型(access category，AC，或称为访问类型)相关。具体地，如下表1所示，表1示出了4种不同接入类型对应的TXOP limit的数值。其中，AC_VO表示接入类型(或访问类型)为语音(voice)流，AC_VI表示接入类型为视频(video)流，AC_BE表示接入类型为尽力而为(best effort)流，AC_BK表示接入类型为背景(background)流。
表1：不同接入类型对应的TXOP limit说明
AC AC_BK AC_BE AC_VI AC_VO
TXOP limit 2.528ms 2.528ms 4.096ms 2.080ms
可选的，语音流的优先级大于视频流的优先级大于尽力而为流的优先级大于背景流的优先级，即优先级顺序从高到低为：AC_VO、AC_VI、AC_BE、AC_BK。可理解的，优先级越高，抢占信道的能力越高。
可理解的，本申请实施例中的“数据传输”和“传输数据”泛指通信，其中的“数据”泛指通信的信息，并不局限于数据信息，还可以是信令信息等。
二、网络分配矢量(network allocation vector，NAV)
虚拟载波监听(virtual carrier sense)是载波监听的一种，是通过控制信息来得知信道情况，而不是实际检测物理信道。具体地，虚拟载波监听从媒体接入控制(medium access control，MAC)帧中携带的相关信息来实现逻辑预测，也就是说，每一个帧携带发送站点下一个帧的持续时间(duration)信息，与之相关的各个站点根据这个持续时间信息对信道占用进行预测。如果一个站点没有侦听到持续时间信息，例如，当监听载波时，这一帧的持续时间字段已经传送完成，则站点只能依靠物理层检测。
虚拟载波监听可利用网络分配矢量NAV来实现。NAV本质上是一个倒计时计时器，随时间的流逝逐渐减少，当倒计时为0时，则认为介质处于空闲状态。因此，虚拟载波监听技术在适当的时候以适当的值设置和更新NAV的计时值。具体地，当一个站点接收到一个帧后，如果该帧的接收地址不是该站点，则该站点可以根据接收到的帧中的持续时间(duration)字段来更新NAV。如果该帧的接收地址是该站点，说明该站点为接收站点，则不可以更新NAV。
可选的，在更新NAV之前，还可以判断当前帧中duration字段的数值是否大于站点当前的NAV数值，如果大于则更新NAV；反之，如果小于或等于，则不更新NAV。其中，NAV数值从接收帧的结束时刻开始算起的。
可理解的，上述duration字段可以用于告知其他非接收站点，信道被占用的时长，防止其他非接收站点接入信道并传输数据。
可选的，当发送站点获得一个TXOP后，可以设置一个duration字段的数值使得TXOP时长不超过TXOP limit。
参见图2a，图2a是本申请实施例提供的NAV设置的一示意图。如图2a所示，发送站点获得TXOP后，在第一个发送帧(如图2a中的请求发送(request to send，RTS)帧)中设置duration字段的数值，使得TXOP时长不超过TXOP limit。然后在后续帧中设置duration字段的数值，使得后续帧中duration字段对应的结束时间点与前一个帧的duration字段对应的结束时间点相同。需要说明的，RTS帧包括duration字段，聚合媒体接入控制协议单元(aggregation MAC protocol data unit，A-MPDU)1包括duration字段，A-MPDU2也包括duration字段。针对RTS帧，其duration字段的数值大于A-MPDU1其duration字段的数值，A-MPDU1其duration字段的数值大于A-MPDU2其duration字段的数值。然而，结合图2a，可以看出，RTS帧、A-MPDU1和A-MPDU2，任意一个帧对应的NAV的结束时间点都是同一时间点。即，在非接收站点分别根据RTS帧包括的duration字段、A-MPDU1包括的duration字段和A-MPDU2包括的duration字段，更新NAV后，RTS帧、A-MPDU1和A-MPDU2，任意一个帧对应的NAV的结束时间点都是同一时间点。可理解的，图2a 中，RTS帧携带的duration字段的数值可以与TXOP时长相同。
参见图2b，图2b是本申请实施例提供的NAV设置的另一示意图。如图2b所示，发送站点获得TXOP后，如果在第一个发送帧(如图2b中的RTS帧)中设置的duration字段的数值小于TXOP limit，或者第一次设置的TXOP时长小于TXOP limit，则可以在后续帧中设置duration字段的数值，使得当前的TXOP时长超过前一个TXOP时长的结束时间点，但是从第一次设置的TXOP时长开始算起，总TXOP时长不能超过TXOP limit。需要说明的，RTS帧包括duration字段，A-MPDU1包括duration字段。结合图2b，可以看出，RTS帧对应的NAV的结束时间点1早于A-MPDU1对应的NAV的结束时间点2。即，在非接收站点分别根据RTS帧包括的duration字段和A-MPDU1包括的duration字段，更新NAV后，RTS帧对应的NAV的结束时间点1早于A-MPDU1对应的NAV的结束时间点2。且，RTS帧对应的NAV的结束时间点1和A-MPDU1对应的NAV的结束时间点2均早于TXOP limit。这表明，在RTS帧发送时刻之后发送的帧，其对应的NAV的结束时间点也是早于TXOP limit。即从第一次设置的TXOP时长开始算起，总TXOP时长不能超过TXOP limit。可理解的，非接收站点根据接收到的各个帧，更新NAV。
上述内容简要阐述了本申请实施例所涉及的部分名词(或术语)的含义，为更好地理解本申请实施例的提供的信道竞争方法，下面将对本申请实施例提供的信道竞争方法的系统架构和/或应用场景进行说明。可理解的，本申请实施例描述的场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。
本申请实施例的技术方案可以应用于无线通信系统，该无线通信系统可以为无线局域网(wireless local area network，WLAN)或蜂窝网。本申请实施例所涉及的方法可以由无线通信系统中的通信设备或通信设备中的芯片或处理器实现，该通信设备可以是一种不支持STR的无线通信设备，例如，该通信设备可以称为多链路设备或多频段设备(multi-band device)。相比于仅支持单条链路传输的通信设备来说，多链路设备具有更高的传输效率和更大的吞吐率。
多链路设备包括一个或多个隶属的站点(affiliated STA)，隶属的站点是一个逻辑上的站点，可以工作在一条链路上。其中，隶属的站点可以为接入点(access point，AP)或非接入点站点(non-access point station，non-AP STA)。为描述方便，本申请将隶属的站点为AP的多链路设备可以称为多链路AP或多链路AP设备或AP多链路设备(AP multi-link device，AP MLD)，隶属的站点为non-AP STA的多链路设备可以称为多链路STA或多链路STA设备或STA多链路设备(STA multi-link device，STA MLD)。为描述方便，“多链路设备包括隶属的站点”在本申请实施例中也简要描述为“多链路设备包括站点”。
可选的，一个多链路设备可包括多个逻辑站点，每个逻辑站点工作在一条链路上，但允许多个逻辑站点工作在同一条链路上。下文提到的链路标识表征的是工作在一条链路上的一个站点，也就是说，如果一条链路上有多于1个站点，则需要多于1个链路标识表征他们。下文提到的链路有时也表示工作在该条链路上的站点。
AP多链路设备与STA多链路设备在数据传输时，可以采用链路标识来标识一条链路或一条链路上的站点。在通信之前，AP多链路设备与STA多链路设备可以先协商或沟通链路标识与一条链路或一条链路上的站点的对应关系。因此在数据传输的过程中，不需要传输大量的信令信息用来指示链路或链路上的站点，携带链路标识即可，降低了信令开销， 提升了传输效率。
一个示例中，AP多链路设备在建立基本服务集(basic service set，BSS)时，发送的管理帧，比如beacon帧，会携带包括多个链路标识信息字段的元素，每个链路标识信息字段可以建议一个链路标识与工作在一个链路上的站点的对应关系。每个链路标识信息字段包括链路标识，还包括：MAC地址，操作集，信道号中的一个或多个，其中MAC地址，操作集，信道号中的一个或多个可以指示一条链路。另一个示例中，在多链路建立关联的过程中，AP多链路设备和STA多链路设备协商多个链路标识信息字段。在后续的通信中，AP多链路设备或者STA多链路设备会通过使用链路标识来表征多链路设备中的一个站点，链路标识还可以表征该站点的MAC地址，工作的操作集，信道号中的一个或多个属性。其中MAC地址，也可以换成关联后AP多链路设备的关联标识(association identifier，AID)。
如果是多个站点工作在一条链路上，那么链路标识(是一个数字的ID)，表征的意义除了包括链路所在的操作集，信道号，还包括工作在该链路上的站点标识，比如站点的MAC地址或者关联标识AID。
多链路设备可以遵循IEEE 802.11系列协议实现无线通信，例如，遵循极高吞吐率站点，或遵循基于IEEE 802.11be或兼容支持IEEE 802.11be的站点，实现与其他设备的通信。
本申请实施例提供的一种信道竞争方法可以应用于一个结点与一个或多个结点进行数据传输的场景中；也可以应用于单用户的上行/下行数据传输场景，多用户的上行/下行数据传输场景中；还可以应用于设备到设备(device to device，D2D)的数据传输场景中。
其中，上述任一结点可以是AP多链路设备，也可以是多链路non-AP设备。例如，AP多链路设备与一个或多个non-AP多链路设备之间进行数据传输的场景；或者non-AP多链路设备与一个或多个AP多链路设备之间进行数据传输的场景；或者non-AP多链路设备与non-AP多链路设备之间进行数据传输的场景；或者AP多链路设备与AP多链路设备之间进行数据传输的场景，本申请实施例对此不做限定。另外，本申请实施例提供的一种信道竞争方法还可以应用于仅支持在单链路进行传输的遗留站点，在此不做限制。
参见图3，图3是本申请实施例提供的无线通信系统的一架构示意图。图3以无线局域网为例，该无线通信系统包括：一个AP多链路设备100，和一个或多个non-AP多链路设备(如图3中的non-AP多链路设备200、non-AP多链路设备300、non-AP多链路设备400)。其中，该AP多链路设备是为non-AP多链路设备提供服务的多链路设备，non-AP多链路设备可以与AP多链路设备之间采用多条链路进行通信，从而达到提升吞吐率的效果。图3中AP多链路设备和non-AP多链路设备的个数，仅是示例性的。
示例性的，多链路设备(如图3的AP多链路设备100、non-AP多链路设备200、non-AP多链路设备300、non-AP多链路设备400中的任一多链路设备)为具有无线通信功能的装置，该装置可以为一个整机的设备，还可以是安装在整机设备中的芯片或处理系统等，安装这些芯片或处理系统的设备可以在这些芯片或处理系统的控制下，实现本申请实施例的方法和功能。例如，本申请实施例中的non-AP多链路设备具有无线收发功能，可以支持802.11系列协议，可以与AP多链路设备或其他non-AP多链路设备进行通信。例如，non-AP多链路设备是允许用户与AP通信进而与WLAN通信的任何用户通信设备。例如，non-AP多链路设备可以为平板电脑、桌面型、膝上型、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、手持计算机、上网本、个人数字助理(personal  digital assistant，PDA)、手机等可以联网的用户设备，或物联网中的物联网节点，或车联网中的车载通信装置等；non-AP多链路设备还可以为上述这些终端中的芯片和处理系统。本申请实施例中的AP多链路设备为non-AP多链路设备提供服务的装置，可以支持802.11系列协议。例如，AP多链路设备可以为通信服务器、路由器、交换机、网桥等通信实体，或，AP多链路设备可以包括各种形式的宏基站，微基站，中继站等，当然AP多链路设备还可以为这些各种形式的设备中的芯片和处理系统，从而实现本申请实施例的方法和功能。
可理解的，多链路设备可以支持高速率低时延的传输，随着无线局域网应用场景的不断演进，多链路设备还可以应用于更多场景中，比如为智慧城市中的传感器节点(比如，智能水表，智能电表，智能空气检测节点)，智慧家居中的智能设备(比如智能摄像头，投影仪，显示屏，电视机，音响，电冰箱，洗衣机等)，物联网中的节点，娱乐终端(比如AR，VR等可穿戴设备)，智能办公中智能设备(比如，打印机，投影仪等)，车联网中的车联网设备，日常生活场景中的一些基础设施(比如自动售货机，商超的自助导航台，自助收银设备，自助点餐机等)。本申请实施例中对于non-AP多链路设备和AP多链路设备的具体形式不做限定，在此仅是示例性说明。其中，802.11协议可以为支持802.11be或兼容802.11be的协议。
可选的，参见图4，图4是本申请实施例提供的多链路设备的一结构示意图。IEEE802.11标准关注多链路设备中的802.11物理层(physical layer，PHY)和媒体接入控制(media access control，MAC)层部分。如图4所示，多链路设备包括的多个non-AP STA在低MAC(low MAC)层和PHY层互相独立，在高MAC(high MAC)层也互相独立。参见图5，图5是本申请实施例提供的多链路设备的另一结构示意图。如图5所示，多链路设备中包括的多个non-AP STA在低MAC(low MAC)层和PHY层互相独立，共用高MAC(high MAC)层。当然，在多链路通信过程中，non-AP多链路设备可以是采用高MAC层相互独立的结构，而AP多链路设备采用高MAC层共用的结构；也可以是non-AP多链路设备采用高MAC层共用的结构，AP多链路设备采用高MAC层相互独立的结构；还可以是non-AP多链路设备和AP多链路设备都采用高MAC层共用的结构；还可以是non-AP多链路设备和AP多链路设备都采用高MAC层相互独立的结构。本申请实施例对于多链路设备的内部结构示意图并不进行限定，图4和图5仅是示例性说明。示例性的，该高MAC层或低MAC层都可以由多链路设备的芯片系统中的一个处理器实现，还可以分别由一个芯片系统中的不同处理模块实现。
示例性的，本申请实施例中的多链路设备可以是单个天线的设备，也可以是多天线的设备。例如，可以是两个以上天线的设备。本申请实施例对于多链路设备包括的天线数目不做限定。在本申请的实施例中，多链路设备可以允许同一接入类型的业务在不同链路上传输，甚至允许相同的数据包在不同链路上传输；也可以不允许同一接入类型的业务在不同链路上传输，但允许不同接入类型的业务在不同的链路上传输。
多链路设备工作的频段可以包括sub 1GHz、2.4GHz、5GHz、6GHz以及高频60GHz中的一个或多个频段。
可选的，参见图6，图6为本申请实施例提供的一种竞争信道的示意图。如图6所示，可以看出，AP MLD包括AP1和AP2，AP MLD不包括AP3，AP3可以是单个设备，也可以隶属其他AP MLD。其中，AP1工作在链路1(link1)上，AP2工作在链路2(link2)上。non-AP MLD包括non-AP STA1和non-AP STA2，non-AP MLD不包括non-AP STA3， non-AP STA3可以是单个设备，也可以隶属其他non-AP MLD。其中，non-AP STA1工作在链路1(link1)上，non-AP STA2和non-AP STA3工作在链路2(link2)上。non-AP STA1在链路1上向AP1发送请求发送(Request-To-Send，RTS)帧。AP1在链路1上接收该请求发送帧后，可以在链路1上向non-AP STA1回复空闲发送(Clear-To-Send，CTS)帧。当non-AP STA1在链路1上接收该空闲发送帧后，可以在链路1上向AP1发送数据(data)帧。当AP1在链路1上接收该数据帧后，AP1可以在链路1上向non-AP STA1发送确认块(block ACK)。
需要说明的，由于链路1与链路2的频段频率间隔较小，当链路1上有数据传输时，信道干扰可能影响到对链路2的CCA。这可能无法监听到链路2的信道信息，即链路2处于盲状态(blindness period，或，deaf period)。其中，盲状态指无法监听到信道上的信息。进一步的，当链路1上有数据传输时，即使non-AP STA2在链路2上发送请求发送帧，也可能由于信道干扰导致无法接收到该请求发送帧。因此，这可能会导致non-AP STA2错过网络分配矢量(network allocation vector，NAV)的刷新。
另外，结合图6，可以看出，当链路1上数据传输完成后，non-AP STA3开始竞争信道。进一步的，non-AP STA3在链路2上发送了请求发送帧，non-AP STA3也在链路2上接收到了空闲发送帧。接着，non-AP STA3可以在链路2上向AP2发送数据帧。而此时，链路2上正在传输请求发送帧。即，non-AP STA3在链路2上向AP2发送的数据帧与链路2上的请求发送帧碰撞。因此，在这种情况下导致的碰撞问题即为盲问题。
为了解决上述问题，在标准802.11-20/1009r1中提出可以在数据传输完成后，针对其他链路，non-STR MLD可以设置媒体同步时延(medium sync delay)计时器，在该计数器内采用(to be decided，TBD)的能量检测(energy detection，ED)阈值对其他链路进行CCA。若其他链路中有某条链路的CCA检测不通过，则意味着该链路上正在传输重合基本服务集合(overlapping basic service set，OBSS)帧。当该OBSS帧传输结束后，non-STR MLD开始竞争信道，启动增强分布式信道接入(enhanced distributed channel access，EDCA)。即，当该OBSS帧传输结束后，在该链路上发送请求发送帧。然而，可能该链路上的OBSS帧对应的传输机会(transmission opportunity，TXOP)仍未结束，即该链路上正在传输该OBSS帧对应的确认块。因此，即，在该链路上该OBSS帧对应的确认块与该链路上的请求发送帧发生碰撞。
参见图7，图7为本申请实施例提供的又一种竞争信道的示意图。如图7所示，STR AP MLD包括AP1和AP2，STR AP MLD不包括AP3，AP3可以是单个设备，也可以隶属其他AP MLD其中，AP1工作在链路1(link1)上，AP2和AP3工作在链路2(link2)上。non-STR non-AP MLD包括non-AP STA1和non-AP STA2，non-STR non-AP MLD不包括non-AP STA3，non-AP STA3可以是单个设备，也可以隶属其他non-AP MLD。其中，non-AP STA1工作在链路1(link1)上，non-AP STA2和non-AP STA3工作在链路2(link2)上。
non-AP STA1在链路1上向AP1发送上行PPDU时，由于链路1与链路2的频段频率间隔较小，导致链路2处于盲状态(参见图7所示的blindness for non AP STA 2)。当链路1上数据传输完成后，non-AP STA2启动媒体同步延迟(medium sync delay)计时器。即，链路1上的上行PPDU的结束时刻与媒体同步延迟的开始时刻对齐/相同。在媒体同步延迟内，non-AP STA2使用TBD(To be decided)的能量检测(energy detection，ED)阈值，比如-82dbm到-62dbm，对链路2进行CCA检测。此时，如果链路2上正在传输下行PPDU， 即链路2上的下行PPDU的开始时刻早于对链路2进行CCA检测的时刻，链路2上的下行PPDU的结束时刻与该CCA检测通过的时刻对齐/相同，那么，non-AP STA2确定链路2处于忙碌状态。参见图7，non-AP STA2确定链路2处于忙碌状态是指在所述下行PPDU(TA是AP3，RA是non-AP STA3)的结束时刻前non-AP STA2认为链路2处于“CCA busy”，所述下行PPDU的结束时刻也是“CCA检测通过”的开始时刻，“CCA检测通过”是指non-AP STA2确定或者检测到链路2不再处于忙碌状态。在这种情况下，non-AP STA2开始退避。即，链路2上的下行PPDU传输完成后，non-AP STA2就在链路2上启动EDCA。参见图7，链路2上的non-AP STA2 back off的起始时刻是下行PPDU传输完成的时刻，此处与图9中的non-AP STA2 back off的起始时刻不同。需要说明的，也有可能是采用了更加严格的ED阈值，导致non-AP STA2确定链路2处于忙碌状态。本领域技术人员知道，CCA忙碌是指检测到的信号超过ED阈值，CCA闲是指检测到的信号不超过ED阈值。non-AP STA2可能错过包头，导致无法更新NAV。从而无法在更新的NAV结束之后，non-AP STA2在链路2上启动EDCA。参见图7，链路2上的下行PPDU(TA是AP3，RA是non-AP STA3)的起始时刻位于图7所示的blindness for non AP STA 2中，这时non-AP STA2无法检测或者接收到DL PPDU。
进一步的，non-AP STA2可以在链路2上向AP2发送请求发送帧。前述请求发送帧可以参见图7中的RTS(TA是non-AP STA2，RA是AP2)。然而，可能链路2上的下行PPDU对应的传输机会(transmission opportunity，TXOP)仍未结束，即链路2上正在传输下行PPDU对应的确认块(可能该确认块未被non-STR non-AP MLD感知，导致无法刷新NAV)。前述确认块可以参见图7中的BA(TA是non-AP STA3，RA是AP3)。结合图7，可以看出，链路2上的下行PPDU对应的确认块的开始时刻与链路2上的向AP2发送的请求发送帧的开始时刻对齐/相同，即链路2上下行PPDU对应的确认块与链路2上向AP2发送的请求发送帧发生碰撞。参考图7，上述“发生碰撞”具体是指链路2上的下行PPDU对应的确认块与链路2上的向AP2发送的请求发送帧的持续时间至少有重叠。
本领域技术人员可以理解，前述non-AP STA2“错过包头”是指该non-AP STA2没有检测到或者收到PPDU的包头。本领域技术人员知道PPDU的包头即前导码preamble，至少包括L-LTF,L-STF,L-SIG等字段。没有检测到PPDU的包头，相当于non-AP STA2认为没有PPDU的起始(no start of a PPDU)。
因此，为了解决在进行信道竞争时如何避免帧间碰撞和干扰的问题，本申请提出了一种信道竞争方法，可以支持不能同时收发的多链路设备在进行信道竞争时减少帧间碰撞和干扰的问题，提高了通信效率。
下面将结合图8-图13对本申请实施例提供的一种信道竞争方法进行详细说明。本申请实施例以第一多链路设备来描述该方法。
在一些可行的实施方式中，本申请实施例的第一多链路设备和第二多链路设备中的一个或者多个多链路设备不支持在多条链路上同时发送和接收(STR)。可理解的，本申请所述的“支持STR”可以指多链路设备具备STR的能力，且在此次通信中使用STR能力；“不支持STR”可以指多链路设备不具备STR的能力，或者可以指多链路设备具备STR的能力，但在此次通信中不使用STR能力。还可理解的，多链路设备在某些情况下可实现STR与non-STR之间的切换，即从支持STR切换到不支持STR，或从不支持STR切换到支持STR。下文将以第一多链路设备不支持STR，第二多链路设备支持STR为例，对本申请实施例提 供的一种信道竞争方法进行说明。
可选的，本申请实施例提及的第一多链路设备可以为图3中的non-AP多链路设备200，第二多链路设备可以为图3中的AP多链路设备100。可理解的，为便于描述，下文以non-AP多链路设备200包括2个non-AP STA为例进行说明。本申请实施例提及的第一非接入点站点可以为non-AP多链路设备200中的任意一个STA，第二非接入点站点为non-AP多链路设备200中的另一STA。本申请实施例提及的第一接入点为AP多链路设备100中的任意一个AP。其中，本申请实施例以两个链路为例进行说明，实际应用中可能有多个(大于两个)链路，多个链路的实现方式，可参考本申请实施例提供的两个链路的实现方式，在此不再赘述。
参见图8，图8为本申请实施例提供的一种信道竞争方法的示意图。如图8所示，本申请实施例提供的一种信道竞争方法包括但不限于以下步骤：
801、在第一链路上数据传输完成后或在第一链路上接收到该数据对应的确认块后，第一多链路设备的第一非接入点站点在第一时间段内对第二链路进行空闲信道评估CCA检测。
其中，在第一链路上传输的数据可以为无线帧，比如，数据帧、管理帧等，在此不做限制。
其中，该第一时间段对应的开始时刻与第一链路上数据传输完成的时刻对齐/相同。
另外，在第一链路上数据传输完成后，第一非接入点站点在第一时间段内对第二链路进行CCA检测。该第一时间段对应的开始时刻早于第一链路上接收到该数据对应的确认块的时刻。
可理解的，本申请实施例中的“对齐”可以指时间上的同步，比如，发送起始时刻对齐(即相同)和/或发送结束时刻对齐(即相同)。另外本申请实施例中的“对齐”，“同步”，“同时”以及“时刻相同”，并不是指的严格意义上的完全绝对相同，在实际实现中，受到两个链路上的PPDU传输参数不同、接入时间不同，收发机处理能力等因素，这里的“对齐”，“同步”或“同时”是允许有一个微小的偏移的，比如不超过短帧间间隔SIFS时间。
需要说明的，第一时间段为一个倒计时计时器对应的时间段。在第一链路上数据传输完成的时刻，该第一非接入点站点启动倒计时计时器。例如，参考图9，“第一时间段”从链路1上的UL PPDU传输结束时开始。
可选的，该第一时间段对应的开始时刻可以为媒体同步延迟计时器(MediumSyncDelay timer，可以参考802.11-20/1009r1中的媒体同步延迟计时器的相关描述)对应的开始时刻，该第一时间段对应的结束时刻可以为媒体同步延迟计时器对应的结束时刻。即，可以理解的，以第一链路上数据传输完成的时刻为基准，该第一非接入点站点启动媒体同步延迟计时器。
另外，该第一时间段对应的开始时刻也可以由第二多链路设备或第二多链路设备的第一接入点设置。比如，针对第一链路和第二链路，第二多链路设备可以设置相同或不同的第一时间段对应的开始时刻。进一步的，第一接入点工作在第二链路。
802、当对第二链路的CCA检测不通过时，该第一非接入点站点根据第二时间段，在第二链路上进行信道竞争。
其中，第二时间段的开始时刻与该CCA的结束时刻对齐/相同。该CCA检测的开始时 刻与第一链路上数据传输完成的时刻对齐/相同，或该CCA检测的开始时刻与第一链路上接收到该数据对应的确认块的时刻对齐/相同。需要说明的，在第二时间段的开始时刻的前一时刻，第一非接入点站点在第二链路上进行CCA检测时，CCA检测不通过；在第二时间段的开始时刻的后一时刻，第一非接入点站点在第二链路上进行CCA检测时，CCA检测通过。前述第一非接入点站点例如图9的non AP STA2，前述CCA检测不通过即指图9中的链路2上的CCA Busy状态，该CCA Busy状态在图9中“第二时间段”之前持续。前述CCA检测通过即指图9中的链路2上的CCA Busy结束之后的状态，这时可以理解为非CCA Busy，即CCA Idle，从CCA Busy切换到CCA Idle起，进入“第二时间段”。
可以理解的，第二时间段可以为经扩展的帧间间隔EIFS时间。该EIFS时间可以为aSIFSTime+AckTxTime+aSIFSTime。其中，aSIFSTime为一个短时间间隔SIFS时间，AckTxTime为发送应答(Ack)帧的时间。
进一步的，第二时间段的最小值可以为aSIFSTime+AckTxTime+aSIFSTime。
可以理解的，当对第二链路的CCA检测通过时，可以按照802.11-20/1009r1在第二链路上进行信道竞争。这里“按照802.11-20/1009r1”的方案是指前述图7所述的方案。该图7的方案与图9所述的方案不同，在图9记载的方案中，在“第二时间段”之后才能进行进行信道竞争，即图9中所示的non AP STA2 back off。显然的，按照图9的方案可以减少可能发生的碰撞。
需要说明的，在本申请中，在第二链路上进行信道竞争，可以包括：第一非接入点站点在第二链路上采用带有冲突避免的载波侦听多址接入(carrier sense multiple access with collision avoidance，CSMA/CA)机制进行信道竞争或采用增强型分布式信道接入(enhanced distributed channel access，EDCA)机制进行信道竞争，在此不做限制。
其中，为了保证接入点和非接入点站点能够接入无线媒体(wireless medium)而又不互相之间发生冲突碰撞，802.11中使用了CSMA/CA机制，该机制也被称为分布式协调功能(distributed coordination function，DCF)。CSMA/CA机制具体为：非接入点站点在发送数据之前，需要对无线媒体进行空闲信道评估(clear channel access,CCA)。如果无线媒体在一段时间内(如分布式帧间间隔(distributed inter-frame space，DIFS))空闲，则非接入点站点可以开始随机退避过程。如果无线媒体在该段时间内繁忙，则非接入点站点需等待无线媒体变为空闲后并保持一段时间(如DIFS)空闲，再开始随机退避过程。当随机退避过程结束后，非接入点站点可以进行帧交换。其中，随机退避过程中的退避时间(backoff time)等于一个随机回退值与一个时隙(slot)时间的乘积。随机回退值是从一个均匀分布的竞争窗口[0,CW]中随机选取的一个值。可理解的，随机退避过程中的退避时间等于信道竞争中退避计数器的初始值。
可选的，CSMA/CA机制中竞争窗口(contention window，CW)存在多个值，非接入点站点首次尝试(Initial Attempt)信道竞争时，CW的值为最小值，即CWmin。当每一次传输失败(例如发生冲突)时，需要进行重传(retransmission)，重新进行信道竞争，CW的值就逐次增大，直到达到CW的最大值，即CWmax。当成功发送数据/传输成功时，CW被重置(reset)为CWmin。
其中，EDCA机制是DCF的增强，它允许不同接入等级的业务具有不同的EDCA参数集。其中，EDCA参数集包括CWmin，CWmax，仲裁帧间距(arbitration inter-frame space， AIFS)等参数。不同接入等级的EDCA参数如表2所示，AC_VO表示接入等级为语音(voice)流，AC_VI表示接入等级为视频(video)流，AC_BE表示接入等级为尽力而为(best effort)流，AC_BK表示接入等级为背景(background)流。
表2：不同接入等级的EDCA参数
Figure PCTCN2021107596-appb-000001
对于某种特定接入等级的业务，其随机退避过程与DCF基本相同，区别在于AIFS取代了DCF中的DIFS，即当信道重新回到空闲时，必须保持AIFS内空闲后才能进行随机退避过程。AIFS的计算方法可以为仲裁帧间距数(AIFS number，AIFSN)和一个时隙时间(a Slot Time)的乘积、与一个短帧间间隔(short inter-frame space，SIFS)之和，即AIFS[AC]＝a SIFS time+AIFSN[AC]*(a Slot Time)。可理解的，AIFS和SIFS的单位均为时间单位。
可选的，在第一时间段内对第二链路进行空闲信道评估CCA检测，包括：第一非接入点站点调整CCA阈值，得到调整后的CCA阈值，调整后的CCA阈值低于调整前的CCA阈值；第一非接入点站点在第一时间段内根据调整后的CCA阈值，对第二链路进行该CCA检测。
其中，该CCA阈值包括能量检测阈值或帧中检测阈值。
需要说明的，本实施方式中，调整前的能量检测阈值可以为-82dbm到-62dbm。调整前的帧中检测阈值可以为-72dbm。进一步的，调整后的帧中检测阈值可以为低于-72dbm的值，比如，调整后的帧中检测阈值可以为-82dbm。
可以理解的，在实施方式中，将根据调整后的CCA阈值对链路进行CCA检测的方式可以称为增强CCA，具体的称呼在此不做限制。进一步的，在本申请中，CCA包括除该增强CCA之外的CCA或增强CCA。比如，除该增强CCA之外的CCA为根据调整前的能量检测阈值或调整前的帧中检测阈值对链路进行CCA检测的方式。可以理解的，第一非接入点站点可以在第一时间段内对第二链路进行CCA检测，包括：第一非接入点站点在第一时间段内对第二链路进行增强CCA检测或除该增强CCA之外的CCA检测。当对第二链路的增强CCA检测或除该增强CCA之外的CCA检测不通过时，第一非接入点站点可以根据第二时间段，在第二链路上进行信道竞争。
本领域技术人员知道，前述记载的“CCA检测不通过”包括：检测到的信号的强度大于前述提到的CCA阈值，此时记为CCA busy。前述CCA阈值例如能量检测阈值(CCA-ED)或者帧中检测阈值(midamble-ED)。相应的，“CCA检测通过”是指检测到的信号的强度不大于前述提到的CCA阈值，此时记为CCA Idle。具体的，可以参考IEEE Std 802.11-2016,19.3.19.5.1 CCA-Energy Detect(CCA-ED)相关的规定：
当接收到的信号强度超过CCA-ED阈值时，CCA-ED应检测信道繁忙条件，如主20MHz信道的dot11OFDMEDTThreshold和辅助20MHz信道的dot11OFDMEDTThreshold(如 果存在)给出的阈值。要求CCA-ED的操作等级的CCA-ED阈值应符合D.2.5中的标准。(CCA-ED shall detect a channel busy condition when the received signal strength exceeds the CCA-ED threshold as given by dot11OFDMEDThreshold for the primary 20MHz channel and dot11OFDMEDThreshold for the secondary 20MHz channel(if present).The CCA-ED thresholds for the operating classes requiring CCA-ED are subject to the criteria in D.2.5.)
可选的，根据第二时间段，在第二链路上进行信道竞争，包括：若第二时间段对应的结束时刻早于第一时间段对应的结束时刻，第一非接入点站点则在第二时间段对应的结束时刻之后在第二链路上进行信道竞争。如图9所描述的方案，前述“当对第二链路的CCA检测不通过时，该第一非接入点站点根据第二时间段，在第二链路上进行信道竞争”是指:在该第一非接入点站点(图9的non AP STA2)检测到CCA Busy转换为非CCA Busy(CCA Idle)后，再经过第二时间段(图9所述内容符合前述“第二时间段对应的结束时刻早于第一时间段对应的结束时刻”)后，该第一非接入点站点才开始进行退避(图9中的non AP STA2 back off)。这里和图7中的方案不同，图7中的方案是在该第一非接入点站点(图7的non AP STA2)检测到CCA Busy转换为非CCA Busy(CCA Idle)后便可以立即开始进行退避。若第二时间段对应的结束时刻晚于第一时间段对应的结束时刻，第一非接入点站点则在第一时间段对应的结束时刻之后或第二时间段对应的结束时刻之后在第二链路上进行信道竞争。如图10所描述的方案，前述“当对第二链路的CCA检测不通过时，该第一非接入点站点根据第二时间段，在第二链路上进行信道竞争”是指:在该第一非接入点站点(图10的non AP STA2)检测到CCA Busy转换为非CCA Busy(CCA Idle)后，在第一时间段和第二时间段的结束时刻这两个时刻中的之一，该第一非接入点站点(图10的non AP STA2)才可以开始进行退避(图10中的non AP STA2 back off)。这里和图7中的方案不同，图7中的方案是在该第一非接入点站点(图7的non AP STA2)检测到CCA Busy转换为非CCA Busy(CCA Idle)后便可以立即开始进行退避。
需要说明的，若第二时间段对应的结束时刻早于第一时间段对应的结束时刻，第一非接入点站点可以在第二时间段对应的结束时刻开始退避。若第二时间段对应的结束时刻晚于第一时间段对应的结束时刻，第一非接入点站点可以在第一时间段对应的结束时刻开始退避，或在第二时间段对应的结束时刻开始退避。
可理解的，上述图8仅是本申请实施例提供的信道竞争方法的一种流程，本申请的信道竞争方法还可以有其他的流程实现。下面将结合几个具体示例，对本申请的信道竞争方法的时序流程进行简要介绍。其中，下面的具体示例仅是为方便理解所做的示例，在实际应用中，本申请的信道竞争方法的时序流程可多于或少于下述具体示例的流程。
为便于描述，下面的具体示例均假设第一多链路设备(如non-AP MLD)包括non-AP STA1和non-AP STA2，第一多链路设备不包括non-AP STA3，non-AP STA3可以是单个设备，也可以隶属其他non-AP MLD。non-AP STA1工作在链路1(link1)上，non-AP STA2和non-AP STA3工作在链路2(link2)上。第二多链路设备(如AP MLD)包括AP1和AP2，第二多链路设备不包括AP3，AP3可以是单个设备，也可以隶属其他AP MLD。AP1工作在链路1，AP2和AP3工作在链路2上；第一多链路设备不支持STR，第二多链路设备支持STR。
一个示例中，参见图9，图9是本申请实施例提供的信道竞争方法的一时序示意图。如图9所示，non-AP STA1在链路1上向AP1发送上行PPDU，由于链路1与链路2的频 段频率间隔较小，当链路1上有数据传输时，信道干扰可能影响到对链路2的CCA。这导致无法监听到链路2的信道信息，即链路2处于盲状态。前述盲状态即图9中所示的blindness for non AP STA2，图9中描述的实施例中，在non AP STA2在链路2上处于盲状态时，链路2上有AP3在向non AP STA3发送DL PPDU。这时，non AP STA2检测不到DL PPDU的开始。
结合图9，可以看出，链路1上的上行PPDU的发送时刻与链路2盲状态开始时刻对齐/相同，链路1上的上行PPDU的结束时刻与链路2盲状态结束时刻对齐/相同。因此，当链路1上的上行PPDU传输完成后，AP1可以在链路1上向non-AP STA1发送确认块。另外，当链路1上的上行PPDU传输完成后，链路2处于非盲状态，即可以监听到链路2的信道信息。可以理解的，当链路1上的上行PPDU传输完成后，non-AP STA2可以以第一时间段对应的开始时刻为基准开始计时。即，non-AP STA2启动倒计时计时器，该倒计时计时器对应的时间段为第一时间段对应的时间段。在第一时间段内，non-AP STA2可以对链路2进行CCA检测。
进一步的，在对链路2进行CCA检测时，由于AP3在链路2正在向non-AP STA3发送下行PPDU，导致对链路2的CCA检测不通过。该“CCA检测不通过”即图9中所示的“CCA Busy”。可以理解的，当该下行PPDU传输完成后，通过了对链路2的CCA检测。该“通过CCA检测”即图9中的“CCA Busy”结束，也即“CCA idle”开始。结合图9，可以看出，该下行PPDU传输结束时刻与对链路2的CCA检测通过的时刻相同/对齐，第二时间段对应的开始时刻与对链路2的CCA检测通过的时刻相同/对齐。进一步的，在第二时间段内，链路2正在传输该下行PPDU对应的确认块BA。而链路2完成传输该下行PPDU对应的确认块的时刻早于第二时间段对应的结束时刻，第二时间段对应的结束时刻早于第一时间段对应的结束时刻，non-AP STA2在第二时间段对应的结束时刻开始退避。在这种情况下，避免了帧间碰撞和干扰的问题。
另一个示例中，参见图10，图10是本申请实施例提供的信道竞争方法的一时序示意图。如图10所示，non-AP STA1在链路1上向AP1发送上行PPDU，由于链路1与链路2的频段频率间隔较小，当链路1上有数据传输时，信道干扰可能影响到对链路2的CCA检测。这导致无法监听到链路2的信道信息，即链路2处于盲状态。前述盲状态即图10中所示的blindness for non AP STA2，图10中描述的实施例中，在non AP STA2在链路2上处于盲状态时，链路2上有AP3在向non AP STA3发送DL PPDU。这时，non AP STA2检测不到DL PPDU的开始。
结合图10，可以看出，链路1上的上行PPDU的发送时刻与链路2盲状态开始时刻对齐/相同，链路1上的上行PPDU的结束时刻与链路2盲状态结束时刻对齐/相同。因此，当链路1上的上行PPDU传输完成后，AP1可以在链路1上向non-AP STA1发送确认块。另外，当链路1上的上行PPDU传输完成后，链路2处于非盲状态，即可以监听到链路2的信道信息。可以理解的，当链路1上的上行PPDU传输完成后，non-AP STA2可以以第一时间段对应的开始时刻为基准开始计时。即，non-AP STA2启动倒计时计时器，该倒计时计时器对应的时间段为第一时间段对应的时间段。在第一时间段内，non-AP STA2可以对链路2进行CCA检测。
进一步的，在对链路2进行CCA检测时，由于AP3在链路2正在向non-AP STA3发送下行PPDU，导致对链路2的CCA检测不通过。该“CCA检测不通过”即图10中所示 的“CCA Busy”。可以理解的，当该下行PPDU传输完成后，通过了对链路2的CCA检测。该“通过CCA检测”即图10中的“CCA Busy”结束，也即“CCA idle”开始。结合图10，可以看出，该下行PPDU传输结束时刻与对链路2的CCA检测通过的时刻相同/对齐，第二时间段对应的开始时刻与对链路2的CCA检测通过的时刻相同/对齐。进一步的，在第二时间段内，链路2正在传输该下行PPDU对应的确认块。而链路2完成传输该下行PPDU对应的确认块的时刻早于第二时间段对应的结束时刻，第二时间段对应的结束时刻晚于第一时间段对应的结束时刻，non-AP STA2在第二时间段对应的结束时刻或第一时间段对应的结束时刻开始退避。在这种情况下，也避免了帧间碰撞和干扰的问题。
参见图11，图11为本申请实施例提供的又一种信道竞争方法的示意图。如图11所示，本申请实施例提供的又一种信道竞争方法包括但不限于以下步骤：
1101、第一非接入点站点根据无线帧，更新网络配置向量NAV，得到更新后的NAV。
其中，该无线帧为在第一链路上正在传输该数据时或在第一链路上正在传输该数据对应的确认块时在第二链路上发送给第二非接入点站点的无线帧，第二非接入点站点为第一多链路设备中除第一非接入点站点之外的非接入点站点。可以理解的，该无线帧是在第二链路处于盲状态时接收到的无线帧，且第一非接入点站点可以根据该无线帧，更新网络配置向量NAV，得到更新后的NAV。
其中，关于该数据，可以参考图8步骤801中关于该数据的描述，在此不加赘述。
其中，无线帧例如可以包括块确认、数据帧、管理帧、触发(trigger)帧等，在此不做限制。
进一步的，第一非接入点站点可以根据无线帧中携带的持续时间信息，更新网络配置向量NAV，得到更新后的NAV。在更新之前，该持续时间信息大于该NAV，即更新后的NAV大于该NAV。可以理解的，该无线帧可以包括持续时间(duration)字段，该duration字段用于指示该持续时间信息，第一非接入点站点可以根据无线帧包括的duration字段，更新网络配置向量NAV，得到更新后的NAV。具体的更新方式，在本申请中不做限制。
比如，第一多链路设备中除第一非接入点站点和第二非接入点站点之外的其他非接入点站点在第二链路上发送PPDU，那么，第一非接入点站点可以根据该PPDU携带的块确认，更新网络配置向量NAV，得到更新后的NAV。该块确认携带持续时间信息，即第一非接入点站点可以根据该块确认携带的持续时间信息，更新网络配置向量NAV，得到更新后的NAV。
1102、第一非接入点站点根据更新后的NAV，对第二链路进行信道竞争。
可选的，根据更新后的NAV，对第二链路进行信道竞争，包括：若更新后的NAV小于在第一链路上该数据传输完成的时刻或在第一链路上接收到确认块的时刻，第一非接入点站点则在第一时间段内对第二链路进行CCA检测；当对第二链路的CCA检测不通过时，第一非接入点站点根据第二时间段，在第二链路上进行信道竞争；或，
若更新后的NAV大于在第一链路上数据传输完成的时刻或在第一链路上接收到确认块的时刻，第一非接入点站点则在更新后的NAV退避至零时在第二链路上进行信道竞争。
其中，关于第一时间段，可以参考图8步骤801中第一时间段的描述，在此不加赘述。关于第二时间段，可以参考图8步骤802中第二时间段的描述，在此不加赘述。另外，关于当CCA检测不通过时，第一非接入点站点根据第二时间段，在第二链路上进行信道竞 争，可以参考图8步骤802相关描述，在此不加赘述。
需要说明的，若更新后的NAV大于在第一链路上数据传输完成的时刻或在第一链路上接收到确认块的时刻，第一非接入点站点根据更新后的NAV开始退避。在更新后的NAV退避为0之前，无论第一链路上的数据是否已传输完成，在更新后的NAV退避为0时，第一非接入点站点可以在第二链路上进行信道竞争。进一步的，在更新后的NAV退避为0时，第一非接入点站点对第二链路上进行除该增强CCA之外的CCA检测。在对第二链路的CCA检测通过时，第一非接入点站点可以在第二链路上进行帧交换。
可以理解的，更新后的NAV退避为0的时刻可以早于或晚于或等于第一链路上数据传输完成的时刻，在此不做限制。进一步的，在第一链路上数据传输完成的时刻，第一非接入点站点启动倒计时计时器，该倒计时计时器对应的时间段为第一时间段。
可选的，在第一链路上数据传输完成的时刻，无论更新后的NAV是否退避为0，第一非接入点站点均可以启动倒计时计时器，该倒计时计时器对应的时间段为第一时间段。
另外，若更新后的NAV退避为0的时刻可以晚于第一链路上数据传输完成的时刻，那么，第一非接入点站点可以在第一时间段内进行信道竞争。进一步的，在更新后的NAV退避为0时，第一非接入点站点可以在第一时间段内对第二链路上进行除该增强CCA之外的CCA检测。在该CCA检测通过时，第一非接入点站点可以在第二链路上进行帧交换。
可理解的，上述图11仅是本申请实施例提供的信道竞争方法的一种流程，本申请的信道竞争方法还可以有其他的流程实现。下面将结合几个具体示例，对本申请的信道竞争方法的时序流程进行简要介绍。其中，下面的具体示例仅是为方便理解所做的示例，在实际应用中，本申请的信道竞争方法的时序流程可多于或少于下述具体示例的流程。
为便于描述，下面的具体示例均假设第一多链路设备(如non-AP MLD)包括non-AP STA1和non-AP STA2，第一多链路设备不包括non-AP STA3，non-AP STA3可以是单个设备，也可以隶属其他non-AP MLD。non-AP STA1工作在链路1(link1)上，non-AP STA2和non-AP STA3工作在链路2(link2)上。第二多链路设备(如AP MLD)包括AP1和AP2，第二多链路设备不包括AP3，AP3可以是单个设备，也可以隶属其他AP MLD。AP1工作在链路1，AP2和AP3工作在链路2上；第一多链路设备不支持STR，第二多链路设备支持STR。
一个示例中，参见图12，图12是本申请实施例提供的信道竞争方法的一时序示意图。如图12所示，non-AP STA1在链路1上向AP1发送PPDU1，由于链路1与链路2的频段频率间隔较小，当链路1上有数据传输时，信道干扰可能影响到对链路2的CCA。这导致无法监听到链路2的信道信息，即链路2处于盲状态。结合图12，可以看出，链路1上的PPDU1的发送时刻与链路2盲状态开始时刻对齐/相同，链路1上的PPDU1的结束时刻与链路2盲状态结束时刻对齐/相同。因此，当链路1上的PPDU1传输完成后，AP1可以在链路1上向non-AP STA1发送确认块1。另外，当链路1上的PPDU1传输完成后，链路2处于非盲状态，即可以监听到链路2的信道信息。可以理解的，当链路1上的PPDU1传输完成后，non-AP STA2可以以第一时间段对应的开始时刻为基准开始计时。即，non-AP STA2启动倒计时计时器，该倒计时计时器对应的时间段为第一时间段对应的时间段。
进一步的，在链路2处于盲状态时，AP3在链路2上正在向non-AP STA3发送PPDU2。结合图12，可以看出，链路2上PPDU2的发送时刻晚于链路2盲状态开始时刻，链路2 上PPDU2的接收时刻早于链路2盲状态结束时刻。即，PPDU2是在链路2处于盲状态时non-AP STA3接收的。进一步的，当non-AP STA3接收该PPDU2时，non-AP STA2可以根据该PPDU2更新NAV。可选的，链路2上PPDU2的接收结束时刻可以早于或晚于或等于链路2盲状态结束时刻，在此不做限定。
可以理解的，当该PPDU2传输完成后，通过了对链路2的CCA检测。结合图12，可以看出，该PPDU2传输结束时刻与对链路2的CCA检测通过的时刻相同/对齐。进一步的，当non-AP STA3接收到该PPDU2后，可以在第二链路上向AP3发送确认块2。non-AP STA2根据该确认块2再次更新NAV。接着，non-AP STA2可以根据再次更新后的NAV进行退避。当再次更新后的NAV退避为0时，non-AP STA2对第二链路上进行除该增强CCA之外的CCA检测。在该CCA检测通过时，第一非接入点站点可以在第二链路上进行帧交换。
另外，结合图12，可以看出，在第一链路上数据传输完成的时刻，无论再次更新后的NAV是否退避为0，第一非接入点站点均以第一时间段对应的开始时刻为基准开始计时。即在第一链路上数据传输完成的时刻，第一非接入点站点启动倒计时计时器，该倒计时计时器对应的时间段为第一时间段。
可以理解的，PPDU2对应的NAV结束时刻早于确认块2对应的NAV结束时刻。可选的，若在确认块2之后接收到来自AP3的其他PPDU，non-AP STA2还可以根据其他PPDU再次更新NAV。
一个示例中，参见图13，图13是本申请实施例提供的信道竞争方法的一时序示意图。如图13所示，non-AP STA1在链路1上向AP1发送PPDU1，由于链路1与链路2的频段频率间隔较小，当链路1上有数据传输时，信道干扰可能影响到对链路2的CCA。这导致无法监听到链路2的信道信息，即链路2处于盲状态。结合图13，可以看出，链路1上的PPDU1的发送时刻与链路2盲状态开始时刻对齐/相同，链路1上的PPDU1的结束时刻与链路2盲状态结束时刻对齐/相同。因此，当链路1上的PPDU1传输完成后，AP1可以在链路1上向non-AP STA1发送确认块1。另外，当链路1上的PPDU1传输完成后，链路2处于非盲状态，即可以监听到链路2的信道信息。
进一步的，AP3在链路2正在向non-AP STA3发送PPDU2。可以理解的，该PPDU2发送时刻晚于链路2盲状态开始时刻，该PPDU2接收时刻早于链路2盲状态结束时刻。即，该PPDU2是在链路2处于盲状态时接收到的PPDU。进一步的，当non-AP STA3接收到该PPDU2时，non-AP STA2根据该PPDU2更新NAV。另外，当non-AP STA3接收到该PPDU2后，可以在第二链路上向AP3发送确认块2。non-AP STA2可以根据该确认块2再次更新NAV。接着，non-AP STA2可以根据再次更新后的NAV进行退避。当再次更新后的NAV退避为0时，non-AP STA2对第二链路上进行除该增强CCA之外的CCA检测。在该CCA检测通过时，第一非接入点站点可以在第二链路上进行帧交换。可选的，链路2上PPDU2的接收结束时刻可以早于或晚于或等于链路2盲状态结束时刻，在此不做限定。
另外，结合图13，可以看出，在第一链路上数据传输完成的时刻，无论再次更新后的NAV是否退避为0，第一非接入点站点均以第一时间段对应的开始时刻为基准开始计时。即在第一链路上数据传输完成的时刻，第一非接入点站点启动倒计时计时器，该倒计时计时器对应的时间段为第一时间段。
可以理解的，PPDU2对应的NAV结束时刻与确认块2对应的NAV结束时刻相同。可选的，若在确认块2之后接收到来自AP3的其他PPDU，non-AP STA2还可以根据其他PPDU再次更新NAV。
根据本技术领域已知的标准，前文各实施方式所述的CCA检测至少包括在PPDU占用的主20MHz信道(Primary 20MHz channel)上的检测，具体的可以参考IEEE Std 802.11-2016，10.22.2.5等章节的内容：当STA和STA是其成员的BSS都支持多个信道宽度时，EDCA TXOP仅基于主信道的活动获得。本子条款中的“空闲介质”是指“空闲主信道”。同样，“忙介质”是指“忙主信道”。一旦根据本子条款获得了EDCA TXOP，使用，11.16.9和10.22.3中定义的进一步约束可能会根据辅助信道、辅助40MHz信道或辅助80MHz信道上的CCA状态限制TXOP期间的传输宽度或拒绝信道访问。(When a STA and the BSS,of which the STA is a member,both support multiple channel widths,an EDCA TXOP is obtained based solely on activity of the primary channel.“Idle medium”in this subclause means“idle primary channel.”Likewise“busy medium”means“busy primary channel.”Once an EDCA TXOP has been obtained according to this subclause,further constraints defined in 11.16.9 and 10.22.3 might limit the width of transmission during the TXOP or deny the channel access,based on the state of CCA on secondary channel,secondary 40MHz channel,or secondary 80MHz channel.)
上述内容详细阐述了本申请提供的方法，为了便于更好地实施本申请实施例的上述方案，本申请实施例还提供了相应的装置或设备。
参见图14，图14是本申请实施例中提供的通信装置的一结构示意图。如图14所示，该通信装置1400可以是上述实施例中的第一多链路设备，还可以是第一多链路设备中的芯片或处理系统，可以实现上述任意一个实施例的方法和功能。由于集成度的差异，该通信装置1400可以包括如图14所示的部件中的一个或多个。如图14所示的部件可以包括：至少一个处理器1401、存储器1402、收发器1403以及通信总线1404。其中，处理器，收发器，存储器等通过总线连接。本申请实施例不限定上述部件之间的具体连接介质。
下面结合图14对该通信装置1400的各个构成部件进行具体的介绍：
处理器1401是通信装置1400的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器1401是一个中央处理器(central processing unit，CPU)，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。其中，处理器1401可以通过运行或执行存储在存储器1402内的软件程序，以及调用存储在存储器1402内的数据，执行通信设备的各种功能。在具体的实现中，作为一种实施例，处理器1401可以包括一个或多个CPU，例如图14中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置1400可以包括多个处理器，例如图14中所示的处理器1401和处理器1405。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个通信设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器1402可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储通信设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储通信设备，也可以是电可擦可编程只读存储器 (Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储通信设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1402可以是独立存在，通过通信总线1404与处理器1401相连接。存储器1402也可以和处理器1401集成在一起。其中，该存储器1402用于存储执行本申请方案的软件程序，并由处理器1401来控制执行。
收发器1403，用于与其他设备(例如第二多链路设备)之间的通信。当然，收发器1403还可以用于与通信网络通信，通信网络例如为以太网，无线接入网(radio access network，RAN)，无线局域网等。收发器1403可以包括接收单元实现接收功能，以及发送单元实现发送功能。
通信总线1404，可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部通信设备互连(Peripheral Component，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
一个示例中，该通信装置1400可以为一个整机的设备，该通信装置可包括：处理器1401，存储器1402以及收发器1403以及通信总线1404。可选的，还可以包括其他部件，比如显示屏、用户界面或信号检测器等。可选的，该通信装置1400为第一多链路设备，可以用于实现前述实施例中涉及第一多链路设备的方法和功能。例如，存储器中存储指令，当处理器调用该指令时，实现上述方法和功能，比如，处理器用于生成信令或帧，收发器用于发送信令或帧。例如，处理器用于执行步骤S141或S201等，收发器用于执行步骤S142，S202或S207等。
另一个示例中，该通信装置1400可以为第一多链路设备中的芯片系统或处理系统，使得安装该芯片系统或处理系统的设备实现前述实施例中的方法和功能。那么该通信装置1400可以包括如图14所示的部分部件，比如通信装置1400包括处理器，该处理器可与存储器耦合，调用存储器中的指令并执行，从而配置安装该芯片系统或处理系统的设备实现前述实施例中的方法和功能。可选的，该存储器可以是芯片系统或处理系统中的一个部件，也可以是芯片系统或处理系统外耦合链接的一个部件。一个示例中，该芯片系统或处理系统安装于第一多链路设备中，可以使得第一多链路设备实现前述实施例中对应的方法和功能。
该芯片系统或处理系统可以支持802.11系列协议进行通信，比如支持802.11be,802.11ax，802.11ac等等。该芯片系统可以安装于各种支持WLAN传输的场景中的设备中，WLAN传输场景中的设备已在本申请说明书中介绍，此处不赘述。
本申请实施例可以根据上述方法示例对第一多链路设备或第二多链路设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，参见图15，图15是本申请实施例提供的通信装置的又一结构示意图。如图15所示，该通信装置1500可以为多链路设备中的芯片或处理系统，该通信装置1500可以执行上述方法实施例中第一多链路设备的操作。该通信装置1500包括：处理单元1501。
一个示例中，通信装置1500为第一多链路设备中的非接入点站点。
其中，处理单元1501可以用于对通信装置1500的动作进行控制管理。例如，在第一时间段内对第二链路进行CCA检测。可选的，若通信装置1500包括存储单元，则处理单元1501还可以执行存储在存储单元中的程序或指令，以使得通信装置1500实现上述任意一个实施例所涉及的方法和功能。
示例性的，上述处理单元1501可以用于执行例如图8中的步骤801，或图8中的步骤801和/或用于本文所描述的技术的其它过程。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
示例性的，该通信装置1500可以为图14所示的通信装置，处理单元1501可以为图14中的处理器1401。另外，该通信装置1500可以包括收发单元，收发单元可以为图14中的收发器1403。可选的，该通信装置1500还可以包括存储器，该存储器用于存储通信装置1500执行上文所提供的任意一个多链路设备间的信道竞争方法所对应的程序代码和数据。上述图14涉及的各部件的所有相关内容的描述均可以援引到该通信装置1500对应部件的功能描述，在此不再赘述。
示例性的，该通信装置1500还可以为芯片或处理器，其中的处理单元1501为芯片或处理器中的处理电路，收发单元可以为芯片或处理器中的输入/输出电路，输入/输出电路为芯片或处理器与其他耦合部件相互通信或交互数据的接口，可确保信令或数据信息或程序指令被输入到芯片或处理器中进行处理，且将处理后的数据或信令输出给其他耦合的部件，并控制安装该芯片或处理器的第一多链路设备实现功能。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序代码，当上述处理器执行该计算机程序代码时，电子设备执行图8、图11中任意一个实施例的方法。
本申请实施例还提供了一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行图8、图11中任意一个实施例的方法。
本申请实施例还提供了一种通信装置，该装置可以以芯片的产品形态存在，该装置的结构中包括处理器和接口电路，该处理器用于通过接口电路与其它装置通信，使得该装置执行上述图8、图11中任意一个实施例中的方法。
本申请实施例还提供了一种通信系统，包括第一多链路设备和第二多链路设备，该第一多链路设备和第二多链路设备可以执行上述图8、图11中任意一个实施例中的方法。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的 组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机可读存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (17)

  1. 一种信道竞争方法，其特征在于，所述方法包括：
    在第一链路上数据传输完成后或在所述第一链路上接收到所述数据对应的确认块后，第一多链路设备的第一非接入点站点在第一时间段内对第二链路进行空闲信道评估CCA检测，所述第一时间段对应的开始时刻与所述第一链路上所述数据传输完成的时刻相同；
    当对所述第二链路的所述CCA检测不通过时，所述第一非接入点站点根据第二时间段，在所述第二链路上进行信道竞争。
  2. 根据权利要求1所述的方法，其特征在于，所述CCA阈值为-82dbm，-72dbm或者-62dbm。
  3. 根据权利要求1或者2所述的方法，其特征在于，所述第二时间段的起始时刻是所述CCA检测不通过转变为CCA检测通过的时刻。
  4. 根据权利要求1-3任意一项所述的方法，其特征在于，所述根据第二时间段，在所述第二链路上进行信道竞争，包括：
    若所述第二时间段对应的结束时刻早于所述第一时间段对应的结束时刻，所述第一非接入点站点则在所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争。
  5. 根据权利要求1-4任意一项所述的方法，其特征在于，所述根据第二时间段，在所述第二链路上进行信道竞争，
    若所述第二时间段对应的结束时刻晚于所述第一时间段对应的结束时刻，所述第一非接入点站点则在所述第一时间段对应的结束时刻之后或所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争。
  6. 根据权利要求1-3任意一项所述的方法，其特征在于，所述根据第二时间段，在所述第二链路上进行信道竞争，包括：
    当对所述第二链路的所述CCA检测不通过并且错过物理层数据单元PPDU的包头时，从所述CCA检测不通过转变为CCA检测通过的时刻起，在所述第二时间段之后在所述第二链路上开始进行信道竞争。
  7. 根据权利要求1-6任意一项所述的方法，其特征在于，所述第二时间段为经扩展的帧间间隔EIFS时间。
  8. 一种通信装置，其特征在于，所述通信装置为第一多链路设备中的第一非接入点站点，包括：
    处理单元，用于在第一链路上数据传输完成后或在所述第一链路上接收到所述数据对应的确认块后，在第一时间段内对第二链路进行空闲信道评估CCA检测，所述第一时间段对应的开始时刻与所述第一链路上所述数据传输完成的时刻相同；
    所述处理单元，还用于当对所述第二链路的所述CCA检测不通过时，根据第二时间段，在所述第二链路上进行信道竞争。
  9. 根据权利要求8所述的装置，其特征在于，所述CCA阈值为-82dbm，-72dbm或者-62dbm。
  10. 根据权利要求8或者9所述的装置，其特征在于，所述第二时间段的起始时刻是所述CCA检测不通过转变为CCA检测通过的时刻。
  11. 根据权利要求8-10任意一项所述的装置，其特征在于，在根据第二时间段，在所述第二链路上进行信道竞争时，
    若所述第二时间段对应的结束时刻早于所述第一时间段对应的结束时刻，所述处理单元，用于在所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争。
  12. 根据权利要求8-10任意一项所述的装置，其特征在于，所述根据第二时间段，在所述第二链路上进行信道竞争，
    若所述第二时间段对应的结束时刻晚于所述第一时间段对应的结束时刻，所述处理单元，用于在所述第一时间段对应的结束时刻之后或所述第二时间段对应的结束时刻之后在所述第二链路上进行信道竞争。
  13. 根据权利要求8-10任意一项所述的装置，其特征在于，所述根据第二时间段，在所述第二链路上进行信道竞争，包括：
    当对所述第二链路的所述CCA检测不通过并且错过物理层数据单元PPDU的包头时，从所述CCA检测不通过转变为CCA检测通过的时刻起，在所述第二时间段之后在所述第二链路上开始进行信道竞争。
  14. 根据权利要求8-13任意一项所述的装置，其特征在于，所述第二时间段为经扩展的帧间间隔EIFS时间。
  15. 一种通信装置，包括：处理器和存储器，所述存储器用于存储指令，当所述处理器运行所述指令时，以使得所述通信装置执行权利要求1所述的方法。
  16. 一种无线通信系统，其特征在于，包括第一多链路设备，其中：
    所述第一多链路设备包括权利要求8-14任一项所述的通信装置。
  17. 一种可读存储介质，其特征在于，所述可读存储介质中存储程序指令，当所述程序指令运行时，使得如权利要求1-7任一项所述的方法被执行。
PCT/CN2021/107596 2020-08-14 2021-07-21 一种信道竞争方法及相关装置 WO2022033283A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
AU2021323746A AU2021323746B2 (en) 2020-08-14 2021-07-21 Channel contention method and related apparatus
JP2023510452A JP2023537151A (ja) 2020-08-14 2021-07-21 チャネル競合方法及び関連機器
EP21855336.0A EP4191902A4 (en) 2020-08-14 2021-07-21 CHANNEL CONFLICT METHOD AND APPARATUS
BR112023002705A BR112023002705A2 (pt) 2020-08-14 2021-07-21 Método de contenção de canal e aparelho relacionado
CN202180055788.4A CN116114296A (zh) 2020-08-14 2021-07-21 一种信道竞争方法及相关装置
MX2023001856A MX2023001856A (es) 2020-08-14 2021-07-21 Metodo de contencion de canal y aparato relacionado.
KR1020237008043A KR20230048390A (ko) 2020-08-14 2021-07-21 채널 경쟁 방법 및 관련 장치
CA3189314A CA3189314A1 (en) 2020-08-14 2021-07-21 Channel contention method and related apparatus
US18/168,048 US20230199850A1 (en) 2020-08-14 2023-02-13 Channel Contention Method and Related Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010820609.9A CN114080050A (zh) 2020-08-14 2020-08-14 一种信道竞争方法及相关装置
CN202010820609.9 2020-08-14

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/168,048 Continuation US20230199850A1 (en) 2020-08-14 2023-02-13 Channel Contention Method and Related Apparatus

Publications (1)

Publication Number Publication Date
WO2022033283A1 true WO2022033283A1 (zh) 2022-02-17

Family

ID=80247655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/107596 WO2022033283A1 (zh) 2020-08-14 2021-07-21 一种信道竞争方法及相关装置

Country Status (10)

Country Link
US (1) US20230199850A1 (zh)
EP (1) EP4191902A4 (zh)
JP (1) JP2023537151A (zh)
KR (1) KR20230048390A (zh)
CN (4) CN116367349A (zh)
AU (1) AU2021323746B2 (zh)
BR (1) BR112023002705A2 (zh)
CA (1) CA3189314A1 (zh)
MX (1) MX2023001856A (zh)
WO (1) WO2022033283A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220124857A1 (en) * 2020-10-21 2022-04-21 Qualcomm Incorporated Direct link communications in multi-link operations
CN116709287B (zh) * 2022-03-01 2024-02-20 华为技术有限公司 一种通信方法和通信装置
CN117042046A (zh) * 2022-04-29 2023-11-10 华为技术有限公司 一种信道竞争方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019050707A1 (en) * 2017-09-11 2019-03-14 Qualcomm Incorporated FREE CHANNEL EVALUATION SETTING OF INTRA-BAND LINK AGGREGATION
WO2020050541A1 (ko) * 2018-09-05 2020-03-12 엘지전자 주식회사 무선랜 시스템에서 프레임을 송수신하는 방법 및 장치
CN110972256A (zh) * 2019-12-11 2020-04-07 展讯通信（上海）有限公司 多链路同步传输、接收方法及装置、存储介质、终端
CN111147165A (zh) * 2020-01-20 2020-05-12 展讯通信（上海）有限公司 无线信道启动方法及装置、存储介质、终端

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010085069A2 (en) * 2009-01-20 2010-07-29 Lg Electronics Inc. Method and apparatus for channel access in contention-based communication system and station
US9742544B2 (en) * 2014-08-08 2017-08-22 Newracom, Inc. Dynamic inter-frame space processing in high efficiency wireless LAN
CN106455117B (zh) * 2015-08-07 2021-07-23 中兴通讯股份有限公司 一种竞争接入方法和装置
WO2017074070A1 (ko) * 2015-10-27 2017-05-04 엘지전자 주식회사 무선랜 시스템에서 다중 사용자의 상향링크 프레임의 전송을 위한 방법
WO2018117723A1 (ko) * 2016-12-22 2018-06-28 엘지전자 주식회사 무선랜 시스템에서 공간 재사용을 기반으로 프레임을 송신하는 방법 및 이를 이용한 무선 단말
EP3753366A4 (en) * 2018-02-16 2021-11-17 Telefonaktiebolaget LM Ericsson (publ) COMMUNICATION NODE AND PROCEDURES EXECUTED WITH IT
WO2020050680A1 (ko) * 2018-09-07 2020-03-12 엘지전자 주식회사 무선랜 시스템에서 피드백 프레임을 수신하는 방법 및 장치
US11102824B2 (en) * 2018-11-05 2021-08-24 Hyundai Motor Company Method and apparatus for avoiding signal collision by enhanced distributed coordination access in wireless local access network
WO2020101807A2 (en) * 2019-09-26 2020-05-22 Futurewei Technologies, Inc. Methods and apparatus aggregating multiple wireless communications channels for flexible full-duplex communications
US20210266965A1 (en) * 2020-02-25 2021-08-26 Qualcomm Incorporated Techniques for non-simultaneous transmit and receive station operation during synchronization procedures

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019050707A1 (en) * 2017-09-11 2019-03-14 Qualcomm Incorporated FREE CHANNEL EVALUATION SETTING OF INTRA-BAND LINK AGGREGATION
WO2020050541A1 (ko) * 2018-09-05 2020-03-12 엘지전자 주식회사 무선랜 시스템에서 프레임을 송수신하는 방법 및 장치
CN110972256A (zh) * 2019-12-11 2020-04-07 展讯通信（上海）有限公司 多链路同步传输、接收方法及装置、存储介质、终端
CN111147165A (zh) * 2020-01-20 2020-05-12 展讯通信（上海）有限公司 无线信道启动方法及装置、存储介质、终端

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GARCIA RODRIGUEZ ADRIAN, SLIDE NOKIA, GARCIA-RODRIGUEZ ADRIAN, NOKIA, ALANEN OLLI, MIKA NOKIA, LOPEZ DAVID, GALATI LORENZO: "Multi-Link for Low Latency Name Affiliations Address Phone email", IEEE, 10 January 2020 (2020-01-10), XP055900162 *
See also references of EP4191902A4

Also Published As

Publication number Publication date
AU2021323746B2 (en) 2024-05-02
JP2023537151A (ja) 2023-08-30
CN114080050A (zh) 2022-02-22
KR20230048390A (ko) 2023-04-11
CN116114296A (zh) 2023-05-12
EP4191902A1 (en) 2023-06-07
EP4191902A4 (en) 2023-12-20
CA3189314A1 (en) 2022-02-17
CN116367348A (zh) 2023-06-30
AU2021323746A1 (en) 2023-03-23
BR112023002705A2 (pt) 2023-05-02
US20230199850A1 (en) 2023-06-22
MX2023001856A (es) 2023-05-18
CN116367349A (zh) 2023-06-30

Similar Documents

Publication Publication Date Title
KR102308351B1 (ko) 액세스 방법 및 장치
WO2022033283A1 (zh) 一种信道竞争方法及相关装置
CN112566272A (zh) 多链路操作信道接入的方法
CN113676298B (zh) 多链路通信方法及相关装置
US20140204872A1 (en) Information transmission method and apparatus
WO2014061926A1 (en) Method and apparatus for channel access in wireless lan system
WO2022057901A1 (zh) 无线局域网中的信道接入方法及相关装置
US20210337596A1 (en) Heterogeneous network allocation vector (nav)-based communication in wireless lan system
WO2014183401A1 (zh) 信道接入方法和接入设备
US20230209600A1 (en) Channel Access Method for Multi-Link Device and Related Apparatus
WO2021254234A1 (zh) 信道竞争方法及相关装置
JP2024014880A (ja) マルチリンクデバイスのためのチャネルアクセス方法、および関連装置
CN112788791A (zh) 多链路信道存取方法
WO2023134581A1 (zh) 信道竞争方法及装置
CN107211453B (zh) 一种信道接入方法及信道接入装置
CN117796020A (zh) 用于支持多链路的通信系统中的nstr通信的方法和装置
KR20220050365A (ko) 비면허 대역을 지원하는 무선 통신 시스템에서의 통신 방법 및 장치

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: 21855336

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023510452

Country of ref document: JP

Kind code of ref document: A

Ref document number: 3189314

Country of ref document: CA

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023002705

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2021855336

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021855336

Country of ref document: EP

Effective date: 20230302

ENP Entry into the national phase

Ref document number: 20237008043

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021323746

Country of ref document: AU

Date of ref document: 20210721

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112023002705

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230214