Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first device sending a first frame over a first link, wherein the first frame is used by the first device to make a request to send data to a second device over a millimeter wave link. Directional transmission of millimeter waves may cause the problem of a "hidden node", which is specific to millimeter wave links. In the present application, a first frame is transmitted by means of another link (i.e., a first link) that is different from a millimeter wave link, such that the transmission of the first frame is not affected by directional transmission, and thus more other devices can monitor the first frame, thereby avoiding the problem of the "hidden node".

Description

Wireless communication method and communication device TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, and more particularly, to a wireless communication method and a communication device. BACKGROUND

[0002] Millimeter wave (MMW) has many attractive advantages, and there is abundant spectrum in most areas. Moreover, the directional transmission and large propagation loss of millimeter wave result in low interference level and more multiplexing opportunities. However, the above characteristics of millimeter wave also lead to some problems.

[0003] SUMMARY

[0004] The present application provides a wireless communication method and a communication device. The various aspects involved in the present application are described below.

[0005] In a first aspect, a wireless communication method is provided. The method comprises: a first device sending a first frame on a first link; wherein the first frame is used for the first device to request to send data to a second device on a millimeter wave link.

[0006] In a second aspect, a wireless communication method is provided. The method comprises: a second device receiving a first frame sent by a first device on a first link; wherein the first frame is used for the first device to request to send data to the second device on a millimeter wave link.

[0007] In a third aspect, a wireless communication method is provided. The method comprises: a third device listening to a first frame and / or a second frame on a first link; wherein the first frame is used for a first device to request to send data to a second device on a millimeter wave link, and the second frame is used to indicate that the second device accepts or rejects the request of the first frame.

[0008] In a fourth aspect, a communication device is provided. The communication device is a first device. The communication device comprises: a sending unit configured to send a first frame on a first link; wherein the first frame is used for the first device to request to send data to a second device on a millimeter wave link.

[0009] In a fifth aspect, a communication device is provided. The communication device is a second device. The communication device comprises: a receiving unit configured to receive a first frame sent by a first device on a first link; wherein the first frame is used for the first device to request to send data to the second device on a millimeter wave link.

[0010] In a sixth aspect, a communication device is provided. The communication device is a third device. The communication device comprises a listening unit configured to listen to a first frame and / or a second frame over a first link, wherein the first frame is used to request a second device to transmit data over a millimeter wave link, and the second frame is used to indicate that the second device accepts or rejects the request of the first frame.

[0011] In a seventh aspect, a communication device is provided, comprising a processor and a memory, the memory being configured to store one or more computer programs, and the processor being configured to invoke the computer programs in the memory to cause the communication device to perform some or all of the steps in the methods of the various aspects described above.

[0012] In an eighth aspect, a communication system is provided, comprising the communication device described above. In another possible design, the system can further comprise other devices interacting with the communication device in the solutions provided by the embodiments.

[0013] In a ninth aspect, a computer-readable storage medium is provided, which stores a computer program. The computer program causes a communication device to perform some or all of the steps in the methods of the various aspects described above.

[0014] In a tenth aspect, a computer program product is provided, which comprises a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to cause a communication device to perform some or all of the steps in the methods of the various aspects described above. In some implementations, the computer program product can be a software installation package.

[0015] In an eleventh aspect, a chip is provided, which comprises a memory and a processor. The processor can invoke and run a computer program from the memory to perform some or all of the steps described in the methods of the various aspects described above.

[0016] Directional transmission of millimeter waves can cause the problem of "hidden nodes" specific to millimeter wave links. By transmitting the first frame over a link different from the millimeter wave link (i.e., the first link), the transmission of the first frame can be unaffected by the characteristics of directional transmission of millimeter waves, so that more other devices can listen to the first frame, thereby avoiding the problem of "hidden nodes" described above. BRIEF DESCRIPTION OF DRAWINGS

[0017] FIG. 1 is a schematic diagram of a wireless communication system to which embodiments of the present application are applied.

[0018] FIG. 2 is an example diagram of a format of a request to send (RTS) frame.

[0019] FIG. 3 is an example diagram of a format of a clear to send (CTS) frame.

[0020] FIG. 4 is an example diagram of a format of another CTS frame.

[0021] FIG. 5 is an example diagram of a format of a DTS frame.

[0022] FIG. 6 is an example diagram of a possible hidden node scenario in millimeter wave link transmission.

[0023] FIG. 7 is a schematic flow chart of a wireless communication method according to an embodiment of the present application.

[0024] FIG. 8 is a schematic flow chart of another wireless communication method according to an embodiment of the present application.

[0025] FIG. 9 is an example diagram of a format of a cross-link DTS frame according to an embodiment of the present application.

[0026] FIG. 10 is an example diagram of a format of a link identification information field.

[0027] FIG. 11 is an example diagram of a format of a second frame according to an embodiment of the present application.

[0028] FIG. 12 is an example diagram of a format of a first frame according to an embodiment of the present application.

[0029] FIG. 13 is an example diagram of a format of a frame control field.

[0030] FIG. 14 is an example diagram of a communication process according to Embodiment 1.

[0031] FIG. 15 is an example diagram of another communication process according to Embodiment 1.

[0032] FIG. 16 is an example diagram of a communication process according to Embodiment 2.

[0033] FIG. 17 is an example diagram of another communication process according to Embodiment 2.

[0034] FIG. 18 is an example diagram of a communication process according to Embodiment 3.

[0035] FIG. 19 is an example diagram of another communication process according to Embodiment 3.

[0036] FIG. 20 is a schematic structural diagram of a communication device according to an embodiment of the present application.

[0037] FIG. 21 is a schematic structural diagram of another communication device according to an embodiment of the present application.

[0038] FIG. 22 is a schematic structural diagram of another communication device according to an embodiment of the present application.

[0039] FIG. 23 is a schematic structural diagram of an apparatus for communication provided by an embodiment of the present application. DETAILED DESCRIPTION

[0040] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0041] Communication system

[0042] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a wireless local area network (WLAN), a wireless fidelity (WiFi), a high performance radio local area network (HIPELAN), a wide area network (WAN), a cellular network or other communication systems, etc. For example, the technical solutions provided by the embodiments of the present application can be applied to a communication system using an 802.11 standard. Exemplarily, the 802.11 standard includes but is not limited to an 802.11ax standard, an 802.11be standard, a more next generation 802.11 standard, etc.

[0043] FIG. 1 shows a schematic diagram of a communication system to which the embodiments of the present application are applicable. Referring to FIG. 1, the communication devices in the communication system 100 can include an access point (AP) 111, an AP 112, and a station (STA) 121 and a STA 122, wherein the STA 121 can access a network through the AP 111, and the STA 122 can access a network through the AP 112.

[0044] In some implementations, a STA can establish an association relationship with one or more APs, and then the STA and the APs having the association relationship can communicate with each other. Referring to FIG. 1, the AP 111 and the STA 121 can communicate with each other after establishing an association relationship, and the AP 112 and the STA 122 can communicate with each other after establishing an association relationship.

[0045] In some implementations, the communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between non-AP STAs, or communication between a STA and a peer STA, wherein the peer STA can refer to a device communicating with the STA at the opposite end, for example, the peer STA can be an AP or a non-AP STA.

[0046] It should be understood that FIG. 1 exemplarily shows two AP STAs and two non-AP STAs, the communication system 100 can also include a larger number of AP STAs, or the communication system 100 can include other numbers of non-AP STAs, and embodiments of the present application do not limit this.

[0047] In addition, the above communication system can be applied to a multi-device cooperation scenario, such as a multi-AP (multiple access points, multi-AP) cooperation scenario, or a multi-site cooperation scenario.

[0048] In embodiments of the present application, the names of APs and / or STAs are not limited. In some scenarios, an AP can also be referred to as an AP STA, that is, in a certain sense, an AP is also a kind of STA. In other scenarios, a STA can also be referred to as a non-AP STA (non-AP STA).

[0049] In some scenarios, the above communication device can also be a "multi-link device (multi-link device, MLD)", that is, a device that can communicate through multiple communication links, where the multiple communication links can include communication links of different frequency bands, for example, can include millimeter wave frequency bands and / or low frequency frequency bands. Generally, if the multi-link device is an AP, the AP can also be referred to as a "multi-link AP". If the multi-link device is a STA, the STA can also be referred to as a "multi-link STA".

