Millimeter-wave-based multi-link communication methods, and apparatuses and devices
By establishing a mapping relationship between anchor channels and millimeter-wave channels in multi-link devices, the problem of cooperation between Sub-7 GHz and millimeter-wave links is solved, improving the utilization and management efficiency of millimeter-wave channels.
Patent Information
- Application Number
- PCT/CN2025/094662
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-13
- Publication Date
- 2026-11-19
AI Technical Summary
In multi-link devices that integrate Sub-7 GHz and millimeter wave (mmWave) bands, how can we more flexibly coordinate the cooperation between Sub-7 links and millimeter wave links to improve the utilization of millimeter wave channels?
By establishing a mapping relationship between anchor channels and millimeter-wave channels between two MLD sites, the anchor channels are used to manage collaborative communication of one or more millimeter-wave channels.
It improves the utilization rate of millimeter-wave channels and enables more efficient channel management and resource allocation.
Smart Images

Figure CN2025094662_19112026_PF_FP_ABST
Abstract
Description
Millimeter-wave-based multi-link communication methods, devices, and equipment Technical Field
[0001] This application relates to the field of communications, and in particular to a multi-link communication method, apparatus and device based on millimeter waves. Background Technology
[0002] In Wireless Fidelity (Wi-Fi), Integrated mmWave (IMMW) technology integrates the Sub-7 GHz band and the mmWave band to significantly enhance Wi-Fi network capacity, increase throughput, reduce latency, and allow for support by a single baseband processor.
[0003] In related technologies, for millimeter-wave links, Sub-7 GHz links allocate Service Periods (SPs) for frame switching. These frame exchanges occur between millimeter-wave sites, for example, between a millimeter-wave Access Point (AP) and a millimeter-wave site (STA). One approach is to allocate a dedicated SP for the Sub-7 GHz link, that is, an SP dedicated to a pair of STAs, with each STA having dedicated access rights to the millimeter-wave channel. However, a dedicated SP can only be used for a pair of STAs, therefore, the utilization rate of the millimeter-wave channel is not very high.
[0004] In multi-link devices (MLDs) that integrate Sub-7 GHz and mmWave, a problem that needs to be solved is how to more flexibly coordinate the Sub-7 link and the millimeter-wave link to improve the utilization of the millimeter-wave channel. Summary of the Invention
[0005] This application provides a millimeter-wave-based multi-link communication method, apparatus, and device for achieving cooperation between Sub-7 links and millimeter-wave links. The technical solution includes at least:
[0006] According to one aspect of the embodiments of this application, a millimeter-wave-based multi-link communication method is provided, the method being executed by a first MLD, the method comprising:
[0007] Send and / or receive at least one frame, the at least one frame being used to determine the mapping relationship between the anchor channel and the millimeter-wave channel;
[0008] The anchor point channel includes an anchor point link or an anchor point channel, and the millimeter wave channel includes a millimeter wave link or a millimeter wave channel.
[0009] According to one aspect of the embodiments of this application, a millimeter-wave-based multi-link communication method is provided, the method being executed by a second MLD, the method comprising:
[0010] Receive and / or transmit at least one frame, said at least one frame being used to determine the mapping relationship between the anchor channel and the millimeter-wave channel;
[0011] The anchor point channel includes an anchor point link or an anchor point channel, and the millimeter wave channel includes a millimeter wave link or a millimeter wave channel.
[0012] According to one aspect of the embodiments of this application, a first MLD device is provided, the device comprising:
[0013] A first communication module is configured to send and / or receive at least one frame, wherein the at least one frame is used to determine the mapping relationship between the anchor channel and the millimeter-wave channel;
[0014] The anchor point channel includes an anchor point link or an anchor point channel, and the millimeter wave channel includes a millimeter wave link or a millimeter wave channel.
[0015] According to one aspect of the embodiments of this application, a second MLD device is provided, the device comprising:
[0016] A first communication module is configured to receive and / or transmit at least one frame, wherein the at least one frame is used to determine the mapping relationship between the anchor channel and the millimeter-wave channel;
[0017] The anchor point channel includes an anchor point link or an anchor point channel, and the millimeter wave channel includes a millimeter wave link or a millimeter wave channel.
[0018] According to one aspect of the embodiments of this application, a first MLD is provided, the first MLD comprising:
[0019] Processor; transceiver connected to the processor; memory for storing executable instructions of the processor;
[0020] The memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the first MLD executes the millimeter-wave-based multi-link communication method as described above.
[0021] According to one aspect of the embodiments of this application, a second MLD is provided, the second MLD comprising:
[0022] Processor; transceiver connected to the processor; memory for storing executable instructions of the processor;
[0023] The memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the second MLD executes the millimeter-wave-based multi-link communication method as described above.
[0024] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein at least one program is stored in the computer-readable storage medium, the at least one program being loaded and executed by a processor to implement the millimeter-wave-based multi-link communication method as described in any of the above aspects.
[0025] According to one aspect of the embodiments of this application, a chip is provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is run on a communication device, implements the millimeter-wave-based multi-link communication method as described in any of the above aspects.
[0026] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium; a processor of a communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to implement the millimeter-wave-based multi-link communication method as described in any of the above aspects.
[0027] According to one aspect of the embodiments of this application, a computer program is provided, which is executed by a processor of a communication device to implement the millimeter-wave-based multi-link communication method as described in any of the above aspects.
[0028] The technical solutions provided in this application have at least the following beneficial effects:
[0029] By establishing a mapping relationship between anchor channels (such as Sub-7 channels) and millimeter-wave channels between two MLD sites, collaborative communication of one or more millimeter-wave channels can be managed based on anchor channels, thereby improving the utilization rate of millimeter-wave channels. Attached Figure Description
[0030] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0031] Figure 1 shows a schematic diagram of a Wi-Fi system provided by an exemplary embodiment of this application;
[0032] Figure 2 shows a flowchart of a millimeter-wave-based multi-link communication method provided in an exemplary embodiment of this application;
[0033] Figure 3 shows a flowchart of a millimeter-wave-based multi-link communication method provided in an exemplary embodiment of this application;
[0034] Figure 4 shows a flowchart of a millimeter-wave-based multi-link communication method provided in an exemplary embodiment of this application;
[0035] Figure 5 shows a flowchart of a millimeter-wave-based multi-link communication method provided in an exemplary embodiment of this application;
[0036] Figure 6 shows a flowchart illustrating a millimeter-wave-based multi-link communication method in another exemplary embodiment of this application;
[0037] Figure 7 illustrates an exemplary format diagram of the mapping relationship field provided in some exemplary embodiments of this application;
[0038] Figure 8 shows a schematic diagram of an exemplary mapping element provided by some exemplary embodiments of this application;
[0039] Figure 9 illustrates the format of the anchor link to millimeter-wave link mapping relationship field provided in some exemplary embodiments of this application;
[0040] Figure 10 illustrates a frame format diagram of an ICF frame provided by some exemplary embodiments of this application;
[0041] Figure 11 illustrates a frame format diagram of another ICF frame provided by some exemplary embodiments of this application;
[0042] Figure 12 illustrates a frame format diagram of an ICR frame provided by some exemplary embodiments of this application;
[0043] Figure 13 illustrates a schematic diagram of an AP MLD transmitting management frames on multiple anchor channels, provided by some exemplary embodiments of this application;
[0044] Figure 14 illustrates a schematic diagram of an AP MLD transmitting management frames on a single anchor channel, provided by some exemplary embodiments of this application;
[0045] Figure 15 illustrates a schematic diagram of accessing a millimeter-wave channel via anchor channel competition and ICF / ICR switching, provided by some exemplary embodiments of this application;
[0046] Figure 16 illustrates a schematic diagram of two MLDs accessing the same millimeter-wave channel through different anchor point channels, provided in some exemplary embodiments of this application;
[0047] Figure 17 illustrates a schematic diagram of ICR frames indicating millimeter-wave channel idle time provided by some exemplary embodiments of this application;
[0048] Figure 18 illustrates a schematic diagram of the AP MLD indicating the station's waiting time to access the millimeter-wave channel via an ICR frame, provided by some exemplary embodiments of this application.
[0049] Figure 19 illustrates a schematic diagram of ICF frames indicating millimeter-wave channel transmission time and duration provided in some exemplary embodiments of this application;
[0050] Figure 20 shows a timing diagram of MLD performing channel detection before millimeter-wave channel access, provided by some exemplary embodiments of this application;
[0051] Figure 21 shows a timing diagram of MLD performing channel detection before millimeter-wave channel access, provided by some exemplary embodiments of this application;
[0052] Figure 22 shows a timing diagram of MLD performing channel detection before millimeter-wave channel access, provided by some exemplary embodiments of this application;
[0053] Figure 23 illustrates a schematic diagram of an MLD simultaneously accessing multiple millimeter-wave channels and transmitting data, provided by some exemplary embodiments of this application.
[0054] Figure 24 illustrates a schematic diagram of a single millimeter-wave channel for transmission provided by some exemplary embodiments of this application;
[0055] Figure 25 illustrates a schematic diagram of an MLD simultaneously accessing multiple millimeter-wave channels and allocating them to different receiving stations for transmission, provided by some exemplary embodiments of this application.
[0056] Figure 26 shows a block diagram of a first MLD device provided in an exemplary embodiment of this application;
[0057] Figure 27 shows a block diagram of a second MLD device provided in an exemplary embodiment of this application;
[0058] Figure 28 shows a schematic diagram of the structure of a wireless communication device provided in an exemplary embodiment of this application. Detailed Implementation
[0059] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0060] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.
[0061] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when," "when," or "in response to determination." In this specification, when expressing the meaning of Boolean values, '0' is expressed as 'first meaning' and '1' as 'second meaning'. Without loss of generality, those skilled in the art will understand that the meanings they represent can be interchanged, i.e., '1' represents 'first meaning' and '0' represents 'second meaning'.
[0062] 1. The Institute of Electrical and Electronics Engineers (IEEE) 802.11ad is a wireless network standard, also known as Wireless Gigabit (WiGig) technology. It uses the 60 GHz band, which has more spectrum available compared to the 2.4 GHz and 5 GHz bands. This allows it to support faster data transmission rates of up to 7 Gbps by using low-power modulation schemes and wider channels, making it ideal for indoor connectivity to support demanding multimedia applications, including video.
[0063] Key features of the Wireless Gigabit / IEEE 802.11ad (WiGig / IEEE 802.11ad) specification include: maximizing performance; minimizing implementation complexity and cost; compatibility with Wireless Fidelity (Wi-Fi) technology; and providing advanced security protection. Key functions include:
[0064] 1) Supports data transfer rates up to 7Gbps;
[0065] 2) Its unique design supports low-power handheld devices such as mobile phones as well as high-performance devices such as computers, and it also adopts advanced power management technology;
[0066] 3) The device can transparently switch between 802.11 networks operating on any frequency band (including 2.4GHz, 5GHz and 60GHz);
[0067] 4) Supports beamforming, which maximizes signal strength and enables good communication at distances of up to 10 meters;
[0068] 5) Use the Galois / Counter Mode in the Advanced Encryption Standard (AES) encryption algorithm for security protection;
[0069] 6) Supports high-performance wireless implementations of High Definition Multimedia Interface (HDMI), DisplayPort, Universal Serial Bus (USB), and Peripheral Component Interconnect Express (PCIe).
[0070] IEEE 802.11ay is part of the IEEE 802.11 series of Wireless Local Area Network (WLAN) communication protocols, operating in the 60 GHz band. It is a successor to IEEE 802.11ad. Its goal is to provide higher data transmission rates and longer transmission distances, while addressing issues such as insufficient wall penetration capability of IEEE 802.11ad.
[0071] IEEE 802.11ay offers extremely high data transmission rates and long transmission distances, making it suitable for various high-speed data transmission scenarios. The target rate for IEEE 802.11ay is up to 176 Gbps. Compared to IEEE 802.11ad, 802.11ay significantly improves transmission distance, reaching 300m-500m. Its technological improvements include Multiple Input Multiple Output (MIMO), channel bonding, beamforming, and dual-polarized antennas, further enhancing performance and efficiency.
[0072] 2. The goal of Integrated mmWave (IMMW) is to integrate Sub-7 GHz and millimeter wave (mmWave) bands to significantly enhance the capacity of Wireless Fidelity (Wi-Fi) networks, increase throughput, reduce latency, and allow a single baseband processor to support 2.4 / 5 / 6 / 60 GHz communication.
[0073] The definition of Integrated mmWave (IMMW) includes:
[0074] 1) The physical layer of millimeter wave (mmWave) should reuse the IEEE 802.11ax / be / bn technology for sub-7 GHz as much as possible to reduce complexity and cost.
[0075] 2) Integrate millimeter-wave (mmWave) links into a multi-link operation (MLO) architecture to reduce connection loss / increase reliability and perform load balancing to reduce latency and increase throughput.
[0076] 3) Millimeter wave (mmWave) operation requires a 2.4 / 5 / 6 GHz connection. Integrated mmWave (IMMW) aims to achieve high-speed short-range communication through the assistance or coordination of the Sub-7 GHz band.
[0077] 3. Channel Access Mechanism: In the Institute of Electrical and Electronics Engineers (IEEE) 802.11 protocol, the basic channel access protocol is the Distributed Coordination Function (DCF). Through the Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) mechanism, it allows different compatible station (STA) devices to share the channel, reducing the probability of collisions.
[0078] The Distributed Coordination Function (DCF) mainly comprises four core mechanisms:
[0079] 1) Carrier sensing mechanism
[0080] The carrier sensing mechanism is divided into physical carrier sensing and virtual carrier sensing. If the result of either sensing indicates that the channel is busy, then the channel is busy.
[0081] Physical carrier sensing employs three channel idle detection methods: energy detection, carrier detection, and a hybrid energy-carrier detection, collectively known as Clear Channel Assessment (CCA). Energy detection assesses the power of the received signal; if the received power exceeds the physical layer's threshold ED_threshold, the channel is considered occupied. Carrier detection detects the preamble portion of the signal in the channel and determines channel occupancy based on the detection result.
[0082] The virtual carrier sensing mechanism is provided by Media Access Control (MAC). The Institute of Electrical and Electronics Engineers (IEEE) standard 802.11 uses a Network Allocation Vector (NAV) to implement virtual sensing. The Dur / ID field in the MAC frame stores the "duration". For a station (STA) receiving this information, it determines the duration the channel will be occupied and accordingly adjusts its own transmission delay. The Network Allocation Vector (NAV) is a timer that defines how long the channel will remain occupied. It starts with the duration of the last received frame and counts down to 0. Each listening station (STA) uses the Network Allocation Vector (NAV) timer. During data communication, a station occupying the channel informs other stations (STAs) how much longer it needs to use the channel by using the duration field in the frame. Stations (STAs) not occupying the channel update their own Network Allocation Vector (NAV) value by comparing it with the duration value in the received packets. The channel is considered idle only when the Network Allocation Vector (NAV) value is 0 and physical carrier sensing indicates that the channel is idle.
[0083] 2) Inter-frame spacing mechanism
[0084] To minimize collisions, the Institute of Electrical and Electronics Engineers (IEEE) standard 802.11 mandates that all stations must wait a short period (while listening) after completing a transmission before sending the next frame. This period is commonly known as the interframe space (IFS). The length of the IFS depends on the type of frame the station is transmitting. Higher-priority frames require a shorter wait and thus receive priority for transmission, while lower-priority frames must wait a longer time. If a lower-priority frame has not yet been transmitted while other higher-priority frames have already been sent to the media, the media becomes busy, and the lower-priority frame's transmission is delayed. This reduces the chance of collisions.
[0085] Interframe space (IFS) is used to prioritize access to the radio medium. The priorities are determined by the length of the IFS; shorter IFS intervals indicate higher priorities. The IFS intervals are listed below from shortest to longest:
[0086] a. Short Interframe Space (SIFS): This is the shortest time interval used to separate frames that require an immediate response, such as control frames (RTS / CTS / ACK). Using the shortest interval between two transmissions in frame exchange sequence prevents other stations waiting for the medium from attempting to use it.
[0087] b. Priority Interframe Space (PIFS): This is an interframe space used for centralized coordination functions and can only be used by stations operating in Point Coordination Function Mode (PCF).
[0088] c. Distributed Interframe Space (DIFS): Can only be used by stations operating in Distributed Coordination Function (DCF) mode.
[0089] d. Extended Interframe Space (EIFS): If an error occurs in the previous frame, the transmitting node must delay sending the next frame by the extended interframe space (EIFS) period instead of the distributed coordinated interframe space (DIFS) period.
[0090] 3) Random Back Off (BO) Mechanism
[0091] The Institute of Electrical and Electronics Engineers (IEEE) uses a binary exponential backoff method in 802.11 to address the backoff time required when a node fails to transmit or encounters a collision. When the Media Access Control (MAC) layer has frames to transmit, after both physical carrier sense (PTS) and virtual carrier sense (VCS) indicate that the channel is idle, if the backoff window count is not zero, the count continues to decrease in units of slot time; otherwise, a random backoff window is generated for backoff. The node selects a random backoff count value based on a random number within the contention window. Once the backoff time is selected, it is equivalent to setting a backoff timer. The contention window value is a parameter between the minimum contention window (CWmin) and the maximum contention window (CWmax) of the physical characteristic value, allowing the node to select the range of random backoff count values. The station continuously listens to the channel within the slot time. If the channel is detected to be idle, the backoff timer continues to count down by one; if the channel is detected to be busy, the remaining time of the backoff timer is frozen, and the system waits again for the channel to become idle and for the time-distributed coordinating interframe space (DIFS) to pass before resuming the countdown from the remaining time. When the backoff timer reaches zero, the entire data frame is transmitted.
[0092] 4) Request to send / clear send handshake mechanism
[0093] Request To Send / Clear To Send (RTS / CTS) is a mechanism adopted by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 protocol to reduce collisions caused by the hidden node problem. The basic idea of RTS / CTS is to reserve a channel using short control packets. If a sending station wants to send a message to a receiving station, it first sends a Request To Send (RTS) control frame. Stations near the sending station, upon receiving this Request To Send (RTS), set their Network Allocation Vector (NAV) value according to the duration field. Upon receiving the Request To Send (RTS), the receiving station replies with a Clear To Send (CTS) control frame. After receiving a Clear To Send (CTS) message, stations surrounding the receiving station set their own Network Allocation Vector (NAV) value based on the duration field. Stations with a non-zero NAV value cannot perform channel idle monitoring, thus avoiding transmission conflicts with both the sending and receiving stations.
[0094] Figure 1 illustrates a schematic diagram of a Wi-Fi system provided in an exemplary embodiment of this application. This Wi-Fi system includes: terminal devices and terminal devices, or terminal devices and network devices, or AP (Access Point) and STA (Station), or AP MLD and non-AP MLD; this application does not limit the specific configuration. This application uses an example of a Wi-Fi system including AP 101 and non-AP STA 102 for illustration.
[0095] In some scenarios, AP can also be called AP STA, meaning that in a sense, AP is also a type of STA.
[0096] In some embodiments, the STA may include AP STA and non-AP STA.
[0097] Communication in a Wi-Fi system can be between an AP and a non-AP STA, between two non-AP STAs, or between a STA and a peer STA. A peer STA can refer to a device that communicates with the STA from the other end. For example, a peer STA may be an AP or a non-AP STA.
[0098] An access point (AP) acts as a bridge connecting wired and wireless networks. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet. AP devices can be terminal devices or network devices with Wi-Fi chips.
[0099] It should be understood that the role of a STA in a communication system is not absolute. For example, in some scenarios, when a mobile phone connects to a router, it is a non-AP STA; when the mobile phone acts as a hotspot for other mobile phones, it plays the role of an AP.
[0100] AP and non-AP STA can be devices used in vehicle networking, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.
[0101] In some embodiments, non-AP STAs can support various current and future 802.11 family WLAN standards, including 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. Non-AP STAs can also be used in network environments supporting next-generation WLAN systems. Next-generation WLAN systems are WLAN systems evolved from 802.11ax systems and are backward compatible with 802.11ax systems. Next-generation Wi-Fi communication refers to any new generation of Wi-Fi communication based on the IEEE 802.11be standard after Wi-Fi 7, such as Extremely High Throughput (EHT) communication and UHR communication. For example, a non-AP STA is a UHR STA.
[0102] In some embodiments, the AP can be a device that supports various current and future 802.11 family WLAN standards, including 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. The AP can also be used in network environments that support next-generation WLAN systems. Next-generation WLAN systems are WLAN systems evolved from 802.11ax systems and are backward compatible with 802.11ax systems. Next-generation Wi-Fi communication refers to any new generation of Wi-Fi communication based on the IEEE 802.11be standard and later, such as EHT communication and UHR communication. For example, the AP could be a UHR AP.
[0103] In this application embodiment, the STA can be a mobile phone, tablet, e-book reader, laptop, desktop computer, television, virtual reality (VR) device, augmented reality (AR) device, mixed reality (MR) device, extended reality (XR) device, baffle reality (BR) device, cinematic reality (CR) device, deceive reality (DR) device, wireless device in industrial control, set-top box, wireless device in self-driving, vehicle communication device, wireless device in remote medical care, wireless device in smart grid, wireless device in transportation safety, wireless device in smart city, or wireless device in smart home, wireless communication chip, application-specific integrated circuit (ASIC), or system on chip that supports WLAN / Wi-Fi technology. Chip, SoC, etc.
[0104] The Wi-Fi system in this application embodiment may support frequency bands including but not limited to: millimeter wave bands (such as 45GHz, 60GHz, etc., which belong to the frequency bands in the range of 30 to 300GHz) and Sub-7GHz bands (such as 2.4GHz, 5GHz, 6GHz, etc., which belong to the frequency bands in the range of 1 to 7.25GHz).
[0105] One or more links can exist between a STA and an AP.
[0106] In some embodiments, the STA and AP support multi-band communication, for example, communicating simultaneously on the 2.4 GHz, 5 GHz, 6 GHz and 45 GHz, 60 GHz bands, or simultaneously communicating on different channels within the same band or different channels in different bands, to improve communication throughput and / or reliability between devices. Such devices are commonly referred to as multi-band devices, or multi-link devices (MLDs), and sometimes also as multi-band entities or multi-link entities. A multi-link device can be an AP device or a non-AP STA device. If the multi-link device is an AP device, it contains one or more APs; if the multi-link device is a non-AP STA device, it contains one or more non-AP STAs.
[0107] A multi-link device, or AP, includes one or more APs, and a multi-link device, or Non-AP, includes one or more non-AP STAs. In the embodiments of the application, Non-APs may be referred to as STAs.
[0108] In some embodiments, STAs exist as one or more BSSs, which are collections of STAs that can successfully synchronize and communicate with each other. A BSS may or may not contain APs.
[0109] In some embodiments, an AP may include multiple APs, and a Non-AP may include multiple STAs. Multiple links may be formed between the APs in an AP and the STAs in a Non-AP, and the APs in an AP and the corresponding STAs in a Non-AP may communicate through the corresponding links.
[0110] In some embodiments, an AP is a device deployed in a WLAN / Wi-Fi system to provide wireless communication functionality to a STA. A STA can be: User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user device. A STA can also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication functionality, computing device, or other processing device connected to a wireless modem, in-vehicle device, or wearable device; however, this application embodiment does not limit the scope of the application.
[0111] In some embodiments, both the AP and the non-AP STA support the IEEE 802.11 standard, but are not limited to the IEEE 802.11 standard.
[0112] Figure 2 shows a flowchart of a millimeter-wave-based multi-link communication method provided in an exemplary embodiment of this application. This embodiment illustrates the method by way of execution by a first MLD. The method includes:
[0113] Step 210: Send and / or receive at least one frame, the at least one frame being used to determine the mapping relationship between the anchor channel and the millimeter wave channel.
[0114] Optionally, the first MLD is an AP MLD and the second MLD is a non-AP MLD; or, the first MLD is a non-AP MLD and the second MLD is an AP MLD. This embodiment illustrates the example with the first MLD being an AP MLD and the second MLD being a non-AP MLD.
[0115] Among them, the anchor channel includes the anchor link or the anchor channel, and the millimeter wave channel includes the millimeter wave link or the millimeter wave channel.
[0116] In some embodiments, the anchor channel is a Sub-7 channel, including a Sub-7 link or a Sub-7 channel. A millimeter-wave channel is also called an IMW channel, a millimeter-wave link is also called an IMW link, and a millimeter-wave channel is also called an IMW channel.
[0117] In some embodiments, the first MLD transmits and / or receives at least one frame on the anchor channel. That is, the first MLD and the second MLD transmit and / or receive at least one frame on the anchor channel. This at least one frame is used to determine the mapping relationship between the anchor channel and the millimeter-wave channel, or the at least one frame is used to indicate the mapping relationship between the anchor channel and the millimeter-wave channel, or the at least one frame is used to establish the mapping relationship between the anchor channel and the millimeter-wave channel, or the at least one frame is used to request the establishment of the mapping relationship between the anchor channel and the millimeter-wave channel, or the at least one frame is used to negotiate the mapping relationship between the anchor channel and the millimeter-wave channel.
[0118] In summary, the method provided in this embodiment can improve the utilization rate of millimeter-wave channels by establishing a mapping relationship between anchor channels (such as Sub-7 channels) and millimeter-wave channels between two MLD sites, thereby enabling the management of collaborative communication of one or more millimeter-wave channels based on anchor channels.
[0119] Figure 3 shows a flowchart of a millimeter-wave-based multi-link communication method provided in an exemplary embodiment of this application. This embodiment illustrates the method by way of execution by a second MLD. The method includes:
[0120] Step 310: Receive and / or transmit at least one frame, the at least one frame being used to determine the mapping relationship between the anchor channel and the millimeter wave channel.
[0121] Optionally, the first MLD is an AP MLD and the second MLD is a non-AP MLD; or, the first MLD is a non-AP MLD and the second MLD is an AP MLD. This embodiment illustrates the example with the first MLD being an AP MLD and the second MLD being a non-AP MLD.
[0122] Among them, the anchor point channel includes the anchor point link or anchor point channel, and the millimeter wave channel includes the millimeter wave link or millimeter wave channel.
[0123] In some embodiments, the anchor channel is a Sub-7 channel, including a Sub-7 link or a Sub-7 channel. A millimeter-wave channel is also called an IMW channel, a millimeter-wave link is also called an IMW link, and a millimeter-wave channel is also called an IMW channel.
[0124] In some embodiments, the second MLD receives and / or transmits at least one frame on the anchor channel. That is, the first MLD and the second MLD transmit and / or receive at least one frame on the anchor channel. This at least one frame is used to determine the mapping relationship between the anchor channel and the millimeter-wave channel, or to indicate the mapping relationship between the anchor channel and the millimeter-wave channel, or to establish the mapping relationship between the anchor channel and the millimeter-wave channel, or to request the establishment of the mapping relationship between the anchor channel and the millimeter-wave channel, or to negotiate the mapping relationship between the anchor channel and the millimeter-wave channel.
[0125] In summary, the method provided in this embodiment can improve the utilization rate of millimeter-wave channels by establishing a mapping relationship between anchor channels (such as Sub-7 channels) and millimeter-wave channels between two MLD sites, thereby enabling the management of collaborative communication of one or more millimeter-wave channels based on anchor channels.
[0126] Based on the embodiments shown in Figure 2 and / or Figure 3, some technical features are described below:
[0127] Mapping relationship type:
[0128] In some embodiments, the mapping relationship includes at least one of the following four types: mapping relationship between anchor link and millimeter wave link; mapping relationship between anchor channel and millimeter wave link; mapping relationship between anchor link and millimeter wave channel; and mapping relationship between anchor channel and millimeter wave channel.
[0129] For example, the first MLD can maintain a mapping table that records the correspondence between different types of anchor channels and millimeter-wave channels.
[0130] Number of mapping relationships:
[0131] In some embodiments, the mapping relationships include: a mapping relationship between an anchor channel and multiple millimeter-wave channels; a mapping relationship between multiple anchor channels and a single millimeter-wave channel; and a mapping relationship between an anchor channel and a single millimeter-wave channel.
[0132] For example, one anchor channel can correspond to multiple millimeter-wave channels, used to control the resource allocation of multiple millimeter-wave channels simultaneously; or multiple anchor channels can correspond to one millimeter-wave channel, used to improve the management reliability of millimeter-wave channels.
[0133] Anchor point channel management functions:
[0134] In some embodiments, the anchor channel is used to publish management frames, which are used to manage the millimeter-wave channel. For example, management frames may include beacon frames, probe response frames, etc., used to indicate information such as the availability and bandwidth of the millimeter-wave channel, and to broadcast TWT SPs on the millimeter-wave channel.
[0135] When the anchor channel is an anchor link, the anchor link can represent one or more of the following functions:
[0136] 1. The first MLD broadcasts the relevant millimeter-wave link / channel. For example, MLD1 broadcasts management frames for the relevant millimeter-wave link / channel on the anchor link.
[0137] 2. MLDs obtain channel resources on millimeter-wave links through channel contention on anchor links. For example, link 1 of MLD1 is the anchor link of its link 3.
[0138] When the anchor channel is an anchor point channel, the anchor point channel can represent one or more of the following functions:
[0139] 1. MLD broadcasts the relevant millimeter-wave link / channel information. For example, MLD1 broadcasts management frames for the relevant millimeter-wave link / channel on the anchor channel.
[0140] 2. MLDs obtain channel resources on millimeter-wave channels through channel contention on anchor channels. For example, the primary sub7GHz channel (20MHz bandwidth) of MLD1 on link 1 is the anchor channel of its primary millimeter-wave channel (20MHz bandwidth) on link 3.
[0141] Optionally, management frames associated with millimeter-wave links / channels, especially those broadcast, can only be transmitted on the anchor link / channel of that millimeter-wave link.
[0142] Optionally, if a millimeter-wave link / channel of an MLD (e.g., a second MLD) has multiple anchor links / channels, then when the MLD broadcasts a management frame about the millimeter-wave link / channel, the management frame must be transmitted at least once on all anchor links / channels of the millimeter-wave link.
[0143] Optionally, if an AP MLD (e.g., the first MLD) has multiple anchor links / channels for a millimeter-wave link / channel, then when the AP MLD broadcasts management frames about that millimeter-wave link / channel, it can choose to send the management frame on one or more anchor links / channels. This requires that all non-AP MLDs of this BSS with sites operating on that millimeter-wave link have at least one anchor link / channel included in the selected anchor link / channel.
[0144] That is, the management frame broadcasting method of the anchor channel includes one or more of the following methods:
[0145] Management frame broadcasting method 1: When the mapping relationship includes a mapping relationship between multiple anchor channels and a millimeter-wave channel, the management frame is broadcast at least once on multiple, or each, or all anchor channels corresponding to the millimeter-wave channel. For example, when a millimeter-wave channel corresponds to multiple anchor channels, the first MLD can broadcast the management frame on all these anchor channels to ensure that all stations can receive the management frame.
[0146] Management frame broadcasting method 2: When the mapping relationship includes a mapping relationship between multiple anchor channels and one millimeter-wave channel, the management frame is broadcast at least once on the first anchor channel or the first set of anchor channels corresponding to the millimeter-wave channel; wherein, at least one anchor channel of the second station operating on the millimeter-wave channel within this BSS belongs to the first anchor channel or the first set of anchor channels. For example, the first MLD can select one or a group of specific anchor channels to broadcast the management frame, but it is necessary to ensure that all second stations operating on the millimeter-wave channel within this BSS can listen to at least one anchor channel to ensure that the station can receive the management frame.
[0147] Access methods for millimeter-wave channels:
[0148] In some embodiments, transmission opportunities or channel access on the millimeter-wave channel are determined based on channel contention on the anchor channel. For example, a first MLD or a second MLD can determine transmission opportunities on the millimeter-wave channel by initiating contention on the anchor channel.
[0149] In some embodiments, where the mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels, channel contention is used to simultaneously compete for transmission opportunities on the anchor channel and at least one millimeter-wave channel. For example, a first MLD can simultaneously compete for the anchor channel and multiple millimeter-wave channels to improve resource utilization.
[0150] Optionally, if multiple millimeter-wave links / channels of an MLD (e.g., a second MLD) share an anchor link / channel, then the MLD can simultaneously acquire the anchor link / channel and at least one of the millimeter-wave links / channels through channel contention on that anchor link / channel.
[0151] Frame transmission method:
[0152] For at least one frame as described above, embodiments of this application provide at least two frame transmission methods: a broadcast frame transmission method and a "request frame-response frame" method. Any one of the at least two frame transmission methods can realize the indication, negotiation, or establishment of the above mapping relationship.
[0153] Broadcast frame transmission method: Figure 4 shows a flowchart of a millimeter-wave-based multi-link communication method illustrated in an exemplary embodiment of this application. The method is executed by a first MLD and / or a second MLD, and includes:
[0154] Step 410: The first MLD sends the first frame via broadcast; correspondingly, the second MLD receives the first frame sent by the first MLD via broadcast.
[0155] The first frame is used to notify one or more second stations of the mapping relationship between the anchor channel and the millimeter-wave channel in this BSS. For example, the first frame can be a beacon frame or a probe response frame. Optionally, the first frame carries mapping relationship information between the anchor channel and the millimeter-wave channel.
[0156] In some embodiments, all MLDs within the same BSS use the same anchor link / channel for the same millimeter-wave link / channel. This can, to some extent, prevent multiple stations from transmitting simultaneously on the millimeter-wave channel / link and causing transmission failure due to asynchrony of millimeter-wave link / channel information on the anchor link / channel.
[0157] Therefore, the first MLD (e.g., AP MLD) can broadcast the anchor channel to millimeter-wave channel mapping relationship of its BSS to one or more second MLDs (e.g., non-AP MLDs) within its BSS. For example, the AP MLD can transmit the anchor channel to millimeter-wave channel mapping element in its beacon frame, probe response frame, and association response frame.
[0158] "Request Frame - Response Frame" Method: Figure 5 shows a flowchart of a millimeter-wave-based multi-link communication method illustrated in an exemplary embodiment of this application. The method is executed by a first MLD and / or a second MLD, and includes:
[0159] Step 510: The second MLD sends a request frame to the first MLD; correspondingly, the first MLD receives the request frame sent by the second MLD.
[0160] Step 520: The first MLD sends a response frame to the second MLD. Correspondingly, the second MLD receives the response frame sent by the first MLD.
[0161] The request frame is used to request the mapping relationship between the anchor point channel and the millimeter wave channel. The response frame is used to indicate whether the requested mapping relationship is accepted or rejected.
[0162] In some possible embodiments, a response frame is mandatory and carries information indicating acceptance or rejection. For example, the response frame may carry a bit where a value of 1 indicates acceptance of the mapping requested by the second MLD, and a value of 0 indicates rejection of the mapping requested by the second MLD. Alternatively, the bit may be set to 0 for acceptance of the mapping requested by the second MLD and 1 for rejection of the mapping requested by the second MLD.
[0163] In some possible embodiments, the response frame is an optional design; not sending a response frame indicates acceptance of the requested mapping relationship, and sending a response frame indicates rejection of the requested mapping relationship; or, not sending a response frame indicates rejection of the requested mapping relationship, and sending a response frame indicates acceptance of the requested mapping relationship.
[0164] In some possible embodiments, if the response frame indicates a rejection of the first mapping requested by the second MLD, the response frame may also optionally carry a second mapping indicated or suggested by the first MLD to the second MLD. This second mapping may be completely different from the first mapping, partially the same, or derived based on a modification of the first mapping.
[0165] The sender and receiver of the aforementioned request and response frames can also be interchanged. For example, Figure 6 shows a flowchart of a millimeter-wave-based multi-link communication method illustrated in another exemplary embodiment of this application. The method is executed by a first MLD and / or a second MLD, and includes:
[0166] Step 610: The first MLD sends a request frame to the second MLD; correspondingly, the second MLD receives the request frame sent by the first MLD;
[0167] Step 620: The second MLD sends a response frame to the first MLD; correspondingly, the first MLD receives the response frame sent by the second MLD.
[0168] In other words, a Non-AP MLD can send a request to an AP MLD to establish a mapping relationship between the anchor channel and the millimeter-wave channel. For example, the non-AP MLD sends a request frame to the AP MLD containing a mapping field or element for the anchor channel to the millimeter-wave channel. This mapping field or element represents the mapping relationship between the anchor channel and the millimeter-wave channel that the non-AP MLD requests to establish. The AP MLD can decide whether to accept the request and send a reply frame containing its decision to the non-AP MLD.
[0169] Note: Alternatively, the AP MLD can send a request frame to the non-AP MLD, and the non-AP MLD can send a reply frame.
[0170] Indicator of mapping relationship:
[0171] At least one of the first frame, request frame, or response frame carries a field for indicating a mapping relationship. In some embodiments, the mapping relationship is indicated by one or more of the following fields: one or more mapping relationship fields, a default mapping relationship; whether a mapping switch time is present; whether an expected duration is present; the number of link mappings; the mapping switch time; and the expected duration.
[0172] in:
[0173] Each mapping field includes one or more of the following fields: Anchor Link ID; Anchor Link Channel Number; Millimeter Wave Link ID; Millimeter Wave Link Channel Number. An example mapping field is shown in Figure 7.
[0174] Anchor Link ID: The link ID used to indicate the anchor link associated with the millimeter-wave link.
[0175] Anchor Channel Number: Used to indicate the channel number of the anchor link, the channel number of the anchor channel, or the center frequency index of the channel.
[0176] Millimeter-wave link ID: The link ID used to indicate the millimeter-wave link associated with the anchor link.
[0177] Millimeter wave channel number: The channel number (or channel center frequency index) of the millimeter wave link or the channel number (or channel center frequency index) of the millimeter wave channel.
[0178] In some embodiments, at least one of the first frame, request frame, or response frame carries an anchor channel to millimeter wave channel mapping element (hereinafter referred to as mapping element). An exemplary mapping element is shown in Figure 8.
[0179] In some embodiments, the mapping switch time field is present when the mapping element is sent by the AP associated with the AP MLD; otherwise, the field is absent. The absence of the mapping switch time field in the mapping element indicates that the indicated anchor link to millimeter-wave link mapping has been established. Optionally, the 2-byte mapping switch time field is in TU (time unit) and its value is set to the establishment time of the mapping relationship, with the TSF (Time Synchronization Function) value corresponding to the BSS identified by the BSSID of the frame containing the mapping element as the time base: that is, bits 10 to 25 of the TSF.
[0180] When the Mapping Switching Time field is present, the Expected Duration field indicates the anticipated effective duration of the proposed anchor link-to-millimeter-wave link mapping, in TUs, calculated from the mapping establishment time indicated in the Mapping Switching Time field. When the Mapping Switching Time field is absent, the Expected Duration field indicates the anticipated remaining effective duration of the established anchor link-to-millimeter-wave link mapping, in TUs. The starting point for the remaining duration is: if the frame carrying the mapping element is a beacon frame, then it is the TBTT (Target Beacon Transmission Time) corresponding to that beacon frame; if the frame carrying the mapping element is not a beacon frame, then it is the nearest TBTT before that frame's transmission.
[0181] Optionally, the expected duration field exists if the mapping element is carried by a beacon frame, probe response frame, association response frame, or reassociation response frame sent by an AP associated with the AP MLD; otherwise, it does not exist.
[0182] Anchor link to millimeter wave link mapping relationship field:
[0183] Referring to Figure 9, this field contains one or more anchor link-to-millimeter wave link mapping fields to indicate the mapping relationship between the anchor link and the millimeter wave link. If the mapping switch time field is present, it indicates a proposed anchor link-to-millimeter wave link mapping relationship; if the mapping switch time field is not present, it indicates an existing anchor link-to-millimeter wave link mapping relationship. The number of anchor link-to-millimeter wave link mapping relationship fields is indicated by the number of mapping relationships field in the control field.
[0184] The default mapping field (also known as the default anchor link to millimeter-wave link default mapping): When this field is set to 1, it indicates that the BSS uses the predefined anchor link / channel to millimeter-wave link / channel mapping described in the following sections; otherwise, this field is set to 0. For example, the default mapping is that the only 2.4GHz link of the default MLD is the anchor link of the IMW link. For example, the default mapping is that the default 2.4GHz channel 1 (or Channel 6 or Channel 11) is the anchor link of the IMW link. For example, the default mapping is that the default 5GHz link of the default MLD is the anchor link of the default IMW link. For example, the default mapping is that the default 6GHz link of the default MLD is the anchor link of the default IMW link.
[0185] Does the mapping switch time subfield exist? If the mapping switch time field exists, this subfield is set to 1; otherwise, it is set to 0.
[0186] Does the expected duration subfield exist? If the expected duration field exists, this subfield is set to 1; otherwise, it is set to 0.
[0187] Number of Link Mapping Relationships: This field sets the number of anchor link to millimeter wave link mapping relationship fields in the mapping element.
[0188] It should be noted that the meanings indicated by the values 1 and 0 above are merely examples, and the values can be interchanged in different embodiments. For example, regarding the existence of a subfield for mapping switching time: if the mapping switching time field exists, this subfield is set to 0; otherwise, it is set to 1. Another example is the existence of a subfield for expected duration: if the expected duration field exists, this subfield is set to 0; otherwise, it is set to 1.
[0189] Predefined mapping relationship between anchor link / channel and millimeter wave link / channel:
[0190] An anchor channel for a millimeter-wave channel refers to the channel access required by that millimeter-wave channel. Anchor channels are typically channels below 7 GHz (i.e., Sub-7 channels). Wi-Fi networks can specify that all their access points (APs) and non-AP STAs use a predefined mapping from anchor channels to millimeter-wave channels.
[0191] A Wi-Fi network can define one or more millimeter-wave channels, each with a different center frequency and a different channel number. For example, the network might set the anchor channel for millimeter-wave channel A (whose center frequency is X MHz and whose channel number or channel center frequency index is A) to 2.4 GHz (or 5 GHz or 6 GHz) channel B (the channel with channel number or channel center frequency index B in the 2.4 GHz (or 5 GHz or 6 GHz) band).
[0192] Wi-Fi networks can define that only certain channels on 2.4 GHz and / or 5 GHz and / or 6 GHz are allowed to be anchor channels.
[0193] Millimeter-wave link NAV RSSI threshold:
[0194] When an MLD (first MLD and / or second MLD) listens for an OBSS MLD transmitting on the anchor channel, and that OBSS MLD is simultaneously transmitting on a millimeter-wave channel, if the RSSI of the PPDU of the OBSS MLD received by the MLD on the anchor channel is greater than or equal to the millimeter-wave link NAV RSSI threshold, then the MLD sets the NAV on the millimeter-wave link. The duration of the NAV setting can be the NAV of the OBSS MLD on the millimeter-wave channel (or the anchor channel). If the RSSI of the OBSS MLD received by the MLD on the anchor channel is less than the millimeter-wave link NAV RSSI threshold, the MLD can access the millimeter-wave link through channel contention on other anchor channels of the same millimeter-wave link.
[0195] When an MLD (first MLD and / or second MLD) detects its own BSS MLD transmitting on the anchor channel, and that same BSS MLD is simultaneously transmitting on a millimeter-wave channel, then that MLD sets a NAV on the millimeter-wave link. The duration of the NAV setting can be the NAV of the BSS MLD on the millimeter-wave channel (or anchor channel).
[0196] Mapping relationship from one anchor channel / link to multiple millimeter-wave channels / links:
[0197] When a millimeter-wave link / channel has multiple anchor links / channels, the first MLD needs to consider sending management frames associated with that millimeter-wave link / channel on one or more anchor links / channels. The purpose is to ensure that all second MLDs receiving management frames receive management frames on at least one of their anchor links / channels. In particular, when the AP MLD broadcasts management frames associated with a millimeter-wave link / channel, the AP MLD needs to guarantee that management frames are sent on at least one anchor link / channel of each non-AP MLD associated with the millimeter-wave link / channel.
[0198] In some embodiments, the fields indicating the mapping relationship are carried by a first element, or a mapping relationship element, or an anchor channel to millimeter-wave channel mapping relationship element. For example, a new information element (IE) can be defined to carry these fields. This information element may be called a mapping element, an anchor link / channel to millimeter-wave link / channel mapping element, etc.
[0199] ICF / ICR frame interaction:
[0200] In some embodiments, the method further includes: after the second MLD successfully competes for a channel on the anchor channel, it sends an ICF frame; the first MLD receives the ICF frame, which is used to inquire whether the channel resource TXOP on the millimeter-wave channel is accessible; the first MLD sends an ICR frame, and correspondingly the second MLD receives the ICR frame, which is used to indicate whether the millimeter-wave channel is available.
[0201] For example, after receiving the ICF frame, the first MLD decides whether to allow the second station to access based on its own resource usage on the millimeter-wave channel, and notifies the second station through the ICR frame.
[0202] In some embodiments, the ICF frame carries one or more of the following fields: millimeter-wave channel request identifier (or millimeter-wave channel request, millimeter-wave link request, millimeter-wave channel request); millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time.
[0203] For example, the second station indicates the requested millimeter-wave channel, the requested TXOP size, and the start time in the ICF frame.
[0204] In some embodiments, the ICR frame carries one or more of the following fields: millimeter-wave channel availability identifier (or millimeter-wave channel available, millimeter-wave link available, millimeter-wave channel available, millimeter-wave channel ready, millimeter-wave link ready, millimeter-wave channel ready); millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time; number of IFS that need to be checked for channel idleness before accessing the millimeter-wave channel.
[0205] ICF / ICR frame format:
[0206] Figures 10 and 11 illustrate two frame formats of ICF frames, respectively. As shown in Figure 10 or Figure 11, an ICF frame includes one or more of the following fields:
[0207] Millimeter-wave link request (1 bit): This field is set to 1, indicating that the TXOP holder requests transmission on the corresponding millimeter-wave link. Otherwise, this field is set to 0.
[0208] Millimeter-wave link ID (4 bits): This field is set to the link ID of the millimeter-wave link that the ICF sender will access.
[0209] Millimeter-wave channel number (1 byte): This field is set to the link ID of the millimeter-wave channel that the ICF sender will access. The receiver in this field should switch its STA operating on the millimeter-wave link indicated in the millimeter-wave link ID field to the millimeter-wave channel indicated in this field to receive data packets from the sender.
[0210] Millimeter wave TXOP: This field is set to indicate the duration of TXOP on a millimeter wave link.
[0211] Start Time: This field is set to indicate when the sender of this field will access the millimeter-wave link.
[0212] In addition, the ICF frame may optionally include one or more of the following fields: frame control, duration, receive address, send address, basic service set identifier, sequence control, and frame check.
[0213] The difference between Figure 11 and Figure 10 is that the millimeter-wave link request field, millimeter-wave link ID field, millimeter-wave channel number field, and millimeter-wave TXO field P in Figure 11 are indicated at the site granularity or user information granularity. That is, one site can correspond to a set of millimeter-wave link request field, millimeter-wave link ID field, millimeter-wave channel number field, and millimeter-wave TXOP field.
[0214] Figure 12 shows a schematic diagram of the ICR frame format. As shown in Figure 12, an ICR frame includes one or more of the following fields:
[0215] Millimeter-wave link available (1 bit): This field is set to 1 to indicate that the receiver is ready to use the millimeter-wave link for receiving. (Or this field is set to 1 to indicate that the sender can access the millimeter-wave link as requested in the ICF field.) Otherwise, this field is set to 0, and the sender is not allowed to transmit on the millimeter-wave link.
[0216] Millimeter-wave link ID (4 bits): This field is set to the link ID of the millimeter-wave link that the ICF sender will access.
[0217] Millimeter-wave channel number (1 byte): This field is set to the link ID of the millimeter-wave channel that the ICF sender will access. The receiver in this field should switch its STA operating on the millimeter-wave link indicated in the millimeter-wave link ID field to the millimeter-wave channel indicated in this field to receive data packets from the sender.
[0218] Start Time: This field is set to indicate when the sender of this field will access the millimeter-wave link.
[0219] IFS Quantity: This field sets the number of IFS durations the sender should be aware of before accessing the millimeter-wave channel.
[0220] In addition, the ICR frame may optionally include one or more of the following fields: frame control, duration, receive address, send address, common information, and frame check.
[0221] Figure 13 illustrates an AP MLD transmitting management frames related to millimeter-wave links / channels on multiple anchor links / channels. MLD1 is an AP MLD operating on links 1, 2, and 3. Links 1 and 2 operate on sub-7 GHz channels. Link 3 operates on a millimeter-wave channel. MLD1 is associated with three non-AP MLDs: MLD2, 3, and 4. MLD2 operates on links 1, 2, and 3. MLD3 operates on links 2 and 3. MLD4 operates on links 1 and 3. Links 1 and 2 are anchor links to link 3 (or the main channels of link 1 and link 2 are anchor channels for the millimeter-wave channel). MLD1 broadcasts a management frame related to millimeter-wave link 3 (i.e., management frame 1 in Figure 13). To ensure that MLD2, 3, and 4 all receive this management frame, MLD1 transmits management frame 1 on links 1 and 2, respectively. In the diagram, BO stands for Back Off, a mechanism used in contention-based media access control (such as CSMA / CA, Carrier Sense Multiple Access / Collision Avoidance).
[0222] As shown in Figure 14, if MLD2, 3, and 4 are all operating on Link 2 and Link 3, then MLD1 can broadcast Management Frame 1 only on Link 2.
[0223] When an MLD (Multi-Level Disk) plans to simultaneously acquire channel resources or transmission opportunities (TXOPs) on both the sub-7 GHz channel and a millimeter-wave link through channel contention, the MLD can first send an ICF (Initial Communication Frame) on the sub-7 GHz channel to inquire about the availability of the millimeter-wave link after completing the channel contention. The ICR (Initial Response Frame) used to reply to the ICF frame will inform the MLD of the availability of the millimeter-wave link. If the ICR frame indicates that the millimeter-wave link is unavailable, then the MLD cannot access the millimeter-wave link. If the ICR frame indicates that the millimeter-wave link is available, then the MLD can access the millimeter-wave link.
[0224] As shown in Figure 15, MLD3 simultaneously accesses the channels on both Link 2 and Link 3 through channel contention on Link 2. After completing channel contention on Link 2, MLD3 learns that Link 3 is accessible via ICF / ICR exchange. That is, the ICR frame replied by MLD1 to MLD3 indicates that Link 3 is available. Therefore, after ICF / ICR exchange, MLD3 accesses Link 3 and begins transmission on Link 3.
[0225] However, Link 3 may also be occupied by another MLD, rendering Link 3 unusable. As shown in Figure 16, MLD2 accesses the channels of Link 2 and Link 3 through another anchor point, Link 2. However, since millimeter waves are directional transmissions, MLD3 may not be able to detect MLD2's transmission on Link 3. Therefore, when MLD2 interacts with ICF1 and ICR1, MLD1 reports to MLD2 that Link 3 is available, while when MLD3 interacts with ICF2 and ICR2, MLD1 reports to MLD3 that Link 3 is unusable.
[0226] Interchange Response (ICR) can help ICF transmitting stations learn more about the channel status of the millimeter-wave link. As shown in Figure 17, the ICR frame can tell MLD3 when Link 3 will begin to be idle (or when Link 3 will end its busy state). For example, the ICR informs MLD3 that Link 3 will begin to be idle at time t. That is, the ICR can tell the ICF transmitting station how many IFS (Interchange Frames) it will take to access the millimeter-wave link.
[0227] As shown in Figure 18, if MLD1 is an AP MLD and sends an ICR frame, then MLD1 can use the ICR frame to notify each site requesting access to the millimeter-wave link that it needs to wait n (n=2 in Figure 18) IFS times to access the millimeter-wave link. The value n can be equal to the maximum number of IFS times that all non-AP MLDs are currently waiting on this millimeter-wave link + 1. Alternatively, the value n can be greater than the maximum number of IFS times that all non-AP MLDs are currently waiting on this millimeter-wave link.
[0228] When an MLD operating on a millimeter-wave link can detect the transmissions of other MLDs on the same BSS on the millimeter-wave link (e.g., the MLD is simultaneously operating on all anchor links / channels of the millimeter-wave link, or the MLD can monitor the transmissions of all other sites on the same millimeter-wave link within the same BSS), then the MLD may not necessarily send an ICF / ICR to obtain channel information for the millimeter-wave link when planning to transmit via the anchor channel. As shown in Figure 19, if MLD3 can receive the ICR frame sent from MLD1 to MLD2 on link 1, it will automatically set NAV for millimeter-wave link 3.
[0229] When an MLD plans to transmit over a millimeter-wave link via an anchor channel, if the MLD knows that the millimeter-wave link is busy at CCA, then the station may not need to send ICF / ICR to obtain the channel information of the millimeter-wave link.
[0230] ICF frames can notify the receiver when the MLD will be transmitted via the millimeter-wave link (e.g., time t) and the transmission time on the millimeter-wave link (e.g., time T).
[0231] As shown in Figures 20, 21, and 22, the MLD transmission can begin a channel detection period of one IFS time at time t (as shown in Figure 20), or end a channel detection period of one IFS time before starting at time t (as shown in Figure 21). The transmission duration T may or may not include the time required for channel detection. Figure 21 shows a transmission duration T that does not include the time required for channel detection, while Figure 22 shows a transmission duration T that includes the time required for channel detection.
[0232] In the case of multiple anchor channels / links mapped to a millimeter-wave channel / link, when several millimeter-wave channels / links share an anchor channel / link, an MLD can access these millimeter-wave links by competing for that anchor channel / link.
[0233] As shown in Figure 23, MLD1 accesses two millimeter-wave links simultaneously and transmits data by competing for channel access on link 1.
[0234] As shown in Figure 24, MLD1 selects one of the millimeter-wave links for transmission by competing for channels on link 1. Note: ICF / ICR in Figure 24 is an optional design.
[0235] As shown in Figure 25, MLD1 simultaneously accesses and transmits through two millimeter-wave links by competing for channel access on link 1. In this case, MLD1 can allocate the millimeter-wave links to different receiving stations for transmission.
[0236] Figure 26 shows a block diagram of a first MLD device provided in an exemplary embodiment of this application. The first MLD device includes:
[0237] The first communication module 2620 is used to send and / or receive at least one frame, the at least one frame being used to determine the mapping relationship between the anchor point channel and the millimeter wave channel; wherein, the anchor point channel includes an anchor point link or an anchor point channel, and the millimeter wave channel includes a millimeter wave link or a millimeter wave channel.
[0238] In some embodiments, the mapping relationship includes at least one of the following four types: the mapping relationship between the anchor link and the millimeter-wave link; the mapping relationship between the anchor channel and the millimeter-wave link; the mapping relationship between the anchor link and the millimeter-wave channel; and the mapping relationship between the anchor channel and the millimeter-wave channel.
[0239] In some embodiments, the mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels; or, the mapping relationship includes a mapping relationship between multiple anchor channels and a millimeter-wave channel; or, the mapping relationship includes a mapping relationship between an anchor channel and a millimeter-wave channel.
[0240] In some embodiments, the anchor point channel is used to publish management frames, which are used to manage the millimeter-wave channel.
[0241] In some embodiments, the mapping relationship includes a mapping relationship between multiple anchor channels and a millimeter-wave channel, and the management frame is broadcast at least once on multiple or each or all anchor channels corresponding to the millimeter-wave channel.
[0242] In some embodiments, the mapping relationship includes a mapping relationship between multiple anchor channels and a millimeter-wave channel, and the management frame is broadcast at least once on the first anchor channel or the first set of anchor channels corresponding to the millimeter-wave channel;
[0243] Among them, at least one anchor channel of the second station operating in the millimeter-wave channel within this BSS belongs to the first anchor channel or the first set of anchor channels.
[0244] In some embodiments, the transmission opportunities or channel access of the millimeter-wave channel are determined based on channel contention on the anchor channel.
[0245] In some embodiments, the mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels, and the channel contention is used to simultaneously compete for transmission opportunities on the anchor channel and at least one millimeter-wave channel.
[0246] In some embodiments, the first communication module 2620 includes:
[0247] The first transmitting module 2640 is used to transmit a first frame via broadcast. The first frame is used to notify one or more second stations of the mapping relationship between the anchor channel and the millimeter-wave channel in this BSS.
[0248] In some embodiments, the first communication module 2620 includes:
[0249] The first receiving module 2660 is used to receive a request frame, which requests a mapping relationship between the anchor point channel and the millimeter wave channel; the first sending module 2640 is used to send a response frame, which indicates whether the requested mapping relationship is accepted or rejected.
[0250] And / or,
[0251] The first sending module 2640 is used to send a request frame, which is used to request a mapping relationship between the anchor point channel and the millimeter wave channel; the first receiving module 2660 is used to receive a response frame, which is used to indicate whether to accept or reject the requested mapping relationship.
[0252] In some embodiments, the mapping relationship is indicated by one or more of the following fields: default mapping relationship; whether the mapping switch time exists; whether the expected duration exists; the number of mapping relationships; the mapping switch time; the expected duration; and one or more mapping relationship fields.
[0253] In some embodiments, the mapping relationship field includes one or more of the following fields: anchor link ID; anchor link channel number; millimeter wave link ID; millimeter wave link channel number.
[0254] In some embodiments, the field used to indicate the mapping relationship is carried by the first element, or the mapping relationship element, or the anchor channel to the millimeter wave channel mapping relationship element.
[0255] In some embodiments, the apparatus further includes: a first receiving module 2660, configured to receive an ICF frame, the ICF frame being used to inquire whether the channel resource TXOP on the millimeter-wave channel is accessible;
[0256] The first transmitting module 2640 is used to transmit an ICR frame, which is used to indicate whether the millimeter-wave channel is available.
[0257] The ICF frame is sent by the second station after it successfully competes for the channel on the anchor point channel.
[0258] In some embodiments, the ICF frame carries one or more of the following fields: millimeter-wave channel request identifier; millimeter-wave link D; millimeter-wave channel number; millimeter-wave TXOP; start time.
[0259] In some embodiments, the ICR frame carries one or more of the following fields: millimeter-wave channel availability identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time; number of IFS that need to be checked for channel idleness before accessing the millimeter-wave channel.
[0260] In some embodiments, the apparatus further includes: a first processing module (not shown), configured to: when an Overlapping Basic Service Set Multilink Device (OBSS MLD) is detected transmitting on the anchor channel and the OBSS MLD is simultaneously transmitted on the millimeter-wave channel, set a Network Allocation Vector (NAV) on the millimeter-wave channel if the Received Signal Strength Indication (RSSI) of the Physical Layer Protocol Data Unit (PPDU) of the OBSS MLD received on the anchor channel is greater than or equal to a first threshold; and if the RSSI of the PPDU of the OBSS MLD received on the anchor channel is less than the first threshold, access the millimeter-wave channel through channel contention on other anchor channels of the millimeter-wave link; and / or, when a Basic Service Set Multilink Device (BSS MLD) is detected transmitting on the anchor channel and the BSS MLD is simultaneously transmitted on the millimeter-wave channel, set an NAV on the millimeter-wave channel if the RSSI of the PPDU received on the anchor channel is greater than or equal to a second threshold;
[0261] The duration of the NAV is the NAV on the millimeter-wave channel or the anchor channel.
[0262] Figure 27 shows a block diagram of a second MLD device provided in an exemplary embodiment of this application. The second MLD device includes:
[0263] The second communication module 2720 is used to send and / or receive at least one frame, the at least one frame being used to determine the mapping relationship between the anchor channel and the millimeter wave channel;
[0264] The anchor point channel includes an anchor point link or an anchor point channel, and the millimeter wave channel includes a millimeter wave link or a millimeter wave channel.
[0265] In some embodiments, the mapping relationship includes at least one of the following four types: the mapping relationship between the anchor link and the millimeter-wave link; the mapping relationship between the anchor channel and the millimeter-wave link; the mapping relationship between the anchor link and the millimeter-wave channel; and the mapping relationship between the anchor channel and the millimeter-wave channel.
[0266] In some embodiments, the mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels; or, the mapping relationship includes a mapping relationship between multiple anchor channels and a millimeter-wave channel; or, the mapping relationship includes a mapping relationship between an anchor channel and a millimeter-wave channel.
[0267] In some embodiments, the anchor point channel is used to publish management frames, which are used to manage the millimeter-wave channel.
[0268] In some embodiments, the mapping relationship includes a mapping relationship between multiple anchor channels and a millimeter-wave channel, and the management frame is broadcast at least once on multiple or each or all anchor channels corresponding to the millimeter-wave channel.
[0269] In some embodiments, the mapping relationship includes a mapping relationship between multiple anchor channels and a millimeter-wave channel, and the management frame is broadcast at least once on the first anchor channel or the first set of anchor channels corresponding to the millimeter-wave channel;
[0270] Among them, at least one anchor channel of the second station operating in the millimeter-wave channel within this BSS belongs to the first anchor channel or the first set of anchor channels.
[0271] In some embodiments, the transmission opportunities or channel access of the millimeter-wave channel are determined based on channel contention on the anchor channel.
[0272] In some embodiments, the mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels, and the channel contention is used to simultaneously compete for transmission opportunities on the anchor channel and at least one millimeter-wave channel.
[0273] In some embodiments, the first communication module 2720 includes a second receiving module 2740, configured to receive a first frame, the first frame being configured to notify the second station of the mapping relationship between the anchor channel and the millimeter-wave channel in this BSS.
[0274] In some embodiments, the first communication module 2720 includes: a second receiving module 2740, configured to receive a request frame, the request frame being configured to request a mapping relationship between the anchor channel and the millimeter-wave channel; a second sending module 2760, configured to send a response frame, the response frame being configured to indicate acceptance or rejection of the requested mapping relationship; and / or, the second sending module 2760, configured to send a request frame, the request frame being configured to request a mapping relationship between the anchor channel and the millimeter-wave channel; and the second receiving module 2740, configured to receive a response frame, the response frame being configured to indicate acceptance or rejection of the requested mapping relationship.
[0275] In some embodiments, the mapping relationship is indicated by one or more of the following fields: default mapping relationship; whether the mapping switch time exists; whether the expected duration exists; the number of mapping relationships; the mapping switch time; the expected duration; and one or more mapping relationship fields.
[0276] In some embodiments, the mapping relationship field includes one or more of the following fields: anchor link ID; anchor link channel number; millimeter wave link ID; millimeter wave link channel number.
[0277] In some embodiments, the field used to indicate the mapping relationship is carried by the first element, or the mapping relationship element, or the anchor channel to the millimeter wave channel mapping relationship element.
[0278] In some embodiments, the apparatus further includes: a second transmitting module 2760, configured to transmit an ICF frame after a successful channel contention on the anchor channel, the ICF frame being used to inquire whether the channel resource TXOP on the anchor channel and the millimeter wave channel is accessible;
[0279] The second receiving module 2740 is used to receive ICR frames, which are used to indicate whether the millimeter-wave channel is available.
[0280] In some embodiments, the ICF frame carries one or more of the following fields: millimeter-wave channel request identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time.
[0281] In some embodiments, the ICR frame carries one or more of the following fields: millimeter-wave channel availability identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time; number of IFS that need to be checked for channel idleness before accessing the millimeter-wave channel.
[0282] In some embodiments, the apparatus further includes: a second processing module (not shown), configured to: when an Overlapping Basic Service Set Multilink Device (OBSS MLD) is detected transmitting on the anchor channel, and the OBSS MLD is simultaneously transmitting on the millimeter-wave channel, if the Received Signal Strength Indication (RSSI) of the Physical Layer Protocol Data Unit (PPDU) of the OBSS MLD received on the anchor channel is greater than or equal to a first threshold, set a Network Allocation Vector (NAV) on the millimeter-wave channel; if the RSSI of the PPDU of the OBSS MLD received on the anchor channel is less than the first threshold, access the millimeter-wave channel through channel contention on other anchor channels of the millimeter-wave link; and / or, when a Basic Service Set Multilink Device (BSS MLD) is detected transmitting on the anchor channel, and the BSS MLD is simultaneously transmitting on the millimeter-wave channel, if the RSSI of the PPDU received on the anchor channel is greater than or equal to a second threshold, set a NAV on the millimeter-wave channel; wherein the duration of the NAV is the NAV on the millimeter-wave channel or the anchor channel.
[0283] Figure 28 shows a schematic diagram of the structure of a communication device (such as a first MLD or a second MLD) provided in an exemplary embodiment of this application. The communication device 2800 may include a processor 2801, a transceiver 2802, and a memory 2803. The processor 2801 can be used to control transmission and / or reception, and to implement the functions of the processing module. The transceiver 2802 can be used to implement transmission and / or reception functions, such as implementing the functions of at least one of the aforementioned transmission module and reception module.
[0284] The processor 2801 includes one or more processing cores, and the processor 2801 executes various functional applications and information processing by running software programs and modules.
[0285] Transceiver 2802 may include a receiver and a transmitter. For example, transceiver 2802 may include a wired communication component, which may include a wired communication chip and a wired interface (such as a fiber optic interface). Optionally, transceiver 2802 may also include a wireless communication component, which may include a wireless communication chip and a radio frequency antenna.
[0286] Transceiver 2802 is used to send and receive at least one frame to perform the millimeter wave-based multi-link communication method in the above method embodiments.
[0287] The memory 2803 can be connected to the processor 2801 and the transceiver 2802.
[0288] The memory 2803 can be used to store a computer program executed by the processor, and the processor 2801 is used to execute the computer program to implement the various steps in the above method embodiments.
[0289] Furthermore, the memory 2803 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static on-demand memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.
[0290] For details not described in this embodiment, please refer to the method-side embodiment above, which will not be repeated here.
[0291] This application also provides a computer-readable storage medium storing a computer program for execution by a processor to implement the aforementioned millimeter-wave-based multi-link communication method and / or data packet transmission / reception method. In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).
[0292] This application embodiment also provides a first chip, which includes programmable logic circuits and / or program instructions. When the first chip is running on a first site, it is used to implement the above-mentioned millimeter-wave-based multi-link communication method on the first site side.
[0293] This application also provides a second chip, which includes programmable logic circuits and / or program instructions. When the second chip runs on a second site, it implements the above-mentioned millimeter-wave-based multi-link communication method on the second site side.
[0294] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. The processor reads and executes the computer program from the computer-readable storage medium to implement the millimeter-wave-based multi-link communication method described above for the first MLD side and / or the second MLD side.
[0295] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.
[0296] It should be understood that the frame format and element format shown in the embodiments of this application are exemplary cases. Under different embodiments or different designs, it is not excluded that at least one of the following designs may change: the position of each field in the frame / element, the arrangement order with other fields, the number of bytes occupied, and the number of bits occupied. This application does not limit the specific format of each frame or element.
[0297] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. A method of millimeter wave based multi-link communication, the method comprising: The method is performed by a first multi-link device (MLD), and the method includes: sending and / or receiving at least one frame, the at least one frame being used to determine a mapping relationship between an anchor channel and a millimeter-wave channel; wherein the anchor channel includes an anchor link or an anchor channel, and the millimeter-wave channel includes a millimeter-wave link or a millimeter-wave channel.
2. The method of claim 1, wherein, The mapping relationship includes at least one of the following four types: the mapping relationship between the anchor link and the millimeter-wave link; the mapping relationship between the anchor channel and the millimeter-wave link; and the mapping relationship between the anchor link and the millimeter-wave channel. The mapping relationship between the anchor channel and the millimeter-wave channel.
3. The method according to claim 1 or 2, characterized in that, The mapping relationship includes a mapping relationship between one anchor channel and multiple millimeter-wave channels; or, the mapping relationship includes a mapping relationship between multiple anchor channels and one millimeter-wave channel; or, the mapping relationship includes a mapping relationship between one anchor channel and one millimeter-wave channel.
4. The method according to any one of claims 1 to 3, characterized in that, The anchor point channel is used to publish management frames, which are used to manage the millimeter-wave channel.
5. The method according to claim 4, characterized in that, The mapping relationship includes a mapping relationship between multiple anchor point channels and a millimeter wave channel, and the management frame is broadcast at least once on multiple or each or all anchor point channels corresponding to the millimeter wave channel.
6. The method according to claim 4, characterized in that, The mapping relationship includes the mapping relationship between multiple anchor channels and a millimeter-wave channel. The management frame is broadcast at least once on the first anchor channel or the first set of anchor channels corresponding to the millimeter-wave channel. Among them, the second station in this Basic Service Set (BSS) operating on the millimeter-wave channel has at least one anchor channel belonging to the first anchor channel or the first set of anchor channels.
7. The method according to any one of claims 1 to 6, characterized in that, The transmission opportunity or channel access of the millimeter-wave channel is determined based on channel contention on the anchor channel.
8. The method according to claim 7, characterized in that, The mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels, and the channel contention is used to simultaneously compete for transmission opportunities on the anchor channel and at least one millimeter-wave channel.
9. The method according to any one of claims 1 to 8, characterized in that, Sending at least one frame includes: sending a first frame via broadcast, the first frame being used to notify one or more second stations of the mapping relationship between the anchor channel and the millimeter-wave channel in this BSS.
10. The method according to any one of claims 1 to 8, characterized in that, The sending and / or receiving of at least one frame includes: receiving a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; sending a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship; and / or, sending a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; and receiving a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship.
11. The method according to claim 9 or 10, characterized in that, The mapping relationship is indicated by one or more of the following fields: default mapping relationship; whether the mapping switch time exists; whether the expected duration exists; the number of mapping relationships; the mapping switch time; the expected duration; one or more mapping relationship fields.
12. The method according to claim 10, characterized in that, The mapping relationship field includes one or more of the following fields: anchor link identifier ID; anchor link channel number; millimeter wave link ID; millimeter wave link channel number.
13. The method according to claim 11 or 12, characterized in that, The field used to indicate the mapping relationship is carried by the first element, or the mapping relationship element, or the anchor channel to the millimeter wave channel mapping relationship element.
14. The method according to any one of claims 1 to 13, characterized in that, The method further includes: receiving an initial control (ICF) frame, the ICF frame being used to inquire whether channel resources or transmission opportunities (TXOPs) on the millimeter-wave channel are available; and sending an initial response (ICR) frame, the ICR frame being used to indicate whether the millimeter-wave channel is available; wherein the ICF frame is sent by the second station after successfully contending for the channel on the anchor point channel.
15. The method according to claim 14, characterized in that, The ICF frame carries one or more of the following fields: millimeter-wave channel request identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time.
16. The method according to claim 14, characterized in that, The ICR frame carries one or more of the following fields: millimeter-wave channel availability identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time; number of idle IFS that need to be detected before accessing the millimeter-wave channel.
17. The method according to any one of claims 1 to 16, characterized in that, The method further includes: when an Overlapping Basic Service Set Multilink Device (OBSS MLD) is detected transmitting on the anchor channel, and the OBSS MLD is simultaneously transmitting on the millimeter-wave channel, if the Received Signal Strength Indication (RSSI) of the Physical Layer Protocol Data Unit (PPDU) of the OBSS MLD received on the anchor channel is greater than or equal to a first threshold, setting a Network Allocation Vector (NAV) on the millimeter-wave channel; if the RSSI of the PPDU of the OBSS MLD received on the anchor channel is less than the first threshold, accessing the millimeter-wave channel through channel contention on other anchor channels of the millimeter-wave link; and / or, when a Basic Service Set Multilink Device (BSS MLD) is detected transmitting on the anchor channel, and the BSS MLD is simultaneously transmitting on the millimeter-wave channel, if the RSSI of the PPDU received on the anchor channel is greater than or equal to a second threshold, setting a NAV on the millimeter-wave channel; wherein the duration of the NAV is the NAV on the millimeter-wave channel or the anchor channel.
18. A multi-link communication method based on millimeter waves, characterized in that, The method is performed by a second MLD, and the method includes: receiving and / or transmitting at least one frame, the at least one frame being used to determine a mapping relationship between an anchor channel and a millimeter-wave channel; wherein the anchor channel includes an anchor link or an anchor channel, and the millimeter-wave channel includes a millimeter-wave link or a millimeter-wave channel.
19. The method according to claim 18, characterized in that, The mapping relationship includes at least one of the following four types: the mapping relationship between the anchor link and the millimeter-wave link; the mapping relationship between the anchor channel and the millimeter-wave link; and the mapping relationship between the anchor link and the millimeter-wave channel. The mapping relationship between the anchor channel and the millimeter-wave channel.
20. The method according to claim 18 or 19, characterized in that, The mapping relationship includes a mapping relationship between one anchor channel and multiple millimeter-wave channels; or, the mapping relationship includes a mapping relationship between multiple anchor channels and one millimeter-wave channel; or, the mapping relationship includes a mapping relationship between one anchor channel and one millimeter-wave channel.
21. The method according to any one of claims 18 to 20, characterized in that, The anchor point channel is used to publish management frames, which are used to manage the millimeter-wave channel.
22. The method according to claim 21, characterized in that, The mapping relationship includes a mapping relationship between multiple anchor point channels and a millimeter wave channel, and the management frame is broadcast at least once on multiple or each or all anchor point channels corresponding to the millimeter wave channel.
23. The method according to claim 21, characterized in that, The mapping relationship includes the mapping relationship between multiple anchor channels and a millimeter-wave channel. The management frame is broadcast at least once on the first anchor channel or the first set of anchor channels corresponding to the millimeter-wave channel. Among them, the second station in this BSS operating on the millimeter-wave channel has at least one anchor channel belonging to the first anchor channel or the first set of anchor channels.
24. The method according to any one of claims 18 to 23, characterized in that, The transmission opportunity or channel access of the millimeter-wave channel is determined based on channel contention on the anchor channel.
25. The method according to claim 24, characterized in that, The mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels, and the channel contention is used to simultaneously compete for transmission opportunities on the anchor channel and at least one millimeter-wave channel.
26. The method according to any one of claims 18 to 25, characterized in that, Receiving at least one frame includes: receiving a first frame, the first frame being used to notify the second station of the mapping relationship between the anchor channel and the millimeter-wave channel in this BSS.
27. The method according to any one of claims 18 to 25, characterized in that, The receiving and / or sending of at least one frame includes: receiving a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; sending a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship; and / or, sending a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; and receiving a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship.
28. The method according to claim 26 or 27, characterized in that, The mapping relationship is indicated by one or more of the following fields: default mapping relationship; whether the mapping switch time exists; whether the expected duration exists; the number of mapping relationships; the mapping switch time; the expected duration; one or more mapping relationship fields.
29. The method according to claim 27, characterized in that, The mapping relationship field includes one or more of the following fields: anchor link ID; anchor link channel number; millimeter wave link ID; millimeter wave link channel number.
30. The method according to claim 28 or 29, characterized in that, The field used to indicate the mapping relationship is carried by the first element, or the mapping relationship element, or the anchor channel to the millimeter wave channel mapping relationship element.
31. The method according to any one of claims 18 to 30, characterized in that, The method further includes: after successful channel contention on the anchor channel, sending an ICF frame, the ICF frame being used to inquire whether the channel resource TXOP on the anchor channel and the millimeter wave channel is accessible; and receiving an ICR frame, the ICR frame being used to indicate whether the millimeter wave channel is available.
32. The method according to claim 31, characterized in that, The ICF frame carries one or more of the following fields: millimeter-wave channel request identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time.
33. The method according to claim 31, characterized in that, The ICR frame carries one or more of the following fields: millimeter-wave channel availability identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time; number of idle IFS that need to be detected before accessing the millimeter-wave channel.
34. The method according to any one of claims 18 to 33, characterized in that, The method further includes: when an OBSS MLD is detected being transmitted on the anchor channel, and the OBSS MLD is simultaneously being transmitted on the millimeter-wave channel, if the Received Signal Strength Indication (RSSI) of the PPDU of the OBSS MLD received on the anchor channel is greater than or equal to a first threshold, setting a NAV on the millimeter-wave channel; if the RSSI of the PPDU of the OBSS MLD received on the anchor channel is less than the first threshold, accessing the millimeter-wave channel through channel contention on other anchor channels of the millimeter-wave link; and / or, when the transmission of the same BSS MLD is detected on the anchor channel, and the same BSS MLD is simultaneously being transmitted on the millimeter-wave channel, if the RSSI of the PPDU received on the anchor channel is greater than or equal to a second threshold, setting a NAV on the millimeter-wave channel; wherein the duration of the NAV is the NAV on the millimeter-wave channel or the anchor channel.
35. A first MLD device, characterized in that, The device includes: a first communication module for sending and / or receiving at least one frame, the at least one frame being used to determine a mapping relationship between an anchor channel and a millimeter-wave channel; wherein the anchor channel includes an anchor link or an anchor channel, and the millimeter-wave channel includes a millimeter-wave link or a millimeter-wave channel.
36. The apparatus according to claim 35, characterized in that, The mapping relationship includes at least one of the following four types: the mapping relationship between the anchor link and the millimeter-wave link; the mapping relationship between the anchor channel and the millimeter-wave link; and the mapping relationship between the anchor link and the millimeter-wave channel. The mapping relationship between the anchor channel and the millimeter-wave channel.
37. The apparatus according to claim 35 or 36, characterized in that, The mapping relationship includes a mapping relationship between one anchor channel and multiple millimeter-wave channels; or, the mapping relationship includes a mapping relationship between multiple anchor channels and one millimeter-wave channel; or, the mapping relationship includes a mapping relationship between one anchor channel and one millimeter-wave channel.
38. The apparatus according to any one of claims 35 to 37, characterized in that, The anchor point channel is used to publish management frames, which are used to manage the millimeter-wave channel.
39. The apparatus according to claim 38, characterized in that, The mapping relationship includes a mapping relationship between multiple anchor point channels and a millimeter wave channel, and the management frame is broadcast at least once on multiple or each or all anchor point channels corresponding to the millimeter wave channel.
40. The apparatus according to claim 38, characterized in that, The mapping relationship includes the mapping relationship between multiple anchor channels and a millimeter-wave channel. The management frame is broadcast at least once on the first anchor channel or the first set of anchor channels corresponding to the millimeter-wave channel. Among them, the second station in this BSS operating on the millimeter-wave channel has at least one anchor channel belonging to the first anchor channel or the first set of anchor channels.
41. The apparatus according to any one of claims 35 to 40, characterized in that, The transmission opportunity or channel access of the millimeter-wave channel is determined based on channel contention on the anchor channel.
42. The apparatus according to claim 41, characterized in that, The mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels, and the channel contention is used to simultaneously compete for transmission opportunities on the anchor channel and at least one millimeter-wave channel.
43. The apparatus according to any one of claims 35 to 42, characterized in that, The first communication module includes: a first transmitting module, used to transmit a first frame via broadcast, the first frame being used to notify one or more second stations of the mapping relationship between the anchor channel and the millimeter-wave channel in this BSS.
44. The apparatus according to any one of claims 35 to 42, characterized in that, The first communication module includes: a first receiving module for receiving a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; a first sending module for sending a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship; and / or, a second sending module for sending a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; and a second receiving module for receiving a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship.
45. The apparatus according to claim 43 or 44, characterized in that, The mapping relationship is indicated by one or more of the following fields: default mapping relationship; whether the mapping switch time exists; whether the expected duration exists; the number of mapping relationships; the mapping switch time; the expected duration; one or more mapping relationship fields.
46. The apparatus according to claim 44, characterized in that, The mapping relationship field includes one or more of the following fields: anchor link ID; anchor link channel number; millimeter wave link ID; millimeter wave link channel number.
47. The apparatus according to claim 45 or 46, characterized in that, The field used to indicate the mapping relationship is carried by the first element, or the mapping relationship element, or the anchor channel to the millimeter wave channel mapping relationship element.
48. The apparatus according to any one of claims 35 to 47, characterized in that, The device further includes: a third receiving module for receiving an ICF frame, the ICF frame being used to inquire whether channel resources or transmission opportunities (TXOPs) on the millimeter-wave channel are available; and a third transmitting module for transmitting an ICR frame, the ICR frame being used to indicate whether the millimeter-wave channel is available; wherein the ICF frame is transmitted by the second station after successfully competing for the channel on the anchor channel.
49. The apparatus according to claim 48, characterized in that, The ICF frame carries one or more of the following fields: millimeter-wave channel request identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time.
50. The apparatus according to claim 48, characterized in that, The ICR frame carries one or more of the following fields: millimeter-wave channel availability identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time; number of idle IFS that need to be detected before accessing the millimeter-wave channel.
51. The apparatus according to any one of claims 35 to 50, characterized in that, The apparatus further includes: a first processing module, configured to, when monitoring the transmission of an Overlapping Basic Service Set Multilink Device (OBSS MLD) on the anchor channel, and the OBSS MLD is simultaneously transmitted on the millimeter-wave channel, set a Network Allocation Vector (NAV) on the millimeter-wave channel if the Received Signal Strength Indication (RSSI) of the Physical Layer Protocol Data Unit (PPDU) of the OBSS MLD received on the anchor channel is greater than or equal to a first threshold; and if the RSSI of the PPDU of the OBSS MLD received on the anchor channel is less than the first threshold, access the millimeter-wave channel through channel contention on other anchor channels of the millimeter-wave link; and / or, the first processing module, configured to, when monitoring the transmission of a Basic Service Set Multilink Device (BSS MLD) on the anchor channel, and the BSS MLD is simultaneously transmitted on the millimeter-wave channel, set a NAV on the millimeter-wave channel if the RSSI of the PPDU received on the anchor channel is greater than or equal to a second threshold; wherein the duration of the NAV is the NAV on the millimeter-wave channel or the anchor channel.
52. A second MLD device, characterized in that, The device includes: a first communication module for sending and / or receiving at least one frame, the at least one frame being used to determine a mapping relationship between an anchor channel and a millimeter-wave channel; wherein the anchor channel includes an anchor link or an anchor channel, and the millimeter-wave channel includes a millimeter-wave link or a millimeter-wave channel.
53. The apparatus according to claim 52, characterized in that, The mapping relationship includes at least one of the following four types: the mapping relationship between the anchor link and the millimeter-wave link; the mapping relationship between the anchor channel and the millimeter-wave link; and the mapping relationship between the anchor link and the millimeter-wave channel. The mapping relationship between the anchor channel and the millimeter-wave channel.
54. The apparatus according to claim 52 or 53, characterized in that, The mapping relationship includes a mapping relationship between one anchor channel and multiple millimeter-wave channels; or, the mapping relationship includes a mapping relationship between multiple anchor channels and one millimeter-wave channel; or, the mapping relationship includes a mapping relationship between one anchor channel and one millimeter-wave channel.
55. The apparatus according to any one of claims 52 to 54, characterized in that, The anchor point channel is used to publish management frames, which are used to manage the millimeter-wave channel.
56. The apparatus according to claim 55, characterized in that, The mapping relationship includes a mapping relationship between multiple anchor point channels and a millimeter wave channel, and the management frame is broadcast at least once on multiple or each or all anchor point channels corresponding to the millimeter wave channel.
57. The apparatus according to claim 55, characterized in that, The mapping relationship includes the mapping relationship between multiple anchor channels and a millimeter-wave channel. The management frame is broadcast at least once on the first anchor channel or the first set of anchor channels corresponding to the millimeter-wave channel. Among them, the second station in this BSS operating on the millimeter-wave channel has at least one anchor channel belonging to the first anchor channel or the first set of anchor channels.
58. The apparatus according to any one of claims 52 to 57, characterized in that, The transmission opportunity or channel access of the millimeter-wave channel is determined based on channel contention on the anchor channel.
59. The apparatus according to claim 58, characterized in that, The mapping relationship includes a mapping relationship between an anchor channel and multiple millimeter-wave channels, and the channel contention is used to simultaneously compete for transmission opportunities on the anchor channel and at least one millimeter-wave channel.
60. The apparatus according to any one of claims 52 to 59, characterized in that, The first communication module includes: a first receiving module, used to receive a first frame, the first frame being used to notify the second station of the mapping relationship between the anchor channel and the millimeter-wave channel in this BSS.
61. The apparatus according to any one of claims 52 to 59, characterized in that, The first communication module includes: a first receiving module for receiving a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; a first sending module for sending a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship; and / or, a second sending module for sending a request frame, the request frame being used to request a mapping relationship between the anchor channel and the millimeter-wave channel; and a second receiving module for receiving a response frame, the response frame being used to indicate acceptance or rejection of the requested mapping relationship.
62. The apparatus according to claim 60 or 61, characterized in that, The mapping relationship is indicated by one or more of the following fields: default mapping relationship; whether the mapping switch time exists; whether the expected duration exists; the number of mapping relationships; the mapping switch time; the expected duration; one or more mapping relationship fields.
63. The apparatus according to claim 61, characterized in that, The mapping relationship field includes one or more of the following fields: anchor link ID; anchor link channel number; millimeter wave link ID; millimeter wave link channel number.
64. The apparatus according to claim 62 or 63, characterized in that, The field used to indicate the mapping relationship is carried by the first element, or the mapping relationship element, or the anchor channel to the millimeter wave channel mapping relationship element.
65. The apparatus according to any one of claims 52 to 64, characterized in that, The apparatus further includes: a second transmitting module, configured to transmit an ICF frame after successful channel contention on the anchor channel, the ICF frame being used to inquire whether the channel resource TXOP on the anchor channel and the millimeter-wave channel is accessible; and a second receiving module, configured to receive an ICR frame, the ICR frame being used to indicate whether the millimeter-wave channel is available.
66. The apparatus according to claim 65, characterized in that, The ICF frame carries one or more of the following fields: millimeter-wave channel request identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time.
67. The apparatus according to claim 65, characterized in that, The ICR frame carries one or more of the following fields: millimeter-wave channel availability identifier; millimeter-wave link ID; millimeter-wave channel number; millimeter-wave TXOP; start time; number of idle IFS that need to be detected before accessing the millimeter-wave channel.
68. The apparatus according to any one of claims 52 to 67, characterized in that, The device further includes: a processing module, configured to: when an OBSS MLD is detected being transmitted on the anchor channel and simultaneously transmitted on the millimeter-wave channel, set a NAV on the millimeter-wave channel if the Received Signal Strength Indication (RSSI) of the Physical Layer Protocol Data Unit (PPDU) of the OBSS MLD received on the anchor channel is greater than or equal to a first threshold; if the RSSI of the PPDU of the OBSS MLD received on the anchor channel is less than the first threshold, access the millimeter-wave channel through channel contention on other anchor channels of the millimeter-wave link; and / or, when the same BSS MLD is detected being transmitted on the anchor channel and simultaneously transmitted on the millimeter-wave channel, set a NAV on the millimeter-wave channel if the RSSI of the PPDU received on the anchor channel is greater than or equal to a second threshold; wherein the duration of the NAV is the NAV on the millimeter-wave channel or the anchor channel.
69. A first MLD, characterized in that, The first MLD includes: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the memory is used to store a program, the processor is used to call the program in the memory, and control the transceiver to receive or send signals, so that the first MLD executes the millimeter-wave-based multi-link communication method as described in any one of claims 1 to 17.
70. A second MLD, characterized in that, The second MLD includes: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the memory is used to store a program, the processor is used to call the program in the memory, and control the transceiver to receive or send signals, so that the second MLD performs the millimeter-wave-based multi-link communication method as described in any one of claims 18 to 34.
71. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one program, which is loaded and executed by a processor to implement the millimeter-wave-based multi-link communication method as described in any one of claims 1 to 17; and / or, the millimeter-wave-based multi-link communication method as described in any one of claims 18 to 34.
72. A chip, characterized in that, The chip includes programmable logic circuitry and / or program instructions, which, when the chip is run on a communication device, implement the millimeter-wave-based multi-link communication method as described in any one of claims 1 to 17; and / or, the millimeter-wave-based multi-link communication method as described in any one of claims 18 to 34.
73. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium; the processor of the communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to implement the millimeter-wave-based multi-link communication method according to any one of claims 1 to 17; and / or, the millimeter-wave-based multi-link communication method according to any one of claims 18 to 34.
74. A computer program, characterized in that, The computer program is executed by the processor of the communication device to implement the millimeter-wave-based multi-link communication method as described in any one of claims 1 to 17; and / or, the millimeter-wave-based multi-link communication method as described in any one of claims 18 to 34.
