WO2025185385A1 - 多链路设备通信方法及相关设备 - Google Patents

多链路设备通信方法及相关设备

Info

Publication number
WO2025185385A1
WO2025185385A1 PCT/CN2025/076186 CN2025076186W WO2025185385A1 WO 2025185385 A1 WO2025185385 A1 WO 2025185385A1 CN 2025076186 W CN2025076186 W CN 2025076186W WO 2025185385 A1 WO2025185385 A1 WO 2025185385A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
link device
service
mapping
links
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/076186
Other languages
English (en)
French (fr)
Other versions
WO2025185385A8 (zh
Inventor
谢强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology (Shenzhen) Co Ltd
Original Assignee
Tencent Technology (Shenzhen) Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology (Shenzhen) Co Ltd filed Critical Tencent Technology (Shenzhen) Co Ltd
Publication of WO2025185385A1 publication Critical patent/WO2025185385A1/zh
Publication of WO2025185385A8 publication Critical patent/WO2025185385A8/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/243—Multipath using M+N parallel active paths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a multi-link device communication method, a multi-link device, a computer-readable storage medium, and a computer program product.
  • the Institute of Electrical and Electronics Engineers introduced the multi-link (ML) mechanism in the IEEE 802.11be protocol standard for wireless local access networks (WLANs).
  • a multi-link device supports data transmission over multiple links.
  • An embodiment of the present disclosure provides a multi-link device communication method, the method being performed by a first multi-link device.
  • the method comprises: upon detecting that a first link transmitting service data between the first multi-link device and a second multi-link device is in a first state, generating a first request frame, the first request frame being used to request the second multi-link device to map a first service identifier of the service data to at least two links between the first multi-link device and the second multi-link device; wherein the first state indicates that a channel quality of the first link is below a threshold and/or congestion exists; sending the first request frame to the second multi-link device; receiving a first response frame returned by the second multi-link device in response to the first request frame; and if the first response frame indicates that the second multi-link device accepts the first request frame, transmitting the service data through the at least two links simultaneously.
  • An embodiment of the present disclosure provides a multi-link communication method, performed by a second multi-link device, the method comprising: receiving a first request frame sent by a first multi-link device, the first request frame requesting mapping a first service identifier of service data to at least two links between the first multi-link device and the second multi-link device, wherein the service data is currently transmitted between the first multi-link device and the second multi-link device via a first link, and the first link is in a first state; the first state indicates that a channel quality of the first link is below a threshold and/or congestion exists; generating a first response frame in response to the first request frame; and sending the first response frame to the first multi-link device; wherein, when the second multi-link device accepts the first request frame, it simultaneously transmits the service data via the at least two links.
  • An embodiment of the present disclosure provides a multi-link device, comprising: one or more processors; and a memory configured to store one or more programs.
  • the multi-link device implements the communication method described in the embodiment of the present disclosure.
  • An embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon.
  • the computer program When the computer program is run on a computer, the computer implements the communication method described in the embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a computer program product, including a computer program.
  • the computer program When the computer program is executed by a computer, the communication method described in the embodiments of the present disclosure is implemented.
  • FIG1 is a schematic diagram of a multi-link communication system provided by an embodiment of the present disclosure.
  • FIG2 is a schematic diagram of an application scenario of transmitting game data using multiple links provided by an embodiment of the present disclosure.
  • FIG3 schematically shows a flow chart of a multi-link device communication method according to some embodiments of the present disclosure.
  • FIG4 schematically shows an interaction diagram of a multi-link device communication method according to some embodiments of the present disclosure.
  • FIG5 schematically shows an interaction diagram of a multi-link device communication method according to other embodiments of the present disclosure.
  • FIG6 schematically shows a flow chart of a multi-link selection strategy method according to some embodiments of the present disclosure.
  • FIG7 schematically shows a format diagram of a service-to-link mapping element according to some embodiments of the present disclosure.
  • FIG8 schematically shows an interaction diagram of a multi-link device communication method according to still other embodiments of the present disclosure.
  • FIG9 schematically shows an interaction diagram of a multi-link device communication method according to still other embodiments of the present disclosure.
  • FIG10 schematically shows a flowchart of a multi-link device communication method according to other embodiments of the present disclosure.
  • FIG11 schematically shows a schematic structural diagram of a multi-link device according to some embodiments of the present disclosure.
  • module refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof.
  • a processor or multiple processors or memories
  • each module or unit can be part of an overall module or unit that includes the function of the module or unit.
  • references herein to "embodiments” mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present disclosure.
  • the appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
  • the “network” and “system” that appear in the embodiments of the present disclosure express the same concept, and the communication system is the communication network.
  • WLANs wireless local area networks
  • a WLAN can include multiple basic service sets (BSSs), and devices in a BSS can include access point stations (AP STAs, also referred to as APs or access points) and non-access point stations (none access point stations, non-AP STAs, also referred to as STAs or stations).
  • BSS basic service sets
  • AP STAs access point stations
  • non-AP STAs non-access point stations
  • each BSS can include an access point and at least one station.
  • An access point is an entity that provides network access to connected stations via wireless media.
  • An access point can connect individual wireless network clients to an Ethernet network.
  • An access point can be a network device equipped with a wireless fidelity (Wi-Fi) chip.
  • An access point can be a device that supports various IEEE 802.11 protocol standards. For example, an access point can support IEEE 802.11ac, IEEE 802.11n, IEEE 802.11g, IEEE 802.11b, IEEE 802.11ax, IEEE 802.11be, and next-generation WLAN protocol standards.
  • An access point can include a centralized controller, a base station (BS), a base transceiver station (BTS), a site controller, and a switch.
  • BS base station
  • BTS base transceiver station
  • An access point can include devices that provide wireless communication capabilities for stations, such as a system-on-chip (SoC).
  • SoC system-on-chip
  • This SoC can include a chip and other discrete components, such as transceivers.
  • An access point can communicate with an Internet Protocol (IP) network.
  • IP Internet Protocol
  • IP Internet Protocol
  • the Internet a private IP network or other data networks.
  • a station can be a wireless communication chip, a wireless sensor, or a wireless communication terminal.
  • a user equipment (UE) supporting Wi-Fi communication functions a remote terminal (remote UE), an access terminal, a user unit, a user station, a mobile device, a user terminal, an intelligent terminal, a wireless communication device, a user agent or user device/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, an in-vehicle device, a wearable device, etc., without specific limitation.
  • UE user equipment
  • remote terminal remote terminal
  • an access terminal a user unit, a user station, a mobile device, a user terminal, an intelligent terminal, a wireless communication device, a user agent or user device/cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA),
  • a station can include a non-AP enhanced high throughput station (non-AP EHT STA) and a non-AP high efficiency station (non-AP HE STA).
  • a station can include a device with transceiver functions, such as a chip system.
  • the chip system may include a chip and other discrete devices, such as a transceiver device.
  • the multi-link communication system according to an embodiment of the present disclosure is exemplarily described below with reference to FIG1 .
  • a Wi-Fi device that supports multi-link operation is a multi-link device (MLD).
  • MLO multi-link operation
  • a multi-link device MLD
  • a multi-link device can support data transmission on multiple links.
  • a multi-link device can be an access point multi-link device (AP MLD) or a non-access point multi-link device (Non-AP MLD).
  • An AP MLD can include multiple access points (APs, for example, three APs, namely AP1, AP2, and AP3, are used as an example in Figure 1, but the present disclosure is not limited to this and may include more or fewer APs).
  • a non-AP MLD can include multiple stations (STAs, for example, three STAs, namely STA1, STA2, and STA3, are used as an example in Figure 1, but the present disclosure is not limited to this and may include more or fewer STAs).
  • Different APs or STAs can operate on different carrier frequencies, such as 2.4 GHz, 5 GHz, and 6 GHz (abbreviated as 2.4G, 5G, and 6G in Figure 1), or different carrier frequencies within the same frequency band (e.g., 5 GHz).
  • a non-AP MLD can be a user terminal that supports multi-link Wi-Fi 7 (i.e., the IEEE 802.11be standard for wireless LANs).
  • An AP MLD can be a hotspot that supports multi-link Wi-Fi 7.
  • Multiple (two or more) links can be established between AP MLD and Non-AP MLD (called multi-link establishment or multi-link association), and data can be transmitted on these multiple links.
  • Link1 (abbreviated as Link1, i.e., Link 1) is established between AP1 and STA1
  • a link L2 (abbreviated as Link2, i.e., Link 2) is established between AP2 and STA2
  • a link L3 (abbreviated as Link3, i.e., Link 3) is established between AP3 and STA3.
  • Each link is uniquely identified by a link ID (identity).
  • Different links have different operating carrier frequencies.
  • Figure 1 assumes that the operating carrier frequencies of L1, L2, and L3 are 2.4 GHz, 5 GHz, and 6 GHz, respectively, but the present disclosure is not limited to this.
  • a service identifier for service data can be established or updated with a high-priority service identifier and mapped to multiple links between AP MLDs and non-AP MLDs.
  • the service data corresponds to a critical, high-speed, or low-latency service, such as gaming, video, audio, or Metaverse services.
  • gaming uses gaming as an example, but the present disclosure is not limited to this.
  • a service identifier can be used to uniquely identify the type of service data, such as voice service, video service, best-effort transmission, or background traffic, to distinguish it from other types of services.
  • the present disclosure does not limit its representation format; for example, a Traffic ID (TID) can be used.
  • TID Traffic ID
  • the TID is used to identify different types of traffic.
  • TID time division duplex
  • Video service has a lower priority than voice service.
  • Web access data is best-effort traffic, which has certain latency requirements but is less sensitive.
  • Background traffic is the least sensitive to latency.
  • TID to represent the service identifier, but the present disclosure is not limited thereto.
  • TID0 to TID7 can be used to represent different service identifiers, wherein the priority of the service data corresponding to TID6 or TID7 is higher than the priority of the service data corresponding to TID0-TID5.
  • the TID of the service data of the game service can be set to or updated to TID6 or TID7, so that the service data of the game service has a higher priority than other services, thereby giving priority to the transmission of the data of the game service and reducing the transmission delay of the game service.
  • TID6 or TID7 can be mapped to multiple links.
  • TID6 or TID7 of the game service is mapped to Link1, Link2 and Link3 at the same time, but the present disclosure is not limited to this. This makes it possible to transmit the game service data simultaneously through Link1, Link2 and Link3, thereby improving the game reliability or reducing the game delay in the IEEE protocol multi-link transmission.
  • the multi-link communication system shown in Figure 1 may also include other multi-link devices, access points or stations in addition to AP MLD and Non-AP MLD, without specific limitation.
  • the multi-link communication system shown in Figure 1 may also include access network (radio access network, RAN) equipment, core network (core network, CN) equipment, network controller, mobile management entity and other network entities, without specific limitation.
  • access network radio access network, RAN
  • core network core network, CN
  • network controller mobile management entity and other network entities, without specific limitation.
  • the communication between the AP MLD and the Non-AP MLD in the multi-link communication system shown in Figure 1 can be wireless communication or wired communication, without specific limitation.
  • the AP MLD and the Non-AP MLD can simultaneously transmit TID6 or TID7 game data (i.e., service data) through Link1 with a working carrier frequency of 2.4 GHz, Link2 with a working carrier frequency of 5 GHz, and Link3 with a working carrier frequency of 6 GHz.
  • TID6 or TID7 game data i.e., service data
  • the multi-link communication system can simultaneously utilize multiple antennas and spectrum resources for service data transmission, enabling AP MLD and non-AP MLD to communicate simultaneously on multiple frequency bands. This improves network throughput and stability, reduces congestion and interference, and enhances overall network performance. Multi-link transmission also increases network reliability. Even if a frequency band or antenna experiences congestion or interference, AP MLD and non-AP MLD can still communicate by combining other available links, thereby reducing the possibility of data loss.
  • the IEEE protocol introduces the Multi-Link Operation (MLO) feature.
  • MLO Multi-Link Operation
  • APs and STAs supporting MLO can transmit data over one of multiple established links (e.g., 2.4 GHz, 5 GHz, 6 GHz, etc.). They can also simultaneously transmit data for the same service over two or more communication links. Each communication link complements the others, reducing data frame retransmissions and improving data transmission reliability. This allows multiple links to transmit service data with the same TID. For example, for gaming services, transmitting game data over multiple links can greatly improve transmission reliability and enhance the gaming experience, especially in environments with poor network coverage.
  • the disclosed embodiment detects the service status and wireless channel environment of each link in multiple communication links that have been established for communication, and sends request frames (including a first request frame, and in some embodiments, a second request frame) to each other through negotiation for Non-AP MLD and AP MLD that support MLO to request to modify the TID mapping of the low-latency game service to the multiple communication links that have been established, so that the multiple communication links send game data, thereby improving the reliability of data transmission and achieving the purpose of enhancing the gaming experience.
  • request frames including a first request frame, and in some embodiments, a second request frame
  • “simultaneous transmission of data of the same service” refers to the parallel transmission of service data with the same service identifier, such as the same TID, on multiple links that have been established between the Non-AP MLD and the AP MLD.
  • One mode is multiple transmissions and single reception (copy mode), that is, multiple frequency bands/multiple links on the AP/STA side simultaneously send the same data with the same TID to the receiving end (STA/AP), and the receiving end automatically selects the data of the fastest frequency band/link. If the frequency band is interfered, the system accepts data from other frequency bands. This method can improve the stability of data transmission.
  • the other mode is multiple transmissions and multiple receptions (joint mode), that is, splitting a piece of data with the same TID into multiple parts (for example, three parts), and sending them simultaneously through multiple (for example, three) frequency bands/multiple (for example, three) links. After receiving them, the receiving end combines the multiple data.
  • the multiple transmission and multiple reception mode can improve the speed of data transmission.
  • “simultaneous transmission of gaming data for the same gaming service” refers to the parallel transmission of gaming data corresponding to the gaming service's TID across multiple links established between the non-AP MLD and the AP MLD.
  • Multiple copies of the same gaming data can be replicated and transmitted in parallel across multiple links to improve transmission reliability, for example, in weak channel conditions.
  • the same gaming data can be split into multiple copies and transmitted in parallel across multiple links to increase transmission speed, for example, in situations of gaming traffic congestion.
  • detecting link traffic conditions refers to detecting whether there is congestion in the data transmission of services (e.g., services) being transmitted on at least one link established between a non-AP MLD and an AP MLD.
  • the degree of congestion can be determined by detecting congestion information. Different congestion levels can be assigned to represent different congestion levels, or congestion information can be used to determine whether a link is in a congested state. For example, a ping packet (a data packet used to test network connectivity) can be periodically sent from a transmitter (non-AP MLD/AP MLD) to a receiver (AP MLD/non-AP MLD) on the detected link, and the transmitter waits for a signal sent back from the receiver.
  • a ping packet a data packet used to test network connectivity
  • the transmitter can determine the time required for the data packet to travel from the transmitter to the receiver and back. This time is referred to as the latency between the transmitter and receiver, also known as the ping value.
  • the ping value can be used to determine different congestion levels or to determine whether the link is in a congested state. For example, if the ping value on a link exceeds a specified duration, the link can be determined to be congested; otherwise, it can be determined to be non-congested.
  • the present disclosure is not limited to the above examples in the manner of detecting the service status of a link.
  • detecting the wireless channel environment of a link refers to detecting the channel quality information of at least one link that has been established between a Non-AP MLD and an AP MLD, and judging whether the detected link is in a weak network environment by using the channel quality information.
  • the channel quality information can be indicated by one or more indicators, such as a channel quality indicator (CQI), signal strength, signal-to-noise ratio, bit error rate, transmission rate, time delay of data transmission in the channel, etc.
  • CQI channel quality indicator
  • the wireless channel environment of a link is judged by detecting changes in relevant wireless communication indicators such as the received signal strength indication (RSSI), that is, the channel quality information includes RSSI.
  • RSSI received signal strength indication
  • the link When it is detected that the RSSI of a link is lower than a threshold (the size of which can be set according to actual needs and is not limited by the present disclosure), the link is judged to be in a weak network environment; otherwise, the link is judged to be not in a weak network environment.
  • a threshold the size of which can be set according to actual needs and is not limited by the present disclosure
  • the communication method provided in the embodiment of FIG3 may be executed by the first multi-link device.
  • the first multi-link device is an access point multi-link device (AP MLD, also referred to as an AP multi-link device) or a non-AP MLD (also referred to as a STA multi-link device).
  • AP MLD access point multi-link device
  • non-AP MLD also referred to as a STA multi-link device
  • Multi-link refers to multiple communication links between an AP and a STA.
  • the second multi-link device mentioned below is a non-AP MLD (non-AP MLD) or an access point multi-link device (AP MLD).
  • a first request frame is generated, where the first request frame is used to request the second multi-link device to map a service identifier of the service data to at least two links between the first multi-link device and the second multi-link device; wherein the first state indicates that a channel quality of the first link is lower than a threshold and/or congestion exists.
  • At least one link has been established between the AP MLD and the Non-AP MLD, and a first link has been determined from the at least one link for transmitting service data.
  • the service data may refer to data of any service, such as any important service, high-priority service, delay-sensitive service/low-latency service, high-speed service, and the following takes the gaming service as an example.
  • the first link may include one link, or may include two or more links. The following takes the example of the first link including one link (hereinafter represented by Link 1 or Link1), but the present disclosure is not limited to this.
  • the first link may be any one or more links among the at least one link that has been established between the AP MLD and the Non-AP MLD.
  • the first status indicates that the channel quality of the first link is lower than a threshold, and/or that there is congestion in the traffic transmitted on the first link.
  • a link can transmit different services.
  • the method proposed in the embodiments of the present disclosure is for any service, such as a gaming service with latency requirements.
  • the AP MLD can make a selection based on the policy, such as selecting two or three links to transmit service data simultaneously, or switching to another link with good channel quality and no congestion for transmission.
  • This policy can be extended to other services, not just gaming services.
  • the TIDs of other services are not mapped to TID6 or TID7. TID6 or TID7 are specifically for gaming services with low latency requirements.
  • the first multi-link device may detect the channel quality information and/or congestion information of the first link, and determine whether the first link is in the first state based on the channel quality information and/or the congestion information. If the channel quality information indicates that the channel quality of the first link is lower than a threshold, that is, the channel quality is poor, and/or the congestion information indicates that the service transmitted on the first link is congested or is in a congested state, then it can be determined that the first link is in the first state.
  • the channel quality information indicates that the channel quality of the first link is equal to or higher than a threshold, that is, the channel quality is good, and the congestion information indicates that the service transmitted on the first link is not congested or is not in a congested state, then it can be determined that the first link is not in the first state, that is, it is not in a weak network environment and no congestion has occurred.
  • the first multi-link device When the first multi-link device detects that the channel quality of the first link that is transmitting service data is poor and/or there is congestion in the service data transmission, the first multi-link device can generate a first request frame and send the first request frame to the second multi-link device to request the second multi-link device to map the service identifier corresponding to the service data (for example, the TID of the service) to at least two links between the AP MLD and the Non-AP MLD.
  • the service data for example, the TID of the service
  • the first request frame generated by the first multi-link device may carry a mapping relationship between the at least two links and the service identifier recommended or required by the first multi-link device.
  • the first multi-link device may determine the at least two links according to a multi-link selection policy.
  • the multi-link selection policy in the disclosed embodiments refers to a method for selecting two or more links from among the multiple links established between an AP MLD and a non-AP MLD for data transmission when two or more links are needed to transmit data between the AP MLD and the non-AP MLD.
  • This multi-link selection policy can be configured based on actual needs.
  • the method may further include:
  • the first link is in the first state, detecting a state of at least one second link between the first multi-link device and the second multi-link device; the at least one second link is a link other than the first link among the links established between the first multi-link device and the second multi-link device;
  • At least one target second link in the second state or the third state is selected from the at least one second link, and the first link and the at least one target second link are determined as the at least two links.
  • the channel quality of the at least one target second link in the second state is lower than a threshold and/or there is congestion
  • the channel quality of the at least one target second link in the third state is higher than a threshold and there is no congestion.
  • the multi-link selection strategy may include: if the first link currently transmitting service data is a single link (using link 1 as an example), and the channel quality of the first link is poor and/or service transmission is congested, then detecting the channel quality information and/or congestion information of a second link that is not currently transmitting service data and that has been established between the AP MLD and the Non-AP MLD.
  • the second link may be any of the multiple links established between the AP MLD and the Non-AP MLD, excluding the first link, where the remaining links include at least one link; or it may be any of the remaining links.
  • the channel quality information and/or congestion information of each link excluding the first link may be detected to determine whether each link excluding the first link is in the second state.
  • a second link has poor channel quality and/or service congestion
  • that second link may be selected as the target second link.
  • multiple second links have poor channel quality and/or service congestion
  • any one of the multiple second links may be selected as the target second link.
  • any link other than the first link is selected as the second link, and its channel quality information and/or congestion information is detected to determine whether the selected second link is in the second state. If the second link is in the second state, the second link is determined as the target second link; otherwise, a new second link is selected from the remaining links, and its channel quality information and/or congestion information is detected to determine whether the new second link is in the second state. This loop is performed until the target second link is determined from the remaining links.
  • the generated first request frame includes a mapping relationship between the service identifier and the first link and the target second link. That is, the service identifier is mapped to the first link and the target second link, so that service data can be transmitted simultaneously through the first link and the target second link.
  • the channel quality of a first link currently transmitting service data is poor and/or service congestion exists, two links with poor channel quality and/or service congestion can be sequentially selected to transmit service data simultaneously, thereby improving the reliability of service data transmission and reducing transmission latency.
  • the present disclosure is not limited to this.
  • any two second links can be selected from the multiple second links as target second links, and the first link is no longer used for transmitting the service data.
  • the first request frame includes a mapping relationship between the two target second links and the service identifier.
  • the multi-link selection strategy may also include: if it is detected that one or more second links are in the third state, that is, one or more second links have good channel quality and there is no service congestion, then any second link can be selected as the target second link, and the first request frame is used to request that the first link be switched to the target second link, that is, the service data is transmitted through the target second link, that is, the first request frame carries the mapping relationship between the service identifier and the target second link.
  • the multi-link selection strategy may also include: if it is detected that multiple second links are in the third state, that is, there are multiple second links with good channel quality and no service congestion, then any two second links can be selected as target second links, and the first request frame is used to request that the service data be transmitted through the two target second links, that is, the first request frame carries the mapping relationship between the service identifier and the two target second links.
  • the multi-link selection strategy may also include: if it is detected that at least one second link is in the third state, that is, there is at least one second link with good channel quality and no service congestion, then any second link can be selected as the target second link, and the first request frame is used to request that the service data be transmitted through the first link and the target second link, that is, the first request frame carries the mapping relationship between the service identifier and the first link and the target second link.
  • the first request frame may only carry the mapping relationship between the service identifier and the target second link, that is, by default, the mapping relationship between the service identifier and the first link is retained.
  • the at least two links to which the service identifier is mapped can also be selected based on the binding relationship between the link and the priority. For example, assuming that the first request frame requests to change the service identifier from a low-priority first service identifier to a high-priority second service identifier, and the high-priority second service identifier has been bound to a predetermined link, for example, the high-priority second service identifier has been bound to link 1, link 2, and link 3, then when the second multi-link device receives the first request frame, it can be known that the first multi-link device is requesting to map the service identifier to link 1, link 2, and link 3, that is, the first request frame requesting to map the service identifier to at least two links can be implicit, that is, it is not necessary to indicate the mapping relationship between the service identifier and the at least two links in the first request frame.
  • the link and priority can be bound at the beginning of the service.
  • the channel quality may deteriorate or the data service of a certain link may be congested.
  • the method provided by the embodiment of the present disclosure can be adopted to negotiate the mapping of the service TID and the link.
  • the first request frame includes information instructing to convert the service identifier from a first service identifier to a second service identifier, wherein the priority of the second service identifier is higher than that of the first service identifier.
  • the service identifier has been determined between the AP MLD and the Non-AP MLD to be the first service identifier, for example, TID2, and TID2 is mapped to Link1.
  • the first multi-link device may modify the service identifier to a second service identifier with a higher priority, for example, to TID6 or TID7.
  • the first request frame may carry information to modify the first service identifier to the second service identifier with a higher priority, so as to request the second multi-link device to modify the first service identifier to the second service identifier, that is, the purpose of reducing delay can be achieved by increasing the priority of the service.
  • the service identifier determined between the AP MLD and the Non-AP MLD before generating the first request frame already has a higher priority, such as TID6 or TID7 itself, then the service identifier does not need to be modified.
  • QoS Quality of Service
  • QoS is a network security mechanism used to address issues such as network latency and congestion.
  • QoS ensures that important services are not delayed or dropped, while also ensuring efficient network operation. For example, for gaming programs, the network priority of the gaming program can be increased, thereby reducing latency and improving the gaming experience.
  • the first request frame is a TID-To-Link Mapping Request frame.
  • the first response frame generated by the second multi-link device in response to the first request frame may be a TID-To-Link Mapping Response frame.
  • the present disclosure is not limited thereto.
  • the first request frame and the first response frame may have other names.
  • the service-to-link mapping request frame includes a service-to-link mapping element (TID-To-Link Mapping element).
  • the TID-To-Link Mapping element may carry a mapping relationship between the service identifier and the at least two links.
  • the service-to-link mapping element includes a service-to-link mapping control (TID-To-Link Mapping Control) field.
  • the service-to-link mapping control field includes a link mapping presence indicator (Link Mapping Presence Indicator) subfield. The first value of the link mapping presence indicator subfield is used to indicate the presence of a service identifier to link mapping field (e.g., Link Mapping of TID6 or Link Mapping of TID7) in the service-to-link mapping element.
  • the service identifier to link mapping field is used to indicate that the service identifier is mapped to at least two links between the first multi-link device and the second multi-link device.
  • the indication information carried by the first request frame for requesting mapping of the service identifier to at least two links is not limited to the above example, and can be explicit or implicit as long as it is any method that can represent the indication information.
  • the first request frame is sent to the second multi-link device.
  • the second multi-link device receives the first request frame sent by the first multi-link device.
  • a first response frame returned by the second multi-link device in response to the first request frame is received; if the first response frame indicates that the second multi-link device accepts the first request frame, the service data is transmitted through the at least two links at the same time.
  • the second multi-link device may decide to accept or reject the first request frame based on its own situation, link situation, mapping relationship between links and services, network conditions, etc., or modify the mapping relationship carried in the first request frame, thereby generating a first response frame to be returned to the first multi-link device, and sending the generated first response frame to the first multi-link device.
  • the mapping relationship carried in the first request frame is a first mapping relationship.
  • the mapping relationship between the service identifier in the first multi-link device and the first link is updated to the second mapping relationship.
  • the second mapping relationship is a mapping relationship between the service identifier and the at least two links determined by the second multi-link device according to the first request frame.
  • the second mapping relationship is obtained by modifying the first mapping relationship by the second multi-link device.
  • a first multi-link device may only request a second multi-link device (e.g., an AP or a STA) to map the service identifier to at least two links. That is, the first request frame may not carry the at least two links requested or suggested by the first multi-link device.
  • the second multi-link device accepts the first request frame, the second multi-link device selects the at least two links mapped to the service identifier.
  • the second multi-link device returns the mapping relationship between the at least two links selected by the second multi-link device and the service identifier to the first multi-link device via a first response frame.
  • the first response frame returned by the second multi-link device may include information indicating the rejection of the first request frame.
  • the first response frame may also include a reason for rejecting the first request frame.
  • the first multi-link device may include in a first request frame a mapping relationship between at least two links required by the first multi-link device and the service identifier.
  • the second multi-link device may only accept or reject the first request frame and may not propose a new mapping relationship between at least two links and the service identifier as suggested or required by the second multi-link device. If the second multi-link device accepts the first request frame, the first response frame returned to the first multi-link device includes information indicating acceptance of the first request frame. If the second multi-link device rejects the first request frame, the first response frame returned by the second multi-link device includes information indicating rejection of the first request frame. In some embodiments, the first response frame may also include a reason for rejecting the first request frame.
  • the first multi-link device may carry the mapping relationship between the at least two links proposed by the first multi-link device and the service identifier in a first request frame.
  • the second multi-link device may choose to accept or reject the first request frame, or modify the mapping relationship between the at least two links proposed in the first request frame and the service identifier.
  • the second multi-link device may also propose a new mapping relationship between the at least two links proposed or required by the second multi-link device and the service identifier. If the second multi-link device modifies the mapping relationship between the at least two links proposed in the first request frame and the service identifier, the second multi-link device may select the new at least two links mapped to the service identifier.
  • the second multi-link device returns the mapping relationship between the new at least two links selected by the second multi-link device and the service identifier to the first multi-link device via a first response frame.
  • the new at least two links may be completely different from, or partially identical to, the at least two links in the first request frame, and the present disclosure is not limited thereto.
  • the first response frame returned to the first multi-link device includes information indicating acceptance of the first request frame.
  • the second multi-link device rejects the first request frame
  • the first response frame returned by the second multi-link device includes indication information of rejecting the first request frame.
  • the first response frame may also include a reason for rejecting the first request frame.
  • the method provided by the embodiments of the present disclosure may further include: if the first response frame indicates that the second multi-link device accepts the first request frame, updating the mapping relationship between the service identifier in the first multi-link device and the first link to the first mapping relationship according to the first response frame.
  • the second multi-link device may update the mapping relationship between the service identifier and the first link in the second multi-link device to the first mapping relationship while generating a first response frame.
  • a first request frame carries a first mapping relationship between the first link, the target second link, and the service identifier
  • the second multi-link device accepts the first request frame.
  • the second multi-link device modifies the first mapping relationship in the first request frame and proposes a new mapping relationship (a second mapping relationship)
  • the first multi-link device accepts the second mapping relationship carried in the first response frame
  • the first multi-link device and the second multi-link device respectively update the mapping relationship between the service identifier and the first link to the second mapping relationship.
  • neither the first multi-link device nor the second multi-link device updates the mapping relationship between the service identifier and the first link, i.e., the first link is still used to transmit service data.
  • the method provided by the embodiments of the present disclosure may further include: transmitting the service data in parallel through the first link and the target second link.
  • the mapping relationship between the service identifier carried in the first request frame and the first link and the target second link, and returns a first response frame to the first multi-link device the mapping relationship between the service identifier and the link on the second multi-link device is updated, that is, the mapping relationship between the service identifier and the first link is updated to the mapping relationship between the service identifier and the first link and the target second link.
  • the first multi-link device receives the first response frame, it updates the mapping relationship between the service identifier and the link on the first multi-link device.
  • the mapping relationship is updated, the first multi-link device and the second multi-link device can simultaneously transmit the service data through the first link and the target second link, that is, transmit service data with the same TID.
  • the method provided by the embodiments of the present disclosure may further include: if it is detected that the transmission of the service data by the at least two links (e.g., the first link and the target second link) does not meet the service data transmission requirements, generating a second request frame to request that the service identifier be mapped to at least three links between the first multi-link device and the second multi-link device; receiving a second response frame returned by the second multi-link device in response to the second request frame; and if the second response frame indicates that the second multi-link device accepts the second request frame, transmitting the service data through the at least three links at the same time.
  • the at least two links e.g., the first link and the target second link
  • the first multi-link device can generate a second request frame to request the second multi-link device to map the service identifier to three or more links.
  • the second request frame may also be a TID-To-Link Mapping Request frame, and correspondingly, the second response frame may be a TID-To-Link Mapping Response frame, but the present disclosure is not limited thereto.
  • the generation and transmission process of the second request frame and the second response frame may refer to the first request frame and the first response frame described above.
  • the above-mentioned multi-link selection strategy may also include: if it is detected that the two links currently transmitting service data (e.g., the first link (taking link 1 as an example) and the target second link (taking link 2 as an example)) still cannot meet the service data transmission requirements, then detecting the channel quality information and/or congestion information of a third link that is not currently transmitting service data and has been established between the AP MLD and the Non-AP MLD.
  • the third link can be the remaining links other than the first link and the target second link among the multiple links already established between the AP MLD and the Non-AP MLD.
  • the generated second request frame includes a mapping relationship between the service identifier and the first link, the target second link, and the target third link, that is, the service identifier is mapped to the first link, the target second link, and the target third link, so that the service data can be transmitted simultaneously through the first link, the target second link, and the target third link.
  • the target third link may be one or more links, which is not limited in this disclosure.
  • a link can also be selected from the remaining second links as the target third link.
  • the embodiment of the present disclosure can achieve that when a small number of links transmitting business data cannot meet the business data transmission requirements, the links are gradually increased to transmit the business data in parallel. This can improve the reliability of business data transmission, reduce transmission latency, and avoid the business occupying too many links, resulting in waste of resources and affecting the data transmission of other businesses.
  • the above-mentioned first request frame and second request frame are only used for illustration and do not actually limit the number and number of request frames sent by the first multi-link device to the second multi-link device. After each update of the mapping relationship, the first multi-link device can detect whether the new mapping relationship can meet the business data transmission requirements.
  • a new request frame can be generated and sent to the second multi-link device until the upper limit of the number of links between the first multi-link device and the second multi-link device is reached, that is, all the links established between the two have been used to transmit the business data.
  • the following multi-link selection strategy may also be adopted: when it is detected that the first link is in the first state, in the first request frame, a request is made to map the service identifier to all links between the first multi-link device and the second multi-link device.
  • both the first multi-link device and the second multi-link device support negotiation of service-to-link mapping. That is, before the first multi-link device of the disclosed embodiment sends the first request frame to the second multi-link device, both the first multi-link device and the second multi-link device are capable of negotiating TID-To-Link Mapping.
  • the communication method provided by the embodiment of the present disclosure detects the service status and wireless channel environment of each link in multiple communication links that have established communication.
  • Non-AP MLD and AP MLD that support MLO they send request frames to each other through negotiation (for example, the first request frame and the second request frame mentioned above, which may be TID-To-Link Mapping Request frames), requesting to modify the low-latency service identifier (for example, TID) to map the service identifier to two or more established communication links, so that the two or more communication links send service data (for example, game data) with the same TID to improve the reliability of data transmission, thereby achieving the purpose of improving service experience.
  • TID low-latency service identifier
  • FIG4 illustrates the embodiment of the present disclosure using a gaming service as an example, where the first multi-link device is a Non-AP MLD and the first request frame is a TID-To-Link Mapping Request frame.
  • the method provided in the embodiment of the present disclosure may include the following steps.
  • game data is transmitted between the Non-AP MLD and the AP MLD through a link (e.g., link 1).
  • the Non-AP MLD detects that the wireless channel environment of the link being transmitted (for example, link 1) is poor or congested, and uses multiple links for transmission, generating a TID-To-Link Mapping Request frame to request that the TID of the gaming service be mapped to multiple links.
  • the Non-AP MLD sends a TID-To-Link Mapping Request frame to the AP MLD.
  • the Non-AP MLD that is transmitting game data with the AP MLD will be affected.
  • the Non-AP MLD detects changes in relevant wireless communication indicators (such as RSSI) of the link or the congestion of the link in real time, and then chooses to map the game TID to two or more links, generates a TID-To-Link Mapping Request frame, and sends the TID-To-Link Mapping Request frame to the AP MLD.
  • relevant wireless communication indicators such as RSSI
  • the AP MLD sends a TID-To-Link Mapping Response frame to the Non-AP MLD.
  • the AP MLD After receiving the TID-To-Link Mapping Request frame, the AP MLD generates a TID-To-Link Mapping Response frame and replies to the Non-AP MLD with a TID-To-Link Mapping Response frame to indicate whether the sender (i.e., the Non-AP MLD) has accepted or rejected the request.
  • the AP MLD in addition to accepting or rejecting the request, can also modify the TID-to-link mapping relationship requested in the TID-To-Link Mapping Request frame and then return the modified TID-to-link mapping relationship to the Non-AP MLD in a TID-To-Link Mapping Response frame.
  • the AP MLD may also detect changes in the wireless environment and congestion of ongoing transmission services (detect congestion of the link where data is being transmitted), and then select to map the game TID to two or more links, while sending a TID-To-Link Mapping Request frame to the Non-AP MLD.
  • the Non-AP MLD receives the TID-To-Link Mapping Request frame and sends a TID-To-Link Mapping Response frame to the AP MLD, as shown in Figure 5:
  • the AP MLD detects that the wireless channel environment of the link being transmitted is poor or congested, adopts multiple links for transmission, generates a TID-To-Link Mapping Request frame to request mapping the game TID to multiple links, and sends the generated TID-To-Link Mapping Request frame to the Non-AP MLD.
  • the Non-AP MLD sends a TID-To-Link Mapping Response frame to the AP MLD.
  • the Non-AP MLD After receiving the TID-To-Link Mapping Request frame, the Non-AP MLD responds with a TID-To-Link Mapping Response frame to the AP MLD, indicating whether the sender (i.e., the AP MLD) accepts or rejects the request.
  • the Non-AP MLD in addition to accepting or rejecting the request, can also modify the TID-to-link mapping relationship requested in the TID-To-Link Mapping Request frame and then return the modified TID-to-link mapping relationship to the AP MLD in a TID-To-Link Mapping Response frame.
  • Figure 6 schematically shows a flow chart of a multi-link selection strategy method according to an embodiment of the present disclosure. It should be noted that the multi-link selection strategy shown in Figure 6 is only an example, and the present disclosure is not limited thereto.
  • Link 1 Assume that AP MLD and Non-AP MLD have established Link 1, Link 2, and Link 3.
  • the service is a gaming service, and the initial decision is to transmit gaming data through Link 1.
  • S62 it is determined whether the current channel quality of link 1 is poor or whether the game data is congested; if not, S63 is executed; if yes, S64 is executed.
  • the process may return to step S61 to continue detecting the communication link 1 that is currently transmitting the game, and the above steps S61 to S63 may be executed in a loop.
  • S65 it is determined whether the current channel quality of link 2 and link 3 is poor or the game data is congested; if not, S66 is executed; if yes, S67 is executed.
  • link 2 or link 3 is selected to transmit the game data, that is, link 1 is switched to link 2 or link 3, and link 1 is no longer used to transmit game data.
  • AP MLD or non-AP MLD monitors the communication link currently transmitting the game data in real time, assuming it is Link 1.
  • Link 1 When the channel quality of Link 1 is poor or the service on Link 1 is congested, the AP will simultaneously monitor the channel quality and service congestion of other links, defined as Link 2 and Link 3.
  • the AP can then choose to transmit the same game data as Link 1 over Link 2 or Link 3. It then checks whether the transmission of the two links meets the game data transmission requirements. If so, the game data continues to be transmitted over the two links. If not, the same game data is transmitted simultaneously over Link 1, Link 2, and Link 3.
  • the embodiment of the present disclosure can implement the above negotiation process through two management frames in the IEEE series of protocols: TID-To-Link Mapping Request frame and TID-To-Link Mapping Response frame.
  • the TID-To-Link Mapping Request frame is sent by a Non-AP MLD to an AP MLD, or by an AP MLD to a Non-AP MLD, to negotiate and modify the mapping of TIDs to multiple communication links.
  • the format of the TID-To-Link Mapping Request frame can be shown in Table 1 below:
  • the TID-To-Link Mapping Response frame is mainly the response of the AP MLD or Non-AP MLD to the received TID-To-Link Mapping Request frame.
  • the format of the TID-To-Link Mapping Response frame can be shown in Table 2 below:
  • Both the TID-To-Link Mapping Request and TID-To-Link Mapping Response frames include the TID-To-Link Mapping element.
  • the data format of the TID-To-Link Mapping element is shown in Figure 7.
  • the TID-To-Link Mapping element includes an Element ID field, a Length field, an Element ID Extension field, a TID-To-Link Mapping Control field, a Mapping Switch Time field, and an Expected Duration field.
  • the TID-To-Link Mapping Control field includes a Direction field, a Default Link Mapping bit, a Mapping Switch Time Present field, an Expected Duration Present field, a Link Mapping Size field, and a Reserved field.
  • the TID-To-Link Mapping Control field also includes a Link Mapping Presence Indicator subfield.
  • the direction field when it is set to the first value (for example, 0), it indicates uplink; when it is set to the second value (for example, 1), it indicates downlink; when it is set to the third value, for example, 2, it indicates uplink and downlink; the fourth value, for example, 3, is a reserved value.
  • the default link mapping bit is used to indicate whether all TIDs are mapped to all links.
  • the default link mapping bit is set to the first value (e.g., 1), it indicates that all TIDs are mapped to all links. Assume that there are three communication links between the Non-AP MLD and the AP MLD: Link 1, Link 2, and Link 3.
  • the default link mapping bit is set to 1, TIDs 0 to 7 are mapped to Link 1, TIDs 0 to 7 are mapped to Link 2, and TIDs 0 to 7 are mapped to Link 3.
  • the Link Mapping Presence Indicator subfield indicates whether the Link Mapping of TIDn field exists in the TID-To-Link Mapping element. If the value of position n in the Link Mapping Presence Indicator subfield is the first value, such as 1, then the Link Mapping of TIDn field exists in the TID-To-Link Mapping element. Otherwise, the Link Mapping of TIDn field does not exist in the TID-To-Link Mapping element.
  • the Link Mapping Size field is used to indicate the size of the Link Mapping Of TIDn field, which can be 0, 1, or 2 bytes.
  • the link mapping field of TID0 is used to indicate which links TID0 is mapped to.
  • the field can carry a bitmap, and each bit in the bitmap can correspond to a link. If the value of a certain bit is 1, it means that TID0 is mapped to the link corresponding to the certain bit. For example, if the value of a certain bit is 0, it means that TID 0 is not mapped to the link corresponding to the certain bit.
  • the length of the above-mentioned bitmap can be equal to the maximum number of links that can be associated between the first multi-link device and the second multi-link device; or, the length of the above-mentioned bitmap can be a fixed value, such as 16 bits; or, the length of the above-mentioned bitmap can be equal to the number of associated links established between the first multi-link device and the second multi-link device, etc.
  • the embodiment of the present disclosure does not limit the setting method of the length of the above-mentioned bitmap.
  • the link mapping fields of other ITDs please refer to the link mapping field of TID0, which will not be described in detail here.
  • the TID0 to TID7 shown in the embodiments of this disclosure are merely examples.
  • the embodiments of this disclosure do not limit the number of link mapping fields for the TID in the service identification and link mapping element.
  • the number of link mapping fields for the TID in the service identification and link mapping element can be the same as the type of TID. For example, if the TIDs are expanded from TID0 to TID7 to TID0 to TID15, the number of link mapping fields for the TID can be equal to 16.
  • the service identifier of the game service is TID6 or TID7
  • a request is made to map the game service to at least two links
  • Link Mapping Of TID6 and Link Mapping Of TID7 exist in the TID-To-Link Mapping element, and Link Mapping Of TID6 corresponds to a 3-bit bitmap, representing Link1 to 3 respectively, and the value of the bitmap is [1 1 0]; Link Mapping Of TID7 corresponds to a 3-bit bitmap, and the value of the bitmap is [1 1 0].
  • the Mapping Switch Time field can be used to indicate the effective start time or effective time of the mapping between the service identifier and the link, or to indicate the effective start time or effective time of the mapping relationship between the service identifier and the link, or to indicate the time when the mapping relationship between the service identifier and the link is established.
  • the Mapping Switch Time Present field is used to indicate whether the Mapping Switch Time field exists in the TID-To-Link Mapping element.
  • the Expected Duration field can be used to indicate the expected end time of the mapping relationship between the service identifier and the link, or to indicate the expected end time of the mapping between the service identifier and the link.
  • the Expected Duration Present field is used to indicate whether the Expected Duration field exists in the TID-To-Link Mapping element.
  • Non-AP MLD can detect the wireless channel conditions of the communication link that is transmitting game data and the congestion conditions of the ongoing business. If the wireless channel is already below the set threshold value (poor channel quality) or the ongoing business is close to congestion or is already in a congested state, multiple links mapped by the business identifier are selected according to the multi-link selection strategy, and STA MLD (i.e., Non-AP MLD) actively sends a TID-To-Link Mapping negotiation message (such as the above-mentioned TID-To-Link Mapping request frame) to AP MLD, and it is recommended to map the low-latency game data TID to the high-level TID6 or TID7, and at the same time map it to two or more links in communication. In this way, low-latency game data can be transmitted on multiple links, thereby improving the reliability of game data and the user's gaming experience.
  • TID-To-Link Mapping negotiation message such as the above-mentioned TID-To-Link Mapping request frame
  • the AP MLD can perform multi-link mapping during the multi-link establishment process. Therefore, the first request frame can also be an Association Request Frame or a ReAssociation Request Frame, and correspondingly, the first response frame can be an Association Response Frame or a ReAssociation Response Frame.
  • the Non-AP MLD/AP MLD can send the desired modified TID-link mapping to the AP MLD/Non-AP by detecting relevant indicators during service.
  • the method provided by the embodiment of the present disclosure may include the following steps:
  • the Non-AP MLD detects the service congestion and wireless channel conditions of the communicating link (for example, link 1) in real time.
  • the communicating link When the communicating link is in a weak network environment or service congestion, it triggers TID-To-Link mapping negotiation, maps the game service data to the higher-level TID6 or TID7, and selects two or more communication links according to the strategy to map TID6 or TID7 to the selected links, and generates a TID-To-Link mapping request frame at the same time.
  • the Non-AP MLD sends a TID-To-Link mapping request frame to the AP MLD.
  • the AP MLD receives the TID-To-Link Mapping Request frame, obtains the TID-To-Link Mapping element recommended by the STA in the Non-AP MLD, accepts the recommended TID-To-Link Mapping element, accepts mapping TID6 or TID7 to two or more communication links, and generates a TID-To-Link Mapping Response frame.
  • the AP MLD may also choose to reject or modify the TID-To-Link mapping element recommended by the STA in the Non-AP MLD.
  • the AP MLD sends a TID-To-Link mapping response frame to the Non-AP MLD.
  • the AP MLD updates the TID-To-Link mapping element.
  • Non-AP MLD updates the TID-To-Link mapping element.
  • AP MLD and Non-AP MLD simultaneously support TID-To-Link Mapping negotiation.
  • the dot11MultiLinkActivated (multi-link activation field) and dot11TIDToLinkMappingActivated (service to link mapping activation field) carried in the association request frame or reassociation request frame, and the association response frame or reassociation response frame transmitted between the AP MLD and Non-AP MLD are set to the first value (e.g., true), and the TID-To-Link Mapping Negotiation Support (service to link mapping negotiation support) in the Capabilities and Operations (capabilities and operations) field in the Basic Multi-Link element (basic multi-link element) is set to non-zero (e.g., set to 3, but the present disclosure is not limited to this).
  • the above indication information indicates that both AP MLD and Non-AP MLD support the service to link mapping function. For example, it can be shown in the following Table 3:
  • Maximum Number of Simultaneous Links is used to indicate the maximum number of links on which service data of the same TID can be transmitted in parallel.
  • SRS single response scheduling
  • AAR AP assistance request
  • STR simultaneous transmit and receive
  • Frequency Separation For STR/AP MLD Type Indication refers to the frequency separation of STR/AP MLD type indication.
  • the two can negotiate to modify the TID mapping of a service to two or more communication links.
  • the AP MLD can also negotiate with the Non-AP MLD to modify the TID-to-communication link mapping, as shown in Figure 9, which may include the following steps:
  • AP MLD detects the congestion and network coverage of the ongoing gaming service communication link in real time. When the congestion exceeds the set threshold or is in a weak network environment, it triggers TID-To-Link mapping negotiation, maps the gaming service data to a higher-level TID6 or TID7, and maps TID6 or TID7 to two or more communication links selected according to the policy, and generates a TID-To-Link mapping request frame at the same time.
  • the AP MLD sends a TID-To-Link mapping request frame to the Non-AP MLD.
  • the Non-AP MLD receives the TID-To-Link Mapping Request frame, obtains the AP-recommended TID-To-Link Mapping element in the AP MLD, and accepts the AP-recommended TID-To-Link Mapping element, or recommends the TID-To-Link Mapping element to the sender (AP MLD), and generates a TID-To-Link Mapping Response frame.
  • the Non-AP MLD sends a TID-To-Link mapping response frame to the AP MLD.
  • Non-AP MLD updates the TID-To-Link mapping element.
  • the AP MLD updates the TID-To-Link mapping element.
  • Non-AP MLD wireless terminal
  • an AP or STA that supports multi-link and TID-To-Link Mapping can independently detect whether the network coverage of the link with which it is already communicating is weak or whether the service is congested, thereby deciding whether to trigger a request frame to be sent to the other party to modify the mapping relationship between the TID of the service and the link, mapping the TID of the service to two or more links.
  • the receiver After receiving the request frame, the receiver sends a mapping response frame of the TID of the service to two or more links to inform the other party whether to accept or reject the request frame.
  • both parties will update the rules for mapping the TID to two or more links.
  • the reliability of service data transmission can be improved, and the user's perception can be enhanced.
  • the reliability of the game can be improved in IEEE protocol multi-link transmission.
  • the method provided in the embodiment of Figure 10 may be performed by the second multi-link device. As shown in Figure 10 , the method provided in the embodiment of the present disclosure may include the following steps.
  • a first request frame sent by a first multi-link device is received, where the first request frame requests mapping of a service identifier of service data to at least two links between the first multi-link device and a second multi-link device, wherein the service data is currently transmitted between the first multi-link device and the second multi-link device via a first link, and the first link is in a first state; the first state indicates that a channel quality of the first link is lower than a threshold and/or is congested.
  • a first response frame is generated in response to the first request frame.
  • a first response frame is sent to the first multi-link device; wherein, when the second multi-link device receives the first request frame, the service data is transmitted through the at least two links at the same time.
  • FIG11 schematically illustrates a schematic structural diagram of a multi-link device 1100 according to an embodiment of the present disclosure.
  • the multi-link device can be a non-AP MLD or an AP MLD.
  • the multi-link device 1100 shown in FIG11 includes a processor 1110, which can call and execute a computer program from a memory to implement the method in the embodiment of the present disclosure.
  • the multi-link device 1100 may further include a memory 1120.
  • the processor 1110 may call and execute a computer program from the memory 1120 to implement the method in the embodiment of the present disclosure.
  • the memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .
  • the multi-link device 1100 may further include a transceiver 1130 .
  • the processor 1110 may control the transceiver 1130 to communicate with other devices.
  • the transceiver 1130 may send information or data to other devices or receive information or data sent by other devices.
  • the transceiver 1130 may include a transmitter and a receiver.
  • the transceiver 1130 may further include an antenna, and the number of antennas may be one or more.
  • the processor 1110 , the memory 1120 , and the transceiver 1130 may implement bidirectional communication with each other via the communication bus 1140 .
  • processor of the embodiment of the present disclosure may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment may be completed by hardware integrated logic circuits in the processor or software instructions.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the various methods, steps and logic block diagrams disclosed in the embodiments of the present disclosure can be implemented or executed.
  • the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present disclosure can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers, etc.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above-mentioned method in combination with its hardware.
  • the memory in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate synchronous DRAM
  • ESDRAM enhanced synchronous DRAM
  • SLDRAM synchronized DRAM
  • DR RAM direct RAM
  • the present disclosure also provides a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to a non-AP MLD or an AP MLD in the present disclosure.
  • the computer program causes the non-AP MLD or the AP MLD to execute the corresponding processes implemented by the non-AP MLD or the AP MLD in the various methods of the present disclosure. For the sake of brevity, these procedures are not further described here.
  • the present disclosure also provides a computer program product including computer program instructions.
  • the computer program product can be applied to the non-AP MLD or AP MLD in the present disclosure.
  • the computer program instructions cause the non-AP MLD or AP MLD to execute the corresponding processes implemented by the non-AP MLD or AP MLD in the various methods of the present disclosure. For the sake of brevity, these instructions are not further described here.
  • the present disclosure also provides a computer program.
  • the computer program can be applied to a non-AP MLD or AP MLD in the present disclosure.
  • the computer program runs on the non-AP MLD or AP MLD, it causes the non-AP MLD or AP MLD to execute the corresponding processes implemented by the non-AP MLD or AP MLD in the various methods of the present disclosure. For the sake of brevity, these procedures are not further described here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开实施例提供一种多链路设备通信方法及相关设备，属于通信技术领域。该方法由第一多链路设备执行，该方法包括：当检测到第一多链路设备和第二多链路设备之间传输业务数据的第一链路处于第一状态，生成第一请求帧，所述第一请求帧用于请求第二多链路设备将所述业务数据的第一业务标识映射到第一多链路设备和第二多链路设备之间的至少两条链路；其中，所述第一状态指示所述第一链路的信道质量低于阈值和/或存在拥塞；将第一请求帧向第二多链路设备发送；接收第二多链路设备返回的用于响应第一请求帧的第一响应帧；若所述第一响应帧指示所述第二多链路设备接受所述第一请求帧，同时通过所述至少两条链路传输所述业务数据。