[0050] In embodiments of the present application, the AP can be a device in a wireless network. The AP can be a communication server, a router, a switch, a bridge, or the like, or the AP can include various forms of macro base stations, micro base stations, relay stations, etc., and of course the AP can also be a chip or circuit or processing system in these various forms of devices, thereby implementing the methods and functions of embodiments of the present application. The AP can be applied to various scenarios, such as sensor nodes in smart cities (such as smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, televisions, sound systems, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as AR, VR, etc. wearable devices), smart devices in smart offices (such as printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, some infrastructure in daily life (such as vending machines, self-service navigation stations in supermarkets, self-service checkout devices, self-service ordering machines), etc.

[0051] In some implementations, the role of a STA in a communication system is not absolute, and in some scenarios, a STA can act as an AP. For example, in a scenario where a phone connects to a router, the phone can be a non-AP STA, while in a scenario where the phone acts as a hotspot for other phones, the phone acts as an AP.

[0052] In the embodiments of the present application, the STA in the embodiments of the present application can be a device with wireless transceiving function, for example, can support 802.11 series protocols, and can communicate with an AP or other STAs. For example, the STA is any user communication device that allows a user to communicate with an AP and then communicate with a WLAN. The STA is, for example, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile terminal, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user equipment, etc.

[0053] The STA in the embodiments of the present application can also be a device providing voice / data connectivity to a user, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc. For example, a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application are not limited thereto.

[0054] By way of example and not limitation, in the embodiments of the present application, the STA can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. For example, a smart watch or smart glasses, etc., and only focus on a certain type of application function, need to be used with other devices such as a smart phone, such as various types of smart wristbands, smart jewelry, etc.

[0055] In addition, in the embodiments of the present application, the STA can also be a terminal device in an internet of things (IoT) system. The IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network, so as to realize the intelligent network of man-machine interconnection and object-object interconnection. In the embodiments of the present application, the IoT technology can achieve massive connection, deep coverage and terminal power saving through, for example, narrow band (NB) technology.

[0056] In addition, in the embodiments of the present application, the STA can be a device in a vehicle-to-everything (V2X) system. The communication mode in the V2X system is collectively referred to as V2X (X represents anything). For example, the V2X communication includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication or vehicle-to-network (V2N) communication, etc.

[0057] In addition, in the embodiments of the present application, the STA can also include a smart printer, a train detector, a gas station sensor, and the like. The main functions include collecting data (part of the terminal device), receiving control information and downlink data of the AP, and transmitting electromagnetic waves to transmit data to the AP.

[0058] In addition, the AP in the embodiments of the present application can be a device for communicating with the STA. The AP can be a network device in a wireless local area network, and the AP can be used for communicating with the STA through the wireless local area network.

[0059] From the perspective of the communication mode supported by the AP, in some implementation manners, the AP can be a device supporting the 802.11be mode. The AP can also be a device supporting multiple current and future WLAN modes of the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.

[0060] From the perspective of the communication mode supported by the STA, in some implementation manners, the non-AP STA can support the 802.11be mode. The non-AP STA can also support multiple current and future WLAN modes of the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.

[0061] In the embodiments of the present application, the frequency bands supported by the WLAN technology are not limited. In some implementations, the frequency bands supported by the WLAN technology can include, but are not limited to, low frequency bands (such as 2.4 GHz, 5 GHz, 6 GHz), high frequency bands (such as 45 GHz, 60 GHz).

[0062] It should be understood that the specific forms of the STA and the AP in the embodiments of the present application are not specially limited, and are only exemplary described herein.

[0063] RTS / CTS mechanism

[0064] The RTS / CTS mechanism is mainly used to solve the problem of "hidden nodes" in a wireless network, that is, two or more devices simultaneously send data to the same receiving device under the condition of being invisible to each other (for example, far away), which may cause signal conflict and data loss.

[0065] The working principle of the RTS / CTS mechanism mainly includes: when the sending device is ready to send data to the receiving device, an RTS frame will be sent first. The RTS frame contains the medium access control (MAC) address of the sending device, the MAC address of the receiving device, and the duration information of the data frame to be sent. According to the above information in the RTS frame, all stations receiving the RTS frame can update their network allocation vectors (NAVs) to reserve the corresponding time period for not sending data.

[0066] The receiving device of the RTS frame will check whether the current channel is available after receiving the RTS frame. If the channel is available and the receiving device is ready to receive data, the receiving device can respond to a CTS frame. Similar to the RTS frame, the CTS frame also contains duration information and receiver address, which informs all STAs listening to the CTS frame (except the device sending the RTS frame) to reserve the channel until the specified duration ends.

[0067] The sending device of the RTS frame will only start sending the actual data frame after a short interframe space (SIFS) after successfully receiving the CTS frame. Once the data frame is correctly received, the receiving device will send an acknowledgment (ACK) frame to the sending device. This is to inform the sending device that the data has been successfully received, thereby completing the data exchange process.

[0068] The RTS / CTS mechanism is generally not used for short frame transmissions, mainly because the introduction of additional control frames increases the overhead of the network, which can reduce overall efficiency, especially when dealing with shorter data packets. Based on this, the RTS / CTS mechanism specifies the conditions for triggering the RTS / CTS handshake process.

[0069] In the related art, the parameter dot11RTSThreshold strictly defines the conditions for triggering the RTS / CTS handshake process. When a station is preparing to send a media access control protocol data unit (MPDU), the station can evaluate the total byte length of the physical layer service data unit (PSDU) to which the MPDU belongs in advance. Once the size of the PSDU exceeds the threshold indicated by the preset dot11RTSThreshold, the STA will send an RTS frame in advance to solicit explicit permission from the receiver before actually starting data transmission. In the case where the size of the PSDU is less than the threshold indicated by the parameter dot11RTSThreshold, the STA will directly start data transmission without sending an RTS frame.

[0070] Under the framework of some communication protocols (such as Wi-Fi 6), the RTS / CTS mechanism is further optimized. For example, the conditions for triggering the RTS / CTS handshake process incorporate considerations based on transmission opportunity (TXOP) duration. When a STA intends to transmit data to an AP or other peer STA, and the expected TXOP duration exceeds the set dot11TXOPDurationRTSThreshold limit, the RTS / CTS handshake will be enforced to ensure efficient spectrum utilization and reduce potential conflicts, thereby optimizing overall network performance and reliability. This improvement not only refines the triggering logic of RTS / CTS, but also enhances coordination and communication efficiency in high-efficiency wireless network environments.

[0071] In some embodiments, the STA can distinguish whether to use the RTS / CTS mechanism according to the byte length of the PSDU or the TXOP duration based on the set dot11TXOPDurationRTSThreshold value. If the dot11TXOPDurationRTSThreshold is 1023 or does not exist, the STA can decide whether to enable RTS / CTS according to the PSDU length; if the dot11TXOPDurationRTSThreshold exists and is not 1023, the STA can decide whether to enable RTS / CTS according to the required TXOP duration.

[0072] The frame structure of the RTS frame and the CTS frame will be described below.

[0073] FIG. 2 is an example diagram of a format of an RTS frame. As shown in FIG. 2, the RTS frame can include the following fields: frame control, duration, receiver address (RA), transmission address (TA), frame check sequence (FCS).

[0074] In the RTS frame, part of bits in the frame control field is defined as: B3 and B2 of the Type field are 0 and 1, respectively (Type value (B3B2) = 01), and B7-B4 of the Subtype field are 1011, respectively (Subtype value (B7B6B5B4) = 1011).

[0075] The duration field can indicate the time required to transmit the pending data frames or management frames. If the calculated duration contains a fractional microsecond, the value is rounded to the next larger integer.

[0076] The RA field is the address of the target receiver, and the TA field is the address of the transmitter. It should be noted that when the RTS frame is transmitted in a non-ht or non-ht duplicate format by a very high-throughput (VHT) STA or a high-efficiency (HE) STA (11ax) to another VHT STA or HE STA (11ax), the TA field can be bandwidth signaling.

[0077] FIG. 3 is an example diagram of a format of a CTS frame. As shown in FIG. 3, the CTS frame can include the following fields: frame control, duration, RA, FCS.

[0078] In the CTS frame, part of bits in the frame control field can be defined as Type value (B3B2) = 01, Subtype value (B7B6B5B4) = 1100.

[0079] When the CTS frame is a response to the RTS frame, the RA field of the CTS frame is set to the address of the TA field of the RTS frame.

[0080] The duration field can be: the value obtained from the duration field of the responding RTS frame, minus the time required to transmit the CTS frame and its SIFS. If the calculated duration contains a fractional microsecond, the value is rounded to the next larger integer.

[0081] FIG. 4 is an example diagram of a format of another CTS frame. The CTS frame shown in FIG. 4 can be, for example, a directional multi-gigabit (DMG) CTS frame. As shown in FIG. 4, the CTS frame can include the following fields: frame control, duration, RA, TA, FCS.

[0082] In the DMG CTS frame, part of the bits in the frame control field are defined as Type value (B3B2) = 01, Subtype value (B7B6B5B4) = 0110, and B11-B8 of the Control Frame Extension field are (Control Frame Extension value (B11B10B9B8) = 0101), respectively.

[0083] When the CTS frame shown in FIG. 4 is a response to an RTS frame, the TA field is the MAC address of the STA that transmits the DMG CTS frame, and the RA field is set to the address of the TA field of the RTS frame.

[0084] As described above, the CTS frame can be used for the receiver to confirm acceptance of the request of the RTS frame. For a millimeter wave link, the related art also proposes a DTS frame. The DTS frame can be used to respond to the RTS frame, and the DTS frame is used for the receiver to reject the request of the RTS frame.

[0085] FIG. 5 is an example diagram of a format of a DTS frame. The DTS frame shown in FIG. 5 can also be referred to as a DMG DTS frame. As shown in FIG. 5, the DTS frame can include the following fields: frame control, duration, RA, NAV-SA, NAV-DA, FCS.

[0086] In the DTS frame, part of the bits in the frame control field are defined as Type value (B3B2) = 01, Subtype value (B7B6B5B4) = 0110, and Control Frame Extension value (B11B10B9B8) = 0110.

[0087] The duration field can be set to the time remaining in the NAV when the transmission of the DTS frame ends.

[0088] The NAV-SA field and the NAV-DA field can contain the MAC addresses of the source device and the destination device, respectively.

[0089] millimeter wave

[0090] Millimeter wave has many attractive features. For example, millimeter wave has abundant spectrum in most areas. In addition, the directional transmission and large propagation loss of millimeter wave result in low interference level and more multiplexing opportunities. Therefore, more and more researches are focused on millimeter wave. In particular, recent researches focus on integrated millimeter wave (IMMW).

[0091] Millimeter wave can work in the high frequency band described above. Therefore, the millimeter wave link can include a high frequency link. For example, the millimeter wave link can include a 45 GHz link or a 60 GHz link.

[0092] The directional transmission feature of millimeter wave will introduce a new "hidden node" problem. The "hidden node" problem of millimeter wave is illustrated below in conjunction with FIG. 6.

[0093] In FIG. 6, the coverage of the AP can cover the locations of STA1-STA4. In FIG. 6, the AP wants to communicate with STA1 through a millimeter wave link. Due to the directional transmission feature of millimeter wave, the RTS frame and the CTS frame transmitted between the AP and STA1 can only be received by the STAs (including STA2 and STA3) in coverage 1 and coverage 2 (framed by the oval box). STA4 cannot receive the RTS frame and the CTS frame, and thus cannot update the NAV. During the data transmission between the AP and STA1, STA2 and STA3 will not transmit data according to the updated NAV based on the RTS frame or the CTS frame. STA4 can transmit data because the NAV is not updated, resulting in a collision of data transmission and causing the data transmission to fail.

[0094] FIG. 7 and FIG. 8 are schematic flowcharts of a wireless communication method provided by embodiments of the present application, respectively, to solve the above problem.

[0095] The method shown in FIG. 7 can be performed by a first device and a second device. The first device and the second device can both be the communication device described above. The first device can include, for example, an AP, a non-AP STA. The second device can include, for example, an AP, a non-AP STA. Illustratively, the first device can be an AP, and the second device can be a non-AP STA. Illustratively, the first device can be a non-AP STA, and the second device can be an AP. The first device and the second device can both be MLDs.

[0096] The method shown in FIG. 8 can be performed by a third device. The third device can be the communication device described above. For example, the third device can include an AP, a non-AP STA. The third device can include a device different from the first device and the second device. The third device can be an MLD or a non-MLD.

[0097] The method shown in FIG. 7 can include step S710. The method shown in FIG. 8 can include steps S811 and / or S812.

[0098] At step S710, the first device transmits a first frame on the first link. The second device can receive the first frame on the first link.

[0099] It should be noted that the target receiving device of the first frame is the second device. The first frame can also be listened to or received by other devices. For example, the first frame can be listened to by a third device. As shown in FIG. 8, step S810 can include step S811. At step S811, the third device listens to the first frame on the first link. The third device can or can not receive the first frame.

[0100] The first link can be a link different from the millimeter wave link. For example, the first link can be a low frequency link. Illustratively, the first link can include a sub-7GHz link or a sub-10GHz link.

[0101] The first frame can be used for the first device to request transmission of data to the second device on the millimeter wave link. Thus, the first frame can have the function of an RTS frame, i.e., the first frame can be a kind of RTS frame. Since the first frame is transmitted on the first link, and the first frame requests transmission of data on the millimeter wave link, the first frame is used to indicate a cross-link data transmission request. Based on this, in the case where the first frame is an RTS frame, the RTS frame can be referred to as a cross-link RTS frame.

[0102] By transmitting the first frame on the other link (i.e., the first link) different from the millimeter wave link, the application can make the transmission of the first frame not affected by the directional transmission characteristics of the millimeter wave, so that more other devices can listen to the first frame, thereby avoiding the problem of "hidden node" of the millimeter wave link.

[0103] In addition, the application can negotiate the use right of the millimeter wave link on the first link through the first frame, so as to realize the data transmission of the millimeter wave link, thereby improving the transmission efficiency.

[0104] It should be noted that the millimeter wave link can also be referred to as a high frequency link. Illustratively, the millimeter wave link can be a 45 / 60GHz link. Alternatively, the millimeter wave link can be an integrated millimeter wave (IMMW) link.

[0105] In some embodiments, the first device can expect to receive the second frame on the first link in a first time period. The first device can or can not receive the second frame in the first time period.

[0106] The second device can transmit the second frame on the first link in the first time period.

[0107] The second frame can also be overheard or received by other devices. For example, the second frame can be overheard by a third device. As shown in FIG. 8, step S810 can include step S812. In step S812, the third device overhears the second frame on the first link. The third device can or can not receive the second frame.

[0108] It is noted that step S810 can include step S811 and / or step S812. For example, in a case where the third device can overhear the first frame, step S810 can include step S811. For another example, in a case where the third device can overhear the second frame, step S810 can include step S812. For yet another example, in a case where the third device can overhear both the first frame and the second frame, step S810 can include both step S811 and step S812.

[0109] The second frame can be used to indicate that the second device accepts or rejects the request of the first frame. That is, the second frame can be used to accept the request of the first frame, or the second frame can be used to reject the request of the first frame. For example, if the mmWave link is available, the second device can transmit the second frame to accept the request of the first frame; if the mmWave link is not available, the second device can transmit the second frame to reject the request of the first frame.

[0110] For an example, if the second device cannot access the mmWave link channel due to the NAV of the mmWave link, and the mmWave link NAV source address is not the first device, the second device can feed back the second frame to reject the request of the first frame according to the received first frame.

[0111] In a case where the second frame is used to indicate that the second device accepts the request of the first frame, the second frame can have the function of a CTS frame, i.e., the second frame can be a kind of CTS frame. Since the second frame is transmitted on the first link, but accepts the request for the mmWave link, the second frame can be used to indicate acceptance of the cross-link data transmission request. Based on this, in a case where the first frame is a CTS frame, the CTS frame can be referred to as a cross-link CTS frame. The flow based on the cross-link RTS frame and the cross-link CTS frame can be referred to as a cross-link RTS / CTS flow.

[0112] In a case where the second frame is used to indicate that the second device rejects the request of the first frame, the second frame can have the function of a DTS frame, i.e., the second frame can be a kind of DTS frame. Since the second frame is transmitted on the first link, but the request rejected is for the millimeter wave link, therefore, the second frame can be used to indicate rejection of the cross-link data transmission request. Based on this, in a case where the first frame is a DTS frame, the DTS frame can be referred to as a cross-link DTS frame.

[0113] Optionally, the first time period can be determined based on SIFS. For example, SIFS after the second device receives the first frame, the second device can send the second frame to the first device on the first link. For another example, SIFS after the first device sends the first frame, the first device expects to receive the second frame sent by the second device on the first link.

[0114] Optionally, the first time period can satisfy one or more of the following: predefined, standard specified, network side configured.

[0115] In some embodiments, in a case where the first device includes a non-AP STA, if the first device receives the second frame within the first time period, and the second frame is used to accept the request of the first frame, the millimeter wave link of the first device can switch to an awake state. Wherein, “the millimeter wave link of the first device can switch to an awake state” can be understood as: “the millimeter wave link STA attached to the first device can switch to an awake state”.

[0116] For example, the first device can be an MLD. If the first device is a non-AP MLD, the millimeter wave link STA attached to the non-AP MLD can be in a power saving state. When the first device receives the cross-link CTS frame, or when the cross-link RTS / CTS procedure is completed, the millimeter wave link STA can switch to an awake state.

[0117] In some embodiments, in a case where the second device includes a non-AP STA, if the second device sends the second frame within the first time period, and the second frame is used to accept the request of the first frame, the millimeter wave link of the second device can switch to an awake state. Wherein, “the millimeter wave link of the second device can switch to an awake state” can be understood as: “the millimeter wave link STA attached to the second device can switch to an awake state”.

[0118] For example, the second device can be an MLD. If the second device is a non-AP MLD, the millimeter wave link STA affiliated to the non-AP MLD can be in a power saving state. After the second device sends the cross-link CTS frame, or after the cross-link RTS / CTS process is completed, the millimeter wave link STA can switch to the wake-up state.

[0119] It can be understood that, in a case where the first device receives the second frame and the second frame indicates that the second device accepts the request of the first frame, the first device and the second device can transmit data on the millimeter wave link before the first device and the second device reach an agreement on this and cannot transmit data on the millimeter wave link. Therefore, switching the devices corresponding to the millimeter wave link to the wake-up state after the transmission of the second frame succeeds can enable the millimeter wave link to wake up when data needs to be transmitted, thereby effectively reducing the power consumption of the millimeter wave link.

[0120] It should be noted that “switching to the wake-up state” can be understood as “switching from the non-wake-up state to the wake-up state”.

[0121] In some embodiments, the millimeter wave link of the first device can switch to the non-wake-up state after the TXOP of the millimeter wave link ends.

[0122] In some embodiments, the millimeter wave link of the second device can switch to the non-wake-up state after the TXOP of the millimeter wave link ends.

[0123] For example, the wake-up state described in the present application can be a full-capability state, that is, the communication device can transmit signals based on the highest capability of the device. Alternatively, the wake-up state described in the present application may, for example, be a high-capability state, that is, the communication device can transmit signals based on the higher capability of the device. Alternatively, in the wake-up state, the communication device can transmit data.

[0124] For example, the non-wake-up state described in the present application can be a doze state. Alternatively, the non-wake-up state described in the present application may, for example, be a low-capability state, that is, the communication device can transmit signals based on the lower capability of the device. Alternatively, in the non-wake-up state described in the present application, the communication device cannot transmit any signals. Alternatively, in the non-wake-up state described in the present application, the communication device cannot transmit data and can only transmit part of the non-data signals.

[0125] In some embodiments, if the second frame is used to reject the request of the first frame, the second frame can indicate a first time length. The first time length can be used to indicate a time length during which the second device cannot receive or transmit data on the millimeter wave link.

[0126] Exemplarily, the first duration can be used to indicate a first timer duration of the second device. In a case that the first timer does not expire, the second device cannot receive or transmit data on the mmWave link. For example, the first timer can be a NAV timer of the second device for the mmWave link, and the first duration can be a remaining duration of the NAV timer after the second frame is transmitted. That is, if the second frame is used to reject the request of the first frame, the second frame can indicate a NAV of the mmWave link.

[0127] Based on the first duration, the first device can determine a duration that the mmWave link of the second device is unavailable, and thus perform corresponding operations according to the first duration. Optionally, after the first duration ends, the first device can repeatedly transmit the first frame. Optionally, within the first duration, the first device can not transmit the first frame. It can be understood that the first device can transmit the first frame to request data transmission on the mmWave link after the mmWave link of the second device is available, which can avoid resource waste caused by unnecessary transmission of the first frame when the mmWave link of the second device is unavailable.

[0128] The first duration can be carried in a first field of the second frame. The first field can occupy, for example, 2 bytes. Optionally, the first field is also referred to as an MMW-duration field.

[0129] As described above, if the second frame is used to reject the request of the first frame, the second frame can be a cross-link DTS frame. The format of the cross-link DTS frame is described below in combination with FIG. 9.

[0130] As shown in FIG. 9, the cross-link DTS frame can include one or more of the following fields: frame control, duration, MMW-duration, RA, NAV-SA, NAV-DA, FCS. The descriptions of the fields such as duration, RA, NAV-SA, NAV-DA, or FCS in the cross-link DTS frame are similar to those of the DTS frame described above, and thus are not described herein again.

[0131] It should be noted that the NAV setting of the cross-link DTS frame is due to the exchange of the cross-link RTS frame and the cross-link CTS frame between the source MLD device and the destination MLD device.

[0132] In some embodiments, if the first device does not receive the second frame within the first time period, the second device can repeatedly transmit the first frame.

[0133] Optionally, if the first device does not transmit data on the first link, the first device can perform a backoff retransmission to repeatedly transmit the first frame.

[0134] Optionally, if the first device transmits data on the first link, the first device can directly transmit the first frame within a TXOP of the first link.

[0135] The repeatedly transmitted first frame needs to meet certain conditions, so as to avoid the problem of too many times of repeatedly transmitting the first frame, or improve the success rate of transmission of the first frame. In the case of not meeting the condition, the first device can give up the transmission of the first frame, or give up the transmission of data, or give up the transmission of data on the first link.

[0136] In some embodiments, the repeatedly transmitted first frame can meet one or more of the following: the number of times of repeatedly transmitting is less than or equal to a first threshold; the transmission is within a TXOP of the first link; the first number of times is less than or equal to a second threshold. The first number of times can be the number of times of successfully contending for the TXOP of the first link for repeatedly transmitting the first frame.

[0137] For example, if the first device does not transmit data on the first link, the first device can perform a backoff retransmission on the first link to repeatedly transmit the first frame. If the number of times of performing the backoff retransmission is greater than or equal to the second threshold and the first device still cannot receive the second frame, the first device can give up the transmission of the first frame, or give up the transmission of data, or give up the transmission of data on the first link.

[0138] For another example, if the first device transmits data on the first link, the first device can directly transmit the first frame within the TXOP of the first link until receiving the second frame or the TXOP ends. If the remaining time of the TXOP of the first link is insufficient for transmitting the first frame or the TXOP ends, the first device can contend for the TXOP of the first link again. If the number of times of contending for the TXOP of the first link is greater than or equal to the second threshold and the first device still cannot receive the second frame, the first device can give up the transmission of the first frame, or give up the transmission of data, or give up the transmission of data on the first link.

[0139] For another example, if the number of times of repeatedly transmitting the first frame by the first device is greater than or equal to the first threshold, the first device can give up the transmission of the first frame, or give up the transmission of data, or give up the transmission of data on the first link.

[0140] It should be noted that the first number of times can be the number of times of successfully contending for the TXOP of the first link for transmitting the first frame. Alternatively, the first number of times can include both the number of times of successfully contending and the number of times of unsuccessfully contending.

[0141] It should be noted that the first threshold can be a positive integer. The first threshold can meet one or more of the following: predefined, standard specified, configured by the network side.

[0142] It should be noted that the second threshold can be a positive integer. The second threshold can satisfy one or more of the following: predefined, standard specified, network side configured.

[0143] In some embodiments, the second frame can indicate one or more of the following: the first identifier, the first bandwidth, the second duration, in the case that the second frame is used to accept the request of the first frame. The following are described respectively.

[0144] The first identifier can be used to indicate the link identifier of the millimeter wave link. The first identifier can indicate the link identifier of the millimeter wave link that the second device works on. When the second frame is in response to a certain first frame, the first identifier indicated by the second frame can be the same as the millimeter wave link identifier indicated by the first frame.

[0145] The first identifier can be carried in a link identifier information (link ID Info) field. FIG. 10 is an example diagram of the format of the link identifier information field.

[0146] As shown in FIG. 10, the Link ID Info field can occupy 8 bits. Among them, the first four bits can be referred to as a link identifier (Link ID) subfield. The last four bits can be reserved. The value of the link identifier subfield can be set to the value of the link identifier of the millimeter wave link. The value of the link identifier subfield can be an integer between 0 and 14. For an AP MLD, the link identifier subfield can indicate a certain AP affiliated with the AP MLD according to the basic service set identifier (BSSID) of the AP MLD. Since the BSSID of each affiliated AP is different, each affiliated AP has a unique link identifier. The AP MLD will not assign Link ID = 15 to any affiliated AP, because Link ID = 15 is the link identifier subfield of the reduced neighbor report element, to identify the reporting AP that does not belong to the AP MLD or whose information is unknown.

[0147] The first bandwidth can be used to indicate the working bandwidth of the millimeter wave link. The working bandwidth of the millimeter wave link can include: 80MHz, 160MHz, 320MHz, 640MHz, 1280MHz, 2560MHz, etc.

[0148] The first bandwidth can be carried in a bandwidth indication field. The value of the bandwidth indication field can be the value of the operating bandwidth. For example, the value of the bandwidth indication field can be 80, 160, 320, 640, 1280, 2560, etc. Alternatively, the value of the bandwidth indication field can correspond to the operating bandwidth. Illustratively, the bandwidth indication field can occupy 4 bits. The correspondence between the value of the bandwidth indication field and the bandwidth can be as shown in Table 1. The x in Table 1 can represent 0 or 1.

[0149] Table 1

[0150] The bandwidth 1, the bandwidth 2, the bandwidth 3, or the bandwidth 4 can be: 80 MHz, 160 MHz, 320 MHz, 640 MHz, 1280 MHz, 2560 MHz, etc. The bandwidth 1, the bandwidth 2, the bandwidth 3, and the bandwidth 4 are different bandwidths.

[0151] For example, when the channel bandwidth of the millimeter wave link can be 80 MHz, 160 MHz, 320 MHz, 640 MHz, the bandwidth 1 can be the bandwidth of 80 Mhz; the bandwidth 2 can be the bandwidth of 160 Mhz; the bandwidth 3 can be the bandwidth of 320 Mhz; and the bandwidth 4 can be the bandwidth of 640 Mhz.

[0152] For another example, when the high frequency channel bandwidth is 160 MHz, 320 MHz, 640 MHz, 1280 MHz, the bandwidth 1 can be the bandwidth of 160 Mhz; the bandwidth 2 can be the bandwidth of 320 Mhz; the bandwidth 3 can be the bandwidth of 640 Mhz; and the bandwidth 4 can be the bandwidth of 1280 Mhz.

[0153] For another example, when the high frequency channel bandwidth is 320 MHz, 640 MHz, 1280 MHz, 2560 Mhz, the bandwidth 1 can be the bandwidth of 320 Mhz; the bandwidth 2 can be the bandwidth of 640 Mhz; the bandwidth 3 can be the bandwidth of 1280 Mhz; and the bandwidth 4 can be the bandwidth of 2560 Mhz.

[0154] The second time length can be used to indicate the time length of the second device occupying the millimeter wave link.

[0155] For the third device, the third device can update the time length of the second timer according to the second time length. Before the second timer expires, the third device cannot receive or send data on the millimeter wave link. Alternatively, during the second timer, the third device can expect that the millimeter wave link channel will be occupied by other devices. For example, the third device can update the time length of the second timer to the second time length. Illustratively, the second timer can be a NAV timer of the third device for the millimeter wave link. The second frame indicates the second time length, which can cause the third device not to send data within the second time length, thereby avoiding the conflict caused by simultaneous data transmission on the millimeter wave link, and thereby reducing the probability of millimeter wave link channel conflict.

[0156] It should be noted that when the second time length is greater than the time length of the second timer, the third device can update the second timer. When the second time length is less than or equal to the time length of the second timer, the third device can not update the second timer.

[0157] In some embodiments, the second time length can be determined according to one or more of the following: the time length required to transmit the second frame, the third time length. Wherein the third time length can be used to indicate the time length of the first device occupying the millimeter wave link. For example, the second time length can satisfy: second time length = third time length - (time length required to transmit the second frame + one SIFS time).

[0158] Optionally, the second time length can be carried in the second field of the second frame. The second field may, for example, occupy 2 bytes. Optionally, the second field is also referred to as the MMW duration field.

[0159] FIG. 11 is an example of a format of a second frame provided by an embodiment of the present application. Wherein the second frame is used to accept the request of the first frame, i.e. the second frame shown in FIG. 11 can be a cross-link CTS frame.

[0160] As shown in FIG. 11, the second frame can include one or more of the following fields: frame control, duration, RA, TA, MMW duration link identification information, link identification information, bandwidth indication, FCS. The MMW duration link identification information field is used to indicate the second time length. The link identification information is used to indicate the first identification. The bandwidth indication field is used to indicate the first bandwidth.

[0161] It should be noted that the duration field of the second frame can satisfy: the value indicated by the duration field = the value indicated by the duration field of the first frame - (the time of transmitting one second frame + the time of one SIFS).

[0162] The RA field of the second frame can be set as the TA field of the responding first frame. For example, in the cross-link DTS, the RA field is the TA field of the responding cross-link RTS. The TA field of the second frame can be set as the RA field of the responding first frame. For example, in the cross-link DTS, the TA field is the RA field of the responding cross-link RTS.

[0163] In some embodiments, the first frame is configured to indicate one or more of: a second identification, a second bandwidth, a third duration.

[0164] The second identification can be configured to indicate a link identification of the millimeter wave link. That is, the second identification can be configured to indicate a unique link identification associated with the millimeter wave link on which the data transmission is to be performed. Alternatively, the second identification can indicate a link identification of the millimeter wave link on which the first device is to operate.

[0165] The second identification can be carried in a link identification information field. The link identification information field can be as shown in FIG. 10. The link identification information field has been described in detail above and will not be repeated here.

[0166] The second bandwidth is configured to indicate an operating bandwidth of the millimeter wave link. The first bandwidth can be carried in a bandwidth indication field. The bandwidth indication field has been described in detail above and will not be repeated here.

[0167] The third duration can be configured to indicate a duration for which the first device occupies the millimeter wave link.

[0168] For the third device, the third device can update a duration of a third timer for the millimeter wave link according to the third duration. Wherein, the third device cannot receive or transmit data on the millimeter wave link before the third timer expires. For example, the third device can update the duration of the third timer to the third duration. Illustratively, the third timer can be a NAV timer of the third device for the millimeter wave link. The first frame indicating the third duration can cause the third device to not transmit data within the third duration, thereby avoiding collision caused by simultaneous data transmission on the millimeter wave link, and further reducing the probability of millimeter wave link channel collision.

[0169] It should be noted that when the third duration is greater than the duration of the third timer, the third device can update the third timer. When the third duration is less than or equal to the duration of the third timer, the third device can not update the third timer.

[0170] It should be noted that the third timer and the second timer described above can be the same timer, or can be different timers.

[0171] Optionally, the third duration can be determined based on one or more of: a duration required for transmitting the second frame, a duration required for transmitting the pending data on the mmWave link, a contention time for the mmWave link.

[0172] The contention time for the mmWave link can also be referred to as a high frequency contention time. The high frequency contention time can be determined by a contention window duration minimum value (which can be indicated by a parameter CWmininitial value). For example, the high frequency contention time can be equal to a value of the parameter CWmininitial value multiplied by a value of the parameter aSlotTime.

[0173] Exemplarily, the third duration can satisfy: the third duration = the contention time for the mmWave link + the duration required for transmitting the second frame + one SIFS time + the duration required for transmitting the pending data on the mmWave link.

[0174] The third duration can be carried in a third field of the first frame. The third field can occupy, for example, 2 bytes. Optionally, the third field is also referred to as a MMW duration field.

[0175] FIG. 12 is an example diagram of a format of a first frame provided by an embodiment of the present application. Exemplarily, the first frame shown in FIG. 12 can be a cross-link RTS frame.

[0176] As shown in FIG. 12, the first frame can include one or more of the following fields: frame control, duration, RA, TA, MMW duration, link identification information, bandwidth indication, FCS. The MMW duration field is used to indicate the third duration. The link identification information field is used to indicate the second identification. The bandwidth indication field is used to indicate the second bandwidth.

[0177] It should be noted that if the first device does not transmit data on the first link, the value indicated by the duration field of the first frame can represent the sum of the maximum time for completing transmission of one second frame and one SIFS time. For example, the transmission time is a first value when the second frame is used to accept the request of the first frame, the transmission time is a second value when the second frame is used to reject the request of the first frame, and the maximum time for completing transmission of one second frame can be the larger one of the first value and the second value. Taking the second value as an example, the value indicated by the duration field of the first frame represents the sum of the time for completing transmission of one cross-link DTS frame and one SIFS time.

[0178] It should be noted that if the first device transmits data on the first link, the value indicated by the duration field of the first frame can be used to indicate the remaining time of the TXOP of the first link after completing transmission of the first frame.

[0179] It is to be noted that if the value of the duration field of the first frame is 0, the receiving end can not feedback any frame (e.g. the second frame). If the value of the duration field of the first frame is 0, the sending end also does not expect any frame (e.g. the second frame) feedback by the receiving end.

[0180] In the first frame, the RA field can be set as the MAC address of the receiving end on the first link (i.e. the affiliated device of the second device on the first link). The TA field can be set as the MAC address of the sending end on the first link (i.e. the affiliated device of the first device on the first link).

[0181] In some embodiments, if the third device does not detect that the first device transmits data on the millimeter wave link within the fourth time length, the third device can reset the third timer.

[0182] It is to be noted that resetting a certain timer can mean setting the timer to 0.

[0183] After the first device sends the first frame, the third device can set the third timer, but there can be a case that the first device cannot transmit data on the millimeter wave link (e.g. the first device does not receive the acknowledgement feedback for the request of the first frame after sending the first frame), i.e. within the time of the third timer, neither the first device nor the third device uses the millimeter wave link, resulting in the case that the millimeter wave link is idle but no device uses the millimeter wave link. Based on the analysis, the present application proposes that the third device can determine whether the first device uses the millimeter wave link within a certain time length (i.e. the fourth time length), and if the first device does not use the millimeter wave link, the third device can use the millimeter wave link after resetting the third timer, so as to fully utilize the resources of the millimeter wave link.

[0184] Optionally, the fourth time length can be determined based on one or more of the following information: the contention time for the millimeter wave link, the time length required for transmitting the second frame, the contention delay for the millimeter wave link, the time delay of a signal from a receiving antenna to a physical layer.

[0185] The contention time for the millimeter wave link is as described above, which will not be repeated here.

[0186] The time delay from the reception antenna to the physical layer can include the time delay from the start of the received PPDU at the reception antenna to the PHY layer sending the earliest notification signal. This time delay can be represented by the parameter aRxPHYStartDelay or StartDelayCompensation. StartDelayCompensation is a compromise of the possible values of aRxPHYStartDelay. In this application, StartDelayCompensation can be the length of one time slot (e.g., can be indicated by the parameter aSlotTime). The fourth time length can be determined based on StartDelayCompensation.

[0187] Optionally, in the case that the second frame is used to accept the request of the first frame, the time length required for transmitting the second frame can be used to determine the fourth time length. For example, the time length required for transmitting the second frame can be the time length required for transmitting the cross-link CTS frame (i.e., the duration of the cross-link CTS frame).

[0188] In some embodiments, the value of the fourth time length can be equal to the sum of the following values: one SIFS time, the time length required for transmitting the second frame, the value of the parameter StartDelayCompensation, the initial value of the parameter CWmin multiplied by the value of the parameter aSlotTime.

[0189] In some embodiments, part of the bits in the frame control field can indicate whether the frame is the first frame or the second frame. In the case that the frame is the second frame, part of the bits in the frame control field can also be used to indicate whether the second frame is used to accept the request of the first frame or to reject the request of the first frame. For example, part of the bits in the frame control field can be used to indicate whether the frame is a cross-link RTS frame, a cross-link CTS frame, or a cross-link DTS frame.

[0190] FIG. 13 is an example diagram of the format of a frame control field. As shown in FIG. 13, the frame control field can include one or more of the following fields: protocol version, type, subtype, control frame extension, power management, more data, protected frame, +HTC.

[0191] B3, B2 of the type field, B7, B6, B5, B4 of the subtype field, B11, B10, B9, B8 of the control frame extension field in the frame control field can be used to indicate that the frame is a cross-link RTS frame, a cross-link CTS frame or a cross-link DTS frame. The value of each bit corresponds to the description as shown in Table 4.

[0192] Table 4

[0193] It should be noted that Table 4 is only an example. The value of each bit corresponding to the cross-link RTS frame, the cross-link CTS frame or the cross-link DTS frame can also be other values. In addition, part of the content in Table 4 can also be implemented separately.

[0194] It should be noted that the value of B3, B2 of the type field, the value of B7, B6, B5, B4 of the subtype field, and the value of B11, B10, B9, B8 of the control frame extension field corresponding to the cross-link DTS frame and the DMG DTS frame can be the same. This is because the cross-link DTS frame is transmitted on the first link, and the DMG DTS frame is transmitted on the millimeter wave link (invalid on the first link), that is, both are transmitted on different links, so even if the values of the above bits are the same, they can be distinguished.

[0195] In some embodiments, in the case that the data to be transmitted is greater than or equal to the data threshold, the first device can send the first frame on the first link. That is, in the case that the data to be transmitted exceeds the data threshold, the first device can enable the millimeter wave link to transmit data. Optionally, in the case that the data to be transmitted is less than or equal to the data threshold, the first device can transmit the data to be transmitted on the first link without sending the first frame, that is, without enabling the millimeter wave link to transmit data.

[0196] Optionally, the data threshold can be determined according to the appropriate range of the data transmission amount of the first link.

[0197] In some embodiments, in the case that the expected transmission duration of the data to be transmitted is greater than or equal to the TXOP threshold, the first device can send the first frame on the first link. That is, in the case that the expected transmission duration of the data to be transmitted is greater than or equal to the TXOP threshold, the first device can enable the millimeter wave link to transmit data. Optionally, in the case that the expected transmission duration of the data to be transmitted is less than or equal to the TXOP threshold, the first device can not enable the millimeter wave link to transmit data.

[0198] In some embodiments, the first device can send the first frame on the first link in a case that an expected transmission duration of the data to be transmitted is greater than or equal to a remaining TXOP of the first link. That is, the first device can enable the millimeter wave link to transmit the data in a case that an expected transmission duration of the data to be transmitted is greater than or equal to a remaining TXOP of the first link. Optionally, the first device can not enable the millimeter wave link to transmit the data in a case that an expected transmission duration of the data to be transmitted is less than or equal to a remaining TXOP of the first link.

[0199] In a case that the first device successfully initiates the millimeter wave link (i.e., the first device receives a second frame that accepts the first frame request), the first device can transmit all the data to be transmitted on the millimeter wave link, or the first device can transmit part of the data on the millimeter wave link and transmit part of the data on the first link.

[0200] In some embodiments, the first device can contend for the first link to send the first frame. For example, the first device can send the first frame immediately after successfully contending for the first link. For another example, the first device can first request to transmit data on the first link after successfully contending for the first link, and the first device can send the first frame on the first link after the second device confirms that the data can be transmitted on the first link.

[0201] In some embodiments, the first device can send the first frame on the first link during the transmission of the data on the first link. For example, the first device can send the first frame on the first link during the transmission of the data on the first link if the first device encounters burst data and the previously declared TXOP of the first link is not enough to complete the transmission of the data. Whether to send the first frame or the content of the sent first frame can be determined according to the actual situation and the remaining time of the TXOP of the first link.

[0202] For ease of understanding, the present application is described in detail below in combination with Embodiments 1-3. In Embodiments 1-3, the first link is a low-frequency link, and the millimeter wave link is referred to as a high-frequency link. The first frame includes a cross-link RTS frame. The second frame includes a cross-link CTS frame or a cross-link DTS frame. The first device includes a transmitting end MLD. The second device includes a receiving end MLD. The third device includes other MLD devices, non-MLD devices.

[0203] Embodiment 1

[0204] In Embodiment 1, the cross-link RTS / CTS procedure is enabled immediately after contending for the channel of the low-frequency link. Embodiment 1 only transmits data on the high-frequency link, and the low-frequency link does not transmit data. FIG. 14 and FIG. 15 are cross-link RTS / CTS procedure diagrams provided by Embodiment 1, respectively.

[0205] As shown in FIG. 14, after the transmitting MLD contends for the channel of the low frequency link, the transmitting MLD sends a cross-link RTS frame. If the channel of the current high frequency link can be used, the receiving MLD can feed back a cross-link CTS frame. After the transmitting MLD receives the cross-link CTS frame, it starts to contend for the channel of the high frequency link and transmits data. In this case, the transmitting MLD only performs cross-link RTS / CTS interaction during the TXOP of the low frequency, and after the interaction is completed, it ends the occupation of the low frequency channel. In this case, the transmitting MLD can only transmit data in the high frequency NAV declared by the cross-link RTS / CTS. In this case, the TXOP duration of the high frequency link is greater than that of the low frequency link.

[0206] As shown in FIG. 15, after the transmitting MLD contends for the channel of the low frequency link, the transmitting MLD sends a cross-link RTS frame. If the channel of the current high frequency link cannot be used, the receiving MLD feeds back a cross-link DTS frame according to the received cross-link RTS frame. The transmitting MLD waits for the high frequency link NAV of the receiving MLD to end and then re-enables the cross-link RTS / CTS process (i.e., performs the process shown in FIG. 14 or FIG. 15).

[0207] As shown in FIG. 14 or FIG. 15, other MLD devices or non-MLD devices can update the NAV of the low frequency link according to the duration field in the cross-link RTS frame and / or the cross-link CTS frame. Other MLD devices can update the NAV of the high frequency link according to the MMW duration field in the cross-link RTS frame and / or the cross-link CTS frame.

[0208] Exemplarily, when an MLD STA (e.g., other MLD device) receives a cross-link RTS frame whose RA is not equal to the MAC address of its low frequency link, the MLD STA updates the NAV of its high frequency link. When a cross-link CTS frame is received and its RA is not equal to the MAC address of its low frequency link, the MLD device updates the NAV of its high frequency link. When the high frequency link NAV needs to be updated, the MLD device sets a new high frequency link NAV value according to the MMW-Duration field of the received frame only when and if the new high frequency link NAV value is greater than the current high frequency link NAV value.

[0209] Embodiment 2

[0210] In embodiment 2, the cross-link RTS / CTS procedure is enabled immediately after the low frequency link contends for the channel. Embodiment 2 transmits data on both the high frequency link and the low frequency link.

[0211] FIG. 16 and FIG. 17 are diagrams illustrating the cross-link RTS / CTS procedure provided by embodiment 2, respectively.

[0212] As shown in FIG. 16, after the transmitting MLD contends for the low frequency channel, the RTS / CTS procedure is first performed.

[0213] When the transmitting MLD transmits the RTS frame, if the transmitting MLD fails to receive the feedback CTS frame within a specified time, the transmitting MLD performs an error recovery procedure, i.e., backoff retransmission.

[0214] When the transmitting MLD receives the feedback CTS frame, the transmitting MLD transmits the cross-link RTS frame. If the high frequency channel is available, the receiving MLD feeds back the cross-link CTS frame. When the transmitting MLD receives the cross-link CTS, the transmitting MLD starts to contend for the high frequency channel. In this case, the transmitting MLD declares the NAV duration of the high frequency link on the high frequency channel and the NAV duration of the low frequency link according to its own needs.

[0215] As shown in FIG. 17, after the transmitting MLD contends for the low frequency channel, the RTS / CTS procedure is first performed. When the feedback CTS frame is received, the transmitting MLD transmits the cross-link RTS frame. If the receiving MLD cannot access the high frequency channel due to the high frequency link NAV at this time, and the high frequency link NAV source address is not the transmitting MLD, the receiving MLD feeds back the cross-link DTS frame according to the received cross-link RTS frame. The transmitting MLD transmits data on the low frequency channel, and waits for the high frequency link NAV of the receiving MLD to end before re-enabling the cross-link RTS / CTS procedure.

[0216] As shown in FIG. 16 or FIG. 17, other MLD devices or non-MLD devices can update the NAV of the low frequency link according to the duration field in the RTS frame and / or the CTS frame. Other MLD devices can update the NAV of the high frequency link according to the MMW duration field in the cross-link RTS frame and / or the cross-link CTS frame.

[0217] Embodiment 3

[0218] Embodiment 3 shows an embodiment of enabling cross-link RTS / CTS procedure in the transmission process of the low-frequency link. The scenario applicable to Embodiment 3 may, for example, be that the transmitting MLD encounters burst data during the transmission of low-frequency data, and the pre-declared low-frequency TXOP duration is insufficient to complete the data transmission. The transmitting MLD may, according to the actual situation and the remaining time of the TXOP, enable cross-link RTS / CTS, and transmit data using the high-frequency link.

[0219] FIG. 18 and FIG. 19 are schematic diagrams of the cross-link RTS / CTS procedure provided by Embodiment 3, respectively.

[0220] As shown in FIG. 18, during the transmission of low-frequency data, the transmitting MLD sends a cross-link RTS frame. If the current high-frequency channel can be used, the receiving MLD feeds back a cross-link CTS frame. After the transmitting MLD receives the cross-link CTS, it starts to contend for the high-frequency channel. In this case, the NAV duration of the high-frequency link declared by the transmitting MLD is declared according to its own needs.

[0221] As shown in FIG. 19, during the transmission of low-frequency data, the transmitting MLD sends a cross-link RTS frame. If the receiving MLD cannot access the high-frequency channel at this time due to the high-frequency link NAV, and the source address of the high-frequency link NAV is not the transmitting MLD, the receiving MLD feeds back a cross-link DTS frame according to the received cross-link RTS frame. At this time, the transmitting MLD can continue to transmit data on the low-frequency, and wait for the high-frequency link NAV of the receiving MLD to end before re-enabling the cross-link RTS / CTS procedure.

[0222] As shown in FIG. 18 or FIG. 19, other MLD devices or non-MLD devices can update the NAV of the low-frequency link according to the duration field in the RTS frame and / or the CTS frame. Other MLD devices can update the NAV of the high-frequency link according to the MMW duration field in the cross-link RTS frame and / or the cross-link CTS frame.

[0223] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and therefore, the parts not described in detail can be referred to the foregoing method embodiments.

[0224] FIG. 20 is a schematic structural diagram of a communication device 2000 provided by an embodiment of the present application. The communication device 2000 can be a first device. The communication device 2000 can include a sending unit 2010.

[0225] The sending unit 2010 can be configured to send a first frame on the first link, where the first frame is used for the first device to request to send data to the second device on the millimeter wave link.

[0226] In an embodiment of the disclosure, the communication device 2000 can be configured to perform part or all of the method steps performed by the first device in the above method embodiments. The communication device 2000 comprises units or modules for performing the method steps corresponding to the above method embodiments. The method processes have been described in detail in the foregoing embodiments, and the modules in this embodiment have the same functions or perform the same steps, and will not be described here. However, it should be known by the person skilled in the art that the foregoing description corresponding to the above drawings can be introduced into this embodiment, and the modules in the communication device 2000 correspond thereto.

[0227] In an optional embodiment, the sending unit 2010 can be a transceiver 2330. The communication device 2000 can further include a processor 2310 and a memory 2320, as shown in FIG. 23.

[0228] FIG. 21 is a schematic structural diagram of a communication device 2100 according to an embodiment of the disclosure. The communication device 2100 can be a second device. The communication device 2100 can include a receiving unit 2110.

[0229] The receiving unit 2110 can be configured to receive a first frame sent by a first device on a first link, where the first frame is used for the first device to request to send data to the second device on a millimeter wave link.

[0230] In an embodiment of the disclosure, the communication device 2100 can be configured to perform part or all of the method steps performed by the second device in the above method embodiments. The communication device 2100 comprises units or modules for performing the method steps corresponding to the above method embodiments. The method processes have been described in detail in the foregoing embodiments, and the modules in this embodiment have the same functions or perform the same steps, and will not be described here. However, it should be known by the person skilled in the art that the foregoing description corresponding to the above drawings can be introduced into this embodiment, and the modules in the communication device 2100 correspond thereto.

[0231] In an optional embodiment, the receiving unit 2110 can be a transceiver 2330. The communication device 2100 can further include a processor 2310 and a memory 2320, as shown in FIG. 23.

[0232] FIG. 22 is a schematic structural diagram of a communication device 2200 according to an embodiment of the disclosure. The communication device 2200 can be a third device. The communication device 2200 can include a monitoring unit 2210.

[0233] The listening unit 2210 is configured to listen to a first frame and / or a second frame on the first link, wherein the first frame is used to request the first device to transmit data to the second device on the millimeter wave link, and the second frame is used to indicate that the second device accepts or rejects the request of the first frame.

[0234] In the embodiments of the present application, the communication device 2200 can be used to execute part or all of the method steps performed by the third device in the above method embodiments. The communication device 2200 comprises units or modules for executing the method steps corresponding to the above method steps. The method flow has been described in detail in the foregoing embodiments, and the modules in the present embodiment have the same functions or execute the same steps, which will not be described here in detail. However, it should be known by the person skilled in the art that the foregoing description corresponding to the above drawings can be introduced into the present embodiment, and the modules in the communication device 2200 correspond thereto.

[0235] In optional embodiments, the listening unit 2210 can be the processor 2310 or the transceiver 2330. The communication device 2200 can further include a memory 2320, as shown in FIG. 23.

[0236] FIG. 23 is a schematic structural diagram of an apparatus for communication according to an embodiment of the present application. The dashed line in FIG. 23 indicates that the unit or module is optional. The apparatus 2300 can be used to implement the methods described in the above method embodiments. The apparatus 2300 can be a chip or a communication device.

[0237] The apparatus 2300 can include one or more processors 2310. The processor 2310 can support the apparatus 2300 to implement the methods described in the foregoing method embodiments. The processor 2310 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0238] The apparatus 2300 can further include one or more memories 2320. The memories 2320 store programs, which can be executed by the processor 2310, so that the processor 2310 performs the methods described in the foregoing method embodiments. The memories 2320 can be independent of the processor 2310 or integrated in the processor 2310.

