WO2023174434A1 - 数据传输方法、装置、芯片、芯片模组及电子设备 - Google Patents

数据传输方法、装置、芯片、芯片模组及电子设备 Download PDF

Info

Publication number
WO2023174434A1
WO2023174434A1 PCT/CN2023/082605 CN2023082605W WO2023174434A1 WO 2023174434 A1 WO2023174434 A1 WO 2023174434A1 CN 2023082605 W CN2023082605 W CN 2023082605W WO 2023174434 A1 WO2023174434 A1 WO 2023174434A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
mapping relationship
traffic identifier
preset value
mapping
Prior art date
Application number
PCT/CN2023/082605
Other languages
English (en)
French (fr)
Inventor
顾祥新
Original Assignee
展讯通信（上海）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 展讯通信（上海）有限公司 filed Critical 展讯通信（上海）有限公司
Publication of WO2023174434A1 publication Critical patent/WO2023174434A1/zh

Links

Classifications

    • 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/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present application relates to communication technology, and in particular, to a data transmission method, device, chip, chip module and electronic equipment.
  • the IEEE 802.11be standard introduces multi-link (ML) technology.
  • a multi-link device (Multi-Link Device, MLD) can contain multiple stations (Station, STA), so that two MLDs can Create multiple links.
  • STA stations
  • data can be transmitted on multiple links, and the link for transmitting data can be determined by the mapping relationship (TID to link mapping) from the traffic ID (TID) to the link.
  • TID-To-Link Mapping negotiation When one party's MLD initiates TID-To-Link Mapping negotiation, the other party's MLD chooses to accept or reject based on its own situation. This may result in the link in the finally established TID-To-Link Mapping being unable to meet the requirements for initiating TID-To-Link Mapping negotiation. The needs of MLD.
  • This application provides a data transmission method, device, chip, chip module and electronic equipment to ensure that data is transmitted according to QoS requirements.
  • this application provides a data transmission method, applied in a first multi-link device, including:
  • mapping relationship negotiation message from a traffic identifier to a link to the second multi-link device, where the mapping relationship negotiation message from a traffic identifier to a link includes a sending reason and a relationship between the target traffic identifier and the first link set.
  • the link in the first link set is used for transmission. Data corresponding to the target traffic identifier.
  • the traffic identifier to link mapping relationship negotiation message is a traffic identifier to link mapping relationship request frame, or a traffic identifier to link mapping relationship response frame.
  • mapping relationship between the target traffic identifier and the first link set is carried in the mapping relationship element from the traffic identifier to the link, and the sending reason is carried in the reason field;
  • the cause field precedes the mapping relationship element from the traffic identifier to the link, or the cause field is in the mapping relationship element from the traffic identifier to the link.
  • the mapping relationship element between the traffic identifier and the link includes a type field, and the type field is used to represent that the mapping relationship between the target traffic identifier and the first link set is a recommendation. , preferred or mandatory.
  • the mapping relationship negotiation message from the traffic identifier to the link is a mapping relationship response frame from the traffic identifier to the link, and the mapping relationship response frame from the traffic identifier to the link includes a status code, and the The status code is used to indicate that the mapping relationship between the target traffic identifier and the first link set is mandatory.
  • the sending reason includes link quality, load balancing or power saving.
  • the sending reason is link quality; and sending a traffic identifier to link mapping relationship negotiation message to the second multi-link device includes:
  • a mapping relationship negotiation message from a traffic identifier to a link is sent to the second multi-link device.
  • the link quality includes at least one of the following: signal strength, signal quality, or link status.
  • the link quality includes signal strength
  • the step of sending a mapping relationship negotiation message from a traffic identifier to a link to the second multi-link device based on the link quality of each link in the second link set includes:
  • the The second multi-link device sends a mapping relationship negotiation message between the traffic identifier and the link.
  • it also includes:
  • the mapping relationship negotiation message between the traffic identifier and the link is sent to the second multi-link device again.
  • the link quality includes signal quality
  • the step of sending a mapping relationship negotiation message from a traffic identifier to a link to the second multi-link device based on the link quality of each link in the second link set includes:
  • the The second multi-link device sends a mapping relationship negotiation message between the traffic identifier and the link.
  • it also includes:
  • the second multi-link device sends a mapping relationship negotiation message between the traffic identifier and the link.
  • this application provides a data transmission device applied in a first multi-link device, including:
  • a sending module configured to send a mapping relationship negotiation message from a traffic identifier to a link to the second multi-link device, where the mapping relationship negotiation message from a traffic identifier to a link includes a sending reason and a target traffic identifier and the first link
  • a transmission module configured to use the link in the first link set to transmit the data corresponding to the target traffic identifier after the negotiation based on the sending reason is successful.
  • the traffic identifier to link mapping relationship negotiation message is a traffic identifier to link mapping relationship request frame, or a traffic identifier to link mapping relationship response frame.
  • mapping relationship between the target traffic identifier and the first link set is carried in the mapping relationship element from the traffic identifier to the link, and the sending reason is carried in the reason field;
  • the cause field precedes the mapping relationship element from the traffic identifier to the link, or the cause field is in the mapping relationship element from the traffic identifier to the link.
  • the mapping relationship element between the traffic identifier and the link includes a type field, and the type field is used to represent that the mapping relationship between the target traffic identifier and the first link set is a recommendation. , preferred or mandatory.
  • the traffic identifier to link mapping relationship negotiation message is a traffic identifier to link mapping relationship response frame, and the traffic identifier to link mapping relationship response frame contains A status code is included, and the status code is used to indicate that the mapping relationship between the target traffic identifier and the first link set is mandatory.
  • the sending reason includes link quality, load balancing or power saving.
  • the sending reason is link quality; the sending module is used to:
  • a mapping relationship negotiation message from a traffic identifier to a link is sent to the second multi-link device.
  • the link quality includes at least one of the following: signal strength, signal quality, or link status.
  • the link quality includes signal strength
  • the sending module is used for:
  • the The second multi-link device sends a mapping relationship negotiation message between the traffic identifier and the link.
  • the sending module is used for:
  • the multi-link device sends a mapping relationship negotiation message between the traffic identifier and the link.
  • the link quality includes signal quality
  • the sending module is used for:
  • the The second multi-link device sends a mapping relationship negotiation message between the traffic identifier and the link.
  • the sending module is used for:
  • the second multi-link device sends a mapping relationship negotiation message between the traffic identifier and the link.
  • this application provides a chip including: a memory and a processor
  • the memory is used to store computer programs
  • the processor is configured to implement the method described in the first aspect when the computer program is executed.
  • the present application provides a chip module, including the chip described in the third aspect.
  • this application provides an electronic device, including: a memory, a processor, and a transceiver;
  • the memory is used to store computer programs
  • the processor is configured to implement the method described in the first aspect when the computer program is executed.
  • the present application provides a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the method described in the first aspect is implemented.
  • the present application provides a computer program product, including a computer program that implements the method described in the first aspect when executed by a processor.
  • This application provides a data transmission method, device, chip, chip module and electronic equipment.
  • the first MLD initiates TID-To-Link Mapping negotiation to the second MLD, it also indicates the reason for sending to the second MLD. , that is, the reason for TID-To-Link Mapping negotiation, so that the second MLD makes a decision based on the sending reason, thereby ensuring that the successfully negotiated TID-To-Link Mapping can meet the needs of the first MLD.
  • Figure 1 is a schematic flow chart of a data transmission method provided by an embodiment of the present application.
  • Figure 2 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • Access point (AP) MLD and non-access point (non-AP) MLD negotiate TID-To-Link Mapping to establish TID-To-Link Mapping.
  • TID-To-Link Mapping is established from TID-To-Link Mapping. Select a link to transmit data in To-Link Mapping.
  • the negotiated message will include its desired TID-To-Link Mapping, and the other party's MLD chooses to accept or reject it based on its own situation, because the other party's MLD does not understand
  • the reason why the initiating MLD initiates TID-To-Link Mapping negotiation and only makes decisions based on its own situation may cause the link in the finally established TID-To-Link Mapping to not meet the needs of the initiating MLD.
  • the embodiments of this application consider that when initiating the TID-To-Link Mapping negotiation, the MLD simultaneously indicates the sending reason to the other party MLD, that is, the reason for initiating the TID-To-Link Mapping negotiation, so that the other party MLD makes decisions based on the sending reason to ensure that the successfully negotiated TID-To-Link Mapping can meet the needs of the initiating MLD.
  • Figure 1 is a schematic flowchart of a data transmission method provided by an embodiment of the present application. This method is applied in the first MLD. As shown in Figure 1, the method includes:
  • TID-To-Link Mapping negotiation message includes the sending reason and the mapping relationship between the target TID and the first link set.
  • the second MLD when the first MLD is a non-AP MLD, the second MLD is an AP MLD; when the first MLD is an AP MLD, the second MLD is a non-AP MLD. In subsequent embodiments, the first MLD is a non-AP MLD and the second MLD is an AP MLD.
  • the situation when the first MLD is an AP MLD and the second MLD is a non-AP MLD is similar.
  • the mapping relationship between the target TID and the first link set is the mapping relationship expected by non-AP MLD.
  • the first link set can include one or more links, and the reason why non-AP MLD expects such a mapping relationship is It is the reason for sending, which can include link quality, load balancing, or power saving.
  • the non-AP MLD determines that the link currently mapped by the target TID has a link with poor link quality and may not be able to guarantee Qos requirements, it can initiate TID-To-Link Mapping.
  • the non-AP MLD expects that the first link set mapped by the target TID includes links that may have better link quality. Or, the non-AP MLD finds that the link mapped by the target TID is busy and cannot meet the service transmission requirements. Therefore, it can initiate TID-To-Link Mapping negotiation for load balancing reasons. At this time, the non-AP MLD expects the target TID.
  • the mapped first link set may include newly added links, or the non-AP MLD initiates TID-To-Link Mapping negotiation for power saving reasons. At this time, the first link set may include the current The reduced link is performed on the basis of the mapped link.
  • the link in the first link set is used to transmit the data corresponding to the target TID.
  • the AP MLD Since the non-AP MLD sends the reason for TID-To-Link Mapping negotiation to the AP MLD, the AP MLD will make decisions based on the sending reason. When the negotiation is successful, the non-AP MLD and the AP MLD The link in the first link set can be used to transmit the data corresponding to the target TID, thereby meeting the needs of non-AP MLD.
  • non-AP MLD when non-AP MLD initiates TID-To-Link Mapping negotiation to AP MLD, it also indicates the sending reason to AP MLD, which is the reason for TID-To-Link Mapping negotiation, so that AP MLD is based on Decision-making is made based on the sending reason, thereby ensuring that the successfully negotiated TID-To-Link Mapping can meet the needs of non-AP MLD.
  • the TID-To-Link Mapping negotiation message sent by the non-AP MLD to the AP MLD is a traffic identifier to link mapping request frame (TID-To-Link Mapping Request frame).
  • the TID-To-Link Mapping negotiation message sent by the non-AP MLD to the AP MLD is a traffic identifier to link mapping response frame (TID-To-Link Mapping Response frame).
  • the mapping relationship between the target TID and the first link set is carried in the TID-To-Link Mapping element (element) , the sending reason is carried in the cause field.
  • the cause field precedes the TID-To-Link Mapping element.
  • the cause field is before the TID-To-Link Mapping element.
  • the cause field is in the TID-To-Link Mapping element, as shown in Table 2 below for the TID-To-Link Mapping element. Format.
  • the TID-To-Link Mapping element includes a type field (Type field).
  • the type field is Suggest, which is used to indicate that the mapping relationship between the target traffic identifier and the first link set is recommended;
  • the type field is Preferred, which is used to indicate that the mapping relationship between the target traffic ID and the first link set is preferred;
  • the type field is Dictate, which is used to indicate that the mapping relationship between the target traffic ID and the first link set is mandatory. of.
  • TID-To-Link Mapping Control field in the TID-To-Link Mapping element is as shown in Table 3.
  • part of B3-B7 in the TID-To-Link Mapping Control field is the Type field.
  • one of B3-B7 in the TID-To-Link Mapping Control field is used to indicate whether there is a Cause field in the TID-To-Link Mapping element.
  • the TID-To-Link Mapping negotiation message sent by the non-AP MLD to the AP MLD is a TID-To-Link Mapping Response frame
  • the Response frame can include a status code (Status Code).
  • the status code is PREFERRED_TID_TO_LINK_MAPPING_SUGGESTED, which is used to represent the mapping relationship between the target traffic identifier and the first link set.
  • the status code is DICTATE_TID_TO_LINK_MAPPING. , used to indicate that the mapping relationship between the target traffic identifier and the first link set is mandatory. Table 4 below shows the format of the TID-To-Link Mapping Response frame where the Cause field is before the TID-To-Link Mapping element.
  • the AP MLD makes a decision based on the information carried in the TID-To-Link Mapping Request frame. , and returns the TID-To-Link Mapping Response frame to the non-AP MLD. If the AP MLD accepts the TID-To-Link Mapping requested by the non-AP MLD, the Status Code in the TID-To-Link Mapping Response frame is SUCCESS.
  • the TID-TO-Link Mapping Response Frame is the status code in Denied_tid_to_LINK_MAPPING, Preferred_to_link_ma. Pping_suggest itet or dictate_tid_link_mapping, status code is the latter two, TID-To-Link Mapping Response frame also has corresponding TID-To-Link Mapping element.
  • the AP MLD makes decisions based on the information carried in the TID-To-Link Mapping Response frame. , if the AP MLD rejects the TID-To-Link Mapping requested by the non-AP MLD, the AP MLD can initiate The TID-To-Link Mapping Request frame is re-negotiated, otherwise, the negotiation is completed.
  • the link in the first link set can be used to transmit the data corresponding to the target TID.
  • the scenario where the transmission reason is link quality can be a scenario where the first MLD is a non-AP MLD and the second MLD is an AP MLD.
  • the sending reason is link quality
  • the AP MLD should accept the TID-To-Link Mapping requested by the non-AP MLD to ensure the target TID data transmission. Qos requirements.
  • AP MLD can make decisions based on its own situation.
  • non-AP MLD determines the link quality of each link in the second link set to which the target TID is currently mapped; based on the link quality of each link in the second link set, sends TID-To to the AP MLD -Link Mapping negotiation message.
  • the non-AP MLD can determine the link quality of each link in the second link set by measuring Beacon frames.
  • the measurement method can refer to related technologies, which is not limited in the embodiments of this application.
  • the link quality includes at least one of the following: signal strength, signal quality, or link status.
  • the signal strength can be characterized by the Received Channel Power Indicator (RCPI) parameter; the signal quality can be characterized by the Received Signal to Noise Indicator (RSNI) parameter; the link status can be the combination of RCPI and/or Or RSNI is converted into the status of good, medium, poor, or broken. If the value of RCPI is in the first range, the link status is determined to be good. If the value of RCPI is in the second range, the link status is determined to be medium. If the value of RCPI is in the third range, the link status is determined to be poor.
  • RCPI Received Channel Power Indicator
  • RSNI Received Signal to Noise Indicator
  • the link status is determined to be down. Or, if the value of RSNI is in the fifth range, determine the link status as good, if the value of RSNI is in the sixth range, determine the link status as medium, and if the value of RSNI is in the seventh range, determine the link status If the value of RSNI is within the eight range, the link status is determined to be down. Or, if the ratio of RCPI/RSNI is in the ninth range, the link status is determined to be good. If the ratio of RCPI/RSNI is in the tenth range, the link status is determined to be medium. If the ratio of RCPI/RSNI is in the eleventh range, the link status is determined to be medium. range, the link status is determined to be poor. If the ratio of RCPI/RSNI is within the range of 12, the link status is determined to be down.
  • the above value range can be set according to the actual situation.
  • the link quality includes signal strength; based on the link quality of each link in the second link set, send a TID-To-Link Mapping negotiation message to the second multi-link device, including:
  • the signal strength of any link in the second link set is less than the first preset value; or if the signal strength is less than the second preset value and the signal strength decreases faster than the third preset value, then send the signal to the second multi-link device TID-To-Link Mapping negotiation message.
  • the non-AP MLD sends TID-To-Link Mapping to the AP MLD.
  • the link in the first link set in the TID-To-Link Mapping negotiation message is the link whose link quality meets the Qos requirements.
  • the first link set may be a link set obtained by removing links from the second link set that do not meet Qos requirements, or it may be a link set obtained by removing links from the second link set that do not meet Qos requirements.
  • the link set obtained after adding other links that meet Qos requirements, or the first link set can also be a link set that is completely different from the second link set and composed of other links that meet Qos requirements. .
  • the signal strength recovers to be greater than the fourth preset value; or, the signal strength recovers to be greater than the fifth preset value and the signal strength increases faster than the sixth preset value, then Send the TID-To-Link Mapping negotiation message to the second multi-link device again.
  • the previously removed link can be re-added to the mapping relationship, so the TID-To-Link Mapping negotiation message can be sent again to re-negotiate.
  • the link quality includes signal quality; based on the link quality of each link in the second link set, send a TID-To-Link Mapping negotiation message to the second multi-link device, including:
  • the signal quality of any link in the second link set is less than the seventh preset value; or if the signal quality is less than the eighth preset value and the signal quality decreases faster than the ninth preset value, then send to the second multi-link device TID-To-Link Mapping negotiation message.
  • the non-AP MLD sends a TID-To-Link Mapping negotiation message to the AP MLD.
  • the link in the TID-To-Link Mapping negotiation message is the first link in the set. A link that meets Qos requirements for link quality.
  • the first link set may be a link set obtained by removing links from the second link set that do not meet Qos requirements, or it may be a link set obtained by removing links from the second link set that do not meet Qos requirements.
  • the link set obtained after adding other links that meet Qos requirements, or the first link set can also be a link set that is completely different from the second link set and composed of other links that meet Qos requirements. .
  • the signal quality recovers to be greater than the tenth preset value; or, the signal quality recovers to be greater than the eleventh preset value and the signal quality improvement speed is greater than the twelfth preset value then send the TID-To-Link Mapping negotiation message to the second multi-link device again.
  • the signal quality recovers to be greater than the tenth preset value; or if the signal quality recovers to be greater than the eleventh preset value and the improvement speed of the signal quality is greater than the twelfth preset value, it means that the signal quality was previously When the link quality of the removed link returns to a level that meets Qos requirements, the previously removed link can be re-added to the mapping relationship, so the TID-To-Link Mapping negotiation message can be sent again to re-negotiate. .
  • the non-AP MLD sends a TID-To-Link Mapping negotiation message to the AP MLD.
  • the link status includes several levels that can be set as needed. The four statuses of good, medium, poor, and broken in the embodiment of this application are only used for illustration, and are not limited to include only these four statuses. status.
  • the non-AP MLD can determine to send the TID-To-Link Mapping negotiation message to the AP MLD based on the link quality of the second link set meeting one or more of the above conditions.
  • the non-AP MLD can also be used when the signal strength, signal quality, or link status meets the above preset conditions. If the value or status condition is set and it lasts for a certain period of time, it is determined to send the TID-To-Link Mapping negotiation message to the AP MLD.
  • the signal strength of any link in the second link set changes from a value greater than or equal to the first preset value to less than the first preset value, and lasted for a certain period of time; for another example, the signal quality of any link in the second link set changed from a value greater than or equal to the seventh preset value to less than the seventh preset value, and lasted for a certain period of time; for another example, the second The status of any link in the link set changes from good to bad for a certain period of time.
  • the above duration can be set separately as needed. This prevents the non-AP MLD from frequently sending TID-To-Link Mapping negotiation messages to the AP MLD, causing signaling storms.
  • the preset values among the conditions met by the link quality in the second link set involved in the above embodiments such as the first preset value, the second preset value... to the twelfth preset value, each preset value
  • the values can be set separately according to each second link.
  • the preset values corresponding to different frequency bands can be different, and the preset values corresponding to different bandwidths can be different.
  • the first value corresponding to the 5G link can be different.
  • the preset value may be different from the first preset value corresponding to the 2.4G link.
  • the second preset value corresponding to the 5G link may also be different from the second preset value corresponding to the 2.4G link.
  • the third preset value corresponding to the 20MHz carrier bandwidth may also be different.
  • a preset value may be different from the first preset value corresponding to the 40MHz carrier bandwidth, and the second preset value corresponding to the 20MHz carrier bandwidth may also be different from the second preset value corresponding to the 40MHz carrier bandwidth.
  • two links are established between non-AP MLD and AP MLD, respectively at 2.4GHz and 5GHz, and are default TID-To-Link mapping (that is, TID is mapped to all links). It is assumed that due to non-AP MLD movement , the link quality of the 5GHz link declines and does not meet the Qos requirements, then the non-AP MLD sends a TID-To-Link Mapping negotiation message to the AP MLD to eliminate the 5GHz link due to link quality reasons.
  • the AP MLD can send the TID-To-Link Mapping negotiation message to the AP MLD again to re-add the 5GHz link to the mapping relationship. middle.
  • two links are established between non-AP MLD and AP MLD, at 2.4GHz and 5GHz respectively, and they are default TID-To-Link mapping (that is, TID is mapped to all links).
  • Non-AP is for power saving considerations.
  • the non-AP MLD starts a new service and finds that the 2.4GHz link is busy and cannot meet the new service transmission requirements. It sends a TID-To-Link Mapping negotiation message to the AP MLD.
  • the reason for sending is load balancing to re-add the 5GHz link to the mapping relationship. middle.
  • FIG. 2 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application. As shown in Figure 2, a data transmission device 200 includes:
  • the sending module 201 is configured to send the mapping relationship between the traffic identifier and the link to the second multi-link device. is a negotiation message, wherein the mapping relationship negotiation message from the traffic identifier to the link includes the sending reason and the mapping relationship between the target traffic identifier and the first link set;
  • the transmission module 202 is configured to use the link in the first link set to transmit the data corresponding to the target traffic identifier after the negotiation based on the sending reason is successful.
  • the negotiation message for the mapping relationship between the traffic identifier and the link is a request frame for the mapping relationship between the traffic identifier and the link, or a response frame for the mapping relationship between the traffic identifier and the link.
  • mapping relationship between the target traffic identifier and the first link set is carried in the mapping relationship element from the traffic identifier to the link, and the sending reason is carried in the reason field;
  • the reason field precedes the mapping relationship element of the traffic ID to the link, or the reason field is in the mapping relationship element of the traffic ID to the link.
  • the mapping relationship element between the traffic identifier and the link includes a type field, and the type field is used to characterize whether the mapping relationship between the target traffic identifier and the first link set is recommended, preferred, or mandatory.
  • the negotiation message for the mapping relationship between the traffic identifier and the link is a response frame for the mapping relationship between the traffic identifier and the link.
  • the response frame for the mapping relationship between the traffic identifier and the link includes a status code, and the status code is used to represent the target.
  • the mapping relationship between the traffic ID and the first link set is mandatory.
  • reasons for sending include link quality, load balancing, or power conservation.
  • the sending reason is link quality; the sending module 201 is used to:
  • link quality includes at least one of: signal strength, signal quality, or link status.
  • link quality includes signal strength
  • Sending module 201 used for:
  • the signal strength of any link in the second link set is less than the first preset value; or if the signal strength is less than the second preset value and the signal strength decreases faster than the third preset value, then send the signal to the second multi-link device Traffic ID to link mapping relationship negotiation message.
  • the sending module 201 is used for:
  • the signal strength is restored to the second multi-link device again.
  • link quality includes signal quality
  • Sending module 201 used for:
  • the signal quality of any link in the second link set is less than the seventh preset value; or if the signal quality is less than the eighth preset value and the signal quality decreases faster than the ninth preset value, then send to the second multi-link device Traffic ID to link mapping relationship negotiation message.
  • the sending module is used to:
  • the signal quality recovers to be greater than the tenth preset value; or, the signal quality recovers to be greater than the eleventh preset value and the signal quality improvement speed is greater than the twelfth preset value, then send traffic to the second multi-link device again Identity to link mapping relationship negotiation message.
  • the data transmission device provided by the embodiment of the present application can be used to perform the method performed by the non-access point multi-link device or the access point multi-link device in the foregoing method embodiments.
  • the implementation principles and technical effects are similar and will not be described again here. .
  • FIG. 3 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the electronic device 300 includes: a memory 301, a processor 302, and a transceiver 303.
  • the memory 301 communicates with the processor 302; for example, the memory 301, the processor 302, and the transceiver 303 can communicate through a communication bus.
  • the memory 301 is used to store a computer program
  • the processor 302 executes the computer program to implement the above communication method.
  • the processor 302 executes the relevant steps executed by the electronic device in the above method embodiment.
  • the above-mentioned processor can be a central processing unit (Central Processing Unit, CPU), or other general-purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC )wait.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps in the method embodiments disclosed in this application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • An embodiment of the present application also provides a chip, including: a memory and a processor.
  • the memory is used to store the computer program; the processor is used to implement the method in any of the above method embodiments when the computer program is executed.
  • An embodiment of the present application also provides a chip module, including the above chip.
  • Embodiments of the present application also provide a computer-readable storage medium, including: a computer program stored thereon, which implements the method in any of the above method embodiments when executed by a processor.
  • An embodiment of the present application also provides a computer program product, which includes a computer program.
  • a computer program product which includes a computer program.
  • the computer program is executed by a processor, the method in any of the above method embodiments is implemented.
  • the aforementioned program can be stored in a readable memory.
  • the steps including the above method embodiments are executed; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state hard disk, tape (magnetic tape), floppy disk (floppy disk), optical disk (optical disc) and any combination thereof.
  • Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine, such that the instructions executed by the processing unit of the computer or other programmable data processing device produce a A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • the term “including” and its variations may refer to non-limiting inclusion; the term “or” and its variations may refer to “and/or”.
  • the terms “first”, “second”, etc. are used to distinguish between categories. similar objects and not necessarily used to describe a specific order or sequence.
  • “plurality” means two or more.
  • “And/or” describes the relationship between related objects, indicating that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. The character “/" generally indicates that the related objects are in an "or” relationship.