Description

多链路设备通信方法及相关设备
本申请要求于2024年3月5日提交中国专利局、申请号为202410254637.7，发明名称为“通信方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及通信技术领域，具体而言，涉及一种多链路设备通信方法、多链路设备、计算机可读存储介质及计算机程序产品。
背景技术
电气与电子工程师协会(Institute of Electrical and Electronic Engineers，IEEE)组织制定关于无线局域网(wireless local access network，WLAN)的IEEE 802.11be协议标准引入了多链路(multi link，ML)机制。其中，多链路设备(Multi-linkDevice，MLD)可以支持在多条链路上进行数据传输。
技术内容
本公开实施例提供一种多链路设备通信方法，所述方法由第一多链路设备执行，所述方法包括：当检测到所述第一多链路设备和第二多链路设备之间传输业务数据的第一链路处于第一状态，生成第一请求帧，所述第一请求帧用于请求第二多链路设备将所述业务数据的第一业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少两条链路；其中，所述第一状态指示所述第一链路的信道质量低于阈值和/或存在拥塞；将所述第一请求帧向第二多链路设备发送；接收所述第二多链路设备返回的用于响应所述第一请求帧的第一响应帧；若所述第一响应帧指示所述第二多链路设备接受所述第一请求帧，同时通过所述至少两条链路传输所述业务数据。
本公开实施例提供一种多链路通信方法，所述方法由第二多链路设备执行，所述方法包括：接收第一多链路设备发送的第一请求帧，所述第一请求帧请求将业务数据的第一业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少两条链路，其中所述第一多链路设备和所述第二多链路设备之间当前通过第一链路传输所述业务数据，且所述第一链路处于第一状态；所述第一状态指示所述第一链路的信道质量低于阈值和/或存在拥塞；响应于所述第一请求帧生成第一响应帧；将所述第一响应帧发送至所述第一多链路设备；其中，当所述第二多链路设备接受所述第一请求帧，同时通过所述至少两条链路传输所述业务数据。
本公开实施例提供了一种多链路设备，包括：一个或多个处理器；存储器，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述多链路设备实现本公开实施例中所述的通信方法。
本公开实施例提供了一种计算机可读存储介质，其上存储有计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行时实现本公开实施例中所述的通信方法。
本公开实施例提供了计算机程序产品，包括计算机程序，该计算机程序被计算机执行时实现本公开实施例中所述的通信方法。
附图简要说明
图1是本公开实施例提供的一种多链路通信系统的示意图。
图2是本公开实施例提供的一种利用多链路传输游戏数据的应用场景示意图。
图3示意性示出了根据本公开的一些实施例的多链路设备通信方法的流程图。
图4示意性示出了根据本公开的一些实施例的多链路设备通信方法的交互示意图。
图5示意性示出了根据本公开的另一些实施例的多链路设备通信方法的交互示意图。
图6示意性示出了根据本公开的一些实施例的多链路选择策略方法的流程图。
图7示意性示出了根据本公开的一些实施例的业务到链路映射元素的格式示意图。
图8示意性示出了根据本公开的又一些实施例的多链路设备通信方法的交互示意图。
图9示意性示出了根据本公开的再一些实施例的多链路设备通信方法的交互示意图。
图10示意性示出了根据本公开的另一些实施例的多链路设备通信方法的流程图。
图11示意性示出了根据本公开的一些实施例的多链路设备的示意性结构图。
具体实施方式
为了本技术领域人员更好理解本公开的技术方案，下面结合本公开实施例中的附图，对本公开实施例中的技术方案进行描述。显然所描述的实施例是本公开一部分实施例，而不是全部的实施例。针对本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本公开保护的范围。
本公开实施例中，术语“模块”或“单元”是指有预定功能的计算机程序或计算机程序的一部分，并与其他相关部分一起工作以实现预定目标，并且可以通过使用软件、硬件(如处理电路或存储器)或其组合来全部或部分实现。同样的，一个处理器(或多个处理器或存储器)可以用来实现一个或多个模块或单元。此外，每个模块或单元都可以是包含该模块或单元功能的整体模块或单元的一部分。
本公开的说明书和权利要求书及附图中的术语“第一”、“第二”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们的任何变形，意图在于覆盖不排它的包含。例如，包含了一系列步骤或单元的过程、方法、软件、产品或设备没有限定于已列出的步骤或单元，而是还包括没有列出的步骤或单元，或还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本公开的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
本公开实施例中出现的“网络”与“系统”表达的是同一概念，通信系统即为通信网络。
本公开实施例可以应用于无线局域网(WLAN)。目前，WLAN采用的协议标准为IEEE 802.11系列。其中，WLAN可以包括多个基本服务集(basic service set，BSS)，而基本服务集中的设备可以包括接入点的站点(access point station，AP STA，也简称为AP或者接入点)和非接入点的站点(none access point station，Non-AP STA，也简称为STA或者站点)。另外，每个基本服务集可以包含一个接入点和至少一个站点。
接入点可以是经由无线媒体为与其连接的站点提供网络接入的实体。接入点可以将各个无线网络客户端接入以太网。接入点可以是无线保真(wireless fidelity，Wi-Fi)芯片的网络设备。接入点可以是支持各类IEEE 802.11协议标准的设备。例如，接入点可以是支持IEEE 802.11ac、IEEE 802.11n、IEEE 802.11g、IEEE 802.11b、IEEE802.11ax、IEEE802.11be、下一代WLAN协议标准等的设备。接入点可以包括集中式控制器、基站(base station，BS)、基站收发台(base transceiver station，BTS)、站点控制器和交换机等。接入点可以包括为站点提供无线通信功能的装置，例如芯片系统。其中，该芯片系统可以包括芯片，还可以包括其它分立器件，如收发器件等。接入点可以与互联网协议(Internet Protocol，IP)网络进行通信。例如，因特网(internet)、私有的IP网或者其他数据网等。
站点可以是无线通讯芯片、无线传感器或无线通信终端。例如，支持Wi-Fi通信功能的用户设备(user equipment，UE)、远程/远端终端(remote UE)、接入终端、用户单元、用户站、移动设备、用户终端、智能终端、无线通信设备、用户代理或用户装置/蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、手持设备、车载设备、可穿戴设备等，对此不作具体限定。站点可以包括非接入点增强型高吞吐量站点(none AP extremely high throughput station，non AP EHT STA)和非接入点高效率站点(none AP high efficiency station，non AP HE STA)等。站点可以包括具有收发功能的装置，例如芯片系统。其中，该芯片系统可以包括芯片，还可以包括其它分立器件，如收发器件等。
下面结合图1对本公开实施例的多链路通信系统做一个示例性说明。
IEEE 802.11be协议标准引入了多链路机制。支持多链路操作(MLO)的Wi-Fi设备为多链路设备(MLD)。其中，多链路设备(MLD)可以支持在多条链路上进行数据传输。多链路设备可以为接入点多链路设备(AP MLD)或者非接入点多链路设备(Non-AP MLD)。AP MLD可以包含多个接入点(AP，例如图1中以三个AP，即AP1，AP2，AP3举例说明，但本公开并不限定于此，可以包括更多或更少的AP)。Non-AP MLD可以包含多个站点(STA，例如图1中以三个STA，即STA1，STA2，STA3举例说明，但本公开并不限定于此，可以包括更多或更少的STA)。不同AP或者STA可以工作在不同的载频上，例如工作在2.4GHz、5GHz、6GHz(图1中分别简写为2.4G、5G、6G)等载频上或者相同频段(例如5GHz)的不同载频上。本公开实施例中，Non-AP MLD可以是支持多链路Wi-Fi 7(即无线局域网的技术标准IEEE 802.11be)的用户终端。AP MLD可以是支持多链路Wi-Fi 7的热点。
AP MLD与Non-AP MLD之间可以建立多条(两条或两条以上)链路(称之为多链路建立或多链路关联)，而数据可以在该多条链路上进行传输。
例如，如图1所示，假设AP1与STA1之间建立有链路L1(Link1的简写，即链路1)、AP2与STA2之间建立有链路L2(Link2的简写，即链路2)、AP3与STA3之间建立有链路L3(Link3的简写，即链路3)等，每条链路由链路ID(identity，标识)唯一标识。不同链路具有不同的工作载频。图1中假设L1、L2、L3的工作载频分别为2.4G、5G、6G，但本公开并不限定于此。
本公开实施例中，可以将业务数据的业务标识建立或更新为具有高优先级的业务标识，并将该业务标识映射到AP MLD和Non-AP MLD之间的多条链路。该业务数据所对应的业务可以是重要业务或者高速业务或者低时延业务，例如游戏业务、视频业务、音频业务、元宇宙业务等，下面均以游戏业务举例说明，但本公开并不限定于此。业务标识可以用于唯一标识业务数据的类型，例如语音服务类型、视频服务类型、尽力传输类型、背景流量类型等，以与其它类型的业务相区别开来，本公开对其表示形式不做限定，例如可以采用业务ID(Traffic ID，TID)表示。TID用于标识不同类型的流量。通过设置TID的值，可以区分不同类型的流量，从而为不同的流量提供不同的服务质量。例如，语音服务对延迟最为敏感，是优先级最高的流量。视频服务的优先级低于语音服务。网页访问的数据流量类型是尽力传输，其对于延迟有一定需求，但是没有那么敏感。背景流量对于延迟要求最不敏感。下面均以业务标识采用TID表示举例说明，但本公开并不限定于此。
例如，图1中假设可以用TID0至TID7(本公开并不限定于此，例如还可以用TID0至TID15)分别表示不同的业务标识，其中TID6或TID7对应的业务数据的优先级高于TID0-TID5对应的业务数据的优先级。假设游戏业务为低时延业务，则可以将游戏业务的业务数据的TID设置为或更新为TID6或TID7，以使游戏业务的业务数据具有比其它业务更高的优先级，从而使得游戏业务的数据优先传输，降低游戏业务的传输时延。对于业务标识映射到TID6或者TID7的游戏业务而言，可以将其业务标识TID6或者TID7映射到多条链路。例如图1中假设将游戏业务的TID6或者TID7同时映射到Link1、Link2和Link3，但本公开并不限定于此。由此使得可以同时通过Link1、Link2和Link3传输游戏业务数据，在IEEE协议多链路传输中提高游戏可靠性或者降低游戏时延。
在一些实施例中，图1所示的多链路通信系统还可以包括除AP MLD和Non-AP MLD之外的其他多链路设备、接入点或者站点等，对此不作具体限定。
在一些实施例中，图1所示的多链路通信系统还可以包括接入网(radio access network，RAN)设备、核心网(core network，CN)设备、网络控制器、移动管理实体等其它网络实体，对此不作具体限定。
在一些实施例中，图1所示的多链路通信系统中的AP MLD和Non-AP MLD之间的通信可以为无线通信或者有线通信，对此不作具体限制。
在图1实施例的基础上，即假设已经将游戏业务的TID6或者TID7映射到Link1至Link3，如图2所示，则AP MLD和Non-AP MLD之间可以同时通过工作载频为2.4GHz的Link1、工作载频为5GHz的Link2、以及工作载频为6GHz的Link3传输TID6或者TID7游戏数据(即业务数据)。
本公开实施例提供的多链路通信系统，能够同时利用多个天线和频谱资源进行业务数据传输，使得AP MLD和Non-AP MLD可以同时在多个频段上进行通信，提高了网络吞吐量和稳定性，减少拥塞和干扰，提高整体网络性能。多链路传输还可以增加网络的可靠性，即使某个频段或天线出现拥塞或干扰，AP MLD和Non-AP MLD仍然可以通过结合其它可用的链路进行通信，从而减少数据丢失的可能性。
在I EEE协议中引入了多链路操作(Multi-link Operation，MLO)特性，支持MLO的AP和STA能够在建立的多条链路(例如，2.4GHz，5GHz，6GHz等)中的一条链路传输数据，也可以在多条(两条或者两条以上)通信链路中同时传输同一业务的数据，每条通信链路之间可以互补，减少数据帧的重传，提高数据传输的可靠性。这样多条链路都传输同样TID的业务数据，例如，对于游戏业务来讲，特别是在网络覆盖弱的环境下，通过多条链路传输游戏数据，能大大提高传输可靠性，提升游戏的体验。本公开实施例通过检测已经建立好通信的多条通信链路中，每条链路的业务情况和无线信道环境情况，对于支持MLO的Non-AP MLD和AP MLD通过协商的方式向对方发送请求帧(包括第一请求帧，在一些实施例中，还包括第二请求帧)，以请求修改低时延游戏业务的TID映射到已经建立好的多条通信链路，使多条通信链路发送游戏数据，来提高数据传输的可靠性，以达到提升游戏体验的目的。
本公开实施例中，“同时传输同一业务的数据”是指Non-AP MLD和AP MLD之间已经建立的多条链路上并行的传输具有同样业务标识例如同样TID的业务数据。其中，进一步又可以采用两种模式。一种模式是多发单收(复制模式)，即AP/STA端多个频段/多条链路同时发送该同样TID的一个相同的数据给接收端(STA/AP)，接收端自动选择最快速的频段/链路的数据，如果频段受到干扰，系统则接受其它频段的数据。这种方式可以提升数据传输的稳定性。另一种模式是多发多收(联合模式)，即把该同样TID的一份数据拆成多份(例如三份)，分别通过多个(例如三个)频段/多条(例如三条)链路同时发送，接收端收到后将该多份数据组合。多发多收模式可以提升数据传输的速度。
例如，当该业务数据为游戏业务的游戏数据时，则是指“同时传输同一游戏业务的游戏数据”，即Non-AP MLD和AP MLD之间已经建立的多条链路上并行的传输具有游戏业务的TID所对应的游戏数据。可以将同一份游戏数据复制多份在多条链路上并行传输，以提高游戏数据的传输可靠性，例如可以在信道环境弱的情况下采取这种模式；也可以将同一份游戏数据拆成多份游戏数据在多条链路上并行传输，以提高游戏数据的传输速度，例如可以在游戏业务存在拥塞的情况下采取这种模式。
本公开实施例中，检测链路的业务情况是指检测Non-AP MLD和AP MLD之间已经建立的至少一条链路上正在传输的业务(例如可以包括业务)的数据传输是否存在拥塞。在一些实施例中，可以通过检测其拥塞信息来判断其拥塞程度，可以划分不同的拥塞等级来表示不同的拥塞程度，或者通过拥塞信息来判断其是否处于拥塞状态。例如，可以通过被检测的该条链路从发送端(Non-AP MLD/AP MLD)向接收端(AP MLD/Non-AP MLD)周期性地向发送ping包(是一种测试网络连接用的数据包)，等待接收该接收端发送回来的信号，由此让发送端获得数据包从发送端传输到接收端并返回所需的时间，这个时间被称为发送端与接收端之间的等待时间，也可以称为ping值，通过ping值的大小可以划分不同的拥塞等级，或者判断该链路是否处于拥塞状态。例如，如果某条链路上的ping值超过规定的时长则可以判定该链路是拥塞的，反之，则判定是非拥塞的。本公开对检测链路的业务情况的方式不限于上述举例。
本公开实施例中，检测链路的无线信道环境情况是指检测Non-AP MLD和AP MLD之间已经建立的至少一条链路的信道质量信息，通过该信道质量信息来判断被检测的链路是否处于弱网环境。该信道质量信息可以通过一个或多个指标来指示，例如信道质量指示(Channel Quality Indicator，CQI)、信号强度、信噪比、误码率、传输速率、数据在信道中传输的时间延迟等。在下面的实施例中，以检测相关无线通信指标例如接收信号强度指示(Received Signal Strength Indication，RSSI)的变化来判断链路的无线信道环境情况，即信道质量信息包括RSSI。当检测到某条链路的RSSI低于阈值(其大小可以根据实际需求进行设置，本公开对其不做限定)时，判定该链路处于弱网环境；反之，则判定该链路未处于弱网环境。
图3实施例提供的通信方法可以由第一多链路设备执行。
在一些实施例中，第一多链路设备为接入点多链路设备(AP MLD，也可以称之为AP多链路设备)或非接入点多链路设备(Non-AP MLD，也可以称之为STA多链路设备)。多链路指的是AP与STA之间有多条通信链路。与之对应的，下文中提及的第二多链路设备为非接入点多链路设备(Non-AP MLD)或接入点多链路设备(AP MLD)。
在S310中，当检测到第一多链路设备和第二多链路设备之间传输业务数据的第一链路处于第一状态，生成第一请求帧，所述第一请求帧用于请求第二多链路设备将所述业务数据的业务标识映射到第一多链路设备和第二多链路设备之间的至少两条链路；其中，所述第一状态指示所述第一链路的信道质量低于阈值和/或存在拥塞。
本公开实施例中，AP MLD和Non-AP MLD之间已经建立至少一条链路，且从该至少一条链路中确定了第一链路用于传输业务数据。其中，业务数据可以是指任一业务的数据，例如任意一种重要业务，高优先级业务，时延敏感业务/低时延业务，高速业务，以下以游戏业务举例说明。该第一链路可以包括一条链路，也可以包括两条或两条以上的链路。以下以第一链路包括一条链路(以下以链路1或者Link1表示)进行举例说明，但本公开并不限定于此。该第一链路可以是AP MLD和Non-AP MLD之间已经建立的至少一条链路中的任意一条或任意多条链路。
在一些实施例中，所述第一状态指示所述第一链路的信道质量低于阈值，和/或，所述第一链路上传输的业务存在拥塞。
本公开实施例中，一条链路可以传输不同的业务，本公开实施例提出的方法针对任一业务例如有时延要求的游戏业务。当一条链路有多个业务数据在传输时，若根据拥塞检测机制检测到存在拥塞，AP MLD可以根据策略进行选择，例如选择两条或三条链路同时传输业务数据，或者切换到另外一条信道质量好且不拥塞的链路进行传输，这个策略可以扩展到其它业务，不只针对游戏业务。在一些实施例中，其它业务的TID不映射到TID6或者TID7，TID6或者TID7专门针对低时延要求的游戏业务。
当AP MLD和Non-AP MLD之间通过第一链路传输该业务数据时，第一多链路设备可以检测该第一链路的信道质量信息和/或拥塞信息，根据该信道质量信息和/或该拥塞信息判断该第一链路是否处于第一状态。若该信道质量信息指示该第一链路的信道质量低于阈值，即信道质量差，和/或，该拥塞信息指示该第一链路上传输的业务存在拥塞，或处于拥塞状态，则可以判定该第一链路处于第一状态。若该信道质量信息指示该第一链路的信道质量等于或高于阈值，即信道质量好，且，该拥塞信息指示该第一链路上传输的业务不存在拥塞或不处于拥塞状态，则可以判定该第一链路不处于该第一状态，即不处于弱网环境且未发生拥塞。
当第一多链路设备检测到正在传输业务数据的第一链路的信道质量差和/或业务数据传输存在拥塞时，该第一多链路设备可以生成第一请求帧，并将该第一请求帧发送至第二多链路设备，以请求第二多链路设备将该业务数据对应的业务标识(例如业务的TID)映射至AP MLD和Non-AP MLD之间的至少两条链路。
在一些实施例中，第一多链路设备生成的第一请求帧中可以携带第一多链路设备所建议或所要求的该至少两条链路与该业务标识之间的映射关系，此时，第一多链路设备可以根据多链路选择策略来确定该至少两条链路。
本公开实施例中的多链路选择策略是指当AP MLD和Non-AP MLD之间需要通过两条或两条以上的链路来传输业务数据时，从AP MLD和Non-AP MLD之间已经建立的多条链路中选择两条或两条以上用于传输业务数据的方式。该多链路选择策略可以根据实际需求进行设置。
在一些实施例中，在生成第一请求帧之前，所述方法可以进一步包括：
若所述第一链路处于所述第一状态，检测所述第一多链路设备和所述第二多链路设备之间的至少一条第二链路的状态；所述至少一条第二链路为所述第一多链路设备和所述第二多链路设备之间已建立的链路中除所述第一链路之外的链路；
从所述至少一条第二链路中选择处于第二状态或者第三状态的至少一条目标第二链路，将所述第一链路和所述至少一条目标第二链路确定为所述至少两条链路。
在一些实施例中，所述处于第二状态的所述至少一条目标第二链路的信道质量低于阈值和/或存在拥塞；
所述处于第三状态的所述至少一条目标第二链路的信道质量高于阈值且不存在拥塞。
例如，该多链路选择策略可以包括：如果当前正在传输业务数据的第一链路为一条链路(以链路1为例)，且该第一链路信道质量差和/或业务传输发生了拥塞，则检测当前未传输业务数据、且已经在AP MLD和Non-AP MLD之间建立的第二链路的信道质量信息和/或拥塞信息。该第二链路可以是该AP MLD和Non-AP MLD之间已经建立的多条链路中，除第一链路以外的剩余链路，该剩余链路包括至少一条链路；也可以是剩余链路中的任意一条链路。即可以检测除了第一链路以外的每条链路的信道质量信息和/或拥塞信息，以判断除第一链路以外的每条链路是否处于第二状态，如果某条第二链路的信道质量差和/或业务存在拥塞，则可以选择该条第二链路作为目标第二链路。如果存在多条第二链路的信道质量差和/或业务存在拥塞，则可以从该多条第二链路中任意选择一条第二链路作为目标第二链路。或者，选择除第一链路以外的任意一条链路作为第二链路，检测其信道质量信息和/或拥塞信息，以判断被选择的该条第二链路是否处于第二状态。如果该第二链路处于第二状态，则将该第二链路确定为目标第二链路；反之，则继续从剩余链路中选择新的第二链路，检测其信道质量信息和/或拥塞信息，以判断该新的第二链路是否处于第二状态。如此循环执行，直到从剩余链路中确定出目标第二链路。在确定出目标第二链路之后，在生成的第一请求帧中包含业务标识与该第一链路与该目标第二链路之间的映射关系，即将业务标识映射到第一链路与目标第二链路，以使得业务数据能够同时通过第一链路与目标第二链路传输。即当正在传输业务数据的一条第一链路的信道质量差和/或存在业务拥塞时，可以循序的先选择两条信道质量差和/或存在业务拥塞的链路同时进行业务数据的传输，以此提高业务数据传输的可靠性，降低传输时延。
可以理解的是，虽然上述举例中以选择第一链路和目标第二链路作为同时传输业务数据的两条链路，即第一链路继续用于传输业务数据，但本公开并不限定于此。再例如，如果检测到剩余链路中存在多条第二链路的信道质量差和/或存在业务拥塞，则可以从该多条第二链路中选择任意两条第二链路作为目标第二链路，第一链路不继续用于传输该业务数据，此时第一请求帧中包含两条目标第二链路与该业务标识之间的映射关系。
再例如，该多链路选择策略还可以包括：若检测到一条或多条第二链路处于第三状态，即存在一条或多条第二链路的信道质量好且不存在业务拥塞，则可以从选择任意一条第二链路作为目标第二链路，该第一请求帧用于请求将该第一链路切换为该目标第二链路，即通过该目标第二链路来传输该业务数据，即第一请求帧中携带业务标识与该目标第二链路的映射关系。
再例如，该多链路选择策略还可以包括：若检测到多条第二链路处于第三状态，即存在多条第二链路的信道质量好且不存在业务拥塞，则可以从选择任意两条第二链路作为目标第二链路，该第一请求帧用于请求通过该两条目标第二链路来传输该业务数据，即第一请求帧中携带业务标识与该两条目标第二链路的映射关系。
再例如，该多链路选择策略还可以包括：若检测到至少一条第二链路处于第三状态，即存在至少一条第二链路的信道质量好且不存在业务拥塞，则可以从选择任意一条第二链路作为目标第二链路，该第一请求帧用于请求通过第一链路和该目标第二链路来传输该业务数据，即第一请求帧中携带业务标识与第一链路和目标第二链路的映射关系。
需要说明的是，由于第一多链路设备和第二多链路设备预先已知业务标识是映射到第一链路的，则当第一多链路设备通过第一请求帧请求将该业务标识映射到至少两条链路时，该第一请求帧可以只携带业务标识与目标第二链路的映射关系，即默认该业务标识与该第一链路的映射关系继续保留。
本公开实施例，可以将不同优先级和不同的链路进行绑定，因此，在多链路选择策略中，还可以根据链路与优先级之间的绑定关系来选择业务标识映射到的该至少两条链路。例如，假设第一请求帧请求将业务标识从低优先级的第一业务标识修改为高优先级的第二业务标识，而该高优先级的第二业务标识已经与预定的链路进行了绑定，例如高优先级的第二业务标识已经与链路1、链路2和链路3进行了绑定，则当第二多链路设备接收到该第一请求帧时，即可以获知第一多链路设备是在请求将该业务标识映射到链路1、链路2和链路3，即第一请求帧请求将业务标识映射到至少两条链路可以是隐性的，即不一定需要在该第一请求帧中指示出该业务标识与该至少两条链路的映射关系。例如可以在开始进行业务时进行链路与优先级的绑定。在业务进行过程中，由于STA站点的移动性，可能会导致信道质量变差或者某条链路数据业务拥塞，此时可以采取本公开实施例提供的方式协商业务的TID与链路的映射。
在一些实施例中，所述第一请求帧包含指示将所述业务标识从第一业务标识转换为第二业务标识的信息，其中，所述第二业务标识的优先级高于所述第一业务标识的优先级。
本公开实施例中，假设在生成第一请求帧之前，AP MLD和Non-AP MLD之间已经确定了业务标识为第一业务标识，例如为TID2，且TID2映射到Link1。当第一多链路设备检测到Link1的信道质量差和/或存在业务拥塞时，第一多链路设备可以将该业务标识修改为更高优先级的第二业务标识，例如修改为TID6或者TID7。此时，该第一请求帧中可以携带将第一业务标识修改为该更高优先级的第二业务标识的信息，以请求第二多链路设备将该第一业务标识修改为第二业务标识，即可以通过提高业务的优先级来达到降低延迟的目的。
在另一些实施例中，若在生成第一请求帧之前，AP MLD和Non-AP MLD之间已经确定的业务标识已具有较高的优先级，例如本身即为TID6或TID7，则可以不用修改该业务标识。
本公开实施例中可以通过服务质量(Quality of Service，QoS)来实现。QoS是一种网络的安全机制,是用来解决网络延迟和阻塞等问题的一种技术。当网络过载或拥塞时，QoS能确保重要业务不受延迟或丢弃，同时保证网络的高效运行。例如，对于游戏程序，能够提高游戏程序的网络优先级别，从而达到降低延迟的目的，提高游戏体验。
在一些实施例中，所述第一请求帧为业务到链路映射请求(TID-To-Link Mapping Request)帧。与之对应的，第二多链路设备生成的用于响应该第一请求帧的第一响应帧可以为业务到链路映射响应(TID-To-Link Mapping Response)帧。但本公开并不限定于此，在其它实施例中，第一请求帧和第一响应帧可以有其它命名。
在一些实施例中，业务到链路映射请求帧包括业务到链路映射元素(TID-To-Link Mapping element)。可以在该TID-To-Link Mapping element中携带业务标识与该至少两条链路之间的映射关系。
在一些实施例中，业务到链路映射元素包括业务到链路映射控制(TID-To-Link Mapping Control)字段。在一些实施例中，业务到链路映射控制字段包括链路映射出现指示(Link Mapping Presence Indicator)子字段。链路映射出现指示子字段的第一值用于指示业务到链路映射元素中存在业务标识到链路映射字段(例如Link Mapping Of TID6或者Link Mapping Of TID7)。
在一些实施例中，业务标识到链路映射字段用于指示业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少两条链路。
可以理解的是，第一请求帧携带的用于请求将业务标识映射到至少两条链路的指示信息不限于上述举例，其只要是能够表示该指示信息的任意方式，可以是显式的，也可以是隐式的。
在S320中，将第一请求帧向第二多链路设备发送。第二多链路设备接收第一多链路设备发送的第一请求帧。
在S330中，接收第二多链路设备返回的用于响应第一请求帧的第一响应帧；若所述第一响应帧指示所述第二多链路设备接受所述第一请求帧，同时通过所述至少两条链路传输所述业务数据。
第二多链路设备接收到该第一请求帧后，可以根据自身情况、链路情况、链路与业务的映射关系、网络状况等来决定接受还是拒绝该第一请求帧，或者修改该第一请求帧中携带的映射关系，以此来生成返回给第一多链路设备的第一响应帧，并向第一多链路设备发送生成的第一响应帧。
在一些实施例中，所述第一请求帧中携带的映射关系为第一映射关系。
当所述第一响应帧中包含所述第二多链路设备确定的第二映射关系时，若所述第一多链路设备接受所述第二映射关系，则将所述第一多链路设备中的所述业务标识与所述第一链路之间的映射关系更新为所述第二映射关系。
在一些实施例中，当所述第一请求帧中不携带第一映射关系、所述第一响应帧中包含第二映射关系时，所述第二映射关系为所述第二多链路设备根据第一请求帧确定的所述业务标识与所述至少两条链路之间的映射关系。
在一些实施例中，当所述第一请求帧携带第一映射关系、所述第一响应帧包含第二映射关系时，所述第二映射关系为所述第二多链路设备对所述第一映射关系进行修改得到的。
在一些实施例中，第一多链路设备(例如STA站点或者AP)可以仅请求第二多链路设备(例如AP或者STA站点)将该业务标识映射到至少两条链路，即在该第一请求帧中可以不携带第一多链路设备所要求或所建议的至少两条链路，当该第二多链路设备接受该第一请求帧时，由第二多链路设备来选择映射到该业务标识的该至少两条链路，第二多链路设备通过第一响应帧将第二多链路设备所选择的该至少两条链路与该业务标识的映射关系返回至第一多链路设备。当该第二多链路设备拒绝该第一请求帧时，第二多链路设备返回的第一响应帧中可以包含拒绝该第一请求帧的指示信息。在一些实施例中，该第一响应帧中还可以包含拒绝该第一请求帧的原因。
在另一些实施例中，第一多链路设备可以在第一请求帧中携带第一多链路设备所要求的至少两条链路与该业务标识之间的映射关系，第二多链路设备接收到该第一请求帧时，其只能选择接受或拒绝该第一请求帧，不能提出第二多链路设备所建议或要求的新的至少两条链路与该业务标识之间的映射关系。如果该第二多链路设备接受该第一请求帧，则向第一多链路设备返回的第一响应帧中包含接受该第一请求帧的指示信息。若该第二多链路设备拒绝该第一请求帧，则第二多链路设备返回的第一响应帧中包含拒绝该第一请求帧的指示信息。在一些实施例中，该第一响应帧中还可以包含拒绝该第一请求帧的原因。
在又一些实施例中，第一多链路设备可以在第一请求帧中携带第一多链路设备所建议的至少两条链路与该业务标识之间的映射关系，第二多链路设备接收到该第一请求帧时，其可以选择接受或拒绝该第一请求帧，或者修改第一请求帧中所建议的至少两条链路与该业务标识之间的映射关系，即第二多链路设备还可以提出该第二多链路设备所建议或要求的新的至少两条链路与该业务标识之间的映射关系。若该第二多链路设备修改第一请求帧中所建议的至少两条链路与该业务标识之间的映射关系，则第二多链路设备可以选择映射到该业务标识的新的至少两条链路，第二多链路设备通过第一响应帧将第二多链路设备所选择的新的至少两条链路与该业务标识的映射关系返回至第一多链路设备。该新的至少两条链路可以与第一请求帧中的至少两条链路完全不同，也可以部分相同，部分不同，本公开对此不做限定。如果该第二多链路设备接受该第一请求帧，则向第一多链路设备返回的第一响应帧中包含接受该第一请求帧的指示信息。若该第二多链路设备拒绝该第一请求帧，则第二多链路设备返回的第一响应帧中包含拒绝该第一请求帧的指示信息。在一些实施例中，该第一响应帧中还可以包含拒绝该第一请求帧的原因。
在一些实施例中，本公开实施例提供的方法还可以包括：若所述第一响应帧指示所述第二多链路设备接受所述第一请求帧，则根据所述第一响应帧将所述第一多链路设备中的所述业务标识与所述第一链路之间的映射关系更新为所述第一映射关系。
第二多链路设备接受该第一请求帧时，第二多链路设备可以在生成第一响应帧的同时，将第二多链路设备中的该业务标识与第一链路之间的映射关系更新为所述第一映射关系。
可以理解的是，上述实施例是以第一请求帧中携带了第一链路和目标第二链路与业务标识的第一映射关系、且第二多链路设备接受了该第一请求帧举例说明的。在其它实施例中，若第二多链路设备修改了第一请求帧中的第一映射关系，提出了新的映射关系(第二映射关系)，且第一多链路设备接受了第一响应帧中携带的第二映射关系，则第一多链路设备和第二多链路设备分别业务标识与第一链路之间的映射关系更新为所述第二映射关系。若第二多链路设备拒绝了该第一请求帧，或者第一多链路设备拒绝了第一响应帧中的新的映射关系，则第一多链路设备和第二多链路设备均不进行业务标识与第一链路之间的映射关系的更新，即仍然采用第一链路传输业务数据。
在一些实施例中，本公开实施例提供的方法还可以包括：通过所述第一链路和所述目标第二链路并行的传输所述业务数据。当第二多链路设备接受第一请求帧中携带的业务标识与第一链路和目标第二链路之间的映射关系时，向第一多链路设备返回第一响应帧时，更新第二多链路设备上的该业务标识与链路之间的映射关系，即从业务标识与第一链路的映射关系更新为，业务标识与第一链路以及目标第二链路之间的映射关系。第一多链路设备接收到该第一响应帧后，更新第一多链路设备上的该业务标识与链路之间的映射关系。映射关系更新完成后，第一多链路设备和第二多链路设备可以通过第一链路和该目标第二链路同时传输该业务数据，即传输同样TID的业务数据。
在一些实施例中，本公开实施例提供的方法还可以包括：若检测到所述至少两条链路(例如，所述第一链路和所述目标第二链路)传输所述业务数据未达到业务数据传输要求，则生成第二请求帧，以请求将所述业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少三条链路；接收所述第二多链路设备返回的用于响应所述第二请求帧的第二响应帧；若所述第二响应帧指示所述第二多链路设备接受所述第二请求帧，同时通过所述至少三条链路传输所述业务数据。
例如，当采用两条链路同时传输具有相同TID的业务数据时，可以检测该两条链路同时传输业务数据是否达到了业务数据传输要求，业务数据传输要求可以根据该业务的具体要求来确定，例如业务的数据传输时延要求、传输速度要求等。如果采用两条链路仍然未达到该业务数据传输要求，则第一多链路设备可以生成第二请求帧，以请求第二多链路设备将该业务标识映射到三条或三条以上链路。
第二请求帧也可以是TID-To-Link Mapping Request帧，对应的，第二响应帧可以是TID-To-Link Mapping Response帧，但本公开并不限定于此。第二请求帧和第二响应帧的生成和传输过程可以参考上述第一请求帧和第一响应帧。
上述多链路选择策略还可以包括：如果检测到当前正在传输业务数据的两条链路(例如第一链路(以链路1为例)和目标第二链路(以链路2为例))仍然不能达到业务数据传输要求，则检测当前未传输业务数据、且已经在AP MLD和Non-AP MLD之间建立的第三链路的信道质量信息和/或拥塞信息。该第三链路可以是该AP MLD和Non-AP MLD之间已经建立的多条链路中，除第一链路和目标第二链路以外的其它剩余链路。以判断第三链路是否处于第二状态，如果第三链路的信道质量差和/或业务存在拥塞，则可以从第三链路中选择一条链路作为目标第三链路(以链路3为例)。在确定出目标第三链路之后，在生成的第二请求帧中包含业务标识与该第一链路与该目标第二链路、以及目标第三链路之间的映射关系，即将业务标识映射到第一链路、目标第二链路与目标第三链路，以使得业务数据能够同时通过第一链路、目标第二链路与目标第三链路传输。该目标第三链路可以是一条或者多条链路，本公开对此不做限定。
再例如，如果在上述确定目标第二链路时，检测了多条第二链路的信道质量信息和/或拥塞信息，且存在多条第二链路的信道质量差和/或业务拥塞，且只从中选择了部分第二链路作为目标第二链路，则在确定目标第三链路时，也可以从剩余的第二链路中选择链路作为目标第三链路。
本公开实施例通过设置上述多链路选择策略，可以实现当数量较少的链路传输业务数据，不能满足业务数据传输要求时，循序渐进的递增链路来并行的传输该业务数据，由此可以提高业务数据传输的可靠性，降低传输时延，又可以避免业务占据过多的链路，造成资源的浪费，避免影响其它业务的数据传输。上述第一请求帧和第二请求帧仅用于举例说明，实际并不限定第一多链路设备向第二多链路设备发送请求帧的次数和数量，第一多链路设备可以在每次更新映射关系之后，检测新的映射关系是否可以满足业务数据传输要求，如果未达到要求，则可以生成新的请求帧发送给第二多链路设备，直至达到该第一多链路设备和第二多链路设备之间的链路条数的上限，即已经采用了两者之间所有已经建立的链路来传输该业务数据。
可以理解的是，在其它实施例中，也可以采用如下多链路选择策略：当检测到第一链路处于第一状态时，在该第一请求帧中，请求将该业务标识映射到该第一多链路设备和第二多链路设备之间的所有链路上。
在一些实施例中，所述第一多链路设备和所述第二多链路设备均支持业务到链路映射的协商。即本公开实施例的第一多链路设备在向第二多链路设备发送第一请求帧之前，该第一多链路设备和第二多链路设备均能够进行TID-To-Link Mapping的协商。
本公开实施方式提供的通信方法，通过检测已经建立好通信的多条通信链路中每条链路的业务情况和无线信道环境情况，对于支持MLO的Non-AP MLD和AP MLD通过协商的方式向对方发送请求帧(例如上述第一请求帧和第二请求帧，可以为TID-To-Link Mapping Request帧)，请求修改低时延业务标识(例如TID)，以将业务标识映射到已经建立好的两条或者多条通信链路，使两条或者多条通信链路发送同样TID的业务数据(例如游戏数据)来提高数据传输的可靠性，以达到提升业务体验的目的。
图4实施例以游戏业务，且第一多链路设备为Non-AP MLD，第一请求帧为TID-To-Link Mapping Request帧进行举例说明。如图4所示，本公开实施例提供的方法可以包括如下步骤。
在S41中，Non-AP MLD和AP MLD之间通过链路(例如链路1)进行游戏数据传输。
在S42中，Non-AP MLD检测到正在传输的链路(例如链路1)无线信道环境差或者拥塞，采用多条链路传输，生成TID-To-Link Mapping Request帧，以请求将游戏业务的TID映射到多条链路。
在S43中，Non-AP MLD向AP MLD发送TID-To-Link Mapping Request帧。
由于无线环境的变化，与AP MLD正在进行游戏数据传输的Non-AP MLD会受到影响，同时Non-AP MLD实时检测该链路的相关无线通信指标(例如RSSI)的变化或者该链路的拥塞情况，然后选择将游戏TID映射到两条或者多条链路，生成TID-To-Link Mapping Request帧，并将该TID-To-Link Mapping Request帧发送给AP MLD。
在S44中，AP MLD向Non-AP MLD发送TID-To-Link Mapping Response帧。
AP MLD收到该TID-To-Link Mapping Request帧后，生成TID-To-Link Mapping Response帧，向Non-AP MLD回复TID-To-Link Mapping Response帧，来告诉发送方(即Non-AP MLD)接收或者拒绝该请求。在一些实施例中，除了接受或拒绝以外，AP MLD还可以修改TID-To-Link Mapping Request帧所请求的TID与链路的映射关系，然后将修改后的TID与链路的映射关系携带在TID-To-Link Mapping Response帧，返回给Non-AP MLD。
在另一些实施例中，AP MLD也可以检测无线环境的变化和正在进行传输的业务拥塞情况(检测正在数据传输的链路的拥塞情况)，然后选择将游戏TID映射到两条或者多条链路，同时向Non-AP MLD发送TID-To-Link Mapping Request帧，Non-AP MLD接收TID-To-Link Mapping请求帧，向AP MLD发送TID-To-Link Mapping Response帧，如图5所示：
在S51中，AP MLD检测到正在传输的链路无线信道环境差或者拥塞，采用多条链路传输，生成TID-To-Link Mapping Request帧，以请求将游戏TID映射到多条链路，并将生成的TID-To-Link Mapping Request帧发送至Non-AP MLD。
在S52中，Non-AP MLD向AP MLD发送TID-To-Link Mapping Response帧。
Non-AP MLD收到该TID-To-Link Mapping Request帧后，向AP MLD回复TID-To-Link Mapping Response帧，来告诉发送方(即AP MLD)接受或者拒绝该请求。在一些实施例中，除了接受或拒绝以外，Non-AP MLD还可以修改TID-To-Link Mapping Request帧所请求的TID与链路的映射关系，然后将修改后的TID与链路的映射关系携带在TID-To-Link Mapping Response帧，返回给AP MLD。
图6示意性示出了根据本公开的一实施例的多链路选择策略方法的流程图。需要说明的是，图6所示的多链路选择策略仅是一种举例说明，本公开并不限定于此。
在S61中，检测正在进行游戏传输的通信链路1。
假设AP MLD和Non-AP MLD已经建立了链路1、链路2和链路3，以业务为游戏业务，且开始确定的是通过链路1来传输游戏数据为例。
在S62中，判断链路1的当前信道质量是否差或者游戏数据是否拥塞；如果否，则执行S63；如果是，则执行S64。
在S63中，如果链路1的当前信道质量好，且游戏数据未拥塞，则继续当前通信链路(例如链路1)传输游戏数据。
在一些实施例中，可以回到S61中继续检测正在进行游戏传输的通信链路1，循环执行上述S61至S63。
在S64中，如果链路1的当前信道质量差，或者游戏数据拥塞，则检测通信链路2和链路3信道质量和数据拥塞情况。
在S65中，判断链路2和链路3的当前信道质量差或者游戏数据拥塞；如果否，则执行S66；如果是，则执行S67。
在S66中，如果链路2和链路3的当前信道质量好，且未发生拥塞，则选择链路2或链路3传输游戏数据，即从链路1切换为链路2或链路3，链路1不再用于传输游戏数据。
在S67中，如果链路2或链路3的当前信道质量差，或者发生拥塞，则选择链路2或链路3传输游戏数据，同时也在链路1传输游戏数据。然后执行S68。
在S68中，检测两条链路传输是否达到了游戏数据传输要求；如果未达到，则执行S69；如果已达到，则执行S610。
在S69中，如果未达到游戏数据传输要求，则同时在三条链路传输游戏数据。
在S610中，如果已达到游戏数据传输要求，则继续在当前两条通信链路传输游戏数据。
本公开实施例中，AP MLD或者Non-AP MLD实时检测正在进行游戏传输的通信链路，假设为链路1，当该链路1的信道质量差或者链路1上的业务存在拥塞时，会同时检测其他的链路的信道质量和业务拥塞情况，定义为链路2和链路3，可以选择在链路2或者链路3上传输链路1同样的游戏数据。然后检测到两条链路的传输是否达到游戏数据传输要求，如果满足，继续在该两条链路上传输游戏数据，如果未满足，则同时在链路1，链路2，链路3上传输同样的游戏数据。
本公开实施例可以通过IEEE系列协议中的两条管理帧：TID-To-Link Mapping Request帧和TID-To-Link Mapping Response帧来实现上述协商过程。
TID-To-Link Mapping Request帧由Non-AP MLD向AP MLD发送，或者AP MLD向Non-AP MLD发送，协商修改TID到多条通信链路的映射。其中，TID-To-Link Mapping Request帧的格式可以如下表1所示：
表1.TID-To-Link Mapping Request帧格式
TID-To-Link Mapping Response帧主要是AP MLD或者Non-AP MLD对接收到TID-To-Link Mapping Request帧的响应。其中，TID-To-Link Mapping Response帧的格式可以如下表2所示：
表2.TID-To-Link Mapping Response帧格式
TID-To-Link Mapping Request帧和TID-To-Link Mapping Response帧中均包括TID-To-Link Mapping(业务到链路映射元素)。TID-To-Link Mapping元素的数据格式如图7所示。
如图7所示，TID-To-Link Mapping元素包括元素ID(Element ID)字段、长度(Length)字段、扩展元素ID(Element ID Extension)字段、以及TID到链路映射控制(TID-To-Link Mapping Control)字段、映射转换时间(Mapping Switch Time)字段、预期持续时间(Expected Duration)字段等。TID到链路映射控制字段中包括方向(Direction)字段、默认链路映射(Default Link Mapping)比特、映射转换时间存在(Mapping Switch Time Present)字段、预期持续时间存在(Expected Duration Present)字段、链路映射大小(Link Mapping Size)字段、保留(Reserved)字段。可选(Optional)的，TID到链路映射控制字段中还包括链路映射出现/存在指示(Link Mapping Presence Indicator)子字段。
其中，当方向字段设置为第一值(例如0)时表示上行；设置为第二值(例如1)时表示下行；设置为第三值例如2时为上下行；第四值例如3为保留值。
默认链路映射比特，用于指示是否将所有的TID映射到所有链路上。当默认链路映射比特设置为第一值(例如1)时，表示将所有的TID映射到所有链路上。假设Non-AP MLD与AP MLD之间共有3条通信的链路，分别是Link1，Link2，Link3。当默认链路映射比特置1时，将TID 0～7映射到Link1上，和TID 0～7映射到Link2上，以及TID 0～7映射到Link3上。
Link Mapping Presence Indicator子字段指示，在TID-To-Link Mapping元素中，是否存在“Link Mapping Of TIDn”字段。如果Link Mapping Presence Indicator子字段的位置n的值为第一值例如1，则表示TIDn的链路映射(Link Mapping Of TIDn)字段存在于TID-To-Link Mapping元素中。否则，TIDn的链路映射字段在TID-To-Link Mapping元素中不存在。
Link Mapping Size字段用于指示Link Mapping Of TIDn字段的大小，可以0或者1或者2字节。
TID0的链路映射字段用于可以指示TID0被映射到了哪些链路上，如该字段可以承载一个比特位图，该比特位图中的每个比特可以对应一条链路。如某个比特的值是1则表示TID0被映射到了该某个比特所对应的链路上。又如某个比特的值是0，则表示TID 0没有被映射到该某个比特所对应的链路上。示例性的，上述比特位图的长度可以等于第一多链路设备和第二多链路设备之间所能关联的链路的最大数量；或者，上述比特位图的长度可以为固定值，如16个比特；又或者，上述比特位图的长度可以等于第一多链路设备和第二多链路设备之间已建立的关联链路的数量等，本公开实施例对于上述比特位图的长度的设置方式不作限定。对于其它ITD的链路映射字段的说明可以参考TID0的链路映射字段，这里不再详述。本公开实施例所示的TID0至TID7仅为示例，随着标准的演进，后续可能还会有更多的业务类型，如TID0至TID15等，因此对于业务标识与链路映射元素中的TID的链路映射字段的个数，本公开实施例不作限定。示例性的，业务标识与链路映射元素中的TID的链路映射字段的个数可以与TID的种类相同。如TID从TID0至TID7扩展到TID0至TID15时，TID的链路映射字段的个数可以等于16。
本公开实施例中，假设游戏业务的业务标识为TID6或者TID7，且请求将游戏业务映射到至少两条链路，例如请求将TID6或者TID7映射到Link1和Link2，则TID-To-Link Mapping元素中存在Link Mapping Of TID6和Link Mapping Of TID7，Link Mapping Of TID6中对应一个3比特的位图，分别表示Link1～3，则该比特位图的取值为[1 1 0]；Link Mapping Of TID7中对应一个3比特的位图，则该比特位图的取值为[1 1 0]。
Mapping Switch Time字段可以用于指示业务标识与链路映射的生效开始时间或生效时间，或者，用于指示业务标识与链路之间的映射关系的生效开始时间或生效时间，或者，用于指示业务标识与链路的映射关系被建立的时间。Mapping Switch Time Present字段用于指示Mapping Switch Time字段是否存在于TID-To-Link Mapping元素中。Expected Duration字段可以用于指示业务标识与链路的映射关系的期望结束时间，或者，用于指示业务标识与链路映射的预期结束时间。Expected Duration Present字段用于指示Expected Duration字段是否存在于TID-To-Link Mapping元素中。
本公开实施例中，AP MLD和Non-AP MLD多链路建立成功后，Non-AP MLD可以检测正在传输游戏数据的通信链路的无线信道情况和正在进行中的业务的拥塞情况，如果无线信道已经低于设定的门限值(信道质量差)或者正在进行的业务已经接近拥塞或者已经处于拥塞状态，根据多链路选择策略选择该业务标识映射的多条链路，STA MLD(即Non-AP MLD)主动向AP MLD发送TID-To-Link Mapping协商的消息(例如上述TID-To-Link Mapping请求帧)，建议将低时延的游戏数据TID映射到高等级的TID6或者TID7，并同时映射到正在通信的两条或者多条链路，这样的话，低时延的游戏数据能够在多链路传输，提高了游戏数据的可靠性和用户的游戏体验。
本公开实施例中，AP MLD在多链路建立的过程中可以进行多链路映射，因此第一请求帧也可以为关联请求帧(Association Request Frame)或重关联请求帧(ReAssociation Request Frame)，对应的，第一响应帧可以为关联响应帧(Association Response Frame)或重关联响应帧(ReAssociation Response Frame)。Non-AP MLD/AP MLD可以在业务进行中，通过检测相关指标向AP MLD/Non-AP发送期望修改的TID与链路的映射。
如图8所示，本公开实施例提供的方法可以包括以下步骤：
在S81中，Non-AP MLD实时检测正在通信链路(例如链路1)的业务拥塞情况和无线信道情况，当正在通信的链路处在弱网环境或者业务拥塞时，触发TID-To-Link映射协商，将游戏业务数据映射到高等级的TID6或者TID7，并根据策略选择两条或者多条通信链路将TID6或者TID7映射到选择的链路，同时生成TID-To-Link映射请求帧。
在S82中，Non-AP MLD发送TID-To-Link映射请求帧至AP MLD。
在S83中，AP MLD接收TID-To-Link映射请求帧，获得Non-AP MLD中的STA推荐的TID-To-Link映射元素，并接受推荐的TID-To-Link映射元素，接受将TID6或者TID7映射到两条或者多条通信链路，同时生成TID-To-Link映射响应帧。
在一些实施例中，AP MLD也可以选择拒绝或修改Non-AP MLD中的STA推荐的TID-To-Link映射元素。
在S84中，AP MLD发送TID-To-Link映射响应帧至Non-AP MLD。
在S85中，AP MLD更新TID-To-Link映射元素。
在S86中，Non-AP MLD更新TID-To-Link映射元素。
本公开实施例中，AP MLD和Non-AP MLD同时支持TID-To-Link Mapping的协商，AP MLD和Non-AP MLD之间传输的关联请求帧或重关联请求帧、以及关联响应帧或重关联响应帧中携带的dot11MultiLinkActivated(多链路激活字段)和dot11TIDToLinkMappingActivated(业务到链路映射激活字段)设置为第一值(例如true)，并且在Basic Multi-Link element(基本多链路元素)字段中的Capabilities and Operations(能力和操作)中的TID-To-Link Mapping Negotiation Support(业务到链路映射协商支持)中设置为非零(例如设置为3，但本公开并不限定于此)。通过上述指示信息来指示AP MLD和Non-AP MLD均支持业务到链路映射功能。例如可以如下表3所示：
表3
Maximum Number Of Simultaneous Links，最大并发链路数量，用于指示同样TID的业务数据最多可以在多少条链路上并行的传输。SRS(single response scheduling，单响应调度)是一种控制帧。SRS Support可以用于指示是否接受该关联请求帧或重关联请求帧携带SRS Control(控制)。AAR(AP assistance request，AP辅助请求)也是一种控制帧。AAR Support可以用于指示是否接受该关联请求帧或重关联请求帧携带AAR Control(控制)。STR(simultaneous transmit and receive，同时发射和接收)是指多链路中同时发生接收中的链路之间的间隔。Frequency Separation For STR/AP MLD Type Indication是指STR/AP MLD类型指示的频率分离。
当AP MLD和Non-AP MLD都支持TID到链路映射的协商时，通过两者协商以达到修改业务的TID映射到两条或者多条通信链路的目的。在另一些实施例中，AP MLD也可以向Non-AP MLD协商修改TID到通信链路的映射，如图9所示，可以包括以下步骤：
在S91中，AP MLD实时检测正在进行游戏业务通信链路的拥塞情况和网络覆盖情况，当拥塞情况超过设定的门限值或者处在弱网环境中，触发TID-To-Link映射协商，将游戏业务数据映射到高等级的TID6或者TID7，并将TID6或者TID7映射到根据策略选择的两条或者多条通信链路，同时生成TID-To-Link映射请求帧。
在S92中，AP MLD发送TID-To-Link映射请求帧至Non-AP MLD。
在S93中，Non-AP MLD接收TID-To-Link映射请求帧，获得AP MLD中的AP推荐的TID-To-Link映射元素，并接受AP推荐的TID-To-Link映射元素，或者向发送者(AP MLD)推荐TID-To-Link映射元素，同时生成TID-To-Link映射响应帧。
在S94中，Non-AP MLD发送TID-To-Link映射响应帧至AP MLD。
在S95中，Non-AP MLD更新TID-To-Link映射元素。
在S96中，AP MLD更新TID-To-Link映射元素。
本公开实施例涉及到在Wi-Fi无线网络中，无线终端(Non-AP MLD)进行低时延业务例如游戏业务，在网络覆盖弱的场景或者业务拥塞场景，支持多链路同时也支持TID-To-Link Mapping的AP或者STA，能够独自的检测已经与之通信的链路的网络覆盖是否弱或者业务是否拥塞，从而决定是否触发向对方发送修改业务的TID与链路的映射关系，将业务的TID映射到两条或者多条Link的请求帧，接收方收到该请求帧后，相对应发送业务的TID到两条或者多条Link的映射响应帧，来告知对方是否接受或者拒绝该请求帧，如果接受，双方都会更新TID映射到两条或者多条Link的规则。通过以上的改进点的优化，特别是低时延业务传输过程中，能够根据网络覆盖状况和业务拥塞情况，自适应优化业务数据在两条或者多条链路传输，尤其在无线网络覆盖弱的场景下，或者正在进行的业务存在拥塞场景下，能够提高业务数据传输的可靠性，提升用户的感知。当该业务为游戏时，可以实现在IEEE协议多链路传输中提高游戏的可靠性。
图10实施例提供的方法可以由第二多链路设备执行。如图10所示，本公开实施例提供的方法可以包括以下步骤。
在S1010中，接收第一多链路设备发送的第一请求帧，第一请求帧请求将业务数据的业务标识映射到第一多链路设备和第二多链路设备之间的至少两条链路，其中第一多链路设备和第二多链路设备之间当前通过第一链路传输所述业务数据，且第一链路处于第一状态；所述第一状态指示所述第一链路的信道质量低于阈值和/或存在拥塞。
在S1020中，响应于第一请求帧生成第一响应帧。
在S1030中，将第一响应帧发送至第一多链路设备；其中，当所述第二多链路设备接受所述第一请求帧，同时通过所述至少两条链路传输所述业务数据。
图10实施例的其它内容可以参考上述其它实施例。
图11示意性示出了根据本公开的一实施例的多链路设备1100的示意性结构图。该多链路设备可以是Non-AP MLD或AP MLD，图11所示的多链路设备1100包括处理器1110，处理器1110可以从存储器中调用并运行计算机程序，以实现本公开实施例中的方法。
在一些实施例中，如图11所示，多链路设备1100还可以包括存储器1120。其中，处理器1110可以从存储器1120中调用并运行计算机程序，以实现本公开实施例中的方法。
其中，存储器1120可以是独立于处理器1110的一个单独的器件，也可以集成在处理器1110中。
在一些实施例中，如图11所示，多链路设备1100还可以包括收发器1130，处理器1110可以控制该收发器1130与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1130可以包括发射机和接收机。收发器1130还可以进一步包括天线，天线的数量可以为一个或多个。
在一些实施例中，处理器1110、存储器1120以及收发器1130之间可以通过通信总线1140实现相互之间的双向通信。
应理解，本公开实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。
上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本公开实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(SynchlinkDRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。应理解，上述存储器为示例性但不是限制性说明。
本公开实施例还提供了一种计算机可读存储介质，用于存储计算机程序。在一些实施例中，该计算机可读存储介质可应用于本公开实施例中的Non-AP MLD或AP MLD，并且该计算机程序使得Non-AP MLD或AP MLD执行本公开实施例的各个方法中由Non-AP MLD或AP MLD实现的相应流程，为了简洁，在此不再赘述。
本公开实施例还提供了一种计算机程序产品，包括计算机程序指令。在一些实施例中，该计算机程序产品可应用于本公开实施例中的Non-AP MLD或AP MLD，并且该计算机程序指令使得Non-AP MLD或AP MLD执行本公开实施例的各个方法中由Non-AP MLD或AP MLD实现的相应流程，为了简洁，在此不再赘述。
本公开实施例还提供了一种计算机程序。在一些实施例中，该计算机程序可应用于本公开实施例中的Non-AP MLD或AP MLD，当该计算机程序在Non-AP MLD或AP MLD上运行时，使得Non-AP MLD或AP MLD执行本公开实施例的各个方法中由Non-AP MLD或AP MLD实现的相应流程，为了简洁，在此不再赘述。
本公开实施例描述的网络架构以及业务场景是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。

Claims (14)

  1. 一种多链路设备通信方法，由第一多链路设备执行，所述方法包括：
    当检测到所述第一多链路设备和第二多链路设备之间传输业务数据的第一链路处于第一状态，生成第一请求帧，所述第一请求帧用于请求第二多链路设备将所述业务数据的第一业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少两条链路；其中，所述第一状态指示所述第一链路的信道质量低于阈值和/或存在拥塞；
    将所述第一请求帧向第二多链路设备发送；
    接收所述第二多链路设备返回的用于响应所述第一请求帧的第一响应帧；
    若所述第一响应帧指示所述第二多链路设备接受所述第一请求帧，同时通过所述至少两条链路传输所述业务数据。
  2. 根据权利要求1所述的方法，其中，所述第一请求帧中包括所述第一业务标识和所述至少两条链路之间的第一映射关系。
  3. 根据权利要求1或2所述的方法，进一步包括：
    若所述第一链路处于所述第一状态，则检测所述第一多链路设备和所述第二多链路设备之间的至少一条第二链路的状态；所述至少一条第二链路为所述第一多链路设备和所述第二多链路设备之间已建立的链路中除所述第一链路之外的链路；
    从所述至少一条第二链路中选择处于第二状态或第三状态的至少一条目标第二链路，将所述第一链路和所述至少一条目标第二链路确定为所述至少两条链路。
  4. 根据所述权利要求3所述的方法，其中，所述处于第二状态的所述至少一条目标第二链路的信道质量低于阈值和/或存在拥塞；
    所述处于第三状态的所述至少一条目标第二链路的信道质量高于阈值且不存在拥塞。
  5. 根据权利要求1至4任一项所述的方法，进一步包括：
    若检测到所述至少两条链路传输所述业务数据未达到传输要求，则生成第二请求帧，以请求将所述第一业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少三条链路；
    接收所述第二多链路设备返回的用于响应所述第二请求帧的第二响应帧；
    若所述第二响应帧指示所述第二多链路设备接受所述第二请求帧，同时通过所述至少三条链路传输所述业务数据。
  6. 根据权利要求1至5任一项所述的方法，还包括：
    若所述第一响应帧指示所述第二多链路设备接受所述第一请求帧，则根据所述第一响应帧将所述第一多链路设备中的所述第一业务标识与所述第一链路之间的映射关系更新为所述第一映射关系；
    若所述第一响应帧指示所述第二多链路设备拒绝所述第一请求帧，则继续通过所述第一链路传输所述业务数据。
  7. 根据权利要求1至6任一项所述的方法，还包括：
    当所述第一响应帧中包含所述第二多链路设备确定的第二映射关系时，若所述第一多链路设备接受所述第二映射关系，则将所述第一多链路设备中的所述第一业务标识与所述第一链路之间的映射关系更新为所述第二映射关系；
    其中，所述第二映射关系为所述第二多链路设备根据所述第一请求帧确定的所述第一业务标识与所述至少两条链路之间的映射关系；或者所述第二映射关系为所述第二多链路设备对所述第一请求帧中包括的所述第一业务标识和所述至少两条链路之间的第一映射关系进行修改得到的。
  8. 根据权利要求1所述的方法，所述第一请求帧中包含指示将所述第一业务标识修改为第二业务标识的信息，其中，所述第二业务标识的优先级高于所述第一业务标识的优先级。
  9. 根据权利要求8所述的方法，进一步包括：
    根据链路与优先级之间的绑定关系，将与所述第二业务标识绑定的链路作为所述至少两条链路。
  10. 根据权利要求1至7所述的方法，所述第一请求帧为业务到链路映射请求帧；
    所述业务到链路映射请求帧包括业务到链路映射元素；
    所述业务到链路映射元素包括业务到链路映射控制字段；
    所述业务到链路映射控制字段包括链路映射出现指示子字段，所述链路映射出现指示子字段的第一值用于指示所述业务到链路映射元素中存在业务标识到链路映射字段；
    所述业务标识到链路映射字段用于指示所述第一业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少两条链路。
  11. 一种多链路设备通信方法，由第二多链路设备执行，所述方法包括：
    接收第一多链路设备发送的第一请求帧，所述第一请求帧请求将业务数据的第一业务标识映射到所述第一多链路设备和所述第二多链路设备之间的至少两条链路，其中所述第一多链路设备和所述第二多链路设备之间当前通过第一链路传输所述业务数据，且所述第一链路处于第一状态；所述第一状态指示所述第一链路的信道质量低于阈值和/或存在拥塞；
    响应于所述第一请求帧生成第一响应帧；
    将所述第一响应帧发送至所述第一多链路设备；其中，当所述第二多链路设备接受所述第一请求帧，同时通过所述至少两条链路传输所述业务数据。
  12. 一种多链路设备，包括：
    处理器；
    存储器，配置为存储计算机程序或指令，当计算机程序或指令被所述处理器执行时，使得所述多链路设备实现权利要求1至10中任一项所述的方法；或者，实现权利要求11中所述的方法。
  13. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，其特征在于，当所述计算机程序在计算机上运行时，使得所述计算机执行权利要求1至10中任一项所述的方法；或者，实现权利要求11中所述的方法。
  14. 一种计算机程序产品，包括计算机程序，其特征在于，该计算机程序被处理器执行时实现权利要求1至10中任一项所述的方法；或者，实现权利要求11中所述的方法。
PCT/CN2025/076186 2024-03-05 2025-02-07 多链路设备通信方法及相关设备 Pending WO2025185385A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410254637.7 2024-03-05
CN202410254637.7A CN120603014A (zh) 2024-03-05 2024-03-05 通信方法及相关设备

Publications (2)

Publication Number Publication Date
WO2025185385A1 true WO2025185385A1 (zh) 2025-09-12
WO2025185385A8 WO2025185385A8 (zh) 2025-10-02

Family

ID=96887549

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/076186 Pending WO2025185385A1 (zh) 2024-03-05 2025-02-07 多链路设备通信方法及相关设备

Country Status (2)

Country Link
CN (1) CN120603014A (zh)
WO (1) WO2025185385A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115209568A (zh) * 2021-04-09 2022-10-18 成都极米科技股份有限公司 多链路系统业务流数据传输的管理方法、装置及存储介质
CN115280894A (zh) * 2020-03-11 2022-11-01 松下电器（美国）知识产权公司 用于多链路建立和链路维持的通信装置和通信方法
WO2023083053A1 (zh) * 2021-11-15 2023-05-19 华为技术有限公司 多链路通信方法、装置及可读存储介质
US20230403598A1 (en) * 2021-04-22 2023-12-14 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Traffic identifier-to-link mapping methods and multi-link devices
US20230413328A1 (en) * 2022-05-03 2023-12-21 Ofinno, Llc Multi-link Flexible Target Wake Time with account for Cross-link Switching Delay

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115280894A (zh) * 2020-03-11 2022-11-01 松下电器（美国）知识产权公司 用于多链路建立和链路维持的通信装置和通信方法
CN115209568A (zh) * 2021-04-09 2022-10-18 成都极米科技股份有限公司 多链路系统业务流数据传输的管理方法、装置及存储介质
US20230403598A1 (en) * 2021-04-22 2023-12-14 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Traffic identifier-to-link mapping methods and multi-link devices
WO2023083053A1 (zh) * 2021-11-15 2023-05-19 华为技术有限公司 多链路通信方法、装置及可读存储介质
US20230413328A1 (en) * 2022-05-03 2023-12-21 Ofinno, Llc Multi-link Flexible Target Wake Time with account for Cross-link Switching Delay

Also Published As

Publication number Publication date
CN120603014A (zh) 2025-09-05
WO2025185385A8 (zh) 2025-10-02

Similar Documents

Publication Publication Date Title
CN113411831B (zh) 数据传输的方法和装置
US11509597B2 (en) Data transmission method and device
US20180199215A1 (en) Filtering extended range frames by high efficiency wireless (hew) stations
US20260113065A1 (en) Methods for improving wireless performance using auxiliary radios
JP2009105989A (ja) ワイヤレスローカルエリアネットワーク（ＷＬＡＮｓ）に対する、選択的通信速度とスケジューリング制御および関連方法を有するアクセスポイント
CN114679795B (zh) 无线局域网中的通信方法、装置及系统
JP2016536903A (ja) 高効率無線通信における適応ｒｔｓ／ｃｔｓ
WO2024109614A1 (zh) 信息指示方法及设备
EP3061308A2 (en) Integration of cellular and wlan systems
WO2021135413A1 (zh) 一种节能控制方法及相关设备
EP4643608A1 (en) Period for multi-access point communication
CN116017583A (zh) 业务优先级确定方法以及相关装置
TW202515223A (zh) 無線網路中的能源管理
WO2006092801A2 (en) Wireless lan with contention avoidance
JP2025138807A (ja) 通信装置、通信装置の制御方法、およびそのプログラム
KR102968137B1 (ko) 스테이션 전송을 위한 다중 액세스 포인트 조정
CN113747501B (zh) 一种通信方法及装置
CN116980968B (zh) 一种多链路的数据传输方法和装置
CN113115257B (zh) 一种连接配置方法、设备及存储介质
CN121753403A (zh) 用于无缝漫游的上下文获取
JP2024075270A (ja) 通信装置、制御方法、及び、プログラム
JP2024531982A (ja) 無線通信ネットワークのためのアソシエーションソリューション
CN120603014A (zh) 通信方法及相关设备
US20240154764A1 (en) Method and apparatus for transmitting and receiving block ack in wireless communication system supporting multi-link
WO2026020464A1 (zh) 关联方法、装置、设备、介质及产品

Legal Events

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

Ref document number: 25767129

Country of ref document: EP

Kind code of ref document: A1