[0239] The apparatus 2300 can further include a transceiver 2330. The processor 2310 can communicate with other devices or chips through the transceiver 2330. For example, the processor 2310 can perform data transceiving with other devices or chips through the transceiver 2330.

[0240] Embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the communication device provided by the embodiments of the present application, and the program causes the computer to perform the method performed by the communication device in the various embodiments of the present application.

[0241] Embodiments of the present application also provide a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided by the embodiments of the present application, and the program causes the computer to perform the method performed by the communication device in the various embodiments of the present application.

[0242] Embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided by the embodiments of the present application, and the computer program causes the computer to perform the method performed by the communication device in the various embodiments of the present application.

[0243] It should be understood that the terms "system" and "network" can be used interchangeably in the present application. In addition, the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0244] In the embodiments of the present application, a "field" can also be referred to as a "domain", a "subfield", or a "sub-domain". A field can occupy one or more bytes (octets), or a field can occupy one or more bits (bits).

[0245] The field name defined in the embodiments of the present application is only an example, and the field can have other names.

[0246] In the embodiments of the present application, the "indication" can be direct indication, indirect indication, or can represent an associated relationship. For example, A indicates B, which can mean that B can be obtained by A; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have an associated relationship.

[0247] In the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0248] In the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or can represent an associated relationship between the two, or can represent an indication and being indicated, configuration and being configured, and the like.