Landscapes

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

Abstract

本申请提供一种数据传输方法、装置、芯片、芯片模组及电子设备。该方法应用于第一多链路设备，包括：向第二多链路设备发送流量标识至链路的映射关系协商消息，其中，流量标识至链路的映射关系协商消息中包括发送原因以及目标流量标识和第一链路集之间的映射关系；在基于发送原因协商成功后，采用第一链路集中的链路传输目标流量标识对应的数据。从而保证了流量标识至链路的映射关系满足第一多链路设备的需求。

Description

数据传输方法、装置、芯片、芯片模组及电子设备
本申请要求于2022年03月18日提交中国专利局、申请号为202210269926.5、申请名称为“数据传输方法、装置、芯片、芯片模组及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种数据传输方法、装置、芯片、芯片模组及电子设备。
背景技术
IEEE 802.11be标准中引入了多链路(Multi-Link，ML)技术，一个多链路设备(Multi-Link Device，MLD)可以包含多个站点(Station，STA)，从而两个MLD之间可以建立多条链路。相应的，数据可以在多条链路上传输，传输数据的链路可以由流量标识(Traffic ID，TID)至链路的映射关系(TID to link mapping)决定。
当一方MLD发起TID-To-Link Mapping协商后，另一方MLD依据自身情况选择接受或拒绝，这可能导致最终建立的TID-To-Link Mapping中的链路不能满足发起TID-To-Link Mapping协商的MLD的需求。
发明内容
本申请提供一种数据传输方法、装置、芯片、芯片模组及电子设备，以保证数据按QoS需求完成传输。
第一方面，本申请提供一种数据传输方法，应用于第一多链路设备中，包括：
向第二多链路设备发送流量标识至链路的映射关系协商消息，其中，所述流量标识至链路的映射关系协商消息中包括发送原因以及目标流量标识和第一链路集之间的映射关系；
在基于所述发送原因协商成功后，采用所述第一链路集中的链路传输 所述目标流量标识对应的数据。
在一种实现方式中，所述流量标识至链路的映射关系协商消息为流量标识至链路的映射关系请求帧，或，流量标识至链路的映射关系响应帧。
在一种实现方式中，所述目标流量标识和第一链路集之间的映射关系携带在流量标识至链路的映射关系元素中，所述发送原因携带在原因字段中；
所述原因字段在所述流量标识至链路的映射关系元素之前，或者，所述原因字段在所述流量标识至链路的映射关系元素中。
在一种实现方式中，所述流量标识至链路的映射关系元素中包括类型字段，所述类型字段用于表征所述目标流量标识和所述第一链路集之间的映射关系为建议的、优选的或强制的。
在一种实现方式中，所述流量标识至链路的映射关系协商消息为流量标识至链路的映射关系响应帧，所述流量标识至链路的映射关系响应帧中包括状态码，所述状态码用于表征所述目标流量标识和所述第一链路集之间的映射关系为强制的。
在一种实现方式中，所述发送原因包括链路质量、负载均衡或节电。
在一种实现方式中，所述发送原因为链路质量；所述向第二多链路设备发送流量标识至链路的映射关系协商消息，包括：
确定所述目标流量标识当前映射的第二链路集中每条链路的链路质量；
基于所述第二链路集中每条链路的链路质量，向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，所述链路质量包括以下至少一项：信号强度、信号质量或链路状态。
在一种实现方式中，所述链路质量包括信号强度；
所述基于所述第二链路集中每条链路的链路质量，向所述第二多链路设备发送流量标识至链路的映射关系协商消息，包括：
若所述第二链路集中任一链路的信号强度小于第一预设值；或者，所述信号强度小于第二预设值且所述信号强度的降低速度大于第三预设值，则向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，还包括：
若所述信号强度恢复至大于第四预设值；或者，所述信号强度恢复至 大于第五预设值且所述信号强度的提高速度大于第六预设值，则再次向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，所述链路质量包括信号质量；
所述基于所述第二链路集中每条链路的链路质量，向所述第二多链路设备发送流量标识至链路的映射关系协商消息，包括：
若所述第二链路集中任一链路的信号质量小于第七预设值；或者，所述信号质量小于第八预设值且所述信号质量的降低速度大于第九预设值，则向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，还包括：
若所述信号质量恢复至大于第十预设值；或者，所述信号质量恢复至大于第十一预设值且所述信号质量的提高速度大于第十二预设值，则再次向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
第二方面，本申请提供一种数据传输装置，应用于第一多链路设备中，包括：
发送模块，用于向第二多链路设备发送流量标识至链路的映射关系协商消息，其中，所述流量标识至链路的映射关系协商消息中包括发送原因以及目标流量标识和第一链路集之间的映射关系；
传输模块，用于在基于所述发送原因协商成功后，采用所述第一链路集中的链路传输所述目标流量标识对应的数据。
在一种实现方式中，所述流量标识至链路的映射关系协商消息为流量标识至链路的映射关系请求帧，或，流量标识至链路的映射关系响应帧。
在一种实现方式中，所述目标流量标识和第一链路集之间的映射关系携带在流量标识至链路的映射关系元素中，所述发送原因携带在原因字段中；
所述原因字段在所述流量标识至链路的映射关系元素之前，或者，所述原因字段在所述流量标识至链路的映射关系元素中。
在一种实现方式中，所述流量标识至链路的映射关系元素中包括类型字段，所述类型字段用于表征所述目标流量标识和所述第一链路集之间的映射关系为建议的、优选的或强制的。
在一种实现方式中，所述流量标识至链路的映射关系协商消息为流量标识至链路的映射关系响应帧，所述流量标识至链路的映射关系响应帧中 包括状态码，所述状态码用于表征所述目标流量标识和所述第一链路集之间的映射关系为强制的。
在一种实现方式中，所述发送原因包括链路质量、负载均衡或节电。
在一种实现方式中，所述发送原因为链路质量；所述发送模块用于：
确定所述目标流量标识当前映射的第二链路集中每条链路的链路质量；
基于所述第二链路集中每条链路的链路质量，向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，所述链路质量包括以下至少一项：信号强度、信号质量或链路状态。
在一种实现方式中，所述链路质量包括信号强度；
所述发送模块，用于：
若所述第二链路集中任一链路的信号强度小于第一预设值；或者，所述信号强度小于第二预设值且所述信号强度的降低速度大于第三预设值，则向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，所述发送模块，用于：
若所述信号强度恢复至大于第四预设值；或者，所述信号强度恢复至大于第五预设值且所述信号强度的提高速度大于第六预设值，则再次向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，所述链路质量包括信号质量；
所述发送模块，用于：
若所述第二链路集中任一链路的信号质量小于第七预设值；或者，所述信号质量小于第八预设值且所述信号质量的降低速度大于第九预设值，则向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，所述发送模块，用于：
若所述信号质量恢复至大于第十预设值；或者，所述信号质量恢复至大于第十一预设值且所述信号质量的提高速度大于第十二预设值，则再次向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
第三方面，本申请提供一种芯片，包括：存储器和处理器；
所述存储器用于存储计算机程序；
所述处理器用于在所述计算机程序执行时，实现如上述第一方面所述的方法。
第四方面，本申请提供一种芯片模组，包括如上述第三方面所述的芯片。
第五方面，本申请提供一种电子设备，包括：存储器、处理器和收发器；
所述存储器用于存储计算机程序；
所述处理器用于在所述计算机程序执行时，实现如上述第一方面所述的方法。
第六方面，本申请提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时，实现如上述第一方面所述的方法。
第七方面，本申请提供一种计算机程序产品，包括计算机程序，所述计算机程序被处理器执行时实现如上述第一方面所述的方法。
本申请提供一种数据传输方法、装置、芯片、芯片模组及电子设备，该方法中第一MLD在向第二MLD发起TID-To-Link Mapping协商时，同时向第二MLD指示出发送原因，也就是进行TID-To-Link Mapping协商的原因，从而使得第二MLD基于该发送原因进行决策，从而保证协商成功的TID-To-Link Mapping能够满足第一MLD的需求。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图做一简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种数据传输方法的流程示意图；
图2为本申请实施例提供的一种数据传输装置的结构示意图；
图3为本申请实施例提供的一种电子设备的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
接入点(Access Point，AP)MLD与非接入点(non-AP)MLD之间通过TID-To-Link Mapping协商来建立TID-To-Link Mapping，当有数据需要传输时，从TID-To-Link Mapping中选择链路来传输数据。当一方MLD发起TID-To-Link Mapping协商时，协商的消息中会包括其期望的TID-To-Link Mapping，而另一方MLD则是依据自身情况选择接受或拒绝，由于另一方MLD并不了解发起方MLD发起TID-To-Link Mapping协商的原因，而仅根据自身情况做决定，因此可能导致最终建立的TID-To-Link Mapping中的链路不能满足发起方MLD的需求。
为了解决上述问题，本申请实施例中考虑到，MLD在发起TID-To-Link Mapping协商时同时向另一方MLD指示发送原因，也就是发起TID-To-Link Mapping协商的原因，从而使得另一方MLD基于该发送原因进行决策，从而保证协商成功的TID-To-Link Mapping能够满足发起方MLD的需求。
下面将通过具体的实施例对本申请提供的数据传输方法进行详细地说明。可以理解的是，下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。
图1为本申请实施例提供的一种数据传输方法的流程示意图。该方法应用于第一MLD中。如图1所示，该方法包括：
S101、向第二MLD发送TID-To-Link Mapping协商消息，其中，TID-To-Link Mapping协商消息中包括发送原因以及目标TID和第一链路集之间的映射关系。
本申请实施例中，第一MLD为non-AP MLD时，第二MLD为AP MLD；第一MLD为AP MLD时，第二MLD为non-AP MLD。在后续实施例中以第一MLD为non-AP MLD，第二MLD为AP MLD为例进行说明，第一MLD为AP MLD，第二MLD为non-AP MLD时的情况类似。
目标TID和第一链路集之间的映射关系是non-AP MLD所期望的映射关系，第一链路集中可以包括一条或多条链路，而non-AP MLD期望这样的映射关系的原因就是发送原因，发送原因可以包括链路质量、负载均衡或节电等。
例如，non-AP MLD确定目标TID当前所映射的链路中存在链路质量较差的链路，可能无法保证Qos需求，则可以发起TID-To-Link Mapping 协商，此时non-AP MLD期望目标TID映射的第一链路集中包括的可能为链路质量较好的链路。或者，non-AP MLD发现目标TID所映射的链路较繁忙，无法满足业务传输需求，因此，可以出于负载均衡的原因发起TID-To-Link Mapping协商，此时non-AP MLD期望目标TID映射的第一链路集中可能包括了新增的链路，又或者，non-AP MLD出于节电原因发起TID-To-Link Mapping协商，此时第一链路集中包括的可能是在当前映射的链路的基础上进行减少后的链路。
S102、在基于发送原因协商成功后，采用第一链路集中的链路传输目标TID对应的数据。
由于non-AP MLD向AP MLD发送了进行TID-To-Link Mapping协商的原因，因此AP MLD在进行决策是会基于该发送原因进行决策，在协商成功的情况下，non-AP MLD和AP MLD即可采用第一链路集中的链路传输目标TID对应的数据，从而满足non-AP MLD的需求。
本申请实施例中non-AP MLD在向AP MLD发起TID-To-Link Mapping协商时，同时向AP MLD指示出发送原因，也就是进行TID-To-Link Mapping协商的原因，从而使得AP MLD基于该发送原因进行决策，从而，保证协商成功的TID-To-Link Mapping能够满足non-AP MLD的需求。
在上述实施例的基础上，对TID-To-Link Mapping协商消息进行说明。
在一种实现方式中，non-AP MLD向AP MLD发送的TID-To-Link Mapping协商消息为流量标识至链路的映射关系请求帧(TID-To-Link Mapping Request frame)。在另一种实现方式中，non-AP MLD向AP MLD发送的TID-To-Link Mapping协商消息为流量标识至链路的映射关系响应帧(TID-To-Link Mapping Response frame)。
可选的，在TID-To-Link Mapping Request frame或TID-To-Link Mapping Response frame中，目标TID和第一链路集之间的映射关系携带在TID-To-Link Mapping元素(element)中，发送原因携带在原因字段(cause field)中。
可选的，在TID-To-Link Mapping Request frame或TID-To-Link Mapping Response frame中，cause field在TID-To-Link Mapping element之前。如下表1所示的为cause field在TID-To-Link Mapping element之前的 TID-To-Link Mapping Request frame的格式。
表1
可选的，在TID-To-Link Mapping Request frame或TID-To-Link Mapping Response frame中，cause field在TID-To-Link Mapping element中，如下表2所示为TID-To-Link Mapping element的格式。
表2
可选的，TID-To-Link Mapping element中包括类型字段(Type field)，可选的，类型字段为Suggest，用于表征目标流量标识和第一链路集之间的映射关系为建议的；类型字段为Preferred，用于表征目标流量标识和第一链路集之间的映射关系为优选的；类型字段为Dictate，用于表征目标流量标识和第一链路集之间的映射关系为强制的。
TID-To-Link Mapping element中的TID-To-Link Mapping Control field格式如下表3。
表3
可选的，TID-To-Link Mapping Control field中的B3-B7的一部分为Type field。
可选的，TID-To-Link Mapping Control field中的B3-B7之一用于指示TID-To-Link Mapping element中是否存在Cause field。
可选的，non-AP MLD向AP MLD发送的TID-To-Link Mapping协商消息为TID-To-Link Mapping Response frame时，在TID-To-Link Mapping  Response frame中可以包括状态码(Status Code)，可选的，状态码为PREFERRED_TID_TO_LINK_MAPPING_SUGGESTED，用于表征目标流量标识和第一链路集之间的映射关系为优选的，可选的，状态码为DICTATE_TID_TO_LINK_MAPPING，用于表征目标流量标识和第一链路集之间的映射关系为强制的。如下表4所示的为Cause field在TID-To-Link Mapping element之前的TID-To-Link Mapping Response frame的格式。
表4
可选的，在non-AP MLD向AP MLD发送的TID-To-Link Mapping协商消息为TID-To-Link Mapping Request frame时，AP MLD基于TID-To-Link Mapping Request frame中携带的信息进行决策，并向non-AP MLD返回TID-To-Link Mapping Response frame，若AP MLD接受non-AP MLD请求的TID-To-Link Mapping，则TID-To-Link Mapping Response frame中的Status Code为SUCCESS。若AP MLD拒绝non-AP MLD请求的TID-To-Link Mapping，则TID-To-Link Mapping Response frame中的Status Code为DENIED_TID_TO_LINK_MAPPING、PREFERRED_TID_TO_LINK_MAPPING_SUGGESTED或DICTATE_TID_TO_LINK_MAPPING，Status Code为后两种时，TID-To-Link Mapping Response frame同时带有相应的TID-To-Link Mapping element。
可选的，在non-AP MLD向AP MLD发送的TID-To-Link Mapping协商消息为TID-To-Link Mapping Response frame时，AP MLD基于TID-To-Link Mapping Response frame中携带的信息进行决策，若AP MLD拒绝non-AP MLD请求的TID-To-Link Mapping，则AP MLD可以发起 TID-To-Link Mapping Request frame重新进行协商，否则，协商完成。
non-AP MLD和AP MLD基于发送原因协商成功后，即可采用第一链路集中的链路进行传输目标TID对应的数据。
在上述实施例的基础上，对发送原因为链路质量的情况做进一步说明。
对于AP MLD，其只能在传输数据时才能获取到链路信号的状态，并不能实时了解各链路的链路质量是否理想。而对于non-AP MLD，其可以通过测量AP MLD的Beacon帧来实时了解链路质量是否理想。因此，发送原因为链路质量的场景可以为第一MLD为non-AP MLD，第二MLD为AP MLD的场景。在发送原因为链路质量时，即表示链路质量不能满足目标TID数据传输的Qos需求，此时AP MLD应该接受non-AP MLD请求的TID-To-Link Mapping，以保证目标TID数据传输的Qos需求。而对于其他的发送原因，AP MLD可以结合自身情况进行决策。
以下对non-AP MLD如何基于链路质量发起TID-To-Link Mapping协商进行说明。
可选的，non-AP MLD确定目标TID当前映射的第二链路集中每条链路的链路质量；基于第二链路集中每条链路的链路质量，向AP MLD发送TID-To-Link Mapping协商消息。
non-AP MLD可以通过测量Beacon帧来确定第二链路集中每条链路的链路质量，测量方法可以参照相关技术，本申请实施例中对此不做限定。
可选的，链路质量包括以下至少一项：信号强度、信号质量或链路状态。示例的，信号强度可以采用接收信道功率参数(Received Channel Power Indicator，RCPI)表征；信号质量可以采用接收信噪比参数(Received Signal to Noise Indicator，RSNI)表征；链路状态可以是将RCPI和/或RSNI转换为好、中、差、断的状态。若RCPI的值在第一范围，将链路状态确定为好，若RCPI的值在第二范围，将链路状态确定为中，若RCPI的值在第三范围，将链路状态确定为差，若RCPI的值在第四范围，将链路状态确定为断。或者，若RSNI的值在第五范围，将链路状态确定为好，若RSNI的值在第六范围，将链路状态确定为中，若RSNI的值在第七范围，将链路状态确定为差，若RSNI的值在八范围，将链路状态确定为断。或者，若RCPI/RSNI的比值在第九范围，将链路状态确定为好，若RCPI/RSNI的比值在第十范围，将链路状态确定为中，若RCPI/RSNI的比值在第十一 范围，将链路状态确定为差，若RCPI/RSNI的比值在十二范围，将链路状态确定为断。上述取值范围可以根据实际情况进行设置。
可选的，链路质量包括信号强度；基于第二链路集中每条链路的链路质量，向第二多链路设备发送TID-To-Link Mapping协商消息，包括：
若第二链路集中任一链路的信号强度小于第一预设值；或者，信号强度小于第二预设值且信号强度的降低速度大于第三预设值，则向第二多链路设备发送TID-To-Link Mapping协商消息。
若第二链路集中任一链路的信号强度小于第一预设值；或者，信号强度小于第二预设值且信号强度的降低速度大于第三预设值，则表示第二链路的信号强度较弱，即第二链路的链路质量较差，链路信号不理想，为了避免AP MLD选择到链路质量较差的链路，non-AP MLD向AP MLD发送TID-To-Link Mapping协商消息，TID-To-Link Mapping协商消息中的第一链路集中的链路为链路质量满足Qos需求的链路。可选的，第一链路集可以是将第二链路集中不满足Qos需求的链路剔除后所得到的链路集，也可以是将第二链路集中不满足Qos需求的链路剔除并添加了其他满足Qos需求的链路后所得到的链路集，或者，第一链路集也可以是与第二链路集完全不同的其他满足Qos需求的链路所构成的链路集。
可选的，在上述实施例的基础上，若信号强度恢复至大于第四预设值；或者，信号强度恢复至大于第五预设值且信号强度的提高速度大于第六预设值，则再次向第二多链路设备发送TID-To-Link Mapping协商消息。
在上述实施例的基础上，若信号强度恢复至大于第四预设值；或者，信号强度恢复至大于第五预设值且信号强度的提高速度大于第六预设值，表示先前被剔除的链路的链路质量恢复至满足Qos需求的水平，此时可以将先前被剔除的链路重新添加至映射关系中，因此可以再次发送TID-To-Link Mapping协商消息，以重新进行协商。
可选的，链路质量包括信号质量；基于第二链路集中每条链路的链路质量，向第二多链路设备发送TID-To-Link Mapping协商消息，包括：
若第二链路集中任一链路的信号质量小于第七预设值；或者，信号质量小于第八预设值且信号质量的降低速度大于第九预设值，则向第二多链路设备发送TID-To-Link Mapping协商消息。
若第二链路集中任一链路的信号质量小于第七预设值；或者，信号质 量小于第八预设值且信号质量的降低速度大于第九预设值，则表示第二链路的信号强度较弱，即第二链路的链路质量较差，链路信号不理想，为了避免AP MLD选择到链路质量较差的链路，non-AP MLD向AP MLD发送TID-To-Link Mapping协商消息，TID-To-Link Mapping协商消息中的第一链路集中的链路为链路质量满足Qos需求的链路。可选的，第一链路集可以是将第二链路集中不满足Qos需求的链路剔除后所得到的链路集，也可以是将第二链路集中不满足Qos需求的链路剔除并添加了其他满足Qos需求的链路后所得到的链路集，或者，第一链路集也可以是与第二链路集完全不同的其他满足Qos需求的链路所构成的链路集。
可选的，在上述实施例的基础上，若信号质量恢复至大于第十预设值；或者，信号质量恢复至大于第十一预设值且信号质量的提高速度大于第十二预设值，则再次向第二多链路设备发送TID-To-Link Mapping协商消息。
在上述实施例的基础上，若信号质量恢复至大于第十预设值；或者，信号质量恢复至大于第十一预设值且信号质量的提高速度大于第十二预设值，表示先前被剔除的链路的链路质量恢复至满足Qos需求的水平，此时可以将先前被剔除的链路重新添加至映射关系中，因此可以再次发送TID-To-Link Mapping协商消息，以重新进行协商。
可选的，若第二链路集中任一链路的链路状态为差或断的状态，则non-AP MLD向AP MLD发送TID-To-Link Mapping协商消息。可选的，若链路状态恢复为好或中，则non-AP MLD再次向AP MLD发送TID-To-Link Mapping协商消息。需要说明的是，链路状态包括几个等级可以根据需要进行设置，本申请实施例中的好、中、差、断4个状态仅用于示例说明，而并非限定链路状态仅包括这4个状态。
还需要说明的是，non-AP MLD可以基于第二链路集的链路质量满足上述一项或多项条件来确定向AP MLD发送TID-To-Link Mapping协商消息。
可选的，除了上述所示例的信号强度、信号质量或链路状态满足的预设值或状态的条件外，non-AP MLD还可以在，信号强度、信号质量或链路状态满足上述的预设值或状态的条件，且持续一定的时长的情况下，确定向AP MLD发送TID-To-Link Mapping协商消息。例如，第二链路集中任一链路的信号强度由大于等于第一预设值的值变得小于第一预设值，且 持续了一定的时长；又如，第二链路集中任一链路的信号质量由大于等于第七预设值的值变得小于第七预设值，且持续了一定的时长；又如，第二链路集中任一链路的状态由好变为差，且持续了一定的时长。上述的时长可以根据需要分别进行设置。从而，避免non-AP MLD频繁向AP MLD发送TID-To-Link Mapping协商消息，产生信令风暴。
上述实施例中所涉及的第二链路集中的链路质量所满足的条件中的预设值，例如第一预设值、第二预设值…直至第十二预设值，各预设值均可以是根据每条第二链路分别设置的，例如不同的频段(band)对应的预设值可以不同，不同带宽对应的预设值可以不同，示例的，5G链路对应的第一预设值与2.4G链路对应的第一预设值可以不同，5G链路对应的第二预设值与2.4G链路对应的第二预设值也可以不同，20MHz载波带宽对应的第一预设值和40MHz载波带宽对应的第一预设值可以不同，20MHz载波带宽对应的第二预设值和40MHz载波带宽对应的第二预设值也可以不同。
示例的，non-AP MLD与AP MLD之间建立了两条Link，分别在2.4GHz和5GHz，且为default TID-To-Link mapping(即TID映射到所有link)，假设由于non-AP MLD移动，5GHz link的链路质量下降不满足Qos需求，则non-AP MLD出于链路质量的原因向AP MLD发送TID-To-Link Mapping协商消息，以将5GHz link剔除。假设再此之后，non-AP MLD继续移动，5GHz link的链路质量回升，满足Qos需求，则AP MLD可以向AP MLD再次发送TID-To-Link Mapping协商消息，以将5GHz link重新加入映射关系中。
示例的，non-AP MLD与AP MLD之间建立两条Link，分别在2.4GHz和5GHz，且为default TID-To-Link mapping(即TID映射到所有link)，non-AP出于节电考虑，向AP MLD发送TID-To-Link Mapping协商消息，将所有TID均映射到2.4GHz link。假设non-AP MLD开启了新业务，且发现2.4GHz link繁忙无法满足新业务传输需求，向AP MLD发送TID-To-Link Mapping协商消息，发送原因为负载均衡，以将5GHz link重新加入映射关系中。
图2为本申请实施例提供的一种数据传输装置的结构示意图，如图2所示，数据传输装置200，包括：
发送模块201，用于向第二多链路设备发送流量标识至链路的映射关 系协商消息，其中，流量标识至链路的映射关系协商消息中包括发送原因以及目标流量标识和第一链路集之间的映射关系；
传输模块202，用于在基于发送原因协商成功后，采用第一链路集中的链路传输目标流量标识对应的数据。
在一种实现方式中，流量标识至链路的映射关系协商消息为流量标识至链路的映射关系请求帧，或，流量标识至链路的映射关系响应帧。
在一种实现方式中，目标流量标识和第一链路集之间的映射关系携带在流量标识至链路的映射关系元素中，发送原因携带在原因字段中；
原因字段在流量标识至链路的映射关系元素之前，或者，原因字段在流量标识至链路的映射关系元素中。
在一种实现方式中，流量标识至链路的映射关系元素中包括类型字段，类型字段用于表征目标流量标识和第一链路集之间的映射关系为建议的、优选的或强制的。
在一种实现方式中，流量标识至链路的映射关系协商消息为流量标识至链路的映射关系响应帧，流量标识至链路的映射关系响应帧中包括状态码，状态码用于表征目标流量标识和第一链路集之间的映射关系为强制的。
在一种实现方式中，发送原因包括链路质量、负载均衡或节电。
在一种实现方式中，发送原因为链路质量；发送模块201用于：
确定目标流量标识当前映射的第二链路集中每条链路的链路质量；
基于第二链路集中每条链路的链路质量，向第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，链路质量包括以下至少一项：信号强度、信号质量或链路状态。
在一种实现方式中，链路质量包括信号强度；
发送模块201，用于：
若第二链路集中任一链路的信号强度小于第一预设值；或者，信号强度小于第二预设值且信号强度的降低速度大于第三预设值，则向第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，发送模块201，用于：
若信号强度恢复至大于第四预设值；或者，信号强度恢复至大于第五预设值且信号强度的提高速度大于第六预设值，则再次向第二多链路设备 发送流量标识至链路的映射关系协商消息。
在一种实现方式中，链路质量包括信号质量；
发送模块201，用于：
若第二链路集中任一链路的信号质量小于第七预设值；或者，信号质量小于第八预设值且信号质量的降低速度大于第九预设值，则向第二多链路设备发送流量标识至链路的映射关系协商消息。
在一种实现方式中，发送模块，用于：
若信号质量恢复至大于第十预设值；或者，信号质量恢复至大于第十一预设值且信号质量的提高速度大于第十二预设值，则再次向第二多链路设备发送流量标识至链路的映射关系协商消息。
本申请实施例提供的数据传输装置可用于执行前述方法实施例中非接入点多链路设备或接入点多链路设备执行的方法，其实现原理和技术效果类似，此处不再赘述。
图3为本申请实施例提供的一种电子设备的结构示意图。如图3所示，该电子300包括：存储器301、处理器302、收发器303，其中，存储器301和处理器302通信；示例性的，存储器301、处理器302和收发器303可以通过通信总线304通信，存储器301用于存储计算机程序，处理器302执行该计算机程序实现上述通信方法。例如，处理器302执行上述方法实施例中电子设备执行的相关步骤。
可选的，上述处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请所公开的方法实施例中的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例还提供一种芯片，包括：存储器和处理器。
存储器用于存储计算机程序；处理器用于在计算机程序执行时，实现如上述任意方法实施例中的方法。
本申请实施例还提供一种芯片模组，包括上述芯片。
本申请实施例还提供一种计算机可读存储介质，包括：其上存储有计算机程序，该程序被处理器执行时实现上述任意方法实施例中的方法。
本申请实施例还提供一种计算机程序产品，包括计算机程序，计算机程序被处理器执行时实现上述任意方法实施例中的方法。
实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一可读取存储器中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储器(存储介质)包括：只读存储器(read-only memory，ROM)、RAM、快闪存储器、硬盘、固态硬盘、磁带(magnetic tape)、软盘(floppy disk)、光盘(optical disc)及其任意组合。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理单元以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理单元执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
在本申请中，术语“包括”及其变形可以指非限制性的包括；术语“或”及其变形可以指“和/或”。本本申请中术语“第一”、“第二”等是用于区别类 似的对象，而不必用于描述特定的顺序或先后次序。本申请中，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。

Claims (18)

  1. 一种数据传输方法，应用于第一多链路设备中，其特征在于，包括：
    向第二多链路设备发送流量标识至链路的映射关系协商消息，其中，所述流量标识至链路的映射关系协商消息中包括发送原因以及目标流量标识和第一链路集之间的映射关系；
    在基于所述发送原因协商成功后，采用所述第一链路集中的链路传输所述目标流量标识对应的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述流量标识至链路的映射关系协商消息为流量标识至链路的映射关系请求帧，或，流量标识至链路的映射关系响应帧。
  3. 根据权利要求2所述的方法，其特征在于，所述目标流量标识和第一链路集之间的映射关系携带在流量标识至链路的映射关系元素中，所述发送原因携带在原因字段中；
    所述原因字段在所述流量标识至链路的映射关系元素之前，或者，所述原因字段在所述流量标识至链路的映射关系元素中。
  4. 根据权利要求3所述的方法，其特征在于，所述流量标识至链路的映射关系元素中包括类型字段，所述类型字段用于表征所述目标流量标识和所述第一链路集之间的映射关系为建议的、优选的或强制的。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，所述流量标识至链路的映射关系协商消息为流量标识至链路的映射关系响应帧，所述流量标识至链路的映射关系响应帧中包括状态码，所述状态码用于表征所述目标流量标识和所述第一链路集之间的映射关系为强制的。
  6. 根据权利要求2-4任一项所述的方法，其特征在于，所述发送原因包括链路质量、负载均衡或节电。
  7. 根据权利要求6所述的方法，其特征在于，所述发送原因为链路质量；所述向第二多链路设备发送流量标识至链路的映射关系协商消息，包括：
    确定所述目标流量标识当前映射的第二链路集中每条链路的链路质量；
    基于所述第二链路集中每条链路的链路质量，向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
  8. 根据权利要求7所述的方法，其特征在于，所述链路质量包括以下至少一项：信号强度、信号质量或链路状态。
  9. 根据权利要求8所述的方法，其特征在于，所述链路质量包括信号强度；
    所述基于所述第二链路集中每条链路的链路质量，向所述第二多链路设备发送流量标识至链路的映射关系协商消息，包括：
    若所述第二链路集中任一链路的信号强度小于第一预设值；或者，所述信号强度小于第二预设值且所述信号强度的降低速度大于第三预设值，则向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    若所述信号强度恢复至大于第四预设值；或者，所述信号强度恢复至大于第五预设值且所述信号强度的提高速度大于第六预设值，则再次向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
  11. 根据权利要求8所述的方法，其特征在于，所述链路质量包括信号质量；
    所述基于所述第二链路集中每条链路的链路质量，向所述第二多链路设备发送流量标识至链路的映射关系协商消息，包括：
    若所述第二链路集中任一链路的信号质量小于第七预设值；或者，所述信号质量小于第八预设值且所述信号质量的降低速度大于第九预设值，则向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
  12. 根据权利要求11所述的方法，其特征在于，还包括：
    若所述信号质量恢复至大于第十预设值；或者，所述信号质量恢复至大于第十一预设值且所述信号质量的提高速度大于第十二预设值，则再次向所述第二多链路设备发送流量标识至链路的映射关系协商消息。
  13. 一种数据传输装置，应用于第一多链路设备中，其特征在于，包括：
    发送模块，用于向第二多链路设备发送流量标识至链路的映射关系协商消息，其中，所述流量标识至链路的映射关系协商消息中包括发送原因以及目标流量标识和第一链路集之间的映射关系；
    传输模块，用于在基于所述发送原因协商成功后，采用所述第一链路集中的链路传输所述目标流量标识对应的数据。
  14. 一种芯片，其特征在于，包括：存储器和处理器；
    所述存储器用于存储计算机程序；
    所述处理器用于在所述计算机程序执行时，实现如上述权利要求1-12中任一项所述的方法。
  15. 一种芯片模组，其特征在于，包括如权利要求14所述的芯片。
  16. 一种电子设备，其特征在于，包括：存储器、处理器和收发器；
    所述存储器用于存储计算机程序；
    所述处理器用于在所述计算机程序执行时，实现如上述权利要求1-12中任一项所述的方法。
  17. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时，实现如上述权利要求1-12中任一项所述的方法。
  18. 一种计算机程序产品，其特征在于，包括计算机程序，所述计算机程序被处理器执行时实现权利要求1-12中任一项所述的方法。