[0249] In the embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables or other information that can be used to indicate related information in devices (for example, including AP and STA), and the specific implementation manner is not limited in the present application. For example, predefinition can mean definition in a protocol.

[0250] In the embodiments of the present application, the term "and / or" is only used to describe the associated relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents an "or" relationship between the associated objects before and after it.

[0251] In the embodiments of the present application, the "including" can mean direct including or indirect including. Alternatively, the "including" mentioned in the embodiments of the present application can be replaced by "indicating" or "used for determining". For example, A includes B can be replaced by A indicating B, or A used for determining B.

[0252] In various embodiments of the present application, the size of the serial number of the above processes does not mean the execution order, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0253] In the embodiments of the present application, the "protocol" can mean a standard protocol in the communication field, for example, it can include WiFi protocol and related protocols applied to future WiFi communication systems, and the present application does not limit this.

[0254] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the above-described device embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and in actual implementation, another division manner can be adopted, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0255] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., can be located in one place or distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0256] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0257] In the above embodiments, all or part of them can be realized by software, hardware, firmware or any combination thereof. When realized by software, all or part of them can be realized in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium readable by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0258] The above descriptions are only the specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, the method comprising: The method comprises: a first device sending a first frame on a first link; wherein the first frame is used for the first device to request sending data to a second device on a millimeter wave link.

2. The method of claim 1, wherein, The method further comprises: during a first time period, the first device expecting to receive a second frame on the first link; wherein the second frame is used for indicating that the second device accepts or rejects the request of the first frame.

3. The method of claim 2, wherein, In a case that the first device comprises a non-access point station, the method further comprises: in a case that the first device receives the second frame during the first time period and the second frame is used for indicating that the second device accepts the request of the first frame, a millimeter wave link of the first device switches to a wake-up state.

4. The method of claim 2, wherein, in a case that the first device receives the second frame during the first time period and the second frame is used for indicating that the second device rejects the request of the first frame, the second frame is further used for indicating a first duration, the first duration is used for indicating a first timer duration of the second device, in a case that the first timer does not time out, the second device is unable to receive or send data on the millimeter wave link.

5. The method of claim 4, wherein, The method further comprises: after the first duration ends, the first device repeatedly sending the first frame.

6. The method of claim 2, wherein, The method further comprises: in a case that the first device does not receive the second frame during the first time period, the first device repeatedly sending the first frame.

7. The method according to claim 5 or 6, characterized in that, The repeatedly sent first frame satisfies one or more of the following: a number of times of repetition is less than or equal to a first threshold; is sent within a transmission opportunity (TXOP) of the first link; a first number of times of contention for the first link for repeatedly sending the first frame is less than or equal to a second threshold.