PCT/CN2023/082605 2022-03-18 2023-03-20 数据传输方法、装置、芯片、芯片模组及电子设备 WO2023174434A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210269926.5A CN116801318A (zh) 2022-03-18 2022-03-18 数据传输方法、装置、芯片、芯片模组及电子设备
CN202210269926.5 2022-03-18

Publications (1)

Publication Number Publication Date
WO2023174434A1 true WO2023174434A1 (zh) 2023-09-21

Family

ID=88022435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/082605 WO2023174434A1 (zh) 2022-03-18 2023-03-20 数据传输方法、装置、芯片、芯片模组及电子设备

Country Status (2)

Country Link
CN (1) CN116801318A (zh)
WO (1) WO2023174434A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200221545A1 (en) * 2019-03-20 2020-07-09 Robert J. Stacey Multi-link discovery signaling in extremely high throughput (eht) systems
CN113543243A (zh) * 2020-04-18 2021-10-22 华为技术有限公司 链路处理方法、多链路设备及计算机可读存储介质
CN113573341A (zh) * 2021-09-23 2021-10-29 成都极米科技股份有限公司 协商业务与链路映射配置的方法、装置、设备及存储介质
CN113747502A (zh) * 2020-05-27 2021-12-03 华为技术有限公司 多链路试关联方法及相关装置
CN114079949A (zh) * 2020-08-21 2022-02-22 华为技术有限公司 一种多链路通信方法、业务与链路映射的方法及设备
CN114340041A (zh) * 2020-09-29 2022-04-12 华为技术有限公司 数据传输方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200221545A1 (en) * 2019-03-20 2020-07-09 Robert J. Stacey Multi-link discovery signaling in extremely high throughput (eht) systems
CN113543243A (zh) * 2020-04-18 2021-10-22 华为技术有限公司 链路处理方法、多链路设备及计算机可读存储介质
CN113747502A (zh) * 2020-05-27 2021-12-03 华为技术有限公司 多链路试关联方法及相关装置
CN114079949A (zh) * 2020-08-21 2022-02-22 华为技术有限公司 一种多链路通信方法、业务与链路映射的方法及设备
CN114340041A (zh) * 2020-09-29 2022-04-12 华为技术有限公司 数据传输方法及装置
CN113573341A (zh) * 2021-09-23 2021-10-29 成都极米科技股份有限公司 协商业务与链路映射配置的方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN116801318A (zh) 2023-09-22