8. The method according to any one of claims 2-7, characterized in that, in a case that the second frame is used for indicating that the second device accepts the request of the first frame, the second frame is further used for indicating one or more of the following: a first identifier, used for indicating a link identifier of the millimeter wave link; a first bandwidth, used for indicating an operating bandwidth of the millimeter wave link; a second duration, used for indicating a duration in which the second device occupies the millimeter wave link.

9. The method of claim 8, wherein, The second duration is determined based on one or more of the following: a duration required for transmitting the second frame; a third duration, used for indicating a duration in which the first device occupies the millimeter wave link.

10. The method according to any one of claims 1-9, characterized in that, The first frame is further used for indicating one or more of the following: a second identifier, used for indicating a link identifier of the millimeter wave link; a second bandwidth, used for indicating an operating bandwidth of the millimeter wave link; a third duration, used for indicating a duration in which the first device occupies the millimeter wave link.

11. The method of claim 10, wherein, The third duration is determined based on one or more of the following: a duration required for transmitting a second frame, the second frame being used for indicating that the second device accepts the request of the first frame; a duration required for transmitting to-be-transmitted data on the millimeter wave link; a contention time for the millimeter wave link.

12. A method of wireless communication, the method comprising: The method comprises: a second device receiving a first frame sent by a first device on a first link; wherein the first frame is used for the first device to request sending data to the second device on a millimeter wave link.