Similar Documents

Publication Publication Date Title
US20170055300A1 (en) Block acknowledgment mechanism
WO2020063108A1 (zh) 数据传输的方法和装置
US20050243755A1 (en) Method and system for adapting wireless network service level
WO2018201878A1 (zh) 承载配置确定、信息发送方法及装置、主基站和辅基站
US20240334239A1 (en) User equipment and wireless communication method for neural network computation
US12108340B2 (en) Wireless communication method using multilink and wireless communication terminal using same
TWI707595B (zh) 一種擁塞控制方法、終端及電腦可讀存儲介質
EP4156768A1 (en) Method, apparatus and device for negotiating traffic-to-link mapping configuration and storage medium
US20220240334A1 (en) Wireless local area network communication method and apparatus, medium, and electronic device
WO2022247879A1 (zh) 通信方法以及相关通信装置
WO2023174434A1 (zh) 数据传输方法、装置、芯片、芯片模组及电子设备
WO2023146994A1 (en) Buffer status report frame transmission in a multi-link communication environment
WO2022151431A1 (zh) 通信方法及装置
WO2022141301A1 (zh) 通信方法、装置和系统
CN114630368B (zh) 控制在多链路上进行数据传输的方法、装置、设备及介质
WO2023134607A1 (zh) 边链路传输方法及装置、存储介质、终端设备
WO2024007161A1 (zh) 通信方法及装置、电子设备及存储介质
EP4346315A1 (en) Buffer status reporting for triggered transmission opportunity sharing
WO2023212960A1 (zh) 扩展现实业务策略实现方法及装置
US20230156516A1 (en) Device, method, and system for transmitting low latency traffic
WO2024192738A1 (zh) 信道操作方法、装置、通信设备及存储介质
CN116980968B (zh) 一种多链路的数据传输方法和装置
US20220201537A1 (en) Session management method and apparatus
WO2023070377A1 (zh) 块确认会话删除方法、装置、多链路设备及存储介质
WO2021104384A1 (zh) Ftp上下行业务同传方法、系统、网络设备及存储介质

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

Country of ref document: EP

Kind code of ref document: A1