13. The method of claim 12, wherein, The method further comprises: In a first time period, the second device transmits a second frame to the first device on the first link; wherein the second frame is used to indicate that the second device accepts or rejects the request of the first frame.

14. The method of claim 13, wherein, In a case where the second device comprises a non-access point station, the method further comprises: In a case where the second frame is used to indicate that the second device accepts the request of the first frame, the millimeter wave link of the second device switches to a wake-up state.

15. The method of claim 13, wherein, In a case where the second frame is used to indicate that the second device rejects the request of the first frame, the second frame is further used to indicate a first time length, the first time length is used to indicate a first timer time length of the second device, in a case where the first timer does not time out, the second device is unable to receive or transmit data on the millimeter wave link.

16. The method according to any one of claims 13-15, characterized by, In a case where the second frame is used to indicate that the second device accepts the request of the first frame, the second frame is further used to indicate one or more of: a first identifier, used to indicate a link identifier of the millimeter wave link; a first bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a second time length, used to indicate a time length during which the second device occupies the millimeter wave link.

17. The method of claim 16, wherein, The second time length is determined based on one or more of: a time length required for transmitting the second frame; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link.

18. The method according to any one of claims 12-17, characterized by, The first frame is further used to indicate one or more of: a second identifier, used to indicate a link identifier of the millimeter wave link; a second bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a third time length, used to indicate a time length required for the first device to transmit a signal on the millimeter wave link.

19. The method of claim 18, wherein, The third time length is determined based on one or more of: a time length required for transmitting a second frame, the second frame being used to indicate that the second device accepts the request of the first frame; a time length required for transmitting to-be-transmitted data on the millimeter wave link; a contention time for the millimeter wave link.

20. A method of wireless communication, comprising: The method comprises: a third device listens to a first frame and / or a second frame on a first link; wherein the first frame is used for a first device to request to transmit data to a second device on a millimeter wave link, and the second frame is used to indicate that the second device accepts or rejects the request of the first frame.

21. The method of claim 20, wherein, In a case where the second frame is used to indicate that the second device accepts the request of the first frame, the second frame is further used to indicate one or more of: a first identifier, used to indicate a link identifier of the millimeter wave link; a first bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a second time length, used to indicate a time length during which the second device occupies the millimeter wave link.

22. The method of claim 21, wherein, The second time length is determined based on one or more of: a time length required for transmitting the second frame; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link.

23. The method of claim 21 or 22, wherein, The method further comprises: the third device updates a time length of a second timer for the millimeter wave link according to the second time length; wherein, before the second timer times out, the third device is unable to receive or transmit data on the millimeter wave link.

24. The method of any one of claims 20-23, wherein, The first frame is further configured to indicate one or more of: a second identification, configured to indicate a link identification of the millimeter wave link; a second bandwidth, configured to indicate an operating bandwidth of the millimeter wave link; a third time length, configured to indicate a time length during which the first device occupies the millimeter wave link.

25. The method of claim 24, wherein, The third time length is determined based on one or more of: a time length required for transmitting a second frame, the second frame being configured to indicate that the second device accepts the request of the first frame; a time length required for transmitting data to be transmitted on the millimeter wave link; a contention time for the millimeter wave link.

26. The method of claim 24 or 25, wherein, The method further comprises: updating, by the third device, a third timer for the millimeter wave link based on the third time length; wherein the third device is unable to receive or transmit data on the millimeter wave link before the third timer expires.

27. The method according to claims 24-26, characterized by, The method further comprises: resetting, by the third device, the third timer if the third device does not detect that the first device transmits data on the millimeter wave link within the fourth time length; wherein the third device is unable to receive or transmit data on the millimeter wave link before the third timer expires.

28. The method of claim 27, wherein, The fourth time length is determined based on one or more of: a contention time for the millimeter wave link; a time length required for transmitting the second frame; a contention time delay for the millimeter wave link; a time delay from a receiving antenna to a physical layer.

29. A communications device, characterized by The communication device is a first device, and the communication device comprises: a transmitting unit, configured to transmit a first frame on a first link; wherein the first frame is configured to indicate that the first device requests to transmit data to a second device on a millimeter wave link.

30. The communication device of claim 29, wherein, The communication device is further configured to: expect to receive a second frame on the first link within a first time period; wherein the second frame is configured to indicate that the second device accepts or rejects the request of the first frame.

31. The communication device of claim 30, wherein, In a case where the first device comprises a non-access point station, the communication device is further configured to: switch a millimeter wave link of the first device to an awake state in a case where the first device receives the second frame within the first time period and the second frame is configured to indicate that the second device accepts the request of the first frame.

32. The communication device of claim 30, wherein, In a case where the first device receives the second frame within the first time period and the second frame is configured to indicate that the second device rejects the request of the first frame, the second frame is further configured to indicate a first time length, the first time length being configured to indicate a time length of a first timer of the second device, the second device being unable to receive or transmit data on the millimeter wave link in a case where the first timer does not expire.

33. The communication device of claim 32, wherein, The communication device is further configured to: repeatedly transmit the first frame after the first time length ends.

34. The communication device of claim 30, wherein, The communication device is further configured to: repeatedly transmit the first frame after the first time length ends.

35. The communication device of claim 33 or 34, wherein, The repeatedly transmitted first frame satisfies one or more of: a number of times of repetition is less than or equal to a first threshold; is transmitted within a transmission opportunity (TXOP) of the first link; The first number of times is less than or equal to a second threshold, and the first number of times is a number of times of contending for the first link for repeating sending of the first frame.

36. The communication device of any of claims 30-35, wherein, In a case where the second frame is used to indicate that the second device accepts the request of the first frame, the second frame is further used to indicate one or more of the following: a first identifier, used to indicate a link identifier of the millimeter wave link; a first bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a second time length, used to indicate a time length during which the second device occupies the millimeter wave link.

37. The communication device of claim 36, wherein, The second time length is determined based on one or more of the following: a time length required for transmitting the second frame; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link.

38. The communication device of any of claims 29-37, wherein, The first frame is further used to indicate one or more of the following: a second identifier, used to indicate a link identifier of the millimeter wave link; a second bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link.

39. The communication device of claim 38, wherein, The third time length is determined based on one or more of the following: a time length required for transmitting a second frame used to indicate that the second device accepts the request of the first frame; a time length required for transmitting to-be-transmitted data on the millimeter wave link; a contention time for the millimeter wave link.

40. A communications device, characterized by The communication device is a second device, and the communication device includes: a receiving unit, configured to receive a first frame sent by a first device on a first link; wherein the first frame is used for the first device to request to send data to the second device on a millimeter wave link.

41. The communication device of claim 40, wherein, The communication device is further configured to: send, to the first device on the first link within a first time period, a second frame; wherein the second frame is used to indicate that the second device accepts or rejects the request of the first frame.

42. The communications device of claim 41, wherein, In a case where the second device includes a non-access point station, the communication device is further configured to: in a case where the second frame is used to indicate that the second device accepts the request of the first frame, switch a millimeter wave link of the second device to a wake-up state.

43. The communication device of claim 41, wherein, in a case where the second frame is used to indicate that the second device rejects the request of the first frame, the second frame is further used to indicate a first time length, the first time length being used to indicate a time length of a first timer of the second device, and in a case where the first timer does not time out, the second device is unable to receive or send data on the millimeter wave link.

44. The communication device of any of claims 41-43, wherein, in a case where the second frame is used to indicate that the second device accepts the request of the first frame, the second frame is further used to indicate one or more of the following: a first identifier, used to indicate a link identifier of the millimeter wave link; a first bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a second time length, used to indicate a time length during which the second device occupies the millimeter wave link.

45. The communication device of claim 44, wherein, The second time length is determined based on one or more of the following: a time length required for transmitting the second frame; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link.

46. The communication device of any of claims 40-45, wherein, The first frame is further used to indicate one or more of the following: a second identifier, used to indicate a link identifier of the millimeter wave link; a second bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link. The third time length is determined based on one or more of the following: a time length required for transmitting a second frame used to indicate that the second device accepts the request of the first frame; a time length required for transmitting to-be-transmitted data on the millimeter wave link; a contention time for the millimeter wave link. The communication device is a second device, and the communication device includes: a receiving unit, configured to receive a first frame sent by a first device on a first link; wherein the first frame is used for the first device to request to send data to the second device on a millimeter wave link. The communication device is further configured to: send, to the first device on the first link within a first time period, a second frame; wherein the second frame is used to indicate that the second device accepts or rejects the request of the first frame. In a case where the second device includes a non-access point station, the communication device is further configured to: in a case where the second frame is used to indicate that the second device accepts the request of the first frame, switch a millimeter wave link of the second device to a wake-up state. in a case where the second frame is used to indicate that the second device rejects the request of the first frame, the second frame is further used to indicate a first time length, the first time length being used to indicate a time length of a first timer of the second device, and in a case where the first timer does not time out, the second device is unable to receive or send data on the millimeter wave link. in a case where the second frame is used to indicate that the second device accepts the request of the first frame, the second frame is further used to indicate one or more of the following: a first identifier, used to indicate a link identifier of the millimeter wave link; a first bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a second time length, used to indicate a time length during which the second device occupies the millimeter wave link. The second time length is determined based on one or more of the following: a time length required for transmitting the second frame; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link. The first frame is further used to indicate one or more of the following: a second identifier, used to indicate a link identifier of the millimeter wave link; a second bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a third time length, used to indicate a time length required by the first device to transmit a signal on the millimeter wave link.

47. The communication device of claim 46, wherein, The third time length is determined based on one or more of the following: a time length required for transmitting a second frame, the second frame being used to indicate that the second device accepts the request of the first frame; a time length required for transmitting to-be-transmitted data on the millimeter wave link; a contention time for the millimeter wave link.

48. A communications device, characterized by The communication device is a third device, and the communication device comprises: a listening unit, configured to listen to a first frame and / or a second frame on a first link; The first frame is used for a first device to request to send data to a second device on a millimeter wave link, and the second frame is used to indicate that the second device accepts or rejects the request of the first frame.

49. The communication device of claim 48, wherein, In a case where the second frame is used to indicate that the second device accepts the request of the first frame, the second frame is further used to indicate one or more of the following: a first identifier, used to indicate a link identifier of the millimeter wave link; a first bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a second time length, used to indicate a time length during which the second device occupies the millimeter wave link.

50. The communication device of claim 49, wherein, The second time length is determined based on one or more of the following: a time length required for transmitting the second frame; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link.

51. The communication device of claim 49 or 50, wherein, The communication device is further configured to: update a time length of a second timer for the millimeter wave link according to the second time length; wherein the third device cannot receive or send data on the millimeter wave link before the second timer expires.

52. The communication device of any of claims 48-51, wherein, The first frame is further used to indicate one or more of the following: a second identifier, used to indicate a link identifier of the millimeter wave link; a second bandwidth, used to indicate an operating bandwidth of the millimeter wave link; a third time length, used to indicate a time length during which the first device occupies the millimeter wave link.

53. The communication device of claim 52, wherein, The third time length is determined based on one or more of the following: a time length required for transmitting a second frame, the second frame being used to indicate that the second device accepts the request of the first frame; a time length required for transmitting to-be-transmitted data on the millimeter wave link; a contention time for the millimeter wave link.

54. The communication device of claim 52 or 53, wherein, The communication device is further configured to: update a time length of a third timer for the millimeter wave link according to the third time length; wherein the third device cannot receive or send data on the millimeter wave link before the third timer expires.

55. The communication device according to claims 52-54, characterized by The communication device is further configured to: if the third device does not detect that the first device transmits data on the millimeter wave link within the fourth time length, reset the third timer; wherein the third device cannot receive or send data on the millimeter wave link before the third timer expires.

56. The communication device of claim 55, wherein, The fourth time length is determined based on one or more of the following: a contention time for the millimeter wave link; a time length required for transmitting the second frame; a contention time for the millimeter wave link; a time delay from a receiving antenna to a physical layer.

57. A communications device, characterized by A communication device comprising a transceiver, a memory for storing a program, and a processor for invoking the program in the memory and controlling the transceiver to receive or send signals, so as to make the communication device perform the method according to any one of claims 1-28.

58. An apparatus, comprising: A device comprising a processor for invoking a program from a memory, so as to make the device perform the method according to any one of claims 1-28.

59. A chip, comprising: A chip comprising a processor for invoking a program from a memory, so that the device installed with the chip performs the method according to any one of claims 1-28.

60. A computer-readable storage medium, characterized in that, A computer program product, which has a program stored thereon, the program causing a computer to perform the method according to any one of claims 1-28.

61. A computer program product, characterised in that, A computer program, which causes a computer to perform the method according to any one of claims 1-28.

62. A computer program, characterized in that, The computer program causes a computer to perform the method according to any one of claims 1-28.

Images